On 05/19/2010 07:55 PM, Peter Eastman wrote:
After investigating this a bit further, I've determined that the
program is still running.  For example, if I set a Timer, that keeps
getting invoked.  It's just SensorEventListeners that don't get
invoked when the screen is turned off.  That's good to know, but
doesn't get me any closer to a solution.  Any suggestions for what I
can do?  Surely it can't be the intended behavior that it's impossible
to turn of the screen without also turning off all sensors.

We haven't got a straight answer about this, AFAIK. This works
fine on the G1, but doesn't work on the N1. If you search the
archives, I think that somebody said that it used to work on the
N1 as well but at some point it stopped working. If true, that
at least says that it's not a hardware issue. But who knows about
other platforms? I know that the iPhone behaves the same way,
so it's possible that it's a hardware related limitation on some
platforms. Pulling up the kernel sources maybe the only way to
settle this, and then only if the accelerometer driver is exposed.

Mike

PS: filing a bug on b.android.com is probably the right thing to do here.
if this is really an attempt to save battery, it's a poor implementation
      because the alternative is to keep the display on, which is grotesque

--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to