Ping. Someone please reply with the status of this issue so that we can figure out how to work around it, or when it might be fixed. I am sorry, it is a huge issue for us, and I have not been able to get any additional information.
Thank you, Artem On Thu, Jan 14, 2010 at 10:36 AM, BGA <[email protected]> wrote: > So I went ahead and did some further testing using a Motorola > Milestone and here are my results: > > 1 - My workaround, as mentioned by Artem, works with it. In other > words, re-registering the sendor listening in stand by mode makes the > sensor works again. > 2 - Acquiring the dim lock after the screen goes off (also as > described by Artem) does not work with it. On the plus side, the > screen does not turn on when you acquire it. ;) > 3 - The HTC Tattoo screen turning on when acquiring the dim lock seems > to be a bug on it. The documentation clearly states that the screen > will not turn on when you do that unless you explicitly ask for it by > also using the ACQUIRE_CAUSES_WAKEUP flag. > 4 - All HTC phones (except for the G1) seem to shut down the > orientation sensor (at least) completely when entering standby mode. > > As a bonus, I also noticed the following: > > 1 - On the Motorola Milestone, there is no need to hold a CPU lock in > the service. Somehow it works without that (and it does not drain the > battery it seems). > 2 - The G1 does not shut down the orientation sensor as, as long as > you hold a CPU lock, you still get orientation changes when in > standby. > > To me it looks like phone manufacturers are doing whatever they want > concerning this subject. This is either because what is supposed to be > done is not specified or because they are simply not following the > specs. This ends up becoming a nightmare for developers and, for > obvious reasons, this is not a good thing. > > I am not sure what can be done to sort this up but it seems that, at > the very least, a way to say "I want to use this sensor even in > standby mode" would solve most of the problems (as long as device > manufacturers would abide to this). > > -Bruno > > > On Jan 14, 12:42 pm, Artem - WorkSmart Labs <[email protected]> wrote: > > Hi Dianne and other Android Team Members, > > > > Please provide some kind of comment on this long-standing and serious > > bug: > > > > http://code.google.com/p/android/issues/detail?id=3708(one of top > > bugs right now) > > "OnSensorChanged() is no longer called in standby mode since last > > Firmware upgrade" > > > > A lot of serious developers have looked at this, and we can't seem to > > find a good solution that works for example on the HTC Hero. The best > > work on this done by Bruno unfortunately still does not work for many > > handsets. I have looked into this carefully, but the issue seems very > > hard to track down. I can repro this on the HTC Tattoo as well. The > > only work-around seems to be to intercept the ACTION_SCREEN_ON event, > > and then to again re-grab the DIM_SCREEN lock, which causes the screen > > to turn on again. This unfortunately drains the battery like mad. > > > > The latest comment on this (from Dianne) said we have to hold a > > partial wake lock, however we are all already doing this and this does > > not help. > > > > This breaks all pedometer and similar applications right now, and our > > users are really sad. > > > > Please please help, or at least comment on the status. > > > > Artem > > -- > 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]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en >
-- 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
