Related
This is extremely recent, just in the past few days.
Seemed to happen after installing ICS MOD ROM, but the problem persists through to Gingerbread ROMs and even new installs of CWM.
Basically when I turn my screen on the screen doesn't recognise me at all. BUT if I turn it off and then on quickly it works again...
This sound like a digitizer problem? What's my options?
read the link in my signature
gdsbalaji said:
read the link in my signature
Click to expand...
Click to collapse
Why...
Oh, weird thing about this I discovered after posting:
This problem only occurs when I wake the phone with power/end call...
Anyone got any idea?
Common fault linked either to end button sticking or touch screen ribbon conector that runs under button is worn by flexing stresses from button use.
there is a thread on apply preassure on button & wiggling it in circular figure of 8 motions with finger in an attempt to clean button if it is sticking issue, procedure could make it better or worse & long term solution is probably dismantling for inspection/repair.
G8D said:
This is extremely recent, just in the past few days.
Seemed to happen after installing ICS MOD ROM, but the problem persists through to Gingerbread ROMs and even new installs of CWM.
Basically when I turn my screen on the screen doesn't recognise me at all. BUT if I turn it off and then on quickly it works again...
This sound like a digitizer problem? What's my options?
Click to expand...
Click to collapse
In short - Yes
Try what Mister B says, it gave me about 5 seconds more of touch screen life after it gave up again for good. But for some others its worked for longer periods of time; but the problem won't go away unless the digitizer is replaced.
Hi guys
I have moved from iPhone to a note 4 and loving it!
I was just wondering if anyone has found the touch screen occasionally doesn't respond to their touch and you have to touch it again. On the iPhone it only ever missed a touch if my finger was in the wrong place, but it never happened on the keyboard. Every so often maybe 5/6 times a day I touch a key on the keyboard and nothing happens, when I try again it's fine. I can't reproduce it, because when I tap anywhere on the keyboard something gets pressed. I was just wondering if this was normal?
Hope you are enjoying your phones!!
Anyone?
It's most likely cause your palm is on the phone. One of the downsides of a slim bezel on a big phone. Also keep in mind if your spen is on the screen, your fingers won't work. A case might help.
I thought about another part of my hand touching the screen, however with half my hand layed across my keyboard I can still type with the other hand. Thanks for the response
I Pele tried factory resetting today and not installed any apps, but it is still happening
I rang Samsung this morning and they advised I return I to the store and get an exchange. Luckily my local store got its first batch of note 4s in this morning and they swapped it out. I restored it all firmware updates put on it and now works fine! The only thing I haven't installed is a Google play system update thing. I was wondering if that was the cause x
Similar issues
I've had similar issues (in fact, that's what brought me here in the first place). Initially, I was able to tap on the screen in the text box and then continue typing (I use Swype). However, now my messaging app (default Messages) just freezes up, forcing me to close the app, clear the memory, and relaunch the app before continuing.
Were you using the default app and/or Swype when you had issues? I'm going to try to factory reset my phone to see if it helps.
It's taken a couple of weeks for this problem to develop, so please keep us posted if this problem arises again on your new phone!
Edit: Also want to point out that when I text, I use one hand to hold the phone and only a finger to swipe my text. As such, only the one finger touches the screen.
unable to use touch screen. only hard key were working >>Note4
Hi everyone,
today i just had the same problem with the touch screen. no response at all .. after i tried and took out the spen .. and surprise it worked with the pen.
tried again with fingers still nothing worked, so i used the pen to reboot the note4.
hope my experience helps.
cheers,
djvaliro said:
Hi everyone,
today i just had the same problem with the touch screen. no response at all .. after i tried and took out the spen .. and surprise it worked with the pen.
tried again with fingers still nothing worked, so i used the pen to reboot the note4.
hope my experience helps.
cheers,
Click to expand...
Click to collapse
Same thing happened to me last night. The touchscreen became unresponsive while using chrome. The phone was a little warm but not bad. I didn't try the pen, sounds like a good idea. I am not certain it was a touch screen issue with mine. Almost more of a processor issue. I got the phone to lock. After pressing the menu or lock button to wake the screen it would take 5-10 seconds to wake. Then I could swipe my unlock pattern. It would not show any lines. I would wait, the screen would turn black after timing out in about 5s. The about 5s after I could hear the speaker make the unlock sound. I ended up doing a battery pull and that fixed the issue. Anyone else have something similar?
Should I try and replace it?
badtoy1986 said:
Same thing happened to me last night. The touchscreen became unresponsive while using chrome. The phone was a little warm but not bad. I didn't try the pen, sounds like a good idea. I am not certain it was a touch screen issue with mine. Almost more of a processor issue. I got the phone to lock. After pressing the menu or lock button to wake the screen it would take 5-10 seconds to wake. Then I could swipe my unlock pattern. It would not show any lines. I would wait, the screen would turn black after timing out in about 5s. The about 5s after I could hear the speaker make the unlock sound. I ended up doing a battery pull and that fixed the issue. Anyone else have something similar?
Should I try and replace it?
Click to expand...
Click to collapse
Observe to see if it happens when you're using other apps too. Chrome has been notorious for causing all sorts of problems, like reboots, freezes, etc on some devices.
Also it may be worth installing Chrome Samsung Support Library.
Sent from my SM-P600 using Tapatalk
iridaki said:
Observe to see if it happens when you're using other apps too. Chrome has been notorious for causing all sorts of problems, like reboots, freezes, etc on some devices.
Also it may be worth installing Chrome Samsung Support Library.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Thank you for the app. I installed it and will keep watching for it again.
swampystorm said:
Hi guys
I have moved from iPhone to a note 4 and loving it!
I was just wondering if anyone has found the touch screen occasionally doesn't respond to their touch and you have to touch it again. On the iPhone it only ever missed a touch if my finger was in the wrong place, but it never happened on the keyboard. Every so often maybe 5/6 times a day I touch a key on the keyboard and nothing happens, when I try again it's fine. I can't reproduce it, because when I tap anywhere on the keyboard something gets pressed. I was just wondering if this was normal?
Hope you are enjoying your phones!!
Click to expand...
Click to collapse
Got the same problem after 2 months of normal usage... I initially though I had installed a third party application which was causing the system freeze but this was not the problem.
- tried factory resetting and not installed any apps, but it is still happening
- When this happens if I take out the spen .... surprise it work. The pen allows me to do anything... But the touch screen does not work with fingers...
- I used the pen to reboot the note4... Still the same problem after reboot... I ended up doing a battery pull and that fixed the issue for.... a couple of minutes... Then the problem came back....
The only solution remaining was to return the phone.... They gave me a Note3 while my Note4 is being repaired...
That's a shame for a product of that price!
:crying:
Same thing is happening with my 2 months old note4 since two weeks ago. An horizontal line 1.5cm in width about 1/3 from the bottom of the screen, became unresponsive. At reboot it works sometimes then it becomes unresponsive again. It looks like in the image I attached, the difference is that the area is horizontal, not vertical. I'm taking my note4 to the store today for warranty, hopefully they will replace it. I haven't abused the device in any way, I have a screen protector since its first day.. I really hope this isn't a serious problem that affects many users.
Just like some of you mentioned above, the pen has no issues on any area of the screen.
Cheers!
amwebexpert said:
Got the same problem after 2 months of normal usage... I initially though I had installed a third party application which was causing the system freeze but this was not the problem.
- tried factory resetting and not installed any apps, but it is still happening
- When this happens if I take out the spen .... surprise it work. The pen allows me to do anything... But the touch screen does not work with fingers...
- I used the pen to reboot the note4... Still the same problem after reboot... I ended up doing a battery pull and that fixed the issue for.... a couple of minutes... Then the problem came back....
The only solution remaining was to return the phone.... They gave me a Note3 while my Note4 is being repaired...
That's a shame for a product of that price!
:crying:
Click to expand...
Click to collapse
same thing happen to my note4 today. the only difference is that yours was fixed for a couple of minutes after removing the battery. my note4 wasn't fixed after that. Only S-pen works, touch screen with fingers wont work. you mentioned you're note4 is getting repaired, did they tell you what may have happened to it so that i'll get an idea of the cause..
You found the appropriate thread, I was just now going to share the link to this thread with you as well as quoting what others experienced,
http://forum.xda-developers.com/showpost.php?p=56313609&postcount=6
http://forum.xda-developers.com/showpost.php?p=56464866&postcount=8
http://forum.xda-developers.com/showpost.php?p=57302776&postcount=9
http://forum.xda-developers.com/showpost.php?p=57304242&postcount=10
http://forum.xda-developers.com/showpost.php?p=58421560&postcount=12
http://forum.xda-developers.com/showpost.php?p=58452707&postcount=13
Never purchase a device without a return / DOA policy. Not worth the hassle. If it hasn't been 30 days, you should call your credit card company or Paypal and place the amount on dispute, wait, you purchased from another market, please tell you didn't pay by cash.
vjevardone said:
same thing happen to my note4 today. the only difference is that yours was fixed for a couple of minutes after removing the battery. my note4 wasn't fixed after that. Only S-pen works, touch screen with fingers wont work. you mentioned you're note4 is getting repaired, did they tell you what may have happened to it so that i'll get an idea of the cause..
Click to expand...
Click to collapse
I have this problem after I flash CWM recovery, before this was flashed with twrp recovery, I reflash stock rom with odin, I flash many times CWM and TWRP and I still have the problem, my warranty it's void now but I think to go at Samsung store to see if they solve my problem. This problem look like a driver for touch corrupted, if somebody find it out how to fix or have any ideea please weritte here, thanks you
I've started to have this problem as well, lower part of the left side of the screen sometimes registers touch instead of scrolling! Very annoying, tried to update recovery, tried tapping screen, doesn't help. The worst thing is I cannot reproduce the issue at will... It seems pretty random.
hi
inter *#2663#
and select fw software.
farnam-ferdosi said:
hi
inter *#2663#
and select fw software.
Click to expand...
Click to collapse
Unfortunately, if the phone is on Verizon, the dialing codes will be disabled.
Potential fix.
Please excuse the necropost But I came here looking for a solution from google and others may too. I found a way to solve this issue/s.
There appear to be two issues affecting this.
1. Overloading the processor.
2. Static.
If your touch input is lagging or doesn't register at all but then suddenly does a few moments later, its likely a type 1. problem. I fixed this by disabling resource intensive features such as s voice. This also improved battery life and overall performance considerably.
If touch simply doesn't work at all, but s pen works fine then the problem is more likely type 2. That being static buildup in your person. Simply touch something that can ground you and it should fix the issue. A metal tap should work. Be wary, you might even get a little zap as you discharge
Hello
I search on forum idea for fix my home button & fingerprint . Method from this topic doesn't work. http://forum.xda-developers.com/oneplus-2/general/guide-oneplus-2-home-button-dead-t3324321
I have OOS 2.2.1 and stock recovery & unlocked bootloader. In test menu I see red text: Fail. Please help me fix my home button. :crying:
P.S. Sorry my English isn't good.
http://forum.xda-developers.com/oneplus-2/development/rom-blisspop-t3226519
Try flashing this + fw included
What worked for me:
1. Upgraded to twrp 3.0.0.2
2. Format everything.
3. Flashed CM13. Clear cache.
4. Boot!
teeluun said:
What worked for me:
1. Upgraded to twrp 3.0.0.2
2. Format everything.
3. Flashed CM13. Clear cache.
4. Boot!
Click to expand...
Click to collapse
YOU MEAN THAT THE PROBLEM IN THE OXYGEN IT SELF
PLEASE GUYS i HAVE THE SAME PROBLEM AND NEED TO SOLVE IT WITH THE SAME OXYGEN
IS THERE ANY HOPE
---------- Post added at 02:26 AM ---------- Previous post was at 02:21 AM ----------
hunter_bruhh said:
http://forum.xda-developers.com/oneplus-2/development/rom-blisspop-t3226519
Try flashing this + fw included
Click to expand...
Click to collapse
if I flash blissbob it will solve the problem ?
but finger print will not work
correct ?
teeluun said:
What worked for me:
1. Upgraded to twrp 3.0.0.2
2. Format everything.
3. Flashed CM13. Clear cache.
4. Boot!
Click to expand...
Click to collapse
Doesn't help
hunter_bruhh said:
http://forum.xda-developers.com/oneplus-2/development/rom-blisspop-t3226519
Try flashing this + fw included
Click to expand...
Click to collapse
Doesn't help too
For me to.I have tried all the methods. That's my last OnePlus device.
Who help me & rakieta with FP & home button?
I'm in the same boat.. Did, at any time, you get the button kinda wet?
Venomous01 said:
Doesn't help
Click to expand...
Click to collapse
This helped me a lot.
After i flashed cm13,
I charged my phone using car charger
While it is charged, i hold down the power button until it is rebooted
I do it twice to get my fingerprint scanner back alive.
Sorry for my bad english.
I was wondering if I could get a little input from some experienced users of the Oneplus devices. I am traditionally a HTC One person. I love the Sense UI's going back to Sense 5. And the One devices sturdy build and strong hardware specs.
I have noticed that the Oneplus 2 is virtually the same spec wise as the One M9. They have the same CPU and similar RAM. The biggest difference in specs would be the display size, resolution and PPI.
I am really tempted to go with the Oneplus 2 mostly for the display size. I just was curious if anyone who uses it also had some experience with a Sense UI device and how they compare. And basically overall comparison to the HTC One M8 or M9.
Thanks,
Venomous01 said:
Who help me & rakieta with FP & home button?
Click to expand...
Click to collapse
Because home button probably we need someone who's good with partitions. In other post I've read like who fixed the problem with the modem and Imei, somehow with fastboot "erase modem". Perhaps similar to what needs to be done with Home button issue. But which partition is responsible for driver of the Home button? Sorry for my English
Venomous01 said:
Who help me & rakieta with FP & home button?
Click to expand...
Click to collapse
Brother just wipe cache, delvik,data and system than install new modem with exodus 6.0.1 and open google app.now reboot.
When the phone will boot your fingerprint sensor andhome button will start working.
It's the method which helped me to reset my OnePlus 2.
Press thanks if i helped.
why is it all of a sudden a lot of people (including my self) are having finger printer reader / home button issue on various OS. I was on CM13, some people are on Oxy****. Is there some sort of hardware firmware issue ?
I bet it is a hardware defect
Sent from my ONE A2005 using Tapatalk
fburgos said:
I bet it is a hardware defect
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
It is not hardware defect my friend.i have come to this conclusion after two times home button and fingerprint sensor failure.
Solution-Wipe system,data,cache and delvik cache in TWRP recovery and flash new modem,exodus 6.0 and open google app and reboot.
I have rocked my OnePlus 2 last three months without fingerprint sensor and dead home button.it is the solution which worked for me.
paradise220 said:
It is not hardware defect my friend.i have come to this conclusion after two times home button and fingerprint sensor failure.
Solution-Wipe system,data,cache and delvik cache in TWRP recovery and flash new modem,exodus 6.0 and open google app and reboot.
I have rocked my OnePlus 2 last three months without fingerprint sensor and dead home button.it is the solution which worked for me.
Click to expand...
Click to collapse
I think its a mix of luck and bad hardware.
Think has been more than a month since I faced that failure in oxislim, no software solutions worked.
Failure, made a twrp backup, tried every software solution, like clear cache, stopped services, clean flash, stock full zip, etc etc, restored twrp backup started using software buttons, then I just started pressing the home button with my fingernail, really hard like trying to scratch the sensor, and somehow it chance to home screen, tested again, unlocked using FP and it has been flawless since.
Sent from my ONE A2005 using Tapatalk
fburgos said:
I think its a mix of luck and bad hardware.
Think has been more than a month since I faced that failure in oxislim, no software solutions worked.
Failure, made a twrp backup, tried every software solution, like clear cache, stopped services, clean flash, stock full zip, etc etc, restored twrp backup started using software buttons, then I just started pressing the home button with my fingernail, really hard like trying to scratch the sensor, and somehow it chance to home screen, tested again, unlocked using FP and it has been flawless since.
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
It's not luck my friend,it's a software glitch.
Oneplus should consider it and correct in any software update.
paradise220 said:
It's not luck my friend,it's a software glitch.
Oneplus should consider it and correct in any software update.
Click to expand...
Click to collapse
how is it a software glitch? CM13 is not even officially released by OnePlus and it too has problems. I am on CM13 seraph's build and my finger print scanner and home button are toast. I'm f'ing fed up with OnePlus, not giving this company a chance any more. Had issues with my OPO and now my OPT.
paradise220 said:
It's not luck my friend,it's a software glitch.
Oneplus should consider it and correct in any software update.
Click to expand...
Click to collapse
I cannot confirm is a software issue but I bet is a hardware defect, why?
In my own experience I blame hardware failure like a bad contact gound issue or something just because software didn't fixed my issue, I did something physically to the hardware and instantly started working, since that failure I've been in stock, oxyslim, h2os, customs and never had an issue.
Also couple of people reported using their phone with wet hands or around moisture and FP stopped working, mine fail in a moisture environment (pocket+exercise+hot weather=sweat).
What I think is that reflashing, clearing cache, charging 0-100 they all make the phone heats, with heat moisture goes out and FP start working again, mine didn't
I made a nandroid of my phone (all software is copied including every "software issue")
Changed everything of the software side. Didn't fixed my issue.
Restored nandroid (the one with the same "software issue" I started) is not fixed. At this point I'm angry and frustrated I scratch and press my home button with my fingernail and it start working again.
My personal opinion based on my experience, mine was software? definitely no.
ludester said:
how is it a software glitch? CM13 is not even officially released by OnePlus and it too has problems. I am on CM13 seraph's build and my finger print scanner and home button are toast. I'm f'ing fed up with OnePlus, not giving this company a chance any more. Had issues with my OPO and now my OPT.
Click to expand...
Click to collapse
So your home button is completely dead? I guess you tried fixing it via software, any success?
Sent from my ONE A2005 using Tapatalk
Looks like common problem, suspect it surfaced after recent upgrade to Oreo. There is a popup that says "Can't read fingerprint blah blah, if problem persists, reboot". Trying to access the fingerprint option, it is also gone from the Settings menu. Also have multiple agents with given administrative rights since I use this phone to access office emails and stuff, it does give them the right to delete fingerprints i suppose, but somehow it just happened out of the blue one day. Repeated rebooting, holding down both volume up and down type of rebooting, clearing cache, doesn't help. Based on simple search it is common enough this problem, but no good solution.' Stock, non root.
Will be grateful if anyone has any ideas. Thanks.
epiphone said:
Looks like common problem, suspect it surfaced after recent upgrade to Oreo. There is a popup that says "Can't read fingerprint blah blah, if problem persists, reboot". Trying to access the fingerprint option, it is also gone from the Settings menu. Also have multiple agents with given administrative rights since I use this phone to access office emails and stuff, it does give them the right to delete fingerprints i suppose, but somehow it just happened out of the blue one day. Repeated rebooting, holding down both volume up and down type of rebooting, clearing cache, doesn't help. Based on simple search it is common enough this problem, but no good solution.' Stock, non root.
Will be grateful if anyone has any ideas. Thanks.
Click to expand...
Click to collapse
Try this. Turn off phone. Hold down power and volume Up and Down together for 10 seconds. It will start in hardware control mode presss power button and phone will restart. This should clear the fault.
Thanks for the suggestion, Sir! Much appreciated.
Actually that was one of the things I tried as well, didn't work though.
rosko166 said:
Try this. Turn off phone. Hold down power and volume Up and Down together for 10 seconds. It will start in hardware control mode presss power button and phone will restart. This should clear the fault.
Click to expand...
Click to collapse
Try squeezing the phone a bit in the area between the power button and cameras. I've heard multiple reports of this working. Seems to be a not-so-great physical connection to the sensor. The newer software may be more picky about it.
I have the sprint variant. My fingerprint reader went out some months ago. I've heard some people were able to get it back, but I wasn't one of them. I'm glad I had the second year warranty now. I had to send it in to LG. They are sending me a whole new phone.
epiphone said:
Looks like common problem, suspect it surfaced after recent upgrade to Oreo. There is a popup that says "Can't read fingerprint blah blah, if problem persists, reboot". Trying to access the fingerprint option, it is also gone from the Settings menu. Also have multiple agents with given administrative rights since I use this phone to access office emails and stuff, it does give them the right to delete fingerprints i suppose, but somehow it just happened out of the blue one day. Repeated rebooting, holding down both volume up and down type of rebooting, clearing cache, doesn't help. Based on simple search it is common enough this problem, but no good solution.' Stock, non root.
Will be grateful if anyone has any ideas. Thanks.
Click to expand...
Click to collapse
The exact same thing happened to me a few weeks ago. I tried everything possible, but nothing worked. I only had a year of warranty, and it had just expired 3 days ago. I had to send it to the LG service center. They replaced the entire back panel and put it back using the water resistant glue (I did end up paying for the repair). But my phone is as good as new. I suggest you do the same thing if you want it fixed.
This worked perfectly for my lg g6. You're a life saver. Thanks so much
jdock said:
Try squeezing the phone a bit in the area between the power button and cameras. I've heard multiple reports of this working. Seems to be a not-so-great physical connection to the sensor. The newer software may be more picky about it.
Click to expand...
Click to collapse
Blissmercury said:
Click to expand...
Click to collapse
Worked for me also. Thanks!
I replaced the glass back and fingerprint sensor myself....and trust me, when it comes to ANYTHING D.I.Y. I am useless....but even I found it simple.
Matt
In most cases is just a sealing tape stratify itself and because of this fingerprint sensor lose connection. Before you replace whole back and sensor you can try to replace sealing tape, in 90% cases I had with G6 it helped.
I solved it with another trick
I removed back cover and noticed the erased thermal paste under motherboard on SoC and glass panel
I cleaned it and applied new one put back cover now it is working without problem
Squeez is not permanent solution
junejo46726 said:
I removed back cover and noticed the erased thermal paste under motherboard on SoC and glass panel
I cleaned it and applied new one put back cover now it is working without problem
Squeez is not permanent solution
Click to expand...
Click to collapse
NICE !
I call that - EPIC WIN!:laugh:
Matt
I have a fix
i have a video on the fix, but as i am a new user, Xda wont lemme post the link. you guys can go look up the channel "ABS TECH" and theres a video on that with english captions.
My OP5 screen had a small crack so I decided to repair it. After following the tutorial on youtube step by step the phone powers up fine. But as soon as the screen goes to sleep, it get stuck in black, although it feels like responsive (Ican hear the clicks and vibrates and all) but it wont wake up
imercado said:
My OP5 screen had a small crack so I decided to repair it. After following the tutorial on youtube step by step the phone powers up fine. But as soon as the screen goes to sleep, it get stuck in black, although it feels like responsive (Ican hear the clicks and vibrates and all) but it wont wake up
Click to expand...
Click to collapse
Could you wake up the screen? Maybe it's a connection problem or related to the proximity sensor?
Did you ever find a solution to your problem? I have exactly the same problem, but it happens only with Android 9.0. Oreo seems to be working OK, but as soon as I upgrade to official 9.0, the screen won't wake up from sleep. The backlight turns on, but the screen stays black. The phone works OK as long as I use it, but if I press the power button or let it to enter "standby mode", it will stay that way (off). I suppose it has something to do with the replacement screen, but since it works with 8.0, I wish there was a workaround to get the LCD to work with Pie too.
Same problem here. Replaced display too.
I've had a similar issue with a different device before (ZTE nubia Z7 mini). I replaced the screen and it would work correctly, but when I booted TWRP, I would get a black screen. I figured that because the replacement screen was not an OEM one, it may have something to do with LCD drivers in the recovery. I used the old cracked screen with the device opened up to navigate in the TWRP recovery, and I flashed an newer/different recovery. Voila, the new recovery worked with my replacement screen. Based on this experience, it may just be an LCD driver compatibility issue with the replacement screen, causing the screen to just go into forever sleep mode. The driver may need to be changed or tweaked in the Pie version for your replacement screen to work with it. Just a thought, not fully certain.
iwantademo123 said:
I've had a similar issue with a different device before (ZTE nubia Z7 mini). I replaced the screen and it would work correctly, but when I booted TWRP, I would get a black screen. I figured that because the replacement screen was not an OEM one, it may have something to do with LCD drivers in the recovery. I used the old cracked screen with the device opened up to navigate in the TWRP recovery, and I flashed an newer/different recovery. Voila, the new recovery worked with my replacement screen. Based on this experience, it may just be an LCD driver compatibility issue with the replacement screen, causing the screen to just go into forever sleep mode. The driver may need to be changed or tweaked in the Pie version for your replacement screen to work with it. Just a thought, not fully certain.
Click to expand...
Click to collapse
You're probably right about the driver issue. My OP5 has no problems whatsoever with Android 8.1, but 9.0 won't work no matter what I do after waking up the device. The backlight turns on and and off for a few times after which nothing happens. The phone is still working normally, but it's in "blind mode" (music will continue playing, volume buttons work...but they're kind of slow and laggy) Too bad that the latest update (9.01) didn't fix this issue either. I really wouldn't hold my breath getting this issue fixed anytime soon (officially) as it seems to be a cheap 3rd party screen problem.
edit: I tried the custom recovery (20181227) and the same thing happens there. Once screen goes off, it won't come back on.
Edit 2: gave up on the replacement screen and ordered an oem lcd. Lets see how it goes.
sbasil said:
You're probably right about the driver issue. My OP5 has no problems whatsoever with Android 8.1, but 9.0 won't work no matter what I do after waking up the device. The backlight turns on and and off for a few times after which nothing happens. The phone is still working normally, but it's in "blind mode" (music will continue playing, volume buttons work...but they're kind of slow and laggy) Too bad that the latest update (9.01) didn't fix this issue either. I really wouldn't hold my breath getting this issue fixed anytime soon (officially) as it seems to be a cheap 3rd party screen problem.
edit: I tried the custom recovery (20181227) and the same thing happens there. Once screen goes off, it won't come back on.
Edit 2: gave up on the replacement screen and ordered an oem lcd. Lets see how it goes.
Click to expand...
Click to collapse
Do keep us updated if changing the display again fixes this issue. Would be interesting if someone had a fix for 3rd party displays but as of now it seems that's highly unlikely
]
iwantademo123 said:
Do keep us updated if changing the display again fixes this issue. Would be interesting if someone had a fix for 3rd party displays but as of now it seems that's highly unlikely
Click to expand...
Click to collapse
Sure.
Got the new OEM amoled screen today. It's brighter, more responsive and doesn't get stuck (black screen) with Android Pie. Problem solved. Price was 3 x higher than the cheap 3rd party screens, but definitely worth it (around 80 euros). All screen gestures work as well.
Bought it on Witrigs (https://www.witrigs.com/oem-lcd-screen-assembly-for-oneplus-5-midnight-black). it came really well packed and arrived fast (7-10 days to Finland). I highly recommend this screen and Witrigs to everyone
Also changed the screen from a friend and have this strange behavior, that the screen won't turn on .. only when I reboot or double press the power button so it launches the camera - the delay tho is about 7s, which is insane! you guys think this is the screen problem, or did I damage something and if yes, what? I repaired about 100 phones in total already ..
Link to the video: https://youtu.be/QmkBspymv8w
androidfreak11 said:
Also changed the screen from a friend and have this strange behavior, that the screen won't turn on .. only when I reboot or double press the power button so it launches the camera - the delay tho is about 7s, which is insane! you guys think this is the screen problem, or did I damage something and if yes, what? I repaired about 100 phones in total already ..
Link to the video: https://youtu.be/QmkBspymv8w
Click to expand...
Click to collapse
Sounds a lot like my OP5 with cheap 3rd party screens which would hardly work at all with Android Pie. If your friend's phone is running on Pie, try downgrading it to Oreo and see if that helps. My phone worked moderately with Oreo but not at all with Pie (wake and touch issues). Currently my OP5 is running Android Pie perfectly with the screen that I bought on Witrigs.
androidfreak11 said:
Also changed the screen from a friend and have this strange behavior, that the screen won't turn on .. only when I reboot or double press the power button so it launches the camera - the delay tho is about 7s, which is insane! you guys think this is the screen problem, or did I damage something and if yes, what? I repaired about 100 phones in total already ..
Link to the video:
Click to expand...
Click to collapse
Bizarre, have you tried the usual factory reset / rom reflash? If you confirm that its not a software related issue, then it probably is just the screen if its not an OEM part. Can't see what else would be the issue here unless there was other kind of damage before the repair maybe
Like @sbasil mentioned, it could just be due to the non-OEM screen being incompatible with Pie drivers.
Thank you for saving my phone
sbasil said:
Sounds a lot like my OP5 with cheap 3rd party screens which would hardly work at all with Android Pie. If your friend's phone is running on Pie, try downgrading it to Oreo and see if that helps. My phone worked moderately with Oreo but not at all with Pie (wake and touch issues). Currently my OP5 is running Android Pie perfectly with the screen that I bought on Witrigs.
Click to expand...
Click to collapse
Thank you for saving my phone
Mine not working with lineage base rom but is good with last pie 9.0.8. Did you try it?
Have this issue too
My OP5 has its original AMOLED screen. Running OS 9.0.8. This started happening after the most recent update. At least I never noticed it before.
I ran *#808# diagnostics, thinking maybe it's the proximity sensor, or the fingerprint scanner, but everything passed.
Also while locked, ambient display works. It's just getting the Home screen to appear after waking the phone that's become agonizing. And it does wake, the touch screen is responsive, it's just completely blind.
I mean consider this: I can take a screen shot, a screen shot, while the screen is in ambient display and the screen shot is of the home screen.
Pressing the power button or home button or notification slider repeatedly sometimes coaxes it to appear, but the only sure way to get the Home screen back is to restart the phone.
I had a black screen issue after changing the screen to an OEM AMOLED one, and after tearing my hair out for a couple of hours, I discovered that turning off " night mode" fixed the problem instantly
Same happened to me... cracked screen, purchased 'OEM screen' installed. Some apps work, some just black screen.
Driver issue? Running Pie 9x. Anyone had success with this by dropping back to Oreo? Would it do anything different to flash the Pie Firmware?
I repair/upgrade OnePlus 3/3T/5/5T phones to donate to families in need at the local family shelter. Some of them have lost or had to sell their phones just to get food and such. Now they need one to arrange job interviews and housing, things of that nature. So anyways, all that to say this.... I have replaced a LOT of displays, and all of them were the 'cheap' ebay variety. Each and every time I would replace the display, the phone would act just as described in this thread.
After long hours of reading, searching, and experimenting, I have found the ultimate and final solution to this problem. The answer to this issue is simple, but was not so simple to find. Whenever anyone does a screen replacement, and the screen is not the high-priced OEM variety, their phone will almost always have extreme difficulty in waking. The fix, and it has worked for me 100% of the time, is to flash a custom kernel. For the OP5/5T the kernel I use that always works is the Affinity kernel. Just flash and forget. The phone will always wake up after you flash that kernel.
However, don't forget, that what also happens with these lower priced replacement screens is that you can no longer double-tap to wake. I still haven't found a solution for that problem, but it always happens each time I replace a screen. The kernel won't help with that. But it does fix the 'won't wake up' problem.
Try it for yourself and see. You will be happy you did!
Oblias said:
... The fix, and it has worked for me 100% of the time, is to flash a custom kernel. For the OP5/5T the kernel I use that always works is the Affinity kernel. Just flash and forget. The phone will always wake up after you flash that kernel.
Click to expand...
Click to collapse
Please, can you point which FW you're using?
d2mac said:
Please, can you point which FW you're using?
Click to expand...
Click to collapse
I'm not clear about what you are asking. What exactly are you calling FW?? Some people mean radio and camera firmware. Some people mean the custom rom that gets flashed. What do you mean?