Does anyone have experience with Huawei SmartWatch 2 as a collector?

[avr248]

Does anyone have experience with Huawei SmartWatch 2 as a collector? Is it necessary to make a patch for the BLT?

[lucychiu]

It would be great to have a timeline of when a patch can be created for the Huawei Watch 2. Happy to provide logs to assist with this.

[mileom85]

It is necessary to have a patch for Huawei SmartWatch 2. Without it it can't work as a collector. We have it but can only send data to WatchFace from smartphone.

[avr248]

Please, if there is someone with knowledge who can prepare to explain how to make a patch... it will help very much !!

[mileom85]

@jamorham is going to try to create a patch. I have sent him backup of system partition from my Huawei Watch 2.

[avr248]

thanks

[lucychiu]

Great thanks. I have the Android 8.0 update (build# OWDE.180215.017), let me know if there's anything I can provide to assist Jon.

[mileom85]

@lucychiu I have submitted system partition from same build. When @jamorham creates patch you will also be able to use it 😄

[jamorham]

I will start work on this shortly

[jamorham]

Can you guys give me all the information about build numbers, kernel version etc from the Settings -> About page from the watch? Thanks.

[lucychiu]

Build: OWDE.180215.017 Google WearOS 1.1 Android 8.0.0 Kernel - cannot find.

[avr248]

Build: OWDE.180215.017 Google WearOS 1.1 Android 8.0.0 Kernel - cannot find.

[ralf-ms]

Buiild: OWDD.180215.018 Google WearOS 1.1 Android 8.0.0

[alexmoir1]

I have set this up for my son. We have a Freestyle libre. On top of that sits an Ambrosia Bluecon device. The Bluecon converts the Libre readings from NFC to Bluetooth & sends them to Xdrip+ running on the watch. The (Android Wear 2) watch sends the data to his (Android) phone, follower (Android) phones & Nightscout in the cloud. When we first set it up it seemed to work great, but the problems arise when the watch loses bluetooth connection to the Bluecon. It's then a major hassle to get it re-connected. So until a more robust solution comes out we've stopped using it. I prepared the attached document to help. BlueconLibreXdripNightscout.docx

[mbickelhaupt]

Build: OWDD.180215.018 WearOS 1.1 Google Play Services: 12.5.29 Android 8.0.0

[mbickelhaupt]

I have the event logs of a failed attempt to use the Huawei 2 on the 05.04.18 build paired with a g5. Succeeded in "found,connecting" but no BGL data pickup.

[jamorham]

I am working on this now. I will update with progress as soon as I have some.

[avr248]

Good Luck

[mileom85]

Build: OWDE.180215.017 Google WearOS 1.1 Android 8.0.0

[jamorham]

Okay, I have now been able to receive readings from the G5 but it isn't yet stable. I'm still working on it, getting closer though.

[jamorham]

Okay, I now have demigod mode working as well. Quite a few modifications are needed overall though.

Is everyone on this thread using the 4G version of the watch?

[ralf-ms]

No, just the wlan version...

[lucychiu]

Hi Jon, That's great news. I am using the 4G version.

Sent from my mobile device

On Mon, 14 May 2018, 8:45 PM JamOrHam, notifications@github.com wrote:

Okay, I now have demigod mode working as well. Quite a few modifications are needed overall though.

Is everyone on this thread using the 4G version of the watch?

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

[alexmoir1]

Yes, 4G

Regards

Ali

On 2018-05-14 09:45, JamOrHam wrote:

Okay, I now have demigod mode working as well. Quite a few modifications are needed overall though.

Is everyone on this thread using the 4G version of the watch?

-- You are receiving this because you commented. Reply to this email directly, view it on GitHub [1], or mute the thread [2].

Links:

[1] https://github.com/NightscoutFoundation/xDrip/issues/374#issuecomment-388742028 [2] https://github.com/notifications/unsubscribe-auth/AXEqRKvHa_iyvUUjQghsGge4Zl3-nUjDks5tyUQZgaJpZM4S-S_E

[mileom85]

Yes, 4G version.

[jamorham]

I'm planning to release two versions. The first version coming very soon will fix the bluetooth and add demigod mode.

A second later version will attempt to optimize battery life and add any other niceties I can get working.

[ralf-ms]

Hi Jon, splendid! Sounds great! Will the versions you mentioned above be functional for both kind of the huawei watch 2 (4G and wlan only)?

[jamorham]

Okay guys, grab the care package here!!

https://drive.google.com/open?id=1vls9Vh1tRqAwSpqcHG71EvWhfuooDhn3

I have tested this with the 4G version. I don't know if it will work on the non-4g version. Please try that out too and when the patches are applying look very carefully at which ones say OK or ERROR so I know where changes may need to occur.

Please make sure to backup your watch before making any changes. In TWRP the system image backup and the boot image backup are the most important. Make sure you also pull these off your watch sdcard and keep them safe. You will need these to back out the changes if anything goes wrong and if I produce a version 2 of the patch I will likely want you to restore from the backup first.

The tests I have done so far look good with this. It should work with G5 and other collectors like miaomiao.

There may still be a stability issue, if you find you're not getting any data then reboot the watch. In my tests it seems like if it doesn't work a reboot fixes it and then it remains solid.

How does it work a live environment? I don't know so please test this and let me know!!

[avr248]

Thanks a lot, I'll try it and update later

[ralf-ms]

Hi Jon, unfortunately not working for OWDD.180215.018: spinning circles for more than 30 minutes. Got "ERROR: for demigod mode" when applying the patches. I did not see any other error messages.

[avr248]

not working for OWDD.180215.018

[jamorham]

@ralf-ms are you able to restore the system image backup? Then delete the services.patch and services.patch2 file from the update-patch zip file and try again. If you can email me link me to a system parititon backup I can take a look at what is different for those patches on OWDD model.

[ralf-ms]

No, I did a clean install with the OWDD rom provided here: https://developer.android.com/wear/releases/wear-preview-downloads (non-preview-image sawfish-factory-OWDD.180215.018.tgz) After removing the two services.patch* files, patching succeeded except for the demigod modes (see attached image), and I'm now able to run the collector on the watch! 👍 I will send you a link to the TWRP backup I made before patching.

[lucychiu]

Currently reinstalling from image in XDA developers. (https://forum.xda-developers.com/watch-2/development/rom-t3705589) Wasn't able to use adb to pull and push using Windows 10. There's a known issue with the creative update. I'll try again in a few days using a Windows 7 system.

[jamorham]

I can probably produce the alternate patch version from the OWDD files available on the android.com link @ralf-ms posted. The main issue with running without demigod mode is that there may be problems with the watch sleeping and missing readings.

[avr248]

Are you going to create a patch soon?

[lucychiu]

Windows 10 Creative Update - ADB pull and push doesn't work, however I was able to use this workaround here to do the ADB pull and push: https://wiki.lineageos.org/adb_fastboot_guide.html. Note: this didn't work for me while I had the TWRP app running.

I did a clean install of Android 8.0 using the image from XDA developers last night, and applied the security and demigod patches. All the patches failed... I wonder if it's because there's a TWRP app install on the Android 8.0 image.

As my watch was purchased from China (Model LEO-DLXX), last year I did flash it with an International rom in order to use the watch properly. (https://forum.xda-developers.com/watch-2/how-to/guide-how-to-flash-english-firmaware-to-t3602140) So I will do a clean install with this rom with Android 7 and wait for the OTA updates back to Android 8.0.

I have used TWRP in the past to load Cyanogenmod onto a tablet, and I was able to copy files to the SD card from the windows explorer. I think the Huawei drivers are not installed properly on my laptop which is why the watch's internal storage didn't show up on windows explorer; and why I was using the ADB commands.

[jamorham]

@avr248 yes I will work on a proper patch for the non-4g version shortly.

[avr248]

thank you so much!

[jamorham]

The care package is updated now with an alternate patch for the non-4g version of the watch:

https://drive.google.com/open?id=1vls9Vh1tRqAwSpqcHG71EvWhfuooDhn3

I haven't been able to test this as I only have a 4g one, so I would be very grateful to know if this works or not. If it fails then you will likely need to restore the system image from backup or reinstall it from the factory image link posted by @ralf-ms above.

@ralf-ms if you apply this then it should enable demi-god mode but the already applied patches will report failed but that wont matter.

[izywizy]

I've been following this thread as I have the Watch 2 non-4g.

I've just applied the 'care package' and can confirm everything went very smoothly as I'm quite familiar with twrp as I use or have used it on quite a few devices so your instructions were very easy to follow.

There were no errors during installation which was done on a Windows 10 PC.

I have tested 'force wear collection' and it works perfectly with libre/blucon combo, not tested wear collection when phone is out of range yet, i'll do that tomorrow.

I'd like to offer my gratitude for the work you've done on this and also to you and the other devs for the brilliant xdrip app.

best regards.

[mbickelhaupt]

Trying to get the watch into fastboot mode. Running on a linux system, I can recognize the device with "fastboot devices" but when I issue the command "fastboot oem unlock" (or any fastboot commands) I get the message waiting on device. On the watch end of things, it is just happily sitting in fastboot mode without receiving any commands. I have enabled adb debugging, is there something I am missing on the watch end that is hanging me up? Sorry to take us back to kindergarten. I can just barely do these flashing and running terminal things, and when something goes awry, I get stuck pretty quick.

TKQ7N17C05000164 fastboot bickelhaupt@bickelhaupt-HP-ENVY-m6-Notebook-PC:~$ fastboot oem unlock < waiting for device > ^C bickelhaupt@bickelhaupt-HP-ENVY-m6-Notebook-PC:~$

[lucychiu]

@izywizy just wondering, do you have the normal windows 10 or one with creative update? Also, do you have the Huawei drivers installed?

[lucychiu]

@mbickelhaupt can you try 'adb devices' and see if it lists your watch?

P.S. With my fresh install on the watch and after enabling adb debug. I went on command prompt and typed 'adb devices' then on the watch it popped up with a message asking me to allow the computer access. This is with the watch running normally, not in fastboot.

[mbickelhaupt]

I'm working with Ubuntu. I have a windows computer that I would prefer, but it sounded like Linux would be easier. I can connect to the watch on adb, and have always accept this computer. I can even run adb commands and force it into the fastboot. Just nothing in fast boot other than the computer recognizing the watch.

[lucychiu]

Okay, I don't know much myself either. Just following the instructions and using Google to work through the issues I'm having.

Sent from my mobile device

On Thu, 17 May 2018, 5:45 PM mbickelhaupt, notifications@github.com wrote:

I'm working with Ubuntu. I have a windows computer that I would prefer, but it sounded like Linux would be easier. I can connect to the watch on adb, and have always accept this computer. I can even run adb commands and force it into the fastboot. Just nothing in fast boot other than the computer recognizing the watch.

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

[jamorham]

@mbickelhaupt I had this problem on one linux box and had to switch to another. I think there may be some low-level usb compatibility issue with the watch itself. Having said that when I tried it another time it did work okay on the first box. I would try another USB port, hub or even another machine if that is an option.

[jamorham]

@izywizy thanks for confirming the non-4g version also works! phew

[avr248]

yesss!!! it work!! thank you very much!!

[izywizy]

@lucychiu, If you're talking about the Win10 April update then no, I did install it but had to revert to the previous version as I encountered the Chrome freezing issue that many have but up to date other than that.

I don't have the Huawei drivers installed just the universal adb drivers which seem to work just fine with any device I'm fiddling with.

@all, I have tested the 'out of range wear collection' by turning off the phone, I waited a good 20 mins or so but no collection. I checked the bluetooth settings on the watch and there was an unknown device showing, I removed that and then scanned and the watch picked up the blucon and registered it but always shows as unavailable. I rebooted the watch and blucon and then after approx 12 mins the watch connected to the blucon and I got my first reading and it carried on collecting for around 30 mins until I turned on the phone again.

The good news is it carries on collecting even when the screen is off so that should help battery usage somewhat.

Not so good news when switching back to the phone, I waited 30 mins and no automatic switch back to phone collecting.

@jamorham regarding the above issue, I notice that when using the watch as collector the data source is always listed as LimiTTer and works fine and when I turned on phone to switch back to phone collecting the data source is still showing as LimiTTer, the problem here is that the the phone will never start collecting unless the data source shows as Blucon, and that always requires a restart of the Blucon.

any suggestions ? thanks.

[ralf-ms]

the new patch worked for me as well (with the bt patches failing like Jon mentioned because they've been already installed). switching back from phone to watch and vice versa seems a little bit messy, I've also found that there are problems sometimes (where you have to wait for 10-15 minutes), but also found it to be running at once and then in turn it is not a bit working (where you have to reset blucon, reboot watch, disable phone's bt and so on). Unfortunately I am not able to tell an exact procedure which path to follow if it is not working at all. When having difficulties I see on the Systemstatus page "Watch Service State: Attempting connection" as well as "Bridge Device: Connecting", without neither of it advancing to "connected".