@Keneda said in Android like gsi (generice system interface) but for ubuntu touch?: @nemo said in Android like gsi (generice system interface) but for ubuntu touch?: However it has been abonded but it proves it is infact possible. It's abandoned because it is a dead end. Any device ported with the "GSI" approach was not full fonctionnal and resulted in devices not daily usable unless someone debuged it and patched it. So same amount of work, if not more, than the classic "halium" porting method. For a device to be daily usable it needs a good port, so a porter commited to that port, not someone using "GSI" thing and going away after. @Luksus would way better explain the GSI issue to you. See there an example : https://forums.ubports.com/topic/4964/fairphone-3-fp3 Spoiler, Fairphone 3 final port is not the GSI way one. that it is to bad but thanks for the reply. I am curious at the exact issues @Luksus ?

@x2u Porting effort is not something that you can do like posting something rude on a forum...

@nintendoeats Yes you can make the systel writable. Either via command sudo mount -o remount,rw / or the Tweak tool. You can follow the manual iinstructions from the repo's readme. You don't need to do all steps, if your changes only affects the system image then just flash that.

@VinceAle7082 I can't answer your build-error question, but: Not sure if it is the same device, but you can have a look here: https://gitlab.com/ubports/porting/community-ports/android11/samsung-galaxy-note-10-plus I would advice you, to clone a repo of the community builds, which matches your device most. Then adjust it, according to your device (deviceinfo, overlays). And try to build it using build.sh. Next to the samsung-community-repo, there are other, more up-to-date repos, which make use of the halium-generic-build tools: https://gitlab.com/ubports/porting/community-ports/halium-generic-adaptation-build-tools You can see this repo, how they get integrated: https://gitlab.com/ubports/porting/community-ports/android9/oneplus-5/oneplus-cheeseburger-dumpling (.gitlab-ci.yaml, build.sh) Its not recommended to use the fullsystemimage build-variant. (Even though, making halium-boot is not the reason).

Hmm, I was referring to the first post, but the curl issue is something different...

@jiho nice the audio call not work, also fingerprint. I'm working now to fix this issues

@SteveDx I have been working on moving the existing port to focal but I don't have any experience so there are a bunch of issues... I can share the code if you are still interested.

https://github.com/bengris32/releases/releases/tag/ruby-21-1.0 lineageos 21 for xiaomi redmi note 12 pro

@WolfLink115 Okay, it won't let me edit this post so I am just going to reply. I have a new Discord now, I lost access to that old one, so the new one is just "wolflink115" without the quotes, no numbers, and all lowercase.

@nontrivial said in Ubuntu Touch Mainline Generic amd64 Issue: Download latest ubuntu-touch-mainline-generic-amd64.img.xz file from https://ci.ubports.com/job/rootfs/job/rootfs-generic-amd64/ Uncompress it with unxz Convert to VirtualBox VDI disk image: VBoxManage convertdd disk.img disk.vdi The boot process appears to hang on "Starting virtual private network daemon". By the way, I know this is a thread from four years ago, but if you web search running UBports image in VirtualBox, it leads here, so I thought I would update it to help the next person save some time... After you run the convert line: $ VBoxManage convertfromraw /home/alaskalinuxuser/snap/utqemu/common/ubuntu-touch-mainline-generic-amd64.img ./ubports.vdi --format vdi And you try to launch it in VirtualBox, you will still hang at Starting virtual private network daemon, but the real issue is the graphic card settings, as @hacker1024 pointed out, but didn't offer the solution. What worked for me was: Display settings in VB: Video Memory 32 MB Graphics Controller VMSVGA Enable 3D acceleration RDS and Recording (don't matter, but I use) disabled. Setting the RAM to 1536MB and using the converted VDI drive seems to work great for me. Hopefully that helps the next person....

@VinceAle7082 I did everything again and now I get this error when doing "mka mkbootimg": 15:50:03 ************************************************************ 15:50:03 You are building on a machine with 6.7GB of RAM 15:50:03 15:50:03 The minimum required amount of free memory is around 16GB, 15:50:03 and even with that, some configurations may not work. 15:50:03 15:50:03 If you run into segfaults or other errors, try reducing your 15:50:03 -j value. 15:50:03 ************************************************************ 15:50:03 Build sandboxing disabled due to nsjail error. ============================================ PLATFORM_VERSION_CODENAME=REL PLATFORM_VERSION=13 LINEAGE_VERSION=20.0-20240402-UNOFFICIAL-d1 TARGET_PRODUCT=lineage_d1 TARGET_BUILD_VARIANT=userdebug TARGET_BUILD_TYPE=release TARGET_ARCH=arm64 TARGET_ARCH_VARIANT=armv8-2a-dotprod TARGET_CPU_VARIANT=cortex-a75 TARGET_2ND_ARCH=arm TARGET_2ND_ARCH_VARIANT=armv8-2a TARGET_2ND_CPU_VARIANT=cortex-a55 HOST_ARCH=x86_64 HOST_2ND_ARCH=x86 HOST_OS=linux HOST_OS_EXTRA=Linux-6.5.0-26-generic-x86_64-Ubuntu-22.04.1-LTS HOST_CROSS_OS=windows HOST_CROSS_ARCH=x86 HOST_CROSS_2ND_ARCH=x86_64 HOST_BUILD_TYPE=release BUILD_ID=TQ3A.230901.001 OUT_DIR=out PRODUCT_SOONG_NAMESPACES=vendor/samsung/exynos9820-common device/samsung/exynos9820-common hardware/google/interfaces hardware/google/pixel hardware/samsung hardware/samsung/aidl/power-libperfmgr vendor/s amsung/d1 ============================================ device/samsung/d1/BoardConfig.mk was modified, regenerating... Adding CUSTOM_LOCALES [ast_ES gd_GB cy_GB fur_IT] to PRODUCT_LOCALES [en_US en_US af_ZA am_ET ar_EG ar_XB as_IN az_AZ be_BY bg_BG bn_BD bs_BA ca_ES cs_CZ da_DK de_DE el_GR en_AU en_CA en_GB en_IN en_XA es _ES es_US et_EE eu_ES fa_IR fi_FI fr_CA fr_FR gl_ES gu_IN hi_IN hr_HR hu_HU hy_AM in_ID is_IS it_IT iw_IL ja_JP ka_GE kk_KZ km_KH kn_IN ko_KR ky_KG lo_LA lt_LT lv_LV mk_MK ml_IN mn_MN mr_IN ms_MY my_MM nb _NO ne_NP nl_NL or_IN pa_IN pl_PL pt_BR pt_PT ro_RO ru_RU si_LK sk_SK sl_SI sq_AL sr_Latn_RS sr_RS sv_SE sw_TZ ta_IN te_IN th_TH tl_PH tr_TR uk_UA ur_PK uz_UZ vi_VN zh_CN zh_HK zh_TW zu_ZA en_XC] [100% 1025/1025] initializing build system ... Adding CUSTOM_LOCALES [ast_ES gd_GB cy_GB fur_IT] to PRODUCT_LOCALES [en_US en_US af_ZA am_ET ar_EG ar_XB as_IN az_AZ be_BY bg_BG bn_BD bs_BA ca_ES cs_CZ da_DK de_DE el_GR en_AU en_CA en_GB en_IN en_XA es _ES es_US et_EE eu_ES fa_IR fi_FI fr_CA fr_FR gl_ES gu_IN hi_IN hr_HR hu_HU hy_AM in_ID is_IS it_IT iw_IL ja_JP ka_GE kk_KZ km_KH kn_IN ko_KR ky_KG lo_LA lt_LT lv_LV mk_MK ml_IN mn_MN mr_IN ms_MY my_MM nb _NO ne_NP nl_NL or_IN pa_IN pl_PL pt_BR pt_PT ro_RO ru_RU si_LK sk_SK sl_SI sq_AL sr_Latn_RS sr_RS sv_SE sw_TZ ta_IN te_IN th_TH tl_PH tr_TR uk_UA ur_PK uz_UZ vi_VN zh_CN zh_HK zh_TW zu_ZA en_XC] [ 92% 1138/1224] including hardware/samsung_slsi-linaro/exynos/Android.mk ... Build Gralloc 1.x libhardware HAL [ 97% 1197/1224] including vendor/halium/audioflingerglue/Android.mk ... vendor/halium/audioflingerglue/Android.mk:41: warning: *** ANDROID_MICRO undefined. Assuming 0 /bin/bash: riga 1: test: -le: atteso operatore unario cat: frameworks/av/include/media/AudioSystem.h: No such file or directory [ 97% 1199/1224] including vendor/halium/droidmedia/Android.mk ... vendor/halium/droidmedia/Android.mk:43: warning: *** ANDROID_MICRO undefined. Assuming 0 [ 99% 1223/1224] finishing build rules ... FAILED: build/make/core/main.mk:1312: warning: device/samsung/d1/lineage_d1.mk includes non-existent modules in PRODUCT_PACKAGES Offending entries: SimpleSettingsConfig fsck.ntfs htop mkfs.ntfs mount.ntfs nano rsync scp sftp ssh ssh-keygen sshd sshd_config start-ssh unrar vim webview build/make/core/main.mk:1312: error: Build failed. 15:51:32 ckati failed with: exit status 1 #### failed to build some targets (01:30 (mm:ss)) ####

@unger Try -j number of threads + 2 (example -j 12, not -j12) Idk if this is the problem but try it, why not?