Develop Bugs

BLUETOOTH issues CM12, CM13 and other ROMs N7100

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.

Bluetooth Connectivity Issues

Dear All,
since having (official Oxygen OS) Android N on my OP3 my bluetooth headset (Sony SBH80) and most other devices are unusable. It seems the strength of the bluetooth signal has dropped by a factor of 10 - as soon as there is more than 1 meter air or more than one material (e.g. trouser pockets) between the phone and the headset the music starts skipping or drops out completely. When I have the phone in my hands near my chest, even tilting my head back breaks the connection.
- I tried other phones, they work completely with the headset fine in any normal use (phone in front pocket)
- The issue was NOT present when I was still on Android 6 (also stock Oxygen OS)
- I recently installed the Oxygen OS Beta (Android 7.1.1) with no change to the issue
I saw here in the forum and on various news sites posts about bluetooth issues with Android 7, but they were from the end of last year, still tried every "trick" or solution that was standing there. Here in the forum I only found posts about connection problems to car bluetooth. The thing is, I can connect fine, it's just that the signal seems to be too weak.
Is anyone facing the same issues or even better, was anyone facing the same issues and found a solution?
Thanks,
Georg

Unresolved BT issues... (updated after 7.1.2)

[I'm running a stock 7.1.1 without root or any other mods]
BT doesn;t work with 2 BT devices which can do phone...
Example:
1) BT watch, Huawei Watch connected - this watch can receive and make phone calls... It has a microphone and speaker, so it works like a full-fledged phone device. It is basically **** Tracy device... look it up ...
2) When the watch is connected, another BT phone device, like a car kit, doesn't connect. You can go to BT settings and manually click on the BT device to connect. Sometimes, it connects w/o extra help. And sometimes, clicking doesn't connect at all. Sometimes it connects automatically. Bugs!
3) When both devices seem to be connected (even though only one is shown to be connected), both can make calls, but only the "active" one receives them...
The active being the one that was connected last.
4)
------ This was not a problem in 7.1.0. Whichever device (watch or car kit) initiated or answered a call, would be used to do the complimentary function - If you make a call on watch, you get audio for the call on watch. If you receive the call on BT car kit, you answer on it. Without fail this worked just fine. Both incoming and outgoing calls. It made sense and it worked beautifully.
-----
Until 7.1.1.
---- Now, if a watch is connected (Huawei Watch, which can act as a phone itself), the BT car kit will not connect. If you connect it manually by clicking on it in BT settings, it will connect, but all phone actions, even initiated from the watch will only work on the phone.
In other words, 7.1.1 killed BT functionality with several BT phone devices.
Why can't they fix it?
UPDATE after 7.1.2
So, 7.1.1 killed phone functionality when both a phone capable watch and another BT phone device were connected simultaneously - both wouldn't work correctly at the same time.
7.1.2 didn't fix this at all.
What 7.1.2 did was introduce new bugs: 1) Weather built-in app no longer works on my Huawei watch, it just spins the circle retrieving weather data and then just goes back to watch face, 2) The watch no longer displays some notifications, for example, SMS.
I played with all of the settings in the watch, phone, and android wear app. Nothing.
I have a theory... Google has two android development teams. Let's call them Team A and Team B. Team A works on a yearly cycle developing new android OSes, for example, they are probably working on Android O right now. Team B picks up development and maintenance duties after Team A makes the initial android release. Team B would be working on Nougat right now. Team B is comprised of rejects from Team A; they have very little talent, attention to detail, or even skill. They may fix 1-2 bugs in an incremental android version, but they introduce 5 more new ones.
This is why Android 7.1.0 was less buggy than 7.1.1, and conversely, 7.1.1 was less buggy than 7.1.2.

Me with my powerbeats it seems to work but eventually it will stop playing music so I turn off headset turn back on and music starts playing again and then the music will start skipping because it hears background noise. It drives me nutts.

..

--

Worked for me.. I could connect to my headphones but yet it acted like it was not connected. Connected to my truck yet it acted like it was not connected.. I for the hell of it wiped dalvik/cache and now it all works with no problems. Headphones instantly worked after doing it. Truck worked just fine this morning..
Sent from my Pixel XL using Tapatalk

--

..
Sent from my Pixel XL using Tapatalk

I'm on stock like the OP. My bluetooth issues are similar and I have one more.
Devices I'm paired to disappear from the BT list. I got in my car yesterday and was surprised the screen needed me to enter my PIN as I had my car in Smart Lock. Go look and sure enough not connected to the car and the BT list doesn't have my car listed as a device. I had to re-pair to the car. Then I had to readd to Smart Lock. This has happened with other BT devices (primarily headsets as that is really the only other things I use with my phone). This happens frequently and almost daily that I lose one or more BT paired devices from the list.
Other times, primarily with my Bose QC35 as I frequently turn it on/off, it will be in the BT list but the phone says I need to pair the device again. This only happens about every 10th time I turn the headphones back on.
Unfortunately, I've only had 7.1.1 on this phone as it is only a few weeks old. So I don't know if stuff would have worked in 7.1.0.

djr4x4 said:
Worked for me.. I could connect to my headphones but yet it acted like it was not connected. Connected to my truck yet it acted like it was not connected.. I for the hell of it wiped dalvik/cache and now it all works with no problems. Headphones instantly worked after doing it. Truck worked just fine this morning..
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I'd like to know what you did to make things work.

Updated op with 7.1.2 info.

Lineage 14.1 / HTC M8 - BT issue

Hi,
I don't know if this thread is here in the right subboard but please let me explain my issue with Lineage 14.1 for the HTC M8 / single sim.
BT is generall works well with headphones and speaker but I have a serious problem with the phonebook function im my VW car navigation system RNS310.
The pairing is easy, also call-in and -out works.
The problem is the phonebook part: no phonebook, no arrived phone calls, no call history are available on the car system.
I tried it several times since the weekly updates dropped in cointaining less or more system changed but: No success since almost a year ago. Deleting the pairing and re-pairing also no success.
The latest rom "lineage-14.1-20181026-nightly-m8-signed" was tested, too.
Any ideas to help are welcome as the bugbash forum
P.S. The original HTC rom works flawlessly in this respect.
P.P.S. The jira bugbash community is dead on this issue.

Hi, I have the same setup and seems to work with my Mercedes no problems. I have noticed Bluetooth disconnecting randomly occasionally, but haven't worked out if its the merc command system or something with lineage 14
Sent from my m8 using Tapatalk

Hi,
that's good for you.
Anyhow it doesn't work in my Golf.
Commercial ROM works as well as other smartphones with factory versions.
So, it remains one of the big disadvantages of LOS 14.1 as well as the HDR camera crashes after second click.
Hopeless.
P.S. A big bunch of patches is forseen for the weekend even some changes in android_bt. Maybe this comes with a solution.

Finally I found a solution: It works !
In settings / apps / system processes I deleted data of the two available BT services.
Then I re-paired the phone and the car and after 30-40 seconds all phonebook stuff was displayes on the car navi screeen.
Case can be closed, I'm happy with the working status.

Question Strange Bluetooth crash on BMW

This only happens when I'm paired and listening to media audio (like youtube or Spotify) on my BMW f10 2012's Bluetooth connection. While listening to the audio I get a super high-pitched sound for about half a second and then the Bluetooth on my Pixel 6 pro crashes and starts up again. After a minute I can reconnect with my car and continue listening to audio. It can happen once or several times during a driving session. No indication as to what causes it.
Speaking of Bluetooth anomalies I also sometimes get into a situation where my car's "next/previous track" doesn't seem to pass the message to the Pixel to change the track. It chooses when to work. I never had an issue with my previous Samsung Note 9 or S8 phone and my partner has a OnePlus 8 Pro and has no issues. It's definitely Pixel-related. I have no problems with the Bluetooth on the Pixel with any other device (headphones, Windows PC, smart speakers etc)

Try lowering the AVRCP version: head to developer settings and search for AVRCP Version. Default is 1.5, try 1.3 or 1.4 and see if it works. Older headunits may need older versions.