I haven't seen anyone else post this yet so I'm hoping someone can help me out. I have a Bluetooth speaker in my car that works fine on stock or on kit Kat roms. But on every lollipop rom I've tried, the audio through the Bluetooth is slightly slowed down (resulting in everything sounded a little lower) and kind of choppy.
The audio plays fine through the phones speaker or through a headset, it's only on Bluetooth that this happens.
Any body else having this problem? Any suggestions?
Same issue here.
I think it may be the speaker I'm using, because I had the same issue when I connected my tablet to it that is also running lollipop. I need to find a different Bluetooth device and see if the problem persists.
supermatt9 said:
I think it may be the speaker I'm using, because I had the same issue when I connected my tablet to it that is also running lollipop. I need to find a different Bluetooth device and see if the problem persists.
Click to expand...
Click to collapse
I was doing a search on this issue myself, which brought me here. It's actually only one speaker I have that does this, and it's the newest BT device I have. It's the HDMX Rave portable BT speaker. It worked fine with the KK ROMs I was using at the time I got it, but ever since updating to LP, only that speaker of all the BT audio devices I own does that.
Weird...
Similar Issue
Hi,
I've also experienced this, although it seems my Bluetooth plays much worse than yours. It's slow for a bit, then choppy and breaks up, then it'll speed up the music to get back to where it should be. It renders Bluetooth music completely unusable.
I've found:
High CPU usage causes this in KK (skydragon) for me. The high-usage culprit is the netd module, not sure if that's relevant.
I've flashed Jasmine Lollipop (5.0.11) lots of different ways, with several different modems, and it still has this issue.
It doesn't seem to depend on the app, as it happens with the default music app and with Spotify (192 Kbps).
It happens on both of my Bluetooth devices, a cheapo portable speaker and my nicer car stereo. I don't know the BT versions they use.
Disabling WiFi helps a little, disabling data does nothing.
Anyone have any workarounds?
i had the same problem when connecting to my car speaker.
funny thing is some days it works great, and other days all of a sudden it just plays all slow. anyone got fix?
So I've been doing some more tinkering. Turning off WiFi will fix the issue for my "dumb" bluetooth speaker (it's a pair button and a power switch only), however it will only fix the issue for the first ~3 minutes on my Clarion car stereo (with all sw updates). I've disabled literally every Bluetooth service, activity, provider, and responder that isn't essential for A2DP connections. I'm able to access the hidden menu item for Bluetooth testing, but I don't really know how to use it. If someone has directions for that I'd gladly put my phone through the paces.
Related
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
So, I'm having a strange issue with my new Note that I can't quite determine where the root cause may be, or if it's a known issue.
If I register my Note with my car as both a phone and an audio device (how the Infiniti nav/stereo works) I can use the Note as a phone fine UNLESS I start an audio app, such as Pandora. Once a2dp audio starts the Note will no longer connect as a phone device, but it works fine for audio.
I had the phone paired with the stock ATT rom but only used it as a phone, so unfortunately, without a restore to stock, I can't tell if the problem exists with the stock rom.
I flashed to flappjaxxx's rom (which I love) the same day I setup the phone to run Pandora via Bluetooth and that's when I started seeing the problem.
I also see some random connect/reconnects that seem a bit more than usual.
So, I can't say there's a correlation, or if this is a known ICS beta issue or what, but I'm hoping it is and that it's not a design flaw
Way I see it it's either:
1. Flashing to any ICS beta rom has the problem, currently?
2. It's in flappjaxxx's build (doubtful)
3. It's user error...(possible )
4. It's an app issue (ie. Pandora is causing the problem?)
Anyone have any thoughts, suggestions or insights? I've done some searching but haven't found this exact issue yet on any posts.
Thanks!
I have a Kenwood DNX9960 in my Avalanche. It connects also for phone and for streaming media. I can be streaming media from either the stock music player or an internet site like pandora or TuneIn and my calls will automatically come through. When the call ends it goes right back to streaming.
It autoconnects to both as long as my phone is in range when I turn on the kenwood. I did have an issue at first where it would not autoconnect. I deleted the pairing from both my phone and headunit. Then when I repaired I paid close attention to check any boxes to "Always" allow connection and I haven't had any issues since.
I understand the normal pairing process, I've had several phones before that worked fine prior to the Note. So, I'm thinking that it is probably a corrupt bluetooth db... I'm going to be reflashing to Flaps new rom and we'll see how that does
Is there a way to delete the pairing from the nav? I would try that
Sent from my SAMSUNG-SGH-I717 using xda premium
There is. I've tried it all, on both sides of the pairing.
I've reflashed the phone to the B6 from FJ, still no joy. The pairing db was new (so no chance of corruption on the phone) and the pairing deleted on the device.
It seems to be a problem with the phone switching between a2dp and phone bt. When a call comes in (while playing say Pandora over bt) the audio cuts out and then the car shows "disconnected" and then "connection failed" if trying to reconnect to the Note as a phone (ie hitting the phone button in the car).
I'm hoping it's the current ICS build. Just have no way to really know. Hoping some other folks will have seen the same issue.
Going to run some tests with different audio sources and see if the behavior is the same.
Well things seem to be working now, for no obvious reason I'll have to assume that the reflash resolved the issue, I just can't tell for sure why it didn't work immediately after. I think it's due to deleting the old pairing on the car and not shutting down the vehicle.
Cheers.
BT connections
I have similar problem connecting to van audio system (vauxhall). After some experimentation it appears to be an ICS problem, if I reflash my note with gingerbread I have seamless connections for both audio and phone. As soon as I upgrade even with offical ICS bluetooth connections become problematic, I can pair but not autoconnect. Tried samsung and they just "fob off" with it's an incompatable device. Until a bug fix is issued it appears as though it's a choic of staying with gingerbread and have a working system or ICS and no handsfree.
Strange new problem...
I use a bluetooth car stereo, and on my phone I have "Smart AudioBook". Basically what happens it, when I start the engine, the phone and stereo sync automatically and it starts playing my audiobook from where it left off. When I turn the car off, it stops.
This all worked fine when I was using a previous ROM (one of the SuperNexus ones, 4.2.2 I think).
I recently changed my ROM though and upgraded to the CM10.2 jellybean 4.3 rom.... but there was some pretty terrible battery issues, and the bluetooth problem started. (Which ill describe below).
I thought it might be a ROM issue though so I tried SlimBean (another jellybean 4.3 rom) and that fixed the battery problem, but the Bluetooth issue was still there... but I couldnt see ay other references to 4.3 causing bluetooth problems (they were apparently all in 4.2, though I never had an issue before..)
THE PROBLEM:
The book will play normally, for a couple minutes or so, but then suddenly the audio will stop, and the stereo screen will say "paused". But if I look at my phone screen, the audiobook is still running (silently thought). I cannot unpause it using the stereo button.
BUT.. if I actually pause it on the phone screen, THEN I can unpause using the stereo and it will start playing through the car speakers again.
This cant be a problem with the stereo, as nothing has been altered on it. This is clearly an android thing.
I am considering one of the 4.2.2 ROMS to install next, and see if that solves anything, but I was wondering if anyone out there had any thoughts on other ways to fix this?
Thankyou
Bluetooth and cm dont mix. 4.3 is still in early stages. Best bet is custom stock based 4.1.2
This has bin covered alot.
--------------
alliances+siyah
I started to get audio dropouts over blue tooth when I upgraded to 5.0. The dropout were quick just like a record skipping. I have tried on several different programs Spotify, google play, and internal phone audio. All were same result. Skipping audio. At first I thought it was the ROM I was on. So I went back to stock, and same issues. I also tried NU player and awesomeplayer in dev settings. Same result. I am pairing with a flexsmart x2. I have not tired any ASOP based roms so I suspect Samsung may be the culprit. Do you guys know if they changed any of the code in lolipop in bluetooth after kitkat? And perhaps did not make something backward compatible?
Let me know if you are on lollipop and having similar issues with note 3 sprint.
I'm having the same issue, I just thought it was my headset.
Sent from my SM-N900P using Tapatalk
Anybody tried Rocket Player, and enabling "Double Buffer" under Settings -> Sound?
The only times I've had problems is when downloading over Wi-Fi and trying to use Bluetooth as well, since they seem to use the same subsystem.
I'm stock rooted 5.0, although I'm now two updates behind...
I've experienced this problem, but not to the severity of you. I think other factors may have influenced my issue. I regularly use a bluetooth headset and heart rate monitor and I don't experience many issues. Are you sure its not the bluetooth device at fault? You could possibly have some dying hardware in the phone too.
i have gone back and forth between lollipop and kitkat the problem with the Bluetooth starts at 4.4.4 and increases with lollipop. 4.4.2 is fine.
Have you tried with a different Bluetooth device? I have one in the car that skips for approx. 2 minutes when I first turn it on, regardless of what phone is connected to it, but then it's all good. Same phones on the home stereo and zero skips.
Dan
Have you tried AOSP based ROMs? Obviously you'll lose Touchwiz features and S-Pen integration- but I have personally used the builds by Jdelano (both PAC ROM and Resurrection Remix) and the bluetooth has worked 100% fine on my car stereo (but that's all I've tested it with).
Asked a question a while back about the issue with Bluetooth audio cutting back to the phone speaker, is there a fix out for it yet? If not, do Huawei know about the bug?
Thanks
Original post text below.
I have this little problem with my new Huawei.
(I have a Mate 10 Pro, couldn't find a section for that specific model)
Whenever I connect it to my car or Bluetooth headphones, the audio from my phone will randomly switch from my car speakers or my headphones to the phone speakers. The only way to get it outputting audio through the Bluetooth device again, is by reseting my Bluetooth connection. However, it does this every time and its driving me insane.
Can someone help me with this? Thanks in advance.
Click to expand...
Click to collapse
My mate 10 pro have terrible bluetooth problems with my earphones, sbc low quality and very noisy. Acc totally broken.
Hxxli said:
Asked a question a while back about the issue with Bluetooth audio cutting back to the phone speaker, is there a fix out for it yet? If not, do Huawei know about the bug?
Thanks
Original post text below.
Click to expand...
Click to collapse
Can't help with a solution I'm afraid but I get the same on BLA-L09 C782, firmware 131. It sometimes refuses to connect to anything until I switch into airplane mode and back.
Other times it will connect fine then switch to loudspeaker almost immediately - even though bluetooth still says it's connected (and the play/pause button works on the device). It seems fairly random and reconnecting a few times gets it to work for a while, but it's annoying when it happens while driving.
My guess is that it's an audio routing issue, so most likely a software glitch.
Has anyone switched to a treble rom and still finding the problem? Or has anyone noticed it has gone with a later firmware update?