Proximity sensor problem during conversation

[Jjarek23]

During the conversation, when I hold the phone to my ear, sometimes the screen wakes up and my ear starts up various functions of the phone. This is very common after updating to Android 12, previously it was less. Please solve this problem ASAP. Phone software version: 31.1010.0410.72, APP software version: 2.9.0.27_220324

[Jjarek23]

@Mattias_ASUS
Did the R&D department give you any answers? Four months ago, I gave you the logs from the phone. I am not satisfied with the answers that they are working on it. I want answers on what stage of solving the problem is and when it will be fixed.

[StealthRequiem]

I can provide an interesting update on this problem. I've recently updated my 2nd Zenfone 8 from Android 11 all the way to .122 on Android 12. After each OTA I performed a factory reset.
So far I'm having no problems with the screen during calls, everything is fine, unlike my previous Zenfone 8 which became almost unusable as a phone.
So.. is it the resets, the build, or a previously pulled update that broke the screen/sensor? The latter might seem unlikely, but remember a ROG 5 update physically broke wi-fi. This doesn't explain though why my previous sensor showed as working and why some Zenfone 9 users are having this problem. I wasn't using a screen protector by the way.
All happy at the moment until the next update breaks something.

[laci_kara]

Actually if You do a proximity sensor test in the SMMI test, it see close proximity way further than the locked screen does.

This is how I tried it:
The phone is locked.
I have covered the proximity sensor.
Then I moved my hand off the sensor until I could unlock the phone with the fingerprint sensor.
I kept the distance here and fired the SMMI test. The test already told me close distance.

If i understand it well, then the phone should have been still in pocket mode.
Either the set threshold or the readout is wrong during use outside SMMI.


I have proven this with an app called sensors toolbox. That also differentiate close of far distance only.
But the sensing distance in the app and on a locked screen (or call) is different.

The app shows still close distance while I can already unlock the phone.
As I seenthere is nothing wrong with the sensor itself but the readout is wrong here.

[willjoe2442]

Clean Dirt and Dust Near the Sensor.
Check to See if a Screen Guard Is Blocking It.
Update Your Phone.
Use an App to Re-Calibrate Your Device's Proximity Sensor.

Regards,
Will

[Mattias_ASUS]

Hello!
Today I got a reply from the team that asks for some details.
"1. First step – Check the P-Sensor function is properly
   >> Start the calculator, enter .12345+= to start the SMMI tool, select Single Test > Proximity Test, and check whether the Sensor is normal
2. If the sensor detection is normal, provide a reproduction method (mainly video, because we want to know the angle of the other machine when answering),
   >> Provide video + log, the video should be taken to the position of the opening of the Proximity sensor and the position relative to the ear (or hair or cheek, depending on the behavior of the user when it can be recreated)
3. If there is a problem with the sensor detection, it may need to be sent for repair "
-------
As for how to create a log I will write it down here:
Please follow the below steps to enable the built-in log tool (Bug reporter).
1.  Open “Calculator APP”
2.  Enter “.19595+=”
3.  Select the Log type according to the type of issue you want to capture. “General cases” will work for most issues.
4.  After your selection the log tool will exit so you can duplicate the issue or wait for it to happen. Try to use the screen recorder to show your issue when possible. If you can't screen record your issue, then please take a screenshot right after the issue has occurred (as a timestamp) so we know where to look in the log.
5.  Navigate back to the log tool via calculator and Tap "FINISH AND SHARE".
6. It takes several minutes for the log to generate. You can exit and do other stuff in the meantime. A silent notification will tell you once the process is done. Tap the notification and then the share button to upload the file to Google Drive and share the link with a moderator. Just make sure to change the permission first so that everyone with the link has permission to view it.
Note: When you're no longer planning on logging your device, enter “.09595+=” in the calculator and the log tool will stop as well as deleting all stored log files. Make sure to share via calculator. The files found in internal storage -> asus_log are not the correct files (they are only 1.2kb)