Xdrip: 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, [e-mail] 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, [e-mail] 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".

[jamorham]

Ok good news that the patches are working. I haven't tested blucon on wear. I know G5 and MiaoMiao are working well with this method. There may be other issues with the blucon connector on wear which are unrelated to whether the bluetooth stack is working at all.

[ralf-ms]

Hi Jon,
complete agreement!
This is a big step forward and I can finally use the watch as a collector which was not possible before.
I'm very grateful for all your effort, work and patience!!
Lets gain some experience over the next days and find out what has to be done in specific situations.
Thanx again for all your support!

[lostboy86]

Sorry i have a 4g, i have flashed boot security fix and demigod patch etc for 4g, but for me the two demigod not applied from twrp, how i can resolve?

i have this rom : https://forum.xda-developers.com/watch-2/development/rom-t3705589

Is also for me for the diabethes, for xdrip.

Can you help me Joan? Thanks a lot

[lucychiu]

@izywizy the April date hasn't pushed through yet to my laptop. I think it's because I did a fresh install removing all the bloatware which has caused me a few issues other than this. Good to know about Chrome freezing with this update.

@all I have managed to apply the patches successfully and enabled demigod mode on my 4G watch. But I can't test until I fix my transmitter.

My problems have been trying to copy files across

1. When I plug the watch in, windows opens a blank folder so I can't copy the backup and patch files between devices.
2. adb pull and push doesn't work for me while in twrp, but works while the watch is running normally.

Also after using twrp to do a backup, for some reason my watch doesn't boot, gets stuck with the Huawei logo. So this time booted back onto twrp and turned on adb sideload and installed the patches that way.
And I've setup the watch now and used ADB pull to grab the backup file. 😊

Will update again when i've got the transmitter working and can test with the watch.

[lostboy86]

Do you have a original rom oreo, or my rom into link above?
Because my bt patch work ok, but i had two error for demigod mode not apply, can you help me?

Thanks a lot

[lucychiu]

@lostboy86, I don't have the original rom for my watch (model LEO-DLXX), which is from China and I replaced it with International rom.
I did try the Oreo rom that you linked above and I received errors when patching it (can't remember which ones). So I went back to Android 7 waited for the OTA updates and have now applied the patches successfully.

[jamorham]

What sort of battery life are people seeing? Even before patching the watch I have for testing here it didn't seem to do a whole 24 hours. More like closer to 12 hours. 4G standby seems to consume 30% of power even when the watch is in wifi-range all day.

[lostboy86]

@jamorham my watch, if i put only bluetooth for miaomiao+libre connect, battery is ok for almost 3/ 3,5 days (ALL other function off : gps, 4g, wifi, gesture, etc).
I know i have a big request, but my watch is 2,5 days battery also because i have a rom above, can you provide your patch for this rom? Is the most rom used for this watch, can increas the battery very very good.

@lucychiu damn, you tell me the patch of @jamorham working only with the original oreo rom?

[lucychiu]

@lostboy86 I looked back at my comment 7 days ago. All the patches (A, B, BT, Demigod 1 and 2) failed for me using the Oreo rom. However you mentioned all the patches apart from demigod 1 and 2 worked for you, so there must be something different with that oreo rom.

[lostboy86]

Yes, for me with latest kernel, a,b,bt ok. Demigod 1 and 2 not apply. With Oreo roms xda modified for long battery etc.

[izywizy]

I have a problem since applying this mod, default apps on the watch will not update, the error message is 'not enough space to update apps'

Now this is not the case as the only apps on the watch are the default apps and xdrip !

Anyone else seeing this or can offer a solution ?

[ralf-ms]

If you've made a system-backup on your watch as recommended by Jon, then this will still very likely consume most of the storage.
To delete the TWRP backup directory and the patch files on you watch, use these commands:
"adb shell" (this will get you an interactive shell on your watch), you will get the prompt
sawfish:/ $
Do a "cd sdcard" (prompt will change to "sawfish:/sdcard $") and then a "rm *.zip" to delete the patch-files and a "rm -rf TWRP". Logout with exit.

Check the capacity using the "Wear OS" application on you phone, goto "extended settings" on your huawei watch and then to storage to check the used and free disk space. It may take a minute or so to get updated values after the above changes.

Here is my complete session log (commands I typed are in bold) from a linux host.
I used df -h on the watch to check (_Avail_ for available capacity) how much I could free, the used space went down from 1.9G to 512M.

root@antares:~# adb shell
sawfish:/ $ cd sdcard
sawfish:/sdcard $ df -h /data
Filesystem Size Used Avail Use% Mounted on
/dev/block/mmcblk0p35 2.2G 1.9G 313M 87% /data
sawfish:/sdcard $ rm *.zip
sawfish:/sdcard $ rm -rf TWRP
sawfish:/sdcard $ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/block/mmcblk0p35 2.2G 521M 1.7G 23% /data
sawfish:/ $exit
root@antares:~#

[izywizy]

@ralf-ms, thanks very much, never thought of that so it's likely the problem.
Wear on phone is showing 2.20GB used/2.42GB total.

and thanks for the detailed instructions which I will carry out when I've finished setting up my new PC.

I did pull the backup to the PC so a safe copy there.

I'll report back when I've done it :)

[lucychiu]

Today I used 'Use Only Wear' mode on. In the past 14 hours, battery started
at 90% and went down to 15%.
At the 10.5 hour mark it lost connection for 30 mins (battery under 40%
from memory), it aggressively restarting collector a few times before I
decided to restart the whole watch. It automatically connected again upon
reboot.

It did lose connection a few times during the day, but the major one was 30
mins and I wasn't patient enough to wait for it to reconnect.

Sent from my mobile device

On Thu, 24 May 2018, 8:28 AM izywizy, [e-mail] wrote:

@ralf-ms https://github.com/ralf-ms, thanks very much, never thought of
that so it's likely the problem.
Wear on phone is showing 2.20GB used/2.42GB total.

and thanks for the detailed instructions which I will carry out when I've
finished setting up my new PC.

I'll report back when I've done it :)

—
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-391485358,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABeN8Gq5lT1iuOH6AvL4JyFmkkIYPh3_ks5t1cZegaJpZM4S-S_E
.

[lostboy86]

@lucychiu Lose connection with MiaoMiao you mean? Only Wear mode means smartphone bluetooth off / without smartphone, and xdrip on watch 2 read directly from miaomiao+libre with bluetooth?

[lucychiu]

@lostboy86 yes the watch is collecting directly from the dexcom transmitter.

I just tried 3 hours with the phones Bluetooth switched off, and the watch
continued to collect from dexcom and send the data to my phone using wifi
(I haven't got a Sim card in). It also sent battery status update.

So the past 3ish hours battery went from 100 to 88%.
Capture rate after 24 hours 99%.

Sent from my mobile device

On Sat, 26 May 2018, 3:12 AM lostboy86, [e-mail] wrote:

@lucychiu https://github.com/lucychiu Lose connection with MiaoMiao you
mean? Only Wear mode means smartphone bluetooth off / without smartphone,
and xdrip on watch 2 read directly from miaomiao+libre with bluetooth?

—
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-392089351,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABeN8Js3c20eQVZCEHf9W2Q68fCpSCDXks5t2B9ZgaJpZM4S-S_E
.

[lostboy86]

@lucychiu ah dexcom, not miaomiao.

[izywizy]

@ralf-ms, finally finished setting up my new PC so had some time to sort out the watch.

Thanks again for the instructions, worked for me and apps now updated :)

Before
/dev/block/mmcblk0p35 2.2G 1.9G 242M 90% /data

After
/dev/block/mmcblk0p35 2.2G 557M 1.6G 25% /data

[ralf-ms]

@izywizy, nice to hear!

@all: so far I'm very pleased and satisfied with jon's patch and bluetooth solution.
I'm using mainly the 'force wear collection ' settings but have also tried the 'connect to watch if phone is out of reach'.
Switching between phone and watch was without any issues, had to wait 10min at most.
Thanks again, Jon, for you quick and functional solution!

[lucychiu]

@All, battery seems to have improved slightly after a few days with the
watch in 'Only Use Wear' mode, getting an extra hour or two... Not sure why.
I have also tried out @izywizy advise to turn off the always on display
today. Started at 100% and after 6.5 hours, it is at 72% and no connection
issues at all. Thanks @izywizy.
This has been amazing not having to carry the phone around. Thanks so much @
JamOrHam.

[borijess]

I applied the patches on my Huawei watch sport 2. It worked over night at a high capture rate. 94 percent. Once I woke up I started to miss data. In the debug settings I added the scan constantly option. Is anyone else having these issues?

[mileom85]

I have finally applied patch everything went ok. I was planning to use watch when smartphone is not in range. Yesterday I have managed to connect to watch. Then I have switched to smartphone and haven't managed to connect to watch anymore. I don't get it. I force Wear collection and it can't connect. Did anybody else have this problems?

[lucychiu]

Have you tried rebooting the watch?
Also in the watch pref settings under xdrip G5, is force screen always on
checked?

Sent from my mobile device

On Tue, 26 Jun 2018, 3:51 AM mileom85, [e-mail] wrote:

I have finally applied patch everything went ok. I was planning to use
watch when smartphone is not in range. Yesterday I have managed to connect
to watch. Then I have switched to smartphone and haven't managed to connect
to watch anymore. I don't get it. I force Wear collection and it can't
connect. Did anybody else have this problems?

—
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-400000955,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABeN8AN4oGZIcx3s8utTYl_48pEJjLEBks5uAQbugaJpZM4S-S_E
.

[borijess]

I patched my watch and I still get a lot of missed readings. It works for a while an then it missings readings for 10 to 20 minutes. What are your readings besides authenticate before each reading?

[lucychiu]

I only have force screen always on and auth G5/read checked in the settings.

Sent from my mobile device

On Tue, 26 Jun 2018, 12:13 PM borijess, [e-mail] wrote:

I patched my watch and I still get a lot of missed readings. It works for
a while an then it missings readings for 10 to 20 minutes. What are your
readings besides authenticate before each reading?

—
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-400134757,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABeN8IzA3ircEV2rwW0eFLVwSFU8mdx-ks5uAXy7gaJpZM4S-S_E
.

[borijess]

Does force screen on kill battery? And does it keep the screen on all the time? What is your capture rate?

[lucychiu]

Yes, it does kill the battery. The workaround is to Force Screen on Xdrip
Prefs settings and on the watch's main display settings, disable always on
display. That way you will get a full day of battery. Capture rate 90-95%.

[borijess]

How do u turn off screen? Does it shut off automatically?

[lucychiu]

Go to: ​Settings - Display - Always-on screen​.
The screen shuts off automatically in 5 seconds...

[borijess]

How long does your battery lasts on average?

[lucychiu]

With force screen always on, I had to charge twice a day.
With force screen off, I charge once a day, but my guess it will last 1-1.5
days depending on the watch usage.

[mileom85]

@lucychiu I have tried to reboot watch multiple times. It still can't connect. All patches have been installed without errors. I don't get it. I don't have force screen always on in xDrip+ prefs, but Always on screen is turned on in Settings.

[lucychiu]

"I don't have force screen always on in xDrip+ prefs, but Always on screen
is turned on in Settings.."

Do the opposite.. force screen on in xdrip prefs. Always on turned off in
settings.

Sent from my mobile device

On Wed, 27 Jun 2018, 1:16 AM mileom85, [e-mail] wrote:

@lucychiu https://github.com/lucychiu I have tried to reboot watch
multiple times. It still can't connect. All patches have been installed
without errors. I don't get it. I don't have force screen always on in
xDrip+ prefs, but Always on screen is turned on in Settings.

—
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-400303768,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABeN8PvPTrNEDWs4yXX40Qzu3B9aD1xBks5uAjQ4gaJpZM4S-S_E
.

[mileom85]

@lucychiu I don't have that option in xDrip+ prefs. I don't understand why.

[borijess]

Why if the patch was applied to the Huawei do we still need to select force screen on in settings on watch. On the polar M600 I did not have to chose that option after I applied the patch.

[lucychiu]

You've selected xdrip prefs - xdrip G5 settings - force screen?
Otherwise then I'm not sure. My xdrip build from my phone is 14 June too.

@borijess I don't know. It's just something I read on Facebook in the xdrip
group when someone else downloaded the patch and couldn't get it working.
This is what they had to do and it solved it for me when I took a few weeks
break and then I couldn't connect to the transmitter anymore.

>

[lucychiu]

I'll try and find the post...

Otherwise this section in the watch guide can shed light as to why you
didn't need it for the Polar.

There are the following two, known exceptions:

-

Force Screen On - Some watches, such as the Moto 360 2nd Gen, fall into
deep sleep preventing the BT Collector from retrieving the transmitter
data. Enabling this preference will trigger the watch to wakeup to read the
transmitter data, then fall back to sleep. This preference is
experimental but may be helpful for watches that do not support the
Always-on
screen feature.

https://github.com/NightscoutFoundation/xDrip/blob/master/Documentation/WatchGuide.md#xdrip-bt-settings

Sent from my mobile device

On Wed, 27 Jun 2018, 8:32 AM borijess, [e-mail] wrote:

Can you post link to the facebook conversation of this app?

—
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-400451979,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABeN8BBeEIXZbgIrGDzjvK4MPkGXUj5Lks5uAppJgaJpZM4S-S_E
.

[borijess]

I found the link on xdrip. Thanks for the info.

[borijess]

Are you able to input treatment from watch? I can not. Dont know if I am missing a setting.

[Isaksen]

Question: Buying a new watch within a day or two?
Is Huawei SmartWatch 2 4G working now? (looking for non phone solution for school/sports days)

New to all this. Daugther with MiaoMiao/Libre Freestyle - Android phone. Working well
Coder background, so hope to contribute in the future

[tboyd91]

Hi everyone, I am struggling to successfully install the patches provided by jamorham and I hope that someone can help me fix my problem. So far I have installed the update patch and security patch; demi God mode was enabled but the BT patch was unsuccessful. I followed the instructions provided in the care package and I have no clue where I went wrong. What would cause the BT patch to fail?

[jserajlic]

Hi, I have huawei watch 2, build OWDE.180926.001.A1, is there any solution to set it as collector.
tnx

[jserajlic]

Solved,
flashed with android_kernel_huawei_sawshark-oreo-wear-dr
and
OWDE.180215.017_LEO-DLXX_Stock
patched with this instructions
bluetooth patched

ERROR with demigod mode
ERROR with demigod-2 mode

for now working fine

[lmiekus]

@jserajlic If you are still looking for the original stock roms OWDE.180215.017 you can find here
https://drive.google.com/file/d/1TwtOBmz-01a2EjLFdFnbGi8pqOGEeOCa/view . Use img files from sawshark.zip and fastboot to flash your watch:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
After that apply fix-boot-security.zip and huawei-watch-2-4g-demi-update-patch. I have used twrp provided by jamorham. Both operations are successful.

Solved,
flashed with android_kernel_huawei_sawshark-oreo-wear-dr
and
OWDE.180215.017_LEO-DLXX_Stock
patched with this instructions
bluetooth patched

ERROR with demigod mode
ERROR with demigod-2 mode

for now working fine

[jserajlic]

fantastic, tnx my man

[Garweho]

Hi everyone,
since a week I'm using a Huawai 2 watch as stand-allone collector. Just out of the box. Without patching the watch! I have follwowing Build: OWDE.180926.001.A1 / Modell: LEO-DLXX
My phone is an old Huawai Y625.
I tried it several times and finally found I had to turn off the automatic update in Playstore immy after setup and then also cut Wear OS from Internet in phone settings. I'm not sure if this is really necessary, but when I tried first, the collector stopped working soon after I turned on wifi on the phone. And didn't restart collecting, even after rebooting the watch or/and phone. But when I do factory reset on the watch, it works right after installing xdrip on the watch.

[lee-b]

Worked for me, without firmware changes, with Glimp, but not Xdrip. Or seemed to at least. I didn't use glimp for long due to the relative lack of features vs. xdrip. Could other HW2 users confirm?

[psvtg]

Guys, please help me! I have Dexcom G6, Xiaomi Redmi 6a and Huawei Watch 2 LTE with Demigod running xDrip+ v.20190518. When I make my HW2 as the collector it can't send data to my Redmi and so my Redmi can't send data to NightScout (my Heroku website) and Dexcom Share. HW2 only collects the data itself. Is there any way to fix this issue? It's needed for the kid to go school with only the HW2 and parents could get the data from HW2 from home following the Nightscout (website or xDrip follower) on their phones.

[jserajlic]

Did you try over wifi connection. If wifi is ok then you need to check your apn setings.

[william-so]

I have the same issue as @psvtg. However my setup is W2 LTE, Sony X Performance phone. W2 does not work as collector in either mode for me. 'Only' mode or 'Not phone nearby' mode. Doesn't matter if it's on WiFi or 4g.

[psvtg]

Did you try over wifi connection. If wifi is ok then you need to check your apn setings.

I tryed that with wifi and with LTE. No difference. On my System Status page in Redmi's xDrip is automatically set 'Phone Service State: Service Stopped' when I activate Force Wear Collection Service so I think the xDrip app blocks all smartphone acttivity including recieving data from smartwatch and the smartwatch doesn't know how to push the data straight to Nightscout or Dexcom Share.

I installed web browser on my HW2 and it runs normally by wifi and LTE.

Is it possible that this issue is because of the developers' code? Or anybody's got this scheme workable?

[lmiekus]

Make sure that both enable and force are checked under android wear integration. Additionaly be sure that treatments events are not recorded in xdrip - this is causing communication problems betwean smartwatch and phone. We are useing Huawei SW2 LTE with Samsung S9 for last 3 months without any problems. Good luck

[william-so]

@lmiekus can you elaborate 'be sure that treatments events are not...' with a screenshot?

[psvtg]

@lmiekus What version of xDrip are you using?

[lmiekus]

I don't have access to computer now but these are carbs or insulin entries that you can do in xdrip on your phone. For some reason they cause communication problems betwean Phone and smartwatch. If this dosen't solve your problem, try last avalible version of android wear insted of wear os.

[lmiekus]

We are useing xdrip from 13.04.2019

[psvtg]

@lmiekus It seems your vesion from 13.04.2019 works fine! And the new versions don't have access to Wear API. Thousands hugs!

[mbickelhaupt]

@jserajlic If you are still looking for the original stock roms OWDE.180215.017 you can find here
https://drive.google.com/file/d/1TwtOBmz-01a2EjLFdFnbGi8pqOGEeOCa/view . Use img files from sawshark.zip and fastboot to flash your watch:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
After that apply fix-boot-security.zip and huawei-watch-2-4g-demi-update-patch. I have used twrp provided by jamorham. Both operations are successful.

Solved,
flashed with android_kernel_huawei_sawshark-oreo-wear-dr
and
OWDE.180215.017_LEO-DLXX_Stock
patched with this instructions
bluetooth patched
ERROR with demigod mode
ERROR with demigod-2 mode
for now working fi0ne

I have the OWDD.180926.001.A1 (Classic Watch 2 non-LTE) I am struggling to successfully patch it and get demigod mode up and running.
I have tried flashing directly with the "update patch" and "fix boot security" with error messages
I have also tried flashing the sawfish ROM from your previous post, created by JanJan, so now my version is OWDD.180926.001.A1-9 Feb-JanJan, and still no luck. Any advice on what to do with this non-LTE version of the classic?

Also, I have a huawei watch sport 2 (non-LTE) that I was able to flash successfully and theoretically works however the mounts for the strap are broken and not repairable. I tried to make and use a recovery from the watch to flash onto this new classic to no avail. I'm not very talented at this stuff so there may be a way to use this old watches recovery that I do not know of.

Thanks for the help

[greenninjas]

@jamorham any chance for you to rebase patches against 4G version Build number OWDE.180926.001.A1 ?

Thanks!

[wisefolks]

Solved,
flashed with android_kernel_huawei_sawshark-oreo-wear-dr
and
OWDE.180215.017_LEO-DLXX_Stock
patched with this instructions
bluetooth patched

ERROR with demigod mode
ERROR with demigod-2 mode

for now working fine

I also have huawei watch 2, build OWDE.180926.001.A1 and I would appreciate it if you could tell me how to Fash it to collector.

https://github.com/NightscoutFoundation/xDrip/wiki/Patching-Android-Wear-devices-for-use-with-the-G5
I referred to the above address but it was not applicable for the build number of OWDE.180215.017.

If you know how to Fash as a Collector with build OWDE.180926.001.A1, I would appreciate your help.

My e-mail address is [email protected].

[mustang011]

I was flashing heawei watch 2 4G to old firmware (original stock roms OWDE.180215.017). I applied patches. MiaoMiao 2 Reader does not work with this watch (xdrip nightly 2019.10.27). In addition, battery life has been reduced by half. I'm going back to the latest firmware and waiting for the patch update for the new firmware (OWDE.180926.001.A1).