jsn7033 / mylockforandroid

Automatically exported from code.google.com/p/mylockforandroid
0 stars 0 forks source link

Failure to properly wake up occasionally (a3) #14

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Press power or any keypad button swiftly
2.
3.

What is the expected output? What do you see instead?
It seems the OS has an issue and ignores our wakeup at times. It most often 
duplicates immediately after a deliberate power key sleep. Other times we 
simply get no response to a press (however under the hood the wakeup and 
unlock has been executed by the OS has sent itself to sleep before anything 
was visible). Other times you see it come on then go dark again. You can 
always avoid the issue by pressing and holding the key for a slightly 
longer amount of time, then releasing. It appears to be a power manager bug 
that we sidestep in the timing. It will never occur if stay awake mode is 
left on.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by myLockan...@gmail.com on 30 Jan 2010 at 6:26

GoogleCodeExporter commented 9 years ago
Eliminated most causes of the inconsistent behavior here. remaining cause 
appears to be 
in the timing of a wakeup from a prolonged dormancy, the key event gets dropped 
on the 
floor before we have a chance to finish resuming to handle it. i'm testing a 
fix in 
which we hold a cpu wake lock, meaning that long dormancy will never cause a 
full cpu 
sleep. i am testing it because i am wary it might cause a power drain. 

Original comment by myLockan...@gmail.com on 4 Feb 2010 at 7:38

GoogleCodeExporter commented 9 years ago
Fixed by telling the CPU we want wake priority. Since we perform no perpetual 
function 
it does not impact any battery usage, we just retain dormant CPU "attention" 
which 
allows our key wakeup to always get handled as expected.

Original comment by myLockan...@gmail.com on 16 Feb 2010 at 5:20