Okay, thank you! I'll try that.
Latest posts made by cornonthecob
Issues porting to Pixel 3
Hello, first time porter here.
Porting to the Pixel 3 (blueline) has been somewhat confusing as the kernel and whatnot is mixed in with the Pixel 3 XL (crosshatch).
I'm currently stuck on the Halium build step.
I'm not sure how to format my progress, so I'll just dump my progress so that I don't miss anything.
I'm having problem finding the kernel configuration. It should be in the
BoardConfig.mkfile, but crosshatch and blueline appear to share one under
device/google/crosshatch/blueline/BoardConfig.mkhas the statement:
I've omitted the steps for syncing the repo.
My manifest (google_blueline.xml) is as follows
<?xml version="1.0" encoding="UTF-8"?> <manifest> <project path="device/google/blueline" name="android_device_google_blueline" remote="los" /> <project path="device/google/crosshatch" name="android_device_google_crosshatch" remote="los" /> <remote name="los" fetch="https://github.com/LineageOS" /> </manifest>
Do I need to add a line to fetch
android_kernel_google_crosshatch? I'm confused.
halium/devices/setup bluelineran with no errors.
hybris-patches/apply-patches.sh --mbran with no errors.
I extracted the vendor blobs using the
extract-files.shin the crosshatch device folder (blueline's links to that one).
It starts differing after I ran
including device/google/crosshatch/vendorsetup.sh including vendor/lineage/vendorsetup.sh
I'm missing a few lines that are shown in the guide.
Since the BoardConfig for blueline includes
BoardConfig-commonfor crosshatch, I ran
grep "TARGET_KERNEL_CONFIG" device/google/crosshatch/BoardConfig-common.mkwith no results.
Am I missing something? Sorry if this should be obvious.
Thanks in advance.