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.
Related
PLEASE NOTE: This patch addresses application force closes on newer google maps applications (5.5-5.7) running on gingerbread-based ROMs for the ERIS. This does not address reboots/restarts (see http://forum.xda-developers.com/showthread.php?t=1157099 for progress on this other problem)
After extensive testing on CondemnedCM7 V15, I believe that the Navigation force closes many of us experience on the newest maps version is fixable (at least on Condemned's ROM; GSB users report that problems still remain) by rolling back google maps framework files to a version used for Android 2.2 ROMS. I have been testing since last week and have not had a single navigation force close. My longest test was 1 hour 10 mins with multiple reroutes and no force close. One known issue, Map application (not navigation) will unexpectedly close (that is, will not offer a force close but will shut down) randomly while using the search box. I have not been able to consistently reproduce this
I am attaching two zip files flashable from AmonRa Recovery if you would like to try the fix. The first replaces the current maps framework with the froyo framework. The second rolls back the change to the latest gingerbread framework.
If you are using maps 5.2 which CS included in the system apps for v15 and are happy with the result, then you do not need to flash this file. If you would like to use the newest maps app (5.7), you may wish to try this.
In theory, this fix would work on an AOSP or Cyanogen gingerbread ROM, so if folks on other devices are having similar problems, they may want to try.
Good luck everyone!
NOTE: this is repeated from CondemnedSoul's CM7 thread. The attachments can be found there: http://forum.xda-developers.com/showpost.php?p=15978440&postcount=535
Thanks for everything your doing on this issue.
I upgraded to 5.7 and flashed the patch. Ran Nav for 30 minutes and all was fine. Not sure when I can test longer but if I do I'll let you know the results.
Only got to run Nav for another 30 minutes today but she worked flawlessly again.
Glad its working for someone other than me!
Sent from my ERIS using XDA App
I can't believe no one else is trying it and letting you know their results.
I guess were the only ones who care, our at least, the only ones who get lost
Sent from my ERIS using XDA App
klobkelosh said:
I guess were the only ones who care, our at least, the only ones who get lost
Sent from my ERIS using XDA App
Click to expand...
Click to collapse
Or the only ones that use that ROM lol
Lol!
Sent from my ERIS using XDA App
Maps 5.8 is out. I'll be testing to see if 1) the navigation patch is still needed, and 2) if it still works. Stay tuned...
Sent from my ERIS using XDA App
klobkelosh said:
Maps 5.8 is out. I'll be testing to see if 1) the navigation patch is still needed, and 2) if it still works. Stay tuned...
Sent from my ERIS using XDA App
Click to expand...
Click to collapse
Have to go get it myself.
klob, will upgrading to 5.8 overwrite the fix files, or should I have run the unfix before upgrading?
Either way all I did was upgrade and so far Nav has been running for 40 minutes. Not driving anywhere, just have Nav running while I'm in the house.
Upgrading maps app will not affect the fix, so if you want to find out if it works with stock gapps, you'll need to flash the unfix. Also, bftb0 on the gsb thread has demonstrated that desktop navigation is not a good test for force closes. I'd get it on the road to be sure.
My commute starts in about 15 minutes. I'll report back soon...
Sent from my ERIS using XDA App
Update: it seems google had fixed whatever was misbehaving in maps 5.7. No force closes on my commute.
Sent from my ERIS using XDA App
I got to use Google Nav today and it wasn't the best. After 5 minutes it went shut off, just shut off and phone went to sleep. Opened Nav back up and after 14 minutes the map locked, never updated/moved, tough screen commands still came up along with menu but nothing worked. Rebooted and applied the fix that klobkelosh posted earlier and it didn't change anything, screen keeps freezing. This is all after full wipe and flashing latest CS v16 vanilla with 5.8 Maps.
Sir_Eagle said:
I got to use Google Nav today and it wasn't the best. After 5 minutes it went shut off, just shut off and phone went to sleep. Opened Nav back up and after 14 minutes the map locked, never updated/moved, tough screen commands still came up along with menu but nothing worked. Rebooted and applied the fix that klobkelosh posted earlier and it didn't change anything, screen keeps freezing. This is all after full wipe and flashing latest CS v16 vanilla with 5.8 Maps.
Click to expand...
Click to collapse
Odd. I just full wipe installed ccm16sth with 5.8 maps and navigation worked fine. One thing I did was disable text to speech, maybe that's the culprit? You can disable by renaming system/lib/libtts.so.
Sent from my ERIS using XDA App
klobkelosh said:
You can disable by renaming system/lib/libtts.so.
Click to expand...
Click to collapse
I don't have that file, got libttspico.so and libttssynthproxy.so.
Sorry, its the libttspico.so file
Sent from my ERIS using XDA App
GPS files the culprit?
Not sure if this will help but today running GSB 3.8 ODEX with Maps 5.8 (no framework mods.) my phone completely restarted in the middle of a walk. The thing is that I was not using Maps nor Nav. I WAS using TrackerBooster, an app that uses GPS to measure my walking distances. So maybe this is more related to GPS files than it is to Maps or Nav. As you can tell I am not a developer, so this may be all one and the same. Just thought posting it might lend a clue. Thanks for all you guys are doing to figure this out!
aceof89 said:
Not sure if this will help but today running GSB 3.8 ODEX with Maps 5.8 (no framework mods.) my phone completely restarted in the middle of a walk. The thing is that I was not using Maps nor Nav. I WAS using TrackerBooster, an app that uses GPS to measure my walking distances. So maybe this is more related to GPS files than it is to Maps or Nav. As you can tell I am not a developer, so this may be all one and the same. Just thought posting it might lend a clue. Thanks for all you guys are doing to figure this out!
Click to expand...
Click to collapse
I tried Telenav with the same force close issue too
Sir_Eagle said:
Only got to run Nav for another 30 minutes today but she worked flawlessly again.
Click to expand...
Click to collapse
Something I noticed... making me wonder if it's memory allocation issue... after a reboot, going right into Nav, it still force closes but not until 30+ minutes,
If I haven't rebooted in a while and have been running other apps like, gmail, exchange, facebook, and the going driving with NAV the reboot happens right away
OK folks, this one is a bit odd. I loaded up P3Droid's rooted 2.3.3 and it's been running great so far, save for one buggy thing.
I opened my camera and the photo portion of the screen (not the whole screen) started to flash in an out, in sync with the camera focus klunk (which seems to be more pronounces in gingerbread, btw). It took me a while, but I figured out that it is somehow linked to the auto-location tagging. The "searching for location" message was blinking as well in the upper left-hand corner. If I turn off the auto tagging feature in the camera app, it works just fine.
So, I played around a bit and found that if I leave VZW location and gps enabled, but disable google location services, I can leave auto location tagging on and have no problem.
Also, auto focus or continuous focus doesn't seem to matter.
Thoughts?
Possibly you froze/deleted a system app that its associated with?
That's all I got of the top of my head...
Sent from my DROID X2 using XDA Premium App
juhde said:
Possibly you froze/deleted a system app that its associated with?
That's all I got of the top of my head...
Sent from my DROID X2 using XDA Premium App
Click to expand...
Click to collapse
Good thought, I forgot to mention, I have not frozen anything. Fully bloated and stock (other than root)
My brother has had the exact same issue on 2.2.2 bone stock and I had to turn off the location tagging to get it to stop. I'd love to hear of a fix for this as well...
Did anyone update Google Map 6.1.0 and experienced Navigation turning-off GPS when it turn-on and asking to enable GPS (it's already enable) and when you enable GPS, go back to click on your address/destination ... Navigation turn-off GPS again?
I have to downgrade Google Map back to 6.0.3 and the problem is gone.
Running BulletProof with Faux' 0.0.8 beta 7 - themed
antiquezip said:
Did anyone update Google Map 6.1.0 and experienced Navigation turning-off GPS when it turn-on and asking to enable GPS (it's already enable) and when you enable GPS, go back to click on your address/destination ... Navigation turn-off GPS again?
I have to downgrade Google Map back to 6.0.3 and the problem is gone.
Running BulletProof with Faux' 0.0.8 beta 7 - themed
Click to expand...
Click to collapse
no man works fine here, just updated...
Thanks my man. I think it may conflict with my tasker app.
There's still the issue of compass being 180 degress off, I think for everyone...my dad has a stock nonrooted locked amaze and he anything after google maps 6.0, the compass is 180 degress off...I've contacted google and reported the problem. reverting back to pre 6.0 map fixes the problem.
seansk said:
There's still the issue of compass being 180 degress off, I think for everyone...my dad has a stock nonrooted unlocked amaze and he anything after google maps 6.0, the compass is 180 degress off...I've contacted google and reported the problem. reverting back to pre 6.0 map fixes the problem.
Click to expand...
Click to collapse
I have the same issue on my stock amaze.
I'm completely stock with Maps 6.1.0, Compass 2.1.1, and mine points correctly north. It's done so both in Michigan and Arizona (don't see why that would make a difference, but I thought I'd add that note).
gregb882 said:
I'm completely stock with Maps 6.1.0, Compass 2.1.1, and mine points correctly north. It's done so both in Michigan and Arizona (don't see why that would make a difference, but I thought I'd add that note).
Click to expand...
Click to collapse
a 3rd party compass works correctly, but the compass in google maps itself points 180 degrees off... This is getting on my nerves, It confuses the navigation and starts giving wrong directions when you're stopped. Anyone find a solution yet? I have reported this to google twice and the past two updates haven't addressed this issue, and it seems to affect some other phones as well.
seansk said:
a 3rd party compass works correctly, but the compass in google maps itself points 180 degrees off... This is getting on my nerves, It confuses the navigation and starts giving wrong directions when you're stopped. Anyone find a solution yet? I have reported this to google twice and the past two updates haven't addressed this issue, and it seems to affect some other phones as well.
Click to expand...
Click to collapse
Crap! You're right. I just checked and my Maps is off 180 degrees, too. Interestingly, as I was walking back into my office from trying it out, I received an update to Maps 6.2. It didn't help, though; still off 180 degrees.
problem has been fixed with google maps 6.3, came out today!
6.3 has me off by 90 degrees which is better than 180 I guess. It's also really shaky/glitchy in certain places. Oh well... They will get it fixed I'm sure.
Sent from my Energized HTC Amaze 4G using xda-premium
Hey all, wondering if anyone can shed some insight for me on this. HTC Rezound running CM 10.1.1 downloaded the .apk file to install the latest and "greatest" google maps v7.0 and I was having some issues the first day and uninstalled/reinstalled a few times. Just took this video (sorry for awkward quality never videoed myself on another phone before =P) of me just moving the screen around and how it's tearing etc. I also went to the settings menu and it was tearing as well. This also happens on the navigation portion as well, just in the time being (at work) just threw this together real quick.
Any insight would be great! Maybe others are having this annoying problem too =/
Thanks
Video Link
UPDATE (7/11 - 2:36pm): Enabled "Force GPU rendering" in developer options and still have disable HW overlays, haven't had as much of a problem as I did in the video above. Will keep testing it though. I feel that the gpu rendering option did help a tremendous amount as well. I also set my CPU governer to "interactive" instead of "ondemand" and raised the max to 1620MHz up from 1512MHz. Will update if I don't experience anymore issues or do =P
Update (7/11 - 3:42): still having the issue app can be restarted and sometimes work right but will soon stop working properly again...
This just makes me want to NOT update right now... on Infection 2.8.1 (CM 10.1 based), think I will wait and keep using the older version until the bugs are fixed, or switch to Waze again like the last time the Rezound has Maps issues.
Omg. I hate the new version. I'm can't come to grips with loosomg built in latitude either. Any heros out there care to post the last non 7 version here?
Sent from my ADR6425LVW using xda premium
Just Google "Google Maps 6.14.4 apk" and you will find tons of places to download it, it is all over the web on almost every APK repository.
Google is working on it, http://www.xda-developers.com/andro...rs/ShsH+(xda-developers)&utm_content=FaceBook
gleggie said:
Google is working on it, http://www.xda-developers.com/andro...rs/ShsH+(xda-developers)&utm_content=FaceBook
Click to expand...
Click to collapse
cool, thanks.
When I'm Navigating, the "Turn right in 5 miles" panel keeps flickering every time the map center updates, and each time the panel flickers off, the map panel expands to compensate, then shrinks back when the panel reappears. Sometimes when this happens, the map panel has artifacting, and it gets pretty hard to navigate certain roads I've never been on before.
The flickering rate appears to be about 2-3 times a second.
acejavelin said:
This just makes me want to NOT update right now... on Infection 2.8.1 (CM 10.1 based), think I will wait and keep using the older version until the bugs are fixed, or switch to Waze again like the last time the Rezound has Maps issues.
Click to expand...
Click to collapse
Waze works great still.. just saying.
Same problem on the HTC Desire HD with CM10.1, Jellytime or CodefireX rom.
I did the whole manual update to Lollipop, unfortunately, my phone keeps searching for GPS when I use apps that need it.
The problem is I like to use a boating app, and I go far enough offshore that I do not get data. Btw, I get this issue with any app that needs GPS, including Pokemon Go!
After searching online, it appears to be a bug in Lollipop itself.
Either downgrade, of go to Marshmallow if I can find a decent daily driver.
Anyone else have similar issue?
leroadrunner said:
I did the whole manual update to Lollipop, unfortunately, my phone keeps searching for GPS when I use apps that need it.
The problem is I like to use a boating app, and I go far enough offshore that I do not get data. Btw, I get this issue with any app that needs GPS, including Pokemon Go!
After searching online, it appears to be a bug in Lollipop itself.
Either downgrade, of go to Marshmallow if I can find a decent daily driver.
Anyone else have similar issue?
Click to expand...
Click to collapse
My Mate2 did the same thing...mostly after google updated a bunch of stuff. Just started doing it about a month or so ago.
Haven't touched it (all stock) in about a week. Got my new Mate8 about 4 days ago
"Searching for GPS" bug, might need to downgrade to KitKat
Try this:
http://forum.xda-developers.com/showthread.php?p=68572626
See post 35!
More details of my experience in that thread. Wife just pre-ordered an iPhone 7, probably out of pity, for me. One day I showed her my Google Maps and set it to drive home. No sound, no directions, but it quickly discerned origin and route home, when we got home it said "you have arrived," but the map, even though the pointer updated position throughout the drive, still showed the route line from the origin!
Sent from my iPad using Tapatalk
I've never had this issue on any ROM
Found a workaround
I was experiencing exactly the same issue! Not only that but it seems like this issue has popped up on reddit and latest amazon reviews too. Seems to have started occurring after July of this year for many people. I haven't determined the root cause, but it seems like it's affecting too many people to be a hardware issue. Some things I tried that DIDN'T work:
* Flashed latest Cyanogen snapshot, although I like it a lot more than stock
* Tweaked the /system/etc/gps.conf file for my region
Finally I found that my phone time significantly drifted off atomic time, noticed it could be a whole second off. After reading online about GPS technology, it seems having an accurate client atomic time should improve GPS performance. I used an app called ClockSync (with root is easier) to make sure my time was accurate and turned off syncing time with cell tower. It worked!! Using a GPS testing app (GPS Status & Toolbox) I can lock on to my position reliably in < 10 seconds. This is still running on Cyanogen.
I'm in love with this phone, so happy I don't have to buy a new one.
fenwaysnow said:
I was experiencing exactly the same issue! Not only that but it seems like this issue has popped up on reddit and latest amazon reviews too. Seems to have started occurring after July of this year for many people. I haven't determined the root cause, but it seems like it's affecting too many people to be a hardware issue. Some things I tried that DIDN'T work:
* Flashed latest Cyanogen snapshot, although I like it a lot more than stock
* Tweaked the /system/etc/gps.conf file for my region
Finally I found that my phone time significantly drifted off atomic time, noticed it could be a whole second off. After reading online about GPS technology, it seems having an accurate client atomic time should improve GPS performance. I used an app called ClockSync (with root is easier) to make sure my time was accurate and turned off syncing time with cell tower. It worked!! Using a GPS testing app (GPS Status & Toolbox) I can lock on to my position reliably in < 10 seconds. This is still running on Cyanogen.
I'm in love with this phone, so happy I don't have to buy a new one.
Click to expand...
Click to collapse
I tried to install CM13. I failed miserably. Then I started by playing the Pokémon Go game and observing the erratic character movement. Then played with the GPS settings. Turning off High Accuracy and leaving on Device Only still is working, except inside structures that block GPS signal. Tried High Accuracy while visiting San Francisco this last weekend and started having issues there, so back to Device Only for me.
Thank you for sharing what has worked for you!!!!
Sent from my MT2L03 using Tapatalk
I found the latest Cyanogen snapshot I tried (cm-13.0-20160823-SNAPSHOT-ZNH5YAO0M5-mt2) too unstable. I started to experience random reboots every day, even while using Google maps turn-by-turn navigation. Restored back to official lollipop build (MT2-L03C00B322) from my backup (that was factory restored before backing up). Now it's suddenly working without any workarounds! I have no idea why it's working now. If you are considering dumping your phone for a new one, you could try a factory reset first to make sure it's not a hardware issue. :/
---------- Post added at 05:26 AM ---------- Previous post was at 05:19 AM ----------
jzchen said:
I tried to install CM13. I failed miserably.
Click to expand...
Click to collapse
It was definitely not straightforward, I ran into several issues. First, TWRP recovery was complaining about invalid file system format so I switched to Cyanogen recovery to flash system. Second, I was getting constant Google services has crashed messages. Found out I needed to install it right after, before rebooting first. Third, I was stuck in boot-loop during Cyanogen startup. A hard reset finally fixed it.
fenwaysnow said:
I found the latest Cyanogen snapshot I tried (cm-13.0-20160823-SNAPSHOT-ZNH5YAO0M5-mt2) too unstable. I started to experience random reboots every day, even while using Google maps turn-by-turn navigation. Restored back to official lollipop build (MT2-L03C00B322) from my backup (that was factory restored before backing up). Now it's suddenly working without any workarounds! I have no idea why it's working now. If you are considering dumping your phone for a new one, you could try a factory reset first to make sure it's not a hardware issue. :/
---------- Post added at 05:26 AM ---------- Previous post was at 05:19 AM ----------
It was definitely not straightforward, I ran into several issues. First, TWRP recovery was complaining about invalid file system format so I switched to Cyanogen recovery to flash system. Second, I was getting constant Google services has crashed messages. Found out I needed to install it right after, before rebooting first. Third, I was stuck in boot-loop during Cyanogen startup. A hard reset finally fixed it.
Click to expand...
Click to collapse
That's a lot to deal with!!!
As of yesterday I am back to High Accuracy, and just as you note everything seems fine, particularly with regards to GPS.
I guess if I want to have Android 7, I'll save up for a phone that comes with it, unless I learn how to manually do it myself. (I was once a CECS major, about 16 years ago...)
Thank you again for sharing your experience! I hope we can all go back to enjoying our exceptionally large screens....
Sent from my MT2L03 using Tapatalk