7 Comments
User's avatar
Arvind Ganesh's avatar

Much the same as yourself. No real changes. I'm glad nothing got worse. I would love a pet mode and for the console display to show the current song.

Zouhdi Hajjaj's avatar

My early impressions on first extensive driving day post-update: 1. The rear view camera issue seems to be more frequent now than it was with version 3.6.4. 2. The UI is taking considerably longer to connect with my Ottocast wireless dongle for Android. I'm trying an infotainment reset and hoping for an improvement. Coincidentally going in for my 1st (since I acquired the vehicle a year ago at 10K miles) maintenance next week, so will ask about any ongoing issues.

soapyfrog's avatar

Using android as the base OS would worry me as it’s really not designed for something important like a car. Still at least it’s not Windows! Also, isn’t Android 13 quite old now? Does it still get security updates?

Paul Lefebvre's avatar

It’s not really Android 13. It’s Android Automotive 13, which is definitely designed for a car. Not sure how long it is supported, though.

soapyfrog's avatar

No citation, but apparently: Polestar and Volvo vehicles (both running AAOS) have been particular targets [for hacking], with users sideloading arbitrary APKs via ADB relatively early after launch. Some owners have gotten full Android app stores, unapproved apps, and custom launchers running this way.

Paul Lefebvre's avatar

It would be handy to have an official way to run apps via adb on the car itself. Having to submit to Play Store first is annoying.

soapyfrog's avatar

Still Android at its core though. It has some full RAM suspend features so it’s more responsive on startup and I gather the really critical stuff is handed off to some HAL/RTOS, but yea, still Android. The benefit of AAOS is that it _is_ Android so easier to integrate a lot of Android software. Same binder IPC, same ART etc.

I wonder if anyone’s rooted it yet to run their own builds?