Previous 1 29 30 31 32 33 Next 1,017 Replies Latest reply: Dec 13, 2014 8:58 AM by Wofatt Go to original post Branched to a new discussion.
  • kz5fhz Level 1 (0 points)

    Util the next upgrade, of corse that will be the vendors fault as well.   Obserd notion thinking that it could be Apple,  Forgive us for even bringing up the idea.


    It couldn't be that they are already set up for the next Rev of Bluetooth or anything....

  • N3ilxb9394 Level 1 (0 points)

    I have the 4400 too and I'm pretty ****** about it... U figure out a solution?

  • William Kucharski Level 6 (14,985 points)

    kz5fhz wrote:


    Util the next upgrade, of corse that will be the vendors fault as well.   Obserd notion thinking that it could be Apple,  Forgive us for even bringing up the idea.


    I know you're trying to be funny, but you're correct; if the next update breaks headends, that too will be the vendor's fault as the standard is backwards-compatible.


    By the way, just as a reminder, Apple changed to AVRCP 1.4 back in iOS 5.0, so the current iOS 6 issue is something entirely different than that.


    At the time this broke some Mazda headends as such:

    10-Jul-2012 02:19 PM Apple Developer Bug Reporting Team :

    Engineering has provided the following feedback regarding this issue:



    We discussed this issue with the manufacturer. They acknowledged there is a critical bug on their platform, as they require the phone to support no more than AVRCP 1.3. Because iOS supports AVRCP 1.4 since 5.0, they do not enable & use any AVRCP 1.3 feature. The bug has been fixed on their newer platforms.

  • kermit4161 Level 1 (0 points)

    Lets hope that the update (next Tuesday most likely?) will address this. I agree, if AVRCP 1.4 was back in iOS 5, then something else broke. My head unit worked perfectly with iOS 5. Hoping to see some fixes come Tuesday!

  • spanks127 Level 1 (0 points)

    Since apple was mute about this issue, I returned my 5 on wednesday of last week, and I also submitted to return all of my company 5's which they are sending me new replacement phones first, then I mail them back.


    After being an apple fan boy for so many years,    I can only say this after four days with my HTC one X: 





    Now I see what everybody was saying for years, and I was just being the fan boi and arguing for apple.


    Good luck guys, I hope Apple eventually fixes your problems,  and I did my job by returning (and in the process of returning) $4200 in phones and accessories.   Surprisingly, since I was "a long term customer", AT&T is even refunding me for all the stupid new cables and adapters I paid for.    Thanks AT&T.

  • fjr_birddog Level 1 (0 points)

    No solution exists.  Either the third party manufacturers will issue firmware updates to comply with Apple's changes, or Apple will release an IOS update fixing what they broke.


    A very, very poorly issued IOS6.


    Fingers crossed for a solution soon.

  • crankerchick Level 1 (20 points)

    That is all people can do, either return the phones or wait it out. The One-X is a great phone (beautiful screen) and it may be blasphemous to say around here, but Android 4.0+ is a great OS with many many more capabilities over iOS. There's no real "best" phone these days, only what works best for the user.


    That said, you returned phones that didn't have AVRCP working right for an Android phone that, I believe, doesn't support AVRCP 1.3 either. Has HTC implemented it as an addition, or are you just going "AVRCP-free" now?

  • spanks127 Level 1 (0 points)

    Took me fifteen minutes to have working AVRCP on my one-x.  

    The reason for me returning the phone was NOT the fact AVRCP  wasn't working on my iphone 5, the problem was that apple did not give us a time frame it would be corrected. If I would have waited past the 30 day window from AT&T for returns, I would have been stuck.  What happenes if apple never fixes the problem?     I now have beautiful streaming data on my head unit via blue tooth, and I once again have control over the phone's audio output via my steering wheel...   Sadly, my fix involved leaving apple.

    It is not right for me to go into details about the pro's of switching to non-apple devices on apple's website,  but I will say this, even if you are a die-hard fanboi, try one out.    You might be surprised.      Plus, my battery is sitting at 83% right now... That is about 40% more than my iphone 5 has even been at this time of the day.   

  • Coasterby Level 1 (0 points)

    Spanks, for those of us potentially interested in switching to an Android device, can you give a quick explanation of how you got AVRCP working on the One X?  It was my understanding that AVRCP control features are not available on most Android devices, but I've heard rumours that they're available on the Galaxy S3.  Thanks in advance.

  • crankerchick Level 1 (20 points)

    You are better than me, because it's the interwebs and I will have a conversation on whatever topic I please on whomever's site I please. :-)


    I'm an Android user also, but sigh alas my current Android phone has crappy battery life and no AVRCP without root and a custom ROM, and even then, it only works on the stock music player (not Pandora, Spotify, etc), which is pretty useless for me as I don't use my Android devices for streaming music I already own.


    My iPhone 5 is getting exceptional battery life compared to my current Android phone (and similar to my previous Android phones).


    I totally understand your switch. Being left in the dark with no comment, even to say "This is a manufacturer problem, not our [Apple's] problem," is better than nothing at all. Gotta do what you gotta do.

  • spanks127 Level 1 (0 points)

    Coasterby,  my fiance's brother is a droid geek.   I should have stated he rooted it for me and it was done.  I looked at many phones that supported AVRCP, and none of the compared to my final choice..





  • Coasterby Level 1 (0 points)

    Thanks Spanks.  Also, for those interested, here is a response I received from Parrot support this morning (after emailing them twice with no response):


    "The engineering team is currently working on this issue.  Unfortunately this was a result of a last second change in the public release of iOS 6 by Apple that led to this."


    We all knew something was up with the vendors being caught off guard by this, and this confirms it.

  • apu2009 Level 1 (0 points)

    I just saw this: ctively-tested-ios-6.1-expected-after-christmas-holidays/


    Are there any people with access to that beta firmware that can confirm if the issue has been fixed?

  • spanks127 Level 1 (0 points)

    Coasterby, I don't believe that for a second.   ios6 beta had the same issue, an there are countless people talking about it WELL before the release to the public.


    And I'm talking about July.... 

  • deepcover Level 1 (0 points)

    I'm not interested in rooting an Android phone. I'll just wait for Apple to fix it. They always release a fix after a major release.  If they don't fix it then, I'll be ******. Right now I'll be patient.  Everyone knows Apple takes their time to issue releases, but they usually address most issues when they do.

Previous 1 29 30 31 32 33 Next