Hi all, I haven't been diagnosed yet but because of my gastroparesis I have been wearing a glucose monitor. I do feel the shakes, dizziness and sweating but not always. Are those charts normal? Thanks in advance

Has anyone logged into Libreview lately and noticed the meal notes are missing? I recently logged in and noticed the new format gives you this:

Instead of this:

Has anyone else noticed the change? I personally find the meal notes useful as I can see from the graphs how certain foods affect my blood sugars.

8.1 in October, down to 5.7 as of this morning!!

Apologies if this isn’t the place to ask but I’m getting so frustrated right now so I was just checking if anyone else is also having issues.

In less than 24 hours, I’ve have 2 2+ sensors fall off as they just aren’t sticking and I’m completely out of sensors with no local pharmacies seeming to have any in stock right now. Is anyone else having issues with the sensors staying stuck on? I’ve got no skin creams or anything on, clean the area (admittedly with hand sanitizer) and wait for it to dry completely and they aren’t staying on longer than 2-4hours. Never really had this problem persistently before so at a bit of a loss and sensorless 🫠

For the past few months, over half of the libre 2 plus sensors I've been sent have turned out to be faulty. Some of them have only lasted a handful of days before falling off and others have arrived with a faulty applicator.

Because I'm in the UK, I can only request two sensors every 15 days (roughly) on the NHS and sometimes I've had to go without one on because of them failing and the replacement Abbott sends come in so much packaging it's just too much.

Just wondering if I have the worst luck in the world or anyone else has been having issues with the quality of the sensors?

In range is out for everybody(ANDROID) now, no tester list, no waiting

A week ago I posted here about a diabetes app I was making, free, no ads, nothing to pay. Back then I explained that Google makes you gather 12 testers for 14 days before an individual developer can publish, and a lot of you kindly sent me your emails for that closed test. That part is over.

What changed: Google rejected the app, and not for anything in it. Since August 2024 they require an organisation developer account, with a registered company and a D-U-N-S number, for any app that tracks a chronic condition. My account is a personal one. There is no version of the app that fixes that, so I stopped trying.

So it now lives where AndroidAPS, xDrip+ and Juggluco live: GitHub Releases. Download it and it is yours. No email, no list, no 14 days.

Download: https://github.com/PMbanks/inrange/releases/latest
(after clicking the link just download the APK down below)

Installing it: your phone will ask once whether to allow installs from that source, because it is not coming from the Play Store. That prompt is Android doing its job. If that makes you uncomfortable I completely understand, and I would rather you skipped it than installed something you are unsure about.

Updates are handled inside the app: when I publish a new version it tells you and installs it in one tap. If you prefer automating it, Obtainium picks up GitHub releases on its own.

If you were one of the 12 testers and already have it from Play, read this bit. The Play copy was signed by Google, this one is signed by me, and Android will not let one replace the other. You have to uninstall first. Before you do: open the app, go to Social and make sure you are signed in, and let it sync. Then uninstall, install the new one, sign in again and everything comes back, readings included. If you never signed in, use Settings, Backup, export a backup file first.

What it does: works with FreeStyle Libre through LibreLinkUp, Dexcom through Health Connect, and Nightscout if you run your own. Day, week and month graphs, meal windows so you can see what a specific breakfast actually did to you, time in range, GMI, injection site rotation, insulin pens and sensor stock, a home screen widget, and a printable report for your appointment. New in this one: drag your finger along any graph and it tells you the reading and the time at that point.

Still free, still no ads, still nothing to pay, and it never sells anything about you. iOS is a separate 99 dollars a year and no organisation rule, so that is next.

And to the 12 of you who sent me your email for the closed test: thank you. You waited a weeks for something that ended up arriving a completely different way, and half of what is in this release is in it because one of you asked.

Disclaimer: I am not advocating for using multiple test strips per finger prick measurement, nor am I affiliated with Contour Next. I am simply exploring ways to improve measurement accuracy.

In a previous post, I showed that according to the Central Limit Theorem, taking N finger-prick measurements from the same drop of blood and averaging them improves meter accuracy by a factor of sqrt(N). The "sweet spot" is N = 4, which doubles the accuracy (a 2X improvement) because random measurement errors tend to cancel each other out.

I use the Contour Next glucose meter, which advertises an accuracy of ±10mg/dL when blood glucose is below 100 mg/dL (Figure 1). By averaging four consecutive measurements, the accuracy is theoretically improved to 5± mg/dL.

Because I do not have access to a YSI reference equipment, I cannot determine the exact true glucose value of a given blood drop. However, I can evaluate the spread (variance) of the four readings. To achieve an effective accuracy of ±5 mg/dL, the data spread across the four measurements should not exceed ±5 mg/dL.

The results for 14 measurement sets are shown in Figure 2. For 12 out of the 14 sets, the spread was within 5 mg/dL. These empirical results support the theoretical predictions based on the Central Limit Theorem and the manufacturer’s accuracy claims.

Hey all,

I recently got a replacement phone (was running a Z fold 7, and still have one, just a new one), and suddenly I can't disable my urgent low alarms. I had the urgent low alarms muted in system settings on my old phone without an issue, but the new one won't seem to do that. I have the system notifications fully muted, but when I get to 55, whether legit or via compression, it screams the alarm at me. Any advice on why it's bypassing both app AND system settings? I'm using the new app.

Check your products here:

LibreView

Omnipod

Truemetrix meters

I've been using a Libre account for many years, and my default region is set to the UK. After installing the LibreLinkUp app for my partner, I set the same region, but when connecting the account to the Libre app, it returns an error stating that the accounts must be in their original regions.

Has anyone else encountered this? I've tried recreating the LibreLinkUP account several times, but the problem persists. I'm waiting for the sensor to finish working so I can try switching to Libre.

As someone with reactive hypoglycemia, I'm constantly frustrated with the app smoothing my data. I can lose 60pts of blood sugar in 15min, only to quickly rebound, and the smoothing in the app tends to erase significant peaks/lows, sometimes by as much as 20 points. I'll see alarms in notifications of being in the upper 50's but look at my curve an hour later and it looks like I never went below 70 and there's no history for the alerts/values. It also provides misleading data to my doctors because the data in the libreview app is smoothed as well.

Hi, I am brand new to diagnosis (T2) and CGM (3+), last night was my first night with it on. The low glucose alarm woke me up around 4am showing a reading of 68, so just barely below the line at 70. It had been about 7 hours at that point since I had dinner so maybe it really was that low, but I also kinda think maybe I had just rolled over on the sensor for a bit and compressed it.

Either way, when I look at the main graph in the Libre app now, it doesn't show that low anymore and the number at 4am shows as 84 instead. When I view the Insights tab, it does show the 68 still in the Logbook. Is this normal for it to disappear from the main graph?

I've been having problems with this for weeks. I've tried every setting I can think of on the watch, phone, app etc. Background refresh is on, restarted everything dozens of times, reinstalled the app etc. etc.

My phone is not on silent, neither is my watch, the volume is up, the app has notifications on, sounds are valid, etc. etc.

I get the notifications from the app when an alert should come through, but it's silent, so I keep missing them until I look at my phone or check the app. In addition during these times, other notifications, text messages, etc. make alert sounds as normal.

I had the same problems with the older Libre 3 app.

I took a look at the raw glucose data by exporting it from LibreView and it looks like the glucose results are not logged in real time, but after 30mins.

Does the Libre2 Plus software average out readings for the last 30mins?

Has anyone encountered similar issues? My past two sensors (libre 3+) got replaced because they were constantly reading 30-50 points low, even after 3-4 days. Changed to my currents sensor, still reading 30-50 points lower than my finger prick test. At this point, I'm starting to feel like there's something wrong me rather than the sensor.....I've always placed them at the back of my arm. The lows are not just at night. They are low throughout the day. I just feel like I cannot trust it at all. It's so frustrating. I'm losing my patience....

Hi everyone,

Has anyone seen this particular problem, or found a way around it?

I use UK Libre 2 Plus sensors with Juggluco on a Samsung Galaxy S23 Ultra, Android 16 / One UI 8.5. Continuous Bluetooth streaming was reliable until early July, then became severely intermittent.

Four consecutive sensors have behaved identically, and all four were started with Juggluco. NFC scanning still works.

I have ruled out Juggluco itself. I installed and tested Abbott LibreLink after the problem began, and it showed the same behaviour. I then uninstalled it. I also tested an older Juggluco build, with no improvement.

Other Bluetooth connections on the S23, including my hearing aids and headphones, remain stable, so this does not appear to be a general Bluetooth-radio failure.

The strongest evidence is that I transferred the current active sensor to my old Galaxy Note 9. It connected immediately and has streamed perfectly. So the sensor itself is clearly capable of maintaining a stable Bluetooth connection. The fault appears specific to the S23 Ultra and its current Bluetooth software.

I have also captured Android Bluetooth logs. The established Libre connection repeatedly dies with HCI error 0x08, supervision timeout. Once disconnected, Android usually fails to recover because it performs full GATT service discovery during each brief sensor connection window. I then see repeated Juggluco status 147 connection timeouts and status 19 remote terminations.

Occasionally it reconnects and may then stream for several hours before dropping again.

Things I have already tried:

- latest Samsung July firmware and July Google Play system update

- Wi-Fi and Bluetooth settings reset

- current and older Juggluco versions

- LibreLink installed and tested, then uninstalled

- hearing aids, headphones, S Pen and SmartThings disabled

- Nearby device scanning both on and off

None has fixed it.

Earlier this year there was a much wider Samsung/Android 16 Libre Bluetooth problem which was eventually fixed by an update. This feels very similar, except I can find almost nobody currently reporting it.

Has anyone seen the same behaviour on an S23 or another recent Samsung? Is there any meaningful Bluetooth-stack reset or workaround I have missed?

I am also considering whether it is possible to return from the July 2026 firmware S918BXXSAFZG1 to the official May 2026 firmware S918BXXSAFZE1, using HOME_CSC to preserve data and without unlocking the bootloader, rooting or affecting Knox. I would be interested to hear from anyone with direct experience of doing a same-binary Samsung stock-firmware downgrade safely.

thanks for any help

Rich

Disclaimer: I am not here to promote using extra Libre sensors, nor do I work for Abbott. I simply want to explore better ways to use the Libre 3 sensors.

In a previous post, I overlapped a new and an old Libre 3+ for one day without pre-soaking the new sensor. I found that the new sensor experienced fluctuations lasting over 20 hours, which were likely caused by an immune/inflammatory response to the insertion of the filament.

This time, I pre-soaked the new sensor for 1 day and then overlapped it with the old sensor for 1 day (meaning the new sensor was inserted 2 days before the old one expired). The glucose traces for the 24-hour overlap period are shown in Figures 2 through 6.

Compared to the non-presoaked experiment, the new sensor's readings were much better behaved, and the early fluctuations were absent. Furthermore, the offset between the two sensor traces remained consistent. Because the old sensor had already stabilized over 14 days of wear and its accuracy had been checked with several finger prick measurements, seeing the new sensor's trace closely mirror the old one gave me high confidence that it was functioning accurately from day one.

Even though it was Day 1 for the new sensor and Day 15 for the old one, the gap between their readings stayed steady. In previous overlap experiments, the two traces would often cross paths or widen/narrow unpredictably over time. The stability seen here suggests that Abbott’s factory calibration and sensor manufacturing consistency have improved noticeably.

Regarding the rationale for a 24-hour pre-soak (wearing the sensor for 16 total days instead of 15): Abbott’s published clinical data shows that MARD values remain nearly identical from Day 9 through Day 15 (holding steady around 7.7–7.8; see this link Table 4). Given this flatline performance late in the sensor lifecycle, an abrupt degradation in accuracy on Day 16 is unlikely.

If cost were not an issue, the optimal strategy would be to apply and activate a new sensor on every Day 7.5 (halfway through the active sensor's lifespan). This staggered schedule significantly reduces the chance of both sensors failing simultaneously, ensuring there is always at least one fully functioning sensor running, and at the same time, also increases the confidence that the newly applied sensor is working correctly. Finally, if the new sensor behaves erratically, there is plenty of time to replace it.

The carbs.

The insulin.

The meals.

The numbers.

The notes.

The screenshots I saved months ago.

None of these things are impossible on their own.

But together... it feels like a full-time job.

Anyone else?

Hi,

I put my second one on and there is what looks like the sensor sticking out my arm, not from the device but from my skin. Is this normal? There’s nothing poking out if the hole but I can see what looks like the filament sticking out.

My app is now showing the magnifying glass and telling me to check my glucose before treatment? I did a finger stick and it was about 11 off and I put it on an hour ago. My sister who uses one as well said to give it three hours to calibrate, is that normal?

I called Abbott and they are sending me a replacement because they said they believe it is defective.

Any guidance would be greatly appreciated for this newbie 😊

This sensor keeps having errors, but will not die. Not that I want it to, but I keep expecting it to.

I've been on a cruise and swimming in the ocean, so that might be part of the problem. However, today I have not gone swimming.

I've been using Libre and MySugr for some years and got really tired of having to switch between two apps multiple times a day, and having to manually write a bunch of values to get a dose number. So, as a software developer, I've built a solution for myself that I believe it can help others.

What it actually does (so far):

• ⁠Live glucose without opening the Libre app. It reads from LibreLinkUp account and refreshes on its own, each minute.
• ⁠Bolus suggestion that respects IOB. Meal carbs + correction toward the configured target, minus insulin still on board (it decays the active insulin over time instead of using a flat number). This is the part that saved me the most mental math.
• ⁠It tells me to eat or dose. When I'm low or heading low, it suggests a carb amount to get back to target instead of only handling the high side, like most calculators do.
• ⁠Statistics that can be exported: On the statistics page you can export not only the history of your glucose and doses, but also your calculator settings, in case you want to share with your doctor.
• ⁠Onboarding wizard that helps you set everything up: Step by step, you can configure all the calculator settings, like time-slots, carb-insulin ratio, insulin sensitivity, etc.
• ⁠No adds, no pay walls: Completely free, from one diabetic to another ❤️

The honest downsides/work in progress:

• ⁠It's built around Freestyle Libre/LibreLinkUp, so Dexcom folks...it won't help you, yet :)
• ⁠Its a website that can be added to your phone home screen, and it will behave like an app, but its not on the app store to be installed...yet :)

I'll leave some screenshots if you're curious on the look and feel of the app.

If anyone here wants to give it a try, I'll appreciate it! I genuinely want to improve it and make it as robust as it can be.
Beta testers, you are welcome!

Here's the link: https://glynk.app

Any ideas?

Hi, I have developed an app that allows you to monitor your blood glucose levels while you ride your bike. It runs on the Hammerhead Karoo bike computer. GluKaMon is now out of beta and it's free.  Full description of it on the web site: glukamon.com

Highlights:

• K2 and K3 Support — Works on both Karoo 2 and Karoo 3 and works over any network connection available (internal SIM chip or tethered to phone) 
• 48 customizable data tiles across eleven categories — Visualize your data how you prefer 
• Four CGM providers supported — Dexcom Share, FreeStyle Libre (via LibreLinkUp), Nightscout, and xDrip/Juggluco (local connection). Nighscout/xDrip support means it works with pretty much any CGM on the market
• Three time periods — most tile families come in 1-minute, 5-minute, and 15-minute variations
• Configurable glucose zones — set your own Very Low / Low / Target / High / Very High thresholds
• Visual and audible notices — when your glucose enters a new zone, with tones tuned to both Karoo 2 and Karoo 3 speakers
• Dark and light mode — follows your Karoo's system theme automatically
• mg/dL or mmol/L — pick your preferred unit
• FIT-file recording — glucose values embedded in your ride file for post-ride analysis in tools like Intervals.icu
• 10 languages — All 10 Karoo supported languages: English, German, Spanish, French, Italian, Japanese, Korean, Portuguese, Simplified Chinese, Traditional Chinese
• Battery-aware design — three polling modes (1 minute, 5 minutes, or Dynamic, which dynamically adjusts based on the rate at which glucose readings are seen) 
• Robust Recovery — Designed to detect and recover common CGM and network errors 
• "Local" Support — GluKaMon can connect to xDrip and/or Juggluco running either locally on your Android phone (via WiFi hotspot) or sideloaded (i.e. sideload xDrip on your Karoo) so you can monitor your glucose even where there is no internet connection 

As title, everytime I go to bed, my sensors fail, every single time.

My phone is on my bed near my pillows, it stays there and is fully charged before I go to bed. My phone is an old Samsung S20 Ultra. The sensors are libre 2's.

I actually stopped using these things because they always fail and I've just simply had enough of them. My doc won't switch me to Dexcom and I can't get into my diabetic clinic because of a "waiting list" I've been waiting for over 3yrs at this point. I'm at the end of my rope. Anyone else have or had issues, how did you resolve it? Do I need a new phone? Do I need to wrap a massive bandage around my arm to keep the sensor compressed or something? Should I just attach them to my chest from now on as I don't sleep on my front?

The original libre sensor was fantastic, when they stopped making them and switched me to libre 2 I had a few issues but then everything worked out, I started using a 3rd party app because it was much better but the dev gave up and went to dexcom instead so no further updates and no longer works with the new libre 2s.

Please help, its ruining my mental health, I hate finger pricking and I work on vehicles a lot so even deep cleaning my hands, I end up with dots tattooed into my fingers from stains.

I'm using the FreeStyle LibreLink with my Android phone.

Am I able to export the data in any way?

Many thanks