Little is said about the incompatibility of Android 16 and the freestyle application.What am I referring to?
Since late 2025 with the Android 16 update, updated phones started having continuous reading issues.The mobile connects and disconnects only from the sensor.Sometimes the disconnections last several minutes and other times several hours (which poses a danger when going to sleep).
According to Abbot, only the Google Pixel are compatible with Android 16 and the sensor.The rest nothing.
Overall, I spent €800 on a Samsung S25+ (which is now an ornament) to have to buy a €160 Motorola because it has Android 14 and works perfectly.
Has this situation happened to you?
Abbot has had this problem for more than five months and they have not solved anything.Of course, it doesn't take long to update the prices of their sensors on the Web.
No signature configured, add it on your user's profile.
My experience is just the opposite, I have a Samsung A55 with Android 16 that is almost two years old now and I have not had any connection problems with the Libre 2. What's more, I bought it to replace a Xiaomi that had a bad habit of disconnecting from the sensor.I also have it connected to a Watch 7 and through GlucoDataHandler I always have the glucose reading on the watch without disconnections and updated to the minute.
An S25 should not guarantee you a stable connection, and the problem you are experiencing could perhaps be due to a problem with access permissions or the battery protection program, which are very cumbersome to configure.I suppose you have even tried resetting all the software by reinstalling Android.Anyway, I want you to solve it because a stable connection is a plus of peace of mind that should not be given up.
All the best!
No signature configured, add it on your user's profile.
@AFlores said:
My experience is just the opposite, I have a Samsung A55 with Android 16 that is almost two years old now and I have not had any connection problems with the Libre 2. What's more, I bought it to replace a Xiaomi that had a bad habit of disconnecting from the sensor.I also have it connected to a Watch 7 and through GlucoDataHandler I always have the glucose reading on the watch without disconnections and updated to the minute.
An S25 should not guarantee you a stable connection, and the problem you are experiencing could perhaps be due to a problem with access permissions or the battery protection program, which are very cumbersome to configure.I suppose you have even tried resetting all the software by reinstalling Android.Anyway, I want you to solve it because a stable connection is a plus of peace of mind that should not be given up.
All the best!
Hi there.Well, the truth is that I don't know what to think anymore.Because it worked well for me until I updated to Android 16. And of course I looked at the compatibility in Abbot's compatibility PDF and it says in a note that Android 16 only works for Google pixels.
And speaking on the phone they told me that they are trying to resolve it, but it has been like this for months.Anyway, I'll have to end up selling the S25+.
All the best
No signature configured, add it on your user's profile.
Hello again, I don't know if this can solve the problem with your Samsung, but maybe it is the solution.Make sure that those two applications, or at least the LibreLink one, run in the background without restrictions on Android 16. In my case, they are the only two that have that permission and that way I don't have the disconnection problem that you suffer from.
Greetings, and I hope it helps you.
wave again,
No signature configured, add it on your user's profile.
I use a Pixel 8 Pro and I have had to authorize it to work in the background and without battery restrictionsand I have the headphones, the watch and the Libre 2 connected to my phone via Bluetooth, and when I drive in the car the wireless Android autoand it has been disconnected but I rarely have enough fingers on one hand to count the number of times it has happened to me, I would follow @AFlores' advice to see if that is what it is, and the application's permissions.
No signature configured, add it on your user's profile.
I don't know if this helps, or will cause more problems... I have a Samsung A55 and it works perfectly with the application... even though aboot tells me that it is not on the list when I have requested a sensor.
Mi total apoyo a las personas y organizaciones que buscan soluciones✌️