spinner contains the name of the sensor. If Juggluco is using more
than one sensor at the same time, you can select for which sensor to
leads you to a screen with information on how to disable battery
optimizations for Juggluco, that can prevent Juggluco from
Bluetooth history: On Libre 2, history are values of the past in 15
minute intervals. Previously they were only received by scanning.
When you turn this option on, the History values are also received
via Bluetooth. Also, other things will work differently. To Libreview
will be sent the history values, instead of averages of the stream
values. The disadvantage is that it is slower. This can be an issue
on WearOS watches.
option has no effect on Libre 3 and US Libre 2 sensors; they
always receive history values via Bluetooth.
Previous versions of Juggluco required location permission to find
the device address of the sensor. This is no longer necessary for the
sensors I use. Maybe there are still sensors out there for which it
is necessary; in that case you can turn it on. After the first
contact Juggluco saves the device address and location permission is
always useless. The device address, if known, is displayed after the
sensor identifier. Red means a US-like sensor.
12 has a new Nearby devices permission, which can be used instead of
location permission for searching for a Bluetooth device address, but
it is also needed for later contact with Bluetooth devices.
stop connecting to this sensor via Bluetooth. If later you want again
receive stream glucose values from this sensor, you only have to scan
Increases effort to contact with sensor in the hope that it results
in less connection errors, but can uses more battery power. Seems to
be needed on Watch4 with Freestyle Libre 2 sensors, but not with
Freestyle Libre 3 sensors and on none of the smartphones I tried it
Let Android instead of Juggluco make the connection with the sensor.
Gives start and end times and last scan and stream times of sensor.
connect to a Freestyle Libre 2 sensor via Low Energy Bluetooth,
Bluetooth should be turned on. Before the sensor is scanned
successfully by this app, nothing will happen. The sensor shouldn't
be connected with FreeStyle reader or other applets on smartphones.
Abbotts Librelink app's alarms should be turned off or the app
stopped. Some Librelink apps seem to contact the sensor while alarms
are turned off and can cause connection problems, so use 'force
to be certain. If you have started the sensor with Freestyle Reader
and you can’t turn it off, you can prevent it from getting into
contact with the sensor by putting the reader in a Faraday
via Bluetooth/Use Bluetooth should
be turned on.
the above conditions are satisfied, it can still take a long time
before the app receives glucose values from the sensor. Often it
takes a minute, but at other times it takes much longer. The
the most difficulties. The most frequent are failures with
status=133, which is the status argument of
bluetoothGatt, int status, int newState).
It means Bluetooth
device not found.
Nearly always it just takes some time before the device is found. It
is also possible that the sensor is connected to another device,
temperary not functioning well, other devices are interfering or the
Bluetooth of Android doesn’t function. Sometimes turning Bluetooth
off and on seems to help or rebooting the phone or turning off the
Bluetooth connection of other devices. Other problems are sometimes
resolved by scanning the sensor.
the sensor with Juggluco (with Sensor via Bluetooth enabled)
on another phone, will steal the connection away from this phone and
it can take some time, with scanning in between, to get it back