@harmhero No, the M8 FHD is a different device. It has a different CPU, a different LCD, and more RAM. I actually own a M8 FHD device, and I like to support that device, too. However, I am currently busy with writing another book, so most likely this will not happen before late summer.
Kai
@linhmieu2 Just a shot in the dark: you only have a handful of udev rules, this seems incomplete. E.g. in my port: https://gitlab.com/redstar-team/ubports/lenovo-tab-m8/lenovo-tab-m8/-/blob/halium-10-4.9/overlay/system/etc/udev/rules.d/70-tabm8.rules?ref_type=heads
Kai
@tigerfoot The TB-8505X has the 4G interface, which is missing in the current kernel. Other than that it should work fine. Not sure if this fits your use case...
I can provide a boot image with a kernel having the additional driver compiled in, but mot likely would need your help with debugging the ofono configuration (in case you are interested in helping to get 4G working).
sd cards works, surfing via wifi works too. IMHO it feels faster than Android, but do not expect wonders.
@linhmieu2 You need to determine the VNDK level of your Android firmware, e.g. with adb shell getprop | grep vndk or using the Treble info app. Use that number to look up the corresponding Android version, e.g. at API levels. For example, if the VNDK version is 34, then you need to put deviceinfo_halium_version="14" in your deviceinfo file.
The VNDK level is the API version level, and this it what counts for halium. Note that the version derived in this way may not correspond the Android version your device displays. E.g. I have a OnePlus 11 running Android 15, but the VNDK version is still 33, which corresponds to Android 13. For this device, I need to use 13 as the halium version.
You may also want to put the number as ApiLevel into the /etc/gbinder.conf file in your system overlay.
There is no "Android 12 kernel". I think it would be better if you post the concrete problems you encounter. The telegram group for porters is also a good place to ask or search for answers.
Kai
@floem7 said in Unlock Bootloader – How To Unlock?:
Second question, how can I backup my original android 11 in case I've screw something?
No recommendation for a backup. You can use the Rescue and Smart Assistent from Lenovo (RSA) to reinstall latest stock Android. Sadly, this tool is only available on Windows.
A good strategy is to use RSA to download the firmware file, and save that file. The path is shown in the upper right corner of the UI while the file is downloaded. Either you are fast enough and you can copy the .zip file, or you need to zip the unzip directory yourself. This firmware file contains all the partition images of the devices, and you can flash them via fastboot to restore Android.
Kai
@floem7 said in Unlock Bootloader – How To Unlock?:
However, I have no clarity on unlocking bootloader. The page linked above doesn't provide/link software for linux. I've borrowed windows machine to use dedicated USB-drivers but still the linked file is not exe but some dlls.
For Linux, you can download the platform tools from Google. Most likely, you need to run the tools as root because of missing udev rules. Many distributions provide these tools, e.g. on latest Ubuntu you can install adb and fastboot with sudo apt install adb fastboot. This will also update the udev rules. A good approach is to install the tools from the distribution, and the latest tools from Google, and make sure that the Google version comes first in the search path.
No USB drivers etc. are needed, and no need to download binaries from random websites.
Kai
Latest build fixes the vertical black lines which can be seen sometimes.
Updates since my last post:
pstore feature workingartifacts.zip now contains a vbmeta.img file to simplify the installationThe repo now includes a script to disable the ugly "Orange State" warning. customizelk.py patches the lk.img from the stock ROM to just return from the function which displays the message. This also avoids the additional 5sec wait time. Please note that this is purely cosmetic.
Have fun,
Kai
@bellagon Thanks for trying. Yes, the missing characters are annoying. I still have not found a solution for it.
@abdalnablse10 Thanks for trying. The problem with offline charging seems to be a regression, may be I disabled too much.
The vertical black lines feel like a "off by 1" error in the graphic pipeline. Not sure if I can do something about that.
@feuersee Thanks for testing! This character repetition in the terminal is something new. I'll try to reproduce it.
@CaptainTalonAlt Thanks for testing! Sounds all good. The missing characters are strange. I suspect some kind of memory or alignment issue. As soon as I change something in the kernel, the missing characters change.
I have ideas about the camera issue, but this will need some time to fix.
@CaptainTalonAlt said in Looking for testers: port for Lenovo Tab M8 HD (TB-8505F):
Most Importantly, Did you consider moving to github? or somewhere less limited?
I think it is fine now. After compressing the files there seems to be enough room left for the future.
Happy New Year!
I hit the 1GB upload limit in GitLab, therefore there were no build for some time. The images in the artifacts.zip file are now bzip2 compressed, which brings me under the upload limit again. (I did not yet update the install instructions.)
I made the following changes:
I also spent a lot of time trying to get a 4.19 kernel to run. So far with no result - it boots but then crashes. The motivation here is that systemd requires at least a 4.15 kernel to support all features.
Have fun,
Kai
@viko Happy New Year!
The dtbo.img contains part of the device tree, and as such it is important. However, during porting it is often not necessary to change that information, and in those cases the file is not provided. If the file is not in the artifacts downloaded from GitLab, then most likely it is not needed.
(Disclaimer: that is my experience from my own port.)
Do you look at generic install instructions, or instructions specific to the port?
@linhmieu2 Did you run prepare-fake-ota.sh and system-image-from-ota.sh (see install kernel)?
You would the flash system.img to the system partition. Also, your deviceinfo_kernel_cmdline seems to miss systempart=/dev/disk/by-partlabel/system.
@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:
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.