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

Issue 670602 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
don't use this account. use chromiu...
Closed: Dec 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

[Generic Sensor] Cannot detect the Ambient Light Sensor on the device which has the sensor

Project Member Reported by wanming....@intel.com, Dec 2 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2937.0 Safari/537.36

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 "Ambient light" Sensor type, click "ADD" button
3. Turn on the switch button

What is the expected behavior?
1. The "Sensor state" should be "activated"
2. "timeStamp" and "illuminance" value shows

What went wrong?
1. The "Sensor state" is "errored"
2. No value show

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 56.0.2924.10 dev(64-bit)  Channel: dev
OS Version: Ubuntu 16.04
Flash Version: Shockwave Flash 24.0 r0

I compare the test results on the same device with Windows 10 platform, and it works fine on Windows 10, see the pictures in the attachment.
 
test1.jpg
134 KB View Download
test2.jpg
150 KB View Download
test3.jpg
123 KB View Download
Cc: aleksand...@intel.com mikhail....@intel.com
Owner: maksim.s...@intel.com
Cc: -aleksand...@intel.com alexande...@intel.com
Hi,

can you paste here the output of "udevadm info --attribute-walk --name=/dev/iio:device*" - instead of * put the ambient light dev node number. 

Thanks!

hi, we didn't install iio on the device.
Status: Assigned (was: Unconfirmed)
For record:

wanming.lin@ has provided me with all the necessary information I asked from him.

It turned out that a sensor with a name "als" has a file name or n attribute name
called in_intensity* instead of in_illuminance*. I've also asked him to provide me with a model name of the laptop.

Once I figure out what data that sensor provides and what math our platform code should do, I'll add a support for that sensor.

PS the sensor is identified as an ambient light sensor under windows platform.

Comment 7 Deleted

Comment 8 Deleted

Comment 9 Deleted

Status: Started (was: Assigned)
Project Member

Comment 11 by bugdroid1@chromium.org, Dec 19 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/1dcb638f139dd8557d992d81d40cbe5cc942887e

commit 1dcb638f139dd8557d992d81d40cbe5cc942887e
Author: maksim.sisov <maksim.sisov@intel.com>
Date: Mon Dec 19 21:29:51 2016

[sensors](CrOS/Linux) Add support for als sensor which has "intensity" naming.

This CL adds support for an als sensor that has "in_intensity_both_raw" naming.
What is more, frequency and offset file names are added as well.

Unittests were changed as well - there is no need to separately delete
a frequency file now in order to receive OnSensorReadingChanged event. A zero
value can be used which means "file must not be created"

BUG= 670602 

Review-Url: https://codereview.chromium.org/2571613003
Cr-Commit-Position: refs/heads/master@{#439571}

[modify] https://crrev.com/1dcb638f139dd8557d992d81d40cbe5cc942887e/device/generic_sensor/linux/sensor_data_linux.cc
[modify] https://crrev.com/1dcb638f139dd8557d992d81d40cbe5cc942887e/device/generic_sensor/linux/sensor_data_linux.h
[modify] https://crrev.com/1dcb638f139dd8557d992d81d40cbe5cc942887e/device/generic_sensor/platform_sensor_and_provider_unittest_linux.cc

Status: Fixed (was: Started)

Sign in to add a comment