Develop Bugs

[Q] Bluetooth A2DP audio occasionally drops out for a second on custom ROMs

Hello all,
I have a very odd problem that I'm hoping others may have run into and solved. When I'm playing audio over the A2DP data path to my car, the audio randomly will drop for half a second, then gradually comes back to full volume over perhaps a second of time. Speaking like a programmer, it's almost like something mutes the audio and then slides the volume up in a loop or something.
This problem did not occur on Bombaridier and the older Synergy Kernel, however it is happening with the newer kernel on Juggernaut v5, Paradox and SlickMOD, leading me to believe something in the kernel or newer system binaries might be causing it. This behavior happens in Pandora, Amazon MP3 and also the stock Music app.
Thinking that maybe a stray notification was the problem, I've tried disabling notifications in all of the apps I know of that notify, I've also tried switching the phone into vibrate and finally into full-silent, but it does not seem to affect the behavior. I have found no likely cause. I wish I was able to log alsa changes; maybe a script running constantly with something like:
Code:
while (true)
do cat /proc/alsa/some_alsa_status_entry >> /tmp/alsalog
sleep 1
done
Does anyone else have any ideas as to what this might be? It's really annoying!
Thanks in advance,
Pete

Dirty Pete said:
Hello all,
I have a very odd problem that I'm hoping others may have run into and solved. When I'm playing audio over the A2DP data path to my car, the audio randomly will drop for half a second, then gradually comes back to full volume over perhaps a second of time. Speaking like a programmer, it's almost like something mutes the audio and then slides the volume up in a loop or something.
This problem did not occur on Bombaridier and the older Synergy Kernel, however it is happening with the newer kernel on Juggernaut v5, Paradox and SlickMOD, leading me to believe something in the kernel or newer system binaries might be causing it. This behavior happens in Pandora, Amazon MP3 and also the stock Music app.
Thinking that maybe a stray notification was the problem, I've tried disabling notifications in all of the apps I know of that notify, I've also tried switching the phone into vibrate and finally into full-silent, but it does not seem to affect the behavior. I have found no likely cause. I wish I was able to log alsa changes; maybe a script running constantly with something like:
Code:
while (true)
do cat /proc/alsa/some_alsa_status_entry >> /tmp/alsalog
sleep 1
done
Does anyone else have any ideas as to what this might be? It's really annoying!
Thanks in advance,
Pete
Click to expand...
Click to collapse
I second this as an issue that I have run across quite often. I use this BT for music in my car on a daily basis. I usually get a .5 second audio drop out at lest twice each song. Seems to be about every 2 minutes if I would have to guess.
I have just learned to get used to it but it would be fantastic if this could be resolved.

I've also tried fiddling with the CPU governor ant the IO scheduler, but to no avail. Im wondering if there is a bug in the bluetooth module introduced in the latest kernel.
Sent from my SGH-T989 using xda premium

Works great for me and I've tried just about every rom and kernel over clocked and under clocked. I had it skip once before, I rebooted and it was fine.
Sent from my SGH-T989 using Tapatalk

I'll give this a bump, because I have the exact same problem. Never had this problem on my Blackberry (sad), in the same car. OP has described the issue better than I could have.

scotty-dont said:
I'll give this a bump, because I have the exact same problem. Never had this problem on my Blackberry (sad), in the same car. OP has described the issue better than I could have.
Click to expand...
Click to collapse
Thanks for posting, out of curiosity, what ROM and kernel are you running? Maybe we can find some sort of similarities...
My phone's currently running SlickMOD 3.1 with kernel "2.6.35.14"
-Pete

I've tried black edition and warfare, never had any issues

tomasitoc said:
I've tried black edition and warfare, never had any issues
Click to expand...
Click to collapse
What version of the kernel on your warfare mod? SlickMOD uses the Darkside 2.6.35.14 kernel.

Dirty Pete said:
Thanks for posting, out of curiosity, what ROM and kernel are you running? Maybe we can find some sort of similarities...
My phone's currently running SlickMOD 3.1 with kernel "2.6.35.14"
-Pete
Click to expand...
Click to collapse
Hi Pete,
I've noticed it on Digital Warfare 2.5.1 and BeastMOD 5.0 ("Test 13"), using TDJ's personal kernel and the same 2.6.35.14 above, respectively.
I'll post to Melvin on rootzwiki in the hopes that he can investigate maybe.
It might be better to bring this up in other sections as well. I came across this post by accident while researching extended batteries.

scotty-dont said:
It might be better to bring this up in other sections as well. I came across this post by accident while researching extended batteries.
Click to expand...
Click to collapse
I originally posted it in a different forum, but a moderator kicked it over here. It's not really an accessories question as I'm pretty sure it's a kernel bug, but I wasn't about to argue with site moderators on a forum like this where I'm definitely the new kid on the block.
That being said, if you have some other suggestions as to where we can ask about this, I'm all ears and would be more than willing to help debug/diagnose. I've been a Linux user since '96, so I'm unafraid of poking around in the kernel's guts to get answers.
Pete

Yeah that's the problem with this place... and why I have less than 10 posts.
On second thought, I'm tempted to just wait. It sounds like we will have a proper ICS rom and true kernel on about April 25th, to coincide with the launch of the HTC One S on T-Mobile. I can't find the threads. Hopefully then it will be an issue of the past.
I'm glad I'm not the only one though.

Just a thought....I don’t think this has anything to do with CPU performance
Hi, I have a Galaxy 2s with this exact problem but I wonder if I might offer a suggestion as to what could potentially be the cause. I have no idea how to fix it but I’m hoping that what I share here might help someone who knows more about the way these things work to be able to solve the problem.
I have spent much of my career working in Broadcast Radio, the problem I have heard my phone have with audio dropouts followed by either a ramp up of volume back to the previous level OR an audio dropouts followed by a momentary slight speed shift in the audio playback (sounds a bit like an old cassette recorded when the batteries are starting to fail) many people would probably not notice the later problem because it is very subtle and you have to know what you’re listening for.
Anyway, I believe this could be caused because of a lack of word clock sync between the phone and the bluetooth receiver. I say this because there have been times when I have had digital audio devices such as CD players that are connected to an audio console or digital amplifier and with both devices free running in terms of their clock synchronisation exhibit almost exactly the same symptoms.
You see all digital audio devices require that the audio data be put into frames much the same as regular Ethernet data is transmitted around a network is put into frames, however in order for the audio to be at the correct pitch and speed generally speaking both the playback device (Phone) and the receiving device (Bluetooth receiver) need to have the same word clock, otherwise you end up with the two devices running freely and the audio frames wont by in sync.
Depending on the Error correction implemented (sample rate conversion) on the receiver you can get really odd audio results. I think that this is what is causing this problem. Basically the Bluetooth receiver and the phone aren’t in sync so every few minutes you get a drop out.
It doesn’t seem to happen when you are talking on the phone which makes me think that when you have a call connection as this is bi-directional, the phone is probably synchronised to the Bluetooth device word clock. But when you are listing to music the connection is mono-directional so there is no sync.
Anyway just a thought. Maybe someone out there who understands the way these units synchronise can figure out a fix.

Mine has random just disconnects from the phone altogether. I have Jawbone Era, Voyager Pro Plus, and a Jabra Wave + and all will just randomly disconnect and have a hard time connecting back to phone audio. It will reconnect to media pretty much first time but won't show coonected to phone audio for some reason unleass I turn off BT, turn off headset, and sometimes even re-boot phone.

I am sure you guys have ruled this out, but this was a common problem with bluetooth audio on android. I haven't had the problem for a long time, but I used to have to disable wifi during my commute due to this dropout. Can you turn off wifi and see if the issue still happens? I was able to identify it by changing the time between wifi scan. If you had custom rom settings you could push it out and sure enough, my bluetooth dropouts happened on the same schedule (2s, 10s, more)
Just a thought.

I had this issue when I tried out juggernaut, so I went right back to Bombardier with Synergy kernel. Anyone have this on any if the ICS roms?
Sent from my beastly Galaxy S 2.

Shane_pcs said:
I am sure you guys have ruled this out, but this was a common problem with bluetooth audio on android. I haven't had the problem for a long time, but I used to have to disable wifi during my commute due to this dropout. Can you turn off wifi and see if the issue still happens? I was able to identify it by changing the time between wifi scan. If you had custom rom settings you could push it out and sure enough, my bluetooth dropouts happened on the same schedule (2s, 10s, more)
Just a thought.
Click to expand...
Click to collapse
I disable my wifi while I'm in the car, so this wasn't my issue. Thanks for the suggestion though!

I used to have occasional a2dp problems, however I have not had them since I started using various ICS releasese. The problems I would occasionally have would be a total loss of bluetooth till I rebooted the phone.
Since using Infamous I haven't had the problem other then for some odd reason occasionally having to reenter the PIN #
I'm using a Scoche Bluefusion in my car.

It had to be the fuse.
Sent from my SGH-T959 using xda premium

After upgrading to DARKSIDE's latest ICS rom, this problem has not recurred. I'm assuming that my early thought was correct in that it was some kind of kernel bug.

Dirty Pete said:
After upgrading to DARKSIDE's latest ICS rom, this problem has not recurred. I'm assuming that my early thought was correct in that it was some kind of kernel bug.
Click to expand...
Click to collapse
With Darkside and the stock ROM I have not only this problem, but crackly/staticy audio and my phone and car won't communicate once I've shut the car off. I have to completely re-pair the phone. They're bugs in 4.0.3, which Samsung dumped off on us.
4.0.4 via CM9 already doesn't exhibit the connection issue (I have to turn Bluetooth on and then off though) but I'm not sure about the others yet.

ATT Samsung Galaxy S III/SGH-I747 4.2.1 bluetooth issues

X-iPhone user here but I have owned android honeycomb tablets in the past.
hey guys, I have been at this for days. I LOVE what 4.2.1 brings to the table over the stock bloatware 4.1.1 that slows down the phone(also kills the battery faster). but No matter what ROM I try I get choppy bluetooth . With CyanogenMod 10.0 BT works but There is no bass until I make a BT call let it ring for 5 seconds then hang up. But there are other issues all BT related as well such as no resume on start up of the headunit.
my question is am I doing something wrong or just not using the right roms?
right now I restored back to the OEM 4.1.1 and my BT works perfect with my poineer AVH-P3400BH with the exception of no METADATA but thats not a big deal.
thanks so much for your reply
Shawn

I've been using the latest vanilla root box. This thing is beastly, give it a shot. I'm a big Bluetooth user too, and the audio is crisp and loud, with good bass, no need to make a phone call. The only thing, every so often (read, not very often) the Bluetooth doesn't like to turn off. All you have to do it force stop Bluetooth sharing in manage apps though.
Give it a shot. Easily one of the best ROMs I've ever used.
Sent from my SGH-I747 using xda app-developers app

406 inferfa
thegreatscott said:
I've been using the latest vanilla root box. This thing is beastly, give it a shot. I'm a big Bluetooth user too, and the audio is crisp and loud, with good bass, no need to make a phone call. The only thing, every so often (read, not very often) the Bluetooth doesn't like to turn off. All you have to do it force stop Bluetooth sharing in manage apps though.
Give it a shot. Easily one of the best ROMs I've ever used.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
hey thanks so much for the fast reply. Can you show me a link? Im excited. I dont want to return this phone.

lotust251 said:
hey thanks so much for the fast reply. Can you show me a link? Im excited. I dont want to return this phone.
Click to expand...
Click to collapse
edit: it was an easy find but what version of it are you using? the offical release or the nightlys?
http://forum.xda-developers.com/showthread.php?t=1898798

crap, It was working for a while with RootBox-JB-d2att-V3.6 but I had to do the phone call before I got bass again. I also cant see Metadata or hear texts. After a few calls and a few texts the phone crashed and I just had a flashing blue light and a black screen. this stinks I really like the phone and want this to work.
im going to try 3.7.1 and if that dont work im going to give up :crying:

Or try task's AOKP. Yet another ROM that has bluetooth working right.

CrackerTeg said:
Or try task's AOKP. Yet another ROM that has bluetooth working right.
Click to expand...
Click to collapse
^ Second this. On Task's AOKP latest and no Bluetooth issues whatsoever. I am a heavy BT user as well.

cjranucci said:
^ Second this. On Task's AOKP latest and no Bluetooth issues whatsoever. I am a heavy BT user as well.
Click to expand...
Click to collapse
Same here. Now if only voice dialing worked over bluetooth ...

[Q] 4.2 Bluetooth issues still present?

I've been ignoring custom roms for about 6 months after I tried one previously and found the bluetooth bug. Just curious if this has found a fix at this point? I'd love to run a CM10.1 rom, but bluetooth audio is a must have for me.

cegna09 said:
I've been ignoring custom roms for about 6 months after I tried one previously and found the bluetooth bug. Just curious if this has found a fix at this point? I'd love to run a CM10.1 rom, but bluetooth audio is a must have for me.
Click to expand...
Click to collapse
the issues from 6 months ago have been gone for sometime now.

fantastic, thank you.
Life's been pretty crazy so i'm out of the loop on where everything has progressed. Once i get AT&T to warranty my phone for the GPS issues i'm having i'll try out one of the new builds.

Bluetooth audio has been working fine
But from my experience there have been problems with Bluetooth dialing.
A recent update of slimbean (version 6) seems to have corrected the problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I don't know that the issue really is fixed in 4.2.2. Doesn't seem to matter what ROM I run (I've tried CM, Carbon, AOKP), I can't get Bluetooth to work at all. It won't scan/find any of my devices or even turn on. I've resorted going back to stock rooted.
Has anyone found a work around or fix?

If bluetooth worked, it wont be 4.2.2. Best to go back to 4.1.x.
Sent from my SAMSUNG-SGH-I747 using xda premium

kt314 said:
I don't know that the issue really is fixed in 4.2.2. Doesn't seem to matter what ROM I run (I've tried CM, Carbon, AOKP), I can't get Bluetooth to work at all. It won't scan/find any of my devices or even turn on. I've resorted going back to stock rooted.
Has anyone found a work around or fix?
Click to expand...
Click to collapse
once in the past, when the CM roms were having bluetooth problems, I tried a different kernel and that fixed issues. The BMS Kernel is pretty stable and great performance/battery. you might give that a try.

Curious problem with bluetooth (interference?) keyboard and mouse

Hi there guys!
This is my first thread, there seems to have been a thread on every problem I've encountered until now..
I have a motorola bluetooth keyboard
and a samsung bluetooth mouse
The keyboard works amazingly well on its own on my note 2. However when I also connect the mouse it starts to lag and type like thissssss. It's so bad it makes the keyboard unusable as you spend more time correcting what you wrote.
If this was a case of normal interference, I'd call it bad luck and leave it there.. HOWEVER - I tested them both on my macbook pro and they work as intended together. Now this puzzles me greatly as I thought they were interfering with each other's frequency, so shouldn't that be independent of the device I'm using?
Since they can work together, I was wondering if anyone could help me out with any suggestions of what's going on so I can come to some kind of solution/fix?
Thanks, looking forward to hearing your thoughts!

Any chance the cpu is underclocked (power saving mode in settings)?
from tapatalk (Galaxy Note 2)

Unfortunately it's not

Look for external keyboard helper in app store. Set delay settings to your liking. You will to have that set as your keyboard. Be aware that samsung keyboard tries to turn on depending on what Rom you ate running. I am somewhat disappointed in the bluetooth performance on my note 2. That is about all I am disappointed about.
Sent from my SGH-T889 using Tapatalk 2

Thank you so much! It worked like a charm! I actually already had the app installed, it was just set to no delay by default. I'm so glad I don't have to go out and replace my mouse
What exactly was it that disappointed you about the bluetooth performance?

prashanthan.g said:
Thank you so much! It worked like a charm! I actually already had the app installed, it was just set to no delay by default. I'm so glad I don't have to go out and replace my mouse
What exactly was it that disappointed you about the bluetooth performance?
Click to expand...
Click to collapse
On some of the ROM/kernels floating around I have had TERRIBLE bluetooth performance, voice wouldn't work to dial numbers over a bluetooth connection, but would work during a phone call, couldn't connect to more than one device without restarting the phone.
However Assassin Rom with the kernel that comes stock with it, that fixes all the problems I have had with bluetooth.

bunnybash said:
On some of the ROM/kernels floating around I have had TERRIBLE bluetooth performance, voice wouldn't work to dial numbers over a bluetooth connection, but would work during a phone call, couldn't connect to more than one device without restarting the phone.
However Assassin Rom with the kernel that comes stock with it, that fixes all the problems I have had with bluetooth.
Click to expand...
Click to collapse
Oh man, I had no idea! It's been ok for what I've used it for, up until this problem, but now its fixed I'm pretty happy with it.
I just wished bluetooth used less battery.. or if the phone powered itself by creating energy :fingers-crossed: but thats probably only going to happen in 4.3

Also, try connecting to wifi using 5ghz (if you are on wifi). I have terrible problems when using 2.4ghz wifi and bluetooth together.
Sent from my GT-N7100 using Tapatalk 4 Beta

This solved my problem.
There's just not enough bandwidth available for 3 simultaneous devices connected to the same device on 2.4GHz band.

Bluetooth A2DP stutter cuts out while streaming music

I was hoping this would be fixed in the 4.4.2 update but it appears to still be there. While listening to anything in my vehicle with bluetooth A2DP the audio seems to cutout, like a bad connection. The song continues to play and sometimes I see the information on the radio screen disappear, as if the phone lost connection.
This happens no matter where I place the phone. Normally it sits in the storage pocket just below the radio but also happens in the mount on my dashboard as well as my center console.
It seems to happen less often if I plug in the charger, and even less if I force the screen to stay awake. I have not had this issue with my Sensation 4G or my Galaxy S3.
Any help is appreciated.

Zylograth said:
I was hoping this would be fixed in the 4.4.2 update but it appears to still be there. While listening to anything in my vehicle with bluetooth A2DP the audio seems to cutout, like a bad connection. The song continues to play and sometimes I see the information on the radio screen disappear, as if the phone lost connection.
This happens no matter where I place the phone. Normally it sits in the storage pocket just below the radio but also happens in the mount on my dashboard as well as my center console.
It seems to happen less often if I plug in the charger, and even less if I force the screen to stay awake. I have not had this issue with my Sensation 4G or my Galaxy S3.
Any help is appreciated.
Click to expand...
Click to collapse
Funny thing is I didn't have this issue at all back on 4.3, but do have it now with 4.4.2
Yay for 'upgrades'

Try turning wife off if it's on.

stevessvt said:
Try turning wife off if it's on.
Click to expand...
Click to collapse
I have tried every combination of different settings and the only thing that seems to help, although does not resolve altogether, is to plug in the charger and tell the screen to stay on during charging. May be something related to the sleep mode putting the CPU at too low of a minimum.
I am looking at other stereos for my vehicle as it may be an issue with the stereo just not being fully compatible with the newer bluetooth version on the Note 3. I need to test this to be sure.

I have the same issue. My screen is always on and charging but it still stutters on occasion. I used to have the HTC One and it had the same issue. I don't think there is a fix except to try a custom rom.

hawkye said:
I have the same issue. My screen is always on and charging but it still stutters on occasion. I used to have the HTC One and it had the same issue. I don't think there is a fix except to try a custom rom.
Click to expand...
Click to collapse
I am using the Sony DSXS310BTX, what about you?

Zylograth said:
I am using the Sony DSXS310BTX, what about you?
Click to expand...
Click to collapse
I have the older 300BTX. One thing that you made me realize is that on 4.3 I was running leankernel the whole time, and with KitKat I was running the stock kernel until this morning.
Going to the gym in an hour and I'll test the bluetooth today to see if switching kernels fixes the issue.
*EDIT*
Didn't skip on me at all on the way home today. This leads me to believe that your skipping problem is kernel-related. Give leankernel a try and let us know if that fixed it for you too?

I was just going to post the same as Kalm. I tried the new v2.0 of LeanKernel and no stutter. Also my Bluetooth MAP is working consistently again with my Ford Sync system. I played about 20mins of music on my Jawbone Jambox with no stutter also.

think this is something specific to a chip. I can stream pandora with pandora control and stream pandora and music over str8 bluetooth via hondalink with no issue.

I think I am going to wait and see what happens when I upgrade to the S5 in a few weeks. If the problem persists I will probably start looking at new head units for my vehicle. I am already eyeing the Pioneer AppRadio 3 LOL

Zylograth said:
I think I am going to wait and see what happens when I upgrade to the S5 in a few weeks. If the problem persists I will probably start looking at new head units for my vehicle. I am already eyeing the Pioneer AppRadio 3 LOL
Click to expand...
Click to collapse
Didn't have any luck with a different kernel?

Kalm_Traveler said:
Didn't have any luck with a different kernel?
Click to expand...
Click to collapse
I am trying to remain stock, once I start flashing ROMs and Kernels it becomes an addiction for me LOL