I use ABRP with Android Auto and an BLE ODB2 adapter. ABRP is only getting the latest SoC from the adapter when the app is activated on the phone. After some minutes, ODB connection goes red on Android Auto screen and is not updated unless I pick up the phone and activate the ABRP app again.
All energy-saving settings of the phone are disabled for ABRP.
Running Android 12 on a Xiaomi Mi 11 Ultra, Skoda Enyaq.
As I wrote here: abrp.upvoty.com/b/report-a-bug/map-freezes-using-android-auto/ it seems after a small test that this issue is resolved in the latest beta. However, I would prefer to check again tomorrow to prove that this behaviour is consistent.
After a number of additional trips I observed that I still have to start the app manually on the phone to make ABRP work reasonably on the car screen. As long as I do not do that, the car screen app is not usable at all. I can select targets, but it won't calculate the route, and there is no display of the SoC. Also, I noticed that the language is English regardless of the personal language.
When I start the app on the phone, it starts calculating the route, shows my personal language, and after a minute or so also displays the SoC from the OBD adapter.
Further testing on the weekend confirmed that I always need to start the ABRP manually on the phone before I can use it on the Android Auto screen in the car.
Just starting the car enables Android Auto, and I can use any app, just ABRP will not be of any use before I manually start it on the phone.
I'm still struggling to find the exact pattern when this works and when not, but after further testing today it seems that using 4.2.0 I have to activate ABRP on the phone once when starting the trip and go into the car settings, potentially even get into the OBD connection setup until it catches the signal - but at least it seems to keep that signal then for the rest of the trip even if I do not touch the phone anymore.
Yesterday I did not go into the car menu, and it never got a signal for the entire trip (> 1 hour).
Still monitoring the topic, but it seems that version 4.20 might have resolved the problem.
Hi, in the other topic you said 4.20 did not work, so does it work now or is there still any other problem?
Not sure what you are referring to, but I reported about the map freeze issue in the other topic. That's a different story.
Still monitoring this issue - yesterday it didn't work again, but I was too busy with my family to explore the details.
Any update on this? It still does not work.
I have tested the new version for a few days now, many thanks, but unfortunately it only made things worse. It hardly finds the dongle when I build up the connection (means it takes very long and many tries until it appears in the list of available BLE devices to connect to), whereas the old version finds it somewhat reliably. And even if I managed to set up the connection it is hardly stable enough to read the SoC.