Help PIN lock activates on landscape

[Fgoyti]

I think I have discovered a bug. I'm using ICS 4.0.3 on my S2 and I have PIN lock set to activate after 30 minutes. So, the screen dims after 15 seconds but PIN lock isn't activated until after 30 minutes. This works just fine if I have my phone in portrait mode....

HOWEVER... if I rotate my phone into landscape mode (such as in the browser, facebook, etc) *BEFORE* the screen dims, and then the screen dims, it ALWAYS goes into my PIN unlock. Immediately. Even though I have set it to 30 min.

I have tested this over and over and confirmed that it only happens when I'm in landscape. In portrait, it respects the 30 minute rule.

Please help! Am I missing something!?

 

[naith_kk]

What launcher are you using? From my ICS 4.0.3 stock rom, Samsung's TWLauncher's homescreen doesn't support landscape rotation... which is probably why the portrait rule applies, and fails at landscape.

If you have a custom launcher, perhaps it would be ideal to have it force display to portrait mode to ensure that the pin lockscreen takes effect.

 

[Fgoyti]

What launcher are you using?

I am using the default/stock launcher but I mean, go into an app that supports landscape, like the browser. So, open the browser and let the screen dim in portrait mode, no pin required. Then, put the browser in landscape mode, let the screen dim, and it asks for the pin!

 

[naith_kk]

Mine doesn't show that problem... so there's a possibility that your ICS may have a glitch. Is your phone ICS upgrade from GB? and did you do a factory reset? this thread explains why users encounter problems and need to factory reset to get their ICS working as it should on the S2.

 

[Fgoyti]

Yes but it's a new phone, I upgraded to ICS as soon as it was done charging. So no apps or anything yet. I'm surprised no one else has this issue.... maybe it is a glitch with just mine

 

[Fgoyti]

Just did a factory reset. Same problem.

 

[naith_kk]

Really sorry to hear you have that bug... but I can't seem to reproduce your bug from my handset, so I'm afraid I can't help much - perhaps another forumer might be able to assist you.