Hey everyone,
I've been battling this issue since Day 1, and its been a bumpy road. It seems as though this is a widespread issue across many Android devices, and fixes range but none of them seem to completely eliminate it.
When connected to Bluetooth audio, certain devices, the audio stutters or "skips". Ive noticed this extensively in KItKat. One fix for rooted devices was to increase the idle CPU frequency, I did so with Tasker and it definitely suppressed the stuttering, but did not completely eliminate it.
One of the most notable points of stuttering is when you answer a call via Bluetooth, then hang up. After hanging up, and music resuming, there is a solid ~10-20 seconds of constant stuttering and skipping until playback returns to normal.
Imagine my surprise when I upgraded to 6.0.1, and had absolutely no stuttering without increase CPU frequency or anything! Just buttery-smooth playback, all the way through, even after hanging up a call.
However, a couple of weeks after, the issue came back again. I had to re-enable my task to increase idle CPU frequency, and that horrible stutter after hanging up a call is back, strong as ever. To me this indicates perhaps something I modified after stock interfered., however nothing I can think of should come close to affecting it, other than XPOSED (however, XPOSED was installed prior to this issue coming back up, and no new modules were added)
Additionally, since Marshmallow, my phone won't reconnect automatically to my head unit. For example, when my car is on accessory mode and the stereo is on and BT connected. When I start the car, the system momentarily turns off for ~5 seconds at most, and turns back on. With Lollipop it would automatically reconnect, here is causes some serious problems as the only way to get them to reconnect after is to turn off the stereo and the phone, and turn both back on again. Sometimes I even have to do a couple of cycles.
Does anyone have any ideas?
i tried to do everything possible to fix the issue... I have a stuttering keyboard as well... anykeyboard I use seems to stutter, it lags a little, but most words that i type apear two times...
I have no issues at all like that, or stuttering throughout the system. It is specifically related to Bluetooth audio.
Anyone?
I've always thought kernel
unibomber said:
I've always thought kernel
Click to expand...
Click to collapse
If you do not have this problem, what kernel do you use? I just flashed BeastMode today, hoping that will bring me a bit of luck. However as it worked initially and a few weeks later broke down into the pathetic mess once again, I have my doubts
I use power amp and in advance I set thread priority to the highest and audio buffer to 750ms. I've used them all and haven't had skipping
unibomber said:
I use power amp and in advance I set thread priority to the highest and audio buffer to 750ms. I've used them all and haven't had skipping
Click to expand...
Click to collapse
Seems to have improved it, but reconnect issue is still present
The reconnect issue may be related to the stuttering.
The unit may be also trying to download contacts at the same time which causes the stutter.
Have you tried unpairing it from the unit, renaming your phone and then pairing it again?
Will Rickards said:
The reconnect issue may be related to the stuttering.
The unit may be also trying to download contacts at the same time which causes the stutter.
Have you tried unpairing it from the unit, renaming your phone and then pairing it again?
Click to expand...
Click to collapse
I have in fact tried to re-pair the unit many times, to no avail. Factory resets also yield no benefits. It is set to auto download contacts, I'll try to disable that option to see if it improves anything.
I have the stuttering almost removed, however it still sometimes occurs. On a recent long-distance road trip, it randomly started stuttering after playing flawlessly for 1.5 hours, it was incredibly frustrating. I rebooted the phone, and the stereo, reconnected and it started playing smoothly again. Keep in mind however this is with both raising idle CPU frequency, and changing the poweramp options mentioned in Post #7
Perhaps I should try a custom ROM?
You can also try stopping media scanning. I think there is a xposed plugin
I only notice this on a non-name-brand headset. (Also, after it happens, I disconnect and reconnect...and it works fine from there on out...until Power down) My other 3 don't have this problem. Music plays, get a call, hang up, music pick right up. Didn't read your post in detail to see if you've tried a different pair of BT receiver.
FWIW it's not just you, also use PowerAmp, have the buffer turned up, and also get stuttering. On pvsgh's stock rooted deodex'd debloated 5.1.1 with beast mode 1.92 + ZL fix and both my motorola s10 headset and sharkk speaker stutter from time to time. It does not seem to be universal. In the beast mode thread it bluetooth audio issue was brought up, but didn't really get much attention ::shrugs, palms up:: I even limited them to media only but still get the stuttering.
Like so many things it seems, it worked ok before the MM update (910t3 on dok2 ootb) and now doesn't. Kinda like my ability to sign into enterprise level (work - EAP login) routers...
CM12.1 didn't make a difference in my case. Been on several stockish 5.1.1 roms as well. It still happens. Swapping out roms doesn't appear to pay off. It hasn't for me anyway :-/
Interested to see if a solution (or a cause?) lands here...
Sent from my SM-N910T3 using XDA-Developers mobile app
Related
I had an issue with a New Potato Tunelink and choppy audio (I have a thread in here somewhere).
I bought a Kinivo BTC450 Bluetooth Hands-Free Car Kit and it does not suffer from the same audio problems, it sounds great... when my phone isn't rebooting.
The only time my phone reboots is in the car. I've disabled Active thinking it might have something to do with that, but no. If I turn off BT the phone doesn't reboot. There is something with my VZW MX and this Kinivo paired together that creates a situation where it unexpected and randomly reboots.
This morning it rebooted almost immediately after connecting. Sometimes I can manipulate the controls, pick a song and start playing it and it will reboot shortly thereafter. Other times it won't reboot and will start working until I go to skip to a song or something. There is no pattern other than BT and this phone hate eachother.
It's frustrating because I don't know when it will reboot. There are no options that I can see to try at this point other than look for something else or plug a stereo miniplug into the MX, which I'm not a fan of doing.
I've not done a factory reset due to the time and inconvenience of getting it all setup again. I've not tried to have VZW replace it.
Any ideas?
Well, a factory reset did not fix this problem.
ShanMan14 said:
I had an issue with a New Potato Tunelink and choppy audio (I have a thread in here somewhere).
I bought a Kinivo BTC450 Bluetooth Hands-Free Car Kit and it does not suffer from the same audio problems, it sounds great... when my phone isn't rebooting.
The only time my phone reboots is in the car. I've disabled Active thinking it might have something to do with that, but no. If I turn off BT the phone doesn't reboot. There is something with my VZW MX and this Kinivo paired together that creates a situation where it unexpected and randomly reboots.
This morning it rebooted almost immediately after connecting. Sometimes I can manipulate the controls, pick a song and start playing it and it will reboot shortly thereafter. Other times it won't reboot and will start working until I go to skip to a song or something. There is no pattern other than BT and this phone hate eachother.
It's frustrating because I don't know when it will reboot. There are no options that I can see to try at this point other than look for something else or plug a stereo miniplug into the MX, which I'm not a fan of doing.
I've not done a factory reset due to the time and inconvenience of getting it all setup again. I've not tried to have VZW replace it.
Any ideas?
Click to expand...
Click to collapse
I've experienced the same thing, but only twice and I connect to bluetooth multiple times per day in both the car and a standalone headset. I can't see any pattern, but it would certainly be nice to know how to prevent it.
I was having trouble with random reboots and I think it was the Updater app running in the background that may have been causing it. I saw that app running, went to Settings and checked for updates (obviously no updates yet). Ever since then, no random reboots. I use Bluetooth every day with a headset and Car audio device. BT working way better than any CM ROM I ran on prior devices.
Sent from my Moto X using xda app-developers app
Something I noticed today while driving was my Bluetooth audio would cutout every few minutes. It only happened on my Nexus 5 with an alpha ROM, but was fixed later. Anyone else notice this?
gakio12 said:
Something I noticed today while driving was my Bluetooth audio would cutout every few minutes. It only happened on my Nexus 5 with an alpha ROM, but was fixed later. Anyone else notice this?
Click to expand...
Click to collapse
On the new moto x? No, I just had a couple hour car ride with zero issues listening to Play Music and Slacker Radio. Made a few calls, no issues either.
This happened to me on a 20 mile bike ride. Horrible having choppy audio for almost a few hours
I just noticed this too. I do have a Moto 360 as well so maybe that is messing with the blueooth? I have gone a couple car rides and it's perfect, and others it's really choppy.
This does seem to be a problem with me too. Sometimes perfect and sometimes not. When connected to Bluetooth I notice that Google maps speaker goes in and out as well as moto voice while driving
I can confirm that if you have a 360 this is the cause. You can verify this by disconnecting the 360 through wear and the problem going away. For now what I have due is set up an IFTT to disconnect wear when by car's Bluetooth is connected.
I actually don't have anything else connected via Bluetooth and it still happens to me.
I figured it out. I was driving and I turned off Bluetooth completely and the voice worked perfectly. As soon as I connected back to Bluetooth the voice got choppy again...
I looked over in the Note 3 forums, and users were experiencing the same thing. Someone said to listen to music with the screen on to fix it. Today I listened to music with the screen left on and sure enough my music didn't stutter once the whole car ride.
This leads me to think either the processor is getting clocked too low for playing music through A2DP when the screen is off, or perhaps active display makes it stutter whenever it activates. I will look into it further today.
In the mean time, does anyone know of a processor control app that will change the minimum processor clock if bluetooth is connected? Perhaps there is one with a tasker plugin.
I'm experiencing the same issue, really sucks.... I'll try disconnecting the Moto360 on my drive today and see if that fixes it - although I swear I've had the issue before while it wasn't connected.
gakio12 said:
I looked over in the Note 3 forums, and users were experiencing the same thing. Someone said to listen to music with the screen on to fix it. Today I listened to music with the screen left on and sure enough my music didn't stutter once the whole car ride.
This leads me to think either the processor is getting clocked too low for playing music through A2DP when the screen is off, or perhaps active display makes it stutter whenever it activates. I will look into it further today.
In the mean time, does anyone know of a processor control app that will change the minimum processor clock if bluetooth is connected? Perhaps there is one with a tasker plugin.
Click to expand...
Click to collapse
SetCPU could possibly do this. You can definitely set the minimum CPU clock, but I'm not a 100% whether you can get it to do this WHEN a bluetooth device is connected. SetCPU has a profiles where you can define certain parameters based on conditions.
Of course, before you can get SetCPU working you'll need to root your phone and I have a suspicion that all other CPU clock apps will need root access too.
Has anyone had any luck resolving this?
gakio12 said:
I looked over in the Note 3 forums, and users were experiencing the same thing. Someone said to listen to music with the screen on to fix it. Today I listened to music with the screen left on and sure enough my music didn't stutter once the whole car ride.
This leads me to think either the processor is getting clocked too low for playing music through A2DP when the screen is off, or perhaps active display makes it stutter whenever it activates. I will look into it further today.
In the mean time, does anyone know of a processor control app that will change the minimum processor clock if bluetooth is connected? Perhaps there is one with a tasker plugin.
Click to expand...
Click to collapse
I'm hoping that either an OTA or Android L will fix this. My Moto X is fine when I'm using my Motorola S11-HD headset, but when connected to my car it goes in and out every few seconds.
So it isn't the processor. So far i have it down to either Wi-Fi or active display. Will report more when i find it.
Turning Wi-Fi off while connected to my car Bluetooth has fixed the issue for me. At least, so far it has.
I'm using PowerAMP for playing music and when I enabled the "high priority" setting in the headphone/bluetooth settings it seems to have resolved the problem until today. This morning on the way from work it started to cut out every few seconds. grrrr...
I have 2 bluetooth adapters in my car, one which takes only phone audio and one which takes phone and media audio, the latter one continously drops and reconnects phone audio (even after forgetting the other device), which makes me believe it is some hardware compatibility issue
I have posted on the official Motorola Forums but I though I should re-post here as well becuase well....XDA fixes things.
So I just purchased a Moto X 2nd Gen Pure Edition as an upgrade to My 1st Gen Moto G. Both phones have the same problem with the Bluetooth Audio sounding like a scratched CD skipping and studdering and it seems to be way worse a problem on the Moto X than I ever had on the Moto G. It's not buffering it happens with music on the phone. It doesn't happen every time I'm in the car but I'd say 50% of the time.
I would think it's the car but before the Moto G I owned a Galaxy Nexus and never had the problem as far as I remember. I'm sure I would remember it's really really annoying. I have even tested with a friends HTC M8 over a long road trip and there seemed to be no issue there. In my car (2011 Subaru Impreza) with the G or X after a time it eventually starts skipping even if it takes a couple hours.
So I did some research before and have tried various things.
I have disabled the Wifi while connecting to BT as Motorola has recommended to owners of other phones. That didn't help them it doesn't help me.
I have removed all other BT devices from the phone while connected. Nope
I have removed the Phone in the profile so my car doesn't try to use it as a phone as well at the same time. Nothing
I have done all of the above at the same time stopped every other program other than Google Music and added the phone to my car fresh and I still have this issue.
During my research about my car the only complaints similar I found seem to come from someone else with Moto phones. I dont' know what they do special with their Bluetooth but it's not helping me out.
You could try to upgrade your car's firmware. Some dealers do this for free, with some cars it is easy to do yourself
godutch said:
You could try to upgrade your car's firmware. Some dealers do this for free, with some cars it is easy to do yourself
Click to expand...
Click to collapse
This is what fixed the audio in my Mustang with Sync. The Ford dealership did not charge me anything for them to do it.
Sent from my XT1095 using Tapatalk
Hey guys,
Love my new S6, because of memory limitations, I'm using spotify more than the music player. I noticed that when I listen to music, the volume keeps changing by itself (but remains at the same "number" that I set), I believe it's an EQ problem due to the voice/instrument equalizer function that keeps adjusting one VS the other. I was able to downgrade the amazon appstore still has version 2.6.0.813 and it's better (but not perfect yet, I hope they fix this bug in the next spotify update, just wanted to share in case you though you were going crazy (as I did).
See http://forum.xda-developers.com/galaxy-s6/help/volume-changing-playing-music-t3089066
Solution
Just found the solution, please close topic
https://community.spotify.com/t5/He...-Distorted-playback-sound-levels/td-p/1028205
Disabling Nuplayer does not work
solution from the previous post does not work, I and others tested it and spotify volume is still messed up with Nuplayer disabled, downgrading seems to be the only solution as of now, sorry for the confusion
Remix22 said:
Hey guys,
Love my new S6, because of memory limitations, I'm using spotify more than the music player. I noticed that when I listen to music, the volume keeps changing by itself (but remains at the same "number" that I set), I believe it's an EQ problem due to the voice/instrument equalizer function that keeps adjusting one VS the other. I was able to downgrade the amazon appstore still has version 2.6.0.813 and it's better (but not perfect yet, I hope they fix this bug in the next spotify update, just wanted to share in case you though you were going crazy (as I did).
See http://forum.xda-developers.com/galaxy-s6/help/volume-changing-playing-music-t3089066
Click to expand...
Click to collapse
actually, I've noticed this problem with Google Play music as well.. I'm not using the equalizer.. for no apparent reason, at some points in certain songs, the volume will inexplicably lower, never quite recovering.. weird
same here. thought i was going deaf bc i had the volume up to 80%
Is it happening with your stock music player? I disabled Nuplayer and spotify is still misbehaving but the Samsung player works fine. I didn't find a Samsung user forum to report the problem but will look more into it.
old version works
Using S6 Edge, had this problem myself with spotify - can confirm using the previous version of spotify fixes the problem.
Agree there's points where it stoll changes volume ever so slightly but definatley a big improvement.
Can't post link to download due to new user restrictions.
Thanks to OP for posting his findings. Big help.
Peace.
I have been going back and forth with Spotify support for weeks on this issue, and it's been escalated to a Tier 2 person who I've been working with for almost a week now. Specifically, my problem is that the sound on any given song will vary throughout the song...it will start at whatever volume I have it set at, then suddenly get about 25% quieter for about 10-20 seconds, then go back up to original volume. This happens in almost a cyclical fashion my entire time listening to Spotify on my phone...whether it be through headphones, phone speak, or a bluetooth speaker. Spotify support even gave me another test account to try, which this issue also happen in on my phone....and they logged into my account on their end and done extensive listening tests, but are not able to replicate on their end. They had me try everything...clearing cache, trying with volume normalization ON, then trying with it OFF, WiFi only, data only, listening to cached music with no data turned on, re-installing, rebooting, updating, deleting all Spotify files/folders from the file manager, listening with corded headphones, bluetooth headphones, phone speaker, bluetooth speaker, etc. They really feel at this point that it's the Samsung Galaxy S6 that doesnt play nicely with Spotify, but they cannot figure out why. I'm still troubleshooting with them but so far no solution, only a ton of things ruled out as culprits. =(
This is a few days old but do you have sound alive enabled?
Sent from my SM-G920T using Tapatalk
I just got a 128 GB OnePlus 3T a few days ago to replace a dead Nexus 6P. So far I'm very happy with the phone (performance, screen, etc, camera is almost as good, blah blah) except one thing.
My bluetooth is completely nuts. Sometimes I will turn it on via Settings or Quick Settings and it will not turn on at all (the slider moves to the right but stays greyed out, then moves back to the left). Other times I am "luckier" and it switches on and begins scanning, and I can see devices in the area. I pair to a speaker dock via NFC or my wireless headphones via tapping on them and the connection is established, you can hear the speakers go "hey something connected".
So that's all fine. But then you start playing music. About 40-60 seconds in it will skip, crackle, or pause the music entirely. Sometimes the device makes its disconnect noise immediately followed by its reconnect noise. At this point pressing 'play' again starts the cycle over again, usually, or sometimes it will just refuse to "talk to" anything any more until you reboot the phone.
The phone came with OOS 3.5.4 out of the box and immediately got an OTA to 4.1.1. I was suspect about the upgrade procedure and sighed and did a full reset and re-flashed the full 4.1.1 image using adb sideload, logged back in, did the barest of minimum updates to the Google apps to make it stop complaining, and then tried music again. More skipping and pausing. My headphones have a volume up/down key on them, pressing that pretty much immediately results in a disconnect.
It's like the AVRCP (command) bluetooth protocol is "fighting" the A2DP audio stream protocol? It doesn't make any sense. This would also explain why my car audio has NEVER worked, because my head unit uses AVRCP to read track names and my headphones and speaker dock don't have any sort of screen to speak of.
I want to love this phone and don't want to pay double for a similar Pixel, but I might just have to return it if it's effectively useless at one of the main things I have a phone for! :crying:
Hmmm...My Bluetooth connection never have that issues. I used Bluetooth headphones and my car head unit. Running oos 4.1.1 as well.
Try dirty flashing your ROM, there might be something wrong with the drivers. Bluetooth commands (volume, pause, voice assistant, skip, etc.) work find on my headset, I don't believe its a compatibility issue.
If that fails, it might be a hardware defect?
I don't have problems with Bluetooth im using sony wireless earphones everyday. Try reformat the phone
Hi!
Android Nougat has heavy issues regarding bluetooth connectivity. If you Google it you will see...
I have the very same Problems like you with my car radio...
This must be finally adressed by Google.
Assassin1985 said:
Hi!
Android Nougat has heavy issues regarding bluetooth connectivity. If you Google it you will see...
I have the very same Problems like you with my car radio...
This must be finally adressed by Google.
Click to expand...
Click to collapse
Huh? Must be an compatability issue between the BT device and your phone. I have 6 active BT devices I use all the time with this phone and my tablet. Car stereo, fitnessband, speakers and inear plugs.
Only issue I sometimes face is the 'stuck in connecting to last used device' where BT needs to be turned off and on again. Wouldn't call it a heavy issue.
bluetooth perfect here. better than my lg g3 that i had previous.
So, more info. If 2.4 GHz WiFi is active in ANY WAY, the bluetooth goes nuts. AVRCP (bidirectional commands) make it worse. Putting the phone in airplane mode to disable the "ambient" wifi location scanning and such, then turning bluetooth on manually and playing some downloaded music, seems to work fine. Switch the WiFi on though (even though my access point is 5 GHz), bam down the toilet. Ugh.
I did a complete reset and flashed OOS 4.1.1 from adb, no improvement. I'm trying the Open Beta 4 right now but I doubt it will be any better.
Did you turn off the scanning feature?
Happens to me like once every 3 days. I usually reboot by then
evilspoons said:
I just got a 128 GB OnePlus 3T a few days ago to replace a dead Nexus 6P. So far I'm very happy with the phone (performance, screen, etc, camera is almost as good, blah blah) except one thing.
My bluetooth is completely nuts. Sometimes I will turn it on via Settings or Quick Settings and it will not turn on at all (the slider moves to the right but stays greyed out, then moves back to the left). Other times I am "luckier" and it switches on and begins scanning, and I can see devices in the area. I pair to a speaker dock via NFC or my wireless headphones via tapping on them and the connection is established, you can hear the speakers go "hey something connected".
So that's all fine. But then you start playing music. About 40-60 seconds in it will skip, crackle, or pause the music entirely. Sometimes the device makes its disconnect noise immediately followed by its reconnect noise. At this point pressing 'play' again starts the cycle over again, usually, or sometimes it will just refuse to "talk to" anything any more until you reboot the phone.
The phone came with OOS 3.5.4 out of the box and immediately got an OTA to 4.1.1. I was suspect about the upgrade procedure and sighed and did a full reset and re-flashed the full 4.1.1 image using adb sideload, logged back in, did the barest of minimum updates to the Google apps to make it stop complaining, and then tried music again. More skipping and pausing. My headphones have a volume up/down key on them, pressing that pretty much immediately results in a disconnect.
It's like the AVRCP (command) bluetooth protocol is "fighting" the A2DP audio stream protocol? It doesn't make any sense. This would also explain why my car audio has NEVER worked, because my head unit uses AVRCP to read track names and my headphones and speaker dock don't have any sort of screen to speak of.
I want to love this phone and don't want to pay double for a similar Pixel, but I might just have to return it if it's effectively useless at one of the main things I have a phone for! :crying:
Click to expand...
Click to collapse
Hi, I have the exact same phone and been having stuttering performance with Bluetooth and Sony MDR-X330BT and worked fine with the 1+ 3. I decided to tell the phone to forget the headphones and start afresh; big mistake headphones kept refusing to pair. I noticed they have the NFC symbol on one of the earpads so I enabled NFC and used app I had downloaded a while back, 'Tap-and-Pair' that did not work either. I did a search today and found a great app that worked - 'NFC Easy Connect' from the Play Store. Now all I need is stable connection from car system which appeared to be tied in with length of screen life before going to sleep but think it may be faulty Twingo as been on the car forum and found others with similar issues but different smartphone to the 1+ 3T. Hope this helps.
I got the OTA and one of the issues I ran into was actually listening to any media app ( Spotify, Youtube, YT Music, etc. ). Whenever I turn the screen off, the audio stops and when you wake the screen to unlock it has a terrible slowdown. I tried this in Safe mode and even factory reset and the issue is still there. I does not happen with the screen on if you're watching a video, etc. only when the screen goes off. Anyone else having this problem?
Edit: I think I found and workaround for this and was driving me crazy cause I listen to a lot of podcast/music whie driving Go to settings/system/developer options/default usb configuration/ and switch it to " no data transfer ". DO NOT tick any other option.
Yes, I am having the same problem, and since I use a wired headset for work calls all day, this is a significant problem.
Your work-around appears to work, but this needs to get fixed.
I have the exact same problem on my Pixel 6 since the March update, identical symptoms including the massive slowdown, and it's infuriating. While doing tests to try to find a work around it suddenly also blasted to 100% volume for some reason causing hearing damage.
April update fixed this issue.