Has anyone else had any problem with Google Maps forceclosing since the last update? I've tried clearinf cache and Dalvik cache, uninstalling and reinstalling but to no avail. I'm wondering what else to try. Thanks!
I was having FC issues to. I restored a nandroid I made before I updated to get the old version back. It seems everyone posting this is on Velocity 1.1. It would be nice to hear from someone not running Velocity 1.1 to see if they are having this issue?
I am running Velocity 1.1 with the 2.2 hack. I copied the maps.apk out of the OTA.Zip for Velocity 1.1 and my Maps is working ok now, so it's definitely a problem with the updated Maps version.
Also I just checked the comments in the Market and a bunch of users are reporting the same issue with various phones. So there you go.
No sigh! I thought I had a solution for this but no sooner than I posted it the FC errors started back
And now maps laughs at you. hahaha I still havent gotten any FC's. Im have 5.2.1 Maybe google maps thinks you are going behind its back with another maps app!
Odd, mine wasnt showing an update. I had just recently reflashed velocity. After downloading it 3 times it finally updated and guess what, force close, force close, force close!
I flashed back to stock 2.2.2 and no more FC's which brings me back to maybe something in Velocity 1.1??
Does anybody have a backup copy of 5.5? 5.6 is just a total piece of crap ... (1) keyboard freeze [hard keys, soft keys] (2) runs automatically on startup (3) locks the droid x (4) causes reboot
It looks like Turning off the "Use wireless networks" setting in Locations & Security works so link to older version removed.
Just tried to download the update of maps (5.7.0) that came out a few ago. It comes up with update of "google maps" unsuccessful. The error is Installation error - Package file is invalid. Anyone else having this problem?
tried 5.7.0, still getting FC error Exception class name Java.lang.NoSuchMethodError Source class com.google.android.location.os.real.SdkSpecific9 I have a sneaky suspicion this might have something to do with Velocity which is 2.2.1 reporting itself as 2.2.2 to get around the system update prompts but just a guess, I'm the first to admit I don't know for sure.
Also as a side note - I downloaded this update using wi-fi, after it downloaded and tried to install wi-fi was off and 3g back on. I checked and wi-fi was supposed to be on so I had to turn it off and back on for wi-fi to start again. I should have a "good" install of velocity 1.1 as I reset to factory, then wiped cache, then wiped dalvik before installing velocity 1.1. It has never done this before, and now only does it if a download/install from market fails with the Package file is invalid error. Any ideas? Is there a way for them to "see" or check that your phone is rooted during the install and have the program fail to install? Just wondering...
I had same problem but eventually it worked with enough tries. Still having the force close issue though.
I am running V1.1 with the most recent scripts, and have used Maps once, Navigation once and Places twice. No FC's at all. I will note, however, that the last time I had Velocity on my phone (v0.4) any application that used Maps - Navigation, Places, etc. - would either FC or lag to the point of causing the phone to reboot. I will try using Maps later on, and if it gives me trouble, I will let you all know.
