<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Home</title><link>https://sourceforge.net/p/juggluco/wiki/Home/</link><description>Recent changes to Home</description><atom:link href="https://sourceforge.net/p/juggluco/wiki/Home/feed" rel="self"/><language>en</language><lastBuildDate>Wed, 14 Jan 2026 14:13:57 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/juggluco/wiki/Home/feed" rel="self" type="application/rss+xml"/><item><title>Home modified by Jaap Korthals Altes</title><link>https://sourceforge.net/p/juggluco/wiki/Home/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v32
+++ v33
@@ -11,9 +11,7 @@
 Normally, the Freestyle Libre sensor sends a glucose value every minute and the receiving app only waits.  Watch 5-7/ultra somehow isn’t able to receive the second glucose value and disconnects. This means that Juggluco has to reconnect every minute, thereby draining the battery. When the battery is 100% full, the SM-L300 predicts 15 hours remaining when the sensor is directly connected to the watch.&lt;br/&gt;
 &lt;img alt="Available" height="432" rel="nofollow" src="https://github.com/user-attachments/assets/8080515c-6510-465e-a37f-3c3c4e0650ab" width="432"/&gt;

-This is only a problem of sensors that send every minute a glucose value: Accu-Check SmartGuide sends only every 5 minute a glucose value, and that value is received very 5 minute without disconnecting. Dexcom G7/ONE+ disconnects also on phones after every glucose value.&lt;p&gt;&lt;/p&gt;&lt;p&gt;
-Also, the sensor uses more electricity because of the constantly re-connections, meaning that a Libre 3+  sensor ends (for example) after 13 days instead of 15 days. Such sensor with an empty battery will give constant status=133 connection errors under WearOS and can no longer be scanned with the phone.
-If you want to use the sensor for the full period, you can either take another watch, only connect the sensor directly with the watch when it is really needed or take Accu-Chek SmartGuide sensors.
+This is only a problem of sensors that send every minute a glucose value: Accu-Check SmartGuide sends only every 5 minute a glucose value, and that value is received very 5 minute without disconnecting. Dexcom G7/ONE+ disconnects also on phones after every glucose value.&lt;/p&gt;
 This problem is shared by Samsung Galaxy Watch 5 to Ultra.
 ## 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.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jaap Korthals Altes</dc:creator><pubDate>Wed, 14 Jan 2026 14:13:57 -0000</pubDate><guid>https://sourceforge.net52b75d93e4268173b1b650cd77c40f041799f3c1</guid></item><item><title>Home modified by Jaap Korthals Altes</title><link>https://sourceforge.net/p/juggluco/wiki/Home/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v31
+++ v32
@@ -11,7 +11,10 @@
 Normally, the Freestyle Libre sensor sends a glucose value every minute and the receiving app only waits.  Watch 5-7/ultra somehow isn’t able to receive the second glucose value and disconnects. This means that Juggluco has to reconnect every minute, thereby draining the battery. When the battery is 100% full, the SM-L300 predicts 15 hours remaining when the sensor is directly connected to the watch.&lt;br/&gt;
 &lt;img alt="Available" height="432" rel="nofollow" src="https://github.com/user-attachments/assets/8080515c-6510-465e-a37f-3c3c4e0650ab" width="432"/&gt;

-This is only a problem of sensors that send every minute a glucose value: Accu-Check SmartGuide sends only every 5 minute a glucose value, and that value is received very 5 minute without disconnecting. Dexcom G7/ONE+ disconnects also on phones after every glucose value.
+This is only a problem of sensors that send every minute a glucose value: Accu-Check SmartGuide sends only every 5 minute a glucose value, and that value is received very 5 minute without disconnecting. Dexcom G7/ONE+ disconnects also on phones after every glucose value.&lt;p&gt;&lt;/p&gt;&lt;p&gt;
+Also, the sensor uses more electricity because of the constantly re-connections, meaning that a Libre 3+  sensor ends (for example) after 13 days instead of 15 days. Such sensor with an empty battery will give constant status=133 connection errors under WearOS and can no longer be scanned with the phone.
+If you want to use the sensor for the full period, you can either take another watch, only connect the sensor directly with the watch when it is really needed or take Accu-Chek SmartGuide sensors.
+This problem is shared by Samsung Galaxy Watch 5 to Ultra.
 ## 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:
&lt;/p&gt;&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jaap Korthals Altes</dc:creator><pubDate>Wed, 14 Jan 2026 14:13:57 -0000</pubDate><guid>https://sourceforge.netf4904dbcc7557cdc0247fd8591347e1be9c10477</guid></item><item><title>Home modified by Jaap Korthals Altes</title><link>https://sourceforge.net/p/juggluco/wiki/Home/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v30
+++ v31
@@ -9,6 +9,8 @@
 ## Watch7
 Samsung Galaxy Watch7 is good at forming a connection with the glucose sensor, but needs to reconnect every minute for sensors that send every minute a glucose value.
 Normally, the Freestyle Libre sensor sends a glucose value every minute and the receiving app only waits.  Watch 5-7/ultra somehow isn’t able to receive the second glucose value and disconnects. This means that Juggluco has to reconnect every minute, thereby draining the battery. When the battery is 100% full, the SM-L300 predicts 15 hours remaining when the sensor is directly connected to the watch.&lt;br/&gt;
+&lt;img alt="Available" height="432" rel="nofollow" src="https://github.com/user-attachments/assets/8080515c-6510-465e-a37f-3c3c4e0650ab" width="432"/&gt;
+
 This is only a problem of sensors that send every minute a glucose value: Accu-Check SmartGuide sends only every 5 minute a glucose value, and that value is received very 5 minute without disconnecting. Dexcom G7/ONE+ disconnects also on phones after every glucose value.
 ## 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.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jaap Korthals Altes</dc:creator><pubDate>Wed, 14 Jan 2026 14:13:57 -0000</pubDate><guid>https://sourceforge.net52a52227e3f30e1aa513c819dc97d749c4f0e5fd</guid></item><item><title>Home modified by Jaap Korthals Altes</title><link>https://sourceforge.net/p/juggluco/wiki/Home/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v29
+++ v30
@@ -8,7 +8,7 @@
 Juggluco can be connected with multiple Wear OS watches at the same time, but only when they use a different companion app. Two watches can be used with the Samsung Galaxy Wearable app, but you have to select which one is active at a given time.
 ## Watch7
 Samsung Galaxy Watch7 is good at forming a connection with the glucose sensor, but needs to reconnect every minute for sensors that send every minute a glucose value.
-Normally, the Freestyle Libre sensor sends a glucose value every minute and the receiving app only waits.  Watch 5-7/ultra somehow isn’t able to receive the second glucose value and disconnects. This means that Juggluco has to reconnect every minute, thereby draining the battery. When the battery is 100% full, the SM-L300 predicts 15 hours remaining when the sensor is directly connected to the watch.
+Normally, the Freestyle Libre sensor sends a glucose value every minute and the receiving app only waits.  Watch 5-7/ultra somehow isn’t able to receive the second glucose value and disconnects. This means that Juggluco has to reconnect every minute, thereby draining the battery. When the battery is 100% full, the SM-L300 predicts 15 hours remaining when the sensor is directly connected to the watch.&lt;br/&gt;
 This is only a problem of sensors that send every minute a glucose value: Accu-Check SmartGuide sends only every 5 minute a glucose value, and that value is received very 5 minute without disconnecting. Dexcom G7/ONE+ disconnects also on phones after every glucose value.
 ## 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.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jaap Korthals Altes</dc:creator><pubDate>Wed, 14 Jan 2026 14:13:57 -0000</pubDate><guid>https://sourceforge.net9473a710c58cbc9745c5947073c2b170f89cfd4c</guid></item><item><title>Home modified by Jaap Korthals Altes</title><link>https://sourceforge.net/p/juggluco/wiki/Home/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v28
+++ v29
@@ -3,7 +3,7 @@
 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.
+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, but only when they use a different companion app. Two watches can be used with the Samsung Galaxy Wearable app, but you have to select which one is active at a given time.
 ## Watch7
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jaap Korthals Altes</dc:creator><pubDate>Wed, 14 Jan 2026 14:13:57 -0000</pubDate><guid>https://sourceforge.netda5fe03ade89120f26529ab6f09a36b2f276fc3f</guid></item><item><title>Home modified by Jaap Korthals Altes</title><link>https://sourceforge.net/p/juggluco/wiki/Home/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v27
+++ v28
@@ -8,7 +8,7 @@
 Juggluco can be connected with multiple Wear OS watches at the same time, but only when they use a different companion app. Two watches can be used with the Samsung Galaxy Wearable app, but you have to select which one is active at a given time.
 ## Watch7
 Samsung Galaxy Watch7 is good at forming a connection with the glucose sensor, but needs to reconnect every minute for sensors that send every minute a glucose value.
-Normally, the Freestyle Libre sensor sends a glucose value every minute and the receiving app only waits.  Watch 5-7/ultra somehow isn’t able to receive the second glucose value and disconnects. This means that Juggluco has to reconnect every minute, thereby draining the battery.
+Normally, the Freestyle Libre sensor sends a glucose value every minute and the receiving app only waits.  Watch 5-7/ultra somehow isn’t able to receive the second glucose value and disconnects. This means that Juggluco has to reconnect every minute, thereby draining the battery. When the battery is 100% full, the SM-L300 predicts 15 hours remaining when the sensor is directly connected to the watch.
 This is only a problem of sensors that send every minute a glucose value: Accu-Check SmartGuide sends only every 5 minute a glucose value, and that value is received very 5 minute without disconnecting. Dexcom G7/ONE+ disconnects also on phones after every glucose value.
 ## 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.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jaap Korthals Altes</dc:creator><pubDate>Wed, 14 Jan 2026 14:13:57 -0000</pubDate><guid>https://sourceforge.net2bdbc2f228a4e230e358f022566ebab03c2b1105</guid></item><item><title>Home modified by Jaap Korthals Altes</title><link>https://sourceforge.net/p/juggluco/wiki/Home/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v26
+++ v27
@@ -8,7 +8,7 @@
 Juggluco can be connected with multiple Wear OS watches at the same time, but only when they use a different companion app. Two watches can be used with the Samsung Galaxy Wearable app, but you have to select which one is active at a given time.
 ## Watch7
 Samsung Galaxy Watch7 is good at forming a connection with the glucose sensor, but needs to reconnect every minute for sensors that send every minute a glucose value.
-Normally, the Freestyle Libre sensor sends a glucose value every minute and the receiving app only waits.  Watch 5-7 ultra somehow isn’t able to receive the second glucose value and disconnects. This means that Juggluco has to reconnect every minute, thereby draining the battery.
+Normally, the Freestyle Libre sensor sends a glucose value every minute and the receiving app only waits.  Watch 5-7/ultra somehow isn’t able to receive the second glucose value and disconnects. This means that Juggluco has to reconnect every minute, thereby draining the battery.
 This is only a problem of sensors that send every minute a glucose value: Accu-Check SmartGuide sends only every 5 minute a glucose value, and that value is received very 5 minute without disconnecting. Dexcom G7/ONE+ disconnects also on phones after every glucose value.
 ## 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.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jaap Korthals Altes</dc:creator><pubDate>Wed, 14 Jan 2026 14:13:57 -0000</pubDate><guid>https://sourceforge.netaf17dc5238176423e54eb553b752c3d10f5e5ace</guid></item><item><title>Home modified by Jaap Korthals Altes</title><link>https://sourceforge.net/p/juggluco/wiki/Home/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v25
+++ v26
@@ -5,7 +5,7 @@
 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.)
+Juggluco can be connected with multiple Wear OS watches at the same time, but only when they use a different companion app. Two watches can be used with the Samsung Galaxy Wearable app, but you have to select which one is active at a given time.
 ## Watch7
 Samsung Galaxy Watch7 is good at forming a connection with the glucose sensor, but needs to reconnect every minute for sensors that send every minute a glucose value.
 Normally, the Freestyle Libre sensor sends a glucose value every minute and the receiving app only waits.  Watch 5-7 ultra somehow isn’t able to receive the second glucose value and disconnects. This means that Juggluco has to reconnect every minute, thereby draining the battery.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jaap Korthals Altes</dc:creator><pubDate>Wed, 14 Jan 2026 14:13:57 -0000</pubDate><guid>https://sourceforge.netac1c8fbeb282414e44693eeeb1aecb2faff60da6</guid></item><item><title>Home modified by Jaap Korthals Altes</title><link>https://sourceforge.net/p/juggluco/wiki/Home/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v24
+++ v25
@@ -6,7 +6,10 @@
 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.
+## Watch7
+Samsung Galaxy Watch7 is good at forming a connection with the glucose sensor, but needs to reconnect every minute for sensors that send every minute a glucose value.
+Normally, the Freestyle Libre sensor sends a glucose value every minute and the receiving app only waits.  Watch 5-7 ultra somehow isn’t able to receive the second glucose value and disconnects. This means that Juggluco has to reconnect every minute, thereby draining the battery.
+This is only a problem of sensors that send every minute a glucose value: Accu-Check SmartGuide sends only every 5 minute a glucose value, and that value is received very 5 minute without disconnecting. Dexcom G7/ONE+ disconnects also on phones after every glucose value.
 ## 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:
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jaap Korthals Altes</dc:creator><pubDate>Wed, 14 Jan 2026 14:13:57 -0000</pubDate><guid>https://sourceforge.net71e47bb6ec5103c19d0b9661abd4e070864bfa66</guid></item><item><title>Home modified by Jaap Korthals Altes</title><link>https://sourceforge.net/p/juggluco/wiki/Home/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v23
+++ v24
@@ -18,6 +18,11 @@
 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.
+
+## OnePlus Watch 3 (OPWWE251)
+This watch works very well with Juggluco. It has a very good battery life and quite stable connection while connecting directly to Libre 2 or Libre 3.
+With phone-sensor connection it can last up to 3 days. 
+
 ## Other Watches
 Here is a list of all WearOS watches that can run Juggluco according to Google Play: https://www.juggluco.nl/JugglucoWearOS/watches.html

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jaap Korthals Altes</dc:creator><pubDate>Wed, 14 Jan 2026 14:13:57 -0000</pubDate><guid>https://sourceforge.net6b42eaedcc96197a7a6bd2e232c8503d39b5e115</guid></item></channel></rss>