Bluetooth issue since Android 13 update

[TheKelbs]

Since my S22+ updated to Android 13 my phone will no longer let me make calls on my car handsfree. I known its the phone as other Samsung model work fine with the kit. Anyone else had this issue and found a fix?

[Tonibelle]

The link you show is for UK support!  I'm in the states and have been having multiple problems since this update and calls to Samsung support have not resolved it.  I can't figure out how to go back to update 12 and remove this mess.  It keeps dropping my handsfree in my car and is such a pain to reset everything and really bad when I'm driving and need to call someone for help as the frequently called names are no longer there.  Guess I'll just call Samsung support again today.

[PaulM1]

Hi, @Tonibelle. This is the Samsung Community for the UK and Ireland, but it is open for all Samsung fans and customers. We're always happy to help, but some enquiries will ultimately need to be directed to the Support Teams in your region.

There is no way to roll back the software version on your phone, so we recommend continuing to liaise with our colleagues.

Our US-based colleagues can be contacted here:

https://www.samsung.com/us/support/contact/

There is also a Community for our US-based customers, fans and enthusiasts here:

https://us.community.samsung.com/t5/Samsung-Community/ct-p/us

[Anonymous User]

Something that worked for me was to go to developer options and change under Bluetooth options the Bluetooth AVRCP settings to 1.4, found that my older note 9 was set to that and thought I'll give it a try on my S21 Ultra and it works like charm so far. All my Bluetooth devices, headsets, car radio speakers and keyboard seems to work fine again. 

[TheKelbs]

Can't seem to find that on my S22+?

[jboman1980]

I tested this, seems to work.

[whart6]

This is in reply to "change under Bluetooth options the Bluetooth AVRCP settings to 1.4" from an earlier post by tobie86243

1. Go to the settings menu and click “About phone” -> software information
2. Scroll down to the bottom where you see “Build number”
3. Tap it seven (7) times. Android developer settings are now enabled.
4. Go to the settings menu again and click Settings->Developer options->Bluetooth AVRCP version.
5. select which Bluetooth AVRCP Version you want such as AVRCP 1.4 from the previous response.

I don't know whether changing the Bluetooth AVRCP Version will fix this issue. I wish Samsung would address it asap. Been an ongoing issue since version 13 was released. just fix please. You must be aware of it. I wear hearing ***** which are bluetooth'ed to my phone. I can be in the middle of a phone call and they disconnect or degrade during the call. My garmin also keeps losing its connection to the phone and needs to keep being repaired. I have a S22+ and tried to roll back to my z-fold 3 but it also had android 13.

[BrentW]

Changing setting to 1.4, did not help with me, also tried 1.6 (was set to 1.5 before changing).    I did get out of developer mode and restarted a couple times, still have grayed Bluetooth toggle that likes to turn Bluetooth off with any change to connection screen.  Sometimes it comes on normal is able to see other devices but any attempt at connection results in the grayed out/default to off operation.  Interestingly we have two S22's, both with Android 13 update, AVRCP  1.5 (Default) and bluetooth on other phone works fine.  Can't figure out what is different but there is absolutely no bluetooth connection on the affected phone.

[Karlderik]

The  security patch Samsung of December S906BXXU2BVL1 solved my bluetooth issues on the S22+

[BrentW]

My model no is SM-S901U (S22 model), noticed patch seems to be unique to the different model no. and Slovenia.  Anyone know how to get US patch for the plain old S22?

[TheKelbs]

Come on Samsung! My phone hasn't worked properly since November and I only got it September.
I've spoken to Helpdesk people sent error logs and absolutely nothing has happened. Atrocious customer service!
Either fix this or replace it with a new device that's still on Android 12.😡