Related
Hi all,
I am at my wits end on this problem if anyone can offer any adivice it would be greatly appreciated. So let me give a recap of what has occured thus far. The water damage tag for some reason turn pink thus i am unable to get warranty exchange. I am pretty certain that the phone has never been expose to any water of anything of that sort, but i do live in houston, tx so might be humidity or what not that cause the tag to turn. Anyways.
1. This all started after i flashed RRE 5.2 RC3. Initially after a successful flash everything seem normal and fine. Then next morning i woke up to a frozen screen with many verticial lines running up and down the screen was almost unreadable. Initially i thought it was a bad flash or just random lock up. I did a hard reset and tried to enter the bootloader. Black screen, it does seem like the backlight is coming up but nothing on the screen. I can hear the phone power on and boot successfully into windows. Activesync connects i can browse the contents of the phone.
2. After flashing to stock att rom and stock htc roms same symptoms. So at this point i am thinking crap bad LCD screen. so I ordered both the digitizer and lcd screen for good measure. I replaced them hoping that a bad LCD was all. replaced both screens and i powered on the phone. same problem. black screen. The phone still powers on and boots into windows. Activesync still connects and i cna still reflash the phone.
3. I work extensively and do both desktop pc and notebook repair. I am not new to dealing with small electronic repairs. but at this juncture i am unable to identify the cause of hte malfunction. i am hoping maybe some of the gurus here might be able to shine some light on the subject.
Thanks in advance for any help.
I would have followed the same approach; your description makes it sound like it might be some kind of backlighting issue at first read. I'm inclined to think it might be a cold connection (bad connector) on the main board.
Silly question, what happens if you power up the phone with the keyboard exposed?
*EDIT* Not sure if you have been here yet: http://www.mikechannon.net/
Cheers,
i just tried to power up the phone with keyboard exposed. Powers up the same as with the keyboard hidden. Still boots up fine but black screen. I already have the service manuel dowloaded. i have checked around with several repair places both local and on the web. Seems like no one has any parts for the att fuze/touch pro gsm except for the lcd and digitizer and a speaker.
its quite possible that it is a main board but as the same time it might be something as simple as a ribbon cable. i have contacted htc about doing a possible repair and they want wayyyy too much for just a main board repair almost $400 USD.
Anyone have a bricked/ non working touch pro they would like to sell ? =P
fkoong said:
its quite possible that it is a main board but as the same time it might be something as simple as a ribbon cable.
Click to expand...
Click to collapse
Could be a bad ribbon cable ... and firmly pressing around the front/back of the unit shows no change?
pressing the phone front and back show no changes to display. in a very dark room I can see that there is light emitting from the display but its just the screen is not displaying anything visable. this occured both before and after i changed out the screens. I'll do another visual inspection of all the boards to see if there is any bad resistors burnt out circuits etc.. but i didn't notice anything mentionable during my first 2 inspections. Maybe 3rd time is the charm.
Thanks for all the feedback thus far Hilaireg it is quite appreciated. All this venting has at least made me feel 1000% better than after i replaced my lcd and still same problem at least i don't feel like a complete idiot!
Sorry I couldn't be of much help ... you've done all the steps a seasoned hardware person would do.
Do post back to let other folks know if you get it back up and running.
Cheers,
you have a pm fkoong.
I have possibly the same problem. Phone got wet, dried it out for 2 days (in a container of rice). Phone worked but had "water marks" on screen that disappeared after two days and everything was fine for about 2 weeks. Then one day (happened to be humid misting rain eve in Charleston) the screen is blank (hint of backlight only). A soft reset and it seems OK for about 1hr, then blank again. The hard resest screen displayed OK (readbale text etc), but didnt work. But as I write this, I retry to document it results correctly and the NATF ROM is reloading and the screen works! We will see how long!!
Well.. not that long, the end of the ROM load and it went blank again, seems like a video driver problem. The Press VoluP to boot does show some red artifact.
Trying hard reset again (No SIM no uSD)
The NATF v4.4 loads and gives me the Tap screen, Align Screen, stylus, loads customization, opera, tf3d, then loads a bunch of files under ...... and then the screen goes blank again, seem like what happened last time, so Ill try loading a fresh ROM copy... later
Hey guys,
I am going crazy here, searching forums did not help me at all.
The lower section of the screen keeps flicking, and not always, what do i mean by flicking, its like the screen at the lower section keeps doing like a strange low refresh rate, and has an old imprint of some old menus. Happens especially when there is the color of gray.
Made a screenshot of the phone, no problems, there, so its not a software rendering problem, might be a drivers problem though, or a defec tin the screen itself.
Frequency is high but not always, and am unable to determine when does that happen exactly. going crazy here, is this a defect? or all touch pro's have this?
Exact explanation summary:
1CM from the bottom of the LCD sometimes flickers as if that 1CM is having an extremely low refresh rate. Mostly happens when there is light gray, but not necessarily, and a soft reset for the phone does not remove it. It happens on random!
Hey,
Yeah it happens to me too! You don't need to do a soft reset, it actually fades away if you watch it closely! I don't know what it is either, and yes it is random as you have stated! I initially thought it was an application I installed as it only started happening after that, so I did a full hard reset and its still happening! Not sure what or how, but hoping next firmware version stops it!
Cheers,
mpls-te
As it happens, that's exactly why I've logged on here today! Any ideas whta the cause might be?
OK, good to see that others have this, so am not alone here, experts here, any ideas? other touch pro users, can you please leave your statements?
I hope its a driver issue.
But from what i noticed, its like, the screen is OFF, as in blank and no back light, but somehow, the application working on the screen before you turned off the device is somehow printing something on the LCD, something that we don't see, and when we actually start the phone and its back light, that OFF LINE imprint pops on screen. Something like that.
Its completely illogical, but dunno, can't find any sense here and am going crazy
Same thing happened to me and a few others as well.
See my thread here.
What rom is everyone using?
I've noticed a similar issue with mine, except rather than something software it seems like it's the backlight for the bottom 1cm of the screen flickering slightly. I don't see any weird pixels or inappropriate screen information, just a dimming/high speed flickering of the backlight in that same regionas yours. It comes and goes. Sometimes weeks without it, then maybe 3 times in a day for a minute or two at a time. Everything else works fine and whatever screen I go to displays fine.
I'm assuming it's a hardware problem with the LED(s) that light up the bottom portion of the screen, and I'm going to use it as an excuse to get a warranty replacement somewhere near the end of the warranty when the phone's getting a little old and worn.
maxh said:
I've noticed a similar issue with mine, except rather than something software it seems like it's the backlight for the bottom 1cm of the screen flickering slightly. I don't see any weird pixels or inappropriate screen information, just a dimming/high speed flickering of the backlight in that same regionas yours. It comes and goes. Sometimes weeks without it, then maybe 3 times in a day for a minute or two at a time. Everything else works fine and whatever screen I go to displays fine.
I'm assuming it's a hardware problem with the LED(s) that light up the bottom portion of the screen, and I'm going to use it as an excuse to get a warranty replacement somewhere near the end of the warranty when the phone's getting a little old and worn.
Click to expand...
Click to collapse
Lool, evil, lets just hope that this problem DOES occur when you go to their shop for your replacement
Good idea though, might do the same thing except that i have to travel abroad to where i got the phone from to actually get the warranty working. Don't forget to re-enable stock SPL and stock ROM
It happens frequently enough I'll be able to get it on video just in case they need proof, but typically they just exchange by mail.
I just posted in another thread about this issue. I have run into the same thing a few times. The bottom portion of the screen flickers, and when i do things that have a dark gray or black screen I can see a ghost image of the left and right soft keys from my TFL3D home screen. It seems to be most noticeable when the screen brightness is set to max. To get it to go away I usually do a few soft resets, and then, if needed, i will turn off the phone and take the battery out for a while. I have never tried waiting it out to see if it will just go away on its own.
proj3ktpat said:
I just posted in another thread about this issue. I have run into the same thing a few times. The bottom portion of the screen flickers, and when i do things that have a dark gray or black screen I can see a ghost image of the left and right soft keys from my TFL3D home screen. It seems to be most noticeable when the screen brightness is set to max. To get it to go away I usually do a few soft resets, and then, if needed, i will turn off the phone and take the battery out for a while. I have never tried waiting it out to see if it will just go away on its own.
Click to expand...
Click to collapse
I see that everyone posting in this thread,that has their signature filled in, is using the Energy ROM. I find that very interesting.
i am having the same problems, sometimes touchflo3d will flicker at the bottom, near the edges. I also get text that can be read through other screens. Like on pocketshield i can see the left and right softkey words still at the bottom. its so odd !
P.S im on energyrom
I'm on NATF v2.2, not an energy rom. But then again, mine looks more like a hardware issue, as I've never seen any ghost images of text or softkeys, just flickering.
can somebody post screens?
maybe the same problem here...
hardreset, other roms > problem still there:-(
Same problem here and I am using stock rom!
here are 3 screens of my xda diamond pro, using latest official o2 rom and newest romeOS eng
hope you can see this prob?! same like yours?
climber1872000 said:
I see that everyone posting in this thread,that has their signature filled in, is using the Energy ROM. I find that very interesting.
Click to expand...
Click to collapse
Well, i doubt EnergyROM has anything to do with that problem, since my Stock ROMz had same problem, never got fixed with any updates HTC used to release. MAYBE some Cooked ROMs out there have this solved, if any, please let us know And my problem is nothing close to screenshots above :S
mj084 said:
here are 3 screens of my xda diamond pro, using latest official o2 rom and newest romeOS eng
...
hope you can see this prob?! same like yours?
Click to expand...
Click to collapse
Dude, those photos are awful, after seeing them am happy with my phone flickering, its nothing close to this.
You see, in your photos, all three of em, you some kind of shadow effect, where text of a button for example has that same text beneath it 3x6mm, that is not my case at all.
My case is as follows, IF i am on the home screen for example all looks ok, except that the bottom 1CM of the screen is flickering. If i go to another window, either a total black one or any other screen, i would still see a ghost of the old home screen, for example, and only at the bottom 1CM.
Will post photos once i get my cam back. Cheers
similar issue
my issue is kinda similar, instead of getting the bottom 1cm or so discoloration or stuck pixels, I get streaks of red or blue on my screen. I have had this happen on each version of NATF I have tried, but don't remember it happening on the stock version (which I am tempted to try again to see if that's the issue).
Could this be a driver issue?
mind is even worse than all you guys, the touch screnn dose not response, and i have the energy rom on it, before it goes wrong. it just suddenly dose not response, than i send it to HTC, they ask for 425.00 for fix.... I will just send this to Asia and get some one to fix it.
But I hope before i send it out, some one can help me here.... anyway can fix it easy!!!!
Hi all, i have the same problem, here's another topic about it
http://forum.xda-developers.com/showthread.php?t=447891&page=2
sooo, yeah. my wife has the t959v. the screen cracked months ago, replaced it with one from ebay, works fine. a few weeks ago, it was involved in an accident and needed yet another screen replacement; ergo, back to ebay i go. installed the new screen yesterday, turn it on, all is well. for a bit.
now, the phone isn't currently, nor has it ever been rooted; pure stock tmo us 2.3.6. during boot, the splash screens and boot animation are gorgeous and perfect in appearance. the recovery menu is exactly as expected. android boots as you'd want it to, and then the display will do one of the following:
-work properly (rare)
-automatically turn off, capacitive buttons still lit, touchscreen unresponsive - turning it "off" darkens the cap buttons, turning it back on flashes the screen on for a half-second, then off, with cap buttons still lit (common)
-graphical corruption ("solarized" colors, completely wrong colors, pixel vomit in essence) (fairly common)
-screen tinting, blue most often, followed by pale yellow, then greenish, then red (almost constant)
-screen inversion - the display will show as rotated 180 degrees; grabbing a framecap in ddms shows it right way up. touches are also inverse; you have to touch where the onscreen element would be if it were displayed properly instead of where the element is; e.g. a button on lower-left will display in the upper right, upsidedown, but the screen registers the button when you touch the lower-left portion of the screen. (quasi common, equally infuriating and hilarious)
none of these problems will show up in a screenshot at all.
i can reliably reproduce any of the above by simply adjusting the screen brightness. this will, quite literally, cycle through every possible defective display mode randomly for a split-second before moving on to a different one as long as you move the brightness slider.
MOST of these issues are transient and are either fixed (temporarily) or replaced with a different listed issue if you lock/unlock the display. it feels like a hardware issue what with the solarizing and color horrors, but is acting like a software issue, considering that recovery and boot are perfect and have never displayed any of these issues. i tried gently flexing and stressing the case in areas that might be a weak connection point, but can't get it to bug out that way.
in no way am i suggesting that i didn't screw something royally in the reconstruction stage, but i tore down and rebuilt that phone 4 times with identical results, so i can guarantee it's not some loose ribbon connector or zif socket.
i beg of you, great minds of xda, what the balls did i muck up this time? any hope for a fix? are there different panels, drivers, something?
thanks in advance
OK, if your screenshots appear normal, then your phone appears to be working correctly!
or at least it thinks it is we can conclude that it isn't the rom, kernel, or anything that you can blame the phone for going screwy.
Try buying another screen??
The ribbon connector might be broken?
yeah, these were what i figured what my options were. it just seems odd that the boot process and recovery menus have error-free displays while only the full android os doesnt. oh well, i'll probably just have to make a stink about it on ebay or something.
thanks for reading
You might try a fresh flash before getting a new screen to see if it is indeed a hardware issue. If you want to try that follow the second link in my signature. You will not need to flash bootloaders since you are currently on KJ6.
lumin30 said:
You might try a fresh flash before getting a new screen to see if it is indeed a hardware issue. If you want to try that follow the second link in my signature. You will not need to flash bootloaders since you are currently on KJ6.
Click to expand...
Click to collapse
hell, warranty's void at this point anyway, right? may as well thanks much!
welp, all went well, screen was perfect through the whole heimdall/recovery process, but the problems still exist in the os c'est la vie. at least my wife's phone is finally rooted, i suppose. thanks anyway!
Have you tried opening it back up and reconnecting?
yup, 4 times, but i guess one more wont hurt
[edit]
it definitely seems to be related (if not related, exacerbated by) changes to screen brightness. turning off autobrightness has helped minimize the issue, but it still presents itself semi-often during screen-off/on events. obviously nothing useful in logcat.
zero01101 said:
it definitely seems to be related (if not related, exacerbated by) changes to screen brightness. turning off autobrightness has helped minimize the issue, but it still presents itself semi-often during screen-off/on events. obviously nothing useful in logcat.
Click to expand...
Click to collapse
That's interesting and could very well be a hardware problem with the screen. You wouldn't see that in recovery as the OS isn't loaded to mess with the brightness in that mode.
Does it do it on-demand if you mess with the brightness slider?
stephen_w said:
Does it do it on-demand if you mess with the brightness slider?
Click to expand...
Click to collapse
you better believe it does. rapid fire cycles through every color until it can't take it anymore and turns off. if i take/refresh a screenshot through ddms and poke blindly at the screen at that point, it'll still take input which is a curious, difficult game to say the least.
zero01101 said:
you better believe it does. rapid fire cycles through every color until it can't take it anymore and turns off. if i take/refresh a screenshot through ddms and poke blindly at the screen at that point, it'll still take input which is a curious, difficult game to say the least.
Click to expand...
Click to collapse
It's that Pink Floyd screen. You're supposed to drop acid & watch the wall when that's going on. LOL j/j
Given that you're on a fresh ROM & the problem persists, I'm leaning toward a hardware issue man. Sorry.
stephen_w said:
It's that Pink Floyd screen. You're supposed to drop acid & watch the wall when that's going on. LOL j/j
Given that you're on a fresh ROM & the problem persists, I'm leaning toward a hardware issue man. Sorry.
Click to expand...
Click to collapse
as fun as that sounds, unfortunately i bet i'll end up just getting my wife a used phone on ebay or somewhere similar and using this one as a development monkey. i was assuming that it wasn't something i could fix but hoping otherwise... yeah, that worked out
I just started having this problem. It wasn't too bad at first, just the color changes, but then it started not showing a screen at all. Changed to three different roms, even back to the stock non-rooted KJ6 and gave up. Keeping it on a steady brightness is the only way to minimize the color changing. I thought your thread had a solution but...
I may try opening it up and fixing the ribbon. But otherwise I'll keep using it as long as I can tolerate it until an S3 or a new Nexus.
kristoper said:
I just started having this problem. It wasn't too bad at first, just the color changes, but then it started not showing a screen at all. Changed to three different roms, even back to the stock non-rooted KJ6 and gave up. Keeping it on a steady brightness is the only way to minimize the color changing. I thought your thread had a solution but...
I may try opening it up and fixing the ribbon. But otherwise I'll keep using it as long as I can tolerate it until an S3 or a new Nexus.
Click to expand...
Click to collapse
nawp, nothing even close to a solution here i did end up buying my wife a whole new replacement phone and turned the broken one into my api10 development device. for what it's worth, yeah, autobrightness off does help a bit for when the phone is actively displaying content, but after you put it to sleep/screen off and try to turn it back on, it's a crapshoot. for a few horrifying hours, the screen was upsidedown even in recovery/boot animation and would NOT flip back to right-side-up until i ran the battery completely flat.
is no fun, 'tis truth. sorry for your troubles.
Ok I've been rooted and modding for almost 2 years now, and this is the first real problem I have had. Just know that ANY suggestions and/or info are appreciated. Ok on with the problem
It looks like the LCD is going out after living with a cracked digitizer for a couple months. first the screen just went grey static and fuzzy. I would put pressure on it, and it would come back and be fine. then it started going completely black, and then i would put pressure on the screen/smack it and it would come back. Now the LCD isn't backlit and is completely nonresponsive.
It seems like it would be a hardware issue, but Im not so sure.. It wasnt doing this at first, but now when I [pull battery and] power on, it gives that short buzz like it does when the splash screen should come up (but doesnt of course), I wait for a minute then it gives that short buzz again, and again like it is in bootloop. The only signs of life are a blinking red LED, vibrating motor, and sometimes if Im lucky the backlight on the 4 keys on the bottom.
I have no access to recovery, bootloader, or splashscreen, and not really sure what to do. Is there a chance that this is a software thing (a kid could wish). If your do believe it is the LCD where is the place to get a cheapest replacement LCD and digitizer? Also could it be a hardware issue to the fatal non-replaceable components?
FYI: rom-eyecandy with bricked kernel not overclocked
So you have damaged hardware? Cracked LCD - I think there is no need to search further for the root cause...
I replaced my digitizer with a white one. Now when I wake my phone, the digitizer takes around 12 seconds before responding. Everything works fine after the initial 12 seconds except for the right side of the screen (front camera onwards) still being unresponsive. On a CM9 rom, I was able to enable 'Show Touches' and noticed that the right side of the screen is filled with 'touches' for the first 12 seconds then disappears.
I have tried flashing different ROMs and kernels with no success. I think this is a faulty digitizer problem.
I moved on to modifying the kernel as a workaround to the problem. Using the stock hidden menu, I determined that the cutoff was at around 415px. I tried changing the 'LGE_TOUCH_RESOLUTION_X' to '415' in '/kernel/arch/arm/mach-tegra/include/nvodm_touch.h' hoping to completely disable that part of the screen. From the dmesg log, it looks like the touchscreen initialization is spending excessive time in the 'tegra_touch_thread' function defined in '/kernel/drivers/input/touchscreen/tegra_odm_touch.c'.
Are there any developers out there that can offer any further insight or suggestions towards this problem? I can deal with the right screen being unresponsive but I would like to fix the initial delay.
Wow crazy. I had that same issue when I first got this phone. The screen would spaz out for a few seconds with many touches so I couldn't unlock it, and the right most edge wouldn't work. Once I replace it I never had the problem since.
Maybe the digitizer was faulty in the first place. That's my guess. Sounds identical to my issue. Can't say if the guy I bought it from dropped it or replaced it with a faulty digitizer.