I'm wondering if others have had the same experience/know of a resolution.
Every time I activate a new sensor, then I continue to receive the notification that the sensor is ready to use. This happens for several days (I think about the full first week) even though I am scanning regularly and dismissing the message. Not really a problem, just kind of annoying.
LibreLink Software Full Version: 2.2.2.4530
Phone: Samsung Galaxy S9+ version 9
Is this notifacation accompanied by a logo/graphic of a man kind of scanning his arm?
Though I preference the Glimp app as a reader on my Galaxy A3, occasionally I open the Libre link with an established sensor & get the odd note..?
I ignore it & scan away...!
I'm wondering if others have had the same experience/know of a resolution.
Every time I activate a new sensor, then I continue to receive the notification that the sensor is ready to use. This happens for several days (I think about the full first week) even though I am scanning regularly and dismissing the message. Not really a problem, just kind of annoying.
LibreLink Software Full Version: 2.2.2.4530
Phone: Samsung Galaxy S9+ version 9
It could be some sort of glitch with the actual Libre link app on the device OS trying to be "helpful?" & not a sensor.
Could even be a Samsung "thing" triggering the "helpfulness?"
My logic is, if the sensor scans within "tolerance" during it's lifecycle. Then it has to be (maybe?) the app?
It could be some sort of glitch with the actual Libre link app on the device OS trying to be "helpful?" & not a sensor.
Could even be a Samsung "thing" triggering the "helpfulness?"
My logic is, if the sensor scans within "tolerance" during it's lifecycle. Then it has to be (maybe?) the app?
My app is fully updated too. (Though my device is different to yours.) I get occaisionaly the alert choice on my phone to use either Glimp or Librelink to tap in a white box..?
Though I don't claim to be a real "techie." I do wager the device, OS & whatever is set up running in the background..?
"Annoying" it is.. Just a little too much "micro managing" by the pocket buddy... I would call it an "oversight" (& possible "confliction.") by developers.. Of all involved Regarding what "ticks" in the device.?
Have you spoken with Abbott? I had this for a month or two, from memory, it was when they updated to their own app from the original one. There was a big fix within a month or two and that fixed it for me. So guessing I'd say that they fixed some device incompatibility that worked for me, but whatever has changed in your setup has reintroduced it.