Related
There are a number of problems with bluetooth on the Galaxy Nexus. Some may be Galaxy Nexus specific, some may be Ice Cream Sandwich specific, I am not sure... Bluetooth performance has been very inconsistent since the launch of Android. (Well, actually it worked perfect in the early days of the G1, but more recent updates seem to make Bluetooth performance more inconsistent.) I would really like to see Google focus on fixing these Bluetooth issues, and I do not know of any way other than starring these issues on code.google.com to bring this to their attention. I have personally experienced the following issues:
1. Rogue phone call upon bluetooth headset connect. This one is very annoying: sometimes the phone will dial the last-called number when a bluetooth headset is connected. Please star this issue if you'd like it to get fixed: http://code.google.com/p/android/issues/detail?id=26004
2. Galaxy Nexus Bluetooth and BT-button become sometimes unresponsive, BT button blackend out (dark gray), needs restart to fix. If you have ever experienced this, you know what I am talking about: sometimes you have to reboot the phone to get it to connect to a bluetooth headset or car. Please star this issue if you'd like it to get fixed: http://code.google.com/p/android/issues/detail?id=24522
3. Apps other than "Music" not receiving Bluetooth Play/Pause commands after 4.0 update. I think this is the cause of apps such as Pandora not auto-pausing upon bluetooth disconnect. Please star this issue if you'd like it to get fixed: http://code.google.com/p/android/issues/detail?id=23172
These issues have a very low number of stars, and do not have an owner assigned to them yet. Please help improve bluetooth performance by voting for these issues. Thanks!
Strange...I'm on AOKP and I don't see any of these issues...
Are you on 4.0.3?
Number 3 is app specific. Those other apps need updates.
I had an issue similar to number 2 when my Nexus was on stock. On custom ROMS, my bluetooth works fine. Are you still on stock?
Sent from my cm_tenderloin using Tapatalk
bekyndnunwind said:
Strange...I'm on AOKP and I don't see any of these issues...
Are you on 4.0.3?
Click to expand...
Click to collapse
I am on stock 4.0.2 (rooted) on a GSM yakju. I've been waiting for a more feature-complete CM9 before switching ROMS, but if you say AOKP doesn't have these issues then I might just switch to AOKP and try it out in the next day or two!
Updated: Problem persists after installing ROM AOKP M4.
adrynalyne said:
Number 3 is app specific. Those other apps need updates.
Click to expand...
Click to collapse
Ahh - good to know, though it is weird that Pandora v 1.5.12 still auto-pauses on bluetooth disconnect.
Bluetooth
I haven't had any issues with my Jawbone bluetooth. I do noticed that different bluetooths work differently with different phones which a big history and swapping different phones and bluetooth headsets. I would try a different bluetooth.
mralexsays said:
Ahh - good to know, though it is weird that Pandora v 1.5.12 still auto-pauses on bluetooth disconnect.
Click to expand...
Click to collapse
I could be wrong.
mralexsays said:
There are a number of problems with bluetooth on the Galaxy Nexus. Some may be Galaxy Nexus specific, some may be Ice Cream Sandwich specific, I am not sure... Bluetooth performance has been very inconsistent since the launch of Android. (Well, actually it worked perfect in the early days of the G1, but more recent updates seem to make Bluetooth performance more inconsistent.) I would really like to see Google focus on fixing these Bluetooth issues, and I do not know of any way other than starring these issues on code.google.com to bring this to their attention. I have personally experienced the following issues:
2. Galaxy Nexus Bluetooth and BT-button become sometimes unresponsive, BT button blackend out (dark gray), needs restart to fix. If you have ever experienced this, you know what I am talking about: sometimes you have to reboot the phone to get it to connect to a bluetooth headset or car.
Click to expand...
Click to collapse
I get #2. Usually it occurs with turning bluetooth on and off multiple times over a period of days or coming out of Airplane mode. I have got around it by leaving bluetooth on all the time. I found that BT does not actually use a much battery.
bekyndnunwind said:
Strange...I'm on AOKP and I don't see any of these issues...
Are you on 4.0.3?
Click to expand...
Click to collapse
I just flashed AOKP, so I should know within a few days if 4.0.3 really solves these issues for me. Thanks!
mralexsays said:
I just flashed AOKP, so I should know within a few days if 4.0.3 really solves these issues for me. Thanks!
Click to expand...
Click to collapse
Whatever is causing these bluetooth issues for me wasn't solved by switching to the AOKP 4.0.3 ROM. Got in my car this morning and bluetooth would not connect - had to reboot my GN. Upon reboot, bluetooth connected and dialed the most recently dialed number. I can't imagine that an app would be causing this, but I'm going to try stripping down my installed apps to the bare minimum and see if that helps. My car bluetooth is a Motorola T605 that worked flawlessly from the original launch of the G1 up until sometime around the Gingerbread releases started coming out, so I don't think it's an issue with the T605 bluetooth unit. I'll keep this ticket updated as I learn more about the issue.
mralexsays said:
Whatever is causing these bluetooth issues for me wasn't solved by switching to the AOKP 4.0.3 ROM. Got in my car this morning and bluetooth would not connect - had to reboot my GN. Upon reboot, bluetooth connected and dialed the most recently dialed number. I can't imagine that an app would be causing this, but I'm going to try stripping down my installed apps to the bare minimum and see if that helps. My car bluetooth is a Motorola T605 that worked flawlessly from the original launch of the G1 up until sometime around the Gingerbread releases started coming out, so I don't think it's an issue with the T605 bluetooth unit. I'll keep this ticket updated as I learn more about the issue.
Click to expand...
Click to collapse
AOKP M4 + Parrot MKI 9200 2.0.2 working fine here.
Checked for firmware updates to the T605?
Sent from my Galaxy Nexus using Tapatalk
No issues here with stock 4.0.1 yakjuux when pairing with Jawbone ERA bluetooth headset. I've seen other posts about issues with pairing with car software tho
daern said:
AOKP M4 + Parrot MKI 9200 2.0.2 working fine here.
Checked for firmware updates to the T605?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I searched, but there is no update for the T605 - I doubt Motorola will ever release one either since the T605 is a very basic bluetooth device - only supports phone and A2DP media - pretty standard.
Would certainly appreciate support for avrcp 1.3/1.4 - my Parrot looks a little sad when doing A2DP as it just displays a little scrolly thing on the display - would be mucho cooler if it displayed track name / artist.
Would be /awesome/ if I could browse the device's media from the Parrot...
One of the apps I uninstalled was the Google "Car Home" app - I suspect that Car Home is what was causing both the "unable to turn on bluetooth" and the "bluetooth dials the most recently dialed number upon connect sometimes" issue. Not 100% sure yet, but seems plausible since Car Home ties in to bluetooth as a system app and I haven't had the issue since uninstalling Car Home. It'll take a few more trouble-free days for me to be sure though... Does anyone who use the Google Car Home app (which must be installed as a system app) NOT have this issue?
It's definitely a hardware or driver problem and does not come from an app. I have this issue since day 1 on my Nexus and I have experienced it on all ROM's I have tried or baked until now. I hope Google or Samsung will do something with our complains.
Planet X said:
It's definitely a hardware or driver problem and does not come from an app. I have this issue since day 1 on my Nexus and I have experienced it on all ROM's I have tried or baked until now. I hope Google or Samsung will do something with our complains.
Click to expand...
Click to collapse
I wonder why some people never see this issue while we do. Is there any other way to draw attention to the bluetooth issues besides starring these defects at code.google.com? Before I made this XDA posts, there were 42 stars for what I consider to be the most important defect (Issue ID 24522 - "Galaxy Nexus Bluetooth and BT-button become somtimes unresponsive, BT button blackend out (dark gray), needs restart to fix"), but as of today, there are still only 49 stars for that issue. That means that only a small fraction of us experience this issue or that not many people care about it.
Although I'm not having any of the problems you describe, I have always found BT on Android to be incredibly unreliable. But then, I have always believed that BT is an absolute joke, the best example of a failed standard in the history of the universe.
The problems I have had consistently with my G1, N1, and now GN:
- Paired headset simply won't connect. Have to reboot to fix. Doesn't happen too often.
- Headset connects, but only media or phone audio, not both. For me this is the most common and happens a LOT. Multiple power cycles on the headset will sometimes fix, but sometimes have to reboot phone.
- Headset connects and will control the phone and music player, but no audio. This happens with some regularity. Have to reboot phone.
Same problems with three brands of headset: Jawbone original, Plantronics Voyager 510, and currently the Moto S305.
I haven't searched the db to see if these bugs are reported. I just quietly despise BT and Google's failure to implement it better.
I don't have these problems with my iPod or iPad, so fully believe it's Google's poor implementation of a poor standard.
More power to you getting the issues addressed, but I think that since BT, which is truly a joke, and yet has been accepted and is widely used by the general public, they are not going to care. Google sets their pain threshold for system failures and bugs fairly high and does not trouble themselves at all with issues that don't rise to that level. For example, here in Puerto Rico where I live, Network Location Services stopped working on TMO a year ago and Google has not fixed it yet despite several solid reports. Until they receive a cacophony, they don't care, and they won't receive a cacophony on something like NLS, because the general public has no clue that it even exists, even though it impacts their daily experience with location aware apps. It's quite frustrating.
GR
GR,
I agree that bluetooth has its share of shortcomings, but basic phone and a2dp audio is something that has been around a long time and really should "just work." I like bluetooth in the fact that I can choose to keep my phone in my pocket and just hop in the car and it's connected for phone and media. A built-in service such as bluetooth should never get stuck in this unusable state that requires a reboot to get it working again. (Especially in the car - that really sucks...) I like the fact that Google is constantly adding new cutting edge features like NFC, but it seems that this comes at the cost of overall stability for some of the basics like bluetooth.
Hi everyone,
The bluetooth on my GSIII has been a complete failure. You can follow the saga here (http://www.benzworld.org/forums/w245-b-class/1662643-2009-w245-samsung-galaxy-s-iii.html), but basically it connects to my car and has no sound with the stock ROM and refuses to connect to the car at all with the AOKP JB build. It suggests an android problem, so I'm wondering if the bluetooth stack can be reloaded to reflashed with something different. If anyone has any ideas, I'm all ears. Thank you!
I have a problem with one of my Bluetooth devices dropping and reconnecting. Not sure why is just one. It works fine on an iPhone. I'm guessing your GS3 isn't the international version?
Sent from my SGH-I747M using xda premium
Nope not international, SGH-I747M from Bell.
I'm trying this. Will report back.
evilmonkey1987 said:
I'm trying this. Will report back.
Click to expand...
Click to collapse
Sweet! please let us know!
I'm having a different issue. it connects and stays connected, plays music but it doesn't list the song/artist info on my eclipse screen but the SG2 will..
Update: no change with the new kernel. The phones pairs but there's no sound, just as was the case before.
evilmonkey1987 said:
Update: no change with the new kernel. The phones pairs but there's no sound, just as was the case before.
Click to expand...
Click to collapse
Try CM9. Bluetooth works much better with it. CM10 should have it fixed as well in a day or two.
Here's a 'six months later' update. My phone went through various android updates and I'm now on Android 4.1.1 (up from 4.0.4). The problem was still not solved, but instead of no audio, I now have one way audio, where people hear me but I don't hear them through bluetooth. I have also gone through a number of custom ROMs and kernels for my phone (including CM9/10 and AOKP) and nothing helped with the issue.
A couple of days ago, my girlfriend's HTC One X (finally!) got its Android update, also from 4.0.4 to 4.1.1. Her phone now works like a charm with the in-car bluetooth.
The solution I ended up with was a car cradle and a couple of NFC tags to control my phone in the car. My NFC tag that's stuck to my car cradle turns off WiFi, starts car mode, starts a car home app and turns my volume to max. All I have to do after that is connect the 3.5mm audio cable and I use my phone in place of the car's infotainment system. That way the phone integrates into the car as well and the only thing I lose are the steering wheel controls (they still work for volume).
My less technologically inclined girlfriend now has everything work auto-magicallly with bluetooth. So I guess all's well that ends well, but to anyone considering a US-spec Galaxy S III, watch out: the bluetooth issue is still not fixed. If bluetooth is critical, consider the HTC One X (but be warned: it has awful battery life!)
I have no issues with stereo Bluetooth and mono Bluetooth. Everything and everyone hears and plays fine. It might be an issue with your headset.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
colbynmeghan said:
I have no issues with stereo Bluetooth and mono Bluetooth. Everything and everyone hears and plays fine. It might be an issue with your headset.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Colby. What version of android, kernel / rom combo are you using?? There's SOOO many people having problems with JB and bluetooth, regardless of rom or kernel setup.
If you're on stock... just nm then.
luncht1me said:
Colby. What version of android, kernel / rom combo are you using?? There's SOOO many people having problems with JB and bluetooth, regardless of rom or kernel setup.
If you're on stock... just nm then.
Click to expand...
Click to collapse
What's wrong with stock? I have no major issues with streaming BT from my phone to my Mazda 3 head unit, or to my Sony MW600 earphones. Even track titles work (the only thing that doesn't work is time display). In my experience, Bluetooth works best on the stock ROM.
Stock Rogers ROM (DLK4 - JB 4.1.1), rooted
KT747 (1/9/2013) kernel
CWM Recovery 6.0.2.3
PlayerPro Music Player
On my old Xperia X10, I had CM7 and had no end of issues with BT:
- Sometimes it would connect and there would be no sound
- Sometimes it wouldn't connect at all
- Sometimes it would cut out after switching songs
- It would stutter a lot whenever Wi-Fi was enabled (but I think that was a problem with the Xperia).
When I tried CM10.0 on my S3 I had similar connection issues, just not as bad. Also, the volume gain over BT was much lower, so I had to turn the car speakers way up. Stock 4.1.1 doesn't have any of these problems. The only problem I had was the audio switching over to speaker after turning off the car, but I fixed it.
Also, BT is apparently broken in 4.2.1 in general, not just CM10.1. Google confirmed a BT patch that works on the Nexus 7, due for release with 4.2.2: http://www.expertreviews.co.uk/smar...confirms-android-4-2-bluetooth-streaming-flaw
TIP: Don't forget to turn up the volume on your phone. I don't know how many times I accidentally turned down the volume and thought that it wasn't working. Now I have Tasker do it for me whenever I connect. :good:
4.1.2 has Bluetooth working use it everyday. (Stock and ROM.) Can't tell u which combo I use at a time. I flash a different ROM everyday. As 4.2.1bluetooth is broken expect for task's AOKP. He has it workingish.
Now as connecting to a car. Depends on what it connects as. And I've learned going to and from ROMs when u connect a source hit the volume up 9/10 times it works
Sent from my SGH-I747 using Tapatalk 2
Is it possible at all to take the new bluetooth stack from JellyBean 4.2 and apply it as a mod to either the stock 4.0.4 Sense ROM or the upcoming (eventually) 4.1 Sense ROM? Or maybe even CyanogenMod 10?
I know that the new stack is actually quite broken for a lot of people, but I have the opposite problem. The existing bluetooth is broken for what I use it with, but the new one works fine. So I'd love to be able to backport it, since I doubt we'll be getting 4.2 for quite some time.
Just FYI the issue is with a Sony car head unit MEX-BT2500. Media/A2DP won't connect with Android 4.0/4.1 bluetooth unless the phone is the one to initiate the connection.... but the default behaviour is for the head unit to initiate it on ignition. So the only way to get it to connect is to start the car, wait for Bluetooth to be ready on the unit, turn bluetooth off on the phone and then turn it back on again. Obviously this is a bit of a faff, and even then the audio skips and sometimes just gets stuck. So it's really not usable.
Related bugs:
http://code.google.com/p/android/issues/detail?id=24012
http://code.google.com/p/android/issues/detail?id=29564
However I've tested my Nexus 7 (running 4.2) on this unit and it works 100% fine. Which is why I'd quite like to get the same bluetooth stack.
Having an issue with no sound emitting from any audio output on the phone, but sound will play through Bluetooth-connected device. No sound from front speaker (phone calls, dial pad), no sound from rear speaker (notifications, ringer, alarm, media) and no sound from wired earpiece/headphones. Seems like it's stuck in Bluetooth/headset mode, but turning off Bluetooth doesn't restore sound. Problem is intermittent, haven't determined pattern to the behavior.
Phone was rooted long ago but kept stock ROM. Flashed Paranoid Android 3.99 RC2 about a month ago, and problem seems to have started shortly thereafter, but not sure if related. Haven't tried to reflash.
Any suggestions? Tried searches, but didn't locate this specific issue.
SGH-T999 (US/T-Mobile Galaxy S3)
Is it a T999 or a T959? And flash back to stock.using Odin. If it still is a problem it's likely hardware related.
Sent from my SGH-T999 using Tapatalk
Sorry, phone is T999.....got rid of the T959 long ago, but must have been stuck in my head.
Will reflash this weekend and hope the sound issue is resolved. Thanks.
yardsale said:
Sorry, phone is T999.....got rid of the T959 long ago, but must have been stuck in my head.
Will reflash this weekend and hope the sound issue is resolved. Thanks.
Click to expand...
Click to collapse
Did some more investigating last weekend before flashing ROM (never did the reflash).....seems that often, not always, if I turn off the car ('13 VW) while still connected to phone Bluetooth, the phone's sound quits working (all sound). Rebooting phone and turning off Bluetooth does not restore sound. The only solution I've found is to reconnect to car's Bluetooth, then turn Bluetooth off before shutting down car, and that only works about half the time, but sound is instantly restored. My estimation is that this wouldn't be hardware related, is that a fair assumption?
I also have a Tasker profile set up on phone to disable PIN lock when phone is connected to Bluetooth device (enables Sena Bluetooth headset used with motorcycle helmet to function properly), could that be causing the problem? Anyone else experience this issue?
Please try another Rom. Some of the Custom Roms may not be uptodate with CM Checkins. This issue was reported a bit back. There were CM Code Fixes that may not have been incorporated in that rom.
I am using Slimbean 2.0 (Android 4.3.1) and have seriously tested its bluetooth capabilities.
its also been reported thst msny car manufacturers did not bother to put any time or money into their BT capable systems. they just threw it together so they could add to feature lists.
Lots of peopke have problems with BT in the car, especially on cm roms. but those are notorious for BT issues to begin with.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
Thanks for the replies. I flashed to Paranoid Android 3.99.1 RC1 but the problem still exists. I never had this issue with any of our vehicles, until switching to PA from stock ROM. If problem becomes unbearable, may go back to stock. Thanks again.
@yardsale
I should have mentioned in the previously. Please read this post of mine. Yes its a different Rom. However, here primarily the issue is that of hardware antenna of the T999 talking to the Car's antenna. Doc is 100 % correct, the manufacturers do use substandard Antenna. On that thread, someone else reported issues with two '13 VW for themselves and their brother's.
hi. I have done so many tests so far so I know what I'm saying.
most used ROMs for N7100 are heavly unstable with bluetooth.
effects are various, from stuttering in a2dp with BT headset to bad reconnecting to low power devices (example smartbands) etc.
again, to connect to some special device I need to reboot many times, for example some kind of internet things.
at the moment the ONLY rom, beside stock, that has a PERFECT manage of bluetooth is:
[OK] ---- [ROM][5.1.1][Haxynox] AOSP for n7100
and roms I tested that has not:
[NOT] ---- [ROM][5.1.1] 12.11.2015 Cyanogenmod 12.1 N7100
[NOT] ---- [ROM][6.0.1] Cyanogenmod 13.0 N7100 Build 8
[NOT] ---- Paranoid Android for Note II(GT-N7100)
[NOT] ---- [ROM][5.1.1_r24][Official][Nightlies]Exodus Android for Samsung note II
[NOT] ---- [ROM][5.1.1][Lollipop][Official][Nightlies] NamelessROM 2.1
[NOT] ---- [ROM] CyanoBiz - CM-13.0 - Doze enable - n7100 / Galaxy Notes2
[continue]
how to test:
there are many methods to test bad handling of bluetooth, most important test with daily use, but to prevent headache you can do in this way.
- pair any bluetooth headset or car free-hand kit.
- play some music to that device
- meantime go to bluetooth option and search for new devices
- if music stutters that rom is affected with bt issues, if not rom will never hurt you and your devices.
so: why I don't stay with Haxynox?
I would but that rom is
a little unstable.
vivavoice volume doesn't work.
bt file transfer crashes.
sometime reboots.
doesn't handle >16GB sd card.
doesn't handle movetosd.
developer is working on CM13 and left this.
please feedback here to have stable bluetooth back!
8rnity said:
hi. I have done so many tests so far so I know what I'm saying.
most used ROMs for N7100 are heavly unstable with bluetooth.
effects are various, from stuttering in a2dp with BT headset to bad reconnecting to low power devices (example smartbands) etc.
again, to connect to some special device I need to reboot many times, for example some kind of internet things.
at the moment the ONLY rom, beside stock, that has a PERFECT manage of bluetooth is:
[OK] ---- [ROM][5.1.1][Haxynox] AOSP for n7100
and roms I tested that has not:
[NOT] ---- [ROM][5.1.1] 12.11.2015 Cyanogenmod 12.1 N7100
[NOT] ---- [ROM][6.0.1] Cyanogenmod 13.0 N7100 Build 8
[NOT] ---- Paranoid Android for Note II(GT-N7100)
[continue]
how to test:
there are many methods to test bad handling of bluetooth, most important test with daily use, but to prevent headache you can do in this way.
- pair any bluetooth headset or car free-hand kit.
- play some music to that device
- meantime go to bluetooth option and search for new devices
- if music stutters that rom is affected with bt issues, if not rom will never hurt you and your devices.
so: why I don't stay with Haxynox?
I would but that rom is
a little unstable.
vivavoice volume doesn't work.
bt file transfer crashes.
sometime reboots.
doesn't handle >16GB sd card.
doesn't handle movetosd.
developer is working on CM13 and left this.
please feedback here to have stable bluetooth back!
Click to expand...
Click to collapse
On RR Lollipop I've had bt stuttering
on dr.ketan kitkat bt was very good
on CM 13 build 7 bt works just fine: tested on mazda infotainment, bt jack adapter, JBL speaker, laptop, pairing with other phone also ok and recently with SmartWatch 3, so I think it's related to hardware if you can't get it to work
thank you for reply. sorry but I don't think is hardware related.
I read tons of thread where n7100 owners wait for a build with decent bluetooth manager. most are still searching for. I was lucky as I found at least haynox build.
so I decided to share this.
did you test playing music through bt speakers and while listen music going to 'searching for bt device' screen?
8rnity said:
thank you for reply. sorry but I don't think is hardware related.
I read tons of thread where n7100 owners wait for a build with decent bluetooth manager. most are still searching for. I was lucky as I found at least haynox build.
so I decided to share this.
did you test playing music through bt speakers and while listen music going to 'searching for bt device' screen?
Click to expand...
Click to collapse
no, I think when it's paired with device and sound plays well, so there is no need to go there, but I#ll check it this evening
yaro666 said:
I'll check it this evening
Click to expand...
Click to collapse
thank you. this may be useful for me.
tested:
[ROM][5.1.1_r24][Official][Nightlies]Exodus Android for Samsung note II
[ROM][5.1.1][Lollipop][Official][Nightlies] NamelessROM 2.1
both have bt issues
yep, I had to go back to stock.. my sony smartwatch 3 was unusable.... I don't like to put my money on trash...
[ROM][5.1.1] 12.11.2015 Cyanogenmod 12.1 N7100
[ROM][6.0.1] Cyanogenmod 13.0 N7100 Build 8
Have problems with bluetooth calls (Static, robot voice), Music player is fine
As I added more bt devices it started to stutter rarely. I noticed that it only stutters when bt is searching, although it's connected.
CM13 build 7.
I believe it's related to data flow, it just can't send/receive that much data simultaneously
ok, after tried so many roms I can say that if you have that stutter bluetooth is less stabile than ideal. can be that you have devices where is less evident. but it's not the way to be:
if you can nandroid backup your note2 and try haynox build. you'll nave stable BT and in test never stutters. in fact there's no way to make it stutter with this ROM. but as said there are other issues..
less than ideal.
[ROM] CyanoBiz - CM-13.0 - Doze enable - n7100 / Galaxy Notes2
my hope for BT was fix by P.A.N. from i9305 github, but NO, it doesn't work well.
waiting for AOSP from same developer
Any news about this?
CM Roms were always weak about bluetooth stream. I have a 6p now and it's happening. On Pure Nexus I'm fine but would love to stay CM
after many devices and settings I came into conclusion, that bluetooth problem is related to android wear app. When I had paired SW3 and allowed Note2 to constantly search for my watch it stutters often, but after uninstalling all that crap, Note don't search for other devices when connected to 1 device and sound doesn't stutter, not even once.
I'm using CM13 build 10
Umm I posted some stuff in Ivan's build 10 rom thread. If you switch network to 2G instead of 3G, bluetooth calling works once again. I tested this about 20 times afterwards and it worked everytime. It even works with traffalguar square's rom.
Hope it helps.
[ROM][6.0.1][v6.18][Beanstalk][OFFICIAL][Great Experience][DU-Features][19.06.16]
This rom have bt issue too.
Still no solution ?
I found a good ROM
I've been struggling with BT Handsfree issue for a very long time. I almost bought a new phone recently, because of this issue. I drive a lot and I really need that function. Samsung original stock rom is so bloated and ugly that it was not an option. Unfortunately non of the CM and AOSP ROMS have fully working BT audio.
I found a solution: [ROM][GT-N7100][TW 4.4.4] Eclipse By AC version 9
It is a stock based ROM with TouchWiz UI. I don't like Samsung interface but this one is really debloated and very pleasant. I think I will get used to it. It's super stable and very fast. I moved to it a few days ago, and my Plantronics M70 headset is finally working like a charm. Just remember to make a full phone wipe before install (including data partition). I had some issues with that.