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
I'm running the latest 9/16 build of CM9 on my Note with AT&T and for the last 4 weeks or so have had NO problems. Starting yesterday I was getting "unfortunately, maps has stopped" messages. Got a couple of them, then all was good, today it started again. I reverted back to 9.1 stable but am still getting the same message. I found a thread in the Nexus 7 forum regarding the same issue but no resolution. I have the latest maps version 6.12.0 and have my GNex and Xoom at my desk with me (GNex running on T-Mobile and the Xoom on Verizon) with no issue whatsoever. I did clear cache and data in the map app and rebooted as was one possible solution in the Nexus 7 thread but that didn't seem like it was a permanent fix based on the other comments.
*AT&T is currently converting my area to LTE (outside of Philadelphia) as we speak though I can't imagine that impacting the maps app but I figured I would mention it just in case.
Any help or suggestions would be appreciated.
This may be wildly coincidental, but I experienced the same messages after trying to install Google Now on CM9. I then re-wiped and re-flashed without issue.
I've been running the latest version since it was posted and I have not added anything new...strange I have not had a single error message since 3 this afternoon??
Sent from my SAMSUNG-SGH-I717 using xda premium
Have you checked permissions for maps ??
Or fixed permissions for all apps ??
Often times the permissions are wrong ...and the app will produce errors or force close ...
Just thinking out loud ...g
Also ....
Maps is highly dependent on the services framework ....
You could also delete your account info and set it up again ......using the data wipe option ...then load maps again ...g
Again ...just a thought ...g
I have never touched the permissions don't know even where to go to check them?? I will do a little research when I get into work and see if I can figure it out thank you for your advice.
Sent from my SAMSUNG-SGH-I717 using xda premium
Hi - My post count is not high enough to ask this question in the CM10.1 thread.
I've installed cm-10.1-20130304-EXPERIMENTAL-fireball-M2.zip and gapps-jb-20130301-signed.zip successfully and most everything seems to be working well except for Google Navigation.
After selecting a destination, it correctly shows my location, determines the route, draws the map and shows route. However, as soon as I begin to drive it freezes and the app stops responding requiring force close.
I don't think it's the GPS since GPS Status, Zillow, c:Geo and even Google Maps all work OK tracking me while I drive.
All I've tried so far is to uninstall/reinstall Google Maps and cold boot.
Any suggestions?
Thanks
I just noticed you said your running the experimental M build. I'm running the nightly from that sane date and nav works just fine.
Sent from my Incredible 4G LTE using Tapatalk 2
MJL99 said:
I just noticed you said your running the experimental M build. I'm running the nightly from that sane date and nav works just fine.
Sent from my Incredible 4G LTE using Tapatalk 2
Click to expand...
Click to collapse
i'm running the m snapshot and GPS works fine.also there is a new gapps package available, which you have I see
I can definitely attest to experiencing this problem on multiple occasions. I haven't put a whole lot of thought or effort into troubleshooting it yet, as I was more inclined to restart my phone and restart navigation so that I don't miss my turn as opposed to sitting there and trying to test various scenarios to see what causes the issue. Without any serious level of troubleshooting, i think the only helpful information that I can bring to the table is that I have only noticed it while the phone is charging in the car. It doesn't happen every time (maybe 20% of the time), but when it does happen, the screen freezes immediately upon the screen flying into the proper position on the map.
smtrekkers said:
Hi - My post count is not high enough to ask this question in the CM10.1 thread.
I've installed cm-10.1-20130304-EXPERIMENTAL-fireball-M2.zip and gapps-jb-20130301-signed.zip successfully and most everything seems to be working well except for Google Navigation.
After selecting a destination, it correctly shows my location, determines the route, draws the map and shows route. However, as soon as I begin to drive it freezes and the app stops responding requiring force close.
I don't think it's the GPS since GPS Status, Zillow, c:Geo and even Google Maps all work OK tracking me while I drive.
All I've tried so far is to uninstall/reinstall Google Maps and cold boot.
Any suggestions?
Thanks
Click to expand...
Click to collapse
read the OP IN development cm 10,1 workarounds, gps fix is there
Shot in the dark. Did you try force closing the maps app and clearing the data and cache of the app then restarting it. I've had this fix problems for apps in the past. Worth a shot.
Sent from my Nexus 7 using xda app-developers app
Thanks for all the suggestions. I'll try a nightly build to see if that fixes it. I'll also try running it while not charging - so far it's also been on the car charger. As I mentioned, the GPS works fine, so the GPS workaround didn't seem to be needed. I did try the force close and clear data/cache.
I did find a working workaround by googling the issue. Apparently it's not uncommon across various phones and Adnroid versions. I couldn't find a fix though.
The work around that works is to set Nav to use 'North Up'. You do that by hitting the little compass symbol on the top left while in nav. It was tricky to hit it quick enough before freezing, but I got it. Thankfully that setting sticks for future nav requests. I get no crashes/freezes when I use it North up. As soon as I switch it back, it freezes. Odd. At least I can use it, but would still be good to find the cause and fix.
somerandomname1 said:
Shot in the dark. Did you try force closing the maps app and clearing the data and cache of the app then restarting it. I've had this fix problems for apps in the past. Worth a shot.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yeah I'd recommend just using a different nightly. I could not replicate this problem with and without a charger on Thursday.
Sent from my Incredible 4G LTE using Tapatalk 2
Same problem. I have wiped, reflashed a dozen different nightlies, and still have the same problem. It works fine in every other rom I try, either Viper or stock. Every cm10.1 causes this problem. I am using the workaround posted above(north up), but it is annoying.
Waze works well, also.
My wife has the same phone, same setup, and hers works fine.
I have yet to experience this issue with CM10.1 and I regularly flash the "sudo" nightly builds posted by mdmower on goo.im.
That said, for those experiencing this issue:
- Did you a full wipe/facotory reset before flashing to the new rom?
- Did you make sure that all your location services were turned on before flashing to the new rom?
-- If you didn't enable all location services before flashing the new rom, I strongly encourage you to flash to a sense rom and follow the instructions provided by mdmower on the CM10.1 thread in the development section.
Good luck!
retrostudd said:
I have yet to experience this issue with CM10.1 and I regularly flash the "sudo" nightly builds posted by mdmower on goo.im.
That said, for those experiencing this issue:
- Did you a full wipe/facotory reset before flashing to the new rom?
- Did you make sure that all your location services were turned on before flashing to the new rom?
-- If you didn't enable all location services before flashing the new rom, I strongly encourage you to flash to a sense rom and follow the instructions provided by mdmower on the CM10.1 thread in the development section.
Good luck!
Click to expand...
Click to collapse
Yes, full wipe and factory reset.
Yes, all 3 location services are on.
GPS locks fine. It works with north up in Maps, and with Waze, and with any other rom. Just not cm10.1
smtrekkers said:
Hi - My post count is not high enough to ask this question in the CM10.1 thread.
I've installed cm-10.1-20130304-EXPERIMENTAL-fireball-M2.zip and gapps-jb-20130301-signed.zip successfully and most everything seems to be working well except for Google Navigation.
After selecting a destination, it correctly shows my location, determines the route, draws the map and shows route. However, as soon as I begin to drive it freezes and the app stops responding requiring force close.
I don't think it's the GPS since GPS Status, Zillow, c:Geo and even Google Maps all work OK tracking me while I drive.
All I've tried so far is to uninstall/reinstall Google Maps and cold boot.
Any suggestions?
Thanks
Click to expand...
Click to collapse
Why are you using such an old nightly? Step up from M2 to the RC. The only issue I've had with the RC is a minor audio problem that has a workaround in place.
Sum Dumb Guy said:
Why are you using such an old nightly? Step up from M2 to the RC. The only issue I've had with the RC is a minor audio problem that has a workaround in place.
Click to expand...
Click to collapse
It's with every nightly, including M2 and RC1.
scottyb96 said:
It's with every nightly, including M2 and RC1.
Click to expand...
Click to collapse
I've been using mdmower's unoficial CM10 releases for a couple weeks and haven't had any google issues. Where have you downloaded your zips?
http://goo.im/devs/mdmower/fireball-cyanogenmod-oc
Sum Dumb Guy said:
Why are you using such an old nightly? Step up from M2 to the RC. The only issue I've had with the RC is a minor audio problem that has a workaround in place.
Click to expand...
Click to collapse
That post was from March when that nightly was current. The later versions didn't fix it either. The issue still exists for me, and I've just been living with the North Up workaround. I suspect it's not something CM10.1 specifically, but that was a contributing factor as it worked before the ROM switch. I think there have even been Google Maps app updates since the issue started that didn't fix it.
With the new kernel version of cm10.1 becoming available, I did a full wipe and fresh install with the 7/1 nightly, and I still have the maps issue. Living with the North Up fix for now.
scottyb96 said:
With the new kernel version of cm10.1 becoming available, I did a full wipe and fresh install with the 7/1 nightly, and I still have the maps issue. Living with the North Up fix for now.
Click to expand...
Click to collapse
cm10.2 from mdmower fixed this problem for me. Navigation works flawlessly now. Reverting back to 10.1 reproduces the issue.
Hey all,
I'm running the newest version of Slick Rom JB (2 Final).
I was running 1.1, and I didn't have any of these problems, but since updating to 2 and updating my radio as recommended I've run into a number of issues. The ones I think can of off the top of my head, and run into most commonly are:
ANY time I launch GMail, read an email, and go "back" using the icon in the top bar rather than the back button, GMail will stop. This only happens when going from an email to my inbox.
My GPS will not get a lock besides a 5 mile radius
Trillian will not connect AT ALL. Just constantly says connecting.
Based on what I've read in the thread, this really isn't the typically experience, so I'm just trying to figure out what could be wrong and how I can fix it.
For the record I have tried the follow:
I restored to an earlier backup when I was running GINSIX v1.6.1 and I do not have ANY of these issues. GPS gets a quick, solid lock. Trillian works fine. GMail does not crash. The only issue I noticed when I restored the backup is that my wifi and tether were both broken. I'm willing to chock that one up to the modem update?
I've tried a clean install by wiping data, wiping cache, installing the rom, wiping the cache, installing Google Apps, reboot. I immediately have the same issues.
I've read that other people have tried to "start from scratch", but I'm not entirely clear of where "scratch" is and how to get there.
So any information anyone would be able to provide would be greatly appreciated.
Thanks in advance.
Ramaniscence said:
Hey all,
I'm running the newest version of Slick Rom JB (2 Final).
I was running 1.1, and I didn't have any of these problems, but since updating to 2 and updating my radio as recommended I've run into a number of issues. The ones I think can of off the top of my head, and run into most commonly are:
ANY time I launch GMail, read an email, and go "back" using the icon in the top bar rather than the back button, GMail will stop. This only happens when going from an email to my inbox.
My GPS will not get a lock besides a 5 mile radius
Trillian will not connect AT ALL. Just constantly says connecting.
Based on what I've read in the thread, this really isn't the typically experience, so I'm just trying to figure out what could be wrong and how I can fix it.
For the record I have tried the follow:
I restored to an earlier backup when I was running GINSIX v1.6.1 and I do not have ANY of these issues. GPS gets a quick, solid lock. Trillian works fine. GMail does not crash. The only issue I noticed when I restored the backup is that my wifi and tether were both broken. I'm willing to chock that one up to the modem update?
I've tried a clean install by wiping data, wiping cache, installing the rom, wiping the cache, installing Google Apps, reboot. I immediately have the same issues.
I've read that other people have tried to "start from scratch", but I'm not entirely clear of where "scratch" is and how to get there.
So any information anyone would be able to provide would be greatly appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Typically "scratch" is going into the recovery, formatting /system /data and /cache and then reflashing. You might also want to compare the checksum to make sure nothing happened to the file during the download. All fairly typical flashing stuff, which it sounds like you probably did already, but worth mentioning. Also, for what this is worth, I'm running SnowJB, and after updating my phone to the JB radio from the stock ICS radio, I had a bunch of weird issues come up that forced me to revert radio images. Something to think about if all else fails.
I had some similar problems and stumbled upon this...
http://forum.xda-developers.com/showthread.php?p=40115473
It worked for me as well as a few others.
Sent from my LG-E970 using xda premium
For now I've rolled back to the ICS radio and my older GINSIX backup, and things are running great. I figure that I'll just stick with this for now, and I'll try the whole JB thing again sometime later when I have more time to fiddle with it.
Thanks for the help!
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