Develop Bugs

screen far too sensitive?

New member here, first post.
I had my g4 several weeks ago (uk version). Great phone, however recently the screen seems far too sensitive. Sometimes apps or other features are activating on their own without me pressing on them.
I looked in the settings but havent found a way to resolve this. Can anyone offer any suggestions?

Just to clarify a bit more about my issue.
Its like the "floating touch" some phones have, where i can be an inch or two away from the screen but it still activates. More rarely, it seems as if it was activating by sensing light or movement. Strange. Is the g4 supposed to have this type of function?

pholmes38 said:
Just to clarify a bit more about my issue.
Its like the "floating touch" some phones have, where i can be an inch or two away from the screen but it still activates. More rarely, it seems as if it was activating by sensing light or movement. Strange. Is the g4 supposed to have this type of function?
Click to expand...
Click to collapse
That sounds like a problem. The G4 is actually known for lacking sensitivity and yours is doing the opposite. enable this settings to see if it is actually detecting ghost touches.
Settings, About Phone, Software Info and tap on 'Buidld number' 7 times. Then go back to settings and tap Developer options, enable 'Show Touches'
if the dots show without your intervention, then it's likely due to faulty touchscreen.
Anyways, do a factory reset and see if it helped.

GUGUITOMTG4 said:
That sounds like a problem. The G4 is actually known for lacking sensitivity and yours is doing the opposite. enable this settings to see if it is actually detecting ghost touches.
Settings, About Phone, Software Info and tap on 'Buidld number' 7 times. Then go back to settings and tap Developer options, enable 'Show Touches'
if the dots show without your intervention, then it's likely due to faulty touchscreen.
Anyways, do a factory reset and see if it helped.
Click to expand...
Click to collapse
Thank you. I will give that a try,
As it happens intermittently, i cant say how quick i will find out if that is the solution, but you have been helpful.
:good:

I remember seeing a sensitivity setting somewhere..

Outta said:
I remember seeing a sensitivity setting somewhere..
Click to expand...
Click to collapse
Its under Accessibility

pholmes38 said:
Thank you. I will give that a try,
As it happens intermittently, i cant say how quick i will find out if that is the solution, but you have been helpful.
:good:
Click to expand...
Click to collapse
Does reset solve the issue? , happening on mine right now. Appreciate your feedback. Thanks

Same here, on Imperium and Stock rom, I have the phone since 6 months and it is a really random issue... my bootloader is unlock so I don't know if I can send it to warranty.
For information I have enable the touch "tracing" in developper menu, and when the issue occurred it's getting me perfect vertical line from bottom to top screen, and open a lot of apps..

leclampin said:
Same here, on Imperium and Stock rom, I have the phone since 6 months and it is a really random issue... my bootloader is unlock so I don't know if I can send it to warranty.
For information I have enable the touch "tracing" in developper menu, and when the issue occurred it's getting me perfect vertical line from bottom to top screen, and open a lot of apps..
Click to expand...
Click to collapse
And from the sound of it... Yours pretty much ****ed, at least to my knowledge. Hardware screwed and no warranty. Just bought mine like 3 weeks ago, and hated it so much. So much hyped, but the experienced is so far ****ty at best.
I suspect mine hardware issue. This seems like it's gonna be the first, and the last LG for me. Even mine with warranty still intact. Blackberry used to give this feeling long ago with their ****ty storm. Now, LG and blackberry can share that same ****ed up grave.

As madgibbon indicates, I was on Accessibility / Motricity / Response time (my phone is in french so i'm not sure if it will be exactly like that on yours) and I have set to "Long".
Since that, the issue is no longer appear, I have also switch to rom V20F (Turkey) with still the same setting for accessibility, and I don't have the issue anymore.
I don't know if it is a hardware issue, my phone falls maybe 4 times but with a case and from a little height, no broken glass or something else.
This is all the things I tried before that ;
Using flipcover (QI charge and quick circle), I have tested the "normal" case but same issue
I had a glass protection, I have removed it and cleaned my screen, same issue
I have done lot of hard reset (i'm kind of full wipe addict), same issue
Only the solution of madgibbon works fortunately, thanks mate
I'm also a bit disappointed by this phone, it is great sure I mean fluid, great camera etc... but I have some little issue that ruin the experience unfortunately (this issue with touchscreen, i'm experiencing issue with my Chromecast too that i don't have with other phones, some heating, I don't find the battery usage so good since MM, can't relock bootloader since now). I don't blame LG because i'm using some of their products and I'm / was really satisfied with : Optimus 2x, Nexus 5, TV, Monitor, Sound Bar. Anyway, waiting for 2016's Nexus and I will see if I switch or not.

leclampin said:
As madgibbon indicates, I was on Accessibility / Motricity / Response time (my phone is in french so i'm not sure if it will be exactly like that on yours) and I have set to "Long".
Since that, the issue is no longer appear, I have also switch to rom V20F (Turkey) with still the same setting for accessibility, and I don't have the issue anymore.
I don't know if it is a hardware issue, my phone falls maybe 4 times but with a case and from a little height, no broken glass or something else.
This is all the things I tried before that ;
Using flipcover (QI charge and quick circle), I have tested the "normal" case but same issue
I had a glass protection, I have removed it and cleaned my screen, same issue
I have done lot of hard reset (i'm kind of full wipe addict), same issue
Only the solution of madgibbon works fortunately, thanks mate
I'm also a bit disappointed by this phone, it is great sure I mean fluid, great camera etc... but I have some little issue that ruin the experience unfortunately (this issue with touchscreen, i'm experiencing issue with my Chromecast too that i don't have with other phones, some heating, I don't find the battery usage so good since MM, can't relock bootloader since now). I don't blame LG because i'm using some of their products and I'm / was really satisfied with : Optimus 2x, Nexus 5, TV, Monitor, Sound Bar. Anyway, waiting for 2016's Nexus and I will see if I switch or not.
Click to expand...
Click to collapse
I will try what you suggested, will report back.
Thanks for the tip.

bloodsuckingcomputer said:
I will try what you suggested, will report back.
Thanks for the tip.
Click to expand...
Click to collapse
Nope, doesn't work, it is indeed, a hardware issue.
Thanks anyway. ?

bloodsuckingcomputer said:
Nope, doesn't work, it is indeed, a hardware issue.
Thanks anyway. ?
Click to expand...
Click to collapse
Screen problem after all, just picked my phone up from the place that I bought for under warranty fix, and they told me they did replace for a new screen, and all is looking fine and dandy for now. Hope it stay this way, finger crossed. 3 weeks purchased and already this problem. I doubt this thing will last.

8.1 Update broke proximity sensor ??

hey guys, maybe someone can help with my pixel 2 XL 64 GB in Germany
Since I upgraded to 8.1 my ambient screen doesn't work properly, black screen on calls and so on. I'm pretty sure it's some change with the proximity sensor. i used some apps to test the sensor and when I clean my screen really hard everything works fine (shows "far" in the test app) but when i just wave without touching the screen, it goes to "near" and doesn't recover until i wipe the screen again ( wtf?). I can't really use the phone like this. I am in contact with Google support but they give the generic suggestions like restart the phone etc.
Everything worked fine under 8.0. i actually went ahead and flashed 8.0 back on and it works properly. it seems like they increased the sensors aggressiveness in 8.1.
For most people the problem gets resolved by taking off the screen protector but I don't have one applied. neither are there any scratches on the display. Maybe my sensor is flawed in some way :/
I also tried the turning on /off adaptive brightness trick, to which there is a thread somewhere.
maybe you guys can share your experiences or fixes,
Thanks and Liebe Grüße from Germany !

grigi93 said:
hey guys, maybe someone can help with my pixel 2 XL 64 GB in Germany
Since I upgraded to 8.1 my ambient screen doesn't work properly, black screen on calls and so on. I'm pretty sure it's some change with the proximity sensor. i used some apps to test the sensor and when I clean my screen really hard everything works fine (shows "far" in the test app) but when i just wave without touching the screen, it goes to "near" and doesn't recover until i wipe the screen again ( wtf?). I can't really use the phone like this. I am in contact with Google support but they give the generic suggestions like restart the phone etc.
Everything worked fine under 8.0. i actually went ahead and flashed 8.0 back on and it works properly. it seems like they increased the sensors aggressiveness in 8.1.
For most people the problem gets resolved by taking off the screen protector but I don't have one applied. neither are there any scratches on the display. Maybe my sensor is flawed in some way :/
I also tried the turning on /off adaptive brightness trick, to which there is a thread somewhere.
maybe you guys can share your experiences or fixes,
Thanks and Liebe Grüße from Germany !
Click to expand...
Click to collapse
I myself had some odd behaviors after updating by using the factory image with the -w removed from the flash-all.bat and ended up starting from scratch due to my cat. (Long story) but anyway, I think you will find a few other folks had bad results of some sort or other after updating. Personally, I would back up everything with TiBu and a good nandroid. ( kill any pin or fingerprint stuff first). Get anything off the internal storage you don't want to lose also.
Worst case you have a few hours of putting it back together and best case you flash from scratch and restore your data partition in TWRP.
If you factor in the time screwing around trying to "fix" it, you might be better off starting over. Unless you did actually install 8.1 from scratch them forget all this. Lol

CyberpodS2 said:
I myself had some odd behaviors after updating by using the factory image with the -w removed from the flash-all.bat and ended up starting from scratch due to my cat. (Long story) but anyway, I think you will find a few other folks had bad results of some sort or other after updating. Personally, I would back up everything with TiBu and a good nandroid. ( kill any pin or fingerprint stuff first). Get anything off the internal storage you don't want to lose also.
Worst case you have a few hours of putting it back together and best case you flash from scratch and restore your data partition in TWRP.
If you factor in the time screwing around trying to "fix" it, you might be better off starting over. Unless you did actually install 8.1 from scratch them forget all this. Lol
Click to expand...
Click to collapse
I did enjoy your cat story a while back! Dang varmints!

FWIW - I received the OTA update on my phone (unlocked version) and the proximity sensor seems to be screwed up. I having the same issues you've described. I've also got the mooshi ion glass screen protector on my phone.

CyberpodS2 said:
I myself had some odd behaviors after updating by using the factory image with the -w removed from the flash-all.bat and ended up starting from scratch due to my cat. (Long story) but anyway, I think you will find a few other folks had bad results of some sort or other after updating. Personally, I would back up everything with TiBu and a good nandroid. ( kill any pin or fingerprint stuff first). Get anything off the internal storage you don't want to lose also.
Worst case you have a few hours of putting it back together and best case you flash from scratch and restore your data partition in TWRP.
If you factor in the time screwing around trying to "fix" it, you might be better off starting over. Unless you did actually install 8.1 from scratch them forget all this. Lol
Click to expand...
Click to collapse
thank you! i already did a fresh factory flash of the 8.1 firmware from the Google devs website. Didn't solve the problem though It works fine on 8.0 so I don't get it.
It's really strange that only a bunch of people experience this problem. I kinda hoped for a functioning phone , at least for 1000 bucks.
I'm considering to get a replacement if nobody finds a fix to this.

Not sure if it'll help, but I installed "Sensors test" by Ettore Zaffaroni. Mine works just fine on 8.1 stock unrooted. The version is the OTA update to DP2.
In the Proximity test, at the bottom of that is says:
Vendor: AMS TAOS
Version: 2
Max Range: 5 cm
Resolution: 1 cm
Current: 01. ma
Maybe check and see if it is the same vendor and version. And if the other numbers match. I measured it activating between 1 1/2 inches and 2 inches, pretty much only directly in front of the sensor. I have a screen protector but with a hole cut out over the sensor.

Same issue here, no screen protector installed. Tried a factory reset without luck, tried safe mode without luck. Only started since 8.1 update.

Since the 8.1 OTA, I'm having an issue where the Always on Display doesn't always stay on and when the screen goes black, I can't use double-tap to wake it back up. I have to use the power button to turn the screen back on. I wonder if it's related to the proximity issue, because it's almost as if the screen thinks you have the phone up to your ear...?

ogarlen said:
Since the 8.1 OTA, I'm having an issue where the Always on Display doesn't always stay on and when the screen goes black, I can't use double-tap to wake it back up. I have to use the power button to turn the screen back on. I wonder if it's related to the proximity issue, because it's almost as if the screen thinks you have the phone up to your ear...?
Click to expand...
Click to collapse
Same issue here. Downloaded Sensors test, and Proximity shows as "NEAR", I've got a screen protector covering the sensor.

I have the same issue. Pixel 2 xl, after upgrading to 8.1, proximity sensor says near when screen protector is on. I think that most likely something is messed up with the update.

Wanted to add that I have a screen protector, however had the same one on 8.0 and had no issues. Also that neither DT2W or raise to wake works when the screen goes black, only pressing the power button. The issue seems intermittent. Always On Display seems to be working about half the time, whether I allow the screen to automatically shut off after a minute or if I press the power button to shut the screen off.

yes i did the test with the app sensor test and it shows "near". I downgraded to 8.0 and it works fine.
For all of you guys with screen protectors:
try removing it, it solved the problem for some people but not for me (i didn't have one on the first place)
or try downgrading if you know how to.
I went to my carrier today and they told me they got an email from Google about the 8.1 update is kinda messed up, so i should wait for the next patch. Idk what's going on, but i hope Google is aware of this.
thanks for the replies though!

I'm also having similar problems with my phone with the sensor. Also with the gesture features not working such as, double tap and flip for camera.
Ambient display not functioning is properly the most annoying, along with black screens after phone calls.

I did notify google of this issue. It would be good if all of you spend few minutes to do the same. That will let them know it is not an isolated incident.

Removing my screen protector immediately solved the problem for me. Just ordered another one that won't cover the proximity sensor.

I don't have a screen protector and I have the same issue with my proximity sensor. Anyone figure out a fix?

dpw2atox said:
I don't have a screen protector and I have the same issue with my proximity sensor. Anyone figure out a fix?
Click to expand...
Click to collapse
No fix that I'm aware of,
but there are many more people with similar issues.

Same here, had a full glass screen protector on my 2xl (on Oreo 8.0)and I cracked it when carrying a pair on ladders, phone was in my pocket at the time. So I ordered the same screen protector again... Once again it worked fine but as soon as the update to 8.1 was installed I was getting a black screen whilst receiving a call and had to wait for the caller to hang up before my phone returned to normal. As soon as I removed the screen protector the phone was fine. I've checked this 3 times and the same thing happens. Google have done something to the proximity sensor in the last update, no question.

Same issue here, no screen protector installed. Screen goes black every time I try to use the phone while on a call.

Funny how my phone worked perfectly with my screen protector before this 8.1 update for the two months the phone as been out. Now I can't hang up phone calls or turn the screen on during phone calls. -_- Hope they fix it soon.

finger print sensor not working

The error message displayed is "fingerprint hardware not available"
Do I need to replace fingerprint sensor or is it a software issue

sanjibrout said:
The error message displayed is "fingerprint hardware not available"
Do I need to replace fingerprint sensor or is it a software issue
Click to expand...
Click to collapse
You may need to do a factory reset so I'd back everything up before trying that though

Thanks for look at the post.
Already done but unsuccessful. Is there anything else I need to do

best option get a non functional phone from ebay and get it replaced

sanjibrout said:
Thanks for look at the post.
Already done but unsuccessful. Is there anything else I need to do
Click to expand...
Click to collapse
I had the same problem. I buyed a new sensor for 20€ and replaced it. Very easy and simple and works fine now?

sanjibrout said:
Thanks for look at the post.
Already done but unsuccessful. Is there anything else I need to do
Click to expand...
Click to collapse
Did you factory reset through the back up and reset settings as that's what worked for me

Same here, after update to 8.1.
There many Bugs in Oreo for 5x.
After restart fingerprint work.
Whatsapp voicemail works when u hear over ear?

sanjibrout said:
The error message displayed is "fingerprint hardware not available"
Do I need to replace fingerprint sensor or is it a software issue
Click to expand...
Click to collapse
Same happened with me, i was in train on my phone and unlocked it with my fingerprint successfully then i came home nothing happened i didn't drop my phone it was in my pocket the whole time, at home when i went to unlock the phone it displayed " Fingerprint Hardware not available", actually this issue happened to me 1 year ago it resolved automatically but now again it's happening my best solution is leave it alone (your phone) and hope future security updates to resolve it.

Display wakeup issues after screen replacement

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!??

Question Does root affects the fingerprint calibration tool?

Hi everyone,
So I just got my screen replaced by UBreakIFix, and now, the fingerprint sensor is getting the "Enrollment was not completed. Can't use fingerprint sensor" message. Since I remember reading about Google releasing a calibration tool, I just tried it. I tried in fastbootd (which gets stuck on downloading) and fastboot (gets stuck at installing). I was wondering if root might be an issue? Or if anyone knows any way to get it working?
Please note that I am trying to avoid factory resetting, but if it really seems like my final option, then I will try it out since I read that people still could not get the fingerprint sensor working after the factory reset.

I don't know if this still applies: Official Google Pixel Install fingerprint calibration software
I think I remember reading in this section about various users saying they couldn't get it to work on their P6P, either.

roirraW edor ehT said:
I don't know if this still applies: Official Google Pixel Install fingerprint calibration software
I think I remember reading in this section about various users saying they couldn't get it to work on their P6P, either.
Click to expand...
Click to collapse
It still does. I have been lurking around the Google Pixel community, and it seems the issue still persists, with no one able to figure out how to get the tool working. The article does say that it would require users to factory reset their phone after, but I have been reading that people still had the same issue after running the calibration tool and factory resetting. I am just questioning if it is only happening to users with root. I am even considering reflashing the official Feb OTA update and then try without root (pray that it is the issue), but if that does not work, I might have to factory reset and pray that it works.

This was happening to me recently but I got it to work on my third try. The only thing I did differently on my third try was press my finger on the sensor harder with each scan and then it worked without issue.
*Edit* - @NelsonTheMoron I couldn't tell if you were joking or not due to your username, haha (and I guess my username is pretty goofy as well lol). But I added a few words to my comment in case there was some confusion.

NippleSauce said:
This was happening to me recently but I got it to work on my third try. The only thing I did differently was press my finger on the sensor harder with each scan and then it worked without issue.
Click to expand...
Click to collapse
Did you just keep trying it until it worked on your third try? Or did you do something different?

I've been digging through my logcats late;y. I pushed the current build a bit too far and certain apps now refuse to accept the fingerprint as a authentication method. The ones that are throwing the errors always come with CA cert errors. The biometrics is tied into the security od the device. Being root is making that more janky one way or the other.
Redid my phone, stock (for me) with bare essentials as far as