08-03-2025 01:35 PM
As title says, the bluetooth connection to multiple devices is broken and cannot be established. It shows connecteded, but phone call audio is not going to car/headset. Also actively moving to bluetooth by selecting via button is not connecting anymore.
A528BXXSAGYA2
19-09-2025 11:07 AM - last edited 19-09-2025 11:15 AM
.
01-10-2025 01:38 PM
Bluetooth issue continues after september update.
*****! 😠
01-10-2025 04:11 PM
What a negative situation! I made a couple of weeks ago the decision to say goodbye to the a52 and bought an other phone. I could not handle this terrible services anymore
06-10-2025 06:49 PM
I also tried the soft reset and the September update, but the only temporary solution I found was unpairing and pairing again with the car.
It worked for some minutes and then spot working again (no audio at the car).
Strangely when working, the only options shown at the Bluetooth details at the mobile are only Calls and Audio, when not working, also Contacts and messages are also shown.
Probably I will also abandon Samsung.
4 weeks ago
Samsung does not even admit it's a bug. They basically say 'losing bt during a call is a hardware failure that we are not responsible for'. Sure... Simultaneous hardware failure on so many devices? And it can be temporarily (minutes) solved by restarting bt (developer options, toggle usb sap)? Highly unlikely but we're stuck with very limited functionality. I know using a phone as actual phone is oldskool, but this is just nuts. Break it, reject it, force people to buy new phones? If it was a US company it'd be sued into bankruptcy.
4 weeks ago
I posted my workaround in another thread at below — it works for me, and I also explained the underlying principle of the problem.
3 weeks ago
3 weeks ago
That one did solve the problem after it re-appeared on my device
Thanks bro!
3 weeks ago
Doesn't work for me. 😌
3 weeks ago
Doesn't work for me on A52S, ve got bluetooth app on 'unrestricted battery' still drops bluetooth. Even in the middle of calls it just stops working. The only fix sofar (for a few minutes at best) is a reboot of phone, or bouncing sap in developer options.