Hi everyone. Like many others using Libre 2, my 'High and Low' alarms stopped working in late November 2022 and for many months continued not to work until Abbot rolled out a fix in early 2023, essentially fixing software incompatibilities following an Android OS upgrade. History appears to be repeating itself as after updating my Android phone OS on 23rd June 2023, I am once again experiencing the same problems with the High and Low level alarms not notifying me when hitting the set trigger point. Is anyone else experiencing the same issue? It took Abbot months to admit that there was a problem last time, leading to many members, who rely heavily on these notifications, experiencing life threatening BG levels. Offers of sending out replacement sensors are of no use if this is once again caused by software incompatibilities. For information, my current sensor and the alarms, were working absolutely fine, right up until the phone OS was updated. A coincidence?
-
Guest - w'd love to know what you think about the forum! Take the 2025 Survey »
Libre2 Alarms not working - a re-run of early 2023?
- Thread starter millat
- Start Date
h884
Well-Known Member
- Messages
- 464
- Type of diabetes
- Type 1
- Treatment type
- Pump
hi millat
I am experiencing similar problem. I have an iPhone SE. When I contacted Abbot they said this was a known problem with iPhones and I should use a reader rather than my phone. They replaced the sensor without any problem.
barrym
Well-Known Member
What phone and what Android update? Was it a version update or monthly security one?
Hi Barry It's a Samsung Galaxy A53 5G. Model SM-A536B/DS. Android Version 13 A536BXXU6CWE9. Last time the Hi and Low alarms stopped working for me wasimmediately after an Android update (and coincidently, an update from Abbot) The Libre app is indicating the following potential reasons 1) Bluetooth is off (which it isn't). 2) Notifications OFF (again not the case), 3) Sensor not communicating with the app (clearly the case, albeit only for alarms. the sensor can be scanned and log results). 4) No Active Sensor. Again same as 3. The sensor can be scanned. The sensor was triggering alarms right up until the Android update. More than a coincidence I would suggest, but who knows.
barrym
Well-Known Member
Just to clarify, was this an upgrade from Android 12 to 13 or a security patch to existing 13?
I don’t recall a LibreLink update last week. Are you sure there was one? My version in About shows 2.8.4.9335.
Just a point of interest, in the chaos you describe at the end of the year, many of us who use Juggluco to get RT CGM out of Libre 3, didn’t have any problems at all during the entire time. That is because we turn off alarms in LL and have Juggluco hijack the bluetooth to get the alarms. Suggest to me it was neither Libre 2 nor Android causing the problem but LL. Unless it’s Samsung specific. I appreciate that’s not much help, but gives you some evidence to beat up on Abbott.
That said, I haven’t noticed anyone else experiencing this though so far.
Sorry I have nothing positive to offer, except maybe trying Juggluco. Other apps are available!
I don’t recall a LibreLink update last week. Are you sure there was one? My version in About shows 2.8.4.9335.
Just a point of interest, in the chaos you describe at the end of the year, many of us who use Juggluco to get RT CGM out of Libre 3, didn’t have any problems at all during the entire time. That is because we turn off alarms in LL and have Juggluco hijack the bluetooth to get the alarms. Suggest to me it was neither Libre 2 nor Android causing the problem but LL. Unless it’s Samsung specific. I appreciate that’s not much help, but gives you some evidence to beat up on Abbott.
That said, I haven’t noticed anyone else experiencing this though so far.
Sorry I have nothing positive to offer, except maybe trying Juggluco. Other apps are available!
Hi Barry. It was a upgrade/patch to existing 13. Apologies, I did not explain well in my last email. The last time I had issues back in late 2022 was when LibreLink was coincidently also updated, within days of an Android update from 12 to 13 for my phone. This is not the case this time. It is early days, so if it is down to the Android update, then this might become more apparent as the days pass. Like the last time, it appears to be related to Bluetooth idiosyncrasies Others may not have posted about this issue yet, or alternatively, the problem is specific to me. it is just such a coincidence that the issue appeared just after the update was installed. This was the case last time, although Abbot took months to acknowledge this before eventually issuing notices to all LL users. A number of users at that time reported it as a 'yellow card" incident, due to the potential health ramifications.
Lakeslover
Well-Known Member
- Messages
- 474
- Type of diabetes
- Type 2
- Treatment type
- Insulin
a bit simplistic I know but have you tried turning your phone off and on, and turning Bluetooth off and on? Can you see the libre in the list of connected Bluetooth devices?
D
Deleted member 527103
Guest
It is some time since I used Libre so my memory may be wrong.
However, my memory is that the sensor is connected via Bluetooth to the app rather than the phone. As a result, it does not appear on the list of connected devices on the phone.
It would be good for someone who has alerts working on their phone to confirm this.
DEBBIESCOTT
Well-Known Member
Use libre 2 & an iPhone X, just checked libre does not appear on the list of connected devices, alarms mostly work, garmin watch connected to phone & vibrates & tells me if blood sugar is high or low
h884
Well-Known Member
- Messages
- 464
- Type of diabetes
- Type 1
- Treatment type
- Pump
I contacted Abbott today to see if there was any update on the issues with alarms on iPhone. The person I spoke with said they were still working on the issue and that I should try the phone again to see if the problem is still there !!! She also kept stressing that that the alarms would only work on whatever device the sensor was started on. This was despite me stressing that I started my sensor with my phone. I am currently user a reader as guided by Abbott previously
h884
Well-Known Member
- Messages
- 464
- Type of diabetes
- Type 1
- Treatment type
- Pump
I had 2 sensors pack in yesterday, permanent Signal loss. No matter what I did I could not resolve the issue. I contacted Abbot and after 45 minutes during which many things were tried some of which I had already tried they told me there were ongoing problems with the iPhone SE and the Libre app. The lack of alarms is another example of this. When I asked I was told this was the only the iPhone there were problems with. Just my luck that I chose that iPhone !!!!
PatsyB
Well-Known Member
I have the sensor and twice had to ring them to say the sensor keeps saying Sensor not working try again in ten minutes, they did send me a replacement but find this annoying and after reading the above I think best carry a pricker around with me lol
D
Deleted member 527103
Guest
If you drive, it is a requirement to carry finger prick around with you when on insulin.
jaywak
Well-Known Member
- Messages
- 936
- Location
- Norwich
- Type of diabetes
- Type 1
- Treatment type
- Insulin
- Dislikes
- Cold weather, angry people, queues,
I told Abbot that I didn't have a compatible phone , which I didn't at the time , and they sent me a reader free of charge , I have since bought an I phone SE which works 75 % of the time but keeps telling me of signal loss and is also a lot slower than the reader which is almost instant so I think i'me going to be using the reader rather than my phone .
The problem currently being experienced is an exact copy of that experienced at the tail end of last year, beginning of this year. I was also offered a replacement sensor at that time but the sensor is not the issue here. As before, it is a problem with the LibreLink app and the phones OS (in my case Android after the latest patch upgrade). Everything has been really stable since the last fix earlier this year with my phone very rarely reporting an out of sync message, but now I get it every 5 minutes (as before after an Android upgrade last November) although the phone is sitting right next to me. Scanning the sensor appears to re-establish the Bluetooth connection and if you coincidently scan just as you have passed your trigger point then you will get an alarm notification pretty soon after. However, once 5 minutes has passed and you get another “signal loss alarm”, then it is back to alarms being disabled. In the actual app there is a constant notification that the Alarms are unavailable due to 1) Channel Notifications disabled, 2) Lock Screen notification disabled, 3) Notification sounds disabled, 4) sound and pop-up notifications disabled. None of these apply to me. I can live with this during the day as I simply have to scan regularly, but where this becomes a real issue is overnight, where I have come to rely on an alarm waking me before my sugar levels drop too low. This is really disappointing. I have been really pleased with Version 2, as setting the alarms appropriately has really allowed me to gain a much better control over my BG levels with my HB1AC levels typically sitting between 6.3 mmol/l and 7mmol/l; and not suffering hypoglycaemic attacks, which for someone who has had Type 1 for 53 years is not too bad. Come on Abbott, the solution is there. We have been through this very same scenario before.
