Google Navigation and other apps crashing/freezing (CDMA, Sprint)
I clean installed (RAR file) the Blazn build w/ sound a couple of days ago. Now I having a lot more stability issues and Navigation freezes up every time I open it. I have searched through google, xda-developers, and on here, and I see people with the same problems with the new build but no solutions or acknowledgement that multiple users are having issues like this. Here is what I did.
I go into google maps to insure I have a GPS fix. It finds me within 2 meters or so. I then go into navigation. It doesn't give me the location error because I have a GPS lock. I then type in the address I want to go to. I have the bar at the bottoms saying "Getting GPS" or something like that. In the middle of the screen it has the "getting directions" or whatever it says, but the little spinning circle animation freezes up. If I click to try to get to the menu. Android tells me it is not responding and I can Force Close or Wait. I force close. Of course Android opens it back up. I then hear the first voice prompt of where to go on my directions. When I click on Navigation to get back into it. It shows me the next turn, but freezes up again. This will go on forever until I force maps and navigation to close manually for good by going into settings and force stopping the processes.
I thought maybe it was the Blazn build, so I renamed the boot directory to something else and clean installed (using the RAR file) the stock build. While it is more stable and I don't get as many random crashes of apps and processes, I still get the same problem with Navigation.
I also have tried to format and attempted to clean install both builds and still have the same problem.
Is there any Sprint customer able to get navigation to work and not crash? I am thinking this is a CDMA/Sprint problem only, and it has something to do with the app accessing the sound, or at least that is my hypothesis, because it was working in all prior builds up to this one.
I realize all of this is a work in progress, I just had not seen this problem talked about since the sound build was made, as this looks to be symptom of sound working.
Any suggestions or thoughts?
|