Fix Update – development status

Current step

Why is version 1.1.8 so extensive?

Bluetooth communication, data fragments, decoding, state management and the interface all sit between a vehicle and its display. Version 1.1.8 therefore considers the complete data path.

Progress

1. 1

   Understand the starting point

   Completed

   Vehicle requests, Bluetooth communication and app updates were examined as one complete data path.

2. 2

   Measure the complete data path

   Completed

   An internal measurement chain follows updates from the request to the app display.

3. 3

   Response-driven updates

   Completed

   New requests follow the actual completion of a vehicle response more closely.

4. 4

   Test driving data separately

   Completed

   Speed, power and gear were examined independently from supplementary information.

5. 5

   Prioritise driving data

   Completed

   Time-critical values receive priority while climate, media and charging data are distributed fairly.

6. 6

   Diagnostics and logging

   Completed

   A diagnostic system records technical events during local development and test drives.

7. 7

   Automatic transport recovery

   Completed

   A controlled recovery was developed for rarely open Bluetooth write operations.

8. 8

   Investigate rare interruptions

   Completed

   Incomplete packets were observed; the exact recurring timing pattern is not conclusively proven.

9. 9

   Isolate recovery completely

   Completed

   Old incomplete responses must not enter new recovery attempts.

10. 10

    Detect interruptions earlier

    Completed

    Incomplete packets are detected earlier without rejecting valid slow responses too soon.

11. 11

    Classify slow responses correctly

    Completed

    Valid but slow responses continue to be processed; recovery starts only substantially later.

12. 12

    Validate everyday operation

    In progress

    The fast driving-data path is validated together with media, climate, charging, tyre pressure, doors and location.

13. 13

    Consistent vehicle states

    Planned

    Related values should be delivered to the interface as one consistent state.

14. 14

    Dedicated telemetry processing

    Planned

    Communication, data processing and the interface are separated more clearly.

15. 15

    Performance refinement

    Planned

    Unnecessary changes, old work items and redundant processing are reviewed again.

16. 16

    Final release acceptance

    Planned

    The new data path is checked as a whole on vehicle hardware, iPhone and iPad.