Develop Bugs

Pixel XL screen flicker

My Pixel XL screen flickers when charged to 100% and I leave the charger plugged in. This happens with my car charger and also my portable battery pack, both which I used with my Nexus 6P no problem.
Soon as I unplug the flicking stops.
Anyone else have this problem? Or heard anything about this?
Sent from my Pixel XL using XDA-Developers mobile app

jblack41510 said:
My Pixel XL screen flickers when charged to 100% and I leave the charger plugged in. This happens with my car charger and also my portable battery pack, both which I used with my Nexus 6P no problem.
Soon as I unplug the flicking stops.
Anyone else have this problem? Or heard anything about this?
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
did u drop it on day 1 if not ask to get a replacement never heard of this issue b4 mine works flawlessly in every way

Mine does it, as well. It's really noticeable at night, when the screen is turned down...
Sent from my Pixel XL using XDA Premium HD app

BaconSeeds said:
did u drop it on day 1 if not ask to get a replacement never heard of this issue b4 mine works flawlessly in every way
Click to expand...
Click to collapse
Never dropped it
Sent from my Pixel XL using XDA-Developers mobile app

335Deezl said:
Mine does it, as well. It's really noticeable at night, when the screen is turned down...
Sent from my Pixel XL using XDA Premium HD app
Click to expand...
Click to collapse
Does it flicker with the charger that came with the phone? Or only other chargers
I don't think mine does...will have to try tomorrow when I get home
Sent from my Pixel XL using XDA-Developers mobile app

I noticed this too. Have a pixel XL and it is very noticeable when watching video on the phone at night with it plugged in.
I have had the phone for one day, no drops or scratches of any kind and only using official chargers/cables.
None of my previous phones had this issue but i am not sure how they got past QA as i am sure many people use their device when charging.

My phone was flickering too when I had it connected to my battery pack.

Looks like theres alot of defective devices out there

I've actually noticed the flicker one night laying in bed too. It was more apparent with Night Mode on. Hmm. wondering if I should seek replacement now...

I have this issue too I've always thought people were overly picky about their new devices but lo and behold here I am. Can't decide if I should bother RMAing...100% and charging isn't a huge use case for me, so as long as no other damage is occurring, I'm not sure it's worth setting up another phone over... Idk. I just want what's in my hand to be perfect

Screen flicker
I've noticed it in mine too. I had a similar problem on a friend's older LG, same symptoms and everything, was just a software bug in his case, hoping it's the same for the pixel, I just got over the death of my moto nexus 6
-Update-
Talking to google support right now, it's sounding like a hardware issue, but they're being tight-lipped as expected with a potential QA issue this close to launch. Going to post updates with troubleshooting steps they send me, but they're being good sports about a potential RMA.
Thanks for chatting with us today!
As discussed in the chat, the following steps may help for flickering screen on your device:
Step 1: Try safe mode.
Did you know:
Running your device in safe mode turns off all third-party apps and is a great way to figure out if any issues are being caused by third-party apps.
Safe mode does not affect normal functionality and features such as making phone calls, texting, camera and photo apps, Google apps, or any stock Android app.
It's recommended that safe mode be used to determine if third-party apps are causing issues such as random reboots, freezing, fast battery drain, or even your screen flickering issue.
To reboot the device into safe mode:
With the device on, hold the Power button on the device to get the "Power off" screen prompt.
Touch and hold Power off until the "Reboot to safe mode" prompt appears.
Touch OK to reboot in safe mode.
Note: To exit safe mode later, simply restart the device normally.
When the device reboots into safe mode, check if the screen flickering has resolved.
If the screen flickering is resolved, great!
If the screen flickering is *not* resolved, continue to Step 2.
Step 2: Update to the latest version of Android OS.
Go to "Settings" > scroll down to "System" > touch About phone (or tablet) > touch System updates.
If your device is modified or rooted, revert your device to original factory image since troubleshooting steps may not work on modified/rooted devices. You can use our Nexus factory images to re-image your device.
Step 3: Reset device to factory settings.
If your device's screen still flickers even when in safe mode and your device did not experience any recent physical damage, resetting your device to factory settings is a last step which may resolve the issue. Resetting your device to factory settings will erase all local data on your device. Backup of your personal local data (pictures, music and video files) is recommended.
To backup personal data on your device
To reset your device to factory settings
**Only for users that have modified their Android device** Troubleshooting steps may not work on modified or rooted devices. Also, modifying or rooting your device may have caused the issue you're experiencing. Revert your device to original factory image.
If your issue was resolved during these steps, great!
If your issue was *not* resolved, call us or reply to this email and reference that you already went through all of our Flicking Screen troubleshooting steps, including resetting your device to factory settings.
You can reply to this email regarding the software update as well. I'm happy to help!
Click to expand...
Click to collapse

is system update available? go to settings>about phone>system updates
if it needs update then you can do that and see how it works
---------- Post added at 01:43 PM ---------- Previous post was at 01:39 PM ----------
is system update available? go to settings>about phone>system updates
if it needs update then you can do that and see how it works

-Deleted-

I literally noticed this this morning. 100% battery, night mode, brightness all the way down. At least I'm not alone

It does it with the official charger also...the one that came with the phone on mine

Deleted

I noticed this on mine as well. The fact that it's only happening while charging makes me think it might have something to do with electrical noise from charging affecting the display. This often happens with the audio output on phones buzzing while charging them, and I've seen it happen on laptops with both audio and video buzzing/flickering (google search either of these issues and you'll get tons of results).
Hopefully we'll get an official answer from Google soon.

I chatted with Google and they told me to go to Verizon, bummer. I really did not want to be bothered with another exchange crap. I came over from note 7. I just want a phone that works right and won't explode.

Just noticed half an hour ago myself after having the phone for 3 days. I've never seen it before tonight. Not sure if I just didn't see it (not sure how I would miss it because now it's very obvious) or if it just started happening now. Only happens while charging, stops immediately after I unplug it. Can confirm it does it while using the included charger.
EDIT: Just contacted Google Support through the built-in support chat in settings. The rep declared it a hardware issue and processed an RMA for me. They told me I can hold off on sending back my current device until my new one arrives. Not happy I got a defective device (still usable, so not a huge issue), but very happy with how fast and easy going their support was.

I noticed this this morning too. It was flickering at 100% charge. If it does it again k may try to replace it. I just opened a new T-Mobile account and have no compatible back up phone, so hopefully they let me keep it until I would get a replacement.

ohio wake lock

Hello all
This week I enabled the permission that allows Better Battery Stats to check for wakelocks etc without requiring root.
Resrarted phone, let it do its magic and then checked results.
Ohio_wake_lock was the big culprit and phone would not enter deep sleep.
On googling I came across next to no answers and some vague mention to disable HTC Push Client.
I disabled the app from the settings and the wakelock has since disappeared and my device now enters deep sleep which it didn't before.
Hopefully this helps others out there. If anyone has extra information on this wakelock it'd be great.

rdmack said:
Hello all
This week I enabled the permission that allows Better Battery Stats to check for wakelocks etc without requiring root.
Resrarted phone, let it do its magic and then checked results.
Ohio_wake_lock was the big culprit and phone would not enter deep sleep.
On googling I came across next to no answers and some vague mention to disable HTC Push Client.
I disabled the app from the settings and the wakelock has since disappeared and my device now enters deep sleep which it didn't before.
Hopefully this helps others out there. If anyone has extra information on this wakelock it'd be great.
Click to expand...
Click to collapse
Hi,
I appear to have the same wakelock issue as you did. Im running lineageos and cant find any traces of htc push client in app drawer, system apps or through titanium backup.
Where did you actually find it?
Thanks in advance.

I got this problem. How to get rid of this.

Harrygsr said:
Hi,
I appear to have the same wakelock issue as you did. Im running lineageos and cant find any traces of htc push client in app drawer, system apps or through titanium backup.
Where did you actually find it?
Thanks in advance.
Click to expand...
Click to collapse
Must be a different app or issue causing the same wake lock. He's on the HTC rom. Lineage is stock Android.
Here is that app, it should open the playstore and you see that it isn't installed.
HTC PNS
I found this with a quick Google search, you may find more info, I didn't look long. An edit may be needed like this, wgich you could share and ask fagyi
https://review.lineageos.org/c/Line.../1/drivers/usb/anx7418/anx_ohio_driver.c#2399

andybones said:
Must be a different app or issue causing the same wake lock. He's on the HTC rom. Lineage is stock Android.
Here is that app, it should open the playstore and you see that it isn't installed.
HTC PNS
I found this with a quick Google search, you may find more info, I didn't look long. An edit may be needed like this, wgich you could share and ask fagyi
https://review.lineageos.org/c/Line.../1/drivers/usb/anx7418/anx_ohio_driver.c#2399
Click to expand...
Click to collapse
Thanks for the reply. I ended up bringing the phone back to my carrier and showed them how fast the battery was draining even after reverting back to full stock HTC. It was still under warranty so they sent it off for repair and came back fixed. The repair company didn't specify what they had changed, it just said something like faulty part replaced but it's good as new now running lineage again :good:

Harrygsr said:
Thanks for the reply. I ended up bringing the phone back to my carrier and showed them how fast the battery was draining even after reverting back to full stock HTC. It was still under warranty so they sent it off for repair and came back fixed. The repair company didn't specify what they had changed, it just said something like faulty part replaced but it's good as new now running lineage again :good:
Click to expand...
Click to collapse
Is it really hardware problem? I am on leedroid and ohio wake lock started yesterday. I tried disable Htc Push Client, but not works. I also flashed Elite Kernel, but no change.
andybones said:
Must be a different app or issue causing the same wake lock. He's on the HTC rom. Lineage is stock Android.
Here is that app, it should open the playstore and you see that it isn't installed.
HTC PNS
I found this with a quick Google search, you may find more info, I didn't look long. An edit may be needed like this, wgich you could share and ask fagyi
https://review.lineageos.org/c/Line.../1/drivers/usb/anx7418/anx_ohio_driver.c#2399
Click to expand...
Click to collapse
Thanks @andybones , I'll be very happy if @fagyi help me .

I had the Ohio_wakelock and OTG_wakelock at the same time causing no deep sleep.
Also, my 10 wasn't fast charging.
I changed the charge port and all issues went away.
Exkm can disable these wakelocks, but that doesn't fix the problem.

mcmorariu said:
I had the Ohio_wakelock and OTG_wakelock at the same time causing no deep sleep.
Also, my 10 wasn't fast charging.
I changed the charge port and all issues went away.
Exkm can disable these wakelocks, but that doesn't fix the problem.
Click to expand...
Click to collapse
Thanks for reply. My fast charging worked, but the charging didn't. I had to reconnect the cable to the phone several times. After that charging started worked.
I tried many firmwares and ROMs (Marshmallow - stock, Nougat - stock, purefusion, Oreo - stock, Leedroid, Pie - lineage, crdroid), but the result was the same.
I decided to return my phone, because i bought it in 21/9/2017. I needed my phone on my holiday, so I flash stock Oreo. After five days wakelocks came out. I don't know how, but now I don't have any wakelocks and my charging works without problems.

Grubmi said:
Thanks for reply. My fast charging worked, but the charging didn't. I had to reconnect the cable to the phone several times. After that charging started worked.
I tried many firmwares and ROMs (Marshmallow - stock, Nougat - stock, purefusion, Oreo - stock, Leedroid, Pie - lineage, crdroid), but the result was the same.
I decided to return my phone, because i bought it in 21/9/2017. I needed my phone on my holiday, so I flash stock Oreo. After five days wakelocks came out. I don't know how, but now I don't have any wakelocks and my charging works without problems.
Click to expand...
Click to collapse
My device is crazy. First two screenshots are from night, where wakelock drain my battery. Others are from today usage.

Grubmi said:
My device is crazy. First two screenshots are from night, where wakelock drain my battery. Others are from today usage.
Click to expand...
Click to collapse
that does look crazy
when I had the hardware issue, it was consistently sucking up battery whether day or night...
I still recommend replacing the charge port, may be an intermittent short in that PCB.

d850 reboot constantly

I have my d850 for a long time. in the past it did this thing where it would reboot constantly until I plugged it in. A new battery solved that issue. Now, 8 months later, it happens again, only difference is that plugging it in doesnt help. Ive tried two new batteries this time, first one didnt work and i figured it was faulty so i returned it and got another, which still doesnt fix the issue. I turned on the phone without my sim and sd card which made no difference either.
I just unrooted my phone and reset to stock, which still doesnt fix the issue either. should i bother with a third new battery to test this? this phone works so smoothly, still fast, still a GREAT phone...I just cant pin point the issue thats causing the reboots as ive tried all i can think of. Id hate to have to toss it. any other suggestions?
thanks in advance!

Have a good read on this thread right here... Maybe some comments may help you
:good:

souler456 said:
Have a good read on this thread right here... Maybe some comments may help you
:good:
Click to expand...
Click to collapse
wow thank you. i have seen a few other threads on how to disassemble the phone for screen flicker, overheating, etc but I havent came across this one. I tried applying thermal paste ( an idea i found in the thread you linked me to), it seems to restart less (without the sim card in, but wifi and location/google maps works fine). since its restarting a lot less, im thinking of opening again and actually purchasing and applying the thermal pad.
Does anyone else have suggestions? and again, thank you!

ohaai said:
wow thank you. i have seen a few other threads on how to disassemble the phone for screen flicker, overheating, etc but I havent came across this one. I tried applying thermal paste ( an idea i found in the thread you linked me to), it seems to restart less (without the sim card in, but wifi and location/google maps works fine). since its restarting a lot less, im thinking of opening again and actually purchasing and applying the thermal pad.
Does anyone else have suggestions? and again, thank you!
Click to expand...
Click to collapse
I use Non-Stock ROM for my device ever since 2 years ago (not a fan of Stock ROMs), and I have no issues aside from early throttling (can be solved with thermal pad). Maybe the issue only persist because you use Stock ROMs. Try changing into Non-Stock ROMs like AOSP or LOS with a good kernel.
:good:
---------- Post added at 05:56 AM ---------- Previous post was at 05:54 AM ----------
souler456 said:
I use Non-Stock ROM for my device ever since 2 years ago (not a fan of Stock ROMs), and I have no issues aside from early throttling (can be solved with thermal pad). Maybe the issue only persist because you use Stock ROMs. Try changing into Non-Stock ROMs like AOSP or LOS with a good kernel.
:good:
Click to expand...
Click to collapse
Edit: If you don't want to, I also remembered that "paper" trick, don't know what thread is it, but it fixed the bootloop on some users. Maybe it's on reddit

souler456 said:
Have a good read on this thread right here... Maybe some comments may help you
:good:
Click to expand...
Click to collapse
souler456 said:
I use Non-Stock ROM for my device ever since 2 years ago (not a fan of Stock ROMs), and I have no issues aside from early throttling (can be solved with thermal pad). Maybe the issue only persist because you use Stock ROMs. Try changing into Non-Stock ROMs like AOSP or LOS with a good kernel.
:good:
---------- Post added at 05:56 AM ---------- Previous post was at 05:54 AM ----------
Edit: If you don't want to, I also remembered that "paper" trick, don't know what thread is it, but it fixed the bootloop on some users. Maybe it's on reddit
Click to expand...
Click to collapse
thats the thing, ive always been rooted. always. but for testing I did unroot and revert back to stock and the problem still sticks. after realizing that I rooted again and went back to marshmallow (instead of nougat, and ive tried more than a few roms using marshmallow and a few different ones with nougat). So ive done with non stock roms for a long time, and i do prefer it.
So ive done the thermal grease without the thermal pad and it worked for a day(literally), and stopped working and constant rebooting all over again. I got a new sim card today, no luck. so i may try this thermal pad. but since just the theermal grease seems to not have fixed the issue, im not so sure the thermal pad will work either, but will give it a try.
another thought though, when flashing roms or kernels, it goes through the process like normal! but when actually booting up or when operating (like texting or surfing the web, or just sitting on the counter/in pocket), it just restarts constantly or bootloops(just shoes the LG screen and turns off, and then LG screen again, and so on)! i cant pin point the issue. im gonna look into the paper trick and possible look into purchasing a thermal pad. can anyone provide links in the one they used? i saw the link in another thread just wasnt sure how long that would take to ship to me. maybe i can see what other used?

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

Uresponsive black screen after updating to Android 10

After updating to 10, a few times a day my phone becomes completely unresponsive. Since the screen is off, I'm not even sure if the phone is powering off. I've flashed the factory image to see if starting clean would fix it, but that didn't work. Anybody else experiencing this?

darkstar73 said:
After updating to 10, a few times a day my phone becomes completely unresponsive. Since the screen is off, I'm not even sure if the phone is powering off. I've flashed the factory image to see if starting clean would fix it, but that didn't work. Anybody else experiencing this?
Click to expand...
Click to collapse
No, but you may be installing an app that is causing it. Try replicating the issue in safe mode. Ruling that out, if you have done a clean install using the full image (not ota) and allowed it to wipe your data there is not much more to do before contacting Google. A clean install restores your phone to its "out of the box" state. If the problem persists, it is likely hardware related. You can try a factory reset from the stock recovery... that is the first thing they will insist you do before processing an RMA.

v12xke said:
No, but you may be installing an app that is causing it. Try replicating the issue in safe mode. Ruling that out, if you have done a clean install using the full image (not ota) and allowed it to wipe your data there is not much more to do before contacting Google. A clean install restores your phone to its "out of the box" state. If the problem persists, it is likely hardware related. You can try a factory reset from the stock recovery... that is the first thing they will insist you do before processing an RMA.
Click to expand...
Click to collapse
I didn't have the issue on Pie and haven't installed any additional apps. It mainly happens after I haven't used the device for a while. It feels like it won't wake up so I have to hold the power button to force a reboot.

darkstar73 said:
After updating to 10, a few times a day my phone becomes completely unresponsive. Since the screen is off, I'm not even sure if the phone is powering off. I've flashed the factory image to see if starting clean would fix it, but that didn't work. Anybody else experiencing this?
Click to expand...
Click to collapse
Yes.
I was just peaking to a buddy with a 2xl and he is having the same issue since 10.

I have an issue where after about two day of it being on it will start to stutter, and then after a couple hours it reboots itself. It's done it since 10 was released. Never had an issue on 9. Now I proactively reboot it once I notice the stuttering. Kind of sucks since 9 was super stable for me. No new apps, and no settings were changed. Just updated to 10, and it started. Kind of like memory is leaking causing it to stutter/freeze, but the last patch they said they fixed the leak. Guess not.

bobbyphoenix said:
I have an issue where after about two day of it being on it will start to stutter, and then after a couple hours it reboots itself. It's done it since 10 was released. Never had an issue on 9. Now I proactively reboot it once I notice the stuttering. Kind of sucks since 9 was super stable for me. No new apps, and no settings were changed. Just updated to 10, and it started. Kind of like memory is leaking causing it to stutter/freeze, but the last patch they said they fixed the leak. Guess not.
Click to expand...
Click to collapse
I just had a random reboot while taking my dog for a walk. Was only listening to SiriusXM. Think I'm going back to Pie until Google gets the kinks ironed out on 10.

https://support.google.com/pixelphone/thread/14074635?hl=en

Booted into safe mode last night and had to force a reboot this morning to get the screen to respond. This is definitely an issue with 10 and not an app. I'm going back to Pie since having my phone turn off every night is unacceptable, especially since my phone is my alarm clock.

I took the OTA before setting up my new P3XL on A10 and don't have any issues. You might try wiping data then restore apps without data.

droidstyle said:
I took the OTA before setting up my new P3XL on A10 and don't have any issues. You might try wiping data then restore apps without data.
Click to expand...
Click to collapse
I flashed the A10 Oct factory image and wiped data. Still have the issue. The only thing that fixes it is going back to Pie.

So this happened to me twice now since being on 10. My screen would go black while using the phone, and then the phone would be unresponsive, so I would need to force a reboot, but after the Google splash screen it goes into recovery, and this message shows "Could not load Android OS. You can try again, or factory reset.". I did "Try again" both times, and it booted fine. Really irks me since I can't afford to do a factory reset since I use a lot of apps that have special info in them (Like Google Auth App that has many devices I need, and resetting I would have to redo every device). I hope Google can fix these issues with the next update.

I think my issue is due to the sensor bug that was introduced in 10. I have disabled the sensors on my phone and it hasn't froze since!! Hopefully Google fixes on the Nov update.

I'm having the issue that after my screen turns off, after a certain amount of time, I cannot get it to turn back on. The phone is still on, but is unresponsive to my input. I have to hard reset.
I have tried reflashing, and tried disabling sensors. I did not have an issue with the 10 September updated, but since updating to the November update, I had the issue non-stop all day.
Platform-Tools fully updated, not using gesture navigation, but the 2-button.

@MeetFace, yes! Same here since the November update. Something isn't right.

I'm still dealing with the black screen issue. Nov update didn't fix it.
https://issuetracker.google.com/issues/143288447

Update, I read in a thread somewhere that disabling darkmode fixed it for one person (rando I know).
I created a tasker script that disables darkmode once the screen shuts off, and enables it when it turns back on. So far, no BSOD this morning (4 hrs)
FWIW

MeetFace said:
Update, I read in a thread somewhere that disabling darkmode fixed it for one person (rando I know).
I created a tasker script that disables darkmode once the screen shuts off, and enables it when it turns back on. So far, no BSOD this morning (4 hrs)
FWIW
Click to expand...
Click to collapse
Can you share the tasker script? I love darkmode, but have never used tasker.

darkstar73 said:
Can you share the tasker script? I love darkmode, but have never used tasker.
Click to expand...
Click to collapse
Yep
https://taskernet.com/shares/?user=...uZXbuaEqxZTMoTxnDDk1yI=&id=Profile:Screen+Off

MeetFace said:
Yep
https://taskernet.com/shares/?user=...uZXbuaEqxZTMoTxnDDk1yI=&id=Profile:Screen+Off
Click to expand...
Click to collapse
How can you tell this is working? I've got it setup ??

MeetFace said:
Yep
https://taskernet.com/shares/?user=...uZXbuaEqxZTMoTxnDDk1yI=&id=Profile:Screen+Off
Click to expand...
Click to collapse
Thanks for this! Phone hasn't gotten a frozen black screen since I loaded the script!