Known but not resolved. Even in the bug report that is mentioned in the thread that you quoted, the only response has been "things might have changed in cupcake". Of course determining what has changed, or if this specific problem has been fixed requires wiping the phone and installing cupcake*, whereas it seems like someone in the know could say "we fixed this", or "this is still the behaviour" and we could stop discussing this.
Jordan * If I haven't heard anything more about this by the end of the week, I will probably end up wiping and upgrading to cupcake. On Apr 17, 2:13 pm, Carter <[email protected]> wrote: > This is a known issue. > > See this > thread:http://groups.google.com/group/android-developers/browse_thread/threa... > > On Apr 17, 4:18 am, David Burström <[email protected]> wrote: > > > Hi Jordan, > > > I can only agree with your findings. Regardless of which lock is being > > used, the service stops sending callbacks as soon as the screen turns > > off or the power button is pressed. > > > :David > > > On Mar 16, 3:01 pm, Jordan Frank <[email protected]> wrote: > > > > A partial wakelock doesn't help because, as I have already explained, > > > as soon as the display goes off, the accelerometers go off. I can keep > > > the CPU awake, and my program continues to run when the display is > > > off. However, as soon as the display goes off, the accelerometers go > > > silent. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
