Skip navigation

bluetooth music issues after iOS6 update

237545 Views 1,014 Replies Latest reply: Mar 16, 2014 4:35 AM by Sedici RSS Branched to a new discussion.
  • William Kucharski Level 6 Level 6 (14,405 points)
    Currently Being Moderated
    Nov 29, 2012 12:58 AM (in response to Saphod)

    Saphod wrote:

     

    And I just found this:

     

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

     

     

    Note the article states:

     

    Drive tested the hands-free and music functions of an iPhone 5 with the latest software updates this week and found it worked flawlessly with new cars made by Audi, Kia, Mazda, Peugeot and Toyota.

    Ford says there have been no reported problems between its new electronic Sync system and the iPhone 5.

    But a spokesman for Hyundai said that some customers had experienced smartphone connection problems.

     

    which makes it sound like a Holden/Hyundai issue.

     

    Holden, is correct about there "needing to be testing," but iOS updates were available to developers for months before the iPhone 5 and iOS 6 were released, which means Holden could have tested long before the release but didn't.

  • linkovich Calculating status...
    Currently Being Moderated
    Nov 29, 2012 5:17 AM (in response to William Kucharski)

    Wow. The fanboy just doesn't give up.

     

    That's OK. You, personally, will be responsible for Apple losing several customers in this thread alone.

     

    Simple fact, since you can't digest easily: both of our iPhones worked with both of our Fords before iOS6. Now they don't. Ford didn't change anything. Apple did.


    When I took my phone to an "Apple Genius", she said it had been "submerged". Both water indicators were WHITE. In other words, she lied. My only question to Apple with five Apple products, and I was lied to.

     

    A Galaxy works.

     

    End of story. I won't waste any more time arguing with a pathetic Apple fanboy anymore. Bye.

  • bah434x Calculating status...
    Currently Being Moderated
    Nov 29, 2012 8:22 AM (in response to nikB123)

    Just had this from Alpine

     

     

    Hi, the update is being worked on, beta versions have been tested OK, The solution should be out before Christmas  

     

    .#Alpine Electronics of UK Ltd.
    Alpine House, Fletchamstead Highway, Coventry, CV4 9TW, United Kingdom

    Technical/Customer Support.  Tel: 0845 313 1660
    Sales Desk.    Tel: 0845 313 1650
    Service Dept.    Tel: 0845 313 1642
    Spare Parts Dept.   Tel: 0845 313 1644

     

  • Luge Calculating status...
    Currently Being Moderated
    Nov 29, 2012 8:37 AM (in response to bah434x)

    Tha'ts great news on Alpine's solution.  I wonder how they will implement it into our existing units?

  • Ryan 76 Calculating status...
    Currently Being Moderated
    Nov 29, 2012 12:24 PM (in response to nikB123)

    In the last ten years I have purchases almost every I-device and have to say this has been the worst experience yet. I was expecting my iPhone 5 to out perform my old iPhone 4 but it is falling short due to software issues.

     

    I Now carry TWO I-devices, one original iPod touch ios5 that flawlessly streams blutooth music to my pioneer stereo and an iPhone 5 ios6 for making phone calls. *** Apple! Leaving your loyal customers in the dark is BS! I would settle for yup it's broke but instead I ask myself should I bail off this Apple train.

  • Coasterby Calculating status...
    Currently Being Moderated
    Nov 29, 2012 12:57 PM (in response to nikB123)

    It seems as though different manufacturers are dealing with this issue in different ways.  Sounds like Alpine and likely Pioneer will come out with firmware updates for affected products.  I thought Parrot had a firmware upgrade in the works, but I'm not sure anymore.  Here's the latest from Parrot:

     

    "I have shared the link you send to the Apple forums with several of the managers here at Parrot.

     

    Based on feedback like yours, we no longer list iPhones with iOS 6 as compatible with our MKi products for A2DP and AVRCP.  We are currently testing the iOS 6.1 beta, and I have no information as to how that testing is going."

     

    Thanks goes to Parrot support for acknowledging the issue and at least looking for a solution (even if it is just by testing Apple's 6.1 beta).

  • Dr Agonlord Calculating status...
    Currently Being Moderated
    Nov 29, 2012 3:47 PM (in response to William Kucharski)

    It's not apples fault that when they updated iOS, things that used to work no longer do.

    Apple Products are not expensive.

    The antennae gate issue was made up by the press.

    Fan boys do not exist. Only people who believe apple is the only product worth having. If a product no longer works with a new apple device or iOS, then it is because the non apple device is obviously not an apple.

    These are not the droids we want.

    Android handsets and tablets are not a threat. Apple devices are perfect.

    You can be on your way.

     

    Nope. I can't leave it there. 

     

    The only people who may not object to the problem are likely to be those unaffected by the problem. I find myself wondering if wk is one of those unaffected and is perhaps unable to fully understand the frustration we are feeling.

     

    We get nowhere generally disagreeing. It merely makes things ever more annoying when in trying to get a point over, somebody fails to appreciate it as being a problem related to apple in any way. The fact is TH

    RE IS STILL A PROBLEM.

     

    So in the clearest way possible. My car stereo workd fine with ios5x. Controls worked from the steering wheel just fine. IOS 6 made things go wrong for my personal setup and until somebody changes something at either apples or pioneers end, then there is nothing I can do to fix it EXCEPT change the head unit or the phone. It is not a user fixable error that can be addressed in any other way.  In my case, and those of others in the same boat, apple WERE responsible for OUR PARTICULAR problems at this time.

     

    It worked, now it doesn't. That is the point, regardless of anything else. I don't care what the new Bluetooth standard brought to the party, I am one of those who got an unwelcome gate crasher who came along and ruin the party altogether. I would happily go back to ios 5 if I could so that I could get the old WORKING (for me) standard rather than the new and USELESS to me version.

     

    There are people here trying to get the point over that something they once had is now gone, and for many that is a potentially expensive loss if they need to replace something to get things working again.

     

    Apple may not see it as their problem, some users may not see it as apples problem, I definitely see it as apples fault REGARDLESS of where the incompatibility of MY devices is concerned.

  • bprecey Level 1 Level 1 (0 points)
    Currently Being Moderated
    Nov 29, 2012 4:06 PM (in response to nikB123)

    My biggest problem is that Apple did this update. I struggle to believe that it was not flagged during beta testing yet Apple did not warn anyone. They then allowed people to innocently upgrade to IOS6 and offer now way back so people are now stuck on IOS6 with these problems whether they like it or not!

     

    So like most others, I blame Apple. It's seems arrogant to me that Apple ignore this. It's easier for them to deal with this than numerous manufactures irrespective of who to point the finger at.

     

    Thankfully, in my case, I had a 4S just inside a year old and took it to the store. I told Apple that I wanted IOS 5.1.1 back which, of course, I was told was impossible. I immediately asked for a replacement as their software made my phone faulty. Luckily they didn't disagree and I got a new one back on IOS5.1.1.

     

    Until this issue is resolved, I'm not changing to IOS6. I still have Google Maps too! ;-)

  • apu2009 Calculating status...
    Currently Being Moderated
    Nov 29, 2012 4:33 PM (in response to nikB123)

    I'm getting tired of nothing happening. I decided to get the Nexus 4 as soon as I can and be rid of my iOS 6 device as my primary cell phone. I'll keep it as a backup for traveling, hopefully with iOS 6.1 the issue will be fixed.

     

    Meanwhile, Pioneer's page hasn't changed at all and it keeps saying "FW updated TBA".

  • crankerchick Level 1 Level 1 (5 points)
    Currently Being Moderated
    Nov 29, 2012 4:33 PM (in response to bprecey)

    "My biggest problem is that Apple did this update. I struggle to believe that it was not flagged during beta testing yet Apple did not warn anyone. They then allowed people to innocently upgrade to IOS6 and offer now way back so people are now stuck on IOS6 with these problems whether they like it or not!"

     

    I actually agree loosely with this. It is infuriating to think that Apple knew about this, which they supposedly did as it was brought up by beta testers and possibly even hinted at by Apple (as posted previously but seemingly in relation to a different update) and basically it was just allowed to go. Regardless of who the problem lies with, the reality IS that it was brought on with iOS 6 and if something is knowingly going to get borked, it's nice to be made known about it and make a choice. Of course, that would never happen, so it is moot anyway, but it still feels good to say it.

     

    William K has fervently and repeatedly referred to the Mazda example as a previous indicator that a fault can lie with the OEMs of the Bluetooth devices, and there is no denying that example. That said, this particular problem isn't with one single manufacturer, so the example serves no more purpose than to just say, it's possible it isn't Apple's fault, and I will concede that. Some of you all need to concede that point as well. It IS possible that it isn't Apple's problem. Perhaps other OEMs aren't following the standard exactly and Apple is so their stuff broke up in the update.

     

    That said, we would ALL be better off if Apple would do something to remedy the situation, as clearly they have the juice for the configurations to work, since they worked in the past. As was also pointed out, though, that also isn't likely to happen.

     

    Apparently, pride goeth before the customer.

     

    I have given up hope on this. I don't think my brand new 2012 car that i could FINALLY do avrcp 1.3 with once I got the iPhone 5 but STILL can't do it because of this issue will be updated to make it work and I think Apple has spoken clearly (by not speaking or patching it in 6.0.1) that they aren't touching it. , Maybe I'm just cynical.

     

    I did send some more request to ore mobile news outlets that I follow, though, in hopes of getting this talked about even more.

     

    I will be calling Acura back soon to find out if there is anything new to report since last month.

  • crankerchick Level 1 Level 1 (5 points)
    Currently Being Moderated
    Nov 29, 2012 4:34 PM (in response to apu2009)

    I hope you don't have any issues with Bluetooth on the nexus 4, because apparently Bluetooth is broken on that too!

  • apu2009 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Nov 29, 2012 4:36 PM (in response to crankerchick)

    Haha that's a good point. I'm hoping there aren't, but if there are then I won't be any more screwed than with my iPhone 4 and I'll have a nice open OS to play with (can't wait to play with NFC tags)

  • William Kucharski Level 6 Level 6 (14,405 points)
    Currently Being Moderated
    Nov 30, 2012 1:37 AM (in response to crankerchick)

    crankerchick wrote:

     

    William K has fervently and repeatedly referred to the Mazda example as a previous indicator that a fault can lie with the OEMs of the Bluetooth devices, and there is no denying that example. That said, this particular problem isn't with one single manufacturer, so the example serves no more purpose than to just say, it's possible it isn't Apple's fault, and I will concede that. Some of you all need to concede that point as well. It IS possible that it isn't Apple's problem. Perhaps other OEMs aren't following the standard exactly and Apple is so their stuff broke up in the update.

     

    That said, we would ALL be better off if Apple would do something to remedy the situation, as clearly they have the juice for the configurations to work, since they worked in the past. As was also pointed out, though, that also isn't likely to happen.

     

    Once more, here's the deal:

     

    Those manufacturers are releasing fixes.

     

    They wouldn't be spending money and engineering time if it was an Apple bug, they'd just wait for Apple to fix it.

     

    If they're releasing an update, it's a bug in their code.

     

    Apple can't "remedy the situation" if it's not their bug; they're adhering to a published standard and aren't responsible if other manufacturers didn't or don't.

     

    All it would take is one person out there with a Bluetooth sniffer/protocol analyzer  to post what Apple was doing wrong and how it diverged from whichever protocol it was diverging from, and it would be all over Slashdot, Gizmodo and the way things have been lately, the network news (with the person responsible likely getting a fair amount of PR themselves if they so desired.)

     

    None has, and believe me there are many, many people on the net who would happily do so as they're not Apple fans.

     

    Blame Apple if you like, but if it's an incompatibility with say the latest version of AVRCP, when Android phones begin shipping with that version they won't work with those head ends, either.

  • Saphod Level 1 Level 1 (0 points)
    Currently Being Moderated
    Nov 30, 2012 2:07 AM (in response to William Kucharski)

    Hope I am not repeating something that is known already:

    http://www.pioneerelectronics.com/PUSA/Apple+Compatibility

     

    Pioneer head units seem to need updates ( found here: https://discussions.apple.com/thread/4327399?start=15&tstart=0 ).

     

    I don't actually care any longer whose fault it is. I just want it too work.

     

    Mazda? Apple? Anyone?

  • bah434x Level 1 Level 1 (10 points)
    Currently Being Moderated
    Nov 30, 2012 2:45 AM (in response to bah434x)

    I dont think Apple is completly to blame here....

     

    I posted the Alpine update as i have just bought one of these units for my daughter and found this issue in the forums by chance so asked the question of Alpine...I havnt even installed the unit yet...

     

    However we both own iPhone 5's with IOS 6.01 installed.. so wanted to make sure there was going to be a resolutiion...

     

    I myself have a VW headunit in my VW Golf that has bluetooth audio and bluetooth hands free and this has worked faultless with all iphones and IOS versions....

     

    So cant really blame the IOS for the issue completly.

1 ... 38 39 40 41 42 ... 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.