Sometimes I have the problem that the map does not follow the vehicle when driving off. The directions and the remaining distance are correct as to where I should turn, but the map remains at the starting point. Even if I activate the different views at the top, this does not change.
So I have to stop, plan again and start the route again. Then it will work.
For me, this has not been fixed. It still occurs regularly even with the newest version 4.2.0.
This happened to me yesterday too. I had to restart the infotainment system to get ABRP to work again.
I saw the same today with ABRP App V4.1.14 that the map does not follow and all other was correct. But this happend only if I'm in any configuration dialog at the same time.
As soon as I've left the configuration dialog, the maps jumps to the correct position.
Maybe you have the same issue.
No that was a different issue which is solved by now. Yours sounds more like an app issue, the other one was in android auto. If you think this is unexpected behaviour, please open another issue.
Will be fixed in next release 4.1.13 which was sent to review and should be available in the next days.
Today I have tried Android Auto first time. Unfortunately the predictet SOC is not updatet. Also my position on the map was always the startposition. 🥴🤗
Could see the same behavior in one of the recent versions. Will try to reproduce this so i can find the root cause.
I had both problems today. The prediction was stuck on 20% even when the actual charge level was below. I stopped for charging three times today and the map followed my position only once after continuing. I do not know what was different at the time when it worked. 🤔
I have an id.4 and use Tronity and a Samsung Galaxy A10. I guess everything will be better if I get a BT-dongle for the OBD-port? 😊
the SoC should be updated latest one minute after, when the plan is refreshed. The not moving map is a bug we are currently trying to hunt down but it is quite hard as it is not so easily reproducable. In that case please replug the USB cable or restart ABRP as a workaround for now until we solved it. Normally only happens at start if at all and then not again. If you find a way to reprodcue this easily, let us know.
Today I took a trip using version 4.1.13. The map moved and the estimated charge level was updated correctly.
VW id.4, Android Auto, Usb-connected.
Hi Sven, can you please provide information about the version of ABRP you use? Also do you use live telemetry? We recently fixed issues related to that and I have not seen such a behavior anymore in our test versions and had it every now and then before, so it looks like that fix we did worked. Should be part of current latest 4.1.11 already, so if you are on a lower version please update. Are you on iOS or Android?
We also just released a new version 4.1.12 which should be available soon, so maybe try again with that version and let us know if you still experience that issue.