Skip navigation

bluetooth music issues after iOS6 update

237710 Views 1,014 Replies Latest reply: Mar 16, 2014 4:35 AM by Sedici RSS Branched to a new discussion.
  • Saphod Level 1 Level 1 (0 points)
    Currently Being Moderated
    Nov 28, 2012 12:54 AM (in response to nikB123)
  • William Kucharski Level 6 Level 6 (14,405 points)
    Currently Being Moderated
    Nov 28, 2012 3:03 AM (in response to Dr Agonlord)

    Dr Agonlord wrote:

     

    All in all, I find apple disappointing in their handling (or lack of handling) this issue.

     

    Apple can't "fix" something that's not their problem.

     

    If some existing devices are incompatible with newer protocols which are supposed to be backwards-compatible, what is Apple supposed to do?

     

    Not innovate?  Not implement features that everyone else will be implementing eventually?

  • Dr Agonlord Level 1 Level 1 (0 points)
    Currently Being Moderated
    Nov 28, 2012 3:13 AM (in response to William Kucharski)

    It worked on IOS 5. Apple released IOS 6 and it stopped working. How is that not their fault? a forced innovation that triggered an issue that did not exist until APPLE updated IOS.

     

    the issue may be in errors in other manufacturers implementation, but for those of us affected, it was apples update/innovation that initiated the failure of our hardware.

     

    I really am not getting into a slanging match again, but Apple broke it, so apple should at the very least acknowledge it. For some people apple can do no wrong in this world, I am not one of those people

  • William Kucharski Level 6 Level 6 (14,405 points)
    Currently Being Moderated
    Nov 28, 2012 3:22 AM (in response to Dr Agonlord)

    Dr Agonlord wrote:

     

    It worked on IOS 5. Apple released IOS 6 and it stopped working. How is that not their fault? a forced innovation that triggered an issue that did not exist until APPLE updated IOS.

     

    the issue may be in errors in other manufacturers implementation, but for those of us affected, it was apples update/innovation that initiated the failure of our hardware.

     

    I really am not getting into a slanging match again, but Apple broke it, so apple should at the very least acknowledge it. For some people apple can do no wrong in this world, I am not one of those people

     

    Apple's not going to be responsible for another manufacturer's bug, end of story.

     

    Go ahead, trash Apple, sell your iPhone, whatever, but it's not going to change.

     

    The Bluetooth protocols changed between what was delivered in iOS 5 and what was delivered in iOS 6.

     

    The changes are supposed to be backwards-compatible, according to the Bluetooth SIG.

     

    However, if a particular company got their implementation wrong, the new protocol won't be compatible with their device, it's as simple as that.

     

    For example, older Mazda 3s could only support devices running AVRCP 1.3 or less due to a firmware error in their device.

     

    AVRCP 1.4 is backwards compatible, but if a manufacturer has code in their device that looks like:

     

    if (avrcp == 1.1)

        do_stack_1.1();

    else if (avrcp == 1.2)

        do_stack_1.2();

    else if (avrcp == 1.3)

        do_stack_1.3();

    else

         error();

     

    there's nothing Apple can do, and the device will "break" due to Apple' support of AVRCP 1.4.

  • linkovich Level 1 Level 1 (0 points)
    Currently Being Moderated
    Nov 28, 2012 4:20 AM (in response to William Kucharski)

    I understand AVRCP.  What you don't understand is that Apple didn't implement it correctlyThat is why it doesn't work reliably and/or consistently with brand-new devices, which you seem to have overlooked.  I'm getting the same inconsistent pairing and song choppiness that everyone else is seeing.  Sometimes it refuses to pair at all, for days, then it magically re-appears.  This is 2012.  That shouldn't happen.

     

    A fanboy is a fanboy.  People don't complain because they're "doing something wrong".  Bluetooth either works reliably, or it doesn't.  A user isn't "doing something wrong" when an iPhone won't pair with a brand-new Bluetooth headset or audio system, especially when any new Android device will.  Blaming the user makes you look like a fanboy - or, worse, an Apple employee who a) refuses to believe anything is wrong, or b) actually do something about it and admit (GASP) guilt.

     

    But thank you for your rock-solid refusal to listen to the complaints objectively.  You're right.  My next phone will be a Sansung Galaxy SIII or a Motorola Razr Maxx, since my neighbor's Galaxy SIII connects and works perfectly in both of our Fords, every time they get in the car.  *Perfectly*.

     

    iOS 6.0.1 is filled with Bluetooth bugs.  End of story.  But I let's revisit this thread when (and if) Apple does quietly release a fix, shall we?

  • linkovich Level 1 Level 1 (0 points)
    Currently Being Moderated
    Nov 28, 2012 4:18 AM (in response to Dr Agonlord)

    Dr Agonlord wrote:

     

    <snip>I really am not getting into a slanging match again, but Apple broke it, so apple should at the very least acknowledge it. For some people apple can do no wrong in this world, I am not one of those people

     

    Well-said.  Plain and simple.

  • spanks127 Calculating status...
    Currently Being Moderated
    Nov 28, 2012 4:28 AM (in response to nikB123)

    I had many posts in this thread when iOS 6 was released, and I still receive email notifications to see how Apple handles this in the end.   I returned every business iPhone that I purchased (11 of them) and all I can say is it was the best decision I've ever made.  I've had every iPhone on every release date since the original, and I am SO happy I migrated away from Apple, and their shady tactics..  As a business owner, I understand it is all about the money, however you can't alienate your customers when there are other alternatives on the market.  I was closed minded when I was a fanboi, and now that I've been to the 'other side', I can only say it is wonderful.  Stop waiting for a software patch, and jump ship.  There are other phones in this galaxy, and they will not let you down.

     

    I do not know who absorbed the cost of my return,  but the phones, and accessories that AT&T took back from me was $4382.28...      I fought back with my money,  you should do the same.    Do not be a slave to this company.

  • Saphod Level 1 Level 1 (0 points)
    Currently Being Moderated
    Nov 28, 2012 4:56 AM (in response to spanks127)

    Oh man, I clicked on the back button again... All lost... Again. :'-(

     

    Basically all I wanted to say is that I prefer the design of Apple products to the Android competition. I am not a fan of the big screen mania (love the iPhone 5 size), and I hate the look and feel of the Android interface. I do not need animated widgets and such nonsense.

     

    You guys must admit that a lot of things DO work on the iPhone, and I would never swap my iPad for an Android tablet.

     

    * ****, I did not want to be drawn into these discussions here. ;-) *

     

    I had a Galaxy S2 (on Optus here in Australia), and after one year, I started to hate it. Not just Apple makes implementation mistakes. After upgrading to Gingerbread, the mail software did not work correctly with the Exchange server at work, and I sometimes couldn't receive any email. Then, after it was fixed with a subsequent update, the battery died too early.

     

    The problem with Android is that there are so many vendor-dependent versions. Terrible. That's one reason I wanted the iPhone: iOS updates are the same for everyone... Or so I thought.

     

    Apple stuffed things up with iOS 6, especially Maps, Wifi and Bluetooth. They should probably have waited a bit longer, but then the public always expects them to come up with something extraordinary. There is a lot of pressure from the consumer side. If the public accepted an "evolutionary" phone, not always "revolutionary", maybe they would have more chances to fix things.

     

    I do not think Apple sits back and rests on their laurels. You must admit that they have some great minds over there in Cupertino. I guess a lot of people forget why we have the smartphone and the tablet in the first place (yes, that was all Steve, I know).

     

    And yes, you pay a high price for Apple products, but you pretty **** well know that when you decide to go for an Apple product (unless you live behind the moon).

     

    Give them some credit and time to fix it. I am sure it'll all be well in the end.

     

    Hopefully... ;-)

     

    --

    http://twitter.com/saphod/status/273710233698856960

  • drewe2000 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Nov 28, 2012 5:38 AM (in response to nikB123)

    Look, there's no reason to snap at each other on here.

     

    The problem is well documented, and every case helps prove it and push Apple and other manufacturers.

     

    At the same time, there are plenty of cases where there are no problems at all - I mentioned one, with the Kenwood KDC-X696 head unit I purchased. It works perfectly with the iPhone 4, 4S, 5, and iPad 3 with iOS 5 and 6.

     

    I know that a friend's Volkswagon EOS works at least as well with the iPhone 5 as it did with the iPhone 4, but for bluetooth it's limited to phone calls and always has been because of corners cut by Volkswagon.

     

    Some people have found solutions that work, others haven't. Some people insist that their stereo won't work no matter what, while others with the same stereo claim there is no problem (Ford has come to my attention).

     

    It's not simply that Apple "broke" something with iOS 6 - otherwise, the bluetooth connection would never work for anyone unless it was a device released after iOS 6, which is clearly not the case.  It shouldn't have happened, but the fact that this bug was uncovered by an Apple update doesn't mean it is strictly Apple's fault.

     

    Nevertheless, it sounds like iOS 6.1 may solve the issue for many.

     

    I would be shocked if any tech support person at Apple, Pioneer, Kenwood, Ford, Inifiniti, Mercedes, or whoever (especially at a local repair shop) actually knew what was happening behind the scenes or admitted it. None of those companies will likely ever admit to being at fault.  Many of those 3rd party manufacturers have stated they have updates on the way to fix the problem, and it sound like Apple does as well. Even after the fixes, they'll likely all point fingers at each other. Why admit fault if they don't have to?

     

    That said, someone pointed to a document on here from Apple stating that there is a known incompatibility issue with iOS 6 and bluetooth, but I can't find it right now. So Apple isn't denying it, they just aren't broadcasting it while they work on a solution.

     

    I think a major problem here is that until very recently, car manufacturers and stereo headset manufacturers never had to pay attention to compatibility or updates. This is a new world to them, and there are growing pains.  It used to be that you simply replace your equipment every few years (from their standpoint).  And they are notorious for not strictly adhering to technical standards.

     

    Apple hosts these forums, but they never (to my knowledge) reply on them. So there will be no response on here, other than from other users trying to help each other.

     

    Keep contacting Apple about it, by all means. But push the third party manufacturers as well, who are most likely at fault.

  • doctorjaymd Level 1 Level 1 (0 points)
    Currently Being Moderated
    Nov 28, 2012 6:43 AM (in response to ThePicardMeneuver)

    Yes, ThePicardMeneuver and babston, I have the same Alpine unit too.  It was so nice when it worked with iPhone 4 (a few months ago!).  Have you had any luck connecting through the USB port?

     

    This forum makes me smirk, and I've started to think of Apple more like Fisher-Price than a technology company. 

    Thank you for your updates, I will do the same if I ever hear back from Apple about Alpine.

  • Luge Calculating status...
    Currently Being Moderated
    Nov 28, 2012 7:48 AM (in response to doctorjaymd)

    Doctorjaymd, connecting through the USB port is not the issue, it works fine via the USB port.

    The issue is that iPhone's used to work beautifully through BT Audio, and no longer do. 

    Sure, I can pull my phone out of my pocket, pull out a USB cord and connect it every time I get in the car, but it sure was nice when I just jumped in the car and music started playing, and I could control and see the tracks via the (Alpine 133BT) head unit.

    It's a step backwards.

  • ThePicardMeneuver Level 1 Level 1 (0 points)
    Currently Being Moderated
    Nov 28, 2012 9:09 AM (in response to nikB123)

    Reading through this always makes me furious I wasted my time updating to the 5.  It really was a **** of a thing to just be able to get in the car and forget about the phone.  Goddamnit I hope SOMEONE comes through in the end!

  • Saphod Level 1 Level 1 (0 points)
    Currently Being Moderated
    Nov 28, 2012 7:30 PM (in response to nikB123)

    Interesting - just received this email as a reply from Mazda Australia:

     

    Thank you for contacting us in regards to your HandsFree system.


    We have very rigorous testing procedures and unfortunately, iPhone 5 did not pass our testing for compatibility with the Mazda HandsFree system. There were too many issues with the phone.


    We are only able to provide support for the compatible phones listed on www.mazdahandsfree.com.au. The phone has to have Bluetooth and a "handsfree" profile and to have passed our testing in order to be compatible. A "headset" profile is not compatible with the Mazda HandsFree system. We do not have any other knowledge regarding this phone or have any troubleshooting tips.

     

    And I just found this:

     

    http://brisbanetimes.drive.com.au/motor-news/iphone-strikes-car-trouble-20121128 -2adj0.html

     

    --

    Make Apple aware of this discussion via Twitter:

    http://twitter.com/saphod/status/273710233698856960

     

    Message was edited by: Saphod

  • rustykerr123 Level 1 Level 1 (15 points)
    Currently Being Moderated
    Nov 28, 2012 8:35 PM (in response to Saphod)

    Ok this is my third attempt to submit this message, apparently apple's own site does not function on their own iPad.

    Saphod wrote:

     

    We are only able to provide support for the compatible phones listed on www.mazdahandsfree.com.au. The phone has to have Bluetooth and a "handsfree" profile and to have passed our testing in order to be compatible. A "headset" profile is not compatible with the Mazda HandsFree system. We do not have any other knowledge regarding this phone or have any troubleshooting tips

    Ok this part of the reply helped me find a little bit of information.  First, Apple changed the profiles to add MAP.  Also, apple expected this issue, they stated it here http://support.apple.com/kb/TS3018, it is a year old, but they expected it with iOS 4 and newer.

     

    Here is what the article says.

    When using a stereo Bluetooth headset or other stereo Bluetooth device with an iPhone, iPad, or iPod touch*, certain features may not work as expected. Examples include:

    • Pressing previous and next controls has no effect.
    • Pressing play/pause control only pauses or starts playback.
    • Pressing other headset controls has no effect.

    * Stereo Bluetooth is available only on iOS devices that support the A2DP Bluetooth profile. Refer to iOS: Supported Bluetooth Profiles.


    ...

     

    After updating your device to the latest version of the iOS, you may notice that certain features on your stereo Bluetooth headset no longer function as expected. Certain Bluetooth headsets do not fully conform to industry-standard Bluetooth protocols, so changes in the iOS (made to ensure compatibility with industry standards) may affect these devices. This is expected behavior and does not indicate an issue with your iPhone, iPad, or iPod touch.

    Contact the headset manufacturer for more information.

    So basically we all are waiting on the manufactures to fix the issues.

    iPhone 4S, iOS 6.0.1
  • William Kucharski Level 6 Level 6 (14,405 points)
    Currently Being Moderated
    Nov 29, 2012 12:51 AM (in response to linkovich)

    linkovich wrote:

     

    I understand AVRCP.  What you don't understand is that Apple didn't implement it correctlyThat is why it doesn't work reliably and/or consistently with brand-new devices, which you seem to have overlooked.  I'm getting the same inconsistent pairing and song choppiness that everyone else is seeing.  Sometimes it refuses to pair at all, for days, then it magically re-appears.

     

    Where's your proof of this being Apple's fault?

     

    BT protocol analyzer dumps?

     

    Comparison of operation with other latest protocol compliant devices?

     

    Anything other than "it doesn't work with my device" observations?

     

    Just because a third party device is brand new doesn't mean those devices implement the latest standards.

     

    Go buy yourself a brand new Android phone; even the Galaxy S III only supports AVRCP 1.3, and some Android devices on the market only support even older versions.)

1 ... 37 38 39 40 41 ... 68 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (46)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.