Joined
·
13 Posts
No, that's not what i meant, i really mean it's messing up the KM left that the car thinks it can do. Look how many kms i'm able to driveMy guess is that the software update is funneled through the CAN/OBD-II bus, which probably runs at something slow like 500 kbps, rather than the 1,000,000 kbps that Ethernet does (or, similarly, a MicroSD or SDCard port, which would cost approximately nothing in hardware costs.)
Begin snark ->
The reason I think this is so, is that this is exactly the kind of design decision an Old Car Empire would make. They have a system for software updates for the old cars, and it works, so why change it when your multimedia system suddenly uses software images that are 1000x bigger?
(Also, the CPU/GPU of the MMI is atrociously slow compared to even a $100 Android phone. But, you know, it's probably still some embedded single-core ARM 7 with a 2D blitter GPU which they got for cheap and have a ten year source for, so why update that more than every 20 years?)
<- end snark.
That could make sense, if the nav knows that the path it's planning is more efficient than your average drive.
Also as it thinks it can drive 840km after entering a 500+km new ride, it will NOT propose any charging stops
This was not the case with software 3608
Problem was triggered with softwareupdate 3812