Develop Bugs

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

Unable to make or take calls properly on CM11

Please refer to this post:
http://forum.xda-developers.com/showpost.php?p=62828995&postcount=1432
Has anyone gotten this problem? The person who posted this has been the only one having this problem. This can't be a rare thing, is it? Is everyone just dealing with this issue until it gets fixed?

Here is a compilation of the comments made about this issue thus far. There seems to be a consensus that screen protectors are not causing this issue.
11th August 2015
AnotherContributor said:
One issue though I've been having is that when I'm making and receiving calls, sometimes the phone display goes black and will frankly not come back on. I press the App button and sometimes the display comes on, sends the call to the Status Bar, and the screen goes dark. So, I have to press the Application button again and draw down the menu to hang the call up. When I press the power button, the screen flashes on for maybe a quarter second then goes dark. It keeps doing that every time you press the power button. The worst case scenario that has happened a handful of times is that when I'm in a call, neither the power nor application button are responsive. When that happens, pretty much the only option is to power down the phone and reboot.
...
I'm not sure if I would be able to dial an extension with the way the phone is acting up. I feel like this was not an issue the first couple of weeks I had CM on the phone. Now, it seems to be happening with every call.
Click to expand...
Click to collapse
14th September 2015
samuraix21 said:
Hi, I have this issue. Were you able to fix this issue? You're the ONLY person that has posted this issue so I'm not sure if this is a rare hardware issue or everyone on this forum is somehow dealing with it until a fix comes up.
Click to expand...
Click to collapse
19th September 2015
hawk1500 said:
are people still experiencing the screen off during call problem? I am not talking about when you put it up to your face, but how the screen turns off and won't come back on?
Click to expand...
Click to collapse
20th September 2015
hawk1500 said:
Naw, no screen protector installed. tried the proximity sensor fix app as well as the xposed don't go to sleep during call module but it still does it.
Click to expand...
Click to collapse
20th September 2015
tonochito said:
i think that bugs should be listed more detailed:
front facing camera does not work well, if i want to take a selfie it crash. video camera also does not work equal it will crash. I had to install Google Camera and Open Camera in order to have both selfie and video options working, With Google Camera i take selfies and with Open Camera i record videos, As the guy talking about the scren off in calls is true, i don't have a screen protector and it has this behaivour, also as i mentioned there is kind of lag when i try to dial a number i have to do twice, it doesn't show up right away. The same goes when i am calling for example my carrier and i have to dial on the IVR i have to dial twice in order to get the dial keypad. I didn't have Google play crash.
Another thing that i notice was setting a wallpaper as screensaver does not fit in the middle or correctly i had to use Quick Pic and the option 768x1280 because with the stock gallery wallpapers are like aside of the middle
Click to expand...
Click to collapse

I think this issue needs some attention. I am having this problem as well (with and without screen protector). There are times that I need to enter extensions and codes during calls which has become impossible. I have two of these phones and they both behave this way. I recommend that people start posting screenshots of the app Proximity Sensor Finder which displays different distance numbers detected by the prox sensor. See my screenshot attachment which shows the proximity sensor always detecting a "covered" state of 0.0cm even when nothing is in front of the screen. Everyone should go try this and post their findings.
Other phones on CM11 were able to fix this problem in the past by adjusting the calibration which is unique for each phone, so I started searching around through the Fire Phone CM11 files and I found these:
/system/etc/permissions/android.hardware.sensor.proximity.xml
I could not discern anything of value from this .xml file.
/persist/sensor_calibration/SHCAL_DU20060142640727.csv
This file seemed promising. Its timestamp is back in 2014 so I assume that this comes straight from the original Fire Phone files. If this file is actively used to govern sensor behavior, I'm wondering if perhaps it is not being read correctly. It makes me wonder if there is a log out there somewhere that could shed more light on it. Anyways, you can open up that badboy in any spreadsheet to discover sensor IDs for a bunch of sensors along with calibration coefficients in the form of:
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=550.30
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=395.62
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=19262.26
You'll have to open it and analyze it in context of the other columns and other sensors. I've attached it (re-saved in xlsx format because .csv files are not permitted - if you don't trust my xlsx just retrieve the file from your phone). I highlighted the rows of interest. We could just mess with coefficient values, but without any guidance, it could just be a waste of time. Plus we don't know if this even governs the sensors or if it's just helpful documentation. If anyone has insight about this or even far fetched theories, please comment!
I'm thinking about doing a 'grep' on the entire file tree for some of these key words like SENSOR_ID=SI1143, SI1143, 4CCU1, COEFF0, SENSOR_TYPE=PROX etc etc - to see if any files use any of these terms. It may prove unfruitful due to the amount of compiled software that is no longer in text form. Any thoughts about any of this?

i have this screen always making a call with any cm11 i have used in the past, i have to press back and again the keypad and works normal, same when i have to dial a number

tonochito said:
i have this screen always making a call with any cm11 i have used in the past, i have to press back and again the keypad and works normal, same when i have to dial a number
Click to expand...
Click to collapse
But if the prox sensor is always detecting a "covered" state, then it completely disables the screen during a call and we are unable to press "back". Could you post your findings from running Proximity Sensor Finder from CM11 Fire Phone?

jdmillard said:
But if the prox sensor is always detecting a "covered" state, then it completely disables the screen during a call and we are unable to press "back". Could you post your findings from running Proximity Sensor Finder from CM11 Fire Phone?
Click to expand...
Click to collapse
i will give a shot, and post my result

In fact, it would be AWESOME if we could get someone (whose screen does behave perfectly during calls) to post their findings from Proximity Sensor Finder. If their screen works perfectly during calls and this app shows 0.0cm all the time for them too, then we can conclude that this app isn't functioning correctly and we know we need to find our root cause elsewhere.

tonochito said:
i will give a shot, and post my result
Click to expand...
Click to collapse
Available but why it doesn't work right?

tonochito said:
Available but why it doesn't work right?
Click to expand...
Click to collapse
Interesting. Is it stuck on 10.00061 even when you cover the front of your phone with your hand? Or does the number fluctuate?
Which ROM build are you on? (I should say, which publish date?)

jdmillard said:
Interesting. Is it stuck on 10.00061 even when you cover the front of your phone with your hand? Or does the number fluctuate?
Which ROM build are you on? (I should say, which publish date?)
Click to expand...
Click to collapse
yes weird it is stuck no matter what i do, well if i put my finger in the "first camera" of the phoen it goes to zero

tonochito said:
yes weird it is stuck no matter what i do, well if i put my finger in the "first camera" of the phoen it goes to zero
Click to expand...
Click to collapse
That suggests to me that the sensor is "all or none" meaning it doesn't bother detecting intermediate values, rather it just has a threshold that determines a covered or not covered state. That seems normal to me. I need to get mine to do that.
Does your screen behave normally during calls? Specifically, does the screen turn on when you pull the phone away from your face?

jdmillard said:
That suggests to me that the sensor is "all or none" meaning it doesn't bother detecting intermediate values, rather it just has a threshold that determines a covered or not covered state. That seems normal to me. I need to get mine to do that.
Does your screen behave normally during calls? Specifically, does the screen turn on when you pull the phone away from your face?
Click to expand...
Click to collapse
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls

I just removed my glass screen protector and now mine behaves just as yours. Which is good that it functions as expected, but also a disappointment about the screen protector. I just looked to request a refund and it appears that they have an excellent return policy so I'm not too worried about it. Now I just need to find a screen protector that doesn't cover the prox sensor. ... sigh.
I'm still interested to see what happens with what you were describing: like how the screen would still behave finicky. I'll keep an eye out for that behavior and I'll let you know if I discover anything about it.
---------- Post added at 01:26 PM ---------- Previous post was at 12:38 PM ----------
tonochito said:
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls
Click to expand...
Click to collapse
I forgot to say thanks! You posting your results helped me figure out where I was going wrong. Gracias!

jdmillard said:
I just removed my glass screen protector and now mine behaves just as yours. Which is good that it functions as expected, but also a disappointment about the screen protector. I just looked to request a refund and it appears that they have an excellent return policy so I'm not too worried about it. Now I just need to find a screen protector that doesn't cover the prox sensor. ... sigh.
I'm still interested to see what happens with what you were describing: like how the screen would still behave finicky. I'll keep an eye out for that behavior and I'll let you know if I discover anything about it.
---------- Post added at 01:26 PM ---------- Previous post was at 12:38 PM ----------
I forgot to say thanks! You posting your results helped me figure out where I was going wrong. Gracias!
Click to expand...
Click to collapse
your welcome

I have a glass protector and i noticed over time that i developed a specific technique for answering the phone. I sort of slowly move it close to my ear and then the sound comes on (hear ringing, able to hear caller). If i press the answer button then put it to my ear, most of the time i cant hear the caller but they CAN hear me.
Never even considered it being a sensor issue. I thought it was CM bug triggered by my setup somehow. I flashed this rom and put the glass screen on within a couple of days after receiving it in the mail and since touch-wise the tempered glass works perfectly it was never even a thought. Dont mean to go on but is anyone else dealing with issues like the one i describe? Whats strange is i dont recall having that black screen issue others are experiencing.

KLit75 said:
I have a glass protector and i noticed over time that i developed a specific technique for answering the phone. I sort of slowly move it close to my ear and then the sound comes on (hear ringing, able to hear caller). If i press the answer button then put it to my ear, most of the time i cant hear the caller but they CAN hear me.
Never even considered it being a sensor issue. I thought it was CM bug triggered by my setup somehow. I flashed this rom and put the glass screen on within a couple of days after receiving it in the mail and since touch-wise the tempered glass works perfectly it was never even a thought. Dont mean to go on but is anyone else dealing with issues like the one i describe? Whats strange is i dont recall having that black screen issue others are experiencing.
Click to expand...
Click to collapse
I was lucky enough to have a good return policy on the glass screen protectors I recently got (for two Fire Phones). I'm returning them today and I've already ordered this as a replacement:
http://www.amazon.com/gp/product/B00WXY18WK?psc=1&redirect=true&ref_=od_aui_detailpages00
It has excellent reviews, decent price, very thin, and it is specifically mentioned many times in the reviews that there is a little cutout for the prox sensor (and you can see if if you look carefully at the pictures). I'm hoping that it will solve my black screen woes and protect my screen. There are reports from folks on these forums saying that there is still some strange behavior during calls (such as your example among others). I personally haven't encountered what you're describing, but I'll keep an eye out to see if I can be of any help.

jdmillard said:
Here is a compilation of the comments made about this issue thus far. There seems to be a consensus that screen protectors are not causing this issue.
11th August 2015
14th September 2015
19th September 2015
20th September 2015
20th September 2015
Click to expand...
Click to collapse
Hi. I like to get back about this since I've been quoted on this.
For me, the glass protector screen that I brought from XtremeGuard was the issue my dad had when he tried to make or take calls. After I removed it, it was back to normal.
The persistent issues now, based on what my dad is telling me, is that sometimes after you dial in a number and call a person, you don't hear the ringing tone to know if it went through or not. My dad would freak out when someone on the other line said something since the ringing tone is not working.

tonochito said:
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls
Click to expand...
Click to collapse
hi
this is usually related to hardware composer.
cheers

superdragonpt said:
hi
this is usually related to hardware composer.
cheers
Click to expand...
Click to collapse
but why? does it matter with the bootloader, i mean i know the CM11 on the Fire phone still on beta with no NFC working and the camera too at least i am using Snap camera and everything works. But making calls is a bit annoying even i don't use the phone to make a lot of calls just for WhatsApp almost all the time

No notification LED after MM update on ZE551ML?

Maybe it is just me and my device, but since the MM update (the real one, not the beta) my notification LED doesn't work. I have tested it with text messages, emails, missed calls, charger plugged into my computer, charging plugged into a standard charger, and charging plugged into the fast charger... nada on any of them.
Anyone having this issue? If so how have you rectified it? It has been a minute since I first got this thing (got it at launch) and the MM update reset all my settings so maybe there is a setting to turn it back on I am missing?
Help out a brother if you can. Thanks.

OK, so does anyone have any suggestions for an app that might help by letting me manually setup the notification LED?

Is Do not disturb mode on?
Sent from my ASUS_Z00AD using XDA Premium HD app

madman604 said:
Is Do not disturb mode on?
Sent from my ASUS_Z00AD using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the reply. It is not in DND as far as I can tell (not on).

If you haven't already, try a factory reset first

Trotter516 said:
Thanks for the reply. It is not in DND as far as I can tell (not on).
Click to expand...
Click to collapse
Have you found a fix for that? Facing the same issue and so far no luck.

godzin said:
Have you found a fix for that? Facing the same issue and so far no luck.
Click to expand...
Click to collapse
Actually yes. After I wiped my phone for my wife the notification now works.
Another issue that I recently found the solution to... if your ZF2's proximity sensor has gotten crazy sensitive since the update try cleaning it. Seriously. Especially if you have a tempered glass screen protector. I thought the piece of advice was bogus but I cracked out my lens cleaning spray and cloth and BOOM, the proximity sensor works correctly again.

Trotter516 said:
Actually yes. After I wiped my phone for my wife the notification now works.
Another issue that I recently found the solution to... if your ZF2's proximity sensor has gotten crazy sensitive since the update try cleaning it. Seriously. Especially if you have a tempered glass screen protector. I thought the piece of advice was bogus but I cracked out my lens cleaning spray and cloth and BOOM, the proximity sensor works correctly again.
Click to expand...
Click to collapse
Thanks! Got the led working again after a factory reset.
By the proximity sensor do you mean the little one next to the selfie camera or the GPS?
After a lot of fixed I've got the ZF2 working fine, except for the "smartlock - safe places" that thing can never work right.

godzin said:
Thanks! Got the led working again after a factory reset.
By the proximity sensor do you mean the little one next to the selfie camera or the GPS?
After a lot of fixed I've got the ZF2 working fine, except for the "smartlock - safe places" that thing can never work right.
Click to expand...
Click to collapse
Sorry, I just realized that you had replied.
Yes, the one beside the camera. Many have had an issue where the screen goes black after you start or answer a call, especially after the update. It seems the update made the proximity sensor much more sensitive. Since all decent screen protectors have a small cutout for the proximity sensor it will tend to accumulate dirt and oil from your skin. Wiping it down doesn't seem to get it clean enough for the sensor so you have to get a little more aggressive to clear the problem up. I went months enduring the problem and even set my phone so I could disconnect from calls using the power button and then ended up stumbling over the solution when setting up the phone for my wife when I upgraded to my Axon 7.

No led indicator
Hi i've been experiencing the same issue. After I update my zenfone 2 ZE551ML 4gb/64gb version, I have noticed that the led incator is not working and it is not found in the settings. Also, another issue I have encountered is that quick charging feature is not working sometimes but sometimes it works. I don't know how to fix. I'd be glad if someone could help with a step by step process. Thanks in advance!

8.1 Update broke proximity sensor ??

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.