Home

WearOS watches

This page is meant to document how well WearOS watches function with Juggluco. Everyone can contribute to this wiki. If you have experience with a certain watch, you can add your observations. Please tell with what type of sensor you use the watch (US Libre 2, EU Libre 2 or Libre 3) and how you use the watch. You can describe how it functions with the sensor directly connected with the sensor and when the phone is directly connected with the sensor and the watch receives its data from the phone. Describe the advantages and disadvantages. In general I can see that the watch needs to be from after Android Wear was renamed to WearOS. This means that it runs Android 8 or higher. Juggluco can't use the NFC in the watch and scanning is always done with the phone.

Samsung Galaxy Watch 4

One of the cheapest WearOS watches currently on the market and the Samsung Galaxy watch that works best with Juggluco. When the phone is connected with the sensor and the watch receives the glucose values from the phone, the watch functions without difficulty; nearly always receiving glucose values when available. Sometimes sync or reinit is needed. When the watch is on the same arm as the sensor it functions very well when directly connected with the sensor. After how long you need to recharge the battery depends on what you do with the watch. Killing and uninstalling other apps helps to extend battery life, see https://xdaforums.com/t/debloat-galaxy-watch-4.4324147. But don’t expect the battery to last more than 24 hour. At the moment it says that 11 h 23 m is left when 53% full. That is 21 h 30 m when 100% full. When recording an activity the battery empties very fast. A few month ago the watch turned itself off after cycling for three hours, the last time it was after 2 hours and 6 minutes. My watch is about three years old. Juggluco can be connected with multiple Wear OS watches at the same time. Both Watches from the same and different companies can be used together. (When adding Watch 7 after Watch 4, the Galaxy Wearable app didn't connect with Watch 4 anymore, but after a factory reset and some more problems it worked again.) Samsung Galaxy watches higher than watch 4 are worse then Watch 4: They only receive a glucose value very 2 minutes instead of every minute. Normally the sensor sends a glucose value every minute and the receiving app only waits. On Watch 5-7 disconnects after every glucose value, making that Juggluco is constantly busy trying to get a connection and that way draining the battery. When you let Android (=WearOS) do the reconnecting, it maybe uses less battery power, but then it misses even more glucose values.

TicWatch Pro

A 30 Euro second hands exemplar functions as well as Watch 4 when directly connected with Libre 2 sensors, except when it is moved very little. When moving very little while I am asleep, Bluetooth of the watch is turned off. This means that it will lose contact with both the sensor and the phone. Putting the watch on the charger helps against this. Sleep analysis doesn't work on TicWatch Pro, so it doesn't matter. Also the following command can help:

adb shell dumpsys deviceidle disable

See:
https://dontkillmyapp.com/general
https://www.juggluco.nl/JugglucoWearOS/install/adb.html

When directly connected with a Libre 3 it only receives every 2 minutes instead of every minute a glucose value from the sensor. When new the battery capacity is 415mAh.