Possible bug - disconnecting from Xdrip more than 20 min, causes permanent unpairing of Dexcom One transmitter

[Nick-Athe]

I need some help on this!!!!
It happened to me twice in the past 3 days. My son left away his phone for about 20-30 minutes and from then on it is impossible to re-connect. When I start pairing again, for the 1st cycle I get the readings but on the 2nd 5-min cycle I get the message "Unpaired". When disconnected for a short period, say 5 min, it reconnects with no problem.

Ple

[Nick-Athe]

FYI: the only solution so far was to use new sensor / transmitter

[steve8x8]

This is a KingKong Mini (2? 2Pro?), right? - can you provide some details about the device, the OS running, and the BT settings in xDrip?

[Nick-Athe]

Yes, it is king kong mini 2, android 10

[jamorham]

Disable the special pairing workaround setting (default is off and is for samsung only) and it should be able to re-pair.

[jamorham]

Can you explain what you mean about changing the transmitter id? Please describe the steps you are following to help me understand and try to reproduce the error.

[Nick-Athe]

sure, see all steps.

a. Initial pairing ok, started the sensor without problems. Phone/Dex1 worked ok for few days.
b. One day, after leaving the phone away for more than 15-20min, on the Phone Service State State: Unpaired. And Brain State: Unbonding Errors. Pairing is lost, I assume, and cannot be reinstated by using “Restarting collector”. Or any other way.
During the days it worked ok, in case it lost signal for a few minutes, it would reconnect without any intervention.
c. From this incident onward, the only way to get data from the transmitter is by using https://navid200.github.io/xDrip/docs/MissedPairRequest.html (this is what I mean by changing transmitter ID). But with this procedure, I only get data once. I have to repeat the process every time I want to read Dex1.

[Nick-Athe]

Is it possible that having dex1 away/disconnected for a prolonged period is perceived as an effort to restart the sensor to extend its life and it gets blocked permanently?

[Nick-Athe]

Today I started a new sensor. I used a new transmitter as my previous one doesn't seem to connect. I was wondering if I can send you by post this receiver so you can try to read from it and find out whats going on with C type dex1. I got a feeling that some security feature prevents transmitters from pairing again once disconnected for a reason. Please let me know. I know that there are couple of more people having the same issue with me

[jamorham]

please contact me jamorham at gmail if you still want to send the transmitter for testing

[Navid200]

Have you disabled battery optimization?

[Nick-Athe]

yes, of course

[Nick-Athe]

aaps, xdrip, have full access, incl. location, without battery optim.

[Nick-Athe]

Good afternoon everyone,
I plan to start a new dex1 sensor in 3 days (when the current Libre1 expires).
I am not sure if you managed to run any tests, or get an idea on what causes the issue of unpairing.
In addition, something I don't really know, is if the transmitter gets to keep in its memory (if any) a record of past failures in connecting, or the device it was connected to. And if this could be a source of failure for subsequent connection attempts to the same or other devices.
This time I will be using Redmi 10C /Android 11/Miui 13 and not KingKong2 as it "died" suddenly tonight and can't turn it on.
If you got any suggestions, please let me know.
Thank you in advance, Nick

[jamorham]

Please let us know how it goes.