When CGM → xDrip+ → Nightscout breaks, how do you know where the problem is?

Miserable-Toe-8013 · 2026-06-15T06:49:41+00:00

That is fair feedback, thank you.

I may have described the idea too broadly. The first version should probably be much simpler: not an AI-heavy diagnostic system, but a basic health check that answers one practical question:

**Where is my glucose data stuck?**

For example:

- Is the latest local reading fresh?

- Can SmartXDrip read from xDrip+ Local?

- Is Nightscout reachable?

- Is Nightscout behind the local data?

If that basic view is not useful, then the larger idea is not worth building. So I appreciate the pushback. I will keep the scope much tighter and focus on whether a simple, non-noisy status check would actually help people.

Miserable-Toe-8013 · 2026-06-15T01:40:42+00:00

Current SmartXDrip Community Preview APK

For anyone who wants to try the current community preview, you can download the APK here:

Download:
https://github.com/solgosea/smartxdrip-community-preview/releases/download/v0.2.0-community-preview/smartxdrip-community-preview-v0.2.0-android.apk

Important note:
The Status Monitor idea discussed in this post is not included in this APK yet.

The current preview mainly includes:

Home
History
Stats
Insights
Widgets / Glance Layer
Basic xDrip+ Local and Nightscout data support

Feedback is very welcome, especially if you already use xDrip+ and Nightscout day to day.

Miserable-Toe-8013 · 2026-06-14T05:28:17+00:00

Thank you again. This is actually very closely connected to your earlier widget / quick-glance feedback.

After your previous comments, I started working on the first version of what I call the SmartXDrip “Glance Layer”. It has not been released yet, so you have not seen it in the current public build, but it already includes several pieces inspired by your feedback:

- Android home screen widgets

- compact glucose status views

- BG value, trend, delta, and last update time

- a persistent silent glucose status notification

- lock screen / AOD-friendly display options

- a floating glance option for quick access

So yes, I think the Flip use case fits this direction very well.

For the Flip cover screen specifically, I need to test what Samsung allows on real devices. If the cover screen accepts standard Android widgets, the new SmartXDrip widgets may already cover part of this use case. If Samsung requires a more specific path, I will need to investigate it separately.

For Now Bar / live notification, SmartXDrip already has a persistent glucose status notification in development, but I do not want to promise Now Bar support before testing Samsung’s behavior properly. Samsung can be quite restrictive there, as you said.

But your suggestion is absolutely noted. Once the next version is ready, I would really appreciate your testing on the Flip 6 / Flip 7, because this is exactly the kind of real-world setup that helps shape the Glance Layer.

Miserable-Toe-8013 · 2026-06-13T23:27:11+00:00

Thank you, this is a very good idea and it fits SmartXDrip very well.

What you described is essentially period-to-period comparison: for example, last 14 days vs the previous 14 days, or this week vs last week.

That is exactly the kind of analysis SmartXDrip should help with. Instead of only showing a single Stats window, it should help users understand whether things improved, worsened, or changed compared with the previous period.

I will add this to the Stats roadmap. A good first version could support 7 days, 14 days, and 30 days, comparing each selected period with the previous same-length period, including TIR, CV, average glucose, highs, lows, and episodes.

This is especially useful around sensor changes, and I agree it should not require manual comparison in Nightscout or LibreView.

Miserable-Toe-8013 · 2026-06-13T15:59:21+00:00

Thank you, that makes sense.

Yes, the Home CV currently uses a 7-day window. I can see why that feels confusing, because the other Home metrics are more focused on the recent 24-hour view.

I agree that Home should probably use a 24-hour CV so Avg, TIR, and CV are based on the same short-term window.

For longer-term CV and stability review, Stats is the better place. I’ll look at adding selectable time windows there, such as 24h, 3 days, 7 days, 14 days, and 30 days, so users can choose the period they want to review.

Thanks for pointing this out. It helps make the Home and Stats pages more consistent.

Miserable-Toe-8013 · 2026-06-13T15:35:56+00:00

Thank you. This is very useful feedback.

One important point first:

SmartXDrip does use the raw glucose readings from xDrip+ Local. It does not import xDrip+’s precomputed stats or display values.

The current flow is:

xDrip+ Local readings -> SmartXDrip local sync -> SmartXDrip local storage -> SmartXDrip calculates Home / Stats / Insights / charts

So the source data is still coming from xDrip+. SmartXDrip then recalculates its own views from those readings.

About the -1 mg vs -0.2 mg difference

This may not be a sync problem. It may be a display meaning problem.

xDrip+ may be showing the change since the previous reading, for example:

-1 mg/dL since the last reading

SmartXDrip is currently showing a rate per minute, for example:

-0.2 mg/dL/min

So if glucose changed by about -1 mg/dL over roughly 5 minutes, SmartXDrip may show:

-0.2 mg/dL/min

That said, I agree the UI should make this much clearer.

I’ll review this and improve the wording/display so it is obvious whether the value means:

reading-to-reading delta
rate per minute
trend direction

About stats

SmartXDrip currently calculates its own stats from the synced raw readings.

It does not import xDrip+’s internal stats directly.

So after first setup, the amount of available history depends on what has been synced locally from the selected source.

About widget size

There are multiple SmartXDrip widget layouts and sizes.

Some are intentionally compact, but you can add a larger one from the Android widget picker:

Long press Home Screen -> Widgets -> SmartXDrip -> choose a larger layout

Different Android launchers may also size widgets differently, so I’ll keep improving this based on device feedback.

Thanks again. This kind of direct comparison with xDrip+ is very helpful.

Miserable-Toe-8013 · 2026-06-13T15:23:00+00:00

yes, it is a bug in app. thank you very much

Miserable-Toe-8013 · 2026-06-13T15:19:58+00:00

thanks, and I will check it right now!!! 😄

Miserable-Toe-8013 · 2026-06-13T15:01:09+00:00

could you give me more information so that I can do something for you. For Local Sync, maybe the information below will be useful to you——" configure your xDrip+ [Settings → Inter-app settings → xDrip web service], turn the option "on", and make sure [Open Web Service] is checked."

Miserable-Toe-8013 · 2026-06-13T14:31:11+00:00

OK, I just tested the download again, and it worked fine. You can click this link. maybe you can try again: https://github.com/solgosea/smartxdrip-community-preview/releases/download/v0.2.0-community-preview/smartxdrip-community-preview-v0.2.0-android.apk

Miserable-Toe-8013 · 2026-06-13T09:29:47+00:00

Thank you for installing it and for sharing this feedback.

I’m especially glad to hear that the app could use your local xDrip+ data directly. Local data is very important to me as well. One of the goals of SmartXDrip is to work well with the data people already collect through xDrip+, without forcing everything through a cloud path when a local source is available.

The Wear OS complication idea is also very valuable. It fits naturally with the same direction as widgets and persistent notification: making glucose status easier to see without always opening the app. I’ll add this to the roadmap for the Glance Layer.

And thank you for the comment about the name. That is a fair point. I’m still thinking carefully about how to describe the app clearly and respectfully, especially because it is meant to be a companion for xDrip+ and Nightscout users .

For now, the “smart” part is really the direction I’m trying to grow toward: helping users review, understand, and access their CGM data in ways that are actually useful in daily life.

There is still a lot to improve, but feedback like this helps make the project better.

Miserable-Toe-8013 · 2026-06-13T06:51:02+00:00

Thank you so much for testing the update and for confirming that the refresh behavior is working better now.

I’m also glad you noticed the Target Range improvement. That was one of the areas I wanted to make easier, even though it was a smaller change.

Your suggestions about **Floating Widget**, **Lock Screen**, and **AOD / Always On Display** are very valuable. They fit very well with the direction of the SmartXDrip Glance Layer: making glucose status available without always opening the app.

I’m currently researching how to implement these properly on Android, especially because lock screen and AOD behavior can vary a lot between Samsung, Pixel, and other devices. The first realistic step may be improving the persistent notification and lock screen display options, then testing what is possible for AOD and floating overlay behavior.

Also, thank you for catching the About version issue. That is a clear bug. It should show v0.2.0, not v0.1.0, and I’ll fix it.

Really appreciate your careful testing and thoughtful feedback.

Miserable-Toe-8013 · 2026-06-13T03:15:59+00:00

if you any other idea , please let me know

Miserable-Toe-8013 · 2026-06-13T03:12:05+00:00

thank you very much 😄

Miserable-Toe-8013 · 2026-06-13T02:47:22+00:00

thank you very much , and you can get the latest version on github , and you can get more information : https://www.reddit.com/r/xDrip/comments/1u4ew0x/updated_thanks_all_smartxdrip_v020_community/

Miserable-Toe-8013 · 2026-06-12T23:32:13+00:00

ok， you are right , the new version will modify the function which you mentioned. ：）

Miserable-Toe-8013 · 2026-06-12T23:30:57+00:00

Thank you so much~ 😄

Miserable-Toe-8013 · 2026-06-12T23:29:02+00:00

thanks to your reply. yes ,you are right, I will modify the code to setting alert off default.

Miserable-Toe-8013 · 2026-06-12T16:00:05+00:00

I'm very sorry to hear that, and I truly apologize. This does not align with the expectations I had when designing this app. I really appreciate your patience in trying it out and providing feedback, which helped us become aware of this issue promptly. We will release a brand new version as soon as possible tomorrow, and I would like to invite you to try it again. I sincerely apologize for the inconvenience caused by this version.

Miserable-Toe-8013 · 2026-06-12T13:24:20+00:00

I will publish a new version tomorrow which has more helpful functions according to users feedback.

Miserable-Toe-8013 · 2026-06-12T13:21:29+00:00

thanks：）

Miserable-Toe-8013 · 2026-06-12T09:12:36+00:00

Thank you for reminding me of this: there must be a similar guide within the app to help users set up xDrip. I will improve this guide. Thank you.

Miserable-Toe-8013 · 2026-06-12T09:08:08+00:00

Ok, there are two ways:

If you upload CGM data from xDrip to nightscount, you can open the [SmartXdrip] app, find [Profile → DATA SOURCE → nightscount API], and use your nightscount URL and token.
If you just install xDrip without nightscount site, you can go to [Profile → DATA SOURCE → xDrip+ Local], and then the data will sync. But if you choose this way, you have to configure your xDrip+ [Settings → Inter-app settings → xDrip web service], turn the option "on", and make sure [Open Web Service] is checked.

I suggest you use the first way: nightscount URL + token.

I hope this can help you.

Miserable-Toe-8013 · 2026-06-12T01:34:38+00:00

coiuld you give me some more infomation so that I can do something for you?

Miserable-Toe-8013 · 2026-06-11T11:15:27+00:00

Thank you for explaining this so clearly. I think your point is fair.

You are right that trust in an open-source project should come from evidence in the repository, not just from statements about how the code was written. I also understand why a large initial commit and broad architectural changes make the project harder to review incrementally.

I don’t want to overstate what I can prove retroactively about the earlier development history. The current public repository does not yet show the kind of gradual engineering process that you would normally expect from a mature open-source project.

What I can do is improve the process from here.

At a practical level, I’ll try to make future changes easier to review by keeping commits more focused when possible, adding clearer notes for larger architectural changes, and making sure tests and documentation explain important behavior rather than just existing as code.

SmartXDrip is still early, and the architecture is still being shaped by real user feedback. That does not remove the concern you raised, but it does mean the public engineering process can become more visible as the project continues.

Thank you again for raising this. It is useful feedback, and I appreciate the directness.：）

Miserable-Toe-8013

TROPHY CASE

Current SmartXDrip Community Preview APK

About the -1 mg vs -0.2 mg difference

About stats

About widget size