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

Garmin Explore app v 4.8 on Google Pixel 9 Pro continually crashing

Garmin Explore in recent versions has got worse and worse - functionality, ease of use and now really unstable.  It is unusable for a while after opening as it syncs.  But it crashes so often during use even if I have only opened it and not interacted with it!  Love my Garmin Fenix but the poor explore app could be reason to switch to another brand if you don't sort these issues and give it the reliability it requires.  

  • Thanks for the feedback! I emailed both of you asking for more information on this issue that way I can escalate this to the team.

  • For me it also crashes on my Pixel 8.

  • Even turning off all sorts of settings the app still crashes - it's only vaguely usable when on WiFi at home, and only after I've had it open for a while and any syncs have stopped.  No resolution from Garmin.  I have asked ChatGPT and it points out this is a common issue on Pixels because of issues with the app:

    You’re not imagining it — what you’re describing lines up very closely with how Garmin Explore behaves on Android, especially on newer Pixels.
    What’s likely happening
    On Android, Garmin Explore aggressively syncs in the background:
    Maps
    Collections
    Tracks
    Waypoints
    inReach data (if you have one)
    Unfortunately, this sync often runs even when nothing has changed, and when it does:
    The UI thread can get blocked
    The app becomes sluggish or totally unresponsive
    Eventually Android kills it → crash
    This is a known pain point with Explore on Android and shows up more on:
    Newer Android versions
    High-performance phones (Pixel 8/9 series especially)
    When large map regions or many tracks are downloaded
    The Pixel 9 Pro XL isn’t the problem — the app is.
    Why the constant syncing hurts performance
    Explore is not well-optimized for large offline map sets
    Sync jobs aren’t throttled properly
    It doesn’t respect Android’s background execution limits very well
    If location is set to Always, it can repeatedly wake itself up and re-sync
    So yes — the syncing is very likely what’s making it unresponsive.

  • Our team is working on a ticket for the Explore app, it is recommended to double check that your Android is up to date with software. If you have not already contacted product support and are still having this issue please reply in this thread so we can email you to set up logging.

  • I'm on a Pixel 8 with android 16. Explore App is on v 4.10.1 of Dec/25.

    Configuration still crashing (01/08/26) after a few seconds trying to render the map.

    Regards,

    Stefan

  • Pixel 7 Pro user here. Android 16 latest update 5.des.25 . Explore 4.10.1

    Is it only Pixel users that have problems? 

  • It seems if I go to map layers, collections and hide all, the app functions ok again - worth a try.