manio07

It's also possible to do it with DPI change. When I set it the very low then the nav bar automatically changes position to vertical... https://github.com/aa-proxy/aa-proxy-rs?tab=readme-ov-file#dpi-settings

I was also tinkering with hyprland but first thing I did was disabling animations and gaps. I also missed scratchpad a lot (using it very often). Finally I am back and love it!

Yeah, that’s true - it’s basically just a different approach. As I understand it, you connect to the dongle on Android and it forwards the data to ABRP - everything happens locally (on your phone), you’re just feeding SOC data into ABRP.

What I had in mind is something quite different: a wireless Android Auto dongle - for example running on a Raspberry Pi - that sits between the car and your phone. In this setup, the device itself connects directly to the dongle (not your phone). Thanks to that, I can “inject” SOC data straight into the Android Auto protocol, which gives you EV support directly in Google Maps!

ABRP is great (it has very precise configuration options, like exact battery percentages you want to arrive at a charger with, etc.), but Google Maps is much more simplified and doesn’t offer that level of tuning. Still, let’s be honest - Google does a really solid job and is basically the standard when it comes to navigation: traffic, hazard reports, everything in one place, and it works really well without additional apps.

If you now add estimated battery percentage at the destination and a live charger database that can be adapted on the fly (Google will automatically route you via chargers on the way), that’s a huge level-up in my opinion - especially for EVs where manufacturers often just completely ignore this stuff.

This is doable with SOC even on your Ionic, details: https://github.com/aa-proxy/aa-proxy-rs#google-maps-ev-routing

https://github.com/aa-proxy/aa-proxy-rs#google-maps-ev-routing