Android 14 and Libre 2: Big Tech v Big Pharma

Status
Not open for further replies.

magpie

Member
Relationship to Diabetes
Type 1
According to Abbott they don't support Android 14 yet. I couldn't even get a date out of them.
Scouring the 'net there seems to be the usual issues around alarms and scanning that come with an android upgrade.
The option not to upgrade to 14 is tricky as it looks like the rollout of 14 is being pushed quite hard by the phone manufacturers. If you've a Google pixel, for instance, it'll be hard to avoid 14 if you want any updates at all. And Samsung are sending the update out to a load of their phones this year.
So looks like little us is going to be squeezed between big tech and big pharma and have barely functioning CGMs until it gets sorted.
What's your experience of 14 and Libre?
BTW I checked out Dexcom and they don't sound any better re android 14.
 
Hello, I’m just going to hang back on an update. I have my set up exactly where I want it. A CGM that makes calls if I need to.
 
My little Libre reader will continue to work as reliably as it always does regardless of updates, without me being caught in the middle between tech and pharma titans. :D
 
My little Libre reader will continue to work as reliably as it always does regardless of updates, without me being caught in the middle between tech and pharma titans. :D
Do you need to regularly upload the data to your team this way to libreview? (Hard wired fashion.)
Librelink phone app just sends it by default.
I come from a generation that had to write this stuff down. (Pee tests or blood.) Felt like doing extra “school homework.” 🙄
 
Do you need to regularly upload the data to your team this way to libreview? (Hard wired fashion.)
Librelink phone app just sends it by default.
I come from a generation that had to write this stuff down. (Pee tests or blood.) Felt like doing extra “school homework.” 🙄
I'm another that uses the reader. It's a once a year upload for the team, and occasionally I want to take a look for myself.
 
I'm another that uses the reader. It's a once a year upload for the team, and occasionally I want to take a look for myself.
Thanks. I reasoned it was more like a “tacho” for a lorry driver? The info was overwritten after a certain length of time. (In this case with a Libre 8 hours. Unless uploaded? Or stored.)
 
I use a Pixel 6a.

I get excited by updates and look forward to them. Foolish? Maybe, but I apply all upgrades, Android or apps as soon as they become available. And I follow tech news with interest and often know the upgrade is available before it gets pushed to little ol' me, and I go get it! It got mw CGM on L2 in that brief window before it was withdrawn, and I enjoyed a couple of months before the problem (did it really exist on Android?) it was fixed.

Life on the edge?

So far, so good.

I have the same philosophy for all my devices, Apple, Linux, Android. Works for me (fingers crossed!).

The above is not a recommendation. Whatever works for you....
 
The latest I got from Pixel support (Google) was that doing the upgrade to 14 is fine, it'll all work!
It also appears to be getting harder to avoid upgrades as Google are dressing them up as security updates and not giving the option of updating an existing OS.

Clearly keeping hold of a reader (if you have one) sounds like a good idea. Being able to hold off major updates easily would be nice (I've asked Pixel support). Abbott getting around to testing/supporting updates in a timely manner would also help (I'm trying to get something more than blather out of them).
 
My new phone in a Pixel 6 running Android 14. I haven't had any issues so far but then haven't stretched the envelope in the last 28 days! Might try it... ; rofl:
 
I'm another that uses the reader. It's a once a year upload for the team, and occasionally I want to take a look for myself.
That is interesting! I was lead to believe that the reader could only store about 3 months of data, so I download it every few months when I remember, but I don't have a strict schedule. I haven't lost any data yet but curious if you have checked that you don't lose data doing it yearly. It is still not an onerous task as it is just a question of plugging it in to my PC for a few minutes and how much of that data my consultant actually looks at is debatable. I imagine he is only interested in the 3 months prior to an appointment, which I tend to do the morning of my appointment anyway.

I love my reader! Tried using an iphone and hated it, even with the full CGM. Sometimes more tech isn't always better and the software updates seem to cause major upheaval for people almost every time judging by the messages here on the forum. Reader is basic but very reliable for me.
 
Good to hear. My Pixel 6 will be on 14 soon despite Abbott's advice. I reckon we're doing their testing for them.

At various times between 1984 and 2019 I used to do software testing and almost continuously in 2012. This included writing test plans both for testing and acceptance testing. When the company I worked for folded at the start of 2013 Job Centre Minus said you had to use UniversalJobMatch. This had many issues and I wrote a report about it that I sent to the support people for the application. In response I was told if it did not work I could use traditional methods. I had to resist replying "Do you mean parchment and quill pen?" 🙂
 
That is interesting! I was lead to believe that the reader could only store about 3 months of data, so I download it every few months when I remember, but I don't have a strict schedule. I haven't lost any data yet but curious if you have checked that you don't lose data doing it yearly. It is still not an onerous task as it is just a question of plugging it in to my PC for a few minutes and how much of that data my consultant actually looks at is debatable. I imagine he is only interested in the 3 months prior to an appointment, which I tend to do the morning of my appointment anyway.

I love my reader! Tried using an iphone and hated it, even with the full CGM. Sometimes more tech isn't always better and the software updates seem to cause major upheaval for people almost every time judging by the messages here on the forum. Reader is basic but very reliable for me.
Looks like you may well be right - the Abbot site does say that a reader will store 'up to 90 days'. To be honest, whenever I've run an upload I (and I guess my HCPs) am only going to be looking at the last 3 months. So my guess would be that I have missed out on data but only stuff that nobody has wanted to look at. My last upload was actually 28 August so 90 days is tomorrow! I'll try to remember to run an upload early next week and check to see if I have a gap in data for 29 August.

I also tried using an iPhone and hated it. Downsides for me are....

My phone has links to work accounts so has to be secure. Hence I need to unlock it with security code before doing a scan. Needs far more effort than swishing a reader.
Related to first point, I both run and cycle. Faffing about unlocking phone not easy when doing either of those but the reader is fine.
Even ignoring the unlocking I found the swish more forgiving with the reader. Don't need to be so precise with getting it lined up correctly.
 
Even ignoring the unlocking I found the swish more forgiving with the reader.
Yes, the reader is easier in that way. Now that they've updated the software, there's not normally a need to scan with the phone at all, though, so there's less need to unlock the phones. (Still need to unlock to look at the graph and maybe the results at all. Though with modern phone that's usually done with a fingerprint reader or something rather than a security code.)
 
Related to first point, I both run and cycle. Faffing about unlocking phone not easy when doing either of those but the reader is fine.
XDrip+ & Garmin (headunit & watch) ftw in that case!
 
XDrip+ & Garmin (headunit & watch) ftw in that case!
Indeed. Come the time to replace current phone and the old running watch I'll definitely be checking out the situation. I've currently got a Forerunner 40 which (I think) isn't flash enough to support XDrip. Have to say I hate the idea of splashing out a load of cash purely to get that functionality but have to see what's available when the time comes.
 
You're right, it doesn't support the datafield I use at least: https://apps.garmin.com/en-US/apps/5a3e2cda-12f0-4afd-88ed-000e67a68d84
There are cheaper options than splashing out on a Fenix 7 though. As a cyclist I find the data useful and I needed a headunit so getting a Garmin which had the ability to show BG was a no-brainer (Do you use a headunit to track rides? This is the thin end of the wedge, but now isn't a bad time to buy).

I also already had a Garmin watch, having been interested in data monitoring (for potential use in working out how it affected my diabetes) for a long while (I was sad when my Basis Peak was discontinued after Intel bought the company and apparently did nothing with it.)

Sorry I've gone off topic!
 
I have a Pixel 7 Pro, and as soon as it upgraded to Android 14 my connectivity to my sensor by Bluetooth has been carnage. It drops out multiple times per day. The only process I've found which seems to work is: turn bluetooth off, uninstall LibreLink, reboot, reinstall LibreLink, turn bluetooth back on and then scan. I don't have time for this! Has anyone got any tips or advice? TIA x
 
As I have stated before, I have a Pixel 6a, and have had NO problems at all. Wish I hadn't said that! So the combination (more or less) is OK.

A rather drastic suggestion would be a factory reset. Install LL but absolutely nothing else and see how that goes. That would test the phone, android 14, and LL, with no other apps, data or config conflict.

edit: typo
 
Last edited:
This morning I got a message "Alarms unavailable" and before my insulin cut in the FORD factor cut in and I got a "High glucose" alarm. Go figure! :( Obviously unstable!
 
Status
Not open for further replies.
Back
Top