Wow thanks I really appreciate itno new kernel changes it seems, but that´s not really surprising.
but since pixel 4a still gets updates, I can just merge the security updates from there.
when I find time I´ll give the kernel a bump.
[Kernel][28.05.2023][4.14.315][A12][A13] Kirisakura 9.1.6 for Pixel 4/XL aka FLORAL
- Thread starter Freak07
- Start date
Thank you for your great work ! I wonder if it is possible to build the kernel myself in order to enable docker-required config manually .Really want to run docker on my phone !
Hi ! I tried to compile the kernel but failed with the following error.
My environment :
Ubuntu 20.04 running in VirtualBox
AOSP clang r475365b + AOSP gcc 4.9 android-13.0.0_r0.21
branches : master_T_floral_caf_27
Command :
I would spare no efforts to offer any information you need to diagnose the problem. PLEASE HELP ME !
Thank you for your excellent work again !
/tmp/vgettimeofday-1bcac4.s: Assembler messages:
/tmp/vgettimeofday-1bcac4.s:3: Error: junk at end of line, first unrecognized character is `"'
/tmp/vgettimeofday-1bcac4.s:3: Error: file number less than one
/tmp/vgettimeofday-1bcac4.s:4: Error: junk at end of line, first unrecognized character is `"'
/tmp/vgettimeofday-1bcac4.s:5: Error: junk at end of line, first unrecognized character is `"'
/tmp/vgettimeofday-1bcac4.s:6: Error: junk at end of line, first unrecognized character is `"'
/tmp/vgettimeofday-1bcac4.s:7: Error: junk at end of line, first unrecognized character is `"'
/tmp/vgettimeofday-1bcac4.s:54: Error: junk at end of line, first unrecognized character is `"'
/tmp/vgettimeofday-1bcac4.s:67: Error: junk at end of line, first unrecognized character is `"'
/tmp/vgettimeofday-1bcac4.s:143: Error: junk at end of line, first unrecognized character is `"'
/tmp/vgettimeofday-1bcac4.s:175: Error: junk at end of line, first unrecognized character is `"'
/tmp/vgettimeofday-1bcac4.s:1131: Error: junk at end of line, first unrecognized character is `"'
/tmp/vgettimeofday-1bcac4.s:1132: Error: junk at end of line, first unrecognized character is `"'
/tmp/vgettimeofday-1bcac4.s:1133: Error: junk at end of line, first unrecognized character is `"'
/tmp/vgettimeofday-1bcac4.s:1134: Error: junk at end of line, first unrecognized character is `"'
/tmp/vgettimeofday-1bcac4.s:1152: Error: junk at end of line, first unrecognized character is `"'
clang-16: error: assembler command failed with exit code 1 (use -v to see invocation)
make[2]: *** [../arch/arm64/kernel/vdso/Makefile:70: arch/arm64/kernel/vdso/vgettimeofday.o] Error 1
make[1]: *** [arch/arm64/Makefile:283: vdso_prepare] Error 2
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory '/home/metatron/pixel4/kernel/FLORAL-master_T_floral_caf_27/out'
make: *** [Makefile:146: sub-make] Error 2
My environment :
Ubuntu 20.04 running in VirtualBox
AOSP clang r475365b + AOSP gcc 4.9 android-13.0.0_r0.21
branches : master_T_floral_caf_27
Command :
$make O=out ARCH=arm64 floral_defconfig
$make -j$(nproc --all) O=out ARCH=arm64 CC=clang CLANG_TRIPLE=aarch64-linux-gnu- CROSS_COMPILE=aarch64-linux-android- CROSS_COMPILE_ARM32=arm-linux-androideabi-
I would spare no efforts to offer any information you need to diagnose the problem. PLEASE HELP ME !
Thank you for your excellent work again !
That's the script I'm using to compile:
FLORAL/build_kirisakura.sh at master_T_floral_caf_27 · freak07/FLORAL
Kirisakura Kernel for the Pixel 4/XL. Contribute to freak07/FLORAL development by creating an account on GitHub.
github.com
From a quick glance the defconfig is not correct. You might need to make sure the other exports are matching as well.
DTC can be compiled either from AOSP source or you can search Google/GitHub for pre compiled ones.
I downloaded pixel 4 aosp kernel source and I found dtc source in kernel/private/msm-google/scripts/dtc .Then I compiled the kernel ,but couldn't found dtc binary in the output folder.How can I build dtc from aosp ? Sorry I'm new in this field...That's the script I'm using to compile:
FLORAL/build_kirisakura.sh at master_T_floral_caf_27 · freak07/FLORAL
Kirisakura Kernel for the Pixel 4/XL. Contribute to freak07/FLORAL development by creating an account on GitHub.
From a quick glance the defconfig is not correct. You might need to make sure the other exports are matching as well.
DTC can be compiled either from AOSP source or you can search Google/GitHub for pre compiled ones.
Hi ! I ran the build script you provide,and I used prebuilt DTC provided by AOSP in "kernel/prebuilts-master/misc/linux-x86/dtc/".Then I received the following error :
I don't know if it's because I'm using a different compiler than you ？
Eager for your help !
Code:
../net/wireguard/ratelimiter.c:185:33: error: ordered comparison between pointer and integer ('unsigned long (*)(void)' and 'unsigned long') [-Werror]
table_size = (totalram_pages() > (1U << 30) / PAGE_SIZE) ? 8192 :
~~~~~~~~~~~~~~~~ ^ ~~~~~~~~~~~~~~~~~~~~~~
../net/wireguard/ratelimiter.c:187:22: error: invalid operands to binary expression ('unsigned long (void)' and 'int')
(totalram_pages() << PAGE_SHIFT) /
~~~~~~~~~~~~~~~~ ^ ~~~~~~~~~~
../include/linux/log2.h:174:23: note: expanded from macro 'roundup_pow_of_two'
__builtin_constant_p(n) ? ( \
^
../include/linux/kernel.h:900:59: note: expanded from macro 'max_t'
#define max_t(type, x, y) __careful_cmp((type)(x), (type)(y), >)
^
../include/linux/kernel.h:824:38: note: expanded from macro '__careful_cmp'
__builtin_choose_expr(__safe_cmp(x, y), \
^
../include/linux/kernel.h:814:19: note: expanded from macro '__safe_cmp'
(__typecheck(x, y) && __no_side_effects(x, y))
^
../include/linux/kernel.h:800:40: note: expanded from macro '__typecheck'
(!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
^
../net/wireguard/ratelimiter.c:187:22: error: invalid operands to binary expression ('unsigned long (void)' and 'int')
(totalram_pages() << PAGE_SHIFT) /
~~~~~~~~~~~~~~~~ ^ ~~~~~~~~~~
../include/linux/log2.h:175:5: note: expanded from macro 'roundup_pow_of_two'
((n) == 1) ? 1 : \
^
../include/linux/kernel.h:900:59: note: expanded from macro 'max_t'
#define max_t(type, x, y) __careful_cmp((type)(x), (type)(y), >)
^
../include/linux/kernel.h:824:38: note: expanded from macro '__careful_cmp'
__builtin_choose_expr(__safe_cmp(x, y), \
^
../include/linux/kernel.h:814:19: note: expanded from macro '__safe_cmp'
(__typecheck(x, y) && __no_side_effects(x, y))
^
../include/linux/kernel.h:800:40: note: expanded from macro '__typecheck'
(!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
^
../net/wireguard/ratelimiter.c:187:22: error: invalid operands to binary expression ('unsigned long (void)' and 'int')
(totalram_pages() << PAGE_SHIFT) /
~~~~~~~~~~~~~~~~ ^ ~~~~~~~~~~
../include/linux/log2.h:176:19: note: expanded from macro 'roundup_pow_of_two'
(1UL << (ilog2((n) - 1) + 1)) \
^
../include/linux/log2.h:157:23: note: expanded from macro 'ilog2'
__builtin_constant_p(n) ? \
^
../include/linux/kernel.h:900:59: note: expanded from macro 'max_t'
#define max_t(type, x, y) __careful_cmp((type)(x), (type)(y), >)
^
../include/linux/kernel.h:824:38: note: expanded from macro '__careful_cmp'
__builtin_choose_expr(__safe_cmp(x, y), \
^
../include/linux/kernel.h:814:19: note: expanded from macro '__safe_cmp'
(__typecheck(x, y) && __no_side_effects(x, y))
^
../include/linux/kernel.h:800:40: note: expanded from macro '__typecheck'
(!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
^
../net/wireguard/ratelimiter.c:187:22: error: invalid operands to binary expression ('unsigned long (void)' and 'int')
(totalram_pages() << PAGE_SHIFT) /
~~~~~~~~~~~~~~~~ ^ ~~~~~~~~~~
../include/linux/log2.h:176:19: note: expanded from macro 'roundup_pow_of_two'
(1UL << (ilog2((n) - 1) + 1)) \
^
../include/linux/log2.h:158:14: note: expanded from macro 'ilog2'
const_ilog2(n) : \
^
../include/linux/log2.h:78:23: note: expanded from macro 'const_ilog2'
__builtin_constant_p(n) ? ( \
^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
../include/linux/kernel.h:824:38: note: expanded from macro '__careful_cmp'
__builtin_choose_expr(__safe_cmp(x, y), \
^
../include/linux/kernel.h:814:19: note: expanded from macro '__safe_cmp'
(__typecheck(x, y) && __no_side_effects(x, y))
^
../include/linux/kernel.h:800:40: note: expanded from macro '__typecheck'
(!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
^
../net/wireguard/ratelimiter.c:187:22: error: invalid operands to binary expression ('unsigned long (void)' and 'int')
(totalram_pages() << PAGE_SHIFT) /
~~~~~~~~~~~~~~~~ ^ ~~~~~~~~~~
../include/linux/log2.h:176:19: note: expanded from macro 'roundup_pow_of_two'
(1UL << (ilog2((n) - 1) + 1)) \
^
../include/linux/log2.h:158:14: note: expanded from macro 'ilog2'
const_ilog2(n) : \
^
../include/linux/log2.h:79:4: note: expanded from macro 'const_ilog2'
(n) < 2 ? 0 : \
^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
../include/linux/kernel.h:824:38: note: expanded from macro '__careful_cmp'
__builtin_choose_expr(__safe_cmp(x, y), \
^
../include/linux/kernel.h:814:19: note: expanded from macro '__safe_cmp'
(__typecheck(x, y) && __no_side_effects(x, y))
^
../include/linux/kernel.h:800:40: note: expanded from macro '__typecheck'
(!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
^
../net/wireguard/ratelimiter.c:187:22: error: invalid operands to binary expression ('unsigned long (void)' and 'int')
(totalram_pages() << PAGE_SHIFT) /
~~~~~~~~~~~~~~~~ ^ ~~~~~~~~~~
../include/linux/log2.h:176:19: note: expanded from macro 'roundup_pow_of_two'
(1UL << (ilog2((n) - 1) + 1)) \
^
../include/linux/log2.h:158:14: note: expanded from macro 'ilog2'
const_ilog2(n) : \
^
../include/linux/log2.h:80:4: note: expanded from macro 'const_ilog2'
(n) & (1ULL << 63) ? 63 : \
^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
../include/linux/kernel.h:824:38: note: expanded from macro '__careful_cmp'
__builtin_choose_expr(__safe_cmp(x, y), \
^
../include/linux/kernel.h:814:19: note: expanded from macro '__safe_cmp'
(__typecheck(x, y) && __no_side_effects(x, y))
^
../include/linux/kernel.h:800:40: note: expanded from macro '__typecheck'
(!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
^
../net/wireguard/ratelimiter.c:187:22: error: invalid operands to binary expression ('unsigned long (void)' and 'int')
(totalram_pages() << PAGE_SHIFT) /
~~~~~~~~~~~~~~~~ ^ ~~~~~~~~~~
../include/linux/log2.h:176:19: note: expanded from macro 'roundup_pow_of_two'
(1UL << (ilog2((n) - 1) + 1)) \
^
../include/linux/log2.h:158:14: note: expanded from macro 'ilog2'
const_ilog2(n) : \
^
../include/linux/log2.h:81:4: note: expanded from macro 'const_ilog2'
(n) & (1ULL << 62) ? 62 : \
^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
../include/linux/kernel.h:824:38: note: expanded from macro '__careful_cmp'
__builtin_choose_expr(__safe_cmp(x, y), \
^
../include/linux/kernel.h:814:19: note: expanded from macro '__safe_cmp'
(__typecheck(x, y) && __no_side_effects(x, y))
^
../include/linux/kernel.h:800:40: note: expanded from macro '__typecheck'
(!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
^
../net/wireguard/ratelimiter.c:187:22: error: invalid operands to binary expression ('unsigned long (void)' and 'int')
(totalram_pages() << PAGE_SHIFT) /
~~~~~~~~~~~~~~~~ ^ ~~~~~~~~~~
../include/linux/log2.h:176:19: note: expanded from macro 'roundup_pow_of_two'
(1UL << (ilog2((n) - 1) + 1)) \
^
../include/linux/log2.h:158:14: note: expanded from macro 'ilog2'
const_ilog2(n) : \
^
../include/linux/log2.h:82:4: note: expanded from macro 'const_ilog2'
(n) & (1ULL << 61) ? 61 : \
^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
../include/linux/kernel.h:824:38: note: expanded from macro '__careful_cmp'
__builtin_choose_expr(__safe_cmp(x, y), \
^
../include/linux/kernel.h:814:19: note: expanded from macro '__safe_cmp'
(__typecheck(x, y) && __no_side_effects(x, y))
^
../include/linux/kernel.h:800:40: note: expanded from macro '__typecheck'
(!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
^
../net/wireguard/ratelimiter.c:187:22: error: invalid operands to binary expression ('unsigned long (void)' and 'int')
(totalram_pages() << PAGE_SHIFT) /
~~~~~~~~~~~~~~~~ ^ ~~~~~~~~~~
../include/linux/log2.h:176:19: note: expanded from macro 'roundup_pow_of_two'
(1UL << (ilog2((n) - 1) + 1)) \
^
../include/linux/log2.h:158:14: note: expanded from macro 'ilog2'
const_ilog2(n) : \
^
../include/linux/log2.h:83:4: note: expanded from macro 'const_ilog2'
(n) & (1ULL << 60) ? 60 : \
^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
../include/linux/kernel.h:824:38: note: expanded from macro '__careful_cmp'
__builtin_choose_expr(__safe_cmp(x, y), \
^
../include/linux/kernel.h:814:19: note: expanded from macro '__safe_cmp'
(__typecheck(x, y) && __no_side_effects(x, y))
^
../include/linux/kernel.h:800:40: note: expanded from macro '__typecheck'
(!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
^
../net/wireguard/ratelimiter.c:187:22: error: invalid operands to binary expression ('unsigned long (void)' and 'int')
(totalram_pages() << PAGE_SHIFT) /
~~~~~~~~~~~~~~~~ ^ ~~~~~~~~~~
../include/linux/log2.h:176:19: note: expanded from macro 'roundup_pow_of_two'
(1UL << (ilog2((n) - 1) + 1)) \
^
../include/linux/log2.h:158:14: note: expanded from macro 'ilog2'
const_ilog2(n) : \
^
../include/linux/log2.h:84:4: note: expanded from macro 'const_ilog2'
(n) & (1ULL << 59) ? 59 : \
^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
../include/linux/kernel.h:824:38: note: expanded from macro '__careful_cmp'
__builtin_choose_expr(__safe_cmp(x, y), \
^
../include/linux/kernel.h:814:19: note: expanded from macro '__safe_cmp'
(__typecheck(x, y) && __no_side_effects(x, y))
^
../include/linux/kernel.h:800:40: note: expanded from macro '__typecheck'
(!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
^
../net/wireguard/ratelimiter.c:187:22: error: invalid operands to binary expression ('unsigned long (void)' and 'int')
(totalram_pages() << PAGE_SHIFT) /
~~~~~~~~~~~~~~~~ ^ ~~~~~~~~~~
../include/linux/log2.h:176:19: note: expanded from macro 'roundup_pow_of_two'
(1UL << (ilog2((n) - 1) + 1)) \
^
../include/linux/log2.h:158:14: note: expanded from macro 'ilog2'
const_ilog2(n) : \
^
../include/linux/log2.h:85:4: note: expanded from macro 'const_ilog2'
(n) & (1ULL << 58) ? 58 : \
^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
../include/linux/kernel.h:824:38: note: expanded from macro '__careful_cmp'
__builtin_choose_expr(__safe_cmp(x, y), \
^
../include/linux/kernel.h:814:19: note: expanded from macro '__safe_cmp'
(__typecheck(x, y) && __no_side_effects(x, y))
^
../include/linux/kernel.h:800:40: note: expanded from macro '__typecheck'
(!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
^
../net/wireguard/ratelimiter.c:187:22: error: invalid operands to binary expression ('unsigned long (void)' and 'int')
(totalram_pages() << PAGE_SHIFT) /
~~~~~~~~~~~~~~~~ ^ ~~~~~~~~~~
../include/linux/log2.h:176:19: note: expanded from macro 'roundup_pow_of_two'
(1UL << (ilog2((n) - 1) + 1)) \
^
../include/linux/log2.h:158:14: note: expanded from macro 'ilog2'
const_ilog2(n) : \
^
../include/linux/log2.h:86:4: note: expanded from macro 'const_ilog2'
(n) & (1ULL << 57) ? 57 : \
^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
../include/linux/kernel.h:824:38: note: expanded from macro '__careful_cmp'
__builtin_choose_expr(__safe_cmp(x, y), \
^
../include/linux/kernel.h:814:19: note: expanded from macro '__safe_cmp'
(__typecheck(x, y) && __no_side_effects(x, y))
^
../include/linux/kernel.h:800:40: note: expanded from macro '__typecheck'
(!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
^
../net/wireguard/ratelimiter.c:187:22: error: invalid operands to binary expression ('unsigned long (void)' and 'int')
(totalram_pages() << PAGE_SHIFT) /
~~~~~~~~~~~~~~~~ ^ ~~~~~~~~~~
../include/linux/log2.h:176:19: note: expanded from macro 'roundup_pow_of_two'
(1UL << (ilog2((n) - 1) + 1)) \
^
../include/linux/log2.h:158:14: note: expanded from macro 'ilog2'
const_ilog2(n) : \
^
../include/linux/log2.h:87:4: note: expanded from macro 'const_ilog2'
(n) & (1ULL << 56) ? 56 : \
^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
../include/linux/kernel.h:824:38: note: expanded from macro '__careful_cmp'
__builtin_choose_expr(__safe_cmp(x, y), \
^
../include/linux/kernel.h:814:19: note: expanded from macro '__safe_cmp'
(__typecheck(x, y) && __no_side_effects(x, y))
^
../include/linux/kernel.h:800:40: note: expanded from macro '__typecheck'
(!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
^
../net/wireguard/ratelimiter.c:187:22: error: invalid operands to binary expression ('unsigned long (void)' and 'int')
(totalram_pages() << PAGE_SHIFT) /
~~~~~~~~~~~~~~~~ ^ ~~~~~~~~~~
../include/linux/log2.h:176:19: note: expanded from macro 'roundup_pow_of_two'
(1UL << (ilog2((n) - 1) + 1)) \
^
../include/linux/log2.h:158:14: note: expanded from macro 'ilog2'
const_ilog2(n) : \
^
../include/linux/log2.h:88:4: note: expanded from macro 'const_ilog2'
(n) & (1ULL << 55) ? 55 : \
^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
../include/linux/kernel.h:824:38: note: expanded from macro '__careful_cmp'
__builtin_choose_expr(__safe_cmp(x, y), \
^
../include/linux/kernel.h:814:19: note: expanded from macro '__safe_cmp'
(__typecheck(x, y) && __no_side_effects(x, y))
^
../include/linux/kernel.h:800:40: note: expanded from macro '__typecheck'
(!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
^
../net/wireguard/ratelimiter.c:187:22: error: invalid operands to binary expression ('unsigned long (void)' and 'int')
(totalram_pages() << PAGE_SHIFT) /
~~~~~~~~~~~~~~~~ ^ ~~~~~~~~~~
../include/linux/log2.h:176:19: note: expanded from macro 'roundup_pow_of_two'
(1UL << (ilog2((n) - 1) + 1)) \
^
../include/linux/log2.h:158:14: note: expanded from macro 'ilog2'
const_ilog2(n) : \
^
../include/linux/log2.h:89:4: note: expanded from macro 'const_ilog2'
(n) & (1ULL << 54) ? 54 : \
^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
../include/linux/kernel.h:824:38: note: expanded from macro '__careful_cmp'
__builtin_choose_expr(__safe_cmp(x, y), \
^
../include/linux/kernel.h:814:19: note: expanded from macro '__safe_cmp'
(__typecheck(x, y) && __no_side_effects(x, y))
^
../include/linux/kernel.h:800:40: note: expanded from macro '__typecheck'
(!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
^
../net/wireguard/ratelimiter.c:187:22: error: invalid operands to binary expression ('unsigned long (void)' and 'int')
(totalram_pages() << PAGE_SHIFT) /
~~~~~~~~~~~~~~~~ ^ ~~~~~~~~~~
../include/linux/log2.h:176:19: note: expanded from macro 'roundup_pow_of_two'
(1UL << (ilog2((n) - 1) + 1)) \
^
../include/linux/log2.h:158:14: note: expanded from macro 'ilog2'
const_ilog2(n) : \
^
../include/linux/log2.h:90:4: note: expanded from macro 'const_ilog2'
(n) & (1ULL << 53) ? 53 : \
^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
../include/linux/kernel.h:824:38: note: expanded from macro '__careful_cmp'
__builtin_choose_expr(__safe_cmp(x, y), \
^
../include/linux/kernel.h:814:19: note: expanded from macro '__safe_cmp'
(__typecheck(x, y) && __no_side_effects(x, y))
^
../include/linux/kernel.h:800:40: note: expanded from macro '__typecheck'
(!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
^
../net/wireguard/ratelimiter.c:187:22: error: invalid operands to binary expression ('unsigned long (void)' and 'int')
(totalram_pages() << PAGE_SHIFT) /
~~~~~~~~~~~~~~~~ ^ ~~~~~~~~~~
../include/linux/log2.h:176:19: note: expanded from macro 'roundup_pow_of_two'
(1UL << (ilog2((n) - 1) + 1)) \
^
../include/linux/log2.h:158:14: note: expanded from macro 'ilog2'
const_ilog2(n) : \
^
../include/linux/log2.h:91:4: note: expanded from macro 'const_ilog2'
(n) & (1ULL << 52) ? 52 : \
^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
../include/linux/kernel.h:824:38: note: expanded from macro '__careful_cmp'
__builtin_choose_expr(__safe_cmp(x, y), \
^
../include/linux/kernel.h:814:19: note: expanded from macro '__safe_cmp'
(__typecheck(x, y) && __no_side_effects(x, y))
^
../include/linux/kernel.h:800 CC net/ipv6/seg6.o
:40: note: expanded from macro '__typecheck'
(!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
^
../net/wireguard/ratelimiter.c:187:22: error: invalid operands to binary expression ('unsigned long (void)' and 'int')
(totalram_pages() << PAGE_SHIFT) /
~~~~~~~~~~~~~~~~ ^ ~~~~~~~~~~
../include/linux/log2.h:176:19: note: expanded from macro 'roundup_pow_of_two'
(1UL << (ilog2((n) - 1) + 1)) \
^
../include/linux/log2.h:158:14: note: expanded from macro 'ilog2'
const_ilog2(n) : \
^
../include/linux/log2.h:92:4: note: expanded from macro 'const_ilog2'
(n) & (1ULL << 51) ? 51 : \
^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
../include/linux/kernel.h:824:38: note: expanded from macro '__careful_cmp'
__builtin_choose_expr(__safe_cmp(x, y), \
^
../include/linux/kernel.h:814:19: note: expanded from macro '__safe_cmp'
(__typecheck(x, y) && __no_side_effects(x, y))
^
../include/linux/kernel.h:800:40: note: expanded from macro '__typecheck'
(!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
make[3]: *** [../scripts/Makefile.build:364: net/wireguard/ratelimiter.o] Error 1Eager for your help !
since wireguard is on gitignore and you´re fetching it during compilation on your own end, do delete the following lines like on the screenshot. that should resolve the error.
Hi, I did what you said and the problem is solved ! But I encountered another error :
Code:
../techpack/audio/asoc/msm-dai-q6-v2.c:27:10: fatal error: 'dsp/sp_params.h' file not found
#include <dsp/sp_params.h>
^~~~~~~~~~~~~~~~~
CC lib/sort.o
1 error generated.
make[4]: *** [../scripts/Makefile.build:364: techpack/audio/asoc/msm-dai-q6-v2.o] Error 1
make[3]: *** [../scripts/Makefile.build:678: techpack/audio/asoc] Error 2
make[2]: *** [../scripts/Makefile.build:678: techpack/audio] Error 2
make[1]: *** [/home/metatron/pixel4/kernel/FLORAL-master_T_floral_caf_27/Makefile:1222: techpack] Error 2Is it because of lacking dependency ?
btw I tried to re-clone the repository and built without modification , but still had the same wireguard error....So , gitignore isn't working properly I guess
? Or is it simply me being stupid...
Check out what gitignore does, then you´ll understand why you need to apply the changes again after cloning the repo from scratch.Hi, I did what you said and the problem is solved ! But I encountered another error :
I tried to google sp_params.h but couldn't find something helpful.Code:../techpack/audio/asoc/msm-dai-q6-v2.c:27:10: fatal error: 'dsp/sp_params.h' file not found #include <dsp/sp_params.h> ^~~~~~~~~~~~~~~~~ CC lib/sort.o 1 error generated. make[4]: *** [../scripts/Makefile.build:364: techpack/audio/asoc/msm-dai-q6-v2.o] Error 1 make[3]: *** [../scripts/Makefile.build:678: techpack/audio/asoc] Error 2 make[2]: *** [../scripts/Makefile.build:678: techpack/audio] Error 2 make[1]: *** [/home/metatron/pixel4/kernel/FLORAL-master_T_floral_caf_27/Makefile:1222: techpack] Error 2
Is it because of lacking dependency ?
btw I tried to re-clone the repository and built without modification , but still had the same wireguard error....So , gitignore isn't working properly I guess
Wireguard is on gitignore, because it´s fetching the wireguard drivers from another repo. That means you need to apply those changes after you cloned the source for the first time or once wireguard is updated.
Check: https://github.com/freak07/FLORAL/blob/master_T_floral_caf_27/scripts/fetch-latest-wireguard.sh
It seems that file was also on gitignore and therefore missing from my repo on github due to
FLORAL/.gitignore at master_T_floral_caf_27 · freak07/FLORAL
Kirisakura Kernel for the Pixel 4/XL. Contribute to freak07/FLORAL development by creating an account on GitHub.
github.com
You can check my repo again, I pushed the file and removed the gitignore line for techpack/audio
HUGE thanks for your patient guidance !
I just compiled the kernel successfully.
I just compiled the kernel successfully.
Hi,
I saw that the kernel code was updated to v4.14.305 on github.
Not requesting for ETA, just curious if we will get a new flashable zip (since the last one is v4.14.302) or should we build it ourselves this time.
Thanks for all your work!
I saw that the kernel code was updated to v4.14.305 on github.
Not requesting for ETA, just curious if we will get a new flashable zip (since the last one is v4.14.302) or should we build it ourselves this time.
Thanks for all your work!
I have an update ready, didn't find time and ultimately forgot to release it.
I'll try to get an update out the next few days
Thank you so much for the quick reply! I'll wait for it then.I have an update ready, didn't find time and ultimately forgot to release it.
I'll try to get an update out the next few days
Have a great day
Update 9.1.4
Hey guys and girls,
So here´s the next release. It includes the changes mentioned in the changelog below.
I wish everybody a great day.
Enjoy the device and the kernel, because I certainly do
Before troubleshooting and reporting any issues make sure to not use any additional mods, scripts or tweaks. This includes all mods and magisk modules, even the tiniest modification you did.
Detailed changelog below.
Please note that you need to use magisk 24.3 for custom roms. Magisk 25 is not compatible there.
Magisk 25210 canary has broken module loading and should be avoided until canary branch is updated.
Changelog:
- merge march security fixes and qpr updates from still supported p4a
- Linux-Stable 4.14.311
- other changes can be found on github
Magisk Module:
- After flashing the kernel, you will see a module called AK3 Helper Module in Magisk Manager. This will fine tune the power-hal. Do not delete it!
Have fun flashing and enjoy your device with latest linux-stable
Why is linux-stable beneficial?
I wish you all a nice day/evening!
Download is below
Download:
Attached to this post as AFH is not working correctly.
How to flash the Kernel:
1. Make sure you are rooted, are using the latest magisk suited for your OS version and a kernel manager capable of flashing a zip is installed. If available you'll can use TWRP as well. Download the kernel.zip to your device.
1a. If you used the SQLITE3 Magisk Module and the GPay Fix Magisk Module in the past (prior to 2.0.0) look at this post: click me
2. Flash kernel zip in via your favorite method. Kernel Managers and Recoveries need to be updated to work with a specific Android Version. It's your job to ensure compatibility! Root will be preserved! (Make sure to be on the latest firmware the kernel is made for)
3. Reboot and profit! Before reporting any issues make sure to read the first three posts of this thread!
Instructions can be found in the OP too!
Have fun, enjoy the kernel and your phone.
If you like my work please consider a donation.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea: http://paypal.me/freak07
Hey guys and girls,
So here´s the next release. It includes the changes mentioned in the changelog below.
I wish everybody a great day.
Enjoy the device and the kernel, because I certainly do
Before troubleshooting and reporting any issues make sure to not use any additional mods, scripts or tweaks. This includes all mods and magisk modules, even the tiniest modification you did.
Detailed changelog below.
Please note that you need to use magisk 24.3 for custom roms. Magisk 25 is not compatible there.
Magisk 25210 canary has broken module loading and should be avoided until canary branch is updated.
Changelog:
- merge march security fixes and qpr updates from still supported p4a
- Linux-Stable 4.14.311
- other changes can be found on github
Magisk Module:
- After flashing the kernel, you will see a module called AK3 Helper Module in Magisk Manager. This will fine tune the power-hal. Do not delete it!
Have fun flashing and enjoy your device with latest linux-stable
Why is linux-stable beneficial?
I wish you all a nice day/evening!
Download is below
Download:
Attached to this post as AFH is not working correctly.
How to flash the Kernel:
1. Make sure you are rooted, are using the latest magisk suited for your OS version and a kernel manager capable of flashing a zip is installed. If available you'll can use TWRP as well. Download the kernel.zip to your device.
1a. If you used the SQLITE3 Magisk Module and the GPay Fix Magisk Module in the past (prior to 2.0.0) look at this post: click me
2. Flash kernel zip in via your favorite method. Kernel Managers and Recoveries need to be updated to work with a specific Android Version. It's your job to ensure compatibility!
Root will be preserved! (Make sure to be on the latest firmware the kernel is made for)3. Reboot and profit! Before reporting any issues make sure to read the first three posts of this thread!
Instructions can be found in the OP too!
Have fun, enjoy the kernel and your phone.
If you like my work please consider a donation.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea: http://paypal.me/freak07
@Freak07
"Please note that you need to use magisk 24.3 for custom roms. Magisk 25 is not compatible there.
Magisk 25210 canary has broken module loading and should be avoided until canary branch is updated."
I think the bug is not on Magisk. Because of some custom ROM as TequilaOS, and evolution-x, this kernel works perfectly with the magisk 25.
"Please note that you need to use magisk 24.3 for custom roms. Magisk 25 is not compatible there.
Magisk 25210 canary has broken module loading and should be avoided until canary branch is updated."
I think the bug is not on Magisk. Because of some custom ROM as TequilaOS, and evolution-x, this kernel works perfectly with the magisk 25.
Hello again
simple question is, does this kernel support OverlayFS? since am about to install another magisk module related to adreno driver which mostly requires OverlayFS to work
thanks
------------
edited: answered here and proven by self
simple question is, does this kernel support OverlayFS? since am about to install another magisk module related to adreno driver which mostly requires OverlayFS to work
thanks
------------
edited: answered here and proven by self
Attachments
Last edited:
Hi ! I tried to compile the kernel myself and encountered this error:
Would you please help me with that? I am willing to provide ANY information you need to diagnose the problems!
Code:
arch/arm64/boot/dts/google/qcom-base/sm8150-v2.dtb: Warning (reg_format): "reg" property in /soc/qcom,glink/adsp/qcom,gpr has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
arch/arm64/boot/dts/google/qcom-base/sm8150-v2.dtb: Warning (reg_format): "reg" property in /soc/qcom,glink/adsp/qcom,gpr/gecko_core has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
arch/arm64/boot/dts/google/qcom-base/sm8150-v2.dtb: Warning (reg_format): "reg" property in /soc/qcom,glink/adsp/qcom,gpr/audio-pkt has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
arch/arm64/boot/dts/google/qcom-base/sm8150-v2.dtb: Warning (reg_format): "reg" property in /soc/qcom,glink/adsp/qcom,gpr/q6prm has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
arch/arm64/boot/dts/google/qcom-base/sm8150-v2.dtb: Warning (avoid_default_addr_size): Relying on default #address-cells value for /soc/qcom,glink/adsp/qcom,gpr
arch/arm64/boot/dts/google/qcom-base/sm8150-v2.dtb: Warning (avoid_default_addr_size): Relying on default #size-cells value for /soc/qcom,glink/adsp/qcom,gpr
arch/arm64/boot/dts/google/qcom-base/sm8150-v2.dtb: Warning (avoid_default_addr_size): Relying on default #address-cells value for /soc/qcom,glink/adsp/qcom,gpr/gecko_core
arch/arm64/boot/dts/google/qcom-base/sm8150-v2.dtb: Warning (avoid_default_addr_size): Relying on default #size-cells value for /soc/qcom,glink/adsp/qcom,gpr/gecko_core
arch/arm64/boot/dts/google/qcom-base/sm8150-v2.dtb: Warning (avoid_default_addr_size): Relying on default #address-cells value for /soc/qcom,glink/adsp/qcom,gpr/audio-pkt
arch/arm64/boot/dts/google/qcom-base/sm8150-v2.dtb: Warning (avoid_default_addr_size): Relying on default #size-cells value for /soc/qcom,glink/adsp/qcom,gpr/audio-pkt
arch/arm64/boot/dts/google/qcom-base/sm8150-v2.dtb: Warning (avoid_default_addr_size): Relying on default #address-cells value for /soc/qcom,glink/adsp/qcom,gpr/q6prm
arch/arm64/boot/dts/google/qcom-base/sm8150-v2.dtb: Warning (avoid_default_addr_size): Relying on default #size-cells value for /soc/qcom,glink/adsp/qcom,gpr/q6prm
CC drivers/net/ppp/pppox.o
DTC arch/arm64/boot/dts/google/qcom-base/sm8150.dtb
AR net/ipv4/netfilter/nf_conntrack_ipv4.o
AR net/ipv4/netfilter/nf_nat_ipv4.o
CC drivers/media/platform/msm/vidc/msm_vidc.o
AR net/ipv4/netfilter/built-in.o
CC drivers/gpu/drm/msm/sde/sde_hw_cdm.o
CC net/ipv4/tcp_diag.o
arch/arm64/boot/dts/google/qcom-base/sm8150.dtb: Warning (reg_format): "reg" property in /soc/qcom,glink/adsp/qcom,gpr has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
arch/arm64/boot/dts/google/qcom-base/sm8150.dtb: Warning (reg_format): "reg" property in /soc/qcom,glink/adsp/qcom,gpr/gecko_core has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
arch/arm64/boot/dts/google/qcom-base/sm8150.dtb: Warning (reg_format): "reg" property in /soc/qcom,glink/adsp/qcom,gpr/audio-pkt has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
arch/arm64/boot/dts/google/qcom-base/sm8150.dtb: Warning (reg_format): "reg" property in /soc/qcom,glink/adsp/qcom,gpr/q6prm has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
arch/arm64/boot/dts/google/qcom-base/sm8150.dtb: Warning (avoid_default_addr_size): Relying on default #address-cells value for /soc/qcom,glink/adsp/qcom,gpr
arch/arm64/boot/dts/google/qcom-base/sm8150.dtb: Warning (avoid_default_addr_size): Relying on default #size-cells value for /soc/qcom,glink/adsp/qcom,gpr
arch/arm64/boot/dts/google/qcom-base/sm8150.dtb: Warning (avoid_default_addr_size): Relying on default #address-cells value for /soc/qcom,glink/adsp/qcom,gpr/gecko_core
arch/arm64/boot/dts/google/qcom-base/sm8150.dtb: Warning (avoid_default_addr_size): Relying on default #size-cells value for /soc/qcom,glink/adsp/qcom,gpr/gecko_core
arch/arm64/boot/dts/google/qcom-base/sm8150.dtb: Warning (avoid_default_addr_size): Relying on default #address-cells value for /soc/qcom,glink/adsp/qcom,gpr/audio-pkt
arch/arm64/boot/dts/google/qcom-base/sm8150.dtb: Warning (avoid_default_addr_size): Relying on default #size-cells value for /soc/qcom,glink/adsp/qcom,gpr/audio-pkt
arch/arm64/boot/dts/google/qcom-base/sm8150.dtb: Warning (avoid_default_addr_size): Relying on default #address-cells value for /soc/qcom,glink/adsp/qcom,gpr/q6prm
arch/arm64/boot/dts/google/qcom-base/sm8150.dtb: Warning (avoid_default_addr_size): Relying on default #size-cells value for /soc/qcom,glink/adsp/qcom,gpr/q6prm
CC net/ipv4/udp_diag.o
CC drivers/misc/qseecom.o
CC drivers/net/slip/slhc.o
CC drivers/pci/pci-sysfs.o
CC drivers/pci/rom.o
CC drivers/gpu/drm/msm/sde/sde_hw_dspp.o
DTC arch/arm64/boot/dts/google/sm8150-coral-dvt-overlay.dtbo
CC drivers/gpu/drm/msm/sde/sde_hw_intf.o
CC net/ipv4/tcp_bbr.o
Error: ../arch/arm64/boot/dts/google/../qcom/pm8150.dtsi:21.1-10 syntax error
FATAL ERROR: Unable to parse input tree
make[3]: *** [scripts/Makefile.dtbo:24: arch/arm64/boot/dts/google/sm8150-coral-dvt-overlay.dtbo] Error 1
make[3]: *** Waiting for unfinished jobs....
CC drivers/perf/arm_pmu.o
CC drivers/net/ppp/pppoe.o
make[2]: *** [../scripts/Makefile.build:678: arch/arm64/boot/dts/google] Error 2
make[1]: *** [arch/arm64/Makefile:244: dtbs] Error 2
make[1]: *** Waiting for unfinished jobs....Would you please help me with that? I am willing to provide ANY information you need to diagnose the problems!
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
6Update 9.1.6
Hey guys and girls,
So here´s the next release. It includes the changes mentioned in the changelog below.
Most interesting change is improvement in camera launch time.
I wish everybody a great day.
Enjoy the device and the kernel, because I certainly do
Before troubleshooting and reporting any issues make sure to not use any additional mods, scripts or tweaks. This includes all mods and magisk modules, even the tiniest modification you did.
Detailed changelog below.
Please note that you need to use magisk 24.3 for custom roms if you want to be sure the device boots!
Magisk 25 or 26 is not compatible on all custom ROMs. This is not related to the kernel or magisk, it´s how AVB is handled by the custom ROMs. Some work and some don´t.
The kernel is primarily made for the stock firmware.
If someone here wants to step up to fix this issue, feel free to do so. Everything about my kernel is open source.
Changelog:
- merge march security fixes and qpr updates from still supported p4a up to latest QPR beta firmware
- Linux-Stable 4.14.315
- improve camera launch time
- other changes can be found on github
Magisk Module:
- After flashing the kernel, you will see a module called AK3 Helper Module in Magisk Manager. This will fine tune the power-hal. Do not delete it!
Have fun flashing and enjoy your device with latest linux-stable
Why is linux-stable beneficial?
I wish you all a nice day/evening!
Download is below
Download:
Attached to this post as AFH is not working correctly.
How to flash the Kernel:
1. Make sure you are rooted, are using the latest magisk suited for your OS version and a kernel manager capable of flashing a zip is installed. If available you'll can use TWRP as well. Download the kernel.zip to your device.
1a. If you used the SQLITE3 Magisk Module and the GPay Fix Magisk Module in the past (prior to 2.0.0) look at this post: click me
2. Flash kernel zip in via your favorite method. Kernel Managers and Recoveries need to be updated to work with a specific Android Version. It's your job to ensure compatibility! Root will be preserved! (Make sure to be on the latest firmware the kernel is made for)
3. Reboot and profit! Before reporting any issues make sure to read the first three posts of this thread!
Instructions can be found in the OP too!
Have fun, enjoy the kernel and your phone.
If you like my work please consider a donation.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea: http://paypal.me/freak07 -
85Kirisakura-Kernel for the Pixel 4 and Pixel 4 XL
Hello everyone,
After rising to the most popular kernel on the Pixel 3/XL forums, here is Kirisakura-Kernel for the Pixel 4 (FLAME) and Pixel 4 XL (CORAL), together FLORAL.
Kirisakura - Kernel is designed to bring a handful of beneficial features to the device, while ensuring excellent performance and smoothness to get you safely through the day!
The kernel aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security, stability and performance!
This includes Linux-Stable, CAF-Upstream, F2FS-Mainline and kernel/common.
If that got you curious,have a read about linux-stable and why it is important here. The stable-process is not the same for every subsystem, but the general idea, rule of thumb and benefits are applicable for other subsystems as well.
Main Features:
- Based on latest kernel sources from Google, Kernel is made for Android 13
- Linux-Stable-Upstream included to latest 4.14.315
- CAF-Upstream usually based on one of the latest tags for sm8150
- include all important fixes/improvements from kernel/common
- compiled with latest Clang 16.0.2 from Google prebuilts and built with -O3 optimizations
- F2FS implementation updated to latest state of kernel/common and kernel.org maintained by Jaegeuk Kim.
- devfreq backports from 5.4 (sd 888 qcom kernel base)
- Safety Net patches are included -> Kernel passes Safety Net (hardware attestation is not related to these kernel patches)
- Flashing the kernel will keep root!
- Tested to work on custom ROMs
- Flashable via EXKM and FKM on a rooted system!
- remove extensive Memory Management logging from Google
- removed nolog usage, remove rtb logging from the kernel
- remove selinux auditing from kernel for lower overhead
- remove IPC logging from the kernel
- introduce kmalloc reclaimable caches for improved memory management
- AnyKernel3 powered by @osm0sis (big thanks!)
EAS related features:
- CleanSlate options to dynamically control freq boosting and sched boosting of powerhal
- small improvements to tasks placement
- fixes from kernel/common to EAS
- improvements from Pixel 5
CPU related features:
- Power saving workingqueues enabled by default (toggleable in EXKM)
have a read here: https://lwn.net/Articles/731052/
this complements EAS in general
- Change various drivers (WLAN, MM, audio, charger, power, thermal, glink etc) to user power efficient workingqueues. This should work well in conjunction with EAS
- include cpuidle patches from CAF
- s2idle-flow improvements from mainline
- improve efficiency while music playback
- arm64: lse: Prefetch operands to speed up atomic operations
- improve camera launch time
File System related features:
- Include latest f2fs changes found on f2fs stable git
- Include rapid GC by @arter97 ( best thing is to read the commit description linked here. I compared GC on stock google f2fs, upstreamed f2fs and f2fs with rapid GC. Rapid GC is the most effective, followed by upstreamed f2fs.)
GPU related features:
- KCAL to control various RGB related display configs (RGB, Hue, Saturation etc -> accessible via CleanSlate Config App)
- add ability to reduce minimum brightness
- add high-brightness-mode (HBM)
- Update GPU driver to latest CAF state
- improve GPU performance (overall smoother experience)
- reduce power consumption when rendering static images
- enable of usage of SD855+ GPU frequencies as optional feature
UI/UX/Usability related features from CleanSlate:
- CleanSlate features made by @tbalden
- Adjust all CleanSlate features with the CleanSlate-Apps found in the CleanSlate-Thread (if you profit from the CleanSlate features make sure to buy the premium versions on Play-Store to support
@tbalden
- CleanSlate options that require permissive selinux in any way are not included, as they can be easily achieved otherwise on a rooted environment and this kernel is not intended to be used rootless (adblocking, props spoofing etc.)
- Flashlight Notification/Call blinking
- Vibrating Notification Reminder
- Sweep to Sleep touchscreen gesture - highly customizable
- DoubleTap on Sweep2Sleep's area gestures - new way to pull down android Notification Area
- Face down screen off - new gesture, e.g. conveniently use together with 'flip to shh' to turn screen off
Network related features:
- Wireguard Support (Details)
Memory related features:
- updated PSI monitor with latest changes
- improved mm with patches from latest mainline
- various other changes from mainline
- included zstd and lz0-rle as options for ZRAM-algorithm (lz4 is probably the best all around, so only change it if you know why and what you are doing)
- allow swappiness up to a value of 200
- Backport to enable CONFIG_HAVE_MOVE_PMD (see here)
- Backport to enable CONFIG_HAVE_MOVE_PUD (see here) (reverted for now as it breaks audio driver)
- improvements to ZRAM writeback (thanks @arter97 )
- disable per cgroup tracking via psi to reduce overhead
Security related features:
- CFI and LTO both kept intact and are used to keep additional security Google implemented for us!
- ThinLTO used as of 3.9.0
- Shadow Call Stack
Tuned PowerHal
- allow kernel to idle on lowest frequencies when no interaction is happening
- increase swappiness during periods without interaction to favor swapping memory, relax swappiness otherwise
- scheduler camera processes to the big cluster and prime core when faceunlock is used
- adjust powerhal behaviour when the camera is used
Misc Features:
TCP Congestion Algorithms:
- advanced algorithms enabled
- includes new bbr2
Wakelock Blocker:
- advanced wakelock blocker with the ability to block any wakelocks (dangerous, use with caution)
- please read [URL="https://arstechnica.com/gadgets/2018/08/p-is-for-power-how-google-tests-tracks-and-improves-android-battery-life/"]this for further info
Other features:
- disable logging to make the kernel more lightweight in various places (includes mm, vma, gpu, ipa etc)
- remove VLAs from the kernel (more info)
- add support for steam controller
- add support for nintendo switch controller
- merge upstream solution for PM/Wakeup driver, which reduces unnecessary logspam and also improves sleeping behaviour
- merge freezer v2 backport from google gerrit (required for developer option ""suspend execution for cached apps"")
Feature section for the "non visible" but perceptible improvements:
- updated binder section (responsible for interprocess communication)
- updated sdcardfs ; have a read about it here:
Requirements
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- working magisk environment
- latest stock rom (custom roms can have issue, several users reported success when rooted with magisk 24.3 instead of latest)
How to flash the Kernel:
1. Download the kernel.zip to your device
1a. While it may not be necessary all times when coming from another custom kernel: You may want to restore stock boot.img as well as stock dtbo.img, which can both be found in the factory image. If you´re on a custom rom, simply dirty flash your ROM. Reroot with magisk and optionally install twrp.zip (if existing). Before reporting issues make sure you do that! Thank you!
1b. If you used the SQLITE3 Magisk Module and the GPay Fix Magisk Module in the past look at this post: click me
You only need to do either 2a OR 2b
2a. If TWRP is available for this device and specific android version, boot to TWRP and flash my kernel.zip. Root will be preserved!
or
2b. Flash kernel zip in EX Kernel Manager or FKM app. Root will be preserved! If a kernel manager is not yet updated to work on a specific Android Version, you need to wait until it is updated or use another one.
4. Reboot and profit!
DOWNLOAD:
Download is located always in this folder or attached to the release post in case it´s now in AFH.
https://www.androidfilehost.com/?w=files&flid=301179
Please also check the release posts for download links or attched files. AFH is often down recently.
Important: Read after Download
Please take a look at the second post after flashing the kernel!
Changelog:
Android 10/ Q Kernels
1.0.0 Initial Release
1.0.1 https://forum.xda-developers.com/showpost.php?p=80712545&postcount=51
1.0.3 https://forum.xda-developers.com/showpost.php?p=80791393&postcount=181
2.0.0 https://forum.xda-developers.com/showpost.php?p=81069625&postcount=341
2.1.0 https://forum.xda-developers.com/showpost.php?p=81168297&postcount=424
2.3.0 https://forum.xda-developers.com/showpost.php?p=81244627&postcount=491
2.3.4 https://forum.xda-developers.com/showpost.php?p=81311861&postcount=561
2.6.0 https://forum.xda-developers.com/showpost.php?p=81408591&postcount=611
2.9.0 https://forum.xda-developers.com/showpost.php?p=81527369&postcount=692
2.9.2 https://forum.xda-developers.com/showpost.php?p=81575075&postcount=702
3.1.0 https://forum.xda-developers.com/showpost.php?p=81625099&postcount=725
3.2.0 https://forum.xda-developers.com/showpost.php?p=81679343&postcount=761
3.9.0 https://forum.xda-developers.com/showpost.php?p=81926617&postcount=802
3.9.1 https://forum.xda-developers.com/showpost.php?p=81943269&postcount=824
4.2.0 https://forum.xda-developers.com/showpost.php?p=82189985&postcount=851
4.5.0 https://forum.xda-developers.com/showpost.php?p=82485339&postcount=892
4.5.6 https://forum.xda-developers.com/showpost.php?p=82562029&postcount=941
4.7.5 https://forum.xda-developers.com/showpost.php?p=82725499&postcount=986
5.0.0 https://forum.xda-developers.com/showpost.php?p=83019609&postcount=1022
5.2.2 https://forum.xda-developers.com/showpost.php?p=83206123&postcount=1066
5.2.6 https://forum.xda-developers.com/showpost.php?p=83387505&postcount=1078
Android 11/ R Kernels
6.0.0 https://forum.xda-developers.com/showpost.php?p=83476821&postcount=1092
6.1.3 https://forum.xda-developers.com/showpost.php?p=83649491&postcount=1131
6.2.4 https://forum.xda-developers.com/showpost.php?p=83849179&postcount=1143
6.6.0 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-84068177
6.6.6 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-84227741
6.8.2 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-84408147
7.1.0 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-84588667
7.1.1 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-84603881
7.2.3 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-84747379
7.4.0 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-84900715
7.4.1 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-84951399
7.4.2 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-85000553
7.4.3 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-85079523
7.4.4 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-85155405
7.9.0 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-85298631
7.9.1 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-85424575
7.9.2 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-85473277
7.9.3 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-85674963
Android 12
8.0.0 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-86063673
8.0.3 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-86236075
8.0.4 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-86413329
8.0.5 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-86550055
8.2.0 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-86843221
8.2.2 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-87006201
Android 13
9.0.0 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-87295655
9.0.2 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-87532941
9.1.0 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-87760941
9.1.1 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-87868847
9.1.4 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-88332237
9.1.6 https://forum.xda-developers.com/t/...r-pixel-4-xl-aka-floral.3992213/post-88583047
Donations:
Donations are not mandatory but very welcome if you want to support development or just buy me a coffee
If you like my work: http://paypal.me/freak07
Credits:
@osm0sis for all his work, including the ak3 installer!
@tbalden for being the best HTC wingman!
@LeeDroid for his awesome roms!
@Captain_Throwback for all the mentoring and guidance!
@Eliminater74 for bringing me into the game and the Inspiration
@nathanchance for his upstream guidance and assistance
@RenderBroken for all of his work and the stuff I could learn from him
@flar2 for all his work
@joshuous for all the help he provided to me in the past!
@topjohnwu for magisk!
@arter97 , @kdrag0n for helping me out several times!
XDA:DevDB Information
Kirisakura Kernel, Kernel for the Google Pixel 4 XL
Contributors
Freak07
Source Code: https://github.com/freak07/FLORAL
Kernel Special Features:
Version Information
Status: Stable
Created 2019-10-27
Last Updated 2020-11-0359Update to 2.0.0
Hey guys and girls,
So here´s the update finally. I worked on this kernel in parallel to the initial release I uploaded on XDA, since I started developing for the Pixel 4 XL. Because ultimately the 2.0.0 release is built upon the kernel base I wanted initially, but wasn´t able to create.
This will be a longer post, but have a bit patience and tenacity when reading this post it might be worth it.
A little context so everybody can follow a bit more easily:
Starting with the Pixel 3/XL, the pixel kernels are more close to "CAF" than on previous Google phones. CAF stands for codeaurora-forums, where the development from Qualcomm for our SOC, the SD855, happens.
Usually OEMs get a snapshot of a CAF-Base from Qualcomm, stop updating it, implement own device or company specific drivers/necessary changes and only add minimal changes to the kernel as soon as it is deemed stable.
The CAF-Developers however constantly push updates to their CAF-Base on their git. It´s a lot of work to completely merge all CAF updates into the kernel, but since there are a lot of device and soc specific fixes and improvements it´s very worth it.
Google used a very early snapshot of the CAF-source to base their Pixel 4/XL kernel upon.
So one of my initial goals was to merge a more recent CAF-Base. This proved to be very difficult however. It ended up in so many failed attempts with a non successfully booting phone that I lost count of it and was on the verge of giving up a few times.
I worked on it for weeks, excluding more and more changes, piece by piece, until I finally got the phone to a state, where I was able to pull a log and work in a specific direction.
After that it was just a lot of time, that went into merging and doing tedious work. I took a peek into many corners of the kernel, while fixing all the conflicts and understanding some of the fixes google applied, which were also fixed by CAF at a later stage.
So I tried to always pick the best solution for the problems Google and CAF faced. Sometimes I reverted a fix from Google, sometimes I reverted a fix from Qualcomm and rather picked the Google one.
I understand the kernel a lot better and learned a lot in the last weeks.
The main difficulties I had to fight with, were the fact that Google is the only OEM that uses LTO in conjunction with CFI and ShadowCallStack for increased security. This requires some low-level changes to arm64/kernel, which conflicts with some more recent changes from CAF. These changes were identified and reverted.
The Pixel 3 and Pixel 4 phones are also the only phones, which make use of the Userspace-Low Memory Killer (ULMK) instead of relying on the kernel side low memory killer. Google put a lot of work and thought into this after the Pixel 3 was released. Very exciting work started on the dev previews of Android 10 on the Pixel 3, regarding the ULMK. I tried these changes on a personal Pixel 3 Rom and was in contact with the google dev responsible for it. I like the approach and thought process behind it. Since CAF is still on the kernel space low memory killer, there were more conflicts, which needed to be identified.
Some of these commits were really inconspicuous. That´s the main reason this took a lot of time.
One more point I´d like to describe:
CAF maintains various tags, which can be merged. There´s a regular CAF-Tag for the sd855, where most OEMs base their kernel upon. It´s also very similar to the CAF-Snapshot google received from Qualcomm, just the OEM version instead of the open-source version.
F2FS state is pretty old on this CAF-base (Google did upstream this to a pretty recent state, because the official f2fs-maintainer/developer is employed by google) , as well as other subsystems. Linux-stable upstream is at 4.14.117.
For comparison the Pixel 4 XL stock kernel is still at 4.14.111. Another symptom of the rather not recent CAF-Base Google built the kernel upon.
Now lets get to the sweet stuff
Then there´s a more advanced CAF-Tag/Branch maintained by CAF for the sd855.
Most of the soc specific and other related drivers have way more recent CAF-Upstream patches. F2FS is on the same level as the Pixel 4. Linux-stable upstream is at 4.14.146. Just to give you an idea.
A short summary of how the new base works in comparison to the 1.x.x releases:
1.x.x: Googles Code + necessary changes to compile as a standalone kernel + linux-stable upstream from kernel.org to 4.14.15x + upstreaming of various subsystems + kernel features
2.0.0: Googles Code + necessary changes to compile as a standalone kernel + nextgen CAF base (includes linux-stable to 4.14.146) + regular CAF base for the sd855+ missing linux-stable upstream (up to 4.14.156) + upstreaming of various subsystems + kernel features
Example 1:
As you can see merging that nextgen CAF base brings more than one advantage. It´s tested code from Qualcomm/CAF which includes upstream updates for various subsystems and also linux-stable updates. That means less rooms for errors introduced by me merging thousands of lines of code.
We have linux-stable upstream up to 4.14.146 tested by Qualcomm on the SD855 in the new kernel base. On the initial 1.0.x kernel I merged linux-stable myself all the way from 4.14.111 to 4.14.15x.
That´s just one example but I think it serves as a good way to understand my motivation better.
Even though one can´t see the updated SOC-specific drivers, the kernel runs way better than the 1.0.x release.
Updates include drivers as GPU, CPU, Modem, Bluetooth, basically nearly all drivers.
For example my bluetooth range when connected to my earstudio has significantly increased due to some CAF-Updates!
Example 2:
Just so you all can see how far away we are from the stock kernel now we take a look at the amount of code changes:
Merging the next-gen CAF-tag: 3,171 changed files with 241,690 additions and 23,565 deletions.
Merging the regular SD855 tag on top: 223 changed files with 5,754 additions and 1,852 deletions.
Not all of these changes end up in drivers we actually use, but it´s still a good indicator.
There were many other changes done to the kernel as well. I try to list them in the changelog!
Regarding the freezes some people faced straight after rebooting:
The only issue I could reproduce myself and solve with the help of a tester that was affected by the freezes too, where caused by F2FS-Upstream not working well with the SQlite3 module and the Gpay Fix Module.
So for now I have excluded F2FS-Upstream from my kernel. Judging from my experience with the Pixel 3 XL Google will soon merge these changes by themselves and then even the stock kernel will exhibit this behaviour.
I can´t see anything wrong with the F2FS-Upstream kernel patches so a solution will have to be found anyway when Google merges these changes into the stock kernel.
If you have used the SQLite3 Module and the GPay Fix Module in the past, please follow step 1a from my instructions.
Screen freezes when using HBM in conjunction with AOD and Android Auto are resolved too.
Please keep in mind. I only looked at the issue with the GPay Fix Module, because I saw some courage from @ilal2ielli providing logs and trying to actively help me.
No magisk modules, scripts, tweaks, modifications, xposed, sound mods or similar are officially supported!
If you face issues, try to reproduce them without any modifications done to the system at all. Then provide logs and steps to reproduce (instructions in post #2). This way I can look into it.
Sometimes a clean flash after using to many mods like xposed, even if installed systemlessly gets rid of all perceived issues!
Posts like: "I have issues please fix will be simply ignored. "
Magisk Module fixing the stock powerhal behaviour:
The power hal of the pixel 4 is partially controlled by a config file. On stock the setup of the power-hal causes the kernel to not idle at 576mhz on the little cluster after some random length of uptime, depending on usage and setup.
This module fixes this behaviour. It´s not critically needed, but may increase battery life a tiny bit.
On stock this config file sets up the power hal to boost top-app schedtune boost to 30 upon interaction and after the boost duration is finished, back to a value of 10.
There are different groups for tasks. top-app tasks are ui-critical tasks, rt-tasks, all that are critical for a smooth experience of the phone.
Setting top-app schedtune boost to 30 causes the follwoing: The scheduler will expect tasks of the top-app group to use 30% more CPU time than they (probably) actually will, and the CPU-frequency governor will speed up the processor accordingly. "Boosting" a process in this way, thus, does not affect its scheduling priority, but it will affect the speed of the CPU on which it ends up running.
The problem is resetting the value back to 10, when no interaction is happening. This seems to cause the little cluster to idle at 1036mhz after the phone is up and running a few hours on 4.14 kernels.
With my module the value gets reset back to 0 instead of 10, when the phone is not being interacted with
As you can see this is not kernel related, but a userspace thing, that just influences how the kernel handles load. So it can´t be fixed in the kernel, it needs to be fixed in userspace.
That´s why I created this magisk module. It can be used on the stock kernel and other kernels as well!
This kernel was more than a month work and I spent countless hours during my free time (and the nights) to get it to this state! Especially preparing the CAF-Base I merged, understanding all changes and consequences which happen by merging it!
I´m glad it worked out and a bit proud it can finally be released!
So please enjoy it hopefully as much as I am I´m going to enjoy the rest of my sunday now!
The kernel was tested for a week without a single issue reported by my testers
A huge thanks to them at this place!
@wrongway213
@Mrcactuseater
@MArtyChubbs
@ilal2ielli
@toastyp
Detailed changelog below.
Enjoy!
Changelog:
Kernel Base
- Completely new kernel base based upon latest Google source
- Next-Gen CAF-Tag LV.AU.0.0.1-02420-qtiquingvm.0 merged
- Regular CAF-Tag for SD855 merged LA.UM.8.1.r1-12200-sm8150.0
- linux-stable upstream to latest 4.14.156
- included patches from kernel/common
- removed F2FS upstream due to conflicts with SQLite operations introduced by SQLite3 Magisk Module and GPay fix magisk module
- remove extensive Memory Management logging from Google
- removed nolog usage, remove rtb logging from the kernel
- remove selinux auditing from kernel for lower overhead
- remove IPC logging from the kernel
- introduce kmalloc reclaimable caches for improved memory management
Features:
- all previous features kept intact
- reduce power consumption when rendering static images
- add support for steam controller
- introduce bbr2 tcp congestion control algorithm
- improve bbr congestion control algorithm
Further Kernel Changes:
- make bluetooth driver more lightweight
- remove IPC logging from several drivers
- improve memory allocations (thanks @arter97 @Sultanxda)
- remove VLA usage (thanks @arter97)
-
Other changes:
- look at github
Magisk Module:
- Add Module to fix config for power hal
Have fun flashing and enjoy your device with latest linux-stable
Why is linux-stable important?
I wish you all a nice day/evening!
Download is below
Download:
Kernel: https://www.androidfilehost.com/?fid=4349826312261650873
Magisk Module: https://www.androidfilehost.com/?fid=4349826312261650875
How to flash the Kernel:
1. Make sure you are rooted and either EXKM or FKM is installed. Download the kernel.zip to your device.
1a. If you used the SQLITE3 Magisk Module and the GPay Fix Magisk Module in the past look at this post: click me
2. Optionally: Flash the magisk module provided in the release post!
3. Flash kernel zip in EXKM or FKM app. Root will be preserved!
4. Reboot and profit! Before reporting any issues make sure to read the first three posts of this thread!
Instructions can be found in the OP too!
Have fun, enjoy the kernel and your phone.
If you like my work please consider a donation.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea: http://paypal.me/freak0742Progress Report/Small Teaser
Hey everybody,
Testing of the new kernel I mentioned some time ago seems very very promising.
I really hope I find some time this weekend to get the release ready.
I started more than 3 times from scratch until everything worked out as I intended it to. That´s the reason, why there were no updates for over two weeks here now.
It´s a completely new kernel base from CAF (basically from their Next-Gen branch) and essentially the kernel like I wanted it from the beginning but wasn´t able to build so it boots up.
I will give a detailed description of everything done in the release post. That will be a long post.
The wait will be worth it so stay tuned.
The new kernel should have the freezing on bootup issue fixed, when any sort of GPay fix is used. I will give short instructions once the kernel is released, to make sure you can start clean there.
A big thanks to @ilal2ielli for debugging this issue with me, patiently providing logs all the time and keeping up with all the test builds I sent to him.
The display issues related to Android Auto when used in conjunction with HBM will also be fixed in the new kernel. Thanks to @toastyp for taking the time, providing me logs and giving feedbacks on test builds I sent him over the last weeks.
I wish everybody a nice day41Update to 4.7.5
Hey guys and girls,
I try to be quite fast with the monthly security updates indeed. Google always publishes the source code, when I´m going to sleep, so depending on your timezone you might have to wait a few hours or a day longer.
Keep in mind, I´m just a human being so if it takes a little bit longer, it´s probably because there´s something else keeping me busy.
With that said here´s the security update for June. We already had most of the changes from merging CAF, Linux-Upstream and other things.
Upstream linux-stable is merged to 4.14.182 as well as CAF-Upstream and mainline f2fs-updates
All recently developed CleanSlate options can be easily accessed via the CleanSlate apps on this kernel as well! Please make sure to buy the premium versions if you profit from these features and want to give a little bit back to @tbalden ! Or just drop him a small donation!
This includes the option to reduce the freq boosting from the stock powerhal and EAS scheduler boosting with adjustable levels. This is a very handy way to safe power on the fly without using the stock powersaver profile.
All option to use different gamma settings to reduce the green tint can be found as well! This includes a few different choices as well.
Please take look at the latest release posts from @tbalden ! These include more detailed explanations!
https://forum.xda-developers.com/showpost.php?p=82660965&postcount=219
https://forum.xda-developers.com/showpost.php?p=82688341&postcount=228
https://forum.xda-developers.com/showpost.php?p=82696759&postcount=233
https://forum.xda-developers.com/showpost.php?p=82725109&postcount=255
Before troubleshooting and reporting any issues make sure to not use any additional mods, scripts or tweaks. This includes all mods, even the tiniest modification you did.
Once you know things are working add them back one by one to make sure everything works.
More details in the changelog!
I wish everybody a great weekend
big thanks to all my testers again:
@Mrcactuseater
@MArtyChubbs @ilal2ielli
@toastyp @Alcolawl
Detailed changelog below.
Enjoy!
Changelog:
Kernel Base
- Merge June Security Update
- Linux-Stable-Upstream to 4.14.182
- Merge latest CAF-Tag for the SD855 as usual
- patches from kernel/common
- updates to f2fs to be inline with f2fs-stable
- update WiFi driver with upstream CAF to remove some logging
Features:
- add all recently developed CleanSlate features! They are all accessible via cleanslate apps, which can be found on the CleanSlate thread! Please make sure to buy the premium versions if you profit from these features and want to give a little bit back to @tbalden !
- option to reduce frequency boosting
- option to reduce EAS Scheduler related boosting
- option to reduce green tint by using different gamma tables (please refer to the release posts I linked above)
Other changes:
- see github
Magisk Module:
- Now included in the kernel.zip (will appear as AK3-Helper Module in Magisk Manager)
Have fun flashing and enjoy your device with latest linux-stable
Why is linux-stable important?
I wish you all a nice day/evening!
Download is below
Download:
Kernel: https://www.androidfilehost.com/?fid=4349826312261823892
How to flash the Kernel:
1. Make sure you are rooted, are using the latest magisk stable and either EXKM or FKM is installed. Download the kernel.zip to your device.
1a. If you used the SQLITE3 Magisk Module and the GPay Fix Magisk Module in the past (prior to 2.0.0) look at this post: click me
1b. Remove the old powerhint-magisk module in magisk manager starting with version 4.5.6 as it´s now included in the kernel.zip. After flashing the kernel it will show up as AK3 Helper Module in Magisk Manager.
2. Flash kernel zip in EXKM or FKM app. Root will be preserved! (Make sure to be on the latest firmware the kernel is made for)
3. Reboot and profit! Before reporting any issues make sure to read the first three posts of this thread!
Instructions can be found in the OP too!
Have fun, enjoy the kernel and your phone.
If you like my work please consider a donation.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea: http://paypal.me/freak0738Update to 2.1.0
Hey guys and girls,
So here´s the next update. I guess you all have noticed by now, that I try to not constantly update the kernel, immediately for every single new commit that makes its way into the kernel.
This has mainly two reasons. I want the kernel to be tested thoroughly. I´m not trying to develop a very close to stock kernel, but I still want it to be stable. Testing needs time and some issues only creep up after a while.
The other reason I´m short on time lately and updating the thread takes time.
Short explanation on some logs I examined, the new CAF-Merge and the December update from Google.
Regarding the logs. I further dug through the source and while testing we stumbled upon a few things.
I took a look at the log @rickysidhu_ send me a few days ago. It´s unfortunately caused by a warning that´s also present in the stock kernel on the Pixel 3 and I saw the same on a log from one of my testers. @rickysidhu_ confirmed it happens on EX-Kernel on the Pixel 4 as well, which is very close to stock. So I´m sure it isn´t something I introduced.
I never encountered the warning or the following reboot on my own device, so it might be something network related tied to a very specific scenario or some sequence of events.
I´m aware of the issue and still looking for a solution.
problem number two is connected to another issue one of my testers run into.
Looking at the log I found this commit from Google present in the stock kernel related to a problem where the device fails to switch between suspend and resume.
It essentially forces a kernel panic, when the device is stuck between suspend and resume. This issue appears to be quite rare, but it happens more frequently for some people.
It seems to me Google had no other choice, than to implement that non-desirable "workaround" for the issue.
If this happens the radar chip and some thermal driver related code seems to be at play.
If you encounter a reboot, immediately go to sys/fs/pstore, zip up the contents and upload them here for me. Give all details about your setup and I will look at the logs.
This brings us to the December update from Google.
Google now enforces warm reboots on thermal related shutdowns. That means logs are kept intact in case a random reboot happens.
I think this is directly related to the suspend/resume issue described above. So google is aware of the issue and seems to work on it.
On the good side, they worked on the face-detection driver and made it work more quickly and efficiently.
Google maxed out PCIe speeds, and fixed an encryption related problem which both impacted file system performance as well
Follow this link for an androbench taken on the December update
There are many other little improvements from Google in the December drop, so the wait was definitely worth it for me.
The last point is reserved for some of my own changes.
The nextgen-CAF tag is now merged to the most recent state to what´s available on the CAF-repos. This second merge brought again many fixes from CAF-Upstream and I can tell the kernel runs better than before from the logs and usage.
I was able to revert a few "emergency" google fixes in the source and replace them again with CAF-Upstream solutions. Some of these reverts seemed over a year old and seemingly forgotten by Google. This might have been the issue for some deep sleep issues. I didn´t encounter a single instance where my phone was left with broken deepsleep for over 2 weeks now.
Additionally I merged an upstream solution for PM/Wakeup driver from kernel/common, which reduces unnecessary logspam and also improves sleeping behaviour/operation.
Since there are some problems with sleep/suspend/resume behaviour on the Pixel 4, I wanted to give this a few weeks before it gets in the release kernel.
Alongside these commits, the Google and CAF drivers which make use of the upstream PM/Wakeup solution, were updated to work properly.
The CAF-Tag brought many improvments to SOC-related driver and EAS- Implementation as well. I certainly haven´t noticed any negative performance issues for now. Hundreds of files were updated. Take a look at github if you´re interested in detailed changes.
Removal of kernel side enforced HBM.
There are currently two ways to enable HBM on this kernel, either use the kernel side enforced HBM (toggleable in EXKM) or enable the hidden factory disabled HBM from Google.
After some Pixel 4 owners reported issues with the HBM toggle in EXKM, I decided to remove this implementation from the kernel for now.
The Pixel 4 and the Pixel 4XL share different BL values. Which made toggling HBM on the Pixel 4 reset the brightness to 1/4 of maximal brightness.
The HBM mode enforced by the kernel makes the display drop to 60hz, maxes the brightness out and renders the brightness slider non-functional.
However enabling the HBM mode baked into stock kernel, but disabled by Google leaves the display at 90hz and the brightness slider functional.
It´s described in the following artice: How to enable disabled factory HBM from Google on the Pixel 4/XL
Since that method works way more smoothly, I decided to remove the kernel side enforced HBM from my kernel.
So refer to that XDA article above for high brightness mode, in case you want it enabled.
A word of warning however. HBM is one of the mods, that can damage your device and Google could arguably deny any warranty claim, if you decided to use it.
Google made the Pixel 4/XL devices only use HBM on HDR video playback.
That might have a few reasons other than to save battery or to "limit" and leave users with a dimmer display.
Yes limiting the maximum brightness saves a bit battery especially when 90hz is used. I guess we all like a bit more battery life.
However what also needs to be seen is the relation of battery life versus increased usability in sunlight by HBM!
here´s a comparison shot with a camera on manual controls. One in a dark corner of the room and one in the "not so bright" German winter sun.
https://photos.app.goo.gl/wmN56Gd6unhvXBym8
As you can see the difference isn´t really big. I wouldn´t say enabling HBM makes usability in the sun better by a huge margin. Even the super bright displays of other phones are not comfortable to use in bright sun.
With the method above every can try by themselves if they increased brightness is worth the increased power consumption and decide for themselves.
Now the warning. Google deliberately made HBM only available on HDR Video playback. That means moving content with less chance of burn in.
Since we don´t have documentation about the safety limites of the displays available, you´re touching ground that isn´t clearly labeled as safe for the display on a daily basis.
Rendering static images on highest brightness in HBM, may "benefit" and accelerate burn in.
If you´re not using HBM and make a warranty claim for burn in, law is on your side when asking for a replacement. If you decide to use HBM and overwrite googles intentions, your in another zone.
Anyway have fun with the release. I´m very satisfied with the kernel so far
Small update on the magisk module:
Magisk Module fixing the stock powerhal behaviour:
The power hal of the pixel 4 is partially controlled by a config file. On stock the setup of the power-hal causes the kernel to not idle at 576mhz on the little cluster after some random length of uptime, depending on usage and setup.
This module fixes this behaviour. It´s not critically needed, but may increase battery life a tiny bit.
On stock this config file sets up the power hal to boost top-app schedtune boost to 30 upon interaction and after the boost duration is finished, back to a value of 10.
There are different groups for tasks. top-app tasks are ui-critical tasks, rt-tasks, all that are critical for a smooth experience of the phone.
Setting top-app schedtune boost to 30 causes the follwoing: The scheduler will expect tasks of the top-app group to use 30% more CPU time than they (probably) actually will, and the CPU-frequency governor will speed up the processor accordingly. "Boosting" a process in this way, thus, does not affect its scheduling priority, but it will affect the speed of the CPU on which it ends up running.
The problem is resetting the value back to 10, when no interaction is happening. This seems to cause the little cluster to idle at 1036mhz after the phone is up and running a few hours on 4.14 kernels.
With my module the value gets reset back to 0 instead of 10, when the phone is not being interacted with
As you can see this is not kernel related, but a userspace thing, that just influences how the kernel handles load. So it can´t be fixed in the kernel, it needs to be fixed in userspace.
That´s why I created this magisk module. It can be used on the stock kernel and other kernels as well!
I recommend using the module as I´m using it myself
V2 boosts the CPU cores to max for 5 seconds instead of only 1, when launching the camera app to ensure smoother operation.
The changes introduced by the new CAF-Tags were tested for over a week without a single issue reported by my testers
A huge thanks to them at this place again.
@wrongway213
@Mrcactuseater
@MArtyChubbs
@ilal2ielli
@toastyp
@Alcolawl
Detailed changelog below.
Enjoy!
Changelog:
Kernel Base
- Merge all Google related changes from December Security Drop
- Next-Gen CAF-Tag updated to LV.AU.0.1.0.r2-00200-qtiquingvm.0
- revert some Google changes, which could lead to a non deep sleep behaviour and replace them with CAF-Upstream solutions
- additionally merge upstream solution for PM/Wakeup driver, which reduces unnecessary logspam and also improves sleeping behaviour
- update Google and CAF drivers to make use of the upstream PM/Wakeup solution
- linux-stable upstream to latest 4.14.158
- update AK3 zip to latest state (thanks to @osm0sis )
Features:
- Remove kernel enforced HBM (only disadvantages at the moment, use this instead: how to activate factory disabled HBM from Google
- make WLAN driver more lightweight and user power efficient workingqueues
- remove an unnecessary wakelock from the WLAN driver (the wlan has more than enough ways to acquire wakelocks)
Further Kernel Changes:
- look at github
Other changes:
- look at github
Magisk Module:
- update to v2
- boost cpu-cores to max when opening the camera app 5 seconds instead of only 1 second to ensure smoother operation until all necessary firmware and drivers are loaded
Have fun flashing and enjoy your device with latest linux-stable
Why is linux-stable important?
I wish you all a nice day/evening!
Download is below
Download:
Kernel: https://www.androidfilehost.com/?fid=4349826312261667498
Magisk Module: https://www.androidfilehost.com/?fid=4349826312261667499
How to flash the Kernel:
1. Make sure you are rooted and either EXKM or FKM is installed. Download the kernel.zip to your device.
1a. If you used the SQLITE3 Magisk Module and the GPay Fix Magisk Module in the past look at this post: click me
2. Optionally: Flash the magisk module provided in the release post!
3. Flash kernel zip in EXKM or FKM app. Root will be preserved!
4. Reboot and profit! Before reporting any issues make sure to read the first three posts of this thread!
Instructions can be found in the OP too!
Have fun, enjoy the kernel and your phone.
If you like my work please consider a donation.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea: http://paypal.me/freak07
New posts
-
[ROM][A13][OFFICIAL] OctaviOS- Latest: Lord Sithek
