Skip to main content

Android Auto crash

Bug Reports

I just installed the 14-day demo version on my Pixel 7 Pro. I connected my Peugeot e-3008 with Enode. But I'm having a big problem. Android Auto starts up and then closes instantly. Then Android Auto stopped starting altogether. If I uninstall ABRP, everything works normally again.

Where does this happen?
ABRP version number (found at bottom of settings menu)
Posted by Chardo ·
Status: Awaiting Clarification15 comments

Log in to comment and vote

Comments15

  • Linda ABRP

    Team•

    Mar 19

    Hi

    If this works now maybe it was just something temporary. Please let us know if the problem continues.

    • Chardo

      •

      Mar 19

      I've turned my phone off and on again, I've turned my car off and on again. Nothing works.The problem is still present.

      • Chardo

        •

        Mar 19

        Android Auto starts working normally as soon as I remove ABRP from the Android Auto launcher. As soon as I re-add it, the problem reappears.

        • Linda ABRP

          Team•

          Mar 19

          According to my colleague this should be fixed if you update the cars software.

          • Chardo

            •

            Mar 19

            The car's software? I don't have control over that; Peugeot manages that over-the-air (OTA) whenever they feel like it. As of now, I don't have any pending updates.

  • Chardo

    •

    Mar 22

    Hello, I'm continuing my various tests. I managed (I don't know how) to get ABRP to appear on my car's screen after restarting everything (car, phone, clearing the Android Auto cache). The map displays correctly, BUT BEWARE, as soon as I start navigation to a destination, Android Auto CRASHES. Android Auto disappears and it's impossible to reactivate it without stopping the car, clearing the cache, etc. I tried with a Pixel 6 Pro instead of my Pixel 7 Pro, same problem. Do you think you could solve this problem or should I abandon the idea of ​​using ABRP Premium?

    • Samuel_ABRP

      Team•

      Mar 23

      Hi Chardo,

      this is exactly the issue, that the users over at issue

      https://abrp.featurebase.app/de/submissions/699eb5f8147be4b89542aeba also reported. I analysed it, and it looked like the amount of data transferred during initialisation of navigation crashes the network stack between Android Auto and your car. One user reported that the software update of the car fixed it for him. My guess is that the amount of data transferred for both the main screen AND the instrument cluster map (which is only visible with active navigation) overloads the data transmission.

      You could try a wired connection (make sure wireless AA is turned off) but not sure it helps.

      We are currently discussing internally, how we can prevent this by for example making it configurable, if the instrument cluster map should be shown, to reduce the amount of data hoping to prevent the network crash.

      We’ll let you know when we have a solution and of course you will get another trial period when we have a solution (or when you got the update for the car).

      Best

      Samuel

      • Chardo

        •

        Mar 23

        Thank you for your reply. For your information, I also tried with the USB cable and the problem is the same.