Develop Bugs

Screen flickering after 4.0.4 update

Hi there, does anyone else experience screen flicker after latest update? I have never had it before, but after updating it does it now and then. Is there any easy fix for it?

eadred said:
Hi there, does anyone else experience screen flicker after latest update? I have never had it before, but after updating it does it now and then. Is there any easy fix for it?
Click to expand...
Click to collapse
Hi!
I experienced flicker after the update. After an factory reset and an battery charge it was gone. Now there's none. Maybe not an easy fix but worked for me!
Skickat från min HTC One X via Tapatalk 2

eadred said:
Hi there, does anyone else experience screen flicker after latest update? I have never had it before, but after updating it does it now and then. Is there any easy fix for it?
Click to expand...
Click to collapse
Guys if I remember correctly, the flicker fix
works like this. It takes time to kick in. Just be patient few says and it should be better.
Aja82 said:
Hi!
I experienced flicker after the update. After an factory reset and an battery charge it was gone. Now there's none. Maybe not an easy fix but worked for me!
Skickat från min HTC One X via Tapatalk 2
Click to expand...
Click to collapse
No action required. Just leave the kernel to do its job
Sent from my HTC One X using Tapatalk 2

eadred said:
Hi there, does anyone else experience screen flicker after latest update? I have never had it before, but after updating it does it now and then. Is there any easy fix for it?
Click to expand...
Click to collapse
In what application do you experience this flicker? is there a certain steps to encounter this? i haven't experience this yet. maybe a restart will help.

griffin0420 said:
In what application do you experience this flicker? is there a certain steps to encounter this? i haven't experience this yet. maybe a restart will help.
Click to expand...
Click to collapse
Grey background, white background, under lamp, in the dark. Depends, but if you don't have it or don't see it do not try to find it.
It's a big issue many threads, long threads, search but rather don't.
Sent from my HTC One X using Tapatalk 2

As i never had any flickering, i could presume it is very deep hardware fault and not a software issue, should be repaired by warranty

Raider0001 said:
As i never had any flickering, i could presume it is very deep hardware fault and not a software issue, should be repaired by warranty
Click to expand...
Click to collapse
Uf lets do not get this down this road again....
Please do not mention hardware fault again....It has nothing to do with this matter....
It might be a hw fault, malfunction, etc. But the ota before this .11 fought against it. Meaning the flickering was minimal or gone for most of us.
Now the technical description I do not know. But in more informed threads there was written that the kernel needs time to adapt to make the flickering go away. And most ppl that had flicker pre .11 were helped in matter of hours or days.
So I believe the flickering will be gone also after some usage. Lets get back to this in few days.
And guys who have nothing better to do as to say, it might be a hardware issue, please dont. I would like if only ppl that know what the flickering is about would write in this thread.
So if you never had it, dont have it now. Please ignore this thread ok?
Thank you
Dont wanna sound arrogant or condescending Raider, but I had fights about this already in custom rom threads. I do not wanna go there again. Sorry.

Why we cant see guy problem s profile? 4 th guy with problem, but dont know his profile, I mean messeges.
Htc One X Venom ViperX Rom + faux123 s kernel + Rezound Mod

So 10 days after the update, even though I had few reflashes, so maybe that doesnt help much, but still the flickering is still there.
Anyone else still has flickering now after a longer 4.0.4 usage and did it get better for some?

I had this before the update, then updated and waited 3 days on full brightness (i.read it has to settle with voltage or some stuff). Maybe you could try having it on full brightness? Not saying it will work & believe me, I understand your pain! Hope something works for you soon!
Keep us updated!
Sent from my now amazing HTC One X thanks to TeamVenoms ViperX rom

My HTC One X screen flickers only when on auto-brightness
Hi,
What do you mean exactly with 'screen-flicker' issues?
Different people use this description for some very different screen issues,
so I don't know if yours is severely bad or just minor...
I personally did experience some light screen flicker when the display is on auto-brightness,
the screen then has short periods where it quickly switches its brightness, and I assumed this
was normal because it's trying to adjust the brightness to the environment lighting.
This effect is easily noticed when scrolling the settings screen and is completely gone
when I deactivate auto-brightness.
maybe this can be helpful...
grtz

steabert said:
Hi,
What do you mean exactly with 'screen-flicker' issues?
Different people use this description for some very different screen issues,
so I don't know if yours is severely bad or just minor...
I personally did experience some light screen flicker when the display is on auto-brightness,
the screen then has short periods where it quickly switches its brightness, and I assumed this
was normal because it's trying to adjust the brightness to the environment lighting.
This effect is easily noticed when scrolling the settings screen and is completely gone
when I deactivate auto-brightness.
maybe this can be helpful...
grtz
Click to expand...
Click to collapse
I have the same thing going on.. it's like the backlight voltage is going up and down real fast.. after reading tons of topics on this matter I guess a lot of you guys are experiencing it.. so where is the official statement from HTC that the update should take up to two weeks to work for the screen???

REBOOT
eadred said:
Hi there, does anyone else experience screen flicker after latest update? I have never had it before, but after updating it does it now and then. Is there any easy fix for it?
Click to expand...
Click to collapse
Just off with HTC after the update last week. (Stock phone not rooted) My One X has been freezing especially on Facebook and twice a day rebooting itself. Slight flickering when scrolling..All errors were logged. Soft reset and Hard reset carried out several times, but no improvement.
HTC have put a service call on it and collecting the phone Thursday.

Murano1 said:
Just off with HTC after the update last week. (Stock phone not rooted) My One X has been freezing especially on Facebook and twice a day rebooting itself. Slight flickering when scrolling..All errors were logged. Soft reset and Hard reset carried out several times, but no improvement.
HTC have put a service call on it and collecting the phone Thursday.
Click to expand...
Click to collapse
Try flashing the RUU (this is the first thing HTC will do). It will wipe your phone, so back up. But test it before restoring.

Mine seems only to be flickering with Sense Launcher. No flickering with Nova Launcher. AND Nova is even smoother.
Sent from my HTC One X

Can someone explain, what this flickering is? It's not similar to the 'Recent Apps'/Grey Colour is it?

I purchased a brand new HOX yesterday which had a screen flicker. The flicker was only noticed on white.
I turned the phone on and was pushed 3 software updates, one after another and thought that after the updates the screen flicker would be solved. I ended up with the 4.0.4 update and the screen flicker was still there. I did a full factory reset and the screen flicker seems to have gone.
I will keep my eye on it, because if needed I can return it for a replacement within 30 days.
Has a factory reset worked for anyone else after updating to 4.0.4?

snapples said:
I purchased a brand new HOX yesterday which had a screen flicker. The flicker was only noticed on white.
I turned the phone on and was pushed 3 software updates, one after another and thought that after the updates the screen flicker would be solved. I ended up with the 4.0.4 update and the screen flicker was still there. I did a full factory reset and the screen flicker seems to have gone.
I will keep my eye on it, because if needed I can return it for a replacement within 30 days.
Has a factory reset worked for anyone else after updating to 4.0.4?
Click to expand...
Click to collapse
Not that I know of. I mean that a factory reset helps.
After it was flickering for me. I decided to go and test a custom kernel. Before the only reason I couldn't go with a custom kernel was the flickering. Only on stock it didn't flicker for me.
So as it was flickering I tried faux again, and now I do not notice it anymore.
Maybe it needed time to settle, maybe the UV helped? Or that I shutdown the capacitive buttons lights? I do not know...
But it can also be the change of scenery. As I was before on another continent

you need to wait till the update settles...

hamdir said:
you need to wait till the update settles...
Click to expand...
Click to collapse
hamdir read this :
My first comment here in the thread with a typo, says = days:
Guys if I remember correctly, the flicker fix
works like this. It takes time to kick in. Just be patient few says and it should be better.
Click to expand...
Click to collapse
And another one of me:
So 10 days after the update, even though I had few reflashes, so maybe that doesnt help much, but still the flickering is still there.
Anyone else still has flickering now after a longer 4.0.4 usage and did it get better for some?
Click to expand...
Click to collapse
So I took the time
I know I need to wait. What I didn't was how long. Hoped like hours, days, took 3 weeks
And I am still not sure its gone, as said different scenery or the other stuff, lights on buttons off, UV, etc

[Q] Galaxy Nexus Sleep of Death

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…)

LeEco Le Pro 3-- red screen occur when pressing the power button to turn off.

Hello everyone, I got LeEco Le Pro 3 two weeks ago. For the past two weeks of testing, I notice that the screen quickly turns red when pressing the power button to turn the screen off. Is any of you facing this problem? It happens randomly, not every time. I have attached the video in slow motion capture in the 7z zip file. So you can see, what I am talking about. Let me know if any of you see it.

In mine sometimes it blink red. Power sleeping your phone rapidly. May red screen is reaction for force kill app?

marik1 said:
In mine sometimes it blink red. Power sleeping your phone rapidly. May red screen is reaction for force kill app?
Click to expand...
Click to collapse
I did not power sleep my phone rapidly. The red screen still persist. I don't know if force kill app cause it. I submit the feedback through the leeco experience center about this issue. This is what I got from them:
"Le Engineer
Hello,
I just get some information for this issue, in low battery level the red screen issue will happen sometimes. We also find the same thing on other brand device.
However R&D team are working on it. Hope it will be fixed in next generation product.
Sorry for inconvenience. Thank you for choosing the LeEco."
So I don't know if my phone is defective or not. It's hard to tell. Base on this message, look like there is no fix for this.

I saw this movie. My phone behave as same as your <sometimes>. May it's EUI problem? Somebody on other ROM like MIUI or CM13 can say something?

marik1 said:
I saw this movie. My phone behave as same as your <sometimes>. May it's EUI problem? Somebody on other ROM like MIUI or CM13 can say something?
Click to expand...
Click to collapse
Mine occur sometime, too. Here is what I analyze:
1. On the home screen; when pressing power button to turn off, red screen occur sometime.
2. Any app that has white background like the waze app I use in the video, red screen occur every time I turn off the screen while leaving the app running. That goes for other app like chrome, whatsapp, google map, gmail, etc. Same result.
3. On the back button, when I press hold, the screen turns off. No red issue. This was on the home screen and this rarely happen. But for apps that is open, same issue.
That is what I like to know if it is hardware defect or software EUI problem. It looks like software issues. It would be great if someone would test it with different roms such as CM13 or MIUI.

crazy1990 said:
Mine occur sometime, too. Here is what I analyze:
1. On the home screen; when pressing power button to turn off, red screen occur sometime.
2. Any app that has white background like the waze app I use in the video, red screen occur every time I turn off the screen while leaving the app running. That goes for other app like chrome, whatsapp, google map, gmail, etc. Same result.
3. On the back button, when I press hold, the screen turns off. No red issue. This was on the home screen and this rarely happen. But for apps that is open, same issue.
That is what I like to know if it is hardware defect or software EUI problem. It looks like software issues. It would be great if someone would test it with different roms such as CM13 or MIUI.
Click to expand...
Click to collapse
It could be a software issue since I don't have that on CM.

marik1 said:
I saw this movie. My phone behave as same as your <sometimes>. May it's EUI problem? Somebody on other ROM like MIUI or CM13 can say something?
Click to expand...
Click to collapse
I never seen with MIUI 8, can anyone give me a sequence to try ?
Tried some times, shut down it's too rapid to see with MIUI.

losteagle said:
I never seen with MIUI 8, can anyone give me a sequence to try ?
Tried some times, shut down it's too rapid to see with MIUI.
Click to expand...
Click to collapse
If you have another phone with slow motion support just like I did, you can try that.

Other thing I want to mention, I would like to know that if the red screen does not happen to people who have CM or MIUI on lepro 3, can any of you go back to EUI and try to do the same steps? If you can. This would more confirm that the software is the issue and not the hardware defect.

Any update?

Hi folks! I've been searching for this rare issue since I got my LM2 last week. I have the very same issue and I notice the same @crazy1990 mentioned here. Besides, I notice this red light is more noticeable when the brightness is higher.
IMO, I don't feel it's a matter of bad hardware (I hope so), as there are no clues of any other issues at all. I'm also using stock (23s) and I suspect it's some poorly designed fade for the ROM.
Any updates from anyone?

Yes. Red screen blink is noticeable when the brightness is high. As of June, I still have this issue since November on this stock rom 21s. So far, there was no screen degradation or any kind of lcd problem. Lcd works perfect since day one. A while back, I installed lineageOS and I still experience red screen when the rom froze and reboot. At this point, I still don't know if it is the software or hardware. I hope someone can help us out.

crazy1990 said:
Yes. Red screen blink is noticeable when the brightness is high. As of June, I still have this issue since November on this stock rom 21s. So far, there was no screen degradation or any kind of lcd problem. Lcd works perfect since day one. A while back, I installed lineageOS and I still experience red screen when the rom froze and reboot. At this point, I still don't know if it is the software or hardware. I hope someone can help us out.
Click to expand...
Click to collapse
At least your report is positive. :fingers-crossed:
Did you try other custom ROMs? RR, Cuoco?

razmth said:
At least your report is positive. :fingers-crossed:
Did you try other custom ROMs? RR, Cuoco?
Click to expand...
Click to collapse
No, but I already tried omnirom and purity rom. No red screen issue. I also tried tars 21s and turbo base rom, the issue is there.

crazy1990 said:
No, but I already tried omnirom and purity rom. No red screen issue. I also tried tars 21s and turbo base rom, the issue is there.
Click to expand...
Click to collapse
Great to know it doesn't happen on Omni/Purity. My biggest concern was an increasing degradation and/or flickering issues arising when changing to a stock ROM.
Thanks for your information.
Sent from my Le X820 using Tapatalk

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

Ambient Display Screen Flashes

Hi Guys!~
Hope all is well !!
... recently I came across my rooted android 11 Pixel 3XL got a screen flashes with bright home screen background during the screen turning off and entering ambient display mode.
I try my best to find a solution but haven't found one yet.
I have tried to reflash to stock, also doesn't fix the problems.
... the only solution I found at this moment is to get android 12 beta which the transition animation from turning off the screen to the wake up of ambient display is totally different and I still prefer to stay with rooted android 11.
Your browser is not able to display this video.

Sounds like a hardware failure, display or mobo.

blackhawk said:
Sounds like a hardware failure, display or mobo.
Click to expand...
Click to collapse
It only happens when the screen turning off from home screen or app.
Trying to shoot a vid to show the issue now.

haritvii said:
It only happens when the screen turning off from home screen or app.
Trying to shoot a vid to show the issue now.
Click to expand...
Click to collapse
If you tried multiple roms especially the stock* one unless it's something you loaded after the flash, it's got to be hardware related. It's possible the non stock rom blew out some hardware too.
Try setting brightness to manual.
A rework around may be the only viable solution.
You ever wonder what happens when one or two of the billions of semiconductor junctions/resistors/caps fails in the chipset or display? You might be looking at an example
It could be a loose connection, or a faulty ribbon cable/connector, a subassembly maybe even battery (if so there be more symptoms).
*unless a known issue in this device.

blackhawk said:
Sounds like a hardware failure, display or mobo.
Click to expand...
Click to collapse

blackhawk said:
If you tried multiple roms especially the stock* one unless it's something you loaded after the flash, it's got to be hardware related. It's possible the non stock rom blew out some hardware too.
Try setting brightness to manual.
A rework around may be the only viable solution.
You ever wonder what happens when one or two of the billions of semiconductor junctions/resistors/caps fails in the chipset or display? You might be looking at an example
It could be a loose connection, or a faulty ribbon cable/connector, a subassembly maybe even battery (if so there be more symptoms).
*unless a known issue in this device.
Click to expand...
Click to collapse
Thank you so much, now I got a great reason to get a new Pixel 6 then

haritvii said:
Thank you so much, now I got a great reason to get a new Pixel 6 then
Click to expand...
Click to collapse
I could be wrong... and even if it is hardware that doesn't mean a work around doesn't exist to make it usable.
Play with it, Androids wuv attention