Libre 2+ Connection Issues #4151
Replies: 17 comments 80 replies
-
|
if you keep NFC scanning you generate a lot of log info that isn't really useful for example that's a screen full of predefined keys to speed up / make reliable the unlock process. Using the spyglass search you can perhaps get some more relevant view - search for "received" or "raw" to show the values being received by BLE or just show the OOP2 screen. Also the xDrip+ system status screen - Bluetooth device - gives some time information. I have seen a few people say the 301 serial number sensors are more challenging - where are they made ? (it's on the box) |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for trying to help me (AGAIN!!!) I don't think refining the search will prove to be of all that much use. For what its worth I think Abbott have been playing silly stupid with the Bluetooth protocols on their sensors. I say this because I am aware of a number of users reporting connectivity issues with sensors and Abbott's own Librelink app. In any case here are some random event logs As regards country of origin? The box is sadly now in recycle heaven. I will however check some of my other sensors tonight when I get home from the gulag as I feel I should have others with similar serial no's.
|
Beta Was this translation helpful? Give feedback.
-
|
An OOP2 screen shot? The audio disconnects are probably the watchdog restarting Bluetooth due to lack of receiving data |
Beta Was this translation helpful? Give feedback.
-
|
maybe tweaking these selections will refine your error log |
Beta Was this translation helpful? Give feedback.
-
|
I have managed to convince myself that these issues are related to changes introduced either by design or by accident to the Libre sensors by Abbott. As I posted earlier on their own app appears to having some difficulty receiving and translating Bluetooth values. To date Librelink problems have never concerned me personally since I only ever use their app to initialise a sensor. in any case here is an OOP2 screenshot showing data before and after yet another lost connection.
What I find particularly curious is the fact that the dropouts do not really follow any particular pattern. I have looked at number of Bluetooth devices connected to my phone at any one time and shutdown them all with the exception of the sensor and my watch and still encountered dropouts. Then with other things connected such as my truck and other various tat sometimes connection drops and sometimes remains relatively stable. There is nothing I can see glaring out in the Xdrip event log. This has also only really occurred with my current and previous sensor. Again as previously stated the previous sensor was only attached for 6 hours and removed. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! I've upgraded to 2025.06.12 but sadly have still got the same issue: On scanning the sensor I get "NFC invalid data - try again" on the home screen and the "Sensor type unknown, returning to Libre1 as failsafe" entry in the event log. Hopefully PhilTU can come to our rescue! I've been happily enjoying Drip+ for over a year now, for me the was move triggered by Abbott's point blank refusal to port LibreLink to smartwatches... |
Beta Was this translation helpful? Give feedback.
-
|
Have you also update OOP2? It is on the same page that I linked in my reply. Opinions vary about what to do about Librelink when you are using Xdrip+ but I always disable it completely. Navid, who put the page together regarding the update suggests disabling multiblock reading. If you post some event logs I will compare them to my own and try to identify any other issues that may be relevant to you. By that time someone may be along with far more technical fire power than my very meagre catapult. I will fo my best to help though as much as I am able. |
Beta Was this translation helpful? Give feedback.
-
With the June 2025 version of OOP2 you need xDrip+ from 20/6/25 or later for the 301 sensor |
Beta Was this translation helpful? Give feedback.
-
|
I'm delighted to report that with PhilTU's guidance (OOP2 2025.06.12, xDrip+ 2025.06.20) my issue of unrecognised Libre 2+ sensors (the ones with the newer '301' firmware) is resolved. Many, many thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Just a quick note to say having successfully started a new 301 sensor I'm back to the full functionality I had with the older 3MH sensors. OP2 2025.06.12 and xDrip+ 2025.06.20 looks like a reliable combination for me at least! |
Beta Was this translation helpful? Give feedback.
-
|
I had the curious delight of having an uninterrupted connection for about 3 hours this morning. I rather foolishly thought all my connection woes were now behind me. 10 minutes ago I lost connection again and I am back to silly swiping. It probably sounds quite unhinged to read but it is however completely true that I would rather have to swipe with Xdrip+ than use Bluetooth data from Librelink. I would not trust it to tell me what day of the week it is, let alone my blood sugars |
Beta Was this translation helpful? Give feedback.
-
|
Updated the Sony to 29/8/25 and broke the connection..... |
Beta Was this translation helpful? Give feedback.
-
|
Hmmm, which is why I suggested the problem is device (sorry - I used the wrong word earlier when I said hardware) related. My backgound is in the telecomms industry where there are strict standards to ensure operability across network operators but the equipment vendors, whilst adhering to said standards, are always looking for opportunities to lock the network operators into them... |
Beta Was this translation helpful? Give feedback.
-
|
@Diabeticliberty - I have a workaround for "limping along with my current sensor until it expires" but sadly I can't share it in a public forum... |
Beta Was this translation helpful? Give feedback.
-
|
And I've had mixed success with Samsung. Before I settled on the S21FE I had an S20FE that refused to stay connected to my home WiFi |
Beta Was this translation helpful? Give feedback.
-
|
Sorry Trevor, I wasn't ignoring you. Based on what PhilTU found and how his findings have worked in my own situation it seems that it is the Xdrip+ app from August where the fault lies not a hardware issue which offers me great relief as I have 18 months left to run on a Samsung S25 Ultra mobile. I would suggest at least for now that anyone out there having the same or similar problems to my own that they use the Xdrip+ app from June 20th. Once again my sincere thanks to @PhilTU |
Beta Was this translation helpful? Give feedback.
-
Coming up for an hour connected |
Beta Was this translation helpful? Give feedback.
-
|
You sir are placed right at the very top of my cool dude list. Been connected uninterrupted since 6.30pm and I am forever in your debt. Thank you ever so much 💓 |
Beta Was this translation helpful? Give feedback.
-
|
95 minutes connection without issue. Seems like I really am fixed,. |
Beta Was this translation helpful? Give feedback.
-
|
My rather giddy state of euphoria was sadly premature. I am still suffering lost connections. Granted they are nowhere near as prolific as they were with the August 25 Xdrip+. I suppose all I can attempt to do is try loading other versions and try to find one that is stable with my phone and sensor. A troubled weekend ahead I think. |
Beta Was this translation helpful? Give feedback.
-
|
If there are no changes to xDrip and my phone has not had any updates since prior to my own issues do you feel that there may be changes to the actual sensors at the bottom of this? If so as users start to work through their existing units and get replaced with the new serial no editions my own issues may of course be experienced by everybody else. Not something I would wish on next doors cat that insists on crapping on my lawn. |
Beta Was this translation helpful? Give feedback.
-
no, I couldn't really see anything. I'm just flipping back to 29/8/25 version after succesfully running 20/6/25 overnight to see what happens, both on the old phone. As an empirical observation people who updated to the 20/6/25 version and the new OOP2 seem to have a much higher success rate than others who updated OOP2 but went to the latest nightly. Maybe next I should try the one after 20.6.25 |
Beta Was this translation helpful? Give feedback.
-
|
Welk I don't feel it's as solid but the latest nightly is doing ok |
Beta Was this translation helpful? Give feedback.
-
|
Just threw the July version on to mine. It went straight on and has started delivering results straight away. Granted it has only been 10 or 15 minutes but I'll take it as an dearly win - I hope!!!
|
Beta Was this translation helpful? Give feedback.
-
|
Naaaahhhhhhh.......this version just blew out on me as well. |
Beta Was this translation helpful? Give feedback.
-
|
After a rather protracted process I eventually ended up back with the June release and while by no means ideal as it does keep losing connection I think that it's the best I can expect, at least for the time being. |
Beta Was this translation helpful? Give feedback.
-
|
The latest nightly build is proving to be really stable for me. Approximately 2-1/2 hours and no dropped connections. Per5haps a little premature but I think now might be a reasonable time to close this thread. Thanks again PhilTU |
Beta Was this translation helpful? Give feedback.
-
|
The car disconnects as Xdrip shuts down Bluetooth and then restarts it to try and re-establish a good connection. As the Bluetooth connection breaks from the car it cannot reconnect without manual intervention. Sometimes the loss of car connection is because I have switched off the engine after arriving home, office, clients location and or other. My own feeling is that for the most part Xdrip is shutting down Bluetooth as it loses connection while I am driving. I have had Bluetooth shutdown in the middle of handsfree calls. There are no real common factors I have been able to cobble together to try and establish why things are failing. |
Beta Was this translation helpful? Give feedback.
-
|
The xDrip Bluetooth watchdog is a last-resort utility and you can disable it. We have this watchdog on a switch so that the user can disable it if they decide it is more trouble than help. I myself had a lot of grief with it before I bought my first Pixel phone. The Pixel phone is solid with respect to connectivity and the watchdog has never triggered since I bought it over 2 years ago. |
Beta Was this translation helpful? Give feedback.
-
|
I have on many occasions considered disabling the Bluetooth watchdog. The thing is though when I am losing connection sometimes Xdrip+ re establishes a connection and I cannot discount the fact that this may be because the watchdog facility is either in part or in full part of this reconnection. Xdrip+ and glucose management are far more important to me than dropping calls mid conversation. |
Beta Was this translation helpful? Give feedback.
-
In this instance it wasn't that because xDrip was recording values when the car went off. I wondered if location was an issue like arriving in a place with a lot of 2.4 GHz WiFi or Bluetooth signals. Is it generally reliable in the car ? |
Beta Was this translation helpful? Give feedback.
-
|
Prior to my current silliness it was stable pretty much everywhere. I have just lost connection again sat in my living room. The usual Blootooth devices around me. Have family turned up so 4 mobile phones with Bluetooth no doubt enabled. A Bluetooth scan will pick up neighbours devices also but nothing overly excessive in terms of numbers |
Beta Was this translation helpful? Give feedback.
-
|
Did a sensor swap over a little while ago. I did have one of the previous series units in the cupboard and fitted that one. Lit up immediately after the one hour warm up and now running without any of my previous problems. The 15 days grace I am hoping for will be welcome as we go on 2 weeks holiday this Sunday. After that it will be back to new series sensors and I really dread the prospect of that. Thanks to @PhilTU and of course @Navid200 for your assistance in everything. I will leave the thread open as suggested.
|
Beta Was this translation helpful? Give feedback.
-
|
3 hours 25 minutes ran without a single dropped connection and still going. Running with the latest September nightly and absolutely zero negative issues. I am delighted, at least for now. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, might be completely unrelated, but I've had recently one Libre 3+ with strange bluetooth connection issues. Just switching APPs Libre 3 / Juggluco could get it working again, but only with one of the APPs at the time, the other APP would not get continuous readings or a connection at all, even with switching APPs right back and forth. If I remember correct, nothing like bluetooth on/off, restart or NFC scan did change anything - only switching the APP. When connected, even the signal range was good. Never had something like this happen before or after. So it could sometimes just be a strange sensor. |
Beta Was this translation helpful? Give feedback.
-
|
interesting suggestion and I dearly hope that you are correct. The previous series of Libre 2+ sensor that I fitted yesterday has now been running for nearly 17 hours and it has been just about as stable as any sensor I have ever used before, if not more so. if my own issues were related to just a single sensor and not the new series with the new serial no's then I will really take that as a win. I will not know for the next 2 weeks as I have 15 days to run on my current unit. |
Beta Was this translation helpful? Give feedback.
-
|
same probleme for me have you know a solution for this disconexion ? |
Beta Was this translation helpful? Give feedback.
-
|
i can only offer you information based on my own experiences over the last couple of weeks. I am running with a Samsung S25 Ultra and a Samsung Watch Ultra using Glucodatahandler for the watch face. I tried utilising 4 different versions of Xdrip+ with very limited degrees of success. The connection losses appeared very random and I could not and can not identify a set of circumstances where connection failures were more likely. I will say that curiously NFC swiping with NFC enabled in Xdrip+ seemed for the most part to re establish connection more quickly but for how long that connection held together was unpredictable. I was swiping the sensor fairly frequently just to get a glucose reading when I had dropped connection. So this comment is purely anecdotal. The only other thing of note to add is the 'Error writing characteristic (2nd try) seemed fairly common to all lost connections @PhilTU drew my own attention to this error message initially. I have found a 3M serial numbered sensor and running with the latest nightly Xdrp release and latest OOP it has so far been flawless. Probably no help to you at all if you are using the serial numbered sensors. |
Beta Was this translation helpful? Give feedback.
-
|
Got home from work this evening and have found 3 of the previous series of sensors. With the one I fitted last night this gives me 60 days grace. For now at least this takes a little pressure off me. |
Beta Was this translation helpful? Give feedback.
-
|
for my part I only have 301 sensors, apparently these are the ones that are marketed and I don't know how to find 3m ones... I hope that Abott hasn't replaced all its 3m sensors with 301 ones otherwise it's going to be a big hassle...
…________________________________
De : Diabeticliberty ***@***.***>
Envoyé : vendredi 12 septembre 2025 18:27
À : NightscoutFoundation/xDrip ***@***.***>
Cc : genesis38470 ***@***.***>; Comment ***@***.***>
Objet : Re: [NightscoutFoundation/xDrip] Libre 2+ Connection Issues (Discussion #4151)
Got home from work this evening and have found 3 of the previous series of sensors. With the one I fitted last night this gives me 60 days grace. For now at least this takes a little pressure off me.
—
Reply to this email directly, view it on GitHub<#4151 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AM7OJAM6CVDSL53JIXLOEOT3SLX6ZAVCNFSM6AAAAACFJQZ4OOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZYGYZDQNY>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I was at my local pharmacy yesterday collecting a new prescription and asked the pharmacist about this very issue. She physically checked every sensor that she had in stock and they were all 301 referenced. She said that when ordering from the wholesaler there was no facility to request a specific series and could not even find out if the 3M series were still available. I do intending investigating further and will report back with what I find. |
Beta Was this translation helpful? Give feedback.
-
|
I did the same yesterday and checked all the serial numbers of the sensors in the pharmacy and they are all 301 in my opinion the 3m series will no longer be marketed... I wonder how we will be able to do with xdrip which loses the connection without stopping it is unmanageable for my loop |
Beta Was this translation helpful? Give feedback.
-
|
If you are correct and I really fear that you are then I will look again at moving over to Dexcom. I once took a G7 on trial as I had a prior extended episode of Libre hell but things settled down and I gave the G7 to a friend who was going overseas and was worried about the geolocking on Libre. I have read wildly conflicting reports about Dexcom. The 10 day life is of course an issue, at least to me. Reliability is of course the ultimate deal breaker. On this issue I'm afraid I cannot speak for or against Dexcom. The thing is though I cannot continually go through what I went through with my previous Libre 3 ser no. In this regard I may have no other choice. |
Beta Was this translation helpful? Give feedback.
-
|
New 301 on last night was stable with Librelink overnight (no loss of signal alarm). Will switch to xDrip soon. Ye olde Sony phone, android 9. Can we try https://github.com/NightscoutFoundation/xDrip/releases/tag/2025.09.05 which is scheduled to be the next stable release. |
Beta Was this translation helpful? Give feedback.
-
|
I'm already running with that version. I was using it for a couple of days prior to changing to my current 3M sensor. I was unfortunately getting signal dropouts with that version and the 3 series sensors so I fear we may be in for a bumpy ride. Can I ask if you are using Librelink with the Bluetooth facility enabled please? If so do you not find the sensor completely locked to the app with Xdrip unable to connect? I read somewhere a long time ago that it was ill advised to enable Librelink Bluetooth for this very reason. I have therefore never used Librelink in this fashion. |
Beta Was this translation helpful? Give feedback.
-
Just now I am only using Librelink (with Bluetooth) to see how stable it is. I will shut it down when I switch to xDrip (actually it's on a different phone) |
Beta Was this translation helpful? Give feedback.
-
|
I was also wondering about switching to a dexcom, changing it every 10 days is not a problem for me, however I would like to have feedback from some people who have tested both because in terms of reliability of results I prefer to go for the most reliable because sometimes with the FSL 2 I have big gaps and it is very dangerous I would be curious to know if there is less gap on the dexcom... regarding the 301 sensor I think it is an incompatibility at the Samsung level because obviously with the xdrip version of September the majority of people do not have a problem it works well so I really think it is an incompatibility between Samsung and 301 the problem remains the same if the problem is not corrected by the creators x drip I will unfortunately also be forced to change to dexcom...the xdrip update 5 September doesn't change my problem |
Beta Was this translation helpful? Give feedback.
-
|
I can see the problem with taking a long time to reconnect after a period of successful operation. This perhaps needs a developer to look at the logs to understand where it is going wrong. Can @Navid200 guide us on this ? |
Beta Was this translation helpful? Give feedback.
-
|
@genesis38470 please understand that I have had and will have pretty much identical problems to your own. I need it solving too. If in fact it is solvable. I think though that it is grossly unfair to apportion blame due to lack of response from developers of ths system that all of us here utilise. Please remember they make no financial gain from Xdrip+ and only developed the app and continue to refine it for the benefit of all of us. If any one is to blame in this then perhaps it is Abbott who keep changing their sensors for reasons that I personally can only speculate on. Financial interest though would be my first port of call. I am absolutely certain that if a solution can be found then it will be found and applied. If not then it may be that Samsung phones are no good for the application with Libre sensors or we all switch to Dexcom. |
Beta Was this translation helpful? Give feedback.
-
|
Samsung is a known problem. Samsung does not use standard Android. This is what you need to look at and follow if you use Samsung: https://dontkillmyapp.com/samsung |
Beta Was this translation helpful? Give feedback.
-
|
I understand Samsung is on one ui and it's différents but i always use Samsung with xdrip and Android app and all has been Always work before the fsl2+... I hope you will fond a solution for this problem and if you want more screenshots of my bug or more information i am happy to give it to you for désolé this problem |
Beta Was this translation helpful? Give feedback.
-
|
I don't blame the administrators of this application at all, which helps us live every day. I completely agree with you. It's Abott's fault for changing its sensors. I'm just saying that despite the help of everyone here, I haven't managed to contact the administrators myself to help solve this problem together. I'm very grateful to be able to use it every day and will continue to use it for years to come because it's based on a community of mutual aid for its development. And if I have to switch to Dexcom to be able to continue using it, I'll do it out of spite, but I hope we'll find a solution for the FSL 2+ and Samsung. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
After starting a new sensor last week and then swapping it out as I was having some issues with Xdrip+ and OOP2 not recognising the sensor I was lucky to get some help from @PhilTU and managed to connect everything. That was when the fun and games really started. I am now having constant issues with Xdrip+ and sensor losing connection. Swiping the sensor with 'use NFC scan' enabled connects it in pretty much every instance but then things drop out again. I am finding that I am sometimes able to maintain connectivity sometimes for anywhere between 10 minutes and 12 hours and sometimes not at all. It appears that Abbott have made some changes to their sensors and I am of the opinion that this may be where the root of the issue lies. Is anyone else experiencing the same or similar and if so have you found any kind of fix? Event logs here:
Beta Was this translation helpful? Give feedback.
All reactions