Re:David C. At this time I rarely use CarPlay around town but only for longer distance driving or driving during commute hours so I can be aware of congestion and find detours. When I works it works great. The issue is getting it to initially work. That said when I first purchased the car Acura support was outstanding. Now it is essentially garbage.
I hadn’t heard about these new features, but presumably they require hardware that’s not present in existing cars. I don’t blame Apple for this – at some point they’ll want to add features that aren’t possible with existing hardware. CarPlay is almost a decade old, and the current version runs on the first car that ever supported it. It doesn’t feel to me that Apple considers the car an accessory they expect you to upgrade every time there’s a new version of CarPlay.
(As a side note, do you know what these new and advanced features are that require a new vehicle?)
As far as the issues with your car, they do sound like a real pain, and would severely dent the attractiveness of CarPlay for me if I had them. From the description it sounds more like a problem with the car rather than CarPlay, but that’s not much comfort (and disappointing that Honda support aren’t taking it seriously). All I can say is whenever I use a car it’s a car club or rental, so I’ve used dozens of makes and models with CarPlay, and it’s worked reliably in all of them. Not to diminish how real the issue is for you, but to suggest that it might not be widespread amongst cars generally.
The OP might be referring to the 2.0 version of CarPlay which would more or less take over the whole dash:
I would think that GM as well as some other brands are not going to let that happen but maybe some will still provide the current CarPlay functions.
Thank you for your understanding. I feel you are partially correct. I believe it is a combination of issues. One is most certainly the vehicle when I comes to connectivity as demonstrated that when I reset the vehicle technology CarPlay reconnects. But the other issue is CarPlay itself on the phone as the lack of consistent operation when setting destinations with CarPlay and transmitting that information to the vehicle display via the chosen map app. Sometimes it works and sometimes it does not. When it does not, notifications are supposed to be present on the phone. Some times they are and sometimes they are not or are significantly delayed when they finally do. Additionally the location of the notification varies as sometimes they appear in the phone notification screen and sometimes in the map app. This seems to be totally inconsistent. When I add Alex Car Echo to the mix which involves the Alexa app, they sometimes appear in the Alexa app and nowhere else. So when the information is not properly transmitted to the vehicle display it becomes the game of hide and seek as to where the notification is so you can click on it to migrate the information to the vehicle display - i.e. severe distracted driving.
You are correct about Car Play 2.0. this is the upgrade that requires you to purchase a new luxury level vehicle to use it of which less than a handful of vehicles currently support it.
First of all I do not believe it is “an evil plot” but a strategy to maximize profits and income for senior executives and dividends for shareholders of which I am one of them. I have not heard of such profit gains being shared among the run of the mill employees. As for a warning I was an Apple employee starting in 1982 and still have an employee number assigned to me under 5000. I owned my first Apple computer, an Apple //e, starting around 1980 where I received it as a prize at the IEEE trade show, WESCON, for being the 1 millionth visitor. This was before Lisa, and Macintosh and Windows. At that time the only competitor OS for individual users was DOS and the Microsoft infant was making hardware, a Z80 card that plugged into the Apple // to run DOS. I purchased that card for my machine directly from Bill Gates himself at an AppleFest convention. As such the contention that “I was warned” I feel is totally incorrect. Additionally what seems to be often forgotten is that Apple only currently exists due to Bill Gates generosity. In those days Apple was on the verge of bankruptcy. It was Bill Gates that gave Steve Jobs the loan that allowed Apple to continue to exist.
This is not correct - nothing is ‘required’. As has been stated earlier, it is highly unlikely Apple would stop support of CarPlay 1 - in the same way it doesn’t halt support for older machines when it updates MacOS. They continue to run happily on the older systems. This is the same as phones, cameras, fridges or any other tech - no-one is ‘forced’ to buy anything new.
Your opinion on GM’s move is valued but you seem to be fabricating arguments about Apple with little foundation.
This is exactly my argument for why CarPlay is so good - I get absolute consistency when moving between my 4 cars. I don’t have to learn each cars foibles, copy anything over or log into anything on the vehicle. I plug in the phone, play my music, read and respond to messages, make calls and navigate to my destination.
I’m sorry your car doesn’t play well with CarPlay, but until you confirm it’s Apple’s fault it’s a moot point. I’m not suggesting CarPlay is perfect, but saying it should be removed from an entire range of vehicles because of your experience isn’t a reasonable conclusion to draw.
Zero vehicles currently support it - Apple hasn’t released it yet. They are announcing the first cars that will support it later this year. iOS - CarPlay - Apple
As others have said, the current CarPlay will continue to work and be supported after 2.0 is released.
1 Like
According to what I read when the announcement came out there were less than a half dozen vehicles that were designed to support it. One of the brands was BMW but I honestly do not remember what other brands were listed. It was also my understanding that it was to be included in the next major release of IOS which given the time span is the current version. However I have no way of confirming that and that given other comments on the subject it may have been delayed. One thing that was made clear some time after was that other than the listed brands and new models at the time, which was late 2022, all other vehicles that were currently in or had ceased production will not support the update but will be stuck with the older or seemingly current version. So in order to utilize the upgrade users will need to purchase a new vehicle of the ones listed or perhaps a later brand and model that is configured to support the upgrade.
The basic issue here is that while in seems as though, from the comments, that it may work properly in some vehicles, but there are vehicles that it does not properly work. This is a matter of safety. I am of the opinion that the CarPlay should be recalled until either it works properly in all vehicles that are designed to support it, or that it should include code to disable it in vehicles in which it does not function properly or reliably. Distracted driving is a prescription for collisions, injury and death. Such unreliable operation is not allowed in aircraft and it should not be allowed in motor vehicles.
What vehicles will support CarPlay 2.0 isn’t decided by Apple. It’s decided by the automakers. Apple tells them what the hardware requirements will be, and the automakers decide whether they want to include them in their vehicles.
Yes, it’s going to initially appear in only high-end vehicles. That how virtually all new features appear in cars: the top-tier models, the luxury lines, get the cool stuff first. Then, if it proves popular, it works its way down to lower models. That’s how CarPlay 1.0 was initially, too. Good or bad, that’s how automakers do things.
But here’s the thing that bothers me about your arguments here: you are acting as though CarPlay 2.0 being initially available in only high-end vehicles is taking something away from you. It’s not. Your existing use of CarPlay will not be affected at all by the release of CarPlay 2.0 if you don’t have a vehicle that supports it. Existing CarPlay features will continue to work the same as they always have. Apple is not dropping support for CarPlay 1.0, nor are any automakers other than GM—and even GM isn’t removing it from vehicles that already have it; they’re just not going to include it in future vehicles.
Of course it would be great if all cars from all manufacturers added all the latest and greatest features right away. If automakers thought it would be in their best interests, they’d offer upgrades all the way down the line. But they don’t think that way. This is not Apple’s fault.
Maybe it’s time to wind this down. It feels like we’re going in circles.
2 Likes
That’s akin to saying Apple shouldn’t be able to sell computers whilst Adobe InDesign has bugs. Neither you or I can definitively say whether Apple or the vehicle makers are at fault but if you believe GM (or any other car maker) is going to be better at software/hardware integration than Apple I think you need to reconsider your position.
1 Like
On one hand you are correct. Tech advances. But on the other hand what this implies, is that Apple has sun setted CarPlay 1.0 and that it seems unlikely that existing bugs will be addressed and fixed. What I believe should have been done was to release CarPlay 2.0 with unsupported features disabled for older vehicles and the bugs or issues being addressed and fixed. So the lucky users that have it working properly will have no issue with continuing with 1.0 until they are ready to purchase a new vehicle because they either want one or the maintenance costs and age of their older vehicle dictates it is time to purchase a new one, and not because Apple has decided to consider their vehicle as an iPhone accessory and in order to get a working properly they need to purchase a new vehicle.
That said I plan to file a formal complaint with the NHTSA requesting that they issue a recall order to recall and disable Apple CarPlay 1.0 until they can provide evidence that it works properly in all vehicles designed to use it or that it be modified to exclude its use on vehicles on which it does not reliably function. This is not a vendetta against Apple but an interest is vehicle safety. When Apple CarPlay fails to work reliably in a vehicle it can result in significant driver distraction with a significant statistical outcome of damage injury or death, not only to the drive and their passengers but to innocent victims of other involved vehicles or pedestrians.
Just ask your self: How would you feel if if a friend, family or other loved one was run over, injured or killed, where the cause of the collision was determined to be the result of driver distraction due to the driver fumbling with a flaky CarPlay when attempting to get directions to a destination?
You’re talking as though 2.0 has already been released. It hasn’t been yet.
There are two devices that need to support a feature in CarPlay 2.0 for it to be available: the phone and the car. If either one doesn’t support it, then it won’t be available. This is how all hardware-dependent features currently work on Apple devices.
Vehicles not equipped with the CarPlay 2.0 software will continue to operate under CarPlay 1.0. Phones not able to run the necessary iOS version to support CarPlay 2.0 will continue to operate using the CarPlay 1.0 feature set.
I don’t understand why you think it won’t work exactly this way. If CarPlay 1.0 works just fine for you, and you’re not buying a vehicle equipped with CarPlay 2.0, nothing changes for you.
Do you realize how absurd this sounds? You are essentially arguing that, because it doesn’t work perfectly in some vehicles, it shouldn’t be allowed to be used in vehicles in which it works without issue. That’s not how safety recalls work. Only vehicles in which issues are identified as occurring get recalled. I’m not sure the NHTSA even has the authority to issue a recall over third-party software.
The same as I’d feel if it happened because of any of the ten million other potential distractions available to drivers. It is the driver’s responsibility to focus on driving. A navigation system is not a safety feature; it is a bonus, an add-on, a convenience. If you need to fumble with the nav system, you should pull off the road or let a passenger do it. If you don’t, and you cause an accident, neither the automaker nor the company that produced the nav system is liable: you are. Because, again, a navigation system is a nonessential feature.
Look, I get that you are frustrated with your experiences with CarPlay. I sympathize. I really do. But your assertions and expected remedies are veering away from reason and moving towards yelling at clouds. You’re arguing that a mid-level inconvenience is a ticking bomb.
If CarPlay doesn’t work for you, you don’t have to use it. You can get almost the same experience by adding a mount for your iPhone and plugging the audio into an aux input. It’s just on your phone screen instead of on the car’s screen. Yes, it’s a little less convenient. Yes, it’s less elegant. But it’s not an unreasonable option.
What is unreasonable is insisting that no one should be able to use CarPlay unless it works perfectly for everyone all the time.
I’m done with this thread. Multiple people have pointed out to you where your assertions are inaccurate or based on misconceptions, and you keep returning with the same arguments and assertions. This discussion no longer seems to be serving any useful purpose or creating any value for anyone.
3 Likes
CarPlay 2.0 hasn’t been released yet and this is exactly what I would expect to see.
1 Like
I’m not sure whether to respond as I think you could now be trolling. This is clearly a nonsense. Driver distractions are a fact of life. Do we ban kids from being in a car because they might distract the driver. Do we ban radios, CDs, windscreen wipers, smoking, NAVMANs, cruise-control?
Have you filed a complaint against Tesla because their self-driving vehicles actually do crash and kill people?
I suspect safety is the precise reason the much-discussed Apple Car is so long coming. They want to get it right. I’m guessing when you and Apple parted ways it wasn’t amicable. You sure seem to have it in for them.
I agree with whoever said this discussion should be closed. I’m a pretty chill kind of guy but some of the discussions are driving me to distraction (pardon the pun).
You probably don’t even have to do that. In my car with CarPlay it still supports playing Bluetooth or USB audio using the stock, non-CarPlay audio system (the same you use to play AM, FM, or SiriusXM radio.) It also has a stock navigation system.
2 Likes
Alright, I’m shutting this topic down. There’s no question that CarPlay is not perfect, but no technology is, and anything that requires coordination between a third-party manufacturer and Apple’s code will have even more room for problems to crop up. But CarPlay is something that a lot of people appreciate greatly.
What’s being described here as “CarPlay 2.0” exists only as a technology demo from WWDC 2022, when Apple said that cars supporting it wouldn’t even start appearing on the market until the end of this year. Given how long it took CarPlay to gain widespread adoption among car manufacturers, I wouldn’t expect to see it in mainstream vehicles for another year or two at best. And that if it ever shows up, given that manufacturers are clearly leery of giving Apple too much control. Regardless, existing versions of CarPlay won’t stop working then, though current cars likely won’t be able to upgrade to the next-generation version because they’ll lack the necessary hardware. As others have said, this is standard practice.
3 Likes