I just flashed the M snapshot of CM10.1. I have it connect to my car Bluetooth. Phone part works fine. It's when I try to play music through the Bluetooth when I start to get problems. The sound will be blown out and fuzzy. After about 1-2 minutes, it will have this problem where I can only best described as " skipping" sound (similar to when a CD would skip). Sound drops out every second alternating with music. Sorry, that's the best I can describe it. I have had issues with poor Bluetooth audio (although different from this problem) before when I was using CM10, but then it seemed to be fixed in the early nightlies of CM10.1. The last one that worked fine was 12/24/2012. Wondering if anyone else has this problem and/or has a fix. Figured I would ask before reverting back to that last nightly that worked great.
jlor23 said:
I just flashed the M snapshot of CM10.1. I have it connect to my car Bluetooth. Phone part works fine. It's when I try to play music through the Bluetooth when I start to get problems. The sound will be blown out and fuzzy. After about 1-2 minutes, it will have this problem where I can only best described as " skipping" sound (similar to when a CD would skip). Sound drops out every second alternating with music. Sorry, that's the best I can describe it. I have had issues with poor Bluetooth audio (although different from this problem) before when I was using CM10, but then it seemed to be fixed in the early nightlies of CM10.1. The last one that worked fine was 12/24/2012. Wondering if anyone else has this problem and/or has a fix. Figured I would ask before reverting back to that last nightly that worked great.
Click to expand...
Click to collapse
This is a well known bug. It turns out that Google acknowledged it in 4.2.1 and is therefore not the fault of the CM team. CM10.1 had it last working in the 12-26 build before all the 4.2 changes were fully merged.
swiggs98 said:
This is a well known bug. It turns out that Google acknowledged it in 4.2.1 and is therefore not the fault of the CM team. CM10.1 had it last working in the 12-26 build before all the 4.2 changes were fully merged.
Click to expand...
Click to collapse
I'm surprised bug hasn't been squashed already then if it's a 4.2 problem. I guess I'll have to use aux cable for now. I guess the reason I assumed it was a CM problem was that I also had Bluetooth audio issues with CM10 builds. Thanks for the response.
you have three options for 4.2.1 and working ad2p
1. the unofficial cm10.1 1/22 build
2. the unofficial aokp 2/21 build
3. the official cm10.1 12/26 build
In having tried both, the performance (everything is smooth as butter) is much better on 2 and 1 is pretty much stock cm10.1. aokp and cm have slightly different customization options, but cm10.1 has specific LED controls that I need so I am sticking with it for now.
Related
I clean installed the "stable" release of CM10 the other day when it came out. My Bluetooth audio has been horrible since. The volume is really low but worse is that the quality is not good either. For phone calls it's use able but I connect it to my car and play music on it too. Needless to say, it makes the music just awful. I also use it with my Big Jambox in the house and this is awful too. I tried wired connection with the Jambox and it was great so it seems to be only Bluetooth audio. I was on CM10 night lies before flashing the stable one. I have tried clean installing the night lies that came after and still the same problem. One thing I haven't tried is clean installing the night lies before the stable version, like I had before. I just wanted to see if others are having this problem and if there is a fix for it first.
I am having the same problem. Is there a fix for this yet? I've been searching and found something about replacing a line in a .conf file however it was posted in gs2 forum.
jlor23 said:
I clean installed the "stable" release of CM10 the other day when it came out. My Bluetooth audio has been horrible since. The volume is really low but worse is that the quality is not good either. For phone calls it's use able but I connect it to my car and play music on it too. Needless to say, it makes the music just awful. I also use it with my Big Jambox in the house and this is awful too. I tried wired connection with the Jambox and it was great so it seems to be only Bluetooth audio. I was on CM10 night lies before flashing the stable one. I have tried clean installing the night lies that came after and still the same problem. One thing I haven't tried is clean installing the night lies before the stable version, like I had before. I just wanted to see if others are having this problem and if there is a fix for it first.
Click to expand...
Click to collapse
radiumX said:
I am having the same problem. Is there a fix for this yet? I've been searching and found something about replacing a line in a .conf file however it was posted in gs2 forum.
Click to expand...
Click to collapse
I got the same thing going on on mine guys ... Bluetooth messes with the sound , but for some reason its from time to time , like if i reconnect it it will work , when it wants to , I have a great system in my car , and its like if I had no base... which sucks lol!!
Yeah I tried reverting the conf fine and it broke a2dp
Sent from my SPH-L710 using Tapatalk 2
I just went back to the Experimental one before they released the stable and of course, the bluetooth audio is back to being good. Haven't flashed any of the nightlies since then. Anyone try the latest nightlies and see if any of them work?
Making a call (to any number... I called my voicemail) then hanging up will fix the quality. Hopefully there will be a fix soon.
Hi,
Coming from gnex... so I'm used to stock android ROMs...
So I flashed CM10 and another ASOP ROM onto the gs3... Having two issues...
1) I found that Google Music does not start playing when I connect to bluetooth with my car stereo... even if I press the button on the bluetooth.. I have to start Music manually.
2) The music quality is horrible... there's no bass at all... something is really wrong here... even playing with EQ it does not do anything... sound is very hollow... flat....
I never had these problems with my gnex and stock android roms... even the stock touchwiz for the gs3 from bell it was fine...
Anyone has any ideas?? I really don't want to put touchwiz roms on... If there's no workaround... I think I'm gonna get a nexus4.....
thanks!
This seems to be a common problem with Jelly Bean roms. My phone does the same thing. There are threads in the forums with temporary fixes, but I would say stick it out for another couple days until 4.2 becomes available to us from the developers. PLEASE don't go back to TouchWiz :crying: the nightmares.
-Brandon
I just hope 4.2 comes out soon... I miss my gnex....
felchi80 said:
So I flashed CM10 and another ASOP ROM onto the gs3...
... there's no bass at all... something is really wrong here... even playing with EQ it does not do anything... sound is very hollow... flat....
Click to expand...
Click to collapse
Not sure if you're experiencing this issue I'm about to tell you about, or something else.
But a release or two ago (not sure if it's fixed yet), the bass was "broken" for bluetooth on CyanogenMOD/AOSP.
Everyone who updated their CM10 started to experience a loss of bass when using bluetooth.
Prior to that it had been fine.
If it hasn't been fixed yet, I'm sure it will be soon. There is a "workaround fix" listed in the CM10 thread.
In general though, music via bluetooth is a big step down in audio quality vs. using the USB audio, which is now working in CM10.
CZ Eddie said:
Not sure if you're experiencing this issue I'm about to tell you about, or something else.
But a release or two ago (not sure if it's fixed yet), the bass was "broken" for bluetooth on CyanogenMOD/AOSP.
Everyone who updated their CM10 started to experience a loss of bass when using bluetooth.
Prior to that it had been fine.
If it hasn't been fixed yet, I'm sure it will be soon. There is a "workaround fix" listed in the CM10 thread.
In general though, music via bluetooth is a big step down in audio quality vs. using the USB audio, which is now working in CM10.
Click to expand...
Click to collapse
oh ok... let check it out.
thanks!
those threads can get so long... hard to follow every post..
So it seems the workaround is to make a call beforehand...
Are there any vanilla android roms that don't have bluetooth issues for our s3?
TW roms seem to have crappy battery life...
Is there a bluetooth audio fix for cm10? I love the rom, and don't want to go back to using stock. However, unfortunately the bluetooth audio in my car just does not work. When it connects it lacks bass, and volume. I've seen others say they have this problem as well. The workaround was to make a call and hang up, and when the music started to play again it had proper volume. I flashed cm10.1 to check it out and when I flashed back to cm10 this workaround no longer worked. Bluetooth is worse than ever now, and when I make a call or take a call it doesn't reconnect after I hang up.
I have seen a couple of posts detailing fixes but none I have tried have worked. Does anyone know if any of the other CM10 based roms or AOKP have integrated a bluetooth fix? Or if there is a fix for CM10 I can apply myself?
radiumX said:
Is there a bluetooth audio fix for cm10? I love the rom, and don't want to go back to using stock. However, unfortunately the bluetooth audio in my car just does not work. When it connects it lacks bass, and volume. I've seen others say they have this problem as well. The workaround was to make a call and hang up, and when the music started to play again it had proper volume. I flashed cm10.1 to check it out and when I flashed back to cm10 this workaround no longer worked. Bluetooth is worse than ever now, and when I make a call or take a call it doesn't reconnect after I hang up.
I have seen a couple of posts detailing fixes but none I have tried have worked. Does anyone know if any of the other CM10 based roms or AOKP have integrated a bluetooth fix? Or if there is a fix for CM10 I can apply myself?
Click to expand...
Click to collapse
I have been using slimbean. I don't seem to have the issues you are having. Granted its a 4.1.2 ROM. But in my experience I have had the best luck with this ROM. It has for me been the most stable, and the least troublesome.
I have exactly the same problem on AOKP
sent from ▪_▪
Yeah I found some code someone posted on another web site. Some were saying that some people have implemented the fix already but CM10 definitely doesn't work. I tried changing the sampling rates etc but no luck.
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'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.