• Guest - w'd love to know what you think about the forum! Take the 2025 Survey »

Libre 2+ using Samsung phones (Android v16 :One Ui 8 software)

D

d88

Member
Messages
5
Location
Scotland
Type of diabetes
Type 2
Treatment type
Insulin
Not sure if this has been discussed anywhere on the forum, so I thought I'd pass this on.

As in the title, if you are using the Libre 2+ (unsure if other Libre versions are affected) and using the latest Samsung phones that have had a recent update(see title), then there are known connectivity issues between the two. This means that the sensor will send data erratically to your phone app and so it cannot be relied upon, especially if you rely on the alarm feature to give you a heads up with possible low glucose/hypo events. You can still measure it manually though.

How do I know this? My last two sensors have been playing up, so I contacted Abbott and their agent stated they were aware of the issue, although there were no clear timescales when it would be resolved.

I'm not sure if other Android phones are affected but if your phone is on Android 16 and your sensors are playing up, then this might be the cause.
 
This is probably related to this thread posted the other month:
IanBish

Thread 'Libre2 Plus and Android 16'

I have a Libre2 plus at the moment and keep getting the "signal loss" message. The phone will scan the sensor successfully via NFC, but will often show a "signal loss" message the next time it tries to update the reading. The app will sometimes work for a while if I toggle the Bluetooth off and on again, force stop the LibreLink app, and restart the app or the phone. The phone is close to the sensor.

My phone was repaired recently, and had a factory reset, and was updated to Android 16. I feel that it could be a problem with the Android version, as my smart scale Withings app no longer...
 
d88 said:
Not sure if this has been discussed anywhere on the forum, so I thought I'd pass this on.

As in the title, if you are using the Libre 2+ (unsure if other Libre versions are affected) and using the latest Samsung phones that have had a recent update(see title), then there are known connectivity issues between the two. This means that the sensor will send data erratically to your phone app and so it cannot be relied upon, especially if you rely on the alarm feature to give you a heads up with possible low glucose/hypo events. You can still measure it manually though.

How do I know this? My last two sensors have been playing up, so I contacted Abbott and their agent stated they were aware of the issue, although there were no clear timescales when it would be resolved.

I'm not sure if other Android phones are affected but if your phone is on Android 16 and your sensors are playing up, then this might be the cause.
Click to expand...
Hi,

Thanks for the heads up.
I’m an Android user but have Android 13 with 5.1 One UI. On an old flagship phone.

Out of curiosity. (Untill Abbott sort this for later phone users.)
Have you considered trying a third party app like juggluco? (Can be downloaded from the play store. So no fiddling with the permission settings to instal the apk?)
It can work independently & maybe more stable for your alarms?

It could be a temporary work around?
 
Ive has big problems on Samsung S24u with Android 16 and ui 8.
The librelink app has now been updated to cover Android 16 compatability so you should be fine now,as long as your app updated this week.
 
The LibreLink app on Google Play says it was updated on 24 November 2025, there's been no update on the phone for it for ages.
 
IanBish said:
The LibreLink app on Google Play says it was updated on 24 November 2025, there's been no update on the phone for it for ages.
Click to expand...
The same thing is happening to iPhone users after the latest update to the iOS. On contacting Abbot they have sent me a separate reader and a new sensor. The new sensor failed to work so they are sending me another new sensor. I don't know but you would think that apple and google would give app developers a heads up so that compatibility can be checked before any os updates are released. But maybe I'm dreaming.
 
Eastbath said:
The new sensor failed to work so they are sending me another new sensor. I don't know but you would think that apple and google would give app developers a heads up so that compatibility can be checked before any os updates are released. But maybe I'm dreaming.
Click to expand...
its very very difficult to test against all models of phones alongside all possibilities of OS versions. same reason windows is updated. There are 'beta editions available for some apple mobiles, same goes for android versions. That is the heads up to some degree.

https://www.google.com/android/beta

Apple Beta

beta.apple.com beta.apple.com

Minor revisions should not break anything, where as major revisions can look up Semantic Version naming if interested. usually goes something like Major.Minor.Patch

If all working no reason to upgrade unless security flaw, waiting a few months til some bugs are reported and rectified could be better the choice. thats both with os's and indeed apps themselves.

Its possible in some cases to downgrade back to a previously working state.


edit added: i would not recremmend signing up to use beta versions of anything, unless prepared for something to possibly break.
 
Back
Top