Join our newly restarted iOS Beta and try out new features sooner: https://testflight.apple.com/join/PDzBYbJw
Read more about ABRP beta at Installing the ABRP Beta version
No connection with car . Obd link cx works with carscanner. But not direct with my opel astra electric.
Whoever is responsible for this version has completely failed. Design over functionality. Where is the bar that shows all the charging stations and the destination (click on it to see your approximate arrival time)? How can you reset the map to the center when you move or zoom it? Why isn’t the old circle with the charging stations there anymore? It was much easier to read than the small 5/6 and green text. If you try to enlarge the information in the bottom left (by sliding it up), you see much less than before, and the column is much wider and covers the navigation bar. The only “good” thing—and even that’s debatable—about the new version is the larger font size for the time.
Scaling broken on Samsung dex secondary display regardless of screen zoom, font size or resolution. It was never perfect but now completely unusable. Most buttons register touch but no action follows.
Since the latest update, the map in Apple CarPlay is zoomed out way too far during navigation. This makes it difficult to see the road ahead and upcoming turns clearly. Before the update, the zoom level was much better and more useful.
This route is not taking the optimal route, likely incorrectly considering the mountain road to be closed for the winter: https://abetterrouteplanner.com/?plan_uuid=2-6aff40ab-db6a61a678646f9c0f81821a OSM (which I assume is the source) allows this route (which is open): https://www.openstreetmap.org/directions?engine=fossgis_osrm_car&route=59.6152075%2C8.9461525%3B59.8786976%2C8.5941579#map=10/59.7512/8.7712
ABRP does not work, valid addresses result an error message
Polestar 4 – Incorrect SOC in Android Automotive ABRP 7.1.12 I have a MY26 Polestar 4 connected to ABRP via Enode. The ABRP phone app correctly displays the vehicle SOC, matching the Polestar dashboard. However, the native ABRP app running on the Polestar native ABRP app running on the Polestar's Google Automotive system consistently displays approximately 5–7% less SOC while driving. Example: - Polestar dashboard: 53% - ABRP phone app: 53% - ABRP in-car app: 46% The discrepancy only occurs in the native in-car application. Enode appears to be working correctly. ABRP version: 7.1.12. Could you investigate whether the Android Automotive app is overriding the Enode SOC with an incorrect vehicle-data reading, and advise whether there is a workaround?
While already started with a navigation, When I click on the routes overview, there is no way for me to choose one of the proposed routes. Not via app and not via car. Also when driving and ABRP shows an alternative route, I can't click on it to follow this on instead.
The error says there are toll roads (which I have blocked). However there are no toll roads in the part of the country I am travelling through
SUC doesn’t exist yet https://abetterrouteplanner.com/?charger_id=1804421542
This happens at random intervals normally if app been running a little while, once stopped and car restarts again seams to reset.
Occasionally, the actual GPS speed is not displayed when using Android Auto. In addition, the speed limit displayed on the screen is incorrect; sometimes in the Netherlands, between 5:00 p.m. and 6:00 p.m., it already indicates that the maximum speed on the A9 in North Holland is 130 km/h, when in reality it is 100 km/h, which can be a costly mistake if you’re not paying attention.
In all versions SOE is bigger than SOC. Real SOC is 71,5 kWh. Your SOE over 100…
The charger shown off I-77 near Mineral Wells, WV IS NOT Electrify America as the charge station image clearly shows. It is a station owned and operated by Matheny Motors and accessible by cc tap. Additionally, the location shown is incorrect; however, I have no means to update this unless I am at the charge station. I am attaching images to support moving this to its correct location. Finally, the charger shown off I-77 near Beckley, WV and IS NOT Electrify America—as the charge station image clearly shows—and it duplicates a non-networked station identified as DC-America. This station station owned and operated by Gauley Beckley and accessible by cc tap. Please adjust its location from the front parking area to the driveway south of the travel plaza building as shown in the attached image of the Vankirk Dr area.
The new version is actually nice, but it doesn't take into account that some people have smaller screens. The search window—which can’t be hidden (and is also a bit buggy when it comes to text input and display)—takes up half the screen. Plus, you have to enter a destination to get rid of it. It’s impossible to just cruise around like this… Please fix this quickly!!
Vehicle selected in ABRP: MG S5 EV 2025 49kWh LFP Live Data source: Direct OBD BLE connection inside ABRP using a Veepeak OBDCheck BLE+ Issue summary: While driving with live OBD data connected, the SoC in ABRP randomly drops by a factor of 10 (rounded) for about 1 second before returning to normal. This spike/dip also appears in Trip History, confirming it is affecting recorded telemetry/OBD parsing rather than just a UI display glitch. The car’s dashboard never shows the drop and stays steady. Observed examples: 60% → 6% → 60% 64% → 6% → 64% 66% → 7% → 66% Timeline / Context: Although the Veepeak OBDCheck BLE+ is not on the officially supported list, this exact car + dongle setup worked reliably for about a year with no hardware changes until this week (after updating to 8.0.0). Car Scanner was briefly tested last week and uninstalled; its connection is disabled in ABRP.