I think I found a fix for a problem that a couple of people have reported on this thread with the password lock feature.
I used to use a simple sequence of numbers for my phone lock, since the lock was turned on by my exchange server's policy, and not by myself. (In other words, the security was important to my email admins, not really to me -- I don't work in a sensitive area of the company.)
I haven't verified this, but I think that using the same sequence on this ROM, caused me to not be able to "log in" to the phone after a reset, since the Unlock button (softkey 1) didn't respond, and neither did the corresponding screen tap.
After a hard-reset to get back in, I noticed that the Lock settings panel complains if you try to enter a code like 0000, the device complains that this is too simple a code, and to choose something harder to guess. (I'm paraphrasing.)
I think the problem was that I'd used a simple code like this when I initially set up the device, and then later after I connected to my exchange server, the policy changed such that the code I'd used was no longer allowed. But instead of letting me in with the invalid code, and then requiring that I change it, I simply got locked out of the device.
Now it may be the case that I can use OWA (on my company's exchange server) to reset my device's lock code, but I didn't get that far, since I tried a more complex code after resetting the device, and didn't want to reset again to re-test.
It may also be the case that I've completely made up the cause above, based on a quirk of timing, and rather than helping anyone by debugging this, I'm just confusing the situation.
Fortunately at least, I'm one of only a couple of people who have had this problem, unless it's become a much bigger issue across say the last 100 or so posts on this now totally mammoth thread.
