Q: bluetooth music issues after iOS6 update
-
Dec 3, 2012 8:48 AMby jpblanchard01,What about the problems many of us are having where our APPLE iPhone was communicating perfectly with ourbluetooth devices and IMMEDIATELY after installing iOs 6.01, the Bluetooth connections stopped working flawlessly. How can that NOT be APPLE's issue and problem. APPLE should be doing everything within their power to fix the problem.
-
Dec 3, 2012 1:51 PMby ctun88,There are multiple posts on the alpine facebook page, that this issue is being worked on, and a fix should be announced soon. I sent a message to Alpine and was informed that it should be soon, though they would not issue an exact or estimated date. Hopefully soon..I'm facing the same issues.
-
Dec 4, 2012 1:38 PMby rustykerr123,Because technically it is not Apple's issue. Just because Apple fixed their code to comply to the standards does not make it their problem. Yes, I am upset about this issue as well, I have been affected with my brand new stereo (at the time of the update it was a few days old). Yes, it would be faster and easier for Apple to fix the issue, but then they have the same issue of the code not being standard again. I would like this issue fixed as well and I believe that each stereo manufacture releasing a firmware update would be best, then everything is made under the standard rather then what works. Maybe after the updates, they would be able to use some of the new Bluetooth features as well, such as the messages.
Or better yet maybe Apple should just start making headunits and solve the whole issue that way, I at least think that would be very interesting to see how Apple would push the market.
-
Dec 4, 2012 2:14 PMby Dr Agonlord,They could have done things better. Maybe Have the firmware default to the previous working version if an error was met rather than just be incompatable. Or perhaps give users the option to select a working standard rather than be forced to have things in an inoperative state.
As to the problem reoccurring, if the option to choose were there, there would be no issue and no reoccurrence. A shame that so many users get shafted by this move forward win he Bluetooth standard.
-
Dec 4, 2012 2:24 PMby rustykerr123,It would be nice if they were able to do this, but there are 2 problems I can see without much thinking.
1. This can cause more problems when people think they know better then the iPhone that really don't, I they change it to a standard that really is not supported on their device it will not work then they will complain to apple, this is more a debugger/developer feature and should not be there for all users.
2. This would put them back into non standard protocols which they are trying to get away from and push everything "made for iPhone" away from as well.
-
Dec 4, 2012 2:29 PMby gorkemfromsea,Every new version of a standard is backward compatible. Like HTML5. Browsers support HTML5 still support HTML4.1. That's basically why we have standards, standards have room for improvement but are also backward compatible...
Same goes for avrcp 1.4, it is backward compatible with avrcp 1.3 It is Apple who did not implement it as backward compatible.
http://en.wikipedia.org/wiki/AVRCP#Audio.2FVideo_Remote_Control_Profile_.28AVRCP .29
-
Dec 4, 2012 3:59 PMby William Kucharski,Same goes for avrcp 1.4, it is backward compatible with avrcp 1.3 It is Apple who did not implement it as backward compatible.
http://en.wikipedia.org/wiki/AVRCP#Audio.2FVideo_Remote_Control_Profile_.28AVRCP .29
A standard requires compliance among both sides of the connection.
It is the head end manufacturers who did not code their Bluetooth stacks properly; we have no proof that Apple did anything other than correctly code to AVRCP 1.4.
-
Dec 4, 2012 4:18 PMby rustykerr123,I thought that it was clear that it is not a backwards compatibility issue any more. Some headunits work and some don't, and Apple has said it is a problem with the headunits and bluetooth standards.
William Kucharski wrote:
It is the head end manufacturers who did not code their Bluetooth stacks properly; we have no proof that Apple did anything other than correctly code to AVRCP 1.4.
That is true, I never realized that before, I am sure my old sony stereo works perfect, except for metadata (but that never worked or was not supported), My nice pioneer does not.
-
Dec 5, 2012 6:35 AMby craigmash,Add my voice. My Motorola S305 bluetooth headphones connect just fine, but I lost music control. Not sure if it happened with 6 or 6.0.1. But they worked great for YEARS with my iPhones.
Since I use these for running, having music control is very important to me. Guess I must hope for a fix from Apple since I know the headphones don't get any updates.
-
Dec 5, 2012 6:39 AMby crankerchick,craigmash wrote:
Add my voice. My Motorola S305 bluetooth headphones connect just fine, but I lost music control. Not sure if it happened with 6 or 6.0.1. But they worked great for YEARS with my iPhones.
Since I use these for running, having music control is very important to me. Guess I must hope for a fix from Apple since I know the headphones don't get any updates.
I have these same bluetooth headphones and they work fine with my iPhone 5, 3rd gen iPad, and 4th gen iPod Touch all running iOS 6.0.1 (and worked fine on iOS 6 too). The controls are fully functional for me and the music streams fine with no dropouts.
If you haven't already, you might try deleting the pair, pairing it again, and perhaps even a factory reset just to be sure.
-
Dec 5, 2012 6:40 AMby deepcover,No. It's actually not like that at all. The Bluetooth issue has to do with a standard that both Apple and the third party stereo manufacturers have to abide by. Since Apple has already stated, for all intents and purposes, that it's not their fault; and stereo companies have already been pushing out fixes, the only thing you can really do is wait on your stereo company to release a firmware upgrade.
