this post was submitted on 21 Dec 2024
82 points (93.6% liked)
Open Source
31692 readers
409 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
One dreams of a day where it could be a thing. My take is that a drop in replacement is not possible because there is no incentive for car manufacturers to provide that hardware interoperability. They profit too much from the work google does to write the software for them, and all your data they can sell. They want you to buy a whole new car to get the latest features, they are not going to make it any easier on you to extend the lifetime of their product.
There are projects like Crankshaft that allow you to add a head unit to a vehicle that does not have one, but that does not get rid of the android app on your phone. As far as i know all these projects relay on a reverse engineered implementation of the android auto spec: https://github.com/f1xpl/openauto
One could read that implementation and make a client, but i am not aware of one that exists, let alone is actively maintained. Ibl believe the reason is the cost of testing the software for compatibility with all the different auto maker hardware makes this too difficult to sustain. I look forward to other responses to see what others are using.