W3C home > Mailing lists > Public > public-device-apis@w3.org > May 2012

Re: Device light and proximity sensor

From: Doug Turner <dougt@mozilla.com>
Date: Wed, 9 May 2012 12:29:17 -0700
Cc: Niklas Widell <niklas.widell@ericsson.com>, Robin Berjon <robin@berjon.com>, "public-device-apis@w3.org public-device-apis@w3.org" <public-device-apis@w3.org>
Message-Id: <AB5857D6-E439-49B8-A541-192146A4ECC7@mozilla.com>
To: "SULLIVAN, BRYAN L" <bs3131@att.com>
We implemented device orientation, device motion, device proximity, device light in Firefox for Android.  You can take a look there?

On May 9, 2012, at 12:26 PM, SULLIVAN, BRYAN L wrote:

> Yes, given an implementation I could create a test. But it might take someone with device-level debugging tools to draw accurate data from the CPU and/or battery status. So an OEM or platform vendor would be better to run specific tests on their platform(s). It could also vary by platform, per the implementation approach, so I donít think a limited test sample would be conclusive.
> Thanks,
> Bryan Sullivan
> From: Doug Turner [mailto:dougt@mozilla.com] 
> Sent: Wednesday, May 09, 2012 12:21 PM
> Cc: Niklas Widell; Robin Berjon; public-device-apis@w3.org public-device-apis@w3.org
> Subject: Re: Device light and proximity sensor
> On May 9, 2012, at 12:18 PM, SULLIVAN, BRYAN L wrote:
> But in both cases, my main concern is the delivery of superfluous events, which I believe would cost in terms of CPU battery etc (I don't have actual test results to validate that assertion).
> This is an important concern, and we should test it to see what energy difference it can make.  Will you be willing to run that experiment?
> Doug
Received on Wednesday, 9 May 2012 19:29:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:46:08 UTC