Yep, Samsung S22 Android v13.Any Android users experiencing this issue?
I have experienced this issue 3 times since taking delivery of my M3 a month ago, so quite rare, but still a bit annoying. It always rights itself after waiting a few seconds.
While I don't have an answer to the issue because phones can have different setups and, let's face it, Bluetooth technology has always been terrible, I can provide a little detail about the technology used to communicate between your phone and Tesla for unlock/lock and drive. The bluetooth used for audio is completely separate, as I explain below.
Bluetooth Low Energy (BLE)
The Tesla app uses Bluetooth Low Energy (BLE) to communicate between your phone and car. BLE is a wireless Personal Area Network (WPAN), native to most smartphones, that constantly transmits a low energy signal every 30ms from your phone. The Tesla is always listening for a BLE signal and when detected, the phone authenticates itself with Tesla. If successful, the car is unlocked and ready to drive.
It's important to note that while the BLE is incorporated into the "Bluetooth" technology, it is not the same as the classic Bluetooth used to connect to your car's audio system (or wireless speaker, earbuds, etc.) BLE co-exists with classic Bluetooth, but is independent.
As I said, I have no answers to solve the problem of unlocking the car, but I hope this helps a little to understand what goes on in the background.
If anyone can build on this or provide a solution to the issue, please do. Cheers!