2.3 - reports of the quick unlock service closing unexpectedly over time

[GoogleCodeExporter]

Several users have experienced a stop of the service for no apparent reason, 
and have to re-enable it from widget or prefs. It has been able to be prevented 
by running in notification mode, this keeps the service protected from any 
system initiated memory-freeing shutdown. I am still investigating the official 
root cause, and have yet to be certain if it would impact all 2.3 users.

Original issue reported on code.google.com by myLockan...@gmail.com on 17 Feb 2011 at 5:59

[GoogleCodeExporter]

reports have come in from a large number of users for this issue. i am testing 
in the 2.3 emulator to identify what is causing the service to disable. it 
doesn't make sense as there are no changes to the services API in 2.2 to 2.3

Original comment by myLockan...@gmail.com on 25 Feb 2011 at 4:17

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

i just installed peter alfonso 2.3 for droid and will commence testing to find 
why this is supposedly happening on all 2.3 setups

Original comment by myLockan...@gmail.com on 25 Feb 2011 at 5:42

• Added labels: Priority-Critical
• Removed labels: Priority-High

[GoogleCodeExporter]

successfully duplicated issue on this 2.3 rom. what i know so far:

the service is still alive according to system running services
we aren't getting any screen events or activity from the service (thus no quick 
unlock)
the pref screen cannot locate our binding to the service (so it treats it like 
the service hasn't been started)
widget click recognizes the bind and tries to turn off quick unlock, but that 
causes a NPE force close, presumably because the bind is actually null.

Original comment by myLockan...@gmail.com on 25 Feb 2011 at 8:24

[GoogleCodeExporter]

log confirms that the issue was a death of the process. there is no indication 
why it died. status notification (foreground) mode would prevent issue.

the system successfully restarts the service 5 seconds after the death, but the 
problem is that it seems to be sitting there in a started but not actually 
calling onStartCommand which gets everything going. the other issue is that 
there is no binding. we need to implement something that recognizes this system 
restarted case which launches an intent to Toggler to get a proper bind in the 
new process.

Original comment by myLockan...@gmail.com on 25 Feb 2011 at 8:28

[GoogleCodeExporter]

the solution is to implement an intent so that the service will know it has 
been started by toggler. that intent will be absent as we use the stick service 
mode when system is recreating it. in onCreate for the service, we can check 
the intent. if it is our toggled intent, proceed as normal. if it is null, 
schedule a toggler call and call stop on ourself so we can be properly started 
through toggler.

Original comment by myLockan...@gmail.com on 25 Feb 2011 at 8:30

[GoogleCodeExporter]

i have tested a fix that worked and updated in the market

Original comment by myLockan...@gmail.com on 26 Feb 2011 at 4:03

• Changed state: Fixed

[GoogleCodeExporter]

i have tested a fix that worked and updated in the market

Original comment by myLockan...@gmail.com on 26 Feb 2011 at 4:03