Issue metadata
Sign in to add a comment
|
DeviceOrientation stopped working in Android Chrome v65
Reported by
goo...@awe.media,
Mar 19 2018
|
||||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: Open this page in Chrome and wave the device around. https://threejs.org/examples/misc_controls_deviceorientation.html What is the expected behavior? You should see the scene move driven by the gyro. What went wrong? The scene does not move. Did this work before? Yes v64 Does this work in other browsers? Yes Chrome version: 65.0.3325.109 Channel: stable OS Version: 8.1.0 Flash Version: This is also raised in https://bugs.chromium.org/p/chromium/issues/detail?id=779443 but this issue is NOT limited to WebView's only. This is impacting the production/stable version of Chrome on Android. NOTE: The component this relates to should be Blink > Sensor but that seems to be missing from the list above.
,
Mar 20 2018
,
Mar 20 2018
Tested the issue using #65.0.3325.109 on Android Pixel XL 8.1.0 as per the steps mentioned in original comment. Somehow device orientation is working for me. Adding related component and CC'ing related dev from the above issue 779443 . CL: https://chromium.googlesource.com/chromium/src/+/b29ba0d062280291845dd8a5bd9dc052e439bbb5 @juncai: Could you please take a look at this and help. Thanks!!
,
Mar 20 2018
Which device are you using? Sensor behavior tends to vary depending on hardware. Does this work on the Chrome Beta or Chrome Dev channels? Beta: https://play.google.com/store/apps/details?id=com.chrome.beta Dev: https://play.google.com/store/apps/details?id=com.chrome.dev Please specify a precise version number when referring to the early release channels.
,
Mar 20 2018
,
Mar 20 2018
See comment here https://bugs.chromium.org/p/chromium/issues/detail?id=779443#c80 Tested on multiple Android devices including Pixels (1 & 2) Galaxy S7s, etc. Chrome stable 65.0.3325.109 deviceorientationabsolute doesn't work at all - deviceorientation does but very sluggish. Chrome Beta 66.0.3359.30 & Canary 67.0.3374.0 both have working deviceorientationabsolute but very sluggish and ugly 8(
,
Mar 20 2018
Hi google@awe.media, for Chrome Beta 66.0.3359.30 & Canary 67.0.3374.0, can you try the following website to see if the deviceorientationabsolute works? https://timvolodine.github.io/deviceorientation-test/ I tested the above website using Chrome Beta 66.0.3359.30, and Canary 67.0.3375.0 on Pixel 2, and the sensor data update frequency is good, and not sluggish.
,
Mar 20 2018
Hi, yep looks like you're right about it working ok in beta (66). I'm now getting about 59 updates/second for deviceorientation and high 40's per second for deviceorientationabsolute (while device is moving). Perhaps there were issues created by v65 in the background 8/ Attached are screengrabs from 65 (so you can see it's really broken there) and 66 to validate my data above. These were taken on a Pixel version 1 running Android 8.1.0 - one of the same devices tested during the initial testing for this issue. Thanks.
,
Mar 20 2018
Hi google@awe.media, thanks for testing that. The 65.0.3325.109 version is not working because the fix for the issue 805146 has not yet been merged to it. We are working on evaluating whether it is necessary to release a new version of M65 to all users. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by goo...@awe.media
, Mar 19 2018