Samsung Galaxy A52 bluetooth

[Paglan]

Hi. I recently purchased a Samsung Galaxy A52 5G. I have a pair of JBL Tune 500BT wireless bluetooth headphones. I have successfully paired the headphones with the phone, through the bluetooth settings. They DID WORK to start with, but then stopped working.

The bluetooth settings still say that the headphones are connected. The headphones make their little 'connected' sound. But no sound is coming through them.

I have confirmed in the specific bluetooth settings  on the phone that the headphones have both 'calls' and 'audio' switched to 'on'.

I have tried other bluetooth devices with the same phone, and they are ALL having the same issue.

I have tested the other bluetooth devices with another phone, and they all work fine.

Please help!

[Lisa1884]

Hi I've just bought a Samsung a52 and the Bluetooth although switched on doesn't seem to find my car for handsfree

[Ckls1]

Thank you, this worked for me without having to restart the phone. Restarting the phone had worked but the issue would arise again. Hopefully this is a permanent solution while we wait for an update to fix the problem. Will update after some time using Bluetooth if the fix is permanent but so far so good. Thank you 😌

[Ckls1]

Confirmed Enabling Turn off A2DP Hardware offload in Developer Options worked for me

 

[Rebreather]

Still working a month later, yay.

[Ckls1]

Working well

[Members_JEVP33Z]

My a52 doesn't even recognize my jbl headphones. Help!

[Warco]

Had the same problem and this fixed it, thank you for sharing. Samsung please fix this with an update, this issue basically makes any Bluetooth device unusable. Cheers!

[RoyBeeKing]

Sort of glad it's not just me. REALLY don't want to have to do a Factory Reset. Just hoping I won't regret jumping ship from my last 15 years of Sony phones...

[Wuzzzop]

Yeah me too i have exactly the sames issues ! I hope samsung i gonna fix it soon with an update :((

[johnhall]

Thanks. I also have this issue. I found that my settings had that off already but switching it ON fixed the issue (for now)