Are you guys having problems with Google Map's compass mode? Even if I hold the unit steadily, the direction on the map starts changing randomly after a few minutes of use. It is really frustrating because I cannot get stable view. BTW, my device is C6833 on the latest stock ROM 532. So far I have checked 4 units and all of them have this same issue. Is it a known/common issue?
Hmm. The compass is fairly accurate in regular maps, but it goes full retard once i switch over to street view and choose the compass mode
For me 'maps' shows my heading accurately. Also in 'back country navigator' its very accurate.
I use it all the time for my job in search and rescue, so i would have noticed inaccuracy..
With street view it shows my heading, but does jump randomly when i select auto compass direction. The 'general' direction is ok, so say I'm heading north will often jump NNE and NNW all the time... so yeah, thats a bit stuffed up
Thanks for the feedback. I do hope it is just a software issue and the next update of firmware or Google Map can resolve it.
Having same trouble while using navigation, the compass go crazy. But if I only use map it work fine, I guess there is some trouble about it. First I believed something on my car where I place my phone was the reason, but i see i am not the only one having it.
Envoyé depuis mon C6802 avec xda premium 4
Related
Phone: Droid X2
Current ROM: Eclipse 1.2 RC1
I don't know how to best explain this, so here goes...
I could not replicate this problem in Stock Froyo, nor stock Gingerbread 2.3.3. The problem seems to appear in stock 2.3.4, and all 2.3.4-based Eclipse ROMs.
In Google Maps and Google Sky Map, the compass shows east and west in reverse. When I face east, the phone thinks it's facing west, etc. I've tried holding the phone in all practical orientations, and the problem persists. When I turn in one direction, the direction arrow in Maps goes in the opposite direction.
In the GPS Status app, the compass is properly calibrated and moving in the right direction, as if there were no problems.
Today's Google Maps update did not remedy the problem.
I've tried switching between or using both Google and VZW Location Services to no avail.
Any ideas?
Well, you killed my idea of calibrating. There may just be a glitch in the app. I haven't had any issues and I have the car dock, constantly use Google Maps/Navigation. I know they update frequently as hell. It also may be your phone... lol. I had the GPS antenna take a **** on my X1 when I hadn't even touched the phone in 3 weeks as I was in Germany and left the phone here. Thus, 1 of the 2 reasons I ended up in an X2
Interestingly enough, Navigation works fine as it is. I'm thinking either app or kernel associated with 2.3.4. I don't think it could be the phone itself. I SBF'd back to both 2.2.2, and later 2.3.3 to test earlier today, and there were no problems with either.
I have noticed since being on 2.3.4 navigation consistantly tells me my destination is on the left when it is on the right... and visa versa.
I just tried this out today. No issues still guys. I am on DX2 E1.2RC1.
---------- Post added at 02:35 PM ---------- Previous post was at 02:08 PM ----------
There is a Google Maps update right now in the market.
I updated to the latest Maps prior to posting this thread.
I had an update yesterday too, this was the 2nd update lol.
What version is it? My Market doesn't show any new update, and I'm currently on Maps v5.11.
oatmealboy said:
What version is it? My Market doesn't show any new update, and I'm currently on Maps v5.11.
Click to expand...
Click to collapse
That is current. It was released yesterday, the 20th
Sent from my DROID X2 using XDA App
Apparently the update didn't download last night, I tried to do it again and my market wouldn't load. I was still on 5.10.1, now on 5.11, I will let you know in a minute if it works.
---------- Post added at 06:28 PM ---------- Previous post was at 06:25 PM ----------
Now my North and South are flipped in compass mode. In Navigation mode it is correct though..
When facing NW is shows me facing SW.
I'm am on eclipse 1.2 rc3 and seeing the same thing this morning. with google maps. the arrow is pointing the opposite direction, same thing when switching to compass mode. hopefully a maps issue and not rom related. I will have to ask a couple liberty peeps it is happening to them.
** a little more information: this only seems to be an issue while standing still and rotating. When driving the compass is pointing/tracking correctly.
Mr_GreenJeans;18922006
** a little more information: this only seems to be an issue while standing still and rotating. When driving the compass is pointing/tracking correctly.[/QUOTE said:
Yep, I'm still having this problem even after flashing 1.2RC3. If you have Google Sky Map, try looking at the sky and rotating. It should also go in the opposite direction.
But yeah, I doubt this is a ROM issue, as it has been happening ever since I flashed to 2.3.4 (regardless of Google Maps version).
Click to expand...
Click to collapse
Same here. Just standing navigation is fine eclipse 1.3rc
Upon further investigation I have determined my orientation is approx. 90° off. Using both google maps and Swiss army compass to verify these findings. Also tried this out on another X2, completely stock 2.3.4 and got the same results. Looks like another 2.3.4 bug. Atleast it doesn't affect navigation, but using the compass, which worked before, is no longer an option.
Sent from my DROID X2 using XDA App
Everyone please confirm: pull " Location Sensor. apk" from the D3 system/app (I took from the D3 liberity rom) and install. Does not correct until reboot.
Boy we really are the black sheep in the family. I cannot believe the oversight on moto's part.
Edit:I had portrait screen on which works. Landscape no.
Edit: I think it only works in portrait. Right?
Maps 5.10.1
NOT A FIX, SORRY FOLKS.
skwoodwiva said:
Everyone please confirm: pull " Location Sensor. apk" from the D3 system/app (I took from the D3 liberity rom) and install. Does not correct until reboot.
Boy we really are the black sheep in the family. I cannot believe the oversight on moto's part.
Edit:I had portrait screen on which works. Landscape no.
Edit: I think it only works in portrait. Right?
Maps 5.10.1
Click to expand...
Click to collapse
Not working for me, pulled from D3 Liberty3 and put in /system/app/ fixed permissions and rebooted twice. still no change in maps or swiss army knife compass. Hopefully it works for others
I used super manager to install and it put it in data/app and uses a data/data also.
I use apksoftware's compass.
Edit: I nandroided back to a previous sys where I thought I had the bug but it works ok just not in landscape.
Hey, guys, I don't think it's Motorola's fault. I have HTC Rezound, Droid DNA and Note 3. All have the same problem. The arrow points about 90 degrees off.
How you all doing?
I use endomondo to track my bike rides. For the most part the tracking is pretty good when I check out a map after my rides, but sometimes it is off by want I would think is 30-60 yards. For example, I will be on a street, with clear view of the sky, and on the map it will look like I was riding right through houses or even in their backyards.
I ride on a local levy and about 60 yards down from it is a creek. Well it often looks like I rode in the creek the whole way.
So my question is, does anyone else use any sports tracking apps for running, walking or bike riding? If anyone does, can you tell me if your GPS tracking is the same way?
Thanks in advance.
endomondo, settings, "uncheck"- Enable Low Power Mode.
If not that its probably the signal in your area, i use endomondo too, it's obviously a phone and wont be so accurate but it shouldn't be jumping around alot.
Also make sure your cpu doesnt clock down because of your profiles and stuff if you're using a Oc/Uv app like Setcpu, it'll tune down accuray aswell.
Thanks for the info. I will try unchecking that option (it was on) and hopefully that helps. Thanks again.
Sent from my MB860 using xda premium
I had realized that the pointer in Google Maps doesn't point to the correct direction. Exactly like this video :
In Google Sky Map, its impossible to rotate 360 degrees, gets stuck in a certain area.
However, the compass works completely fine in pure compass apps, such as GPS Status, or the "Compass" app from Catch.com.
Could someone who have a Razr do a test and let us know if its working for you?
Your help would be much appreciated!
I can report the same issue!
brkelley said:
I can report the same issue!
Click to expand...
Click to collapse
Google Sky only works in horz., must be a Google API to the compass problem See if it works with the razr held flat.
Anybody else?
I can confirm having this issue in Google Sky Maps. No issue in the Compass app (Catch.com one), haven't checked GMaps, yet.
same problems here
chiehkai said:
I had realized that the pointer in Google Maps doesn't point to the correct direction. Exactly like this video :
In Google Sky Map, its impossible to rotate 360 degrees, gets stuck in a certain area.
However, the compass works completely fine in pure compass apps, such as GPS Status, or the "Compass" app from Catch.com.
Could someone who have a Razr do a test and let us know if its working for you?
Your help would be much appreciated!
Click to expand...
Click to collapse
Maybe a noob solution, but might wanna give the compass calibration tool in the GPS-status app a try, it fixed an orientation problem in Maps on my wife's charge...it was only reading accurate directions while moving...GPS vectoring worked, but when the phone relied on the magnetic orientation it pointed in the wrong direction... after compass calibration it worked fine
Hey guys,
am I the only one who thinks that Google Maps has gotten slower and laggier on our Galaxy SII with the ICS-Update?
Panning and Scrolling is a little choppy and the device gets very warm when using Google Maps for more than a minute. I tried to do some investigation and found out that the Latitude process is really heavy on the CPU, which might cause both issues.
Im using the latest Google Maps on the LPQ rom, and though this is not a dealbreaker, it's just not the way it's supposed to be for me.
PS: I'm not using Google's Latitude service at all, but i guess the latitude process is also used for locating you on the map.
Well I can say that yes, it does take some good seconds to switch to that Auto rotation mode (don't know the exact term), but otherwise it's OK. Besides it's not ICS but the app itself may not be well compatible yet!
Yes, it is slower on ICS for me too.
well, good to know it's not just my phone then, let's hope this will be fixed with an update soon, or maybe someone smarter than I will find out what's the cause
I've finally hit a breaking point with Maps 7.x. Has anyone else still been having problems with it, or better yet, not had problems with it?
This is a video showing some of the problems I've been seeing. Most noticeable is the jittering glitches. If I'm driving around, the screen is unreadable for directions or street names. At the end is a screenshot I took of a completely glitched out warning prompt to tell me "please enable wifi and mobile network to improve accuracy" though you'd never be able to guess that.
http://www.youtube.com/watch?v=yMAVZnMx3m8
I'm running Infection 2.9.1, and I've tried several kernels (ROM default, Hiro, and Funkybean) and switched up the governors and schedules, and nothing has seemed to work. I've tried disabling/enabling hardware overlays. I'm just at a loss, and hoping someone out there knows more than I do. I just finally had it because it's cool enough outside to run now without getting heat stroke, and Endomondo (my running app) freaks out and loses signal 5 steps into a run. Downgrading to Maps 6.x makes everything happy. Is sticking with the old Maps still the best solutions for this?
Is there any more information that I can provide to eventually get this resolved?
nu Maps stinks on Rezound
I unwisely installed the new Maps from Google Play Store.
It forgot my Favorite places and cached location. Experienced
poor location finding and not-fun routing to locations.
After hating it for a week, I searched for Maps 6.14.4.apk
and installed it with Root Explorer. I am very glad to have
a good working version of Maps running again now.
dbighead77 said:
I've finally hit a breaking point with Maps 7.x. Has anyone else still been having problems with it, or better yet, not had problems with it?
This is a video showing some of the problems I've been seeing. Most noticeable is the jittering glitches. If I'm driving around, the screen is unreadable for directions or street names. At the end is a screenshot I took of a completely glitched out warning prompt to tell me "please enable wifi and mobile network to improve accuracy" though you'd never be able to guess that.
http://www.youtube.com/watch?v=yMAVZnMx3m8
I'm running Infection 2.9.1, and I've tried several kernels (ROM default, Hiro, and Funkybean) and switched up the governors and schedules, and nothing has seemed to work. I've tried disabling/enabling hardware overlays. I'm just at a loss, and hoping someone out there knows more than I do. I just finally had it because it's cool enough outside to run now without getting heat stroke, and Endomondo (my running app) freaks out and loses signal 5 steps into a run. Downgrading to Maps 6.x makes everything happy. Is sticking with the old Maps still the best solutions for this?
Is there any more information that I can provide to eventually get this resolved?
Click to expand...
Click to collapse
To be honest google has been messing up alot of things for the Rez lately and maps being one of them....no matter what kernel you are on or what rom you are on its not gonna fix this maps issue...personally i prefer waze as it is not only free on google play but just works alot better and are even more up to date than google maps....plus it has many cool features like it lets you know if theres a cop or accident up ahead...also to note theres a gps test app out there that gives you a much better lock on your gps so it wont loose its signal as much
I have the same flickering issue until I close the app and reopen it. Seems to work fine after that.