On glycemic data watches

@Lone said:

@nigiriI don't know if the app you are testing is Juggluco, but if it is, there is a post in which they say that it and Diabox interfere with the signal and cause Librelink to not work correctly.I don't know if that will be the case, I only have Librelink installed and I can't evaluate it.

@JordiV: I was busy with this watch thing and I just saw the data on the watch.I have only installed GlucoDataHandler on the phone and the watch, in addition to installing Librelinkup on the phone.Since I have no idea about all these things, I now have the problem of making the number (now 87) appear above the clock.

Diaboxkotlin with LibreLink work well, Juggluco failed me.

LibreLink would disconnect and I thought it was because of Diabox, but when everything failed I saw that no, it fails the same without anything.The SW is weak to the Bluetooth signal because the sensor sends it in the same band to the mobile, for all applications, it is the management of the App, in this case LibreLink what is not powerful.

I already only have those two with an old A52G mobile with Android 14 and the S4 watch.

If something works... it is best not to change.

@JordiV almost new sensor and I have run out of alarms because it only supports readings and it was due to Juggluco.

@nigiri said:

@JordiValmost new sensor and I have run out of alarms because it only supports readings and it was because of the Juggluco.

Of course, you lose all the history of the App.

Thank you, @

Thank you @