Skip to main content

Android Auto SoC ruins API Transmisson

Bug Reports

Hi there,

I used ABRP today the first time since the implementation of SoC via Android Auto. I generally used the generic API which worked quite good with my Peugeot and PSACC.

But today navigating was a nightmare as the SoC jumped between a 100% and the real value. Therefore ABRP wanted to suggest new routes with or without charging stops all the time.

Even now, away from the car, the values jumps between different values even though ABRP says, there is no API connection. A made a bug report, maybe that helps:

https://api.iternio.com/1/?eventlog_uuid=2344e212-cceb-41bd-b1f8-f59daf669d31

Best,

Henning

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

Log in to comment and vote

Comments2

  • Matt (ABRP)

    •

    Jul 8, 2025

    Thanks for reporting!

    Can you please try turning off Android Auto telemetry? See instructions here: Live Data via Android Auto

    We are experimenting with the new AA implementation in the Beta so some things might not work yet as expected, if you’d like a more stable experience you can always leave Beta for now.

    • Henning Schwartz

      •

      Jul 29, 2025

      Hi Matt,

      thank you for your reply. I didn’t see it until now.

      Peugeot changed something in their API. Therefore the time stamp for the transmission of the SoC was outdated. The PSA Car Controller by Flobz transmitted an old date and ABRP didn’t know what to do with it. I apllied a fix for PSACC and now it seems to work again.

      Sorry for blaming you!

      Best