Often see "xdrip is not responding"

[zdooder]

I've been using xDrip+ for several years, since I was on a meter and MDI (!! for it's awesome predictability engine), to using a CGM (Dexcom G6, then G7), to using a pump, etc. Since I moved over to the Dexcom G7, and there was no BYOD app to broadcast to xDrip+ (I was not satisfied with the lack of backfilled data for xDrip+), I opted to abandon the Dexcom G7 app and use the native G7 support in xDrip+. But since doing this, I very often see "xDrip is not responding" popups occurring. I generally just hit "Wait" and the notice goes away, and there don't see to be any ill effects, but I feel like this is not great and I'd like to try to troubleshoot it.

The Hardware Data Source "page" just gives me:

But the Dex Debug Settings are:

My Classic Status Page is:

The G5/G6/G7 Status Page is:

The phone is a Samsung Galaxy Fold 4, running Android 14. Phone Hardware Information:

I do have a Galaxy Watch5, if that matters, for which I have enabled "Android Wear Integration" with the following settings:

Finally, if I need to (or just should) downgrade, I'm happy to do that. I figured it best to try the latest available version to rule out the possibility that an older version was causing my problem. The latest nightly seems to be no different, however (but also, no worse).

Any suggestions?

[Navid200]

Thanks for the screenshots.

xDrip not responding is a catastrophic failure.
I am surprised you are seeing that.

@jamorham

[jimbaxter]

I see this error about once a day for a few months. Though I have a different setup of OOP2 and the Freestyle Libre 2.
It usually goes away immediately once you hit wait.

Although I have found that recently it is sounding the alarm for missed BG readings after 30 minutes a quite often which it never used to do, this is when I have the phone on me. I thought it might be a Pixel 8 Bluetooth hardware issue, though perhaps it relates to the not responding issue?

[Navid200]

From the 3-dot menu button at the top right corner of the main screen, go to Import Export features −> Cloud Backup −> Select Backup location.
Log in to your Google Account to enable Google Drive backup.

Now, Do backup now.
Then, you should see something like this:

What does it show as the backup size?

[PhilTU]

Does your watch collect directly from the sensor without the phone ? If not you can remove the "Enable wear collection service" option, which may be irrelevant to your problem but worth a try.

[zdooder]

I am not certain if the watch collects directly from the G7 or not (but I suspect it has based on the "Watch Service State: Service Stopped " message on the status screen). I thought it would be useful for the watch to collect data when the phone was out of range, but it's not a requirement (very rarely is the phone out of range for any serious length of time, and the only real benefit is not having to pull out the pump to check).

I tried disabling the "Enable Wear Collection Service" option, but immediately got the "not responding" message, and have gotten it additional times since then with the option still disabled.

[PhilTU]

but immediately got the "not responding" message,

ok, was worth a try as it won't collect direct to the watch AFAIK no was something that could be eliminated.

[zdooder]

I didn't think to include in my initial write-up, but I have a NightScout service set up on a VPS. It's not used for much, but I do have a few things that query it for recent BG levels to display them. The xDrip+ configuration for this is:

I got to wondering if the uploads (or downloads) from that service might be a factor.

I also noticed when checking this that I also had enabled "Dexcom Share Server Upload", probably a long time ago when I was concerned about my provider wanting to use Dexcom Clarity to monitor my treatments. I know (now) that the two ("share" and "clarity") are not related, but I didn't then. Additionally, now that I'm on a pump, they use t:connect to perform this monitoring, as it shows CGM readings in addition to treatments. I have disabled the "Dexcom Share Server Upload" function to see if that might be the cause of the problem.

[jamorham]

Most likely thing I would suspect would be too much data stored. What glucose retention setting do you have? I would suggest setting it to 365 to only store a year's worth of data. If its not that we can try to dig deeper.