Hi Dianne, Thanks for your response.
How can I find out particular apps is able to watch the accelerometer. Please let me know if you have any pointers on this. Regards, Jagan On Sun, May 15, 2011 at 9:57 AM, Dianne Hackborn <hack...@android.com>wrote: > Make sure there aren't any apps watching the accelerometer. The platform > watches it while the screen is on to be able to know when to rotate the > screen. Other than that, I assume this is your build so you'll need to look > at what is going on. > > > On Fri, May 13, 2011 at 8:51 PM, jagan <402ja...@gmail.com> wrote: > >> Hi All, >> >> In my device, accelerometer sensor is keep on generating events, even >> in phone is in stationary. >> >> Due to this non-stop event generation my phone conserve more power in >> idle. >> [it operates at high frequency state (p-state)] >> >> With out accelerometer power consumption is quite well. >> >> Here is the getevent o/p for non-stop events: >> >> /dev/input/event1: 0003 0000 00000010 >> /dev/input/event1: 0003 0002 fffffeea >> /dev/input/event1: 0000 0000 00000000 >> /dev/input/event1: 0003 0000 0000000f >> /dev/input/event1: 0000 0000 00000000 >> /dev/input/event1: 0003 0000 00000010 >> /dev/input/event1: 0003 0002 fffffee8 >> /dev/input/event1: 0000 0000 00000000 >> /dev/input/event1: 0003 0000 0000000f >> /dev/input/event1: 0003 0002 fffffee9 >> /dev/input/event1: 0000 0000 00000000 >> /dev/input/event1: 0003 0000 0000000e >> /dev/input/event1: 0003 0002 fffffeea >> /dev/input/event1: 0000 0000 00000000 >> /dev/input/event1: 0003 0000 0000000f >> /dev/input/event1: 0003 0002 fffffee9 >> /dev/input/event1: 0000 0000 00000000 >> /dev/input/event1: 0003 0001 ffffffb1 >> /dev/input/event1: 0000 0000 00000000 >> /dev/input/event1: 0003 0001 ffffffb2 >> /dev/input/event1: 0003 0002 fffffeea >> /dev/input/event1: 0000 0000 00000000 >> /dev/input/event1: 0003 0000 00000010 >> /dev/input/event1: 0003 0002 fffffee9 >> /dev/input/event1: 0000 0000 00000000 >> /dev/input/event1: 0003 0000 0000000e >> /dev/input/event1: 0003 0002 fffffeea >> /dev/input/event1: 0000 0000 00000000 >> /dev/input/event1: 0003 0000 0000000f >> /dev/input/event1: 0003 0002 fffffee9 >> /dev/input/event1: 0000 0000 00000000 >> /dev/input/event1: 0003 0000 0000000e >> /dev/input/event1: 0003 0002 fffffeea >> /dev/input/event1: 0000 0000 00000000 >> /dev/input/event1: 0003 0002 fffffee9 >> /dev/input/event1: 0000 0000 00000000 >> /dev/input/event1: 0003 0000 0000000f >> /dev/input/event1: 0000 0000 00000000 >> >> Please let me know if you have any inputs on this issue. >> >> Regards, >> Jagan >> >> -- >> unsubscribe: android-porting+unsubscr...@googlegroups.com >> website: http://groups.google.com/group/android-porting >> > > > > -- > Dianne Hackborn > Android framework engineer > hack...@android.com > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. > > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
