Skip navigation

bluetooth music issues after iOS6 update

237262 Views 1,014 Replies Latest reply: Mar 16, 2014 4:35 AM by Sedici RSS Branched to a new discussion.
  • crankerchick Level 1 Level 1 (5 points)
    Currently Being Moderated
    Oct 11, 2012 8:38 AM (in response to spanks127)

    spanks127 wrote:

     

    You guys are cracking me up.  Because Pioneer is working out a patch for Apple's fault, some of you are saying this isn't an apple issue.    Apple released a version of blue tooth that is NOT backwards compatible and since Pioneer is going to keep their customers happy by releasing a patch for Apple's negligence.     Pioneer's fix will correct 33% of the $5000+ in equipment I have that is not working due to Apple's shady iOS release.

     

    If 6.1 isn't released by the 19th,  all of my iphone 5's are heading back to at&t.

    I'm with you. I am willing to concede that it is possible that it might not be Apple's fault, but that just doesn't seem likely. I mean, *all* of these different devices and manufacturers all have firmware that somehow manages to break backward compatibility? Just doesn't seem likely. Apparently it's possible, but more likely that Pioneer is fixing something that someone else broke because it's good customer service to do so.

  • rustykerr123 Level 1 Level 1 (15 points)
    Currently Being Moderated
    Oct 11, 2012 8:39 AM (in response to spanks127)

    I actually think it is partially the manufactures fault as well as mostly apples fault.  It sounds like pioneer and others used a nonstandard protocol method, apple did not support backwards compatibility and removed this option.  I think that they both need to release a fix to better future proof, even though it is not 100% possible.

     

    There is no way it will be released on the 19th of October, maybe the 19th of November.

  • spanks127 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Oct 11, 2012 9:08 AM (in response to rustykerr123)

    So you really think that 7 companies (that I know of) all conspired to use nonstandard protocols? 

     

     

    Let me guess, if the iOS7 only supports wireless R routers, and is not backwards compatible with G or N, are you going to say that routers should have been ready for apples iOS7?    Think about what you're saying.

  • rustykerr123 Level 1 Level 1 (15 points)
    Currently Being Moderated
    Oct 11, 2012 9:15 AM (in response to spanks127)

    Well the way you say it it sound like it was done to screw us.  I think there was options laid out, and they chose to use a simple preconfigured set or something like that.  I am not really sure, I just believe it has to be both of their faults, you would think that all these companies would check to make sure it is right before selling the device or releasing the update, but if they all assume the other will keep them in mind and test it for them, then the small bugs on each might show up as a major issue in the end when not one checks it.

  • spanks127 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Oct 11, 2012 9:18 AM (in response to rustykerr123)

    It was not tested properly, and released before it should have been.  We are talking about apple here.   I'm afraid they've jumped the shark with iOS6.   It obviously wasn't tested like the previous releases.  Full of bugs,   and this blue tooth issue is insane.

     

    I'm actually going to be at the apple store in 2 hours where I hope they swap my iphone 5 out for a new once since my battery dies after 8 hours of being unplugged from the charger. 

  • rustykerr123 Level 1 Level 1 (15 points)
    Currently Being Moderated
    Oct 11, 2012 9:25 AM (in response to spanks127)

    Yes, Apple either did not test it or not as well as before, but pioneer should have tested it during beta to find out that there was an issue before the final release.  Apple should not be responsible for making sure every little feature works with pioneer's stereo, but they should have tested one on each version of the protocol, perhaps they did and they all worked for them, I don't know their process. 

     

    Apple made a bad update, other companies did not check compatibilities until it was too late.

  • spanks127 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Oct 11, 2012 10:19 AM (in response to rustykerr123)

    Again,  look at my analogy for wireless routers.   All of these head units and blue tooth communication devices worked just fine with iOS4,  iOS5,  iOS5.1, and somehow they all stopped working with iOS6.

     

    Do you really think that the FUTURE PROTOCOLS should not be backwards compatible?   Pioneer has successfully been using a version of blue tooth that worked flawlessly with the iphone iOS prior to 6.  Why would it be Pioneer's, or any other companys responsiblity to insure that future versions of apple software stick to the working protocols that are on millions of peripherals out there?   Pioneer should not be forced to change prior setups due to apple's negligence of not offering a backwards compatible version of blue tooth?

     

    I've been an "apple fanboi" by owning every single phone they ever made.  I've never had any issues like this.  Apple has yet to release a single statement on blue tooth issues,  nor the battery issues. 


    Pioneer was basically forced to step up to the plate and take partial blame because they do not want to be inundated with returns for everybody who upgraded to iOS6.  They have to maintain a working relationship with apple or they would lose the rights to say their devices work with the iphone.  Pioneer is in a bad spot, along with all the other companies that were screwed over by Apple failing to test these items. 

     

    I'm not sure how many of you followed the beta forums for iOS6, but this was a known problem since day one when it was released to developers.   Apple knew this was an issue and did not correct it.

     

    I also notice that pioneer head units that used to support video in will no longer be able to handle it due to apple's switch to the new connector.  It is not compatible with video out.  Again, apple screws everybody.

     

    But in the end, apple cares about money. They're a business.  And I'm sure the return of all my business phones will easily be negated with the sales of lightning connectors in about ten minutes through their website.

     

    Apple has lost a customer in me unless they address or patch this in the next week...   I have thirty days through at&t to return my device if I am not happy, and I surely am not happy.

  • crankerchick Level 1 Level 1 (5 points)
    Currently Being Moderated
    Oct 11, 2012 10:22 AM (in response to spanks127)

    spanks127 wrote:

     

    ...Why would it be Pioneer's, or any other companys responsiblity to insure that future versions of apple software stick to the working protocols that are on millions of peripherals out there?   Pioneer should not be forced to change prior setups due to apple's negligence of not offering a backwards compatible version of blue tooth?

     

    This.

  • Abcm12 Calculating status...
    Currently Being Moderated
    Oct 11, 2012 1:41 PM (in response to nikB123)

    My old iphone 4s with IOS 6 bluetooth music worked in my car. Today Got new 4s phone with new IOS 6 and did not work in car, phone calls would come in through Bluetooth but music didn't.  Weird...called apple couldn't fix it, went to apple store and they reset the phone and music worked via bluetooth in store when paired with a music device. came back to the car paired it off again, music did not work. So, I reset the whole navigation system and deleted all personal data. Once that done I paired again my iPhone 4S and low and behold my music worked by Bluetooth!!!! Hope this info please.

  • electronicsguy Level 2 Level 2 (190 points)
    Currently Being Moderated
    Oct 11, 2012 2:08 PM (in response to Lighty_)

    thats wierd. i thought BT4 would maintain profile compatibility with BT3. I can pair up with my laptop which is BT3.

  • William Kucharski Level 6 Level 6 (14,395 points)
    Currently Being Moderated
    Oct 11, 2012 3:25 PM (in response to spanks127)

    spanks127 wrote:

     

    Again,  look at my analogy for wireless routers.   All of these head units and blue tooth communication devices worked just fine with iOS4,  iOS5,  iOS5.1, and somehow they all stopped working with iOS6.

     

    [ … ]

     

    I'm not sure how many of you followed the beta forums for iOS6, but this was a known problem since day one when it was released to developers.   Apple knew this was an issue and did not correct it.

     

    Apple historically will not correct problems caused by their correct adherence to a standard.

     

    Some wireless routers actually did break with the release of iOS 6, the biggest example being several HP (and Lancom) routers, as can be read here:

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

     

    Now, the "IEEE Std 802.11n-2009" states that this parameter should have only 3 as valid length. Contrary to that, the current "IEEE Std 802.11-2012" defines the valid length between 3 and 8.

     

    It seems that our HP/H3C equipment treats "Extended Capabilities" parameter length == 4 as fatal error and rejects the association (instead of just ignoring this parameter).

     

    From the formal point of view, Apple's implementation is correct, and HP should correct its firmware. We've got in touch with HP about this issue and are now awaiting their response.

     

    HP recently released a firmware fix to resolve this; there is at present no reason to believe that Pioneer isn't having to take similar action for similar reasons; note also that IEEE 802.11-2012 was supposed to be completely backwards compatible with IEEE 802.11-2007 and all its amendments (802.11k, r, y, b, w, p, z, v, u and s.)

     

    To use an example I've used in other threads, let's pretend there's a bug where the head end calculates a request to add "2 + 3" as "5" but one to add "3 + 2" as "6."

     

    If iOS 6 starts adding "3 + 2" where previously it had added "2 + 3," it's not Apple's responsibility to go back and make sure they only ever add "2 + 3."

     

    Those who have been around for a while may remember a similar incident when Mac OS X 10.3 "Panther" was released in October, 2003: many, many users of a wide variety of brands of FireWire hard drives were finding their hard drives to have become corrupted once attached to a system running Panther.

     

    It turned out those drive manufacturers all used one common part, the Oxford 922 bridge chipset, which is what turned out to have a particularly nasty firmware bug.

     

    It's quite possible that, for example, some sample code distributed by the Bluetooth SIG could have had an error that, if used verbatim, would result in a problem like this.

     

    Or it actually could be Apple's issue.

     

    Point is, until someone speaks up, we simply don't know - we do not have sufficient data to reach a conclusion as of yet.

     

    That's why it's vital to contact AppleCare if you're having this issue - so both Apple and device makers have the widest range of examples available to track down and completely root cause the issue.

     

    But I can tell you that companies like Pioneer wouldn't spend the time and cost to release a firmware update for an issue that was likely to be fixed in one fell swoop by a future release of iOS.

  • William Kucharski Level 6 Level 6 (14,395 points)
    Currently Being Moderated
    Oct 11, 2012 3:31 PM (in response to crankerchick)

    Also, as I mentioned previously, just to keep things interesting, the Bluetooth SIG recently approved and ratified AVRCP 1.5.

  • crankerchick Level 1 Level 1 (5 points)
    Currently Being Moderated
    Oct 11, 2012 4:51 PM (in response to William Kucharski)

    True. Can't say for sure. But still, it's not like we are talking about 1 or even 2 manufacturers. This is multiethnic manufacturers all being affected in the same way. I guess if they all adopted the same implementation (this parrot or whatever) and it doesn't adhere to the standard, then that would make sense. I just hope that isn't the case. We will know soon enough by way of an update (or not) from Apple. I still don't think that Pioneer issuing an update means anything though.

  • crankerchick Level 1 Level 1 (5 points)
    Currently Being Moderated
    Oct 11, 2012 4:53 PM (in response to crankerchick)

    *multi not multiethnic. *iPhone LOL

  • SLC RN Calculating status...
    Currently Being Moderated
    Oct 11, 2012 7:14 PM (in response to Abcm12)

    @Abcm12, I have almost the exact same problem. I have a 2009 Ford Edge that my 3Gs and bluetooth worked perfectly fine. I skipped a generation and went to the 5. Once I synced my phone with with the car's computer system, I tell it to call a person and it says it person's # cannot be found. I have to manually dial phone # and then it works. Can't listen to music, podcast, audiobooks etc. from my new Iphone.

1 ... 26 27 28 29 30 ... 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.