Hacker News Reader

Comment by ubermonkey | Hacker News Reader

I mean, who cares about $automaker's infotainment if Carplay or AndroidAuto is available?

Subaru's bluetooth implementation adds multiple seconds of delay, so your navigation instructions will be so late that you'd miss turns if you relied only on audio.

It also randomly crashes and fails to connect (in my experience)

I don't know, my Volvo supports both and I pretty much never bother using Android Auto, it's just such a faff. The built in interface(sensus) works great and the navigation is really good. Like, what do you use either of those two systems for?

Who cares about carplay or androidauto when plain ass bluetooth does most everything you should be caring to do while operating your vehicle (which you should in fact be 100% focused on and not touching your damn phone or other screens or anything else.)

At least Android Auto supports integration with steering wheel buttons and center console display on many cars — I imagine CarPlay too — this means you can can keep your music and navigation (favorites and such) in one place.

Bluetooth natively supported my steering wheel buttons in my SAAB 2005 9-3t, a decade before Android Auto or CarPlay ever existed.

I am counterpointing that you need to look at the screen with Android Auto: you don't.

My older 2008 car also had a bluetooth system with similar capabilities, except that it did not have navigation (that was a 2000 EUR add-on). I did have to copy my MP3 music to a CD to play in the car — only once I added an aftermarket infotainment could I use USB or SD cards to put music on them.

That car even supported something called rSIM (remote SIM, where phone exposes your SIM card over a special protocol for modem in the car to use — I guess similar to eSIM today, except that the phone could decide to share it). The only problem was that only Nokias supported that well, and not for long, but it used an external car antenna to improve reception when travelling :)

Reply on news.ycombinator.com