Related
I m facing an awkward problem with my WFS's touch.... It works pretty fine with everything for sometime but after some irregular time, it starts acting erratically and I simply loose the focus on the screen...... the touch buttons automatically start acting until I lock the phone using power button.... As soon as I do so, it works like a charm again after sometime....
Notes:-
1. It doesn't happen in any particular ROM.
2. It doesn't happen in any particular apps.
3. It doesn't happen in any particular time interval, it just happens, sometimes after 10 seconds only, and sometimes not even for half an hour continuously.... (I was watching a movie on phone on mxplayer.... It worked pretty fine for about 45 minutes, and all of sudden, the touch closed the movie....... I turnt the screen off and then again came back, then it happened again within 10 to 20 seconds continuously for about 10 times so I got pissed off and kept the mobile aside.......)
4. I have tried almost everything out there related to touch fixes for WFS, like unlock freeze problem solutions etc, but neither of them happens to work in my case.....
5. I just have a hunch that its moisture problem.... I guessed, that when I use my phone's screen continuously, it works like a charm like earlier, but when the screen gets heated up ,it starts reacting erratically......
If anyone has any solution of at least knows the accurate problem, I wold b really thankful to them...........
I have tried using different ROMs, Kernels etc...........
nikhilkaushik said:
I m facing an awkward problem with my WFS's touch.... It works pretty fine with everything for sometime but after some irregular time, it starts acting erratically and I simply loose the focus on the screen...... the touch buttons automatically start acting until I lock the phone using power button.... As soon as I do so, it works like a charm again after sometime....
Notes:-
1. It doesn't happen in any particular ROM.
2. It doesn't happen in any particular apps.
3. It doesn't happen in any particular time interval, it just happens, sometimes after 10 seconds only, and sometimes not even for half an hour continuously.... (I was watching a movie on phone on mxplayer.... It worked pretty fine for about 45 minutes, and all of sudden, the touch closed the movie....... I turnt the screen off and then again came back, then it happened again within 10 to 20 seconds continuously for about 10 times so I got pissed off and kept the mobile aside.......)
4. I have tried almost everything out there related to touch fixes for WFS, like unlock freeze problem solutions etc, but neither of them happens to work in my case.....
5. I just have a hunch that its moisture problem.... I guessed, that when I use my phone's screen continuously, it works like a charm like earlier, but when the screen gets heated up ,it starts reacting erratically......
If anyone has any solution of at least knows the accurate problem, I wold b really thankful to them...........
I have tried using different ROMs, Kernels etc...........
Click to expand...
Click to collapse
What if i told you there is a perfectly working forum for questions?
POST IN THE RIGHT FORUM PLEASE.
sukhjit321 said:
What if i told you there is a perfectly working forum for questions?
POST IN THE RIGHT FORUM PLEASE.
Click to expand...
Click to collapse
And what if I told u that I already did and when no one answered, to get this question raised to the right people I had to ask it here.........
No offense, but this problem of mine is making me mad cos sometimes my phone becomes unusable for sometime.... No disrespect to the forum rules.... Nor to you or anyone.... But I need at least a proper hint about the problem.... If you wanna delete this thread thinking that I have violated the rules, then sure, be my guest....
nikhilkaushik said:
And what if I told u that I already did and when no one answered, to get this question raised to the right people I had to ask it here.........
No offense, but this problem of mine is making me mad cos sometimes my phone becomes unusable for sometime.... No disrespect to the forum rules.... Nor to you or anyone.... But I need at least a proper hint about the problem.... If you wanna delete this thread thinking that I have violated the rules, then sure, be my guest....
Click to expand...
Click to collapse
So what? Just bump the topic. There is a proper place for posts.
YOU had a question. Hence the post should be in Q&A forum. As simple as that.
If noone replied that's because maybe no one knows any solution.
nikhilkaushik said:
I m facing an awkward problem with my WFS's touch.... It works pretty fine with everything for sometime but after some irregular time, it starts acting erratically and I simply loose the focus on the screen...... the touch buttons automatically start acting until I lock the phone using power button.... As soon as I do so, it works like a charm again after sometime....
Notes:-
1. It doesn't happen in any particular ROM.
2. It doesn't happen in any particular apps.
3. It doesn't happen in any particular time interval, it just happens, sometimes after 10 seconds only, and sometimes not even for half an hour continuously.... (I was watching a movie on phone on mxplayer.... It worked pretty fine for about 45 minutes, and all of sudden, the touch closed the movie....... I turnt the screen off and then again came back, then it happened again within 10 to 20 seconds continuously for about 10 times so I got pissed off and kept the mobile aside.......)
4. I have tried almost everything out there related to touch fixes for WFS, like unlock freeze problem solutions etc, but neither of them happens to work in my case.....
5. I just have a hunch that its moisture problem.... I guessed, that when I use my phone's screen continuously, it works like a charm like earlier, but when the screen gets heated up ,it starts reacting erratically......
If anyone has any solution of at least knows the accurate problem, I wold b really thankful to them...........
I have tried using different ROMs, Kernels etc...........
Click to expand...
Click to collapse
I'm having same problem...
Some guys from forum suggested that it may be caused by using non-HTC charger or damaged charger...But my problem has not resolved after changing charger...
Do you have any other suggestion?
Sorry everyone, my apologies for breaking the rules.....
Solution
I went to HTC customer service center and they just saw the problem and said they'd require to update the touchscreen firmware.... I asked them to do it, so they asked me for some time to get it from other service center.... They said it'd flash everything, but as of now I'm not sure whether they're right or wrong, but I'm waiting for them to get the card....
Apologies again to everyone for opening a wrong topic.... I request the mods to remove this thread....
Problem: Cannot turn on the screen by pressing the power button sometimes. The screen is black or very dim, I cannot tell. One can see nothing on the screen, and it doesn’t accept any touch input, either. The phone still rings if there’s an incoming call. If this happens, the following several presses (about 10 - 20) on the power button will probably lead to a reboot. The “screen auto-rotate” and the proximity sensor may fail after the reboot, but will recover after a manual reboot.
Frequency: Fewer with higher Rom version. About once per day for 4.3.
Other description:
The problem frequently happens when I just take the phone outside my house/office, and seldom happens when the phone just stays somewhere.
The problem seems to be irrelevant to the remaining battery capacity or the uptime, but it never happens when charging.
The problem seems to be irrelevant to the Apps installed.
The problem seldom happens in the first 3-4 days after flashing a Rom, but happens more and more frequently as time goes by. My guess is some cache is stuffed by some trash, which causes the problem. The phone may be fine as long as the trash can be cleaned up on a regular basis.
I manually reboot my phone at most every two days.
Solutions tried, but don’t work
Flashing official ROMs 4.0.4, 4.1.1, 4.1.2, 4.2.2 and 4.3 following the procedure “adb reboot bootloader; fastboot oem unlock; flash-all; fastboot oem lock”, without google wallet, not rooted.
Turning off the auto-brightness control, as suggested by some post on the Internet.
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Thymo said:
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Bobby_yan said:
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Click to expand...
Click to collapse
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Thymo said:
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Click to expand...
Click to collapse
No.
No, I just tried the official ROMs. Any suggestion?
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
eKeith said:
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
Click to expand...
Click to collapse
Thanks a lot. I'm trying it.
Bobby_yan said:
Thanks a lot. I'm trying it.
Click to expand...
Click to collapse
LagFix does NOT help in my case. Any other suggestions? Thanks.
I've also had this blank screen with calls still ring issue for as long as I can remember, nearly 2.5 yrs.
I've always suspected it's my ROM and so I'd try out another ROM'S, BUT no other ROM works like how I'd like, so I always come back to my ROM.
It doesn't happen every single day, but it does happen very often.
I've tried using apps that auto reboot daily, but eventually this blank screen issue will return.
Unfortunately I can't seem to find any solution, so I just put up with it, it's like the 1 only flaw with my ROM.
&
Not to be at all rude, but I'm really glad op has had this issue from testing other versions of Android, cause then at least I know I don't need to give up my great tablet mode ROM.
LOL
I think I've finally found a work around for this screen of death.
Using Exposed, download/install this module/extension:
Disable Proximity
http://repo.xposed.info/module/com.mrchandler.disableprox
It does exactly what it's name is and ever since then I've not once had to remove my GN battery to work again because the screen went completely dead.
NVM
Screen still goes dead.
Anyone find an actual fix to this?
isajoo,
I had pretty much the same problems with my Galaxy Nexus running CyanogenMod 11 M12.
It got better by doing the following :
Blowing dry air in the earpiece… though the proximity sensor is clearly beside it. Can't do any harm though, I guess.
Settings/Applications/All/menu/Reset applications preferences (or whatever that's called in english) : that seemed to do a lot of good to my phone ! However, it's a very unsatisfactory answer on a technical point of view, as I still don't know WHAT was precisely needed. It's a "magic wand" solution for which I can't give an explanation.
Not specifically related, but greatly helped my phone in the responsiveness area : Trimmer (fstrim) (https://play.google.com/store/apps/details?id=com.fifthelement.trimmer), an updated version of LagFix that you may already know
Hope that helped !
(I wanted to try http://www.androidlegend.com/how-to-perform-proximity-sensor-calibration-on-any-samsung-phone/ as well, but apparently, /sys/class/sensors/proximity_sensor/prox_cal does not exist on my phone…)
I took the plunge to Android 7.0 Nougat, however I am having some major problems. Initially I had everything stock, and every once in a while my phone would reboot when on WiFi. Sometimes it rebooted within 5 minutes of booting back up, sometimes it would reboot 1 hour after booting back up. There is a whole thread about it here (note: not the bootloop issue occasionally talked about in that thread, although it could be related I guess): https://productforums.google.com/forum/#!topic/nexus/kaMOvuf093Q
I was wondering if anyone else has run into this issue? It definitely seems to be linked to WiFi only. A bunch of users apparently narrowed down a few apps that triggered the reboots more frequently (Napster, for example), but the problem seems deeper than just a rogue app. Safe mode does seem to alleviate the issue, but this is not really an acceptable solutions to me. I tried another kernel (Franco's), but that didn't fix anything. I was wondering if anyone who had this problem had any success fixing it by changing ROMs or kernels? I also read that turning off WiFi scanning may also help--I will report back if this fixes anything.
Any suggestions welcome, thanks!
This could be part of the hardware issue that is happening, it talented to me and I finally have my phone back
Sent from my Nexus 5X using Tapatalk
Which Model of LG 5X?
Do you have H-790 or H-791 Model?
Cheesejam said:
I took the plunge to Android 7.0 Nougat, however I am having some major problems. Initially I had everything stock, and every once in a while my phone would reboot when on WiFi. Sometimes it rebooted within 5 minutes of booting back up, sometimes it would reboot 1 hour after booting back up. There is a whole thread about it here (note: not the bootloop issue occasionally talked about in that thread, although it could be related I guess): https://productforums.google.com/forum/#!topic/nexus/kaMOvuf093Q
I was wondering if anyone else has run into this issue? It definitely seems to be linked to WiFi only. A bunch of users apparently narrowed down a few apps that triggered the reboots more frequently (Napster, for example), but the problem seems deeper than just a rogue app. Safe mode does seem to alleviate the issue, but this is not really an acceptable solutions to me. I tried another kernel (Franco's), but that didn't fix anything. I was wondering if anyone who had this problem had any success fixing it by changing ROMs or kernels? I also read that turning off WiFi scanning may also help--I will report back if this fixes anything.
Any suggestions welcome, thanks!
Click to expand...
Click to collapse
sorry my bad, wrong thread
ashokabs said:
Do you have H-790 or H-791 Model?
Click to expand...
Click to collapse
I have a H-790 Nexus 5x on Verizon.
has been happening to me too -- reboots randomly about once or twice a day. (only realize it since fingerprint scanner does not work and i am forced to key my passcode at first login post reboot).
It seems that the H 790 production series are faulty
Nexus 5x reboot problems
Yes it would appear so. However, I have read one post in Google Forums that speaks of problems with H791. However, it could be related to the wifi problem. There are two problems - one is problem booting initially and finally phone does not boot into the ROM and cannot be recovered. This seems to be related to hardware problem in H-790 series. The other has been isolated to the WiFi scanning which causes a crash.
giannism13 said:
It seems that the H 790 production series are faulty
Click to expand...
Click to collapse
Yeah, I am definitely having a problem with the WiFi crash. Would a custom kernel fix this? A custom ROM would, right? Any ideas for a fix for this?
ashokabs said:
Yes it would appear so. However, I have read one post in Google Forums that speaks of problems with H791. However, it could be related to the wifi problem. There are two problems - one is problem booting initially and finally phone does not boot into the ROM and cannot be recovered. This seems to be related to hardware problem in H-790 series. The other has been isolated to the WiFi scanning which causes a crash.
Click to expand...
Click to collapse
I have read the same too, but he's the only one among the hundrends of h790 users who have the same problem.
Cheesejam said:
Yeah, I am definitely having a problem with the WiFi crash. Would a custom kernel fix this? A custom ROM would, right? Any ideas for a fix for this?
Click to expand...
Click to collapse
You could try too, but I doubt it will fix anything. Its a hardware problem
giannism13 said:
I have read the same too, but he's the only one among the hundrends of h790 users who have the same problem.
You could try too, but I doubt it will fix anything. Its a hardware problem
Click to expand...
Click to collapse
I thought the bootloop issue was hardware related, but not the random reboots issue? Ex: Safe mode fixes the problem for me.
ashokabs said:
There are two problems - one is problem booting initially and finally phone does not boot into the ROM and cannot be recovered. This seems to be related to hardware problem in H-790 series.
Click to expand...
Click to collapse
IMO opinion this is just the eMMC dying problem that people have reportedly sporadically over the past 12mo. That problem has affected both H790 and H791. It likely just became more likely to show up after the 7.0 update because that was a large update, but by no means is a large update going to cause the problem by itself. The core problem is eMMC that was waiting to fail and could have happened just when web browsing but a large update just pushed it over the edge. Some phones you can do many large updates and never see a problem, then boom, one day randomly it just reboots and bootloops, with no amount of flashing or resetting making any difference.
Cheesejam said:
I thought the bootloop issue was hardware related, but not the random reboots issue? Ex: Safe mode fixes the problem for me.
Click to expand...
Click to collapse
If safe mode fixes the problem, then I was wrong. Try to find which app conflicts with the system and uninstall it
giannism13 said:
If safe mode fixes the problem, then I was wrong. Try to find which app conflicts with the system and uninstall it
Click to expand...
Click to collapse
I really wish Google would fix this, this isn't really an acceptable solution to me. :/
I have a h790 nexus 5x and haven't seen this issue, knock on wood. However if it's linked to wifi scanning that was issued in another post you may try disabling wifi scanning to see if the issue is resolved. If not it's definitely the emmc in my opinion
Sent from my Nexus 5X using XDA-Developers mobile app
Cheesejam said:
I really wish Google would fix this, this isn't really an acceptable solution to me. :/
Click to expand...
Click to collapse
If it is indeed not a a hardware problem, then don't wait for Google to fix it overnight. Besides, it may be the case that there is no bug at all, and you flashed a corrupted firmware. Your Best bet right now is to try some custom Roms and kernels and see if it fixes the problem. If you don't want to mess with user made firmware then I would suggest you to reflash the latest stock image form Google. If both of the above fail, the you are forced to roll back to marshmallow
You can try to disable wifi scanner on sleep,.
After the Nougat upgrade, I was having random reboots on my 5X (LG-H791). It always happened when my 5X was sleeping (laying on my working desk or on my bedside table for some time). After the reboot it was working fine again for some hours, so it does not seem to be the bootloop issue. I remember that I had a few rare reboots after upgrading to Nougat 7.0, but after the last 7.1.1 upgrade the reboots occured at least every second day.
Last Friday I had enough of it. I downgraded to the last stock Marshmallow 6.0.1 (MTC20K), and it didn't crash a single time after that.
My wife's 5X is having the same random reboots. The reboots are less frequent (but still occur) when WLAN is turned off. I will downgrade her's too, if my 5X is still still stable after the next weekend.
I wonder if this is a different problem, or if this is just a first symptom of the bootloop issue. If it's a bug in Nougat, then shouldn't much more (if not all) 5X owners experience these random reboots?
Cheesejam said:
I took the plunge to Android 7.0 Nougat, however I am having some major problems. Initially I had everything stock, and every once in a while my phone would reboot when on WiFi. Sometimes it rebooted within 5 minutes of booting back up, sometimes it would reboot 1 hour after booting back up. There is a whole thread about it here (note: not the bootloop issue occasionally talked about in that thread, although it could be related I guess):
I was wondering if anyone else has run into this issue? It definitely seems to be linked to WiFi only. A bunch of users apparently narrowed down a few apps that triggered the reboots more frequently (Napster, for example), but the problem seems deeper than just a rogue app. Safe mode does seem to alleviate the issue, but this is not really an acceptable solutions to me. I tried another kernel (Franco's), but that didn't fix anything. I was wondering if anyone who had this problem had any success fixing it by changing ROMs or kernels? I also read that turning off WiFi scanning may also help--I will report back if this fixes anything.
Any suggestions welcome, thanks!
Click to expand...
Click to collapse
hi, i had the exact same problem with my nexus 5x from carphonewarehouse (uk), and when it was given in to repair i was promised money in return, however they ended up refusing to give money and gave a replacement phone instead, the only way to fix this issue is apparently to get a replacement, as it is most likely a hardware issue google haven't accounted for
I've had the random restart issue for a while now. I got a "new" replacement in November for a different issue and have been on 7.0 the whole time (until last week when I got 7.1.1 OTA). I'm going to call today about another replacement. I've just had two restarts in the last hour.
Hi, I was wondering if anyone else had similar issue. I have been using android smartphones for years now and since always I've been using custom roms. But never actually happen to get issue like this on Lenovo P2.
Problem description:
When device is unlocked. After some time the screen is ON it starts touching by itself at the middle of the screen.
Always the same spot. It doesn't matter if I'm using my phone at that moment or not, touchscreen can touch itself while I'm using it and it interrupts my usage.
I am not using any modifications. Only lineage root is installed. The problem started after installing Lineage OS official build, one of the first 5 builds, and continues to happen till now.
Here are the videos showing how does it look like.
https://youtu.be/5vR83OoGOFg
https://youtu.be/i0eLwmBvCI8
lozohcum said:
Hi, I was wondering if anyone else had similar issue. I have been using android smartphones for years now and since always I've been using custom roms. But never actually happen to get issue like this on Lenovo P2.
Problem description:
When device is unlocked. After some time the screen is ON it starts touching by itself at the middle of the screen.
Always the same spot. It doesn't matter if I'm using my phone at that moment or not, touchscreen can touch itself while I'm using it and it interrupts my usage.
I am not using any modifications. Only lineage root is installed. The problem started after installing Lineage OS official build, one of the first 5 builds, and continues to happen till now.
Here are the videos showing how does it look like.
Click to expand...
Click to collapse
Try stock ROM again, if it still happens, your display has a hardware issue
i got that same problem
i have that same problem, and seems be software why dont have sense this, i do it nothing, someone help me? i already flash stock and same still
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
You most likely got a bad part. OEM like One plus and xioami are known for using something called product binning. Which means their parts have a higher failure rate then other oems. They also dont make extra parts really so what you got was most likely just a generic screen like you can buy at any shop in China.
Nothing you can really do about it except try a different screen but to be honest I would get a different device and this time dont skip on the price. You get what you pay for and when a good device is cheap there is always a reason. (why do you think most of the owners and mods of XDA run Iphones as their daily drivers and leave android for a hobby)
gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
As an experiment, try stock OOS and see whether the issue goes away.
i too have this problem cant find any solution anywhere been trying for about a week now arrggghh
ireaper4592 said:
i too have this problem cant find any solution anywhere been trying for about a week now arrggghh
Click to expand...
Click to collapse
tnsmani said:
As an experiment, try stock OOS and see whether the issue goes away.
Click to expand...
Click to collapse
Hey there again. I know my answer is kinda late but I wanted to share my experience. So I tried like 10 different custom ROMs with different Android version. The problem got even worse sometimes.
Anyway a few days ago I installed stock OOS and the problem is fixed now. I could not believe at first, but after excessive testing I am 100% sure now.
Anyone can tell why? Is the stock display driver proprietary?
TBH I always used to use custom ROMs (mostly CyanogenMod and now Lineage. Now on stock rom O feel like everything is better than ever before. Battery life, performance. Some features even offer more customization than custom ROMs.
I always thought the opposite is the case since custom roms advertise things like this. I will definitely stick with stock rom for now!
gt-kingz said:
Hey there again. I know my answer is kinda late but I wanted to share my experience. So I tried like 10 different custom ROMs with different Android version. The problem got even worse sometimes.
Anyway a few days ago I installed stock OOS and the problem is fixed now. I could not believe at first, but after excessive testing I am 100% sure now.
Anyone can tell why? Is the stock display driver proprietary?
TBH I always used to use custom ROMs (mostly CyanogenMod and now Lineage. Now on stock rom O feel like everything is better than ever before. Battery life, performance. Some features even offer more customization than custom ROMs.
I always thought the opposite is the case since custom roms advertise things like this. I will definitely stick with stock rom for now!
Click to expand...
Click to collapse
Thanks for the confirmation. The cheaper screens seem to have an issue which is not faced by the costlier ones. I have found while roaming the threads that sometimes flashing OOS helps. May be a driver issue.
My understanding from what I've read, third party displays needed kernel support.
I paid OP to replace mine - no problems.
Hi!
I'm having a similar issue with my Oneplus 5. Had my screen replaced (new one: OEM) and now it doesn't wake up most of the time either using power button or double tap or fingerprint scanner. I tried everything that I read on forums but nothing worked. Now I seem to have found a solution that I haven't read anywhere yet: I turned off night mode and now it's working as it should. Actually, whenever I want to use any screen adjustment feature like night mode, reading mode etc the screen doesn't wake up. But if I keep the default settings, there is no problem. The issue is definitely the new screen because before that I used night mode all the time (I mean after dark). Now I'm still thinking if I should return the phone to the repair shop and ask for another screen (they offer one year warranty after the repair) or just deal with it... I mean these OEM screen are cheap for a reason (as someone had written here before) and there is no guarantee that the next one will be good, and I don't feel like waiting weeks again for an uncertain outcome, also I can live without said features (gonna miss night mode tho'). Any suggestion? Should I give it a try? Maybe the repair shop made a mistake during assembly? Anyway, I hope this comment will be helpful for those lurking for a solution for a similar problem.
csabatoro said:
Hi!
I'm having a similar issue with my Oneplus 5. Had my screen replaced (new one: OEM) and now it doesn't wake up most of the time either using power button or double tap or fingerprint scanner. I tried everything that I read on forums but nothing worked. Now I seem to have found a solution that I haven't read anywhere yet: I turned off night mode and now it's working as it should. Actually, whenever I want to use any screen adjustment feature like night mode, reading mode etc the screen doesn't wake up. But if I keep the default settings, there is no problem. The issue is definitely the new screen because before that I used night mode all the time (I mean after dark). Now I'm still thinking if I should return the phone to the repair shop and ask for another screen (they offer one year warranty after the repair) or just deal with it... I mean these OEM screen are cheap for a reason (as someone had written here before) and there is no guarantee that the next one will be good, and I don't feel like waiting weeks again for an uncertain outcome, also I can live without said features (gonna miss night mode tho'). Any suggestion? Should I give it a try? Maybe the repair shop made a mistake during assembly? Anyway, I hope this comment will be helpful for those lurking for a solution for a similar problem.
Click to expand...
Click to collapse
Did you try OOS?
OEM screen is not cheap (atleast compared to what is offerred online).
May be you are better off with what you have since you have found a work around. Who knows what you will get next time?
Yea I have same problem it works totally fine on oos but on custom roms it is ****ed up
skymera said:
My understanding from what I've read, third party displays needed kernel support.
I paid OP to replace mine - no problems.
Click to expand...
Click to collapse
How much plz?
Shreeram02 said:
Yea I have same problem it works totally fine on oos but on custom roms it is ****ed up
Click to expand...
Click to collapse
Thank you also for confirming that on OOS there is no issue. Looks like the cheaper of the online replacements have this issue while the costlier ones don't.
Funniest thing is I have a slim ROM backup on 7.1. and that works fine so like what the f--- any ideas people?
gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
Yes, I have the same issue and I wanted to revert back to Stock OOS, but I just tried Caesium latest kernel, and the display wakeup issue seems to have gone. I'm using Havoc OS 2.3 based on Android Pie.
Guys the latest mad kernal reborn it wakes up all the time
At least for my screen
It used to be worse on all the other kernals
Finally found a solution
I had same problem on custom roms after replacement of display of my oneplus3...i was on oos 5.0.8 i had no issues in that but am a custom rom user and now the solution is flash any rom clean flash not dirty flash and flash gapps then flash any module if you want like magisk and then reboot setup the device and after first boot flash mcd custom kernel and yippeee enjoy... Present am on havoc os with no issues... Try and let me know...
Mohammed Raihan said:
I had same problem on custom roms after replacement of display of my oneplus3...i was on oos 5.0.8 i had no issues in that but am a custom rom user and now the solution is flash any rom clean flash not dirty flash and flash gapps then flash any module if you want like magisk and then reboot setup the device and after first boot flash mcd custom kernel and yippeee enjoy... Present am on havoc os with no issues... Try and let me know...
Click to expand...
Click to collapse
post link to one u have plz
Mail me i have that file..
[email protected]
There is issue while sending here
Mohammed Raihan said:
[email protected]
There is issue while sending here
Click to expand...
Click to collapse
got anyway working fine cheers dude
Even i have the same problem as mentioned above..even i changed my oneplus 3 display
I always prefer custom roms..but screen wakeup issue had made my phone worse...then i tried oos 5.0.8 and it works like a charm...yeah i know its very old android version but no other option though...
Others who have same problem and have no issues going back to oos oreo then go for it...your problem is solved..
---------- Post added at 01:47 PM ---------- Previous post was at 01:43 PM ----------
ireaper4592 said:
got anyway working fine cheers dude
Click to expand...
Click to collapse
Is this kernel working for you!??