How about use this for Glucose Display on system

Or this ?

DiaBox Android 20250430 Release

1.Fix frequent crash exceptions
2.Fix UI display issues on Android 15
3.Add voice broadcast after completion, followed by an alarm
4.Add Libre2 countdown timer
5.Add Display on System
6.Fix Widget for 5*4/5*3
7. Fix Notification Snooze
8.Add Custom Alarm Tone Option
9.Fix Subscription Plan Erorr
10.Improve Log in

The current version of DiaBox Android (20250430) has the following known issues:
1. Frequent crashes on some Android 15 devices – Due to the wide range of Android devices and system variations, we are still investigating these issues. Reported affected devices so far include:
• S25 — Android 15
• Pixel 8/9 — Android 15
We have conducted simulation testing on Pixel 7 Pro and OnePlus 8T (LineageOS 22) and have not encountered the issue on those devices.
2. Crash when enabling “Glucose Display On System” on Android 15 devices – This issue has been identified and fixed. The fix will be included in the next version.
3. Magic Link Expired – This issue has been reported by some users and prevents successful login. We are currently investigating the root cause.
4. Alarm feature not functioning properly under some settings – This feature will be restructured in an upcoming version.
5. Garmin/G-Watch integration not working for some users – This issue is still under investigation. Most users have reported the feature working as expected.

If you wish to report a bug or request a feature, please use the tags #BugReport or #FeatureRequest, and provide as much detail as possible. Incomplete or unclear reports may be ignored.

DiaBox remains an actively evolving project. We prioritize development and releases based on usability and stability.

Regard

----DiaBoxDevTeam

DiaBox Android 20250520 Release

1.Fix the Android 15 file write permission request exception bug
2.Fixed a login-related exception
3.Add handling for pausing notification alerts
4.Fix Alarm setting Bug
5.Fix the crash bug

Please kindly follow some basic guidelines when submitting issues:

First, it’s best to post messages in English; otherwise, we may not be able to respond promptly.

Second, please include log information whenever possible, as it helps us locate and identify the issue more efficiently.
Third, avoid posting duplicate messages. If your issue hasn’t received a response, try providing more details—such as logs or steps to reproduce the problem—or contact us directly via email:

diaboxapp@gmail.com

Anyone testers want to try new version ,pm pls

Phil is answering everyone’s questions purely out of goodwill, as I’m usually busy writing code. Some of the questions being asked are actually issues that have already been discussed many times before. I will compile a list of frequently asked questions here and pin it, but please understand that not every user will read it.


---

Q1: How can I download DiaBox on iOS?

A1: DiaBox is currently not available on iOS, and there are no plans to support iOS in the future. Although there have been some experimental feature integrations (such as Libre 3), there is no release plan or testing plan.
The reason is that, due to complaints from Abbott, Apple removed the app for violating App Store policies. Distributing the app outside the App Store or TestFlight comes with significant obstacles and would generate a large volume of support requests, far beyond our capacity.


---

Q2: Can Libre 1 / 2 / 3 be restarted?

A2: No. Libre 1 used to be restartable, but Libre 1 sensors manufactured after April 2025 can no longer be restarted.
For Libre 2 / 2+ / 3 / 3+, there are currently no restart methods and no ongoing research in this area.


---

Q3: Which sensors are currently supported?

A3:

Libre 1

Libre 2 / Libre 2+ (ID 310 is implemented but not yet released)

Libre 3 / Libre 3+



---

Q4: What Android versions are supported?

A4: Android 8.0 to Android 15.
Android 15 is only partially supported in the version released this past May. The upcoming release will support Android 16, and Android 17 will be supported after its official release.


---

Q5: Will more sensors or transmitters be supported?

A5: Currently, the only supported third-party transmitter is the Bubble series, as the DiaBox project received significant early support from the Bubble Dev Team. There are no plans to support other third-party transmitters. DiaBox believes that as more real-time CGM systems become available, such accessories will become unnecessary.

As for additional sensor brands: we are currently testing support for LinX, and it appears that restarting may be possible. There are no plans for other brands at this time.


---

Q6: Will more smartwatches be supported?

A6: In reality, this functionality is almost identical to what xDrip+ already provides. We are reconsidering whether it’s necessary, as many users prefer using DiaBox together with xDrip+ for data contribution and then rely on xDrip+ for smartwatch connectivity. Duplicating this code doesn’t seem very meaningful.


---

Q7: Will the project source code be released?

A7: No. This involves legal and patent-related issues.


---

Finally, this project is currently largely a personal hobby. I’m not trying to create uncertainty for users, but as commercial companies impose increasingly strict limitations on data access, we need to seriously consider what it really means to stand on the opposite side of that trend.

​🚀 DiaBox Android 20251229 Release Candidate
​What's New:
​✅ Libre 2+ Support
​Added full support for Libre 2+ (Model 310).
​⌚️ Expanded Hardware Compatibility
​Support added for AiDex LinX, DiaExpert, and LumiFlex.
​Includes Sensor Reset functionality.
​⚠️ Note: Initial testing indicates a significant drop in accuracy after sensor restarts. Calibration features are currently in development and not yet available.
​🤖 Android 16 Support
​Compatibility added for Android 16.
​Note: Compatibility with Samsung OneUI (Android 16) is currently untested.
​💾 Offline Backup & Restore
​Backup/Restore functionality is no longer tied to your account. You can now safeguard your data without needing to log in.
​🛠 Bug Fixes
​Resolved DiaBox Magic login issues.
​General stability improvements and minor bug fixes.

​It seems that the support for AiDex has stepped on some toes. I want to emphasize that DiaBox is strictly a personal passion project with no commercial interests. While there is a paid subscription for DiaBox Follow, it exists solely to cover maintenance costs—and even then, it doesn't operate at a scale that actually breaks even. This is precisely why functions like backup and recovery are designed to run entirely offline.
​Furthermore, DiaBox does not employ heavy code obfuscation or protection. This is a "door" left open in good faith (in fact, we could open it much wider by making certain instructions completely public). Therefore, those attempting to crack DiaBox as a form of retaliation can stop; it won't hurt DiaBox, it will only hurt the users.

Please do not ask any further questions about Libre restarts. As of now, only Libre Pro/H can be reset. Restart vulnerabilities in other Libre versions have already been patched and disabled by Abbott through firmware updates and are no longer available.

Waiting for public release with calibration feature for AiDex

Tester Recruitment:

What’s in store:
• Android 16 compatibility — can your device survive the upgrade?
• Libre 2 / 2+ EU support — let’s see those sensors play nice.
• LumiFlex / DiaExpert / LinX — connection, calibration, and yes… the mysterious reset!

Come join the fun and help us make DiaBox even smarter.

LinX tester slots are full — now recruiting Libre 2 / 2+ EU testers.

Based on the limited test reports we have received, the following issues have already been resolved:
1. Bluetooth connection failures caused by Nearby Device permissions
2. AiDex / LinX connection, calibration, and reset
3. Multilingual support (still with a few incomplete elements)
4. Some interaction issues: UI-layer faults causing alerts not to be silenced, and silent actions in the notification bar being ineffective
5. Adjustments for special sensor features, including reset, restart, and calibration

Currently, there has been very little feedback from participants. After the initial tests, only a few people submitted reports, which have been validated through multiple version updates. We sincerely thank these contributors — they will soon receive a release candidate version.

A confusing situation:

Some LinX distributors keep messaging us to ask about the release dates for LinX-supported versions, while others are demanding that we stop releasing software with LinX support, or at least not support the Chinese and Russian versions.

We still do not understand these motivations and demands. As mentioned in the previous message, we are not responsible for these commercial organizations or their actions, nor do we have any connection with them.