New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 718145 link

Starred by 16 users

Issue metadata

Status: Verified
Owner:
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression


Participants' hotlists:
Fixing-touch


Sign in to add a comment

"Auto rotate" doesn't work on Kevin device

Project Member Reported by songsuk@chromium.org, May 3 2017

Issue description

Chrome Version       : 59.0.3071.36
Platform             : 9460.24.0  

What steps will reproduce the problem?
(1)  fold the device into tablet mode
(2)  enable "Auto rotate" option
(3)  rotate the device to portrait mode

What is the expected result?
It should display in portrait mode.  

What happens instead?
The screen doesn't change to portrait mode. It display in landscape mode.

Please provide any additional information below. Attach a screenshot if
possible.
Works fine in Chrome 59.0.3071.25 / 9460.11.0 -kevin
Works fine in 59.0.3071.36/9460.24.0  - Cyan

 
Owner: zork@chromium.org
Status: Assigned (was: Untriaged)

Comment 2 by zork@chromium.org, May 5 2017

Owner: sammiequon@chromium.org
Sammie, could you look into this next week?

Comment 3 by wutao@chromium.org, May 11 2017

TOT does not work for kevin, elm.
minnie works.

Comment 4 by wutao@chromium.org, May 11 2017

Cc: wutao@chromium.org
It looks like it happened between 59.0.3071.25 and 59.0.3071.36, but I'm not 100% certain.
Cc: keta...@chromium.org
+ketakid@

I did some digging in and it seems like kevin does not have the accelerometer file, thus the display manager is not getting any rotations.
https://cs.chromium.org/chromium/src/chromeos/accelerometer/accelerometer_reader.cc?rcl=0762cfd079b91ff195345470c6253e9605716e0c&l=35

My other test device (caroline) does have this file. Would this be a firmware issue?
Cc: abodenha@chromium.org afakhry@chromium.org derat@chromium.org sammiequon@chromium.org gwendal@chromium.org osh...@chromium.org
 Issue 721379  has been merged into this issue.
Cc: -gkihumba@chromium.org adlr@chromium.org
+adlr@

adlr@ - Any thoughts on the root cause of this? Thanks!

Comment 9 by adlr@chromium.org, May 12 2017

Gwendal, would you know about rotation?
it is a duplicate of b/38189383, the bad cl (c/490847) landed in 9460.16.0/59.0.3071.31. 
Cc: briannorris@chromium.org
Status: Fixed (was: Assigned)
Should be fixed on 9460.38.0?
Labels: Merge-TBD
[Auto-generated comment by a script] We noticed that this issue is targeted for M-59; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-59 label, otherwise remove Merge-TBD label. Thanks.
Labels: -Merge-TBD
Fixes are merged as part of the aforementioned bug.
Status: Verified (was: Fixed)
9460.42.0, 59.0.3071.57
 Issue 723697  has been merged into this issue.
looks like it's broken again in:

61.0.3124.0 (Official Build) canary (32-bit)

9630.0.0 (Official Build) canary-channel kevin
Labels: -M-59 M-61
Status: Assigned (was: Verified)
(Feel free to open a new bug if the cause is different this time.)
I looked in chrome://system/ and under 'Sensor_info' there's a message saying:

cat: /sys/bus/iio/devices/iio:device*/*calibbias: No such file or directory
/sys/bus/iio/devices/iio:device*/*calibbias: 

Sounds similar to this older issue, if not, I'll open another issue. 
Owner: gwendal@chromium.org
Is this still happening? Assigning to gwendal@ since he fixed it first time around.

Comment 21 by willg...@gmail.com, Jun 21 2017

No, it worked again after updating to a newer build.
Status: Fixed (was: Assigned)
Closing based on #21.
Status: Verified (was: Fixed)
Verified on build 9686.0.0
 Issue 722582  has been merged into this issue.

Sign in to add a comment