Hello good
I have a patchy free and there is no way to link it with xDrip .... I have followed all the tutorials that I have found to see if it enlightened me and nothing ... 😓
Free use 2 and I need xdrip to later link with my band ....
A help ???
I have it configured to use free2 patched ....
I have started a sensor in XDrip several times and nothing ...
I have FreeLink installed patch and original and the readings work with both.
I also have OOP in progress
What I receive from Xdrip is that BG is not available ...
Thank you
No signature configured, add it on your user's profile.
You are making a mess.One thing is the patching app and another OOP2.Uninstall the original app and OOP2 (it is used to dispense with the appoala app and be able to calibrate the free), make sure that the pavement works, the alarms above all.Done this, in XDrip chooses as a free data source2 Patched App and ready, to operate, in a few minutes you will have readings in XDRIP.If the mobile does not restart.
No signature configured, add it on your user's profile.
Well, something else must happen ... In the notification, BG Reading is still appeared to me ...: '(
But in this notification also puts xDrip data collection service is running
I have uninstalled oop2 (somewhere I read that it was necessary despite the patch: o) ...
I have restarted the mobile ...
I start freeLink patch, start xDrip, for the sensor, start sensor and still work ... and I have as a free data source2 patched ...
The original LibreLink I have to let it pass the data to Libreview ...
In LibreLink we don't complain that the alarms fail ...
Any idea?
Thank you
Health!
No signature configured, add it on your user's profile.
pisaldi said:
because something else must happen ... In the notification it continues to appear bg reading unavailable ...: '((
But in this notification also puts xDrip data collection service is running
I have uninstalled oop2 (somewhere I read that it was necessary despite the patch: o) ...
I have restarted the mobile ...
I start freeLink patch, start xDrip, for the sensor, start sensor and still work ... and I have as a free data source2 patched ...
The original LibreLink I have to let it pass the data to Libreview ...
In LibreLink we don't complain that the alarms fail ...
Any idea?
Thank you
Health!
You have to start the sensor with the patching app.
No signature configured, add it on your user's profile.
pisaldi said:
because something else must happen ... In the notification it continues to appear bg reading unavailable ...: '((
But in this notification also puts xDrip data collection service is running
I have uninstalled oop2 (somewhere I read that it was necessary despite the patch: o) ...
I have restarted the mobile ...
I start freeLink patch, start xDrip, for the sensor, start sensor and still work ... and I have as a free data source2 patched ...
The original LibreLink I have to let it pass the data to Libreview ...
In LibreLink we don't complain that the alarms fail ...
Any idea?
Thank you
Health!
If you already have the sensor started, you can not, you have to wait for a new one and start it with the patch.I have Diabox, what can you do it see any moment in the sensor's life.
No signature configured, add it on your user's profile.
I have started a new sensor with the patching and now it works for me ...
Now it's time to synchronize with my band 4 ... there is less ...
No signature configured, add it on your user's profile.
It cost me, but I finally got it ...
Now the big doubt that arises is if the great disparity of results that I am obtaining is normal ...
In a moment of upload principle I get the following:
XDRIP: 86
FreeLink Path: 101
Original LibreLink: 116
Can you do something to mitigate these results and get close as possible ???
I have always believed the original LibreLink results, but now I would be serious about whether they are reliable results ...
Thank you
Health!
No signature configured, add it on your user's profile.
pisaldi said:
cost me, but I finally got it ...
Now the big doubt that arises is if the great disparity of results that I am obtaining is normal ...
In a moment of upload principle I get the following:
XDRIP: 86
FreeLink Path: 101
Original LibreLink: 116
Can you do something to mitigate these results and get close as possible ???
I have always believed the original LibreLink results, but now I would be serious about whether they are reliable results ...
Thank you
Health!
You can't do anything, how do I know.
No signature configured, add it on your user's profile.
I believe that if you compare so many app is crazy.I also do not know if it is not dangerous to compare with each other.I pay attention to XDRIP and compare with capillary measurement.And usually goes very even
Mamá de Tomás 10 años. Dt1 hace 5 años. Con Iport y free1+Bubble mini. Argentina.
Tresiba 9u y Lispro.
pisaldi said:
cost me, but I finally got it ...
Now the big doubt that arises is if the great disparity of results that I am obtaining is normal ...
In a moment of upload principle I get the following:
XDRIP: 86
FreeLink Path: 101
Original LibreLink: 116
Can you do something to mitigate these results and get close as possible ???
I have always believed the original LibreLink results, but now I would be serious about whether they are reliable results ...
Thank you
Health!
Something of difference is always, if you make capillary measurement with different glucometers there is also, that is little difference you put.
No signature configured, add it on your user's profile.
I leave here Link to a topic that seems interesting and related, recommended reading!;)
Link
Diabetes Tipo 1 desde 1.998 | FreeStyle Libre 3 | Ypsomed mylife YpsoPump + CamAPS FX | Sin complicaciones. Miembro del equipo de moderación del foro.
Autor de Vivir con Diabetes: El poder de la comunidad online, parte de los ingresos se destinan a financiar el foro de diabetes y mantener la comunidad online activa.
Hello good.
I have been using the patcherada app and the XDrip several years.The point is that since I have changed phone to a OnePlus every day at 3:00 in the morning the service of the patching app stops "taking readings" and I have to scan the sensor manually.Under normal conditions and at another time I would not matter, but at 3:00 it is something annoying and even "critical."
It once happened to my previous phone but always at another time and related to the sensor change.
Has something similar happened to you?
No signature configured, add it on your user's profile.