NightscoutFoundation / xDrip

Nightscout version of xDrip+
https://jamorham.github.io/#xdrip-plus
GNU General Public License v3.0
1.38k stars 1.14k forks source link

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

Closed avr248 closed 3 years ago

avr248 commented 6 years ago

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

jamorham commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

@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 commented 6 years ago

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 commented 6 years ago

@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 commented 6 years ago

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 commented 6 years ago

@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 commented 6 years ago

@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 commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

@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 commented 6 years ago

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, notifications@github.com 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 commented 6 years ago

@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 commented 6 years ago

@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, notifications@github.com 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 commented 6 years ago

@lucychiu ah dexcom, not miaomiao.

izywizy commented 6 years ago

@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 commented 6 years ago

@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 commented 6 years ago

@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 commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

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, notifications@github.com 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 commented 6 years ago

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 commented 6 years ago

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, notifications@github.com 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 commented 6 years ago

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

lucychiu commented 6 years ago

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 commented 6 years ago

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

lucychiu commented 6 years ago

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

borijess commented 6 years ago

How long does your battery lasts on average?

lucychiu commented 6 years ago

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 commented 6 years ago

@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 commented 6 years ago

"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, notifications@github.com 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 commented 6 years ago

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

borijess commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

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, notifications@github.com 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 commented 6 years ago

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

borijess commented 6 years ago

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

Isaksen commented 6 years ago

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 commented 6 years ago

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 commented 5 years ago

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

jserajlic commented 5 years ago

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 commented 5 years ago

@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 commented 5 years ago

fantastic, tnx my man

Garweho commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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

william-so commented 5 years ago

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.