According to this article, the Oneplus 7 Pro does not have an optical/IR/hardware proximity sensor:
Optical hardware proximity sensors have been around since the dawn of the smartphone and are used to turn off the screen and disable touch functionality when a user is in-call. Since they typically rely on infrared hardware sensors, they require unsightly holes on the front of the phone in order to function. In contrast, Elliptic Labs’ patented software-based virtual smart sensors possess no such handicap, providing cleaner design while simultaneously offering support for additional features such as gesture and presence detection through its proprietary fusion of sensor data, AI, and machine learning.
Click to expand...
Click to collapse
This would seem to indicate that the procedures espoused in various threads related to proximity sensor calibration via the factory test menu (*#808#) are not actually doing anything, and that also the various suggestions that the sensor is behind the display are erroneously based on information related to other phones.
Using an app that let me read the proximity sensor, my own (albeit limited) testing seems to confirm this notion in that covering the display with your hand does not trigger the proximity sensor (regardless of the position of the phone). However, I can get it to react when I bring it to my ear. My guess is that the motion sensors are being relied upon, and possibly the microphone as well (to detect noise level changes when the phone it brought close to the face). Additionally, the reading is ever only 0 or 5 cm - nothing in between - which further lends credence to the lack of hardware.
I cannot account for why some people are saying that running the proximity sensor test somehow fixes double tab to wake issues, but given that many others seem to have limited or no success with this method leads me to suspect the reasoning is fallacious (post hoc, ergo propter hoc). (I'm not trying to cast aspersions, and mean no offense.)
Don't know about that, but every phone that I ever owned have always shown 0 or 5 on proximity sensor tests. So, that's not a good indication for your theory.
Just adding some information, not saying you are wrong or anything. I honestly don't know.
It seems like what they are doing is using the earpiece as the proximity sensor but only when the device is held up to the ear.
If you download the app "sensors multitool" on Google play and look at proximity, you can see covering the earpiece with a piece of paper does nothing until the phone is in an upright position.
The thing is, the phone also has an ir proximity sensor under the screen but it seems that they have disabled it in the latest 9.5.8 because before cpuz and other tests would make it visible in the upper middle-right of the screen but after updating to 9.5.8, it no longer works. Would also explain why you can't go into the calibration settings for it anymore.
Edit: if you select light sensor in the multitool app, you can cover the upper right portion of the screen with a piece of paper or something else and see the value go down and then back up when you uncover it. That's the ir proximity sensor as well.
And here's another thing. Attached is a screenshot from the ifixit oneplus 7 pro teardown video. When they remove the motherboard, you can clearly see the two cutouts in the display for the ir proximity sensor/lux sensor on the top right (left on screenshot because back of display)
jdhedden said:
According to this article, the Oneplus 7 Pro does not have an optical/IR/hardware proximity sensor:
This would seem to indicate that the procedures espoused in various threads related to proximity sensor calibration via the factory test menu (*#808#) are not actually doing anything, and that also the various suggestions that the sensor is behind the display are erroneously based on information related to other phones.
Using an app that let me read the proximity sensor, my own (albeit limited) testing seems to confirm this notion in that covering the display with your hand does not trigger the proximity sensor (regardless of the position of the phone). However, I can get it to react when I bring it to my ear. My guess is that the motion sensors are being relied upon, and possibly the microphone as well (to detect noise level changes when the phone it brought close to the face). Additionally, the reading is ever only 0 or 5 cm - nothing in between - which further lends credence to the lack of hardware.
I cannot account for why some people are saying that running the proximity sensor test somehow fixes double tab to wake issues, but given that many others seem to have limited or no success with this method leads me to suspect the reasoning is fallacious (post hoc, ergo propter hoc). (I'm not trying to cast aspersions, and mean no offense.)
Click to expand...
Click to collapse
Interesting theory, but this device definitely does have an infrared proximity sensor. Just open CPU-Z and raise the phone up like you're making a call, then take a picture of the screen with another phone.
Related
Is it possible to remove fingerprint from aod on p30 pro without removing fingerprint sign in? I can't find settings for it...
I don't know about yours, but mine isn't there until I pick up the phone or touch the screen?
If you want to completely remove it then you can't - the way the finger print sensor works requires the screen to light up at max brightness under your finger so it can capture the fingerprint with the optical sensor.
Watch the 'JerryRigEverything' YouTube teardown to find out more info on how it works, but when scanning for a fingerprint it needs the illumination
milosmeda said:
Is it possible to remove fingerprint from aod on p30 pro without removing fingerprint sign in? I can't find settings for it...
Click to expand...
Click to collapse
I was wondering this too as I'm starting to get slight screen burn from a combination of that and the intense light required to unlock. My S10+ has an option to turn it off, and muscle memory dictates that it isn't really necessary after a few days of use.
leoni1980 said:
I was wondering this too as I'm starting to get slight screen burn from a combination of that and the intense light required to unlock. My S10+ has an option to turn it off, and muscle memory dictates that it isn't really necessary after a few days of use.
Click to expand...
Click to collapse
As I said above, the reason for the intense light is that it uses and optical sensor rather than an ultrasonic sensor (as used in the S10+). Without the light it simply will not be able to see fingerprints.
NJ72 said:
As I said above, the reason for the intense light is that it uses and optical sensor rather than an ultrasonic sensor (as used in the S10+). Without the light it simply will not be able to see fingerprints.
Click to expand...
Click to collapse
I understand that but I'd like to at least be able to turn off the fingerprint indicator. I hold my phone in my hand most of the day so it's a bit annoying that it pops up every time you move the phone. You can switch off this indicator on the S10 and it has nothing to do with the technology - it's just a guide.
I am having an issue where always on display is staying ON while in pocket/faced down on the table. Feels like the proximity sensor is not working while on the AOD.
Plus, the proximity sensor doesn't seem to work while in the pocket either. The setting 'prevent accidental touches' has been enabled, however it is still responding to 'double tap to wake' while in the pocket for whatever reason...
Is there any fix to this?
I noticed the AOD stays on in my pocket as well. I thought maybe it was by design that way, even though it makes no sense.
Have not had a single pocket wakeup though.
It does seem that the proximity sensor (which is really the camera) doesn't work especially well though, from reports of people noticing it on phone calls. Hopefully something that can be fixed in software.
jdock said:
I noticed the AOD stays on in my pocket as well. I thought maybe it was by design that way, even though it makes no sense.
Have not had a single pocket wakeup though.
It does seem that the proximity sensor (which is really the camera) doesn't work especially well though, from reports of people noticing it on phone calls. Hopefully something that can be fixed in software.
Click to expand...
Click to collapse
Thanks mate, appreciate your feedback. Proximity sensor works fine on my phone during calls. Can't think of any reason why Samsung would intend it this way...
Proximity sensor issue here as well
I have the same problem. I put phone into test mode and it was bad compared to my wife's s9 search proximity sensor s20fe on YouTube and see others with issue
There is no fix. This is apparently the way AOD works now. I can't remember if it started with the S10s or S20s.
uggies said:
I am having an issue where always on display is staying ON while in pocket/faced down on the table. Feels like the proximity sensor is not working while on the AOD.
Plus, the proximity sensor doesn't seem to work while in the pocket either. The setting 'prevent accidental touches' has been enabled, however it is still responding to 'double tap to wake' while in the pocket for whatever reason...
Is there any fix to this?
Click to expand...
Click to collapse
I did some research on s20fe proximity sensor, because I desperately wanted flip case to open and close the screen.
Here is what I have noticed: there are two "proximity sensors" both sides of the front camera. These sensors close the screen during call if you touch them (I'm not sure if it's enough to touch just 1 or do you have to touch both of them). You need to touch these with your cheek or finger cause they need a electric field.
Phone also utilizes front camera light sensor during call: if there is no light, it turns off the screen but for this to happen phone needs to be on up right position. Screen won't close if the phone is on desk and you cover the camera.
So anyways, my point is that the proximity sensor is not able to detect if your phone is in the pocket or not. Only way for the phone to detect this is with the front camera light sensor, and I guess this would increase the battery consumption so much, there is no point.
You can test your "proximity sensors" by typing *#0*# in dialer numpad, select sensors and touch from the side of the front camera. If the screen turns green sensors are working.
No problems with Verizon S20 FE 5G UW
Huberttus said:
I did some research on s20fe proximity sensor, because I desperately wanted flip case to open and close the screen.
Here is what I have noticed: there are two "proximity sensors" both sides of the front camera. These sensors close the screen during call if you touch them (I'm not sure if it's enough to touch just 1 or do you have to touch both of them). You need to touch these with your cheek or finger cause they need a electric field.
Phone also utilizes front camera light sensor during call: if there is no light, it turns off the screen but for this to happen phone needs to be on up right position. Screen won't close if the phone is on desk and you cover the camera.
So anyways, my point is that the proximity sensor is not able to detect if your phone is in the pocket or not. Only way for the phone to detect this is with the front camera light sensor, and I guess this would increase the battery consumption so much, there is no point.
You can test your "proximity sensors" by typing *#0*# in dialer numpad, select sensors and touch from the side of the front camera. If the screen turns green sensors are working.
Click to expand...
Click to collapse
I just purchased the Samsung S20 FE 5G UW (how about we shorten this to FE UW?) with all updates AND a glass screen protector and have no touch/proximity issues.
FYI I bought it at the Costco kiosk for a few dollars less per month, no activation charges and a 90 day return policy.
the Galaxy S20 FE (5G) has no physiscal proximity sensor.
Insted it uses a combination of the front camera, touch screen and gyroscope.
I have tested the proximity issues, luckily for me there were ok...turn green. The only thing that drive me crazy is the touch screen issues which never been fixed even after updates. Oh well at least its better than before.
Huberttus said:
I did some research on s20fe proximity sensor, because I desperately wanted flip case to open and close the screen.
Here is what I have noticed: there are two "proximity sensors" both sides of the front camera. These sensors close the screen during call if you touch them (I'm not sure if it's enough to touch just 1 or do you have to touch both of them). You need to touch these with your cheek or finger cause they need a electric field.
Phone also utilizes front camera light sensor during call: if there is no light, it turns off the screen but for this to happen phone needs to be on up right position. Screen won't close if the phone is on desk and you cover the camera.
So anyways, my point is that the proximity sensor is not able to detect if your phone is in the pocket or not. Only way for the phone to detect this is with the front camera light sensor, and I guess this would increase the battery consumption so much, there is no point.
You can test your "proximity sensors" by typing *#0*# in dialer numpad, select sensors and touch from the side of the front camera. If the screen turns green sensors are working.
Click to expand...
Click to collapse
Mate great information here, really appreciate this.
Tested the Proximity sensor using *#0*#, I agree with your analysis. The proximity must be using electric reaction to detect if my ears are touching it or not. Covering it with a book does not trigger a proximity sensor... This explain why my screen keeps waking up in the pocket.
As much as this is annoying, there appears to be no way out Just have to let the phone face outside rather than my legs.
I also have the same issue, while on a phone call, the phone's screen goes on and off constantly and I can see the notification bar moving. Very annoying.
This is a terrible design by Samsung. The punch hole usually goes in the "Empty" part of the ear, so the screen stays mostly on.
I might just return the phone because of this issue, I don't see it getting fixed by a software update.
I have the exact opposite issue with the proximity sensor on my Samsung S20 plus running Android 10 - i.e. it works well by turning the screen off when my ear/cheek/face is very close to the proximity sensor during phone calls; whereas, when the phone's screen is locked and turned off, the proximity sensor is turned off as well. Control by hardware? Software/firmware? Don't know?! To turn the screen on without using the Power hardware button, I had to enable the "Double Tap" feature in Settings.
On earlier/other Android mobile devices - Samsung included - the proximity sensor is always on - whether the screen is on, off, or currently locked. When it's always on, you can be innovative and build a widget, for instance, to turn the screen on by "waving" your hand above the proximity sensor to interrupt the laser. I suspect new(er) Samsung mobile devices like S20 and Note20 variants might be using a "virtual" proximity sensor setup/combo for controlling the device's screen - and that really sucks!
To test if the proximity sensor is always activated on Samsung S20 and Note20 variants, I type *#77692# - which displayed a hardware screen to test proximity and light sensors. Note: if you type *#0*#, the proximity and light sensor options are absent from the hardware test screen.
Has anyone found any method - via codes even - to permanently turn on the proximity sensor, even when the screen is locked and turned off?
I searched through AOSP framework vanilla codes and couldn't see anything out of the ordinary regarding control of the proximity sensor. Samsung might be doing something dubious with their firmwares/hardwares though - well, at least, the S20 and Note20 variants are having issues with the proximity sensor setup.
P.S: Not sure if you guys are aware, but Samsung mobile devices with odd designation tends to be more problematic than their even-designated counterparts, like screen's burn-ins/shadows on Samsung S3 devices, light sensor fluctuation (which affects screen brightness control) on Samsung S5s, and now proximity problems with the S20s and Note20. Samsung S20 variants are in fact "S11" variants renamed. So the trend continues with Samsung always stuffing up their odd-designated device releases.
Hi All,
I am using Nokia 7 plus for past 2 years. Andorid 10 with Nov security patch. Recently, my proximity sensor stopped working and I am not able to use phone any more (due to black screen during calls). I even root my phone and installed edxposed framework for disabling proximity sensor but no luck. Even sensor disabler not working for me. Any suggestions would be much helpful as I want to use this phone badly
I have same problem (stop working after lcd replace), try more solution, but at end i find one "working"... In Developer options enable QuckSettingsDeveloperTiles/SensorOff, this add Sensor tile to top pulldown QuckSettings menu, before call must you manually enable it, after call disable (because sensor off disable all sensors and also camera ;-)
k3dar7 said:
I have same problem (stop working after lcd replace), try more solution, but at end i find one "working"... In Developer options enable QuckSettingsDeveloperTiles/SensorOff, this add Sensor tile to top pulldown QuckSettings menu, before call must you manually enable it, after call disable (because sensor off disable all sensors and also camera ;-)
Click to expand...
Click to collapse
Yeah, I have been using it. Problematic when attending calls in Skype which wont work unless you switch again. Thanks anyway
In my experience, proximity sensors don't stop working, they just work all the time! Often there's a small rubber gasket which separates the UV LED from the sensor. Can be lost when replacing a screen - I did this myself on a Moto G. Screen would go black in a call and couldn't be unlocked. I found the gasket on the floor, replaced it and this fixed the problem. Replaced the screen on a Nokia 7 Plus recently, same problem. I couldn't find a missing gasket this time, but glued a small piece of rubber between sensor and LED and this fixed the issue. Had to experiment with the size of the rubber piece to get it working properly. I think some of the UV light bounces off the back of the screen and is picked up by the sensor , if this piece is missing. My $0.02 worth...
Guys, I am frustrated with proximity sensor of my Nokia 7 Plus, as soon as I call, screen goes black.
I could stop it by enabling Developer Mode and disabling sensors, but this disables all sensors not proximity, and my camera stopped working.
Can I just remove it from mother board? any way to disable only proximity sensor?
Thanks in advance.
MrNams said:
Guys, I am frustrated with proximity sensor of my Nokia 7 Plus, as soon as I call, screen goes black.
I could stop it by enabling Developer Mode and disabling sensors, but this disables all sensors not proximity, and my camera stopped working.
Can I just remove it from mother board? any way to disable only proximity sensor?
Thanks in advance.
Click to expand...
Click to collapse
If you've had the screen replaced, I think the rubber gasket separating the IR LED and sensor has been lost. Seems to be a common cause of this kind of problem. Cheers
Gastrocnemius said:
If you've had the screen replaced, I think the rubber gasket separating the IR LED and sensor has been lost. Seems to be a common cause of this kind of problem. Cheers
Click to expand...
Click to collapse
Many thanks for quick reply.
Yes, I replaced screen. I don't remember about rubber gasket, but now i have to open scree and fix it.
Can we just remove proximity sensor from board? What functions get affected?
MrNams said:
Many thanks for quick reply.
Yes, I replaced screen. I don't remember about rubber gasket, but now i have to open scree and fix it.
Can we just remove proximity sensor from board? What functions get affected?
Click to expand...
Click to collapse
I guess just the screen turning off during a call. But removing it may damage some other component, I guess. I also wonder if the screen stays off or on permanently if the sensor is removed. If you're taking the screen off anyway you could just try my fix of glueing a small piece of plastic or rubber between the sender and receiver, has worked for me and is still working. But this is just my opinion, all the best in whatever you decide to do. Cheers
Gastrocnemius said:
If you've had the screen replaced, I think the rubber gasket separating the IR LED and sensor has been lost. Seems to be a common cause of this kind of problem. Cheers
Click to expand...
Click to collapse
Yes, I replaced screen. I don't remember about rubber gasket, but now i have to open scree and fix it.
Can we just remove proximity sensor from board? What functions get affected?
Gastrocnemius said:
I guess just the screen turning off during a call. But removing it may damage some other component, I guess. I also wonder if the screen stays off or on permanently if the sensor is removed. If you're taking the screen off anyway you could just try my fix of glueing a small piece of plastic or rubber between the sender and receiver, has worked for me and is still working. But this is just my opinion, all the best in whatever you decide to do. Cheers
Click to expand...
Click to collapse
Ok Thanks, I shall try it.
One more question
Is there a way to disable only proximity sensor through OS/App? This will save my effort to remove it from board and possible damage to board.
Am working on another 7 Plus which has the gasket fitted to the proximity sensor and took some pictures so y'all can see what I'm talking about. First picture is of the gasket, second is the sensor without the gasket. Cheers
Just checked in to this forum for give Gastrocnemius a big "Thank you"!
We have a Nokia 7 Plus with the "normal" USB connection issue.
Send to repair to an independent repair station (so not Nokia), who offered a good price.
When it came back it looked fine, charging and fast charging was possible, we have been happy.
Until the first call... Black screen with dialing.
A short search showed: many problems after an update, looked like software related issue with no solution.
Shortly after the new USB connection was faulty again.
So the phone went into a drawer and replaced with a new Nokia.
Now my old Redmi 4 is too old and some for me important apps will not work with the "old" android.
I remembered the Nokia 7 plus and started to repair the USB board, also as a trial if i can handle mobile phone repairs for myself. Well, cheap USB board found, change successful... not! Broke the Display (stayed black after assembly, board from display got hot, probably cable broken).
Ok next step, new display, screen works and and charging repaired on first view.
Function check: black screen during call. Tried several proximity fix tools without success.
The app Phone Check clearly identifies as proximity sensor as "close" / near, no change.
The change to far came only when the display was way to the side. So, the sensor is working, but the function close far is not working.
After weeks I discovered this fred! Gasket? Which gasket! There is no gasket! Check with several videos on YT, yes, gasket identified!
So I tried the mentioned fix rubber band but was not able to get it working.
Then I looked for a gasket online and found one available for the Nokia 2 / TA 1007 on EBAY for a couple of Euros and ordered it for giving it a try.
I just assembled the gasket.... the 7 plus no works like new!
So I'm assuming that during the first USB-board change the gasket got lost and the check by the repair company was only performed for the charging and no more checks for the rest or they didn't care (ASUMING!)
Long story short:
If the gasket is missing you can use the one from the TA-1007!
It does look a little bit different than the above gasket but mine worked. No further assembly from the phone is required, just slip it over the sensor (make sure that the big hole is left, seen as microphone is up and sensor is up left [don't know how to describe better]).
Thanks again for the hind to the missing gasket.
Best regards from Munich,
Thorsten
(typos corrected)
Blackboie said:
Just checked in to this forum for give Gastrocnemius a big "Thank you"!
We have a Nokia 7 Plus with the "normal" USB connection issue.
Send to repair to an idependent repair station (so not Nokia), who offered a good price.
When it came back it looked fine, charging and fast charing was possible, we have been happy.
Until the first call... Black screen with dialing.
A short search showed: many problems after an update, looked like softwrae related issue with no sollution.
Shortly after the new USB connection was faulty again.
So the phone went into a drawer and replaced with a new Nokia.
Now my old redmi 4 is to old and some important apps wil not work with the "old" android.
I remembered the Nokia 7 plus and started to repair the USB board, also as a trial if i can handle mobile phone repairs for myself. Well, cheap USB board found, change sucsessful... not! Broke the Display (stayed black after assembly, board from display got hot, probably cable broken).
Ok next step, new display, yes, phone and charging repaired.
Funktion check: black screen during call. Tried proximity fix tools without sucess.
The app Phone Check clearly identifies as proximity sensor as "close" / near, no change.
The change to far came when the display was way to the side. So the sensor is working, but the function close far is not working.
After weeks I discovered this fred! Gasket? Which gasket! There is no gasket! Check with several videos on YT, yes, gasket identified!
So I tried the mentioned fix rubber band but was not able to get it working.
Than I looked for a gasket online and found one available for the Nokia 2 / TA 1007 on EBAY for a couple of Euros and orderet it for giving it a try.
I just assembled the gasket.... the 7 plus no works like new!
So I'm assuming that during the first USB-board change the gasket got lost and the check by the repair company was only performed for the charging and no more checks for the rest or they didn't care (ASUMING!)
Long story short:
If the gasket is missing you can use the one from the TA-1007!
It does look a little bit different than the above gasket but mine worked. No further assembly from the phone is required, just slip it over the sensor (make sure that the big hole is left, seen as microphone is up and sensor is up left [don't know how to discribe better]).
Thanks again for the hind to the missing gasket.
Best regards from Munich,
Thorsten
Click to expand...
Click to collapse
Glad to hear it worked for you Thorsten!
I feel there is no proximity sensor in this phone..
Becuase while i am on call , even though the screen is touched to my ear , it will light up randomly as i am walking and turning.
Is that function managed by accelerometer and gyroscope as in new redmi phones ?
The autobrightness is also acting weird for me in some cases .
aj7400 said:
I feel there is no proximity sensor in this phone..
Becuase while i am on call , even though the screen is touched to my ear , it will light up randomly as i am walking and turning.
Is that function managed by accelerometer and gyroscope as in new redmi phones ?
The autobrightness is also acting weird for me in some cases .
Click to expand...
Click to collapse
It doesn't do so for me but yes if I move my face when talking the screen turns on but then goes back off immediately. It seems that proximity sensor is managed by the accelerometer combined with ai just like it was in my old OnePlus 7Pro. However, I could be totally wrong!
amirage said:
It doesn't do so for me but yes if I move my face when talking the screen turns on but then goes back off immediately. It seems that proximity sensor is managed by the accelerometer combined with ai just like it was in my old OnePlus 7Pro. However, I could be totally wrong!
Click to expand...
Click to collapse
While on call I tried to use another phone`s camera to search for proximity sensor ( it is ir based , so camera picks it up).
But couldnt find it
aj7400 said:
While on call I tried to use another phone`s camera to search for proximity sensor ( it is ir based , so camera picks it up).
But couldnt find it
Click to expand...
Click to collapse
So then, my suspicions are right..It's accelerometer+ai
I think it uses the camera too. If you try unlock the phone with the selfie camera covered, it will try to prevent it.
Likewise, if you make a call with your phone placed flat on a surface, you can get the screen to turn off by covering the camera.
adamlee2012 said:
Yes it has one. It's near the light sensor... They are both under the display.
Click to expand...
Click to collapse
I dont think it has .
Even when i am on call , phone just touching my ear , it randomly lets the screen turn on .
Also as far as i remember , always on display in the previous generations used to turn off when the phone was in pocket ( or screen was covered)
But here , the aod always remains on regardless if phone is in pocket or outside .
adamlee2012 said:
I’ve just tested mine during phone call. It’s definitely there… I’ve seen it.
Click to expand...
Click to collapse
Yes you are right. It has an ir based one like note 10,20, s10, s20...
Samsung probably is wondering if they should make it invisible with no indicator. That tiny flashing circle has caused more commotion than a midget hooker in the playpen. Every new model provokes this same discussion... talk about a fixation
Using the camera sensor be prohibitive because of power consumption. It would still need an IR emitter to work properly. Net zero gain... and a lot of added complexity at best.
You can test the light sensor with CPU-Z, cover the space to the right of the front camera, that's also what triggers display dimming no matter what adaptive brightness settings you have.
my S20 FE does the same thing on calls. super irritating... i wonder if Samsung will correct the SD card slot omission mistake on the S22. they did the same thing with the S6 and fixed it on the S7
inpression said:
You can test the light sensor with CPU-Z, cover the space to the right of the front camera, that's also what triggers display dimming no matter what adaptive brightness settings you have.
Click to expand...
Click to collapse
The light sensor is there , itried with cpuz , but i feel the proximity sensor does not work properly .
It wakes up the screen during calls
this have been issue for Pixel devices, proximity sensor not working properly.
Mine's on same boat, proximity sensor always read something blocks (distance 0cm).
actually it does not hurt for most of time, but only 2 things.
AOD turned off, i prefer AOD is always on..
display off when calling.
There is workaround.. just press the screen, the proximity area, then it works normally for a while.
I kept doing that, and it fixed for couple of months in last winter.
It started happening again when I stayed in Desert area, 90F over night.
looks like proximity sensor should be stuck on some "right" place, but glue does not hold it tight?
I donno... anyways, it happened again when weather comes warmer.
so, I was looking for a solution, just disable the proximity sensor, or make it always 5cm reading.
nothing works so far!
first trial. use "disable sensors" in developer option.
I created a tasker command for toggle that function --> this works. but...
it disables mic as well, cannot use during phone call.
for AOD, that command does not work when screen is off. command does not go through for AOD.
second trial. use disable sensor addon for xposed (now LSPOSED with magisk)
not working on Android 13 and 12.
Looks like it worked on Android 8 or 9? not an option for pixel 5.
I gave up at this point.
Pixel 5 is great phone, light and small enough, easy to carry. performance is not great but ok for me. battery life is also ok.
easy to unlock bootloader, flip to other custom roms..
because of only for this small proximity sensor, this is hard to use for me..
Is there any way to disable it?
see this thread for a general idea of what to do.
[Q] Disable proximity sensor via terminal emulator
Hi @ all, I have that following problem: My phones display turns off automatically while im receiving or doing a call. My proximity sensor is broken and i would like disable it and i found a good solution here in this formus...
forum.xda-developers.com
that is for a HTC phone and is a 10 year old thread but I think if you can identify the correct device you can use root to effectively prevent it from changing state.
Maybe not. its been a while since I messed with Android Internals.
Worth a try.
I recently got a refurbished Pixel 5 and had this same issue, a few searches on the internet and I learned about the screen gap fiasco. If I'm not wrong isn't the reason behind the proximity issue this same screen gap on top left. As far as mine is concerned, I heated it up a little to loosen the adhesive, covered it in a soft cloth and then applied a plastic clip I had lying around on top left for compression. I left it overnight and voila the sensor works perfectly now. Also I have a relatively tight case on.