Native Google Maps Planung berechnet immer von 3% zu wenig SoC

  • habe mal an byd gemailt.


    Dear BYD Technical Support & Software Team,




    I am writing to report what seems to be a reproducible software bug regarding the State of Charge (SoC) reporting between the vehicle system and Google Maps (both in the vehicle's built-in Android Automotive infotainment and when syncing routes via the Google Maps smartphone app) on my BYD Atto 3 Evo.



    1. Observed Behavior (Constant -3% Offset)


    Dashboard vs. Google Maps: Regardless of the current battery level, Google Maps always receives a starting SoC that is exactly 3 percentage points lower than the official SoC displayed on the vehicle's instrument cluster.

    Example 1 (Commute): When the vehicle displays current 72% SoC, the Google Maps mobile app (via cloud sync) shows current 69% SoC. For my commute, Google Maps calculates an arrival SoC of 60% (which correctly reflects a 9% energy consumption based on the wrong 69% starting value, rather than the actual 72% -> 63%).

    Example 2 (Short 1 km trip in-car): Using Google Maps built-in directly inside the car for a destination just 1 km away immediately predicts a 3% battery drop upon arrival. This confirms that the in-car system is also starting its calculation from the -3% offset value and does not correct itself during navigation.

    Comparison with ABRP: Using A Better Routeplanner (ABRP) connected directly to the vehicle's telemetry shows the exact, accurate values (72% start -> 63% arrival, 9% consumption), proving that the vehicle's consumption modeling is fine, but the initial SoC value passed to Google is shifted.


    2. Likely Technical Root Cause

    It appears that the BYD Android Automotive Vehicle Hardware Abstraction Layer (VHAL) is mapping the unscaled internal BMS raw SoC (which excludes the lower buffer) instead of the customer-facing display SoC shown on the instrument cluster to the standard Android EV battery property (INFO_EV_BATTERY_LEVEL / EV_BATTERY_LEVEL).


    Because the offset is strictly linear and constant (-3%), fixing this mapping in the VHAL / firmware to pass the scaled dashboard SoC value will immediately make Google Maps arrival predictions 100% accurate.


    Vehicle Details:


    Model: BYD Atto 3 Evo Design

    Current Infotainment Firmware Version: 1.3.0


    Please forward this detailed finding to the infotainment / VHAL software engineering team so it can be resolved in an upcoming OTA update.

  • E-Autos bisher: Seat Mii EV, Hyundai Kona EV, Cubra Born, Tesla M3, Tesla Y.

    Atto 3 Evo Design / Time Grey / innen Grau /

    Bestellt 20.04.2026 / Auslieferung 21.05.2026 /gekauft bei Feser Erlangen.

    AHK GDW ab 30.08.2026 Montage bei Kupplung vor Ort in Pilsting

    GJR 235/50 18 V101 Sailun Atrezzo 4Seasons Ultra

  • Servus,

    Danke für die Antwort von BYD

    Gruß 🙋‍♂️

    E-Autos bisher: Seat Mii EV, Hyundai Kona EV, Cubra Born, Tesla M3, Tesla Y.

    Atto 3 Evo Design / Time Grey / innen Grau /

    Bestellt 20.04.2026 / Auslieferung 21.05.2026 /gekauft bei Feser Erlangen.

    AHK GDW ab 30.08.2026 Montage bei Kupplung vor Ort in Pilsting

    GJR 235/50 18 V101 Sailun Atrezzo 4Seasons Ultra