The past couple months with my new Sprint Galaxy Nexus on stock I've been able to stream rdio to my car's audio over bluetooth. I wanted to try AOKP on the device, though, so I did, and much to my chagrin, rdio no longer streams over the bluetooth :\
What DOES work:
- Calls over bluetooth
- Google Play Music player over bluetooth
What does NOT work:
- rdio over bluetooth
The bluetooth is connected, and rdio starts playing (the time indicator moves) but there is no sound coming from my car speakers or from the phone speakers.
Anyone have any thoughts/ideas/explanations/suggestions, or is anyone else experiencing the same thing?
Any help would be appreciated,
Thanks for writing in. We don't anticipate any issues using Rdio on custom ROMs, but sometimes issues are reported with certain builds. I've not heard of this behavior particular behavior from other custom ROM users, but I'll share this report with the rest of the team and see if I can gather any more helpful information.
There may be some support information on the Open Kang Project website (http://aokp.co/index.php/news), or on their forums (http://rootzwiki.com/forum/424-aokp/) if you haven't checked already
Let me know if you have any updates on the issue, and I'll let you know if I hear any other news.
Hi Mike, Thanks for your response
I went to the AOKP people before coming here, and they helped me narrow things down a bit. They seem to think it's an issue with rdio being incompatible with AOKP's stereo bluetooth stack. Since other apps audio work (including Google Music), they think it's an issue with rdio.
It'd be nice if I wasn't the only person having this issue though.. I guess the combination of car bluetooth + rdio + aokp is pretty rare.
Thanks for following up with that report. I haven't been able to find any more information as to why Bluetooth isn't working with your particular setup, but we've had reports of various Bluetooth compatibility issues due to the variety headsets or car stereos out there; it's something the team is looking into optimizing in future updates. We appreciate you sharing your findings, and we'll let you know if we have any updates on this.
Just wanted to say I experienced this exact behavior with the CyanogenMod 10 nightlies on my Verizon GNex - hopefully it will sort itself out as things are updated!
It looks like the problem is that any app that doesn't support AVRCP 1.3 is susceptible to this problem. There's a few threads discussing it here:
Any chance Rdio could be updated to support the 1.3 profile? :)
Thanks for the info, I'll get in touch with the team about this.