@Keneda said in Update port for Ubuntu Touch 20.04 on Xiaomi Mi 6:

@kuailexs
Please edit your image to hide personal infos like mac addresses, IMEI , serials and so on.

Done.

your doin good lad 🙂

@GooseDev72

hi did you found a solution ?
have a simular issue

@Keneda xd, Well there have been many changes in the kernel

@redmiguy3 Thank you! I have tried porting postmarketOS to this device too, but the kernel I used is broken. I don't have the files for the port anymore, but I will restart development and try to port this device.

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

@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