Oneplus one screen touching itself. - ONE Q&A, Help & Troubleshooting

I have had my oneplus one for about a month now. And for the first time I dropped it. About 2 feet. And my friend kicked it about a foot to prevent it from hitting the tile and It landed on flat carpet. The phone has a small dent on the lower left corner and screen has 2 small scratches that I only can see in sunlight. So I've been using my phone and every once and awhile it will go insane and the touchscreen will move on its own and press things. I hope this isn't an issue cause of dropping it.. I have a warranty but have alot on this opo already. Is there a possibility it's software?

TeChNoC4AzY said:
I have had my oneplus one for about a month now. And for the first time I dropped it. About 2 feet. And my friend kicked it about a foot to prevent it from hitting the tile and It landed on flat carpet. The phone has a small dent on the lower left corner and screen has 2 small scratches that I only can see in sunlight. So I've been using my phone and every once and awhile it will go insane and the touchscreen will move on its own and press things. I hope this isn't an issue cause of dropping it.. I have a warranty but have alot on this opo already. Is there a possibility it's software?
Click to expand...
Click to collapse
The Touchscreen failure you have sounds a lot like the problem I had from time to time with mine (without dropping).
There are also other bugs with the screen:
- unresponsive screen (-> reboot fixes temporarily)
- weird behavior like you descrive (ghost touches)
- fast typing not getting recognised
These problems will be fixed with the next 2 OTAs (both in august).
Wait if the fixes do work for you. If not it has definatly something to do with the accident.

keileruno said:
The Touchscreen failure you have sounds a lot like the problem I had from time to time with mine (without dropping).
There are also other bugs with the screen:
- unresponsive screen (-> reboot fixes temporarily)
- weird behavior like you descrive (ghost touches)
- fast typing not getting recognised
These problems will be fixed with the next 2 OTAs (both in august).
Wait if the fixes do work for you. If not it has definatly something to do with the accident.
Click to expand...
Click to collapse
OTA Announced today. Change log has a fix for turning on in pocket, but not for the unresponsive screen.

Actually I have had similar behavior and I'm using slimkat 7 now. This morning I couldn't enter even pin code as my phone didn't allow some presses. Numbers 1,2,4&5 weren't registered at all. Same time I couldn't use pull-down menu as it bounced back up after 1cm pull. Also when trying use power menu all options were unable to register. I force shut down phone twice and still same thing. Then I just wiped whole screen with moist cloth. And problem solved.
So there was something invisible holding my screen like finger or something.
I have had similar incident couple times earlier. When writing or so on....
Sent from my Oneplus One via Tapatalk

keileruno said:
The Touchscreen failure you have sounds a lot like the problem I had from time to time with mine (without dropping).
There are also other bugs with the screen:
- unresponsive screen (-> reboot fixes temporarily)
- weird behavior like you descrive (ghost touches)
- fast typing not getting recognised
These problems will be fixed with the next 2 OTAs (both in august).
Wait if the fixes do work for you. If not it has definatly something to do with the accident.
Click to expand...
Click to collapse
How much longer do you think it will be before the new Ota releases.

TeChNoC4AzY said:
How much longer do you think it will be before the new Ota releases.
Click to expand...
Click to collapse
search the forum the ota is out if you know how to use adb sideload

The ghost touches lasted for 30 seconds today.. Anyone else having this to?

Yes it's annoying the crap out of me, seem to have the least amount of issue running slimkat with sensei kernel. Every other kernel seems to either leave the screen completely unresponsive a min after boot, or touch becoming increasingly less as time/process load increases. Really hope this issue is fixed soon.

Chris.fowler said:
Yes it's annoying the crap out of me, seem to have the least amount of issue running slimkat with sensei kernel. Every other kernel seems to either leave the screen completely unresponsive a min after boot, or touch becoming increasingly less as time/process load increases. Really hope this issue is fixed soon.
Click to expand...
Click to collapse
Best thing is to go back to the XNPH22R Kernel. For me it fixed the frozen screen completly.
http://forum.xda-developers.com/showthread.php?t=2780725
It won't work with 30O though. 25R is working with 22R Kernel.
All other kernels are not working very smooth for my device. The OTA fixing this issue is anounced for August. No releasedate has been set though.

Is that kernel compatible with an aosp ROM lime slim or am I going to have to put a cm ROM bck on the phone

Chris.fowler said:
Is that kernel compatible with an aosp ROM lime slim or am I going to have to put a cm ROM bck on the phone
Click to expand...
Click to collapse
CM 11S kernels are only for CM 11S. 22R is a CM 11S kernel.

My phone has been alright today. Except for afew freezes. But I Wana Stay with cyanogenmod 11s. I think it will be updated soon. I really can't wait for Android L. Will android L be with cyanogenmod as well?

Great now the middle of my screen us touch dead........ Ughh

Well now all seems fine.. But earlier screen in center was dead and phone was non stop Ghost touching... Even after restarts. Sigh. This update needs to release already....

Hello

playya said:
search the forum the ota is out if you know how to use adb sideload
Click to expand...
Click to collapse
It won't update itself?

It's a known issue.. Vote it on Jira!https://jira.cyanogenmod.org/browse/BACON-145

I'm about to throw my phone, this is VERY irritating.........

It keeps Ghost touching non stop. I should of never got one.

TeChNoC4AzY said:
It keeps Ghost touching non stop. I should of never got one.
Click to expand...
Click to collapse
Install the 22R OTA and Kernel.... then you can easily wait for the fix...

Related

Is there a ghost in my phone?[CASE SOLVED]

OK now I know there isn't a Ghost in my phone but at times my phone behaves like its possessed. The problem is with the touch screen. At times my phones starts to do stuff on its own. Like open random apps, bring down the notification bar and then brings it back up. Once it even opened my whatsapp and then opened the keyboard and typed a message and sent it to an contact. And during this time it doesn't really respond to my touches. But it happens very rarely like ones in two days and that too for a min or two. Been happening for a two weeks now. I have the latest CM 7 Nightly installed. So what do u reckon is happening? Is it a software bug or an Hardware bug? And how do I fix it?
..
Sent from my sending thing.
I had the same problem. LG Service Center said, that they need to change the touchscreen. Try to flash another ROM, if you get the same problem, then unroot and flash stock firmware and go to LG Service Center or change the screen yourself
But I hope it's your ROM, good luck!
on my sgs i have this weird ghost while charging.. are you running ics?
sweettaniyaa said:
OK now I know there isn't a Ghost in my phone but at times my phone behaves like its possessed. The problem is with the touch screen. At times my phones starts to do stuff on its own. Like open random apps, bring down the notification bar and then brings it back up. Once it even opened my whatsapp and then opened the keyboard and typed a message and sent it to an contact. And during this time it doesn't really respond to my touches. But it happens very rarely like ones in two days and that too for a min or two. Been happening for a two weeks now. I have the latest CM 7 Nightly installed. So what do u reckon is happening? Is it a software bug or an Hardware bug? And how do I fix it?
Click to expand...
Click to collapse
this one was the best query I have ever read tania hope u are not watching fear files these days
sweettaniyaa said:
OK now I know there isn't a Ghost in my phone but at times my phone behaves like its possessed. The problem is with the touch screen. At times my phones starts to do stuff on its own. Like open random apps, bring down the notification bar and then brings it back up. Once it even opened my whatsapp and then opened the keyboard and typed a message and sent it to an contact. And during this time it doesn't really respond to my touches. But it happens very rarely like ones in two days and that too for a min or two. Been happening for a two weeks now. I have the latest CM 7 Nightly installed. So what do u reckon is happening? Is it a software bug or an Hardware bug? And how do I fix it?
Click to expand...
Click to collapse
It is surely a hardware problem i had the same problem. My screen had got damaged as it wud get wet regularly. I changed the touch screen and it is now as good as new
Running Ginger Snap v1.3 Best gaming rom ever
A developer told me that sometimes on some devices, it happens while charging, becaude of charger errors..
sweettaniyaa said:
OK now I know there isn't a Ghost in my phone but at times my phone behaves like its possessed. The problem is with the touch screen. At times my phones starts to do stuff on its own. Like open random apps, bring down the notification bar and then brings it back up. Once it even opened my whatsapp and then opened the keyboard and typed a message and sent it to an contact. And during this time it doesn't really respond to my touches. But it happens very rarely like ones in two days and that too for a min or two. Been happening for a two weeks now. I have the latest CM 7 Nightly installed. So what do u reckon is happening? Is it a software bug or an Hardware bug? And how do I fix it?
Click to expand...
Click to collapse
Change your kernel, these may be kernel panicks.
Sent from my LG-P500 using xda app-developers app
myawan said:
Change your kernel, these may be kernel panicks.
Click to expand...
Click to collapse
This could be a reason cause it all began when I flashed DJNoXD's Kernel 2.5.2. But then I re flashed the latest CM 7 nightly over it and it continued to show the symptom's. Also I did not over clock, never did.
Today when it showed the same possessed behavior, I pressed the power button and it at once came back to my control. So I guess its a temporary solution to it.
dafabsl said:
A developer told me that sometimes on some devices, it happens while charging, becaude of charger errors..
Click to expand...
Click to collapse
It never happened during charging.
Found the Culprit
It was being caused by a pair of external speakers, which has it own power source, which I connected to the phone. I am guessing the speaker was sending some kind of charge to the phone. When I connected the speaker, the touchscreen completely stopped working. and even after I disconnected the speaker the touchscreen would continue to behave the way I described in my first post. Probably stored that charge somewhere. Bottom line, now that I have stopped connecting the speakers its stopped that behavior. There case solved. Feel like Scooby Doo. There was no Ghost after all.
Lolzz..

Different touchscreen bug

Hi,
My OPO is having some strange behaviors when it comes to the touchscreen. Not only I'm having the ghost touches (still no fix out, right?), but I'm also having a strange bug that makes the center portion of the screen unusable all the freaking time.
I made a video (sorry for the bad quality, the glitch about 25 seconds in and the general noobness ) showing the bug in action (sometimes it happens on the lock screen, which is infuriating cause I have to way of unlocking and have to wait until good guy OPO gets his **** together).
Anyway, is there anyone with a similar problem? any fix on the mind of an illuminated soul? or to the warranty (or lack of it) with it?
Thanks.
mromariz said:
Hi,
My OPO is having some strange behaviors when it comes to the touchscreen. Not only I'm having the ghost touches (still no fix out, right?), but I'm also having a strange bug that makes the center portion of the screen unusable all the freaking time.
I made a video (sorry for the bad quality, the glitch about 25 seconds in and the general noobness ) showing the bug in action (sometimes it happens on the lock screen, which is infuriating cause I have to way of unlocking and have to wait until good guy OPO gets his **** together).
Anyway, is there anyone with a similar problem? any fix on the mind of an illuminated soul? or to the warranty (or lack of it) with it?
Thanks.
Click to expand...
Click to collapse
i am with the same problem..the scrren freezes randomly for a few minutes and then working fine..i don't understand how is possibile..every boot from two days
iker_92 said:
i am with the same problem..the scrren freezes randomly for a few minutes and then working fine..i don't understand how is possibile..every boot from two days
Click to expand...
Click to collapse
I just want to understand if there's or will be any software fix for this problem, or if I just have to give up and start thinking about warranty.(happened again has I write this message ).
i hope is software related..i wait the next ota with hope for the fix..otherwise i will send it in assistance..
iker_92 said:
i hope is software related..i wait the next ota with hope for the fix..otherwise i will send it in assistance..
Click to expand...
Click to collapse
I have it too...When i wake up my phone sometimes i have to wait a few sec before the screen becomes responsive...It must be something related to touchscreen software or drivers, theyre really bugged as now.
Yea I also have it, I had it yesterday when i had to call cardstop when my wallet was stolen and my screen wasn't working.
Powered off for 5 min then only the bottom of the screen was was working.
hey guys Abhisek Devkota of CM says that is a firmware related issue caused by partnbers that gave drivers to cm..they now are working hard for it and in this month should be two updates..the firts with the workaround on the ota in the next days and the second with kernel patch
iker_92 said:
hey guys Abhisek Devkota of CM says that is a firmware related issue caused by partnbers that gave drivers to cm..they now are working hard for it and in this month should be two updates..the firts with the workaround on the ota in the next days and the second with kernel patch
Click to expand...
Click to collapse
I hope so, its happening almost every time I unlock/try to unlock the phone now. its really annoying, specially during calls, yesterday I called a friend and he didn't pick up so the call went to the voicemail, since I didn't want to leave any message I tried to end the call, but because of this bug I had to put the phone to sleep and wake it up to end the call making me pay for a dam voicemail.
Any news on a fix for this ?
I am having this issue as well but it just started today and I have had the phone for about 3 weeks. After a few minutes of use my touch screen except for the navigation buttons and the status bar become unresponsive and I have to power cycle my device to get the screen working again.
It happened to me today as well. I sure it will be fixed but still glad I have my Nexus 5 till then.
I have found a temporary fix (at least for me). After trying out many different kernels I ended up with the XNPH22R Kernel (http://forum.xda-developers.com/showthread.php?t=2780725). After a reboot the screen frooze but then recoverey without reboot. Now I had no freeze for around 30 hours without reboot. Still running the XNPH25R CM11s Rom.
Phone is rooted and unlocked.
There are also speculations that the freezes could be temperature related or at least partially.
keileruno said:
I have found a temporary fix (at least for me). After trying out many different kernels I ended up with the XNPH22R Kernel (http://forum.xda-developers.com/showthread.php?t=2780725). After a reboot the screen frooze but then recoverey without reboot. Now I had no freeze for around 30 hours without reboot. Still running the XNPH25R CM11s Rom.
Phone is rooted and unlocked.
There are also speculations that the freezes could be temperature related or at least partially.
Click to expand...
Click to collapse
Yeh I also get that feeling (about the temperature) . I'm gonna try that kernel once I get home thanks.
http://forum.xda-developers.com/one...-30o-ota-slowly-rolling-t2844689/post54755925
It's a known issue.. Vote it on jira! https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/BACON-145

[Q] Touchscreen Issues

I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance
ttxcsabby said:
I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance
Click to expand...
Click to collapse
I've never experienced any issues like this. Contact Nvidia Customer care.
This screen is very responsive!! Make sure you are all up to date with your ota and make sure you have a look in a settings / SHIELD POWER CONTROL/ OPTIMIZED
ttxcsabby said:
I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance
Click to expand...
Click to collapse
I've had that many times during one single day. Had to literally reboot the thing 5 or 6 times that day. COMPLETELY NO RESPONSE FROM THE SCREEN, ONLY BUTTONS. Still have to clue what the deal was. Hasn't done it since, but the issue DOES exist. And yes, I bought from the very first batch, straight from Nvidia.
I've had this problem since day one. Also the tab crashes at random times and it getting ****ing annoying. Thinking of returning the thing. It's worse than useless. Turn the screen off and you can bet that i'll have to reboot to get the touchscreen working again.
Idk why this helped but it did. I switched from using philz touch recovery to cwm recovery...now screen works less than half the time I turn it back on. That's still better than never.
Sent from my SHIELD Tablet
I've never experienced this on Stock, Only on Pac-Man ROM and CM11. Either way it is very annoying.
This is a reaaallllllyy ghetto work around until the issue is solved, but the way I worked around it on CM11 is to have Tasker and Secure settings wake the device for a few seconds every 45 mins - 1 hour. Ever since I've had Tasker performing that task I've had no issues with the screen being unresponsive.
I have figured out how to fix the touchscreen issues. All you have to do is go under Settings>Apps>All Apps and find anything that ranges from Google Taiwanese or any Google foreign language app and disable it. There should be two of them. I haven't had any problems since I disabled them. :good:
I found something that has worked so far. I always use Nova launcher since it's my fav. I didn't think much of leaving the launcher that came with the rom. I went to titanium backup and froze the other launcher and it solved the touchscreen issue. This also fixed the app crashing problems most of the time. Still if I run more than two applications at the same time everything on the tab starts crashing. Seems to be a ram problem. I checked max backround processes and it's at "normal" which usually is fine. If anyone has a solution to the crash problem please let me know. Meanwhile i'll keep trying stuff.
Sent from my SHIELD Tablet
Same problem here... Funnily enough I just wanted to try a custom rom to see whether this issue will be fixed and a new official upgrade to 7.0 came up - https://shield.nvidia.com/support/shield-tablet-k1/release-notes/1
Will see whether ithe problem is gone.
There was a time when my screen became a bit unresponsive. Very random. Calibrating the touch sensor fixed it up. Its a bit hidden but you'll find it by going into Settings>About Tablet (device)>Click on Model Number 3 times>The calibrating settings will pop up hit Touch then hit Start. It'll do it's thing and reboot. Hopefully it helps.
2kool2Bcruel said:
There was a time when my screen became a bit unresponsive. Very random. Calibrating the touch sensor fixed it up. Its a bit hidden but you'll find it by going into Settings>About Tablet (device)>Click on Model Number 3 times>The calibrating settings will pop up hit Touch then hit Start. It'll do it's thing and reboot. Hopefully it helps.
Click to expand...
Click to collapse
I had a similar issue with touchpoints not working near the corners, calibration fixed things for me also. It's pretty quick and easy to do so I urge you to try that before doing a factory reset.
So far so good... Android N seems to fix the problem
Sent from my Pixel using Tapatalk

Messed-Up Display

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.

SOD (sleep of death)

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.

Categories

Resources