Skip navigation

bluetooth music issues after iOS6 update

238186 Views 1,014 Replies Latest reply: Mar 16, 2014 4:35 AM by Sedici RSS Branched to a new discussion.
  • mowog74 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Oct 2, 2012 8:28 PM (in response to William Kucharski)

    Regardless of whose fault it is, there's no denying Apple just released an update that instantly and irreversibly (for now, anyway) breaks what for many of their customers is an important piece of functionality. If Apple knew in advance that this many bluetooth devices would stop working properly with iOS devices, then this is another in a long string of F-you's Apple has dished out to its loyal customers.  If Apple didn't know, then their customers are paying the price for an unbelievably shoddy testing process. Either way I don't see how anyone can side with Apple on this issue with a straight face.

  • Coasterby Calculating status...
    Currently Being Moderated
    Oct 2, 2012 11:10 PM (in response to mowog74)

    This post is for anyone using a Parrot bluetooth system.  I use my iPhone over a Parrot mki9100 system.  I started getting the same AVRCP remote music control (i.e. play/pause/skip) issues and metadata (song name, artist) issues discussed in this forum once I upgraded to an iPhone 5 (with iOS 6 of course) .  For me there is one very tedious yet effective fix for this: go to the settings menu, select bluetooth, select paired devices, select the phone currently paired and then select disconnect.  After it's disconnected I reconnect by selecting 'connect' in the same menu.  Controls and metadata come back every time I do this.  I should note that after I disconnect the iPhone is still playing music and is still doing so at the point when the two systems reconnect.  I come back to this point later in this post.  Anyway, to me the fact that this works has two important implications.  1) I can't see this being an issue of compatibility between the Parrot and iOS versions of AVRCP if the functionality resumes after disconnect/reconnect and 2) I don't see how this could be an issue with Parrot's firmware if it works after disconnect/reconnect.  Something seems to be going on with iOS 6 that prevents the iOS AVRCP from properly initiating.  Back to my point about the ongoing music play during disconnect/reconnect, maybe a bug in iOS makes it such that music needs to be playing in order for iOS to properly initiate AVRCP?  Whatever the cause, for those of you using Parrot systems and looking for a temporary fix (albeit an annoying one), try the disconnect/reconnect.  And to Apple: I'm really looking forward to that fix.

  • William Kucharski Level 6 Level 6 (14,440 points)
    Currently Being Moderated
    Oct 3, 2012 12:02 AM (in response to Coasterby)

    Coasterby wrote:

     

    1) I can't see this being an issue of compatibility between the Parrot and iOS versions of AVRCP if the functionality resumes after disconnect/reconnect and 2) I don't see how this could be an issue with Parrot's firmware if it works after disconnect/reconnect.  Something seems to be going on with iOS 6 that prevents the iOS AVRCP from properly initiating.  Back to my point about the ongoing music play during disconnect/reconnect, maybe a bug in iOS makes it such that music needs to be playing in order for iOS to properly initiate AVRCP?

     

    Or there could be something in AVRCP where some state is supposed to be retained by the receiver of the data stream and that bit of the state machine gets reset on a reconnect.

     

    Apple could in no way conceivably test with every head end (though frankly each BT manufacturer could certainly test with iOS devices; meanwhile Apple made seeds of iOS 6 available to developers months before its release, so why didn't Parrot and Kenwood test their products?)

     

    A good example of designing to standards would be that in the United States, AC current is 110 - 125 VAC at 60 Hz.

     

    Say one day power companies find they can save money by installing a cool new regulator that has been invented that delivers exactly 110 VAC to wall outlets.

     

    But say certain appliances stop working, because they really need 111 - 125 VAC.

     

    The power company isn't responsible for going supplying 111 VAC, even though they made a change that "broke" the appliances; the spec has always been there that stated 110 - 125 VAC, and should have been followed when designing products.

     

    We still don't know where the problem lies, but with each day I become more suspicious that no BT vendor has yet pointed the finger at Apple, as it would take but a few minutes with an iOS 6 device, their firmware listings and a BT protocol analyzer to see what's going on where, yet iOS 6 has been available to the public for two weeks as of Oct. 4.

     

    Frankly, I'm shocked no one has leaked the root cause of this problem to Slashdot or The Register by now; surely some engineer somewhere knows…

  • mowog74 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Oct 3, 2012 5:35 AM (in response to William Kucharski)

    @William Kucharski, it's true that in your example the power company would be within their rights, so to speak, to supply exactly 110 VAC.  But what if the number of affected devices were large?  Say half of all refrigerators use compressors supplied by the same vendor that all require 111 VAC?  Wouldn't it be pretty customer-hostile for the power company to make that change without making more of an effort to ensure 3rd parties were caught up, or at least give some warning to their customers so that they could pressure the fridge vendors?  It would also be pretty irresponsible of the power company not to have tested the change in advance against such a large set of devices.

     

    Anyway I agree with you if it turns out the number of affected users is relatively small -- I wouldn't expect Apple to test against every bluetooth device out there. There just seems to me to be a lot of chatter about this so I'm assuming it's a more widespread issue.

  • aknedude Calculating status...
    Currently Being Moderated
    Oct 3, 2012 5:57 AM (in response to nikB123)

    I have now heard from a very big carsound reseller in scandinavia.

     

    And they have talked to Pioneer, Kenwood, JVC and Alpine. They have had 1000 of unsatisfied customers calling  the last  week, And they all say  they the same. Bluetooth stinks on ios 6.

     

    They are NOT gonna update the software to work with ios6.

    they all have found an error in ios 6 bluetooth protocol it should be easy to fix but.

     

    its up to apple to fix this.... It worked before and they have to get it to work again.

     

    These are the words from the Car radio manufactures.

     

    I have a avh-2400BT with same errors

  • William Kucharski Level 6 Level 6 (14,440 points)
    Currently Being Moderated
    Oct 3, 2012 6:02 AM (in response to mowog74)

    mowog74 wrote:

     

    @William Kucharski, it's true that in your example the power company would be within their rights, so to speak, to supply exactly 110 VAC.  But what if the number of affected devices were large?  Say half of all refrigerators use compressors supplied by the same vendor that all require 111 VAC?  Wouldn't it be pretty customer-hostile for the power company to make that change without making more of an effort to ensure 3rd parties were caught up, or at least give some warning to their customers so that they could pressure the fridge vendors?  It would also be pretty irresponsible of the power company not to have tested the change in advance against such a large set of devices.

     

    I think you misunderstand utility companies if you think they'd care…

  • Boltssss Calculating status...
    Currently Being Moderated
    Oct 3, 2012 7:54 AM (in response to jimm521)

    I also went back to the USB cable BUT, I still can't make a call with out picking up my phone!

    I was looking forward to upgrading my iPhone 4 to the 5 but I dont know now!

  • William Kucharski Level 6 Level 6 (14,440 points)
    Currently Being Moderated
    Oct 3, 2012 2:13 PM (in response to aknedude)

    Unfortunately, this sounds more like a rumor than actual fact.

     

    I don't think any of these manufacturers would be shy about publicly pointing the finger at Apple were it an iOS issue, so that's why I'm surprised none has, if that's where the fault lies.

     

    (It would also be all over CNet, Gizmodo, Slashdot, The Register, etc.)

  • Boltssss Level 1 Level 1 (0 points)
    Currently Being Moderated
    Oct 3, 2012 2:36 PM (in response to William Kucharski)

    So everything worked 100% for me,  I dowmloaded iSO6 and the very next time I am in my truck I can't make a call or control my music on my phone as I did the day before using bluetooth.....Wake up William!

  • Stevo14896 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Oct 3, 2012 2:40 PM (in response to William Kucharski)

    If this Bluetooth problem is a rumor, I would not be on this forum trying to figure out what is wrong with my Bluetooth connection after updating to IOS 6. It's been two weeks since I've had this problem but yet it keeps arising and will not work.

     

    My conclusion of the problem:

    iOS 6 followed new Bluetooth protocols where vendors are not up to date via Bluetooth which is causing the problems. Without vendors updating their Bluetooth it could not be Apple's fault. Though... Updates usually have a backwards compatible way of connecting to older devices so what it seems like apple disabled that feature for more current devices.

     

    Either way they are canceled out.

  • William Kucharski Level 6 Level 6 (14,440 points)
    Currently Being Moderated
    Oct 3, 2012 2:49 PM (in response to Boltssss)

    As stated numerous times, just because a device doesn't work with iOS 6, that doesn't mean Apple broke anything; in many cases it's the device that's broken.

     

    Most recently, many users found that their iOS devices running iOS 6 no longer would associate with various HP wireless access points.

     

    Why?  It turns out that Apple correctly conforms with the latest 802.11n standard, and HP did not (and has since released a fix):

     

    iOS 6 sends a parameter "Extended Capabilities" in its association request to the AP. This "Extended Capabilities" parameter has a length of 4.

     

    The "IEEE Standard 802.11n-2009" states that this parameter should have only 3 as valid length.

     

    Contrary to that, the current "IEEE Standard 802.11-2012" defines the valid length between 3 and 8.

     

    It may very well turn out there's a similar issue going on with the BT/AVRCP standards.

  • Boltssss Level 1 Level 1 (0 points)
    Currently Being Moderated
    Oct 3, 2012 2:49 PM (in response to William Kucharski)

    Apple should allow me to put my phone that was outstanding back to the way it was!

    iOS6 was to make my phone better.... iOS6 FAILED TO DO THAT FOR ME....Too bad is not an answer......

  • SkylineFan Level 1 Level 1 (10 points)
    Currently Being Moderated
    Oct 3, 2012 3:26 PM (in response to nikB123)

    I am having exact same issue with my iPhone 4S and AVH-P8400BH ... the bluetooth connects but I cannot control the headunit while stearming and it does not show artist/track names ... it just shows NO INFO PROVIED while streaming thru bluetooth.

  • jester56 Calculating status...
    Currently Being Moderated
    Oct 3, 2012 5:33 PM (in response to nikB123)

    I think Boltsss has the best idea for a temporary fix that will put everyone back in the drivers seat. Just make iOS 5 available for us to reinstall. We know that it works properly. Why should Apple care if we "backflush" to get our BT working? Considering there are so many users with the same exact problems, it should be an easy decision. And it can take the pressure off of them to come up with a quick fix and make us happy that we can use our expensive equipment again. It always seems like the simplest solution is so hard for companies to see.

     

    And William - Thanks for taking so much time to try and present the other side of the coin. There are a lot of threads out there on this subject that you could be in. You picked this one.

  • natelindberg Calculating status...
    Currently Being Moderated
    Oct 4, 2012 5:28 AM (in response to nikB123)

    Same issues here.  Updated iPhone 4 from iOS 5.1.1 to iOS6.  Motorola S305 bluetooth headset worked fine prior to update.  Since then, if I attempt to pair my headphones, the circle spins, nothing ever happens. 

1 ... 20 21 22 23 24 ... 68 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (47)

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.