The time was set to auto set
Only the center screen got the correct time after that
The driver screen was not time synchronized , so it was failing
had to manually correct the time
Are you saying that there are 2 separate clocks, both of which can be set independently? Or did the coding change to set the time automatically require you to manually set the time in order for the time to be synchronized throughout all modules? Since making this coding change, I've never set the time manually and haven't noticed any problem, but I don't use low-cost charging.
EVMan wrote:is this backup the very first original car configuration or the previous last configuration.?
The BimmerCode developer told me that the more recent Android version stores a new backup of each module's parameter values only if a coding change has been saved. The older iOS version stores a new backup whenever a module is accessed even if nothing has changed which can result in many duplicate backups and excessive memory use. He told me that he planned to implement the Android backup algorithm in the iOS version at some point, but I don't know whether this has been done yet.
It's always true with the Android version that restoring the most recent backup would restore the system to the state immediately before the last changes were saved. But with the older iOS versions and maybe even the current version, restoring the most recent backup would restore the system to its previous state only if coding changes were saved the last time the module was accessed. Because of this uncertainty, if I visit a module but don't save any changes with my iOS version, I delete the backup that has been created so that duplicate backups don't remain.