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
Hello all... got kind of a big problem that i at the moment don't have an answer to,..
inastalled advanced configuration tool 3.2 on HTC Polaris, the first crash i had was when I enabled animation for menus... (the start menu turned black and the polaris froze), but when i managed to start the advanced configuration tool i unchecked it and it was ok,...
the MAJOR PROBLEM accured when I set the touch screen sensitivity, because the touch part of the screen is inresponsive,.. meaning it does not work at all,.. tryed very hart pressing but it doesn't do it.. the problem is because i can't reach eg start menu or the lower 2 shortcuts with hard button cursor (the wheel)... gestures work however, so i can call the touch flo cube but am not able to select anything, and sam thing goes for enetering pin,.. so i'm not able to make phone calls at the moment.. did few hard resets, and uninstalled the adv. conf. tool but nothing helped... can anyone tel me where (and how to get there) can i adjust this back to normal, i wanted to do this in the advanced configuration tool 3.2 but the problem is you cant make any changes since the screen doesn't work,.. same with reinstalling the program, i can select to install it on a card but canot "click" on next since the screen doesn't do it and the hard keys "can't go there"
so really really someone help me please...
thnx
Are you sure you hard reset and this problem went away or did you mean soft reset?
Maybe aligning the screen will help reset the pressure? Click the button in the middle of the wheel and the GPS button at the same time, the Windows align screen pops up. See if that helps.
I find it very hard to believe that you hard reset and the touch screen sensitivity is still not there. That can't be right.
Hi,
thanx for the reply,... another problem that accoured afterwards was that my friend held the end button (wich locks the keys, screen) and the phone was additionally locked... and literally nothing (again NOTHING ) helped, spent 5 hours trying to save the situation,.. i did soft reset (so your assumption was right) but when later tryed hard reset it probably wasn't done since the instructions say you do it with holding gps and iExplorer buttons while soft reseting it... this resulted in getting the "hard reset screen" wich says to confirm hard reset with hitting the send button, wich unfortunatelly i wasnt able to find in hard keys, and nothing else but this warning text was on the screen as well.. so in the end it probably ended upo wit soft resetting it, anyways it didn't help,... i decided to reinstall the rom i downloaded on htc official site,... it went thru ok and the phone is , though out of the box at least functional,... but in the end, i must admit that am a little surprised this happened with this tool pack (i actually avoided altering the registers just in order to avoid this kid of situations since i don't really know much about these things)... was expecting it to work (in my case) a bit better, more stable. All i wanted really was to get a bit louder speaker volume when ringing and ability to alter the HTC home toolbar, since i find the weather screen totaly irreliable and never really use it, so i thought I would have sth there that i might really have some use of..
well nevertheless.. the phone is working, that's all that matters at the mom so i can again start finishing my phd wich i am defending in a week
PS. the fact that you can not do practically anything without the touch screen just sucks big time, if i compare it to the mouse on pc,... i saved the situation many times with the keybord .. in 1 word strange
take care
My Mobile
Perhaps you should have tryied out the "My Mobile" aplication that allows you to use your mobile from a PC.
It shows a windows with the mobile screen and you can touch it and use the mobile like if you was touching the REAL mobile...
Late for that solucion, perhaps another with that problem can solve it this way...
Chears
@gastonfama: am not sure this would help, since a friend that has htc diamond has this tool pack on and it work k ok on his phone,.. that's why i predicted that it is going to be stable enough on mnie as well,.. so in my thinking, if the 2 htc that are rather alike had such different "reaction", than an emulation would be even less comparable to mine, thanks though
Had the same problem with Schaps_AdvancedConfig and wrong HKEY_LOCAL_MACHINE\Drivers\TouchPanel\PressureThreshold setting.
XML I used had "200" as advised value (system default is 2908!),
after changing you could hit it with a hammer and nothing.
Managed to set is back to recommended value 9000 using MyMobiler app and all problems gone.
See also HKEY_LOCAL_MACHINE\Drivers\TouchPanel\PressureThreshold
sys default is 18866, I use now 19866 and I'm happy
Check tips&tricks thread
I got the same problem, I wanna to install "My Mobiler" but due to the screen is locked, I can't continue the installation, any help ?
well as far as I see here (forgot how i installed it after previous post) you have an exe here :
http://www.mymobiler.com/downsafe.aspx
so you will install it from the pc anyways, but how will you make the confirm on where to install it (mybe if you put storage card out and there will be only 1 memory option, but you will still have to confirm installation i guess).. i wasnt able to confirm without the screen on polaris,.. maybo on some other phone
double post...mistake
I had that same screen not working problem after tweaking the phone with advanced config 3.3, 3.2, 3.1, only hardware buttons work.
Problem can only be solved by Hard Reset. Version 2.2 I think is the only one that works (not thoroughly tested though)
Hi. I have a huge problem. When I press the settings in the Start Menu my phone soft-resets immidiatly.
I dont know why.
As far as I know there is no path to the settings (Like in the windows folder),
But I've tried deleteing and recreating \Windows\Start Menu\Settings.
Nothing works. I dont know if it is some kind of virus or just a bug. Most likely its the registry that is messed up.
I haven't installed any programs on my phone recently and I use the LG KS20.
If I dont get a response quickly I will make a hard reset (If so, I will tell that on this thread).
The only time that this happens is usually when there is a major failure afaik and that you may have deleted a vital file. If you have everything backed up prior to the incident, just hard reset the device and pull up the back-up.
Well, I could't wait anymore without my settings so I made a hard reset,
And it worked.
Most likely the registry had been messed up, But its back to usual now.
Thanks for the help, Everyone who posted of this thread
hard reset is always the most secure solution
So, I decided to try Ultimate X2 BetaII. Here's my problem:
I decided to flash to OEM ROM first, as I've read this is better with some ROMs, but I think I did something stupid. Instead of using the .exe file to install (_ATT Tilt_RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship.exe), I decided I wanted to install with my SD card, so I extracted the .nb file (KaiserIMG_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.19_Ship.nbh) and renamed it "KAISIMG.nbh" and copied it to my SD card. I installed with the standard SD card method, and now I'm stuck at a (seemingly) endless screen alignment that loops over and over. The only posts I've found so far on this topic seem to deal with hardware issues, but my screen has worked okay until now, so I'm guessing I screwed something up software-wise by impatiently trying my own idea, instead of following instructions.
Mind you all, this is only my second attempt at flashing a ROM, and the first one I flashed was months ago, so you can consider me somewhat of a newb.
By the way, I just tried going through the screen align twenty times to see if there was any change, and I'm still stuck there. I haven't tried making a welcome.not file yet, but I'll give it a shot now. It seems like even if that works, there should be a way to fix my problem properly. Any ideas?
welcome.not
Welcome.not does get me past the align screen and into the Ultimate X2 Beta II ROM. This does, of course leave me unable to align my screen with the WM app. Still looking for a "proper" fix.
Did you try a different ROM?
RE: Did you try a different ROM?
I first had the screen alignment problem after flashing the OEM ROM. Afterward, I flashed Ultimate X2 Beta II, and the problem persisted. I flashed back to OEM, and the problem was still there, so I flashed back to Ultimate X2, and after conferming the existance of the same issue, I used the welcome.not bypass. I suppose this will be okay, if I can find another way to align the screen, besides the WM screen alignment utility. I saw a post regarding a possible Reg key that changes the max screen alignment repeats. Perhaps altering that key would make it save my initial alignment and end the infinite loop?
P.S. Does anyone know of a screen alignment utility that works from the device and saves the settings, a way of working around the WM utility?
Registry Keys?
Are there registry keys I could alter to fix my screen alignment?
You do have a correct HARDspl right? When you enter bootloader you should see hard spl. Flash another spl and see what happens. Sorry im not of more help but im on my phone.
I have HardSPL 3.29. Ultimate X2 Beta II is running quit well. Radio's working fine, too. I just can't figure out my screen alignment issue. If someone could hook me up with a screen alignment file or registry settings, and perhaps clue me in a little on how to implement, that would, perhaps, be a temporary fix.
Well then think old school. If the cross is moving when you press it i would think the digitizer is ok. So clean the edges around the screen really good. Maybe some lint or dust around the edges. Also maybe loosen the screws on the back a little in case the screen is in a bind.
Yeah, I think the digitizer is fine. I already cleaned the edges with a business card. I don't have a torx kit with me, but I'll keep the screw loosening in mind. I figured the problem must be a result of extracting the .nbh file from the OEM install file, rather than running the .exe. However, flashing again (I used the .exe files for the OEM and Ultimate X2 the second cycle of flashing, rather than using my SD card) hasn't helped. I ran across the following thread, and am downloading the app now. I don't know if it will help, but maybe if someone else runs it and extracts their alignment settings, they can post them for me to try out?
http://forum.xda-developers.com/showthread.php?t=396466
Reg Key
Here's another instance of the same type of solution:
corollatercel said:
So i've been having problems with the screen alignment on mine since i had one spot on my MDA screen that was dead and my screen was cracked so the alignment wizard basically got stuck in limbo when I tried to calibrate it. SO basically what I had to do was download PHM Registry Editor and change the registry key touch referenced in here.
kernelguy said:
My touchscreen had a crack only at the bottom. After skipping the 'align screen' during initial ROM load, I lived with a non-functional touch screen for a day or two. I then remembered the post from equinoxe that had registry settings for his phone. I took those settings and updated my registry. I now have a decent touch screen - at least the top 3/4 works fine.
The key and settings are:
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH]
"CalibrationData"="1922,1957 3330,639 3317,3276 600,3230 609,677 "
I could surmise that the screen is being treated as a square of 3900 x 3900 dots. 0,0 seems to be the top, right corner.
kernelguy
Click to expand...
Click to collapse
Afterwards I used the remote alignment tool (attached) to retrieve the correct settings from the correctly aligned mda(after changing the registry key then rebooting the device) then made sure the file was saved on my pc....normally it's saved by default in the C:\Program Files\Code Factory\Remote Screen Alignment directory. The file was called WIZA200.dat. I did a soft reset then when the alignment screen came up I did the skip function in the remote screen alignment application and it automatically read the proper calibration from the wiza200.dat file and then properly calibrated my mda now my screen is properly calibrated even though i never ran the alignment wizard.
So here are the Instructions folks:
1. Download the latest activesync and connect your mda to your computer and verify your device is connected(not as guest)
2. Perform a soft/hard reset on your MDA then tap your screen to start the screen alignment wizard
3. Download the remote screen alignment tool attached and install it on your machine.
4. Download the wiza200.txt file attached and rename it to WIZA200.dat then put it in the C:\Program Files\Code Factory\Remote Screen Alignment directory on your computer
5. Ensure your MDA is connected to your pc(A green activesync Icon usually indicates a connection )
6. Open the remote screen alignment tool on your pc meanwhile your phone be displaying the alignment screen wizard.
7. Click SKIP in the screen alignment tool.
Assuming everything went fine a message box displaying "The operation has been completed successfully. Your device will be restarted." should pop up on your computer and your device should restart. Afterwards your phone will run the files it always does when you do a soft/hard reset then you touch screen should be properly calibrated and work fine.
Click to expand...
Click to collapse
If someone could do a fresh, accurate screen alignment and report the registry key settings, I could try editing them for myself and see if that does it.
check your pm
check your pm
Thanks!
Thanks for the help, guys. I found the kaiser.dat file in the program's directory, opened with notepad, and copied the string into the appropriate reg key:
2002,1944 3292,635 3352,3272 681,3268 624,673
Thanks, lewnetoons, for providing your info, as well:
1862,1960 3131,673 3129,3260 628,3291 635,655
I suspect my digitizer may need replacement because it wasn't terribly accurate before I encountered this problem, but I'll have to find a proper solution for the "Align Screen" loop for a new digitizer to even matter. This is enough to appease me for now, as my screen is now responding semi-accurately, but if anyone can come up with a fix for my align screen loop, so I won't have to rely on the "welcome.not" fix, I would appreciate it a LOT.
A little off-topic, but it seems to me that five points isn't enough to align the whole digitizer in the first place.
Thanks a lot, guys, I'm good for now.
Bob_Beard said:
Thanks for the help, guys. I found the kaiser.dat file in the program's directory, opened with notepad, and copied the string into the appropriate reg key:
2002,1944 3292,635 3352,3272 681,3268 624,673
Thanks, lewnetoons, for providing your info, as well:
1862,1960 3131,673 3129,3260 628,3291 635,655
I suspect my digitizer may need replacement because it wasn't terribly accurate before I encountered this problem, but I'll have to find a proper solution for the "Align Screen" loop for a new digitizer to even matter. This is enough to appease me for now, as my screen is now responding semi-accurately, but if anyone can come up with a fix for my align screen loop, so I won't have to rely on the "welcome.not" fix, I would appreciate it a LOT.
A little off-topic, but it seems to me that five points isn't enough to align the whole digitizer in the first place.
Thanks a lot, guys, I'm good for now.
Click to expand...
Click to collapse
glad you got it fixed my brother
It occurs to me that I may not have been clear in my first post. I didn't use NBHExtract or anything. I opened the exe with 7-Zip, extracted the larger of two nbh files, renamed it, copied it to my SD card, and flashed it to my phone. I don't know why I did it that way, and it seems like it sort of worked, but something was lost in translation. I've done half a dozen or so flashes since then, but the problem still exists. Any insight into a possible permanent solution for this semi-permanent problem would be very much appreciated.
So, I've gone through a few flashes and my screen alignment still works for the most part, but it can be a pain in the ass using programs that have have small expandable menus or buttons at the bottom of the screen. I can fine tune this a little better using my slow, primitive hand-modify the registry method, but I would still appreciate any input on fixing the problem.
I guess I'm looking for one of two possible solutions:
1. A program that does exactly what the built-in screen alignment utility does.
2. A way to fix whatever I ****ed up, so I can use the screen alignment utility without it looping infinitely.
So, once again, does anyone have any helpful input?
Bob_Beard said:
So, I've gone through a few flashes and my screen alignment still works for the most part, but it can be a pain in the ass using programs that have have small expandable menus or buttons at the bottom of the screen. I can fine tune this a little better using my slow, primitive hand-modify the registry method, but I would still appreciate any input on fixing the problem.
I guess I'm looking for one of two possible solutions:
1. A program that does exactly what the built-in screen alignment utility does.
2. A way to fix whatever I ****ed up, so I can use the screen alignment utility without it looping infinitely.
So, once again, does anyone have any helpful input?
Click to expand...
Click to collapse
try flashing abu's new rom that doesn't require screen alignment. see what happens.
I flashed it within hours of its release, but I'm not sure how it's affected me, since I still keep "welcome.not" in the root directory of my SD card, and I input my alignment config into the registry after every flash. I may expirament with it, though, by removing "welcome.not" and/or reflashing.
Bob_Beard said:
I flashed it within hours of its release, but I'm not sure how it's affected me, since I still keep "welcome.not" in the root directory of my SD card, and I input my alignment config into the registry after every flash. I may expirament with it, though, by removing "welcome.not" and/or reflashing.
Click to expand...
Click to collapse
yeah give it a try and see what happens