Showing results for 
Search instead for 
Did you mean: 

Bluetooth issues with Android 13 update

Star II

Model Name:  ZenFone 8
Firmware Version: WW_33.0210.0210.210 (TKQ1.220807.001.33.0210.0210.210)
Rooted or not: No
Frequency of Occurrence: Every time
Name & APP Version:

- Apps using Bluetooth devices on the fly without being paired on the system. EliteHRV, HRV4Training, KubiosHRV, Polar Beat, SmartRow. Fully updated.

All these apps connect to devices (SmartRow pulley and HRM strap) without having the BT devices paired through the system/OS pairing, but rather do on-the-fly pairing through the apps.

The problem is that since the Android 13 update, the devices connect but don't provide data, apart from SmartRow BT pulley which provides glitchy data with constant dropouts.

I see that Google released an update for Google Pixel that has a fix for bluetooth devices not pairing.
> Fix for issue occasionally preventing connection with certain Bluetooth devices or accessories

Any ETA for ASUS to release it for ZenFone 8? Or any workouts meanwhile? I tried clearing caches, reseting Bluetooth, reinstalling apps, disabling all battery optimizations and OptiFlex through the phone system, no luck.

Thank you


It is Android 13 that has created many problems on devices of other companies, even on the Pixel of Google itself. Downgrade to Android 12 and you won't have any problems anymore.

We can downgrade, but Asus will force us to upgrade to Android 13 even if we disable automatic updates.

Star I

I am facing same Bluetooth issue with ROG 5s, it gets paired but no sound, clear cache and restarting phone solves the issue but its not permanent. Waiting for permanent solution from ASUS. 

Star I

I too have this problem with the Whoop fitness band. 
Downgrading to android 12 is the only option, but I continuously have to fight the OS not to install the update.

When will ASUS give some indication that on this ? Super frustrating.

@keren_ASUS You need to do something here!

I have no illusions that the Bluetooth issue in Android 13 will be fixed (I wish I was wrong), but at least I was able to successfully block the update and stay on Android 12.