DiaBox
Open in Telegram
6 161
Subscribers
No data24 hours
-67 days
+430 days
Data loading in progress...
Similar Channels
Tags Cloud
No data
Any problems? Please refresh the page or contact our support manager.
Incoming and Outgoing Mentions
---
---
---
---
---
---
Attracting Subscribers
October '25
October '25
+5
in 0 channels
September '25
+72
in 0 channels
Get PRO
August '25
+121
in 0 channels
Get PRO
July '25
+114
in 0 channels
Get PRO
June '25
+108
in 0 channels
Get PRO
May '25
+151
in 0 channels
Get PRO
April '25
+135
in 0 channels
Get PRO
March '25
+123
in 0 channels
Get PRO
February '25
+113
in 0 channels
Get PRO
January '25
+116
in 0 channels
Get PRO
December '24
+117
in 0 channels
Get PRO
November '24
+132
in 0 channels
Get PRO
October '24
+109
in 0 channels
Get PRO
September '24
+87
in 0 channels
Get PRO
August '24
+104
in 0 channels
Get PRO
July '24
+148
in 1 channels
Get PRO
June '24
+99
in 0 channels
Get PRO
May '24
+159
in 0 channels
Get PRO
April '24
+173
in 1 channels
Get PRO
March '24
+144
in 0 channels
Get PRO
February '24
+171
in 1 channels
Get PRO
January '24
+178
in 2 channels
Get PRO
December '23
+182
in 0 channels
Get PRO
November '23
+161
in 0 channels
Get PRO
October '23
+179
in 0 channels
Get PRO
September '23
+210
in 0 channels
Get PRO
August '23
+230
in 0 channels
Get PRO
July '23
+251
in 0 channels
Get PRO
June '23
+226
in 0 channels
Get PRO
May '23
+168
in 0 channels
Get PRO
April '23
+168
in 0 channels
Get PRO
March '23
+180
in 0 channels
Get PRO
February '23
+215
in 0 channels
Get PRO
January '23
+266
in 0 channels
Get PRO
December '22
+274
in 0 channels
Get PRO
November '22
+189
in 0 channels
Get PRO
October '22
+166
in 0 channels
Get PRO
September '22
+182
in 0 channels
Get PRO
August '22
+191
in 0 channels
Get PRO
July '22
+200
in 0 channels
Get PRO
June '22
+154
in 0 channels
Get PRO
May '22
+180
in 0 channels
Get PRO
April '22
+167
in 0 channels
Get PRO
March '22
+234
in 0 channels
Get PRO
February '22
+132
in 0 channels
Get PRO
January '22
+213
in 0 channels
Get PRO
December '21
+319
in 0 channels
Get PRO
November '21
+115
in 0 channels
Get PRO
October '21
+225
in 0 channels
Get PRO
September '21
+288
in 0 channels
Get PRO
August '21
+303
in 0 channels
Get PRO
July '21
+87
in 0 channels
Get PRO
June '21
+91
in 0 channels
Get PRO
May '21
+80
in 0 channels
Get PRO
April '21
+89
in 0 channels
Get PRO
March '21
+651
in 0 channels
| Date | Subscriber Growth | Mentions | Channels | |
| 05 October | +1 | |||
| 04 October | +2 | |||
| 03 October | 0 | |||
| 02 October | +1 | |||
| 01 October | +1 |
Channel Posts
| 2 | 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 | 3 342 |
| 3 | 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 | 3 377 |
| 4 | 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 | 3 469 |
| 5 | 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 | 4 218 |
| 6 |  Or this ? | 4 074 |
| 7 |  How about use this for Glucose Display on system | 3 513 |
| 8 | Known Issues:
1– G-Watch not functioning – currently being fixed
2– Custom alarm configuration – currently being fixed
3– Android 15 interaction compatibility – currently being fixed
4– Widgets not working (2×2, 5×4) – currently being fixed
5– App fails to launch on some devices – under investigation | 3 417 |
| 9 | This is an optimized and fixed version based on 2025-04-07, primarily addressing the following:
1. Resolved Libre 2/2+ availability issues: Fixed the “sensor error” and restored Bluetooth connectivity.
2. Optimized the missed reading alert logic, especially for conflicts caused by multiple apps connecting to the same sensor.
3. Set a default 1-minute update interval for Libre 2/2+ and 3/3+ sensors — this interval is currently not adjustable.
4. Added audio prompts for initial Bluetooth connection establishment and for reconnections after long disconnections.
5. Improved the countdown strategy for Bluetooth data updates. | 2 997 |
| 10 | Users who encountered a “Sensor Error” when using Libre 2 with the latest version, please send me a private message. We are currently testing a new version to try to resolve this issue. | 3 533 |
| 11 | A quick fix version，apk file replaced
with Widget and Android 15 support test | 4 286 |
| 12 | Further Explanation About Login & Registration:
From the very beginning, DiaBox was designed to function without requiring a server, ensuring that it can continue running even if we stop development or maintenance one day. We have always upheld a decentralized approach and do not wish to store or manage any user data.
Your data should always remain on your device or any trusted location of your choosing, rather than being controlled by an external third party—including DiaBox Follow. | 4 350 |
| 13 | More Details About This Version:
1. Full support for all Libre 2/Libre 2+ types via direct Bluetooth connection, as well as support for these sensors via Bubble Nano.
2. Full support for all Libre 3/3+ types via direct Bluetooth connection, without requiring a specific region’s LibreView account. You can simply use the same account you use to log into the Libre 3 App, without any regional restrictions.
3. Login issue fixes & restoration of DiaBox Follow service. However, since most users are on the free plan, maintenance costs are high. If we cannot find a more cost-effective technical solution in the future, this feature may be discontinued.
4. Fixed an issue where some alarms could not be turned off.
5. Optimized app startup speed and overall stability.
6. Added Trend data backfill for Libre 3/3+, supporting up to 120 minutes (2 hours).
7. Modified the “Line” display mode: It now shows historical curves instead of the current value. When selecting “Line,” you will see two sets of data: Trend readings displayed as dots, and historical values displayed as a continuous line.
8. Reduced app file size.
9. Various other bug fixes. | 3 607 |
| 14 | This version has undergone a complete overhaul in sensor support and connection logic to enable support for more sensor types in the future. The main improvements include:
1 – NFC Functionality Optimization
• Faster sensor recognition and command exchange
• Automatic activation of sensors when an uninitialized sensor is detected
• Automatic activation of Bluetooth connection (Libre 2/2+ & Libre 3/3+)
2 – Bluetooth Connection Optimization
• Improved stability for a more reliable connection | 3 453 |
| 15 | Dear DiaBox Users,
We hope you’re doing well, and we want to thank you for your continued support and patience.
Recently, we’ve received some reports about DiaBox Follow being unavailable, especially regarding login issues. We sincerely apologize for the inconvenience this has caused.
After a few days of investigation, we identified the problem as a failure in the third-party login service we use. Unfortunately, fixing this requires updating the app itself, which means all previously released versions may be affected. Because of this, we will no longer be able to offer support for login issues in older versions — thank you for your understanding.
We’d also like to remind everyone that DiaBox Follow is an optional service. While only a small group of users actively use it, it does require significant maintenance on our side. For remote monitoring needs, we continue to support Nightscout, which remains a robust and reliable solution. However, Nightscout requires self-hosting or using a hosting provider.
Some users have also mentioned that even after a successful login, they still can’t get data via DiaBox Follow. From the limited logs we’ve received, this appears to be due to connectivity issues between the master device and the CGM sensor — if the master can’t get glucose readings, there’s no data to share with the follower.
We’ve recently updated the login component and improved the login process, and we’re currently testing the new version for better reliability.
We’re also working on improving the Bluetooth connectivity. While we haven’t pinpointed the exact cause, it could be related to new sensor types or complex usage environments — for instance, frequently switching apps to connect with the same sensor may cause interference.
A few users have reported issues connecting with Bubble, but we haven’t received logs yet, so we can’t investigate further. If you’re experiencing similar problems, we’d love to hear from you.
📬 To report issues, please email us at: diaboxapp@gmail.com
📄 To share log files: Settings → About → Share Log
Thank you again for your support, and we truly apologize for any inconvenience caused.
Warm regards,
The DiaBox Dev Team | 3 520 |
| 16 | 当然可以。以下是经过润色后更加友好和易于理解的中英文版本：
⸻
中文（更友好语气）
亲爱的用户朋友们：
我们最近收到一些关于 DiaBox Follow 服务无法使用的反馈，主要表现为无法登录。对此，我们深感抱歉，并感谢大家的耐心等待和持续支持。
经过几天的调查，我们发现问题出在我们使用的第三方登录组件上，该服务目前出现了故障。要解决这个问题，我们必须发布新的应用版本，也就是说，现有的旧版本都可能会遇到登录问题。为此，我们将不再对旧版本的登录问题提供单独支持，敬请理解。
需要说明的是，DiaBox Follow 一直是我们提供的一个可选服务，目前使用它的用户数量相对较少，但维护成本却不低。对于希望实现远程监测的用户，我们仍然推荐使用 Nightscout。Nightscout 是一个成熟的远程查看解决方案，但需要您自行托管或寻找托管服务商。
另外，也有部分用户反馈，在登录成功后仍无法获取到来自 DiaBox Follow 的数据。从我们收到的一些日志分析来看，问题通常是出现在主设备无法连接 CGM 设备，导致无法获取血糖数据，从而无法同步给 Follow 用户。
为了改善体验，我们最近已经更新了登录组件，优化了登录流程，并正在做最后的测试。同时，我们也在持续优化蓝牙连接部分的代码。目前尚不能完全确定连接问题的具体原因，可能是因为传感器型号发生了变化，或是在复杂的环境中使用多个 App 与传感器连接造成干扰。
还有用户提到与 Bubble 设备的连接问题，但我们暂时还未收到相关日志，所以目前无法进一步分析。如果您遇到类似问题，欢迎通过邮件联系我们，并分享您的日志文件，这对我们非常重要。
📬 反馈请发邮件至： diaboxapp@gmail.com
📄 日志分享路径： 设置 → 关于 → 分享日志
再次感谢大家对 DiaBox 的支持和理解，给您带来的不便我们深表歉意。
— DiaBox 开发团队
⸻
English (Friendly Tone)
Dear DiaBox Users,
We hope you’re doing well, and we want to thank you for your continued support and patience.
Recently, we’ve received some reports about DiaBox Follow being unavailable, especially regarding login issues. We sincerely apologize for the inconvenience this has caused.
After a few days of investigation, we identified the problem as a failure in the third-party login service we use. Unfortunately, fixing this requires updating the app itself, which means all previously released versions may be affected. Because of this, we will no longer be able to offer support for login issues in older versions — thank you for your understanding.
We’d also like to remind everyone that DiaBox Follow is an optional service. While only a small group of users actively use it, it does require significant maintenance on our side. For remote monitoring needs, we continue to support Nightscout, which remains a robust and reliable solution. However, Nightscout requires self-hosting or using a hosting provider.
Some users have also mentioned that even after a successful login, they still can’t get data via DiaBox Follow. From the limited logs we’ve received, this appears to be due to connectivity issues between the master device and the CGM sensor — if the master can’t get glucose readings, there’s no data to share with the follower.
We’ve recently updated the login component and improved the login process, and we’re currently testing the new version for better reliability.
We’re also working on improving the Bluetooth connectivity. While we haven’t pinpointed the exact cause, it could be related to new sensor types or complex usage environments — for instance, frequently switching apps to connect with the same sensor may cause interference.
A few users have reported issues connecting with Bubble, but we haven’t received logs yet, so we can’t investigate further. If you’re experiencing similar problems, we’d love to hear from you.
📬 To report issues, please email us at: diaboxapp@gmail.com
📄 To share log files: Settings → About → Share Log
Thank you again for your support, and we truly apologize for any inconvenience caused.
Warm regards,
The DiaBoxDev Team | 1 |
| 17 | Server Maintenance Notice
We are currently performing server maintenance and migration to resolve long-standing issues with login and DiaBox Follow. The maintenance is expected to last for approximately 4 hours. We will notify you in this channel once it is completed.
Additionally, a new update for DiaBox Android will be released this week, primarily addressing issues found in version 202411119, such as alarms that cannot be paused or turned off and incomplete display content on certain pages. Please refer to the next version’s changelog for detailed updates.
If you have any other bug reports, please submit them as soon as possible.
Thank you for your support and understanding. | 3 861 |
| 18 | Has anyone tried deploying Nightscout on Akash? It seems to be a very cost-effective deployment method.
#Nightscout | 2 526 |
| 19 | When providing feedback or reporting an issue, please include the following necessary information:
• Phone model
• System version
• Type of sensor used
• DiaBox version
Then, provide a detailed description of the issue, such as:
1– Unable to automatically fetch data via Bluetooth.
2– After enabling sharing with the watch, the phone updates readings automatically, but the watch does not.
etc… | 3 528 |
| 20 |  NEXT Release Widget Design | 2 807 |
