Is this tested?

[MightyM17]

Does the kernel work with espresso3g/wifi

[SakiiCode]

It can be compiled without errors, check this guide here

I don't remember if I could get it running on my espressowifi

[MightyM17]

So it dosent need anything specific for espresso3g/wifi
I'm planning to add halium support and upstream PostMarketOS from 3.0 to 3.18 using this kernel
I can help but I don't know much about it

[MightyM17]

plus according to the guide we should be able to build lineage os 15 (oreo?) with this?

[SakiiCode]

My goal was to port ubuntu touch (halium 7.1), the guide is for building lineageos 14.1.

Halium currently requires a device with a Linux kernel version greater than or equal to 3.10.0.
Some Halium distributions may use a kernel as old as 3.4, such as Ubuntu Touch.

The kernel version here is 3.8, so it "should" be good for ubuntu touch. PostmarketOS needs kernel 3.17

[MightyM17]

The kernel version here is 3.8, so it "should" be good for ubuntu touch. PostmarketOS needs kernel 3.17

Nope.... we have a working PostmarketOS with 3.0.101 kernel (from LineageOS)

[MightyM17]

My goal was to port ubuntu touch (halium 7.1), the guide is for building lineageos 14.1.

Even i am trying to do that but halium-boot seems to be broken for me (i used 3.4 from Unlegacy-Android)

[MightyM17]

Another question i have is how does one exactly "update" kernel as in you got this from ti's git and then what? They are on 4.x kernel iirc

[SakiiCode]

I cloned the master branch which is on 3.8.13. Just noticed there are other branches with up to version 4.9. I don't know how stable these are.

If you want to use that you can try adding a remote in your roomservice.xml. Edit the revision part to change branches

<remote fetch="https://git.ti.com/git/" name="ti" revision="ti-linux-4.9.y" />

Then replace the project tag of current kernel with the new repo

<project name="android-sdk/kernel-omap" path="kernel/ti/omap4" remote="ti" />

Then run

repo sync --force-sync kernel/ti/omap4

Also turns out there are some incorrect configuration in https://github.com/SakiiCode/android_hardware_ti_omap4 , so the guide I wrote doesn't work currently. I'll try to push some changes later if I have time

[MightyM17]

Welp I get tons of errors (trying to get halium for ubuntutouch)
https://pastebin.com/AiENKkmC

Used SakiiCode/android_hardware_ti_omap4 seems to have removed all errors

[MightyM17]

Also thanks a lot for the help about kernel!

[MightyM17]

Update - i cant seem to make halium-boot.img work for espresso, it is just too big (size of image is larger than size of target)

[SakiiCode]

Are you installing it with TWRP? You have to flash it with heimdall (linux) or odin (windows)
Also heimdall needs to be built from source, the latest downloadable version doesn't work

https://docs.halium.org/en/latest/porting/install-build/reference-rootfs.html#install-hybris-boot-img-on-samsung-devices

[MightyM17]

Are you installing it with TWRP? You have to flash it with heimdall (linux) or odin (windows)
Also heimdall needs to be built from source, the latest downloadable version doesn't work

https://docs.halium.org/en/latest/porting/install-build/reference-rootfs.html#install-hybris-boot-img-on-samsung-devices

Wait what?! Why cant i flash from twrp https://docs.ubports.com/en/latest/porting/halium_7-1/Installing.html
Ubuntu touch tells that

[MightyM17]

Still dosent work... PC cant detect tab so i cant ssh in (hybris-boot seems to work fine tho)

[MightyM17]

I cloned the master branch which is on 3.8.13. Just noticed there are other branches with up to version 4.9. I don't know how stable these are.

If you want to use that you can try adding a remote in your roomservice.xml. Edit the revision part to change branches

<remote fetch="https://git.ti.com/git/" name="ti" revision="ti-linux-4.9.y" />

Then replace the project tag of current kernel with the new repo

<project name="android-sdk/kernel-omap" path="kernel/ti/omap4" remote="ti" />

Then run

repo sync --force-sync kernel/ti/omap4

Also turns out there are some incorrect configuration in https://github.com/SakiiCode/android_hardware_ti_omap4 , so the guide I wrote doesn't work currently. I'll try to push some changes later if I have time

Welp roomservice.xml? sorry i have never worked with lineageos before (100+ gb is too big for me to download)

[SakiiCode]

Welp roomservice.xml? sorry i have never worked with lineageos before (100+ gb is too big for me to download)

Sorry it's not roomservice.xml just the same xml where you manage these sources (halium/devices/manifests/samsung_espressowifi.xml or something like that)

Still dosent work... PC cant detect tab so i cant ssh in (hybris-boot seems to work fine tho)

That's similar to where I got stuck when I tried. I could set IP address but ssh didn't work. Unfortunately my data cable broke so can't do any testing right now.

[MightyM17]

That's similar to where I got stuck when I tried. I could set IP address but ssh didn't work. Unfortunately my data cable broke so can't do any testing right now.

Ooof that 30 pin cable :(

Sorry it's not roomservice.xml just the same xml where you manage these sources (halium/devices/manifests/samsung_espressowifi.xml or something like that)

okay but wont i need to add espresso files? defconfig and other files which i dont know

[MightyM17]

So well whats your plan ahead for development?

[SakiiCode]

defconfig is the kernel config and located at arch/arm/configs/espresso_defconfig. I already added that to this repo though it may be incorrect and related to the problem
halium/hybris-boot/fixup-mountpoints was already set up before
halium/devices/manifests/samsung_espressowifi(or espresso3g).xml is where you set these repositories

not many other files need to be added/edited

I'm new to C++ programming and android porting, and already spent quite some time with this, so out of ideas.

[MightyM17]

Welp i will try (3.4 seems to work properly acc to andi)

[MightyM17]

Also i think i should try 4.9? idk what to do after downloading it (like i dont think it will work we will need espresso scripts)

[SakiiCode]

I already wrote the procedure above for 4.9

Tried compiling and it said fatal error: asm/system.h: No such file or directory so it will need patches in the code too

[MightyM17]

Oh yikes well i will try mainlining it then

[MightyM17]

Have you tried with this https://github.com/OMAP4-AOSP/android_kernel_samsung_espresso (see the branches)

[SakiiCode]

Oh my god, Unlegacy-Android's CyanogenMod 12.1 configuration works first try no modifications. This can be a good starting point for halium 5

[MightyM17]

Oh my god, Unlegacy-Android's CyanogenMod 12.1 configuration works first try no modifications. This can be a good starting point for halium 5

wait what?!! whats the kernel source? also Halium/projectmanagement#238 lets talk about it here :D

[MightyM17]

I am trying right now with https://github.com/OMAP4-AOSP/android_kernel_samsung_espresso/blob/wip/3.10

[MightyM17]

When did u update for a 3.10 cm12.1 fork :0

[MightyM17]

Maybe even build 4.9 ;) https://git.ti.com/cgit/android-sdk/kernel-omap/tree/?h=ti-android-4.9.y so then we might also be able to build oreo and up

[SakiiCode]

cm-12.1 branches are the patches I made to https://github.com/Unlegacy-Android/android_hardware_ti_omap4 and TI's 3.10.y kernel, but couldn't get it compiled so not really a progress

[SakiiCode]

Maybe even build 4.9 ;) git.ti.com/cgit/android-sdk/kernel-omap/tree/?h=ti-android-4.9.y so then we might also be able to build oreo and up

error: #error Your compiler is too buggy; it is known to miscompile kernels 🤣

[MightyM17]

cm-12.1 branches are the patches I made to https://github.com/Unlegacy-Android/android_hardware_ti_omap4 and TI's 3.10.y kernel, but couldn't get it compiled so not really a progress

We should try android_kernel_samsung_espresso

[MightyM17]

Any new updates @SakiiCode ?

[SakiiCode]

I gave up on halium, better deal with postmarketOS, at least that works on that older kernel. Mainlining it is definitely not my level.

[MightyM17]

I gave up on halium, better deal with postmarketOS, at least that works on that older kernel. Mainlining it is definitely not my level.

Yikes :( halium might work with 3.0 kernel and patches for Apparmor etc.

[MightyM17]

Still going on?

[SakiiCode]

Nope, nothing new

[MightyM17]

Well figured it out finally xD, the power reset mode was due to halium boot being too big for the device's boot partition. Using XZ compression instead of GZIP and it now is 7.x MB which fits in the boot partition even with twrp :D

[MightyM17]

Hey, Ubuntu Touch also works now!! Should I close this commit now?

[SakiiCode]

Really? Can you give me a link?

[MightyM17]

Link for what?

[MightyM17]

Do you plan on working on this or not?

[SakiiCode]

No my device is almost dead and I won't be doing any more kernel modding, so this issue can be closed.

If you have suggestion how to revive it if I can't turn it on to get to twrp, and if I put it on a charger it won't go past 3% let me know please

[MightyM17]

No my device is almost dead and I won't be doing any more kernel modding, so this issue can be closed.

If you have suggestion how to revive it if I can't turn it on to get to twrp, and if I put it on a charger it won't go past 3% let me know please

Stuck on 3%? that sounds pretty weird, have you tried reconnecting battery and/or replacing it?

[SakiiCode]

No, I didn't want to take it apart

[MightyM17]

No, I didn't want to take it apart

Its not that hard, there's also an ifixit guide :P
But ig you probably wouldnt wanna spend money on it if the battery has issues, its quite old

[SakiiCode]

It was a bot scam message, don't fall for it

Github instantly deleted the comment but remained in your emails

[MightyM17]

Ah alrighty thanks!

…

On Wed, 21 Feb, 2024, 5:02 pm Sakii, ***@***.***> wrote: It was a bot scam message, don't fall for it Github instantly deleted the comment but remained in your emails — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQZJ774GGIIO6B2LTVVH5JDYUXLNLAVCNFSM4WKDBQA2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJVGY2DKNBWGUYQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>