Hi there,
i'm currently on the newest cm13 nightly and if i'm updating my system my compass is always completly wrong. After different solution for the compass calibration it will work till the next update again. Is there a way that the compass has not to be calibrated on every update? it's really annoying because sometimes the calibration works instantly and then sometimes it takes more than 10 minutes.
Especially if i want to use gps and have not calibrated after update, it can be that i need much time for calibration to get gps work..
Thanks
Related
Can someone PLEASE tell me how to calibrate the compass on this thing? I have tried the figure 8, and also going to setting>display>E-Compass calibration it just keeps saying:
Please rotate DUT according X, Y and Z-axis respectively! until accuracy equal 3.
Then says Calibration Finish, and a little video, but nothing ever changes, and there is nothing to press to calibrate it.
I'm a little curious on the compass calibration too. The compass is jittery, it's like voltage fluctuations or something. I'm wondering if it's a actual hardware problem or its it's a software problem. ... .. still not too sure about this phone I got about 15 days left to return it.
Sent from my jittery ass compass MOTWX435KT using Tapatalk...lol
I'm having the same problem with the compass. I did the initial calibration but even now it's almost always +/-30 degrees off on way or the other.
I do see a little improvement if I do the figure 8 or rotate it around all three axis whenever I want to use it.
I also hope it's just software and there's a fix for it. So far I haven't had any luck downloading other compasses and re-calibrating it through them.
I haven't had any issues, but the app "GPS Status" has an option to calibrate the compass. Might be worth a shot.
Ever since i did the update, the GPS takes several minutes to get a lock. Even if I exit Google Maps after it gets a lock and then re-start GMaps again within seconds, it takes again several minutes to get a lock. As if it is doing cold start every time GMaps gets active.
Before OTA update it would take a second to get a lock after just exiting GMaps and re-starting it. A couple of hours later, and dozen miles away, it was still locking within 10 seconds.
Now everything takes many minutes.
GPS Status is showing strong signal from 4-5 satellites, but GMaps is not locking.
Does anyone else have similar problem?
Are you actually getting a lock from gps status or just 4-5 satellites?
I had a similar problem before the update, first lock took about half an hour in gps status, after that it was quicker but still not great.
Sorry to report the update fixed the issues in my case. It could be due to the old radio being better suited to your geographic location than the new one. Unfortunately its hard to really test this unless you are willing to s-off and test some radio/ril combinations.
Sent from my Cyanogenmod hungry Htc Sensation.
My experience is pretty much the opposite of the OP. I've noticed GPS locks are much faster after the OTA. Using GPS Test they were fast before, typically less 15 sec and nearly always under 30 sec, and after the update closer to 5 sec. However, over time I've seen a good bit of variation day-to-day so I can't say with any certainty that my observation is directly related to the OTA. And based on the reports in this thread it seems likely the OTA didn't fix or break GPS.
I have seen Google Nav take much longer than GPS Test to get a lock. I've also had it completely hang my phone where a battery pull was the only option. This when GPS Test would work fine. So I'm quite certain that Google Nav is buggy. Mostly it works, but sometimes not. If it's taking too long to get a lock I will exit, use GPS Test to get a lock, then go back to Nav and it typically locks quickly.
Regarding GPS Test taking minutes to lock that's most likely due to either not having a data connection or a corrupted ephemeris. If you do have a data connection then use the options to clear and update the AGPS data. The next lock may take 20-30 sec but after that it should be back to normal.
samnada said:
My experience is pretty much the opposite of the OP. I've noticed GPS locks are much faster after the OTA. Using GPS Test they were fast before, typically less 15 sec and nearly always under 30 sec, and after the update closer to 5 sec. However, over time I've seen a good bit of variation day-to-day so I can't say with any certainty that my observation is directly related to the OTA. And based on the reports in this thread it seems likely the OTA didn't fix or break GPS.
.
Click to expand...
Click to collapse
EXACTLY the same as that.. 6+ satellites in less than 10 seconds (usually about 5) and the same is true when using google maps.
same thing here instant lock few seconds
less then 30 sec inside
The thing with the GPS Status is that it is showing many satellites with strong signal (i.e. 11 with green bars) but it is not locking either for minutes.
alexsql said:
The thing with the GPS Status is that it is showing many satellites with strong signal (i.e. 11 with green bars) but it is not locking either for minutes.
Click to expand...
Click to collapse
Are you running stock or a ROM?
I'm on stock and have seen this a couple of times. I've been able to fix it by clearing and reloading the AGPS data. This can be done under Settings in GPS Test (https://market.android.com/details?id=com.chartcross.gpstest&hl=en).
OK, i fixed it.
I am on stock and I've tried reloading AGPS but that did not fix it.
I used GPS Status ->Settings ->GPS&Sensors ->Sensor Filtering
After I changed the filtering from Weak to None the GPS locks within seconds.
The weird thing is that now, if I change the filtering back to Weak or even Strong, it still locks in seconds
alexsql said:
OK, i fixed it.
I am on stock and I've tried reloading AGPS but that did not fix it.
I used GPS Status ->Settings ->GPS&Sensors ->Sensor Filtering
After I changed the filtering from Weak to None the GPS locks within seconds.
The weird thing is that now, if I change the filtering back to Weak or even Strong, it still locks in seconds
Click to expand...
Click to collapse
When you say reloading AGPS didn't fix it, how long did you wait for a lock? It can take longer for the first lock after reloading than normal. From your description it may have been the AGPS reload that actually fixed it, then once it got the first lock it was back to the normal fast locks regardless of the filter setting. Just a guess. I haven't played with the filter setting since far as I can tell it's only available in GPS Status, which I normally don't use.
Regardless, glad it's resolved. Also glad to know about that filter setting for future reference.
I did AGPS reload 2-3 hours ago and it did not work until I did the filter thing.
alexsql said:
I did AGPS reload 2-3 hours ago and it did not work until I did the filter thing.
Click to expand...
Click to collapse
Ok. That does seem odd. Also odd that changing the filter back didn't break it. Hard to diagnose that without knowing a lot more about how it works underneath. Still a useful trick to know about. Thanks.
samnada said:
Ok. That does seem odd. Also odd that changing the filter back didn't break it. Hard to diagnose that without knowing a lot more about how it works underneath. Still a useful trick to know about. Thanks.
Click to expand...
Click to collapse
That filtering is for the sensors for your gyroscope on the device not the GPS. It smoothes out the display in the program so your "bubble" in your compass isn't jittery.
Hi everybody,
Just noticed I'm having some issues with sensors being used 100% of the time by navigation apps, eating up my battery like crazy.
First I've noticed Sygic 11.2.6 showing as the second battery consumer (about 25% of the total battery usage at any given time) with orientation sensor used 100% of the time even though no process related to Sygic was running.
Restarting would fix the problem, only for it to reappear as soon as I started Sygic again.
After I've uninstalled Sygic I noticed Google Maps 6.6.0 having about the same behavior, using the accelerometer 100% of the time even after force closing the app. Again, restarting the phone would fix the issue but running Maps once would make it appear again.
I tried uninstalling the updates, reverting to version 5.8.0 and no more accelerometer issues. Updated to 6.6.0 and started having the same issues again. Uninstalling the updates once more and again no sensor issue.
One interesting thing is that if I restart the phone and then disable auto-rotation, once I run Sygic or Google Maps 6.6.0 the apps start using the orientation/accelerometer sensor 100% of the time just like they use to (even though it's disabled!!!!...?!?!).
To me this would seem like a software issue. Anybody else experiencing something similar?!
Thank you in advance for your opinions!
Inginerul said:
Hi everybody,
Just noticed I'm having some issues with sensors being used 100% of the time by navigation apps, eating up my battery like crazy.
First I've noticed Sygic 11.2.6 showing as the second battery consumer (about 25% of the total battery usage at any given time) with orientation sensor used 100% of the time even though no process related to Sygic was running.
Restarting would fix the problem, only for it to reappear as soon as I started Sygic again.
After I've uninstalled Sygic I noticed Google Maps 6.6.0 having about the same behavior, using the accelerometer 100% of the time even after force closing the app. Again, restarting the phone would fix the issue but running Maps once would make it appear again.
I tried uninstalling the updates, reverting to version 5.8.0 and no more accelerometer issues. Updated to 6.6.0 and started having the same issues again. Uninstalling the updates once more and again no sensor issue.
One interesting thing is that if I restart the phone and then disable auto-rotation, once I run Sygic or Google Maps 6.6.0 the apps start using the orientation/accelerometer sensor 100% of the time just like they use to (even though it's disabled!!!!...?!?!).
To me this would seem like a software issue. Anybody else experiencing something similar?!
Thank you in advance for your opinions!
Click to expand...
Click to collapse
Yes... noticed this with Sygic. It's a known app bug, and they still haven't fixed it yet. Haven't had this issue with Google maps though. Be warned however that any navigation app will chew up your battery very fast... Can't help it since it's accessing the Net, Compass, Accelerometer and GPS antenna - all at the same time at a high refresh rate...
Thank you fir your reply!
I know navigation is supposed to use a lot of battery but doing it even with processes closed?
It's good to know you confirm the Sygic bug. Honestly I've googled for 2 days and wasn't able to find any useful info about such a bug with Sygic. And for me, since Google Maps 6.6.0 acts the same way, it makes me think it's also a bug. For now I'm sticking to Maps 5.8.0 and I've reported the issue over to Google.
Thank you again!
Does anyone ever have the issue of the compass always pointing in the wrong direction?
I've done manual sensor calibration by going into the service menu (*#0*#, Sensor) quite a few times but the compass always resets.
levitron said:
Does anyone ever have the issue of the compass always pointing in the wrong direction?
I've done manual sensor calibration by going into the service menu (*#0*#, Sensor) quite a few times but the compass always resets.
Click to expand...
Click to collapse
Probably would have been best to not start a new thread for this since you already commented in another one.
My compass is still fine and working properly from my one calibration from the other thread. Are you getting the blue compass line with a "3" next to it?
I had the "3" and blue line. It was pointing to the true North after calibration. Then it lost the calibration. I've since recalibrated it.
I'm keeping an eye out on this. Will monitor it.
So after a few weeks of testing, I've concluded that the compass resets every time I reboot my phone. This happens consistently without fail.
The fix for me is to do a calibration every time I reboot the phone - this means "twirling" my phone in a circular motion (it's faster than doing the separate axis calibration). Usually this will recalibrate my phone in under 10 "twirls".
I guess it's something to do with the compass not being able to store the calibration permanently. Perhaps it's a R/W permissions issue. I'm on stock Three UK firmware, not rooted.
Hi. I've been experiencing severe issues about GPS and navigation on my OPO, which is exrtemely frustrating.
I can't have a decent navigation system on my device, as the blue pointer on Google Maps is usually extremely vague about the position and sometimes, even if I start the navigation, the pointer doesn't follow my track, stuck on my starting place.
I tried everything: the problem appeared to be solved on CM 12, but then I had to downgrade back to CM 11 because the battery was draining so fast.
Any idea? Thanks!