Juggluco
8.5 57
v10.3.4-phone-li3-si-x-g por Jaap Korthals Altes
Sobre Juggluco
AVOID ANDROID 13: LOW ENERGY BLUETOOTH IS BROKEN.Abbott's Freestyle Libre 2 sensors transmit every minute the perceived glucose value to the connected reader or smartphone. Abbott's Librelink app uses this value only for low and high glucose alarms. Juggluco displays this value on the smartphone in addition to low and high glucose alarms. So you can know your current glucose value without scanning.
Newer versions of Juggluco can also be used with Freestyle Libre 3 sensors, but all further remarks relate to Libre 2. See http://jkaltes.byethost16.com/libre3 for more information about the use of Libre 3.
Juggluco can only take over the Bluetooth connection of a sensor that is already in use, when ALL COMPETING CONNECTIONS WITH THE SENSOR ARE REMOVED by FORCE CLOSING the Libre app and turning off Freestyle reader or turning off alarms of these apps and devices. Hereafter you scan the sensor a few times with your smartphone while Juggluco is in the foreground and, when everything goes well, within 20 minutes or less Juggluco will establish a connection with the sensor and start receiving glucose values via Bluetooth.
After using a sensor with Juggluco, you can still scan the sensor with Librelink or Freestyle Reader, but their alarms will never work again (Patched versions of the Libre 2 or Librelink app can take over the Bluetooth connection when the sensor is new for them (with the result that sensor doesn't work with Juggluco anymore)).
In addition to the Bluetooth stream of glucose values, Juggluco displays the result of scanning: the current value and past 8 hours history out of the memory of the sensor. All in one detailed graph.
You can also add your amounts of insulin, carbohydrate and activity to the graph.
From the Bluetooth stream data summary statistics are generated: time in range, estimated A1c and, if enough data is gathered, a summary graph.
Juggluco can send glucose values to smartwatches in four ways:
- by creating an Android notification that is redirected to some smartwatches (Notify);
- via watch app Kerfstok running on some Garmin watches;
- via xDrip watch apps on all kinds of smartwatches;
- via glucose broadcasts to other Android apps that sends them to connect watches;
- Juggluco for WearOS.
Juggluco can use (but not start) US Freestyle Libre 2 sensors.
WearOSA variant of Juggluco now runs on WearOS. It contains a watch face that shows the minutely glucose value, besides the time and four complications.
Every sensor has to be initialized by the connected Android phone running Juggluco.
Juggluco for Wear OS can operate two ways:
• Receive the glucose values from a smartphone connected to the sensor;
• Directly connect the watch with the sensor and send the glucose values from the watch to the phone.
Earlier a direct connection between Watch 4 and sensor was unusable with half of the Freestyle Libre 2 sensors, because of too many connection errors, but after adding the Turbo button, I had these problems with only 3 of 9 sensors. Also the connection, with the few Freestyle Libre 3 sensors I have tested, is very good. If, when directly connected with the watch, a sensor has too many connection errors, you can connect the watch with the sensor via the smartphone.
For more information: http://jkaltes.byethost16.com/JugglucoWearOS
Newer versions of Juggluco can also be used with Freestyle Libre 3 sensors, but all further remarks relate to Libre 2. See http://jkaltes.byethost16.com/libre3 for more information about the use of Libre 3.
Juggluco can only take over the Bluetooth connection of a sensor that is already in use, when ALL COMPETING CONNECTIONS WITH THE SENSOR ARE REMOVED by FORCE CLOSING the Libre app and turning off Freestyle reader or turning off alarms of these apps and devices. Hereafter you scan the sensor a few times with your smartphone while Juggluco is in the foreground and, when everything goes well, within 20 minutes or less Juggluco will establish a connection with the sensor and start receiving glucose values via Bluetooth.
After using a sensor with Juggluco, you can still scan the sensor with Librelink or Freestyle Reader, but their alarms will never work again (Patched versions of the Libre 2 or Librelink app can take over the Bluetooth connection when the sensor is new for them (with the result that sensor doesn't work with Juggluco anymore)).
In addition to the Bluetooth stream of glucose values, Juggluco displays the result of scanning: the current value and past 8 hours history out of the memory of the sensor. All in one detailed graph.
You can also add your amounts of insulin, carbohydrate and activity to the graph.
From the Bluetooth stream data summary statistics are generated: time in range, estimated A1c and, if enough data is gathered, a summary graph.
Juggluco can send glucose values to smartwatches in four ways:
- by creating an Android notification that is redirected to some smartwatches (Notify);
- via watch app Kerfstok running on some Garmin watches;
- via xDrip watch apps on all kinds of smartwatches;
- via glucose broadcasts to other Android apps that sends them to connect watches;
- Juggluco for WearOS.
Juggluco can use (but not start) US Freestyle Libre 2 sensors.
WearOSA variant of Juggluco now runs on WearOS. It contains a watch face that shows the minutely glucose value, besides the time and four complications.
Every sensor has to be initialized by the connected Android phone running Juggluco.
Juggluco for Wear OS can operate two ways:
• Receive the glucose values from a smartphone connected to the sensor;
• Directly connect the watch with the sensor and send the glucose values from the watch to the phone.
Earlier a direct connection between Watch 4 and sensor was unusable with half of the Freestyle Libre 2 sensors, because of too many connection errors, but after adding the Turbo button, I had these problems with only 3 of 9 sensors. Also the connection, with the few Freestyle Libre 3 sensors I have tested, is very good. If, when directly connected with the watch, a sensor has too many connection errors, you can connect the watch with the sensor via the smartphone.
For more information: http://jkaltes.byethost16.com/JugglucoWearOS
Actualización de Juggluco 10.3.4-phone-li3-si-x-g
Bug fix.
Más información
Características de Juggluco
Versiones antiguas
Más
Variant
Arch
Version
DPI
807
October 7, 2025
Juggluco
10.3.4-phone-li3-si-x-g
(807)
Requires Android: Android 8.0+
Architecture: arm64-v8a
Screen DPI: nodpi
SHA1: 0d164ca031d2b074754b5546691a20335b15fa2d
Base APK: tk.glucodata.apk
Split APKs: config.ar, config.arm64_v8a, config.de, config.en, config.es, config.fr, config.hi, config.in, config.it, config.ja, config.ko, config.my, config.pt, config.ru, config.th, config.tr, config.vi, config.xhdpi, config.zh
Size: 13.59 MB
arm64-v8a
Android 8.0+
nodpi
807
October 7, 2025
Juggluco
10.3.4-phone-li3-si-x-g
(807)
Requires Android: Android 8.0+
Architecture: arm64-v8a
Screen DPI: nodpi
SHA1: 3add082ea50454edc5172cdab2740825d45c8859
Base APK: tk.glucodata.apk
Split APKs: config.ar, config.arm64_v8a, config.de, config.en, config.es, config.fr, config.hi, config.in, config.it, config.ja, config.ko, config.my, config.pt, config.ru, config.th, config.tr, config.vi, config.xxhdpi, config.zh
Size: 13.6 MB
arm64-v8a
Android 8.0+
nodpi
807
October 8, 2025
Juggluco
10.3.4-phone-li3-si-x-g
(807)
Requires Android: Android 8.0+
Architecture: arm64-v8a
Screen DPI: nodpi
SHA1: f589cff25e908c2db502d8487c99742dff803ff8
Base APK: tk.glucodata.apk
Split APKs: config.ar, config.arm64_v8a, config.de, config.en, config.es, config.fr, config.hi, config.in, config.it, config.ja, config.ko, config.my, config.pt, config.ru, config.th, config.tr, config.vi, config.xxxhdpi, config.zh
Size: 14.56 MB
arm64-v8a
Android 8.0+
nodpi
807
October 8, 2025
Juggluco
10.3.4-phone-li3-si-x-g
(807)
Requires Android: Android 8.0+
Architecture: armeabi-v7a
Screen DPI: nodpi
SHA1: 4df78a3a0e532fdeae8aa923423dca8b43900990
Base APK: tk.glucodata.apk
Split APKs: config.ar, config.armeabi_v7a, config.de, config.en, config.es, config.fr, config.hi, config.in, config.it, config.ja, config.ko, config.my, config.pt, config.ru, config.th, config.tr, config.vi, config.xhdpi, config.zh
Size: 13.92 MB
armeabi-v7a
Android 8.0+
nodpi
Requires Android: Android 5.0+
Architecture: arm64-v8a, armeabi-v7a, x86, x86_64
Screen DPI: nodpi
SHA1: 55a515b653eb3692291f6f1c2a583c266721fc81
Size: 48.04 MB
Variant
Arch
Version
DPI
806
September 30, 2025
Juggluco
10.3.3-phone-li3-si-x-g
(806)
Requires Android: Android 8.0+
Architecture: arm64-v8a
Screen DPI: nodpi
SHA1: f41ff578e5058d7e23868d315fd1e263453e77b9
Base APK: tk.glucodata.apk
Split APKs: config.ar, config.arm64_v8a, config.de, config.en, config.es, config.fr, config.hi, config.in, config.it, config.ja, config.ko, config.my, config.pt, config.ru, config.th, config.tr, config.vi, config.xxxhdpi, config.zh
Size: 14.56 MB
arm64-v8a
Android 8.0+
nodpi
806
October 1, 2025
Juggluco
10.3.3-phone-li3-si-x-g
(806)
Requires Android: Android 8.0+
Architecture: arm64-v8a
Screen DPI: nodpi
SHA1: 4533ce13e1d3cb43f9322ef8d39d141451be5b41
Base APK: tk.glucodata.apk
Split APKs: config.ar, config.arm64_v8a, config.de, config.en, config.es, config.fr, config.hi, config.in, config.it, config.ja, config.ko, config.my, config.pt, config.ru, config.th, config.tr, config.vi, config.xhdpi, config.zh
Size: 13.58 MB
arm64-v8a
Android 8.0+
nodpi
806
October 1, 2025
Juggluco
10.3.3-phone-li3-si-x-g
(806)
Requires Android: Android 8.0+
Architecture: arm64-v8a
Screen DPI: nodpi
SHA1: d03666f651576333193d326d3fc4c499c0f89581
Base APK: tk.glucodata.apk
Split APKs: config.ar, config.arm64_v8a, config.de, config.en, config.es, config.fr, config.hi, config.in, config.it, config.ja, config.ko, config.my, config.pt, config.ru, config.th, config.tr, config.vi, config.xxhdpi, config.zh
Size: 13.59 MB
arm64-v8a
Android 8.0+
nodpi
806
October 3, 2025
Juggluco
10.3.3-phone-li3-si-x-g
(806)
Requires Android: Android 8.0+
Architecture: armeabi-v7a
Screen DPI: nodpi
SHA1: 20b052d9cbd13e6a6fc7637e08adc51befe676cb
Base APK: tk.glucodata.apk
Split APKs: config.ar, config.armeabi_v7a, config.de, config.en, config.es, config.fr, config.hi, config.in, config.it, config.ja, config.ko, config.my, config.pt, config.ru, config.th, config.tr, config.vi, config.xhdpi, config.zh
Size: 13.92 MB
armeabi-v7a
Android 8.0+
nodpi
Variant
Arch
Version
DPI
803
September 27, 2025
Juggluco
10.3.2-phone-li3-si-x-g
(803)
Requires Android: Android 8.0+
Architecture: arm64-v8a
Screen DPI: nodpi
SHA1: e805c11bc0887bb37c8306fd7b9250a808c0799d
Base APK: tk.glucodata.apk
Split APKs: config.ar, config.arm64_v8a, config.de, config.en, config.es, config.fr, config.hi, config.in, config.it, config.ja, config.ko, config.my, config.pt, config.ru, config.th, config.tr, config.vi, config.xhdpi, config.zh
Size: 13.59 MB
arm64-v8a
Android 8.0+
nodpi
803
September 27, 2025
Juggluco
10.3.2-phone-li3-si-x-g
(803)
Requires Android: Android 8.0+
Architecture: arm64-v8a
Screen DPI: nodpi
SHA1: bfdfcb80d4c9f75662ff06675a69c4d3eebe4302
Base APK: tk.glucodata.apk
Split APKs: config.ar, config.arm64_v8a, config.de, config.en, config.es, config.fr, config.hi, config.in, config.it, config.ja, config.ko, config.my, config.pt, config.ru, config.th, config.tr, config.vi, config.xxhdpi, config.zh
Size: 13.61 MB
arm64-v8a
Android 8.0+
nodpi
803
September 27, 2025
Juggluco
10.3.2-phone-li3-si-x-g
(803)
Requires Android: Android 8.0+
Architecture: armeabi-v7a
Screen DPI: nodpi
SHA1: 3ee2670e58a916d70b33ad2b478199a96c2da6f2
Base APK: tk.glucodata.apk
Split APKs: config.ar, config.armeabi_v7a, config.de, config.en, config.es, config.fr, config.hi, config.in, config.it, config.ja, config.ko, config.my, config.pt, config.ru, config.th, config.tr, config.vi, config.xhdpi, config.zh
Size: 13.93 MB
armeabi-v7a
Android 8.0+
nodpi
Más información
Nombre de paquete:
Categoría:
Fecha de actualización:
2025-10-08
Última versión:
10.3.4-phone-li3-si-x-g
Pedir actualización:
Disponible en:
Requisitos:
Android 8.0+
Denunciar:
Descarga segura
APKFab.com y el enlace de descarga de esta aplicación son 100% seguros. Todos los enlaces de descarga de aplicaciones que aparecen en APKFab.com son de Google Play Store o enviados por los usuarios. Para la aplicación desde Google Play Store, APKFab.com no lo modificará de ninguna manera. Para la aplicación enviada por los usuarios, APKFab.com verificará la seguridad de la firma de APK antes de publicarla en nuestro sitio web.