Related
My Treo 750 (WM5) from ATT touchscreen periodically stops working... I just got it a few months ago. After a soft/hard restart, the touchscreen will work for one click then stop working.
When the screen is dim, and I touch it; it lights up and becomes bright again. So it's responding to touch... just not when i select any buttons, etc.
I tried the align screen, but it can't get pass the first cross hair... so I have to do a soft restart.
All I've installed is Microsoft Live, Google Maps, Good Messaging, and the HSPDA hack.
It was working with all of those apps without any changes for about a month.
Any ideas why the touchscreen stops working?
I would like to upgrade to WM6... but I am afraid that if it's broken and I bring it back to ATT they'll say it was because of the unoffical WM6. Is there a way to backup my WM5 and upgrade to WM6?
I have the same problem with my Treo 750 "German Version". The Hotline from Palm was very competent and I send the Treo to repair. After the repair it works fine. I think the best way is send it to reparation
Good Luck
Oliver
I have had exactly the same issues on two units, the first one was replaced in the first month return to base policy.
The second one was replaced after some discussions with Palm technical support, they asked me to Hard reset etc. with no resolution to the problem, so they instantly offered a replacement.
The replacement from Palm has been fantastic, it was 1.16-RWE, and is now 2.23-RWE., so I ended up with a non-branded phone as well.
And same here too. At 3 weeks, my new Treo, started to not respond intermittently. A few days later, the touchscreen failed completely and I ended up with keyboard input/navigation only. Service provider sent me a new unit (as failure was within their 30 replacement period). Now I'm on day 15 of my second 30-days and hoping this one will be OK.
I had the same issue few months back when I first got mine. Did some search and saw several others have the same problem. Exchanged it for another one and has been working fine.
I believe it was some type of hardware issue. If you let your Treo sit powered off, it will come back for a life, but only long enough for it to "warm up."
hi can you guys tell me how to contact AT & T for replacement? what's the number to call and how would i know if it's till under warranty? please let me know how.. i have a cingular unit, unlocked. I'm in the Philippines right now. please help me, I am very frustrated right now since i cant get my touch screen to work.
whoopsie said:
hi can you guys tell me how to contact AT & T for replacement? what's the number to call and how would i know if it's till under warranty? please let me know how.. i have a cingular unit, unlocked. I'm in the Philippines right now. please help me, I am very frustrated right now since i cant get my touch screen to work.
Click to expand...
Click to collapse
answer anybody?
I just sent an email to palm, in Australia, they replaced the unit.
Just go to your counties palm web site and look under support.
Replacement is the only fix I think. Mine has been working great since it was replaced.
I recently had a problem with my 1st Touch Pro with image ghosting/ burn in and ive just had it replaced. Now the same problem is happening with the new device. The problem only seams to happen with custom roms being used on the device. If i re-flash my phone back to the default/stock rom i get no screen problems at all.
Any idea why this only happens on custom roms and not the default/stock rom??
edit: ive attached an example of what i mean in image ghosting/burn in. Just in case some people wasn't sure what i meant by it.
More info?
Heya! What was the last ROM you had this problem with? Version info would be extremely helpful as I have heard that specific builds have some graphics bugs.
I've had that same issue as well on 2 different fuze's. Using various builds of EnergyROMs... However, after reflashing to stock and using it awhile, I'd get the ghosting on that too.
Anyone have any ideas?
Ehh my 2nd Fuze is doing this so I'm getting a replacement, and I'll just do the HTC ROM upgrade and keep WM6.1. I'm tired of it, and the landscape view also distorts the start menu icons 90% of the time.
Having flashed back to a stock rom, doing a hard reset... Playing with it for awhile... The ghosting is evident on it as well... I've also had where the bottom section of the screen will flicker quickly...
Anyone else?
I think it's a hardware defect. My first phone did that, and then after a few weeks, I had to get a warranty replacement because the screen eventually went completely black after doing it intermittently).
I've had both ghosting effects & occasional rapid flickering since I first bought the Fuze back in November. It's intermittent but happens most when the device is hot (either from use or simply being in a hot location). So far it always clears up after a while. This happened on the stock rom and every custom rom I've used so far.
I'm fairly certain it's a hardware issue with the Fuze/TP because the ghost will tend to remain there for a while even after a soft reset.
Hopefully my good fortune continues and it doesn't end up breaking permanently some day.
it is definitely a hardware issue.
I just received a "repaired" phone back from HTC today only to turn it on and find the same problem. I had to call again today and complain...and the only thing they could do for me was ask me to send it in again....so pissed.
I literally got 5x FUZE replacements and each had this until this last one I've gotten...!
Vid: http://www.youtube.com/watch?v=fFb4bQomqPw
Thx
JFlitt
JFlitt said:
I literally got 5x FUZE replacements and each had this until this last one I've gotten...!
Vid: http://www.youtube.com/watch?v=fFb4bQomqPw
Thx
JFlitt
Click to expand...
Click to collapse
were they replaced through HTC or ATT?
I am on my third Fuze.
First day when I upgraded to Fuze the screen started doing this. So I took it back to AT&T for replacement. On the drive back home screen on second device started doing exact same thing. Took it back and got yet another replacement. This one works, but I have seen it happen once or twice in the 3 or 4 months I've had it.
AT&T also told me when I got this phone that it was the last exchange I could make for the 90-day exchange. If I had another problem I'd have to send this back to the company. WTF is that all about? You're going to inconvenience me because you keep giving me bad eggs? At least this one works right.
Is anyone with a Touch Pro having the same issues? Or is it all just us AT&T customers?
I have an O2 Xda Touch Pro. The only symptom I have that remotely resembles the ones listed here is the flickering at the bottom. But, in my case at least, the flickering is caused by a particular shade of gray displayed in Opera...and that's the only time it happens. So, again for me, it seems to be a software issue.
Drew
Flickering is another side affect that mine occasionally has... just in the bottom 1/5th or so of the screen... Most easily seen when in landscape mode in messaging.
those are all hardware issues too, its just only being displayed because that certain shade of grey is whats making it visibly noticeable.
Well, we'll see if replacement number 4 has the same issues soon...
They actually offered me a BlackBerry Bold/9000 as a replacement phone like it is even in the same universe.
Hardware differences?
Anyone with a buggy Fuze want to post the part number / sku number etc...? Maybe we are looking at a bad batch or a bad but unannounced hardware version?
I had this too on energyrom, I allways passed it off as a touch flow 3d opengl issue which would draw to the screen.
But thinking about it, it does occour when the device is hot, and the screen flickers also.
But It allways goes away after a soft reset for me.
Vodaphone UK TP
I have this problem too :/
Well, I just got my replacement, and it is doing it as well. I'll post some screen shots of it later on today.
Anyone want to tell me what numbers we want/need?
I love my Touch Pro - really I do, its got all the features I want currently (except a digital compass would be good with some AR software, but that's not important roght now).
However, having got my first TP back in February I am about to send my handset back yet again as it has died again.
The first handset had a serious problem with battery drain and switching itself on (ie screen on) when not in use - I posted here about this at the time (clicky).
The o2 UK repair centre (Anovo) first of all said they'd fixed the fault, but after two weeks the phone was doing the same again - I did confirm this was not a software issue by running it ofr two weeks without any of my usuall applications on it.
So it went back again and was returned 'No Fault Found'.
At this point I demended a replacement handset. The replacement I received (a refurbished unit) had a speaker fault - crackling whenever the speaker activated, ie before a call connected and during.
That one went back as well and I ended up with an SE X1 for a while. OK but not a Touch Pro (and wouldn't run my legitimately purchased Tom Tom Nav 5 s/w). This was because o2 UK said they had no more stock of the Touch Pro and wouldn't be getting any more (why? too many problems with it?)
Eventually I got a call from o2 after numerous letters of complaint saying that they were going to exchange the SE X1 for a brand new boxed Touch Pro.
I have had this brand new replacement since August now.
About a month ago it died on me again. It just wouldn't switch on. Disconnecting and reconnecting the battery resulted in the flash on the back flashing, the handset vibrating (as though it was starting up) but nothing else.
Connecting the charger resulted in the flash on the back flashing bright about every second.
A hard reset would not work at this stage.
After a couple of days I heard the 'battery low' sound from the drawer that it was stashed in. SO tried a hard reset again - nothing. Tried a hard reset again with the charger plugged in and it reset and cam back to life.
... for two weeks...
then it died again.
This time is very similar to last with theflash falshing thing, except that if I try a hard reset it seems to go through the motions but without the screen coming on (ie the vibration. The beeping sound. Click the volume down and it pings again as though its starting the reset, then about a minute later the vibration again as though its restarting after the reset). But the screen doesn't come on at all. And the lights don't light up on the front buttons or the keypad.
Unfortunately I didn't have myMobiler installed on the handset so I couldn't try connecting to it from my PC (myMobiler did try installing but as I couldn't click the 'OK' button it didn't complete).
So. Are my four deaths of the TP unique or has anyone else had similar problems with this handset?
-FM
Not I.
I have had my Touch Pro (AT&T's HTC Fuze) since December 2008 and I have not had a single real problem with it. I say "real" because I have had times when I couldn't get a GPS lock and of course the phone is slow sometimes, but that's what I've come to expect from HTC.
Anonymitee said:
I have had my Touch Pro (AT&T's HTC Fuze) since December 2008 and I have not had a single real problem with it. I say "real" because I have had times when I couldn't get a GPS lock and of course the phone is slow sometimes, but that's what I've come to expect from HTC.
Click to expand...
Click to collapse
you need the 1.14.25.35 radio. and a different rom. maybe atts 5.11 rom if you want to still keep it stock. 1.14.25.35 is atts radio too so that stock and wont void your warranty as well.
Fuze Died Today, I Think
I've used this fuze since December of 2008 and have been quite pleased with the performance. (considering that it IS Windows) My signature radio works quite well in the mid west North America and travels well through different data protocols. Like H to Edge to GPRS and back to 3G again.
Today I flashed a new rom via usb and now it won't pass the splash screen. That flash appeared normal in all respects. Tried several hard resets (to the bootloader screen) and have tried to re-flash a different rom via micro sd card.
I've begun to think that this may be a hardware failure and would appreciate any advise for troubleshooting. Keep in mind that device will NOT connect via usb.
my screen went white a couple days ago. it would end up showing the windows logo for a while then a white screen. i hard reset a few times but nothing worked so i reloaded atts 5.11 rom and now it just stays at the "initial setup of the touchflo interface may take serveral minutes please wait" screen and wont get passed. i saw another thread about the white screen months back but i cant find it again. im just gonna wait till they have tilt2s and claim it under warranty. im gonna miss having flash, i use it to light up everything, but im sure a larger screen will make up for it.
Well I now have a bit more info on this since the phone cam eback from 'repair'on Saturday.
All they had done at the repair centre was to 'reload software' (their words, not mine). ie I guess they flashed the ROM again.
It worked for a day, though I guessed that was more coincidence than anything - after all, when this handset first did this a few weeks before it suddenly started working again a few days later.
Luckily in that time I'd remembere to install MyMobiler this time, and so when the screen died I connected to my laptop and fired up a remote view of the phone.
The screen itself was dead, but everything else seemed to be working on the phone - except that while the screen was dead I had an error displayed on screen. The error was "MicropERROR" as attached here.
So I Googled the error message, and what a shock a nice long thread on XDA-dev about it. Seems it s a fairly common problem with the Diamond, Touch Pro and Touch HD. Joy!
So the phone is now back with 'o2' again for another 'repair' this time with the attcahed screenshot enclosed. I have been warned again, though, that the Serra is out of stock and if they can't repir it I may have to select a substitute. As far as I am concerned there is no substitute - there is no other phone at the mo with the Touch Pro's features (hardware keyboard, VGA/WVGA screen, A-GPS, g-sensor, WinMo, runs TomTom Nav5).
I fear the worst again, and fear I'm back where I was in July with an impossible choice to make thanks to o2 UK discontinuing the Serra / Touch Pro after a few months of supplying it.
-FM
well i got my TP back in March.09 and last month i have to replace the mother board and the back speaker other than that all is good so far
but i was so frustrated with HTC support centre (which is the main one in Taiwan ) real unpleasant experience as you all may know
Cheers!
Time to send mine back
Just had an issue with my last one, it was only 5 months old and the screen started looking like it had a vertical hold issue. Just got my refurbished one in Wednesday and now it is doing the same thing after playing games on it for 5 minutes. The speaker phone is crackling too for some reason and when charging it at night it's like the screen will not fully black out. I am wondering if I even want to try another one of HTCs products or not. Nice phones but to many headaches it seems.
Hi everyone,
I bought a Oneplus One in past July with enthusiasm.
After few days of use, began the "ghost swipes" issue (as every owner of the One) and multitouch issues (my phone is basically recognizing 1 finger at the same time) preventing any pinch to zoom or notification expand gesture.
But that's not the worst, after few weeks of use, began the most annoying issue I ever had on a device : my touchscreen is going crazy detecting contacts on the touchscreen by itself.
This issue began slowly but is getting worse over time. I noticed that the issue appears only after keeping my phone on my pocket for a while... I need to wait up to 10 mins after taking it out for the problem to disappear.
At first, a simple reboot was temporary the issue but not anymore. It's simple, I only can use my phone 10% of the day... During the remaining 90% it calls numbers, takes photos, deletes messages by itself...
Watch this video, it speaks for itself :
I do not know if anyone else has the same issue or not and I can't determine if it is a software problem, a hardware one or a combination of both...
I opened a support ticket on Oneplus website (but it seems I won't have answer before a few weeks... ) and I don't even know if they will accept doing a swap (OPO support is one of the worst I know).
What's sure is I am really disapointed by this device, whatever its price tag... And I won't recommend it to anyone and I won't give out my invites.
Guys, don't buy this phone and wait for the next Nexus device with which you'll have a high quality device at a decent price...
I let them a little while to find a fix to this situation and if nothing comes, I'll buy another one and use all means at my disposal to be refunded (the French law is quite helpful in the field).
.ant1
There are many users facing this issue. Check around the forums you'll see numerous threads about this issue, you might also find some tips to reduce the issue.
AFAIK this is as of yet not permanent fix for this issue, but since i dont have this issue i havent been following it so i might be wrong. Good luck though.
Google "bacon 55"
Sent from my OnePlus One using Tapatalk VIP
The only solution is to RMA the device. Took me 6 weeks of haggling with One Plus but finally the RMA is in process.
I blamed OnePlus for months for not doing anything for the annoying problem related to the touchscreen panel in a lot of models of the OPO. I was sure it was an hardware problem and only a RMA could have done something for me. I couldn't return my phone cause i always need it and i didn't have alternative phones to use. So i just gave up, living with some not-extremely-frustrating-unresponsiveness during fast typing.
But...
After installing the last official CM11S update (the 05Q one), i noticed some strange responsiveness during a chat with a friend. I was curious, so i reinstalled YAMTT for some test. I couldn't believe that all my inputs were perfect even at fast speed. I still don't know if it was a software or hardware issue, but OnePlus seems to have finally fixed my situation.
Looking for your experience after the update.
Elvecio said:
I blamed OnePlus for months for not doing anything for the annoying problem related to the touchscreen panel in a lot of models of the OPO. I was sure it was an hardware problem and only a RMA could have done something for me. I couldn't return my phone cause i always need it and i didn't have alternative phones to use. So i just gave up, living with some not-extremely-frustrating-unresponsiveness during fast typing.
But...
After installing the last official CM11S update (the 05Q one), i noticed some strange responsiveness during a chat with a friend. I was curious, so i reinstalled YAMTT for some test. I couldn't believe that all my inputs were perfect even at fast speed. I still don't know if it was a software or hardware issue, but OnePlus seems to have finally fixed my situation.
Looking for your experience after the update.
Click to expand...
Click to collapse
Not yet they aren't. It appears to have affected the functionality of double tap to wake for some people.
Doesn't seem like they're updating us on the investigation either. If they've fixed it using software, at the very least they should tell affected users why all the previous updates didn't work for them.
I've been on the nightly road since mid August, in my experience touch issue improved a lot after the touch firmware update in October, however there are still very rare cases where finicky / unresponsive touch happens, you don't want that when you ask someone for her contact in a bar on Halloween and she can't input the letter 'n'.
After that I think I experienced touch issue twice, I foolishly thought this was fixed sometime ago, however it came back big time the day before yesterday, and I was on the latest nightly... So in short, touch issue is not gone
touch issue
even im having touch issues with double tap and typing.
Touch screen seems less responsive since this update
Sent from my A0001 using XDA Free mobile app
anuradha1208 said:
even im having touch issues with double tap and typing.
Click to expand...
Click to collapse
William Haven said:
Touch screen seems less responsive since this update
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Do you guys have any problems with vertical scrolling (i.e. in lists, webpages etc.)?
I'm thinking about downgrading... I'm currently running CM12 nightlies and the touchscreen is annoying me
vantt1 said:
Do you guys have any problems with vertical scrolling (i.e. in lists, webpages etc.)?
Click to expand...
Click to collapse
Everywhere
this is hopeless, I just went and looked at touch firmware updates, last ones are 1221 at the end of october and 1222 around new years, I remember it working ok during that time, and some time after that, how come I am experience severe touch issue these couple days, touch turned into swipes, swipes registered as touches, unresponsible parts on the screen. I am almost beginning to think it's about the weather/temperature, problems are more frequent when I am out hiking for a long time.
although somebody mentioned that last change was having problems days after http://review.cyanogenmod.org/#/c/83558/
st11 said:
this is hopeless, I just went and looked at touch firmware updates, last ones are 1221 at the end of october and 1222 around new years, I remember it working ok during that time, and some time after that, how come I am experience severe touch issue these couple days, touch turned into swipes, swipes registered as touches, unresponsible parts on the screen. I am almost beginning to think it's about the weather/temperature, problems are more frequent when I am out hiking for a long time.
although somebody mentioned that last change was having problems days after http://review.cyanogenmod.org/#/c/83558/
Click to expand...
Click to collapse
There are at least two different touchscreen issues as far as we know:
One is where the touchscreen is semi-terrible all the time regardless of temperature
The other is where the touchscreen becomes unresponsive with the increase in temperature, and subsides if the phone is restarted or cools down
Is there a way of finding out which firmware is being used for colorOS?
I can't take this anymore, I am considering flashing either 44s or color OS