Database Info

Sensation screen unresponsive for short time after turning on

I have just replaced my digitizer (was dust under the screen and also a scratch on the digitizer itself, along with the fact I damaged it removing the sticky tape) and the whole screen is almost completely unresponsive. Brand new, but wont work fully until I touch the screen for a bit or give it time to sit after activating the lockscreen.
Once it is through it's "warmup" the screen works flawlessly. It just acts like a slug before that... Also rendering the quick launch lock screen completely worthless. Anyone have any ideas what could be the culprit?
Sent from my HTC Sensation 4G using XDA Premium App

I too replaced a broken screen on my sensation, and i am experiencing the exact same problem as you. Only for me it's only the lower left part of the screen that 'takes time to warm up'.
Did you find any solution?

Not yet. I have another digitizer on order, and fingers are crossed. If not, ill be biting the bullet and waiting for the nexus prime. I have this feeling that it is something other than the digitizer which is extremely sensitive. If people are claiming responsiveness issues after a week or two of use, and while on their sixth or seventh sensation... It sounds like something is slowly deteriorating or building up.
Sent from my HTC Sensation 4G using xda premium

I don't think it's the digitizer either, probably something else ont he phone. However i don't think it is the same problem as everybody else is having, since they experience their screen being unresponsive in general rather than just after turning on.
I am though going to try some of the fixes suggested, i.e. improve the grounding by placing some aluminum foil under the cover and see if it helps.

What does "turning on" mean? Cold boot up? If so, then the CPU on the phone will be busy doing stuff. If you mean waking up from sleep, then that's another problem.

for me it's both cases, both when booting the phone and just when turning the screen back on. What's strange is that it is only the lower part of the screen that's frozen :-S after 10-20 seconds it suddenly springs back to life just as nothing had happened and works flawlessly until i turn the screen of. Then i see the exact same problem again.
I also noticed now that the screen also freezes after calling somebody and when you hang up :-0 I really don't know what is wrong with the phone!

If the phone is unsecured (never sleeps) it will work flawlessly. As soon as I click the top button to secure the screen, or take a phone call, once I try to unlock/ use the screen again... The problem comes back. The left side of the screen is the most responsive, usually moving my finger around for about five or ten seconds will restore full sensitvity. I received a new digitizer in the mail, just waiting on tape. Interesting note; they are different digitizers. The original was HTC/ tmobile brand while the replacement is simply HTC. The ribbon cable also reads different. My original: pyd v1.0, sw-10 94v-0, e3082521117. The new one reads: pyd v1.0, e21954-1, ruICACichia, 94v-0 1112. The current digitizer replacement is also a standard HTC label... I wonder if it is because it isn't a specific model replacement.
Sent from my HTC Sensation 4G using xda premium

Alright so i tried doing all the fixes related to the grounding issue, and i didn't affect anything at all.
I'm going back to the repair shop today (have a three months warranty) to tell them to have a look at it again and see if they can fix the issue. Maybe they have a spare digitizer they could try instead of my current one. I will let you know if anything helps!

Sounds good. I am betting its either an incorrect digitizer for the model of phone (us/eu/whatever) improper mounting or damage, or just planetary alignment or something equally stupid. I'm really hoping someone figures out this problem... It is frustrating to spend more time figuring out how to fix a phone than you actually do using it.
Sent from my HTC Sensation 4G using xda premium

what9000 said:
Sounds good. I am betting its either an incorrect digitizer for the model of phone (us/eu/whatever) improper mounting or damage, or just planetary alignment or something equally stupid. I'm really hoping someone figures out this problem... It is frustrating to spend more time figuring out how to fix a phone than you actually do using it.
Click to expand...
Click to collapse
True, had i known from the start i would probably just have bought a new phone, rather than spend on the money on getting the screen replaced :-S

Well, I replaced the digitizer for a second time. Seems to be the same thing so far. Different initial responsiveness spot (looks like the right side might be more sensitive now) but I didn't have high hopes. I wonder what it could be...
Sent from my HTC Sensation 4G using xda premium

So i went back to the repair shop and got it fixed. I guess they weren't in the mood for scientific inquiry, because they simply disassembled the phone and installed a new digitizer. After that everything is working fine, altough i will never know if it was the digitizer itself or some faulty wiring somewhere :-S

Worked for me
I have had exactly the same problem you all have experienced. The first digitizer I ordered from a company on e-bay gave me huge problems at the unlock screen. Bought a new one from skalshop and it works perfectly. I even tried it without tape to make sure it worked before I glued the thing together and it worked perfect.

[Q] screen disaster - random tinting, solarization, turns upside down

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.

[Q] New LCD and Digitizer DOA?? Help please!

So I ordered a new LCD and digitizer from new harbor via amazon.
I took the phone apart, installed the new array, and powered it on, and the screen is great (maybe even brighter than the last one) but it just has zero touch input.
The last screen worked fine, but the LCD was broken. I could have it acknowledge touches so I dont think that the motherboard or anything else is broken, so I wonder what may have went wrong.
Should I take this mofo apart again and see if I have a loose connection? Maybe the ribbon cable is not connected right?
Probably the past is DOA?
Help please! thanks.

stevenjcampbell said:
So I ordered a new LCD and digitizer from new harbor via amazon.
I took the phone apart, installed the new array, and powered it on, and the screen is great (maybe even brighter than the last one) but it just has zero touch input.
The last screen worked fine, but the LCD was broken. I could have it acknowledge touches so I dont think that the motherboard or anything else is broken, so I wonder what may have went wrong.
Should I take this mofo apart again and see if I have a loose connection? Maybe the ribbon cable is not connected right?
Probably the past is DOA?
Help please! thanks.
Click to expand...
Click to collapse
Try the screen calibration.
Sent from a dream.

Teichopsia said:
Try the screen calibration.
Sent from a dream.
Click to expand...
Click to collapse
Is this somewhere in the service menu? I can boot into its custom menu by holding down volume and power... Not sure if there's more to it.
It's rooted s-off so I get menus to get into recovery or fast boot etc
Sent from my SCH-I535 using xda app-developers app

Scratch that. Just re read your post. "Zero touch input". It's an option in the rom.
There are a few threads/posts where people have replaced the screen, either here or the dhd forum. Check what they had to say. I have absolutely no experience in that. Perhaps it's a cable as you said, but before doing that, I would research on it first. You may end up like me with 9 screws left over after taking apart my ps3 three times (screwing it up even more).
Sent from a dream.

Teichopsia said:
Scratch that. Just re read your post. "Zero touch input". It's an option in the rom.
There are a few threads/posts where people have replaced the screen, either here or the dhd forum. Check what they had to say. I have absolutely no experience in that. Perhaps it's a cable as you said, but before doing that, I would research on it first. You may end up like me with 9 screws left over after taking apart my ps3 three times (screwing it up even more).
Sent from a dream.
Click to expand...
Click to collapse
Removing and taking it apart isn't a problem. There are only eight screws.
This isn't fun... To be certain.
Sent from my SCH-I535 using xda app-developers app

stevenjcampbell said:
Removing and taking it apart isn't a problem. There are only eight screws.
This isn't fun... To be certain.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Did you ever get this taken care of?

Just replaced mine. LCD intact. Touch no longer working. They aren't kidding: this phone isn't fun to work on. It's a *****. I've repaired a half dozen iPhones. This makes that stuff seem rudimentary.
Sent from my Desire HD using xda app-developers app

I've had my inspire apart several times. Other than removing the Flash/GPS, and separating the LCD from the frame its quite simple. If you want a pain try a slide phone.

stevenjcampbell said:
So I ordered a new LCD and digitizer from new harbor via amazon.
I took the phone apart, installed the new array, and powered it on, and the screen is great (maybe even brighter than the last one) but it just has zero touch input.
The last screen worked fine, but the LCD was broken. I could have it acknowledge touches so I dont think that the motherboard or anything else is broken, so I wonder what may have went wrong.
Should I take this mofo apart again and see if I have a loose connection? Maybe the ribbon cable is not connected right?
Probably the past is DOA?
Help please! thanks.
Click to expand...
Click to collapse
Understand your pain because just recently I had to change my entire screen for my Inspire 4G. I assume that you did everything correctly but here is the video that helped me on youtube:
HTC INSPIRE Screen Repair and LCD / DIGI REPLACEMENT from phonedoctors
If you did everything correctly it could just mean that you prob got a faulty part

[Q] Screen staying black when turning on

Recently my phone screen started to stay black when i go to turn it on, but the phone itself is awake. I can feel the vibration response from using the phone, the screen itself just stays black.
I've tried rebooting the phone, clean flashing a different rom, flashing it back to stock via Odin, and I've read through all other threads about this topic. Nothing fixes it. Does anyone have any ideas as to how to fix the phone?
Thanks!

XInSaNeFartX said:
Recently my phone screen started to stay black when i go to turn it on, but the phone itself is awake. I can feel the vibration response from using the phone, the screen itself just stays black.
I've tried rebooting the phone, clean flashing a different rom, flashing it back to stock via Odin, and I've read through all other threads about this topic. Nothing fixes it. Does anyone have any ideas as to how to fix the phone?
Thanks!
Click to expand...
Click to collapse
My guess is the connection between the screen and the main board has become disconnected. However this is only a guess based upon what happened to one of my phones which I then fixed by opening up and checking this connection. Depending upon the device this can be anywhere from easy to virtually impossible to do. Luckily I haven't had to open up my GS3 (yet).

muiriddin said:
My guess is the connection between the screen and the main board has become disconnected. However this is only a guess based upon what happened to one of my phones which I then fixed by opening up and checking this connection. Depending upon the device this can be anywhere from easy to virtually impossible to do. Luckily I haven't had to open up my GS3 (yet).
Click to expand...
Click to collapse
I actually just started to take mine apart to check for any noticeable issues like that

XInSaNeFartX said:
I actually just started to take mine apart to check for any noticeable issues like that
Click to expand...
Click to collapse
You shouldn't have any problems taking it apart and putting it back together. I did have a little bit of a issue trying to put the antenna wire back on but I think I ended up using a ball point pen to reattach it.

ThePagel said:
You shouldn't have any problems taking it apart and putting it back together. I did have a little bit of a issue trying to put the antenna wire back on but I think I ended up using a ball point pen to reattach it.
Click to expand...
Click to collapse
I had it all taken apart except for the screen, which coincidentally is the part i need to take off. I'm just slightly hesitant about it since it's easy to break...

XInSaNeFartX said:
I had it all taken apart except for the screen, which coincidentally is the part i need to take off. I'm just slightly hesitant about it since it's easy to break...
Click to expand...
Click to collapse
Have you used ifixit as a reference to aid you? They have teardowns of nearly every entertainment electronic device that has relevance. Here's the international S3 teardown.
I want to make this clear, I have never taken apart my phone to the extent of getting beneath the display or anything that in depth. So I can not troubleshoot with you should you have questions.

SlimSnoopOS said:
Have you used ifixit as a reference to aid you? They have teardowns of nearly every entertainment electronic device that has relevance. Here's the international S3 teardown.
I want to make this clear, I have never taken apart my phone to the extent of getting beneath the display or anything that in depth. So I can not troubleshoot with you should you have questions.
Click to expand...
Click to collapse
yeah i used it as a reference after taking apart, but I'm still unsure about taking the screen off. Seems easy to break. I may see if i can sell the phone before doing that

XInSaNeFartX said:
yeah i used it as a reference after taking apart, but I'm still unsure about taking the screen off. Seems easy to break. I may see if i can sell the phone before doing that
Click to expand...
Click to collapse
Yeah that could be a bad idea because you need special adhesive to put it back on. I don't even wat to think about cleaning the old adhesive off if you can reuse the old screen.

[Q] I Screwed Something Up

A friend of mine had a Galaxy S3 Amber with a broken (and blank) screen and wanted her data from it's internal memory that is locked and not in debugged mode. I did a lot of research and found the best, most efficient way was to do a motherboard swap with another gs3. I had a Galaxy S3 Blue. I watched a couple of videos and it seemed rather easy. I gathered the proper tools and was EXTREMELY careful not to break or rip anything (and to my knowledge i did not). When i put her motherboard from the amber one into the blue one and the screen would not come on. My first thoughts were it must be her motherboard that went bad. Well when i went to put my blue gs3 back together (again being very careful this entire time) I'm now having the same issue as she was. Black screen, no back light. The bottom lights DO come on and i feel it vibrate when i get a message. There was also no power on chime...
I know its hard to tell with out looking but any ideas on what could be wrong or what i might have screwed up? i checked all the connections and everything looks perfect. Nothing is bent or connected wrong and I didn't force or break anything.
update: so i found that the touch part of it still works fine. i can hear the ripple unlock as well as all the other sounds and such when i touch around and i can here it opening apps. the only issue lies in the screen itself being blank with no back light what so ever,

First of all remove the battery and attempt to power on, then leave without battery for 1 min, I know this sounds silly but it worked on an old iPhone 3G so anythings worth a shot.
If that doesn't work go back into the S3 and make sure all the data clips are firmly in place and locked down but not twisted in anyway. Also make sure their is no moisture or dust on the ribbons. You may not realise it but even the smallest imperfection with this can cause massive issues down the line.
If all else fails her phone may have broke your screen, I don't know how but it is a possibility
Hope I could help and good luck

TechMinerUK said:
First of all remove the battery and attempt to power on, then leave without battery for 1 min, I know this sounds silly but it worked on an old iPhone 3G so anythings worth a shot.
If that doesn't work go back into the S3 and make sure all the data clips are firmly in place and locked down but not twisted in anyway. Also make sure their is no moisture or dust on the ribbons. You may not realise it but even the smallest imperfection with this can cause massive issues down the line.
If all else fails her phone may have broke your screen, I don't know how but it is a possibility
Hope I could help and good luck
Click to expand...
Click to collapse
so i took it apart again today to double check and clean everything and under inspection i noticed a teeny tiny slit on the edge of the lower, bigger ribbon. i know the smallest bit could be horrid. Any fix and would that cause just the screen to not show? i don't know if that is the led connection but i think it may be.

amshook said:
so i took it apart again today to double check and clean everything and under inspection i noticed a teeny tiny slit on the edge of the lower, bigger ribbon. i know the smallest bit could be horrid. Any fix and would that cause just the screen to not show? i don't know if that is the led connection but i think it may be.
Click to expand...
Click to collapse
If theirs a slit I'm affraid that could be it for the screen, like I said even the smallest imperfection can cause massive issues. The slit is probably in the one of the data sections of the ribbon cable which is why data for the screen isn't being carried.
For the fix I don't think their is one unless you can fit a new ribbon on to yout S3's screen
Sorry about the screen

So I took it all apart again. Cleaned ever little thing I could and now it works again. ?

amshook said:
So I took it all apart again. Cleaned ever little thing I could and now it works again. ?
Click to expand...
Click to collapse
Excellent, must have just had some dust or gunk on the cable
Glad you got it working again:victory:

TechMinerUK said:
Excellent, must have just had some dust or gunk on the cable
Glad you got it working again:victory:
Click to expand...
Click to collapse
As am I. Thanks alot for helping. I appreciate it. id buy you a beer if I could lol.

amshook said:
As am I. Thanks alot for helping. I appreciate it. id buy you a beer if I could lol.
Click to expand...
Click to collapse
No problem, thats what XDA is here for:laugh: