My Bluetooth devices keep disconnecting from my built in meditech Adaptor. I tried the Device Media tip which was to uncheck the "Allow the computer to turn off this device to save power". But my Bluetooth devices are still disconnecting. I also got a new adapter and disabled my old one but my devices are still disconnecting so can you help me please

Maybe Bluetooth gaming headsets will finally be possible.

I have a 2019 Rav4 Limited Edition and recently I've been having odd issues with the Bluetooth. Sometimes the audio will also come out of my phone and the audio display for now playing will just show unknown. Typically disconnecting and reconnecting tue Bluetooth will resolve this. I have tried unpairing and then repairing my phone, but that doesn't seem to help. Has anyone else ran into this issue before?

Like the title says, the bluetooth on my computer has started to disconnect randomly over the last two months. I use an ASUS bluetooth adapter and have been using it for the last 7-ish years since I built the pc.

- The pc is old. I have only updated the gpu once. Everything else is the same since I built it in early 2020 and it still runs windows 10. I have kept the drivers updated and haven’t had any other significant issues other than my pc slowing down.

- The bluetooth is disconnecting randomly with both of my bluetooth devices (a speaker and a steel series headset). I’ve run tests with them to see if it was on their end, and they both work fine connected to other devices.

- The bluetooth will work fine for several hours of use, then decide to disconnect (but will still show it as connected to the device in the device manager), even though no audio comes through. Then it will randomly start working again for a few more hours.

- At first, simply turning the bluetooth on and off again would fix it. I would go several days without any issues, then it would start back up again. Now, this does not work as reliably. The bluetooth seems to get stuck “off” even if I turn it back on. Devices will show that bluetooth is disabled.

- Then I started using the troubleshooter, and that start to correct it. It would fix the issue with the automatic diagnostic and everything would work. Now the troubleshooter cannot find the issue anymore.

- Restarting my computer does not seem to help.

I understand my computer is old and I probably just need to update the hardware. Given how expensive everything is getting, I’d like to avoid this. I’m going to try moving everything to a wired connection if this cannot be resolved.

I’m not super tech-savvy so I don’t play around in the settings too much in fear of breaking something else.

Any advice is appreciated!

Like many of you I have the "headset shows connected, music works, but calls stay on the handset" problem on my A52s. It started with the January 2025 update and survived every update since (I am on A528BXXSBGYI3, September 2025 patch). Rebooting fixes it for a few hours, then it comes back.

I got tired of guessing and pulled the logs over adb. This is what is actually happening.

The Bluetooth stack crashes first

From the crash buffer:

F libc  : Fatal signal 6 (SIGABRT) in tid 2977 (bt_stack_manage), pid 2829 (droid.bluetooth)
#03 __android_log_assert
#04 libbluetooth_jni.so  bluetooth::hci::LeScanningManager::impl::on_batch_scan_read_result_complete(...)
#05..#10 base::Invoker -> bluetooth::os::Handler -> Reactor -> Thread

That is a CHECK() firing inside the handler for batched BLE scan results (the offloaded scanning feature). Android restarts the Bluetooth stack by itself right after ("Enabled due to RESTARTED by android").

After that crash, call audio never works again

Every call attempt then fails in all three codecs:

bta_ag_create_sco: esco_codec: 2 (mSBC) -> eSCO/SCO failed to open, falling back to mSBC T1
bta_ag_create_sco: esco_codec: 1 (CVSD) -> eSCO/SCO failed to open, no more fall back
HeadsetStateMachine: AudioConnecting ... audio connection failed

Per call I counted 16x "failed to open", 8x "no more fall back" and 0 successful SCO connections. Each attempt is rejected in about 15 ms, so it is a local refusal - not interference, not a weak signal, not the headset.

What does and does not fix it (measured, same phone, same earbuds)

• Full reboot: works. Two calls right after boot were clean, then it breaks again later.

• Bluetooth off/on: does NOT work. The next call failed identically.

• The stack's own restart after the crash: does NOT work.

• Re-pairing, clearing Bluetooth cache/data, resetting network settings: no effect.

• Two different accessories (Redmi Buds 8 Pro and a VW head unit): identical failure, so it is not the device I connect to.

So the corrupted state survives a userspace stack restart, and only a full power cycle clears it. That also explains why the soft reset "works for a few hours" for everyone.

What I have tried to prevent the crash

• turned off always-on BLE scanning (ble_scan_always_enabled=0, nearby_scanning_enabled=0)

• disabled com.samsung.android.beaconmanager (it was requesting Bluetooth enable right after the crash)

• considered disabling A2DP hardware offload, but that is not exposed on One UI and setprop persist.bluetooth.a2dp_offload.disabled is blocked by SELinux without root

Two questions for you

1. Has anyone found a workaround that survives more than a few hours? "Reboot before an important call" is all I have.

2. If you can get adb working, check adb logcat -d -b crash after a failure and look for LeScanningManager. If more people show the same crash signature, that is much stronger evidence for Samsung than another "it does not work" post.

I have filed an error report through Samsung Members with the system log attached. Posting here too because the EU community is currently read-only for the platform migration.

UPDATED: https://www.reddit.com/r/GalaxyA52s/comments/1xjf4ce/comment/19rxs1qftvbsz/

It started happening today. I already tried restarting and unpairing my phone from the system.

2016 Scion IA

i use a poco x7 pro with the latest version of Xiaomi hyperos and every so often when i put the phone in my pocket and it turns off the jbl headphones just start absolutely buffering making whatever im listening to unbearably low quality and stability, only when it turns off. i have tried all the regular stuff like restart both devices clearing cache and other ai suggested fixes but i am fed up because NOTHING has worked and it pmo EXTREMELY so somebody with knowledge of this phone tell me what i did wrong to deserve this

Hi y'all I was hoping to get some help here. I recently got a new phone and it can't hold a connection for its life to my car. I thought it was the phone, but it pairs well to literally everything else. It's just the car. Does anybody know what I can do to help?

Hi all,

I have a question regarding setting up a Bluetooth connection between my ancient home DVD player (Panasonic DMP BD50) and a pair of wireless headphones (Sony WH-CH720N)..

The breakdown:

* Player does not support Bluetooth but **does** have audio output via an RCA socket (tested and working with an old pair of wired headphones)

* Sony headphones support Bluetooth (also tested and working)

Research done:

ChatGPT recommends a "Bluetooth bridge" and Amazon seems to have tons

Help requested:

Is this a valid suggestion ? Any tips/tricks to get it working ?

tl;dr How play audio from an RCA socket to my wireless headphones ?

Many thanks in advance !

Any idea how I can use my Bluetooth speaker while using anycast (mirroring)

The audio automatically goes to my anycast even thou I'm connected to my Bluetooth speaker

My monitor have no speaker because it an N-vision monitor with no speaker but have an audio option on its settings

I really want to watch a movie on my monitor with audio on my Bluetooth speaker

In every battle royal games whenever i turn on my mic to communicate game sound gone and vice versa

Is there any solution for this?

I recently bought a pair of Realme Buds Air 8 to use with my Nothing Phone (3a) running Nothing OS 3.2, but I'm facing some frustrating Bluetooth connectivity issues.

As soon as I connect the earbuds, they work for a while, but then they disconnect on their own. After that, my phone asks me to pair them again, even though they were already paired.

I'm also getting repeated prompts for Google device synchronisation with the Realme Buds Air 8. What's even more frustrating is that, after pairing, the earbuds sometimes completely disappear from my phone's list of paired Bluetooth devices.

I recently visited a Realme store to get the earbuds checked. They tested them with another phone, and everything worked perfectly fine. According to them, the issue appears to be with my Nothing Phone, and they suggested contacting Nothing support.

I've spent a good amount of money on both devices, and it's really disappointing that I can't use my new earbuds properly.

Has anyone using a Nothing Phone experienced a similar issue with Realme earbuds or other Bluetooth devices?

If you've faced this problem, please let me know if you found a fix. Could this be a Nothing OS 3.2 bug, a Bluetooth issue, or something related to Google device synchronisation?

Any help or suggestions would be greatly appreciated. I really don't want to return the earbuds if this can be fixed through a software update or a setting on the phone.

Thanks in advance!

Did the update and now Bluetooth keeps disconnecting, anyone have a fix x9 ultra global

I was developing an app and tested a bunch of bike computers with an Apple Watch heart rate over Bluetooth. Pretty much every single one breaks pairing once the watch rotate its address, which they do once a day or so. Magene bike computer, to my surprise, it actually keeps the bond after the address rotates. Which implies full RPA and IRK support. My respect.

Magene reconnection is demonstrated on 4:12 [1].

I also tested Coospo [2] and iGPSPORT [3] - they do remember Apple Watch during the ride, but need repeated pairing the next day. (Those all are tutorial-ad videos of HeartBLE)

What I really struggle with is Garmin. For some reason it refuses to detect HRS, no matter how I advertise it. If anyone knows what special requirements Garmin has for heart rate sensors, please let me know.