Related
Sorry for the long title, and I would post this in the HD revolution forum but I'm not allowed?
Regardless:
I switched to Android Revolution HD from Cyanogen about a month ago and this one issue is driving me frigging CRAZY!! Whenever I'm streaming audio through bluetooth either to my headset or my car it cuts out. I figured out today it's directly related to how many applications are running in the background or how much the processor is having to work.
If I'm listening to audio and try to browse the web it starts cutting out on the order of 1-2 times per 10 seconds. It's not continuing to play the song during the chop either, it straight up halts audio playback for about 1/10th of a second. The weird thing is that it does NOT do this when playing audio through the headphone jack. Only when streaming over bluetooth. The chop is very negligent but it sounds like the phone cutting audio for a notification but I don't have any.
I Googled this and found several different resolutions from turning off WiFi to turning the phone's radio completely off, none of which have worked. I've reinstalled the ROM a total of 3 times, the last of which I re-downloaded the file and checked the MD5. I did not have the problem unrooted or with Cyanogen.
Can anyone help and/or move this thread to the correct forum? Again I am not allowed to post under the development forum.
Thanks.
Okay. So today I did a bit of testing. I downloaded the latest version of Revolution HD and flashed to the new ROM. I love Sense 3.0, but this is driving me nuts. I reverted back to both the version of Cyanogen that I had, as well as their newest version. Both Cyanogen version work like they are supposed to, no streaming issues whatsoever.
I decided to try out Synergy, as a friend at work recommended it. I like Synergy so far just like Revolution HD but I'll be damned if it doesn't have the same issue. Audio cuts in and out while streaming any content over bluetooth. Youtube, MP3, doesn't matter. I'm half tempted to try every single sense 3.0 rom until I find one thats stable but it sounds like an isolated issue with my phone...
Just wanted to get this thread back on the front and update with the things I tested today. If anyone can help or has any ideas I haven't tried, then by all means...
Thanks.
I know I'm not the only one experiencing this issue as I see it crop up on almost every Android forum without resolution...
What do I need to do to gain access to the thread where a dev might actually read my post..
Edit: Oh I have to have at least 10 posts. Well hopefully someone will reply to this and give me the opportunity to raise my post count so I can elevate this issue...
I've the same issue running cm7. No music streaming over bluetooth.
Sent from my Motorola Startac running Atari 2600 software!
pwraggcan said:
I've the same issue running cm7. No music streaming over bluetooth.
Sent from my Motorola Startac running Atari 2600 software!
Click to expand...
Click to collapse
While it seems like the same issue CM uses different BT drivers then sense based roms.
The problem here seems to be a ram issue more then the BT issue. As stated when the music starts skipping is when other apps are in use while listening to music. Have you tried a different music player? What player do you use?
I have tried every player on the market. It's any media that's streamed, be it a Youtube video, MP3, or what have you.
Again, the problem instantly corrects itself when I run CM7. I actually thought it might be a CPU issue. I know there is the undervolt script on Revo HD so I tried changing around the CPU frequencies as well as running a non-undervolted version of the ROM to no avail. It really feels like a driver issue.
Is there someway to grab the drivers from CM7 and use those with the Sense ROMs?
Irishwake83 said:
I have tried every player on the market. It's any media that's streamed, be it a Youtube video, MP3, or what have you.
Again, the problem instantly corrects itself when I run CM7. I actually thought it might be a CPU issue. I know there is the undervolt script on Revo HD so I tried changing around the CPU frequencies as well as running a non-undervolted version of the ROM to no avail. It really feels like a driver issue.
Is there someway to grab the drivers from CM7 and use those with the Sense ROMs?
Click to expand...
Click to collapse
No it can't be done. The drivers CM uses are sub par compared to the stock drivers in sense based roms. Not sub par as in being bad but as in swapping less signal strength for a few rarely needed options.
Sense roms are not compatable with the open source drivers.
Now when you say it corrects is self are you testing with the same player on both roms?
Well, yes and no. Youtube videos play fine in CM7 and not in HD Revo. I do however use the default player in CM7 which is different than the players that I have tried with the Sense ROMs.
Irishwake83 said:
Well, yes and no. Youtube videos play fine in CM7 and not in HD Revo. I do however use the default player in CM7 which is different than the players that I have tried with the Sense ROMs.
Click to expand...
Click to collapse
To be honest I am not sure. I have no problems with my BT connection while listening to music oor watching YouTube but then I don't run my system using heavy apps like GPS. Don't trust a phone GPS at all lol. Burning can play a game and listen to music at the same time. It could be that with sense being a ram hog that it is eating up all your resources and sense CM roms don't have have sense it uses alot less. I run senseless rom built off of the official release and don't have this issue
Bluetooth Range
I am experiencing something similar with my music cutting in and out on my bluetooth wireless headphones... however, the issue is range. They work perfectly when they are in direct line-of-sight and within 5'-0". Once I put the phone in my pocket, the music cuts out. The same goes if I am in direct line-of-sight but farther than 5'-0". I've tried this with several bluetooth wireless headphones and my experience is the same. My assumption would be it's the ROM, but it's a fresh install and I have no other apps running other than the ones the ROM came with. Anyone has any ideas?
sarichter said:
I am experiencing something similar with my music cutting in and out on my bluetooth wireless headphones... however, the issue is range. They work perfectly when they are in direct line-of-sight and within 5'-0". Once I put the phone in my pocket, the music cuts out. The same goes if I am in direct line-of-sight but farther than 5'-0". I've tried this with several bluetooth wireless headphones and my experience is the same. My assumption would be it's the ROM, but it's a fresh install and I have no other apps running other than the ones the ROM came with. Anyone has any ideas?
Click to expand...
Click to collapse
What rom?
Sorry, Android Revolution 7.0.3
sarichter said:
I am experiencing something similar with my music cutting in and out on my bluetooth wireless headphones... however, the issue is range. They work perfectly when they are in direct line-of-sight and within 5'-0". Once I put the phone in my pocket, the music cuts out. The same goes if I am in direct line-of-sight but farther than 5'-0". I've tried this with several bluetooth wireless headphones and my experience is the same. My assumption would be it's the ROM, but it's a fresh install and I have no other apps running other than the ones the ROM came with. Anyone has any ideas?
Click to expand...
Click to collapse
I have the same problem. While the phone is in line-of-sight it works well, but as soon as I put it in my pocket the music cuts.
I tried IceColdSandwich 7.2; Android Revolution HD 7.0.3 and CM7.1 with MortPlayer and PowerAmp
The headset is a Jabra HALO2.
I did narrow it down to the software in the ROM Android Revolution HD 7.03 that is affecting the bluetooth transmitter on the phone. Is there a fix in the works for this? It would be a shame to install a totally new ROM for this reason alone since the rest of the ROM is absolutely fantastic!
I think that the problem is not related with the ROM, it's in Bluetooth technology. Distance, surrounding WiFi or other radio waves and of course the strength of transmitter and receiver (as usually they are very small).
I have the same problem with my two different headsets used with my desktop, laptop and mobile. Interruptions are very rare when headsets are close to the device, other conditions like movements and something in between are causing problems.
This is why I think that the problem is not in ROM or phone model, all my devices are having the same issue sadly.
imnamak said:
I think that the problem is not related with the ROM, it's in Bluetooth technology. Distance, surrounding WiFi or other radio waves and of course the strength of transmitter and receiver (as usually they are very small).
I have the same problem with my two different headsets used with my desktop, laptop and mobile. Interruptions are very rare when headsets are close to the device, other conditions like movements and something in between are causing problems.
This is why I think that the problem is not in ROM or phone model, all my devices are having the same issue sadly.
Click to expand...
Click to collapse
I would partially agree with you on the technology... but... the stock ROM allowed me to do things with my Bluetooth headsets that I could not do with this Android Revolution ROM. Using deductive logic, it is the ROM that is the limiting factor. I used to be able to get 30 foot range with my bluetooth on my phone with the stock ROM, but now all I get is about 3 to 5 feet and it has to be direct line of sight.
Don't get me wrong, Android Revolution is a wonderful piece of coding... it is just too bad it has this fault. If I knew how to code, I would try to fix this issue myself but I have no training and it would take an awfully long time before I was able to make anything useful to be considered a 'fix'. Hopefully someone can figure this out and share it!
imnamak said:
I think that the problem is not related with the ROM, it's in Bluetooth technology. Distance, surrounding WiFi or other radio waves and of course the strength of transmitter and receiver (as usually they are very small).
I have the same problem with my two different headsets used with my desktop, laptop and mobile. Interruptions are very rare when headsets are close to the device, other conditions like movements and something in between are causing problems.
This is why I think that the problem is not in ROM or phone model, all my devices are having the same issue sadly.
Click to expand...
Click to collapse
It turns out to be the ROM. I've finally gotten around to changing ROMs and bluetooth worked just like the stock ROM that came with the phone. AR has been upgraded to 7.0.4 but I haven't been able to get it working (prior to changing ROMs). Must've been some funny glitch with the ROM software support for the bluetooth device. I now get range of up to 50 feet (tested so far) with no line of sight (through wood framed walls).
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 was trying to pair my s3 to my stock car radio so I could stream music through the phone but for some reason it doesnt work anymore after I flashed a rom. Is there something in stock that I'm missing?
I'm currently on Wicked 2.0 and tried pairing but everything works except the music. I remember when it worked fine on stock but during pairing it gave me a 2nd option during connection called gconnect, gmusic or g something lol. My car is a 2012 that has a2dp capability and it did work the other day prior to flashing so before I go back stock any other ideas?
Well as always try restarting your phone, and maybe delete pairings that you have seen. Sometimes when I've paired, I believe it saves so you can do it easier. Just try deleting that and then retry. I may have it confused with something else though
Sent from my SPH-L710 using xda app-developers app
seoulseek80 said:
I was trying to pair my s3 to my stock car radio so I could stream music through the phone but for some reason it doesnt work anymore after I flashed a rom. Is there something in stock that I'm missing?
I'm currently on Wicked 2.0 and tried pairing but everything works except the music. I remember when it worked fine on stock but during pairing it gave me a 2nd option during connection called gconnect, gmusic or g something lol. My car is a 2012 that has a2dp capability and it did work the other day prior to flashing so before I go back stock any other ideas?
Click to expand...
Click to collapse
Be sure to check the changelogs of the Roms you are using to see if that is a known issue, as well as, search the specific thread for the Rom for any issues related to bluetooth streaming issues. Though I'm not familiar with Wicked 2.0, if it's an AOSP rom, they have had a2dp issues from time to time. If it's touchwhiz, you'll want to see if it could be a kernel related issue.
Having the same problem
ReapersDeath said:
Well as always try restarting your phone, and maybe delete pairings that you have seen. Sometimes when I've paired, I believe it saves so you can do it easier. Just try deleting that and then retry. I may have it confused with something else though
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I went to CyanogenMod 10.1-201330121-EXPERIMETNAL-d2spr-M1 and I have the same issue. I can no longer get Bluetooth audio to stream music properly. It starts fine, but then after a few seconds I get this weird slowing-down and skipping distortion.
I've unpaired, repaired, turned off everything, turned it all back on, taken out the battery, etc. The whole 9 yards, and I'm still getting the same thing every time I try and stream music.
pandemicsoul said:
I went to CyanogenMod 10.1-201330121-EXPERIMETNAL-d2spr-M1 and I have the same issue. I can no longer get Bluetooth audio to stream music properly. It starts fine, but then after a few seconds I get this weird slowing-down and skipping distortion.
I've unpaired, repaired, turned off everything, turned it all back on, taken out the battery, etc. The whole 9 yards, and I'm still getting the same thing every time I try and stream music.
Click to expand...
Click to collapse
With AOSP roms, such as CyanogenMod, a2dp has been a consistent issue. However, the recent beta of LiquidSmooth, 3.2.1, is what I currently have running on my GS3 and it had some sort of a2dp fix in it that restored streaming quality to bluetooth. Give it a shot. It'll operate similarly to CM10.1.
Flash the latest nightly of CyanogenMod for working a2dp. It wasn't working on the M1.
Sent from my SPH-L710 using Tapatalk 2
Vanakatherock said:
Be sure to check the changelogs of the Roms you are using to see if that is a known issue, as well as, search the specific thread for the Rom for any issues related to bluetooth streaming issues. Though I'm not familiar with Wicked 2.0, if it's an AOSP rom, they have had a2dp issues from time to time. If it's touchwhiz, you'll want to see if it could be a kernel related issue.
Click to expand...
Click to collapse
Could see anything noted beside me. i think it is an asop rom but can get it to stream music. I might go to cm10.1 or back to stock. I love this rom but I need my streaming audio lol
Works great for me on jelly bomb v13. I stream music to my headset and a portable speaker daily over Bluetooth.
Sent from my SPH-L710 using Tapatalk 2
seoulseek80 said:
Could see anything noted beside me. i think it is an asop rom but can get it to stream music. I might go to cm10.1 or back to stock. I love this rom but I need my streaming audio lol
Click to expand...
Click to collapse
CM 10.1 is AOSP. Any ROM under the "original development" thread is usually AOSP based. AOSP is what has had the A2DP issues, but recent versions of CM 10.1 & my ROM of choice, LiquidSmooth 3.2.1, have seemingly got the bluetooth issues fixed.
finally figured out just encase anybody ever needs to know but it was called GmusicConnect. It popped up but had to be done under aux out and config >bluetooth music pairing. totally separate menus then the actual phone call pairing
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