App resets on boot and turns off, pattern lock delay doe not work and resets

[GoogleCodeExporter]

What steps will reproduce the problem?
1. rebooting the app
2.
3.

What is the expected output? What do you see instead?
It is expected that the app will require your unlock pattern once after 
reboot and then turn off your unlock pattern until timeout limit is 
reached.  What is happening is after reboot, the lock pattern is disabled, 
the app is disabled, and the timeout is disabled leaving an unsecured 
phone.

What version of the product are you using? On what operating system?
1.5 Android (Droid)

Please provide any additional information below.

Original issue reported on code.google.com by louma...@gmail.com on 11 Apr 2010 at 11:24

[GoogleCodeExporter]

You phone android 2.0 if it is a motorola droid.

The timeout is not designed to restart after boot (unless you have start at 
boot 
actually enabled in the main myLock settings), however the pattern lockdown is. 
Example - you tell the phone to reboot while myLock is enabled but the timeout 
hasn't gone off. When the phone reboots you should see the pattern screen, or 
potentially the regular unlock slider which when unlocked reveals the pattern 
lockdown screen.

Please post your log when the issue next occurs or email to me. This way I can 
investiage what is causing it to fail to initialize during your boot. We've 
experienced wavesecure and screebl boot startup interfering with the secure 
myLock 
startup.

Original comment by myLockan...@gmail.com on 11 Apr 2010 at 3:14

[GoogleCodeExporter]

I was not able to duplicate this issue. When the phone is restarted it starts 
up 
with the normal unlock screen, which remains for a few moments. When the boot 
handling in myLock startup occurs, it forces the password lock on, securing the 
phone. If you can provide a log I can determine if there is something 
interfering 
during your reboot.

Original comment by myLockan...@gmail.com on 11 Apr 2010 at 4:03

[GoogleCodeExporter]

I believe your issue was caused by an incidental reset of the preferences file 
due 
to the update for idle lock addon. I recommend to uninstall and reinstall the 
app to 
ensure the prefs file is saved correctly going forward.

I will take a few steps to reduce the chance of failures on reboot, as well. I 
will 
implement a checkbox you need to enable to indicate you use security pattern. 
If you 
have security and do not check the box, mylock will not work. If you stop using 
pattern security, uncheck the security mode so mylock will not try to reinstate 
it. 
This security mode checkbox will ensure that during reboots or unexpected 
process 
death we will stringently require the pattern setting to be enabled. 

Original comment by myLockan...@gmail.com on 11 Apr 2010 at 5:18

• Changed state: Started
• Added labels: Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by myLockan...@gmail.com on 12 Apr 2010 at 8:01

• Changed state: Fixed