Often see "xdrip is not responding" #3544
Replies: 5 comments 4 replies
-
Thanks for the screenshots. xDrip not responding is a catastrophic failure. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
Most likely thing I would suspect would be too much data stored. What |
Beta Was this translation helpful? Give feedback.
-
I had the glucose retention set to unlimited. I changed it to 365 days. I did get a few more of the not responding messages, but it hasn't occurred in some time, so I believe that this ultimately was the cause and it's resolved now. Thanks so much for your help! |
Beta Was this translation helpful? Give feedback.
-
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?
Beta Was this translation helpful? Give feedback.
All reactions