Huawei watch 2 support

[andreagubellini]

Hi everyone,
I was thinking about this for quite some time.
Is there any chance we could get Asteroid on huawei watch 2?
I would be glad to help on the porting.

[jrtberlin]

Hi, we have the Huawei watch 2 on the list of possible ports. I don't think that we have made any progress on the watch.
I would start by checking the porting guide (https://asteroidos.org/wiki/porting-guide/).
If you have questions make sure to check our IRC.

Additional note: this is the repository of the sync client for Android.

[nabeelmoeen]

just saw support being added for the Huawei watch GT 2... hoping the huawei Watch 2 classic would be there soon as well

[ajayjohn]

Same here. +1 for the Huawei Watch 2 (LEO-DLXX)

[jrtberlin]

To get started on the Huawei Watch 2 we need the partition table of the device.
If somebody has one we could use your help.

Steps to do:

1. Boot TWRP with fastboot boot
2. use adb to get the output of: ls -al /dev/block/platform/soc/7824900.sdhci/by-name

[dave18]

Hi, I'm new to all this, but is this the right output?

~ # ls -al /dev/block/platform/soc/7824900.sdhci/by-name
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
drwxr-xr-x 2 root root 740 Jan 1 04:29 .
drwxr-xr-x 4 root root 820 Jan 1 04:29 ..
lrwxrwxrwx 1 root root 21 Jan 1 04:29 DDR -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 Jan 1 04:29 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Jan 1 04:29 abootbak -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Jan 1 04:29 boot -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Jan 1 04:29 cache -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 Jan 1 04:29 cmnlib -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 Jan 1 04:29 cmnlibbak -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Jan 1 04:29 config -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Jan 1 04:29 devinfo -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Jan 1 04:29 fsc -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Jan 1 04:29 fsg -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Jan 1 04:29 keymaster -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Jan 1 04:29 keymasterbak -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 Jan 1 04:29 keystore -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jan 1 04:29 misc -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Jan 1 04:29 modem -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 Jan 1 04:29 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 1 04:29 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 1 04:29 nfc -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 1 04:29 nvbin -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 Jan 1 04:29 nvdata -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 1 04:29 oem -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Jan 1 04:29 recovery -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 Jan 1 04:29 reserved -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 Jan 1 04:29 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Jan 1 04:29 rpmbak -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Jan 1 04:29 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Jan 1 04:29 sbl1bak -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Jan 1 04:29 sec -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 Jan 1 04:29 splash -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Jan 1 04:29 ssd -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jan 1 04:29 system -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 20 Jan 1 04:29 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 1 04:29 tzbak -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Jan 1 04:29 userdata -> /dev/block/mmcblk0p35

[jrtberlin]

Thanks @dave18, this is what we are looking for!

[dave18]

Glad I could help. happy to test any builds on my Watch 2 if needed.

[MagneFire]

@jrtberlin and I are working on a port for the Huawei Watch 2(sawshark/sawfish). We don't own this watch so this is a unique opportunity for the community to help 😉

We both own the regular Huawei Watch (sturgeon) of which I did the port.

At first glance the two seem very similar. The (probably) biggest challenge is to port the Android base from Marshmallow to Nougat.
It turns out that some people are/were already working on this (https://github.com/iuncuim/android_manifest/commits/ng and https://github.com/asteroid-platy/android_manifest)

The current road map we will use to get a working port will be as follows:

• Port sturgeon to an Android 7 base.
• Make Linux kernel boot on sawshark/sawfish (needs debugging help from you)
• Get partition mapping (done thanks to @dave18)
• Create system tarball for sawshark/sawfish(using the Android 7 base)
• Make the compositor work
• Get touchscreen to work
• Get sensors to work(seems similar to sturgeon)
• Get Bluetooth to work(may also be a struggling point)
• Get modem to work

A repository for the Huawei Watch 2 has already bee setup: https://github.com/MagneFire/meta-sawshark-hybris

Of course, when we have something to test we will publish that here. Though, keep in mind that porting the Android base is a time consuming task, meaning that it'll probably take sometime before we have anything to test for you.

[flocke]

@jrtberlin @MagneFire Thank you for working on this. I own a Huawei Watch 2 (sawfish) and am pretty well versed in both the Linux and Android ecosystems as well as development for both (I'm the author of andOTP). So if you need any specific information or testing feel free to contact me.

[MagneFire]

Sorry for not getting back at this sooner. But I have successfully ported the Android base to 7.1.1 on sturgeon (the Huawei Watch Classic).

And I have just built a version for the Huawei Watch 2. This one has the system base from a sawfish build. Which is apparently the Bluetooth variant. So in any case I am not sure if it will work for sawshark LTE variant.

Download: https://www.dropbox.com/sh/h0kzcky4qls3v60/AAC7nBfhSoPpStSQ6Gx4h769a?dl=0

First of all, I don't expect it to boot fully. So depending on how far it gets in the boot process there are different things to debug.

To flash

Just follow the general instructions on the install page (pick for example sturgeon). I recommend using the temporary installation as this makes things easier to debug.

It reboots

The first thing to try is to boot AsteroidOS with --cmdline debug-ramdisk parameter.
Keep an eye on device manager/dmesg to see if an ADB device comes available. It is still possible that it reboots. In that case I need to do a little more debugging 😉

EDIT:
Just a heads up, I have updated the version linked. It has the following changes integrated from sturgeon:

• Update libhybris to latest upstream.
• Fix vibrator
• Fix setting props
  • This fixes some weird issues where files couldn't be found.
• Create a symlink from sawshark to every sawfish library.

Things that could work

Of course I couldn't test this so this is a list of things that may work:

• Boots
• Graphics
• Vibrator
• USB in ADB mode
• Sensors (didn't look into this at all, but binaries are at the same location)
• Speaker
• Microphone
• Touchscreen (Assuming that event0 is the touchscreen device)

Things that are likely broken

Some bugs are general on all platforms sawshark will be no different 😄

• Tap-to-wake
  • sturgeon needs patches for it to work https://github.com/AsteroidOS/meta-sturgeon-hybris/blob/master/recipes-kernel/linux/linux-sturgeon/0009-synaptics_i2c_rmi4-Adds-a-wakelock-when-the-screen-i.patch and https://github.com/AsteroidOS/meta-sturgeon-hybris/blob/master/recipes-kernel/linux/linux-sturgeon/0007-tap-to-wake-fix.patch
  • sawshark does however not use a synaptics driver, a cypress driver is used instead (https://android.googlesource.com/kernel/msm/+/64509af72645d75ac23bae112b183b2b3cd27dd6)

Things that won't work

Some of these are bugs and some aren't actually finished yet:

• Bluetooth (misses patches)
• USB in network/developer mode(This is a bug on sturgeon, must occur here too)

[FlorentBrianFoxcorner]

@MagneFire thank you.

Tried booting the BT variant, following https://asteroidos.org/install/sturgeon/

The watch is unlocked now. Followed -> 2 b. Temporary installation:

adb push -p /home/fv/Downloads/asteroid-image-sawshark.ext4 /sdcard/asteroidos.ext4
adb reboot bootloader
fastboot boot /home/fv/Downloads/zImage-dtb-sawshark.fastboot

=> The watch then boots again into Wear OS.

Then tried:

fastboot --cmdline "debug-ramdisk" boot /home/fv/Downloads/zImage-dtb-sawshark.fastboot
fastboot: unrecognized option '--cmdline'
fastboot -c "debug-ramdisk" boot /home/fv/Downloads/zImage-dtb-sawshark.fastboot
downloading 'boot.img'...
OKAY [ 0.448s]
booting...
OKAY [ 0.162s]
finished. total time: 0.609s

=> watch hangs in fastboot and does not react on anything except holding both buttons until reset... then again booting into Wear OS

fastboot --version
fastboot version 1:8.1.0+r23-5ubuntu2
Installed as /usr/lib/android-sdk/platform-tools/fastboot

[MagneFire]

@FlorentBrianFoxcorner Thanks for testing! 😄
It is actually great to see that the watch hangs when you boot it with fastboot -c "debug-ramdisk" boot /home/fv/Downloads/zImage-dtb-sawshark.fastboot.
Can you verify whether or not you can connect to the watch using adb when it is frozen in this mode?
If adb shell works, can you send the logs for dmesg?
And try to find the asteroidos.ext4 file using the commands (in adb shell):

. /machine.conf
mkdir /sdcard
mount /dev/$sdcard_partition /sdcard
ls /sdcard

Also, does it show the AsteroidOS boot logo at this point?

Another thing, can you also send the output of dmesg on WearOS?

For reference sake, this may also be helpful: https://asteroidos.org/wiki/boot-process/

[FlorentBrianFoxcorner]

@MagneFire, YES, I was able to connect!

dmesg-asteroid.txt

It does not show the logo but is stuck at the frozen fastboot menu.

The kernel seems to lack CONFIG_QUOTA, I was NOT able to mount sdcard, mind dmesg.
The partition layout and the image do seem to be ok. I checked with:

adb pull /dev/mmcblk0p35 ./
sudo mkdir /media/debug
sudo mount -o loop ./mmcblk0p35 /media/debug

-> My Ubuntu box was able to mount the resulting image RW alright.

For dmesg on Wear Os I need root or is there a shortcut?

127|sawfish:/ $ dmesg
dmesg: /dev/kmsg: Permission denied