By my count...

moishe
joecentral
CaptnHowdy
JohnGrayson
rhanson
manders
hippie
dcpoppy
c500capt
bgav

Edited to add the following:

TedK
Abssprint

That's 12 (As of 7/8/05).

Brian

This message was edited by bgav on 07/08/05 09:01 ET.

Are you also including all the people who have had dim backlights develop in last several weeks? If so, count me in too. These people should be included in this poll. Same situation but a different problem.

add me to the list also....

Mine also crapped out on Tuesday..Man I hope that somebody comes up with a fix..I don't have the extra cash to just run out and get a new remote..Philips should take care of this!!!

Not a touchscreen issue, but I have posted a couple of threads elsewhere on RC that highlight 2 problems;

1./ Would not accept a .pcf of more than 299K, yet said memory was 83% free!

2./ InfraRed signal suddenly very weak ( see thread Faulty(ish) NG950...)

anyone else experienced these?

I have a customer who is bringing his back to me for the same screen problem. I was able to fix it the first time by sheer luck, but now it has the same problem. philips should take notice!! this in my opinion is a firmware issue.

Robert,

I don't think this is a firmware issue. I was solid on 2.3.9 for awhile, and suddenly one day no response. That's when I started playing with firmware, and then got some response but no calibration. Now I'm back at No response from touchscreen, but the hard keys respond. I think it's a hardware issue as bgav suggested.

I will also respond to the prontoteam e-mail addy. This forum is bittersweet. At least I'm not the only one experiencing this problem, but I feel bad that so many other people are going through what I am.

I think it still is a firm ware issue due to responce time of keying. touching the screen gives multiple commands (debounce) confusing the firmware that is the only explanation I have. It is possible that the screen could be defective I'm not ruling it out.
never the less so many of us are having this problem and Philips should investigate and correct.
Bob

You can add me to the list. The touchscreen on my TSU3000 stopped responding completely with firmware 3.1.15. I attempted to upgrade to the new firmware and got an error half way through the upgrade. The unit is now completely dead.

I started this "poll" for TSU3000 owners who are having touchscreen, backlight, and calibration problems. The poll has a standardized format for people to report their problems.

Brian

This message was edited by bgav on 07/09/05 08:18 ET.

Before checking the forums I saw that there was a new firware upgrade for the TSU 3000. I decided to downlad it and installed it. I had the same calibration issues as most people posting here. I then decicded to downgrade my firmware and now i get nothing on the remote. Going to email the Prontoo team and have them fix this dam thing! I hope that they going to fix this thing for no charge, they created this problem by releasing bugged firmware to to fix bugged firmware!

Posted this in the roll call thread as well. It has been a year, so I forgot that this isn't the first time I've seen this behavior:

[Link: remotecentral.com]

I found the older software versions.
Can you explain via email how to downgrade firmware.
Thanks for your time.

Now same problem in my one and a half year old Pronto Ru 950. First time a month ago touchscreen stopped to work for two days. Then it works whole month and now it's dead again. I send e-mail to prontoteam but no answer. I start to look another programmable lcd touchscreen remote without word Philips. Any suggestions?

I am a long time lurker of RC and today when I returned from a two-week vacation my remote just wasn't working. No one had used it in the two weeks I was gone and it was working fine before I left. The touchscreen is just all of the sudden unresponsive, although the hard keys get the remote to light up. I upgraded the firmware... no luck. So I came to RC and, low and behold, there's a thread a mile long on this issue beginning only in the last month! That seems way to coincidential to me. I've helped a lot of friends program their remotes and I am just waiting for the calls to start rolling in on why their's simply stopped working.

Clearly this must be a manufacturing/firmware defect of some sort for which Philips should be held accountable. I'll be sending them a letter because it seems emails aren't doing the trick. I'll keep everyone posted (pun intended) and checking back in case someone figures out how to fix the thing! I'm just happy to hear I'm not the only one out there. Thanks for the posts...

This message was edited by slapo on 07/20/05 23:39 ET.