Database Info

Backlight turn of after 10 sec

Hello,
My phone turns of the display after 10 sec.
It reacts on a keypress but it is very anoying.
Are there more people with this problem?
I think it comes from a program called Automatic Keylock but it won't go away when i Uninstal this program.
I think it must be in the register somewhere but it's not in the controlpanel/power.
Any suggestions?
MAybe a dll?

aage said:
I think it must be in the register somewhere but it's not in the controlpanel/power.
Click to expand...
Click to collapse
Go to HKEY_CURRENT_USER/ControlPannel/Power/ then LeftClic to Values, If you have Display clic in it to see and modify the value, if not:
RightClic, New Value/DWORD/ name it Display; put 60 in the Value Data, Baseecimal .
Cheers.

Wow This Works!!!
Thanks This Was Driving Me Crazy.
This Is So Nice , Great!!!
You Are A Hero

you dont need to edit registry!!!!
it is in start->settings->power management
you can control how long it takes for the backlight to go off and the display to switch off seperately for on battery and on ac
aage said:
Wow This Works!!!
Thanks This Was Driving Me Crazy.
This Is So Nice , Great!!!
You Are A Hero
Click to expand...
Click to collapse

flykthewiz said:
you dont need to edit registry!!!!
it is in start->settings->power management
you can control how long it takes for the backlight to go off and the display to switch off seperately for on battery and on ac
Click to expand...
Click to collapse
If you have started to use CorePlayer/TCPMP and/or TomTom, then you NEED to edit the registry, as the value in the "delay before backlight will turn off" is modified to a billion number instead of 60 seconds.
Off course it's in the settings , power management....

But that wasn't aage's problem!!!
I use tomtom but I have created a script using mortscript that runs tomtom then deletes that pesky reg key. That way the power management still works
KevinSephiroth said:
If you have started to use CorePlayer/TCPMP and/or TomTom, then you NEED to edit the registry, as the value in the "delay before backlight will turn off" is modified to a billion number instead of 60 seconds.
Off course it's in the settings , power management....
Click to expand...
Click to collapse

KevinSephiroth said:
If you have started to use CorePlayer/TCPMP and/or TomTom, then you NEED to edit the registry, as the value in the "delay before backlight will turn off" is modified to a billion number instead of 60 seconds.
Off course it's in the settings , power management....
Click to expand...
Click to collapse
Not true for me. I use TT6.0.0 and CP and I don't have to make any reg change whatsoever.

How did you get tt6 loaded and running. and are you having the reported problems not being able to navigate the menus/selection lists with the dpad.
The problem kevin reports is with ttn5 mobile (which sadly is the only wm smartphone version that tomtom support - "support" that is a strange word when used in the same sentence as tomtom!!!)
jockyw2001 said:
Not true for me. I use TT6.0.0 and CP and I don't have to make any reg change whatsoever.
Click to expand...
Click to collapse

thnx it worked

flykthewiz said:
ttn5 mobile (which sadly is the only wm smartphone version that tomtom support - "support" that is a strange word when used in the same sentence as tomtom!!!)
Click to expand...
Click to collapse
LOL
Yeah I was referring to this one, since you're not supposed to use TT6 (intented to be used with PPC) , but here everyone use custom app/rom
BTW, I never used TT, just CorePlayer, and though it worked fine for some days, one day it refused to turn off backlight, so I created this registry dword and voilà !

Question
never mind

[Hack] FULLY disable automatic screen rotation

I've come to notice that no one REALLY knew how to fully disable screen rotation on WM devices.
Some offered 3rd party apps to get the job done, some only knew how to disable automatic rotation, but when the device went into standby and woke up again - the screen rotated back. So that didnt really work.
So if you're as desperate as i was about screen rotation,
this is what you need to do:
1. Get dotfred's free taskmanager HERE, and run it.
2. Go to "Devices" tab, and look for "MIS1:" device (oem_misc.dll)
3. Long-Tap on it, and tap on "Stop"
4. Long-Tap on it again, and now choose "Set Manual"
EDIT: This should be enough. try flipping your screen/sliding your keyboard and see if the screen changes orientation.
Now put your device on standby, and turn it on again. If orientation stays the same - you're done. If not - try steps 5-7, although they seem to be irrelevant.
5. Go to "Notifications" tab, and look for "Notifications\NamedEvents\VCPowerWakeupEvent"
6. Tap on it to make it selected
7. Disable it
(In dotfred's taskmanager, there should be a button for disabling it, but for some reason some devices couldn't see the button icons, although the buttons are still clickable. Under the notifications list there is an empty light-blue line - the buttons are there, eventough you can't see them.
The disable buttons is somewhere i the middle of that light-blue line, just tap the center until a message box popps up and asks if you'd like to disable this notification - Tap on yes.)​All those steps are a one time deal - they stick even after an SR.
This has been tested on htc universal and works great.
The screen will keep its orientation even if you flip your screen, take out your built in keyboard, or turn the device off and back on.
The only time your screen will revert back to the original orientation is when you soft reset your device.
Hope this helps

So now, if you need something to help you rotate your screen on demand, you could use this small app that i've made.
its called ScreenRotate.exe (naturally), and you use it like this:
usage: ScreenRotate.exe <command line argument>
0 : Rotete to angle 0
90 : Rotete to angle 90
180 : Rotete to angle 180
270 : Rotete to angle 270
CW : Rotate clockwise
CCW : Rotate counter-clockwise
MIRROR : Mirror the current angle
If nothing will be specified at command line, nothing will happen.
.NET CF 2 is needed.​
I really recommend using it along with FTouchFlo.
This way, to rotate the screen manually, you just need to drag your finger the way you want the screen to be shown, from top to bottom.
I find it quite comfortable while driving...
Those are the changes you'd need to change in FTouchFlo to make it work with ScreenRotate:
DownUpApp:\Program Files\FTouchFlo\ScreenRotate.exe
DownUpAppCmdLine:mirror
LeftRightApp:\Program Files\FTouchFlo\ScreenRotate.exe
LeftRightAppCmdLine:cw
RightLeftApp:\Program Files\FTouchFlo\ScreenRotate.exe
RightLeftAppCmdLine:ccw​

Thank you so much... I have been looking for this for sooo long.
This is the perfec way to make it stick in either Portrait / Landscape.
There have been many users such as myself who have wanted our devices to stay in landscape and this is the perfect hack.
Thanks again... Cheers
BTW -> Tested and works on my Hermes
Just added it to the Hermes Wiki (Can be found under regisrty tweaks although it's not a reg tweak)

happy to hear that!
you're welcome mate.

I have a tytn hermes with satin black and in the notifications tab there isn't any notification named "Notifications\NamedEvents\VCPowerWakeupEvent". I have searched in the notifications tab in task manager and also in the notification queue in memaid. So when i soft reset the device everything goes back where it was (auto rotate screen). Any help? Thank's
EDIT: It is working perfectly even without this notification. I just tested it. So everything OK! ThanX again

zalaros said:
I have a tytn hermes with satin black and in the notifications tab there isn't any notification named "Notifications\NamedEvents\VCPowerWakeupEvent". I have searched in the notifications tab in task manager and also in the notification queue in memaid. So when i soft reset the device everything goes back where it was (auto rotate screen). Any help? Thank's
EDIT: It is working perfectly even without this notification. I just tested it. So everything OK! ThanX again
Click to expand...
Click to collapse
actually, you're right.
i guess the notification has nothing to do with it,
i don't remember what made me think it does.
i'll edit the hack accordingly.
thanx zalaros

Unfortunatelly I have found 2 bugs. I have a tytn hermes with black satin medium installed. The first bug is that with mis1 unloaded the device can not connect with the pc anymore. When I plug the device it is just being charged but active sync won't open at all. The second bug is that I can not load mis1 again. No matter what I have tried the device mis1 won't be loaded again if I had unloaded it. Any ideas?

Ok i found a way to reload this specific device (mis1).
1. Run taskmanager.
2. Go to "Devices" tab, and look for "MIS1:" device (oem_misc.dll) (it is unloaded if you have done everything described on the 1st post)
3. Long-Tap on it, and choose "Set Manual"
4. Long-Tap on it again, and choose "Set Automatic"
5. Soft reset your device

zalaros said:
Unfortunatelly I have found 2 bugs. I have a tytn hermes with black satin medium installed. The first bug is that with mis1 unloaded the device can not connect with the pc anymore. When I plug the device it is just being charged but active sync won't open at all. The second bug is that I can not load mis1 again. No matter what I have tried the device mis1 won't be loaded again if I had unloaded it. Any ideas?
Click to expand...
Click to collapse
I have the same syncing problem

Doesn't seem to work on my Tilt/Kaiser-Dutty 6.0..
Any other ideas?

redlynr said:
I have the same syncing problem
Click to expand...
Click to collapse
Just solved!
The ActiveSync troubleshooter (menu: Help/Troubleshooter for ActiveSync) offered to clear the "Enable advanced network functionality" check box. While trying to do that, an error message "Failed to disable RNDIS ..." was popping up every time. As per this suggestion, I removed virtual COM ports from Bluetooth settings and then it was possible to clear that check box.
Immediately thereafter ActiveSync woke up on the PC and offered to create a new partnership (because I deleted everything in frustration earlier). No problems for half a hour.
Then I left the administrator account and logged on as the usual limited user. ActiveSync again was unable to connect until the advanced functionality check box was restored. Does it seem that those both accounts will require different settings? Dunno, I haven't checked yet.

On my Wizard, with the TNT Rom (August 08), I don't see the device MIS1, and I don't see the event in the TaskManager.
Any ideas how to disable screen rotation, when I slide the keyboard?
Thanks in advance

Sprint HTC Touch Pro ROM 1.03.651.4
The MIS1 solution did not work for my phone (Sprint HTC Touch Pro ROM 1.03.651.4), but I found that this does:'
HKLM\System\GDI\Rotation\CamAppActive = 1
Presumably the device thinks the camera is active and thus doesn't rotate the display.
Obviously this will return to 0 after soft reset, so I used TaskMgr 2.9 to export the entry, then added a startup shortcut to import this entry with the /silent flag.
UPDATE: This fix interferes with data entry in Opera. When I try to type into a google search box, I get one character, the box looses focus, and I gotta tap on it again to type any more. Severely annoying. Goes back to normal when I change CamAppActive back to 0, and close and reopen the keyboard. I may make an exe to toggle or just make two reg import shortcuts.

Way cool!
Works for me too on a Kaiser, with old Dutty ROM.
How in the world did you figure it out? Look at that key?
Thanks, Jeff

It made perfect sense, but admittedly I tried changing everything under "Rotation" before I tried that one.
Item #21 on this list clued me into that area of the registry:
http://forum.xda-developers.com/showthread.php?t=398265

El Zilcho.
Bupkis. I've been knocking my brains out trying to disable autorotation, but still have manual enabled. (I've got some apps that play nice only in landscape, and some only like portrait. Also, I'd like to be able to slide my keyboard out really quick-like to enter some quick text, then slide it back w/o messing with screen orientation.) I tried the MIS1 disable, but no-go for me. Also tried messing with the Rotation entries, specifically the SlideKey key, but apparently that value is volatile and changes with each slide. Oh well! Unless there's a way to lock the SlideKey value so it can't be changed, that'd fix my issue. Hmm.
EDIT: Forgot to mention. I've got the Tilt (8900 I guess?) with vanilla OEM 6.1 ROM, modded only for no-bloat. (Did the old battery trick after reset/reinstall to prevent bloatware.)
EDIT: After I typed this up, figured I'd try using Settings>Screen (or somesuch) to just fix perspective. Still auto-rotates. KaiserTweak and Advanced Config can't get it to stick on one or the either, either. Editing registry turns up same results. Settings right now say it's fixed at 0 degrees but it still autorotates.
Late-breaking edit, 14-JUN-10: Got rid of it a few months ago anyways, moved to a Rhodium. No D-pad, so no more worries about those games that didn't like rotation, as they needed the D-pad to work anyways, and the TP2 doesn't have one.

Doesn't work on touch pro 2
http://forum.xda-developers.com/showthread.php?p=5928161#post5928161
That's what I resorted to!

Wow
Wow, pretty hard core fix! On the Sprint Touch Pro 2 Stock 6.1 my reg entry above only works to prevent rotation when the keyboard is slid out, it will not help with the autorotation provided by the sensor. I however put together some .reg files, with my perceived essential fixes including disabling sensor rotation:
http://forum.xda-developers.com/showthread.php?t=651166

So, following post 'step by step' didn't change anything with my screen rotation settings. still automatically rotates all the time when I don't want it too...really frustrating. This is about the 4th hack I've tried with no success. Does anyone know what the proper solution is for the HTC Rhodium? I'm running stock AT&T Tilt 2 Rom WM 6.5.
I know there are programs you can install to take over rotation control...I'm just looking for a reg change or service hack or something to stop auto rotate from ever happening.
Thanks to anyone who knows the answer!!

Keyboard Light

I am having an absolute FIT with the damn keyboard light on my 750! It gos off after about 5 seconds, and THAT is ridiculous! I was told by a source at Palm there IS a registry entry to fix this, but he could not divulge the info (I did tell him I was open to receiving an anonymous email, but haven't seen it yet!)
Anyone have any ideas? He said it was the same one that worked on the TyTn/Hermes/8525 but I have not found it yet....
Help??

HKEY_CURRENT_USER\ControlPanel\Backlight and key is QKeyLedTimeout. The number of seconds is usually set to default at 10. you can make it any number you like. Mine is set at 20.

I wonder if this also relates to my current issue too - can anyone comment?
The backlight on my Treo 750's keyboard refuses to come on IN USE - however I'm fairly convinced it's not a hardware issue; when performing a soft reset the keypad lights up fine during the boot cycle.
It's as if there's a registry entry that sets the "turn off keypad light after" value to 0 (i.e; always off).
Thoughts?
Cheers,
Steve

Found It in WM5
I traded in my WM6 phone for a Treo 750 with WM5 - wow, everything is where it should be, and the phone works the way it should!
As far as the On-Off issue, Steve, I see that in line in my phone - the key is set to 1, so I would try changing that:
HKEY_CURRENT_USER\ControlPanel\Backlight and key is QKeyOnOff change it from 0 to 1
Let me know - this could be my first crack at helping someone else out!!

I have a question. I can not seem to find the registry edit area for the Treo 750 running WM6. Can you help me in giving me some instructions on getting to this so I can edit the file to keep the keyboard lights on for longer than a few seconds?

on my kaiser it's set to 30 by default.

[email protected] said:
I have a question. I can not seem to find the registry edit area for the Treo 750 running WM6. Can you help me in giving me some instructions on getting to this so I can edit the file to keep the keyboard lights on for longer than a few seconds?
Click to expand...
Click to collapse
Hi there,
There is no default registry editor on WM devices, so you will have to install one if you want to make any changes. You will find a few built into well known commercial apps such as MemMaid and Resco Explorer (I've used both and they work fine on WM6). There may also be some free ones around.

Windows Mobile 6.5 - Lock Screen is slow

Hi,
I have installed the latest WM6.5 Build 21725 (http://forum.xda-developers.com/showthread.php?t=513605) on my HTC Touch Pro.
But I have a problem (which occurs on all tested roms) with the lock screen: I lock the device. The lock screen appears fast and is immediately responsible. But when I go to suspend mode (by waiting or pressing the power key) and then let wake up the device, I have always to wait a lot of time until the lock screen is responsible to unlock the device. This is very annoying and I want to fix that "bug". Can anybody help me?

Same here. And does anyone know how to remap one of the softkeys to lock the screen? Instead of have to push start >> lock?

i had this with a 6.5 rom
what i did was after i turn backlight on i quickly press the hangup buttton and then the slide works fine
this may have to do until the rom becomes more stable

-PiLoT- said:
i had this with a 6.5 rom
what i did was after i turn backlight on i quickly press the hangup buttton and then the slide works fine
Click to expand...
Click to collapse
Thanks for your tip, but it doesn't work

Sorry this was gibberish

then im sorry i cant help
all i can do is ask youve tried this on a 6.1 based rom

this is a knowing trouble because of the beta
Hey pilot... this is a real kick on the ass cause nobody answer this many times users needs a third party app to lock their devices... i didnt lock my device... i just turn it off and disable all the buttons you see... its like a locked simply and crapy phone function.

well i know it looks good que but the problem i had was after a while in standby the buttton would shift to any side however i know the phone wasnt crashed due to the little arrow animatiuons kept going as normal all i did was tap the phone down button and then it worked as it should mind you this was davie ducks v8 on the hd

I figured out that the lock screen is immediately responsible if you set a password. But I don't want to slide AND then type a password

just slide the time bar at the below screen before slide the lock :| i got this bug after upgrading into a 6.5 rom :| now it's done by myself :">

remember at the time of the OPs question 6.5 was very buggy
a lot of the latest releases are a lot better

Laggy
I also have this laggy problem when clicking the right key to bring up unlock screen, takes a while for the unlock screen to appear.
Was looking at ThrottleLock which looks good, but not compatible with 6.5.
I hate iphones so don't want S2U2 !!
Looking forward to update

Correction
Correction, just tried an older version of throttlelock app 0.6, and it works with windows mobile 6.5

Is there some way to just turn the lock screen off? I hate how slow it is on my backup phone, an LG KS20

You may have it in settings-personal, if not, go to HKLM\software\microsoft\shell\lockscreen, and change 'enable' from 1 to 0. Then, you'll have to old-style lockscreen. If you want to see the lockscreen settings applet, then change 'ShowLockScreenPicker' from 0 to 1. You may need to soft reset (but you may not).

Farmer Ted said:
You may have it in settings-personal, if not, go to HKLM\software\microsoft\shell\lockscreen, and change 'enable' from 1 to 0. Then, you'll have to old-style lockscreen. If you want to see the lockscreen settings applet, then change 'ShowLockScreenPicker' from 0 to 1. You may need to soft reset (but you may not).
Click to expand...
Click to collapse
Thanks Ted! Works perfectly, for some reason the Lock Screen settings applet won't show, but that's not important as the first registry key solves my problem.

Yeah one way is to set back original WM5x/6/6.1 LockScreen but I have solved it another way... Maybe you have noticed that the new WM6.5 lock screen has delay ONLY on first run so what about put a shortcut to "\Windows\Startup" to lock device on startup (http://www.vijay555.com/?Releases:VJDeviceLock - working also with WM6.5)? I mostly don't need to use the device in first seconds after startup so everything necessary can load to memory and then after unlocking my device is everything relatively fast ;-) BTW you can set lockings with tool named Smart Lock (http://forum.xda-developers.com/showthread.php?t=505032).

bkf1 said:
Yeah one way is to set back original WM5x/6/6.1 LockScreen but I have solved it another way... Maybe you have noticed that the new WM6.5 lock screen has delay ONLY on first run so what about put a shortcut to "\Windows\Startup" to lock device on startup (http://www.vijay555.com/?Releases:VJDeviceLock - working also with WM6.5)? I mostly don't need to use the device in first seconds after startup so everything necessary can load to memory and then after unlocking my device is everything relatively fast ;-) BTW you can set lockings with tool named Smart Lock (http://forum.xda-developers.com/showthread.php?t=505032).
Click to expand...
Click to collapse
The problem with the 6.5 lockscreen is that it kills gwes.exe (at least in my experience). Do a soft reset, open up a task manager and look at gwes.exe. With dotfred's, I'll start at maybe 15 MB, and as soon as I open the lockscreen (I get the delay, too), the gwes usage jumps by about 6 MB, and none of the ram is released. It makes my device buggy over time. Gwes.exe is bloated enough with 6.5.3 roms, you really don't need the lockscreen killing it like that.
I don't know if it's an issue on a stock rom, but the cooked ones have problems. In the 6.5 cooking thread, Da_G said a while ago that it had to do with how most kitchens compile roms. They compress all files the same way, and ignore flags in the dsm's that say whether or not a file should be compressed. He's said that cooking an uncompressed rom fixes the problem. I've tried making a cab of the lockscreen and running it that way, but I still get the initial delay and the 6 MB ram-tax on gwes.exe, so whatever is breaking the lockscreen during cooking because of the forced compression isn't in the lockscreen packages. Anyway, the lockscreen is cool, but I personally hate what it does to gwes.exe, so I don't use it.

What your saying about cooked vs. stock is likely correct, as I had briefly owned an HTC Pure (ATT branded Diamond 2), which shipped with 6.5, and there were absolutely no delays with the lock screen. On the other hand, I still haven't flashed 6.5 onto my X1, so I don't know if its just that my LG can't handle the lockscreen with its 400mhz qualcomm.

New ROM - no more permanent changes in the registry?!!

Go to
HKCU\ControlPanel\Backlight\AutoDeviceLockEnable = 0
Try to change the value to 1
It's not possible.
The entry disappears and a new entry "Locklevel" appears.
"Locklevel" is set to 0.
Now try to change this to 1.
This works, but after Softreset the value of Locklevel is 0 again.
You see, you can't permanently change some registry entrys anymore.
It seem's that the new ROM has some special security "improvements".
Or is it a Bug of the new ROM? Maybe this is the reason why it's not officially available over HTC website?
Any ideas???

I can't reproduce the first step but I can reproduce the second.
I'm perfectly able to set the enableautolock key to 1, but (and this is the weirdest thing) it hasn't any effects, even after a softreset. What I noticed though, is that BsB tweaks 1.2 reports that the autolock is off, despite the fact that the enableautolock key is set to 1 (and stays 1 also after a soft reset).
Until I set autolock manually to on in BsB tweaks the registry values doesn't have any effect. After I switch the autolock on in BsB tweaks the autolock works perfectly after a softreset. (Yet, there isn't anything changed in the registry)
I stand by my case, it is BsB tweaks that is causing this problem and not the new ROM. (Again, after my upgrade I hadn't any problems whatsoever with the lock status. It was after the installation of BsB tweaks that the problems occured).
Locky me , the lock works perfectly now

It must be the ROM because even after hard reset there is no Auto Lock!!!

Which ROM do you have?

appelflap said:
Which ROM do you have?
Click to expand...
Click to collapse
the new one, 1.48.

Which one from this list. I have the official dutch rom and do not have the problems you mentioned.

I've the german ROM.
But I just noticed that after a new hard reset it suddenly worked.
Now it looks as if you were right, the problem must be BSB Tweaks 1.2.

Glad it worked out for you. Cheers

hi guys!
it's not my app problem, there are 2 reg keys to enable auto lock:
HKCU\ControlPanel\Backlight\AutoDeviceLockEnable
HKCU\ControlPanel\Keybd\DeviceLockWhenSuspend
the reg key handled by my program is the second one that's why when you change the first one the status of the tweaks doesnt change. Anyways if you enable autolock first key will be edited also.

makeveral said:
hi guys!
it's not my app problem, there are 2 reg keys to enable auto lock:
HKCU\ControlPanel\Backlight\AutoDeviceLockEnable
HKCU\ControlPanel\Keybd\DeviceLockWhenSuspend
the reg key handled by my program is the second one that's why when you change the first one the status of the tweaks doesnt change. Anyways if you enable autolock first key will be edited also.
Click to expand...
Click to collapse
When i use your app, nothing happens to HKCU\ControlPanel\Keybd\DeviceLockWhenSuspend
It seem's that your app doesn't work proper on newest ROM.

Benz-Driver said:
When i use your app, nothing happens to HKCU\ControlPanel\Keybd\DeviceLockWhenSuspend
It seem's that your app doesn't work proper on newest ROM.
Click to expand...
Click to collapse
just tryed and it works perfectly, i'm using rom 1.48 also
edit: are you using bsb tweaks 1.2? or older?

I use german 1.48 and BSB Tweaks 1.2.
The Auto Lock problems appeared first after having installed BSB Tweaks.

Benz-Driver said:
I use german 1.48 and BSB Tweaks 1.2.
The Auto Lock problems appeared first after having installed BSB Tweaks.
Click to expand...
Click to collapse
but i still dont know wich problem you have? it doesnt auto lock? you cant change registry? or my app is not working? xD
if it doesnt autolo lock is because you have to lock it for first time manually the other should be fine, at least i havent seen anyone else with problems (apart from the locking manually first time or it wont work (wich is a rom prob))

I'm glad that has been cleared up. BsB (edit: makeveral), thanks for your clarification on this point. Keep up the good work.

Hmm. Now, after having locked the phone manually, it seems to work. Thanks!
But, what i don't understand, is, that without BSB, after hard reset, it worked normal (without having to lock the phone manually the first time).