$ ./halium-install-master/halium-install -p ut -s ./ubuntu-touch-android9-arm64.tar.gz ./system/var/lib/lxc/android/android-rootfs.img Here is the output: D: Chosen rootfs is ./ubuntu-touch-android9-arm64.tar.gz D: Chosen android image is ./system/var/lib/lxc/android/android-rootfs.img D: Chosen release is ut D: Compress images before pushing: false I: Writing rootfs into mountable image I: Writing android image into mountable image I: Running post installation tasks enabling SSH ... [done] Please enter a new password for the user 'phablet': Enter new UNIX password: Retype new UNIX password: passwd: password updated successfully I: Shrinking images e2fsck 1.45.5 (07-Jan-2020) resize2fs 1.45.5 (07-Jan-2020) The filesystem is already 138429 (4k) blocks long. Nothing to do! I: Unmounting images I: Pushing rootfs and android image to /data via ADB I: Pushing rootfs to /data via ADB .halium-install-imgs.DQXbh/rootfs.img: 1 file pushed. 32.9 MB/s (3221225472 bytes in 93.286s) I: Pushing android image to /data via ADB .halium-install-imgs.DQXbh/system.img: 1 file pushed. 32.7 MB/s (576184320 bytes in 16.791s) I: Renaming to system-as-root compatible system image real 1m50,149s user 0m0,650s sys 0m4,607s I: Cleaning up umount: .halium-install-rootfs.anHND: not mounted.

@sploochy said in Anbernic RG351MP: There are already many pre-built ubuntu images with retro game interfaces Maybe you should try to make a normal Ubuntu, not Touch, on it since there is already some working builds of it. Touch is a particular OS for mobile devices.

@arubislander big thx!!!!

@mighty sure, I'll just move this discussion at github. [https://github.com/Halium/projectmanagement/issues/238]

@flohack I own an hammerhead device and would like to test a "recent" Linux system on it. I gladly make myself available as an alpha tester. Is there already a Halium 9 based build to test?

@doniks Thanks for the post, it gave me clues on my issue. This is an old thread but wanted to add to your post because it took me so long to get it to compile. Having never compiled an Android Kernel before I think I spent 2 days on it. Using Ubuntu 18, gcc-4.8 was not available through apt. I ended up download the AOSP8 source. The source contains gcc for the android version located in prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android Looking at the build.config.aarch64 file https://android.googlesource.com/kernel/common/+/a5d10f0defc377d43672b304e31e37a517fbf0bf/build.config.aarch64 I found the variables, needed for the kernel source. ARCH=arm64 CLANG_TRIPLE=aarch64-linux-gnu- CROSS_COMPILE=aarch64-linux-androidkernel- CROSS_COMPILE_COMPAT=arm-linux-androidkernel- LINUX_GCC_CROSS_COMPILE_PREBUILTS_BIN=prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin LINUX_GCC_CROSS_COMPILE_COMPAT_PREBUILTS_BIN=prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/bin/ There were a lot of other dependencies I had to install but that took care of the correct gcc version. Hope this helps someone.

@s710 said in OnePlus 7 UBPorts GSI development found on XDA, new thread?: @catalyst said in OnePlus 7 UBPorts GSI development found on XDA, new thread?: @s710 think you are better asking him on the discord. looks like he hasn't logged into the forum for a little over a year now. Which discord? It's on the XDA forum in the same thread that was posted here. Here's a direct link https://discord.gg/nNaA5jfY93

@reaper1312 Please check the info here https://forums.ubports.com/topic/2068/halium-first-steps for basic info and if your device is suitable. Currently we have no 5G capability IIRC.

@user-0 well done !!

@mrt10001 Those blobs are now out of the kernel with GKI. They are in separate modules, and vendors must make them compatible with AOSP LTS kernel. So you can make a generic way of doing UT ports, and even, i guess, update kernel with AOSP LTS one, or blobs modules during android device life, without doing UT port from scratch everytime. I assume too that if android structure doesn't change in future between major updates, installind UT on those devices, let say an "halium 12" UT port on an android 13 updated from 12 device, will be possible without downgrading to 12. I may be too optimistic but the actual kernel mixup is a real problem and i believe causes the most of UT ports issues.

@stanwood thank you for the information and for your patience, I will keep an eye on you and wait for the system to mature a little longer, I trust you, I respect you

i believe i found the answer: config PHYS_OFFSET in my device kernel code. [kernel code dir]/arch/arm/Kconfig: config PHYS_OFFSET hex "Physical address of main memory" if MMU depends on !ARM_PATCH_PHYS_VIRT default DRAM_BASE if !MMU default 0x00000000 if ARCH_EBSA110 || \ ARCH_FOOTBRIDGE || \ ARCH_INTEGRATOR || \ ARCH_IOP13XX || \ ARCH_KS8695 || \ ARCH_REALVIEW default 0x10000000 if ARCH_OMAP1 || ARCH_RPC default 0x20000000 if ARCH_S5PV210 default 0xc0000000 if ARCH_SA1100 help Please provide the physical address corresponding to the location of main memory in your system.

@tg78 It seems that your device is not connecting to ubports installer through adb. Did you unlocked phone bootloader ? Did you install adb drivers on PC ? Did you use a data capable usb cable ? Did you use USB 2.0 port on PC ? USB 3.0 is to avoid if possible. Did you try another usb cable/usb port ?