Stuck at checking kernel configuration.

Carlo

I can't understand how to check the kernel config and apply the changes as shown as in the Modify the kernel configuration part of the porting guide. I guess it might not be generating since under BUILDDIR/kernel/ folder I cannot find my device. Am I missing something? I am new to the argument of porting so please be kind if this was a trivial question. Thanks!

Lakotaubp

@carlo Which device are you porting? it might help with an answer, Thanks.

Carlo

@lakotaubp I get the same error both for nexus 9 and for samsung s4. I initially speculated that it was a nexus 9 related error, maybe due to the manifest or something, but got the same result with the s4.

Flohack

Well to get a kernel you have to add it to a local manifest in the halium/devices repo and then let it be set up by the setup script in that repo. Otherwise kernel will be empty, yes

Carlo

@flohack I have created the repo manifests. For example a rough manifest for jfltexx is

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="LineageOS"
    fetch="https://github.com/LineageOS"
    revision="los-16.0" />
<!--Dependencies-->
<project path="device/samsung/jfltexx" name="android_device_samsung_jfltexx" remote="LineageOS" revision="lineage-16.0" />
<project path="device/samsung/jf-common" name="android_device_samsung_jf-common" remote="LineageOS" revision="lineage-16.0" />
</manifest>

I have created it under BUILDDIR/halium/devices/manifests/samsung_jfltexx.xml

The jf-common line comes from the lineage.dependencies file.

Flohack

@carlo Yes you are missing the kernel in the anifest.

Carlo

@flohack Ok, thanks, now I understand better. So I will add a line that goes something like:

<project path="kernel/samsung/jf" name="android_kernel_samsung_jf" remote="LineageOS" revision="lineage-16.0" />

Thanks.

Flohack

You probably want to fork those repos, since you will have to make modifications 100%

BR

Carlo

@flohack thanks a lot, I will do. BR