I have a strange problem using A2DP with non-stock ROMs. Basically, the device will pair and the music player will start playing the track but no sound comes out. This happens with all apps except for the Apollo player that comes with the ROM. I can get audio on another ROM to temporarily play on another app if I use the search function within Apollo but it stops the audio after exactly 5 seconds (although on the app the playback continues). I think it is somehow related to BlueZ because I had this problem on my old phone (G2X) as well. If I use a ROM based on stock everything is fine.
Related
Hi. I am absolutely clueless with this.
I am used to having my phone paired with my car stereo which acts both as a headset and as a multimedia playback device. Im using this for a couple of years now and been doing that with iPhones, Galaxies and now the Atrix nad this has never happened before.
This is the problem. Ever since I updated to Gingerbread when I answer a phone call with my car stereo, and end the call, the default Music player on the android pops up and starts playing whatever is on the playlist. I can try and pause the audio and it will play again in a few seconds. I can even force close the app and it will pop open back again. It happened with the old Music, with the new Music (with Google Music support), with Grooveshark, Winamp, you name it.
Figuring it was happenning because of a faulty ROM I installed every single GB based rom out there, including the leak version, the official version, Kenneth's beta 4.5, Kenneth's Alien ROM.
I have factory reset and tried installing everything manually (not restoring through CWM or Titanium). No fix.
Any clues?
Any thoughts on this? Thank you.
I've found that the music player only works when no pre-installed or Google apps are on auto end. IDK why, but it has to do with interconnectedness.
The media player is reacting to the media pairing event as if a button was pressed.
I trap this using a Tasker profile triggered by the bluetooth connection to my car kit; the entry task grabs Media Button Events and the exit task releases them. This stops the media player launching.
Monkey see, monkey do.
If thats the problem then try headset interceptor and choose the app you want the button presses to be sent to...worth a short. Free app in the market.
Sent from my MB860 using XDA App
I havent seem to run in to anyone with this issue.
I pair my phone to my car stereo fine in the stock GB rom. Play music and talk on the phone endlessly.
But with any ICS version so far, even official. It causes reboots, randomly.
Am I the only one suffering from this?
Not the same, but something similar.
I can connect with my car stereo, have to do it twice (once for music streaming and once for handsfree). Once connected, i can stream music fine. Even the controls on my steering wheel work. When I receive a phone call sound is muted and i can talk fine as well.
After I hang up the phone, the music doesn't come back, only a 0.5 second stutter every 2-3 seconds. On my phone, in the music player I can see that it's my phone that has the problem; the visualisation displays exactly how i hear the sound.
This behaviour also occurs when I turn off my car and turn it on again.. there doesn't seem to be a single thing that i can do to get music to play again, just some fiddling usually gets it to work (but then i have to stop my car first before i can have music..)
If anyone has any ideas for troubleshooting let me know!
I honestly think ics has compatibility issues with certain bluetooth devices.
We can only hope they realize this and take measures to correct it.
Gingerbread is flawless.
Sent from my GT-I9100 using XDA
Just a notice that this seems fixed for me now.
I've upgraded to the 4.0.4 Rom found here: Click!
Next to this i'm using the app "doubleTwist"
ICS talks a different language then gingerbread when it comes to A2DP, especially for the play/pause commands, which seem important to me..
A2DP issues
I find I have similar issue. I have a SONY bluetooth deck in my car and my phone will lock up and force restart mid song or mid phone call.
Anyone have any ideas apart from flashing that 4.0.4 Rom
I'm having no audio when I connect my phone to the car through Bluetooth. I do have call audio both ways but I can't play music or sounds. Phone doesn't say anything, acts like it is playing music but no sound. I'm using task650's aokp 4-4-2012.
Also, I can't install Samsung apps, there are some apps there I use. Any way to get it working?
Thanks for reading.
I have the same issue. I found the work arround by open music app then make a call after you hear ring disconnect phone and try running music again. Some how it works for me..
bluetooth is working fine here.
i use pandora and make calls over my head unit in my car. no issues at all
samsung apps? you arent going to be using samsung apps in aokp.....
I have been using 4-14-2012, Build 31, and now 4-18-2012, and each one the Bluetooth audio works. I would recommend updating to a newer version and try again.
Also, most of the Samsung apps hook into touchwiz or back end services that are not in AOKP.
I just installed CyanogenMod 10.1.2 Stable (via SafeStrap 3.11), everything went perfect. A couple days later, I finally went to re-sync my phone to my PriusV's Entune system to play music via Google Play Music (with playlists stored locally on the phone).
Music plays back OK, however my issue is that no song details (Track title, artist name, disc name, playback position) will display on the Entune screen, and none of the car's control buttons (play/pause/next track/prev track) will do anything. I don't want to have to pull out my phone to change tracks or see what song just came on while i'm driving when this is what the details and controls on the car are supposed to do for me.
Anyone out there have any thoughts/ideas/suggestions/possible fixes?
neoramasay said:
I just installed CyanogenMod 10.1.2 Stable (via SafeStrap 3.11), everything went perfect. A couple days later, I finally went to re-sync my phone to my PriusV's Entune system to play music via Google Play Music (with playlists stored locally on the phone).
Music plays back OK, however my issue is that no song details (Track title, artist name, disc name, playback position) will display on the Entune screen, and none of the car's control buttons (play/pause/next track/prev track) will do anything. I don't want to have to pull out my phone to change tracks or see what song just came on while i'm driving when this is what the details and controls on the car are supposed to do for me.
Anyone out there have any thoughts/ideas/suggestions/possible fixes?
Click to expand...
Click to collapse
I have a Highlander without Entune (Stock Stereo), so it's not a direct comparison but here's what I found. Music details don't display on the stereo. I've tried countless apps/hacks but nothing has worked. They spent all their dev $$ on getting it to work on the iPhone and left Android users in the dust. So I'm not sure music details have ever worked with Android.
The steering wheel controls however work fine for me, so that's strange. In the bluetooth settings on the phone, when connected to the stereo, is 'media' connected? It should be.
I wonder if an updated bluetooth controller for android would fix this issue for everyone?
I suppose I should clarify a bit - when i mentioned this being after installing CyanogenMod 10.1, I was assuming that one would take it things were working under stock, which was the case.
So: Stock - bluetooth playback showing track/artist/disc information, position in the song, and car controls worked (though stock had an older version of Google Play Music, so this could also be a source of conflict)
CyanogenMod: bluetooth only plays music, does not display any of the other information, and controls do not work. (Cyanogen 10.1 comes pre-built with the newer version of play music, so downgrading would be.... difficult and i'd rather try and make it work without doing so)
I guess what I want to try and find out is if it is CyanogenMod or Google Play Music's new version that is next to incompatible with Entune. With Stock, I had near 100% functionality (only shuffle/repeat toggles did not work - but even those don't work right with my wife's iPod, so i'm not worried about those functions).
Since i'm essentially dual-booted through SafeStrap, I may try going back on Stock, updating Play Music, and testing - if updating Play Music causes Stock to loose functionality equally, then i guess i'll have my answer - obviously i'll post back with results.
If functionality is still present on Stock after updating play store, then that traces it back to being something with Cyanogen, and the bluetooth driver it uses.
OK - sorry for the back to back posts, but I got lucky on some digging and found my answer.
CyanogenMod does not have something called AVRCP (Audio Video Remote Control Profile) revision 1.3+ built into it's bluetooth stack. This is because that is not something that is included by default under AOSP 4.2.x. So unless you want to build your own bluetooth stack and put it into Cyanogen, you're not going to get track info/controls.
Google has announced that under AOSP 4.3, they will be building Bluetooth version 4 support into Android, and version 4 supports AVRCP 1.3+ natively, thus Cyanogenmod's next version based off of AOSP 4.3 will then contain AVRCP support.
So, the short of it is, hang in there for the next major release of Cyanogen and all will be resolved!
Most manufacturers build AVRCP support into the bluetooth stack for their devices, hence why stock worked and now CyanogenMod does not.
Huh good to know. I knew that Android 4.3 included an upgrade to BT, but I didn't realize it would fix this issue. I wouldn't even know how to build my own BT stack, but it would be useful in the long run.
+1 on this
I have a Nexus 4 with CM 10.1.2 connected to my Skoda Octavia built-in bluetooth. I play music with Apollo (Cyanogenmod's music player) and I get to hear the songs and can skip to the next/previous songs with steering wheel controls but don't get to see the song title/artist info.
My Nexus One with CM 7 however does play music fine and shows all song details and steering wheel controls work fine.
So based on 1.) the fact that my 3.5 year old Nexus One (with CM 7 - Android 2.3.7) shows song details fine and 2.) the excellence of the CyanogenMod team, I think this can be resolved with some coding rather then waiting for Android 4.3 or CM 10.2 with an updated bluetooth stack.
Unfortunately I can't say if this issue only started appearing after the 2 security updates (10.1.1 and 10.1.2) since CM 10.1.2 was the 1st ROM I flashed on my Nexus 4. Although in this post goo.gl/KQ6J7H some guy who encounters the same issue, also experienced the issue on CM 10.1 (so before the security updates 10.1.1 & 10.1.2).
Apart from the song details not showing, I also noticed that sometimes I can't enable bluetooth at all and need to reboot my phone for it to work again. When tabbing the bluetooth icon in powercontrol widget or even directly in Settings it simply won't enable bluetooth. Also experienced by the guy from post goo.gl/KQ6J7H
I'm hoping to see this annoying bluetooth issue resolved asap.
So this is a little hard to explain.
***EDIT: ITS ANY APP THAT USES INTERNET FOR AUDIO THAT COMPLETELY STOPPED BLUETOOTH***
I tried to use youtube to play a song over bluetooth and it completely locked up the app and I had to force close ON THE NEW PHONE AND OLD PHONE
AND NOW IT JUST MADE THE PHONE RESTART BY ITS SELF
Is this a rom problem?
The other day i was trying to listen to some music using a cracked version of spotify that I've used for over a year with no problem. The audio randomly stopped working, so I tried to just use the stock music player because I was going to an area where I didnt have any service anyway. The stock music player wouldn't work. I made sure it was playing by looking at the seek bar and it would sometimes start at 0:01, then jump to 0:05 and so on but no audio was coming through. The only way to make system audio work again, is to completely restart the phone. I uninstalled spotify, and the problem never came back until I reinstalled spotify with a different version, hoping it'd fix the problem. It hasnt. So, I decided to use a different phone but the same model phone, rooted, with the same rom, and it did it again. ON A COMPLETELY DIFFERENT PHONE. I don't know what happened, but even on a clean flash, with no other apps installed, spotify kills my bluetooth and system audio.
What the hell is going on?
The android version is 4.4.2, and it's a stock rooted deodexed rom.