Hello
I recently updated to Miui V11 Global on my MIX 2S and started noticing some issues with the magnetometer and gyro. Version 11.0.4 (PDGMIXM).
First the Gyroscope Sensor seems not to be reporting (even in CIT or sensor apps) although the device can still know its orientation because TYPE_GAME_ROTATION_VECTOR is being reported.
Second, the magnetometer seems to be shifted and I can't calibrate it properly, notably in Google maps it shows a shift of about 50 degrees clockwise (when I'm pointing the true north, it reports 310 degrees instead of 0). When I try the 8 shaped thing, it doesn't properly calibrate itself. I also tried CIT and it efectively shows the north about +50 degrees clockwise. This fixed itself I don't know how.
Are you having this kind of issues in V10 or in other V11?
ZareliMan said:
Hello
I recently updated to Miui V11 Global on my MIX 2S and started noticing some issues with the magnetometer and gyro. Version 11.0.4 (PDGMIXM).
First the Gyroscope Sensor seems not to be reporting (even in CIT or sensor apps) although the device can still know its orientation because TYPE_GAME_ROTATION_VECTOR is being reported.
Second, the magnetometer seems to be shifted and I can't calibrate it properly, notably in Google maps it shows a shift of about 50 degrees clockwise (when I'm pointing the true north, it reports 310 degrees instead of 0). When I try the 8 shaped thing, it doesn't properly calibrate itself. I also tried CIT and it efectively shows the north about +50 degrees clockwise. This fixed itself I don't know how.
Are you having this kind of issues in V10 or in other V11?
Click to expand...
Click to collapse
I have the same problem
ZareliMan said:
Hello
I recently updated to Miui V11 Global on my MIX 2S and started noticing some issues with the magnetometer and gyro. Version 11.0.4 (PDGMIXM).
First the Gyroscope Sensor seems not to be reporting (even in CIT or sensor apps) although the device can still know its orientation because TYPE_GAME_ROTATION_VECTOR is being reported.
Second, the magnetometer seems to be shifted and I can't calibrate it properly, notably in Google maps it shows a shift of about 50 degrees clockwise (when I'm pointing the true north, it reports 310 degrees instead of 0). When I try the 8 shaped thing, it doesn't properly calibrate itself. I also tried CIT and it efectively shows the north about +50 degrees clockwise. This fixed itself I don't know how.
Are you having this kind of issues in V10 or in other V11?
Click to expand...
Click to collapse
In the end I solved it by installing a stable Chinese ROM, I installed several global ROMs and the sensors still did not work, although the installation of the Chinese Rom failed and stayed in the boot logo, then I installed a custom ROM and all the sensors worked again. It cost a lot but it worked. If you have already tried installing several ROMs, try installing a Chinese ROM and then changing it worked for me. good luck to everyone
Related
Mine seems to be really sensitive so that the screen rotates even if I tilt the phone a small amount. Is there any way to fine-tune it?
--
Sent from my HTC EVO 4G using Tapatalk Pro.
Wondering this also since I noticed there is no calibration for it in CM6.
Don't know about on CM6 but on other roms, go to Settings > Display > G-Sensor calibration.
Anyway to do this on non-rooted phones? Ever since I upgraded to Froyo it seems to rotate if I tilt it even just slightly off it's axis
Those directions were for rooted and non rooted phones...
Greenfieldan said:
Anyway to do this on non-rooted phones? Ever since I upgraded to Froyo it seems to rotate if I tilt it even just slightly off it's axis
Click to expand...
Click to collapse
Turn off garbage rotation with Switchpro
Anyone gotten a reply from Cyanogen? I messaged him on Twitter, but he never responded.
If you download, GPS Status from the market and in settings under " Help and release notes " it says this...........
My compass points to the wrong direction or I'm asked to calibrate my compass. What should I do?
Your phone contains a digital compass which measures the magnetic field's strength in three direction with three separate sensors. The orientation of your phone is calculated from these values. Unfortunately the sensitivity of the sensors are a little different. To correctly calculate your orientation your phone must measure first these differences. This is done during the calibration process. To calibrate your phone, simply find a space where no external magnetic field is present (preferable outside of buildings) and rotate your phone 1-2 times on EACH of its three axes (Swinging your phone in big 8s in all direction will also do, but it' less scientifically correct ). If you feel that your compass has become inaccurate you can repeat this procedure.
But i dunno if it works or not..
BAleR said:
If you download, GPS Status from the market and in settings under " Help and release notes " it says this...........
My compass points to the wrong direction or I'm asked to calibrate my compass. What should I do?
Your phone contains a digital compass which measures the magnetic field's strength in three direction with three separate sensors. The orientation of your phone is calculated from these values. Unfortunately the sensitivity of the sensors are a little different. To correctly calculate your orientation your phone must measure first these differences. This is done during the calibration process. To calibrate your phone, simply find a space where no external magnetic field is present (preferable outside of buildings) and rotate your phone 1-2 times on EACH of its three axes (Swinging your phone in big 8s in all direction will also do, but it' less scientifically correct ). If you feel that your compass has become inaccurate you can repeat this procedure.
But i dunno if it works or not..
Click to expand...
Click to collapse
That just calibrates the compass.
Hello everyone,
To fix the dialer bug thing, I applied all the suggestions which were mentioned here http://code.google.com/p/android/issues/detail?id=17383 like using the proximity sensor app, etc etc....
Now I am getting a good battery backup like 12+ hrs on a full charge (without using wifi/data).
So now the problem is that when I am playing a game say cut the rope, the game goes in potrait mode which is fine, but if by mistake my finger hovers over (or touches) the proximity sensor area, the screen goes off and locks. This is frequently happening
Is anyone facing this issue?? Is there a fix to this??
There are several topics on red dim light (emitting out of proximity sensor) on the galaxy note 2 just left to the front facing camera. I was having same problem for 2-3 days back, one of two sensors beside front facing camera lit up continuously showing red dim light even with phone screen off or at standby mode. I searched a lot about this topic and was disappointed. There was also solution given by one senior member about uninstalling Viber, Viber was found as culprit messing with proximity sensor and keeping it on all the time. This really helped a bit. Here is solution.
It is not only Viber a culprit but you have to go into flashback and recall which was the last app you have installed after which actually the problem started, mine was rockettalk, all these are kind of apps which deal with instant messaging, internet calling, etc Just recall and find out such app and uninstall it, after that just reboot your device and check whether the quick glance feature is off i.e., settings/motion/quick glance, make sure it is not ticked. Reboot our device and thats it........!!! The annoying red dim light is gone :laugh:
i9100 proximity sensor doesn't work
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
During calls the proximity sensor isn't working properly. The display keeps going on and off and many times you end up having accidental touches which can lead to the pulling down of the notification drawer and even cause apps to open randomly.
However, it behaves differently with every single occasion I get to make a call. Sometimes it works better and sometimes it's worse. It also seems to be influenced by the environment I'm in. If for example I'm inside my apartment talking on the phone, when I move from a darker area of the room towards the open window and vice-versa, it seems to be triggering the light sensor which is somehow communicating with the proximity sensor, thus causing the display to go on and off.
Can anyone confirm this issue?
Yes, even I have observed the same, sometimes it works like a charm and sometimes it just keeps toggling very badly.
Same thing happens with my device. It's comman with many Xiaomi devices I purchased in the past. Maybe a software update will fix it.
My Proximity Sensor always turn off screen after click "Call" without near my face. I just got a new redmi note 7 pro replacement because that.
Just updated to the latest MIUI China Stable 10.3.5.0 version and the bug appears to have been solved. I've tested it in different lighting conditions and the screen stays off in each and every scenario. So that's one less bug to deal with.
My pixel 4a's proximity sensor related functions (tap to wake, always on display, screen off during call) are not working properly
The hardware seems working fine while checking.
What may be causing the issue, and is there any way to fix this on latest versions???? Please someone help
The problem was with the device itself. By checking with sensor test application, proximity sensor shows value 0.5cm and covering the sensor shows 0.0cm. The problem is it won't turn back to value 0.5 ( not covering condition).
It stays at 0.0
By just applying some pressure to my display on the edge, it's working fine.
Recently I dropped my phone and the display might have some gap with the frame or something.
I have seen so many people on the internet have complaints similar to this across different pixel devices, that's why I thought of it might be a software issue.