Autorotate and pedometer problem - Xiaomi Mi 9 Questions & Answers

These two don't work. I think it's due to sensors but how do I fix them without persist thing? Thank you.

Related

Is there anyway to test hardware functions?

I remember (but not for sure) a settings page that gave you the ability to test different sensors and what-not. the reason for my question is because when i make a call the proximity sensor doesnt work, and i wanna know is it because of the rom or anything software related, or is it the sensor itself, since i recently had repair done on the screen.
thanks.
Nobody knows? i got a 30-day warrenty, so if my proximity sensor really isnt working i need to know soon.
I've used an app previously that would display raw readouts from the various sensors in the device, including the proximity and ambient light sensors. Stand by while I try to find what app that was...
In the meantime, you can at least verify that half of the sensor is working by looking at the screen through a digital camera or other phone's camera. The proximity sensors works off of a flashing IR LED that you should be able to see through a digital imaging sensor. The sensor is located to the left and below the speaker.
Also, I believe the application I was using is called "Elixir", and is free on the Market.
Thanks man, great app. everything is working ok now.

[Q] Need way to disable proximity sensor

My proximity sensor seems to have stopped working (always gives a value of 0.0) as a result whenever a call is placed the screen goes off and i cant do anything at all, cant even end the call. This seems to be hardware problem, as cleaning the area is not helping.
Is there a way to disable the proximity sensor completely/permanently?
The only working way i found was using the "Hardware Disabler" app in play store and disabling /sys/bus/platform/drivers/proximity, but that makes the phone as slow as hell. How would I go about deleting this folder otherwise? Root Explorer is not allowing me to do this.
All the other solutions i found on the net do not help (using proximity recalibration, adding lines to build.prop, putting a script in init.d - Though perhaps I am not using it correctly).
Someone please help. The problem is driving me crazy.
Note: using CM9.0 RC2
Nobody has any issues with the proximity sensor on their phones?
And is there no actual way to disable it?
nobody here who can help?
manish_bhaumik said:
Nobody has any issues with the proximity sensor on their phones?
And is there no actual way to disable it?
Click to expand...
Click to collapse
I still need help on this?
Hi, last time I tried MIUI rom and iinm there is an option to disable the proximity sensor. But, if you doesn't like MIUI.. I am don't know any other workaround for it anymore.
Or try some different ROM to make sure if it is actually hardware issue or software issue.....
Use miui rom and press on dial and then menu...Again press on setting and Answer setting .. You will find there the option to disable proximity sensor..

Is proximity working for you in apps?

Yes, another proximity question!
I have trouble with this sensor using 3rd party apps.
On system it works fine without a problem (screen on/off during phone call never had any problems)
but any apps which use this sensor stops working after rebooting.
-Gravity screen on/off
-Automaton gestures
-Automate it!
These are the apps I tried and encountered problems with...so pretty much all of them!
The sensor works, cpuz sees it working with both distances 3cm near and 10cm far, but apps don't :S
For example if I try to record sensor state in automate it it just reads '10 far' and notihng else.
aamof rules with sensor far work fine but with near don't....
I encountered this problem both across 10.1 and 10.2 and different roms...anybody else encountered this isse?
I recalibrated tegra.so from adb...I'll try to go back to stock and try from there recalibration but seen thtat it "works"
I'm not sure how that is going to help.....
Rudjgaard said:
Yes, another proximity question!
I have trouble with this sensor using 3rd party apps.
On system it works fine without a problem (screen on/off during phone call never had any problems)
but any apps which use this sensor stops working after rebooting.
-Gravity screen on/off
-Automaton gestures
-Automate it!
These are the apps I tried and encountered problems with...so pretty much all of them!
The sensor works, cpuz sees it working with both distances 3cm near and 10cm far, but apps don't :S
For example if I try to record sensor state in automate it it just reads '10 far' and notihng else.
aamof rules with sensor far work fine but with near don't....
I encountered this problem both across 10.1 and 10.2 and different roms...anybody else encountered this isse?
I recalibrated tegra.so from adb...I'll try to go back to stock and try from there recalibration but seen thtat it "works"
I'm not sure how that is going to help.....
Click to expand...
Click to collapse
yeah, i noticed in viber screen doesn't turn off when you put your phone enxt to your ear. i dont have any other apps that use proximity sensor other than phone app, but that one works without issues.
the issue persists in stock as well as custom roms. no idea how it was on ics, though
It also appears on stock?! wow never would've thought...
It's a pretty considerable bug to have never been mentioned before...
all problems with proximity encountered so far always seemed caused by bad calibration..
this kinda sux :S
Devs and wise people, do you think this could be caused by the fact that the 'near' state is set at 3cm reading and 3rd party apps look for 0 distance with 0% tolerance to have widespread compatibility?
Do you think it is possible to change these settings?

does anyone facing fingerprint issue post oreo update?

Post oreo update I'm facing fingerprint response issues. It is not responding at least once for thrice.how to fix this?
No one problem here. Try to reset your phone. I've done this and solved some bugs like smart lock not working.
Or maybe clean your fingerprint sensor and rescan your finger with different positions.

[X522] Broken sensors -can i fix it?

Hello i have issue with Le2 x522.
Phone seems to have wrong working sensors.
For now its LSM6DS3 - Its accelerometer and gyroscope
In accelerometer menu X axis seems to be reversed so when i rotate phone on one side screen gets rotated in oposite.
Also orientation sensor looks pretty off.
I have tried google maps trick, also tired MIUI9 diagnostic menu calibration but it didn't work(punched phone few times in area of camera too).
Ended up with reflashing SmallEUI by Auriel(stock kernel) and still its not working.
Any ideas how to solve that issue?
Kiciuk said:
Hello i have issue with Le2 x522.
Phone seems to have wrong working sensors.
For now its LSM6DS3 - Its accelerometer and gyroscope
In accelerometer menu X axis seems to be reversed so when i rotate phone on one side screen gets rotated in oposite.
Also orientation sensor looks pretty off.
I have tried google maps trick, also tired MIUI9 diagnostic menu calibration but it didn't work(punched phone few times in area of camera too).
Ended up with reflashing SmallEUI by Auriel(stock kernel) and still its not working.
Any ideas how to solve that issue?
Click to expand...
Click to collapse
I'm not sure about this method:
in miui 9 thread for le 2 by sagarmakhar, in the 2nd post, it was about volte, but involved a thing about sensors. according to him, wipe persist from his recovery, then flash stock rom and then copy the 'sensors-settings' into /persist/sensors/ (I don't remember the folder now, please refer to that post) and reboot....May work, i don't think that it can brick your device but try at your own risk:fingers-crossed: Good luck

Categories

Resources