Motorola Droid Update Continues Through Sept 4

[Hiker5208]

The 22D update just turned on security settings that should have been there all along really. You are right about it being for the work email. It caught me by surprise and I am a PC tech with some exchange experience. I went to the connect the dots pattern rather than the PIN, just seems a bit easier to me. Only the Exchange admin at your work can undo it to the best of my knowledge and I doubt any of them will do it.

I got the update this morning. Now it forces me to put in a PIN every time I want to use the phone. I assume this is due to the fact that I receive my work e-mail on the Droid. I get why we should use the PIN but I hate it. Is there any way to bypass it? I've tried & even called Verizon. The reps I spoke with seemed to have never heard of this. My previous AT&T phone had it too and it was even more cumbersome than the one on the Droid.

[badog]

It's not really an exchange problem, it's a bug in the 22D update. It doesn't fully understand what the exchange policy is set to. Meaning if the exchange policy is disabled, (or requires a password/pin of 4 digits or less) 22D still forces you to enter 4 digits. The 22D update requires a 4 digit pin/password no matter what. The only time it will make a difference is when the policy is set to more than 4 digits. There are policy settings to force a pin or a password. That will change the phone display to either a number pad or a full keyboard display, but still requires at least 4 digits/characters no matter what...exchange policy enabled or disabled.

I've done extensive testing on our corporate exchange servers (we have over 60,000 users on exchange, so it's not just a home server I hack around on). I have tested this on 2003 and 2010, they both do the same.

yea for updates

[dwoid]

Interesting... I've been running metiCkOne's odexed rooted busyboxed (Google's) FRG22D over (OTA's) FRG01B for the last few days, and have been receiving plenty of emails from my work's Exchange server. Yet I don't have to use either a pin or a password to access my Droid at all.

I have to wonder if there's some difference between Google's FRG22D patch and the actual OTA FRG22D patch...

That or since my Droid is rooted, perhaps there's an internal permission difference.

Access to my Droid has remained the same under this release of FRG22D as it has always been has under 2.0.1 and 2.1, just swipe to get in (unless you specifically turn on security).

It's not really an exchange problem, it's a bug in the 22D update. It doesn't fully understand what the exchange policy is set to. Meaning if the exchange policy is disabled, (or requires a password/pin of 4 digits or less) 22D still forces you to enter 4 digits. The 22D update requires a 4 digit pin/password no matter what. The only time it will make a difference is when the policy is set to more than 4 digits. There are policy settings to force a pin or a password. That will change the phone display to either a number pad or a full keyboard display, but still requires at least 4 digits/characters no matter what...exchange policy enabled or disabled.

I've done extensive testing on our corporate exchange servers (we have over 60,000 users on exchange, so it's not just a home server I hack around on). I have tested this on 2003 and 2010, they both do the same.

yea for updates

[badog]

I think you are right about a difference in updates. I rooted mine (stock) to test it out and it didn't make a difference. I'd say their is definitely a difference between Google's FRG22D patch and the actual OTA FRG22D patch. Receiving mail works fine, it's the password/pin policy that it doesn't understand.

[Snoking]

I think you are right about a difference in updates. I rooted mine (stock) to test it out and it didn't make a difference. I'd say their is definitely a difference between Google's FRG22D patch and the actual OTA FRG22D patch. Receiving mail works fine, it's the password/pin policy that it doesn't understand.

Are you talking about a difference between the rooted FRG22D and the OTA FRG22D??? As I believe that manual non-rooted FRG22D and the new OTA FRG22D are the same 1.6MB file. Chris

[badog]

No, I'm talking about the other rooted ROM's that are out there. The OTA frg22d and the leaked google version are the same and have the same issues.

[Snoking]

No, I'm talking about the other rooted ROM's that are out there. The OTA frg22d and the leaked google version are the same and have the same issues.

So are people reporting this issue with exchange severs to VZW?

Chris

[badog]

I'll be calling today or tomorrow. I've been waiting until phones started officially receiving the ota update.

[mthokie21]

Still waiting for the update...and my laptop died 5 days ago so all I have is my Droid.

[dwoid]

Worth mentioning, the FULL release of the FRG22D OTA (not the patch release) has been captured from an actual Verizon push and is being discussed here:

OFFICIAL FRG22D OTA patch is here. DOWNLOAD NOW!