Oneplus 5 Black screen after replacement - OnePlus 5 Questions & Answers

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?

Related

screen non responsive after wake up

​Had my vega for just 3 days, i left it on charge on the first night and when i tried to use it the morning after the touch screen was more or less completely dead, only a 1" stripdown the left side in landscape mode was responding to touch so i couldn't even unlock it without using the wake then press the back button method - even then the screen was non responsive.
I did a reboot hoping this would solve it but no change, anyway after leaving it off for half an hour and rebooting the screen started to work again and I had no further issues that day.
that night i let it go to sleep again and had the same issue again this morning, the screen was non responsive after a prolonged( 6hour ) sleep
this time i decided to see if it was software so put it into nvboot mode and flashed the modaco rom, - after getting the new rom up and running the screen was still lazy, serious dead spots in terms of touch, i let it go to sleep for a few hours in the afternoon and tonight the touch is not working again.
I bought it online from dixons, and tbh the box appeared to have already been opened when i got it.
I'm starting to think its a faulty unit with a serious hardware fault - has anyone else experienced the same - did you find a fix?
Have you tried running the screen calibration tool, i think it is included in the modaco rom. I have not had anything as serious as you seem to have (only a slight dead spot in the bottom left corner of the screen, which the tool fixed) might be worth a go, if you have not tried it, before getting a exchange.
thanks Ganjaman, cant get the darn thing past the accept terms and conditions screen after a fresh install of stock rom because i cant press the accept button because its in a non responsive part of the touch screen.
dont think i have any option but to return it
jimsey said:
thanks Ganjaman, cant get the darn thing past the accept terms and conditions screen after a fresh install of stock rom because i cant press the accept button because its in a non responsive part of the touch screen.
dont think i have any option but to return it
Click to expand...
Click to collapse
Bad luck! Hope you can get a exchange in-store.
Have flashed the new 1.09 rom and it seems to have fixed the screen issue.
What was interesting. Was that if I warmed the tablet up slightly near a heater the screen would slowly start working again. Ganjaman, will your 1.08 update add market to 1.09
I am going to remake it for v1.09 shortly, i need to remove flash change the build.prop and i am going to add usb switcher. Glad you sorted it.

Can't unlock - just relocks and goes black

My rooted 32GB has just started doing this (2nd time this has occurred now). When I try to unlock, it just makes a click sound and relocks and blacks the screen. The first time resolved itself. Not sure if a reboot will help (probably so), but wondering if anyone has seen this or has any suggestions.
doncaruana said:
My rooted 32GB has just started doing this (2nd time this has occurred now). When I try to unlock, it just makes a click sound and relocks and blacks the screen. The first time resolved itself. Not sure if a reboot will help (probably so), but wondering if anyone has seen this or has any suggestions.
Click to expand...
Click to collapse
Is there any magnet near the N7? (if you have case, maybe the it is not working to well, most of the case is not prepared for daily use )
Ábel
Does the screen turn on and everything looks fine, but there is no touch response at all? Do the hard buttons prompt the menu's like power down and volume control but there is absolutely no touch input? I am asking these questions because if it is doing this you are having the same issue as me, I had been working on this issue for a solid month with absolutely no luck and the issue kept getting more frequent.I have re-flashed stock Google images both 4.1 and 4.2 with absolutely no luck. After the clean installs I did not root it I left the it completely stock and the issue is still there, also I thought it may have been my Poetic magnet case, well i took it out of the case and it still does it. I even removed my $20.00 dollar Steinheil Ultra Crystal Screen Protector thinking that may have something to do with it but that's not the issue. After every reboot it will work fine, so I was completely frustrated and could not find that many people on line with this issue. I finally had to send mine back to ASUS and they stated it was a screen assembly issue and they could replicate the problem, well I got it back last week and five minutes after booting it up the issue is still there so needless to say I have to RMA it again. What really bugs me is the Nexus 7 worked fine for two months not one problem then, I left it in a cabinet for 2 days without touching it and that's when the issue started and it has just gotten worse.
I apologize for the long story if this is not your issue but I just wanted to save you a lot of hassle if it is.
My issue isn't as complicated, fortunately for me. The screen is black (even though cover, with magnet, is open). I hit the power button once to get the screen to light up and slide the unlock. It looks normal but only flashes for an instant, then makes the click and the screen goes black again.
It self resolved again, so I actually am suspecting that it could be that when the case is folder over, the magnet may possibly be causing this. So thanks for that suggestion. Next time it happens I'll be looking specifically for that to see if I can narrow it down.

screen/backlight issue, tripped knox phone, what to do?

I'll preface by saying I am an IT professional for work so this is no noob request.
So, this all started with my capacitive buttons acting up. I have CWM (tripped knox), SlimROM. What was happening was when my capactive buttons were lit and then would dim... whenever I'd press ANYWHERE on the screen (with the capactive buttons dimmed), it would press the back button for me. Made no sense to me, sounds weird I know. Never got around to trying to flash a new rom or anything, just ended up permanently having the buttons dimmed.
Fast forward a few days... in my car in the cupholder, spilled energy drink where my phone was sitting in cup holding. Probably only an inch high or so with my phone upside down (home button to the sky), so the charging port side was safe. That day is when it went south. I'd hit the power button on, screen would come on. Power button off and on again, screen would not go on (but capactive buttons WILL light up, and digitizer works and you can hear the audio). Off and on again, maybe came on. Intermittent. Put in rice for 36 hours. Same thing. Note that when the screen IS on it is perfectly fine and usable (the capacitive button problem is gone now too....). I set the display to turn off after 30 minutes of inactivity. It's been on for like 10 right now and hasn't flickered or nothing. It's just if I turn the phone off, and back on, chances are it will not come back on (but capacitive buttons always light and touch screen and audio still works). It seems to only come on when it's been left for a while. Like if I turned it off now, and went off/on/off/on/off/on it would probably stay black until i left for 10 minutes and then might fire on.
My Note 3 model is SM-N900W8 (Canadian TELUS). Behind the battery there is a speck of a circle that is pink looking. Unsure if this is a Liquid Damage Indicator. Another CLEAR liquid indicator on the top left when case is off is clearly white, the LDI on the battery is white. Had a hard time finding image that shows the LDI's. Anyway, KNOX is tripped. As far as I've researched I cannot change this. I do have a CWM image of the stock Samsung firmware. But, there is no point in going through warranty at this point (phone IS under warranty though) unless I can revert KNOX, and confirm the LDI's are all white......
I am thinking this would be a relatively easy hardware fix though. Everything seems to work perfectly fine if the screen IS on. It's just the screen getting on being finicky.....
Any suggestions?
Currently getting all data off, and then will try flashing another firmware etc. but this really seems like a hardware issue.....
Thanks for any advice!
brockmo said:
I'll preface by saying I am an IT professional for work so this is no noob request.
So, this all started with my capacitive buttons acting up. I have CWM (tripped knox), SlimROM. What was happening was when my capactive buttons were lit and then would dim... whenever I'd press ANYWHERE on the screen (with the capactive buttons dimmed), it would press the back button for me. Made no sense to me, sounds weird I know. Never got around to trying to flash a new rom or anything, just ended up permanently having the buttons dimmed.
Fast forward a few days... in my car in the cupholder, spilled energy drink where my phone was sitting in cup holding. Probably only an inch high or so with my phone upside down (home button to the sky), so the charging port side was safe. That day is when it went south. I'd hit the power button on, screen would come on. Power button off and on again, screen would not go on (but capactive buttons WILL light up, and digitizer works and you can hear the audio). Off and on again, maybe came on. Intermittent. Put in rice for 36 hours. Same thing. Note that when the screen IS on it is perfectly fine and usable (the capacitive button problem is gone now too....). I set the display to turn off after 30 minutes of inactivity. It's been on for like 10 right now and hasn't flickered or nothing. It's just if I turn the phone off, and back on, chances are it will not come back on (but capacitive buttons always light and touch screen and audio still works). It seems to only come on when it's been left for a while. Like if I turned it off now, and went off/on/off/on/off/on it would probably stay black until i left for 10 minutes and then might fire on.
My Note 3 model is SM-N900W8 (Canadian TELUS). Behind the battery there is a speck of a circle that is pink looking. Unsure if this is a Liquid Damage Indicator. Another CLEAR liquid indicator on the top left when case is off is clearly white, the LDI on the battery is white. Had a hard time finding image that shows the LDI's. Anyway, KNOX is tripped. As far as I've researched I cannot change this. I do have a CWM image of the stock Samsung firmware. But, there is no point in going through warranty at this point (phone IS under warranty though) unless I can revert KNOX, and confirm the LDI's are all white......
I am thinking this would be a relatively easy hardware fix though. Everything seems to work perfectly fine if the screen IS on. It's just the screen getting on being finicky.....
Any suggestions?
Currently getting all data off, and then will try flashing another firmware etc. but this really seems like a hardware issue.....
Thanks for any advice!
Click to expand...
Click to collapse
So how did it go?
I would just bring it to repair, it's better to lose a hundred canadian (send to repair or fix yourself) than to bear with a broken phone that doesn't sleep properly.
Test the proximity sensor and ambient light sensor.... If you have any "pocket mode" or active display features active in your rom try disabling those... Sounds like your warranty is definitely void but you could take it to a local independent shop if samsung wants too much to fix it.
Good luck!
Sent from my SM-T320 using Tapatalk
nicholaschum said:
So how did it go?
I would just bring it to repair, it's better to lose a hundred canadian (send to repair or fix yourself) than to bear with a broken phone that doesn't sleep properly.
Click to expand...
Click to collapse
Since I cannot stand when I research an issue, finally find someone with the same question and turns out there was never a resolution response, I am going to say that much to my shock, reflashing to my stock Samsung TouchWiz nandroid fixed the issue. I then clean flashed the latest SlimROM and all is well. I had dirty flashed to the latest (stable) SlimROM 4.4.4 and it worked fine for weeks which is why I had little to no faith a reflash would fix. Especially since the screen would be blacked out during the boot screens. That is baffling to me. A custom ROM/kernel should have no effect prior to the ROM booting should it? I guess I am wrong on that? Regardless, happy I did not have to work around the KNOX being triipped....
brockmo said:
Since I cannot stand when I research an issue, finally find someone with the same question and turns out there was never a resolution response, I am going to say that much to my shock, reflashing to my stock Samsung TouchWiz nandroid fixed the issue. I then clean flashed the latest SlimROM and all is well. I had dirty flashed to the latest (stable) SlimROM 4.4.4 and it worked fine for weeks which is why I had little to no faith a reflash would fix. Especially since the screen would be blacked out during the boot screens. That is baffling to me. A custom ROM/kernel should have no effect prior to the ROM booting should it? I guess I am wrong on that? Regardless, happy I did not have to work around the KNOX being triipped....
Click to expand...
Click to collapse
That's so strange, but congratulations on fixing it.
You should have a boot animation with any ROM you flash, just remember to check your MD5's to the developer's MD5's after you download.

[Q] momentarily unresponsive touch screen

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

Touch stop working after turning off and on the screen.

I've been using the PH-1 for a year and a half and its great, but a couple days ago i would unlock the phone via fingerprint (as ussual), it would unlock but the touch wont work, so i factory reset the phone and still the same, remove the case and the screen was loose (almost complete), but the cable was well connected on both sides so i got the screen glued, but still the same.
Im using Android Pie (from day 1) with March update (updated like a week ago), in order to use the phone beyond what Google assistant can do i have to reboot the phone (using power and volume buttons) to get the touch to work again and dont let the screen go off. Sometimes after rebooting the touch works even if i turn the screen off and on, but i think its just luck.
You guys think it might be a software issue? or hardware issue? because i don't live in the US or CA, so i would have to wait a couple weeks for the screen to get here and i would'nt be able to return it in case its not a screen malfunction.
I really don't wanna change my phone, i love the PH-1.
EDIT: i just replaced the screen with a new one from fixez.com and the problem persists, i think april's update broke something. is there something i can do to check the software? Pls help.
I rooted my phone and almost the same thing happens. I turn off the screen and turn it back on and the touch is unresponsive. Howver, ONLY the apps left on screen are unresponsive. I can still pull down from status bar its weird.
Update 1: I saw u mention fingerprinting. I removed mine and somehow it seems to have stopped. I'll use it for about another day or 2.
Update2: Well it doesn't. If my screen times out with an app open. The app is unresponsive upon waking.

Categories

Resources