Related
Wondering if anyone else has had this problem. I've tried a few ROMs - CM11, Carbon, and currently SlimKat and often (every few minutes) the interface sort of pauses. By that i mean touches are not registered. I've turned on display touches in developer options so i can see when the phone is behaving.
Its very strange because Philz Touch Recovery never has any problems but the phone is almost unusable at many points during the day. Often can't even unlock the darn thing.
I don't think its the actual digitizer because during its lucid moments there is no delay, touches are where they should be etc but then it will simply not work. Most often it involves the keyboard (which i'ves switched from the built-in to the Google Keyboard on the play store as a test). I've run some of the display test apps and am able to use every point on the screen...when its behaving.
Any help is appreciated!
On some Motorola Atrix it was problem with cable between motherboard and digitizer with about the same behavior as you described.
Zeljko1234 said:
On some Motorola Atrix it was problem with cable between motherboard and digitizer with about the same behavior as you described.
Click to expand...
Click to collapse
Thanks for the info I'll open it up tonight or tomorrow to take a peek.
Some users managed to find working position of damaged cable. In your case, maybe is just plugged out from connector or contact became dirty.
Be careful and good luck!
Hello XDA,
My Nexus 5 running CM12 5.0.2 nightly will not respond to the touches anymore infact when I press the power button to activate the display it acts as if someone is touching it randomly messing all the apps that are running and opening and closing many other things.
Furthermore it displays weird and burned lines throughout the screen. It was not dropped, no water went inside the device or anything. If it helps I did install the OTA updates that CM gives us.
I have also attached pictures so you may get a better understanding of my problem.
Thanks in advance.
Saad S. said:
Hello XDA,
My Nexus 5 running CM12 5.0.2 nightly will not respond to the touches anymore infact when I press the power button to activate the display it acts as if someone is touching it randomly messing all the apps that are running and opening and closing many other things.
Furthermore it displays weird and burned lines throughout the screen. It was not dropped, no water went inside the device or anything. If it helps I did install the OTA updates that CM gives us.
I have also attached pictures so you may get a better understanding of my problem.
Thanks in advance.
Click to expand...
Click to collapse
Has this happened after you flashed a rom or.. ??
semirr said:
Has this happened after you flashed a rom or.. ??
Click to expand...
Click to collapse
Yes after I flashed the rom but not directly after. But after a good 1 month.
Saad S. said:
Yes after I flashed the rom but not directly after. But after a good 1 month.
Click to expand...
Click to collapse
Hmm I see. Well since a month HAS passed, its definetly not the rom thats causing the problem, i don't know if anything regarding the software could even be causing the problem. Its 100% hardware and by that i mean the screen, you should change it, the touch and also the display are messed up.
semirr said:
Hmm I see. Well since a month HAS passed, its definetly not the rom thats causing the problem, i don't know if anything regarding the software could even be causing the problem. Its 100% hardware and by that i mean the screen, you should change it, the touch and also the display are messed up.
Click to expand...
Click to collapse
Is it possible that a driver update could fix this, if so then how?
Saad S. said:
Is it possible that a driver update could fix this, if so then how?
Click to expand...
Click to collapse
Hmm i dont think that a driver could be the problem. And if it is i dont know how you could fix it Google it
I hate to be the bringer of bad news - but your screen is toast. Fortunately you can replace the touch and display components all at once.
http://www.amazon.com/Skiliwah-Digitizer-Assembly-Google-nexus5/dp/B00HN0U168
Here is what you need to perform the repairs - and here are the procedures for disassembly.
https://www.ifixit.com/Teardown/Disassembling+Nexus+5+Display+Teardown+-+liquid+damage/32410
Trust me, it's not that difficult. Unfortunately, it's a bit pricey ($60 for the screen and digitizer), nevertheless much cheaper than a new device or sending your device in for repairs.
Rma
Problem Solved
The screen isn't toast, neither is the digitizer. I have 2 of these phones. The parts which cause problems like this are the main board and the ribbon with the USB connector on it, which also attaches the screen & digitizer to the main board. One was showing lines exactly like this, & also no touch. I put a replacement main board in. Works great now. The other, wouldn't even turn on. I put the main board from the first phone in the second one, it still wouldn't turn on. I replaced the ribbon cable, it turns on and perfectly replicates the issue from the first phone. So now, I have one fully functioning LG Nexus 5, and another which turns on with the same problem as yours. This is good, I started out with 2 of them that were useless to me. So, it appears that your display and touch issues are caused solely by a bad main board. A replacement main board costs somewhere around $75. After swapping stuff around, I have 2 bad main boards, 1 bad USB ribbon & 1 working phone of 2. Not bad, not bad at all.
So my Nexus 5 (a couple months ago) has started to just randomly go black. I get notifications and stuff, and the backlight but no display. Not sure what to do or what part to replace. Would flashing/rooting help at all?
Appears to be a hardware problem.
Was the phone every dropped or exposed to water/moisture? Possible loose connection inside?
No way to tell for sure if the phone needs a new screen unless you are able to test the motherboard in another N5.
audit13 said:
Appears to be a hardware problem.
Was the phone every dropped or exposed to water/moisture? Possible loose connection inside?
No way to tell for sure if the phone needs a new screen unless you are able to test the motherboard in another N5.
Click to expand...
Click to collapse
It's been dropped a couple times but not like any major drops or anything. Im pretty sure I checked all the connections inside and they were good. Im starting to figure out that the phone has to be off for a little bit then I have to charge it and turn it on and it works again
Sounds like it could be a damaged lcd or lcd connection. If it can work after being charged while powered off, could be battery or USB flex cable issue.
audit13 said:
Sounds like it could be a damaged lcd or lcd connection. If it can work after being charged while powered off, could be battery or USB flex cable issue.
Click to expand...
Click to collapse
OK thanks, ill have to look up some videos on how to check everything
Same problem
cocook2000 said:
So my Nexus 5 (a couple months ago) has started to just randomly go black. I get notifications and stuff, and the backlight but no display. Not sure what to do or what part to replace. Would flashing/rooting help at all?
Click to expand...
Click to collapse
The screen suddenly goes black and after force reboot every thung is fine. When screen was black i tried calling my no it ranged but i cannot answer thr phone.
It had happed around 5-6 times in a about a week with me.
Cant figure problem.
After reboot every thing is fine working normally
[email protected] said:
The screen suddenly goes black and after force reboot every thung is fine. When screen was black i tried calling my no it ranged but i cannot answer thr phone.
It had happed around 5-6 times in a about a week with me.
Cant figure problem.
After reboot every thing is fine working normally
Click to expand...
Click to collapse
Ya I figured out I have to reboot it a bunch of times then it will work
I think it might be the battery because this is my dad's old phone so it's been in use for a solid 3 years.. I wish I knew for sure though
So I have discovered that if my screen is on for a while the task bar at the bottom starts to shift up and down
Have you found out more about this? I think I have the same problem. My phone never turns black while I use it. But when the screen is off/sleeping, it sometimes won't turn on again. So a force reboot fixes it. Sometimes this happens a lot, some times it works fine a whole day.
Sent from my Nexus 5 using Tapatalk
tor0en said:
Have you found out more about this? I think I have the same problem. My phone never turns black while I use it. But when the screen is off/sleeping, it sometimes won't turn on again. So a force reboot fixes it. Sometimes this happens a lot, some times it works fine a whole day.
Click to expand...
Click to collapse
No I decided to send it into LG I'll update this when they tell me what's up with it
cocook2000 said:
No I decided to send it into LG I'll update this when they tell me what's up with it
Click to expand...
Click to collapse
OK!
I could also mention that this happen every time I unlocked the lockscreen on stock ROMs, and custom. But nameless ROM for some reason got it to this point at least. If any one have black screen on unlocking the block screen, try nameless rom...
Sent from my Nexus 5 using Tapatalk
tor0en said:
OK!
I could also mention that this happen every time I unlocked the lockscreen on stock ROMs, and custom. But nameless ROM for some reason got it to this point at least. If any one have black screen on unlocking the block screen, try nameless rom...
Click to expand...
Click to collapse
So what your saying is to try the rom and see if it fixes it? Can I have a link or something, I don't know much about roms
cocook2000 said:
So what your saying is to try the rom and see if it fixes it? Can I have a link or something, I don't know much about roms
Click to expand...
Click to collapse
Maybe, I don't think so. My phone was useless, black screen on every screen unlock. But namelessrom took that away, so that tip about nameless was for those who have the same black screen I had earlier. But now I have the same black screens as you do. Anyway, if you want to try it out, nameless-rom.org
Sent from my Nexus 5 using Tapatalk
Happens with my nexus too. The screen goes blank randomly ..... But i have managed to deal with it.
Its happan to me also, with 4 nexus 5 of my family.
Is a firmware problem?
I'm trying to buy a new flex cable to see if it will help I'll update when I find out
You're replacing the USB charging flex cable? If you are, be careful with cheap third-party replacements as I have read reports of people having issues with charging, signal, or speaker functionality after installing the cable.
tor0en said:
Have you found out more about this? I think I have the same problem. My phone never turns black while I use it. But when the screen is off/sleeping, it sometimes won't turn on again. So a force reboot fixes it. Sometimes this happens a lot, some times it works fine a whole day.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ya so i sent it to LG finally and the diagnostic said that it was a flex cable issue which I was sure that it was anyway but I have a confirmation now
I've had a similar problem when my display suddenly started failing. First, there was colourful bands over the working display, then colourful static only and then black with backlight only. Bought a new phone, left it for a year and today after digging in the phone for a while I found a fix. The connection between the motherboard (the top bit) and the daughter board (the bit below battery with USB and connection to display) was somewhat loose and when pressed on, the display worked beautifully. I stuffed the insides with some tape to maintain pressure on the connection and phone works great.
Might not work for your problem, but it's worth a try if you're out of warranty and have tools to disassemble the phone.
Has an had any issues with screen calibration? Sometimes when I click on the screen it presses to the left of it. When I'm in the recents screen for my apps, it sometimes swipes away instead of selecting it, and I'm unable to consistently unlock the phone while it is charging. (Works like once in every 5 times) however, I'm on sure if that one is related.
Anyone have any ideas?
Which firmware are you on? I remember older firmwares were having a bit of a touch sensitivity isues.
Sammath said:
Which firmware are you on? I remember older firmwares were having a bit of a touch sensitivity isues.
Click to expand...
Click to collapse
I'm on MHA-L29C567B183. US version of the phone. Stock
Did you install a screen protector? Could be the reason for sensitivity issues. If not, I don't know. Maybe a factory reset Will help?
Sammath said:
Did you install a screen protector? Could be the reason for sensitivity issues. If not, I don't know. Maybe a factory reset Will help?
Click to expand...
Click to collapse
I removed the screen protector when I purchased it. I could do a factoru reset and see how it goes. Hopefully it's software related and not hardware related.
I do hope so as well then. I do have to say that the factory installed screen protector doesn't do this screen justice.
Sammath said:
I do hope so as well then. I do have to say that the factory installed screen protector doesn't do this screen justice.
Click to expand...
Click to collapse
I thought it was for protecting it in the box?
Mine had a lot of air bubbles in it so removed it right away.
My charger still has the plastic on it though xD
ante0 said:
I thought it was for protecting it in the box?
Mine had a lot of air bubbles in it so removed it right away.
My charger still has the plastic on it though xD
Click to expand...
Click to collapse
Lol, no, this phone comes with a screen protector pre installed .
The touch sensitity is definitely off a little. I have to swipe the notification bar sometimes twice for it to come down. I also get some missed taps but it's infrequent enough that it isn't a problem for me. I heard they started fixing touch latency and optimization in 5.1. Don't know if we will ever see it.
If you are not using the stock charger weird things can happen.
Alrighty update: Factory settings still yields the same results. It's not frequent enough to make me go crazy, but it's still roughly the same. I guess my real pet peeve is when I need to go to the app manager to return to an open app and it just closes out. I've lost a lot of information that way like recipes when cooking and etc.
What I really don't understand is the fingerprint sensor not working while it's charging. It doesn't matter what charger I use. It just doesn't respond most of the time (Sometimes it unlocks like it's suppose to)
Im using Quick Charger from SS and I have this problem too. It's nice to know this is a common issue, not only me. I dont have any issues with fingerprint when charging, just notice when the battery between 5-60% it's insensitive for me (maybe quick charge is working strongly in this range), "insensitive" here means when you press and hold any things on the screen, it'll "tap" it and open it instead, all pressing or sliding or zooming actions are normal, just dragging has issue. When the battery is 70% and above, it becomes normal and no more insensitive touch. Just that so I think I can bear this thing.
I noticed, that my 1+1 always works ok on stock roms (cm11,cm13 from this forum) and when i set up Android Oreo or Halogen (7.1.2 unoff) or even Flyme 6, my screen don't want to wake up from time to time, buttons vibrate, sound works, all works except screen. Even though, i noticed one way to wake it up, just repeat the touches some times, double tap to panel (i don't see it), and again, to block the screen... it wake up always, or reboot sometimes, but this is not a variant to use at real situations. somtimes headphones help, sometimes usb cable, but no 100% solution.
may be someone know how to solve this problem? i saw a lot of messages here about SOD, and no solution. just something about a modem or flash stock, but this is a software trouble, may be it is firmware.zip or just one .bin file inside (power management). may be this error can be solved?
I really want to go to Oreo and today i tried to do it, but when I suddenly understood that it doesn't work again (after stock) i decided to go back, no way to use it. may be i should take some files from stock?
60puc said:
I noticed, that my 1+1 always works ok on stock roms (cm11,cm13 from this forum) and when i set up Android Oreo or Halogen (7.1.2 unoff) or even Flyme 6, my screen don't want to wake up from time to time, buttons vibrate, sound works, all works except screen. Even though, i noticed one way to wake it up, just repeat the touches some times, double tap to panel (i don't see it), and again, to block the screen... it wake up always, or reboot sometimes, but this is not a variant to use at real situations. somtimes headphones help, sometimes usb cable, but no 100% solution.
may be someone know how to solve this problem? i saw a lot of messages here about SOD, and no solution. just something about a modem or flash stock, but this is a software trouble, may be it is firmware.zip or just one .bin file inside (power management). may be this error can be solved?
I really want to go to Oreo and today i tried to do it, but when I suddenly understood that it doesn't work again (after stock) i decided to go back, no way to use it. may be i should take some files from stock?
Click to expand...
Click to collapse
This has happened to me before.What I simply did was replace the display.
Mr.Ak said:
This has happened to me before.What I simply did was replace the display.
Click to expand...
Click to collapse
that's the way, but not for me. i've just changed my display, i just can check old one, it is not broken, just a dead zone on the touchscreen. but it means that the revision is incorrect, it is something like a driver, i think. i already had the same situation with a old tablet, it didn't wake up anytime after boot, it was discussed at 4pda, so people found, that only one of the 3 revisions works ok at last firmware, i had 2 type of display and could to swith and check it. but it wasn't so good with colors, so i stayed at stock. it seems that situation is the same now.
60puc said:
that's the way, but not for me. i've just changed my display, i just can check old one, it is not broken, just a dead zone on the touchscreen. but it means that the revision is incorrect, it is something like a driver, i think. i already had the same situation with a old tablet, it didn't wake up anytime after boot, it was discussed at 4pda, so people found, that only one of the 3 revisions works ok at last firmware, i had 2 type of display and could to swith and check it. but it wasn't so good with colors, so i stayed at stock. it seems that situation is the same now.
Click to expand...
Click to collapse
Nope,I'm pretty sure it's the display that you changed.Get a refund or replacement.
Mr.Ak said:
Nope,I'm pretty sure it's the display that you changed.Get a refund or replacement.
Click to expand...
Click to collapse
Why do yoy think so? Stock fw can realize all functions for that display, why custom can't do it at the hardware level? no reason to think so.
Just only one idea - is a revision. Now i can try my old display. And if i'd manage to change touchscreen, that can be a solution. But i don't.
60puc said:
Why do yoy think so? Stock fw can realize all functions for that display, why custom can't do it at the hardware level? no reason to think so.
Just only one idea - is a revision. Now i can try my old display. And if i'd manage to change touchscreen, that can be a solution. But i don't.
Click to expand...
Click to collapse
As I already said,the same issue happened to me after I changed my display.I asked for replacement and replaced that damaged display,boom! I don't know what's so hard in it for you to understand.
Thank you for advice. I've just opened a dispute. Today it didn't woke up at stock firmware.
60puc said:
Thank you for advice. I've just opened a dispute. Today it didn't woke up at stock firmware.
Click to expand...
Click to collapse
Aliexpress?
Yes. But at first everything was ok. And when i installed oreo it stops some times and Sod started. I tried to use 7.1.2, it SOD's anyway. Then the stock was the solution. I'm already relaxed, and decided that it is software error, but after a few days it started again.
I've accepted this display, but with your help it's not so late to open a dispute. I think it will be ok.
60puc said:
Yes. But at first everything was ok. And when i installed oreo it stops some times and Sod started. I tried to use 7.1.2, it SOD's anyway. Then the stock was the solution. I'm already relaxed, and decided that it is software error, but after a few days it started again.
I've accepted this display, but with your help it's not so late to open a dispute. I think it will be ok.
Click to expand...
Click to collapse
Get ready with a lot of proofs tho'!
to me it happens, I do not know if it is the same as described, but unlocking the screen works everything but not touch, lock, unlock, and it works, what is it due?
Gab_echelon said:
to me it happens, I do not know if it is the same as described, but unlocking the screen works everything but not touch, lock, unlock, and it works, what is it due?
Click to expand...
Click to collapse
See previous page,I've already explained what is the cause of the issue.
I just finished replacing my screen, been waiting for my broken antenna cable and volume button flex to arrive. Everything works except the damn SOD i never had with my old screen. Tried turning off the proximity sensor check and still a no go. The screen turns on fine initially and trying to wake it instantly works all the time, but if I leave it off for any longer than 5 sec probably it won't respond to anything - power button, volume button, double tap and plugging in the usb cable connected to a power source.
Does this sound more like a governor issue? The rom installed is lineageOS (just updated to 10-30 release). Looking up my purchase log to open a dispute...
tested it again, repeated lock/unlocks puts it into the SOD state, doesn't even take 2 sec to do it...
oh wow, it does this even in the twrp recovery. I have wiped cache and dalvik cache just for the hell of it but doubt that was the real cause...
Gab_echelon said:
works everything but not touch
Click to expand...
Click to collapse
we've got a reverse situation. touch, buttons, sounds, modem works, but not screen (if you lock/unlock it 10-20 times it can raise again without reboot.
Buratei said:
it does this even in the twrp recovery.
Click to expand...
Click to collapse
i've got the first SOD in twrp mode. it doesn't matter, but at first - no troubles were with that. and now it works so so at home. and if i use it outdoor it becomes very often, but at home it seems that it works ok, just only seems, because if i want - i can do some manipulations (use camera, lock/unlock it etc) and the SOD appears again. but custom os executes SOD more frequently. i think it can be real overvoltage, like people says.
there are many posts here and everyone advices not effective solutions (flash stock, modem, fw ...) at first it helped me, but now i know there is no way, i can just try but ...
long time ago i owned an old tablet iconbit matrix - it has just the similar issue. it boots, but if you go to a sleep mode - it didn't wake up every time. it lights works ok inside, but no image. i had two displays and if i used one in a custom rom it worked ok, but not another one. stock rom works ok with every display. the solution was a display driver, like at windows OS.
cause of developers bugs, it was a little different (not stock-based) and some revisions of display works ok, others aren't.
so, i think it can be fixed, but the solution for me - change a display like the first reply says. Ali seller read this topic and posted me this in a few days after i started this topic:
Your dispute has been processed and the money will back to you in 7~10 working days.
so could you give us a positive feedback, please?
Best regards.
so, i'll order another one, no trouble, i hope this will help me to enjoy my oneplus.
60puc said:
so could you give us a positive feedback, please?
Best regards.
Click to expand...
Click to collapse
They always ask for positive feedback in exchange for refund/replacement.Bastards,aren't they? @evronetwork
For the sake of other people that'll read your feedback and make their decisions upon it,don't do it! Just complain this bribery to aliexpress staff ffs!
well I wish I bought from aliepxress... I bought mine from ebay to pinch some pennies, and because I was waiting on other replacement parts (which were only needed due to damage occurred during a screen replacement op) to ge here I am way over the protection period. aw shiiiiit, I guess you live and learn
gotta tell you though, the screen is a bit wacky in other ways too. the capacitive buttons do light up but not completely (kinda dark in the corners) and the colors look a bit off. hopefully the seller would honor the refund/return request...
EDIT: whoa... kinda hard to believe, but I messed around with battery profile just for the hell of it and by some pure luck discovered that the "performance" profile (second one from the far right) works just fine and wakes the screen every time. The "balanced" profile and everything below that gives me an insta-death. go figure!
EDIT2: guess I spoke too soon. it sure as hell looked like fixed, but it came back after a while. maybe it is just more sporadic than I thought...
No solution yet? I think, that it can be some trouble with lights (this wire with 3 contacts), because touch starts, but no image. may be the signal comes to the matrix, but it is not enough energy to enable this diods. what can we do? im going to change the back side of the screen.
ow, no way, don't even try, it has combined technology. i disasabled the whole wire, no chance there...
http://i102.fastpic.ru/big/2017/1215/50/bd4e28b5b320ad2b4de26baf9d809350.jpg
http://i103.fastpic.ru/big/2017/1215/28/9803686e8a12d29baa902c3a2577de28.jpg
60puc said:
No solution yet? I think, that it can be some trouble with lights (this wire with 3 contacts), because touch starts, but no image. may be the signal comes to the matrix, but it is not enough energy to enable this diods. what can we do? im going to change the back side of the screen.
ow, no way, don't even try, it has combined technology. i disasabled the whole wire, no chance there...
http://i102.fastpic.ru/big/2017/1215/50/bd4e28b5b320ad2b4de26baf9d809350.jpg
http://i103.fastpic.ru/big/2017/1215/28/9803686e8a12d29baa902c3a2577de28.jpg
Click to expand...
Click to collapse
What happened to getting a new display?
I use this one, because it works ok, but only at home. As a home tablet. At the street it fails every time.
I can reboot it if it doesn't wake up. But it wakes up often, so i don't want to order new one now. I want to check my mainboard to be sure, that it is dispaly problem
a bit late, but thought I should update on the situation... all working fine after a (yet another) LCD replacement. Much better color balance to boot, points to QC problems at the supplier's end. If I ever have to do this again, I am definitely going to inspect the new LCD as soon as I receive I receive it.