bluetooth music issues after iOS6 update

Looking around the communities, it is obvious that this problem is common for every iPhone 4 owner who uses Bluetooth in their vehicles. Twenty pages here and forty-two in another forum. More and more in others. With, I dare say, hundreds of users having one common problem, you would think Apple would at least acknowledge it and tell us that they're working on it or tell us we're out of luck. The other common factor seems to be that we've all spent an ****** full of cash to put good quality stereo units in our cars. This being so we could take advantage of the advanced features of the units... LIKE BLUETOOTH. I'd like to say that I'm confident that Apple won't leave us all hanging on this issue...

This is just a guess, and it doesn't make it easier to swallow...

But it would not surprise me if the devices you are all trying to pair with iOS6 don't follow the protocol precisely. Some companies take shortcuts or simply don't care - and when a device (typically from Apple) is very strict with a protocol (this happens often with USB devices which even mis-identify themselves to the computer), they don't work together.

If this is something that is actually Apple's fault, I'm sure they'll find a way to patch it with an update (hopefully soon). If this is something that's due to those other manufacturers, it all depends on them updating firmware or software to more accurately work with the protocol. And... they don't have much reason to do so. The right thing would be to fix it, of course.

Hmmm Let's see if I have this right with some reference (read - "confusing") material... Wiki says -

"Mac OS X

Since version 10.2, Apple Inc.'s Mac OS X has contained an integrated Bluetooth stack.^[10] Included profiles are DUN,SPP,FAX,HID,HSP,SYNC,PAN,BPP and OBEX. Version 10.5 adds support for A2DP and AVRCP.

BlueMagic 3.0 is Open Interface's (now Qualcomm) highly portable embedded Bluetooth protocol stack which powers Apple's iPhone and Qualcomm-powered devices such as the Motorola RAZR. BlueMagic also ships in products by Logitech, Samsung, LG, Sharp, Sagem, and more. BlueMagic 3.0 was the first fully certified (all protocols and profiles) Bluetooth protocol stack at the 1.1 level."

Now that this has totally confused the pooch, it's time for the screwdriver. As it was explained earier, iOS 5 used Bluetooth protocol 10.3. 10.3 played with his Bluetooth radio pals with no problems. But along comes iOS 6. He's the new kid on the block and has a mean two day stubble. He's got BT protocol 10.4 and he has nary a care for the 10.3 playground gang. So they take their stuff and go home. They DO leave the line open for bare music streaming and phone call quality that are just on this side of dump. New kid 10-4 swaggers around with iPhone 5 and is the new BPOC (Big Protocol Of Cars). He works with vehicles like Manny, Moe & Jack. Since iPhone 5 is in the spotlight, iPhone 4 and BT 10.3 stand at the bus stop in the rain.

PLUS, in the meantime, we of the 10.3 protocol sit and wait while the Apple CEO apologizes for "Maps". Give me a doggone break! He actually tells users to run other map apps until they fix the Apple app! Give us a break!

We deserve better treatment and a fix for this glitch. At least an acknowledgement of the problem and that they're doing something about it. C'mon Apple!

More than one vendor's HDTV has shipped with bugs like that, unfortunately.

Whenever standards are involved, both "sides" program to them but, unfortunately, if one party gets it wrong the two won't interoperate.

I have gone back to using a USB cable... and now I have control over music playback from the car controls... its not elegant, we know wires are bad, but it's much safer than fooling with the phone while driving. If you ahve that option you should do it. Someday the powers that be will fix this either on the host or client side of the BT relationship. In the mean time we've all learned a lesson or two.

Also, I've been suitably chastized for mentioning the words which Apple found offensive. The previous post had not techincal content so they removed it. I can see that. Sorry Apple. I didn't mean to offend you. I was just surprised I hadn't heard anyone go there.

I just upgraded two of our iphones to IOS6. The stereo I just put into my car to operate the phone six weeks ago stopped functioning with the upgrade. I paid close to $500 for this Kenwood radio with new speakers and installation. Its the model KDC-BT852HD. It worked perfectly. It was safe to operate the phone while driving. I was very happy with the setup.

So after reading all available information on the internet it seems the issue revolves around any manufacture that uses something called parrot for bluetooth.

Whats worse is Apple at this point is the only one who could make this issue go away quickly and they are so far refusing to do so. All thats necessary is that they allow their customers to roll back to the prior version of the operating system in the short term. In this case 5.1.1.

I for one am very disappointed in apple. We are a big apple family with many computers and devices. When I call Apple they say they cant do anything. When I call Kenwood they say they cant do anything either. I feel like I threw my money in the toilet.

That is a lot of money to spend on a low end stereo, personally, I install myself that way I have more to spend on the stereo itself. My last truck I got a low end stereo configured it to have the 8 speakers powered by the factory amp, then wired a decent amp to the factory subwoofer box with an upgraded speaker. My current truck, I just got it and put in a Pioneer 4400bh (valued $500, paid >$400) spent 3 days installing every little thing including reverse camera. Then updated to iOS 6, Bluetooth did not function correctly, I paid the extra rather then using the stereo I pulled from my last truck for the meta tag feature. Based on what I have been reading, it sounds like my old stereo might still have Bluetooth control, I will have to test that.

Just as an update from pioneer, at least what I am getting from them. They submitted the issue to their engineering department. A week later, I asked what I should be expecting, apple to update or pioneer. I got a "more annoyed" reply saying the say thing. I am going to send another reply to see if they are changing response yet. I am also going to go to the apple store to see what they can do, or tell me.

I have been trying to follow along with the forum, but their is some much on here, is the issue still present on the iPhone 5?

aknedude wrote:

Well i have had enough, My Pioneer carstereo is beeing replaced in a few days. im going for a

JVC KW-AV60BTE this time, they have no problems with bluetooth. and i like the interface much more than pioneers.

Note that for what it's worth many of the Toyota factory head ends having no problem with iOS6 are sourced from JVC.

Hi everyone...

Just wanted to add myself to the huge list of people with this problem. Having issues with iPhone 4S, running iOS 6 and a Kenwood KDC-BT92SD. I can still do Streaming music via bluetooth and talking in handsfree-mode, but can't control the iphone from the headunit or get any meta data on the Display as were shown on iOS 5.

Hope Apple will Release an updated iOS 6.x soon.

greetings from Germany

@William Kucharski...thanks for adding some levity to this thread. I've said the same thing a couple times as well. Don't be so quick to blame Apple for this problem. If the fault is Apple's, we'll find out soon enough and everyone's venom will be rightly justified. If not, and the problem is with OEMs dragging their feet and falling asleep during the upgrade cycle, then the stereo manufacturers will have a major problem. Either we'll get a fix in the form of an OS update or a firware update.

Me? I'm betting on a firmware update from the OEMs. That's the only thing they can do. If it's a hardware problem...oh boy. That's another story.

My 3GS worked just fine with our JVC after market Bluetooth stereo (KD-R526) until I upgraded to IOS 6. It wouldn't even find the Bluetooth device. Now with the iPhone 5 I am having the same problem. No matter what I do I cannot get the Bluetooth to connect or even find the Bluetooth connection.

I've been monitoring this thread for a while now, since i 'fixed' my issues with a quick downgrade to 5.1.1 whilst the firmware was still being signed (JBOOTS75 - I had to clear and re-pair devices for full functionality to return btw) and have been getting more and more sick of the Apple apologists.

Even if the bugs lie in the manufacturers head units and/or Parrot firmware IT IS STILL APPLES FAULT, and I'll tell you why:

See the side my Alpine box (yes, it's retorical): it displays a made for iphone logo, as do plenty of units from all manufacturers still in the supply chain.

I can't make and release a Toaster and just slap a logo like that on it. Ergo, Apple must approve use, which should require compliance testing (If it doesn't - APPLES FAULT). I would not be suprised if a substantial fee was levied for the privelage of displaying and marketing products with such a benefit . Apple should have a database of approved products or how else would they sue TX's Amazing iPhone Toaster (If it doesn't - APPLES FAULT). Thus they should ensure any updates dont 'break' ALL approved units, maintaining compliance. However, I accept that some bugs/errors may not be able to be fixed but customers should be clearly advised which units are affected in release notes, they can then make an informed decision whether to 'upgrade' (as it didn't - APPLES FAULT).

But, but, but, that would take time and cost money: www.boohoohoo.com. Hand's up who got their kit for free?

Typhx wrote:

See the side my Alpine box (yes, it's retorical): it displays a made for iphone logo, as do plenty of units from all manufacturers still in the supply chain.

I can't make and release a Toaster and just slap a logo like that on it. Ergo, Apple must approve use, which should require compliance testing (If it doesn't - APPLES FAULT). I would not be suprised if a substantial fee was levied for the privelage of displaying and marketing products with such a benefit . Apple should have a database of approved products or how else would they sue TX's Amazing iPhone Toaster (If it doesn't - APPLES FAULT). Thus they should ensure any updates dont 'break' ALL approved units, maintaining compliance. However, I accept that some bugs/errors may not be able to be fixed but customers should be clearly advised which units are affected in release notes, they can then make an informed decision whether to 'upgrade' (as it didn't - APPLES FAULT).

Nice try, but the MFI program only certifies compatibility with units available as of the time the device was manufactured.

Or is it your point of view that Apple should provide free Lightning dock adapters because the design of the iPhone 5 broke devices that worked perfectly well with the old dock connector?

Unfortunately the iPhone 5 doesn't provide any good news!

I am running Bluetooth into a MY12 Golf GTI. It happily runs the audio, however every minute or two I get a fraction of a second audio dropout. Very noticeable and very annoying.

I have also lost the ability to access playlists etc via the car.

On a slightly positive note, the song and artist info does show on the car screen.

Everything worked perfectly a couple of weeks ago via my 4S.

Or is it your point of view that Apple should provide free Lightning dock adapters because the design of the iPhone 5 broke devices that worked perfectly well with the old dock connector?

Actually that is my point of view. Are you so sure of Apple's infallibility that you really think this is so preposterous? I've bought cheap computer mice before that came with a USB-to-PS2 adapter just in case I wanted to connect it to a 20-year old computer. Is it that strange that I'd expect my $600 phone to come with an adapter so I could connect it to a $200 device I bought 6 months ago?

William Kucharski wrote:

Note that this is Kenwood admitting at least some of these issues are theirs, as they are the ones developing a firmware update, rather than state"Apple will fix their bug."

They aren't admitting anything of the sort. The fact that Kenwood is developing a firmware update to address these issues is simply proof that they want their devices to work, it doesn't necessarily mean anything's wrong with their own implementation. It's just as likely that they've decided to put their customers first and develop a patch to work around some noncompliance in Apple's code. That aside, nice find on the article.