G7 erratic behaviour; defective sensors? bluetooth interference?

[dagord]

Hello, I recently switched to Dexcom G7 after having happily used G6 with xDrip for a couple of years on the same phone as now (Xiaomi Redmi note 10)
First of all, let me clarify I'm currently running the last nightly version (2024.04.19) and I'm using the
settings suggested

The first sensor worked fine without noticing any relevant issue until its expiration.

The second sensor gave me a lot of problems!

• after the warmup, which I did on evening, it started returning values every 15 minutes; only on the following morning I got it working as supposed (reading every 5 minutes) without any intervention
• But almost every night, even if at a random time, the 15 minutes issue came up again during the night; once I could fix it forcing a new pair request (forget the bluetooth device -> changing the transmitter id -> insert correct trasmitter id -> pair device again); another night I had to toggle the "avoid scanning" option
• This night I was so frustrated that I decided to remove the sensor and to start a new one.

So now I'm with my 3rd sensor; it worked fine until this afternoon: I went away from my smartphone for 30 minutes and when I come back the 15 minutes thing came up again!
This is an extract from my logs:

So I decided to test the trasmitter signal with BLE Scanner; both the transmitters (the new and the old, that was near to me and wasn't expired yet) were correctly found but even when "clear and bold" the values were not returned to xDrip; suspecting an interference with the old sensor I moved it to another room and the issue disappeared!

So, coming back to the original issue: why am I experiencing those disconnections during nightime?
I keep my supply of sensors in the bedside table, but I don't think they're causing interference since they're still sealed and not activated.
It was a sensor issue for sure or is there something I can do to investigate further?

I'm asking this because I experienced an identical issue with my old G6 transmitter: after an Android 13 update it started returning values every 15 minutes, but the issue affected only xDrip; the workaround was to use the BYODA Dexcom app and xDrip in companion mode. Eventually, the issue disappeared after an xDrip update.

[Navid200]

Xiaomi is a known problem phone.

This is what is recommended for all phones that experience intermittent connectivity:
https://navid200.github.io/xDrip/docs/Intermittent.html

I had occasional disconnects myself with G6 and a Motorola phone until I got a Pixel phone about 9 months ago.
Since then, there has been no disconnects. I have been using G7 for the past 6 months.

Since you have not posted a screenshot of your status page, I cannot make any other suggestions.

[Navid200]

Does the problem still persist?

[Navid200]

Anyway, the's still a bug that I had already noticed previously: when a reading is missed (e.g. I'm in another room) the subsequent reading is often skipped as well (even if I'm back), so I need to wait for other 5 minutes.

Would you please help me understand this?

Do you mean after you return to the phone, you will never have proper operation and you will have a missed reading once every 10 minutes? Meaning you only get every other reading consistently?

Or, when you return, you will have one more missed reading before everything goes back to normal and you have no more missed readings until you move away from the phone again?

[dagord]

The second version is correct. For example, let's suppose I go to the other room at the 4th minute, so the phone skips the reading at the 5th minute; at the 6th minute I come back, but the phone also skips the next cycle. At the 15th minute, it becomes regular again. It's not a regular behaviour, so it's difficult to replicate it.

I discovered, however, that by re-enabling the 'minimize scanning' option (which you had advised me to disable: #3454 (reply in thread)), the connection has become much more stable, at least with the latest nightly release (2024.06.28); I don't know if this makes sense

[Navid200]

OK,
Thanks for explaining. And I am sorry about asking you to disable minimize scanning. It was only an experiment. I am glad you re-enabled it.

I have occasionally experienced the same thing. What I consider a serious problem is if there are consistent disconnects, not when I walk away and on return, miss one more reading.

Just to let you know, there is an open PR: #3567
The description of it suggests that it is to address the problem you have described.

Thanks

[dagord]

And I am sorry about asking you to disable minimize scanning. It was only an experiment. I am glad you re-enabled it.

No problem! I'm happy if this can help you in improving the app. It seems that disabling minimize scanning actually improved the connection on the old release, but on the newer releases it just breaks something.
And yes: my issue is exactly the one described in the thread you linked!