search

KIRANBHAT / mylockforandroid

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

mylock will not display pattern unlock screen at boot. #28

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Uninstalled and reinstalled mylock.
2. Set pattern lock and enabled status icon.
3. Rebooted Droid.

What is the expected output? What do you see instead?
Expected to display pattern unlock screen at boot.

What actually happened was Droid can be unlocked by simply sliding on 
unlock screen after reboot(no pattern unlock screen).

What version of the product are you using? On what operating system?
1.3.4a     Droid Version 2.1

Please provide any additional information below.
I followed instructions on issue 27 without any luck.

Original issue reported on code.google.com by louma...@gmail.com on 15 Apr 2010 at 4:28

GoogleCodeExporter commented 9 years ago 
By the way -  Since myLock is an app and not part of the firmware, we have to 
wait 
for the system to perform several boot tasks before it notifies us of the boot. 
Therefore you will always see the non-secure lockscreen first. It doesn't 
display the 
pattern screen as the very first screen.

If the phone is displaying the non-secure and awake, you will see it cancelled, 
then 
restored with secure. If you unlock that, when myLock starts it will force the 
screen 
to shut off, restoring the pattern lock screen. if the screen is asleep, next 
time 
you wake it the pattern will be required. These are the handling myLock will 
follow 
if it successfully loads and sees your security preferences at boot.

If you find it never forces the screen off after unlocking the non-secure 
lockscreen, 
you may have too many things trying to load at boot. If you can send me a Log I 
can 
then recommend additional solutions as to why you are hitting low memory during 
boot, 
causing myLock startup to fail.

Original comment by myLockan...@gmail.com on 15 Apr 2010 at 2:23

GoogleCodeExporter commented 9 years ago 
So to summarize - I believe that the boot startup from myLock might be getting 
killed 
by the system if you hit a low memory during boot. Try 1.3.4b and see if it 
will 
force lockdown as expected. Then I will need logs if it does not. You should 
see 
myLock appear in status bar for a moment before it executes the lockdown.

There is no way for myLock to make the system show the secure lock as the first 
screen shown, because the system boot's first operation is to display the 
lockscreen 
and will be in non-secure mode at that moment.

Unless there is some way myLock can get a notification that the system is 
shutting 
down and restore security during that- if so we could prevent this in reboot 
scenarios but still not help if battery pull restart is done.

Original comment by myLockan...@gmail.com on 15 Apr 2010 at 2:36

GoogleCodeExporter commented 9 years ago

Original comment by myLockan...@gmail.com on 1 May 2010 at 5:43