02-26-2011 1:07 PM
Just updated my captivate to Froyo. Now, every time the screen times out, I get a pin lock to be able to access the phone again. I have MS exchange server. Our admin has set the pin lock to 30 minutes. Having to unlock the phone after 10 seconds is a total pain in the butt!!!!
Anyone know how to fix this?
Solved by: Go to Solution.
02-26-2011 6:23 PM
Unfortunately that's how Froyo works. You can:
1. Buy a 3rd party software to sync with Exchange.
2. Hack the phone to use a special Email.apk that bypasses PIN policy. Your IT admin probably won't be too thrilled to hear that.
- edited 02-28-2011 8:02 AM
Yes, this is very frustrating. On 2.1, you could configure a pattern-lock in addition to your corporate PIN. And, mine also only asked for the corporate PIN if off >30 min. On 2.2, if corporate is enforcing a PIN, you have no option to also configure a pattern-lock. Maybe because there is no backup locking, the corporate PIN is always asked for.
I use Easy Profiles that allows an option to disable locking. That is no longer working on 2.2, but is being investigated (I believe) by the developer. Disabling the locking *does* work inside of BeyondPod, so there must be a way to still do it on 2.2 (Of course, once you venture outside of BeyondPod, you're asked for your PIN).
Do you have a name for the alternate software for Exchange Syncing?
- edited 02-28-2011 8:58 AM
TouchDown is the only full blown Exchange sync that works correctly with the PIN requirement because it does not use Froyo OS PIN management. I tested it and it works on Froyo.
I don't really like to use TouchDown, not because of its cost ($$), but because of its lack of integration with the OS. The contacts and calendar are contains within the app itself, not integrated with phone contacts and calendar. The UI looks like stuck in old PocketPC mode.
If you read Google's Froyo seucrity statement for Exchange PIN lock, it suggests that you set your screen timeout to match your Exchange server requirement, e.g. 30 minutes. This of source will have significant impact on battery usage.
My old Windows Mobile phone had this same issue after WM 6.xx update. I kind of learnt to live with it.