Zum Hauptinhalt springen

Android crash on e3008 when using navigation

Bug Reports

When I start the navigation on ABRP, Android Auto crashes and gets me back to the car system. No other navigation service is active at the same time. As soon as I cut navigation in ABRP from the phone, Android Auto starts again and works fine. No problem when using Google maps. The e3008 has the navigation both on the driver screen and the infotainment screen, maybe that is the issue?

Where does this happen?
ABRP version number (found at bottom of settings menu)
Gepostet von Guillaume Robert ·
Status: Completed19 kommentare

Melden Sie sich an, um zu kommentieren und abzustimmen

Kommentare19

  • Samuel_ABRP

    Team•

    6. März

    Angeheftet

    According to the latest feedback, there was a very recent vehicle software update, that fixes the Android Auto connection issues. So everyone that sees the same issue, please check, if you are on the latest vehicle software and if you can update. The update should fix the Android Auto issues. This is no ABRP related issue, it is related to the Android Auto running in the vehicle.

  • Roeland Dhondt

    •

    2. März

    Exactly the same issue. I have e5008, which is basically the same car.

    It seems to be the case that ABRP does not know how to handle the dual screen capabilities?

    The expected behaviour is that, when navigation starts, the map gets projected on the digital gauge cluster aswell as the main Android Auto screen. Google Maps and Waze seem to be handling this just fine.

    • Samuel_ABRP

      Team•

      3. März

      Hi Roeland,

      just checked the logs for your user, and you still seem to be on 7.0.1, latest is 7.0.3 which already contains a few fixes for Android Auto, could you please update and check if it works for you or if the issue persists?

      • Roeland Dhondt

        •

        3. März

        Just tried with 7.0.3, issue persists unfortunately.

        • Samuel_ABRP

          Team•

          3. März

          Thanks for testing, please install the latest beta Installing the ABRP Beta version which is 7.0.4 and contains some fixed for how errors reported on Android. It might help us identify the issue as the previous error reports were a bit cryptic. That should help in identifying the crash. Just let it crash a few times so we can make sure one of the errors is sent to us. Thanks!

  • Linda ABRP

    Team•

    2. März

    Hi

    “The e3008 has the navigation both on the driver screen and the infotainment screen, maybe that is the issue?” Does this mean that you use the cars navigation at the same time as ABRP? If so that’s why ABRP does not work.

    • Guillaume Robert

      •

      2. März

      Hi,

      No, what I meant is that the navigation app I use displays on both the infotainment and driver screens. For example if I launch Google Maps, it shows a zoomed out view of the whole itinerary on the infotainment and detailed view with next intersection on the driver screen. I never use the car built-in navigation system. I hope it is more clear explained like this.

  • Linda ABRP

    Team•

    3. März

    I have sent this to my colleagues so they will look at it.

  • Samuel_ABRP

    Team•

    3. März

    Hey @Guillaume Robert ,

    I checked our crash reports and can’t find anything for your user. Did you turn off crash reports? If so could you please turn them on so we can check if we can see anything?

    • Guillaume Robert

      •

      3. März

      Hello Samuel,

      I just checked my app and the crash reports are enabled, but only the android auto view crashes, when I access the app on my phone, the navigation is still running, so it doesn’t seems like the app itself crashes, but more that something in the navigation mode make android auto fail. Tell me if anything could help you in your diagnostics, I can take a video of the behavior on the car screen for example, or check in android studio if any suspicious log fires when the problem occurs. Just let me know what you need.

      Also, just to let you know, I am subscribed to the beta in the Play Store and I just received the 7.0.4, not sure if it changes anything on your side to retrieve reports.

      • Samuel_ABRP

        Team•

        3. März

        7.0.4 is good as it fixes a few issues related to reporting errors on Android in a more readable way. So if you could use that version and reproduce the crash a few times we might eventually get a proper report. Lets see if we get one next time and only if that doesn’t work check the next steps.

        • Guillaume Robert

          •

          4. März

          Hello,

          I tried about 5-10 times yesterday around 7:10 p.m CET. It did still make the android auto system crash, but the app itself on my phone never crashed, so I don’t know if you will still get crash reports. Let me know if I can help you diagnose in any other way.

          • Samuel_ABRP

            Team•

            4. März

            Thanks for trying. Unfortunately I didn’t get anything. There is one more thing you could try:

            https://developer.android.com/studio/debug/bug-report

            When you create such a bug report after the crash, we would be able to see them as it also collects the errors written to the local logs. Its a bit more effort though, but would probably help us seeing the actual crash. You can upload it to google drive and share the link with samuel@iternio.com (don’t post it here).

            • Guillaume Robert

              •

              5. März

              Hello,

              I just shared the file with you. Let me know if you need anything else.
              First time using this report feature, if it doesn’t work as expected, please let me know.

              • Samuel_ABRP

                Team•

                5. März

                Angeheftet

                Hi,

                thanks for your fast feedback, really appreciated. Had a look at the logs. In the logs it looks like ABRP actually doesn’t crash, but rather the whole Android Auto process dies. Reading your initial message again you mentioned “When I start the navigation on ABRP, Android Auto crashes and gets me back to the car system” Did you mean the actual car infotainment by that? I thought it went back to the Android Auto app drawer, but it really looks like the whole connection breaks.

                One thing you could try to see if it makes a difference is using a cable instead of the wireless connection. However we have not heard of this before, so it might be a combination of Phone / Android version and/or car, that behaves weird here.

                Please let us know, if using the cable makes a difference. Also getting in contact here with google might help:

                https://support.google.com/androidauto/community-guide/347802564/how-to-report-an-issue-with-android-auto-and-get-more-help?hl=en

                I think some users that had issues with Android Auto before also reset the app (clear cache) / uninstalled the updates and set it up again from scratch. Maybe that might help too.

                • Guillaume Robert

                  •

                  6. März

                  Angeheftet

                  Hi,

                  I did try both wired and wireless but it yielded the same result.

                  It seems you were right though on the cause, as it just happened that the car suggested a big update wednesday evening (about 1.5GB) and I was able to test it this morning, and ABRP was working in navigation mode on both screens without Android Auto crashing. It seems they updated the bundled Android Auto version as it gained a fullscreen button on the infotainment display. You must have been using an API that maps and waze weren’t using and that caused the crash in the old version.

                  Anyway, thank you for your time and help diagnosing the problem.

                  I have a trip planned next weekend, so I will be able to test if it is stable on the new version or if the problem comes back.

                  Best regards

  • Diego Frei

    •

    3. März

    I have the same issue in my e5008, as soon as I start the navigation of a planned route Android Auto crashes an tries to reconnect repeatedly. The navigation still works on the phone as I can hear the route advisories out of my phones speaker.

    I had this issue already last year as we got our new e5008 but then after an update (I do not remember to which version) I worked during our holidays. Later in 2025 the problems started again after another update.

    • Samuel_ABRP

      Team•

      6. März

      Hey, in 2025 we had a bug in Android Auto, that the instrument cluster display map was not shown. We later fixed it, so if the data of two screens was a bit too much, it could explain it. Do you remember from when it still worked if you had the instrument cluster map or only the main AA screen?

  • Guerinel

    •

    13. März

    •

    Zusammengeführte Anfrage

    •

    1 Stimme

    Android Auto crash when starting a trip

    Android Auto 15.9
    ABRP 7.0.0
    Samsung Galaxy S24+ and Samsung Galaxy S22
    Peugeot E-3008
    Wired and Wifi connection

    I can access ABRP home page, access every functionnality.
    But as soon as I start a trip, Android Auto crash immediately
    Connection is lost, when it come back it crash again immediately => infinite loop until I manually stop the trip on my phone.

    Tested on Samsung Galaxy S24+ and S22, wired or wifi connection, with or without ODBBLE dongle: same result.

    I have no issue with Maps, Waze, or any other application.

    This issue has started begining of december (so before 7.0.0 ABRP version) and still occur today.

    Thanks for your help