Halium

08 Apr 2024 19:23

anyway since it's really common code across their devices, I've been wondering if it can be workarounded kernel side

Halium

08 Apr 2024 19:20

As in, it would work without loading iy

Halium

08 Apr 2024 19:20

probably not, as they don't break ABIs

Halium

08 Apr 2024 19:18

I'm guessing not, but does it look like a gki violation?

Halium

05 Apr 2024 21:05

so it breaks with overflow once systemd boots

Halium

05 Apr 2024 21:04

but there you specifically won't be able to use GKI easilly

Halium

05 Apr 2024 21:03

which device is this

Halium

05 Apr 2024 21:02

idk much about porting, and my device is already WIP by the Halium project

Halium

05 Apr 2024 21:01

eh, I'll give it a try

Halium

05 Apr 2024 20:57

Is it already possible to use GKI?

Halium

04 Apr 2024 10:23

in general just start with deviceinfo and udev rules in overlay, then expand when needed

Halium

04 Apr 2024 10:05

Well thank you for the start-up.

My device is Realme GT Neo 2 and it's SoC is Snapdragon 870.

Halium

04 Apr 2024 09:32

and better to move this discussion to /channel/ubports_porting

Halium

03 Apr 2024 05:48

People already answered you and you just ignored those messages. If you want to run UT on your device, use the UT porting guide and ask for help in the UT Porting group. This is not the right place for that

Halium

03 Apr 2024 00:13

I almost have the same questions you have.

Halium

08 Apr 2024 19:20

so other modules seem to depend on it

Halium

08 Apr 2024 19:20

it's in their ems scheduler

Halium

08 Apr 2024 19:20

Isn't it a "useless" vendor-hook module?

Halium

05 Apr 2024 21:05

it can be patched in the module itself, but then it's not GKI either

Halium

05 Apr 2024 21:04

Samsung introduced few annoying bugs, like assuming a very low number of root cgroups in their scheduler code

Halium

05 Apr 2024 21:04

Ubuntu Touch, not Halium then

Halium

05 Apr 2024 21:02

so I thing it's better that I wait for it to be complete, but right now I want to try using GKI

Halium

05 Apr 2024 21:01

also hop over to the UBports porting group from the link a few messages above if UT is what you're porting, this group is more or less relegated to legacy purposes and Halium developers

Halium

05 Apr 2024 21:00

kind of, though since device specific drivers still have their quirks probably better to actually have a kernel source for porting even if your device uses 5.4+ kernel

Halium

04 Apr 2024 10:37

I see, well thank you, will start soon with it.

Halium

04 Apr 2024 10:22

maybe refer to Fairphone 4 then, but it also has plenty of specific tweaks

Halium

04 Apr 2024 09:34

I replied you're on the wrong track, but if you do something else, I can't prevent you, but you're obviously on your own

Halium

04 Apr 2024 09:32

1) yes
2) which is your device/SoC?
3) well, start from deviceinfo, then can't say in advance

Halium

03 Apr 2024 04:07

And no one answers, dead group

Halium

02 Apr 2024 16:39

Hello there,

I am currently trying to port Ubuntu Touch for my device and came across this guide which does explain it : https://docs.ubports.com/en/latest/porting/build_and_boot/H9_gitlab_build.html

I have some questions regarding this :

1) Do I have to choose the Halium 11 for this task, as my VNDK version is reported as 30.0, even when my android version is currently at 13?


2) If the above is true and i need to use Halium 11, should i base my device on this : https://gitlab.com/ubports/porting/reference-device-ports/android11/volla-phone-22/volla-mimameid

3) If yes to the above point, do i need to update only the deviceinfo or perhaps the other files in that repo as well? I know that i need the boot.img which i am planning to pull from my own device, but is there anything extra apart from this? [As the guide mentioned above is a bit old as its for Halium 9?]



I guess these many questions are enough for this stage. Sorry if they are very silly, I am new to all of this.

Thank you.