Force collection on smartwatch does not work on any watch except Sony Smartwatch 3

[Vaughanabe13]

Based on my own experience with 5 android wear watches and everyone else's experience documented in the facebook group, I have come to the conclusion that there is only one single watch that works when running the collector service, and that is the Sony SW3. I have also tried the original Moto 360, Moto 360 Sport, Moto 360 v2, Zenwatch 2, Zenwatch 3, and Zenwatch 3 after upgrading to Android Wear 2.0. Other reports say that it does not work on the huawei, the nixon, LG sport, urbane, etc.

While they all work with xdrip as a regular watchface viewer, none of them except the SW3 will get readings at all. Every indication on my ZW3 right now shows that it is working - watch is listed correctly in the xdrip app settings, force collection is enabled, location permissions are enabled on the watch, all the settings between the phone and watch match up, Dexcom shows up in the bluetooth settings menu of the watch, Android Wear is listed as the collector both on the watch and phone, etc. But no readings ever come in, even after hours of waiting. Tried multiple restarts of both phone and watch, tried leaving the phone off or in airplane mode. Tried toggling scan constantly and wake screen before reading options. Tried toggling aggressive service restarts. Tried manually restarting the collector. I even factory reset the watch twice. Nothing works.

I am hoping someone working on the code can work on this further because to me, being able to run the collector service on my watch is the single most important thing about the app and I know others feel the same way. Apple/Dexcom is now catching up because the Apple Watch will be able to function as a standalone collector with the G5 now. For now I will continue using the Smartwatch 3 but I don't think it is a good solution for the future since the SW3 can only be bought through ebay and old stock that is quickly running out, and there are other issues with that watch such as the nasty battery drain bug.

I understand this will probably be a challenge to figure out why the other watches aren't working. I would even be willing to send my zenwatch 3 to a developer who is serious about working on it. I think it is that important for the future of the G5 and xdrip.

[paaascal]

Google.ca type Nfc smartwatch ;)

[betulin]

Hello from Spain, I've been reading the post and I concluded there is no collector watch, except Z3, S3 and i'm not sure about Huawei-watch 2 and Fibit - Special Versa edition. I am looking for collector watch which not needs to be connected to the phone. I'm not thinking in using Nigthscout, at least, for the moment. I am using Freestyle libre + Miao Miao. I'd appreciate any advice. Many Thanks

[patelrupesh]

hi, I have just bought Sony Smartwatch 3 after reading on a lot of weblinks that this watch seamlessly as a collector without needing any modifications to the ROM however unfortunately my SW3 doesn't give any readings when selecting the option of "Force Wear Collection Service" - though I do see on the watch a message saying that "Force Wear Enabled". I just see the last reading with the strikethrough line on the xdrip+ watchface. Can someone please help as this is the 2nd watch that I bought (First one was Huawei 2 - that too didn't work).

Thanks, Rupesh

[SimonPhilpott]

@patelrupesh same as me. I've walked Xdrip versions right back to 13th March and none of them collect via the smartwatch 3. I did notice that 30th March and previous versions of Xdrip showed the Blucon as 'bonded# which for me at least using the phone ads a huge amount of reliability for re-pairing when dropping in and out of range.

[patelrupesh]

That's unfortunate to read Simon. Does anyone have a solution for this please - Sony smartwatch 3 as a collector? I hope someone might know how to get this working as there are plenty of users on the internet saying that they have been using the SW3 as a collector.

[patelrupesh]

Can someone please assist?

Thanks.

[Vaughanabe13]

The SW3 does work as a collector, and once you get it working it works reliably and very well, although sometimes it can be a pain to get it working. Here are the settings that work for me.

• Make sure your Hardware Data Source is set to G5 Transmitter and that your Dexcom Transmitter ID is correct.
• In G5/G6 Debug Settings in the phone, check "Use the new OB1 Collector". I also have "Allow OB1 unbonding" and "Allow OB1 initiate bonding" checked. Check "Authenticate G5 before each read" and do not check "Unbond G5 for each read." You can try both ways with the "Scan for G5 constantly". It doesn't need to be on, but sometimes I seem to get better/quicker connections when I leave it on. Either way it doesn't seem to make much difference.
• Go to "Smart Watch Features->Android Wear Integration." Ensure AW Integration is enabled, enable the wear collection service, enable "Force Wear Collection Service."
• Go to "Less common settings" and check "Aggressive service restarts." I'm not sure if this is necessary or not but I tend to always leave it on.

Now, sometimes the settings between the watch and the phone get out of sync. For example, make sure the "Force Wear Collection" setting is enabled in both the watch settings and the phone. Sometimes it will only be set in one or the other. Make sure they both are enabled.

After you change all these settings, start your sensor session (if it isn't already started). I also like to go to the System Status screen and tap "Restart Collector" just for good measure. On this page, you eventually want to see in the Connection Status: "DexcomW2 Authed, FW:1.0.4.10" which means your collector is properly bonding to the G5 transmitter.

More things you need to do: In the SW3, make sure the software of the watch is up to date, by performing a software update through the Android Wear interface. Then go to the Permissions settings in the watch settings, and go to Xdrip+ and enable all the permissions including location. YOU WILL NOT GET ANY READINGS UNLESS PERMISSIONS ARE ENABLED. It's also a good idea in your phone app permissions to grant xdrip+ all the permissions including location. Make sure the xdrip+ is the selected watch face, and again make sure the settings are synchronized with the phone settings.

Next you should perform a system restart of both the watch and the phone.

Next you may need to pair your Dexcom sensor to the watch. Within the first 4-8 minutes of running the collector on the watch using Force Wear Collection, you will get a pop-up on the watch screen that shows your Dexcom transmitter ID and asks you to pair bluetooth. Make sure you are watching the watch face during this time because this is time sensitive. Accept the pairing procedure, and then you should start getting readings within 10 or 15 minutes max. You only have to pair your transmitter once, but you will have to do this step again in the future when you get a new transmitter with a different ID.

Once you start getting readings, you can go into the phone app and enter your BG calibration (I believe calibration from the watch is currently unsupported).

I should also mention that this whole process will be much smoother if you don't have any other devices trying to connect to the G5 transmitter. That means turn off your G5 receiver, or any other receiver device that may be looking for G5 readings (Tandem X2, etc.).

Unfortunately the whole process is still very cumbersome but it does work eventually, and works well once it gets going. I typically get >93% collection rate.

[patelrupesh]

Thanks @Vaughanabe13 I did try all the options suggested in your message however without joy - unfortunately. Just one difference - I'm using a combination of Libre+Blucon and not Dexcom G5. Don't think this would make any difference though.

Strange part is that the xDrip+ application on both the watch and phone stop giving readings as soon as I select option "Force Wear Collection Service".

Not sure however it seems that the issue is with the current xDrip+ releases rather than the watch itself. Anyways, whatever the root cause is, the watch doesn't work as a collector for me even after doing all possible suggested configuration changes.

Does anyone else have an idea on this. Can I please request the development team to assist with this.

Did send Jon couple of emails however seems he's busy as haven't responded yet.

Thanks all - please help.

[Vaughanabe13]

You could try going back to a previous version of xdrip+ and trying that. It's certainly possible that something has broken compatibility. I really can't speak to the blucon personally since I don't use it and I'm not an xdrip developer, sorry. I really wish there were official transmitter-to-watch products out there and that it didn't have to be something cobbled together.

On Tue, Jul 3, 2018 at 10:22 PM patelrupesh notifications@github.com wrote:

Thanks @Vaughanabe13 https://github.com/Vaughanabe13 I did try all the options suggested in your message however without joy - unfortunately. Just one difference - I'm using a combination of Libre+Blucon and not Dexcom G5. Don't think this would make any difference though.

Strange part is that the xDrip+ application on both the watch and phone stop giving readings as soon as I select option "Force Wear Collection Service".

Not sure however it seems that the issue is with the current xDrip+ releases rather than the watch itself. Anyways, whatever the root cause is, the watch doesn't work as a collector for me even after doing all possible suggested configuration changes.

Does anyone else have an idea on this. Can I please request the development team to assist with this.

Did send Jon couple of emails however seems he's busy as haven't responded yet.

Thanks all - please help.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/149#issuecomment-402351994, or mute the thread https://github.com/notifications/unsubscribe-auth/AOJ6QkyLOkugWWZbnbo9eZMjpytKqpS3ks5uDDTzgaJpZM4OgNLz .

[simondavies560]

We had an Asus Zenwatch 2 working very effectively with a build from some time in the middle of January (sorry, can't remember the exact build), and had some temporary success with a March 12th build with Ticwatch, but that connection has always been very flaky. Definitely suggest rolling back to older versions, Sony SW 3 does seem to have been the watch of choice historically.

On Thu., 5 Jul. 2018, 02:31 Vaughanabe13, notifications@github.com wrote:

You could try going back to a previous version of xdrip+ and trying that. It's certainly possible that something has broken compatibility. I really can't speak to the blucon personally since I don't use it and I'm not an xdrip developer, sorry. I really wish there were official transmitter-to-watch products out there and that it didn't have to be something cobbled together.

On Tue, Jul 3, 2018 at 10:22 PM patelrupesh notifications@github.com wrote:

Thanks @Vaughanabe13 https://github.com/Vaughanabe13 I did try all the options suggested in your message however without joy - unfortunately. Just one difference - I'm using a combination of Libre+Blucon and not Dexcom G5. Don't think this would make any difference though.

Strange part is that the xDrip+ application on both the watch and phone stop giving readings as soon as I select option "Force Wear Collection Service".

Not sure however it seems that the issue is with the current xDrip+ releases rather than the watch itself. Anyways, whatever the root cause is, the watch doesn't work as a collector for me even after doing all possible suggested configuration changes.

Does anyone else have an idea on this. Can I please request the development team to assist with this.

Did send Jon couple of emails however seems he's busy as haven't responded yet.

Thanks all - please help.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub < https://github.com/NightscoutFoundation/xDrip/issues/149#issuecomment-402351994 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AOJ6QkyLOkugWWZbnbo9eZMjpytKqpS3ks5uDDTzgaJpZM4OgNLz

.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/149#issuecomment-402522628, or mute the thread https://github.com/notifications/unsubscribe-auth/Aif7RN1JJrofh-wrhaJAIGDppUkUIejVks5uDO3ugaJpZM4OgNLz .

[RicardoFBCoelho]

Saw this very interesting topic. I am looking for a Smartwatch myself to connect with Libre – my aim is to set up a CGM. I’ve seen a few reported watches like Sony SW3, Finow Q1 and several models from Ticwatch that do this without the smartphone.

However, I would like to ask if anyone has experience with any model from Samsung such as Samsung Gear 3 or the new Galaxy watch. In theory, they should have the tech to work but they operate on Tizen OS and not Android Wear.

I appreciate all the help. Thanks,

Ricardo

[betulin]

Hi, I am trying to set up a s. watch as standalone collector. S. watch it should get readings when MiaoMiao is out of range of the phone and when it's back in phone range, it would connect to it again and s.watch's readings should be syncc. Also, I'd like to follow both, the SW and phone on my own phone. It could be on IOS or Android or both, not problem.I could use, Xdrip or Spike or NS. I'd really appreciate any suggestions are wellcome. I've been reading about . I'd like to tell you what I have found so far:

1. The Sony SW3 works as an standalone collector but it is not possible to follow it as a follower. Neither in xDrip nor in NS. It does not require any patch but it is sometimes hard to get connection
2. Those watches, which are full Android and have sim, basically works as if they were a phone. They allow standalone connection, follow-up with xDrip as a follower and since they have sim and data connection, they also allow to see it in NS. Unfortunately, its, battery is too short. They are not submersible.
3. There are some Smartwatches with Android WOs which can working as standalone collectors after applying a patch. Some of them has sim card. However, this is only described for the dexcom g5 sensors and I do not know, for sure, if they shoul be patched or not using MM. They are more expensive . They have a very good battery and they are submersible.
4. The iwatch, so far, do not work as standalone collectors, they need the iPhone nearby I'd appreciate any corrections, suggestion, information could me set up an standalone collector that can be follow, good battery, IP68 . 5.Fitbit ionic can get readings but I haven't be able to understand where they canoe from. I understood they are taken from xdrip acting the watch as a follower, but no sure.

The 3rd option would be the best for me but I don't know if they work with MM without patching. I'd prefer not to patch, because I don't feel confident enough to go through it

Thanks a lot

[tKostka]

@jamorham: I tried to patch my new Polar M600 with the BT fix but was getting error during the install in the TWRP shell:

ERROR : with firmware patch A ERROR : with firmware patch B ERROR : could not patch BT ERROR : with demigod mode ERROR : with demigod-2 mode

I've tried several times, with several reboots. It seems there was an Update from Polar recently, the Bulid Number of my M600 ist different from the number in the PDF Guide: OWDB.180305.008 vs OWDB.180305.015 Is this the problem? If so, would it be possible to get an updated patch?

By the way, I made this with my Windows 10 Notebook. To help other Windows users, you may add the following in your future PDF guides. I was missing a smartwatch driver for fastboot, so i had to download and manually force windows to use the android google driver (https://developer.android.com/studio/run/win-usb). The fastboot commands are different from Linux. In the Windows shell it is just fastboot oem unlock (not fastboot –i 0xda4 oem unlock) and fastboot boot twrp-polar-m600.img. The fastboot option -i is not available in Windows.

Thanks for all of your work, i'm using xDrip for years now. I hope you can help with this problem.

EDIT: add TWRP logs from the install error, but I don't understand whats wrong there

mount: mounting /dev/block/platform/mtk-msdc.0/by-name/system on /system failed: Device or resource busy xdelta3: source file too short: XD3_INVALID_INPUT xdelta3: normally this indicates that the source file is incorrect

TWRP.log

[SimonPhilpott]

I've had a pretty good experience with using a Miao Miao over the top of my Libre and removing the SW3 from its strap and putting it into a small roll pouch around my neck. That got me back in the water for most activities. Most roll pouches for electronics are IPX8 and support touchscreen use which banded with the (flakey) IP68 rating is about as reliable as things are going to get.

The Nixon Mission would be a great step, but that being said it;s no use if the Miao Miao remains as IP68. You're only as waterproof as item with the lowest rating after all.

[heygar]

I just recently started messing with this with my ZW3. I'm looking for a smartwatch I can wear out on a catamaran cruise of sorts. Lots of water activity. I've decided to try the Misfit Vapor as I can get a used one for ~$50 on Ebay. Has anyone had any luck running the Vapor as a collector? Or is it totally impossible?

[Braintelligence]

@heygar did you have any luck with the vapor?

[heygar]

The bidding went above my comfort level for the risk of it not working. I'm still looking for a water proof wear OS watch I can confidently use as a stand alone collector.

[lee-b]

I've noticed that this works (on a Huawei Watch Pro 2 to a MiaoMiao) with Glimp, but not XDrip, for some reason. I never tried Glimp on my old SW3 and Nightrider, but couldn't get XDrip's watch-based collection working with that setup either.

[Navid200]

It seems the issue this thread was opened for was already addressed.