Thanks for the answer. Is this a bug that appeared in Ubuntu Touch 16.04 or 20.04?

@Satanas1275 While we are all for seeing more and all kinds of Linux on phones, soliciting help on a Postmarket OS port is very much off topic for this forum, wouldn't you agree?

right now the graphics stack is giving me some issues in all this ...i might break on this for a bit and work the opi5 build or a plethora of programs for a bit to avoid burn out

also also forgot to mention im almost done porting the ubports device installer to a clickable as well so it runs on device https://ubports.com/ubports-installer

the opi 5 build uses the same script for my x86_64 version currently i still have not tested the opi5 version just the x86_64 version so idk UT build script: https://drive.google.com/file/d/1psGjDJQ40fcwWYlxNBS_0QZW_Tpne4ZU/view?usp=drive_link

I have tried to get help from the ubports_porting telegram group,but automatically kicked and blacklisted due to my pastebin link

@k.nacke im finally back with the tablet, can you teach me how to port a device

@k.nacke Thank for the hint

Update: UBports CI now spits out a recovery ramdisk for Halium 10.0 and up. Select your Halium generation and download the ramdisk here: https://ci.ubports.com/job/UBportsCommunityPortsJenkinsCI/job/ubports%252Fporting%252Fcommunity-ports%252Fjenkins-ci%252Fgeneric_arm64/

@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

@glowingscrwdrvr if encryption has been set up (presumably by Android?) for subdirectories only, then this should work. File-based encryption (ext4 & f2fs) works on a per-directory basis. But I would first confirm that this is the case.

@faveoled it disconnecting by me (because the charging cable is about to broken)

@a20sporter can we take a look at your deviceinfo file?