Hi all,
I've found that in the Google Maps app, the direction that the app thinks I am facing is almost invariably wrong, and often varies wildly even when I'm not moving. I think it is related to the rotation vector sensor (Sensor.TYPE_ROTATION_VECTOR) but I was wondering if others had experienced similar problems.
I've looked at the various sensors (and compared them to a Nexus 5) and two stand out: the Uncalibrated Gyro (Sensor.TYPE_GYROSCOPE_UNCALIBRATED), and the Rotation Vector (Sensor.TYPE_ROTATION_VECTOR).
The Uncalibrated Gyro seems to sit with a z-axis value of 1.17 rad/s, and the rotation vector *sometimes* seems to stick at a high value too.
Anyway, the question is:
(1) Do other people find that Google Maps tends to detect them pointing in the wrong direction, or turning when they are in fact not turning, and
(2) Do other people find that the rotation vector sometimes sticks at a weirdly high value (if they have the tools to check: I wrote one to check myself, which I can attach if desirable but being unknown I don't know if anyone would trust to install it =)
Cheers.
This may seem a basic question, but did you try calibrating the compass via the service menu?
Enter *#*#7378423#*#* in the dialler.
Service tests
Compass
Follow the on screen guide.
That always seems to correct any "creep" or odd readings with my compass and gyro. You can also check the gyro from the service test menu.
Sent from my C6603 using Tapatalk
kingvortex said:
This may seem a basic question, but did you try calibrating the compass via the service menu?
Click to expand...
Click to collapse
Cheers, I did do that but it didn't seem to make a difference. However, now GMaps seems to be working pretty well so that's good. (It's done that before, but maybe this time it will last). However, the game Ingress is still having problems (which it doesn't have under Stock). Like GMaps, it tries to detect the direction you are facing. On Stock 4.4.4, Ingress does a tolerable job of detecting direction of facing - it mostly gets it right. However, using CM11 the behaviour is really weird: turning the phone has no effect until a tipping point, at which it is detected that I've done a sudden 180, and if I keep turning the phone it eventually happens again. Doing the phone-calibration-twirl has no effect in this case. (Note: that is rotational movement with the phone laying flat on a table, and a metaphorical tipping point. I'm not standing the phone up until it tips over)
Maybe related, but maybe not: Having done some more testing with a few ROMs and kernels, what I've found is that CM11 (both official and _infected builds, with both the included kernel or the multirom-modified kernel) don't provide a TYPE_GYROSCOPE_UNCALIBRATED sensor (where as the stock 4.4.4 ROM does).
That said, Ingress doesn't appear to *use* the TYPE_GYROSCOPE_UNCALIBRATED (instead only using LINEAR_ACCELERATOR, ROTATION_VECTOR and MAGNETIC_FIELD) so I'm a bit confused. (Edit: I believe these are the sensors being used based on the hex values being passed to getDefaultSensor in the smali of Ingress.)
The sensor results for both stock and CM11 look to be about the same, with the exception of the 'Uncalibrated Gyroscope' not being present in CM11 whereas it is present in stock 4.4.4. I think that sensor missing is probably a bug, but I'm not exactly sure where to report what is probably a device-specific bug for CyanogenMod.
tl;dr;
Calibration movements might have fixed it in Google Maps, but Ingress is still having problems in CM11 (but not Stock 4.4.4).
I think there is a sensor missing in CM11 that is in stock, and that's probably a bug. Where should a device-specific yuga bug in CM11 get reported?
This may seem a basic question, but did you try calibrating the compass via the service menu?
Enter *#*#7378423#*#* in the dialler.
Service tests
Compass
Follow the on screen guide.
That always seems to correct any "creep" or odd readings with my compass and gyro. You can also check the gyro from the service test menu.
Sent from my C6603 using Tapatalk
Sent from my C6603 using XDA Free mobile app
---------- Post added at 10:03 AM ---------- Previous post was at 09:19 AM ----------
Sorry guys for this copy paste, my mistake.
I have exactly the same problem.
Calibration do nothing.
Sent from my C6603 using XDA Free mobile app
Related
looks like data output of my captivate's sensors is reverted with accelerometer, that means I starting any compass app and puts phone to horizontal surface and rotates it clockwise and counterclockwise, normally compas should rotates but it doesn't.
When I put it at an angle to the surface, compass starts rotating. Behaves itselfs as the accelerometer sensor
The strange thing is that compass working like a charm on KK4 modem, but I can't use KK4 modem on CM\MIUI build because of abnormal sensitivity (it is too sensitive) of mic during call, the caller can't hear me clearly.
I trying to google for this problem but didn't find anything usefull, also I tries to calibrate it, of course it didn't help
Any ideas how to fix the problem, its really annoying me during GPS navigation-the map alvays rotating?
P.S. now I'm using MIUI-1.12.9.10 I9000XXJVT baseband and Glitch v13 kernel
I'm actually seeing the same thing; my compass seemingly responds primarily to accelerometer or gyroscope detected motion (or the magnetometer is just busted). As far as I know, this only started happening after I updated to KK4 and installed CM7 over it (the compass was fine under CM7 installed over KB2). I've tested other modems, including KK4, to no avail. Flat surface calibration (face up and face down) and the compass calibration (using the figure 8 rotation) indeed do not help.
Has anyone else experienced this issue and/or have any suggestions? Could this at all be related to GB bootloaders? I doubt the latter to be the case, but I'm all out of ideas here, because outside of things within the OS, that's the only thing I can think of that's changed.
ROM: CyanogenMod v7.2.0 RC0 KANG
Kernel: Glitch v13.1
Modem: JK4
So I cleared /data/system/yas529.cfg and rebooted the phone, and the system created a new file one on startup. This seems to have... changed... something. That is, the phone seems to be reading the magnetometer now, but it's behaving crazily. Firstly, the compass reads west when the phone is pointed north. Secondly, when I move the phone counterclockwise, the compass actually also spins counterclockwise, so when I reorient the phone from north to west, the compass actually points from west to north.
Compass recalibration via figure 8 motion and pitch/roll recalibration (both with phone face up and face down) don't help. Anyone familiar with /data/system/yas529.cfg, and what a "good" copy looks like? Mine currently has the following values:
Code:
13,19,16,174,26,-158,3,255,255,255,2147483647,2147483647,2147483647,0,
The previous one that seemed to respond primarily to accelerometer/gyroscope had the following values:
Code:
14,19,16,-46,52,-170,3,255,255,255,2147483647,2147483647,2147483647,0,
Well. I have no idea why this worked, but I decided to revert to stock KK4, then reinstalled CM7, starting with 7.1.0, then worked my way up to 7.2.0-RC0.
Testing the GPS again, the compass is working fine now. Looking at /data/system/yas529.cfg, I see the following:
Code:
14,19,16,39,-49,159,3,255,255,255,2147483647,2147483647,2147483647,0,
While in KK4, I also rooted and checked this file, and saw the following:
Code:
13,19,16,36,185,150,3,255,255,255,2147483647,2147483647,2147483647,0,
In either case, the compass worked fine. Perhaps worth noting is the fact that the 6th item in the list is actually positive, which may or may not be related to my previous observation that the compass rotation made no sense (not sure, really). I tried negating that number to see if I could reproduce the issue, but it didn't work (and in fact, calibrating the compass only flipped the number to positive, even though calibration always used to set it negative). Not sure what to say.
Anyway, all looks well now. For anyone else who runs across this issue, the only thing I can suggest is for you to just try reinstalling CM7 (and possibly reverting all the way back to stock if reinstalling alone doesn't help).
I find different apps have different results. There are compass apps that work. Keep looking
Sent from my SGH-I897 using xda premium
I didn't test only a single compass app; I tested several apps (Maps, GPS Essentials, GPS Status, to name a few), tested several different modems (JL3, JK4, KK4, to name a few), and calibrating various sensors (accelerometer/gyroscope, magnetometer, GPS). Nothing helped.
After the reinstall, the exact same apps with the exact same modems are working. The fact is that something was screwed up with the install that caused this.
- When the compass wasn't working, my install process was: KK4, Corn Kernel (without rooting), then straight to CM 7.2.0-RC0.
- Before then (when the compass was working previously), my install process was: KB2, root, CM 7.1.0, and then nightlies upward to 7.2.0.
- This time around (with the compass working), my install process was: KK4, Corn Kernel (with root), then CM 7.1.0, then CM 7.2.0-RC0.
I'm not sure I'm up for reinstalling repeatedly just to eliminate possibilities, but I suspect it may have been an issue with the install/upgrade process itself. Or just a random glitch. Either way, the moral of the story is that if nothing else helps, try reinstalling (possibly from stock).
For some reason my compass seems to be poorly calibrated and when I use Google Maps the navigation works, but I sometime lose direction. In order to fix I need to rotate my phone in all different ways. But after a reboot the compass goes back to being off. Does anyone else have this issue? Is this a defect or software?
I found exactly the same issue yesterday trying to navigate around London. Google maps has been dodgy lately on my note 3, xperia z and my girlfriends HTC one s so I put it down to a bug, I might try another navigation app to see if it's the phone
BrandonPrice31 said:
For some reason my compass seems to be poorly calibrated and when I use Google Maps the navigation works, but I sometime lose direction. In order to fix I need to rotate my phone in all different ways. But after a reboot the compass goes back to being off. Does anyone else have this issue? Is this a defect or software?
Click to expand...
Click to collapse
Are you using a case? Particularly one with metal in it such as an s-view case. If so, you have to recalibrate the compass after every reboot.
jonstatt said:
Are you using a case? Particularly one with metal in it such as an s-view case. If so, you have to recalibrate the compass after every reboot.
Click to expand...
Click to collapse
this is not dependant on cases etc., same here as on note3, ... : with each reboot the calibration resets. maybe this is how samsung wants it to be!
jonstatt said:
Are you using a case? Particularly one with metal in it such as an s-view case. If so, you have to recalibrate the compass after every reboot.
Click to expand...
Click to collapse
I'm using the s view case hmmm
TML1504 said:
this is not dependant on cases etc., same here as on note3, ... : with each reboot the calibration resets. maybe this is how samsung wants it to be!
Click to expand...
Click to collapse
Do you have same issue?
This has been an ongoing issue with Samsung Phones. This is my 3rd and and none of them have worked correctly in Maps, without navigating.
When you are just driving around (not navigating) you are using the compass....
When you are navigating, Maps is using the GPS and comparing your last point to your current point to determine your direction of travel. This causes navigating to work right and non-navigating to be wrong.
I have not found a consistent solution. Also on Google Skymap, with the AR type view, it is nearly useless for this same reason. It can't seem to sense your proper orientation due to the compass issue. (though I admit to not trying skymap on the Note 4)
Its not so much a bug, as it is Samsung and Google doing things differently.
boufa said:
This has been an ongoing issue with Samsung Phones. This is my 3rd and and none of them have worked correctly in Maps, without navigating.
When you are just driving around (not navigating) you are using the compass....
When you are navigating, Maps is using the GPS and comparing your last point to your current point to determine your direction of travel. This causes navigating to work right and non-navigating to be wrong.
I have not found a consistent solution. Also on Google Skymap, with the AR type view, it is nearly useless for this same reason. It can't seem to sense your proper orientation due to the compass issue. (though I admit to not trying skymap on the Note 4)
Its not so much a bug, as it is Samsung and Google doing things differently.
Click to expand...
Click to collapse
So you have this issue with the Note 4 when using Google Maps while driving? Moving my note in all directions calibrated it but then reboot forgets.
BrandonPrice31 said:
So you have this issue with the Note 4 when using Google Maps while driving? Moving my note in all directions calibrated it but then reboot forgets.
Click to expand...
Click to collapse
I dont mess with the recalibration process. Its annoying and i hate it, but its not so bad that i recalibrate. I also dont reboot very often, but in the past, the recalibration doesnt stick for long even when not rebooting.
I love google maps for navigating, but it sucks for driving around. The biggest issue is that the screen turns off on its own when not navigating. Waze is great for driving around, it doesnt shut off the screen, and gives you all the traffic info you need. It also routes the voice through the phone regardless of if you are connected to the car by bluetooth. The biggest complaint with waze is that it isnt multi window compatible. On my rooted note 2 i used waze on the left of the screen for traffic issues, and maps on the right side of the screen for navigation.
Hi!
I am facing problems with the orientation sensors (accelerometer and/or gyroscope), because installing several applications to test them (or use games), it is clearly observable, that they are a bit off (with enough to be disturbing when required). For example, games or tests that simulate a ball, and my phone is laying on a horizontal table, the ball rolls quickly to the edge of screen. This happens as well with the built-in tests in the "service menu" of the phone, for accelerometer and gyroscope also.
Do you have any suggestions how could I calibrate these sensors globally (for every app)?
Thanks.
Info
vetko said:
Hi!
I am facing problems with the orientation sensors (accelerometer and/or gyroscope), because installing several applications to test them (or use games), it is clearly observable, that they are a bit off (with enough to be disturbing when required). For example, games or tests that simulate a ball, and my phone is laying on a horizontal table, the ball rolls quickly to the edge of screen. This happens as well with the built-in tests in the "service menu" of the phone, for accelerometer and gyroscope also.
Do you have any suggestions how could I calibrate these sensors globally (for every app)?
Thanks.
Click to expand...
Click to collapse
factory Reset ur phone and then use PC companion app to Repair Firmware...
this can wipe current data and install fresh firmware on ur device
:good:
Hi,
I have the same problem. Only the x axis of the accelerometer seems to be affected : it show a value around 1 instead of 0 while the phone is sitting flat. Y and Z display normal values.
All the software solutions I have tried have had no effect at all... It seems the built-in test reads raw data from the accelerometer. It is hard to imagine how this can be a hardware problem though...
Anyway, in my case I believe a software fix (x=x-1) would do the trick but I have no idea how to do such a thing ! Any help ?
@vekto : Have you solved the issue by any chance ?
Would anyone care to try the accelerometer tests and post their results ?
Typing *#*#7378423#*#* will get you on the service menu. The two significant tests are "accelerometer" and "gyroscope".
I'd post some screenshots myself but I'm not allowed yet...
I'm having the same problem now. It seems one axis is affected. Haven't found a way around so far. This is sad because it affects the images taken with Google Camera Sphere mode. The images are badly aligned together with glitches in between. My phone wasn't like this before.
Either a SW fault - might be able to calibrate with GPS Status & Toolbox app, for example - or a FW fault - and reflashing ROM might help (highly unlikely) - or HW fault - the sensor has moved on the board (which is a bad sign anyway, might be on the way to disconnecting itself).
I sent mine to Xperia Care and got it back with the accelerator fixed. Still unclear if it's a HW problem...
It came back with a white spot on the screen (near the power button) though... so I sent it back again
I'm also having issues with the gyroscope. Installed Bubble app to calibrate the gyro. It showed the gyro was of a couple of degrees. Unfortunately the bubble app calibration doesn't work in a game like Need for Speed. It's very difiicult to achieve good times in the game right now since I have to hold it tilted to the left to go straight ahead.
So if anyone has a fix or workaround... Please do post.
Same problem, Seems after factory reset whith wipe dalvik cache.
any solution?
02nd March 2017, my autorotate has completely stopped working, restart, safe-deposit and reset do not fix. Diagnostics show Gyroscope Light Sensor and accelerometer failed testing, 3 years of same issue, surely there must be a fix that works by now?? ( please note, " turning it off and on again " does not fix it )
Helps Please
I have the same issue. Since last week, gyro, accelerometer, light and proximity sensors stop working. I've tried reflashing stock ROM without success. I have not warranty (almost 3 years old), so I even try to disassemble , disconnect an reconnect every flex (I don't know exactly were the sensors are located on the board). After that I get almost 8 hours of fully functionally sensors and then, they stop working again, so I'm almost sure it's a hardware issue.
Same problem for 3 years
I'm just now getting around to doing something about this. As my power button stopped working I can't post requested screenshot without going to the pc. I have been shopping new (fall 2018) phones after having the Z3+ since release. In my research I'm finding the phone still is better than Samsung, LG, and the pixel3 for me because the 3.5mm phone jack is mandatory for me using my device with an i-rig midi requiring both that port and the USB at the same time. I'm going to do everything I can to keep using this phone till it falls to dust. It's one of 4 Sony I've bought since the day Z1 came out of t-mo. I look forward to testing solutions. :good:
Some time after my post, I bought a new jack/proximity sensor flex and replace it. This solved the issue, but weeks later, the bottom portion of the touch screen becomes unresponsive. May be I have done something wrong... may be programmed obsolescence...
Hi I'm facing a problem of my gyroscope I don't know which one is not working a gyroscope or accelerometer. My gyroscope is so delay when I play pubg mobile and I can't also calibrate my Gsensor it always says FAIL but I put in a perfect flat surface please please please help me with this problems
I picked up the nexus 6 from AT&T a couple days ago and love it but I have one issue. The compass is off by 90 to 180 degrees. If I spin it around enough it usually calibrated itself but only lasts until the next time I start maps.
I've seen a couple of comments indicating similar issues but I'm not sure if it is a hardware issue and should be replaced.
Does the compass work correctly for everyone else?
Sent from my Nexus 6 using Tapatalk
Same issue here
I have the same issue with my Nexus 6 64Gb blue, bought in Germany from Amazon.de.
Calibration helps but it decalibrates soon, and then the compass is off by 90° or 180°.
DontHaveACLue said:
I picked up the nexus 6 from AT&T a couple days ago and love it but I have one issue. The compass is off by 90 to 180 degrees. If I spin it around enough it usually calibrated itself but only lasts until the next time I start maps.
I've seen a couple of comments indicating similar issues but I'm not sure if it is a hardware issue and should be replaced.
Does the compass work correctly for everyone else?
Click to expand...
Click to collapse
That would NOT be a hardware issue. That is entirely software.
doitright said:
That would NOT be a hardware issue. That is entirely software.
Click to expand...
Click to collapse
Why are you so sure it's a software issue if the sensor loses calibration no matter what?
max.shirshin said:
Why are you so sure it's a software issue if the sensor loses calibration no matter what?
Click to expand...
Click to collapse
heres one way to calibrate a compass in android.. https://www.youtube.com/watch?v=AzQSsUsOWJc
simms22 said:
heres one way to calibrate a compass in android..
Click to expand...
Click to collapse
Exactly, except that in case of Nexus 6 the calibration only helps for about half an hour. It corrects the compass sensor and it starts behaving as it should, only to start showing random direction when you open Google Maps the next time. I've been testing it for several days, both inside and outside, in different places, running calibration several times a day. In no less than a couple of hours (usually even faster) it goes nuts again.
If you own a Nexus 6 as well, and do NOT have this issue, please let us know where you bought the device and which exact model it was (white or blue? memory size?)
Thank you very much in advance!
ingdir said:
Exactly, except that in case of Nexus 6 the calibration only helps for about half an hour. It corrects the compass sensor and it starts behaving as it should, only to start showing random direction when you open Google Maps the next time. I've been testing it for several days, both inside and outside, in different places, running calibration several times a day. In no less than a couple of hours (usually even faster) it goes nuts again.
If you own a Nexus 6 as well, and do NOT have this issue, please let us know where you bought the device and which exact model it was (white or blue? memory size?)
Thank you very much in advance!
Click to expand...
Click to collapse
bought mine through tmobile. black(blue) 32gb version
max.shirshin said:
Why are you so sure it's a software issue if the sensor loses calibration no matter what?
Click to expand...
Click to collapse
Calibration *IS* a software function. You feed corrections into the compass driver to compensate for the magnetic fields generated by the phone itself. If it is losing calibration, it CAN ONLY be a software issue. The data generated by the compass HARDWARE is not affected by calibration. The calibration adjustments are applied to values after they have been received from the hardware by the driver, and before being passed on to userland.
---------- Post added at 08:02 PM ---------- Previous post was at 07:50 PM ----------
ingdir said:
Exactly, except that in case of Nexus 6 the calibration only helps for about half an hour. It corrects the compass sensor and it starts behaving as it should, only to start showing random direction when you open Google Maps the next time. I've been testing it for several days, both inside and outside, in different places, running calibration several times a day. In no less than a couple of hours (usually even faster) it goes nuts again.
Click to expand...
Click to collapse
Are you totally certain that this is a function of losing calibration and not of needing a NEW calibration? The problem is that a compass reads magnetic fields. Nearly EVERYTHING generates magnetic fields, ABSOLUTELY EVERYTHING that uses electricity will generate magnetic fields. Everything with IRON in it will generate magnetic fields, typically in line with earth's magnetic field so it won't interfere (much), but if that thing with iron in it is MOVED, it will DEFINITELY interfere for quite a long time until it resets.
What the calibration does, is it tries to sort out all the competing magnetic fields in order to lock in to the true earth magnetic field. If you keep switching the compass on at different locations, then absolutely YES, it will spit out various incorrect values. In fact, if you go get yourself a regular old fashioned magnetic compass (with a needle on a pin in an oil bath) and you move it around, it WILL react to all the different things that produce a magnetic field.
Maybe try going into a forest, calibrating it, sitting around for a few hours (maybe a camp fire?), and then checking if it keeps its calibration.
doitright said:
Calibration *IS* a software function. You feed corrections into the compass driver to compensate for the magnetic fields generated by the phone itself. If it is losing calibration, it CAN ONLY be a software issue.
Are you totally certain that this is a function of losing calibration and not of needing a NEW calibration?
Click to expand...
Click to collapse
No, I'm not. Well, here are some possibilities to consider:
1. External magnetic fields affecting the phone in a way the compass goes nuts.
Before Nexus 6, I had Nexus 5 for 1 year and its compass worked perfectly in the same locations where Nexus 6 compass fails: same apartment, same office, same places around the city. Moreover, I don't even remember calibrating my Nexus 5, the compass just worked. Now I have Moto G as a temporary phone as I've sent my N6 back to Amazon, and Moto G compass works excellently as well -- again, no calibration required. So we have at least two devices with compasses working fine in the same environment.
2. Software bug that causes calibration data to be dropped.
I had the compass problem both on stock Lollipop and on CM. I also have a friend who did NOT have any compass issues while running exactly the same setup (first stock, then the same builds of CM) on the same Nexus 6 model. In Android, apps typically can't work with drivers on such a low level that could affect the calibration, and I don't run any special apps (except Google Maps) that do something with the compass. So it CAN be a software bug, but then it has to be very picky. Running a phone on pure CM without Google Maps for several days could be a good test as Maps is the only app that had something to do with a compass on my phone.
3. Some magnetic interference inside the device itself, or the sensor being too sensitive and/or having a hardware problem of its own.
This one seems the most likely to me, as it fits a pattern: the problem happens consistently on one device while never happening on other devices with identical configuration, several users have this problem (there are threads on reddit and other places, too) while the majority seems to be unaffected, and other devices with a compass work just fine in same locations.
Anyway, there obviously ARE devices around which can have a compass working just fine, and be it either a software or a hardware issue with Nexus 6, it's good if more people report a similar issue (or a lack thereof).
I have the same issue. I have calibrated from home and on the road in several states. I does not hold calibration.
I'm road warrior, and this is a real problem when traveling.
Sent from my Nexus 6 using XDA Free mobile app
Hi there,
I just bought a used Mi 5 to replace my previous one which I lost and I saw it as a good opportunity to try out the MicroG fork of LineageOS. I flashed the newest firmware and installed the OS and it's running quite well all in all – however I have two weird problems:
1. When using mapping software my compass seems way off. Is there an easy way to calibrate it?
2. (Potentially related) The device screen sensor is flipped when held horizontally. The screen orientation seems correct when held as usual, but as soon as I try to take a picture in landscape mode they turn out flipped upside down. Can anybody explain this? Can I overwrite this somehow?
Thanks a lot for any help
PS: I can't edit the title anymore so I'll add this as a separate paragraph. I've had problems with losing my signal at random intervals since I've had the previous Mi 5, with this one it's no different. Is this a known problem for Lineage-based ROMs? Any way to improve the situation there?
Hm.. so I tried the following firmware images from github/XiaomiFirmwareUpdater/firmware_xiaomi_gemini/releases (can't link to this unfortunately):
fw_gemini_miui_MI5Global_V9.6.1.0.OAAMIFD_e569ca4e32_8.0.zip
fw_gemini_miui_MI5_V9.6.1.0.OAACNFD_996b4bcbff_8.0.zip
fw_gemini_miui_MI5Global_8.7.19_7a80214a95_8.0.zip
They all show the same behavior regarding to the camera orientation bug. It's independend of the camera app in use. I also tried enabling and disabling the Camera2 module in Magisk, which did not seem to have any effect. I found a similar issue for the front camera after enabling Camera 2, but this seems to be unrelated.
Does the same happen with non microG versions of LOS?
Have you already calibrated the compass using the gestures in all 3d axis? Search for it on youtube.