General Kernel source finally released

Search This thread

Zylam Marex

Member
Dec 26, 2008
37
3
Redmi K20 Pro
Redmi Note 11
Does the Kernel being for Android 11 mean its useless for us? Can Android 12/13 roms not be made with it? I really just wanted working doubletap2wake, would the Android 11 Kernel make that happen? Thank you!
 

NeoPreacher

Senior Member
Dec 4, 2012
877
489
38
Bielefeld
Moto G5 Plus
Redmi Note 8
Does the Kernel being for Android 11 mean its useless for us? Can Android 12/13 roms not be made with it? I really just wanted working doubletap2wake, would the Android 11 Kernel make that happen? Thank you!
No; sure; works already flawless in PA, but sure why not. There are others problems eg. missing drivers in source and missing devs in group. Fyi: many people using a13 custom rom with a11 stock kernel actually on rn11
 

Zylam Marex

Member
Dec 26, 2008
37
3
Redmi K20 Pro
Redmi Note 11
No; sure; works already flawless in PA, but sure why not. There are others problems eg. missing drivers in source and missing devs in group. Fyi: many people using a13 custom rom with a11 stock kernel actually on rn11
Oh wow really, tape2wake works great in PA? I have tried almost all roms but PA. Thank you for letting me know, a shame the Kernel is missing drivers and such. I wonder why Xiaomi is trying to make sure the Note 11 is never developed for, it's such a good phone with a custom rom.
 

aureljared

Senior Member
May 2, 2013
967
669
dantis.me
Redmi Note 11
tap2wake also works on PixelExperience, FWIW.

EDIT: board_id.h is present in the same directory, not in include/. \

I've tried compiling the kernel from Xiaomi's sources and stumbled across an error about a missing header file:
Code:
drivers/misc/st21nfc.c:43:22: fatal error: board_id.h: No such file or directory
 #include <board_id.h>
                      ^
compilation terminated.
make[2]: *** [scripts/Makefile.build:338: drivers/misc/st21nfc.o] Error 1
make[1]: *** [scripts/Makefile.build:642: drivers/misc] Error 2

This file board_id.h does not exist in the include/ folder. Perhaps Xiaomi uploaded incomplete sources?
 
Last edited:

maXDAmn

Senior Member
Jul 23, 2016
274
53
tap2wake also works on PixelExperience, FWIW.

EDIT: board_id.h is present in the same directory, not in include/. \

I've tried compiling the kernel from Xiaomi's sources and stumbled across an error about a missing header file:
Code:
drivers/misc/st21nfc.c:43:22: fatal error: board_id.h: No such file or directory
 #include <board_id.h>
                      ^
compilation terminated.
make[2]: *** [scripts/Makefile.build:338: drivers/misc/st21nfc.o] Error 1
make[1]: *** [scripts/Makefile.build:642: drivers/misc] Error 2

This file board_id.h does not exist in the include/ folder. Perhaps Xiaomi uploaded incomplete sources?
yes
 

aureljared

Senior Member
May 2, 2013
967
669
dantis.me
Redmi Note 11
Much easier to compile this kernel using Clang rather than GCC. Still getting used to it, it's been a good while since my last kernel compile, haha.

Does anyone know how to build a new boot image by hand? I have a working boot.img for PixelExperience and I'd like to replace the kernel with one that I built for testing, but I'm not sure if I should still use mkbootimg like with older Android devices as this is the first time I'll be dealing with a device that uses dtb/dtbo files. Any insights would be welcome.

EDIT: board_id.h is present in the same directory, not in include/.
 

SAM209

Senior Member
Mar 23, 2012
139
12
Not an expert here. What exactly are the benefits of this? What does it mean for custom ROM development?
 

aureljared

Senior Member
May 2, 2013
967
669
dantis.me
Redmi Note 11
Not an expert here. What exactly are the benefits of this? What does it mean for custom ROM development?
For one, it is theoretically easier to keep the device up to date without having to wait for Xiaomi's updates. Some changes that come with Android's monthly security patches are made to the kernel, for example, and having the kernel source code means we can apply those patches faster than if we were to wait for updated kernel builds from Xiaomi.

Some ROMs like LineageOS also require kernels to be built from source (i.e., not prebuilt) for a device to be granted official status.
 
  • Like
Reactions: SAM209

jasmin811

Senior Member
Apr 28, 2015
118
52
Tuzla
Hello,
Can someone guide me on how to install that kernel on redmi note 11 (Pixel Experience custom os)
Already installed twrp 3.7.0 but gives me some errors all the time like Invalid zip file format!.
I download it as zip from github and put it in twrp folder and install it from there.

Thanks in advance
 

NeoPreacher

Senior Member
Dec 4, 2012
877
489
38
Bielefeld
Moto G5 Plus
Redmi Note 8
Hello,
Can someone guide me on how to install that kernel on redmi note 11 (Pixel Experience custom os)
Already installed twrp 3.7.0 but gives me some errors all the time like Invalid zip file format!.
I download it as zip from github and put it in twrp folder and install it from there.

Thanks in advance
There's nothing to flash here. Only the link to the kernel source. There's still some work to do for a flashable kernel (compiling eg). Also there are drivers missing in the source it seems. What you tried was flashing the uncompiled kernel source package i guess and that.. doesn't work
 

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    It finally happened the source code is released
    https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/spes-r-oss

    Leaving this also as a place for first discussions. So, go for it. đŸ¤˜
    3
    It only took them a year and three months to release it.

    Oh god...
    2
    The benefits of reading...
    1
    It finally happened the source code is released
    https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/spes-r-oss

    Leaving this also as a place for first discussions. So, go for it. đŸ¤˜
    Finally!!! đŸ”¥
    1
    Running the (unofficial)LOS here - indeed tap2wake is broken as described above. 5 seconds after the screen turns off it won't work anymore. However, there's a trick I discovered by mistake that works also after those 5 seconds, without destroying that (disastrously designed) fingerprint scanner button:
    - double tap the screen and then tap the third time and keep the finger on the screen until it turns on. Works every tine.

    Now, according to my observations it looks like a power management issue and not necessarily the tap2wake disfunctionality. If i put the phone on charging, the simple (double) tap2wake works every time. Also, tap2wake works all the time if I charge the phone at 100%. Therefore I believe that normal (double) tap2wake doesn't work when the phone enters doze mode. .. and it doesn't enter doze mode if the battery is charged at 100%.
    But this issue with phone not entering doze mode after a 100% charge looks like a common LOS issue - i had it for years (didn't got fixed) on an Samsung device with official LOS.