Blank window instead of readings

[Inkalika]

After Sensor Error 373 the sensor readings are not readable. After an hour the readings are received via NFC, but they are not displayed on the main window. After rebooting the phone, the error type and sensor number disappear. There is a blank screen at this point. But if I turn on another phone, then on the new phone readings start to be displayed and change. Helps a complete reinstallation, change of version. But this time it didn't help.
Program version 7.4.6, 7.3.1. Libre 2 sensor
This situation occurs already with the second sensor in a row

Is it acceptable to turn on two phones to poll one sensor via bluetooth? Can polling two phones via bluetooth of a sensor cause Sensor Errod (373) error?
Noticed that if 2 phones are enabled via bluetooth there is a Sensor Error, but the NFC readings are coming through on both phones.

[j-kaltes]

A sensor can connect via Bluetooth only with one device at a time. See https://www.juggluco.nl/Juggluco/index.html#multiple
You can scan via NFC with multiple devices. You can also use one device via Bluetooth and then another device as long as you turn off Juggluco on the first device or turn off Bluetooth or "Use Bluetooth" and before scanning the sensor on the new device terminate the sensor on Juggluco on that device so that the sensor is initialized a new.
On the last screenshot you have disable Bluetooth so that will never work.

[Inkalika]

That's weird. Because when the bluetooth is off, on the right side I see the phrase "Enable bluetooth" (or Desable bluetooth?) . And after turning bluetooth on, the screen stays in this place without any readings or serial number. But on the other phone the readings start coming right away.

[j-kaltes]

As said, you can't connect two phones to the same sensor.

After turning on USB debugging in developers options, you connect the phone to your computer, open a terminal and confirm that the phone is connected by typing "adb devices". You go to a writable directory and press:

adb shell run-as tk.glucodata cat /data/data/tk.glucodata/files/logs/trace.log > trace.log

trace.log is than written in that directory.

[Inkalika]

Before turning on the bluetooth on the old phone, I turn off the bluetooth on the new phone, but even after 10 minutes after turning on the bluetooth, the readings are not coming. But if I turn off the bluetooth on the old phone and turn it on on the new phone, the readings come to the new phone very quickly.

[j-kaltes]

Yes, you should scan again to make it work and either wait a long time before scanning or terminate the sensor on that phone and scan again. Bluetooth and "Sensor via Bluetooth" should also be turned on. There are also phones with bad Bluetooth that only very reluctantly make a connection with the sensor, see #76 (comment)
Also when switching to a phone with good Bluetooth, it can take a terrible long time before it is working again after having scanned the sensor with another phone. This is totally different from switching between a phone and a watch that are connected via a mirror connection, thus having the same authentication information.

[Inkalika]

Three phones:

1. Redmi 12C After restoring the NFC bluetooth readings transmission, it still did not start transmitting (waited for more than 10 minutes). Black screen was displayed on the right side of the program.
2. Redmy 9C This phone was read the sensor when the first phone did not transmit readings via bluetooth for a long time. The readings came quickly
3. Samsung A12 One bluetooth reading came in, then Sensor Error appeared for a few minutes. One reading came back and then the error appeared again.
   Ended up having to opt for a second phone until a new sensor is installed