6.1.0 is eating up all phone resources, navigation is lagging
ABRP is eating up all CPU and memory resources when driving long roads, rendering the phone unusable.
We drove about 500km, we had configured the route to avoid toll roads which took us to lots of side roads implying turns every 5 to 20km.
Most of the time this makes the phone useless. I was driving and my wife wanted to change the playlist in Deezer and send a Whatsapp message, this deemed to be impossible unless we stopped ABRP. The phone is getting very slow, the navigation starts lagging: e.g. we were instructed to take a left turn but we had already drove by the intersection for about 1km.
Closing other apps does not help neither.
Phone is a Samsung Galaxy A53 5G with latest updates.
Android Auto was running and we also had ODB connection.
- Where does this happen?
- ABRP version number (found at bottom of settings menu)
Log in to comment and vote
Comments3
Geoffrey
Jul 30
Allright, One year later took ABRP again on a Roadtrip…. It was quite an unpleasant experience. It seems nothing improved since last year. On longer routes, it just eats up all of the phone resources.
I used the latest version at the time of writing 7.x.x something
Worse, it always lost the OBD2 pairing, I had to unlink and relink my vLinker OBD dongle almost every time I started the car. I switched to beta version and this seemed to be solved.
When driving I run 3 apps: ABRP through AA, Deezer and aprs.fi. The latter runs on the phone screen. I can run Deezer and aprs.fi with Gmaps all in paralle, all is very smooth.
At one point I got a phone call during navigation and it caused the phone to crash….
Eventually we used ABRP to locate charging location and navigate using GMaps ….
Linda ABRP
Jul 24, 2025
Hi
We will release 6.1.1 within the next couple of days with some fixes for Android auto. Please see if that solves the problem.
Geoffrey
Jul 30, 2025
Only drove about 100km with 6.1.1, I can see some improvement but the phone still gets slower.