Hi XDA-community.
I've tried to find some solution but there is not so much information on this topic.
This issue is present only while using BT headset.
I've been using various versions of CM 10 - 11. And in some part of them (CM 10.1, 10.2) I've found some strange cracking noise in the background while i am using my BT headset. Different roms have different level of this noise. It can be clearly heard in CyanVivo 10.2. This thing shows up in video and audio. It makes listening to the music more or less unpleasant.
Is there anyone who has a similar issue or maybe knows how to solve this trouble ?
Maybe there's some way to combine 10.2 features with 10 bluetooth libs.
Currently there's no way to check CM 11, bluetooth headset is broken in a current stable build.
Related
I believe I have found an issue with the latest (stable + nightlies) cyanogen mod rom with Bluetooth headset audio, and before I go about posting to the Dev thread I wanted to get some help with understanding how or what info a need to gather.
I have a car stereo that has support for Bluetooth (both media and voice), and whilst the phone syncs to the unit and plays music just fine, when trying to place a call, all that can be heard is a loud buzzing when the call is connected (@ both ends).
The stereo is functioning correctly, and works fine for both voice and media with my SGS2 (also running cyanogen). I also have the same model stereo in another car, and the problem manifests on this unit too.
Prior to flashing cyanogen I was using other roms (both standard and mod's) and never had any issues with voice calls.
I have tried changing the baseband, and ril but this had not made any difference. I have also paired with other headsets and they work fine, so this is down to some compatibility issue with the stereo and Cyanogen's Bluetooth stack settings, I think.
Before posting this as a bug, is there anything else I should try, and if not what info do I need to gather (other than version numbers etc) to ensure I give the dev's enough info to work with?
Thanks
If it's in stable, use the issue tracker.
I was just wondering if anyone else was having problems with a bluetooth headset using Cyanogenmod 10.1? The call quality while using the handset is great, but when I use my bluetooth (Jawbone Era, Motorola Sliver Elite) the call quality is absolutely terrible, the person can't even hear what I'm saying.
I say Cyanogenmod because that's my favorite rom, but it also happens on AOKP, PAC, ParanoidAndroid, and pretty much every other Vanilla type Rom.
Any help or suggestions?
The same problem with Jawbone Era. All works fine in Samsung stock 4.1.2 ROM.
Yep. I have this problem, too.
Bummer, as I'm writing a Bluetooth headphone round-up for a magazine this month, and I can't review call quality without borrowing a friend's phone.
Known Issue
Hey guys the bluetooth isssue your speaking of is a VERY well known issue in CM its one of the few bugs that is still being ironed out. Its also present in basically every other aosp type rom because they are all based on CM. The awesome cyanogen devs are working on it constantly and im sure they will get it figured out :good:
So if you here any reference of an "upstream" issue in a ROM thread its most likely referring to it being an issue in CM and therefore the ROM in question. :good:
Bluetooth car connections drops and really bad audio quality when on call.
FanDroid09 said:
Hey guys the bluetooth isssue your speaking of is a VERY well known issue in CM its one of the few bugs that is still being ironed out. Its also present in basically every other aosp type rom because they are all based on CM. The awesome cyanogen devs are working on it constantly and im sure they will get it figured out :good:
So if you here any reference of an "upstream" issue in a ROM thread its most likely referring to it being an issue in CM and therefore the ROM in question. :good:
Click to expand...
Click to collapse
Hi everyone, I have used PARANOIDANDROID in the past for Samsung Note and had a great experience using it. Just installed the PARANOIDANDROID on my new HTC one.
I am having two issues that are forcing me to go back to a stock rom,.
1st) Bluetooth connection with car, when calling the audio quality is really bad. The person on the other end cannot understand what I am saying.
2nd) when on a call with a headphone /w mic and connected to my Mac, the mass storage keeps going on and off. This affects the audio quality of the phone call.
All other issues that have been reported here I am OK to way for, but the BlueTooth issue forced me to look for a stock ROM for now.
I hope the great the people working on these Rom ( Paranoidandroid and Cyanogenmod ) can fix these issues quickly.
no bluetooth for voip apps
I've tested CM on note I and II, the same issue shows up, I cannot use bluetooth with voip apps. Same goes for 10.2. Too bad
I'm using CarbonRom is both HD and HD+ and this problem is the same for both. Today, I made a phone call and the person wasn't getting enough volume and the words were garbled. I tried the headset with Google Voice search and VoiceToText in other apps. It is evident that the mic isn't working correctly. I tried a different wired headset and the result was the same. For reference the headsets are a Klipsh S4A and stock that comes with Galaxy S3. The onboard mic works as expected. I paired a Bluetooth headset and, surprisingly, that worked the best of all.
Sometimes this is a kernel issue. I reflashed the rom without the fstrim kernel and that made no difference.
I am thinking that this is a bug that may be in the various Android, custom roms and that's why I didn't post only in CarbonRom thread. It may even be a problem with stock. I don't think there are many people that use a wired headset with mic. I make phone calls with MagicJack.
Maybe a few people that have a headset with mic can try and report back if this is a problem for the particular rom they are using.
someone here http://forum.xda-developers.com/showthread.php?t=2388088 mentioned it worked with cm 10.1, maybe that one would work for you
king200 said:
I'm using CarbonRom is both HD and HD+ and this problem is the same for both. Today, I made a phone call and the person wasn't getting enough volume and the words were garbled. I tried the headset with Google Voice search and VoiceToText in other apps. It is evident that the mic isn't working correctly. I tried a different wired headset and the result was the same. For reference the headsets are a Klipsh S4A and stock that comes with Galaxy S3. The onboard mic works as expected. I paired a Bluetooth headset and, surprisingly, that worked the best of all.
Sometimes this is a kernel issue. I reflashed the rom without the fstrim kernel and that made no difference.
I am thinking that this is a bug that may be in the various Android, custom roms and that's why I didn't post only in CarbonRom thread. It may even be a problem with stock. I don't think there are many people that use a wired headset with mic. I make phone calls with MagicJack.
Maybe a few people that have a headset with mic can try and report back if this is a problem for the particular rom they are using.
Click to expand...
Click to collapse
Yes, I can confirm this issue, apparently.
I'll try to see what could be done.
Hi all,
The headphone port on my TP is broken and I'm on CM 10.1 Snapshot which wouldn't work with my bluetooth headphones, I could pair them but when I wanted to use them with Netflix or YouTube the sound kept coming out of the speakers even though the "media audio" option was ticked . I did a full uninstall of Android installed Evervolv AOSP Android 4.3.1 JB (20140129) and had exactly the same problem with that ROM. I know the headset works fine as I have it paired and working perfectly with my Samsung Note II.
I can keep trying different ROMs and versions of ROM's but I'm hoping someone here can tell me which of the (relatively) stable ROMS works best with Bluetooth?
Cheers,
Ben
Hi everyone, thanks for taking the time to look at this.
I'm having an issue where if I run any CM based rom I get "com.bluetooth.android has stopped responding" when connecting to my Mazda car stereo or my jawbone speakers. I've had this issue on every version of CM that has been out since November. If I use a stock based rom, everything works fine and I don't have any issues. It doesn't matter if I'm using 4.4.2 or 4.4.4, the previous scenario still holds true.
Any ideas what I can try in order to solve the issue or at least narrow it down further?
I really like flashing different roms and checking out the awesome features everyone has added, but I unfortunately need my bluetooth to work properly.
Thanks in advance for all the help!
nuggetfn22004 said:
Hi everyone, thanks for taking the time to look at this.
I'm having an issue where if I run any CM based rom I get "com.bluetooth.android has stopped responding" when connecting to my Mazda car stereo or my jawbone speakers. I've had this issue on every version of CM that has been out since November. If I use a stock based rom, everything works fine and I don't have any issues. It doesn't matter if I'm using 4.4.2 or 4.4.4, the previous scenario still holds true.
Any ideas what I can try in order to solve the issue or at least narrow it down further?
I really like flashing different roms and checking out the awesome features everyone has added, but I unfortunately need my bluetooth to work properly.
Thanks in advance for all the help!
Click to expand...
Click to collapse
Ha. I have the exact opposite problem. I have a 2013 Subaru Outback and every AOSP rom works perfectly and any stock rom has issues. Calls work fine on both stock and AOSP based roms, but media playback has always presented a problem for me on stock roms. On AOSP roms I can play Netflix, Youtube, music, etc through my car speakers but I can only get Play Music to work on stock roms. Sometimes on a stock rom, Youtube will play for 2 seconds but then cutoff the audio. The video will continue to play, but the audio is lost. Very strange.
I've searched around a bunch, and it looks like i's not an uncommon issue, but it doesn't look like there's a systematic solution. I assume there are too many variables (car makes, models, years, stereo upgrades, Nav options, etc) to be able to isolate an issue. You just have to keep trying different iterations.
Keep me posted if you find a solution.