Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I'm chatting now with an apple tech about this problem. Its not going well....

Usually doesn't especially since the people manning the chats are just customer service reps who don't have any actual technical training (sorry to burst their bubble but Apple's "Genius 101 University" 2 week class isn't technical training.

But hey, hopefully the bug reports actually get looked at. Surely Tim Cook must want to be able to use his phone in the car.
 
Same problem in my Aston Martin rapide s. New car this April. No issues with iPhone 5s with the 6 it connects, it's syncs the contacts but won't interrupt car audio for calls!!
 
Usually doesn't especially since the people manning the chats are just customer service reps who don't have any actual technical training (sorry to burst their bubble but Apple's "Genius 101 University" 2 week class isn't technical training.

But hey, hopefully the bug reports actually get looked at. Surely Tim Cook must want to be able to use his phone in the car.

In case anyone was wondering:

I certainly understand your frustration. Restoring from the backup could reinstall the software glitch that is causing the issue to begin with. We recommend manually resyncing all of your content back onto the unit to avoid that.

Me:Manually resync? Sounds very complicated. I've never done that before. Is a fix in the works, because I'd rather just wait for that I think.

AprilThe restore helps the device to be able to make calls via bluetooth. We can certainly try it to see if it will help with your issue as well.

AprilThe best thing to do is submit feedback directly to Apple via the apple.com/feedback website. This will make them aware of the issue. Our case notes are also taken into account for any upcoming updates.
 
In case anyone was wondering:

I certainly understand your frustration. Restoring from the backup could reinstall the software glitch that is causing the issue to begin with. We recommend manually resyncing all of your content back onto the unit to avoid that.

Me:Manually resync? Sounds very complicated. I've never done that before. Is a fix in the works, because I'd rather just wait for that I think.

AprilThe restore helps the device to be able to make calls via bluetooth. We can certainly try it to see if it will help with your issue as well.

AprilThe best thing to do is submit feedback directly to Apple via the apple.com/feedback website. This will make them aware of the issue. Our case notes are also taken into account for any upcoming updates.

Case in point about my comment regarding the customer service agent on the other line of the chat. LOL
 
Settings > General > Reset > Reset Network Settings

Which will reset Wi-fi and Bluetooth settings.


Now please realize that the these manufacturers can do weird things with paired devices that may not be the fault of iOS 8, such as restricting what functions are available to unrecognized/unapproved devices or not allowing them to pair at all. This would require an update on the radio to fix. Apple could have screwed something up as well or both of them.

I personally haven't seen issues with my vehicle (not a Hyundai) and iOS 8 on a 5S or 6+.
 
Settings > General > Reset > Reset Network Settings

Which will reset Wi-fi and Bluetooth settings.


Now please realize that the these manufacturers can do weird things with paired devices that may not be the fault of iOS 8, such as restricting what functions are available to unrecognized/unapproved devices or not allowing them to pair at all. This would require an update on the radio to fix. Apple could have screwed something up as well or both of them.

I personally haven't seen issues with my vehicle (not a Hyundai) and iOS 8 on a 5S or 6+.

given that people with Hyundai, Aston Martin, BMW, Lexus, and Toyota have reported issues, it seems the only commonality is Apple. I tried it with a stock 6 and it definitely does the same thing. A restore or network reset won't do anything.
 
Hi

You can Range Rover to the list. Just been outside to try and exactly the same issue!

Use my hands free a fair amount and this sucks
 
given that people with Hyundai, Aston Martin, BMW, Lexus, and Toyota have reported issues, it seems the only commonality is Apple. I tried it with a stock 6 and it definitely does the same thing. A restore or network reset won't do anything.

They could share the same OEM radio manufacturer as well. The OEM for mine is Fujitsu-Ten.

Try changing the name of your phone then: Settings > General > About > Name

Remove any special characters and just make it plain text. May even want to remove spaces.

Quotes (single or double) or other special characters may not be getting passed through correctly during the handshake and may be causing an error if it is not getting parsed out correctly. Apple or the OEM could be looking for specific device strings that are no longer being recognized to make these exceptions.
 
They could share the same OEM radio manufacturer as well. The OEM for mine is Fujitsu-Ten.

Try changing the name of your phone then: Settings > General > About > Name

Remove any special characters and just make it plain text. May even want to remove spaces.

Quotes (single or double) or other special characters may not be getting passed through correctly during the handshake and may be causing an error if it is not getting parsed out correctly. Apple or the OEM could be looking for specific device strings that are no longer being recognized to make these exceptions.

If someone pulls it out of the box brand new, and it doesn't work out of the box, there's an issue with Apple, not the setup of the phone nor the car.
 
If someone pulls it out of the box brand new, and it doesn't work out of the box, there's an issue with Apple, not the setup of the phone nor the car.

By that logic, it must be your car. It worked for me right out of the box, right?

I am just offering suggestions of what "might" get it working based on years of seeing what happens when programmers might be hard-coding device strings, looking for specific manufacturers and deviating from standards, etc.

Technology is not that simple, unfortunately. One slight deviation from any side can cause disruptions in how things "should" work. Otherwise, if everything were perfect, Hyundai wouldn't provide compatibility charts with special notes for multiple phone manufacturers even though they're "all" supposed to be using the same standards:

www.hyundaiusa.com/BlueTooth/
 
By that logic, it must be your car. It worked for me right out of the box, right?

I am just offering suggestions of what "might" get it working based on years of seeing what happens when programmers might be hard-coding device strings, looking for specific manufacturers and deviating from standards, etc.

Technology is not that simple, unfortunately. One slight deviation from any side can cause disruptions in how things "should" work. Otherwise, if everything were perfect, Hyundai wouldn't provide compatibility charts with special notes for multiple phone manufacturers even though they're "all" supposed to be using the same standards:

www.hyundaiusa.com/BlueTooth/

I can't believe you're defending Apple on this one. It's hard to take anything you say seriously when you take that position.
 
Just speaking for myself and my KIA. After installing 8.0.2 my issue has gone away. Hopefully everyone else is resolved shortly.
 
I can't believe you're defending Apple on this one. It's hard to take anything you say seriously when you take that position.

I'm not defending or accusing. Without seeing the underlying coding from either party, I can't condemn anyone. I offered possible workarounds until "some party" potentially fixes the underlying issue.

I've seen programmers make coding decisions or assumptions that wind up mishandling things when devices involved are updated because those assumptions/decisions no longer apply to that specific version of software or new device. From a technology perspective these programming mistakes can happen with any device involved, and in this case be the radio or the phone.

I see it all of the time with other things that follow "standards" and sometimes you have to try workarounds in the meantime.
 
I'm not defending or accusing. Without seeing the underlying coding from either party, I can't condemn anyone. I offered possible workarounds until "some party" potentially fixes the underlying issue.

I've seen programmers make coding decisions or assumptions that wind up mishandling things when devices involved are updated because those assumptions/decisions no longer apply to that specific version of software or new device. From a technology perspective these programming mistakes can happen with any device involved, and in this case be the radio or the phone.

I see it all of the time with other things that follow "standards" and sometimes you have to try workarounds in the meantime.

If Hyundai was broke, sure, it's clearly something between Hyundai and Apple. That's not the case. A dozen or so brands now won't work with whatever Apple changed in the current iOS version. If the device was compliant with BT standard spec, this wouldn't happen. If it happens to one person, it's a one-off. If it happens to most, it's an issue. If you want to defend Apple's position, so be it. You have a right to... but when many versions of iOS have worked with almost all cars, and they release an update and the bluetooth can't place a call in most cars, that's a big issue, and has zero to do with the car maker.

Addon- It's not new technology... bluetooth is a technology that's not rocket science. It upsets me reading your defense of Apple on this one. This is why issues don't get resolved, because people like you blame things outside of Apple. The car company didn't change their software. The phone maker did. To suggest that you buy a phone that's compatible with a spec then becomes unable to connect with that spec you paid to be compatible with is laughable. Stop making excuses. We pay a lot of money to have phones that work with the spec they're designed to work with. Clearly the iPhone 6 claims they work with Bluetooth... my cars have bluetooth. I didn't get what I paid for. All of my other devices work fine with my car, except those on iOS 8.
 
I can't believe you're defending Apple on this one. It's hard to take anything you say seriously when you take that position.

Ohhh I can! I have owned every iPhone since day one. I am as Apple fan boyish as you can get. However, I was always a fanboy for the simple fact that I found time and again their stuff worked as intended, out of the box.

This OS release has *not* been like every other OS release. There have been fundamental issues, things that are broken on a scale I haven't seen before. Yet people still post to this forum insisting that this is like every other release, software has bugs, yada yada.

This release is a joke. Yeah, Apple is going to make piles of money, I get it (so whomever is about to respond with the tired "Apple made "X", so therefore the product must be great!" can stuff it). They sold these devices on the basis of what came before them though. This launch has been terrible. Just terrible. I have gone through two phones now, each with deal breaking issues. I'm now using an Android device as my daily driver cause it Just Works.

Android fans had it right when they said "Welcome to 2012" when Apple announced these phones. What they didn't realize was that they meant iOS 8 would like like a buggy 2012 Android device.
 
After pairing my iphone6 to my Chevy truck my phone wouldn't call out but incoming calls worked fine,rebooted phone and all is well.
 
My 2012 Acura TL will connect initially and sometimes drop the bluetooth connection. Bringing up the quick controls on the iphone (6 btw running 8.0.2) and toggling bluetooth off and on again seems to fix it. It is annoying though
 
Ohhh I can! I have owned every iPhone since day one. I am as Apple fan boyish as you can get. However, I was always a fanboy for the simple fact that I found time and again their stuff worked as intended, out of the box.

This OS release has *not* been like every other OS release. There have been fundamental issues, things that are broken on a scale I haven't seen before. Yet people still post to this forum insisting that this is like every other release, software has bugs, yada yada.

This release is a joke. Yeah, Apple is going to make piles of money, I get it (so whomever is about to respond with the tired "Apple made "X", so therefore the product must be great!" can stuff it). They sold these devices on the basis of what came before them though. This launch has been terrible. Just terrible. I have gone through two phones now, each with deal breaking issues. I'm now using an Android device as my daily driver cause it Just Works.

Android fans had it right when they said "Welcome to 2012" when Apple announced these phones. What they didn't realize was that they meant iOS 8 would like like a buggy 2012 Android device.

iOS 7.0 daily life was the worst for me, with constant re-springs. iOS 4.0 was the second worst due to ActiveSync issues causing Exchange issues and giving me a 100+ work week after it was released. My glasses are not rose-colored. iOS 8 issues have been minimal so far in my personal experiences. Could it be better? Yep.

I have had Android devices and my radio not get along very well (last one, a OnePlus One) and has been noted as being a general BT stack problem in most Android devices and my radio not getting along. Having to force pairing, track information not always working (or only works once and stops updating), auto play not always working, etc. iOS 7 & 8 and my current vehicle have been the opposite.

As previously stated... I have not been defending Apple, but offering possible workarounds to try to get things working. Bluetooth and other wireless technologies have way too many parts at play to be consistent across the board (different chipsets, software, drivers, etc) and don't always play nice together and the issues are not always as clear cut as you would like.
 
iOS 7.0 daily life was the worst for me, with constant re-springs. iOS 4.0 was the second worst due to ActiveSync issues causing Exchange issues and giving me a 100+ work week after it was released. My glasses are not rose-colored. iOS 8 issues have been minimal so far in my personal experiences. Could it be better? Yep.

I have had Android devices and my radio not get along very well (last one, a OnePlus One) and has been noted as being a general BT stack problem in most Android devices and my radio not getting along. Having to force pairing, track information not always working (or only works once and stops updating), auto play not always working, etc. iOS 7 & 8 and my current vehicle have been the opposite.

As previously stated... I have not been defending Apple, but offering possible workarounds to try to get things working. Bluetooth and other wireless technologies have way too many parts at play to be consistent across the board (different chipsets, software, drivers, etc) and don't always play nice together and the issues are not always as clear cut as you would like.

I get what you're doing, but you're not talking to someone with limited experience with devices. In the past two years, as a sample, I've owned virtually all the major handsets. *All* of them have connected to two different cars without issue. This is the first time I've had a problem. And you have to understand, *this* one issue is stacked on top of a myriad others I've experienced with three different handsets in the last week.

This is not a usual release. This has been a terrible upgrade.
 
I had the same problem today. I did general > reset > reset all settings and this worked for me.
This is the only thing that worked for my on my Ford Mytouch SYnc system.

It's been reported to have happened to a good number of people but when I did this it finally worked correctly.

The fact that this worked for many people would make me think there is some default value or something internal on the 6 and 6+ that makes it need a reset.

You will still keep your apps and all that but will need to re-enter some information (like touch ID fingerprints), etc...
 
So a quick update, and this may be for only those with a Hyundai like me, lol

So I was playing around with it. Like I said, it connected, synced, and downloaded the contacts just fine. However when the radio or satellite radio is playing, an incoming call doesn't interrupt the music, nor does an outgoing call placed (as it ALWAYS has with iPhone 5S on iOS 7 and every phone ever connected to it).

However, if I go into the audio settings, select "stream on connect" and then press the media button, it launches the music playing off the phone. I can then pause the music on the phone, and place\receive a call while in that mode. Caller ID doesn't pass through, nor does the fact that I'm on a call, but at least the audio comes through. This is not how the system was designed, it's merely a workaround that's half-baked until Apple comes up with a patch for the bluetooth they broke.

Hopefully their fix comes soon!

----------

Add Infiniti to the list of cars that have BT issues with iOS8.

I think there should be a list where it doesn't work, since now just about every brand has piped in saying it doesn't work now.
 
Add Ford too. No experience with Sync, but I have a (UK) 2012 Grand C-Max with Ford Audio and Bluetooth and iOS 8 beta 1-5 worked perfectly, GM, nada. Ford engineer has had the same experience with the Sync system, but a few resets and his is stable-ish. Their update site is dead and Ford have no idea when an update is coming, but they do know they lag massively behind.

They need this update pretty damn quick. Because I need Bluetooth in my car.

EDIT: Should explain what mine does. I can connect the two fine. But theres two major things I've noticed.
1) I can get my contacts loaded fine, can call anyone, however it displays a wrong number but calls the right number. Once the call is finished, the calling UI does not go away unless I press hangup. Then try to make another call and the radio locks up.
2) Connect the two together fine, but when the orange DSP (Something to do with how it processes audio, Digital Signal Processing I think its called, comes up when I activate handsfree, except in this case, I haven't touched handsfree) light comes on, the radio just instantly freezes until I turn Bluetooth off.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.