Hi there,
I migrated to LOS two weeks ago and I'm fairly happy with it. It runs really smoothly, however I think I have found a bug. From time to time when I wake up my phone it just shows the clock (with the correct time) on a blue tile. The phone seems to still be working as I can use the flashlight (by pressing and holding the pwr button when in sleepmode), but no matter what I do, I can't do anything useful. I'm stuck on that screen.
I haven't found out what causes this strange behavior.
All I can do is remove the battery and reboot.
Has anyone else come across this phenomenon and knows more than I do?
[Edit:]
Can't post the picture, as I don't have enough posts yet
[/Edit:]
Cheers
johntwenty
Update:
I had to go back to CM as the phone function didn't work.
I do like LOS 14.1 a lot, however all the features are of little use if people at the other hand can't hear me
So much for now. I'll probably try LOS again at a later time, when more of the issues are fixed.
Thanx
johntwenty
Alright,
I've gone back to LOS 14.1. and installed the most recent nightly build lineage-14.1-20170315-nightly-klte-signed.zip.
The phenomenon described above is still present, however, I noticed that if I hit the back button within one or two seconds, my phone will get back to normal. If I wait longer, there is no way to recover without removing the battery.
I hope that this information might help.
Cheers
johntwenty
Yes. Experiencing exactly this. sm-g900v, may 24th Klte.
It was one of the reasons why I've stopped using LOS.
I've read somewhere that you need to disable S-View Cover somewhere in the settings to get rid of this bug.
It was after reflashing to TW ROM, so I haven't tested this solution.
Thanks for feedback. via Google determined s view is flip cover. Completely disabled...see if it continues.
Yes, it's a special Samsung cover which I've never used.
I think that the phone should respond to its magnet.
Since I have no this cover, the phone could be "misled" by a magnet in my bag or something.
Haha...believe may have put it together. Have carried ecig (joytech vtc mini) along with phone in same hand with them touching each other. VTC mini has 2 small strong magnets on 18650 battery cover. It's only occurred half dozen times since using Lineage this last month and has not locked up lock screen since disabling flip cover.
Just one more reason not to smoke :lol
Hi All ,
Where is this S-view cover disable on Galaxy Note 3 please ?
Thanks for info 'flip cover' on setting disabled.
Just want to add that I had this problem again yesterday, after a long while, with Lineage 14.1-20171214-NIGHTLY-klte. Left it like this overnight, same in the morning.
I noticed that many things still work: bluetooth auto connects, sounds are played. Probably everything works except one cannot use the screen.
Connecting adb works, changing screen resolution changes the form of that color rectangle but doesn't help. Reboot via adb works (and I think the force reboot via Power+VolDown also works).
Hiano said:
Just want to add that I had this problem again yesterday, after a long while, with Lineage 14.1-20171214-NIGHTLY-klte. Left it like this overnight, same in the morning.
I noticed that many things still work: bluetooth auto connects, sounds are played. Probably everything works except one cannot use the screen.
Connecting adb works, changing screen resolution changes the form of that color rectangle but doesn't help. Reboot via adb works (and I think the force reboot via Power+VolDown also works).
Click to expand...
Click to collapse
I've had this issue today but noticed I had the S-View-Cover Option enabled. How about you?
bbsc said:
It was one of the reasons why I've stopped using LOS.
I've read somewhere that you need to disable S-View Cover somewhere in the settings to get rid of this bug.
It was after reflashing to TW ROM, so I haven't tested this solution.
Click to expand...
Click to collapse
Thank you so much for this info. Got the exact same problem on my HTC10 and turning the setting completely off in the settings solved it. I think the reed contact in my phone must be broken or sth... but at least I don't have to restart my phone every time it happens!
Shark5060 said:
Thank you so much for this info. Got the exact same problem on my HTC10 and turning the setting completely off in the settings solved it. I think the reed contact in my phone must be broken or sth... but at least I don't have to restart my phone every time it happens!
Click to expand...
Click to collapse
Me too! Galaxy S5.
Thanks for tips. I've just use neodymium magnet. I've moved on phone back and Android is usable again without rebooting!
I don't know why sometime phone thinks that cover is used. To many magnetic fields around?
Hi guys, I'm having the same problem with a Note 3 N9005. I installed TWRP 3.2.2.0 and then LineageOS 14.1. After booting the device I see for a second "next" , but the screen jumps too quickly to a blue tile with time and date. There it stucks. I got an ORIGINAL SAMSUNG flip-cover (the one with magnets, cover closed-> screen is off), but even with this thing installed it doesn't work. Same thing happens, blue tile and no responding to the flip cover at all. Disable S-view cover is not an option, as i can't get into the phone's OS at all.
How do i get into the phone's OS and settings? Does the trick with the magnet work for somebody?
Please, explain clearly how you got around this issue. Thanks in advance!
thaineth said:
Hi guys, I'm having the same problem with a Note 3 N9005. I installed TWRP 3.2.2.0 and then LineageOS 14.1. After booting the device I see for a second "next" , but the screen jumps too quickly to a blue tile with time and date. There it stucks. I got an ORIGINAL SAMSUNG flip-cover (the one with magnets, cover closed-> screen is off), but even with this thing installed it doesn't work. Same thing happens, blue tile and no responding to the flip cover at all. Disable S-view cover is not an option, as i can't get into the phone's OS at all.
How do i get into the phone's OS and settings? Does the trick with the magnet work for somebody?
Please, explain clearly how you got around this issue. Thanks in advance!
Click to expand...
Click to collapse
I always delete Flipflap as one of the first things I do on a fresh install. It seems to always act up for me. The trick with the magnet is to pass it across the screen in the area above the recents key, that should trip the smart cover off, then you can disable it in options, or remove the app completely if you have root.
EDIT: Sorry, just noticed you have a Note 3, these instructions are for s5, magnetic sensor may be in different spot on note 3
I was struggling to find the setting to turn off the S View cover on LineageOS 16 on my S5.
Found it in Settings > Connected devices > Connection preferences > Smart Cover
Turn it off via the toggle at the top!
We'll see how it goes! Thanks!
This is also apparently just bad design in Lineageos
for the S5 or whatever layer of software/firmware controls this, as this Blue Screen of Death disables power-button NMI forced reboots: if this happens on a fixed-battery phone, you get to wait until it goes flat, which is why I'll stick with the S5 forever.
Following the instructions, I found and disabled Smart Cover in Connection Preferences (many thanks to whoever figured this out); apparently Lineageos 16 ships with this enabled (bad design). I'd never even heard of a Smart Cover or knew the phone had a magnet gimmick like the tablets do.
One principle of software design which is not widely appreciated is that doing too much is often worse than not doing enough.
Related
So Yesterday for no reason at all my 8525's screen went white. i thought it had frozen or some thing but it didn't snap out of it. I pressed the ok button on the side and could hear noise. I decided to restart. Nothing. Did this like 7 times. Finally I let it sit without the battery for like an hour. I worked but the colors were all messed up. Reset and it worked fine. So i set my alarm went to sleep and woke this morning to an email and a white screen. Turning it on and off a couple of times did it and I was already frustrated.
Then I read on a forum about Activesync automatically opening throughout the day to try and connect. So I tweaked that to manual connections. Still the same. So I decided to take advantage of the warranty but I needed to set back my rom b/c as you already know, it voids it. Also thinking that re-flashing might get rid of whatever it was failing in. No, still the same, and now worse. As or an hour ago, my navigation pad doesn't work either. It actually works for about a second when I turn it on and then after I press anything on the pad or surrounding buttons, it's gone.
I really would like to fix it myself at least for now and use the warranty exchange at about 11 months but if theres nothing I can do, I guess I can go get a new one. Also, I don't know if it has anything to do with it, but I downloaded Google Maps to my phone yesterday on the road (through 3G) and that was the only new program installed( I think it mightve been this).
Has this happened to anyone else?
Any help would be much appreciated. I hope I explained enough for anyone to respond. Thank you in advance to anyone with anything really.
Actually if you do a search under white screen you'll find many entries. Any attempt to fix yourself will void the warranty. If you are lucky it may only be the d-pad connector that is loose. This it is possible to check yourself but if have a warranty then I suggesting using it.
Otherwise see the link to my site in my signature for dismantling and service manual guides.
Mike
Thanks. You know I think I will take advantage of the warranty sometime this week. I don't know what happened. But I'm to update my situation. It now seems as though my directional pad seems to be the problem. it glitches on and off and using it sometimes creates the fade-out to white screen. I have to let it go to standby on its own to get my screen back or play around turning it on and off for a bit.
Also, once i re-installed me ATT rom with no applications, my screen seems to be off. I have a 1/32th sliver of the bottom of the screen at the top of my touchscreen. Even in landscape it shows my scroll bar and everything. I didn't even drop it but it is now slightly skewed down. Any input on this?
I also found this website talking about the same problem having with and unorthodox solution (which I tried to no avail). Here's the link if anyone want to check this out. http://www.htcwiki.com/page/AT&T+8525+Display+issues:+Display+is+dim,+blank,+white,+has+lines,+etc.?t=anon
Anyways, I'm gonna call ATT about this see if they can help but I think I will replace, I just didn't want to so soon.
Thanks again for the quick answer.
ckent03 said:
Thanks. You know I think I will take advantage of the warranty sometime this week. I don't know what happened. But I'm to update my situation. It now seems as though my directional pad seems to be the problem. it glitches on and off and using it sometimes creates the fade-out to white screen. I have to let it go to standby on its own to get my screen back or play around turning it on and off for a bit.
Also, once i re-installed me ATT rom with no applications, my screen seems to be off. I have a 1/32th sliver of the bottom of the screen at the top of my touchscreen. Even in landscape it shows my scroll bar and everything. I didn't even drop it but it is now slightly skewed down. Any input on this?
I also found this website talking about the same problem having with and unorthodox solution (which I tried to no avail). Here's the link if anyone want to check this out. http://www.htcwiki.com/page/AT&T+8525+Display+issues:+Display+is+dim,+blank,+white,+has+lines,+etc.?t=anon
Anyways, I'm gonna call ATT about this see if they can help but I think I will replace, I just didn't want to so soon.
Thanks again for the quick answer.
Click to expand...
Click to collapse
Everything they suggest on that site you have tried I guess, the soft and hard resets etc.
I agree with you about the d-pad (directional buttons). Those with this problem often report that the d-pad or it's connector are re;lated to this issue.
Pleased you have chosen the warranty route. You see evn if you opened it up, it can work for a short while and then return again. Also push hard for replacement not repair. They may do this automatically but if not try to persuade them. The reason is that quite a few folks have reported that even after an HTC repair the problem can come back. Actually I think there may be more than one physical cause of this issue and sorting one thing does not mean it won't come back via another route.
The good news is, if you get a good one as I did on the second attempt, I never had white screen or alignment issues - despite heavy use.
Mike
Once again, thank you Mike for all your input. I will be issuing an order for replacement instead of repair. Being at work all day today I've seen that it hasn't "whited' out, if you will, but has actually kept working. Ever so often the d-pad goes but comes back in a few seconds. It may be due to the WM6 i had on it so for now i will keep the original ATT upgrade of WM5 and try to hold off on the warranty as long as I can before it expires. That way I can enjoy a healthy new 8525 longer.
For now I will keep looking around in these forums and see if there ever is a solid solution. Thanks again, and good luck with all.
CKent
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.
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
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
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?