Skip to main content

Dacia Spring 2024 in Android Auto reports SoC 5-11% lower than Dashboard and ODB-II

Bug Reports

I have a Dacia Spring 2024 and it can provide the SoC via Android Auto to ABRP. The reported SoC is, however, between 5 and 10% lower than shown in the car’s dashboard. E.g. when the car is fully charged, it appears as 90% in ABRP.

It seems, that the deviation depends on the actual charge. I collected the following readings:

Car  | ABRP via Android Auto
100% | 89% (sometimes 90%)
90%  | 80%
86%  | 75%
80%  | 70%
60%  | 51-52%
55%  | 48%
40%  | 35%
35%  | 30%
31%  | 28%
(I have not yet gone to lower charging states, but the diff seems to be getting lower the lower the SoC is.)

It would be great if this could be fixed and/or a possibility to add a correction factor could be added to readings from Android Auto SoC.

Thanks in advance!

Where does this happen?
ABRP version number (found at bottom of settings menu)
Posted by Martin C. ·
Status: Planned3 comments

Log in to comment and vote

Comments3

  • Samuel_ABRP

    Team•

    Sep 4, 2025

    Hey Martin,

    did you already send a bug report to Dacia? We only pass along the values, so it’s the values they provide and the proper solution would of course be that they fix it.

    We can however check if there is something we can do here. It would be a manual process though (like entering upper and lower correction values) and if the soc is not linear the middle soc values would also not be correct.

    So my suggestion here is that we provide something in the AA settings, that when you fully charged the car, you can correct the upper range of the soc value, and when you discharged to like 10% you can correct the lower range, so we map the soc to the car display value. This could work, in some cases might not.

    What do you think about this idea?

    • Martin C.

      •

      Sep 4, 2025

      Hi Samuel,

      I think that would be perfect. It looks like the value reported by Dacia is assuming a wrong value for the maximum charge of the battery, so I expect being able to correct the value at the extreme points (fully charged, empty, or better let’s say, at 10%) would be a good workaround. The lower the SoC becomes, the less the difference it seems. The lowest I currently went was a displayed SoC of 20% which was reported as 15% via Android Auto. So I somehow feel that close to 0 both values would actually close in.

      I have not yet reported this to Dacia, since normally those bug reports seem to vanish somewhere along the reporting line, but I’ll give it a try.

  • Matt (ABRP)

    •

    Aug 18, 2025

    Thank you for reporting! We will take a look at this and fix it.