AAPS keeps saying recalculated value used

[TWilhoWI]

AAPS keeps saying "recalculated value used" with G7. I've followed the setup guide. The only thing i've enabled extra is "Special Pairing Workaround".
Version: 2024.04.19.
Phone: Cubot Mini 3

[Navid200]

This is a question for the AAPS team.
But, I will tag someone who may be able to help.

@olorinmaia

[rpm5099]

Not to pile on in the wrong forum (sorry), I have noticed this as well @olorinmaia.

With G7 I've never seen it not show the recalculated data warning. I think the warning is meant to be in response to noisy data, but I'm not sure. This is also the case with the Libre 3, except the Libre 3 data is extremely smooth and virtually always 100% accurate, less noise than G6 and way less noise than G7. I haven't looked at the code closely to figure out what it means but I have no idea what is actually being "recalculated". It's also unclear which features do not function when this warning is present.

[TWilhoWI]

Second shows missed reading?

[TWilhoWI]

Hi Navid, my previous phone had this issue, that's why I enabled it.
Now trough the night my sensor status changed to "sensor errors"?

[TWilhoWI]

I had to re-enable to setting. The phone constantly disconnected.

[Navid200]

xDrip is free and you can use it as you wish.
We set it up such that it can be used with most phones, but may be not with all.
So, we explain how each setting should be used: https://navid200.github.io/xDrip/docs/Intermittent.html

I am doing my best to help you. I have tried to identify the word pair and clarify that you should not use the special pairing workaround if you phone does not unpair on its own. You keep using the word disconnect.

We may have a language problem here and I am not going to insist. I am sorry if it is not working for you.

[TWilhoWI]

Without the setting it is unpairing. So I guess I have to enable it.
Now for the values which comes at different times? Is this because of the special pairing?

[Navid200]

Yes, if it unpairs, you should enable the special pairing workaround setting.

I need to do some experiments to understand the G7 behavior better to figure out the mechanism behind the additional transmissions.
Before I can do that or unless someone else can shed some light on this, I don't have enough knowledge to make any statements about them.

[olorinmaia]

This is not caused by xDrip, and is like Navid say an AAPS issue. Simply because G7 delivers BG data more often at irregular times compared to G6. AAPS expect BG data every 5 min, which doesn't cope well with G7 as each sensor got it's own transmitter and therefor BG interval will differ more often than G6. It also seem to send BG data at irregular times if a few readings are missed (but I'm a new user of G7 so not sure about this yet). I also notice that yellow warning sign in AAPS is activated almost all the time.

I recommend following this issue, and possibly commenting on how you consider this can be improved in AAPS:
nightscout/AndroidAPS#3197

See here for more info about the yellow warning sign:
https://androidaps.readthedocs.io/en/latest/Getting-Started/Screenshots.html#yellow-warning-sign

[Navid200]

I am running some experiments to see if I can do anything to improve the G7 collector.
This is where I am including the details about my experiments in this regard: https://navid200.github.io/xDrip/docs/Dexcom/G7OnceAMinuteScan.html

At this point, this is just a thought. I hope to be able to improve things. Thanks for your patience.

[Navid200]

Can you also make sure that the following setting is enabled?
Settings -> Less common settings -> Aggressive service restarts

[TWilhoWI]

It is enabled

[Navid200]

I have opened a PR to improve this: #3461
My hope is that it will not increase battery consumption. I am testing it now.
We now have to be patient and wait for a review.

[TWilhoWI]

Thanks Navid! Please keep me posted!

[Navid200]

Please use the xDrip release of May 22, 2024 or any after that.
xDrip used to get confused and screw up the timetamps when G7 went into the once a minute transmission. That does not happen any more.

So, you should not get the warning from AAPS any longer.
Of course, you may still get it every time you start a new G7. But, you should never get it just because of a disconnect.

[TWilhoWI]

Hi @Navid200 , repost. I still have some disconnections.

[TWilhoWI]

It's a Cubot mini 3 phone. Seeing this error above, will this classify as a unpairing?
I'm willing to give the special pairing workaround a test?

[Navid200]

Yes, it does since you approved a pair request and it is still needing to pair again, which means that it unpaired on its own.
Unless, you went to the phone Bluetooth settings and forgot the paired device.

[TWilhoWI]

Perfect, I will enable the setting.
Does it require a reboot of the device?

[Navid200]

It wouldn't hurt

[TWilhoWI]

Using this setting it seems very stable now!