ABRP V5.5.2 The time display for the next stopovers and the destination and the durations in the route information are increasingly distorted during the journey

It is completely incomprehensible to me why the ticket, which I opened two years ago concerning the same error was closed during the last 2 months (https://abrp.featurebase.app/en/p/time-at-the-next-stopoverdestination-is-displayed-incorrectly-in-the-2) although the error has continued to exist since version 4.3.9 until now (5.5.2)!

I am therefore submitting the ticket here again for processing.

ABRP V5.5.2 (3180)

iPhone 13 Pro iOS 18.2

Apple CarPlay

The departure time displayed for the next stopovers and the destination in the route information becomes increasingly falsified during the journey.

So the time information is completely misleading and absolutely useless the way it is currently calculated.

In the example, there are only 22 minutes left until arrival at the destination at 08:37. The route information permanently displays the duration of 1h1min during the journey. It does not show the actual time left to drive. This is probably a value that is calculated only once at the start of the route and then not updated.

The display of the planned arrival time in the route information is incorrect. It seems as if the planned arrival time (with +/-1 minute rounding accuracy) is displayed according to the following formula: Current time + planned duration = planned arrival time. 08:15 + 1h1min = 09:17

However, it should be displayed as follows: Start time + planned duration = planned arrival time. 07:36 + 1h1min = 08:37

In another example, ABRP then shows a departure time from the next charging station on a long route with many charging stops, from which you can calculate a charging time of over 4 hours, although ABRP itself correctly only speaks of a charging time of 50 minutes :-(

ABRP always adds the duration to the xth charging stop, which it originally calculated at the beginning(!) of the route, to the current time. However, this calculation is incorrect, as already explained above.

The incorrect calculation affects all departure times from intermediate points/charging stations and also the destination time at the end of the journey.

Another example: Time until next way point 17h 13min!

I hope this time the ticket is not simply closed again.