Calibration of proximity sensor ? - Xiaomi Mi A3 Questions & Answers

Hello,
I have problem with proximity sensor. Phone thinks that something is close to screen all the time. On stock 9 I've seen that data from sensor was changing depending on distance but after updating to stock 10 that's not the case anymore. Today I've finally tried crdroid and evolution x with same effect.
Maybe I'm missing something.
I will be glad and happy with any clues thanks.

---

I had same issue. Tried everything with no luck at all. Phone had the global ROM (mixm if I remember correctly)
Tried lots of custom ROMs and different fixes and still the same.
Just before I throw it to the wall I installed the European official ROM (euxm) with miflash and lock bootloader again and miracle happened.
Now it works like a charm.
Sent from my ZUK Z2121 using Tapatalk

---

Can you link firmware that you flashed ?
Thanks

---

nininikos said:
I had same issue. Tried everything with no luck at all. Phone had the global ROM (mixm if I remember correctly)
Tried lots of custom ROMs and different fixes and still the same.
Just before I throw it to the wall I installed the European official ROM (euxm) with miflash and lock bootloader again and miracle happened.
Now it works like a charm.
Sent from my ZUK Z2121 using Tapatalk
Click to expand...
Click to collapse
can you link me the european ROM?
tnx

---

they are here https://forum.xda-developers.com/mi-a3/how-to/rom-xiaomi-mi-a3-laurelsprout-t3962489 and https://mirror.codebucket.de/firmware/laurel_sprout/ but this did not help in my case.
I founded also this https://www. the*********** .com/android-10-sensors-bug-fix-guide/ but i will test this in few days - enough flashing for now...

---

th0m4s said:
they are here https://forum.xda-developers.com/mi-a3/how-to/rom-xiaomi-mi-a3-laurelsprout-t3962489 and https://mirror.codebucket.de/firmware/laurel_sprout/ but this did not help in my case.
I founded also this https://www. the*********** .com/android-10-sensors-bug-fix-guide/ but i will test this in few days - enough flashing for now...
Click to expand...
Click to collapse
Then what helped u??

---

I still have this issue. I was having enough flashing for that day and I didn't play with it form then.

---

th0m4s said:
I still have this issue. I was having enough flashing for that day and I didn't play with it form then.
Click to expand...
Click to collapse
Well i fixed that shiit? a guy did a great job with Edxposed and magisk module! I now find no sensor bug.. enjoying Android 10!

---

You simply disabled sensor or you calibrated it somehow ?

---

th0m4s said:
You simply disabled sensor or you calibrated it somehow ?
Click to expand...
Click to collapse
I calibrated it but it starts doing problem again though!!
I used app proximity service but no use..
And also dialed *#*#64663#*#* then calibrate.but starts problem after sometime..
I then used sensor disabler module on Edxposed with magisk module! Then it works like charm!
It was just increasing lux max value !

---

Sami Devo said:
I calibrated it but it starts doing problem again though!!
I used app proximity service but no use..
And also dialed *#*#64663#*#* then calibrate.but starts problem after sometime..
I then used sensor disabler module on Edxposed with magisk module! Then it works like charm!
It was just increasing lux max value !
Click to expand...
Click to collapse
I just tryed that method but still the same ´probleme
I switched the both Light and proximity to max value
But the screen still black and incontrolable whenn making a call
i#m on last 10 buildt and rooted ofc

---

moyses said:
I just tryed that method but still the same ´probleme
I switched the both Light and proximity to max value
But the screen still black and incontrolable whenn making a call
i#m on last 10 buildt and rooted ofc
Click to expand...
Click to collapse
Then u better switch to Android 9 .. goto miui11 1st.. then stock 9.. after that flash latest stock 10 again clearing both slots

---

I've finally solved my issue.
1. flash custom recovery and mound persist partition
2. adb pull /persist/sensors/registry/registry/stk3x3x_0_platform.ps.fac_cal
3. make backup copy
4.
{"stk3x3x_0_platform.ps.fac_cal":{"owner":"sns_stk3x3x","near_threshold":{"type":"flt","ver":"3","data":"1169.000000"},"far_threshold":{"type":"flt","ver":"3","data":"1067.000000"},"ctir_calibration":{"type":"flt","ver":"3","data":"578.000000"}}}
Click to expand...
Click to collapse
in my case last value is less than first two so I've changed it to 2578
5. adb push stk3x3x_0_platform.ps.fac_cal /persist/sensors/registry/registry/
I not sure if other people have same problem but this solved my issue so I'm shearing.
big thanks to Rajendran Rasa for shearing his persist image