Search results

You can either get it from kernel.org or kernel/common: git pull https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git v4.14.190 git pull https://android.googlesource.com/kernel/common d2d05bcf4b4edf8d028fa420dee3c6644aa5b4ac The kernel/common hash is Greg's merge of 4.14.190...

You will need to build the modules into the kernel. For newer kernels, it is a little bit more complicated. Normally, you would just change the '=m' entries in the configuration file to '=y' but there are modules elsewhere. I would recommend using a basic custom kernel like ElementalX or the...

I know that ANDROID_MAJOR_VERSION is a Samsung specific thing... I am not sure beyond that unfortunately. That is probably the source of your issue but I am not sure. Are you trying to compile a stock or custom kernel?

You do not need to run 'make clean' if you have not actually built anything.

You need to use 'make O=out' for all invocations of 'make'.

Yes, it is generally better to use more recent compiler versions. You get access to new warnings that can find latent bugs in your code and each compiler releases typically fixes latent bugs within the compiler as well. It is up to you though, it is all about the gains versus the effort you...

No, just disabling MODULES is enough because the kernel won't have the loading support. Unfortunately, I do not have much else to offer you :(

Helping you boot a kernel is outside the scope of this thread. Please find your device specific forum and ask there. It seems like a broken kernel source but I don't know, that should not be happening with the stock source. The ANDROID_MAJOR_VERSION thing might be necessary. Yes, you can...

"#error NO corresponding project of mtk_udi.h header file can be found!!!" Seems your source might be incomplete but I don't know. Are you using "O=out" with all of your make commands? It all depends on the device and kernel. .ko are kernel modules and generally/usually need to be...

git clone -b android-9.0.0_r1 https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9

Your CROSS_COMPILE variable is just not set properly. It needs to either be the full patch to your aarch64-linux-gnu- or aarch64-linux-android- toolchain or just aarch64-linux-gnu- or aarch64-linux-android-, depending on what you are doing.

Either build android-10.0.0_r0.49, where this was fixed because of a linux-stable merge or cherry-pick the actual fix: https://android.googlesource.com/kernel/msm/+/760f8522ce08a24abac3208290f93fe3fffc0d6c

Unfortunately, my time nowadays is limited between my job, school, and more important open source projects. However, compiling with GCC 9.2.0 is the same as compiling with GCC 4.9.4, you point the CROSS_COMPILE variable at the GCC 9.2.0 toolchain (or use PATH and update the CROSS_COMPILE prefix...

Was your kernel source originally a zip file? Basically, what that error means is that git can't find a common ancestor, which ultimately means that NO upstream Linux commit exists in your repository, which usually happens when you take a zip'd or tar'd kernel source, run git init on it, git add...

For number 1, you can either use the LOCALVERSION environment variable (export LOCALVERSION=-mykernelname) or CONFIG_LOCALVERSION in your defconfig. For number 2, I have no idea.

He means fetching the linux-4.4.y branch from https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/. You can use my repo (the one you have linked there) instead if you would like. In either case, I would highly recommend merging the changes instead of cherry-picking as it will make...

I mean, I feel like that statement is fairly well worded. If you are compiling on your phone, you would be doing a native rather than cross build so the host tools would work. This guide is written from an x86_64 host perspective, hence that comment.

I would recommend reading this guide that I have: https://gist.github.com/nathanchance/965028fc180b1cced015ac7530b2eaeb

Looks like autoconf-archive needs to be installed on Ubuntu: https://github.com/USBhost/build-tools-gcc/issues/32#issuecomment-494173124 If you have further issues, open an issue in that repo as I no longer maintain that script.

You need to rebuild the Wi-Fi module against the source that you compiled then flash it. Alternatively, you can try building the Wi-Fi source into the kernel image but that is usually broken or you can force the module to load by whitelisting it in kernel/module.c (there are commits floating...

No, you have it backwards; MODPOST 0 MODULES means that all drivers are built in. MODPOST # MODULES means that there are .ko (kernel module) files that needs to be gathered up and flashed to have access to the drivers. It means build the object files in a separate directory rather than It...

You don't seem to be describing a problem... the regular * means that the drivers are built in, M means they are built as modules.

Do you have any modules enabled in your config?

No, the Image.gz is most likely the one you want to use (gzip compressed Image). I don't know of a device off the top of my head that uses a decompressed kernel image. You'll want to run: make O=../out menuconfig after make O=../out mido_defconfig.

Revert this commit: https://github.com/FSadino/android_kernel_oneplus_msm8996/commit/9af64df256276978ad8d8539b4109effa422bee6 You have the toggable one: https://github.com/FSadino/android_kernel_oneplus_msm8996/commit/b1f51dc25045f13ed049ecf04ea66ef74c3d8112 I would recommend fixing those...

You will need https://github.com/nathanchance/marlin/commit/8d6c215f5e84454790e4d43d9819b8e23b904aff for vdso32 support on 3.18.

Sounds like you need this: https://github.com/kenny3fcb/nethunter_kernel_zuk_msm8996-3.18/commit/5aced38f07dedf13a42eed0965750724bb605036 I haven't added it to my msm-3.18 patch as I never needed it, leading me to believe it is environment related.

The issue with Wi-Fi calling on my kernel was a result of disabling CONFIG_DUMMY: https://github.com/nathanchance/wahoo/commit/dbedc0a7cccf9d32c2de3f4d22665277da8dd38f That doesn't appear to be the case here...

All Android devices are little endian so you want the regular aarch64-linux-gnu one.

This applies to me as well :)

This is because WireGuard temporarily turns BUILD_BUG_ON into a no-op for Clang. This can be fixed by marking that variable as __maybe_unused: https://github.com/nathanchance/op6/commit/ebd67e95a8c7e508b43edeedb479adff9622c397

You need to use make O=out instead of make Be sure to run make mrproper before compiling again.

MSF Jarvis has brought Caesium to the Pixel 2 (XL) :) Subscribe to his thread for update posts and such: https://forum.xda-developers.com/pixel-2/development/taimen-walleye-caesium-kernel-v0-2-t3878737 If you want a kernel that is going to be similar in feel and stability as Flash, look no...

MSF Jarvis has brought Caesium to the Pixel 2 (XL) :) Subscribe to his thread for update posts and such: https://forum.xda-developers.com/pixel-2/development/taimen-walleye-caesium-kernel-v0-2-t3878737 If you want a kernel that is going to be similar in feel and stability as Flash, look no...

Update to 2.15! This will be the last build of Flash indefinitely. I am stepping back from Android as I have become exhausted with all of the work of staying up to date. I recently started a new job, which has consumed most of my free time, and I have been contributing to ClangBuiltLinux, a...

Update to 2.10! This will be the last build of Flash indefinitely. I am stepping back from Android as I have become pretty exhausted with all of the work of staying up to date. I recently started a new job, which has consumed most of my free time, and I have been contributing to...

Update to 3.19! This will be the last build of Flash indefinitely. I am stepping back from Android as I have become exhausted with all of the work of staying up to date. I recently started a new job, which has consumed most of my free time, and I have been contributing to ClangBuiltLinux, a...

I will most likely switch to it within the next couple of builds, I already have the commits picked from kernel/common on my private builds. Sent from my Google Pixel 2 XL using XDA Labs

For the record, someone asked if I had added it and I said no, not that I wouldn't do it. I've been working on another side project so I haven't really been paying attention to the Android kernel space. Sent from my Google Pixel 2 XL using XDA Labs

Ugh forgot to bump that in the AnyKernel script, it'll be fixed in the next build. Sent from my Google Pixel 2 XL using XDA Labs

Update to 2.14! Remember any and all bug reports need to include logs and clear steps to reproduce (see the info in the OP). You should also know what version it started with. If you want to be a tester and get builds before they are released here or just hangout, feel free to stop by Telegram...

Update to 3.18! Remember any and all bug reports need to include logs and clear steps to reproduce (see the info in the OP). You should also know what version it started with. If you want to be a tester and get builds before they are released here or just hangout, feel free to stop by Telegram...

There will be a formal announcement on the mailing list when 3.18 is officially dead and I will announce it here. Greg has purposefully made 3.18 updates happen less often; right now the ratio of 3.18 updates to other stable updates is about 1:3 (for every three stable updates, 3.18 will get...

You take that back. Sent from my Google Pixel 2 XL using XDA Labs

I don't currently plan to upgrade although I may be getting a 6T through OnePlus' developer program. We'll see. I've been rather focused on another project as of late.

I'm definitely not having any issues. Could be a rogue app. Sent from my Google Pixel 2 XL using XDA Labs

4.4.162 has been merged into the msm-4.4 tree. 4.9.135 has been merged into the msm-4.9 tree.

4.9.135 has been merged in. Sorry, I forgot to announce 4.9.134 apparently :/

4.4.162 has been merged in.

4.4.162 has been merged in.