@k.nacke Thanks for the proposal, I will first start to install (which will be the challenge like any first time For the 4G I will normally used my phone shared connection (bluetooth or wifi). But why not helping once my yearly trip will end. Shall I first start to initialize the tablet with its android, or can I start directly to flash and boot Linux ?

@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

@pdgf Building a UBports recovery for the stand-alone porting method requires a ramdisk-recovery.img file to be placed in the device tree's root directory. Currently one has to fetch it from a different device tree in GitLab, but I've proposed changes so that it's available as an artifact on our Jenkins CI instance. Will update this once the recovery ramdisk is downloadable from Jenkins.

@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?

(SOLVED)i forgoted to flash vbmeta and now config works

@maahymot Not that I know of, but I also do not own the Mi A1.

@MrT10001 okay , i formated userdata partion to ext4 and flash again but this problem continues...

@linhmieu Here is the Port Development Guide. Read through that first, and ask specific questions as they come up.

@tigerpro have you made any progress on this port? Id be very interested in using this if volte was worked out

On the Xiaomi 6, the ofono-binder-Plugin software package must be in a lower version (1.1.15). The latest version will cause the ofono process to crash。 The specific reason for the crash of the ofono process has not been found yet

@tenbucket It might just be the fact I have no experience porting devices but I personally find this to be really impressive, keep up the good work man and keep us all posted.

Up to date tutorial for installing UBT on X3 Pro : https://forums.ubports.com/topic/11334/ubuntu-touch-ubt-tutorial-installation-guide-for-poco-x3-pro-vayu-and-help-channel