EDIT (3 hours after posting the above discouragement): Okay, done with my crying towel, decided to give it another go.
Uninstalled the version I had (it had become completely non-functional), grabbed the latest nightly build of xdrip+ from 9/29, reinstalled and set up again. It’s working, so far.
A few things that may of “disturbed the force”: I allowed an Android update to go forward yesterday that I’d been putting off for weeks. I’m thinking that had something to do with it. Also, I’m running a month-newer version from what I downloaded this morning.
Also running my Dexcom receiver in parallel, even though there is a note somewhere not to, that xdrip and the receiver step on each other. So far, hasn’t been an issue for the hour everything’s been up and running again. I’m hoping this continues, so I have a backup if xdrip gets flaky again.
I have had total success, with near-perfect capture for the last two days using xdrip+. I’m a fan again!
The problem was my Android Wear Huawei watch. For some reason, when its connected (via bluetooth) to my Galaxy S6, it gets in the way of the phone talking to the G5 over bluetooth.
For some reason, having my Gear S2 watch connected via BT doesn’t interfere.
It’s a mystery, but I’ve confirmed this is indeed the problem. So, I’m running successfully now with xdrip+, and very happy. Only issue is access to the information via Wearable Widgets on the watch is a bit more cumbersome than with Android Wear, and the display isn’t as nice. However, I can fix that myself since xdrip+ is open source… I’m going to take the AW watchface and turn it into an Android Launcher widget. This will allow it to be used as a watchface on the G2 through Wearable Widgets, yielding the exact same look/feel as Android Wear.
Hey - I’m happy if you are!! I happen to like the app, but understand the problems. I’ve not been using my Android Wear watch for a while, either. Been using my Pebble Time. Still, I’ve had too many disconnects, but think the developer’s been trying to resolve that issue.
Glad it does not appear to be a problem with the Gear S2 – I’d like to hear about your progress working on the code.
So the parts for the bridge to my G4 showed up yesturday. I soldered everything up and had xDrip+ running in about 1.5 hours. It is very stable and everthing works.
I must admit that I am like a kid on Christmas morning plaing with the new toys. The prediction stuff is cool - I already do this on an excel spreadsheet but on xDrip is more convenient. Of course prediction is only as good as the numbers you use and I tend to make my own decisoona anyways.
The algorithm seems much better on xDrip than the G4 reciever which makes me think my new G4 has the old pre-505 firmware .
Now… which watch do I get? The last watch thread is a bit old.
I had problems with AW connected to my S6. For some reason, my S2 doesn’t cause the same “interference”, even though it connects via bluetooth just like the Huawei AW watch.
Your display options and functionality will be better with an AW watch. It just may not work, depending on what else you have running on the phone, watch, and other bluetooth devices connected / connecting to your phone.
Another problem I had with AW: S6 didn’t like to connect to my car when I was using xdrip+ with AW. No problem with my S2.
So, I’ve accepted the limitations of having to use another bit of software on the S6/S2 combo – Wearable Widgets – to use xdrip and have my BG on my watch.
A new development in this arena: One of the xdrip+ developers has modified the Android launcher widget to include the time (something it didn’t before), making it usable as a “watchface” via WW. This makes it nearly as good as the native AW watchface in terms of the information displayed. Only thing missing then is direct interactivity on the watch itself, which I can easily live without. The only feature in this space on the native AW watchface is being able to enter treatments (insulin, carbs) from the watch – I have to pull my S6 out to do that, but it’s a minor inconvenience and more than acceptable.
For me this is just as well, as I prefer the S2 over AW anyway.
Just got an automatic update from the xdrip+ application and installed it. Went and looked at the github repository for the project to see what had changed… There are several commits (code changes) related to Android Wear and bluetooth issues.
Gonna give AW another try now and see what happens… maybe the problems I was having have been fixed. I’ll report back…
xDrip+ latest builds supports standalone Android wear watches for G5. This means you can run xDrip+ in standalone mode on the watch without being connected to your phone. Upon reconnecting, all BGs are synced to your phone.
Just started a new transmitter, and it’s a completely different experience. I have no doubt now that part of my earlier problem was just a weak radio signal from the transmitter near the end of its battery life. The new one is reading no problem even with my body in between the transmitter on the back of my arm, and my phone in my pocket on the other side.
AND… thank God for xdrip! My Dexcom reciever decided to go belly-up this weekend, with an Error 21 (or something) and “Call technical support” on the display. If it weren’t for xdrip+, I wouldn’t have my CGM. As it is, I haven’t missed a beat, and I have the luxury of calling Dexcom tomorrow when I get around to it, rather than the millisecond they open for business.
Any reason you don’t call the 24/7 technical help line? I know certain things must be handled by the M-F business staff.
[/quote]Well, there is xdrip as the main reason
However, even without xdrip, I wouldn’t bother, as I’ve heard/read about this error before several times around the internet, and the solution is a replacement receiver. Since it’s not getting shipped before Monday, there’s no point in calling them now.
[quote=“Trying, post:33, topic:56373, full:true”]
Sorry, I thought you already had the link to xdrip+.
[/quote]Thanks… of course, I do have that link.
I’m missing something, because I can’t find anything about direct BT connection from the watch to the G5 transmitter anywhere in the repository, jamorham’s site, or in the app. I would assume there would be some sort of configuration on the watch itself, but maybe not.
Could you give some specifics on how to set up the Android Wear part of this to be standalone? Or, if there is a writeup somewhere, a link to it?
I’d love to be able to take the phone out of the loop.
There is a discussion on gitter but it is still being tested so no documentation yet. First install, and connect Wear device to your phone through Android wear app. Then in xdrip+, activate Wear Integration under Settings, and also the first option to connect directly to G5 under the Wear Integration section. This option will allow your wear device to connect to G5 when your phone is it of range. This should happen automatically but there is some lag, maybe 5 minutes during the switchover, depending when the last BG was received from the transmitter. The second option, Use Wear G5 Collection Service, will force G5 connection to be processed by the watch instead of your phone even when within range of the phone. This is useful if your phone bt connection is poor. The wear device, too, can have signal drops though, too, but restarting the watch resolves it.
EDIT: Okay, found the discussion on gitter, read through it, grabbed the 10/14 nightly build, and am trying it out with my Huawei watch.
If it works well, we Android-types will have a leg up on the Apple fanboys!
Kidding aside, it will be a really great feature to be able to have my CGM directly on my smartwatch at all times, even when I DON’T have my phone with me, which does happen infrequently but regularly.
Yes, the standalone watch is especially useful for sports. I mostly use my watch even when within range of my phone now since it seems to have better BT connection.
