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
Just curious how many people are having issues with stock Google apps and the stock browser after the ota update. The Gmail and maps will get stuck on a white screen as does the stock browser and the play store will just lock up on whatever screen it was currently on. Google wallet will freeze during the unlocking your device notice. These are the only ones I have found so far but I had none of these issues before the ota update. A phone restart will fix it for a period of time but I'm currently having to restart my phone 2 times a day to get the apps to work properly again.
Sent from my EVO using Tapatalk 2
I also forgot to add that during the restart after the screen turns off you can will change the ring volume up and down and hear it change for 2-3 seconds before the phone actually does restart. I noticed this when I had my Bluetooth headset still connected and it was not telling me it was disconnected for at least 4-5 seconds after the screen turned off unlike before the update when it was no more than a second.
Sent from my EVO using Tapatalk 2
juanm269 said:
Just curious how many people are having issues with stock Google apps and the stock browser after the ota update. The Gmail and maps will get stuck on a white screen as does the stock browser and the play store will just lock up on whatever screen it was currently on. Google wallet will freeze during the unlocking your device notice. These are the only ones I have found so far but I had none of these issues before the ota update. A phone restart will fix it for a period of time but I'm currently having to restart my phone 2 times a day to get the apps to work properly again.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Mine does this as well, the only "fix" I have found for it is rebooting the phone. Then it works for a few days until it randomly decides to freeze again.
I was having the same problems where the browser will be a white screen and not work. I went twrp and wipe cache/dalvik cache and haven't had a problem since
Sent from my EVO using Tapatalk 2
Same problem here
Sent from my EVO using xda premium
I have been having the same problem also been having random reboots at times
I'm rooted and flashed the latest firmware, is there any way it can be undone
Sent from my EVO using xda premium
After the update! The stock browser doesn't highlight the the URL address when tapped like before...Instead we have to manually delete the URL to search something else or press the little X after tapping on the URL.
Wtf!? Yeah count me in too. I just did a restart and it didn't fix problem. Gwallet still in notification bar saying initializing.
Sent from my EVO LTE
Also been having the same problem since updating, most noticable with the browser just being a white screen. Tried wiping cache & dalvik cache again, doesn't seem to help. Stock ROM with S-OFF. Surprised I haven't seen more mentions of this problem, but perhaps it's not widespread?
Well as I've learned over my time at xda updates are always catch 22's. That's why I choose to wait and read users feedback on how the latest ota is functioning. However none if this is revelant to your issues just figured I'd post it for future reference. Also have you guys tried a full wipe of your current rom? After you make a backup of your data of course to see if that will help ??
#Root-Hack_Mod*Always\=LTE
Yeah...I was having the same problem after the ota, but after a couple of reboots things started to work right.
Im having this too, is getting very annoying. Sometimes i just want to use the phone quickly for something and have to re-start the phone... I feel like breaking it against the floor.
Sent from my EVO using xda app-developers app
I too am having the same issue. Play and browser all fail to respond. Wiped cache etc. Still repeats each time.
Sent from my EVO using xda app-developers app
I wound up here after searching for this error, which just started with me yesterday with the browser (stock). It just displays a white screen when I try to use it.
I've had the latest update (flashed with 1.22.651.3 odexed ROM from xHausx and firmware from Captain Throwback) about a week now and this just started happening yesterday.
Yesterday I somehow got it to work again by clearing the Internet cache and then I performed a search from the Google search bar and all was well. I was thinking at the time that it was stuck on a particular page and that this got around it. But that fix isn't working for me today, so I'm going to try to clear dalvik/cache from twrp as recommended here and see where that gets me.
It's good to know I'm not the only one though... I wonder if there's anything else more specific we all have in common since we seem to be a fairly small subset. Maybe we all flashed the Odexed update for example?
EDITED TO ADD: Appears to affect Gmail too. And possibly several other Google apps as mentioned here and in other threads. Since there was a Gmail update I did yesterday, I'm going to try to uninstall that as mentioned in this other thread I found http://forum.xda-developers.com/showthread.php?t=1810829
CheriePie said:
I wound up here after searching for this error, which just started with me yesterday with the browser (stock). It just displays a white screen when I try to use it.
I've had the latest update (flashed with 1.22.651.3 odexed ROM from xHausx and firmware from Captain Throwback) about a week now and this just started happening yesterday.
Yesterday I somehow got it to work again by clearing the Internet cache and then I performed a search from the Google search bar and all was well. I was thinking at the time that it was stuck on a particular page and that this got around it. But that fix isn't working for me today, so I'm going to try to clear dalvik/cache from twrp as recommended here and see where that gets me.
It's good to know I'm not the only one though... I wonder if there's anything else more specific we all have in common since we seem to be a fairly small subset. Maybe we all flashed the Odexed update for example?
Click to expand...
Click to collapse
Install chrome. Problem solved.
njfoses said:
Install chrome. Problem solved.
Click to expand...
Click to collapse
NOT helpful at all since it affects not only the stock browser but other Google apps as well.
Refer back to my original post which I updated with additional information.
I've found if I reboot and never use the stock browser I don't have the white screen problem. I set maxthon as the default and act like the stock browser doesn't exist.
Sent from my EVO using Tapatalk 2
I reverted back to the previous version of Gmail yesterday hoping that would fix the problem but it still happened. This morning when I clicked an email notification from my status bar, Gmail did the white screen thing and needed to be shut down manually. Just to verify that this and the browser incident were related, I tried to launch the stock browser and it too was white screen.
So those of you suggesting to install an alternate browser to get around this issue need to understand that this is a lot more widespread than the browser alone. For me, both my Gmail and Google Offers were white screens this morning upon trying to launch them so it definitely appears to affect all Google apps.
Yeah this happens to me as well. Its really bad now. Nothing fixes. It does it on all the roms with newer OTA for me. Only two roms will work for me without this problem. I have tried everything. Wiped everything, Reflashed, Checked my sd card, factory reset, you name it. It even does it on restored roms that didn't have the problem before. I don't know what to do....
A developer told me to try and manual flash boot.img through fastboot but I'm not even sure how to do that. Need to read up on it.
I have had the issue to wear when I am trying to open the browser app, it will actually freeze the entire phone until I hit the home button repeatedly in play store will not load anything until I fully restart the phone I've tried fixing for missions do a nandroid restore nothing seems to work
Sent from my EVO using xda app-developers app
I'm on rooted stock (latest OTA) and every few days all of my google apps will stop responding (Maps, Wallet, search, etc.). I can open them, but they never get to the main screen of the app (just a blank screen). Rebooting it solves the issue. I haven't noticed any correlation with other apps running. Does anyone have any idea what might be causing this? I've finally got my phone the way I like it and I'd hate to hard reset if I don't have to.
Thanks!
I just noticed my gmail did that this morning. It might be because of the recent app update. Either way, it's only happened to me once so far, so keeping my fingers crossed.
I've done a reset to fix this and it did.....for a while but now it's back. I have to reboot or Google apps won't open fully, they just hang.
I have the same issue with Gmail, navigation and sometimes the web browser. A reboot fixes the hang but who wants to do that all the time.
+1
I am having the same issues. Reboot fixes it.
+1 pretty sure it was the gmail update. I uninstalled and it seems to be working fine again.
Nextelian said:
+1 pretty sure it was the gmail update. I uninstalled and it seems to be working fine again.
Click to expand...
Click to collapse
Trying this. Fingers crossed! This has been happening to me almost once a day for the past couple weeks.
Sent from my ELTE using Tapatalk 2
Yep once a day for past 4 days now. Browser and gmail. Getting ridiculous having to do 'battery pulls' so much.
Sent from my EVO LTE
Same Gmail blank screen not responding issue for me too.
Sent from my EVO using xda app-developers app
Mine The Same But Im Not Rooted Hope They Fix It Soon
Try getting the logcat for the event. You can use "alogcat" from market. Search on how to use logcat ( it's color coded for obvious events). Magic bit ( "self" changing) events are more difficult. "Autostarts" from market will let you see your spinlocks, so if any unrelated app has the screen or some other resource then you've got the cause.
Uninstalling the gmail updates had no effect. Happened 3 times in the last 24 hours. Getting very frustrating.
Sent from my ELTE using Tapatalk 2
I have the same issue as well with gmail loading to a white screen. I've tried doing a force stop but that didn't help, which made no sence when a reboot fixes it.
Mine started doing this too, only started about a week ago. I always have to reboot too, very annoying.
"We're coming from a pure power source"
Its google wallet. Delete or disable and reboot. Clear data in google service framework as well.
Sent from my EVO using Tapatalk 2
Are you using a custom launcher? I was using Apex launcher and it worked awesome for the longest time. Recently my gapps started locking up as well so I uninstalled Apex and haven't had a lockup since. I did NOT reboot after uninstalling Apex, and the issue has cleared up.... Give it a shot if you're using a custom launcher.
I am running the stock with the OTA update (no custom ROM or root) and I'm seeing this as well. Good thing is, this has nothing to do with your custom ROMs. Bad thing is, this is a real issue that seem to be affecting everyone!
cloak.n.dagger said:
I am running the stock with the OTA update (no custom ROM or root) and I'm seeing this as well. Good thing is, this has nothing to do with your custom ROMs. Bad thing is, this is a real issue that seem to be affecting everyone!
Click to expand...
Click to collapse
Oh dang. I'm stock ROM, but I did root it. I haven't seen it since I've uninstalled Apex. Guess it's just a matter of time before I see it again...
huludical said:
Its google wallet. Delete or disable and reboot. Clear data in google service framework as well.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Just do as huludical has said here. So far this is the only fix that has been working. Something with the Wallet fix in the OTA starting screwing up the way many other Google apps communicate with their servers. By disabling/uninstalling Wallet and clearing the data/cache for Google Services Framework and then a quick reboot and the issue is no more.
Granted, this means, that once again we are unable to use Wallet but that's a small price to pay when the alternative is having Gmail, Maps, Chrome etc etc freezing up every day or so.
Is there an update to this situation? I am UN rooted and this is happening to me
So after updating to the newest version of Google Now, it now force closes. Any idea as to why? I was able to roll back to the previous version and it works fine now.
Edit: After reading some of the development forums this issue seems to be affecting the JB based ROMs (CM10/AOKP). If you're running one of these, it's likely the problem relates to the oes texture problem. Sadly that problem isn't likely to be fixed.
It's helpful to note if you're running any custom ROMs/scripts. There are many circumstances that could cause an app to FC, and more info could help us point you in the right direction.
Sent from my DROID X2 using xda app-developers app
I am running CM10 Alpha 2
Its most likely what ROMFlashah said. It probably has to do with the textures. Our ROM doesnt have these so when it tried to use them, it force closes. The same thing that happens with Gmail and others. Its sad to think we will no longer be able to use any update they put out for google now from now on.
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.