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

    Just found this online:  For those that don't want to follow the link, here's an excerpt from the page:



    "This update will address the issue of the iPhone 5 and or Apple devices running iOS 6 not working correctly with A2DP controls (AVRCP). The iPhone 5 and iOS 6 is not backward compatible with older versions of Bluetooth software in some models. This update has been released by Parrot especially for Advent OE radios ONLY to address this issue."


    I'm guessing this page was very recently put up.  Looks like Parrot might be prioritizing it's third-party vendors above its own customers.  As far as I know this is the first firmware update relating to the iOS 6 issue that has been released.  Be careful as Advent makes it clear that this update is intended for their radios only.

  • William Kucharski Level 6 (14,985 points)

    fjr_birddog wrote:


    Yet a hardware/software compatibility issue that COULD NEVER HAVE PASSED TESTING WITH APPLE OR THE AFFECTED MANUFACTURERS remains unaddressed.


    Let's see, that would require Apple to own one of every device ever made, or the manufacturers to use one of the developer seeds of iOS 6 that were available for months before its release to the public.


    Apple presumably did their testing (and if the newer spec contradicts the old, it's always best to conform to the newer version), so where were the manufacturers?


    It's not good that this compatibility issue came up, but we still don't know where the burden for correction lies.


    (Parrot's move, like Kenwood's, seems to also imply it's a bug on the part of the device manufacturers.)

  • Feek Level 1 (0 points)

    I emailed Alpine again today.


    This is the reply I received:


    "Hi we have updates for the 2 din units, the single din will follow, probably around next week...

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


    So hopefully it won't be long now.

  • crankerchick Level 1 (20 points)

    For anyone with a 2012+ Acura TL, I just got off the phone with Acura again and got some new information. They do have reports of bluetooth issues since the iOS 6 update. They haven't tested the iPhone 5 yet, but they have received reports of issues with it as well.


    They will be testing the iPhone 5 with the vehicle in November for compatibility, but they have already received reports of issues with the phone, from simple pairing issues and audio dropouts. For Tech owners, they have had reports of those problems as well as, of course, no metadata for songs.


    This particular representative said that traditionally with Apple they do NOT receive the phones prior to release. The plan is to test it throughout November, notate what has issues and drill deeper into what is causing it and report the findings. That is traditionally how things are done.


    Lastly, he noted that in the case of non-compliance on Apple's part, the best they can do, of course, is to report that back to Apple. If the issues are on their end, they can and do offer updates for vehicles that can be updated, when applicable. I asked specifically if they have updated things in the past, and if so, how long does it take, and he said yes they have been known to issue updates, but they do take time. In this particular case, due to the popularity of iPhones, issues like not being able to pair at all, have audio on a received call, and basic function issues would most certainly be addressed in some fashion if possible.


    I would encourage anyone with issues to make sure you are reporting the problem to both Apple and your car/stereo manufacturer.


    I stand by belief that the best hope for the fastest fix is from Apple, at least in my case. Perhaps it's different with aftermarket stereo manufacturers, but who knows.


    My opinion, we just have to either sit tight and wait and see or return the phone if it's a dealbreaker.


    Message was edited by: crankerchick

  • deepcover Level 1 (0 points)

    But these issues have nothing to do with the iPhone 5, the change that broke things was in iOS 6.  If Acura developers were really paying attention they would have tested the developer releases against their product months ago when iOS 6 pre-release versions were available.

  • crankerchick Level 1 (20 points)

    Nothing I said contradicts your statment. They are just saying they don't know if there is anything about the iPhone 5 that might be incompatible, regardless of iOS 6 updates, because the iPhone 5 is new and they don't get that particular hardware until after release.


    It's true that they could and should have tested the iOS 6 update when it become available, on iPhone 4S. Unfortunately, I didn't think to ask if it is traditional to test new OS updates or not. That would have been a good answer to know. I'm too lazy to call back and wait on the line now.


    The point is, they aware of some incompatibility between iOS 6 and their HandsFree Link, and they will also be testing the iPhone 5 specifically in November.


    I made sure to mention that my other iDevices worked fine in iOS 5 and *also* broke with the iOS 6 update, for whatever that counts for.

  • deepcover Level 1 (0 points)

    I didn't mean to downplay your report. It was more my frustrations with the car audio companies. Thank you for sharing this information.

  • Dr Agonlord Level 1 (0 points)

    Personally I don't think we should be blaming the car audio companies. everything was working fine. IOS 6 came out and things fell over. Regardless of who is actually at fault for the incompatibility, it was IOS 6 that triggered the failure. Time moves on and things change, progress makes its own incompatibilities ,windows on a pc for example, or new hardware not working with new games. But bluetooth on the iphone has always been berated for its lack of facilities from day one, For something that many of us use regularly (bluetooth) to be tweaked/changed/altered/upgraded or whatever other term you prefer, only to then screw up something important (to us) is careless. I know that Apple cannot check every device out there, but the fact that AVRCP has been kicked in the nuts must have shown some clue somewhere in the developers minds, if not on the test devices they used. How hard can it be to check what devices use AVRCP then ask around a few to see if it will cause trouble rather than just go ahead and release the new stuff and find out later that it screwed the pooch.


    I cant blame Pioneer for what IOS 6 did. When I bought the head unit it worked flawlessly with the iphone 4 on ios5.1.1

    I upgraded my phone to a 5 and obviously got IOS 6. The new phone and IOS doesn't work with the pioneer. It can't be Pioneers fault that an operating system and phone that didn't exist when the head unit was built is now incompatible. well, it could be their fault, but to my mind, IOS 6 broke the connection. If it was (as has been said here) a bluetooth firmware upgrade, then we should at least have an option to go back to something that works. Even if the audio manufacturers do firmware updates for their devices, there will be a lot of disappointed people out there as not everyone has the nerve or ability to upgrade firmware.  Whereas Apple DO have the ability to correct the issue for all those affected now and for those who would be affected in the forseeable future.

  • William Kucharski Level 6 (14,985 points)

    Dr Agonlord wrote:


    Whereas Apple DO have the ability to correct the issue for all those affected now and for those who would be affected in the forseeable future.


    Not at the cost of not working correctly with future hardware, sorry.


    Apple products are generally compatible with the latest versions of standards adopted at the time of their release for the sake of future compatibility.


    If certain manufacturers are locked into older standards, fewer and fewer devices will be compatible with their headends moving forward.


    For example, if were say an AVRCP 1.3 vs 1.4 issue, you don't really think Android devices will stay at 1.3 forever for the sake of compatibility, do you?


    Of course not; within a year or so everything will be AVRCP 1.4, and you'd see a bunch of "My Galaxy S IV doesn't work with my Kenwood car stereo" posts on Android forums.

  • Dr Agonlord Level 1 (0 points)

    so what have we gained with the upgrade?  I appreciate that progress is required, but at the expense of what is working now? is it not possible to run the 2 bluetooth standards in tandem for those who have no access to devices on the new software? not everything outside of apples control will get upgraded, for those who had it working and lost it on their iphone 4 and cannot go back, it must be extremely irritating. Without opening another aspect or repeat aspect of the argument, the bluetooth connection for many is broke. somebody needs to fix it. I don't care who as long as it gets fixed.

  • William Kucharski Level 6 (14,985 points)

    Dr Agonlord wrote:


    so what have we gained with the upgrade?


    For AVRCP 1.4, the standard provides for browsing of multiple media players and basic search capabilities - but it's unknown whether iOS uses those capabilities.


    Quoting Wikipedia:

    Audio/Video Remote Control Profile (AVRCP)

    This profile is designed to provide a standard interface to control TVs, Hi-fi equipment, etc. to allow a single remote control (or other device) to control all of the A/V equipment to which a user has access. It may be used in concert with A2DP or VDP.

    It has the possibility for vendor-dependent extensions.

    AVRCP has several versions with significantly increasing functionality:

    • 1.0—Basic remote control commands (play/pause/stop, etc.)
    • 1.3—all of 1.0 plus metadata and media-player state support
      • The status of the music source (playing, stopped, etc.)
      • Metadata information on the track itself (artist, track name, etc.).
    • 1.4—all of 1.0, 1.3, plus media browsing capabilities for multiple media players
      • Browsing and manipulation of multiple players
      • Browsing of media metadata per media player, including a "Now Playing" list
      • Basic search capabilities
  • F this. Level 1 (0 points)

    I hate to say it, but Apple is really being a bully with their products! They are not playing nicely together at ALL since this latest google maps, no YouTube, and now--no Alpine Bluetooth control! iOS5 works fine with my brand new Alpine CDE-hd138--but iOS6 completely blows.

  • mowog74 Level 1 (0 points)

    F this. wrote:


    I hate to say it, but Apple is really being a bully with their products! They are not playing nicely together at ALL since this latest google maps, no YouTube, and now--no Alpine Bluetooth control! iOS5 works fine with my brand new Alpine CDE-hd138--but iOS6 completely blows.

    I'm guessing that you only hate to say it because this is just the first time you've been affected by it.  But Apple screws over large portions of their customer base all the time. Sometimes the breaking change is more justified than others, like when a new OS is fundamentally incompatible with old hardware but the OS is significantly better because of the new hardware.  In this case with Bluetooth compatibility I haven't yet seen any evidence that the breaking change was necessary in order to support enhanced functionality.  And for what it's worth, I don't consider "being up to date with the current standard" to be an example of enhanced functionality.  In fact, in my case and many others it's quite the opposite.

  • fjr_birddog Level 1 (0 points)

    Ok, it's Wikipedia, so grain of salt...


    But this clearly defines BACKWARD COMPATIBILITY.


    Something's broken in iOS 6.

  • William Kucharski Level 6 (14,985 points)

    The standard is backwards compatible.


    However the vendor's implementation may not be.


    That's one reason why many newer headends are having no issues compared to those that have been out for a few years.

Previous 1 28 29 30 31 32 Next