I talked with Apple Cust Svc this morning and they ran me through a couple of possible fixes to no avail. They are aware of the problem and are working on a programming fix in a future patch.
I would think that they would know better than to disable EVERY device running IOS 6 for Bluetooth Radio/Pandora.
This is Apple's issue with Apple's AVRCP not being Backward compatible...
Apple can Address this with a iOS 6.X Patch Update or ALL of the other Manufacutrers of Bluetooth Devices can Update their Firmwares... (good luck with the later!!)
According to the AVRCP, the Latest Version Keeps the functionality of the Previous Version?????
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
I called Alpine "Customer Service" a few minutes ago regarding the problem. I have a CDE-W235BT head unit. They were less than useless. The rep told me they didn't even know if it was an Alpine issue or an Apple issue. I wonder if the Samsung's Galaxy S3 is having this problem. Might be time for me to look into another platform.
Here's an update for all Pioneer people. It's the basic not our fault, but their fault. ViceVersa for Apple. Just got off the phone with Pioneer, and they said that were pretty much out of luck. They're working on stuff, but the new Lightning Connector transmits audio Digitally now, instead of analog signals. The decks can't read it. So if you have or spent a bunch of money on a new deck from Pioneer, you're out of luck as far as using the iPhone 5. If you updated to iOS6, they said they are working on an update to have it work with the decks.
As far as bluetooth streaming, same deal. Pioneer claims Apple changed their bluetooth, so it's not compatible. Apple says it's Pioneer who has to update their decks. This would ultimately fix the Artist/Title info showing up on the deck, as well as gain controls again.
Basically, if you got an iPhone 5, and spent a ton of money on a new Pioneer deck like me (AVH-P8400bh) you're screwed. I hope i'm wrong though...
I believe you are half right and half wrong. If you connect your iPhone 5 with the cable included with it and read the iPhone as a device, it would work, it would be looking at it as an audio file and the stereo does the work, however, if you rely on the special cable that you buy septerately, the one with the USB and 1/4" connector,you might be out of luck. I could be wrong as well, I have the 4400bh, I have not used it yet, just installed it, but my last stereo was a sony and the USB connection worked as a data device.
You might be able to purchase the adapter to make it work as well, it is only $29.
When iOS 5 was released, there was a Bluetooth bug with the volume. Apple released an update for the volume problem about six weeks later if my memory serves me correctly.
Showing they will fix it if it's their bug; we just don't know yet.
If you have a device with the issue, report it to AppleCare; if it's not Apple's bug Apple will forward the reports on to the vendors.
Quite frankly, I suspect Apple and/or the vendors already have it root caused unless it's something not common to all iOS 6 devices (e.g. if upgraded iOS devices fail, but new ones do not.)
Note that many had similar issues with Mazda head ends and iOS 5:
and that issue turned out to be:
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.
One can imagine their firmware might have been written with a statement such as "if AVRCP_VERSION == 1.3" rather than ">= 1.3."
Since the version of AVRCP supported has, to the best of my knowledge, remained 1.4, it's unclear what features/differences may be confusing units talking to iOS 6.