WM6 Password issue

[nj_lee]

Hi All

I have searched on the forums for a bit of advice on this issue, and it seems to be a WM6 problem (some comments on other xda-dev device-specific forums but none i could find on the shift).

Every so often, my shift decides not to recognise my password, and therefore i need a hard reset. Not good after i spent all the time liberating it! This has happened twice now.

On xda-dev forums for other devices, they suggest you hold the 'on-off button' for 10 seconds after setting the p/w the first time, which will work around the problem. Unfortunately, the shift doesn't have such a button for the snapvue bit.

This seems to be a WM6 issue, which is made worse for the shift given the above issues (losing liberation, no on-off workaround).

Does anyone encounter this on their shift as well? I am surprised not to see it on the forum, so i hope i didn't miss anything. By the way, the solution 'don't use password' is no good for me, since to sync with my work server i must use one - and it comes on every 15 mins maximum without use!

I am intrigued also because i have a new HTC touch dual, and this p/w problem does not happen at all?

Odd. Any thoughts? Thanks all,

Nick

[nj_lee]

Hi all

sorry to bump this up, but I am just wondering whether the lack of replies since I posted this the night before I went on a job for a week is because of:

a) i am the only one who experiences this and thus noone knows how to fix it

b) anyone who does know has already posted to another thread i cant find?

Sorry to bug, just wondering.

Cheers, Nick

[pof]

Never had this issue in any wm6 device.

[Farsquidge]

Never had this issue in any wm6 device.

Same here..
Just an odd thought, are you using a long password? WinMo really only likes a 4 digit numerical PIN for password as it is a system originally designed for PDA's and enhanced for mobile phone use. Hence unlock via keypad.

[nj_lee]

Hi guys

thanks for that, no i am using a 4 digit password.

Interesting, it seems to have stopped since i wrote the first post, have taken it away on 2 major work trips and it's all good. However, i have not liberated it again yet. I think i am going to re-liberate it and see whether the issue happens again.

There are definitely postings on some of the other forums here on xda-dev, so it is a known issue, but maybe i am just unlucky....

N