Thanks Yusuf. That's helpful - I am very familiar with that
documentation. I was looking for something more though. I'm hoping to
see a more comprehensive discussion about this behavior. I need to
put together something for QA testers. No state can be left un-
described for what I need.
And
Hi Richard, sorry I really don't have time to go into detail on this stuff
at this point (and don't personally know enough to cover everything
anyway). Ultimately the source code -- in particular PowerManagerService
and the keyguard interactions as start in PhoneWindowManager -- is the
ultimate
O.K. I'll dive into PowerManagerService then - that's a good place to
look more into.
I agree this should be discussed on Android Porting as well. I'm just
more worried about how applications are affected for the moment.
But, I'll keep an eye on porting in the meantime. I imagine someone
One place to start is to learn about the PowerManager:
http://developer.android.com/reference/android/os/PowerManager.html
Yusuf Saib
Android
·T· · ·Mobile· stick together
The views, opinions and statements in this email are those of the
author solely in their individual capacity, and do not
Unless there is a third party app messing with you, there is something
broken with your software. The typical behavior is:
- Screen dims after the screen-off timeout sets in preferences, and then
turns off (and locks) a few seconds later.
- Screen turns off and locks with you press them end call
5 matches
Mail list logo
