forked from j-kaltes/Jugglucohelp
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathsensorhelp.html
116 lines (116 loc) · 8.26 KB
/
sensorhelp.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8"/>
<title></title>
<meta name="generator" content="LibreOffice 7.5.5.2 (Linux)"/>
<meta name="created" content="00:00:00"/>
<meta name="changed" content="2023-09-29T12:22:21.061846050"/>
<meta name="created" content="00:00:00">
<meta name="created" content="00:00:00">
</head>
<body lang="en-US" dir="ltr"><p style="margin-top: 0.35in; margin-bottom: 0.35in; border: none; padding: 0in">
<font face="basic sans"><font size="5" style="font-size: 18pt"><b>Sensor</b></font></font></p>
<p style="margin-top: 0.02in; margin-bottom: 0.02in; border: none; padding: 0in">
<font face="basic roman"><font size="2" style="font-size: 10pt">T<font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt">he
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
show information.</font></font></font></font></p>
<p style="margin-top: 0.02in; margin-bottom: 0.02in; border: none; padding: 0in">
<font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt"><i><b>Doze
mode</b></i> leads you to a screen with information on how to disable
battery optimizations for Juggluco, that can prevent Juggluco from
functioning.</font></font></p>
<p style="margin-top: 0.02in; margin-bottom: 0.02in; border: none; padding: 0in">
<font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt"><i><b>Stream
history</b></i>: 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.</font></font></p>
<p style="margin-top: 0.02in; margin-bottom: 0.02in; border: none; padding: 0in">
<font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt">This
option is always turned on for Libre 3 sensors and US Libre 2
sensors.</font></font></p>
<p style="margin-top: 0.02in; margin-bottom: 0.02in; border: none; padding: 0in">
<font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt"><i><b>Permission</b></i>:
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.</font></font></p>
<p style="margin-top: 0.02in; margin-bottom: 0.02in; border: none; padding: 0in">
<font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt">Android
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.</font></font></p>
<p style="margin-top: 0.02in; margin-bottom: 0.02in; border: none; padding: 0in">
<font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt"><i><b>Terminate</b></i>:
stop connecting to this sensor via Bluetooth. If later you want again
receive stream glucose values from this sensor, you only have to scan
it again.</font></font></p>
<p style="margin-top: 0.02in; margin-bottom: 0.02in; border: none; padding: 0in">
<font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt"><i><b>Turbo</b></i>:
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
on.</font></font></p>
<p style="margin-top: 0.02in; margin-bottom: 0.02in; border: none; padding: 0in">
<font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt"><b>Android</b>:
Let Android instead of Juggluco make the connection with the sensor.</font></font></p>
<p style="margin-top: 0.02in; margin-bottom: 0.02in; border: none; padding: 0in">
<font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt"><i><b>Info</b></i>:
Gives start and end times and last scan and stream times of sensor.</font></font></p>
<p style="margin-top: 0.02in; margin-bottom: 0.02in; border: none; padding: 0in">
<font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt">To
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 '</font></font><font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt"><i>force
stop</i></font></font><font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt">'
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 </font></font><a href="https://www.offgridweb.com/preparation/faraday-bags-testing-commercial-and-diy-wireless-signal-blockers/amp"><font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt"><u>Faraday
cage</u></font></font></a><font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt">.</font></font></p>
<p style="margin-top: 0.02in; margin-bottom: 0.02in; border: none; padding: 0in">
<font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt"><b>Sensor
via Bluetooth/Use Bluetooth</b></font></font><font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt">
should be turned on.</font></font></p>
<p style="margin-top: 0.02in; margin-bottom: 0.02in; border: none; padding: 0in">
<font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt">If
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
</font></font><font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt"><i>Connection
stage</i></font></font> <font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt">gives
the most difficulties. The most frequent are failures with
status=133, which is the status argument of
</font></font><a href="#onConnectionStateChange_android_bluetooth_BluetoothGatt__20int__20int_"><font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt"><u>onConnectionStateChange(BluetoothGatt
bluetoothGatt, int status, int newState)</u></font></font></a><font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt">.
It means </font></font><font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt"><i>Bluetooth
device not found</i></font></font><font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt">.
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.</font></font></p>
<p style="margin-top: 0.02in; margin-bottom: 0.02in; border: none; padding: 0in">
<font face="Liberation Serif, serif"><font size="3" style="font-size: 12pt">Scanning
the sensor with Juggluco (with <i>Sensor via Bluetooth</i> 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
again.</font></font></p>
<p style="margin-top: 0.04in; margin-bottom: 0.04in; border: none; padding: 0in">
</p>
</body>
</html>