@arubislander Yes I have seen it but didn't use it. I will ask there. Thanks.

@ksp-atlas Could you include the actual par of the logs that include the errors you are experiencing?

@GooseDev72 hi did you found a solution ? have a simular issue

@SiberianKitty I think this is the link for the latest rootfs built by the ci: https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/

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

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