Been having this issue ever since moving to official UVLE1 derived ROMs. I have tried everything except going to the Mr X rom. I would other ROM types( i have actually) but need wi-fi calling as tmobile does not dare enter my house. The issue is that bluetooth conencts to my Kenwood headunit immediately but then disconnects anywhere between 2 minutes and ten minutes later. It will then reconnect 30-60 seconds later but not have any audio unless i hit the play button on the headunit itself. I tried "bluetooth keep alive" app but did not work for me- yes i tried all the options. I actually got it working one night but flashed another rom and cant remember what i did. I've spent hours searching this issue. Anyone else have any luck?
oh some additional information: Problem is not present on any other rom bases including CM9, AOKP, Gingerbread, and skyrocket based ROMS. I have also turned off phone audio to strictly keep it to media with no difference. My Nexus 7 does not have this problem with the head unit.
this might or might not relate to your ROM but it helps my connection with AOKP anyways browse to /system/etc/bluetooth/ open up file audio.conf
look for the "autoconnect=" should be halfway through the page make sure there's no "#" in front and that it says AutoConnect=true
I'm on AOKP and it helps me, sometimes only phone audio connects for mine but ^^ that helped it.
Always seems to connect quickly- just disconnects just as efficiently lol. I will however give this a try and look around the rest of the config file.
yeah i looked around at the config file too and there doesn't seem to be anything else that might trigger a random disconnection. But for me, it always connected quickly, but for some reason with AOKP the media wasn't connecting all the time, and then someone mentioned the "#" in front of the AutoConnect. Hope it helps.
configuration
Teo032 said:
yeah i looked around at the config file too and there doesn't seem to be anything else that might trigger a random disconnection. But for me, it always connected quickly, but for some reason with AOKP the media wasn't connecting all the time, and then someone mentioned the "#" in front of the AutoConnect. Hope it helps.[/QUO
Itookyour advic and then wentonefurther. ItookthewhileBluetooth folder from cm9and copied it. been good for about ten minutes so far. if I continue to have problems I'll copy over the Bluetooth apk. thanksagain.
Click to expand...
Click to collapse
Software Engineer with Bluetooth Car Disconnect Issue
Hi, this is my first post. Think I am in the right place.
I have a Samsung Galaxy S2 (hercules) and a 2010 VW Tiguan. The phone is running ICS, but problem happened on Gingerbread too. The problem happens at random times, but normally seems to happen while on the phone. I have tried a number of things including turning off the PAB service when running Gingerbread (didn't work). I also modified the config files from a tip from another post, but this didn't work either.
Below is a a portion of a log of when this appeared recently. I have not looked into much further just yet, but maybe this will help or maybe someone can explain what they think is happening at the disconnect. Thanks.
Note - The disconnect happened at 12:05:
08-06 11:58:28.267 E/BluetoothPbapVcardManager(20687): write outputstrem failedjava.io.IOException: Abort Received
08-06 11:58:28.267 E/BluetoothPbapVcardManager(20687): write outputstrem failedjava.io.IOException: Abort Received
08-06 11:58:28.267 E/BluetoothPbapVcardManager(20687): write outputstrem failedjava.io.IOException: Abort Received
08-06 11:58:28.287 E/BluetoothPbapObexServer(20687): operation close failedjava.io.IOException: Abort Received
08-06 11:58:29.318 D/Bluetooth HSHFP( 592): AudioStateIntent: 00:0E:9F:7B:96:BA State: 11 PrevState: 10
08-06 11:58:29.428 I/AudioHardwareMSM8660( 175): Routing audio to Bluetooth PCM
08-06 11:58:29.468 D/Bluetooth HSHFP( 592): AudioStateIntent: 00:0E:9F:7B:96:BA State: 12 PrevState: 11
08-06 12:02:05.559 I/HeadsetService(24033): Headset=false; Bluetooth=false
08-06 12:05:21.790 I/AudioHardwareMSM8660( 175): Routing audio to Bluetooth PCM
08-06 12:05:22.060 D/Bluetooth HSHFP( 592): AudioStateIntent: 00:0E:9F:7B:96:BA State: 10 PrevState: 12
08-06 12:07:25.884 D/Bluetooth HSHFP( 592): AudioStateIntent: 00:0E:9F:7B:96:BA State: 11 PrevState: 10
08-06 12:08:05.953 E/Bluetooth HS/HF( 592): BluetoothSocket could not connect
08-06 12:08:07.955 D/Bluetooth HSHFP( 592): AudioStateIntent: 00:0E:9F:7B:96:BA State: 10 PrevState: 11
08-06 12:20:16.896 D/BluetoothAdapterStateMachine( 332): BluetoothOn process message: 2
08-06 12:20:16.926 D/BluetoothAdapterStateMachine( 332): Bluetooth state 12 -> 13
replacing the Bluetooth folder with the one from cm9 fixed my problem completely. you can try bluetoothkeepalive app as it works for some. i have since ditched tmo based roms in lieu of JB and haven't had issues yet. limited use so far since i been pairing my nexus 7 with stereo mostly
TeamHackura said:
replacing the Bluetooth folder with the one from cm9 fixed my problem completely. you can try bluetoothkeepalive app as it works for some. i have since ditched tmo based roms in lieu of JB and haven't had issues yet. limited use so far since i been pairing my nexus 7 with stereo mostly
Click to expand...
Click to collapse
Oh, forgot to mention that the log file is with cm9. It seems to happen less with cm9, but not fixed for me. Will take a look at that app, and continue my mission to fix this.
Thanks for the reply!
I know this is dead but upgraded to note two on T-Mobile and issue is there.
Sent from my Nexus 7 using Tapatalk HD
Related
I have problems with my Bluetooth and the paired device in the car with almost every recent ROM.
After about 10 minutes driving with a connected phone, the Bluetooth shuts down on my Diamond. When I go to Settings -> ... > Bluetooth -> Mode -> Turn on Bluetooth is unchecked. If I check it again it connects again with the phone and about 10 minutes later it's off again.
I went back to the RUU_Diamond_HTC_WWE_EastEurope_1.93.479.3_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship.exe. It's against my feelings, believe, etc. but I want to solve it .....
I installed Advanced Configuration Tool (3.0), went to Bluetooth -> Audio gateway power save and Disabled it. I did it because I was reading about suspended devices and power save features. I thought that the loss of Bluetooth is been caused by a saving power feature.
After a soft reset, the Bluetooth stays connected.
It's a start, but I'm not happy with it ... I would like to use cooked ROM's and optimal settings in the ROM.
There are other tweaks too in Bluetooth, for example the supported bitpool, etc. Perhaps those settings cause the shutdown of a connected Bluetooth device instaed of the power save feature.
Has anyone this kind of problems too with paired Bluetooth devices?
If so, would you like to help me to find the cause?
If not, can you describe what device you use (Jabra, TomTom, car radio, etc.), which ROM, which radio and extra tweaks?
Hi
I do have the same problem. I am using my Diamond with my Opel Astra (Vauxhall) and a CD70 radio with built in handsfree (Opel UHP). It disconnects after 10 minutes and after calls. Everything else works fine. Changing rom and radios has not helped so far. If I don't close the comm manager it stays connected but disconnects after a call because the comm manager is closed with the end of the call. Is there a way to force the comm manager not to close?
Olli
olliver said:
Hi
I do have the same problem. I am using my Diamond with my Opel Astra (Vauxhall) and a CD70 radio with built in handsfree (Opel UHP). It disconnects after 10 minutes and after calls. Everything else works fine. Changing rom and radios has not helped so far. If I don't close the comm manager it stays connected but disconnects after a call because the comm manager is closed with the end of the call. Is there a way to force the comm manager not to close?
Olli
Click to expand...
Click to collapse
I have a CD70 too in a Opel Zafira.
This "comm manager" thing is interesting, but it looks to me like an Opel issue.
Can't you flash firmwares by opel?
Riel said:
Can't you flash firmwares by opel?
Click to expand...
Click to collapse
That's an option, but my Trinity (P3600) performed great with the same car. Will an upgrade solve my problems? I know one thing, it's not cheap either.
I tried it with different ROM's, but it still happens.
I tried it with different radio's, nothing changed.
Till today, I've got now the new radio (v1.05.25.BS14).
http://forum.xda-developers.com/showthread.php?t=432770
It has fixed the delays in GPS + faster GPS fix and more important fo me Bluetooth didn't stop today.
I'm sure 100% sure yet, but seems to be better.
I got something to complain too about the new radio. The radio signal is less strong than the .05 radio.
Same problem here
My Vectra is equipped with CD70.
Previously I've owned a Kaiser and the problem was solved by one of the 6.1 radios, bluetooth connection was rock solid.
Right now I have the same problem with Diamond - after every single phone connection, when I'll hangup, the phone disconnects CD70. When I'll try to reconnect manually using CD70 everything is fine.
I've noticed that the same problem exists when I'm using Nokia bluetooth headset - one call, bluetooth connection dropped...
I've tried following Diamond radios:
.05
.07
.08
.BS14
and two Raphael radios by Bepe:
1.03.25.18
1.02.25.11
Each Diamond radio behaves the same way. Each Raphael radio adds a bonus - random bluetooth connection problems.
Right now I'm back with .05, I think I'll look for the software I've seen once (can't recall the name) - it's a PDA application designed for connecting to the car bluetooth systems and it has been cerftified to work fine with CD70.
Use Jetware Mobile for htc-diamond.
jetware
That's the software I couldn't remember the name.
Anyway I gave it a shot and it gets even worse, I couldnt get the connection lasting longer then 2-3 minutes, totally unstable
Right now I got back to radio .08 - the bluetooth link is rock solid, I guess I'll just need to get used to reconnecting after each phone call
Same bluetooth system in my car, same problems as you guys.
To avoid the disconnections after calls you need to go, with 'Advanced Config' to bluetooth->Audio gateway power save, and switch it to disabled.
For me this little change solve the 'first' problem, but I have another one that I don't know how to solve: the aparently random bluetooth disconections. Sometimes BT is not disconnected in hours, sometimes in days.
I am also using Jetware Mobile, but i didn't feel any improve...
The random ones depend on the radio rom version - I was using .05 and it was rock solid.
I will try .16 with audio gateway started and with power save disabled as you advised - I thought about it earler but previously I tried to disable the power save without enabling audiogateway service
Well, we will see if it works or not.
Hi,
I also have a Vectra CD/70 combination, for 2 yrs now.
I had a HTC3300 and 2years i had not a single problem with Bluetooth connection.
Now i have a HTC Diamond Touch Pro and have the same problems you guys have.
I tried all your suggestions, radio's and so on with no good result.
The good news is .. its an Opel problem and it seems to be that a Bluetooth Firmware Upgrade is available from Opel Germany. I just contacted my dealer and next week he will Upgrade my bluetooth firmware.
I will keep you guys informed.
Hello,
had the same problem with my Opel CD70.
Using Jetware Mobile and limited the entrys who copied to the car to a max. of 5. Also disable the call lists. Now it works.
I think the Opel/Vauxhall Bluetooth Connection disabels if to many entries are copied to the car.
Hello,
any News about our Bluetooth Problem ???
I also have a CD70 from Opel and I cannot understand why my Diamond swich of Bluetooth after a while ?
Is it an Opel-Problem or does anybody now an Application which helps ?
Thanks a lot for Your help,
Stepos
Hi,
I am currently using BTrestore (http://home.casema.nl/rgschmidt/WM/Downloads/BTRestore_V_1_0_0_PPC.ARMV4.CAB). This utility checks the status of the bluetooth stack every 5 secs and (re)enables it everytime it's down. It seems that the 5 secs are short enough to keep the phone connected. It's not a real solution and unfortunately this tool is sometimes instable too, but it absolutely extends the connection time with the UHP.
Maybe bullock can tell us if the carkit upgrade solves anything...??
I also created a ticket at HTC, but they refuse to troubleshoot user specific issues. They told me they only look into issues if they get enough calls from different users and to keep an eye on the update site (they seem to be able to solve issues without knowing what the actual issue is...). So I would encourage everyone here to create a HTC ticket for this issue. I still think it is an HTC issue: a bluetooth stack should never go down without any user intervention.
Good luck!
BTrestart and Jetware Mobile doesn`t help, my Touch diamond disconnect again from Opel CD70 and swiched off Bluetooth !
Can anybody help ?
Sorry guys, the OpelDealer is still "searching" for the Bluetooth upgrade.
After several phonecalls maybe next week (1st week of Febr) it will be made available to the dealer.
Like i said ... i willl keep you informed ... still have this lousy problem !!
..does anybody use the new Rom 2.03 ? Any difference ?
I also asked my Opel-Dealer for an Update of UHP, next week I 'll get new Information....
... well guys I had my CD70 updated !! I am/was very sceptical because the only thing they did was a re-install of the Language of the Navi System with a version 2005 CD. I asked if that was all to correct my Bluetooth problem .... the (smiling) answer was YES.
I have it now for 24hrs ...... and Bluetooth is still on )
I will let you know the result after a week !!
..i can't beleave it works with a 2005-update ! Great !
My Opel-Dealer is still busy in selling 10 Opel Corsa every day (..the magic word is "Abwrackprämie") , so I'll have a date there next week...
When I bought my Vectra the dealer had also to reinstall the Language-CD, maybey it was the wrong version....
...... Sorry guys ......
This update DOES not do the magic trick !! So we have to find another solution
who has the right idea ??
I have the Motorolla S9 bluetooth A2DP stereo headset.
I also have the Hero currently running VillainROM 3.4 but I've been trying to run a bt connection for A2DP media playback with almost all Android 2.1 ROMS with same results.
The phone pairs fine but once I start playing any mp3 headset disconnects and reconnects at random.
I should mention that bluetooth works great in my car with the stock stereo system for simple phone calls.
I searched the entire forum but couldn't find anyone else with this issue ... Modaco 3.1 people report bt stereo playback to be working fine .. I think this is a 2.1 issue as VillainROM 3.3 and 3.4 and BeHero and other 2.1 based roms have this issue.
please HELP
Hello rafynet
i had same problem and i have solved with this method:
your phone must be rooted
there is a file in /etc/bluez/audio.conf
copy that to your pc.Change the lines
from
-----------------------------
Enable=Source,Control,Sink
Disable=Headset,Gateway
-----------------------------
to
-----------------------------
Enable=
Disable=Headset,Gateway,Source,Control,Sink
-------------------------------------------
save it.
copy the changed file back to /etc/bluez/
I have tried this solution in all rom that i have tested and all work well for me, watch the entire article:
Issue 3960: Bluetooth issues with car systems in Android 1.5 / 1.6
I'm sorry, i can't post this link on forum!!
search it in google.
sorry for my english!
I'm waiting your feedback!!
I hope this solution works well for you. Try this!
your solution helped a little bit ... but bluetooth connection still drops and re-connects all the time ... it's very annoying.
I'm fairly sure this will be fixed when we get the official Hero 2.1 update.
I had noticed the same thing with my Motorola T505 ROKR handsfree adapter. Worked fine in 1.5, but in 2.1 it would disconnect every 30 seconds or so, then reconnect.
However... I've just got a new car stereo (Pioneer DEH-P6100BT) and it actually works *BETTER* in VillianROM 4.0 than it did in Modaco 3.2. In Modaco, it would only connect to "phone audio" and not "media audio," and I had to go into the Android settings and enable "media audio" each time I got in my car. With VillainROM, it connects automatically and it doesn't disconnect. Also, I've found that in 2.1, when listening to BT Audio, the music doesn't get interrupted by notification sounds, which I hated about 1.5.
I've had nothing but problem with a2dp on the hero, and it's probably the feature I need to work the most. I tried a whole host of 1.5 and 2.1 roms but none of them would consistantly connect to my pioneer deh-p700bt. I read somewhere that it's been a problem for lots of people since the 2.73.x series of updates, so I downgraded to the T-Mobile 1.76.110.6 stock rom and it's worked perfectly for me ever since! I'll have to stick with that one for now and hope it gets fixed in the upcoming 2.1 update
Hi,
I have a question about this subject :
i have a bluetooth car stereo with phone handfree inclued.
With all ROMs I tried (and a tried a lot...)
the phone handsfree always worked
Depend of the ROM, some items were available or not : (battery indicator or signal level indicator for example)
With only one ROM (and I don't remember which one), I could transfer my contact list from the phone to the car stereo system (with bluetooth).
Does someones knows if this feature will be again available into the next ROM (official or not) ?
Thx
PS : sorry for my bad english
yan74s said:
Hi,
I have a question about this subject :
i have a bluetooth car stereo with phone handfree inclued.
With all ROMs I tried (and a tried a lot...)
the phone handsfree always worked
Depend of the ROM, some items were available or not : (battery indicator or signal level indicator for example)
With only one ROM (and I don't remember which one), I could transfer my contact list from the phone to the car stereo system (with bluetooth).
Does someones knows if this feature will be again available into the next ROM (official or not) ?
Thx
PS : sorry for my bad english
Click to expand...
Click to collapse
The Android SDK did not include a bluetooth API in 1.5, but it is included in 2.1. I would guess we'll see a big improvement with the official 2.1 update.
Hi, I've got a small issue with my bluetooth a2dp device. The device is this one:
BlackBerry Remote Stereo Bluetooth Gateway. It is made by RIM, but works with any device supporting a2dp. My issue with the Galaxy Nexus is that it no longer auto connects.
My setup is in my vehicle, I keep the bluetooth receiver connected to the aux power jack and aux audio in in the center console. This way, when I start the car, the receiver powers up and tries to auto-connect to the last device. On my vibrant with Android 2.1/2.2 this worked fine. When I dabbled with CyanogenMod and some other custom roms, it stopped working but I chalked it up to some problem with the custom rom.
Now, I'm seeing the same sort of problem: if I keep the screen of my nexus on, I can see the bluetooth icon change blue, and then immediately change back to gray. To me, this indicates that the receiver succeeds in connecting but is then disconnected for some reason. The device only supports a2dp, not the handsfree profile. When I looked into the Android kernel code, I found a place where the kernel will try to connect the handsfree profile if the a2dp profile is auto-connected, but it wasn't clear if that was the actual problem or not.
Anyone else have any similar experiences?
I have the same device in my 2008 Accord coupe which is placed in the center arm console. I had an Evo 3D that would automatically connect when I would start the car and BT was already enabled on my phone. I too switched to a different ROM and would have issues auto connecting so I switched back to a different ROM. Now on my stock GN, I have to manually go into settings and click the device to connect. I see no settings about auto connecting when in range. I will have to see if the BT icon turns blue and then back to gray... haven't looked for that. If anyone has thoughts on this, I'm all ears!!
bigdawgr6 said:
I have the same device in my 2008 Accord coupe which is placed in the center arm console. I had an Evo 3D that would automatically connect when I would start the car and BT was already enabled on my phone. I too switched to a different ROM and would have issues auto connecting so I switched back to a different ROM. Now on my stock GN, I have to manually go into settings and click the device to connect. I see no settings about auto connecting when in range. I will have to see if the BT icon turns blue and then back to gray... haven't looked for that. If anyone has thoughts on this, I'm all ears!!
Click to expand...
Click to collapse
I suspect it has something to do with Android's attempts to auto connect to the headset profile when a A2DP profile is connected.
See:
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
#AutoConnect=true
Click to expand...
Click to collapse
from https://github.com/android/platform_system_bluetooth/blob/master/data/audio.conf
I have seen the code where this happens and it seemed that if the headset profile failed to connect, the A2DP connection was also disconnected. Though, I can't recall what file it was.
jjohns63 said:
I suspect it has something to do with Android's attempts to auto connect to the headset profile when a A2DP profile is connected.
See:
from https://github.com/android/platform_system_bluetooth/blob/master/data/audio.conf
I have seen the code where this happens and it seemed that if the headset profile failed to connect, the A2DP connection was also disconnected. Though, I can't recall what file it was.
Click to expand...
Click to collapse
Strangely enough, the phone paired with the device twice without issue yesterday and failed once later on that same day. I'm toggling BT off and then on to get connection for now.
It seems like the phone and device are connecting without issue but I know I haven't done anything to change it. I'm on AOKP M3 and Leankernel V1.8 if that helps. When I first flashed those two, I still had connections issues, so switching to them wasn't a resolution.
I am not sure this really helps your issue but it is related. I wrote an app that will auto-connect Bluetooth devices. It is free on the market and is called A2DP Volume. The current implementation of auto-connect looks for one device connection and then connects another. I started another widget that will simply connect a Bluetooth device but I have not finished that one. A2DP Volume is free, open source, and ad free. You can find the open source project on Google Code. Just search for A2DP Volume.
I have been trying this for weeks and this app solved it!!! Thanks for making the app!
jroal said:
I am not sure this really helps your issue but it is related. I wrote an app that will auto-connect Bluetooth devices. It is free on the market and is called A2DP Volume. The current implementation of auto-connect looks for one device connection and then connects another. I started another widget that will simply connect a Bluetooth device but I have not finished that one. A2DP Volume is free, open source, and ad free. You can find the open source project on Google Code. Just search for A2DP Volume.
Click to expand...
Click to collapse
jjohns63 and bigdawgr6,
Any update on this problem? I don't have the Nexus, but I have Droid Incredible 2. I also run into the same problem when I use CyanogenMod 7.2, which is a AOSP based ROM. The connection is fine with the stock ROM. I have tried to change things in the audio.config but it does not seem to help. I think I ran into a post somewhere saying HTC stock ROM uses a propietary bluetooth stack and AOSP and CyanogenMod uses BlueZ open source stack, and that is where the problem is.
Anyway, it would be nice if you guys can share some info.
Thanks!
I have probably not so unique situation.
My Honda allows for calling via bluetooth but not audio streaming. I use an old Blackberry Gateway for that which works perfectly when I had my Samsung S2.
With the Note, the BB Gateway connects and streams audio fine but the car cannot maintain a constant connection at the same time.
I use A2DP volume (which is pretty awesome for free) to force connection attempts. If the BB gateway is not connected, the car maintains its connection. It seems the Note2 cannot do both.
Does anyone have similar problems or a work around? Or maybe know if the new leaked update fixes this? I heard it does update something about BT...
I'm stock rooted BTW
scoobmd said:
I have probably not so unique situation.
My Honda allows for calling via bluetooth but not audio streaming. I use an old Blackberry Gateway for that which works perfectly when I had my Samsung S2.
With the Note, the BB Gateway connects and streams audio fine but the car cannot maintain a constant connection at the same time.
I use A2DP volume (which is pretty awesome for free) to force connection attempts. If the BB gateway is not connected, the car maintains its connection. It seems the Note2 cannot do both.
Does anyone have similar problems or a work around? Or maybe know if the new leaked update fixes this? I heard it does update something about BT...
I'm stock rooted BTW
Click to expand...
Click to collapse
I'm having the same problem. I have a 2006 Pontiac GTO with a Kenwood touch screen and my Note 2 will connect fine, and it will stay connected with no issues until I switch to another playlist, artist, or song. That's when it seems to just disconnect itself and then, about 30 seconds later, reconnect itself.
I've tested this on stock unrooted (LJ1 and LJC), stock rooted (LJC and LK8), Jellybomb v10.2 and v11 (LJC), and H20 beta's 2.1 and 3.1 (LK8) with no luck. I also just recently started trying to use A2DP volume and it definitely helped with displaying the correct song name, artist and album (it wasn't changing when the song would change prior to using A2DP) so it's definitely an improvement but...
Considering how much I drive and how much I LOVE music this is becoming an area of major concern. If any of the amazing developers, or anybody for that matter, has any words of wisdom, suggestions, fixes, etc. it would be HUGELY appreciated.
That_Guy0505 said:
I'm having the same problem. I have a 2006 Pontiac GTO with a Kenwood touch screen and my Note 2 will connect fine, and it will stay connected with no issues until I switch to another playlist, artist, or song. That's when it seems to just disconnect itself and then, about 30 seconds later, reconnect itself.
I've tested this on stock unrooted (LJ1 and LJC), stock rooted (LJC and LK8), Jellybomb v10.2 and v11 (LJC), and H20 beta's 2.1 and 3.1 (LK8) with no luck. I also just recently started trying to use A2DP volume and it definitely helped with displaying the correct song name, artist and album (it wasn't changing when the song would change prior to using A2DP) so it's definitely an improvement but...
Considering how much I drive and how much I LOVE music this is becoming an area of major concern. If any of the amazing developers, or anybody for that matter, has any words of wisdom, suggestions, fixes, etc. it would be HUGELY appreciated.
Click to expand...
Click to collapse
I'm having similar problems with certain roms. Only my truck is a Chevy not Honda. Using blackberry audio gateway. The "Note Card 2.2" rom works perfect for me, along with JellyBomb. I didn't like JellyBomb. I want to switch to another. I need to spend time and found out what is different between the working and non-working Roms. I had the same problem with my EVO 4g. Some Roms worked perfect, others acted up.
Ever since installing the September update I have had troubles with Bluetooth connecting and staying connected to my Galaxy Watch 3 and my hearing aids. Everything worked flawlessly until that installation. Is this a known issue or has anyone else observed this?
Quite the opposite for me, this update has made my phone more reliable to Bluetooth connections.
My BT headphones disconnect all the time. I think my Fitbit does too
With A13, the Bluetooth stack used by Android was changed. I saw some issues early on (problems pairing, needing to forget and repair, pairings simply disappearing), but after redoing some pairings, things seem to be getting better. Still some odd stuff, like impossible options enabled (like "Input Device" and "Contact Sharing" on speakers without that capability).
It's obviously a work in progress.
As mentioned above by Mike, I did also do a fresh start no restore for Android 13 since I thought I was having issues with other things that was really annoying me with android 13 after upgrading to that, all the problems that caused me to fresh start were still present but almost all of these have gone after Sept update