I need to work on kernel developing and try to compile AOSP and custom kernel for Pixel 4.
First try:
Kernel Build:
repo init -u https://android.googlesource.com/kernel/manifest -b android-msm-coral-4.14-android11-qpr2
repo sync
build/build.sh
AOSP: (android-11.0.0_r17)
cd aosp
source build/envsetup.sh
lunch aosp_flame-userdebug
export TARGET_PREBUILT_KERNEL=$CWD/kernel/out/android-msm-floral-4.14/dist/Image.lz4
m -j30
Then I flash all the img to Pixel 4 via fastboot -w update all_img.zip.
The touchscreen does not work.
It seems that in Android 10, the Kernel out file is no long Image.lz4-dtb. The dtb file is separated out. And I failed to replace the dtb files and kernel modules.
Second try:
This time I move all the kernel dist files to the aosp/device/google/coral-kernel. But the touch screen still do not work.
Related
Hi guys,
I'd like to tinker around a bit with the tiamat or other kernels for the Xoom
are the following steps enough to get it working ?
- clone the repo
- adjust toolchain paths (or create an external script that does it)
- make stingray_defconfig
- make -j2
- test-boot the zImage via fastboot
- if it's successful copy over the kernel-modules & flash the kernel via fastboot
how about an initramfs ?
have I forgotten anything ?
Many thanks in advance for your help !
edit:
slowly understanding how all this works,
still might need some help
I think that will get you started. I'm not an expert, but when I'm tinkering with kernels I pull the proc config strait from the device after flashing the kernel I want to modify. That way I know that the default config is correct. For example, if I wanted to modify the kernel running on an EOS nightly, after cloning the repo I would flash the EOS nightly ROM containing the kernel I want to modify. Then run the following commands to pull the kernel config from the kernel running on my device:
Code:
adb pull /proc/config.gz .
gunzip config.gz
mv config .config
The .config then goes in the root of the kernel source directory. That may do exactly the same thing as the "make defconfig" you mentioned but I just prefer to trust the defaults from the ROM and not the repo.
Why wont my compiled rom with Linaro optimzations boot ive successfully compiled rom for other devices just not this one have any thoughts i even this
git clone git://github.com/TheMuppets/proprietary_vendor_broadcom.git -b cm-10.1 vendors/broadcom
git clone git://github.com/TheMuppets/proprietary_vendor_nvidia.git -b cm-10.1 vendors/nvidia
git clone git://github.com/TheMuppets/proprietary_vendor_motorola.git -b cm-10.1 vendors/motorola
missed some file/library
dl an rom, open .zip file and compare all file with you rom.
you will find some missing file
Hi,
I am porting CM-10 to Geeksphone Peak. If I replace init config files + init itself in my produced boot.img with the files included in working ROM, device connects to ADB. Otherwise, not. I have also tried to use my init and config files from working ROM and vice versa, both did not work.
I did not specify any init files in my device source tree, but some default init file were produced anyway. In those are imported some non-existing files (such as init.${ro.hardware}.rc), so far I have tried to comment these lines with the same result.
Do I have to make so device specific init config files? Is there anything else needed to be set up (nothing is mentioned on the wiki for porting CM)? Is there any way to debug if ADB can not connect to the device?
Just note: I am porting CM-10 with following commands:
Code:
. build/envsetup.sh
lunch cm_peak-eng
mka bacon
I need some help of the developer to compile the kernel of the letv 1s. I tried to compile with the instruction provided on the letv 1s source code. I successfully compiled it with some warnings, although when I flash it, the phone failed to boot.
This is what I used to compile
------------------------------------------------------------------------------------------------------------------------
Le 1S Kernel Build mini-Howto
===============================
1. Build
--------
- get toolchain
From android git server, codesourcery etc.
- aarch64-linux-android-4.9
- Unpack kernel source
Suppose kernel source has been unpacked to <kernel> dir.
- make output folder
$ mkdir <kernel>/out
- export env variables
export correct "CROSS_COMPILE" to use the toolchain path you have downloaded.
$ export CROSS_COMPILE=<Your cross compilee dir>/aarch64-linux-android-4.9/bin/aarch64-linux-android-
$ export JOBS=16 # Can be CPU core # x 2
- build kernel
$ cd <kernel>
$ make -C $PWD O=$PWD/out ARCH=arm64 x500_defconfig
$ make -j$JOBS -C $PWD O=$PWD/out ARCH=arm64 KCFLAGS=-mno-android
2. Output files
---------------
- Kernel: out/arch/arm64/boot/Image
--------------------------------------------------------------------------------------------------------------------------
Expect help from @DroidThug & other developers
superac11 said:
I need some help of the developer to compile the kernel of the letv 1s. I tried to compile with the instruction provided on the letv 1s source code. I successfully compiled it with some warnings, although when I flash it, the phone failed to boot.
This is what I used to compile
------------------------------------------------------------------------------------------------------------------------
Le 1S Kernel Build mini-Howto
===============================
1. Build
--------
- get toolchain
From android git server, codesourcery etc.
- aarch64-linux-android-4.9
- Unpack kernel source
Suppose kernel source has been unpacked to <kernel> dir.
- make output folder
$ mkdir <kernel>/out
- export env variables
export correct "CROSS_COMPILE" to use the toolchain path you have downloaded.
$ export CROSS_COMPILE=<Your cross compilee dir>/aarch64-linux-android-4.9/bin/aarch64-linux-android-
$ export JOBS=16 # Can be CPU core # x 2
- build kernel
$ cd <kernel>
$ make -C $PWD O=$PWD/out ARCH=arm64 x500_defconfig
$ make -j$JOBS -C $PWD O=$PWD/out ARCH=arm64 KCFLAGS=-mno-android
2. Output files
---------------
- Kernel: out/arch/arm64/boot/Image
--------------------------------------------------------------------------------------------------------------------------
Expect help from @DroidThug & other developers
Click to expand...
Click to collapse
Hello.
Sorry for the late reply, but have Exams going on.
You can try using https://github.com/DroidThug/android_kernel_leeco_MT6795 as the source
I have fixed up stuff here and there. You may try compiling from here
Also, if you would like, you may use UBERTC from
https://github.com/DroidThug/aarch64-linux-android-gcc-4.9
You may also use the script from https://raw.githubusercontent.com/D...8bc37a9f01b6ddc77971754bdadd0e476/infernus.sh
DroidThug said:
Hello.
Sorry for the late reply, but have Exams going on.
You can try using https://github.com/DroidThug/android_kernel_leeco_MT6795 as the source
I have fixed up stuff here and there. You may try compiling from here
Also, if you would like, you may use UBERTC from
https://github.com/DroidThug/aarch64-linux-android-gcc-4.9
You may also use the script from https://raw.githubusercontent.com/D...8bc37a9f01b6ddc77971754bdadd0e476/infernus.sh
Click to expand...
Click to collapse
Thank you , Although i had already coompiled kernel and started to build the cm 13, everything gone good except brunch command,
----------------------------------------------------------------------------------------------------
[email protected]:/mnt/new/minimal$ lunch
You're building on Linux
Lunch menu... pick a combo:
1. cm_x500-eng 5. minimal_hammerhead-userdebug
2. cm_x500-user 6. minimal_mako-userdebug
3. cm_x500-userdebug 7. minimal_shamu-userdebug
4. minimal_angler-userdebug
Which would you like? [aosp_arm-eng] 1
build/core/product_config.mk:222: *** Can not locate config makefile for product "cm_x500". Stop.
WARNING: Trying to fetch a device that's already there
WARNING: device/LeTV/x500/minimal.dependencies file not found
build/core/product_config.mk:222: *** Can not locate config makefile for product "cm_x500". Stop.
** Don't have a product spec for: 'cm_x500'
** Do you have the right repo manifest?
[email protected]:/mnt/new/minimal$
superac11 said:
Thank you , Although i had already coompiled kernel and started to build the cm 13, everything gone good except brunch command,
----------------------------------------------------------------------------------------------------
[email protected]:/mnt/new/minimal$ lunch
You're building on Linux
Lunch menu... pick a combo:
1. cm_x500-eng 5. minimal_hammerhead-userdebug
2. cm_x500-user 6. minimal_mako-userdebug
3. cm_x500-userdebug 7. minimal_shamu-userdebug
4. minimal_angler-userdebug
Which would you like? [aosp_arm-eng] 1
build/core/product_config.mk:222: *** Can not locate config makefile for product "cm_x500". Stop.
WARNING: Trying to fetch a device that's already there
WARNING: device/LeTV/x500/minimal.dependencies file not found
build/core/product_config.mk:222: *** Can not locate config makefile for product "cm_x500". Stop.
** Don't have a product spec for: 'cm_x500'
** Do you have the right repo manifest?
[email protected]:/mnt/new/minimal$
Click to expand...
Click to collapse
You are building Minimal OS eh?
Minimal is based off AOSP, and the tree you use is of CyanogenMod.
You might have to edit stuff here and there
Hi guys
I'm new to rom development, I have many question to deal with...
First thing first, I'm about to download android source as per the steps in source.android.com, but i have limited data quota per day. so i searched the internet to reduce the downloading source size and i found that adding
Code:
--depth=1
to git clone command will reduce the downloading size.
But I need to know what is the difference between below two git clone commands
Code:
repo init --depth=1 -u https://android.googlesource.com/platform/manifest -b android-5.0.0_r1.0.1
and
Code:
repo init -u https://android.googlesource.com/platform/manifest -b android-5.0.0_r1.0.1
Second thing is I'm building rom for Huawei ascend P6-U06 (code name: hwp6-u06), for this device i can't find kernel tree, device tree and vendor blobs for lollipop. I'm only getting kernel tree, device tree and vendor blobs for Kitkat in github (cm-11.0 based) can i use these ones
orelse can i use google common kernel source to build custom kernel