Maps Force closes During Navigation

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Begin navigating to a destination
2. Drive some, do a turn or two. 
3. Maps force closes. 

What is the expected output? What do you see instead?

Normally maps/Nav follows your movement without issue. 

Currently maps crashes and Navigation continues to operate in a somewhat flaky 
way in the background. 

What version of the product are you using? On what operating system?
Maps 6.12.0

CM 10-20121012-NIGHTLY-evita

Please provide any additional information below.

Original issue reported on code.google.com by RayFo...@gmail.com on 17 Oct 2012 at 4:24

[GoogleCodeExporter]

I've experienced the exact same issue across three ROMs as seen here - 
http://forum.xda-developers.com/showthread.php?t=1803376

Stock ICS (not sure if it was 1.75 or 1.82 at the time)
CleanROM (various iterations of it)

With both of these, Navigation will display the map fine for a few minutes, 
then a message that "Maps has crash" pops up and the Navigation icon disappears 
from the notification drawer and bar.  The Navigation bit is still running in 
the background and the directions are still spoken.  Eventually the Navigation 
icon in the notification bar/drawer - I can click on it to open Maps back up 
like nothing ever crashed.  

CyanogenMOD 10 nightlies (builds around 10/06 - 10/10)

The same behavior happens except that Maps crashes immediately upon showing the 
visual map - there is no duration where the map actually works.

Original comment by jspi...@gmail.com on 26 Oct 2012 at 10:11

[GoogleCodeExporter]

Some log entries for the curious:

10-26 07:25:15.242 D/dalvikvm(10536): GC_CONCURRENT freed 3002K, 21% free 
12162K/15331K, paused 3ms+5ms
10-26 07:25:15.332 W/dalvikvm(10536): -2047744016 byte allocation exceeds the 
67108864 byte maximum heap size
10-26 07:25:15.332 I/dalvikvm-heap(10536): Forcing collection of SoftReferences 
for 2247223280-byte allocation
10-26 07:25:15.382 D/dalvikvm(10536): GC_BEFORE_OOM freed 148K, 21% free 
12120K/15331K, paused 55ms
10-26 07:25:15.382 E/dalvikvm-heap(10536): Out of memory on a -2047744016-byte 
allocation.

Can someone please explain how -2GB is even trying to get allocated in the 
second line??  I've got more logs if it will help.

Original comment by jspi...@gmail.com on 27 Oct 2012 at 6:21

[GoogleCodeExporter]

My experience has been that the Issue is only present if you keep the DISPLAY 
of maps on. Otherwise Nav runs in the background fine, gives audible directions 
at appropriate times, but when you have it in the foreground doing the tracking 
it freezes and crashes. 

Original comment by RayFo...@gmail.com on 2 Nov 2012 at 4:07

[GoogleCodeExporter]

I wanted to note that all of the Sense based roms don't have issues with 
running Navigation but any CM10 variant seems to bring about this issue.

What version of the product are you using? On what operating system?
Maps 6.14.0
CM 10-20121102-NIGHTLY-evita

Things I've attempted:

Full wipe of SD Card.

RUU back to 1.85
Flash CM10
Install Maps through Play Store

RUU back to 1.73
Flash CM10
Install Maps through Play Store

Build.prop tweaks used for screen tearing
debug.composition.type=dyn

Original comment by ricky...@gmail.com on 2 Nov 2012 at 7:22

[GoogleCodeExporter]

Do you still get that *exact* same logcat on newer CM nightlies? Please update 
to a newer nightly and please provide a logcat. Would like to see if the app is 
still calling for too much Memory or not.

Original comment by h8r...@gmail.com on 4 Nov 2012 at 10:21

[GoogleCodeExporter]

First time I'm attempting to get a logcat so not sure if this is what you were 
looking for... here is the logcat I pulled shortly after my navigation 
crashed/stopped responding.

This is running the 11/4 nightly. No custom kernel.

Original comment by ricky...@gmail.com on 5 Nov 2012 at 7:36

Attachments:

• 2012-11-04-23-27-31.txt

[GoogleCodeExporter]

Just thought I would post a temporary solution I discovered. Navigation will 
work as long as I don't have the map follow me. Basically I zoom out on the map 
and I never get a force close or anr. Not sure if that will be case for the 
rest...

Original comment by ricky...@gmail.com on 8 Nov 2012 at 4:07

[GoogleCodeExporter]

Yes, the issue is only when maps is tracking. If you press the home button and 
let nav run backgrounded, it is fine.

H8: Can someone give me the procedure to follow to get a useable/helpful log 
file for you? do I need to start a "record" before initiating the problem?

I'm on 11/7 nightly and wiped data/cache on the maps app before testing. 

Original comment by RayFo...@gmail.com on 8 Nov 2012 at 10:29

[GoogleCodeExporter]

Got some GPS changes for next nightly. Let me know if this gets better.

Original comment by h8r...@gmail.com on 11 Nov 2012 at 3:47

[GoogleCodeExporter]

Running 11/11 nightly. Fc and anr aren't happening as fast but still unusable. 
I attached a log. Hopefully this one is more helpful...

Original comment by ricky...@gmail.com on 13 Nov 2012 at 7:54

Attachments:

• 2012-11-12-23-18-02.txt

[GoogleCodeExporter]

My experience is this lately. 11/11 nightly:

when i start Navigation. It Loses data connection. then Loses GPS, then 
everything comes back and works fine (15-30 Seconds later)Except Tracking... 
maps still closes during route tracking - if you hit home (or switch tasks) to 
background Maps, Nav will continue guidance in the background fine. 

Original comment by RayFo...@gmail.com on 13 Nov 2012 at 6:28

[GoogleCodeExporter]

It looks like the Nocturnal Dirty 4.2 ROM that's partially based on CM10 has 
fixed the GPS/Data issue:

http://forum.xda-developers.com/showpost.php?p=35034096&postcount=1075

Any chance we could incorporate that fix back into CM10?

Original comment by silel...@gmail.com on 5 Dec 2012 at 6:41

[GoogleCodeExporter]

I start Navigation and get to the rolling map just fine.  After usually a 
couple minutes I get a message that Maps has crashed.  Usually if I hit "OK", 
the spoken navigation will still run in the background and Navigation will 
begin running again - I can tell because the icon appears in the Notification 
Bar again.  I can drop the shade down and go back to Navigation just fine.  It 
will crash again just the same way but it will not restart.

I do not appear to be losing data or GPS, just the rolling map crashes.  I've 
attached a log.  I was running CM10 build 20121203 at the time.  This has 
noticeably improved from the last time I used CM10 - the first time I was on 
this ROM (back in October) it would crash the moment the rolling map opened up.

Original comment by jspi...@gmail.com on 6 Dec 2012 at 4:29

Attachments:

• 2012-12-04-07-27-05-partial.txt

[GoogleCodeExporter]

I've been running the 10.0 Stable since it came out and after some recent 
traveling I noticed an issue when trying to use the Navigation app. When I 
would attempt to use it, the app would run for not even a minute and then crash 
out to the main Maps app or to the home screen.

Thought it was GPS related but nope. Re-flashed clean still no good. Finally 
did some research now that I had time and I found this page 
(http://code.google.com/p/cyanogenmod/issues/detail?id=6611) that pretty much 
captures the exact issue. Basically, if I put the map into 3D mode by hitting 
the compass (or if it starts there automatically) the app freaks out and 
crashes. In the Maps app, if I put it in 3D mode it starts doing some graphical 
glitching as well.

So it seems to be something with the 3D graphics causing the apps to break.

Original comment by cove...@gmail.com on 10 Dec 2012 at 3:49

[GoogleCodeExporter]

Noticing that newer nightlies (12-16 right now) when Navigation is running in 
the background, it will "GPS Signal Lost" every 2-8 minutes while traveling. 

Original comment by RayFo...@gmail.com on 18 Dec 2012 at 6:22

[GoogleCodeExporter]

Could it be an issue regarding changing modes with glonass on/off ?  Anyone 
know if it's possible to entirely disable glonass to test this theory?

Original comment by ben...@gmail.com on 19 Dec 2012 at 2:32

[GoogleCodeExporter]

Original comment by h8r...@gmail.com on 25 Dec 2012 at 12:51

• Added labels: Milestone-CM10

[GoogleCodeExporter]

Original comment by h8r...@gmail.com on 4 Feb 2013 at 8:06

• Added labels: Function-Apps

[GoogleCodeExporter]

This works in cm10.1 w/o issues now. There probably will no longer be any focus 
on cm10 on this issue, so please use cm10.1 (should soon be on nightlies). 
Thanks for your understanding.

Original comment by h8r...@gmail.com on 8 Feb 2013 at 3:48

• Changed state: Done