im using hellkat the 2/23/14 build (I have t-mobile galaxy s2)...its a great ROM everything seems to be working fine except for streaming pandora via bluetooth.
When i start pandora (using version 5)...the music plays fine no issues. But when I turn on BT to stream to car or any other device the music just keeps skipping to next track (skips after attempting to play the current selection for about 10 secs....i say attempting because it stays on the current track attempts to play it but i dont hear anything and neither the progress_bar for song nor timer move).
Before Hellkat I was using BeanStalk 4.4.2 and pandora was streaming fine over BT.
Things I have tried to fix this none of these worked:
1. Turning off wifi then streaming
2. Went in to bluetooth setting > 'Visibility Timeout' > set to 'never'
3. Tried un-installing pandora and reinstalling.
4. Went into recovery mode, wiped cache/ delvik cache
I believe this is not a bluetooth issue because I can stream youtube audio over BT from my phone to external speakers/laptop/car and that works fine.
Is there a fix for this issue that I just can not find or is this known 'issue'? Any suggestions for a fix?
Thanks
looks like this is possibly a known issue per:
http://forum.xda-developers.com/showthread.php?t=2658698
x2014d said:
looks like this is possibly a known issue per:
http://forum.xda-developers.com/showthread.php?t=2658698
Click to expand...
Click to collapse
Same problem here. I decided to switch over to Dirty Unicorn and everything works fine. Better battery life too. Unfortunately I could not post in the developer's thread to inform them of the problem.
similar behavior from other streaming audio apps
Have similar behavior on other streaming apps:
Spotify:
as soon as BT is turned on and connection is established there is no sound from phone or device the music is being streamed to. But the track does not keep skipping to next one like in pandora...its just silence.
if i turn BT off (on other device) while the song is 'playing' seems like the song status changes to 'pause' after a minute or so and if i press play ...music resumes with sound only from the phone.
Grooveshark:
If song already playing then establishing BT connection then nothing changes sound still comes from phone.
But if BT is established already then there is no sound from phone or other device. Until you break connection then press play on another selectin then sound resumes from the phone. I did a double check to make sure the volume was not turned down.
Rdio:
If BT is already established we get 'Media Player Error for {song}'
If we turn off BT and wait there is still not sound but it eventually causes reboot once it loops through a certain number of songs.
If you start rdio with BT off (turned off on remote device) then song starts with sound from phone.
If we turn on BT while a song is playing, connection is established but sound still comes from phone. But if you try to skip to next song, get Media player error again.
Having the same issue on Samsung exhilarate and cm 11 nightlies. It worked at one point in cm 11, but I can't pinpoint when it went awry...
Sent from my SAMSUNG-SGH-I577 using Tapatalk
Did anyone find the resolution to this problem? I switched to Dirty Unicorn and it works on and off. Sometimes it even turned off my bluetooth and I would have to reboot my phone to turn it back on.
Music Player does likewise
I have been using Avatar Rom for the last year or so and as most roms, it has its issues now and again. I am currently running the latest version based on CM11 and since I can't post on the developer thread I thought I would add my 2 cents here.
I have a set of bluetooth headphones and they work just fine except for recenlty on the latest kitkat verson of Avatar rom. It connects fine to the headphones. I can even start and stop the music from playing using the headset buttons, but when I hit play, the music progress bar goes full scale and hangs there for a time after which it advances to the next track and does the same thing. During all this there is no sound from the headphones. When I disconnect bluetooth it will then, after a time, begin to play the music from the phone speaker. I restored an earlier version of Avatar and tried it and it worked fine. I think it was a later version of Jelly Bean.
At any rate, it appears there is an issue with the CM11 KitKat. It may be KitKat all together. Since I haven't the posting history to post on the developer forum I decided to do it here. There was one post from someone on the develper thread that is having the same issue. Unfortunately the Avatar developement thread has very little activity and little or none from the developer. They are, however, still updating. At least they have a week or so ago.
Edit: Since there doesn't seem to be any immediate fixes for this issue I have reverted back to an earlier version of Avatar which uses CM 3.0.101 dated Jan 25th. This is working for now with the bluetooth headphones. I'll continue to use this one until such time as the issue is resolved or I find a ROM I like better.
Electraglider said:
I have been using Avatar Rom for the last year or so and as most roms, it has its issues now and again. I am currently running the latest version based on CM11 and since I can't post on the developer thread I thought I would add my 2 cents here.
I have a set of bluetooth headphones and they work just fine except for recenlty on the latest kitkat verson of Avatar rom. It connects fine to the headphones. I can even start and stop the music from playing using the headset buttons, but when I hit play, the music progress bar goes full scale and hangs there for a time after which it advances to the next track and does the same thing. During all this there is no sound from the headphones. When I disconnect bluetooth it will then, after a time, begin to play the music from the phone speaker. I restored an earlier version of Avatar and tried it and it worked fine. I think it was a later version of Jelly Bean.
At any rate, it appears there is an issue with the CM11 KitKat. It may be KitKat all together. Since I haven't the posting history to post on the developer forum I decided to do it here. There was one post from someone on the develper thread that is having the same issue. Unfortunately the Avatar developement thread has very little activity and little or none from the developer. They are, however, still updating. At least they have a week or so ago.
Edit: Since there doesn't seem to be any immediate fixes for this issue I have reverted back to an earlier version of Avatar which uses CM 3.0.101 dated Jan 25th. This is working for now with the bluetooth headphones. I'll continue to use this one until such time as the issue is resolved or I find a ROM I like better.
Click to expand...
Click to collapse
I'm starting to think that the problem is with KitKat and not any specific custom ROM. I recently flashed The Collective and everything is working pretty good. The con to this is that the functions like "volume wake" is not implemented in this version
I also ran a search for "bluetooth" on each of the posts regarding new and active ROMs and it seems that their are very little mentioning of any fixes to this problem. It is as if there are little testing done regarding pairing the phone's bluetooth with the car's system. I would love to have this problem address but it seems that I don't have the correct amount of post to raise up the problem in the developer's thread. I hope this post catches developer's attention regarding this matter.
At the end of the day, I still love all these developers' work because without them, the S2 would've been dead a long time ago. :good:
Same issue.
Phone= Note 3 running TW kitkat on Tmobile
Connecting device: Ca-Fi Android head unit
Thinking its a Kit Kat issue. My head unit works fine when connected to another wifi source. Pandora never starts playing music. Just skips through songs.
I try streaming from phone to headunit over blutooth and pandora on phone keeps not responding. i have done factory resets, different phone roms, dns edits, congestion mods, network tweaks. same behavior regardless.
Fixed by turning off voice over LTE
Sent from my SM-N900T using Tapatalk
I recently updated to the deodexed stock kitkat rom with kt747 kernel. Everything is running fine except audio files in every program but poweramp have major crackling/static issues. The audio files play fine on my computer, it happens both over headphones and through phone's speaker. I use poweramp for all of my music but am really missing being able to use pocketcasts. Audio in youtube app also works fine. I have tried a factory reset and am at a loss for what else I can try to fix the problem. If anyone has any advice or tips or is experiencing a similar problem I would be very grateful to hear from you.
I think that the DSP doesn't process it right with a KK kernel although I do not have issues on stock kk ......have you tried a different audio processor like DSP manager or viper4android etc....?
Tried both of those and it didn't seem to help. Oddly enough I had one podcast today that I was able to play through pocketcasts without audio issues, but all the rest of my podcasts were ****ed up.
Well try a different kernel.....I read reports that some kernels don't provide enough power to the DAC and so it can cause crackling
Is anyone else having Bluetooth audio problems on 5.0? I can play music and video just fine over Bluetooth, but whenever I launch a game like Real Racing 3 my audio completely breaks up, and is unusable. It's not stutter every few seconds, it's a constant break up of the sound.
I've tried a few different games, and two different Bluetooth audio devices, no joy.
Odd thing is, this issue is the same when I try to do a screen cast to my chromecast. The audio is completely messed up and stuttering.
My N7 2013 is on stock (no root) Android 5.0. I did a clean install, formatting the entire tab. I have very little installed on it. I've done some searching here and on Google but all the posts relate to the 4.4.2 update, and was meant to be fixed...
This is my first post so if this is misplaced or otherwise please bear with me...
So, I just recently flashed a custom ROM to my LG G3 (D850) to try. Its my first time doing so, and I put the LiquidSmooth 4.0 ROM to my phone without any issue, and I love evey bit of it thus far.
My issue however: I drive a 2015 dodge challenger and it has this Bluetooth uConnect system which I use for media streaming through spotify. I have come to realize that the audio quality is far better than the stock ROM, when it works. There seems to be an odd phenomenon where the system clear is getting the data, as it shows metadata no problem, however audio itself doesn't seem to come through unless I manually unchecked media access on my device, and recheck it. I have tried disabiling the viper4android driver and that made no difference. Is there anything I could do to resolve this?
This is incredibly frustrating. I had none of these issues with bluetooth on my S8+ whatsoever.
So one annoying thing that stood out was the bluetooth on this device. It keeps skipping and stuttering tracks whenever I play it on my Bose QuietComfort 35. It's normal on all my other wired cans but I usually use the QC35 alongside my phone during commutes.
Just to clarify, I'll list down all the "fixes" that I've tried. Obviously NONE of them fixed, or even alleviated the problem.
Cleared cache (this one just doesn't make sense imo)
Removed battery optimization on my music apps
Turned off WiFi & Bluetooth scanning
Switch Bluetooth audio codecs
Updated to 4.7.6
and PLEASE... if you DON'T have this problem, do NOT post how you DON'T HAVE THIS PROBLEM here, I'm looking for fixes, not jokes. Thank you.
I also have a QC35 and I don't have any issue but I post anyway
Joking aside I'm using 4.7.6 and my QC35's firmware is 1.3.4 and using the HBC codec.
What's your bose firmware ?
What do you use as a music player ? (I'm using the default Google Play music)
And what do you mean my "It's normal on all my other wired cans" ? Why would wired headphones have stutters ?
raptor2003 said:
I also have a QC35 and I don't have any issue but I post anyway
Joking aside I'm using 4.7.6 and my QC35's firmware is 1.3.4 and using the HBC codec.
What's your bose firmware ?
What do you use as a music player ? (I'm using the default Google Play music)
And what do you mean my "It's normal on all my other wired cans" ? Why would wired headphones have stutters ?
Click to expand...
Click to collapse
Everything's the same as you except I use PowerAmp as my music player and SoundCloud for streaming (both stutters/skips as well). I stated that I didn't have this problem on my wired headphones just to clarify.
I notice the problem most when I'm commuting and I have mobile data turned on. It went even more haywire when I downloaded something on Google Drive. Hopefully it gets addressed with Android Oreo and the official Bluetooth audio codecs being implemented.
Oh bad me I read the you said it was normal to have stutters while being red... Night too short.
I'll trying PowerAmp to see how it goes.
raptor2003 said:
Oh bad me I read the you said it was normal to have stutters while being red... Night too short.
I'll trying PowerAmp to see how it goes.
Click to expand...
Click to collapse
I think it has something to do more with the connections. It goes even bonkers when I'm moving around rather than laying in one place.
EpsilonT51b said:
This is incredibly frustrating. I had none of these issues with bluetooth on my S8+ whatsoever.
So one annoying thing that stood out was the bluetooth on this device. It keeps skipping and stuttering tracks whenever I play it on my Bose QuietComfort 35. It's normal on all my other wired cans but I usually use the QC35 alongside my phone during commutes.
Just to clarify, I'll list down all the "fixes" that I've tried. Obviously NONE of them fixed, or even alleviated the problem.
Cleared cache (this one just doesn't make sense imo)
Removed battery optimization on my music apps
Turned off WiFi & Bluetooth scanning
Switch Bluetooth audio codecs
Updated to 4.7.6
and PLEASE... if you DON'T have this problem, do NOT post how you DON'T HAVE THIS PROBLEM here, I'm looking for fixes, not jokes. Thank you.
Click to expand...
Click to collapse
I think I saw somewhere it's an issue with aptx HD, try to force Bluetooth codec in advanced settings to aptx or sbc.
vkass said:
I think I saw somewhere it's an issue with aptx HD, try to force Bluetooth codec in advanced settings to aptx or sbc.
Click to expand...
Click to collapse
I just said that switching Bluetooth codecs didn't work.
I'm having Bluetooth quality issues as well, particularly crackling and skipping. I noticed that if I download a file while streaming the quality will drop dramatically and the audio stream will crackle like crazy. I have tried all three codecs in nougat to no avail.
Should I upgrade to Oreo to get this sorted? Do custom kernels cause issues with the quality?
Thanks.
OnePlus 5t, theOne 7.1.1 (stock basically), viper4arise and Dolby
Update: when into EX Kernel Manager (specifically under the misc I/O settings), and change the I/O from ZEN to FIOPS. Not once has the music stuttered since, though I have only tested on SBC. If I get more results I'll bring them in.
Please note - I am on blu_spark, and I honestly do think it may have been the cause of the bluetooth skips/scratchiness. I turned off Dolby Atmos and Viper just to be sure.
Latest Oreo Beta build. Stream bluetooth, Pandora, iHeart and talk on the hands free no problems here. Lexus CT200h vehicle.
Would really check your cars manufacturer website. Most have a section where you can download latest firmware to a USB and flash your car to ensure you have the latest bluetooth firmware.
Working flawlessly on my car.
Anyone have any experience with the Oreo update?
Since updating to 4.7.6, I've experienced the following issues:
despite being connected to a bluetooth device, sound still comes out of phone speakers
static/distortion for a few minutes when initially connected to my car (2017 Chevy SS)
Upon connecting to car bluetooth, randomly the phone will call my phone number
I can usually fix these issues by either going into airplane mode for a minute or two or rebooting. Sometimes, I have to do this multiple times.
I've cleared cache but made no difference and I don't want to have to factory reset after every single update. Is it possible to flash factory images without nuking your data? You can do this with Google's Nexus/Pixel factory images.
I've got a different problem with 8.1 and BT audio. After upgrading to android 8.1, suddenly my car audio system doesn't receive songs data (artist, song, album). It's just display "no title".
Does anyone encountered similar issue?
raven6679 said:
I've got a different problem with 8.1 and BT audio. After upgrading to android 8.1, suddenly my car audio system doesn't receive songs data (artist, song, album). It's just display "no title".
Does anyone encountered similar issue?
Click to expand...
Click to collapse
Ugh, exact same issue. I don't suppose you're using a car with a UConnect system in it? Dodge, Jeep? All those crappy brands?
I am able to make phone calls just fine but I can't stream audio to save my f**king life. This happened right after the upgrade to 8.1 and latest update did nothing to fix this nor did it mention the issue. Has Oneplus even acknowledged the issue?
Im actually having the same exact issue, with Uconnect on a 2017 Chrysler 300s. Bluetooth skipping and sounds like crap. Have tried pretty much everything so far and no fixes
this what happen to me ...bluetooth to speaker klipsch ... sometimes got crack sound ...i mean wtf
Has anyone been able to figure this out? I'm still experiencing issues as well. OP5T and QC35.
I've been working OP support for almost 2 months via email and the cannot figure out how to fix this for be BT CALLS sound terrible,
I'm having problems with Bluetooth in a ford fiesta 2015. The phone is on 8.1.0 stock, no root. The device itself connects to the car perfectly, but fails to download the phone book, and says I loose signal when trying to make a call. The device registers that I've asked to call a certain person but nothing else happens afterwards.
I didn't have this problem on 5.0.4