Related
I am having a very weird, and oddly repeating hardware problem with my HTC TP.
My original one started having this problem about 3 months after I bought it. The problem had two aspects - the screen appears as if the LCD material in it has moved or changed format (see image below) - and the touch function of it became problematic, often identifying the press in the wrong location.
I gave it to the vendor during warranty, and after some issues with the lab was offered a new device (it was indeed brand new, battery date indicated that). The new device - after less than a month - started having the exact same problem! (I'm giving it for repair tomorrow)
Is anyone familiar with this problem? Is this just a streak of bad luck? or am I doing anything bad to my devices? As far as I know - I'm not doing anything bad to them - the 2nd one was so short with me it haven't even dropped once. And before that I had a imate KJAM for 2.5 years without such problems.
Ideas?
It looks like too much pressure was applied to the LCD screen.
it is odd though - especially as it occured in such a short time on my new device, and I have not done anything especially bad to it
it definitely has the "feel" of a pressed LCD, but this is during rest. btw - in both times it was just the center area, and both cases a very similar size problem.
the only type of pressure I can think of is when it is in my pocket, but comeon, I am quite positive HTC did not design a device that can not withstand being in a pocket.....
it's a random defect that some screens get
and also a sign of worse things to come I believe
had a friend who bought a new one and it already had
it when it got it he of cause sendt it back
so I just coincidently got two of them ?!
That's quite jinxy
anyway - got today back my first phone, repaired (screen replaced).
Let's hope this doesn't re-appear.
Ofer.
sorry a little off the mark
e
i dont know if anybody has had this or a similar problem but i finally got my phone where i want it. i am running 6.5 on my fuze the only issue i am having is the phone dosent give me any vocal notification when someone is calling me while i am on the phone. i have already made sure that call waiting is set to notify me in the phone services but still dosent beep. if someone calls me it does come through cause if i am looking i can see it just dont hear it. it even alerts me after the fact telling me i have a missed call. just not during
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,
I have CyanogenMod-7.1on my HTC Wildfire.
I had rooted my phone around 4 months back. Everything seemed to work fine. Suddenly from past 2-3 days, I am having some with the touch screen. Touch is not getting registered in one specific line horizontaly across the screen. There hasn't been any physical damage, neither did my phone fell down anytime. This behaviour is consistent at the same location. (Specific Location : between 1st and 2nd lines on the keyboard) Can there be any software problem or there is an issue with the hardware. Anybody faced such issue previously?? Please help.
Where to start...
Basically I have 2 problems. Firstly. After getting a call that lasts (it seems about 5 or more minutes) the screen goes black. Nothing but a battery pull solves the problem. Yesterday I discovered the proximety sensor was a notable issue amongst users of the desire. I had a screen protector on. And where the sensor was it was scuffed. So I took it to my mates computer shop and he put on a new screen cover yet the problem still persists.. 1st problem.
2nd problem. All of a sudden my remote on stock headphones have stopped working. Can't skip tracks. Can't play from middle button and can't pick up calls via hands free. They are working sound wise. But like I said. No function with the remote.
I was thinking maybe an app is overriding the functions.
So last night. (i have a rooted s-off hboot phone) I reflashed satalite Rosie final version. And re partitioned the he card. (totally clean phone) still no remote function and black out still occuring.
This morning I think. Well running a sense 3.5 Rom on a a8181 might be the problem.. (even though it has worked before) so I flash qurpra v6 final edition.. same problem.. Not.liking some of the features of that Rom. Including battery notification fail. I reflash satalite Rosie.
I'm still in the same position I started.
Id like to add... No damage to the phone at all. It's pristine. Same goes for the headset. It worked fine (headset a few days ago) I just don't get it Tbh....
Thanks in advance for any help given
Sent from my HTC Desire using xda premium
Oh well. New headphones off eBay and the remote works so must be damaged.
New screen protector cleaned near proximity sensor and that's that sorted.
Just thought I'd add this because there are lots of people with the same problems. So Google says anyway.
Just thought I'd post possible solutions.
Sent from my HTC Desire using xda premium