I've been having problems with bluetooth playback with CM 10.2 and was wondering if I can do anything to resolve/improve it. Basically what happens is when I'm playing music (doesn't matter what player) the song will "pause" for a second and continue playing. This will happen once ever 10-30 seconds during playback and makes it unbearable at times. I saw a few other complaints with other devices and CM 10.1/10.2 and a some mentioned it might be an issue with the bluetooth stack in Android 4.2/4.3. Bluetooth seems to work fine on Stock Sense ROM without issues so something in the Stock ROM's bluetooth is right and something with Stock Android's is wrong (I assume).
Does anyone have any ideas on what it could be (if I'm wrong in my assumption above) and if there is anything that can be done to help resolve it?
Just an update on some things that I've noticed in the past day or two. I was trying to record the problem with the Soundcloud app while playing a song with Play Music. When I had the Soundcloud app recording the skipping only happened four or five times during the songs but as soon as I stop recording and left the Soundcloud app the song would go back to it's normal 15-25 skips. I'm not sure if this is at all relavant but it was something I noticed. If anyone wants a recording just let me know and I'll post a link. Thanks again.
Just in case anyone comes across this thread in the future it seems like the RC1 build of CM fixed my Bluetooth issues. It happens maybe once every few songs which is a huge improvement over previous versions.
Sent from my One using xda app-developers app
floofer said:
Just in case anyone comes across this thread in the future it seems like the RC1 build of CM fixed my Bluetooth issues. It happens maybe once every few songs which is a huge improvement over previous versions.
Sent from my One using xda app-developers app
Click to expand...
Click to collapse
Any updates on a fix for bluetooth stutter cm 10.2?
Im running stable release.
It is random but occurs more so with pandora than with apollo
radpp16 said:
Any updates on a fix for bluetooth stutter cm 10.2?
Im running stable release.
It is random but occurs more so with pandora than with apollo
Click to expand...
Click to collapse
I updated to a 4.4 ROM and haven't had a single issue with that. It even sends the timing data to say how much of the song has played vs how much is left. what I heard was up until 4.4, AOSP relied on the manufacturers to write their own Bluetooth code so when using a Sense ROM the bluetooth worked fine. I think there has always been something inherently wrong with the CM bluetooth code for some devices which causes the instability. If you can I'd try a 4.4 ROM to see if that fixes it.
Related
Does anyone have this problem? I'm on the latest version of AOKP with Franco Kernal...Everytime I listen to music, it will randomly stop and I would have to press play again. This happens at random times, (seconds, minutes, hours). I'm using Google Music (Play Music). I have tried PowerAMP and other players, but they seem too all do it.
It's kind of bugging me
ogxjason15 said:
Does anyone have this problem? I'm on the latest version of AOKP with Franco Kernal...Everytime I listen to music, it will randomly stop and I would have to press play again. This happens at random times, (seconds, minutes, hours). I'm using Google Music (Play Music). I have tried PowerAMP and other players, but they seem too all do it.
It's kind of bugging me
Click to expand...
Click to collapse
It could be a bug with Franco's sound hacks he implements in his kernels. Perhaps try using a different kernel?
anton2009 said:
It could be a bug with Franco's sound hacks he implements in his kernels. Perhaps try using a different kernel?
Click to expand...
Click to collapse
hmmm...can anyone else confirm this that's also using Franco's Kernal....
I get this on stock. I thought it was related to another piece of software (pocketcasts) that I installed about the same time the problems started. Seem that the first song is played, then it pauses or stops.
Could be a buggy headphone connector (in the phone), where it send a faulty signal telling the system that you have unplugged the headphones. Does it only happen while using headphones?
My connector does that as well, but opposite. When not using headpones it sometimes signals that something has been plugged in, and all audio is routed to the non-existing headphones.
this bug definitively occurs on francoKernel!
Try flashing another kernel (Popcorn for example) and the bug is gone.
Seems to have something to do with the sound limit. If it's too loud it stops automatically. Try reducing the volume to 60% with the hard buttons and you'll see that it stops acting like that.
It's not a Franco's kernel only problem. I have the same issue on Stock 4.0.2 (GSM, unlocked, unrooted).
It is not the headphone connector that is buggy either since i'm experiencing this with bluetooth headset as well (A2DP headset).
The music app is not crashing either since it doesn't require a full "load" when i select the app. Press play again and all is good until next time.
It happens to me on stock as well. With both the music and listen apps. Seems to happen if I'm playing music for a half hour or so without using the phone.
Sent from my Galaxy Nexus using xda premium
I am running AOKP M3 and Franco's kernel and am experiencing the exact same thing.
Benxter said:
this bug definitively occurs on francoKernel!
Try flashing another kernel (Popcorn for example) and the bug is gone.
Seems to have something to do with the sound limit. If it's too loud it stops automatically. Try reducing the volume to 60% with the hard buttons and you'll see that it stops acting like that.
Click to expand...
Click to collapse
I have noticed this. When i turn down the volume it stops doing it. But when i turn it up to max it will start doing it again
Sent from my SAMSUNG-SGH-I717 using Tapatalk
I experience this on google listen on stock 4.0.1. I thought it was a bug with the app losing audio focus. But then they updated and claimed an audio focus fix, yet it still happens. I can force this bug to happen by multitasking moderately. So i truly think this bug is related to the over aggressive memory management on this phone.
Yea I'm using Axi0m and I notice this. I think its an issue with the headphone jack. When I installed power amp, one of the features is to detect connection to the headphones... then the phone started to randomly start and stop playing music completely random.
I updated and it seems to be fixed. Still stops occasionally but at least I can listen for an extended period.
Sent from my Galaxy Nexus using xda premium
Franco Kernel updater
I'm running Lean Kernel and I get this all the time when I have the volume set to MAX on the device itself, I find if I turn it down just a bump then the problem goes away. This may be some type of fail safe for the phone itself. ??? But just turn your vol down one click and you're good to go.
I always had issues playing music with franco.kernel, it did me just like you are talking about. That **** used to drive me crazy! Anyways, no issues with CM10 M2. Also using the built in CM kernel.
yup, had this thing on both stock and codename android. google music app
Just gotta wake up this thread.
I'm having this issue on CM10.2... I had this same thing on stock JB some time ago when I connected to my BT headset..
Is there any fix for this?
Btw.
I don't use any custom kernels and this is not caused by any kernel and I don't think this to be caused by BLE.
Benxter said:
this bug definitively occurs on francoKernel!
Try flashing another kernel (Popcorn for example) and the bug is gone.
Seems to have something to do with the sound limit. If it's too loud it stops automatically. Try reducing the volume to 60% with the hard buttons and you'll see that it stops acting like that.
Click to expand...
Click to collapse
^^This
I had the same issue and realized I had the volume up too loud with the mods I had installed. Keep the volume below 80% and the problem will disappear.
Possible solution
I used to have this issue as well, where after a certain period of not actually using the phone, the music playback would just pause itself.
I discovered that I had Play music "Greenified" which is basically a hibernating task manager. That was killing the background process of any music players I had open.
Wether or not you have the Greenify app, check for any automatic task killers and get rid of them.. Maybe that will help one of you guys, it sure helped me.
Only had this happen using headphone volume boost... don't use it
Sent from my Galaxy Nexus using Tapatalk 2
I am running into an issue with streaming my media over a2dp bluetooth. There is a lot of distortion, pops, and sped up audio. This started happening when I installed nightlies that upgraded to 10.1, along with the new gapps.
I have spent the last four hours trying to fix this device. I am now at the point of putting it back to stock, which I really hate to do bc I love CM10.
Any advice? Is this a known issue? The audio will play fine via a2dp for about 15-30 seconds, and then the distortion occurs.
Thanks so much,
Jennifer
jruggiero said:
I am running into an issue with streaming my media over a2dp bluetooth. There is a lot of distortion, pops, and sped up audio. This started happening when I installed nightlies that upgraded to 10.1, along with the new gapps.
I have spent the last four hours trying to fix this device. I am now at the point of putting it back to stock, which I really hate to do bc I love CM10.
Any advice? Is this a known issue? The audio will play fine via a2dp for about 15-30 seconds, and then the distortion occurs.
Thanks so much,
Jennifer
Click to expand...
Click to collapse
I'm having this same exact problem. It happened when I updated to the 12/27 nightly I believe. I just rolled back to 12/26 but haven't had a chance to check it. It's really bad because data doesn't work well on 12/26 so I have to choose between streaming music bluetooth or data...
mbeez said:
I'm having this same exact problem. It happened when I updated to the 12/27 nightly I believe. I just rolled back to 12/26 but haven't had a chance to check it. It's really bad because data doesn't work well on 12/26 so I have to choose between streaming music bluetooth or data...
Click to expand...
Click to collapse
Yikes! Well, I'm glad it isn't just me, but am sorry you are experiencing this too. I hope it is fixed soon! I kept trying other nightly builds and then tried to go back to 10.0, but kept getting errors with 10.0 builds. I went back to stock this afternoon as a result of this. I do prefer CM10 to stock Touchwiz JB, though.
I'm wondering if anyone else is having this problem or if they fixed it in one of the recent builds?
mbeez said:
I'm wondering if anyone else is having this problem or if they fixed it in one of the recent builds?
Click to expand...
Click to collapse
Yep, it's there on the 1/1/2013 build Everything else seems silky smooth, but the BT problem is still there. I wonder if the "dial a number and then hang up" fix wirks for this like it did with the previous BT audio bug from CM10
adamriggins said:
Yep, it's there on the 1/1/2013 build Everything else seems silky smooth, but the BT problem is still there. I wonder if the "dial a number and then hang up" fix wirks for this like it did with the previous BT audio bug from CM10
Click to expand...
Click to collapse
doubtful, but might be worth a try. I really hope they fix this soon.
bump. wondering if anyone else is experiencing this?
A2dp distortion is a well known issue relating to problems with the audio driver. Builds up to 12/26 do not have this issue. The newer 10.1 builds have no audio issues (except over BT) so if you cannot live without BT I would suggest a clean flash back to 12/26.
zkz90 said:
A2dp distortion is a well known issue relating to problems with the audio driver. Builds up to 12/26 do not have this issue. The newer 10.1 builds have no audio issues (except over BT) so if you cannot live without BT I would suggest a clean flash back to 12/26.
Click to expand...
Click to collapse
Yes, I went back to 12/26 and the only issue i have now is connecting to mobile data. it takes a couple times toggling the airplane mode before it connects but id rather do that than not have streaming bluetooth which I use daily. any idea when they will fix it?
anyone know if this has been fixed yet? i haven't seen anything in the dev logs
mbeez said:
anyone know if this has been fixed yet? i haven't seen anything in the dev logs
Click to expand...
Click to collapse
Is there a way to track this issue other than the changelogs ? Are the devs aware of the issue ?
johoja said:
Is there a way to track this issue other than the changelogs ? Are the devs aware of the issue ?
Click to expand...
Click to collapse
I have the same issue when I'm on ktoonz kernel. When I flashed back to the stock kernel it went away
Galaxy S 3 32gb ...Sprint
jelly bean LJ7 rooted....yahhhyuhhh
has this been fixed yet?
I was trying to pair my s3 to my stock car radio so I could stream music through the phone but for some reason it doesnt work anymore after I flashed a rom. Is there something in stock that I'm missing?
I'm currently on Wicked 2.0 and tried pairing but everything works except the music. I remember when it worked fine on stock but during pairing it gave me a 2nd option during connection called gconnect, gmusic or g something lol. My car is a 2012 that has a2dp capability and it did work the other day prior to flashing so before I go back stock any other ideas?
Well as always try restarting your phone, and maybe delete pairings that you have seen. Sometimes when I've paired, I believe it saves so you can do it easier. Just try deleting that and then retry. I may have it confused with something else though
Sent from my SPH-L710 using xda app-developers app
seoulseek80 said:
I was trying to pair my s3 to my stock car radio so I could stream music through the phone but for some reason it doesnt work anymore after I flashed a rom. Is there something in stock that I'm missing?
I'm currently on Wicked 2.0 and tried pairing but everything works except the music. I remember when it worked fine on stock but during pairing it gave me a 2nd option during connection called gconnect, gmusic or g something lol. My car is a 2012 that has a2dp capability and it did work the other day prior to flashing so before I go back stock any other ideas?
Click to expand...
Click to collapse
Be sure to check the changelogs of the Roms you are using to see if that is a known issue, as well as, search the specific thread for the Rom for any issues related to bluetooth streaming issues. Though I'm not familiar with Wicked 2.0, if it's an AOSP rom, they have had a2dp issues from time to time. If it's touchwhiz, you'll want to see if it could be a kernel related issue.
Having the same problem
ReapersDeath said:
Well as always try restarting your phone, and maybe delete pairings that you have seen. Sometimes when I've paired, I believe it saves so you can do it easier. Just try deleting that and then retry. I may have it confused with something else though
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I went to CyanogenMod 10.1-201330121-EXPERIMETNAL-d2spr-M1 and I have the same issue. I can no longer get Bluetooth audio to stream music properly. It starts fine, but then after a few seconds I get this weird slowing-down and skipping distortion.
I've unpaired, repaired, turned off everything, turned it all back on, taken out the battery, etc. The whole 9 yards, and I'm still getting the same thing every time I try and stream music.
pandemicsoul said:
I went to CyanogenMod 10.1-201330121-EXPERIMETNAL-d2spr-M1 and I have the same issue. I can no longer get Bluetooth audio to stream music properly. It starts fine, but then after a few seconds I get this weird slowing-down and skipping distortion.
I've unpaired, repaired, turned off everything, turned it all back on, taken out the battery, etc. The whole 9 yards, and I'm still getting the same thing every time I try and stream music.
Click to expand...
Click to collapse
With AOSP roms, such as CyanogenMod, a2dp has been a consistent issue. However, the recent beta of LiquidSmooth, 3.2.1, is what I currently have running on my GS3 and it had some sort of a2dp fix in it that restored streaming quality to bluetooth. Give it a shot. It'll operate similarly to CM10.1.
Flash the latest nightly of CyanogenMod for working a2dp. It wasn't working on the M1.
Sent from my SPH-L710 using Tapatalk 2
Vanakatherock said:
Be sure to check the changelogs of the Roms you are using to see if that is a known issue, as well as, search the specific thread for the Rom for any issues related to bluetooth streaming issues. Though I'm not familiar with Wicked 2.0, if it's an AOSP rom, they have had a2dp issues from time to time. If it's touchwhiz, you'll want to see if it could be a kernel related issue.
Click to expand...
Click to collapse
Could see anything noted beside me. i think it is an asop rom but can get it to stream music. I might go to cm10.1 or back to stock. I love this rom but I need my streaming audio lol
Works great for me on jelly bomb v13. I stream music to my headset and a portable speaker daily over Bluetooth.
Sent from my SPH-L710 using Tapatalk 2
seoulseek80 said:
Could see anything noted beside me. i think it is an asop rom but can get it to stream music. I might go to cm10.1 or back to stock. I love this rom but I need my streaming audio lol
Click to expand...
Click to collapse
CM 10.1 is AOSP. Any ROM under the "original development" thread is usually AOSP based. AOSP is what has had the A2DP issues, but recent versions of CM 10.1 & my ROM of choice, LiquidSmooth 3.2.1, have seemingly got the bluetooth issues fixed.
finally figured out just encase anybody ever needs to know but it was called GmusicConnect. It popped up but had to be done under aux out and config >bluetooth music pairing. totally separate menus then the actual phone call pairing
I get no bass when streaming music, only what sounds like mid and treble. I tried finding the DSP Manager app, but I'm not able to open it for some reason, unless it's been merged into the settings.
Haven't tried Bluetooth lately so I don't know if the issue was ever fixed but after starting up BT make a call and then hang up when it connects the sound will be normal after that. It was a cm10/aosp issue from long ago...
May or may not be your problem, just thought I would pass that along
Sent from my SPH-L710 using xda app-developers app
n2mschf said:
Haven't tried Bluetooth lately so I don't know if the issue was ever fixed but after starting up BT make a call and then hang up when it connects the sound will be normal after that. It was a cm10/aosp issue from long ago...
May or may not be your problem, just thought I would pass that along
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
This works but I'd rather not have to do it every single time I want to listen to music, especially if I just run into the store real quick then come back out to resume the stream. Right now, I just place a quick call to voicemail then end it, so tha the stream kicks in normally.
Does anyone know if they fixed this bug in any of the 10.0 nightlies after 10.0 stable? I don't much care for 10.1, if it can be avoided.
I've searched the forums and found quite a bit of people saying they have experienced this, but I'm not sure if they were using notes or not.
For some reason, it doesnt matter what app I'm using, pandora, xm, or the stock players. They all studder just slightly, sometimes more so when the screen is off.
It's not a bluetooth specific thing, it happens over bluetooth as well as the speaker of the note3.
Is there a solution for this? It really drives me crazy and how can I host a party next weekend with this doing that
My girlfriend does not experience this on her nexus 5, is my problem specific to jellybean?
Thanks for your advice!
stokedcrf said:
I've searched the forums and found quite a bit of people saying they have experienced this, but I'm not sure if they were using notes or not.
For some reason, it doesnt matter what app I'm using, pandora, xm, or the stock players. They all studder just slightly, sometimes more so when the screen is off.
It's not a bluetooth specific thing, it happens over bluetooth as well as the speaker of the note3.
Is there a solution for this? It really drives me crazy and how can I host a party next weekend with this doing that
My girlfriend does not experience this on her nexus 5, is my problem specific to jellybean?
Thanks for your advice!
Click to expand...
Click to collapse
yep same problem.
i had it on nexus 4 - 4.3. but um, didn't start on my note 3 until after a few days of use. I'm not sure rebooting helps for long. i tried poweramp and jetaudio and stock player. Skips everywhere.
I tried setting decoder priority and buffer size to higher on Poweramp. Not sure if it'll help but we'll see.
I'm on N2 right now that has exact same problem, but BT only related. The micro pauses also differ between the receivers Sony Ericsson MW600 is so far the worst offender, the pauses last 1/2 second, on other receivers it's barely noticeable.
At least on N2 it's not related to the JB version, it was happening on 4.1.2 and 4.3. Changing kernel also doesn't affect the issue.
I suspect the cause is BT doesn't get enough priority and if lot's of apps running on the background it starts skipping. Usually I just reboot the phone then it works fine for a few hours, sometimes I use fast reboot app, that kills background processes it helps somewhat too.
svyr said:
I tried setting decoder priority and buffer size to higher on Poweramp. Not sure if it'll help but we'll see.
Click to expand...
Click to collapse
Using PowerAmp I went to Huge buffer and Highest priority and it seems to have fixed the stuttering for me. I'm on rooted stock.
>Using PowerAmp I went to Huge buffer and Highest priority and it seems to have fixed the stuttering for me. I'm on rooted stock.
yup. same. now wish they'd add the same features to jetaudio+ and other players D:
I get this problem often. Odd.
I'm not sure if this is a solution but I noticed the problem went away when I was using different roms/kernel combinations.
Currently I've been using the compulsion kernel with some international roms and the problem hasn't come back!
Is it the kernel or rom I can't be sure. But either way it's fixed.
If someone experiencing problems with their rom wants to try the compulsion kernel and see if the problem still exists maybe it can help a lot of people.
Sent from my SM-N9005 using Tapatalk