[Jon Westfall]

Originally Posted by ChristopherTD

Jon

Thanks for posting this, I had enabled that tweak but lost it after a hard reset and couldn't remember where it had come from. Trying to find anything on XDA Developers is enormously difficult - just too much stuff to sift through.

I shall make a note of this for next time!

You're right - I've found that when it comes to XDA-Devs, if you find the information once - store it somewhere in your own files! Otherwise finding it again will be a nightmare! It's a great resource, but it really needs more organization!

[Jon Westfall]

Originally Posted by ChristopherTD

Jon

Thanks for posting this, I had enabled that tweak but lost it after a hard reset and couldn't remember where it had come from. Trying to find anything on XDA Developers is enormously difficult - just too much stuff to sift through.

I shall make a note of this for next time!

You're right - I've found that when it comes to XDA-Devs, if you find the information once - store it somewhere in your own files! Otherwise finding it again will be a nightmare! It's a great resource, but it really needs more organization!

[iPAUL]

This problem also plagues the Axim X51 (WM5) after applying Dell's A12 ROM update.

The registry edit worked to fix my X51v - Confirmed.

Thanks HUGE for posting this!!!

iPAUL

[welovejesus]

Jon,
Thanks a million for sharing this! It's best hack of the year IMHO. It will save many people from car wrecks :wink:

[zx9john]

Hey all - thank you for this thread (saved by google once again)...

Tell me - will setting the DWORD to 0 disable this feature completely?

It's driving me nuts (so bad i have a steering wheel on my crotch).

With my corporate authentication layer and SIM PIN i have 3 passwords to enter before i can use my damn phone sometimes.

[BoxWave]

I just caught up with this thread, a.w.e.s.o.m.e. Very happy to see the problem has been taken care of.

[zx9john]

hi guys,

I thought i'd post this up here as this registry mod wasn't working too well for me and some more google'n turned this up (from XDA-developers.com) and it fixed it good 'n proper on my atom.

"it is very simple registry hack. just go to hklm\security\policies\policies, look for name '00001023', and change the value to 1"

that allows you to go into Settings/Lock and change the time-out to 24 hours but the key will sometimes get reset back to zero...

one of the good ppl over at m*******today.com created a sweet little .cab that will monitor that key and change it back to 1 if the exchange server tries to overwrite the hack.

http://m*******today.com/forum/showt...8058#post68058

[martin_ayton]

On my WM5 Vario II (aka TyTn) I loved this hack. When I recently got my WM6 Vario III (aka Tilt / TyTn II), it was one of the first hacks I applied, however, there appears to be a problem with it on my machine at least:

If I apply the hack, it does sort out the password timeout on AC power issue. However, it also resets the password timeout on screen-off to zero. If I then go back in to the password settings to give myself a few minutes between the screen going off and having to enter my password again, then that action undoes the original hack. So... it appears that I can either have my PPC staying live and accessible when it's on AC power, or I can have it not needing a password instantly it goes to sleep (on battery power) or I turn it off, but not both at the same time.

Does anyone have a solution to this?

Cheers, Martin.

[Edited for clarity]

[eepyaich]

Originally Posted by martin_ayton

On my WM5 Vario II (aka TyTn) I loved this hack. When I recently got my WM6 Vario III (aka Tilt / TyTn II), it was one of the first hacks I applied, however, there appears to be a problem with it on my machine at least

I'm glad I'm not the only one - I upgraded my Vario II yesterday and have seen exactly the same problem! It feels as though there should be a different set of registry settings that do what we want, but I'm very nervous of trying other registry changes.

Anyone managed to solve this issue yet?