diff --git a/docs/CROWDIN/cs/CompatibleCgms/Libre2MinimalL00per.md b/docs/CROWDIN/cs/CompatibleCgms/Libre2MinimalL00per.md index 38d606b00b0c..b6aa5c5412ab 100644 --- a/docs/CROWDIN/cs/CompatibleCgms/Libre2MinimalL00per.md +++ b/docs/CROWDIN/cs/CompatibleCgms/Libre2MinimalL00per.md @@ -292,31 +292,24 @@ Press the Hamburger menu in the upper left of the xDrip+ Overview screen and sel On the **BT Device** (swipe left) screen you can verify further connection details of the sensor as well as use this screen for troubleshooting connections. Below is a list of fields and their purposes to assist in connection troubleshooting. -*NOTE: **DO NOT click on Bluetooth Pairing** in this window as your sensor has already been paried or is in the middle of the pairing and bonding process. Doing so will attempt a direct pair and you will have to start the process from Step 5 all over again.* +*NOTE: **DO NOT TOUCH AND CHANGE Bluetooth Pairing from Disabled** in this window. Doing so will attempt a direct pair, it will fail (Not bonded) and you will have to start the process from Step 5 all over again.* -- **Phone Service State:** The last time the phone made a BT connection to the sensor +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) +- **Phone Service State:** The last time the phone made a BT connection to the sensor (it should be less than 5 minutes ago) - **Bluetooth Device:** Displays current status of the connection (either **Connected** or **Disconnected**) - -- **Active device connection:** Displays the status of the bluetooth bond after connection. **True** means the sensor is connected and bonded. - - **Device Mac Address**: This is the hardware ID of the sensor +- **Bluetooth Pairing**: This should be **Disabled, tap to enable**. Be careful to NOT tap this. If you tap it by mistake, tap it again until it returns to disabled. +- **Slowest wake up**: You can ignore this. xDrip+ doesn't spend its time waiting for readings: it will start expecting them at after a certain time (traditionally 5 minutes). If no data arrives at that time, you'll see "Woke up early" meaning xDrip+ was expecting data to be ready but there's none. Slowest wake up is the highest delay encountered before receiving data normally. +- **Next Wake up**: Should say 5 minutes -- **GATT device connected:** This is the hardware ID registered in the Android BT service. Any bluetooth devices actively bonded to your phone will display their hardware ID here. The GATT and Device Address should match for your sensor hardware ID. - -- **Request Data:** Only shown with Engineering Mode enabled in xDrip+. Pressing **Test for xBridgePlus protocol** you can manually start a request for data from your sensor. - -- **Received Data:** This is a hexadecimal representation of the data stream coming from your sensor. If you see characters here then you are actively receiving data from the sensor. The data should change after pressing **Test for xBridgePlus protocol**. - -- **Send Data:** This is the data request hexadecimal stream sent to the sensor to start data retrieval. After pressing **Test for xBridgePlus protocol** you should see this field update however, the data may not change a the request is the same each time. - - ![xDrip+ scan](../images/minimal00per/xdripSStat.png) +![xDrip+ scan](../images/minimal00per/xdripSStat.png) (minimallooper-notes)= ### **Poznámky** -- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (ie. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to rebond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. +- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (i.e. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to re-bond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. - - **What is going on?** When a Bluetooth connection is made a private shared key is created that is needed to allow communication between the sensor and the calling application/device. There is a high probability that the LL app or the Reader creates a new private shared key for communication during the connection. This means that after bonding, xDrip+ is not aware of the new key and will not be able to communicate with the sensor. @@ -459,6 +452,9 @@ Make sure you are running the latest versions of xDrip+ and OOP2. - Verify OOP2 is not put to sleep by the phone battery savings apps and settings - Verify Google Play protect is disabled as it will kill OOP2 +- Did you change Bluetooth Pairing in System Status? Touch it back to bring it back to **Disabled** + +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) #### Missed readings diff --git a/docs/CROWDIN/cs/images/minimal00per/xdripSSbond.png b/docs/CROWDIN/cs/images/minimal00per/xdripSSbond.png new file mode 100644 index 000000000000..8a222fc80895 Binary files /dev/null and b/docs/CROWDIN/cs/images/minimal00per/xdripSSbond.png differ diff --git a/docs/CROWDIN/cs/images/minimal00per/xdripSSlog.png b/docs/CROWDIN/cs/images/minimal00per/xdripSSlog.png index cb1fac206823..9edaa3f2bb48 100644 Binary files a/docs/CROWDIN/cs/images/minimal00per/xdripSSlog.png and b/docs/CROWDIN/cs/images/minimal00per/xdripSSlog.png differ diff --git a/docs/CROWDIN/cs/images/minimal00per/xdripSStat.png b/docs/CROWDIN/cs/images/minimal00per/xdripSStat.png index 77fac8ebc0cd..1e77e9229cd2 100644 Binary files a/docs/CROWDIN/cs/images/minimal00per/xdripSStat.png and b/docs/CROWDIN/cs/images/minimal00per/xdripSStat.png differ diff --git a/docs/CROWDIN/de/CompatibleCgms/Libre2MinimalL00per.md b/docs/CROWDIN/de/CompatibleCgms/Libre2MinimalL00per.md index 5bc5cd70d032..241b31f6830c 100644 --- a/docs/CROWDIN/de/CompatibleCgms/Libre2MinimalL00per.md +++ b/docs/CROWDIN/de/CompatibleCgms/Libre2MinimalL00per.md @@ -292,31 +292,24 @@ Press the Hamburger menu in the upper left of the xDrip+ Overview screen and sel On the **BT Device** (swipe left) screen you can verify further connection details of the sensor as well as use this screen for troubleshooting connections. Below is a list of fields and their purposes to assist in connection troubleshooting. -*NOTE: **DO NOT click on Bluetooth Pairing** in this window as your sensor has already been paried or is in the middle of the pairing and bonding process. Doing so will attempt a direct pair and you will have to start the process from Step 5 all over again.* +*NOTE: **DO NOT TOUCH AND CHANGE Bluetooth Pairing from Disabled** in this window. Doing so will attempt a direct pair, it will fail (Not bonded) and you will have to start the process from Step 5 all over again.* -- **Phone Service State:** The last time the phone made a BT connection to the sensor +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) +- **Phone Service State:** The last time the phone made a BT connection to the sensor (it should be less than 5 minutes ago) - **Bluetooth Device:** Displays current status of the connection (either **Connected** or **Disconnected**) - -- **Active device connection:** Displays the status of the bluetooth bond after connection. **True** means the sensor is connected and bonded. - - **Device Mac Address**: This is the hardware ID of the sensor +- **Bluetooth Pairing**: This should be **Disabled, tap to enable**. Be careful to NOT tap this. If you tap it by mistake, tap it again until it returns to disabled. +- **Slowest wake up**: You can ignore this. xDrip+ doesn't spend its time waiting for readings: it will start expecting them at after a certain time (traditionally 5 minutes). If no data arrives at that time, you'll see "Woke up early" meaning xDrip+ was expecting data to be ready but there's none. Slowest wake up is the highest delay encountered before receiving data normally. +- **Next Wake up**: Should say 5 minutes -- **GATT device connected:** This is the hardware ID registered in the Android BT service. Any bluetooth devices actively bonded to your phone will display their hardware ID here. The GATT and Device Address should match for your sensor hardware ID. - -- **Request Data:** Only shown with Engineering Mode enabled in xDrip+. Pressing **Test for xBridgePlus protocol** you can manually start a request for data from your sensor. - -- **Received Data:** This is a hexadecimal representation of the data stream coming from your sensor. If you see characters here then you are actively receiving data from the sensor. The data should change after pressing **Test for xBridgePlus protocol**. - -- **Send Data:** This is the data request hexadecimal stream sent to the sensor to start data retrieval. After pressing **Test for xBridgePlus protocol** you should see this field update however, the data may not change a the request is the same each time. - - ![xDrip+ scan](../images/minimal00per/xdripSStat.png) +![xDrip+ scan](../images/minimal00per/xdripSStat.png) (minimallooper-notes)= ### **Notiz** -- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (ie. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to rebond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. +- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (i.e. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to re-bond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. - - **What is going on?** When a Bluetooth connection is made a private shared key is created that is needed to allow communication between the sensor and the calling application/device. There is a high probability that the LL app or the Reader creates a new private shared key for communication during the connection. This means that after bonding, xDrip+ is not aware of the new key and will not be able to communicate with the sensor. @@ -459,6 +452,9 @@ Make sure you are running the latest versions of xDrip+ and OOP2. - Verify OOP2 is not put to sleep by the phone battery savings apps and settings - Verify Google Play protect is disabled as it will kill OOP2 +- Did you change Bluetooth Pairing in System Status? Touch it back to bring it back to **Disabled** + +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) #### Missed readings diff --git a/docs/CROWDIN/de/images/minimal00per/xdripSSbond.png b/docs/CROWDIN/de/images/minimal00per/xdripSSbond.png new file mode 100644 index 000000000000..8a222fc80895 Binary files /dev/null and b/docs/CROWDIN/de/images/minimal00per/xdripSSbond.png differ diff --git a/docs/CROWDIN/de/images/minimal00per/xdripSSlog.png b/docs/CROWDIN/de/images/minimal00per/xdripSSlog.png index cb1fac206823..9edaa3f2bb48 100644 Binary files a/docs/CROWDIN/de/images/minimal00per/xdripSSlog.png and b/docs/CROWDIN/de/images/minimal00per/xdripSSlog.png differ diff --git a/docs/CROWDIN/de/images/minimal00per/xdripSStat.png b/docs/CROWDIN/de/images/minimal00per/xdripSStat.png index 77fac8ebc0cd..1e77e9229cd2 100644 Binary files a/docs/CROWDIN/de/images/minimal00per/xdripSStat.png and b/docs/CROWDIN/de/images/minimal00per/xdripSStat.png differ diff --git a/docs/CROWDIN/el/CompatibleCgms/Libre2MinimalL00per.md b/docs/CROWDIN/el/CompatibleCgms/Libre2MinimalL00per.md index 9a422104e713..9680a78fe4d2 100644 --- a/docs/CROWDIN/el/CompatibleCgms/Libre2MinimalL00per.md +++ b/docs/CROWDIN/el/CompatibleCgms/Libre2MinimalL00per.md @@ -292,31 +292,24 @@ Press the Hamburger menu in the upper left of the xDrip+ Overview screen and sel On the **BT Device** (swipe left) screen you can verify further connection details of the sensor as well as use this screen for troubleshooting connections. Below is a list of fields and their purposes to assist in connection troubleshooting. -*NOTE: **DO NOT click on Bluetooth Pairing** in this window as your sensor has already been paried or is in the middle of the pairing and bonding process. Doing so will attempt a direct pair and you will have to start the process from Step 5 all over again.* +*NOTE: **DO NOT TOUCH AND CHANGE Bluetooth Pairing from Disabled** in this window. Doing so will attempt a direct pair, it will fail (Not bonded) and you will have to start the process from Step 5 all over again.* -- **Phone Service State:** The last time the phone made a BT connection to the sensor +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) +- **Phone Service State:** The last time the phone made a BT connection to the sensor (it should be less than 5 minutes ago) - **Bluetooth Device:** Displays current status of the connection (either **Connected** or **Disconnected**) - -- **Active device connection:** Displays the status of the bluetooth bond after connection. **True** means the sensor is connected and bonded. - - **Device Mac Address**: This is the hardware ID of the sensor +- **Bluetooth Pairing**: This should be **Disabled, tap to enable**. Be careful to NOT tap this. If you tap it by mistake, tap it again until it returns to disabled. +- **Slowest wake up**: You can ignore this. xDrip+ doesn't spend its time waiting for readings: it will start expecting them at after a certain time (traditionally 5 minutes). If no data arrives at that time, you'll see "Woke up early" meaning xDrip+ was expecting data to be ready but there's none. Slowest wake up is the highest delay encountered before receiving data normally. +- **Next Wake up**: Should say 5 minutes -- **GATT device connected:** This is the hardware ID registered in the Android BT service. Any bluetooth devices actively bonded to your phone will display their hardware ID here. The GATT and Device Address should match for your sensor hardware ID. - -- **Request Data:** Only shown with Engineering Mode enabled in xDrip+. Pressing **Test for xBridgePlus protocol** you can manually start a request for data from your sensor. - -- **Received Data:** This is a hexadecimal representation of the data stream coming from your sensor. If you see characters here then you are actively receiving data from the sensor. The data should change after pressing **Test for xBridgePlus protocol**. - -- **Send Data:** This is the data request hexadecimal stream sent to the sensor to start data retrieval. After pressing **Test for xBridgePlus protocol** you should see this field update however, the data may not change a the request is the same each time. - - ![xDrip+ scan](../images/minimal00per/xdripSStat.png) +![xDrip+ scan](../images/minimal00per/xdripSStat.png) (minimallooper-notes)= ### **Σημειώσεις** -- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (ie. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to rebond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. +- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (i.e. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to re-bond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. - - **What is going on?** When a Bluetooth connection is made a private shared key is created that is needed to allow communication between the sensor and the calling application/device. There is a high probability that the LL app or the Reader creates a new private shared key for communication during the connection. This means that after bonding, xDrip+ is not aware of the new key and will not be able to communicate with the sensor. @@ -459,6 +452,9 @@ Make sure you are running the latest versions of xDrip+ and OOP2. - Verify OOP2 is not put to sleep by the phone battery savings apps and settings - Verify Google Play protect is disabled as it will kill OOP2 +- Did you change Bluetooth Pairing in System Status? Touch it back to bring it back to **Disabled** + +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) #### Missed readings diff --git a/docs/CROWDIN/el/images/minimal00per/xdripSSbond.png b/docs/CROWDIN/el/images/minimal00per/xdripSSbond.png new file mode 100644 index 000000000000..8a222fc80895 Binary files /dev/null and b/docs/CROWDIN/el/images/minimal00per/xdripSSbond.png differ diff --git a/docs/CROWDIN/el/images/minimal00per/xdripSSlog.png b/docs/CROWDIN/el/images/minimal00per/xdripSSlog.png index cb1fac206823..9edaa3f2bb48 100644 Binary files a/docs/CROWDIN/el/images/minimal00per/xdripSSlog.png and b/docs/CROWDIN/el/images/minimal00per/xdripSSlog.png differ diff --git a/docs/CROWDIN/el/images/minimal00per/xdripSStat.png b/docs/CROWDIN/el/images/minimal00per/xdripSStat.png index 77fac8ebc0cd..1e77e9229cd2 100644 Binary files a/docs/CROWDIN/el/images/minimal00per/xdripSStat.png and b/docs/CROWDIN/el/images/minimal00per/xdripSStat.png differ diff --git a/docs/CROWDIN/es/CompatibleCgms/Libre2MinimalL00per.md b/docs/CROWDIN/es/CompatibleCgms/Libre2MinimalL00per.md index ed0c99c0d329..3fb73921782b 100644 --- a/docs/CROWDIN/es/CompatibleCgms/Libre2MinimalL00per.md +++ b/docs/CROWDIN/es/CompatibleCgms/Libre2MinimalL00per.md @@ -292,31 +292,24 @@ Press the Hamburger menu in the upper left of the xDrip+ Overview screen and sel On the **BT Device** (swipe left) screen you can verify further connection details of the sensor as well as use this screen for troubleshooting connections. Below is a list of fields and their purposes to assist in connection troubleshooting. -*NOTE: **DO NOT click on Bluetooth Pairing** in this window as your sensor has already been paried or is in the middle of the pairing and bonding process. Doing so will attempt a direct pair and you will have to start the process from Step 5 all over again.* +*NOTE: **DO NOT TOUCH AND CHANGE Bluetooth Pairing from Disabled** in this window. Doing so will attempt a direct pair, it will fail (Not bonded) and you will have to start the process from Step 5 all over again.* -- **Phone Service State:** The last time the phone made a BT connection to the sensor +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) +- **Phone Service State:** The last time the phone made a BT connection to the sensor (it should be less than 5 minutes ago) - **Bluetooth Device:** Displays current status of the connection (either **Connected** or **Disconnected**) - -- **Active device connection:** Displays the status of the bluetooth bond after connection. **True** means the sensor is connected and bonded. - - **Device Mac Address**: This is the hardware ID of the sensor +- **Bluetooth Pairing**: This should be **Disabled, tap to enable**. Be careful to NOT tap this. If you tap it by mistake, tap it again until it returns to disabled. +- **Slowest wake up**: You can ignore this. xDrip+ doesn't spend its time waiting for readings: it will start expecting them at after a certain time (traditionally 5 minutes). If no data arrives at that time, you'll see "Woke up early" meaning xDrip+ was expecting data to be ready but there's none. Slowest wake up is the highest delay encountered before receiving data normally. +- **Next Wake up**: Should say 5 minutes -- **GATT device connected:** This is the hardware ID registered in the Android BT service. Any bluetooth devices actively bonded to your phone will display their hardware ID here. The GATT and Device Address should match for your sensor hardware ID. - -- **Request Data:** Only shown with Engineering Mode enabled in xDrip+. Pressing **Test for xBridgePlus protocol** you can manually start a request for data from your sensor. - -- **Received Data:** This is a hexadecimal representation of the data stream coming from your sensor. If you see characters here then you are actively receiving data from the sensor. The data should change after pressing **Test for xBridgePlus protocol**. - -- **Send Data:** This is the data request hexadecimal stream sent to the sensor to start data retrieval. After pressing **Test for xBridgePlus protocol** you should see this field update however, the data may not change a the request is the same each time. - - ![xDrip+ scan](../images/minimal00per/xdripSStat.png) +![xDrip+ scan](../images/minimal00per/xdripSStat.png) (minimallooper-notes)= ### **Notes** -- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (ie. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to rebond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. +- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (i.e. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to re-bond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. - - **What is going on?** When a Bluetooth connection is made a private shared key is created that is needed to allow communication between the sensor and the calling application/device. There is a high probability that the LL app or the Reader creates a new private shared key for communication during the connection. This means that after bonding, xDrip+ is not aware of the new key and will not be able to communicate with the sensor. @@ -459,6 +452,9 @@ Make sure you are running the latest versions of xDrip+ and OOP2. - Verify OOP2 is not put to sleep by the phone battery savings apps and settings - Verify Google Play protect is disabled as it will kill OOP2 +- Did you change Bluetooth Pairing in System Status? Touch it back to bring it back to **Disabled** + +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) #### Missed readings diff --git a/docs/CROWDIN/es/images/minimal00per/xdripSSbond.png b/docs/CROWDIN/es/images/minimal00per/xdripSSbond.png new file mode 100644 index 000000000000..8a222fc80895 Binary files /dev/null and b/docs/CROWDIN/es/images/minimal00per/xdripSSbond.png differ diff --git a/docs/CROWDIN/es/images/minimal00per/xdripSSlog.png b/docs/CROWDIN/es/images/minimal00per/xdripSSlog.png index cb1fac206823..9edaa3f2bb48 100644 Binary files a/docs/CROWDIN/es/images/minimal00per/xdripSSlog.png and b/docs/CROWDIN/es/images/minimal00per/xdripSSlog.png differ diff --git a/docs/CROWDIN/es/images/minimal00per/xdripSStat.png b/docs/CROWDIN/es/images/minimal00per/xdripSStat.png index 77fac8ebc0cd..1e77e9229cd2 100644 Binary files a/docs/CROWDIN/es/images/minimal00per/xdripSStat.png and b/docs/CROWDIN/es/images/minimal00per/xdripSStat.png differ diff --git a/docs/CROWDIN/fr/CompatibleCgms/Libre2MinimalL00per.md b/docs/CROWDIN/fr/CompatibleCgms/Libre2MinimalL00per.md index c3fb6a8bb95e..911f4e905135 100644 --- a/docs/CROWDIN/fr/CompatibleCgms/Libre2MinimalL00per.md +++ b/docs/CROWDIN/fr/CompatibleCgms/Libre2MinimalL00per.md @@ -292,31 +292,24 @@ Press the Hamburger menu in the upper left of the xDrip+ Overview screen and sel On the **BT Device** (swipe left) screen you can verify further connection details of the sensor as well as use this screen for troubleshooting connections. Below is a list of fields and their purposes to assist in connection troubleshooting. -*NOTE: **DO NOT click on Bluetooth Pairing** in this window as your sensor has already been paried or is in the middle of the pairing and bonding process. Doing so will attempt a direct pair and you will have to start the process from Step 5 all over again.* +*NOTE: **DO NOT TOUCH AND CHANGE Bluetooth Pairing from Disabled** in this window. Doing so will attempt a direct pair, it will fail (Not bonded) and you will have to start the process from Step 5 all over again.* -- **Phone Service State:** The last time the phone made a BT connection to the sensor +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) +- **Phone Service State:** The last time the phone made a BT connection to the sensor (it should be less than 5 minutes ago) - **Bluetooth Device:** Displays current status of the connection (either **Connected** or **Disconnected**) - -- **Active device connection:** Displays the status of the bluetooth bond after connection. **True** means the sensor is connected and bonded. - - **Device Mac Address**: This is the hardware ID of the sensor +- **Bluetooth Pairing**: This should be **Disabled, tap to enable**. Be careful to NOT tap this. If you tap it by mistake, tap it again until it returns to disabled. +- **Slowest wake up**: You can ignore this. xDrip+ doesn't spend its time waiting for readings: it will start expecting them at after a certain time (traditionally 5 minutes). If no data arrives at that time, you'll see "Woke up early" meaning xDrip+ was expecting data to be ready but there's none. Slowest wake up is the highest delay encountered before receiving data normally. +- **Next Wake up**: Should say 5 minutes -- **GATT device connected:** This is the hardware ID registered in the Android BT service. Any bluetooth devices actively bonded to your phone will display their hardware ID here. The GATT and Device Address should match for your sensor hardware ID. - -- **Request Data:** Only shown with Engineering Mode enabled in xDrip+. Pressing **Test for xBridgePlus protocol** you can manually start a request for data from your sensor. - -- **Received Data:** This is a hexadecimal representation of the data stream coming from your sensor. If you see characters here then you are actively receiving data from the sensor. The data should change after pressing **Test for xBridgePlus protocol**. - -- **Send Data:** This is the data request hexadecimal stream sent to the sensor to start data retrieval. After pressing **Test for xBridgePlus protocol** you should see this field update however, the data may not change a the request is the same each time. - - ![xDrip+ scan](../images/minimal00per/xdripSStat.png) +![xDrip+ scan](../images/minimal00per/xdripSStat.png) (minimallooper-notes)= ### **Notes** -- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (ie. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to rebond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. +- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (i.e. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to re-bond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. - - **What is going on?** When a Bluetooth connection is made a private shared key is created that is needed to allow communication between the sensor and the calling application/device. There is a high probability that the LL app or the Reader creates a new private shared key for communication during the connection. This means that after bonding, xDrip+ is not aware of the new key and will not be able to communicate with the sensor. @@ -459,6 +452,9 @@ Make sure you are running the latest versions of xDrip+ and OOP2. - Verify OOP2 is not put to sleep by the phone battery savings apps and settings - Verify Google Play protect is disabled as it will kill OOP2 +- Did you change Bluetooth Pairing in System Status? Touch it back to bring it back to **Disabled** + +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) #### Missed readings diff --git a/docs/CROWDIN/fr/images/minimal00per/xdripSSbond.png b/docs/CROWDIN/fr/images/minimal00per/xdripSSbond.png new file mode 100644 index 000000000000..8a222fc80895 Binary files /dev/null and b/docs/CROWDIN/fr/images/minimal00per/xdripSSbond.png differ diff --git a/docs/CROWDIN/fr/images/minimal00per/xdripSSlog.png b/docs/CROWDIN/fr/images/minimal00per/xdripSSlog.png index cb1fac206823..9edaa3f2bb48 100644 Binary files a/docs/CROWDIN/fr/images/minimal00per/xdripSSlog.png and b/docs/CROWDIN/fr/images/minimal00per/xdripSSlog.png differ diff --git a/docs/CROWDIN/fr/images/minimal00per/xdripSStat.png b/docs/CROWDIN/fr/images/minimal00per/xdripSStat.png index 77fac8ebc0cd..1e77e9229cd2 100644 Binary files a/docs/CROWDIN/fr/images/minimal00per/xdripSStat.png and b/docs/CROWDIN/fr/images/minimal00per/xdripSStat.png differ diff --git a/docs/CROWDIN/he/CompatibleCgms/Libre2MinimalL00per.md b/docs/CROWDIN/he/CompatibleCgms/Libre2MinimalL00per.md index 0971961a586d..8adc7a11aa8d 100644 --- a/docs/CROWDIN/he/CompatibleCgms/Libre2MinimalL00per.md +++ b/docs/CROWDIN/he/CompatibleCgms/Libre2MinimalL00per.md @@ -292,31 +292,24 @@ Press the Hamburger menu in the upper left of the xDrip+ Overview screen and sel On the **BT Device** (swipe left) screen you can verify further connection details of the sensor as well as use this screen for troubleshooting connections. Below is a list of fields and their purposes to assist in connection troubleshooting. -*NOTE: **DO NOT click on Bluetooth Pairing** in this window as your sensor has already been paried or is in the middle of the pairing and bonding process. Doing so will attempt a direct pair and you will have to start the process from Step 5 all over again.* +*NOTE: **DO NOT TOUCH AND CHANGE Bluetooth Pairing from Disabled** in this window. Doing so will attempt a direct pair, it will fail (Not bonded) and you will have to start the process from Step 5 all over again.* -- **Phone Service State:** The last time the phone made a BT connection to the sensor +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) +- **Phone Service State:** The last time the phone made a BT connection to the sensor (it should be less than 5 minutes ago) - **Bluetooth Device:** Displays current status of the connection (either **Connected** or **Disconnected**) - -- **Active device connection:** Displays the status of the bluetooth bond after connection. **True** means the sensor is connected and bonded. - - **Device Mac Address**: This is the hardware ID of the sensor +- **Bluetooth Pairing**: This should be **Disabled, tap to enable**. Be careful to NOT tap this. If you tap it by mistake, tap it again until it returns to disabled. +- **Slowest wake up**: You can ignore this. xDrip+ doesn't spend its time waiting for readings: it will start expecting them at after a certain time (traditionally 5 minutes). If no data arrives at that time, you'll see "Woke up early" meaning xDrip+ was expecting data to be ready but there's none. Slowest wake up is the highest delay encountered before receiving data normally. +- **Next Wake up**: Should say 5 minutes -- **GATT device connected:** This is the hardware ID registered in the Android BT service. Any bluetooth devices actively bonded to your phone will display their hardware ID here. The GATT and Device Address should match for your sensor hardware ID. - -- **Request Data:** Only shown with Engineering Mode enabled in xDrip+. Pressing **Test for xBridgePlus protocol** you can manually start a request for data from your sensor. - -- **Received Data:** This is a hexadecimal representation of the data stream coming from your sensor. If you see characters here then you are actively receiving data from the sensor. The data should change after pressing **Test for xBridgePlus protocol**. - -- **Send Data:** This is the data request hexadecimal stream sent to the sensor to start data retrieval. After pressing **Test for xBridgePlus protocol** you should see this field update however, the data may not change a the request is the same each time. - - ![xDrip+ scan](../images/minimal00per/xdripSStat.png) +![xDrip+ scan](../images/minimal00per/xdripSStat.png) (minimallooper-notes)= ### **Notes** -- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (ie. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to rebond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. +- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (i.e. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to re-bond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. - - **What is going on?** When a Bluetooth connection is made a private shared key is created that is needed to allow communication between the sensor and the calling application/device. There is a high probability that the LL app or the Reader creates a new private shared key for communication during the connection. This means that after bonding, xDrip+ is not aware of the new key and will not be able to communicate with the sensor. @@ -459,6 +452,9 @@ Make sure you are running the latest versions of xDrip+ and OOP2. - Verify OOP2 is not put to sleep by the phone battery savings apps and settings - Verify Google Play protect is disabled as it will kill OOP2 +- Did you change Bluetooth Pairing in System Status? Touch it back to bring it back to **Disabled** + +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) #### Missed readings diff --git a/docs/CROWDIN/he/images/minimal00per/xdripSSbond.png b/docs/CROWDIN/he/images/minimal00per/xdripSSbond.png new file mode 100644 index 000000000000..8a222fc80895 Binary files /dev/null and b/docs/CROWDIN/he/images/minimal00per/xdripSSbond.png differ diff --git a/docs/CROWDIN/he/images/minimal00per/xdripSSlog.png b/docs/CROWDIN/he/images/minimal00per/xdripSSlog.png index cb1fac206823..9edaa3f2bb48 100644 Binary files a/docs/CROWDIN/he/images/minimal00per/xdripSSlog.png and b/docs/CROWDIN/he/images/minimal00per/xdripSSlog.png differ diff --git a/docs/CROWDIN/he/images/minimal00per/xdripSStat.png b/docs/CROWDIN/he/images/minimal00per/xdripSStat.png index 77fac8ebc0cd..1e77e9229cd2 100644 Binary files a/docs/CROWDIN/he/images/minimal00per/xdripSStat.png and b/docs/CROWDIN/he/images/minimal00per/xdripSStat.png differ diff --git a/docs/CROWDIN/ko/CompatibleCgms/Libre2MinimalL00per.md b/docs/CROWDIN/ko/CompatibleCgms/Libre2MinimalL00per.md index 567ff3a1ffad..dc51b4146ffc 100644 --- a/docs/CROWDIN/ko/CompatibleCgms/Libre2MinimalL00per.md +++ b/docs/CROWDIN/ko/CompatibleCgms/Libre2MinimalL00per.md @@ -292,31 +292,24 @@ Press the Hamburger menu in the upper left of the xDrip+ Overview screen and sel On the **BT Device** (swipe left) screen you can verify further connection details of the sensor as well as use this screen for troubleshooting connections. Below is a list of fields and their purposes to assist in connection troubleshooting. -*NOTE: **DO NOT click on Bluetooth Pairing** in this window as your sensor has already been paried or is in the middle of the pairing and bonding process. Doing so will attempt a direct pair and you will have to start the process from Step 5 all over again.* +*NOTE: **DO NOT TOUCH AND CHANGE Bluetooth Pairing from Disabled** in this window. Doing so will attempt a direct pair, it will fail (Not bonded) and you will have to start the process from Step 5 all over again.* -- **Phone Service State:** The last time the phone made a BT connection to the sensor +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) +- **Phone Service State:** The last time the phone made a BT connection to the sensor (it should be less than 5 minutes ago) - **Bluetooth Device:** Displays current status of the connection (either **Connected** or **Disconnected**) - -- **Active device connection:** Displays the status of the bluetooth bond after connection. **True** means the sensor is connected and bonded. - - **Device Mac Address**: This is the hardware ID of the sensor +- **Bluetooth Pairing**: This should be **Disabled, tap to enable**. Be careful to NOT tap this. If you tap it by mistake, tap it again until it returns to disabled. +- **Slowest wake up**: You can ignore this. xDrip+ doesn't spend its time waiting for readings: it will start expecting them at after a certain time (traditionally 5 minutes). If no data arrives at that time, you'll see "Woke up early" meaning xDrip+ was expecting data to be ready but there's none. Slowest wake up is the highest delay encountered before receiving data normally. +- **Next Wake up**: Should say 5 minutes -- **GATT device connected:** This is the hardware ID registered in the Android BT service. Any bluetooth devices actively bonded to your phone will display their hardware ID here. The GATT and Device Address should match for your sensor hardware ID. - -- **Request Data:** Only shown with Engineering Mode enabled in xDrip+. Pressing **Test for xBridgePlus protocol** you can manually start a request for data from your sensor. - -- **Received Data:** This is a hexadecimal representation of the data stream coming from your sensor. If you see characters here then you are actively receiving data from the sensor. The data should change after pressing **Test for xBridgePlus protocol**. - -- **Send Data:** This is the data request hexadecimal stream sent to the sensor to start data retrieval. After pressing **Test for xBridgePlus protocol** you should see this field update however, the data may not change a the request is the same each time. - - ![xDrip+ scan](../images/minimal00per/xdripSStat.png) +![xDrip+ scan](../images/minimal00per/xdripSStat.png) (minimallooper-notes)= ### **Notes** -- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (ie. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to rebond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. +- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (i.e. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to re-bond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. - - **What is going on?** When a Bluetooth connection is made a private shared key is created that is needed to allow communication between the sensor and the calling application/device. There is a high probability that the LL app or the Reader creates a new private shared key for communication during the connection. This means that after bonding, xDrip+ is not aware of the new key and will not be able to communicate with the sensor. @@ -459,6 +452,9 @@ Make sure you are running the latest versions of xDrip+ and OOP2. - Verify OOP2 is not put to sleep by the phone battery savings apps and settings - Verify Google Play protect is disabled as it will kill OOP2 +- Did you change Bluetooth Pairing in System Status? Touch it back to bring it back to **Disabled** + +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) #### Missed readings diff --git a/docs/CROWDIN/ko/images/minimal00per/xdripSSbond.png b/docs/CROWDIN/ko/images/minimal00per/xdripSSbond.png new file mode 100644 index 000000000000..8a222fc80895 Binary files /dev/null and b/docs/CROWDIN/ko/images/minimal00per/xdripSSbond.png differ diff --git a/docs/CROWDIN/ko/images/minimal00per/xdripSSlog.png b/docs/CROWDIN/ko/images/minimal00per/xdripSSlog.png index cb1fac206823..9edaa3f2bb48 100644 Binary files a/docs/CROWDIN/ko/images/minimal00per/xdripSSlog.png and b/docs/CROWDIN/ko/images/minimal00per/xdripSSlog.png differ diff --git a/docs/CROWDIN/ko/images/minimal00per/xdripSStat.png b/docs/CROWDIN/ko/images/minimal00per/xdripSStat.png index 77fac8ebc0cd..1e77e9229cd2 100644 Binary files a/docs/CROWDIN/ko/images/minimal00per/xdripSStat.png and b/docs/CROWDIN/ko/images/minimal00per/xdripSStat.png differ diff --git a/docs/CROWDIN/lt/CompatibleCgms/Libre2MinimalL00per.md b/docs/CROWDIN/lt/CompatibleCgms/Libre2MinimalL00per.md index d4d38de632d5..d2d5eb011ccf 100644 --- a/docs/CROWDIN/lt/CompatibleCgms/Libre2MinimalL00per.md +++ b/docs/CROWDIN/lt/CompatibleCgms/Libre2MinimalL00per.md @@ -292,31 +292,24 @@ Press the Hamburger menu in the upper left of the xDrip+ Overview screen and sel On the **BT Device** (swipe left) screen you can verify further connection details of the sensor as well as use this screen for troubleshooting connections. Below is a list of fields and their purposes to assist in connection troubleshooting. -*NOTE: **DO NOT click on Bluetooth Pairing** in this window as your sensor has already been paried or is in the middle of the pairing and bonding process. Doing so will attempt a direct pair and you will have to start the process from Step 5 all over again.* +*NOTE: **DO NOT TOUCH AND CHANGE Bluetooth Pairing from Disabled** in this window. Doing so will attempt a direct pair, it will fail (Not bonded) and you will have to start the process from Step 5 all over again.* -- **Phone Service State:** The last time the phone made a BT connection to the sensor +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) +- **Phone Service State:** The last time the phone made a BT connection to the sensor (it should be less than 5 minutes ago) - **Bluetooth Device:** Displays current status of the connection (either **Connected** or **Disconnected**) - -- **Active device connection:** Displays the status of the bluetooth bond after connection. **True** means the sensor is connected and bonded. - - **Device Mac Address**: This is the hardware ID of the sensor +- **Bluetooth Pairing**: This should be **Disabled, tap to enable**. Be careful to NOT tap this. If you tap it by mistake, tap it again until it returns to disabled. +- **Slowest wake up**: You can ignore this. xDrip+ doesn't spend its time waiting for readings: it will start expecting them at after a certain time (traditionally 5 minutes). If no data arrives at that time, you'll see "Woke up early" meaning xDrip+ was expecting data to be ready but there's none. Slowest wake up is the highest delay encountered before receiving data normally. +- **Next Wake up**: Should say 5 minutes -- **GATT device connected:** This is the hardware ID registered in the Android BT service. Any bluetooth devices actively bonded to your phone will display their hardware ID here. The GATT and Device Address should match for your sensor hardware ID. - -- **Request Data:** Only shown with Engineering Mode enabled in xDrip+. Pressing **Test for xBridgePlus protocol** you can manually start a request for data from your sensor. - -- **Received Data:** This is a hexadecimal representation of the data stream coming from your sensor. If you see characters here then you are actively receiving data from the sensor. The data should change after pressing **Test for xBridgePlus protocol**. - -- **Send Data:** This is the data request hexadecimal stream sent to the sensor to start data retrieval. After pressing **Test for xBridgePlus protocol** you should see this field update however, the data may not change a the request is the same each time. - - ![xDrip+ scan](../images/minimal00per/xdripSStat.png) +![xDrip+ scan](../images/minimal00per/xdripSStat.png) (minimallooper-notes)= ### **Notes** -- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (ie. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to rebond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. +- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (i.e. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to re-bond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. - - **What is going on?** When a Bluetooth connection is made a private shared key is created that is needed to allow communication between the sensor and the calling application/device. There is a high probability that the LL app or the Reader creates a new private shared key for communication during the connection. This means that after bonding, xDrip+ is not aware of the new key and will not be able to communicate with the sensor. @@ -459,6 +452,9 @@ Make sure you are running the latest versions of xDrip+ and OOP2. - Verify OOP2 is not put to sleep by the phone battery savings apps and settings - Verify Google Play protect is disabled as it will kill OOP2 +- Did you change Bluetooth Pairing in System Status? Touch it back to bring it back to **Disabled** + +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) #### Missed readings diff --git a/docs/CROWDIN/lt/images/minimal00per/xdripSSbond.png b/docs/CROWDIN/lt/images/minimal00per/xdripSSbond.png new file mode 100644 index 000000000000..8a222fc80895 Binary files /dev/null and b/docs/CROWDIN/lt/images/minimal00per/xdripSSbond.png differ diff --git a/docs/CROWDIN/lt/images/minimal00per/xdripSSlog.png b/docs/CROWDIN/lt/images/minimal00per/xdripSSlog.png index cb1fac206823..9edaa3f2bb48 100644 Binary files a/docs/CROWDIN/lt/images/minimal00per/xdripSSlog.png and b/docs/CROWDIN/lt/images/minimal00per/xdripSSlog.png differ diff --git a/docs/CROWDIN/lt/images/minimal00per/xdripSStat.png b/docs/CROWDIN/lt/images/minimal00per/xdripSStat.png index 77fac8ebc0cd..1e77e9229cd2 100644 Binary files a/docs/CROWDIN/lt/images/minimal00per/xdripSStat.png and b/docs/CROWDIN/lt/images/minimal00per/xdripSStat.png differ diff --git a/docs/CROWDIN/nl/CompatibleCgms/Libre2MinimalL00per.md b/docs/CROWDIN/nl/CompatibleCgms/Libre2MinimalL00per.md index 3ee104cec5a6..25a85e331ad6 100644 --- a/docs/CROWDIN/nl/CompatibleCgms/Libre2MinimalL00per.md +++ b/docs/CROWDIN/nl/CompatibleCgms/Libre2MinimalL00per.md @@ -292,31 +292,24 @@ Press the Hamburger menu in the upper left of the xDrip+ Overview screen and sel On the **BT Device** (swipe left) screen you can verify further connection details of the sensor as well as use this screen for troubleshooting connections. Below is a list of fields and their purposes to assist in connection troubleshooting. -*NOTE: **DO NOT click on Bluetooth Pairing** in this window as your sensor has already been paried or is in the middle of the pairing and bonding process. Doing so will attempt a direct pair and you will have to start the process from Step 5 all over again.* +*NOTE: **DO NOT TOUCH AND CHANGE Bluetooth Pairing from Disabled** in this window. Doing so will attempt a direct pair, it will fail (Not bonded) and you will have to start the process from Step 5 all over again.* -- **Phone Service State:** The last time the phone made a BT connection to the sensor +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) +- **Phone Service State:** The last time the phone made a BT connection to the sensor (it should be less than 5 minutes ago) - **Bluetooth Device:** Displays current status of the connection (either **Connected** or **Disconnected**) - -- **Active device connection:** Displays the status of the bluetooth bond after connection. **True** means the sensor is connected and bonded. - - **Device Mac Address**: This is the hardware ID of the sensor +- **Bluetooth Pairing**: This should be **Disabled, tap to enable**. Be careful to NOT tap this. If you tap it by mistake, tap it again until it returns to disabled. +- **Slowest wake up**: You can ignore this. xDrip+ doesn't spend its time waiting for readings: it will start expecting them at after a certain time (traditionally 5 minutes). If no data arrives at that time, you'll see "Woke up early" meaning xDrip+ was expecting data to be ready but there's none. Slowest wake up is the highest delay encountered before receiving data normally. +- **Next Wake up**: Should say 5 minutes -- **GATT device connected:** This is the hardware ID registered in the Android BT service. Any bluetooth devices actively bonded to your phone will display their hardware ID here. The GATT and Device Address should match for your sensor hardware ID. - -- **Request Data:** Only shown with Engineering Mode enabled in xDrip+. Pressing **Test for xBridgePlus protocol** you can manually start a request for data from your sensor. - -- **Received Data:** This is a hexadecimal representation of the data stream coming from your sensor. If you see characters here then you are actively receiving data from the sensor. The data should change after pressing **Test for xBridgePlus protocol**. - -- **Send Data:** This is the data request hexadecimal stream sent to the sensor to start data retrieval. After pressing **Test for xBridgePlus protocol** you should see this field update however, the data may not change a the request is the same each time. - - ![xDrip+ scan](../images/minimal00per/xdripSStat.png) +![xDrip+ scan](../images/minimal00per/xdripSStat.png) (minimallooper-notes)= ### **Notes** -- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (ie. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to rebond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. +- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (i.e. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to re-bond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. - - **What is going on?** When a Bluetooth connection is made a private shared key is created that is needed to allow communication between the sensor and the calling application/device. There is a high probability that the LL app or the Reader creates a new private shared key for communication during the connection. This means that after bonding, xDrip+ is not aware of the new key and will not be able to communicate with the sensor. @@ -459,6 +452,9 @@ Make sure you are running the latest versions of xDrip+ and OOP2. - Verify OOP2 is not put to sleep by the phone battery savings apps and settings - Verify Google Play protect is disabled as it will kill OOP2 +- Did you change Bluetooth Pairing in System Status? Touch it back to bring it back to **Disabled** + +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) #### Missed readings diff --git a/docs/CROWDIN/nl/images/minimal00per/xdripSSbond.png b/docs/CROWDIN/nl/images/minimal00per/xdripSSbond.png new file mode 100644 index 000000000000..8a222fc80895 Binary files /dev/null and b/docs/CROWDIN/nl/images/minimal00per/xdripSSbond.png differ diff --git a/docs/CROWDIN/nl/images/minimal00per/xdripSSlog.png b/docs/CROWDIN/nl/images/minimal00per/xdripSSlog.png index cb1fac206823..9edaa3f2bb48 100644 Binary files a/docs/CROWDIN/nl/images/minimal00per/xdripSSlog.png and b/docs/CROWDIN/nl/images/minimal00per/xdripSSlog.png differ diff --git a/docs/CROWDIN/nl/images/minimal00per/xdripSStat.png b/docs/CROWDIN/nl/images/minimal00per/xdripSStat.png index 77fac8ebc0cd..1e77e9229cd2 100644 Binary files a/docs/CROWDIN/nl/images/minimal00per/xdripSStat.png and b/docs/CROWDIN/nl/images/minimal00per/xdripSStat.png differ diff --git a/docs/CROWDIN/pb/CompatibleCgms/Libre2MinimalL00per.md b/docs/CROWDIN/pb/CompatibleCgms/Libre2MinimalL00per.md index 567ff3a1ffad..dc51b4146ffc 100644 --- a/docs/CROWDIN/pb/CompatibleCgms/Libre2MinimalL00per.md +++ b/docs/CROWDIN/pb/CompatibleCgms/Libre2MinimalL00per.md @@ -292,31 +292,24 @@ Press the Hamburger menu in the upper left of the xDrip+ Overview screen and sel On the **BT Device** (swipe left) screen you can verify further connection details of the sensor as well as use this screen for troubleshooting connections. Below is a list of fields and their purposes to assist in connection troubleshooting. -*NOTE: **DO NOT click on Bluetooth Pairing** in this window as your sensor has already been paried or is in the middle of the pairing and bonding process. Doing so will attempt a direct pair and you will have to start the process from Step 5 all over again.* +*NOTE: **DO NOT TOUCH AND CHANGE Bluetooth Pairing from Disabled** in this window. Doing so will attempt a direct pair, it will fail (Not bonded) and you will have to start the process from Step 5 all over again.* -- **Phone Service State:** The last time the phone made a BT connection to the sensor +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) +- **Phone Service State:** The last time the phone made a BT connection to the sensor (it should be less than 5 minutes ago) - **Bluetooth Device:** Displays current status of the connection (either **Connected** or **Disconnected**) - -- **Active device connection:** Displays the status of the bluetooth bond after connection. **True** means the sensor is connected and bonded. - - **Device Mac Address**: This is the hardware ID of the sensor +- **Bluetooth Pairing**: This should be **Disabled, tap to enable**. Be careful to NOT tap this. If you tap it by mistake, tap it again until it returns to disabled. +- **Slowest wake up**: You can ignore this. xDrip+ doesn't spend its time waiting for readings: it will start expecting them at after a certain time (traditionally 5 minutes). If no data arrives at that time, you'll see "Woke up early" meaning xDrip+ was expecting data to be ready but there's none. Slowest wake up is the highest delay encountered before receiving data normally. +- **Next Wake up**: Should say 5 minutes -- **GATT device connected:** This is the hardware ID registered in the Android BT service. Any bluetooth devices actively bonded to your phone will display their hardware ID here. The GATT and Device Address should match for your sensor hardware ID. - -- **Request Data:** Only shown with Engineering Mode enabled in xDrip+. Pressing **Test for xBridgePlus protocol** you can manually start a request for data from your sensor. - -- **Received Data:** This is a hexadecimal representation of the data stream coming from your sensor. If you see characters here then you are actively receiving data from the sensor. The data should change after pressing **Test for xBridgePlus protocol**. - -- **Send Data:** This is the data request hexadecimal stream sent to the sensor to start data retrieval. After pressing **Test for xBridgePlus protocol** you should see this field update however, the data may not change a the request is the same each time. - - ![xDrip+ scan](../images/minimal00per/xdripSStat.png) +![xDrip+ scan](../images/minimal00per/xdripSStat.png) (minimallooper-notes)= ### **Notes** -- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (ie. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to rebond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. +- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (i.e. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to re-bond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. - - **What is going on?** When a Bluetooth connection is made a private shared key is created that is needed to allow communication between the sensor and the calling application/device. There is a high probability that the LL app or the Reader creates a new private shared key for communication during the connection. This means that after bonding, xDrip+ is not aware of the new key and will not be able to communicate with the sensor. @@ -459,6 +452,9 @@ Make sure you are running the latest versions of xDrip+ and OOP2. - Verify OOP2 is not put to sleep by the phone battery savings apps and settings - Verify Google Play protect is disabled as it will kill OOP2 +- Did you change Bluetooth Pairing in System Status? Touch it back to bring it back to **Disabled** + +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) #### Missed readings diff --git a/docs/CROWDIN/pb/images/minimal00per/xdripSSbond.png b/docs/CROWDIN/pb/images/minimal00per/xdripSSbond.png new file mode 100644 index 000000000000..8a222fc80895 Binary files /dev/null and b/docs/CROWDIN/pb/images/minimal00per/xdripSSbond.png differ diff --git a/docs/CROWDIN/pb/images/minimal00per/xdripSSlog.png b/docs/CROWDIN/pb/images/minimal00per/xdripSSlog.png index cb1fac206823..9edaa3f2bb48 100644 Binary files a/docs/CROWDIN/pb/images/minimal00per/xdripSSlog.png and b/docs/CROWDIN/pb/images/minimal00per/xdripSSlog.png differ diff --git a/docs/CROWDIN/pb/images/minimal00per/xdripSStat.png b/docs/CROWDIN/pb/images/minimal00per/xdripSStat.png index 77fac8ebc0cd..1e77e9229cd2 100644 Binary files a/docs/CROWDIN/pb/images/minimal00per/xdripSStat.png and b/docs/CROWDIN/pb/images/minimal00per/xdripSStat.png differ diff --git a/docs/CROWDIN/pl/CompatibleCgms/Libre2MinimalL00per.md b/docs/CROWDIN/pl/CompatibleCgms/Libre2MinimalL00per.md index 567ff3a1ffad..dc51b4146ffc 100644 --- a/docs/CROWDIN/pl/CompatibleCgms/Libre2MinimalL00per.md +++ b/docs/CROWDIN/pl/CompatibleCgms/Libre2MinimalL00per.md @@ -292,31 +292,24 @@ Press the Hamburger menu in the upper left of the xDrip+ Overview screen and sel On the **BT Device** (swipe left) screen you can verify further connection details of the sensor as well as use this screen for troubleshooting connections. Below is a list of fields and their purposes to assist in connection troubleshooting. -*NOTE: **DO NOT click on Bluetooth Pairing** in this window as your sensor has already been paried or is in the middle of the pairing and bonding process. Doing so will attempt a direct pair and you will have to start the process from Step 5 all over again.* +*NOTE: **DO NOT TOUCH AND CHANGE Bluetooth Pairing from Disabled** in this window. Doing so will attempt a direct pair, it will fail (Not bonded) and you will have to start the process from Step 5 all over again.* -- **Phone Service State:** The last time the phone made a BT connection to the sensor +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) +- **Phone Service State:** The last time the phone made a BT connection to the sensor (it should be less than 5 minutes ago) - **Bluetooth Device:** Displays current status of the connection (either **Connected** or **Disconnected**) - -- **Active device connection:** Displays the status of the bluetooth bond after connection. **True** means the sensor is connected and bonded. - - **Device Mac Address**: This is the hardware ID of the sensor +- **Bluetooth Pairing**: This should be **Disabled, tap to enable**. Be careful to NOT tap this. If you tap it by mistake, tap it again until it returns to disabled. +- **Slowest wake up**: You can ignore this. xDrip+ doesn't spend its time waiting for readings: it will start expecting them at after a certain time (traditionally 5 minutes). If no data arrives at that time, you'll see "Woke up early" meaning xDrip+ was expecting data to be ready but there's none. Slowest wake up is the highest delay encountered before receiving data normally. +- **Next Wake up**: Should say 5 minutes -- **GATT device connected:** This is the hardware ID registered in the Android BT service. Any bluetooth devices actively bonded to your phone will display their hardware ID here. The GATT and Device Address should match for your sensor hardware ID. - -- **Request Data:** Only shown with Engineering Mode enabled in xDrip+. Pressing **Test for xBridgePlus protocol** you can manually start a request for data from your sensor. - -- **Received Data:** This is a hexadecimal representation of the data stream coming from your sensor. If you see characters here then you are actively receiving data from the sensor. The data should change after pressing **Test for xBridgePlus protocol**. - -- **Send Data:** This is the data request hexadecimal stream sent to the sensor to start data retrieval. After pressing **Test for xBridgePlus protocol** you should see this field update however, the data may not change a the request is the same each time. - - ![xDrip+ scan](../images/minimal00per/xdripSStat.png) +![xDrip+ scan](../images/minimal00per/xdripSStat.png) (minimallooper-notes)= ### **Notes** -- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (ie. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to rebond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. +- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (i.e. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to re-bond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. - - **What is going on?** When a Bluetooth connection is made a private shared key is created that is needed to allow communication between the sensor and the calling application/device. There is a high probability that the LL app or the Reader creates a new private shared key for communication during the connection. This means that after bonding, xDrip+ is not aware of the new key and will not be able to communicate with the sensor. @@ -459,6 +452,9 @@ Make sure you are running the latest versions of xDrip+ and OOP2. - Verify OOP2 is not put to sleep by the phone battery savings apps and settings - Verify Google Play protect is disabled as it will kill OOP2 +- Did you change Bluetooth Pairing in System Status? Touch it back to bring it back to **Disabled** + +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) #### Missed readings diff --git a/docs/CROWDIN/pl/images/minimal00per/xdripSSbond.png b/docs/CROWDIN/pl/images/minimal00per/xdripSSbond.png new file mode 100644 index 000000000000..8a222fc80895 Binary files /dev/null and b/docs/CROWDIN/pl/images/minimal00per/xdripSSbond.png differ diff --git a/docs/CROWDIN/pl/images/minimal00per/xdripSSlog.png b/docs/CROWDIN/pl/images/minimal00per/xdripSSlog.png index cb1fac206823..9edaa3f2bb48 100644 Binary files a/docs/CROWDIN/pl/images/minimal00per/xdripSSlog.png and b/docs/CROWDIN/pl/images/minimal00per/xdripSSlog.png differ diff --git a/docs/CROWDIN/pl/images/minimal00per/xdripSStat.png b/docs/CROWDIN/pl/images/minimal00per/xdripSStat.png index 77fac8ebc0cd..1e77e9229cd2 100644 Binary files a/docs/CROWDIN/pl/images/minimal00per/xdripSStat.png and b/docs/CROWDIN/pl/images/minimal00per/xdripSStat.png differ diff --git a/docs/CROWDIN/pt/CompatibleCgms/Libre2MinimalL00per.md b/docs/CROWDIN/pt/CompatibleCgms/Libre2MinimalL00per.md index 2ca777b4223e..ab8114170c0d 100644 --- a/docs/CROWDIN/pt/CompatibleCgms/Libre2MinimalL00per.md +++ b/docs/CROWDIN/pt/CompatibleCgms/Libre2MinimalL00per.md @@ -292,31 +292,24 @@ Press the Hamburger menu in the upper left of the xDrip+ Overview screen and sel On the **BT Device** (swipe left) screen you can verify further connection details of the sensor as well as use this screen for troubleshooting connections. Below is a list of fields and their purposes to assist in connection troubleshooting. -*NOTE: **DO NOT click on Bluetooth Pairing** in this window as your sensor has already been paried or is in the middle of the pairing and bonding process. Doing so will attempt a direct pair and you will have to start the process from Step 5 all over again.* +*NOTE: **DO NOT TOUCH AND CHANGE Bluetooth Pairing from Disabled** in this window. Doing so will attempt a direct pair, it will fail (Not bonded) and you will have to start the process from Step 5 all over again.* -- **Phone Service State:** The last time the phone made a BT connection to the sensor +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) +- **Phone Service State:** The last time the phone made a BT connection to the sensor (it should be less than 5 minutes ago) - **Bluetooth Device:** Displays current status of the connection (either **Connected** or **Disconnected**) - -- **Active device connection:** Displays the status of the bluetooth bond after connection. **True** means the sensor is connected and bonded. - - **Device Mac Address**: This is the hardware ID of the sensor +- **Bluetooth Pairing**: This should be **Disabled, tap to enable**. Be careful to NOT tap this. If you tap it by mistake, tap it again until it returns to disabled. +- **Slowest wake up**: You can ignore this. xDrip+ doesn't spend its time waiting for readings: it will start expecting them at after a certain time (traditionally 5 minutes). If no data arrives at that time, you'll see "Woke up early" meaning xDrip+ was expecting data to be ready but there's none. Slowest wake up is the highest delay encountered before receiving data normally. +- **Next Wake up**: Should say 5 minutes -- **GATT device connected:** This is the hardware ID registered in the Android BT service. Any bluetooth devices actively bonded to your phone will display their hardware ID here. The GATT and Device Address should match for your sensor hardware ID. - -- **Request Data:** Only shown with Engineering Mode enabled in xDrip+. Pressing **Test for xBridgePlus protocol** you can manually start a request for data from your sensor. - -- **Received Data:** This is a hexadecimal representation of the data stream coming from your sensor. If you see characters here then you are actively receiving data from the sensor. The data should change after pressing **Test for xBridgePlus protocol**. - -- **Send Data:** This is the data request hexadecimal stream sent to the sensor to start data retrieval. After pressing **Test for xBridgePlus protocol** you should see this field update however, the data may not change a the request is the same each time. - - ![xDrip+ scan](../images/minimal00per/xdripSStat.png) +![xDrip+ scan](../images/minimal00per/xdripSStat.png) (minimallooper-notes)= ### **Notes** -- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (ie. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to rebond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. +- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (i.e. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to re-bond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. - - **What is going on?** When a Bluetooth connection is made a private shared key is created that is needed to allow communication between the sensor and the calling application/device. There is a high probability that the LL app or the Reader creates a new private shared key for communication during the connection. This means that after bonding, xDrip+ is not aware of the new key and will not be able to communicate with the sensor. @@ -459,6 +452,9 @@ Make sure you are running the latest versions of xDrip+ and OOP2. - Verify OOP2 is not put to sleep by the phone battery savings apps and settings - Verify Google Play protect is disabled as it will kill OOP2 +- Did you change Bluetooth Pairing in System Status? Touch it back to bring it back to **Disabled** + +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) #### Missed readings diff --git a/docs/CROWDIN/pt/images/minimal00per/xdripSSbond.png b/docs/CROWDIN/pt/images/minimal00per/xdripSSbond.png new file mode 100644 index 000000000000..8a222fc80895 Binary files /dev/null and b/docs/CROWDIN/pt/images/minimal00per/xdripSSbond.png differ diff --git a/docs/CROWDIN/pt/images/minimal00per/xdripSSlog.png b/docs/CROWDIN/pt/images/minimal00per/xdripSSlog.png index cb1fac206823..9edaa3f2bb48 100644 Binary files a/docs/CROWDIN/pt/images/minimal00per/xdripSSlog.png and b/docs/CROWDIN/pt/images/minimal00per/xdripSSlog.png differ diff --git a/docs/CROWDIN/pt/images/minimal00per/xdripSStat.png b/docs/CROWDIN/pt/images/minimal00per/xdripSStat.png index 77fac8ebc0cd..1e77e9229cd2 100644 Binary files a/docs/CROWDIN/pt/images/minimal00per/xdripSStat.png and b/docs/CROWDIN/pt/images/minimal00per/xdripSStat.png differ diff --git a/docs/CROWDIN/ro/CompatibleCgms/Libre2MinimalL00per.md b/docs/CROWDIN/ro/CompatibleCgms/Libre2MinimalL00per.md index 9b5634ca71a9..d0735305d6c1 100644 --- a/docs/CROWDIN/ro/CompatibleCgms/Libre2MinimalL00per.md +++ b/docs/CROWDIN/ro/CompatibleCgms/Libre2MinimalL00per.md @@ -292,31 +292,24 @@ Press the Hamburger menu in the upper left of the xDrip+ Overview screen and sel On the **BT Device** (swipe left) screen you can verify further connection details of the sensor as well as use this screen for troubleshooting connections. Below is a list of fields and their purposes to assist in connection troubleshooting. -*NOTE: **DO NOT click on Bluetooth Pairing** in this window as your sensor has already been paried or is in the middle of the pairing and bonding process. Doing so will attempt a direct pair and you will have to start the process from Step 5 all over again.* +*NOTE: **DO NOT TOUCH AND CHANGE Bluetooth Pairing from Disabled** in this window. Doing so will attempt a direct pair, it will fail (Not bonded) and you will have to start the process from Step 5 all over again.* -- **Phone Service State:** The last time the phone made a BT connection to the sensor +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) +- **Phone Service State:** The last time the phone made a BT connection to the sensor (it should be less than 5 minutes ago) - **Bluetooth Device:** Displays current status of the connection (either **Connected** or **Disconnected**) - -- **Active device connection:** Displays the status of the bluetooth bond after connection. **True** means the sensor is connected and bonded. - - **Device Mac Address**: This is the hardware ID of the sensor +- **Bluetooth Pairing**: This should be **Disabled, tap to enable**. Be careful to NOT tap this. If you tap it by mistake, tap it again until it returns to disabled. +- **Slowest wake up**: You can ignore this. xDrip+ doesn't spend its time waiting for readings: it will start expecting them at after a certain time (traditionally 5 minutes). If no data arrives at that time, you'll see "Woke up early" meaning xDrip+ was expecting data to be ready but there's none. Slowest wake up is the highest delay encountered before receiving data normally. +- **Next Wake up**: Should say 5 minutes -- **GATT device connected:** This is the hardware ID registered in the Android BT service. Any bluetooth devices actively bonded to your phone will display their hardware ID here. The GATT and Device Address should match for your sensor hardware ID. - -- **Request Data:** Only shown with Engineering Mode enabled in xDrip+. Pressing **Test for xBridgePlus protocol** you can manually start a request for data from your sensor. - -- **Received Data:** This is a hexadecimal representation of the data stream coming from your sensor. If you see characters here then you are actively receiving data from the sensor. The data should change after pressing **Test for xBridgePlus protocol**. - -- **Send Data:** This is the data request hexadecimal stream sent to the sensor to start data retrieval. After pressing **Test for xBridgePlus protocol** you should see this field update however, the data may not change a the request is the same each time. - - ![xDrip+ scan](../images/minimal00per/xdripSStat.png) +![xDrip+ scan](../images/minimal00per/xdripSStat.png) (minimallooper-notes)= ### **Notes** -- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (ie. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to rebond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. +- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (i.e. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to re-bond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. - - **What is going on?** When a Bluetooth connection is made a private shared key is created that is needed to allow communication between the sensor and the calling application/device. There is a high probability that the LL app or the Reader creates a new private shared key for communication during the connection. This means that after bonding, xDrip+ is not aware of the new key and will not be able to communicate with the sensor. @@ -459,6 +452,9 @@ Make sure you are running the latest versions of xDrip+ and OOP2. - Verify OOP2 is not put to sleep by the phone battery savings apps and settings - Verify Google Play protect is disabled as it will kill OOP2 +- Did you change Bluetooth Pairing in System Status? Touch it back to bring it back to **Disabled** + +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) #### Missed readings diff --git a/docs/CROWDIN/ro/images/minimal00per/xdripSSbond.png b/docs/CROWDIN/ro/images/minimal00per/xdripSSbond.png new file mode 100644 index 000000000000..8a222fc80895 Binary files /dev/null and b/docs/CROWDIN/ro/images/minimal00per/xdripSSbond.png differ diff --git a/docs/CROWDIN/ro/images/minimal00per/xdripSSlog.png b/docs/CROWDIN/ro/images/minimal00per/xdripSSlog.png index cb1fac206823..9edaa3f2bb48 100644 Binary files a/docs/CROWDIN/ro/images/minimal00per/xdripSSlog.png and b/docs/CROWDIN/ro/images/minimal00per/xdripSSlog.png differ diff --git a/docs/CROWDIN/ro/images/minimal00per/xdripSStat.png b/docs/CROWDIN/ro/images/minimal00per/xdripSStat.png index 77fac8ebc0cd..1e77e9229cd2 100644 Binary files a/docs/CROWDIN/ro/images/minimal00per/xdripSStat.png and b/docs/CROWDIN/ro/images/minimal00per/xdripSStat.png differ diff --git a/docs/CROWDIN/ru/CompatibleCgms/Libre2MinimalL00per.md b/docs/CROWDIN/ru/CompatibleCgms/Libre2MinimalL00per.md index f2f79f85b818..07f001cb13fa 100644 --- a/docs/CROWDIN/ru/CompatibleCgms/Libre2MinimalL00per.md +++ b/docs/CROWDIN/ru/CompatibleCgms/Libre2MinimalL00per.md @@ -292,31 +292,24 @@ Press the Hamburger menu in the upper left of the xDrip+ Overview screen and sel On the **BT Device** (swipe left) screen you can verify further connection details of the sensor as well as use this screen for troubleshooting connections. Below is a list of fields and their purposes to assist in connection troubleshooting. -*NOTE: **DO NOT click on Bluetooth Pairing** in this window as your sensor has already been paried or is in the middle of the pairing and bonding process. Doing so will attempt a direct pair and you will have to start the process from Step 5 all over again.* +*NOTE: **DO NOT TOUCH AND CHANGE Bluetooth Pairing from Disabled** in this window. Doing so will attempt a direct pair, it will fail (Not bonded) and you will have to start the process from Step 5 all over again.* -- **Phone Service State:** The last time the phone made a BT connection to the sensor +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) +- **Phone Service State:** The last time the phone made a BT connection to the sensor (it should be less than 5 minutes ago) - **Bluetooth Device:** Displays current status of the connection (either **Connected** or **Disconnected**) - -- **Active device connection:** Displays the status of the bluetooth bond after connection. **True** means the sensor is connected and bonded. - - **Device Mac Address**: This is the hardware ID of the sensor +- **Bluetooth Pairing**: This should be **Disabled, tap to enable**. Be careful to NOT tap this. If you tap it by mistake, tap it again until it returns to disabled. +- **Slowest wake up**: You can ignore this. xDrip+ doesn't spend its time waiting for readings: it will start expecting them at after a certain time (traditionally 5 minutes). If no data arrives at that time, you'll see "Woke up early" meaning xDrip+ was expecting data to be ready but there's none. Slowest wake up is the highest delay encountered before receiving data normally. +- **Next Wake up**: Should say 5 minutes -- **GATT device connected:** This is the hardware ID registered in the Android BT service. Any bluetooth devices actively bonded to your phone will display their hardware ID here. The GATT and Device Address should match for your sensor hardware ID. - -- **Request Data:** Only shown with Engineering Mode enabled in xDrip+. Pressing **Test for xBridgePlus protocol** you can manually start a request for data from your sensor. - -- **Received Data:** This is a hexadecimal representation of the data stream coming from your sensor. If you see characters here then you are actively receiving data from the sensor. The data should change after pressing **Test for xBridgePlus protocol**. - -- **Send Data:** This is the data request hexadecimal stream sent to the sensor to start data retrieval. After pressing **Test for xBridgePlus protocol** you should see this field update however, the data may not change a the request is the same each time. - - ![xDrip+ scan](../images/minimal00per/xdripSStat.png) +![xDrip+ scan](../images/minimal00per/xdripSStat.png) (minimallooper-notes)= ### **Notes** -- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (ie. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to rebond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. +- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (i.e. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to re-bond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. - - **What is going on?** When a Bluetooth connection is made a private shared key is created that is needed to allow communication between the sensor and the calling application/device. There is a high probability that the LL app or the Reader creates a new private shared key for communication during the connection. This means that after bonding, xDrip+ is not aware of the new key and will not be able to communicate with the sensor. @@ -459,6 +452,9 @@ Make sure you are running the latest versions of xDrip+ and OOP2. - Verify OOP2 is not put to sleep by the phone battery savings apps and settings - Verify Google Play protect is disabled as it will kill OOP2 +- Did you change Bluetooth Pairing in System Status? Touch it back to bring it back to **Disabled** + +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) #### Missed readings diff --git a/docs/CROWDIN/ru/images/minimal00per/xdripSSbond.png b/docs/CROWDIN/ru/images/minimal00per/xdripSSbond.png new file mode 100644 index 000000000000..8a222fc80895 Binary files /dev/null and b/docs/CROWDIN/ru/images/minimal00per/xdripSSbond.png differ diff --git a/docs/CROWDIN/ru/images/minimal00per/xdripSSlog.png b/docs/CROWDIN/ru/images/minimal00per/xdripSSlog.png index cb1fac206823..9edaa3f2bb48 100644 Binary files a/docs/CROWDIN/ru/images/minimal00per/xdripSSlog.png and b/docs/CROWDIN/ru/images/minimal00per/xdripSSlog.png differ diff --git a/docs/CROWDIN/ru/images/minimal00per/xdripSStat.png b/docs/CROWDIN/ru/images/minimal00per/xdripSStat.png index 77fac8ebc0cd..1e77e9229cd2 100644 Binary files a/docs/CROWDIN/ru/images/minimal00per/xdripSStat.png and b/docs/CROWDIN/ru/images/minimal00per/xdripSStat.png differ diff --git a/docs/CROWDIN/sk/CompatibleCgms/Libre2MinimalL00per.md b/docs/CROWDIN/sk/CompatibleCgms/Libre2MinimalL00per.md index 6c46c2c78d98..dc51b4146ffc 100644 --- a/docs/CROWDIN/sk/CompatibleCgms/Libre2MinimalL00per.md +++ b/docs/CROWDIN/sk/CompatibleCgms/Libre2MinimalL00per.md @@ -60,6 +60,7 @@ A list of definitions exists at the bottom of this document. If you are unfamili - *[Notes](#minimallooper-notes)* - *[Advantages](#minimallooper-advantages)* - *[Disadvantages](#minimallooper-disadvantages)* +- *\[Troubleshooting\](#minimallooper-troubleshooting)* ## Before You Start @@ -190,6 +191,8 @@ Once scanned the QR code above, if you have a Samsung phone (but this is also us ![xDrip+ debug settings](../images/minimal00per/xdripDBG.png) +(minimallooper-OOPsettings)= + **Less Common Settings -\> Other misc options** > **Settings for OOP2 Configuration** @@ -256,6 +259,10 @@ A 60 second waiting period is enforced because the sensor can’t be scanned dur ![xDrip+ scan](../images/minimal00per/xdripscan3.png) +Open xDrip+ event logs and check the sensor paired correctly with xDrip+. + +![xDrip+ scan](../images/minimal00per/xdripstream.png) + (minimallooper-step8)= ### **Step 8: Data Collection between 3 and 15 Minutes** @@ -285,31 +292,24 @@ Press the Hamburger menu in the upper left of the xDrip+ Overview screen and sel On the **BT Device** (swipe left) screen you can verify further connection details of the sensor as well as use this screen for troubleshooting connections. Below is a list of fields and their purposes to assist in connection troubleshooting. -*NOTE: **DO NOT click on Bluetooth Pairing** in this window as your sensor has already been paried or is in the middle of the pairing and bonding process. Doing so will attempt a direct pair and you will have to start the process from Step 5 all over again.* +*NOTE: **DO NOT TOUCH AND CHANGE Bluetooth Pairing from Disabled** in this window. Doing so will attempt a direct pair, it will fail (Not bonded) and you will have to start the process from Step 5 all over again.* -- **Phone Service State:** The last time the phone made a BT connection to the sensor +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) +- **Phone Service State:** The last time the phone made a BT connection to the sensor (it should be less than 5 minutes ago) - **Bluetooth Device:** Displays current status of the connection (either **Connected** or **Disconnected**) - -- **Active device connection:** Displays the status of the bluetooth bond after connection. **True** means the sensor is connected and bonded. - - **Device Mac Address**: This is the hardware ID of the sensor +- **Bluetooth Pairing**: This should be **Disabled, tap to enable**. Be careful to NOT tap this. If you tap it by mistake, tap it again until it returns to disabled. +- **Slowest wake up**: You can ignore this. xDrip+ doesn't spend its time waiting for readings: it will start expecting them at after a certain time (traditionally 5 minutes). If no data arrives at that time, you'll see "Woke up early" meaning xDrip+ was expecting data to be ready but there's none. Slowest wake up is the highest delay encountered before receiving data normally. +- **Next Wake up**: Should say 5 minutes -- **GATT device connected:** This is the hardware ID registered in the Android BT service. Any bluetooth devices actively bonded to your phone will display their hardware ID here. The GATT and Device Address should match for your sensor hardware ID. - -- **Request Data:** Only shown with Engineering Mode enabled in xDrip+. Pressing **Test for xBridgePlus protocol** you can manually start a request for data from your sensor. - -- **Received Data:** This is a hexadecimal representation of the data stream coming from your sensor. If you see characters here then you are actively receiving data from the sensor. The data should change after pressing **Test for xBridgePlus protocol**. - -- **Send Data:** This is the data request hexadecimal stream sent to the sensor to start data retrieval. After pressing **Test for xBridgePlus protocol** you should see this field update however, the data may not change a the request is the same each time. - - ![xDrip+ scan](../images/minimal00per/xdripSStat.png) +![xDrip+ scan](../images/minimal00per/xdripSStat.png) (minimallooper-notes)= ### **Notes** -- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (ie. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to rebond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. +- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (i.e. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to re-bond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. - - **What is going on?** When a Bluetooth connection is made a private shared key is created that is needed to allow communication between the sensor and the calling application/device. There is a high probability that the LL app or the Reader creates a new private shared key for communication during the connection. This means that after bonding, xDrip+ is not aware of the new key and will not be able to communicate with the sensor. @@ -414,3 +414,62 @@ On the **BT Device** (swipe left) screen you can verify further connection detai - **OOP2** - Out of Process Algorithm version 2, the 3rd party app that receives encrypted data delivered to from the FSL 2 sensor (by Bluetooth or NFC scan) and then decrypts the encrypted data. Once decrypted, the data is then sent to xDrip+.   + +(minimallooper-troubleshooting)= + +### Troubleshooting + +#### Failure to scan the sensor with NFC + +- Make sure your phone NFC reader is enabled in Android settings. +- The NFC reader must be compatible with **ISO 15693** tags. Some Cubot phones are very difficult to use. +- Look into you phone documentation to identify the NFC antenna position. Bring it to the sensor and stay on it for 10 seconds: xDrip+ NFC reading takes longer than the vendor app or the reader. +- Try to close xDrip+ before scanning the sensor. +- Make sure no other app wants to read the sensor (you might see a selection with different app choices when scanning: select xDrip+ but don't move the phone). +- Try all combinations of xDrip+ NFC settings *Use faster multi-block reading method* and *Use Any-tag optimized reading method* knowing that NFC scans are usually more reliable with both these options **off**. + +#### Stuck on collecting initial readings + +*Note: FSL 2 is not recognized as a trusted data source when calibrated manually.* + +Set [OOP2 calibration](#minimallooper-OOPsettings) strategy to "No calibration" until you have everything working. + +Then you can decide to calibrate or not. + +![xDrip+ scan](../images/minimal00per/xdripinitial.png) + +#### Sensor is reported as FSL1 + +![xDrip+ scan](../images/minimal00per/xdripL1.png) + +Make sure you are running the latest versions of xDrip+ and OOP2. + +#### Connection to the sensor fails + +- Verify OOP1 is disabled (see [here](#minimallooper-OOPsettings)) + +![xDrip+ scan](../images/minimal00per/xdripstreamfail.png) + +- Verify OOP2 is not put to sleep by the phone battery savings apps and settings +- Verify Google Play protect is disabled as it will kill OOP2 +- Did you change Bluetooth Pairing in System Status? Touch it back to bring it back to **Disabled** + +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) + +#### Missed readings + +Make sure OOP2 shows values that are not 0 or -1, it might be a sign your sensor is failing (example below in mmol/l). + +![xDrip+ scan](../images/minimal00per/OOP2values.png) + +Sensor age has not advanced might also be a sign your sensor has issues. This means xDrip+ received a value, but discarded it as it was not acceptable (sensor error). + +![xDrip+ scan](../images/minimal00per/xdripnotadvanced.png) + +#### Restart from scratch sensor pairing + +1. xDrip+ menu -> Stop sensor (it won't stop the FSL2, just change xDrip+ state to not started) +2. xDrip+ menu -> System status -> Forget device +3. Scan the sensor with xDrip+ NFC. Wait at least one minute +4. xDrip+ menu -> Start sensor. Wait at least one minute +5. Scan the sensor with xDrip+ NFC, a few times, always waiting at least one minute between two scans diff --git a/docs/CROWDIN/sk/images/minimal00per/xdripSSbond.png b/docs/CROWDIN/sk/images/minimal00per/xdripSSbond.png new file mode 100644 index 000000000000..8a222fc80895 Binary files /dev/null and b/docs/CROWDIN/sk/images/minimal00per/xdripSSbond.png differ diff --git a/docs/CROWDIN/sk/images/minimal00per/xdripSSlog.png b/docs/CROWDIN/sk/images/minimal00per/xdripSSlog.png index cb1fac206823..9edaa3f2bb48 100644 Binary files a/docs/CROWDIN/sk/images/minimal00per/xdripSSlog.png and b/docs/CROWDIN/sk/images/minimal00per/xdripSSlog.png differ diff --git a/docs/CROWDIN/sk/images/minimal00per/xdripSStat.png b/docs/CROWDIN/sk/images/minimal00per/xdripSStat.png index 77fac8ebc0cd..1e77e9229cd2 100644 Binary files a/docs/CROWDIN/sk/images/minimal00per/xdripSStat.png and b/docs/CROWDIN/sk/images/minimal00per/xdripSStat.png differ diff --git a/docs/CROWDIN/tr/CompatibleCgms/Libre2MinimalL00per.md b/docs/CROWDIN/tr/CompatibleCgms/Libre2MinimalL00per.md index 1910cf7b2035..64f5003e75c8 100644 --- a/docs/CROWDIN/tr/CompatibleCgms/Libre2MinimalL00per.md +++ b/docs/CROWDIN/tr/CompatibleCgms/Libre2MinimalL00per.md @@ -292,31 +292,24 @@ Press the Hamburger menu in the upper left of the xDrip+ Overview screen and sel On the **BT Device** (swipe left) screen you can verify further connection details of the sensor as well as use this screen for troubleshooting connections. Below is a list of fields and their purposes to assist in connection troubleshooting. -*NOTE: **DO NOT click on Bluetooth Pairing** in this window as your sensor has already been paried or is in the middle of the pairing and bonding process. Doing so will attempt a direct pair and you will have to start the process from Step 5 all over again.* +*NOTE: **DO NOT TOUCH AND CHANGE Bluetooth Pairing from Disabled** in this window. Doing so will attempt a direct pair, it will fail (Not bonded) and you will have to start the process from Step 5 all over again.* -- **Phone Service State:** The last time the phone made a BT connection to the sensor +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) +- **Phone Service State:** The last time the phone made a BT connection to the sensor (it should be less than 5 minutes ago) - **Bluetooth Device:** Displays current status of the connection (either **Connected** or **Disconnected**) - -- **Active device connection:** Displays the status of the bluetooth bond after connection. **True** means the sensor is connected and bonded. - - **Device Mac Address**: This is the hardware ID of the sensor +- **Bluetooth Pairing**: This should be **Disabled, tap to enable**. Be careful to NOT tap this. If you tap it by mistake, tap it again until it returns to disabled. +- **Slowest wake up**: You can ignore this. xDrip+ doesn't spend its time waiting for readings: it will start expecting them at after a certain time (traditionally 5 minutes). If no data arrives at that time, you'll see "Woke up early" meaning xDrip+ was expecting data to be ready but there's none. Slowest wake up is the highest delay encountered before receiving data normally. +- **Next Wake up**: Should say 5 minutes -- **GATT device connected:** This is the hardware ID registered in the Android BT service. Any bluetooth devices actively bonded to your phone will display their hardware ID here. The GATT and Device Address should match for your sensor hardware ID. - -- **Request Data:** Only shown with Engineering Mode enabled in xDrip+. Pressing **Test for xBridgePlus protocol** you can manually start a request for data from your sensor. - -- **Received Data:** This is a hexadecimal representation of the data stream coming from your sensor. If you see characters here then you are actively receiving data from the sensor. The data should change after pressing **Test for xBridgePlus protocol**. - -- **Send Data:** This is the data request hexadecimal stream sent to the sensor to start data retrieval. After pressing **Test for xBridgePlus protocol** you should see this field update however, the data may not change a the request is the same each time. - - ![xDrip+ scan](../images/minimal00per/xdripSStat.png) +![xDrip+ scan](../images/minimal00per/xdripSStat.png) (minimallooper-notes)= ### **Notes** -- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (ie. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to rebond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. +- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (i.e. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to re-bond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. - - **What is going on?** When a Bluetooth connection is made a private shared key is created that is needed to allow communication between the sensor and the calling application/device. There is a high probability that the LL app or the Reader creates a new private shared key for communication during the connection. This means that after bonding, xDrip+ is not aware of the new key and will not be able to communicate with the sensor. @@ -459,6 +452,9 @@ Make sure you are running the latest versions of xDrip+ and OOP2. - Verify OOP2 is not put to sleep by the phone battery savings apps and settings - Verify Google Play protect is disabled as it will kill OOP2 +- Did you change Bluetooth Pairing in System Status? Touch it back to bring it back to **Disabled** + +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) #### Missed readings diff --git a/docs/CROWDIN/tr/images/minimal00per/xdripSSbond.png b/docs/CROWDIN/tr/images/minimal00per/xdripSSbond.png new file mode 100644 index 000000000000..8a222fc80895 Binary files /dev/null and b/docs/CROWDIN/tr/images/minimal00per/xdripSSbond.png differ diff --git a/docs/CROWDIN/tr/images/minimal00per/xdripSSlog.png b/docs/CROWDIN/tr/images/minimal00per/xdripSSlog.png index cb1fac206823..9edaa3f2bb48 100644 Binary files a/docs/CROWDIN/tr/images/minimal00per/xdripSSlog.png and b/docs/CROWDIN/tr/images/minimal00per/xdripSSlog.png differ diff --git a/docs/CROWDIN/tr/images/minimal00per/xdripSStat.png b/docs/CROWDIN/tr/images/minimal00per/xdripSStat.png index 77fac8ebc0cd..1e77e9229cd2 100644 Binary files a/docs/CROWDIN/tr/images/minimal00per/xdripSStat.png and b/docs/CROWDIN/tr/images/minimal00per/xdripSStat.png differ diff --git a/docs/CROWDIN/zh_CN/CompatibleCgms/Libre2MinimalL00per.md b/docs/CROWDIN/zh_CN/CompatibleCgms/Libre2MinimalL00per.md index 804f0e339ed7..8650125e99bb 100644 --- a/docs/CROWDIN/zh_CN/CompatibleCgms/Libre2MinimalL00per.md +++ b/docs/CROWDIN/zh_CN/CompatibleCgms/Libre2MinimalL00per.md @@ -292,31 +292,24 @@ Press the Hamburger menu in the upper left of the xDrip+ Overview screen and sel On the **BT Device** (swipe left) screen you can verify further connection details of the sensor as well as use this screen for troubleshooting connections. Below is a list of fields and their purposes to assist in connection troubleshooting. -*NOTE: **DO NOT click on Bluetooth Pairing** in this window as your sensor has already been paried or is in the middle of the pairing and bonding process. Doing so will attempt a direct pair and you will have to start the process from Step 5 all over again.* +*NOTE: **DO NOT TOUCH AND CHANGE Bluetooth Pairing from Disabled** in this window. Doing so will attempt a direct pair, it will fail (Not bonded) and you will have to start the process from Step 5 all over again.* -- **Phone Service State:** The last time the phone made a BT connection to the sensor +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) +- **Phone Service State:** The last time the phone made a BT connection to the sensor (it should be less than 5 minutes ago) - **Bluetooth Device:** Displays current status of the connection (either **Connected** or **Disconnected**) - -- **Active device connection:** Displays the status of the bluetooth bond after connection. **True** means the sensor is connected and bonded. - - **Device Mac Address**: This is the hardware ID of the sensor +- **Bluetooth Pairing**: This should be **Disabled, tap to enable**. Be careful to NOT tap this. If you tap it by mistake, tap it again until it returns to disabled. +- **Slowest wake up**: You can ignore this. xDrip+ doesn't spend its time waiting for readings: it will start expecting them at after a certain time (traditionally 5 minutes). If no data arrives at that time, you'll see "Woke up early" meaning xDrip+ was expecting data to be ready but there's none. Slowest wake up is the highest delay encountered before receiving data normally. +- **Next Wake up**: Should say 5 minutes -- **GATT device connected:** This is the hardware ID registered in the Android BT service. Any bluetooth devices actively bonded to your phone will display their hardware ID here. The GATT and Device Address should match for your sensor hardware ID. - -- **Request Data:** Only shown with Engineering Mode enabled in xDrip+. Pressing **Test for xBridgePlus protocol** you can manually start a request for data from your sensor. - -- **Received Data:** This is a hexadecimal representation of the data stream coming from your sensor. If you see characters here then you are actively receiving data from the sensor. The data should change after pressing **Test for xBridgePlus protocol**. - -- **Send Data:** This is the data request hexadecimal stream sent to the sensor to start data retrieval. After pressing **Test for xBridgePlus protocol** you should see this field update however, the data may not change a the request is the same each time. - - ![xDrip+ scan](../images/minimal00per/xdripSStat.png) +![xDrip+ scan](../images/minimal00per/xdripSStat.png) (minimallooper-notes)= ### **备注** -- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (ie. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to rebond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. +- **Using LL NFC Scans AFTER bonding/pairing in xDrip+ is completed**: You can conduct NFC scans but the bonding/pairing process with xDrip+ needs to be completed first. Always look at xDrip+ and see if it is close to the 5 minute reading (i.e. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to re-bond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. However between these BT readings I have not had any problems executing an NFC scan followed by immediately disabling the app. I am not sure if LL needs to be disabled each time but I disable it to be on the safe side. - - **What is going on?** When a Bluetooth connection is made a private shared key is created that is needed to allow communication between the sensor and the calling application/device. There is a high probability that the LL app or the Reader creates a new private shared key for communication during the connection. This means that after bonding, xDrip+ is not aware of the new key and will not be able to communicate with the sensor. @@ -459,6 +452,9 @@ Make sure you are running the latest versions of xDrip+ and OOP2. - Verify OOP2 is not put to sleep by the phone battery savings apps and settings - Verify Google Play protect is disabled as it will kill OOP2 +- Did you change Bluetooth Pairing in System Status? Touch it back to bring it back to **Disabled** + +![xDrip+ scan](../images/minimal00per/xdripSSbond.png) #### Missed readings diff --git a/docs/CROWDIN/zh_CN/images/minimal00per/xdripSSbond.png b/docs/CROWDIN/zh_CN/images/minimal00per/xdripSSbond.png new file mode 100644 index 000000000000..8a222fc80895 Binary files /dev/null and b/docs/CROWDIN/zh_CN/images/minimal00per/xdripSSbond.png differ diff --git a/docs/CROWDIN/zh_CN/images/minimal00per/xdripSSlog.png b/docs/CROWDIN/zh_CN/images/minimal00per/xdripSSlog.png index cb1fac206823..9edaa3f2bb48 100644 Binary files a/docs/CROWDIN/zh_CN/images/minimal00per/xdripSSlog.png and b/docs/CROWDIN/zh_CN/images/minimal00per/xdripSSlog.png differ diff --git a/docs/CROWDIN/zh_CN/images/minimal00per/xdripSStat.png b/docs/CROWDIN/zh_CN/images/minimal00per/xdripSStat.png index 77fac8ebc0cd..1e77e9229cd2 100644 Binary files a/docs/CROWDIN/zh_CN/images/minimal00per/xdripSStat.png and b/docs/CROWDIN/zh_CN/images/minimal00per/xdripSStat.png differ diff --git a/docs/CROWDIN/zh_TW/CompatibleCgms/Libre2MinimalL00per.md b/docs/CROWDIN/zh_TW/CompatibleCgms/Libre2MinimalL00per.md index d0b9cd3bc88a..0216d8d70b24 100644 --- a/docs/CROWDIN/zh_TW/CompatibleCgms/Libre2MinimalL00per.md +++ b/docs/CROWDIN/zh_TW/CompatibleCgms/Libre2MinimalL00per.md @@ -292,31 +292,24 @@ 在 **BT 設備**（向左滑動）螢幕上，您可以查驗傳感器的進一步連線詳情，並使用此螢幕進行連線故障排除。 以下是各欄位及其用途的列表，以協助連線故障排除。 -*注意：**不要在此視窗中點擊藍牙配對**，因為您的傳感器已經配對或正在進行配對和連線的過程。 這樣會嘗試直接配對，您將不得不從步驟 5 開始重新執行整個過程。* +*NOTE: **DO NOT TOUCH AND CHANGE Bluetooth Pairing from Disabled** in this window. Doing so will attempt a direct pair, it will fail (Not bonded) and you will have to start the process from Step 5 all over again.* -- **手機服務狀態：** 手機上次與傳感器建立藍牙連線的時間。 - -- **藍牙設備：** 顯示連線的當前狀態（**已連線** 或 **已中斷連線**） - -- **活動設備連線：** 顯示藍牙連線之後的狀態。 **True** 意味著傳感器已連線且已配對。 +![xDrip+ 掃描](../images/minimal00per/xdripSSbond.png) +- **Phone Service State:** The last time the phone made a BT connection to the sensor (it should be less than 5 minutes ago) +- **Bluetooth Device:** Displays current status of the connection (either **Connected** or **Disconnected**) - **裝置 Mac 位址**: 這是傳感器的硬體識別碼。 +- **Bluetooth Pairing**: This should be **Disabled, tap to enable**. Be careful to NOT tap this. If you tap it by mistake, tap it again until it returns to disabled. +- **Slowest wake up**: You can ignore this. xDrip+ doesn't spend its time waiting for readings: it will start expecting them at after a certain time (traditionally 5 minutes). If no data arrives at that time, you'll see "Woke up early" meaning xDrip+ was expecting data to be ready but there's none. Slowest wake up is the highest delay encountered before receiving data normally. +- **Next Wake up**: Should say 5 minutes -- **GATT 裝置已連線:** 這是註冊在 Android 藍牙服務中的硬體識別碼。 任何與您的手機配對的藍牙裝置將在這裡顯示其硬體識別碼。 GATT 和裝置位址應該與您的傳感器硬體識別碼相符。 - -- **請求資料:** 僅在 xDrip+ 的工程模式啟用時顯示。 按下**xBridgePlus 協議測試** ，您可以手動開始請求傳感器的資料。 - -- **接收資料:** 這是從您的傳感器傳來的資料流的十六進制表示形式。 如果您在此看到文字，則表示您正積極接收來自傳感器的資料。 按下**xBridgePlus 協議測試**後，資料應該會改變。 - -- **發送資料:** 這是發送到傳感器以開始資料擷取的資料請求十六進制流。 按下**xBridgePlus 協議測試**後，您應該看到此欄位更新，然而資料可能不會改變，因為請求每次都是相同的。 - - ![xDrip+ 掃描](../images/minimal00per/xdripSStat.png) +![xDrip+ 掃描](../images/minimal00per/xdripSStat.png) (minimallooper-notes)= ### **註釋** -- **在配對/連線完成後使用 LL NFC 掃描**: 您可以進行 NFC 掃描，但需要先完成與 xDrip+ 的配對/連線過程。 始終查看 xDrip+，確保它接近 5 分鐘讀取值（例如 4 分鐘前），如果接近 5 分鐘，請等待新的藍牙讀取值進來後再進行 NFC 掃描。 如果您在錯誤的時間捕捉到，將會干擾 xDrip+ 的藍牙流程，導致無法接收藍牙讀取值，這可能需要一段時間才能重新配對並再次傳輸，且有時傳感器的藍牙連線可能會被 LL “搶走”。 然而，在這些藍牙讀取值之間，我運行 NFC 掃描後立即停用應用程式並沒有遇到任何問題。 我不確定是否每次都需要停用 LL，但我為了安全起見會停用它。 +- **在配對/連線完成後使用 LL NFC 掃描**: 您可以進行 NFC 掃描，但需要先完成與 xDrip+ 的配對/連線過程。 Always look at xDrip+ and see if it is close to the 5 minute reading (i.e. 4 minutes ago), if it is near 5 min, wait for the new BT reading to come in and then conduct the NFC scan. If you catch it at the wrong time it will disturb the BT process in xDrip+ and not receive BT readings, which can take a while to re-bond and transmit again and sometimes a sensor BT connection can be “stolen” by LL. 然而，在這些藍牙讀取值之間，我運行 NFC 掃描後立即停用應用程式並沒有遇到任何問題。 我不確定是否每次都需要停用 LL，但我為了安全起見會停用它。 - - **發生了什麼事情?** 當藍牙連線建立時，會創建一個私有共享密鑰，這是允許傳感器與呼叫應用程式/裝置之間進行通信所需的。 LL 應用程式或讀取器在連接期間高機率會創建一個新的私有共享密鑰來進行通信。 這意味著在配對後，xDrip+ 無法識別新金鑰，因此無法與傳感器通信。 @@ -459,6 +452,9 @@ - 驗證 OOP2 是否未被手機的省電應用和設定讓其進入待機狀態 - 驗證 Google Play 保護已停用，因為這會影響 OOP2 +- Did you change Bluetooth Pairing in System Status? Touch it back to bring it back to **Disabled** + +![xDrip+ 掃描](../images/minimal00per/xdripSSbond.png) #### 讀數遺失 diff --git a/docs/CROWDIN/zh_TW/images/minimal00per/xdripSSbond.png b/docs/CROWDIN/zh_TW/images/minimal00per/xdripSSbond.png new file mode 100644 index 000000000000..8a222fc80895 Binary files /dev/null and b/docs/CROWDIN/zh_TW/images/minimal00per/xdripSSbond.png differ diff --git a/docs/CROWDIN/zh_TW/images/minimal00per/xdripSSlog.png b/docs/CROWDIN/zh_TW/images/minimal00per/xdripSSlog.png index cb1fac206823..9edaa3f2bb48 100644 Binary files a/docs/CROWDIN/zh_TW/images/minimal00per/xdripSSlog.png and b/docs/CROWDIN/zh_TW/images/minimal00per/xdripSSlog.png differ diff --git a/docs/CROWDIN/zh_TW/images/minimal00per/xdripSStat.png b/docs/CROWDIN/zh_TW/images/minimal00per/xdripSStat.png index 77fac8ebc0cd..1e77e9229cd2 100644 Binary files a/docs/CROWDIN/zh_TW/images/minimal00per/xdripSStat.png and b/docs/CROWDIN/zh_TW/images/minimal00per/xdripSStat.png differ