2024 Kia EV6, stock head unit.
Edit with some quick notes because I didn't realize this blew up:
This is NOT yet usable as a replacement to stock. Working:
- Boots! (32 bit only because stock is 32bit, so no AAOS)
- Display
- Touch
- WiFi
- Maybe BT
- Maybe Modem (not gonna test that)
- GPS (uses translation daemon)
- Climate/controls/sensors/some energy stats - as much as MICOM provides anyway (uses translation daemon)
- GPU
- VPU (really need to test more)
Not working yet:
- Audio/amp control
- Power sequencing like when to turn off display, wake/sleep etc
- Any kind of head unit experience (this will come later, I'll try AGL first, and if I can get 64 bit then I'll try AAOS)
Use NEMESIS to get root on Android: https://github.com/xwtk/hmg_nemesis
Blog post that has a small section on this: https://w-floyd.com/2026/10/notes-on-llms-part-01/#2024-kia-ev6-head-unit I'll post more there as I find the time. I am using LLMs for a lot of the heavy lifting as I try things out (never to write my blog). I link to my GitHub repos there, where this work is being actively pushed.
I only bought this car a week ago.
Don't be an idiot and actually reflash your unit if you try this - I am using kexec to boot from an image from the USB, so this is completely nondestructive (NEMESIS is what actually is installed to the system).
Some more photos!
Yeah, you already said it was running Linux. (I love Linux, just funny how audio always seems to be so difficult to get working properly)
Very cool, I like it!
screams in pipewire
I had that experience, too. Then, some years back, I just stopped having issues with audio in Linux, it Just Worked.
But, maybe a year ago, my desktop machine started this thing where there is noise when the audio driver is active (I'm guessing, I don't really know). That is, if the system plays a sound, for some seconds after that, I'll hear noise from the speakers. Then it cuts off, until the next sound is played.
I've done some searching on the issue, without useful results, everything is about the power saving setting, which has had no effect for me. And the issue those people are having is different than mine, and I haven't hit on quite the right search terms to distinguish.
Similar thing happened to me, I think it was the switch to pipewire that made everything just work.
I'm going to take a wild swing here and say that's probably because there's still a load more audio controller ICs out there than for other interfaces and/or the other interfaces are more standardised on the firmware drivers. Therefore not all drivers cover all audio ICs so it's a bit of a faff to find the right one.