Hi everybody!
I'm having problems with my Pocket PC.
It all begun a while ago, when a part of my screen stopped working (didn't respond to touches). So I did a hard reset. Then, it wouldn't pass the Align Screen procedure. So I made a file on the Pocket PC root folder called welcome.not - and it worked, the welcome screen was bypassed.
Now, however, everything on the screen is mirrored. Not the image on the screen but the response to my touches. So when I press the upper right corner with my stylus, it reacts in the lower left - and reverse, across the whole screen.
What I want now is of course a state like before the hard-reset. I can accept a part of the screen not working, but I want something at least to be useable.
I think this would be easily fixed by just running Align Screen, but that doesn't work - it gets stuck in a infinite loop.
Maybe there are some Align Screen "profiles" to place in the windows folder/registry?
I'm using a HP iPAQ 214 Enterprise.
Randor244
might it be a ROM problem?
Maybe, though I think the problem is that the screen is completely unaligned and therefore is totally wierd.
What I think I need is:
1. An application to browse the PPC registry from a desktop PC
2. Sceen align data to put in in the registry (I've read somewhere else that that data is stored in the registry)
Or, maybe I'm wrong
In case it is a rom problem, can I solve it easily in any way?
well to be honest, the first thing i'd do is switch a ROM... unless it's a ROM you got from XDA and is well-known..
if the rom switching doesn't work, i'd download a pda control app like MyMobiler or SOTI Pocket Controller to fix this. maybe you have hardware problems with your screen..
I don't know where the screen alignment data sits in the registry but i'm sure you can find it on this forum. if you manage to change and it still doesn't work... maybe replac ea screen? there's a marketplace section in which you might be able to buy spare parts.. and there are guide on dismantling so you can replace the screen yourself
well to be honest, the first thing i'd do is switch a ROM... unless it's a ROM you got from XDA and is well-known..
Click to expand...
Click to collapse
Well, I havn't got much knowledge on how to do these things... Could I get a brief explanation?
I know what ROM is and so on... but how to switch it... hmm...
I'm sorry, can't help you with that.. i'm not familiar with the iPaq... but I understand that you never switched a ROM so it's probably the original one.. and you shouldn't have a problem with it.
try aligning your screen using the registry.. if it doesn't work.. i'd go with replacing a screen.
Yeah, I would also like to align the screen using the registry - but how? I need to know some values to input, right? And as far as I know they need to be specific for my model
So how?
maybe you can contact HP and ask them?
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
A friend brought me a good one today. He has an AT&T Touch Pro with a touch screen issue.
He brought me the phone months ago and I flashed the ROM. All was good. He then deleted a bunch of files one night accidentally and hard booted the phone in an attempt to get the files back. Upon hard reboot the phone hung at the calibration screen and he could not get past that. To describe, the screen calibration works on 3 of the 4 corners, if you hold the press the stylus to the screen quite firmly, but the top right corner will not calibrate however long I told the stylus to the screen.
He brought it to me today and I figured that a fresh ROM would resolve the issue. So I loaded a new ROM and the phone hung again at screen calibration. So I did some research and found a "welcome.not" work around to get us past the screen calibration issue. This was successful and I was able to get us to the home screen.
The issue is that the screen is very unresponsive and I have flashed the device so it's not a ROM flash issue. Is there a driver he might have accidentally deleted that is not reinstalled on a ROM flash? I know I am probably grasping at straws here but I thought this community might have some insight to what the issue is.
I have also considered the idea that I may need to replace the digitizer for this phone if that is the issue and am prepared to do so but thought I would throw this question out to the community for any tips/tricks or ideas you may have before cracking the case on this thing.
Thanks for your help in advance.
--Mike
Oh and I forgot to mention that sometimes the screen works if you tap it continuously but most times, there is no response.
--Mike
Moved as not ROM Development.
Hey Mike,same issue over here.I couldn't find any solutions so far.By the way,what's that "welcome.not" thing?
Well,after some google search i ended up with this.http://bittangents.com/2008/10/28/removing-welcome-message-doctors-appointment-on-pocket-pc-2003/
I suppose that you were meaning that...right?
Check out this one too
http://forum.xda-developers.com/showthread.php?t=355010
The calibration of the screen
IWPantel - Thanks for referring to my blog
To stop the welcome message, you need to put the Welcome.NOT in the root of a sd card or of the device. I don't believe this is your issue, however.
There are typically three reasons why the screen will become unresponsive.
#1 You have a bad touchscreen. Assuming that the screen was working perfectly, I highly doubt this is your issue.
#2 You are calibrating the screen with the stylus straight up. Believe it or not, the touch point changes if you are straight up and down, or if you have the stylus as if you are writing. The angle will affect the touch point.
#3 You have a conflicting .reg file in the Application or Platform directory of the handheld. The calibration settings are stored in the device's registry and they need to be updated. If you did a persistant registry tweak (where it exports the registry into NV ram, the calibration settings will overwrite the calibration settings you create on system startup.
Feel free to contact me with any questions.
-Brent
brentblawat said:
IWPantel - Thanks for referring to my blog
To stop the welcome message, you need to put the Welcome.NOT in the root of a sd card or of the device. I don't believe this is your issue, however.
There are typically three reasons why the screen will become unresponsive.
#1 You have a bad touchscreen. Assuming that the screen was working perfectly, I highly doubt this is your issue.
#2 You are calibrating the screen with the stylus straight up. Believe it or not, the touch point changes if you are straight up and down, or if you have the stylus as if you are writing. The angle will affect the touch point.
#3 You have a conflicting .reg file in the Application or Platform directory of the handheld. The calibration settings are stored in the device's registry and they need to be updated. If you did a persistant registry tweak (where it exports the registry into NV ram, the calibration settings will overwrite the calibration settings you create on system startup.
Feel free to contact me with any questions.
-Brent
Click to expand...
Click to collapse
Brent, I had the same problem here! My Fuze simply stopped responding to my touchs....
#1 Taking this as true
#2 I tried a hard reset, but nothing happens. I can not touch the screen to calibrate
#3 I just can not understand what you proposed.
Please, help me!
I don`t know why, but my cell just back to normal!
Now it's everything working!
@brentblawat - How come you are a Junior Member when your answer is so hardcore.
Anyhows, I have the same problem with my phone, I have tried all the software tricks I could think of. I guess your point 3 asks us to manually enter the calibration data in registry. Have tried it doesnt work.
I cant replace the hardware as I have Tmobile MDA and I dont get the spare parts for this here. the digitizer is different from the one in Touch pro.
Hello all,
Awhile back the touchscreen on my Sprint TP2 (RHOD400) was off. I click in one spot, it clicks an inch high. Sometimes more, sometimes less..I tried calibrating, but I couldn't even click the center target once. The problem stopped for awhile, then started up again last week. This time the problem is worse. I press in one area, it presses one to two inches away. I have the phone in landscape mode and try to press the upper right hand corner 'x' and it brings up the notification window. Sometimes the lower right part of my screen is completely inaccessible, and I cannot send a text for quite awhile. Other times it is fine, but not fine to the point where I can get super accurate clicks. I was running Mr.X rom, and flashed to Mighty, but this did not solve the problem. I have also cleared storage. I used to run haret android for awhile, would this have caused any problems? I thought I should try that again since I can force the phone to use a calibration.txt file that works for sure, and see if the phone is "fixed" then. I guess my options are...
Try haret android again
task 29?
reflash?
be sad, it's a digitizer issue
(tldr) Touchscreen is off, but not always by the same amount. Reflashing wouldn't cure it and I can't calibrate it. Targets keep going around and around after the reflash, where before I couldn't get them to click even once.
Maybe one of those will fix my problem..I hope so, but I posted here to see if anyone else had heard of an intermittent touchscreen issue like this?
Thanks for reading/help guys.
Can a mod move this to http://forum.xda-developers.com/forumdisplay.php?f=488 Touch pro 2/Tilt forum? I feel as if I posted it in the wrong forum and I'd get more responses in the other. Thanks!
Have you tried pressing the two volume buttons at the same time to get to that calibration screen. Then try to calibrate and see what happens. If this does not work for you then I would think its a hardware issue.
i think my phonne is fudged up, its in perfect conditon and has no cracks,neither did i drop the phone or anything.
yesterday all of a sudden my hardware buttons ( bottom 3 buttons), and the lower part of the screen stopped working completely,not even in twrp,meaning i cant swipe to flash there becuase its in the part of the screen that dosent work.
anyone has any idea what i can do? i tried disabling and enabling hardware buttons,and resetting of course.
is there anything i can flash through fastboot to maybe fix it? maybe touch firmware or something
pretty sure its a hardware problem though
it was very hot were i live,so i think maybe the heat ruined something inside the phone
Experiencing similar issues
I am having the same problem, though I think I am a little more fortunate than you in terms of the amount of the screen that is not responsive. For the timebeing, I turned on on-screen buttons and allowed a full 180 degree rotation, which allows the button functions to work if the screen is rotated. It at least makes the phone usable for now.
Any help would really be appreciated.
Cheers
DjDafiDak said:
i think my phonne is fudged up, its in perfect conditon and has no cracks,neither did i drop the phone or anything.
yesterday all of a sudden my hardware buttons ( bottom 3 buttons), and the lower part of the screen stopped working completely,not even in twrp,meaning i cant swipe to flash there becuase its in the part of the screen that dosent work.
anyone has any idea what i can do? i tried disabling and enabling hardware buttons,and resetting of course.
is there anything i can flash through fastboot to maybe fix it? maybe touch firmware or something
pretty sure its a hardware problem though
it was very hot were i live,so i think maybe the heat ruined something inside the phone
Click to expand...
Click to collapse
I am having the same issue. I can't reflash anything as when I swipe in twrp, the bar only goes partway across the screen then just bounces back to the beginning. Been searching the web for hours trying to find a solution.