Newsroom Update

Tap to Pay on iPhone is now available in Canada. Learn more >

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Crackle and Pop using CarPlay

I am having an issue with audio quality when using CarPlay. This issue affects playback using both iTunes and the Podcast app. Every 3 - 15 minutes the audio will skip for about half a second and very often, but not always, comes back highly distorted with crackling and popping. Very occasionally it will skip and not experience an audio drop.


The only work around I have found is to either turn off the car and restart it, or unplug the phone from the USB and re-plug it. This works until the next skip, which are occurring more frequently in recent days.


Switching to a different podcast or album results in a clean signal until another skip occurs. Switching from an affected podcast or album to a clean one, then back again, does not fix the issue. Once corrupted the audio remains corrupted until the phone is disconnected then reconnected.


I have tried the following with no success -

  • Rebooting the phone
  • Using a new lightning cable

iPhone 6s, iOS 11.3

Posted on Apr 24, 2018 10:04 AM

Reply
207 replies

Aug 9, 2018 2:16 PM in response to Nahaz

Took my Hyundai Tucson 2018 Active x model

Into Hyundai to get its first service. Told them about the popping sound on car play. Got told that there definately is an issue but that Apple is in the process of bringing out an update for this issue. They said it’s nothing to do with the Hyundai itself. I was expecting this answer to be honest.

Aug 9, 2018 9:15 PM in response to SM-CO

Did Apple seriously just censor a bunch of posts then regarding if the iOS 12 beta fixes this issue? If so I would find that very disappointing and actually indirect violation of their own Apple Beta Software Program Agreement which states publicly available information is not considered confidential!


Considered and referred to in this Agreement as “

Confidential Information.” Information that otherwise would be deemed Confidential Information but (a) is generally and legitimately available to the public through no fault or breach of yours, (b) is generally made available to the public by Apple, (c) is independently developed by you without the use of any Confidential Information, (d) was rightfully obtained from a third party who had the right to transfer or disclose it to you without limitation, or (e) any third party software and/or documentation provided to you by Apple and accompanied by licensing terms that do not impose confidentiality obligations on the use or disclosure of such software and/or documentation will not be considered Confidential Information under this Agreement

Aug 9, 2018 9:48 PM in response to babowa

Apple and their representatives (Apple Care, direct employees) have made numerous statements, often in writing, about this bug and ongoing efforts to remedy it. This information has been disclosed by “no fault of my own” and is “publicly available” Therefore the discussion of this bug and possibly remedies are not a a breach of confidentiality.


I’m absolutely disgusted that anyone would report the discussion of a remedy or bug fix in a beta version of its OS, and Futher disgusted that Apple would take action and delete posts.

Aug 9, 2018 10:45 PM in response to Nahaz

You are giving me way too much credit. None of the users here - myself included - have any power to "ban" or "unban" anyone.


Neither can anyone other than the hosts (Apple employees) remove any posts and their email should include an explanation (at least the ones I have received all did and yes, I've had posts removed). They do have a rule about not discussing anything related to someone running a beta version of a Mac OS or iOS and do remove such discussions. Obviously, you can discuss any problems as long as you are running a publicly released version. It actually all makes sense: if you are running a beta, all bets are off (so to speak) because the behavior of your device may be odd/glitchy/different than running a regular OS; so, unless I'm also running a beta, I would not be able to help you because I wouldn't be able to recreate your problem on my device.

Aug 9, 2018 11:47 PM in response to babowa

babowa wrote:


You are giving me way too much credit. None of the users here - myself included - have any power to "ban" or "unban" anyone.


Neither can anyone other than the hosts (Apple employees) remove any posts and their email should include an explanation (at least the ones I have received all did and yes, I've had posts removed).

Well I had no such notice or warning. I tried to log into the discussion and it said I was unauthorised. Last post I saw was yours with the warning about talking about beta software and NDA, which is why I assumed it was you.


Now here's the problem for us and Apple. I will try and word it so I don't upset the powers at be.


1. We are/were all running released versions of Apple iOS with Apple Carplay

2. The problem with Carplay reportedly didn't exist until Apple released iOS 11.3 (Someone can correct me if I am wrong)

3. Several users have allegedly had their speakers, head units and firmware replaced. Some have had ground isolation units installed. All of this has made no difference to the fault.

4. Cartronics have allegedly said the problem is not with their hardware but rather with Apple's iOS. Some users can report that this appears to be the case because the problem only started for them when they did a upgrade of their phone's software.

5. Some users have allegedly reported that a future iOS version fixes this problem and some of us wanted to verify if this is the case. The only way for them to report on success or not is to download, install and then report back to the discussion group if the software update resolves the issue.

6. If the users are allegedly being banned from this group for reporting back their findings, then how are we suppose to know if the issue has been resolved?


Now a car is probably the 2nd biggest expense you will make apart from owning your own home. I would think more importance would be assigned to this problem to help resolve this issue that is happening to Apple phone users.


Fingers crossed come September, iOS 12 fixes this problem once and for all as I will also be in the market for a new iPhone.




Regards

Aug 10, 2018 8:20 AM in response to Nahaz

5. Some users have allegedly reported that a future iOS version fixes this problem and some of us wanted to verify if this is the case. The only way for them to report on success or not is to download, install and then report back to the discussion group if the software update resolves the issue.


6. . If the users are allegedly being banned from this group for reporting back their findings, then how are we suppose to know if the issue has been resolved?


That's easy: You will know/find out after the new iOS is publicly released and everyone can share their experiences. That is how Apple wants it.


Now a car is probably the 2nd biggest expense you will make apart from owning your own home. I would think more importance would be assigned to this problem to help resolve this issue that is happening to Apple phone users.


These are user to user forums, so neither Apple support personnel nor Apple Engineers generally read the thousands of daily posts here - discussing it here just results in "me too" responses which will not be very helpful.


Instead, anyone in a beta program should use the built in feedback assistant app and everyone else should use the feedback mechanism and/or contact Apple support about the issues they are having.

Aug 14, 2018 9:33 PM in response to bjorn.b

Apple why don't you just delete the whole thread and pretend this issue doesn't exist? I'm sick of having my posts deleted! I've been watching what the community moderators are deleting and the posts do not even MENTION iOS B*tas and thats the justification you're using to censor posts.


The b*ta is freely available. Regardless no one wants to discuss the b*ta, people just want to know if a bug from iOS 11 is fixed!!!! We don't CARE ABOUT the freely available public b*ta made available PUBLICLY by Apple!

And just to restore my previous post I said I'm about to throw my iPhone out the window and buy a pixel. I won't be CENSORED. Way to treat paying customers and someone who is just trying to help and avoid people installing a B*TA who doesn't need to install it just out of the hope it would fix a bug from iOS 11!


Apple CarPlay audio distortion iOS 11.3 to present - Hyundai & others using 'CARTRONICS' - YouTube

Aug 14, 2018 11:59 PM in response to bjorn.b

This thread keeps getting pieces cut from it and I keep getting an "Unauthorised" message every time it happens. What is going on?


I took my car in for a service. The verbal response from the Hyundai Technician was that this is an Apple Firmware issue. Cartronics are not interested in doing anything at this stage because if they do manage to fix/find the bug, Apple could quite easily break it with another iOS update. CarPlay is Apple's issue and they need to fix it.


I can opt out of my current phone contract in September and get a new phone. I am seriously thinking of dumping my iPad and iPhone X for a Galaxy Note 9 and a Microsoft Surface Pro.


While I like the idea of Apple having complete control over their products, this is one case where it's hurting the user especially when we spend over 101 minutes per day driving cars and listening to music etc.

Aug 15, 2018 2:52 PM in response to Miller_Lite_87

They are all violating their non-disclosure agreement. The only “legal” news are things Apple has made public. Personally, I do not understand the logic used here, but the rules are the rules. I would also never enroll in anything if I did not have any kind of support available. But, again, that is how Apple has decided it should be: no support, just report problems via the feedback assistant. There are the developers who have forums, but you need to establish an account there and there is an invitation-only program which also offers a forum. But there is nothing for the public beta.

Aug 15, 2018 10:24 PM in response to Schmidlapp84

Schmidlapp84 wrote:


I’ve escalated to Apple support today as well. They found this thread and will pass on the urgency of the problem to ”RTA alerts”. It’s about all we can do.


Thanks Schmidlapp84.


I've also contacted Cartronics (www.cartronics.net.au) if you live in Australia. Not sure if there is a US version of the site.

A woman by the name of Shelley got back to me. Here is her response.


"Hi 😃 Thanks for contacting us today. This is a worldwide Apple issue, with software versions iOS 11.3 or greater. Please refer to the Apple forums for more information. Let me know if there is anything else I can help you with."


I wish I knew where this MORE information was. From their response It appears Cartronics are pointing the finger clearly at Apple.

Crackle and Pop using CarPlay

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.