Develop Bugs

Proximity sensor failure

My DHD has problems with the proximity sensor. I returned the device to the vodafone store (Netherlands), and they changed the device for a new one that worked.
Today, 1 day later, my second DHD is now having the exact same problem with the proximity sensor.
When I make a call, the screen immediately goes black, and the device no longer responds to any button (not even the power button on top). The ony way to get the device back to life is by removing and reinserting the battery.
Video of the problem
When I receive a call, the screen stays unlocked, even when the device is placed against my ear, so I end up with my ear pressing the active screen....
I've read more complaints about this exact problem on the tweakers.net forum. It is still unknown whether this is a hardware of software failure.
UPDATE
The problem seems to be related to the lightsensor, when holding a locked DHD in front of a bright light source, the device wil unlock (as long as you keep it in front of the light).
It might be, that when used in bright daylight a DHD will function properly.
Also, when calling using the headset, the problem does not occur. When inserting a headset in a "locked" DHD, it will wake up.
UPDATE2
Some facts, to "bust" some myths about the problem:
- It seems the problem can happen on all DHD's, not just devices with a particular S/N, software version, carrier (telco) or color.
- It has something to do with the light sensor (which is the same sensor as the proximity sensor) since the device unlocks when held in front of a bright lightsource, some users claim their device works well, as long as they are in daylight.
- The DHD uses a CM3602 proximity/light sensor, the same as a regular Desire
- The problem might not occur immediately after purchase, sometimes it takes a few days before it starts, thus switching your DHD for a new one might only solve your problem for a few hours/days (this is what happend to my second and third... yes third device)

Seems like the same kind of problem: http://forum.xda-developers.com/showthread.php?t=811282

Exactly the same post. Nice detail that I'm also a Dutch user bought it at a Vodafone store.

So, that's at least 3 devices reported with this problem.
Is there a way to turn off the proximity sensor? This would mean I have to turn the screen off manually when I make or receive a call, but that way, I don't have to reset the device every time I make a cell

Maybe you guys have found why it failed the google test ?

1-2-3 from the first stock - that is an failure that will come back to all of us...
did you try contact HTC ??

I wouldnt be very worried tbh, this is surely software related else they wouldnt release any batch of cellphones and delay the release for more than just a few weeks.

Can you make a Video and load it up on Youtube?
If we have a video it´s much easier to show HTC the problem... maybe we can load this video up on facebook to the HTC page...

Really bad if this failure concerns all DHDs. But why 3 devices?
I only count LeonM1234 and WizardX?
Edit: Ah I see 2x LeonM1234 and 1x WizardX. Forget this post

liorra3 said:
1-2-3 from the first stock - that is an failure that will come back to all of us...
did you try contact HTC ??
Click to expand...
Click to collapse
Will try contacting HTC Netherlands tomorrow, today is Sunday...
name_th said:
Really bad if this failure concerns all DHDs. But why 3 devices?
I only count LeonM1234 and WizardX?
Click to expand...
Click to collapse
This is my second DHD with this problem
P.S. Can any mod please remove the 1 post per 5 minutes limit, it is quite annoying... thanks!

A lot of HTC phones have a similer problem. Its S/W related (the desire had it when it was first out e.g. it the screen used to go black and not re-light untill you placed it on a table or the other person hung up)
I would be suprised if 3 phones have the same fault unless it SW related :-D

HTC's new Windows phone seems to have a similar error with the proximity sensor:
As I'm a new user I'm not allowed to post a working link. I try to write it so the system accept it.
www . techeye.net / mobile/one-day-after-launch-event-windows-phone-bug-spotted
If this turns out to be true it's more hardware related than software, isn't it?

i think to cancel my DHD order until that issue will check.
Apache14 said:
A lot of HTC phones have a similer problem. Its S/W related (the desire had it when it was first out e.g. it the screen used to go black and not re-light untill you placed it on a table or the other person hung up)
I would be suprised if 3 phones have the same fault unless it SW related :-D
Click to expand...
Click to collapse
the solution with the desire was an software update ?

Milini said:
HTC's new Windows phone seems to have a similar error with the proximity sensor:
As I'm a new user I'm not allowed to post a working link. I try to write it so the system accept it.
http://www.techeye.net/mobile/one-day-after-launch-event-windows-phone-bug-spotted
If this turns out to be true it's more hardware related than software, isn't it?
Click to expand...
Click to collapse
There you go proper link and welcome!

liorra3 said:
i think to cancel my DHD order until that issue will check.
the solution with the desire was an software update ?
Click to expand...
Click to collapse
Yep was solved with a S/W update

You can add one more to the list. Friend of mine had the same problem with his proximity meter. I will receive my D-HD either tomorrow or the day after, I'll let you know if it works properly.

mach03 said:
You can add one more to the list. Friend of mine had the same problem with his proximity meter. I will receive my D-HD either tomorrow or the day after, I'll let you know if it works properly.
Click to expand...
Click to collapse
Keep in mind, my device worked as it should the first day...

i don't understand how it can work fine one day and the following day it messes up lol

Apache14 said:
Yep was solved with a S/W update
Click to expand...
Click to collapse
hee
sorry for the noob one, but s/w - is ? they need make some software update ? or replace the phone ?

liorra3 said:
hee
sorry for the noob one, but s/w - is ? they need make some software update ? or replace the phone ?
Click to expand...
Click to collapse
s/w is software... you practically answered your own question

[Q] Black screen on HTC Desire

Hi guys
i have a strange issue on my device,since stock ROM i guess, the problem is follows:
my screen just go black sometimes i thing it happend only when a call is in progress or when call is ended by the third part, the screen just stay black and no solution but uplug battery and start up the phone
i had this problem eaven on my stock Rom froyo 2.2, then i try leedroid 2.3 and it was ok i guess, then i try oxygen rc6 everything works superb,fast,clean,smooth but the black screen occures multiple times in one day (today around 3 times) so i was forced to return to my stock froyo 2.2 and hopes will be ok,
the problem is as i search thru internet... seems like one of the sensors works baddly, i think is the proximity sensor, what can i do? should i sent my device to repair? i realy appriciate any help and suggestions and ideas how can fix this problem....

still no solution it happens on stock froyo 2.2 too but in smaller period as on oxygen rc6, i try set --- display off to value 30 minute from previously 2 minutes and problem dont occured for last 2 days

this might seem like an ovbious answer but when your making a call the desire has a light/proximity sensor to the left of the top htc logo that turns the screen black when it senses something, this is to stop you pushing buttons with your ear.
i dont mean to insult your intelligence or anything, just saying ya know if it happens when not in a call it sounds like a software issue

i already know that, searchin a lot about this problem mate trust me, i also know when the proximity sensor is located and what is his function but the issue happening only when a call is made never happend just like that so i thing no sw prob, using stock froyo 2.2 now no root just a clean official and it happens like 2 times per day when i was calling more that 2 minutes when i set in setting--display to turn off screen in 10 minutes this problem dont show up soo i dont know realy maybe i sent my device to reklamation will see

This happens me with root and without root. It's when your using anything that has with the SD card to do with. Like the gallery, it has gone black for me to under a call though... I dont know how to fix this problem, and it's very frustrating to take out the battery all the time.

My friend i am working in mobiles but i couldn't guess the problem cause i bought my cousin this HTC desire until she removed the screen guard (( the plastic sticker for protect the screen)) from the screen and i solved the problem so easily.
Best of luck

true is that i am using Zagg shield, but this cannot solve the problem cuz i try few days without any screen protector and the problem was still there,
but i guess i solve this problem few months ago, i notice that the black screen after call happend when my network is set to "GSM only" strange but since i use WCDMA only the problem is gone, dont know surely but guessing, also when i use mobile network in gsm only mod, phone freezes totaly and only unplug battery helps, as i said since i am using wcdma/hsdpa/3g only non of these strange thing happens
hope this help for someone

AssassinSvK said:
true is that i am using Zagg shield, but this cannot solve the problem cuz i try few days without any screen protector and the problem was still there,
but i guess i solve this problem few months ago, i notice that the black screen after call happend when my network is set to "GSM only" strange but since i use WCDMA only the problem is gone, dont know surely but guessing, also when i use mobile network in gsm only mod, phone freezes totaly and only unplug battery helps, as i said since i am using wcdma/hsdpa/3g only non of these strange thing happens
hope this help for someone
Click to expand...
Click to collapse
Hi, guy!!
I've the same problem several months ago. Have you solved by using WCDMA only??
Thanks

Hi all,
This was happen to me last few day and i google whole world, finally i find my answer and i hope it was help for those who facing this kind of problem.
I can confirm this problem no related to rooted or without rooted phone. this problem definitely come from the proximity sensor which people highlighted this sensor located at top left of htc logo which u can see a blue color circle there.
Try watch this video of disassemble htc desire and you will find the way to clean this proximity sensor area.
Tools to use for dis-assembly:
1. Philips screw driver.
2. Torx screw driver
Cleaning tools:
1. a wet small cotton buds.
Hope this method can help.
Area to clean:
1. The proximity sensor which you will see covered by a black rubber
2. The casing area which i show on photo.
Disassembly Video:
youtube.com/watch?v=sXZqIjtFoAU
i231.photobucket.com/albums/ee126/nkh73925/untitled.jpg
I were unable to post due to spamming protection system from XDA. Please add urlsef the http.

screen wont come back on during call

my wife has the att nitro hd, when the screen goes off during a call sometimes nothing including power button will turn it back on. Anyone know of a fix? did the ATT small update fix this?
Actually it comes back on after a long minute or two. Not very helpful if you need the dialpad or keys, etc.
I have just rooted it for her and installed CWM.
I have added a few proximity tweaks to build.prop
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
I'll have to take alook into the lg hidden dialer menu to see if I can disable this.
I dont like this sensor on my device either, but I have an option in settings to disable it, which makes it bearable.
thanks for the help guys.
I have noticied LG throws together some junky builds, typos, bad english/grammar. Wonky sensors etc. Incorrect kernel build ReadMe's
I thought I recall someone with another device just placing a peice of tape over the sensor. hmmm..worth a try.
cheers.

chrisrotolo said:
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
Click to expand...
Click to collapse
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****

aremcee said:
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****
Click to expand...
Click to collapse
What about the tweaks that aren't BS? Are they already included in your CM9 builds?

From what I can tell, pretty much the main thing that build.prop is good for is providing information about the system and software (i.e. info about the build). It's not really used much for useful configurations as far as I know.

networks tweaks actually have doubled me download speed.
I still have faith.
but can anyone answer my questions I posted in ICS SLim thread and PM'ed Andasa , no responses yet.
does ICS slim or CM9 have option to keep lcd no during call? and does it work??
what's working not working? I found changelogs but not a working/not working list for CM9.
and has anyone successfully restored a nandroid from ICS to GB without real issues?
thanks guys.

i doubt the ota fixed your issue as the issue is not one that occurs for every nitro.
I can tell you that when I make a phone call they screen stays no.
what's working not working, well, many of us are running it daily with no probs.
as you prolly know, it is a nightly build so a public list of what's working or not isn't rly part of the deal.
i've succesfully restore a nandroid from both slim and cm9 back to the stock att rom and others many many times. dozens.

thanks good enough.
I will have to give it a go.
would you recommend one or the other?
CM9 or slim?
thank you.

well, I like them both a lot. slim is just a trimmed down version of cm9 and i _think_ it does run just a bit snappier........maybe..but it's not wildly different from cm9. I usually switch back&forth throughout the day.

There's no setting in CM9 to disable the proximity sensor, although there may be a way to do it.

We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?

no driver said:
We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?
Click to expand...
Click to collapse
If you bought it from a store, get it exchanged for a new one.

actually works much faster on cm9, but therr still should be an optin to keep lcd on during call. i found some free apps that will disable hardware drivers but cant find the name of the proximity sensor driver, only that is named LGE.

Unfortunately it was given to us by a friend after my wife lost her Captivate, so taking it to a store to exchange is probably not going to work too well. As far as I can tell it was never used before we got it--the battery was still in it's own sealed pouch, the texting and driving warning was on the phone, and the phone went through the whole initial setup routine--but they didn't send us the box, I guess to cut down on mailing costs. I was hoping there was a known solution.

Ok, I downloaded two proximity sensor test apps today, but neither showed any activity. On my Captivate I get different readings with Proximity Sensor Finder (market link), but on the Nitro it is stuck at 3cm and it doesn't register anything no matter where I put my hand over the phone.
Can someone whose phone works right try installing this app and make sure that it picks up different readings on this device? OP, if you are still having issues, can you also try this app and see if it is static for you?
Thanks.

Took off the screen protector that they installed at the AT&T store and now the proximity sensor works just fine. OP, do you have a screen protector on your device?

we had an awfully thick one from att. we have since changed it to a super thin one. screen off is not a real problem on cm9, however i feel all devices should have the option to disable proximity sensor/keep lcd on during calls.

It's worth trying to use the warranty on the phone. Even though you dont have the original sales reciept, the phone has been released for less than a year, so no matter when you bought it, it is still within it's year long guaranteed warranty window.
Finished reading the thread, I suppose this post is now irrelevent

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

screen turns black on incoming call

Hello good day. When I receive a call to my redmi note 8 device, the screen turns black before I bring the phone to my ear. I wake up the device with the help of a button or fingerprint. I am getting information about the sensor setting. but it didn't work. I get a calibrated error message. previously i was using india original update now i am using xiaom.eu stabil 12. i am getting the same error. please help. thanks

I have the same problem. Try installing the latest firmware. It didn't work for me. A quick work around is to quickly cover and uncover the top portion of the phone where the proximity sensor is located (near the selfie camera). The phone screen should come back on. I really wish this would get fixed for the numerous people that have this issue.

tripper22 said:
I have the same problem. Try installing the latest firmware. It didn't work for me. A quick work around is to quickly cover and uncover the top portion of the phone where the proximity sensor is located (near the selfie camera). The phone screen should come back on. I really wish this would get fixed for the numerous people that have this issue.
Click to expand...
Click to collapse
Thank you for your answer. i'm loading other roms. In a few days the problem starts again. So I wonder if there is the same problem with other xiaomi models?

mesut0114 said:
Thank you for your answer. i'm loading other roms. In a few days the problem starts again. So I wonder if there is the same problem with other xiaomi models?
Click to expand...
Click to collapse
I forgot to mention that you shouldn't have any kind of screen protector on your phone when you are trying to figure this out. I don't know about other models. I've had the exact same problem with two different RN8's. It's either a bad batch of proximity / light sensors or it's a firmware / software problem that is yet to be resolved. I have done a full search of this forum and numerous users have the same issue we do. Nobody has a fix as far as I know. Please let me know if you learn anything new.