This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Map won't display for activities longer than ~30km

If I look at an activity that is less than about 25km the map displays perfectly. If I do the exact same action on an activity longer than 30km then the app doesn't open the map but goes back to the activity list. Can't narrow it down... Not enough data to narrow it down further.

No error messages.

Connect v2.0.1
Android 4.4.2 on Google Nexus 4 (and 7)

0 Former Member over 11 years ago

MCHUNNYMONSTER, please post the activity ID. To find the activity ID, sign-in to Garmin Connect from a web browser. Go to the list of activities. While hovering over an activity, notice in the browser's status bar (usually located at the bottom of the browser), the ID suffixed to the URL. Thanks.

0 The_Hunnymonster over 11 years ago

453745501 and 445904468 as examples.

0 Former Member over 11 years ago

Thanks for the activity IDs. I haven't been able to reproduce the problem. I've never seen an activity with so many laps. :) I suspect this may be where the problem lies, but I'll have to wait until tomorrow to try to load the activity map on a few different phones. The attached photos were taken using a brand new HTC One Android phone.

Is the crash happening on the summary screen or the large full-screen map page?

0 The_Hunnymonster over 11 years ago

Only happens when you go for the large full-screen map (and GCM 1.3.x didn't suffer the issue).

Mainly has so many laps because I'm also gathering lap-drift data for your Fenix colleagues (where the lap is marked progressively later after each lap... so 1.004, 2.007, 3.011...) - it's no big deal for me really - but if there's someone out there doing a 100km+ bash with 5km laps he'll be "put out" to say the least.

0 Former Member over 11 years ago

Fixed in Version 2.0.2

It turned out to be a memory issue with some Android devices. Testing with Nexus phones and tablets produced the same problems as you described. The fix is coded and will be released in version 2.0.2. Thanks again, MCHUNNYMONSTER, for your assistance.

0 The_Hunnymonster over 11 years ago

Works for me...