Google Maps East-West Reversed
I'm running rooted "official" Gingerbread and as with the prior Gingerbread leaks when using Google Maps East and West seem to reverse themselves but not North and South. This does not happen with the compass and when calibrated it shows right direction. The same goes for third party compass and GPS apps. Only Google Maps and Nav seem to be affected.
Is anybody else still encountering this problem? Has a solution been found?
I'd hate to be stuck on Froyo just because of this issue, but I do need this phone to work correctly in maps and as a GPS unit.
(if this has already been brought up with regards to the OTA GB release, please merge it with any existing threads. i searched briefly but did not notice any threads on this subject)"In the beginning the Universe was created. This has made a lot of people very angry and has been widely regarded as a bad move." ~ D.N.A.
In Google Maps, east and west show up reversed when in portrait mode held either vertically or horizontally. North and south are reversed when the phone is in landscape mode and held horizontally. When held vertically in landscape all directions are displayed correctly.
The same issues show up in Google Sky Maps. Landscape is fine when the phone is held perpendicular to the ground, but it seems to get confused the second I start tilting it parallel to the ground.
None of this occurs in any third party compass app."In the beginning the Universe was created. This has made a lot of people very angry and has been widely regarded as a bad move." ~ D.N.A.
- 05-30-2011, 09:49 AM #3
I am getting the same thing on Google Sky Maps with Official GB. Runs fine in landscape. But if you point at the horizon find East and then rotate the phone to portrait East changes to West. Pointing North or South and rotating does not do this.
How do get this "feature" in google maps?
I just get north at the top of the screen with any orientation.Dyslectics of the World UNTIE!
- 05-30-2011, 11:46 AM #4
- "In the beginning the Universe was created. This has made a lot of people very angry and has been widely regarded as a bad move." ~ D.N.A.
- 05-30-2011, 02:27 PM #6
Hopefully once the release becomes truly official (still in pre-release "SOAP" right? ) there will be an update to Google Sky, Maps, and Nav to fix this. Would be crazy not to. Seems like a change was made in GB to the accelerometer that is messing with those programs. I just don't understand why the third party apps aren't affected....
pre-release "SOAK", yes, but this was an issue that was noticed when the first leaked gingerbread got into the hands of the public.
- 05-30-2011, 07:35 PM #8
Yes, but no reason to release the update to maps, sky, etc until GB is officially actually released, right? What I'm guessing is that the solution lies in the Google mapping programs, not in GB itself...(edit:....since third party compass programs work fine, GB is doing SOMETHING correctly)
- 05-30-2011, 08:40 PM #9
- 05-30-2011, 11:26 PM #10
- 06-02-2011, 07:50 PM #12
Is there any word out on a fix for this yet? What I can't believe is that this kind of bug ever got out the door. It's not some obscure subtle issue, it's a Droid X with vertigo! I know from the message chain it showed up in SOAK, but how did it ever get that far? Google OS and an incompatible Google stock app -- that's sad!
If anyone has any word on an update I'd appreciate knowing.
Droid X (Android 2.3.3 Stock)
- 06-03-2011, 12:31 AM #14
- 06-07-2011, 12:43 PM #15
I hope this issue has not fallen off the radar. I'm still having problems with this and I can't seem to find any acknowledgement from Verizon, Google, or Motorola that the problem exists or any idea of what they intend to do or when they intend to fix it.
Anyone know something I don't about this?
Last edited by booberthecat; 06-07-2011 at 12:46 PM. Reason: typoBooberthecat
Droid X (Android 2.3.3 Stock)
- 06-08-2011, 03:29 PM #16
- 06-08-2011, 04:09 PM #17
Thanks for staying on top of this, booberthecat. Here's the latest response from Google employee "MrEvan"
So the engineers are on it and appear to have zeroed in on the problem. That's good. A fix should hopefully be coming sooner rather than later, but I don't have any concrete timing for you yet. I'm sure this is a pain, and if I were you, I'd want it resolved as soon as possible. I'll keep monitoring progress internally and circle back with you when I know more.
- 06-08-2011, 04:18 PM #18
- 06-16-2011, 01:18 PM #19
- 06-16-2011, 02:05 PM #20