Having updated to OS2.0 I have a problem with my Playbook not asking for a password when I wake it up or if I hit the new 'Lock' button, but it does still ask when I do a reboot.
Any one else had this problem or know how to fix it?
Thanks
I have the same problem.. Also, I notice that when charging, the screen will come back from standby by tabbing on any part of the screen and no password asking as well.. In fact, I faced the same problem in beta version but thought that it should be fixed by the official release. I did the wipe out but the issue is still here. If anyone knows how to fix this, it would be great.
I updated mine yesterday and it was mostly fine. I didn't set it to use a password. I use it at home.
This morning when I went to turn it on it asked for a password. I wasn't able to get in. I called support and they had me enter random passwords 10 times till it erased itself and started over. She indicated that this is a problem some people are having.
I'm having the exact same problem. Upgraded to OS2 on 2012-02-21 and everything was working fine. All of a sudden the screen lock does not work and my cameras (front and back) are not working.
I've rebooted, done a security wipe and reinstalled the OS using the BlackBerry Desktop software, the problem persists. The password lock only works after rebooting or when the PlayBook has been turned off and is turning back on. The cameras don't work. I either get a error message or a black screen.
Rim did change the behavior when charging. The pb will awake without the full swipe. But my password does kickin if I allow the correct time to pass. Screen timeout and password lock are two different timers.
As for the camera - warranty
Rim Support
Tel:
Canada Toll Free: 1-877-644-8405
United States Toll Free: 1-877-644-8410
Puerto Rico Toll Free: 1-855-651-4936
Email: [email protected]
(UK Support) 0800 096 2805
I am having the same problem and that is as of the last update. Before that my playbook was fine and now the the security lock does not lock unless i reboot the system. I see that this is a problem that has been happening for months. Have anyone gotten a fix for this?