@Ernst-Jan15 Interestingly, I had the same problem when building a new version for my Lenovo Tab M8 this Monday. No overlay keyboard at all.

@MrT10001 Waydroid starts. I opened all pre-installed apps, took a selfie, install F-Droid via the browser, installed Fossify Gallery from there, and viewed the photo. At this level, it works.
I did not try any serious Android app. There was a notable delay between pressing the button in the camera app and the photo being taken. I did not run other UT apps parallel. It does not feel like a lot of fun (like Android on this device), but it runs.

Latest build has the following updates:

• Now building Noble
• Waydroid working again
• Fixed some typos in the udev rules

Annoyingly, the missing letters seems to be worse on Noble. I did not yet find a way to fix that.

Have fun,
Kai

@neonmodder123 I can reproduce the hang, which is good.
I think there is no binderfs in the kernel 4.9 - simply too old for that.

@neonmodder123

complains something about not finding device sensors.

I'll check as soon as I get my next kernel change working.

@CaptainTalon Thanks for trying. What did you do with waydroid? I could install it, and it started it (takes an eternity to come up though), but I only tried the web browser. I think the biggest problem is the limited memory of the device.

@itsjusthim Thanks for trying.
The kernel misses the telephony support, which causes the imei not showing up. I only own the F model, so I cannot help with this. (n case you would like to try yourself, replace akita_row_wifi with akita_row_call in the deviceinfo file, and in all overlay files, and build the all img files. This will enable the missing kernel support, but more might be missing.)
I am still working on the grahics issues.

@MrT10001 said in Looking for testers: port for Lenovo Tab M8 HD (TB-8505F):

@k.nacke I am playing with scaling as it was scaled at 16 and I thought that was scrambling text, but even at 12 some text is missing (using the Tweak tool).

This is one area for which I really need feedback. This is not only my first port, it is the first time I see Ubuntu Touch on a real device. E.g. the icons may be too large....

@MrT10001 I added you as developer to the repository. Feel free to change the readme.

@MrT10001 Thanks! That is great news!

./fastboot -w (It will error here, ignore).

That error should go away when you cd into the directory with the stock rom files first.

@voodoojaza My plan is to finish the port of the Tab M8 HD, and then try the Tab M8 FHD. I own both tablets, and my main motivation is that with Ubuntu Touch the tablets seem usable. At least the UI reacts fast. Android is a pain on those devices.
Porting without the hardware is not possible, and while I think that it should be easier to get a port for the M8 3rd gen and M8 4th gen after finishing the current port I am not sure that I am willing to spend money for such low end devices.

With the existing ports for the M10 it should be possible to get the other M10 models working rather fast. I looked into the M11 because that tablet is somewhat similar to the M8, however Lenovo did not publish the kernel sources for it. So yeah, not really motivated for that.

@Lesharoturbo No idea. The artefacts are build with Focal, and I never noted missing letters. However, when building for Noble I see a couple of missing characters. I do not have EGL fully working, this could be the cause.

@Lesharoturbo No. I am still working on this port. I think to be able to receive OTA the port must be an official commuinty port. For that I still have to fix some bugs.

@MrT10001 That is possible. Before turning to UT I tried to port LineageOS 17 for the tablet. In my notes for that I have

fastboot --disable-verification flash vbmeta vbmeta.img

using the vbmeta.img from the stock rom (downloaded with the Lenovo Rescue and Smart Assistant).

@MrT10001 Thanks for looking at this. What you are seeing reminds me of my journey getting the kernel boot on my device.
I have a pristine M8 HD and M8 FHD, I will try to install the images there and try to find out what is missing/changed on my development device.

@MrT10001 Any chance you could boot into recovery and see if there is a kernel crash message in /proc/last_kmsg or in /sys/fs/pstore?

I also see the fastboot -w message. I am not sure if the message has functional implications. But using an older fastboot version seems not possible, I get an error when I try to flash a partition with older ones.

I discovered the following work around: You download the firmware with the Lenovo RSA tool. When you run fastboot -w in the directory where the files are stored, then the message goes away. I think the command tries to read the image for the userdata partition.

Kai

@MrT10001 Thanks. That was just a shot in the dark, but it's the same display as mine. Need to think what is causing your bootloop.

Btw, the 3Gb/32Gb model is the Tab M8 FHD. I have that tablet, too, but did not yet work on a UT port for it.

Kai

@MrT10001 Thanks for trying. I also have the 2GB/16GB model, so that should be fine. I think the 3GB/32GB is the model with lte.
One question for me is which display does your model have? E.g. what does

adb shell cat /sys/bootinfo/hardware_info | grep LCD

show? (That should work under Android, too.) I would like to make sure that it finds the display.

Kai

I made some progress with the port:

• waydroid is working now
• enabled all kernel configurations for the android container
• disabled rescue mode
• MTP is working
• dtbo.img is now generated

However, I still see some permission issues which needs fixing.

Have fun,
Kai

Hi Eugen,

Following the link you posted, click on "UBports installer" in the menu on the right side. The page then scrolls to the section where you can download the installer. (The installer does not install Ubuntu Touch on your devices if your device is not supported.)

If you do not want to use the installer, then you can download the partition images from the build pipeline. The file artifacts.zip contains the boot and the system image.

Kai