[sensors] Receive null reading on a device with sensor supported |
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2935.3 Safari/537.36 Steps to reproduce the problem: Test Devices: HP EliteBook Revolve 810 and ThinkPad UltraBook S1 Yoga Test Platform: Windows 8.1 Enterprise Test case: https://honry.github.io/demo/tests/ambient-light/AmbientLightSensor_example.https.html 1. run test 2. check the console log 3. change the ambient light and rotate the device What is the expected behavior? sensor readings are reported correctly, and 'onchange' event is fired What went wrong? Ambient Light and Gyroscope sensors report null reading and 'onchange' isn't fired on HP EliteBook Revolve 810. Only Gyroscope sensor reports null reading and 'onchange' isn't fired on ThinkPad UltraBook S1 Yoga. It's odd, I am not sure if the problem is from my devices or the API implementation. But I am sure that my devices support the Ambient Light and Gyroscope sensor and there's no "NotFoundError" thrown. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 57.0.2935.3 Channel: canary OS Version: 6.3 Flash Version: Shockwave Flash 24.0 r0
,
Dec 1 2016
@wanming.lin -- The given url in comment #0 is opened as blank page . Attached screenshot for reference. Could you please check the URL and provide us the correct url , that may help in triaging the issue better. Thanks!
,
Dec 1 2016
,
Dec 1 2016
@hdodda, The url is correct, please check the console log to capture reading data.
,
Dec 6 2016
Steps to reproduce the problem: Test Case: https://generic-sensors.appspot.com/ Test Device: Dell Inspiron 13 7000 Series Test Steps: 1. Click the button at the top right corner 2. A popup shows, and choose the "Groscope" Sensor type, click "ADD" button 3. Turn on the switch button I found the state of groscope sensor is "activated", but no any value display on the screen(please refer to attachment "Windows 10.jpg"). It is work fine on Linux OS(refer to the "Linux.jpg").
,
Dec 6 2016
Besides, I run the test case on Windows 8.1 (HP EliteBook Revolve 810). The state of Ambient light and Gyroscope sensor is "activated". The value of timeStamp and x,y,z does not show on the screen.(refer to the comment Windows 8.1.jpg)
,
Dec 13 2016
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 14 2016
,
Dec 21 2016
,
Dec 21 2016
@wanming.lin I checked the test and there is a bug in it. Basically, sensor object goes out of scope and GC'ed. You can try rewriting the test by binding sensor object to a onchange function, then I think it would be fine.
,
Dec 22 2016
@alexander.shalamov, but the issue is still existed, see #5.
,
Jan 9 2017
@wanming.lin, #5 shows that sensor is successfully activated, but sensor reading is not yet available. On Windows platform, sensors will deliver new readings whenever there is a change. If you pick up laptop and rotate it, you will see that new readings are available.
,
Jan 10 2017
hi, @alexander.shalamov, the problem is that there's no new readings event if I rotate the devices(HP EliteBook Revolve 810 and ThinkPad UltraBook S1 Yoga), I am not sure if the problem is from my devices or the API implementation. But I am sure that my devices support the Ambient Light and Gyroscope sensor and there's no "NotFoundError" thrown.
,
Jan 24 2017
,
Jan 25 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/988f519584a682a2191c6ca72f91380f91d8166a commit 988f519584a682a2191c6ca72f91380f91d8166a Author: alexander.shalamov <alexander.shalamov@intel.com> Date: Wed Jan 25 07:25:31 2017 [sensors][win] Use angular velocity values for gyroscope sensor This CL aligns implementation of gyroscope sensor with the specification and uses angular velocity reading values instead of angular acceleration. Unit tests updated to verify changes. BUG= 669765 Review-Url: https://codereview.chromium.org/2648423005 Cr-Commit-Position: refs/heads/master@{#445974} [modify] https://crrev.com/988f519584a682a2191c6ca72f91380f91d8166a/device/generic_sensor/generic_sensor_consts.h [modify] https://crrev.com/988f519584a682a2191c6ca72f91380f91d8166a/device/generic_sensor/linux/sensor_data_linux.cc [modify] https://crrev.com/988f519584a682a2191c6ca72f91380f91d8166a/device/generic_sensor/platform_sensor_and_provider_unittest_linux.cc [modify] https://crrev.com/988f519584a682a2191c6ca72f91380f91d8166a/device/generic_sensor/platform_sensor_and_provider_unittest_win.cc [modify] https://crrev.com/988f519584a682a2191c6ca72f91380f91d8166a/device/generic_sensor/platform_sensor_reader_win.cc
,
Jan 25 2017
,
Jan 25 2017
Gyroscope issue is fixed, ambient light issue is not reproduceable. Please open new bug for ambient light sensor if you think that bug is not fixed.
,
Feb 7 2017
QA verified this issue. Gyroscope issue has been fixed.
,
May 4 2017
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ajha@chromium.org
, Nov 30 2016