Hi, I got my Mi 3 this week. I noticed some weird behavior from my magnetometer and Accelerometer, wondering if anybody else is experiencing the same. After a day of use, sensors go haywire and suddenly stop reporting data. Can't use compass and my auto rotate stops working. I tried different apps to see if it's a global problem or just a not compatible app, so far when sensors go blank, the effect is global. Even the Mi self test is not reading anything from the sensors. Pedometer is on the other hand operational tho.
Things come back to normal after a restart. I suspect it must be a software bug maybe?
sherlock.holmes said:
Hi, I got my Mi 3 this week. I noticed some weird behavior from my magnetometer and Accelerometer, wondering if anybody else is experiencing the same. After a day of use, sensors go haywire and suddenly stop reporting data. Can't use compass and my auto rotate stops working. I tried different apps to see if it's a global problem or just a not compatible app, so far when sensors go blank, the effect is global. Even the Mi self test is not reading anything from the sensors. Pedometer is on the other hand operational tho.
Click to expand...
Click to collapse
My sensors are working but they are wrongly calibrated :/ and pedometer isn't working! I thought the pedometer was disactivated by default...
greenpays said:
My sensors are working but they are wrongly calibrated :/ and pedometer isn't working! I thought the pedometer was disactivated by default...
Click to expand...
Click to collapse
Dial *#*#6484#*#* it's the built-in test. U can recalibrate your accelerometer there and also test the device. Use power button to exit. And for +-45 test's of the accelerometer tilt your device on it's corners.
sherlock.holmes said:
Dial *#*#6484#*#* it's the built-in test. U can recalibrate your accelerometer there and also test the device. Use power button to exit. And for +-45 test's of the accelerometer tilt your device on it's corners.
Click to expand...
Click to collapse
Thanks for the tip it works perfectly!
By the way, you are using European firmware or Global, because for me the pedometer isn't counting the steps :/
greenpays said:
Thanks for the tip it works perfectly!
By the way, you are using European firmware or Global, because for me the pedometer isn't counting the steps :/
Click to expand...
Click to collapse
I'm glad to hear it worked for you. My pedometer comes and goes... Not reliable unfortunately. btw how can I check my ROM region? Got the October patch, It doesn't solve the bug...
I also have problems with my vibrator. It doesn't react to short vibrations (that much I can make out of it).
sherlock.holmes said:
I'm glad to hear it worked for you. My pedometer comes and goes... Not reliable unfortunately. btw how can I check my ROM region? Got the October patch, It doesn't solve the bug...
I also have problems with my vibrator. It doesn't react to short vibrations (that much I can make out of it).
Click to expand...
Click to collapse
Well I seem to have the global version. MIXM
I hope they get problems solved fast.
If anybody else with the device is reading this post, can you please check your sensors with an appropriate app and see if yours is also malfunctioning randomly?
I had this problem, but I just restarted the device and everything came back normal
braulio_holtz said:
I had this problem, but I just restarted the device and everything came back normal
Click to expand...
Click to collapse
Yes! It goes away with restarting (and sometimes doesn't!!!)
But it's just a temporary fix, in matter of hours, you r back to the square one.
sherlock.holmes said:
I'm glad to hear it worked for you. My pedometer comes and goes... Not reliable unfortunately. btw how can I check my ROM region? Got the October patch, It doesn't solve the bug...
I also have problems with my vibrator. It doesn't react to short vibrations (that much I can make out of it).
Click to expand...
Click to collapse
Go to Accessibility settings and turn on Touch Vibration. Keeping it off also hinders the in call volume function. Hope it helps
Arkapravoarka said:
Go to Accessibility settings and turn on Touch Vibration. Keeping it off also hinders the in call volume function. Hope it helps
Click to expand...
Click to collapse
Well yeah, it did work actually. But the thing is, I don't like to have the touch vibrations on always, I just want it to work with G-board and some other apps that use short vibrations as a feedback...
It's like the touch vibrations setting, controls everything lol.
It's definitely a bug they have to get fixed.
So it turns out the sensor problem that I reported is being caused by the G-cam port I had installed. The solution is to close the app (in the multitasking menu !?) Whenever you are done using it.
Flash the stock rom again and your problem will be solved for sure, also faced the same issue.
I have same issue and flash stock rom but still not working how can i fix it ?
I also have a problem with compass apps. north and south are correct shown, west and east are not correct.
Stefan_1 said:
I also have a problem with compass apps. north and south are correct shown, west and east are not correct.
Click to expand...
Click to collapse
I use this solution and it worked.
https://forum.xda-developers.com/showpost.php?p=82161897&postcount=4
My Mi A3 has just got an system update of android 10. Just after that, my camera isn't working. Please help me out of this problem.
Chaitanya123 said:
My Mi A3 has just got an system update of android 10. Just after that, my camera isn't working. Please help me out of this problem.
Click to expand...
Click to collapse
Did you try wiping data and cache for camera app?
Related
Am I the only one having problems with the Proximity Sensor on the Atrix? I can't seem to get it to kick in when on a call. I have already dial-toned a couple of people when talking on the phone. I have tried covering up the sensor by placing the palm of my hand over the to 1/2 of the phone and it never kicks in.
Can someone verify for me that it does work and not some software bug.
Thanks,
Ed
Did you ever find the problem? My proximity sensor has stopped working also.
i am having an issue with mine too. at first i thought it was an issue with the screen not coming back on, but now i realize that the proximity sensor is not turning off the screen at all and my screen is just turning off when the screen timeout value is reached.
my phone is rooted, i have used titanium backup to freeze some of the apps associated with blur, and i have installed the hack to use webtop mode. can others that have this issue confirm if they are running stock or modified software?
***EDIT***
http://forum.xda-developers.com/showthread.php?p=12035170#post12035170
Any of you guys ever find a fix for this? I just noticed that mine is not working anymore either. It's rooted using aRoot but it was working for a while and now it doesn't anymore. I have another couple of days to exchange in store if I want to if it's a phone issue.
Crap, I'm having the same issue now too -- was working fine since I had it, but this occured just today, Day-2 of using 1.5.7 .... wonder if it's related ...
Crap, I'm having the same issue now too -- was working fine since I had it, but this occured just today, Day-2 of using 1.5.7 .... wonder if it's related ...
Reboot seems to fix this -- but annoying >_<
Is anyone that is having these issues using bluetooth? I have isolated mine to bluetooth and sent an issue report to Motorola.
same problem here but not using bluetooth
My wife's Atrix does the same thing. "dials or hangs up while in a call". She does not own a bluetooth headset and I have only connected a Motorola 305 one time to it. Reboot fixes the problem. Reboot seems to take forever when compared to my Dell Streak.
Ed Venture said:
Am I the only one having problems with the Proximity Sensor on the Atrix? I can't seem to get it to kick in when on a call. I have already dial-toned a couple of people when talking on the phone. I have tried covering up the sensor by placing the palm of my hand over the to 1/2 of the phone and it never kicks in.
Can someone verify for me that it does work and not some software bug.
Thanks,
Ed
Click to expand...
Click to collapse
Had the problem with mine when I installed a different launcher had to delete it and restart the phone now it works ....for me anyways
Sent from my MB860 using XDA App
Hi I believe I traced the problem with the proximity sensor not working to Handcent SMS. On two separate Atrixes, as soon as I uninstalled Handcent and rebooted the phone the problem went away and stayed away. I have since installed GoSMS and now it happens just sometimes (usually after I install a new app) but a reboot after installing an app ususlly fixes it.
My Phone has a standard Telstra (Australia ROM) and is not unlocked or modified in any way.
Ed Venture said:
Am I the only one having problems with the Proximity Sensor on the Atrix? I can't seem to get it to kick in when on a call. I have already dial-toned a couple of people when talking on the phone. I have tried covering up the sensor by placing the palm of my hand over the to 1/2 of the phone and it never kicks in.
Can someone verify for me that it does work and not some software bug.
Thanks,
Ed
Click to expand...
Click to collapse
hi, you can try this
open /system/build.prop and add this
persist.mot.proximity.touch=1
reboot phone
Seem that i have this problem on my atrix,when i calling someone,the screen turn off immediately and the led on proximity sensor just keep turn on when i stop calling,i cant imagine this atrix have a lot a lot hardware problem
Sent from my MB860 using Tapatalk 2
If you are using unlocked bootloader or if u have unlocked the dim using a code then u will have to disable the In Pocket detection and then try sounds crazy but worked for me.
Sent from my MB860 using xda premium
ranjithkumar1201 said:
If you are using unlocked bootloader or if u have unlocked the dim using a code then u will have to disable the In Pocket detection and then try sounds crazy but worked for me.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
care to share how?
Similar issue
Just installed latest stable build onto my Atrix 4G, everything seemed fine last night, although I was using phone with bluetooth, this morning get a call, answer, screen goes dark, red proximity light comes on, and I can hear no sound, [later on the caller said he could hear me fine].
Phone would not wake up right off, and when it did it I still could not hear caller.
Been screwing around with settings all morning to no avail, discovered that the phone will only work with bluetooth device connected. without bluetooth the device goes dark, cannot wake up, have to hard reboot, with bluetooth and volume button awaken enabled, it performs normally, so possible connection to issues in post with proximity but with a bluetooth twist...
12as2005 said:
hi, you can try this
open /system/build.prop and add this
persist.mot.proximity.touch=1
reboot phone
Click to expand...
Click to collapse
Did that...... Does nothing much....
12as2005 said:
hi, you can try this
open /system/build.prop and add this
persist.mot.proximity.touch=1
reboot phone
Click to expand...
Click to collapse
Worked for me!!!
Stock rom with, root, atrix tweaks installed.
Thank's a lot!!!
I have been using my S2 since the beginning of February 2012 and have not noticed at any time other than when making calls that the proximity sensor was activated (dull red glow). Just last night I noticed that the sensor seems to be activated all the time now, screen on, calling, whatever...
It of course turns off when the S2 is turned off. When booting back up it does not get enabled again until the end of media scanning.
Any ideas how to check which app or process is enabling this when it is not necessary nor wanted?
Shameless bump. Surely somebody has an idea what variable is involved or what program I can use to change the behavior?
Try after a fresh install with full wipe if it happens
Sent from my GT-I9100 using Tapatalk 2 Beta-5
Well I don't know why, but the sensor has stopped running continuously without any intervention. Thanks for the reply.
I had a similar problem and I found out it was an app causing that - viber.
Probably it was the same with you.
NunxPT said:
I had a similar problem and I found out it was an app causing that - viber.
Probably it was the same with you.
Click to expand...
Click to collapse
Thanks! I had the same problem , and it was indeed Viber.
Btw , did you managed to fix it ?
ZVictor said:
Thanks! I had the same problem , and it was indeed Viber.
Btw , did you managed to fix it ?
Click to expand...
Click to collapse
New viber update today and the issue is fixed
Viber was the problem for me too
Hi all,
This is my first thread... I've looked every forum, every existing thread looking for an explanation / solution, with no luck at all... I hope somebody has experienced this with its prime and found a solution, because I'm thinking in RMA it...
The thing is that my sensors stopped working! No accelerometer, no magnetometer. The screen rotates itself to portrait mode when an app asks for it, but it stays that way when exiting the app. I have to go to Settings -> Display to uncheck and check Autorotation to go back to landscape mode. This is annoying! I installed an app called Elixir 2 and in the sensors page only the microphone is listed as present. Every other sensor is displayed as not present.
I noticed it two weeks ago, but I wanted to look for a solution instead of getting it replaced. I think it came with a .15 and it was updated to .21 in the first connection to Internet. I waited for the .28 to be released just in case it fixed the problem, but it did nothing, still has the problem.
By the way, I tried a cold boot and a factory reset... still nothing.
If I can have any word from anyone I will be pleased!
Thank you!
PS: forgive my english, I'm from Spain
Get the app called elixir2. its free. Kirk show u detailed info on everything, including sensors. itll show real time info on them. allows u to cut them off n on or reset them. it might help.
demandarin said:
Get the app called elixir2. its free. Kirk show u detailed info on everything, including sensors. itll show real time info on them. allows u to cut them off n on or reset them. it might help.
Click to expand...
Click to collapse
Well, that's exactly what I did! I said it before It just shows an X beside every sensor and under them it says something like "not present" (I don't have the Prime here right now). In that sensors page the only one that is shown as working is the microphone.
Any idea?
Thank you anyway!
demandarin said:
Get the app called elixir2. its free. Kirk show u detailed info on everything, including sensors. itll show real time info on them. allows u to cut them off n on or reset them. it might help.
Click to expand...
Click to collapse
Here's a snapshot of the Elixir2 sensors' page.
Hi, I cannot suggest anything new to try.
Today I noticed some of my sensors were not working, tried playing Riptide and found I could not turn. Also tried a level app and found that the orientation was not being detected. My problem was fixed by powering off then turning on again. I did not try elixir2 before the power off, therefore could not say if my prime was in a similar state.
Good luck in getting your prime going again.
Cheers stv
Sent from my Transformer Prime TF201 using XDA
stvlgm said:
Hi, I cannot suggest anything new to try.
Today I noticed some of my sensors were not working, tried playing Riptide and found I could not turn. Also tried a level app and found that the orientation was not being detected. My problem was fixed by powering off then turning on again. I did not try elixir2 before the power off, therefore could not say if my prime was in a similar state.
Good luck in getting your prime going again.
Cheers stv
Sent from my Transformer Prime TF201 using XDA
Click to expand...
Click to collapse
Well, at least someone experienced the same... even with a reset I can't make it work. Is there any "ultra-reset" I can do?
Before .28 I get the same issue.
Sensor can restart after a reboot or a cold start, but after I plug on the dock or after a deep sleep,the sensor stop.
Sometime, after a restart the sensor was not recognized. I use elixir also to check.
Now with .28, the sensor work well.
DesmoRFR said:
Before .28 I get the same issue.
Sensor can restart after a reboot or a cold start, but after I plug on the dock or after a deep sleep,the sensor stop.
Sometime, after a restart the sensor was not recognized. I use elixir also to check.
Now with .28, the sensor work well.
Click to expand...
Click to collapse
Did you update to .28 over wifi or using a microSD?
Thank you!
Update done through Microsd.
I have tweaked buil.prop on .21 and result Fota didn't work.
Think also to make a cold reboot and clear cache of all application (can be done with elixir).
demandarin said:
Get the app called elixir2. its free. Kirk show u detailed info on everything, including sensors. itll show real time info on them. allows u to cut them off n on or reset them. it might help.
Click to expand...
Click to collapse
demandrin - off topic, do you know where I may be able to get the circiut board that has the microsd slot and the touch screen sensor connectors. I accidentally damaged the connectors and now I can only use the tablet with the keyboard dock as a mini laptop. I emailed Asus but they would not sell me the part. I wonder if Gary would be nice enough to sell me the part.
Is HP the only company that sells parts to customers (I love HP for that reason LOL!!)
DesmoRFR said:
Before .28 I get the same issue.
Sensor can restart after a reboot or a cold start, but after I plug on the dock or after a deep sleep,the sensor stop.
Sometime, after a restart the sensor was not recognized. I use elixir also to check.
Now with .28, the sensor work well.
Click to expand...
Click to collapse
An update with my problem: I finally installed the .28 through SD card, having wiped all the data first, and the result is the same: no sensors are present. No autorotation, no compass, no auto-brightness. Elixir shows only the microphone as one of the sensors, everything else is shown as "not available" (as shown on my previous snapshot).
Any help?
Thank you!
sunne2k said:
An update with my problem: I finally installed the .28 through SD card, having wiped all the data first, and the result is the same: no sensors are present. No autorotation, no compass, no auto-brightness. Elixir shows only the microphone as one of the sensors, everything else is shown as "not available" (as shown on my previous snapshot).
Any help?
Thank you!
Click to expand...
Click to collapse
And yesterday, with no reason at all, ALL of my sensors (accels, gyro, magnet field, etc.) started working again. I just powered the tablet on and voilà, everything was perfect! Elixir showed all the sensors up and running!
I think this post can be closed now... I hope it doesn't happen again!
Has anyone else had the problem of wake up gestures and pedometer that stops working? The weird thing is....it works fine when attached to the charging cradle?
Check to see if you have enabled the power saving mode. This will turn off the motion wake gesture.
Nope...not activated. Ive done hard resets...reboots, dialed that code to see if the gyro etc had values (it did) im at a loss.
I've been having the same issue ever since I updated the gear to the latest release. Some one please help.
Ok.... I guess we have self repairing watches....mine started working again. WEIRD!
hattrick1965 said:
Ok.... I guess we have self repairing watches....mine started working again. WEIRD!
Click to expand...
Click to collapse
Lol yeah mine started working a day or two ago also. Weird stuff. Glad it's fixed though.
Hi All
Any one facing proximity issues here , i saw so many peoples reported in mi forums that when we make a call screen blacks out when we moved to ears( Thats normal) and won't turn back again , so i have to wait the other side person to hangup the call or screen won't turn on power button does work that time, i think this only affects with Sensortek stk3x1x sensor, Redmi note 3 pro comes with two proximity sensors one is from Liteon and other is Sensortek.... Liteon sensors doesn't have this issue, for temporary fix "Wipe proximity area with a cloth or reboot fixes this and it comes back after sometime....( Calibrated but same it works for sometime) no idea wats causing this , issues there in Miui and CM roms....
I found sometimes a flip case with a magnet can cause issues like this when folded right back against the back of the phone, the screen won't come back on because it thinks the flip case is closed.
meangreenie said:
I found sometimes a flip case with a magnet can cause issues like this when folded right back against the back of the phone, the screen won't come back on because it thinks the flip case is closed.
Click to expand...
Click to collapse
yeah but i don't have flipcase, this sensor issues starts with those have "Sensortek Proximity Sensor" Liteon doesn't have issue i think....
Flash the rom again using mi flash tool u will find that yr issue will be solved
Or go to test mode amd calibrate the sensor... that's all
Fastboot flash persist persist.img from latest miui rom? I recently had a problem with sensors. The above cured all
@Hemphiz i think that method for dead sensors bro, this one working sometimes it doesn't mostly if we flash a new rom and use no issues but if we reboot the phone after sometime issue starts.... @ra.one i did that bro flashmiui and recalibrate sensor but that works for temporary please check which sensors you got from this app from playstore https://play.google.com/store/apps/details?id=imoblife.androidsensorbox
if you got Liteon Sensors mostly no issues with proximity, if u got Sensortek u will be having issues or once u got issue it will come back..... im not sure why is causing that..... this is really very annoying bug.... Thousands of people reported in Mi forums about these proximity issues on various devices even on newly launched Redmi 3s/ prime may be they have all got "Sensortek Proximity Sensors".......
This is not a bug, You can disable Prevent Pocket dials under Settings-->Lock screen-->Prevent pocket dials...
I had this since last miui 6.9.9 flash.
Disabled prevent Pocket dials and All is working fine
Edit: for a few hours it was working.
Now its the same again. Phone blacked Out After a call and wont turn on, After a few seconds its coming back. As i said , since flashing new 6.9.9
Android2003 said:
This is not a bug, You can disable Prevent Pocket dials under Settings-->Lock screen-->Prevent pocket dials...
I had this since last miui 6.9.9 flash.
Disabled prevent Pocket dials and All is working fine
Edit: for a few hours it was working.
Now its the same again. Phone blacked Out After a call and wont turn on, After a few seconds its coming back. As i said , since flashing new 6.9.9
Click to expand...
Click to collapse
like i said it may be mostly an issue with Sensortek proximity, can u check which sensors u got from this app https://play.google.com/store/apps/d...droidsensorbox
I have sensortec.
But i think its Software related.
Its since last Update.
I calibrate the Sensor and the issue with calls is still there.
Sensor Works fine, test is okay.
Android2003 said:
I have sensortec.
But i think its Software related.
Its since last Update.
I calibrate the Sensor and the issue with calls is still there.
Sensor Works fine, test is okay.
Click to expand...
Click to collapse
Yes i think its software related but, one trick works clean flash the same rom and use it for a week without any reboot...... (DO CLEAN FLASH and Dont reboot the phone)
don't need to calibrate.... for me when i install new rom and use it for a week no issues , if i reboot the phone the issue starts after sometimes.... i don't knw wats causing it so many peoples with sensortek having issues and this bug is not resolved from Miui 7 to Now Miui 8 MM, the issue there in Custom roms im using RR rom i have issues....
Guys For those having issues Check which sensor you got from this app, if u have proximity issues while calling its mostly "Sensortek"
https://play.google.com/store/apps/details?id=imoblife.androidsensorbox
We need Permanent fix....
I also have exact same issue and i have sensortek sensor. But i can unlock the screen while on a call by pressing power button and then unlocking with fingerprint. Bit annoying
Sent from my Redmi Note 3 using Tapatalk
haree87 said:
I also have exact same issue and i have sensortek sensor. But i can unlock the screen while on a call by pressing power button and then unlocking with fingerprint. Bit annoying
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
So its confirmed its an issue with Sensortek Sensor, no Liteon users reported here, like i told flash the same rom which you are in (clean flash) and don't reboot phone for a week there will be no issues it works perfectly, if u reboot a phone once the issue starts again after sometime so after reboot something is going on no idea what....
i am using this app(for rooted users) on official RR and it works fine
https://play.google.com/store/apps/details?id=com.mobiledirection.proximitysensorreset
anujyadava said:
i am using this app(for rooted users) on official RR and it works fine
https://play.google.com/store/apps/details?id=com.mobiledirection.proximitysensorreset
Click to expand...
Click to collapse
even me used, but i don't think its properly working..... this issue starts only after a reboot, when u flash new roms and after boot dont reboot or power off the phone for a week, not needed any apps, proximity will work properly but once u rebooted issue starts....
But this app's settings load every time phone boots up.so it will work after every boot.
press thanks if I helped u in any way
anujyadava said:
But this app's settings load every time phone boots up.so it will work after every boot.
press thanks if I helped u in any way
Click to expand...
Click to collapse
yes this app i tested earlier, but after sometimes may be in a day or two it won't work....
Found another related issue with proximity , i think proximity is not working properly when there is not enough light around us something related with ambient light sensor i think ..... Eg: if we are in a dark room proximity won't work correctly turn on the light and try it works properly.... i think Xiaomi messed up with something with both sensors Liteon and Sensortek thats why Liteon users face Gyroscope lag in games in dark room and now i think may be the same reason why proximity not working properly in dark room....
hello. I have the BUG but my phone has sensortek version 1 (not 2)
When in a call the screen wont turn off when placing the phone at my ears. With whatsapp the bug wont happend.
I think this is a BUG related to sensor + phone app
A functional workarround is to dial, then press menu (putting the call at background) and then putting the call at foreground again. It works 100% of the time.
Any news? I have this annoying problem too!