8.1 Update broke proximity sensor ?? - Google Pixel 2 XL Questions & Answers

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.

Related

[Q] Proximity sensor problem(?)- can flashing a ROM solve it?

Hi,
I've searched high and wide for a solution (other than sending it back to Motofailure repair) and am failing at finding one so far. So I'm hoping I can get some help from here.
So, this is the situation: I make a call, screen instantly turns dark and will only light up again when I press on the area where the light (&) proximity sensor is.
I've already tried the following.
1.) Done a factory reset (3x) - with mem card, with reformatted mem card, w/o mem card.
2.) Clearing the dust on the earpiece hole using an air duster.
3.) There were times that I worked properly after I've uninstalled apps but the issue came about again after a couple of tries.
So, now I'm thinking that I might want to root my Defy to set things right. I'm quite familiar with RSD Lite as I've used it before on my RAZR2 V8.
A bit of background: I bought my Defy on pre-order so this is one of the earlier models. I had the earpiece problem and sent it to Motofailure repair and the whole process took a month (32 days to be exact - long story. I'm avoiding having to send this PoS back. They updated the software when I got it back.
As far as I can recall, I didn't had this problem before the earpiece problem. And I'm thinking it might be a software problem hence I'm now looking at a solution by rooting and flashing the ROM with an original one.
I have no way of finding out (as far as I know) whether this is a hardware problem (hence hesitating to have it sent back to Motofailure repair).
What I've also observed is that when there is direct bright light, it works normally but when its dim, then the problem appears.
I don't have any screen protectors, just so you know.
Can anyone advise me on what to do?
During a call proximity sensor is activated to turn off the screen at the moment it detects proximity and asumes you are using the phone against your hear, so it turns off screen to save energy.
I think you might have some app installed in your phone, using and reversing the sensor status so it detects proximity when there isnt, and viceversa
You might want to try removing apps using that sensor and see if problem gets solved, there is also an app in the masket called sanity; which makes extensive use of proximity sensor for vaqrious things, and have an option to reverse proximity sensor, you might want to try it and see if problem gets fixed.
You might try this things: remove apps using proximity sensor, test phone. Deactivate in pocket detection; test phone, and install sainity, test phone, install a new rom?
If speaker is bigger than original one, or there was an assembly error, light/proximity sensor won't fit into right place.
I've seen such reports and you can't do anything unless you open up thing and check the problem, but you haven't seen the right assembly so you may not know the right place.
Are you using any screen protector? I know some screen protectors cause this problem.
Edit: Nevermind, I see that you're not using any.
how to calibrate the proximity sensor?
My new defy 's proximity sensor seems cannot work correctly,when i making a call ,the screen shut off immediately,and the screen could not light on by any key,but when i touch the proximity sensor with my finger,the screen may be light on!
so i download a app to test the proximity sensor which name's"Android sensor data",this app fingue out the state of proximity sensor,"near" or "far",sometimes I just passing my finger over the proximity sensor, the reading will show 'near' and then remain 'near' even when my finger is moved away!
Can anyone else help me to calibrate the proximity sensor?google told me some android phone can do this ,such as htc, zte etc.
goole tell me android phone have some standard testcode,such as *#*#4636#*#* can show the phone statue,it works correstly in Defy,*#*#0588#*#* test the proximity sensor ,but it doesn't work in defy!!!
I don't think this issue could be solved trough software tweaks. Chances are this is a hardware problem. Maybe you should contact the Motorola support.
try disabling in-pocket detection
have the same problem. it started 2 days ago. Im using CM7. It just turns dark and wont wake up unless someone else is calling me. Just got it tested, and when i cover the sensor with my finger it says 0cm distance for long time.
I've tried data wipe and similar, but nothing helped so far.
EDIT: I've just tried wiping the place where proximity sensor is with some soft cloth and alcohol and for the time being, it works. O.O
Could Wipe Dalvik help?

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

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!

Proximity sensor issues?

Hey everyone. I'm enjoying this phone but I do have a few small issues which I'm hoping I can forget about once custom ROMs start to come out
(Come on and release factory images already Razer!!!)
One of them is the proximity sensor which I find incorrectly thinks I've taken my head away from the earpiece during a call and then starts spamming commands with my cheeks.
I have this issue on like every second phone call and it's a bit irritating. Especially when I still haven't received (other than the first one when I first got the phone) any more updates.
The other main gripe is the lack of a pocket sensor/script. Probably related. As in, if you have double tap to wake enabled, good luck putting this in an awkward pocket (inside motorbike jacket pocket) without waking the screen and spamming commands again with your fingers.
Lastly. I wish they had just put the fingerprint sensor somewhere else. I have turned the screen off so many times while watching YouTube it's actually starting to really annoy me
Just wondering, even if you like this phone overall, and I do, if anyone else had these gripes?
I'm having the same issue with a Razer phone I picked up this week. It's a pain.
I've tried using this as advised on another thread and it seems to be working fine, so I'm totally lost.
https://play.google.com/store/apps/details?id=ru.andr7e.sensortest
Handaloo said:
I'm having the same issue with a Razer phone I picked up this week. It's a pain.
I've tried using this as advised on another thread and it seems to be working fine, so I'm totally lost.
https://play.google.com/store/apps/details?id=ru.andr7e.sensortest
Click to expand...
Click to collapse
I'm just glad to hear someone else is noticing this. Does nobody else make phone calls on their phones??
Had the issue with the proximity sensor on a phone call again last night. Realllly annoying.
At least factory images are out now, unfortunately, it took so long, developers etc don't look too bothered about this device - I may be wrong and would be delighted to start seeing some custom stuff out there. So long as they can keep the 120Hz functionality!
Yeah I would definitely be tempted if a good Rom was released. You're probably right about it though, not a HUGE demand for these.
I've had it several times with calls and it will be super annoying if it doesn't get fixed with an update soon. I'll give you a shout if I get anywhere with it outside of this thread.
EDIT:
And yet, I just took two calls this morning back to back with ZERO issues.
anyone any more luck on this?
nk33 said:
anyone any more luck on this?
Click to expand...
Click to collapse
Nope. I still get these issues from time to time.
I even switched to global ROM and they exist there too.
Hi all.
This issue was resolved on my phone with a hard reset (volume up + power button), then a factory reset (in settings -> system -> reset options ). The proximity sensor now works as it is supposed to.
Hope this helps.

Proximity sensor bug

After the update I'm having trouble with the proximity sensor. It stops suddenly. Usually when I put the smartphone in the pocket. It was perfect before 172 firmware. Anybody notice anything? Any tips? I have the EVRL29. I also made a factory reset.
Lord_Maumad said:
After the update I'm having trouble with the proximity sensor. It stops suddenly. Usually when I put the smartphone in the pocket. It was perfect before 172 firmware. Anybody notice anything? Any tips? I have the EVRL29. I also made a factory reset.
Click to expand...
Click to collapse
Hey, you can use the APP that comes with your phone to check if the proximity sensor fails.
How to open it: HiCare-Service-Smart diagnosis-Auto
Good luck
Thanks, But everything's fine with the sensor as Hicare. I don't believe it's a hardware problem, but I don't know what I can do about the system.
Lord_Maumad said:
Thanks, But everything's fine with the sensor as Hicare. I don't believe it's a hardware problem, but I don't know what I can do about the system.
Click to expand...
Click to collapse
Do you have a black screen when you are talking?
When the sensor is locked, no. Sometimes the screen turns black immediately when I get the phone call. That is, the sensor is locked. Passing the finger over the sensor a few times, it unlocks and goes back to work.
Having the same issue. I thought it was because of Drupe (am using it instead of default dialer). Weirdly, proximity sensor activates even before attending the call sometimes and am not able to do anything. Just let the call ring it out and then have to call back as even locking/unlocking doesnt work.
have upgraded to version 184 and the problem continues. I don't know what to do. Disappointment with Huawei
cashif said:
Having the same issue. I thought it was because of Drupe (am using it instead of default dialer). Weirdly, proximity sensor activates even before attending the call sometimes and am not able to do anything. Just let the call ring it out and then have to call back as even locking/unlocking doesnt work.
Click to expand...
Click to collapse
Hi, did you solve the problem? I downgraded and it worked again, so I decided to upgrade and it stopped again
Lord_Maumad said:
Hi, did you solve the problem? I downgraded and it worked again, so I decided to upgrade and it stopped again
Click to expand...
Click to collapse
Problem stopped after updating to latest firmware 184 version
Lord_Maumad said:
After the update I'm having trouble with the proximity sensor. It stops suddenly. Usually when I put the smartphone in the pocket. It was perfect before 172 firmware. Anybody notice anything? Any tips? I have the EVRL29. I also made a factory reset.
Click to expand...
Click to collapse
Are you using full cover tempered glass screen protector?
Unfortunately I'm not ?
I don't know if it is updated firmware bug or hardware failure. My friend's phone has this problem too, and even worse when dialing or listening to voice SMS in FB messenger, the screen was off until the voice finished. I thought it was full cover screen protector; however, it was not after I suggested him to take off the screen protector, and the problem still persisted. Anyway he told me there was not any problem before updating.
Lord_Maumad said:
Unfortunately I'm not
Click to expand...
Click to collapse
Are you using full cover tempered glass screen protector?In addition, can you check whether the position of your sensor is clean.
I'm not, and it's clean. It works until I put it in my pocket, then it gets stuck.
Today I realized one thing, if I touch the screen where the sensor is for more than 2 seconds, it hangs. If I stay near, it works ?
Lord_Maumad said:
Today I realized one thing, if I touch the screen where the sensor is for more than 2 seconds, it hangs. If I stay near, it works ?
Click to expand...
Click to collapse
My friend just sold his mate 20x with proximity sensor error and bought a new one with the same firmware version 9.0.0.184. The new one worked functionally with its proximity sensor. I think that his previous mate 20x had proximity sensor hardware's problem, not dead but not functional.
Ich have the same issue with a P30 Pro New Edition. I hope it's a hardware issue and the replacement unit will be fine.

Categories

Resources