I landed in Atlanta an hour ago.
Since that time, I have been trying to sync my Basis B1 activity monitor watch. If for no other reason than to get the watch set to the east coast timezone.
Slowness and eventual failure. Repeatedly.
One big complaint I have about iOS devices in general is that they seem to have much poorer background operation than Android. For example, on Android my Basis watch would sync without me having to open the application. Worse, I seem to have to babysit it to ensure that the iPhone does not go into a powersave mode.
I do not know if this is fundamental to iOS, or just a simple matter of programming. Certainly, many iOS apps & devices behave this way - they operate only when in foreground.
This reminds me of old MacOS, with "cooperative multitasking", rather than fully preemptive scheduling.
This may be a compromise to save battery life. Certainly my iPhone seems to have better life than a Samsung with comparable battery. But that may be the fault of Samsung bloatware, rather than Android itself.
--
This iOS characteristic does not let Basis off the hook.
The Basis consistently fails at 49% transferred. At one point I saw a "low memory" warning on the watch. Low memory when sync'ing - surely they reserve a minimum buffer size to finish a transfer.?
Subscribe to:
Post Comments (Atom)
1 comment:
Finally "synced". 1.5 hours.
Well, not really synced.
My watch has the correct timezone.
The iPhone app reports synced a minute ago.
But the watch reports that I walked 2K steps in the airport so far, while the app and website report none.
As you can imagine, a combination of bluetooth sync, usb sync, hard reset. All in an order that seems non-reproducible.
Post a Comment