Lifeflash digitizer innaccuracy

[Merittman]

Fellas,

Run across this problem today with my Lifeflash (with powerdrive installed, 128 Mb RAM, 4Gb Flash Drive, 2 Gb SD Card). My touchscreen is functioning, but poorly. I installed Dmitry's powerdigi and discovered that only the top, right-hand quarter of the screen is sensitive to touch. Moving the stylus across this smaller box moves the cursor across the entire screen. I cannot accurately tap anywhere on the screen as it is. I cannot use powerdigi to repair this issue, since the stylus will not register as a tap anywhere below the half-way point. Is this:

1. A software issue, and if so, how can I fix it?
2. A hardware issue, and is so, will i need to replace the digitizer? Where would I go to find replacement parts.

I have read that a hard reset might fix this problem, but I want to identify what the problem is first. Any ideas? Thanks in advance.

Merittman

[dmitrygr]

sounds like some software wrote a bad hwrDensity value to your Os's windows manager globals. a soft reset should fix it. if not, try a warm reset, or a hard reset.

[joepagIII]

and if its determined its your digitizer i have a spare....however follow dmitrys advice....first

[Merittman]

I feel like I'm trying to reinvent the wheel. In doing some further research, someone pointed to Palm's website regarding touchscreen calibration. In an infinite loop (while trying to calibrate the touchscreen) they suggest that the problem might be something caught underneath the edge. To correct, they suggested taking a piece of paper (high tech solution) and going along that edge, dislodging anything that might be stuck there, and causing touchscreen problems. I tried this. I dislodged some dust, and a hair. The touchscreen now works across the top fourth of the screen, and the remaining three-fourths (the bottom 3/4 now, rather than the corner) are unreachable.

I have soft-reset the LF a couple of times now and the issue remains unresolved. After I backup all my data, I will perfom a Hard Reset.

[Merittman]

The Hard Reset seems to have fixed the problem. Now I'm back to my old digitizer problem (being a few pixels off), so far, as I'm reinstalling my software, everything's back to normal.

[Merittman]

As an aside, what software might be the culprit of this problem?

[Merittman]

Just a quick note. After the Hard Reset, I Hotsync'ed my data back to the LF, then I did a NVBackup Restore. I found I had a problem again with the digitizer. This proves to me that the problem is software-related. Now I hav eto carefully reinstall my software, rather than do a general restore. GREAT!

[_Em]

Try a general restore followed by adding CleanStart. Then enable your apps in sets and find out when you start having digi problems.

[Merittman]

If I could find out where this is:
"hwrDensity value to your Os's windows manager globals"
If its in a file that I can delete from my backup, I can restore the rest, right?

[icefireicefire]

No, this is a probematic setting left by a REALLY badly written app. Did you install anything new to cause this?

BTW, it means that it thinks that it is a 160x160 screen, not a 320x480 one.

[JavaJiveJump]

nice troubleshooting answer icefireicefire... how did you know about that?

[Merittman]

Thank you for getting back to me. Now that you mention it, this "badly written app" is most likely written for a pre-OS5 unit, right? I'm trying to think if I've installed anything recently that was really old. The only thing that comes to mind is Recycle, which was an old app for Palmpilots that attempted to defrag main memory. I never could get it to work on my lifedrive.

However, since the problem reappears when I do a full restore, it must be a file setting that is changed. Is there away to identify that particular file and just not restore that one, or this problem more systemic?

[_Em]

It's probably a setting embedded in one of your prefs files or other OS config files; I think we have a list around here somewhere of the usual suspects; I can't remember it offhand though.

Icefire is correct that it was most likely caused by an app that assumed all Palms were 160x160 and wrote something back to an OS database based on that assumption.

[Merittman]

Let me attack this problem from the other direction. Are there any apps out that will protect the 320x480 settings in the OS? Or perhaps rewrite the OS settings to correct any problems?

[dmitrygr]

yes, but i never released it
[man, what a common answer :-) ]

[_Em]

Just so people know: that answer of Dmitry's isn't saying "yes, but I'm unwilling to let anyone else have a copy of this wonderful software" -- it says "yes, but you need to have my level of knowledge to be able to use it safely in its current state. I haven't felt it was worth the time needed to get it polished up for the general public."

[joepagIII]

hey its better than releasing hal fa@@#@ written code...

[Merittman]

Dare I ask for a copy? Or an idea where to look? I would love to restore my original settings, or have a program that would protect the 320x480 settings and/ or restore them after they've been written over. I may be the only LF user with this problem, but if there are programs out there that corrupt the integrity of the interface, we all might do with a little protection. I'm not a programmer, so I don't know how complex this issue is. This issue sounds like a vulnerability to the OS, if an older program can alter the UI settings like this. Wouldn't a patch like this be important?

[joepagIII]

did you use nv bacukup if so have you tried say a selective restore....if your setup is anything like mine it could take a good long time to figure it out....go to your palm folder and look and see what you have installed .....may not help but wont hurt to look

[Merittman]

That's why I wondered if anyone knew exactly what files needed to be edited out. I know a restore causes the problem to recur, so it must be one or more files that are causing the bug. If you are saying that its an application, rather than a single file, then you are right, I have my work cut out for me.

[joepagIII]

any luck with your problem

[Merittman]

As of today, I've restored my essential files to my LF, and have not had the digitizer problem yet. I've saved a secondary backup of my present state, since only a hard reset (or quick reset) eliminates the problem. This is the only solution I have at this time.

[joepagIII]

well im glad its somewhat resolved...