Pixel 8a: Android 16 and Venu 3 14.15: TOXIC COMBINATION

DO NOT UPGRADE to Android 16 or take any upgrades to your Venu 3 if your watch and Connect app are working fine.  Mine were working fine on Android 15, but either the upgrade to Android 16 OR the latest/most recent Venu 3 update has caused frequent disconnects.  3 or 4 times per day I'll need to re-add my Venu 3 to the Connect app.  It'll just be completely missing when I open the app.  I can have the app open and sitting right next to my watch, and I'll get the "phone disconnected" message on my wrist.

So far I've:

Cleared app cache

Cleared all app data

Turned off all possible battery optimizations for the app

Turned off any bluetooth power saving settings in the phone

Soft reset my Venu 3

None of this has helped.  On top of that, there's no way to get Voice Assistant working.

I like this watch when it works, but I'm still in the return window.  I think I'm going to do so.

  • Found this on Reddit and trying it now... Watch connected on its own after rebooting both the phone and watch... Not sure if it's a fix, but worth testing...

    "I've been having the same issues, but (at least for the last 12 hours) it seems I have found a fix. I have changed the bluetooth AVRCP version from 1.5 (standard) to 1.6 in developer mode. Since the change and reboot of my pixel 8a and garmin venu3 the connection between them seems stable. Let's hope it stays that way... Fingers crossed"

  • Thank you for this.  I'm trying it now.  Turning off Advanced Protection really seemed to be working for me, but this morning it was disconnected and I got the popup in Connect to reconnect my watch.  (However, tapping outside of that message dismissed it and the watch and phone reconnected on their own.)

    I've tried this Bluetooth setting, and re-enabling Advanced Protection.  

    Google want me to reset all my WiFi and Bluetooth options.  I know this is a reasonable ask, I just really don't want to set up my Chromebook, Pixel buds, car, various home devices, and then redo the Wifi for here, church, work, etc again.  I don't mind doing basic troubleshooting, but it honestly feels sometimes like we're asked to do a lot in order to troubleshoot these devices, especially when something changes.

  • This did not help... Within an hour it disconnected again. 

  • I disconnected as well, both with and without Advanced Protection on.  Changed it back to 1.5, rebooted, turned off Advanced Protection, rebooted.  Rebooted my watch.  It's stayed connected and was still connected when I checked Connect this morning. 

  • I'm going on 4 hours without a disconnect and hoping it's fixed.  I turned off battery optimization for both Connect and Connect IQ, then went into Apps - System Apps - Legacy Bluetooth, and cleared CACHE (don't clear storage).  Then reboot phone.  Will try to report back tomorrow if it's still working better this way.

  • knew that was too good to be true...  disconnected again...

  • I have the same problem but I just need to open Garmin Connect to reconnect my Venu 3.

    Sometimes it ask to restart the configuration, but it reconnect even if I skip

    Is it possible to create an automate that open Garmin Connect when the connection is lost?

  • Too good to be true here as well. Now I'm connected via Bluetooth to my phone but not Connect. Toggling, swiping Connect out of memory, have not helped. Guess I'll do what Google has asked and reset network settings. What a pain. 

  • I've had the issue since updating to Android 16 on my pixel 8a with Venu 3.  For me, it seems to consistently trigger whenever there is another device that connects to the phone.  It causes the Venu 3 connection either become unstable or disconnect.  In the case of unstable, the watch looks connected, but updates take a long time in Connect, or fail to finish, and/or message sync doesn't work.  Once I turn off/on bluetooth, Venu connects and stays connected.  I know that if I connect a device to the phone like headphones, car, etc, the watch connection is going to disconnect or look connected but be unstable. The unstable connection obfuscates the trigger in my case. There might be other triggers going on over time, but alternate device connection is somewhat consistent in making it fail for me.

  • Same problem but with Pixel 7a... Can't believe this is a massive issue.