Entering password on XDA Orbit 2 - Touch Cruise General

Because i am using Direct Push to get my emails on our secure exchange server Windows forces me to enter a password when turning on my Orbit 2. Trouble is the brightness of the backlight is reduced almost immediately i turn my phone on and it makes it very difficult (in fact almost impossible) to see the screen to enter my password especially in daylight. Can anyone help?

Hi Bortis, I'm new to the forum so spent ages trying to find a solution to a similar problem.
I dont set the pasword lock all of the time but had the same problem with the keylock. i.e. when locked the backlight went off.
I needed to use a registry editor (PHM Regedit in my case)
I then edited registry keys as shown on the top of page 2 on
http://forum.xda-developers.com/showthread.php?t=384865
I know the usual answer is 'do a search' but having spent ~ 6 hours doing that I HTH.
cheers
tom

I had the same problem with my Orbit II. I followed some simple advice from NoFatePPC and have had no problems since even after doing a reset
-----------------------------------------------------------------------------
go here in your registry:
\HKCU\ControlPanel\Backlight\LockLevel
you should see a bunch of keys and a folder called "LockLevel" - inside that folder is the LockLevel key with a value of 1 or 0 - you don't need to go inside that folder. just rename it from "LockLevel" to "LockLevelx" (add an x to the end of the folder's name)...
that's it.
Original thread link
http://forum.xda-developers.com/showthread.php?t=351709

Thanks guys. That works. I'm happy.

Cannot unlock password on Orbit 2
Hello,
I have an HTC Orbit 2 (POLA 200). It's locked in O2, but that not the problem. The problem I'm having is that it suddenly started to show me the password unlock screen. I've tried to hard reset it and access the boot loader, but it is NOT working When I try to hard reset it (camera button + reset button, then release the reset button and keep the camera button pushed) it just restarts normally. It shows that "O2 Welcome" splash screen, then the screen with Windows Mobile 6.1 and then it gives the password screen. On the top, it appears that I have signal through HDSPA and the muted sound icon. Also, it says that I can make only emergency calls. I don't know what to do, because I haven't set any password. I've tried a few standard ones like: 1234, 0000 - but nothing. However, if I put in "999" without the quotes, the screen light gets stronger and it says that I must press DIAL to talk, but that's the emergency thing . I have to let you know that I cannot sync the phone through active sync or anything like that.
Any ideas?
Thanks,

Related

Password

Hello Everyone,
Last night I've activated the password function to my mobile phone but the strange thing is i couldn't open my phone with the same password on Windows Mobile.
I thought that it could be fixed by re-installing the ROM but couldn't suceed because of ActiveSync connection.
Can anyone help me about this issue please? How could I deactivate the password?
P.S: I'm using WM6 on my Dopod 838
could you be a little more specific about the problem? you dont have to use activesync to upgrade your rom. just put your phone into bl mode and go from there. that WILL clear the password as long as your updating the ce rom. or just do a hard reset
would formatting the storage/chipondisk not clear any password setting on the device ?
I think i have a quite silly situation, this is the normal Windows CE Password which we use usually and activates itself when we turn on the phone or some minutes later after we didn't use it.
I thought the same but i need to open my phone with password for cleaning storage. Actually i don't know how to hard reset this phone, i only was using "Storage Clear" application for erasing whole thing.
For installing new rom, I need to make CID unlock and the phone does not run the application without having the ActiveSync connection (guest connection) with phone.
Hard reset: Hold both software "---" keys on the keyboard and reset with stylus. Then hit "0" key to hard reset or "X" key to cancel.
Bootloader mode: Hold light and power buttons together and reset with stylus. (The light button is on the front edge of the phone, near the volume slider). In bootloader mode please keep in mind that the backlight is turned off, therefore the screen is hard to read in poor light.

WM6 screen goes off after 5 Sec

hi got Tornado imate sp5m i ve flashed the rom with WM6 Perfect English after flashing i seems corrupted it gets freeze if i dont use it for several hours and when use it the screen goes off every 5 seconds with an annoying chime and tried Vanila aswel but getting the same problem.
Note: After Clear Storage it works fine again for sometime. i have T9English and Sp5m Buttons Installed nothing else
Any Solution
i ve format my phone installed GSM update and then WM6 and followed step by step.
Same problem here with Vanilla Edition.
Screen goes off after 7secs no matter what time-outs are set under power management. If I cange values in power management, it works fine again, but after some time it starts cutting off screen after 7secs, that is very annoying.
yes it doesnt care about time management it got its own time well much annoying thing is it hangs sometimes and i found no call is recieved when it seems hang
did u Clear the storage ? the problem seems solve but for a while
Set these registry settings and you'll be fine:
Code:
[HKEY_CURRENT_USER\ControlPanel\Power]
"Display"=dword:0000003C
[HKEY_CURRENT_USER\ControlPanel\Power\LockLevel]
"LockLevel"=dword:00000000
The display will go off after 60".
pauliusba said:
Same problem here with Vanilla Edition.
Screen goes off after 7secs no matter what time-outs are set under power management. If I cange values in power management, it works fine again, but after some time it starts cutting off screen after 7secs, that is very annoying.
Click to expand...
Click to collapse
screen goes off after 7 seconds only after the keypad is locked (that's the best i can do to prevent screen from lighting when the joystick is accidentally toggled inside your pocket for example). but if it is not locked, (in my experience) it corresponds to the timeout set under power management. but still i will check on that.
This display timeout behavior is normal for WM5/6.
In [HKEY_CURRENT_USER\ControlPanel\Power] there is usually only one key when the keypad is unlocked. The "Display" key stores your normal timeout setting in seconds. When you lock the keypad, the "Display" key is set to 7 seconds and your normal timeout setting is set to a new key called "TimeoutSaved". When you unlock the keypad, the "TimeoutSaved" is deleted and the "Display" key is set to your normal timeout setting. So far so good...
But, there's also another key in [HKEY_CURRENT_USER\ControlPanel\Power\LockLevel] called "LockLevel". It seems that it controls the normal Display/TimeoutSaved behavior. It's normal value is "0". But some times it is changed (I think AutoKeyLock and LowLevel have something to do with it) and set to "3" or "4". All you need is reset it to "0".
That value keeps restoring back and 5-sec time-out problem remains. There is no workaround here...
Just to point out, Nitro's registry settings appear to be in hex, whereas most ROMs I've used show it to me in normal numbers (is that binary? because I thought binary was only 0 or 1).
Either way, 0 is 0. I wonder if it's possible that this key should be in hex and the keylock programmer used the wrong way to enter info, or maybe vice versa but still wrong data?
pauliusba said:
That value keeps restoring back and 5-sec time-out problem remains. There is no workaround here...
Click to expand...
Click to collapse
It's actually 7 seconds and you have to power off your phone, wait a minute (or two) and start it up again.
This is a really common problem/question. If you had used the search you wouldn't have had to post and wait.
Look at this. This is solution for your problem
Possible cause
I think I may have found what is causing this issue. I noticed that if I let the keylock program run, it changes the backlight, etc to timeout and go black in about 5 seconds. I have to go into config and change it to a higher number, then back down to what I want it to be.
It got to the point that just had to disable that keylock program, otherwise, I have to constantly reset the power management settings.
When I don't have the keylock program running, the timeouts all work as advertised. Strange, eh?
Quakie
I had this, I found a solution, delete the LockLevel key with a registry editor, reboot and the problem has never occurred again

Touch Cruise Backlight Problem

When I am on a call the backlight on my Touch Cruise turns off - I don't mind this. The problem is that when I try to turn it back on it is extremely dim (even if the backlight setting is "bright") and I need to use "Adjust backlight" to make it brighter. In sunlight this is almost impossible to do since I cannot read the screen. Even after I readjust the brightness, whenever the backlight turns off and I turn it back on, the backlight is dim again.
I have tried renaming the \HKCU\ControlPanel\Backlight\LockLevel folder to LockLevelx - this has not worked.
I have tried setting \HK:M\Drivers\Builtin\RIL\EnableFastDormantDisplayDuringCall to 0 - this has not worked.
Help please!
Do you have this problem all the time or you can see this misbehaviour just now?
I'm asking, because this could be caused by some other software you installed on your device,
which does some "things" with the backlight or some call manager like PhotoContacts etc.
This happens all the time. It does not happen after I soft reset the device until I use the phone. As soon as I use the phone the backlight turns off and is dim whenever I turn it back on.
- Are you running some "cooked" unofficial ROM?
- if you are using HTC Home, try to deactivate it, just choose some different homescreen schema but not HTCHome, make a soft-reset a try it.
- check HKEY_CURRENT_USER\ControlPanel\BackLight\LockLevel\LockLevel - this should have the value 0
- running standard ROM
- deactivating HTC Home doesn't help
- LockLevel is set to 0
This periodically happens on my device too. And it's really, really annoying. I found that one way to make it go back to 'normal' for a while is to change both lock levels (in locklevel and locklevelx to value 1) then back to level 0 (including the waiting and the soft resets) and then it seems to go back to normal again.
what seems to set it off for me is using the call history to dial a number, but this is sporadic.
Thank you Marissa and Hujer. Unfortunately both your suggestions have not worked.
I have had the same problem. What helped in my case is deleting locklevel and locklevelx from the registry and then soft reset. Worked for me!!
Thanks Tim B but that did not work either. If I soft reset my device OR delete locklevel & locklevelx and soft reset, then the backlight comes back on at the correct level of brightness....until I make and end my first telephone call - then the backlight only comes back on dim. By the way if I delete locklevel, it stays deleted until I make and end my first call - then it's in the registry (with value 0) again.
sclhtc said:
Thanks Tim B but that did not work either. If I soft reset my device OR delete locklevel & locklevelx and soft reset, then the backlight comes back on at the correct level of brightness....until I make and end my first telephone call - then the backlight only comes back on dim. By the way if I delete locklevel, it stays deleted until I make and end my first call - then it's in the registry (with value 0) again.
Click to expand...
Click to collapse
Exact same happens to me, using Bepe 64 rom. Real pain in the neck.
Possible workaround
This sounds very much like the same problem Trinity users have faced since that device was released. Try searching the Trinity Forums. There was a reg fix...something to do with "fast off" or similar.
The workaround there was, after the phone call, to press the power key to put the device into standby, and then when it wakes the next time the backlight is restored. Try that anyway.
No luck with this either.
I now have the same problem. My earlier solution (delete locklevel and locklevelx) is not working anymore. There must be someone who knows how to solve this.
I am willing to do a hard reset but then I will have the problem again that after turning the phone on when it is locked the display is not readable.
Any good solutions??
Tim B said:
I now have the same problem. My earlier solution (delete locklevel and locklevelx) is not working anymore. There must be someone who knows how to solve this.
I am willing to do a hard reset but then I will have the problem again that after turning the phone on when it is locked the display is not readable.
Any good solutions??
Click to expand...
Click to collapse
Exact same happens to me, using official rom.
I had to do a double reg edit, try this which is what I use:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"EnableFastDormantDisplayDuringCall"=dword:00000000
[HKEY_CURRENT_USER\ControlPanel\Phone]
"Sleep"=dword:00000000
Reboot!
Thanks but that didn't work either.
Just to be clear I do not mind the backlight staying on, dimming or turning off during a call but when I press "Call End", the backlight dims (which I do not want) and if the backlight turns off after a call it is dim when I turn it back on (which I also do not want).
Did anyone find a solution to this?
Have tried all the things on here, and some work for a little while, but then the problem reoccurs
Wow, this is so strange. Mine comes back on at the same brightness level.
You all are experiencing the same thing as Marisa?
It is an odd problem because it seems that it occurrs all of a sudden out of the blue.
One time you make/receive a call and afterwards, even if the call was only a few seconds, you terminate it and the screen either is already dim or then dims and will stay dim unless you hit a backlight changer. Even then, if you lock the phone, or the phone dims after your prescribed time, it then stays dim. The only way to temporarily fix it is to set it to the normal level and then soft reset. It will then behave properly until the next phone call.
It is very inconvenient as if it locks while this is going on, you can hardly see to unlock it.
I have trawled the internet for hours looking for solutions to this. The Kaisertweak does not work for this on this device (don't know why!) Installed Schapps but the very tweaks I need do not appear when installed on my device.
All the registry edits don't work. In fact when I go to do them, the value is already at the recommended value anyway. Renaming locklevel seems to work sometimes for a while, but then reverts back.
I think it is more a problem of undimming than dimming. It dims when I expect it to dim, but does not light up again afterwards. The Kaiser solution of pressing the power button or d-pad to do this does not work on the Orbit.
I have a fairly non scientific feeling that it's something to do with either Shell, Pontui or Co-Pilot. I have uninstalled Shell & Pontui, but it has made no difference. Makes no difference either if HTC Home is/isn't installed/running.
Another strange thing is that when it is in its dimmed state, I only have to touch the page where the backlight slider is for the light to come back up. I don't need to touch the slider at all, it's already where it should be, 3/4 of the way up.
In fact I have done the registry tweak which is supposed to stop it dimming during calls altogether, and checked to see that it 'took' and it is still happening.
Somewhere, there must be a registry key or somesuch which controls what happens after this "temporary" dimming, which says, the call is over/the device is unlocked - go back to prescribed brightness. But I can't find it.
This is a really insidious problem which drives you mad, especially when you are out and working, you don't have time for this nonsense. If all else fails in a week or so I will try a hard reset, i just don't have time right now.
Any help gratefully received.
I have just emailed O2 with this problem. Let's see when/if they reply.

Tornado (WM6 Platinum) doesn't start

Hi,
I'm experiencing a strange problem with my Tornado (i-mate SP5, WM6 Platinum Edition). Today it stopped working suddenly, I had to remove the battery. When rebooting, the i-mate sceen appears, then the HTC logo, then Nitrogenius' splashscreen, then a beep sounds, and afterwards the screen is black and nothing happens, no keys are responding. I can "switch off" the phone by long pressing of the power key. Reset with pressing the 2 soft keys and the starting key does not work, the phone starts until the splashscreen and afterwards the screen goes black. Strangely I can connect the phone with activesync, synchronize contacts and calendar and even explore the device with activesync's filemanager; and the battery is charging, too.
Any suggestions except reflashing?
Regards
The same happen to me,backlight doesn't function. Start -- 9 start again 3 ok... flash light is enable ,now i should change home screen settings and power settings... set backlight to 10 minutes or more...
Then it should function
ma3ks said:
The same happen to me,backlight doesn't function. Start -- 9 start again 3 ok... flash light is enable ,now i should change home screen settings and power settings... set backlight to 10 minutes or more...
Then it should function
Click to expand...
Click to collapse
Thanks for the hint, I tried, but unfortunately I seem to miss something. Could you elaborate a bit how you managed to switch on backlight.
Thanks a lot!
EDIT: It worked! You made my day!
After pressing the keys you mentioned (and some others, too) and after rebooting again the backlight is on again. Thanks a lot!
I met the same problem in many cases and I found the culprit, it is tornadolowlight or tornadopowercontrol. while these appli are activating if I soft reset or by force restart (removing battery) then next startup will get a blank screen. But actually in this case the device is on and working only thing is its backlight is off. So, by using a torch light or simply using MyMobiler from a pc you can see the screen, and start that culprit appli then done
OR another thing I have done is I put shortkey for MultiFlashLight and whenever such situation happened I just press the shortkey and activated it and done

Help - Orbit 2 / HTC home crashing problem

Hi
I've had my orbit 2 for a while now using the o2 software and I thought today I would try and install HTC home to see what all the fuss is about!
I downloaded the cab and installed it but now my orbit 2 crashes on start up!
When I turn it on I get the blue o2 welcome screen, the green windowms mobil 6.1 screen then it loads. The o2 smart bar is still there and the two screen buttons say calander and contacts (as its always been).
Those buttons then change to phone and menu I believe and the phone crashes!
How do do a factory reset the phone without being able to turn it on?
Update: It appears I can access the phone when its plugged into my pc, but as the phone crashes sometimes!
Help!!!!
press the two hardware phone keys together and then, while holding
them pressed, softreset with the pen. A message should appear on
the screen, that you will lose all personal data. Press green button
to confirm and phone will HARDRESET...
Good luck,
Olioaglio
Are you using the right cab file?
Hi,
I have an Orbit 2 and have no problems with my 6 tab HTC home file.
You do need to take care which version you are using though.
The cab file I have and which I know does work is:
HTC.Kaiser.Home.Eng.0409.6Tab.sch
Instead of hard resetting your orbit 2, just remove the cab file you're using and install the cab file I list above and which you should find by doing a search of this site. Then do a soft reset and it should be fine.

Categories

Resources