Yesterday I was happily cruising all day with IOS Public Beta 13.6 without a glitch. This morning my phone was updated to 13.1 Public Beta automatically and rendered CarPlay totally useless. Back to Bluetooth to listen to music

 

Wait - you were on 13.6 and "upgraded to 13.1?

 

OOPS I meant IOS 13 Public Beta 6.......

 

Clarification: First sentence I meant to say IOS 13 Public Beta 6

 

For sure IOS13 beta 1 breaks CarPlay in 2019 RDX. I posted this in the other thread also:

Now that 13.1 for is out for iOS public beta also, I would strongly recommend avoiding it for RDX owners...breaks it completely whereas the 13.0 previous beta is just fine. I had to restore last night after updating to the 13.1 developer beta yesterday, and was able to get back to the 13.0 public Beta release before they stuck 13.1 beta also on the public beta ring.

 

Well i mean.. you're using Beta software..

 

Sure I agree with that, and had no problems myself to downgrade to 13.0 beta afterwards. Just warning RDX customers that may be testing that 13.1 PUBLIC beta not only introduces some little bugs with CarPlay with our cars, it completely outright breaks it, which could be enough to change their decision to run any additional public betas or even try and stay on the current 13.0 beta they are on now.

 

Roger that. So the question is if it causes issues for other manufacturers as well or if it is another Acura thing.

EDIT: A quick review of the VW/Audi forums doesn't show any issues.

 

I can confirm that the latest firmware update for the infotainment system broke CarPlay for iOS 13.1. It's hardly usable. CarPlay worked fine with the previous infotainment firmware.

 

Going to try a couple resets to see if it clears up, if not I will use BT for music and have to use the shitty Acura Navigation if needed.......Nice to get your confirmation though and it is disheartening that it seems the Acura update is what broke it. I bet other manufactures CarPlay implementations did not crash after the 13.1 beta release. Does not bode well......:-(

 

it seems to be just may be the rdx, since my brothers 2019 acura ILX still worked ok with 13.1 beta.

 

I just turned off auto-update in the nick of time. Thanks!

Sitting fat and happy at iOS 13.0 public beta 6.

It is rumored that iOS 13 will go live Sept. 10.

 

Thanks for the heads up. I might remove the profile just in case.

 

Pretty sure it’s a Acura issue as even 13.1 beta works with 1.1.2 but once you update to 1.1.4 bang, it’s more or less useless as the touchpad becomes inoperative. iOS 13 .nn has been in developer hands and this means the Infotainment SW developers as well for awhile now and 2 fixes in the 1.1.4 release totally hosed the system is really strange. I am leaning to just throwing in the towel and replace the RDX soon. Was at a dealer yesterday and was told a BIG update is coming this fall., I would not hold my breath on that one as even if Acura does release something I have no confidence it will resolve the issues.

 

iOS releases are usually the Wednesday before the Friday the new phone is released. I would expect the release of iOS 13 to be Wednesday, 9/14

 

Good, It will be interesting to see the 13.1 official release and see what happens with D1.1.4........Less than 2 weeks away if your dates are right.

 

Also looking at the release notes for D1.1.4 the first 2 entries are the only NEW items in this release as the others are from prior updates. Graphics update is more than likely the culprit that broke the touchpad in the IOS 13.1/D1.1.4 combination.

1. NEW SOFTWARE VERSION D.1.1.4
   
   The new software contains the following enhancements and rare bug fixes.
   1. Clock displays incorrect time and/or time zone by one hour.
      
   2. Graphics update.

 

Just did a search and found this regarding the IOS 13 release:

1. The CarPlay changes will be available for any device with the updated iPhone software and do not require any updates to the car itself.

You can read the entire article and judge for yourself as I think lots of people are in denial......

https://www.caranddriver.com/news/a2...apple-carplay/

 

It is obvious that Acura borked CarPlay integration when they designed the system.

 

‘Here is a great video of IOS 13 in a Ford of all things, wish the RDX system worked like this. Copy and paste the following string in your web browser: https://www.google.com/url?sa=t&rct=...Q99UWR7myJ39ig

 

I don't have an iPhone, but my mother-in-law just bought a base Tucson and CarPlay there works very similarly. Within seconds, I was able to get the screen up, enter an address and get navigation going.

At this point, I have no clue why manufacturers still put in nav systems and I have no idea why/how Acura screwed up such a simple integration. In the big scheme of things, arPlay/AA is no different than BT - build the interface to a standard and you're home free.

 

But that's just the problem. Acura deliberately introduced a new input device that didn't have support, so the whole damn thing is jerry-rigged.

When Apple decides to "think different" they throw considerable CS talent at the problem and hammer it until they get it right. They probably drop a billion bucks on software development before breakfast. Acura, not so much.

 

Lets face it, Acura just has a bunch of boneheads in over their heads. If Fords, Chevys and others can make these systems work right out of the gate without any problems like we have had Acura is a huge disappointment. Think I will call Acura corporate tomorrow and give them a chance to take my RDX back and return all my money or I will take my chances with the class action suit or even maybe just dump the damn vehicle and never buy a Honda/Acura product ever again. They probably will not care as plenty of sheep around to purchase vehicles.

 

Latest IOS Beta 13 works in the Palisade with no issues.. Drove to Des Moines from Kansas City this last weekend using my son's phone and we tried just about every app we could and there were no freeze ups, delays or any other issue with Carplay. In fact, I think I like it more than Android Auto and might get myself an iPhone...

 

Since the dawn of software people have been installing beta systems and then feeling outraged and frustrated when it doesn’t work, despite warnings not to use it in regular production. If the production release of iOS 13 breaks CarPlay on my RDX I will join the angry chorus; if not I will just thank those who had the time and spirit of adventure to encounter and report on the problems in the beta.

 

Who will your angry chorus be towards, Acura or Apple? If CarPlay in iOS 13 works on every manufacturers' infotainment system except Acura's where will the finger point? The problem isn't Apple it is Acura's inept programmers.

 

that's why they called it Beta..

 

I had tried IOS 13.1 on my rdx and it was broke w freezing and glitches on D1.1.2 prior to the 1.1.4 update so I don’t think it’s acura’s update to 1.1.4 that killed it. Having said that the 13.1 beta did work with my brothers 2019 ilx so its still something with the rdx interface that is incompatible w iOS 13.1, whether you have 1.1.2 or 1.1.4 firmware on the rdx.

I think the public beta testers realize it’s beta but the scary thing is not knowing whether 13.0 or 13.1 will be released on sep 12 and whether this issue, which was only recently became an issue w 13.1, will be again fixed prior to release in just 2 weeks.

 

Not true. I trust Apples Software more so than any other. I worked in IT for 33 years at a prestigious University run Government Research Lab. Apple was a big part of our heterogenous network and computing infrastructure since 1984. We even switched 100's of users from Windows to Apple Systems with not a single person wanting to revert back. I can't even count on one hand major hardware failures in all those years. Sure, we had occasional software bugs etc but even then it was fixed in short order. I even ran developer beta SW that actually resolved issues so I can tell you that Apple releasing Public Beta's is going to be pretty up to snuff more so than developer beta releases.

As far as your analogy of the IOS 13 Beta breaking Acura's CarPlay implementation are suspect to say the least.....

Yes, I was running IOS 13.1 already with at least a useable system which still had some annoying issues with Acura D.1.1.2

Then I installed Acura version D.1.1.4

So how in the world can you, and you are not alone, say that Apple's SW broke Acura's CarPlay implementation?

Boggles my mind.

 

certainly appreciate your experience. I’m not so sure why you seemed so offended by my post. You can’t say it’s “not true” since you’re not here to see my car interface. But this was just my honest experience...I had multiple freezes and crashes when first connecting iOS 13.1 on D1.1.2, this was before the car notified me of the D1.1.4 update. I could care less who’s at fault, just would like it to work and I’m not upgrading to 13.1 until that is fixed. I am also an Apple user for a long time and generally trust their macs, iPad, iPhones more than any other windows/android hardware so not looking to be biased here also. Please try to be less offended next time when someone is just sharing their experience.

 

Yes, beta software can break things, but if it only breaks things on one specific platform (in this case RDX), then it probably isn't the fault of the beta version

 

I was not implying that 13.1 on D1.1.2 was perfect by all means. Still had numerous glitches but not as frequent and worse when I installed D1.1.4. I realize that different user interactions with the system can manifest various different outcomes but the fact remains that issues still exist and I wish it was fixed ASAP as well. Just frustrating that these issues we are still having today were already being reported when the newly designed 3rd Gen RDX was initially released and sold. Its been going on now for over a year.

Sorry to have been so harsh.

 

I agree with you generally speaking, I would have thought the same. It’s also unfortunate that both things were released at essentially the same time. Just based on my experience that day, I was trying to get somewhere and needed waze and had just been running iOS 13.1 CarPlay for the first time in the rdx. Noticed the hangs and crashes and was very frustrated and had to run waze while holding the phone in my hand. Only after that experience during the same drive did the update notification to 1.1.4 popped up on my car, and I thought what the heck, waze on CarPlay already stopped working May as well let the 1.1.4 update run while driving. It was a frustrating afternoon just as I was relying on CarPlay to navigate. Again, I generally agree with you, but with Acura having such a different touchpad interface, it’s possible that 13.1 simply broke the interface w the rdx software while with others it’s fine?

Also more importantly, going back to 13.0 beta (rolled back a few hours later that night) works perfectly with 1.1.4 on my rdx again, how can we explain that?

 

Dunno. I just think it's weird that a 13.1 beta came out when 13.0 should be going Golden Master for imminent release. People who watch such things seem to agree.

https://www.macworld.com/article/339...o-install.html

FWIW CarPlay seemed pretty stable under 13.0 public beta 6 and D1.1.2 but I haven't really used it enough with D1.1.4 to make an assessment.

But I have rarely or never had the kind of system collapses some RDX owners are reporting, under any previous combination of Acura and Apple software. This makes me wonder if there is a hardware QC problem.

Which is not to say I have been satisfied with the performance of the system, but I consider crashes and hung systems a more serious issue and I can empathize with those owners whose systems are that pathological.

 

Sure it’s all good, no worries. I agree the whole thing is very frustrating. W beta I would think there may be minor crashes or glitches, but with 13.1, the touch pad freezes and the CarPlay interface keeps booting it self without resolve until you unplug the phone. I couldn’t even start any apps before the thing froze and crashed. Thankfully 13.0 beta (beta 7 I think) has kept it working perfectly again, no crashes or glitches noted at all here on 1.1.4 on rdx. I’m just nervous that they’ll jump to this 13.1 release as official release with problems still in place. I have a spare iPhone se, that I’m probably going to try the next 13.1 beta or release whichever comes first and make sure that it’s working with rdx before putting that on my main driver iPhone XS Max. Fingers crossed!

 

Normally with Apple once the Beta designation is gone as with the IOS 13.1 release it has gone what's called Golden Master which means this is the one that's a candidate as the final pre-release version. Apple is highly confident at this point that most of the know bugs are are resolved. There could be more fixes before the drop dead date of the release but then it would be version IOS 13.2

Most 3d party companies developers start testing the apps or implementations during the beta cycles. Apparently Acura was absent from this process.The 1.1.4 update should have already been factory tested against the 13 betas months ago. It is really going to get interesting when IOS 13 is released the everyones devices.

As a side I was researching a replacement for the RDX as I am near the end and was looking at the KIA Telluride and noticed that even the 16K Kia Rio has CarPlay and Android Auto that works. I do like the size, spirited driving dynamics and design of the RDX so the 3row Telluride and Palisade are a no go for me.

 

I'm a bit confused about the betas. Is 13.1 a developer beta at this point, and some flavor of 13.0 is the public beta? Or has 13.1 moved to public beta?

 

Never mind. I see that 13.1 is public beta.

 

and still really broken

 

You mean the Acura Infotainment is still really broken........