Versa, firmware: 32.70.8.0
Samsung S8+ (SM-G955F) Android v.9
App v: 3.27
I've had my watch now for a few months & been working pretty well.
Sync's seemed to work well over Bluetooth/BLE & tracking metrics OK.
Of late (not sure for how long this has been an issue), the watch has not been able to properly use connectivity.
I keep getting the "Oops, looks like there's no Internet connection" whenever I try to do anything requiring a connection, such as changing watch-face or installing/updating apps.
I've tried this several different ways:
* removing watch straps & phone cover to eliminate any possible interference
* clearing cache on the mobile app & ensuring background data usage is enabled, phone in "high-powered mode" to prevent connectivity throttling or suspension of apps to the background.
* connecting to several WiFi AP's, including hotspotting from my mobile & doing so through a VPN
* removing said AP's from the watch to try & force it to pull data via the bluetooth connection
* doing a factory reset of the watch & re-initialising it again - I had to do this like 3 times, as it gave me some grief during this process (phone had previous bluetooth connection saved that I had to remove 1st). PITA that only served to clear out the watch-faces I paid for, with no means of getting them back now, so won't be repeating that complete waste of time.
* I've not yet removed & re-installed the mobile app, as I have little confidence I won't lose my profile & preferences. Yes, I know that this is all meant to be cloud-based, but see issues above re being able to trust connection & competence.
(Possibly related, ) I've also never had any good experiences with the "feature" where the watch was supposed to "automagically" pick up when I start my exercise routine, i.e. walking or jogging to/through the park, and had to always manually initiate & stop this (which I'll usually forget), so now I just don't bother.
If I were to guess, Id say this looks like just very poor quality firmware for this device, and my guess is the manufacturer may not actually resolve this, as they have a new model out, and that this seems a recurring issue throughout this forum what has not been adequately addressed.
