Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Apple's risky bet on CarPlay

theturnsignalblog.com

Post reply on HN
Print view View original

521–530 of 537 posts

Re: Apple's risky bet on CarPlay

#521

Post by briHass »

wnissen wrote: post #494
js2 wrote: post #181

Earlier quoted context omitted.

> But, between 2013 and 2017, things were a complete mess. In-car systems were too integrated to be replaceable with a third party 2-DIN unit, but too primitive to run carplay/AA Mazda sells a retrofit kit for their 2014 (Mazda 3) / 2016 (other models) and newer cars that didn't come with native CP/AA. It's about $200 and DIY if you're the least bit handy: https://mazdaparts.org/mazda-3-smartphone-mirroring-kit.html

I have installed that unit but I wouldn't characterize it as for the "least bit handy". It involves removing all the panels from the screen, center console, and shifter, and fishing some wiring behind the climate controls. Definitely do-able, but not for the faint of heart. The wiring is easy to connect, to be sure, Japanese are outstanding at that. Totally worth the money. I just wish I could put in one of the facto…

Having done this recently, the pro tip is that you can pop out the old USB/SD panel by inserting a hook pick into the holes on the front and yanking. It will pop the plastic faceplate off, and then you can access the clips to remove the entire unit. Mine was actually fine and I was able to pop the faceplate back on if I wanted to reuse it (not sure why I would), but no guarantee.

Turned it into a 15 minute job vs probably an hour+ of messing with the center console. Babysitting the software update takes the most time.

Re: Apple's risky bet on CarPlay

#522

Post by 486sx33 »

Almost bought a ford mustang but for some reason that year ford did not have CarPlay that worked via Bluetooth , you had to have the phone hooked up via usb and maps was glitchy as hell during the test drive. Bought a challenger instead which is a bigger nicer car anyway and CarPlay is flawless. I have a 2020 Yukon XL as well which is amazingly flawless for CarPlay , too bad GM dropped CarPlay. I wouldn’t buy another GM without it.

Re: Apple's risky bet on CarPlay

#523

Post by pbronez »

I recently rented a car with Android Automotive. I was not impressed. It was laggy, clunky, and confusing. Fortunately it supported CarPlay, so I mostly used that.

The one cool feature was that Google maps driving directions showed up on the front instrument cluster in addition to the center console. That’s a feature I’d like to have more broadly.

Re: Apple's risky bet on CarPlay

#524

Post by js2 »

briHass wrote: post #521
wnissen wrote: post #494

Earlier quoted context omitted.

I have installed that unit but I wouldn't characterize it as for the "least bit handy". It involves removing all the panels from the screen, center console, and shifter, and fishing some wiring behind the climate controls. Definitely do-able, but not for the faint of heart. The wiring is easy to connect, to be sure, Japanese are outstanding at that. Totally worth the money. I just wish I could put in one of the facto…

Having done this recently, the pro tip is that you can pop out the old USB/SD panel by inserting a hook pick into the holes on the front and yanking. It will pop the plastic faceplate off, and then you can access the clips to remove the entire unit. Mine was actually fine and I was able to pop the faceplate back on if I wanted to reuse it (not sure why I would), but no guarantee. Turned it into a 15 minute job vs pro…

Very much depends on the model, trim level, and generation. Even on the Mazda 3, the location of the USB hub depends on whether the car has a CD player.

I did the "drill holes in the front of the USB hub" trick so I didn't have to remove the console. But then I dropped a socket and ended up having to remove the console to retrieve it and it only took maybe 15 minutes. I could do it again in 5 knowing all the steps.

Re: Apple's risky bet on CarPlay

#525

Post by lostmsu »

dboreham wrote: post #99
StephenSmith wrote: post #12

If you're in the market for a new-to-you car, then I recommend looking at the model years where they switch from wired car-play to wireless car-play and buying the previous model-year. Typically this difference of one model-year can add thousands to the cost of the vehicle, especially because wireless car-play is so coveted. The experience of wireless is fantastic, but is it worth several thousand dollars? Maybe, but…

In my experience wireless car play is a nothingburger -- you end up plugging in your phone to charge it anyway. If it's not plugged in, the wireless interaction draws so much power that you need to plug it in. Stable configuration is therefore: plugged in. (yes you can sometimes have the combination of wireless CP and wireless charging, but wireless charging also sucks).

I almost never plug my phone in the car, and I have wireless android auto dongle. Might be an iPhone issue.

Re: Apple's risky bet on CarPlay

#526

Post by hsbauauvhabzb »

jacooper wrote: post #508
hsbauauvhabzb wrote: post #350

Two things scare me about Android / Apple car integration - I’d be interested in experiences others have had: Obsolescence - ‘your phone is too old to use with this car’ or your car being too old for your phone. Double points for software updates to either which disable functions or features. Vendor lock-in - are the players mutually exclusive? Does having a phone from one manufacturer limit my car choices?

> Vendor lock-in - are the players mutually exclusive? Does having a phone from one manufacturer limit my car choices? Realistically it's going to be the other way around

That’s semantically irrelevant, and potentially incorrect depending on context. 0/10.

Re: Apple's risky bet on CarPlay

#527

Post by roydivision »

wodenokoto wrote: post #371
roydivision wrote: post #370

All I look for is a USB connection to the simple stereo, plug my phone in and mount it on the dash. I fail to see why I have to deal with the additional cognitive load of an other interface that WILL go wrong when I already have a perfectly good one in my pocket. (No, I don't even want Bluetooth, ugh).

I also prefer this, but I find that lots of cars for some reason end up with weird volume levels for turn-by-turn compared to the music. Have you found a bullet proof way of adjusting this?

Interesting, no, I don't have this, luckily. I do have a weird thing that Siri speaks through the phone's speaker not the car's speakers, even when I'm playing music through the car's speakers over USB. This would probably be fixed if I used Bluetooth for the audio, but that's a whole level of pain I'd rather avoid.

Re: Apple's risky bet on CarPlay

#528

Post by fennecbutt »

withinboredom wrote: post #421
lupusreal wrote: post #414

Earlier quoted context omitted.

Sensor fusion is AI I guess.

AI can be distilled down to a series of if-statements. That's basically all it is.

This is true of literally any software and if you really wanna oversimplify it, our brains are just a bunch of if statements (condition based logic) too...

Re: Apple's risky bet on CarPlay

#529

Post by withinboredom »

fennecbutt wrote: post #528
withinboredom wrote: post #421

Earlier quoted context omitted.

AI can be distilled down to a series of if-statements. That's basically all it is.

This is true of literally any software and if you really wanna oversimplify it, our brains are just a bunch of if statements (condition based logic) too...

I noticed too late to add /s or to attribute the quote, but kinda sad that people are taking it literally.

It’s a play on the quote “Life is a series of choices and reactions” from “Before The Fall”

Re: Apple's risky bet on CarPlay

#530

Post by joshstrange »

zbentley wrote: post #509
dagmx wrote: post #178

Earlier quoted context omitted.

The author is talking about Android Automotive which is different than Android Auto. Auto is driven from your phone whereas Automotive is running on your car directly.

> Android Automotive which is different than Android Auto I know this isn't the highest value comment in the world, but god Google's product naming/differentiation is terrible. I can't imagine a more guaranteed-to-confuse (or worse, more guaranteed to lead to misleading second-party marketing) nomenclature.

It couldn’t be simpler.

Android Automotive (AA) is obviously different from Android Auto (AA). You see, AA runs on the car and runs the infotainment system whereas AA is just screen mirroring for Android phones. AA supports CarPlay just like it supports AA. Apple doesn’t have anything like AA, CarPlay is equivalent to AA.

Lastly, it’s not like “Auto” is short for another word such that people would mistake the two. It’s clear as day.

/s

Post reply on HN