I just started using a Libre 2 a couple of weeks ago, and initially loved it. When I switched to a new sensor for the first time, the Signal Lost Alarms became practically nonstop and I have no idea how to "clear" the red warning once it occurs (Scanning doesn't help.). I've call Libre Support 3 time and am convinced that I would be better off if I were simply allowed to read through the script/flowchart being attempted by the "agent" for myself. I finally convinced them to send a new sensor -- in 3 to 5 business days. I raised hell and they agreed to send it overnight -- for 3-day delivery.
Something has got to give. Dealing with diabetes is a life-and-death matter and if they can't build devices that can keep a simple Bluetooth connection alive, they shouldn't be allowed in the market.
Sorry to hear about the problems you're having @Deadeye_Pete.Just started using the Libre 2 yesterday. I'm getting multiple loss of signal issues already. This is a big issue for me since I have low hypo awareness.
I was using the Dexcom G6, but that is now only supported in my area (Shropshire) for insulin pump users, so I was put onto L2 because it has alarms.
It also has a lot of quality of life issues compared with Dexcom, too.
I'm not saying the Dexcom was perfect, but it kept a good connection between sensor & phone. Unless I wandered away from my phone...
Just started using the Libre 2 yesterday. I'm getting multiple loss of signal issues already. This is a big issue for me since I have low hypo awareness.
I was using the Dexcom G6, but that is now only supported in my area (Shropshire) for insulin pump users, so I was put onto L2 because it has alarms.
It also has a lot of quality of life issues compared with Dexcom, too.
I'm not saying the Dexcom was perfect, but it kept a good connection between sensor & phone. Unless I wandered away from my phone...
The Libre 2 is a dangerous medical product, and Abbott's response is to lie and obfuscate but never to provide any kind of solution. Your sentiments echo mine (see Alastair Gordon posting below). Just the fact that you cannot go back to an earlier version of the app before this horror show started is an abomination.There are many people who are also experiencing identical problems on both Android phones and iPhones, if other forums are anything to go by.
My phone isn't on the list of "official" smartphones listed as compatible with Libre 2 and Librelink. However, if you go into the Freestyle Librelink app on Google Play store using your smartphone, there is a section that tells you whether the Librelink app is compatible with your mobile. It says mine is.
I've checked my phone using the diagnostic tools provided by my mobile manufacturer. According to those diagnostic tools there is nothing wrong with my phone and particularly its near field communication and low energy bluetooth, both of which are working "normally."
My Android phone's operating system upgraded itself from 12 to 13 in the last 5 weeks. I don't have a problem with that. When you buy a new mobile you pay for operating system updates and security patches for a period of time which are supposed to make your mobile more "stable," more secure and less prone to being hacked. Google and mobile phone manufacturers are entitled to update their mobile operating systems and phones.
Around 15 November 2022 Abbott put in Google Play store its first update to Freestyle Librelink. The primary purpose of the update was to allow the smart insulin pens Novopen 6 and Novopen Echo Plus to communicate with Librelink, but also to fix some bugs in Librelink.
My phone downloaded and installed that update. Since then the high and low glucose alarms don't work on my phone. Neither does the signal loss alarm. And my phone now registers constant false "scan errors."
Thankfully I am not hypo unaware. But what are you supposed to do if you are hypo unaware, you've gone to sleep and you are relying on Freestyle Libre 2 sensors and the Librelink app to issue an alarm to wake you (or a partner/friend/carer) up so you are alerted to your sugars potentially going low, so you can double check and have a fighting chance to do something about it?
I've contacted Abbott Customer Services on many occasions and gone through their checklist of things to try (all permissions allowed; turn all alarms off and on again; delete cache; restart phone; uninstall and reinstall Librelink; Abbott sending out replacement sensors on the basis that the sensor you're wearing is faulty). None of these "solutions" has solved the problem permanently.
Abbott put out a further update around 1 December 2022 which was supposed to fix the issues caused by the first update. But the second update still hasn't fixed the problem on my phone permanently.
There's a limit to the number of times I'm prepared to turn my mobile phone on and off again each day to make Librelink work properly.
I don't want to carry around a separate reader in order to get alarms. I remember when Abbott first began promoting the Libre 2 in the UK. At that time they were proactively encouraging users that everything could be done on one's smartphone using their Librelink app.
This issue has been going on for the best part of 6 weeks now and Abbott don't appear to be any closer to sorting the problems with Librelink out permanently for a number of users.
For me Libre 2 is unfit for purpose at present.
It is monumentally stupid that there isn't a simple process where you can simply remove the updates so that Librelink is put back to the state it was in before the original upgrade issued in mid November 2022.
It also extraordinarily disappointing no one in the NHS appears to be liaising with Abbott to encourage them to sort this problem out asap. Being able to get replacement Libre 2 sensors isn't enough.
The Dexcom people must be rubbing their hands with glee though (notwithstanding that apparently the number of prescriptions for non-Abbott glucose monitors in England is reported to be comparatively very small since NICE updated its glucose monitor eligibility guidance in April 2022 and there was some "umbrella" guidance/edict issued by NHS England in August 2022 allowing a wider number of flash and/or continuous glucose monitors to be prescribed - which most integrated care boards/integrated care systems have either ignored or been tortoise-like in implementing).
It will be interesting to see how long it takes Abbott to fix this mess and how many customers they will lose in the meantime.
Reinstalling does not just lose your 90-day history, it also trashes your $100 sensor with whatever life it had left on it. Worst of all, it does nothing to solve the loss-of-signal and loss-of-alarm problem.Mine does this too. Solution suggested is remove app and reinstall! Some folk have said this worked for them, but you lose the 90 day history on the phone, which I'm not prepared to do at the moment,
All data is secure on LibreView server though, assuming you are using it.
Hmm, I’m not sure about that. I’ve certainly ‘added’ another phone/app to an existing sensor, which is what is happening if you do a fresh install. Hoever the fact that you quote “$100” I am assuming you are in the US, and I know your sensors used to be different over there so you may be correct for those.Reinstalling does not just lose your 90-day history, it also trashes your $100 sensor with whatever life it had left on it. Worst of all, it does nothing to solve the loss-of-signal and loss-of-alarm problem.
Interesting, thank you. I am in Canada where I yesterday saw the Libre 2 sensors on sale for C$139 (roughly US$115). If I do a fresh install, the current sensor is trashed and the loss-of-signal error persists. So more useless and expensive advice from Abbott. I appreciate your suggestion of trying Juggluco. I will do that and get back to you.Hmm, I’m not sure about that. I’ve certainly ‘added’ another phone/app to an existing sensor, which is what is happening if you do a fresh install. Hoever the fact that you quote “$100” I am assuming you are in the US, and I know your sensors used to be different over there so you may be correct for those.
Edit: To add suggestion
In order to recover functionality you need, you might want to consider a third party app like Juggluco (on Play Store). Runs along side LL if required or will update LV directly. Seems more robust generally. Much more low level control in the app. For example if you leave the phone out of range it will alert you, and usually reconnect when back in range. Some times it takes a few minutes, and others can be stubborn. If you are impatient you can tell the app to ‘forget’ the sensor and ‘re-ebable’ to connect again.
You shouldn’t have to go to these lengths but…..
I downloaded and installed Juggluco on my Samsung S21 Android phone. It is able to read the Libre 2 sensor by direct NFC scanning, but the app is very crude and it seems impossible to set up alarm limits, so I’m no further ahead. I let Juggluco add the end date of the sensor to my Google Calendar (nice feature), but now it opens my calendar every time I open Juggluco, and I cannot get around it. Maybe I am not finding the magic, but it seems very crude.Interesting, thank you. I am in Canada where I yesterday saw the Libre 2 sensors on sale for C$139 (roughly US$115). If I do a fresh install, the current sensor is trashed and the loss-of-signal error persists. So more useless and expensive advice from Abbott. I appreciate your suggestion of trying Juggluco. I will do that and get back to you.
Thank you for the suggestion. I downloaded and installed Juggluco on my Samsung S21 Android phone. It is able to read the Libre 2 sensor by direct NFC scanning, but the app is very crude and it seems impossible to set up alarm limits, so I’m no further ahead. I let Juggluco add the end date of the sensor to my Google Calendar (nice feature), but now it opens my calendar every time I open Juggluco, and I cannot get around it. Maybe I am not finding the magic, but it seems very crude.Hmm, I’m not sure about that. I’ve certainly ‘added’ another phone/app to an existing sensor, which is what is happening if you do a fresh install. Hoever the fact that you quote “$100” I am assuming you are in the US, and I know your sensors used to be different over there so you may be correct for those.
Edit: To add suggestion
In order to recover functionality you need, you might want to consider a third party app like Juggluco (on Play Store). Runs along side LL if required or will update LV directly. Seems more robust generally. Much more low level control in the app. For example if you leave the phone out of range it will alert you, and usually reconnect when back in range. Some times it takes a few minutes, and others can be stubborn. If you are impatient you can tell the app to ‘forget’ the sensor and ‘re-ebable’ to connect again.
You shouldn’t have to go to these lengths but…..
Of course I have done all the things you suggested and more. When Libre 2 works (increasingly rare) it is perfect, as per my configuration. But no amount of “digging” can correct the endless Bluetooth signal failures, and hours spent with support agents likewise produces no happiness. Remember that this problem started with the last app software update, so the problem lies exclusively with Abbott and blaming the user is a fool’s errand.It is a fairly basic interface certainly, but highly configurable - just what you’d expect from a techy with no ‘user’ validation of the useability.
However, alarms are configureable for BG level, sound, length of alarm ring, and finally at what time to nudge you again if still out of range.
In the most polite way, can I suggest you spend a bit of time digging in the app, reading the ‘help’ and online docs although I would agree they are not wholy user friendly.
Happy exploring - it will be worth it!
Tried removing the Samsung S21 Android phone from its case, and the LibreLink app still has the alarm condition "Alarms are unavailable. Scan Sensor". Nothing so far has resolved this fatal error, not even the string of lies and nonsense that came from Abbot's technical support agents.I think I read somewhere of Bluetooth connection problems disappearing when the phone was removed from a case.
I know it shouldn't make a difference, might be worth trying though
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?