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.
Related
at the begining , my HD is fine.
But , after 2month , the phone has some rotation problem( it doesn;t matter, as you can solve it by pressing the on/off buttom )
But now, the phone's screen can't switch on, when i touch the four buttom on the surface of phone, it still vibrate..just i can't switch on the screen"
i have already tried all the things like take out the battery, press the reset buttom... the problem still occur,
Screen can sometime turn on luckily~
but, if the phone's screen is switched off for a while, the problem still occur..
can any professional heal my phone?
likashing said:
at the begining , my HD is fine.
But , after 2month , the phone has some rotation problem( it doesn;t matter, as you can solve it by pressing the on/off buttom )
But now, the phone's screen can't switch on, when i touch the four buttom on the surface of phone, it still vibrate..just i can't switch on the screen"
i have already tried all the things like take out the battery, press the reset buttom... the problem still occur,
Screen can sometime turn on luckily~
but, if the phone's screen is switched off for a while, the problem still occur..
can any professional heal my phone?
Click to expand...
Click to collapse
Obvious questions: Have you tried a hard reset?, Diff rom? Have you loaded up anything weird that mighta casued issues? If it will do a hard reset then do it. Start from scratch. If it works then be mindful of what you reload it with. If that doesn't get it, try a diff rom. At this point you got nothing to lose. Will it go into bootloader mode?
Battery comes to mind also. Have you run it down to nothing? Sometimes that will affect the charging capabilities. When the screen is dark can you still hear sound? Def do the HR.
My suggestion would be, to give the HD to your reseller and get it fixed.
I have had the same problem, and as my HD also didn't connect to my PC anymore, I send it in, and got a brand new one, because they couldn't fix it. Make a backup while you can, because the problem will get worse over time.
Likashing, the same exact thing started to happen to me a couple days ago. I've hard reset and flashed a new ROM. It seems that the problem is intermittent. After I just let the phone sit for a few minutes, the screen will come back on. It makes me wonder if this is heat-related issue. Anyway, I'm screwed, because I have no warranty since I bought it from a guy in Australia (I'm in US and needed the T8285).
I'll definitely be keeping an eye here to see if there's any resolution other than repair.
while the screen does not turn on, have you maybe tried to use another phone to call your HD and check if the screen turns on when the call arrives?
maybe if the screen turns on it's more a software related issue (so hardreset et cetera might be worth a try), if not, i fear it's hardware
crashDebug said:
while the screen does not turn on, have you maybe tried to use another phone to call your HD and check if the screen turns on when the call arrives?
maybe if the screen turns on it's more a software related issue (so hardreset et cetera might be worth a try), if not, i fear it's hardware
Click to expand...
Click to collapse
Good point crashDebug... I will definitely try that the next time the behavior is exhibited (right now is one of those times where I can't intentionally duplicate the issue... of course!)
stpete111 said:
Likashing, the same exact thing started to happen to me a couple days ago. I've hard reset and flashed a new ROM. It seems that the problem is intermittent. After I just let the phone sit for a few minutes, the screen will come back on. It makes me wonder if this is heat-related issue. Anyway, I'm screwed, because I have no warranty since I bought it from a guy in Australia (I'm in US and needed the T8285).
I'll definitely be keeping an eye here to see if there's any resolution other than repair.
Click to expand...
Click to collapse
...i have no warranty too....
in Taiwan , there are couple of people have these situation, the maintenance staff working Htc, said that it is a motherboard problem or the screen problem...but i wonder that why only few people have this problem. My phone is completely fine before i flash the HSPl1.56OLINEX.but when i try to flash back to Hspl 1.4 , the problem still happen.....
cbreze said:
Obvious questions: Have you tried a hard reset?, Diff rom? Have you loaded up anything weird that mighta casued issues? If it will do a hard reset then do it. Start from scratch. If it works then be mindful of what you reload it with. If that doesn't get it, try a diff rom. At this point you got nothing to lose. Will it go into bootloader mode?
Battery comes to mind also. Have you run it down to nothing? Sometimes that will affect the charging capabilities. When the screen is dark can you still hear sound? Def do the HR.
Click to expand...
Click to collapse
i have tried diff rom and diff HSPL....
sometimes, the phone's screen still can turn on luckily, then i can go to bootloader mode, but if the phone sit for a while, the phone's screen can't turn on...then i can't get into bootloader. ..
i can hear sound when someone phone me...but the screen still keep dark!
Exactly same problem here
HTC purchased in Sweden.
Cant switch screen on, when incoming calls come it rings but no screen alive. Vibration when pressing the buttons at bottom. And the low battery sound i can here when low on battery.
When connecting it to charger the orange light at power button will not light up (orange) as usually.
My problems started when i had the HTC in my jacket pocket, a VERY rainy day, so the phone was moist OBS not wet. Thats what i beleive ghappened to my phone.
And now i can not find the purchase receipt to the phone
It might be entirely unrelated, but the screen on my THD also had the same problems immediately after a few flights from coast to upcountry 1800m elevation during summer. The system powered up but the display remained off, and no amount of fiddling would switch it on.
The first time it took a few hours and then spontaneously corrected itself. The second time I had to remove the battery for two days, and then all was fine again. Only happened after flights from coast in summer. It hasn't happened again, but then it's winter here in the southern hemisphere.
I suspect condensation, but that's only a guess...
I have the same problem too here in Australia. It started with the screen not turning on but the buttons still work. Then you'll sometimes notice the screen is inverted and upside-down.
I've sent mine in for service. Haven't got it back yet but I understand the motherboard needs to be replaced.
In short, this is definitely a hardware problem and if you look around the discussions on the net, this is slowly becoming quite a common problem with HD.
forumx said:
I have the same problem too here in Australia. It started with the screen not turning on but the buttons still work. Then you'll sometimes notice the screen is inverted and upside-down.
I've sent mine in for service. Haven't got it back yet but I understand the motherboard needs to be replaced.
In short, this is definitely a hardware problem and if you look around the discussions on the net, this is slowly becoming quite a common problem with HD.
Click to expand...
Click to collapse
Yes exactly, I have had the upside down screen too! Well at the very least it is good to know that people are experiencing this problem other than me. I love this phone so I will have to pay to for the repair. If anyone here has any idea or estimate of what this will cost, please share this here.
The problem for me was the moist, after three days it started to react again... And now it seems to be working...
I guess the air up in the mountains are moist... maybe...
AddeBC said:
The problem for me was the moist, after three days it started to react again... And now it seems to be working...
I guess the air up in the mountains are moist... maybe...
Click to expand...
Click to collapse
So then that's two people so far (including AFW from the first page) who have said that after some situations involving moisture have passed, things are back in working order. I hope for the same to happen soon.
so it is due mainly to wateR?
leobox1 said:
so it is due mainly to wateR?
Click to expand...
Click to collapse
I doubt it is related to water. My device never gets near water or moisture and still experience this problem. I do wonder if it is heat related as the device can get quite hot during charging and perhaps cause the motherboard to play up after a while.
btw, does any of you use some sort of plastic/silicone cover. I wonder whether this type of cover blocks the heat from dispersing.
As i understand it, so far only people who have flashed a different ROM (and with it maybe radios) to their device. If it's a heat issue it could be something to do with the radio version. I have tried different radios and there was one in particular that heated my phone up like crazy while i was listening to music without the screen on (but i don't recall which one it was).
I only used stock rom and never flash my device and still have problem...
forumx said:
I doubt it is related to water. My device never gets near water or moisture and still experience this problem. I do wonder if it is heat related as the device can get quite hot during charging and perhaps cause the motherboard to play up after a while.
btw, does any of you use some sort of plastic/silicone cover. I wonder whether this type of cover blocks the heat from dispersing.
Click to expand...
Click to collapse
I do not have any type of cover on mine.
I agree with the possibility of it being a heat issue though.
Very perplexing. This past weekend I again travelled from Joburg to the coast (from 1800m elevation to sea level), and again the THD screen stopped responding to input whilst at the coast. I desperately fiddled, reflashed, hard reset at least 10 times to see if I could get the screen to work, but it always booted up locked, and no amount of fiddling would do anything. I even put the thing on an oil heater for a few hours, hoping that if condensation was the culprit (my current theory) then a goodly dose of heat would at least evaporate any moisture, and once, for about a minute the screen responded, and then again went dead to touch. I had to use another phone all weekend. This evening, on returning to Joburg, I resolved to get another device, maybe the Diamond 2. After a few hours back home I retrieved the THD, put in the SIM and, lo and behold, it worked fine. This is most vexing, but I fear the THD will have to go -- I just can't live with this unreliability. Sad, really, because I love the big display, I love the fact that guys like Throy are cooking good ROMs. In many ways the THD is about the best out there, at least for my needs. But that &@&* thing has to be reliable.
Hi,
After being a long time lurker and benifiting hugely from the XDA community, I've ran into a problem with my Nexus 4 that has led me to create this thread (after having found nothing through searches).
I recently dropped my phone into a pond (clean pure water). I plucked it out quickly, dried it off, removed my SIM and left it to sit in some rice for 48h.
I pulled it out, and it worked just fine. However, as often happens with water damage, I am now, several days later, experiencing some frustrating issues.
When the screen switches off (screen timeout, lock button, proximity sensor during a phone call) I am unable to wake it. The screen is still responsive to touch, as I can unlock the screen and then hit the volume buttons and hear a sound, or if music is playing it will continue to play for example, so the phone isn't off. When in the right light, I can actually see the screen, but it's very very very dim (unusable).
I am rooted + CWM + custom roms / kernels.
What I have tried :
- Changing roms (AOKP, CM)
- Kernels (Franco, stock, CM) to no avail, as well as doing a factory data reset from CWM.
- More rice
- Software stuff, like disabling lock screen, setting brightness to max, using volume to unlock.
What I haven't tried:
Doing a full reset with a factory image (as I'm currently on holidays)
Opening the phone and playing around.
Has anyone experienced similar issues? Any help would be appreciated. Is this just a send back to Google situation?
Many thanks,
Jooci said:
Hi,
After being a long time lurker and benifiting hugely from the XDA community, I've ran into a problem with my Nexus 4 that has led me to create this thread (after having found nothing through searches).
I recently dropped my phone into a pond (clean pure water). I plucked it out quickly, dried it off, removed my SIM and left it to sit in some rice for 48h.
I pulled it out, and it worked just fine. However, as often happens with water damage, I am now, several days later, experiencing some frustrating issues.
When the screen switches off (screen timeout, lock button, proximity sensor during a phone call) I am unable to wake it. The screen is still responsive to touch, as I can unlock the screen and then hit the volume buttons and hear a sound, or if music is playing it will continue to play for example, so the phone isn't off. When in the right light, I can actually see the screen, but it's very very very dim (unusable).
I am rooted + CWM + custom roms / kernels.
What I have tried :
- Changing roms (AOKP, CM)
- Kernels (Franco, stock, CM) to no avail, as well as doing a factory data reset from CWM.
- More rice
- Software stuff, like disabling lock screen, setting brightness to max, using volume to unlock.
What I haven't tried:
Doing a full reset with a factory image (as I'm currently on holidays)
Opening the phone and playing around.
Has anyone experienced similar issues? Any help would be appreciated. Is this just a send back to Google situation?
Many thanks,
Click to expand...
Click to collapse
Your backlight has became faulty. Presumably the circuitry that tells it to turn on when out of standby is damaged, I'd suggest sending it to google as this will be very hard to fix at home without good knowledge of circuitry and good practice with a soldering iron.
Harry GT-S5830 said:
Your backlight has became faulty. Presumably the circuitry that tells it to turn on when out of standby is damaged, I'd suggest sending it to google as this will be very hard to fix at home without good knowledge of circuitry and good practice with a soldering iron.
Click to expand...
Click to collapse
Hi,
Thanks for your response. I was curious as to whether it was a hardware issue or not, seeing as the backlight did work for a few days, and that the backlight does work when I switch the phone on.
I guess this is a send back to Google then... Although I have no idea how much they charge for repairs.
Cheers,
new signs
Harry GT-S5830 said:
Your backlight has became faulty. Presumably the circuitry that tells it to turn on when out of standby is damaged, I'd suggest sending it to google as this will be very hard to fix at home without good knowledge of circuitry and good practice with a soldering iron.
Click to expand...
Click to collapse
The phone is reworking now... from time to time. In the past 3 weeks it's gone totally back to 100% functionnality 3 times, for about 48h total. It seems totally disjointed from what i'm doing (driving, or in a club).
When the phone works properly, the Screen shows up in my battery consumption stats normally ; I have noticed when the backlight is not working (so I'm unable to wake the phone) that the "Screen" does not show up in the battery consumption stats. What could this mean? I'm still tossing up about sending the phone to Google or just selling it for parts and buying a new Nexus. If the phone is sometimes working, does this mean it should be a quick (and cheap) fix? Or will the whole motherboard have to go?
Thanks again
So I'm here in the US, but I'm using the Korean SHV-E300L. About a week ago, my phone fell off my bed and cracked slightly, but the touch screen responded perfectly. However, last night while I was texting, I noticed the screen scrolled a little slower than normal, and I couldn't quite text as fast. Today everything was normal until a few hours ago, where the screen would seem to hang and not respond, and sometimes the notification panel would start to drop, but never fully descend. I went into developer options and turned on "Show touches" and it shows a persistent input in the upper left corner of the screen. Other than replacing the screen, is there anything software related that I can do about this?
jkid218 said:
So I'm here in the US, but I'm using the Korean SHV-E300L. About a week ago, my phone fell off my bed and cracked slightly, but the touch screen responded perfectly. However, last night while I was texting, I noticed the screen scrolled a little slower than normal, and I couldn't quite text as fast. Today everything was normal until a few hours ago, where the screen would seem to hang and not respond, and sometimes the notification panel would start to drop, but never fully descend. I went into developer options and turned on "Show touches" and it shows a persistent input in the upper left corner of the screen. Other than replacing the screen, is there anything software related that I can do about this?
Click to expand...
Click to collapse
Do you have a stock firmware or custom? If you have a custom try re-flashing it if you never had issues with it. The best way to go is if you are on stock firmware soft-reset your phone by holding the power button until it forces power off then turn it back on. If that doesn't fix your issue then your hardware is messed up.
The S4 screen is very sensitive and I hate it sometimes because the smallest air bubble on my device makes the screen go crazy touching all kinda stuff. Good luck!
NYCDianand said:
Do you have a stock firmware or custom? If you have a custom try re-flashing it if you never had issues with it. The best way to go is if you are on stock firmware soft-reset your phone by holding the power button until it forces power off then turn it back on. If that doesn't fix your issue then your hardware is messed up.
The S4 screen is very sensitive and I hate it sometimes because the smallest air bubble on my device makes the screen go crazy touching all kinda stuff. Good luck!
Click to expand...
Click to collapse
Well I literally just rooted it after posting this because I needed to get some files. But it's the stock ROM, firmware, etc.
jkid218 said:
Well I literally just rooted it after posting this because I needed to get some files. But it's the stock ROM, firmware, etc.
Click to expand...
Click to collapse
try doing a soft reset then it should help or at least im hoping so.
It hasn't worked but for some reason when the phone is in landscape it does a bit better. I'll try to do a screencap video
Also, If I just unlock the phone and let it sit, no touches register
I've read a lot about the screen flickering issue, suggestions range from changing options in developer options, removing your SD, squeezing certain parts of the phone, slapping it, replacing the screen etc. I was rooted on lollipop using this method: http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370 and after the root the screen returned to normal for about 20 minutes. Over about a month or so after this the problem got worse, I'd have to press the power button 20 or more times to get the screen to come one and as of 3 days ago I haven't been able to use the phone at all. Today I was messing with it and found that if I reboot the phone holding the power and volume down buttons, the screen flickers and I see the yellow triangle with an exclamation point briefly, and flickers out again until the samsung boot screen, every time I do this, the phone stays on. I have USB stayawake on and if plugged in the phone will stay awake for hours until I push the power button to turn off screen, and then repeat the reboot process. Just in case there was a software issue I upgraded to the latest update by using odin, I'm now on 6.0.1 and the phone was working perfectly for an hour before it returned again. If the issue is the flex/ribbon cable that connects the screen or other hardware issue, I don't see how rebooting would help, but if its a software issue, I don't understand why its only after I turn off the screen. Regardless, even when the phone was working it would still flicker on the lowest brightness, but at least the power button would work. Anyone have any ideas?
I've been in this type of your situation believe me all those solutions you mentioned above non of them really work, infact i nearly got my phone twisted because of one stupid yellow flickers. As of now the only perfectly working solution according to my extensive research is first of all never put it in auto brightness, you can reduce the brightness to a minimum, this happens on many samsung devices like s4,note 3 and even some s6 due to the amoled screens you'll notice when you reduce your brightness to the lowest it start immediately. I only got one report on this same issue damaging a s5 but it rear so dont be scared of loosing your phone. I'll upload a sreenshot of my minimum brightness to give an ldea.
nura380 said:
I've been in this type of your situation believe me all those solutions you mentioned above non of them really work, infact i nearly got my phone twisted because of one stupid yellow flickers. As of now the only perfectly working solution according to my extensive research is first of all never put it in auto brightness, you can reduce the brightness to a minimum, this happens on many samsung devices like s4,note 3 and even some s6 due to the amoled screens you'll notice when you reduce your brightness to the lowest it start immediately. I only got one report on this same issue damaging a s5 but it rear so dont be scared of loosing your phone. I'll upload a sreenshot of my minimum brightness to give an ldea.
Click to expand...
Click to collapse
The not using auto brightness does stop the screen from flickering so if I have to turn it down, I turn it down to just below where it starts happening but I still have the issue of the screen not coming on with the power button consistently, it flashes on for a second then back off, not nearly long enough for me to unlock the phone, except for when I restart it using power+vol down
EDIT: I see now this probably should've gone in the help and troubleshooting sub-forum, if any mod sees this, please move it for me.
It worked perfectly for me except your is getting worse by the week. Never mind i just got a new way may be it'll work on your phone, move your brightness tray to the highest or at the middle, keep using it as normal for every day use for at least a week. It worked for my indian friend as he told me. Keep in touch.
nura380 said:
It worked perfectly for me except your is getting worse by the week. Never mind i just got a new way may be it'll work on your phone, move your brightness tray to the highest or at the middle, keep using it as normal for every day use for at least a week. It worked for my indian friend as he told me. Keep in touch.
Click to expand...
Click to collapse
The first day it didn't seem to make a difference but I didn't check on it a lot, after that I've checked a few times and it does seem to make a difference it comes on much more frequently now, almost every time, but what could be the cause of the issue then? When I thought it was the ribbon cable connecting the screen I wasn't opposed to replacing it if I have to, but now I'm not sure how to go about fixing this or if I even can other than just leaving brightness up
Just to update, keeping it on max brightness did a lot to solve the issues, but it was still under warranty through Samsung so I sent it in, its on its way back, but according to the report they replaced the LCD
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?