MaherOlivia
Member
- Messages
- 8
Funny got the same issues over here.
There have been a stack of updates to Samsung phone so wonder if something has broken, I'm using the xDrip build from 13 April which is better but not great and more often than not will drop the connection.
Be interested to know if you find anything out, don't know if @porl69 is having any issues.
Another thing to just be wary of is that Libre 2 is on its way. This has Bluetooth so that the Libre Readers (will need a change if your running Libre 1) can have alarms set on it. The issue is that I believe the bluetooth is encrypted which means that AT the moment MiaoMiao and xDrip (or other 3rd party software) won't work with it. I also believe that the xDrip dev guys are working on this but I do not at the moment know where they are up to.
Practically from the moment of their appearance – an international team of programmers creating applications such as Spike, xDrip, Nightscout, closed loops in which I have the pleasure to participate from the beginning – began work on their decoding and enabling cooperation with those sensors.
The work ended in the last days (with the exception of the Libre US 14-day sensor, which is still underway). Fortunately, all problems with these new sensors have been solved. Unfortunately – it is necessary to replace the new, updated internal software in intermediary devices, i.e. in MiaoMiao, BluCon, GNSentry, my transmitters, etc. Some of them allow such updating by the user, others will have to be sent back to the manufacturers.
@porl69 and @Connie’s Dad plus anyone else watching this thread.
Was mooching around the xDrip site and don't know if any of you have come across this thread https://github.com/NightscoutFoundation/xDrip/issues/840 but it is a discussion about watch not working and possible work arounds, I'm trying one out at the moment![]()
@porl69 and @Connie’s Dad plus anyone else watching this thread.
Was mooching around the xDrip site and don't know if any of you have come across this thread https://github.com/NightscoutFoundation/xDrip/issues/840 but it is a discussion about watch not working and possible work arounds, I'm trying one out at the moment![]()
What do they mean when they talk about builds? Is this just an old version of the xDrip app. Is what they are suggesting as easy as deleting current xDrip and reinstalling an older version?
Uninstall the software off your phone and watch and reinstall, BUT beware that doing this will remove all your settings and data.
Each build is just a version of the app. There is a stable release and then the following test releases which are available are usually updated every day and referred to as 'nightlies'.
You don't have to uninstall/reinstall with xDrip. It's possible (unless something is seriously broken in the app) to simply install older and newer versions over the top of what you have running and I've done this before.
Thank you Knikki for your time and effort on this issue. Believe me it is much appreciated@Connie’s Dad and @porl69
OK I have been running with this build from 31 Jan 209
https://github.com/NightscoutFoundation/xDrip/releases/tag/2019.01.31
First night it would not play ball but then I went to the watch, went to the app settings and Enabled "Force Collector force phone to use wear collection services" then restarted the Collector on the Watch (hit the three buttons top left Start Collector I think is the Cloud icon)
This worked, went out for a walk and was way out of range of the phone and the watch worked.
Back inside and it did take about 5 - 10 minutes for the phone and watch to talk to each other.
Now I switched both phone and watch off last night.
This morning I switched the phone on and nothing would not connect to anything.
Went in to the setting and switched off the Watch App and it eventually sprung back in to life.
Switched the Watch on later, re-enable the Watch in the xDrip setting on the phone, and nothing would not work.
I then went into the setting on the phone and switched off the "Force Collector" option.
Since then it has remained working with he phone nearby and when out of range.
You might have to fiddle around with settings, "Force Collector On Phone" and the "Enable Collector" but at least mine is now working as I want.
Good luck.
@Connie’s Dad and @porl69
OK I have been running with this build from 31 Jan 209
https://github.com/NightscoutFoundation/xDrip/releases/tag/2019.01.31
First night it would not play ball but then I went to the watch, went to the app settings and Enabled "Force Collector force phone to use wear collection services" then restarted the Collector on the Watch (hit the three buttons top left Start Collector I think is the Cloud icon)
This worked, went out for a walk and was way out of range of the phone and the watch worked.
Back inside and it did take about 5 - 10 minutes for the phone and watch to talk to each other.
Now I switched both phone and watch off last night.
This morning I switched the phone on and nothing would not connect to anything.
Went in to the setting and switched off the Watch App and it eventually sprung back in to life.
Switched the Watch on later, re-enable the Watch in the xDrip setting on the phone, and nothing would not work.
I then went into the setting on the phone and switched off the "Force Collector" option.
Since then it has remained working with he phone nearby and when out of range.
You might have to fiddle around with settings, "Force Collector On Phone" and the "Enable Collector" but at least mine is now working as I want.
Good luck.
Yes the watch is at the moment working standalone.
@Laois80 a smart alarm clock? Wow didn't now you you get one of those, good luck with your quest![]()
Sorry only just picked up on this as i don't seem to have got the Alert.
To be honest it works but can drop connection on more than regular basis, which is a pain. Seems there was an update to Samsung blue tooth sometime in March which is causing all the issues, have not been back on the xDrip forums recently to see if any progress has been made.