For the last few weeks, since right around the time of the last update, my Samsung A53 5G will disconnect and reconnect randomly. This happens no matter what device I'm using, and happens with increasing frequency until Bluetooth devices are essentially unusable.
I've tried the following to resolve:
Unpairing and repairing the impacted devices.
Clearing all my network/bluetooth connections.
Resetting the phone.
Only resetting the phone has worked, and that only worked for a limited time; I reset my phone less than a week ago, and this issue has started up again today.
There was another issue reported with Bluetooth following the latest update in the following post:
okay, then it's something that needs to be checked by samsung directly.
Reproduce the issue or when it happens again, immediately report error to samsung members app > get help > error report.
you can also suspect hardware defect since Nice Catch didn't detect anything, the phone could be disabling BT due to hardware malfunctioning. So your 2nd option is to visit authorized repair center for BT part checkup.
My son also purchased an A53 about a week after I did. He's been experiencing the same issue, he says it only happens while he's listening to Audible. I would swear that it has happened to me with Spotify as well, but I have to admit that I listen to Audible ~80% of the time during the day, so I'll have to try a different app tomorrow and see what happens.
It actually appears to be a specific issue with Audible. As I noted in another note on this chain, my son purchased an A53 about a week after I did. He has also been observing this issue, but noted that it only appeared to be happening with Audible. I listened to Spotify for a few hours last night without any issues. This morning I finished up an audiobook in Audible for about two hours, and this occurred several times. I've been listening to podcasts in another app for 2-3h without any issues.
In my other post regarding this, I noted that it had previously happened while I was listening to Spotify. However, I'm not good about actually clearing apps out of memory, so Audible was probably running in the background. It is not today. I may fire it up and leave it in the background to see what happens.
