I have an Amazfit Neo that I use with the amazing Gadgetbrigde on Android.
But I believe most Huami watches (at least the cheap/early non-Zepp-OS Amazfit and Xiaomi) are pretty similar, in my understanding, adding support for one would open up the door to quite a few of them (with some adaptions per watch, of course).
Could you explain some of the (planned?) repowerd changes? Especially those that deal with cpufreq? It sounds like a cool concept. But where do we configure this for devices? And what else might touch cpufreq settings (android init scripts, vendor-specific stuff...)?
I have an Amazfit Neo that I use with the amazing Gadgetbrigde on Android.
But I believe most Huami watches (at least the cheap/early non-Zepp-OS Amazfit and Xiaomi) are pretty similar, in my understanding, adding support for one would open up the door to quite a few of them (with some adaptions per watch, of course).
For the record, I just gave ubuntu-touch-mainline-generic-amd64.img a try on my Intel tablet (Dell Venue 8 Pro).
After downloading I wrote the image to an USB stick with dd, connected the stick using an OTG adaptor and selected it in the boot device dialog [1].
It booted into gui mode just fine, but lots of stuff (like the orientation sensor or turning off the screen) doesn't work. It's a cool proof of concept anyway, especially since the performance is really good, considering that this is an old Atom tablet and booting from a slow USB drive.
YMMV, because this tablet has some quirks even without UT.
I think this might be worth looking into, because there are a lot of x86 tablets around that are to slow for a heavy Linux desktop with Gnome and all its bells and whistles, but would be ideal as a fast, modern UT device.
Oh, btw, you can make it run in a recent VirtualBox. I had to convert it using something like:
VBoxManage convertfromraw ubuntu-touch-mainline-generic-amd64.img ubports.vdi --format vdi
Make sure to enable multitouch input in the VM settings, if you have a tablet or convertible 
[1]: The tablet originally ran regular Win 8 (or 10), and has a "normal" BIOS/EFI.
Thanks for the detailed writeup, although I prefer booting from an .img instead of the partition. This way I can just reflash boot and have my Android back 
By the way, I saw that you are struggling with the bluetooth as well. Did you make any progress there (assuming that karin has the same bcrm43... as suzuran)? I believe (might be totally wrong) that Bluedroid is located pretty deep in the kernel, and you cannot really get access from the outside (meaning that this is a kernel issue). I never found what to (back)port from other devices to make it work, though.