Related
Noma kernel for Huawei U8150
I'm introducing my custom kernel for Huawei U8150 IDEOS phones. In Kenyan Swahili noma usually means "tight," as in: "That music is tight!" It can be used in other ways too, but I like this connotation the best.
GoalsMy aim is to learn about Linux kernel internals, practice software development using git, and to share with the community. In addition to that, I want to explore and test tweaks which lead to increased/optimized performance on this bargain phone (it's very popular in Kenya). Some of the areas of improvement I have in mind are:
CPU scheduling (UI responsiveness, reducing lag)
CPU frequency scaling governors (smartass? ondemandX? interactiveX?)
I/O scheduling and filesystems (flash disk performance, throughput, latency, maybe simpleio scheduler?)
Security (network, local)
Newer drivers (mainstream, community kernel sources)
Newer GCC compilers (CodeSourcery, Linaro)
Easy rooting
Integrate ClockWorkMod Recovery
Integrate busybox
Explore different compression algorithms (LZO, gzip, LZF, etc) for zImage...
Compcache (zram) (info, announcement)
SLOB memory allocator for better memory allocation? (info)
Current features
Code:
- multi-touch gestures (on devices with [url=http://mjanja.co.ke/2011/08/does-your-huawei-u8150-support-multi-touch-gestures/]supported hardware[/url])
- over/under clocking of CPU frequencies
- Tiny RCU ([url=https://lwn.net/Articles/323929/]info[/url])
- BFQ I/O scheduler ([url=http://algo.ing.unimo.it/people/paolo/disk_sched/]info[/url])
- simpleio scheduler ([url=https://github.com/erasmux/hero-2.6.29-flykernel/wiki/Smartass]info[/url])
- "ck" patch set, including the Brain **** CPU scheduler (BFS) ([url=http://www.kernel.org/pub/linux/kernel/people/ck/patches/2.6/2.6.32/2.6.32-ck2/]info[/url])
- optimized memcopy/memmove ([url=https://github.com/alanorth/kernel_huawei_u8150/commit/871656cbba8ee70d0896ac5cae35a31c2e0873e3]info[/url])
Downloadsfastboot-flashable boot images:
20120514v1: info, download
20110903v83: info, download
20110827v56: info, download
20110824v49: info, download
20110823v47: info, download
noma_20110711v26_boot.img (the "oops, I messed up my phone" kernel... safe, stable defaults; close to "stock" Huawei)
Possibly more here (on github)
Change logChange logs are a pain in the ass to keep up to date, but you can see changes live in the git repository itself. See the commit history of the below branches if you're curious:
froyo-noma-dev commits (dev, bleeding edge)
froyo-noma commits (stable)
Source code
I respect the GPL (the license covering the Linux kernel), so all the up-to-date source code for this kernel is available on github. My kernel is, in turn, based on the publicly-avaiable Froyo kernel sources from Huawei. You're free to fork, modify, and re-release the code as your own, but you must provide the source code for your resulting work. Doing so ensures you honor the terms of the license, but you're also giving back to the community. Basically, don't be a ****.
Credits
I've written zero lines of C code for this kernel. My work is merely to search for interesting modifications to the Linux kernel and add them to a git repository. The real work has been put in by the following people:
Linus Torvalds and all the other Linux kernel hackers around the world
tj_style (multi-touch gesture support)
Stefano Viola (over/underclock)
Renaud Allard for his Galaxy S awesome sauce (kernel, initramfs, etc)
Erasmux (smartassV2)
Let me know if I've left you out.
Donations
Hahaha! No seriously, save your money; I am gainfully employed and I just do this for fun (and lulz)! Instead, just hit "thanks" on this thread. Or, if you're ever in Nairobi you could always buy me a cup of coffee.
Reserved for flashing instructions...
Could you please post fashing instructions via custom recovery?
Im a bit of a noob.
Thanks.
Use fastboot!
Antownee said:
Could you please post fashing instructions via custom recovery?
Click to expand...
Click to collapse
I usually just flash from fastboot lately, as I'm between ROMs too much and I don't bother installing a custom recovery. I suppose I should modify my build scripts to make recovery-flashable zips... hang tight!
... or, if you can't wait, check out my in-depth blog post about compiling and flashing custom kernels on Huawei 8150. I wrote it a few weeks ago when I was a U8150 n00b.
v47 (20110823)
Changes in 20110823v47 (from the git commit log):
Add new, lookup3-based jhash. See: http://burtleburtle.net/bob/hash/doobs.html
pids: fix a race in pid generation that causes pids to be reused immediately
lib/decompress_bunzip2.c: fix checkstack warning
kbuild: drop unifdef-y support
net sched: fix some kernel memory leaks
net/ipv4: Eliminate kstrdup memory leak
Add noma_defconfig. `ARCH=arm make noma_defconfig` to use.
Mostly security and memory leak fixes. The new jhash implementation is based on lookup3.c, a newer, more-efficient implementation (more info here). It's mainly used in the kernel's ipv4 and ipv6 stacks, so don't expect revolutionary performance increases, but it's backwards compatible with the old implementation, so it couldn't hurt to include it.
Default IO scheduler is now deadline (the same as stock Huawei) until I can do some performance tests of other schedulers on this device. Note: I've included BFQ, Anticipatory, CFQ, and noop as well, so you can use those if you like!
Download: noma_20110823v47_boot.img
v49 (20110824)
Changes in 20110824v49 (from the git commit log):
Default to ZLO compression of kernel and ramdisk. LZO has roughly the same (but worse) compression, but is much faster to decompress.
Add LZO compression support for initramfs and old-style initrd
Add support for LZO-compressed kernels on x86
Add support for LZO-compressed kernels for ARM
Add support for LZO-compressed kernels
LZO compression is not as efficient but should be faster than the default compression (gzip), which should improve boot time. See: http://free-electrons.com/blog/lzo-kernel-compression/.
Download: noma_20110824v49_boot.img
Why are you working on Froyo and not on Gigerbread?
Why I'm still working on Froyo
unknhawk said:
Why are you working on Froyo and not on Gigerbread?
Click to expand...
Click to collapse
As this is basically a research project (for both me and the community), the primary reason I'm still "working" on Froyo is that most U8150s are still running Froyo. It's an incredibly popular phone in Kenya (maybe 250,000 - 500,000 units sold?), but I have a hunch very few of them are running non-stock ROMs. Sure, CyanogenMod 7 has a fairly-active U8150 port in progress, but it's not widely used yet.
Like I said, this is primarily a research project, so I'm experimenting for my own curiosity. A part of that is to help people get into Linux kernel, Android, and open-source software development. I want to help set an example of openness, collaboration, documentation, etc.
Also, a lot of the mods I'm making can just as well apply to Gingerbread when we finally get there.
Custom kernel booting on U8150 CM7
unknhawk said:
Why are you working on Froyo and not on Gigerbread?
Click to expand...
Click to collapse
Fun times... I just got a custom kernel to boot on CM7. It's nowhere near as usable as tilal's kernel, but it is a good exercise. More info here on my blog.
I suppose that whenever I get bored enough with Froyo I could always hop over to CM7. AOSP is where my heart is anyways.
v56 (20110827)
Changes (from the git commit history):
Add su, Superuser.apk, and busybox. This kernel/boot.img will now actively root Huawei stock ROMs.
Remove pre-zipped ramdisks as they are now generated on the fly from the compile scripts.
Correct the name of the compressed ramdisk (mkbootfs technically creates a cpio archive, which I then zip).
Make sure `make clean` doesn't delete our pre-compiled wireless module.
Add mkbootfs for creating ramdisks, and update compile.sh to create ramdisks on the fly instead of using a pre-zipped one.
Add ramdisk from U8150 V100R001C18B842
The build system is now a little more flexible and generates ramdisks on the fly. This should make it more powerful and complete. I've also included su, Superuser.apk, and busybox to enable a very cool new feature: rooting! If you haven't forked or cloned my kernel repository yet, what are you waiting for?
Regarding "rooting," forget what you've heard (it's probably wrong). Here's what it actually means:
Copying the su binary to /system/bin/su
Copying the Superuser.apk application to Superuser.apk
Period. What this means is that Android applications can call on the su binary whenever they want to do perform system administration actions (ie, not normal user actions), such as removing system applications with Titanium Backup. The Superuser.apk application is simply a frontend for su; whenever an application tries to execute su, a Superuser dialog pops up asking you to allow or deny the request. This notion, known as "privilege separation," is a common one in all operating systems.
Download: noma_20110827v56_boot.img
v83 (20110903)
Changes (from the git commit history):
sched: export nr_running symbol for use by smartassV2 CPU governor.
config: sync with latest config
sched_fair: Restore less extereme latency values (latency of 6ms)
sched: enable HRTICK
sched_fair: Enable HRTICK
cpufreq: add smartassV2 governor
Switch busybox, older version (1.18.4) but slimmer, more appropriate for our needs (from https://faramir.eriador.org/r/).
Minimum frequency to 122MHz at boot, as well as smartassV2 governor.
Optimized ARM RWSEM algorithm
Cleanup after installation of su stuff. We're on a ramdisk after all, we need to conserve memory.
Change location of root stuff so it isn't in the $PATH
Add Simple I/O Scheduler
Add V(R) i/o scheduler
Update to latest Linaro GCC 4.6 compiler.
Two major changes are the addition of the simpleio IO scheduler and the smartassV2 CPU governor. The simpleio scheduler is based on/around the noop and deadline schedulers, designed specifically with non-rotating media in mind (flash disks, hello!). The smartassv2 CPU governor controls how your CPU switches between frequencies (from 122MHz at idle to 672MHz when in use). I haven't done any benchmarks, but these should improve responsiveness and battery life (in theory at least!).
Other than that, the latest Linaro GCC 4.6 compiler, some small optimizations to ARM-specific functions, and ramdisk/boot cleanups. If you're curious about smartassV2 there's more info here, on erasmux's github page here.
Download: noma_20110903v83_boot.img
cm7 nightly bugged one ?????? i dnt like it iz there iz n e fixed cm7 for ideos ????
btw your kernel doesnt works with cm7 and can u please make a kernel for samsung galaxy gio with smartass v2 ??
Aorth, I tried flashing you kernal, and unfortunately there is one error when flashing with the latest CM7.1. After the flash, the phone will be stuck at the boot screen. I was wondering if you can get this fixed, that'll be great
This kernel is meant for stock ROMs
Den15 said:
Aorth, I tried flashing you kernal, and unfortunately there is one error when flashing with the latest CM7.1. After the flash, the phone will be stuck at the boot screen. I was wondering if you can get this fixed, that'll be great
Click to expand...
Click to collapse
Yeah, this kernel was really meant for Froyo stock ROMs. It won't work on CyanogenMod builds because the ramdisk's init scripts are not compatible.
My U8160 kernel repo has a kernel which works on CM7... but you'll have to compile it yourself
nice kernel ........... working fine on ideos u8150-B .... I flash it with stock rom ................. battry becomes efficient ...
Good Job!
Hello aorth,
I'm now using the LEANdroidMOD 5 based on your kernel and I have to say the name NOMA suits it to a tee. It's my default ROM now when I'm not testing your or tilal6991's builds. Thanks and you have yourself a happy holiday season!
hello,
will there be any update of your noma kernel? this is my fav because all roms out there eat my battery like mad, so i just use your kernel and i'm happy with it
greetings
oh man please update, this is one nice kernel!
CM7 u8150 april 5th
IS this already built in to your CM7 last updated april 5th rom or is that a diffrent kernel? which one is better? would it be hard to install it on that rom? whats the advantages over the built in cm7 rom? Thanks sounds awsome anything to make that baby faster is great. Good work
SU Binary Outdated notification
flasehd v83 on the stock 2.2.1 kenya 1 mutli touch rom all went good but whenever i restart the phone su binary shows the notifications bout su binary being outdated which i updated , i did it multiplie times but it comes up everytime the phone is rebooted , other than that su binary working ok ,
dont know how to fix it , other than that the phone is working so responsive , enjoying it
when i flashed the kernel , the phone was already rooted
cheeeeeeeeeeers
Q&A for [Kernel][23/10/14][D850]Rin Kernel 1.6
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Kernel][23/10/14][D850]Rin Kernel 1.6. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
i tried this method I. my att g3
Tectas said:
RIN Kernel for D850
Close to stock with some sugar added ... delicous!
Hey guys and girls,
you may have seen my unified stock kernel thread already (or may not, but doesn't matter). This kernel is my attempt to build up on the fixed source and add some additional features for us mod lovers to thinker with and to personalize your device to your usage. For now, I'll keep it close to my stock source and just pull some additional features and fixes in, but not to much. That may change in the future (maybe even soon), but for now, I'll stick to that paradigm.
First of, DISCLAIMER, I'm not responsible for bricked devices, dead unicorns, rainbows with missing colors, world war, nose bleed, void warranty (you know that already, don't you? your warranty is void now and it's your fault ) or any other harm happening to your device, you or people around you!
What does it serve?
Built with linaro 4.9.1 cortex-a15 optimized toolchain
IO Schedulers
BFQ
CFQ
DEADLINE
FIFO
FIOPS
NOOP
ROW
SIO
TRIPNDROID
VR (default)
ZEN
Governors
Adaptive
Conservative
DanceDance
IntelliActive
IntelliDemand
Interactive (default)
Lagfree
Lionheart
OnDemand
Performance
Powersave
SmartassV2
Userspace
Wheatley
Smartmax
Voltage control
SoundControl
Intelli-Thermal v2
Many under the hood fixes
Stability
More to come
How to apply it?
IMPORTANT: Read through all the requirements, steps and warnings before you do anything, if any requirement doesn't match or you don't know what one or more of the steps below mean or do, ask before you do any of them, if you don't know how all the steps can be done, let it be and wait for the bootloader unlock, I warned you, if you don't do and something bad happens, I'll just laugh at you!!
Requirements? Yes!
D855/P/K, F400/K/S/L, D850
Root
How to use the command line
PC
working fastboot
working adb
How to boot the kernel?
Plugin your device to the PC
Open a terminal and execute
Code:
adb shell # open a shell over adb
su # change to superuser
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/storage/external_SD/stock-laf.img # backup the stock download mode to your external sd
exit # exit the superuser shell
exit # exit the adb shell
adb pull /storage/external_SD/stock-laf.img . # backup the download mode image from you external sd to the PC
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf # remove the stock download mode
BEWARE, THIS WILL REMOVE YOUR DOWNLOAD MODE!!! YOU WON'T BE ABLE TO FLASH KDZ FILES BEFORE YOU RESTORED IT!!!!
Turn off the device completely, plug in the USB-cable, if you pulled it out and start the device by holding vol up + power till you see some white text on the screen, fastboot should be written somewhere on the screen, afterwards execute the following command on the PC (while in the directory you've downloaded the kernel image to).
D850:
Code:
fastboot boot D850-rin-1.6.img # boot the kernel
BEWARE, NEVER USE FLASH AT FASTBOOT ONLY BOOT, IT WILL TRIGGER SECURITY OF THE LOCKED BOOTLOADER AND YOU WON'T BE ABLE TO BOOT ANYMORE!!!!
You're done now and booted to the custom kernel!
How to make sure you're running the kernel?
To check if you properly booted into the kernel execute this in the command line (terminal emulater or through adb shell):
Code:
cat /proc/version
it should show
Code:
Linux version 3.4.0-rin-g58903a9-dirty ([email protected]) (gcc version 4.9.1 20140710 (prerelease) (crosstool-NG linaro-1.13.1+bzr2673 - Linaro GCC 2014.07 - Cortex-A15) ) #53 SMP PREEMPT Thu Aug 14 13:26:42 CEST 2014
Once more a warning READ IT!!:
BEWARE, when you reboot you'll boot to the stock kernel, you'll have to boot the custom kernel over fastboot every time, when you boot normally, you'll be on the stock kernel, this won't lead to issues, but you'll miss the benefits of this kernel, I know that's not optimal, but the best we can get with the locked bootloader.
How to restore Download mode?
Code:
adb shell # open a shell over adb
su # change to superuser
dd if=/storage/external_SD/stock-laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf # restore the stock download mode from the backup on your external sd
Changes?
23.10.2014/1.6
D850 support added
Simple GPU Algorithm Support
Overclocking up to 2.76 Ghz
exfat support
intelli-thermal v2 added
smartmax governor added
memutil optimizations
build with NEON kernel mode
2-way call recording patch
DriveDroid cdrom emulation support
Faux SoundControl
Simple-OnDemand fixed
Cpu Freq Limiter
some small fixes and enhancements
14.08.2014/1.0.1
net/ipv4|include/asm-generic: Enhancement of out of bounds fix
14.08.2014
Initial release
Full list of commits can be found here
Where to get it from?
D850-rin-1.6.img: AndroidFileHost | xda | dev host
md5sum: cd843592764abee8cb03dc701612832e
Show me the so(u)rce(ry)!
https://github.com/tectas/android_kernel_lge_msm8974ac/tree/rin-kitkat
Donators (huge thanks, you're simply great )
@Toneman07
@Helloworld294
@shaarky
Credits
XDA
Google
LG
@HolyAngel
@faux123
@KAsp3rd
myfluxi
If you like my work, please show your appreciation by pressing the thanks button, if you want to do more, i've nothing against a little donation, but I'm as happy when you just thank me by pressing the button
XDA:DevDB Information
Rin Kernel, Kernel for the AT&T LG G3
Contributors
Tectas
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1.6
Stable Release Date: 2014-10-23
Created 2014-10-24
Last Updated 2014-10-24
Click to expand...
Click to collapse
phone and on the fastboot screen out it says that the file was to large... What does that mean and where did I go wrong
Was wondering if you will bump the kernel now that their site is live?
http://apps.codefi.re/bump/
kpparry0156 said:
phone and on the fastboot screen out it says that the file was to large... What does that mean and where did I go wrong
Click to expand...
Click to collapse
Please don't quote whole OPs...
Are you sure you took the right file? Just from saying "that's the procedure I've used" I can't tell, sorry, if that's exactly how you've done it, it has to work, as for anybody else, if you did something slightly different, you need to tell.
guyd said:
Was wondering if you will bump the kernel now that their site is live?
http://apps.codefi.re/bump/
Click to expand...
Click to collapse
Jup, coming today
bump kernel?
It's coming out today.. So I can bump a custom kernel or the rin 1.6 kernel for the d850 correct
kernel
Nice
Have you tried using any other toolchain? I came from arrrghhh's anykernel, which was built on SaberMod, which was very snappy as compared to Linaro in my testing.
Sent from my LG-D850
Sinterion said:
Have you tried using any other toolchain? I came from arrrghhh's anykernel, which was built on SaberMod, which was very snappy as compared to Linaro in my testing.
Sent from my LG-D850
Click to expand...
Click to collapse
Yes, tried sabermod already, it's just even stricter than linaro at compiling, have to change a bit stuff, to be able to compile with it, but it's already on the schedule.
Sent from my LG-D855 using Tapatalk
Tectas said:
Yes, tried sabermod already, it's just even stricter than linaro at compiling, have to change a bit stuff, to be able to compile with it, but it's already on the schedule.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
Cool! Well if you need a tester for the D850, just shoot a PM my way!
Sent from my LG-D850
Curious why some devices get the green screen and some don't. I installed cloudy, then tried installing the kernel zip and same thing. Let me know if you want me to test anything if you get to a point and need someone that's getting the green screen, I'll be more than happy to help
Kernel Version Info
When I go to "Kernel Version" under "Software Information" it shows the Kernel Version as 3.4.0
Is this normal? Or is it supposed to say "Rin Kernel 1.7.1"?
What is the most efficient or favorite setup for Kernal
Thanks for getting a flashable zip file out! I was waiting for this because I didn't want to risk messing something up with the original installation method. From what I have read, people really like the kernel. I'm DLing it now!
OP. Any plans to make custom kernel's for AOSP Roms?
Sent from my LG-D850 using XDA Free mobile app
animator776 said:
When I go to "Kernel Version" under "Software Information" it shows the Kernel Version as 3.4.0
Is this normal? Or is it supposed to say "Rin Kernel 1.7.1"?
Click to expand...
Click to collapse
Yes, that's normal. Has something to do with the Linux version.
guyd said:
Yes, that's normal. Has something to do with the Linux version.
Click to expand...
Click to collapse
Ok, thanks. I was wondering because I've flashed kernels in the past that display a custom kernel version i.e. "Dorimanx"
I believe the kernel version that is displayed can be changed in the build.prop
Anyone care to post their stable settings for this kernel? I remember a similar thread for the S4 which really helped guys like me who aren't real familiar with all of the different kernel tune-ables.
I've searched the dev thread and this one but didn't see any reports about icon themes reseting after reboot. I finally flashed this kernel tonight and each time I've rebooted after tweaking cpu freqs, the icon theme I'd applied using Nova Launcher reverts back to default icons. I've been on stock kernel since July and this has only happened since flashing this kernel a few hours ago. Any ideas?
JediSooner said:
I've searched the dev thread and this one but didn't see any reports about icon themes reseting after reboot. I finally flashed this kernel tonight and each time I've rebooted after tweaking cpu freqs, the icon theme I'd applied using Nova Launcher reverts back to default icons. I've been on stock kernel since July and this has only happened since flashing this kernel a few hours ago. Any ideas?
Click to expand...
Click to collapse
I'm using Nova with some alternate icons without issue. Don't know what to tell you except it's working fine for me.
Problem solved and it wasn't anything kernel related. I forgot that I was playing with moving apps to SD the other day and moved all of my icon packs. Apparently, regardless of the launcher being used, it will load before the SD card initializes, so the icon packs aren't found. I've moved then back to the phone and all is well. Google is definitely my friend.
WARNING : I am not responsible for Thermonuclear war in your pocket or bricked devices, use at your own risk!!!! following insructions
I know it is too late but Finally Custom kernel for our Rm2pro is finally ready
I have put a lot of effort to fix the ****ty oppo source, especially fixing WiFi took pain in my ass.
Features:
1. enabled system rw remount, now you can uninstall system apps directly, use apps like adaway
2.add support for Btrfs, Reseirfs, Xfs , Ntfs in kernel
3. add lz4, bzip2, lzo, lzma and xz compression option for ramdisk
WIP
1. lz4 compression of kernel
2. various cpu governors and i/o schedulers
Planned features:
1. Multi Rom booting option with Kexec
2. upstreaming with Linux kernel and CAF === Lot of security fixes
3. I am not gonna leave this kernel any soon :laugh:
Bugs : you tell me
lenk : https://www.androidfilehost.com/?fid=1395089523397968557
Special Mention:
1.thanks to @osm0sis for his anykernel2 zip
2. Everyone else who helped me with this
Compatible Roms:
Oreo : any rom Stock or custom
Pie : You test and tell me
Flash Instruction:
1. First backup your boot.img in recovery in case it will be helful later
2. flash the zip from recovery and reboot!! No need to wipe any ****
FAQ:
1.How to report bugs?
take a proper dmesg log and logcat and report
2.Where to report?
Preferably in Realme 2 pro Telegram group , if not possible here
3. How to request feature?
preferable in this thread, and (if) any link where you found that feature
XDA:DevDB Information
Redfeast_Kernel, Kernel for the Realme 2 pro
Contributors
redfeast
Source Code: https://github.com/redfeast/android_kernel_oppo_RMX1801
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1.1
Stable Release Date: 2019-05-18
Created 2019-05-18
Last Updated 2019-06-04
Good work mate keep it up
Great work! Keep it up!
Feature requests
1. Dts Eagle support (audio enhancement)
2. Little gpu over clock (idc about cpu)
3. Charging speed around (1500Ma)which is safe as max pro m1 comes with 1800ma out of the box. (realme has only given 900-1100Ma)
4. DT2W
??
Great work mate.
great work mate. i only request you return the gpu clock to 2.2 as it should be and maybe some oc for cpu as well. thank you. will try asap.
I guess R2pro battery can't sustain overclock of either GPU or CPU from stock values, may be that is why they lowered them
redfeast said:
I guess R2pro battery can't sustain overclock of either GPU or CPU from stock values, may be that is why they lowered them
Click to expand...
Click to collapse
i think it just to preserve more battery thats why they set it to 1.9-2ghz only instead of 2.2ghz. it's nice if we can have option to 2.2ghz though
This kernel is very useful. now red color warning message (ie., rooted mobile) is not coming!!! and we can delete unwanted system apps via es file manager. but we can delete in local drive only. Any way im happy. i hope this kernel maybe work in upcoming stable stock pie rom. Thank you guy.
Thanks for the kernel...The red notification is no longer coming after rooting ..
But LMAO what did u do to the CPU with this kernel??
My antutu score got reduced from 130000 to 85000
Really happy for seeing custom kernel:good:
Hotspots bug is there
Kernel is good. But one major bug is there. That bug is wif hotspot. After flashing kernel and magisk. Mobile is perfectly rooted. red colour warning msg is also stopped and RW is working. very interesting, But first time hotspot is working but after restarting mobile and laptop, the hotspot will not work properly. Laptop shows connected but no internet!!! i cheched stock rom coloros 5.2 ver 14, 15 and 17.
hero197 said:
Kernel is good. But one major bug is there. That bug is wif hotspot. After flashing kernel and magisk. Mobile is perfectly rooted. red colour warning msg is also stopped and RW is working. very interesting, But first time hotspot is working but after restarting mobile and laptop, the hotspot will not work properly. Laptop shows connected but no internet!!! i cheched stock rom coloros 5.2 ver 14, 15 and 17.
Click to expand...
Click to collapse
It is not a bug of kernel but lite Os, I'm using Hotspot seemlessly. I lite Os or color Os disable pill killer and restart, your Hotspot should work
Is this kernel works on ColorOS 6 beta.
Update - its not working on ColorOS 6.
redfeast kernel 1.1 is not uploaded!!!???. kindly give the new redfeast kernel for color os 6. Rooting notification is coming. so need your help to fix it.
hero197 said:
redfeast kernel 1.1 is not uploaded!!!???. kindly give the new redfeast kernel for color os 6. Rooting notification is coming. so need your help to fix it.
Click to expand...
Click to collapse
I removed 1.1 due to bugs. Pie release takes more time.
hero197 said:
Kernel is good. But one major bug is there. That bug is wif hotspot. After flashing kernel and magisk. Mobile is perfectly rooted. red colour warning msg is also stopped and RW is working. very interesting, But first time hotspot is working but after restarting mobile and laptop, the hotspot will not work properly. Laptop shows connected but no internet!!! i cheched stock rom coloros 5.2 ver 14, 15 and 17.
Click to expand...
Click to collapse
Hotspot has something to do with encryption, i use this kernel with encrypted stock A17 hotspot working fine, but if i decrypt other device cannot connect to my hotspot
redfeast said:
WARNING : I am not responsible for Thermonuclear war in your pocket or bricked devices, use at your own risk!!!! following insructions
I know it is too late but Finally Custom kernel for our Rm2pro is finally ready
I have put a lot of effort to fix the ****ty oppo source, especially fixing WiFi took pain in my ass.
Features:
1. enabled system rw remount, now you can uninstall system apps directly, use apps like adaway
2.add support for Btrfs, Reseirfs, Xfs , Ntfs in kernel
3. add lz4, bzip2, lzo, lzma and xz compression option for ramdisk
WIP
1. lz4 compression of kernel
2. various cpu governors and i/o schedulers
Planned features:
1. Multi Rom booting option with Kexec
2. upstreaming with Linux kernel and CAF === Lot of security fixes
3. I am not gonna leave this kernel any soon :laugh:
Bugs : you tell me
lenk : https://www.androidfilehost.com/?fid=1395089523397968557
Special Mention:
1.thanks to @osm0sis for his anykernel2 zip
2. Everyone else who helped me with this
Compatible Roms:
Oreo : any rom Stock or custom
Pie : You test and tell me
Flash Instruction:
1. First backup your boot.img in recovery in case it will be helful later
2. flash the zip from recovery and reboot!! No need to wipe any ****
FAQ:
1.How to report bugs?
take a proper dmesg log and logcat and report
2.Where to report?
Preferably in Realme 2 pro Telegram group , if not possible here
3. How to request feature?
preferable in this thread, and (if) any link where you found that feature
XDA:DevDB Information
Redfeast_Kernel, Kernel for the Realme 2 pro
Contributors
redfeast
Source Code:https://github.com/redfeast/android_kernel_oppo_RMX1801
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1.1
Stable Release Date: 2019-05-18
Created 2019-05-18
Last Updated 2019-06-04
Click to expand...
Click to collapse
Is this possible to use magisk v19.3 with full support i mean no Core Only mode.
as currently v19.3 only works in Core Only mode.
reply soon
thanks
Adityas95 said:
Is this possible to use magisk v19.3 with full support i mean no Core Only mode.
as currently v19.3 only works in Core Only mode.
reply soon
thanks
Click to expand...
Click to collapse
No you can't. Due to ColorOS 6 security, Magisk 19.3 doesn't work fully. Thus, current working version is only 17.1 which has magiskhide as well as module loading.
This kernel is for RMX1801. Don't flash it on RMX1807 or you'll be soft bricked your device.
@redfeast
Thanks! There's one bug in the kernel source - this folder being empty:
/android_kernel_oppo_RMX1801-master/drivers/staging/qcacld-3.0
I removed all references to it and it compiles fine - cheers!
Any chance of porting the drivers over from that kernel (4.4.78) over to the latest one (4.4.193)? The reason being: I cannot enable KVM Virtualization due to a bug in /arch/arm64/kernel/cpu_errata.c that referenced a function named "bp_hardening".
This bug has been fixed in 4.4.193 - but many files have been changed across /arch/arm64/
Kirisakura-Kernel for the Pixel 7/Pro
Hello everyone,
To keep it short: Here is Kirisakura - Kernel for the Google Pixel 7 Pro aka Cheetah and the Pixel 7 aka Panther, together Pantah.
I would appreciate if everybody that flashes the kernel, reads at least once through this opening post and the following ones.
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, F2FS-Stable 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.
By merging linux-stable regularly we get most security updates months ahead of the stock kernel and also before they even end up in the android security bulletin.
The kernel includes a lot of improvements and contributions from other developers as well. Without those contributtion this kernel would not exist as it is.
A big part of improvements originate from @arter97´s, @kdrag0n´s and @Sultanxda´s work. Many others contributed in some way or another to this kernel.
A big thanks to all of them at this place!
Now lets continue with a list of features in the next paragraph!
Features:
Main Features:
- Based on latest A13 kernel sources from Google, Kernel is made for Android 13 Stable
- Linux-Stable-Upstream included to 5.10.183
- Compiled with prebuilt Google clang 17.0.2
- Backport entire RCU subsystem to linux 6.0
- Lazy RCU which should result in power-savings while the device is lightly-loaded or idling, more information here
- Backport Maple tree from Linux 6.1
- improve preallocations from maple tree (affects especially android)
- reduce necessity to rewalk the maple tree
- Per VMA-locks in conjunction with Maple Tree RCU-Mode (improve app launch time, this feature in general benefits greatly from lazy rcu!)
- further improve maple tree/per-vma locks introduced in an earlier release
- Dynamic Energy Models depending on device state
- make TEO-Cpuidle util-aware (improves latency, performance and decreases energy consumption for certain workloads, more information here)
- improve CPU throttling behaviour
- improvements to uclamp, prevent capacity inversion (reduce missed frames)
- greatly speed up camera launch time!
- merged kernel/common (improvements to android-common-kernel straight from google)
- MM subsystem reworked (more info and some patchsets linked in this post)
- Multi-gen LRU backported/reworked and enabled (more info here, here as well and here) to improve mm and reduce cpu cycles, latest V15 state
- pelt multiplier tied into powerhal to speed up scheduler during interaction (more info here)
- prevent frequency spikes caused by small transient tasks when the device is idle(more info here)
- tie mechanism to prevent frequency spikes caused by small tasks also into powerhal
- scheduler improvements for RT (realtime) tasks
- introduce and setup PMU limiter (prevents CPU from spiking to max when it isn´t needed, based on PMU reads, more information here)
- improve camera performance by tuning the powerhal during recording
- bias tasks of rt, sf and ta groups to prefer high capacity cpus during app launches, interactions
- improve app launches via powerhal
- restrict maximum CPU-Freqs during screen off/ idle to 1.4GHZ for all clusters to save power
- introduce unfair f2fs rwsems to prevent writer starvation and improve IO perf under heavy load
- fuse: give wakeup hints to scheduler to speed up compress/decompress in internal storage (details)
- enable RCU_BOOST (details here), also fix RCU_BOOST behaviour
- F2FS-Stable updated
- merge and enable f2fs block_age-based extent cache (improve the accuracy for data temperature classification, reduce the garbage collection overhead after long-term data updates)
- TCP backports from mainline
- SSG IO scheduler for reduced overhead and less CPU cycles (more lightweight and android optimized)
- scheduler backports from linux-main
- mm updates from linux-main
- locking updates frm linux-main
- improve memory performance by tweaking google´s eh zram implementation
- fix sysfs endpoint for googles eh zram
- affine IRQS to CPU 7 during camera usage for improved performance as it tends to overload the little cores
- use bbr as default TCP congestion algorithm (fasted algo according to this excellent research from @kdrag0n found here )
- include bbrv2 from google, more info here
- Enable support for TTL spoofing
- important patches from kernel/common for 5.10 (here are more details)
- increase priority of GPU work
- several updates from QPR beta, and a few from Pixel 6 that googles missed to include in the pixel 7 kernel
- improve thermals
- change compaction proactiveness based on device state for improveed memory management
- improve ZRAM usage
- reduce overhead
- improve performance and efficiency by properly wiring up pixel_sched with teo util awareness (thanks @ada12 for spotting this!)
- update to cpuset/cgroup subsystem (speeds up camera launches, device unlocks etc as cpusets are switched on those conditions, patches reduce overhead in those conditions)
- flashing the kernel will preserve root
CleanSlate Features
- CleanSlate Features from @tbalden, big applause here! (s2s, notification booster, battery saver, flashlight notifications. Please note: cleanslate features that work otherwise with rooted devices like kadaway (adblocking) are not implemented on this kernel since I´m running rooted)
- Check the CleanSlate thread for more information about those features
- The CleanSlate thread also contains the apps that allows you to control those features!
- If you consider those features useful, maybe consider purchasing the apps in the PlayStore or a small donation to @tbalden, he deserves it! Don´t forget to switch to beta channel for those apps, as this is needed for device running A13!
Various Optimizations:
- update several drivers to use power efficient workingqueues (for example wlan driver)
- f2fs: reduce timeout for uncongestion
- f2fs: Demote GC thread to idle scheduler class
- f2fs: set ioprio of GC kthread to idle
- tcp: enable advanced tcp, give user more options for tcp alorithm
- mm: vmstat: use power efficient workingqueues
Wakelock Blocker:
- advanced wakelock blocker with the ability to block kernel wakelocks (dangerous, use with caution, please read this for further info). You should only block kernel wakelocks in case you face uncontrollable scenarios, like company wifi causing a wakelock to be active 100% of the time! Blocking kernel wakelocks to "improve" battery life almost always backfires and causes issues!
Powerhint Module:
- restrict little cluster to 1,4ghz mid cluster to 1,4ghz and big cluster to 1,4ghz during screen off, to reduce battery usage for example during music playback
- only use little cores during screen off/device suspend
- account for scheduler and other changes done to the kernel
- boost memory interface controller during interaction (decreased missed frames, improved soc efficiency according to google docs)
- tie pelt multiplier into the powerhal (more info here)
- prevent frequency spikes caused by small transient tasks during idle operation (more info here)
- boost scheduler using the pelt multiplier during fingerprint unlock operation
- setup and control PMU limiter via powerhal (more info here)
- switch between default and custom idle energy model on device is being interacted with / device idle.
- reduce missed frames during scrolling/device interaction by adjusting uclamp boosts
- dynamically adjust target load for memory interface during interaction.
- remove dynamic GPU policy change as it´s causing instability and is unneeded due to GVFS period
- implement handling during video recording of CPU like Google did on QPR A13
- more small improvements
DOWNLOAD:
Downloads are attached to the release posts linked below in the changelog section.
Please note that androidfilehost is currently not working properly.
Link to AFH:
Spoiler
Deprecated afh download, still here for old releases:
https://www.androidfilehost.com/?w=files&flid=336658
Changelog:
Android 13.0.0 Stable (not QPR beta!)
1.0.0 Initial Release | Mirror for Download in case AFH is not working
1.1.0 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-87743627
1.2.0 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-87822161
1.2.1 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-87878321
1.2.2 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-87944505
1.2.3 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-87960183
1.2.4 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-88108123
1.3.0 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-88286027
Raviantah_1.0.0 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-88316285
Raviantah_1.0.1 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-88323527
Raviantah_1.0.2 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-88399915
Raviantah_1.0.4 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-88497279
Raviantah_1.1.0 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-88645103
Requirements
- vbmeta flags for verity/verification disabled (this requires a wipe if you´re coming from stock with those flags enabled), check the FAQ for information on how to do this
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment so you can flash back to stock in case something goes wrong
- working magisk environment (a device rooted with latest magisk, use stable in case you want to be absolutely safe)
- IMPORTANT: Unrelated to the kernel, but update both slots of your phone to A13 before you flash anything to your device!
- it´s handy to have a backup and a way to return back to stock (check the faq for that)
- make sure to download the correct kernel version for your firmware. (you can´t flash a kernel made for stable firmware on a QPR beta or dev preview and expect there to be no isses, the release posts mention which firmware the respective kernel releases are compiled for)
- this kernel is tested on stock google firmware. If you want to use it on custom roms you´re kind of on your own as I can´t account and give support for any changes custom roms apply that could render the kernel incompatible. (e.g. if you´re custom rom is still on the previous months update, there may be issues flashing an updated kernel for the next month on top or custom roms requiring specific kernel changes to work correctly )
- it´s always best to start on stock images and don´t have another custom kernel flashed when flashing this kernel for the first time. consecutive flashes can just be installed on top, if not I´ll mention it in the release post
- read the first and second post, there's a lot of valuable information
How to flash the Kernel:
1a. Make sure you tick all the requirements above
1b. Make sure to flash the release made for your firmware! Usually the release post contains information on that
1. Download the kernel.zip (unified for both devices) and the correct powerhint module depending on your device (Pixel 7 = panther || Pixel 7 Pro = cheetah)
2. Flash the powerhint module via magisk manager as you would any other magisk module! Make sure to flash the latest one. It will be mentioned in the release post if there´s an update.
3. Flash the kernel.zip via EXKM, FKM or kernel flasher. Root will be preserved.
4. Reboot and profit.
Donations:
Donations are not mandatory but very welcome if you want to support development or just buy me a coffee/tea/beer
If you like my work: http://paypal.me/freak07
Credits:
@osm0sis for all his work on AK3.
@tbalden for being the best HTC, Pixel, OnePlus and Asus wingman!
@capntrips for all his work on the pixels, avb, hashtree patcher, the counsel and the kernel flasher!
@LeeDroid and @mwilky for their awesome roms and work I used on multiple devices!
@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 helping me out
@flar2 for all his work
@joshuous for all the help he provided to me in the past!
@arter97 for giving me advice
@kdrag0n for his help and advices!
@topjohnwu for magisk and his entire work!
Source Code: https://github.com/freak07
F.A.Q:
Question: How do I check the state of avb flags for verity/verification on my phone?
Answer: Check @capntrips post here and get the magisk module for this from here. After flashing the magisk module reboot your phone. You can now use the commands from @capntrips post to check.
Question: How do I update my phone to a new monthly update if this kernel is installed?
Answer: The easiest solution is to just use any full firmware package to update your phone to the new stock firmware. You can do so with the android web flash tool, a factory image or a full OTA image.
An excellent guide on how to use the factory image to do so was posted by @roirraW "edor" ehT on this thread. Feel free to use this as a reference.
I also posted what I do each month to update my phone here.
This also serves as the easiest way to return back to stock, if you don´t like the kernel and feel not comfortable flashing anything via fastboot.
Just remember to disable verity/verification vbmeta flags each time you update your phone as described in the next question below.
If you boot once, without them disabled a wipe is required to disable them again.
Question: How do I disable the vbmeta flags for verity/verification?
Answer: The easiest solution is to use the android web flash tool and tick the correct checkbox.
Alternatively extract the vbmeta.img from the matching factory image and flash it in fastboot via:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Please note that disabling those flags will require a full wipe for the device to boot if coming from flags enabled state!
And a further note: You need to repeat this command every time you flash a full firmware zip ( a factory image or a full OTA.zip) to update the firmware of your phone as those contain a vbmeta image. Otherwise the flags will be reset to default enabled and it will require another wipe to disable them again! As with the firmware.zips, you need to tick the checkbox in the webflasher every month you update your phone or flash a firmware there!
Question: How do I return back to stock?
Answer: Extract boot.img, dtbo.img, vendor_kernel_boot.img and vendor_dlkm.img from the matching factory image provided on googles download page.
Flash those images via fastboot/fastbootd and you will be back on stock kernel. If you don't know the fastboot commands to flash the images, check the instructions how to flash those images in post #4.
Alternatively dirty flash the whole firmware without wiping by using either the android web flash tool, a factory image or a full OTA image. If you disabled the vbmeta flags, don't forget to disable them again (or tick the correct options on the web flash tool) after flashing a full firmware package and re-root.
Kernel flasher has the capability to backup those partitions as well, but if your phone doesn´t boot, because you flashed a kernel for stable firmware on dev preview that backup will not help you.
Question: Does this kernel include a mod similar to the well known KCAL modification?
Answer: No it does not, as KCAL is tapping into a QCOM specific driver and that´s not included in the tensor source as it´s based on exynos.
There´s a very powerful app called CF Lumen from @Chainfire, that serves the same purpose and even includes far more options that were available from kernelspace. Link to the thread here.
Question: How to report bugs properly?
Answer: Have a look at post #3 in the linked thread. The linked guide is a pretty good starting point.
Before reporting any bug make sure you´re running on a supported firmware. Usually I'm announcing in the release post, the firmware the kernel.zip is compatible with, but most of the time the kernel is updated when a firmware update drops.
Please make also sure you're running a stock configuration.
That´s means you´re not using any mods, tweaks in kernel managers or other root tweaks , magisk modules, xposed/lsposed etc, scripts or other modifications that alter various functions like sound mods, data traffic, sleeping behaviour, scheduler, magical battery tweaks etc.
Try to describe the issue as detailed as possible! Give your exact setup, like rom, magisk version, kernel version.
Is the issue reproducible? Does it happen frequently?
Please make sure to meet the points described above, provide logs as detailed in the link above, otherwise debugging is a lot more time consuming and harder. (kernel flashing apps usually support exporting logs of flashes too) If these requirements aren´t met and I don´t find time to either reproduce the issue myself or I´m not able to reproduce the issue myself, reports might just be ignored. If you can already reproduce the issue and provide logs it greatly limits the amount of time I have to spent until I figure out how to reproduce it.
Question: What about unlocking, rooting, passing safetynet, apps detecting root/modifications and other topics that are vaguely related, but not really subject of this thread?
Answer: If you want to modify your phone via root/magisk in any way you need to unlock the bootloader. Unlocking will result in safetynet not passing. This has nothing to do with the kernel. At the moment of writing this, safetynet not passing can be worked around with a magisk module called "Universal SafetyNet Fix".
Not passing safetynet is unrelated to the kernel since hardware attestation is enforced on nearly all newly released devices now.
If you´re not passing safetynet banking apps might for example be detecting root. There are various tricks to hide root/modifications to the phone from banking apps or others but that´s not really subject of this thread.
I recommend taking a look at this excellent collection of helpful threads from @roirraW "edor" ehT!
It can be found following this link!
Question: I get a device corrupted message after flashing the kernel or just reboot to bootloader. How to get rid of it?
Answer:
There seems to be an issue with verity on Pixel devices that can trigger randomly. That means even if the expected hashes match the device refuses to boot due to this bug.
Short answer, flash magisk patched init_boot.img via fastboot, afterwards flash stock init_boot.img. That should clear this situation.
AOSP Build Environment and Standalone Kernel builds (monolithic builds)
I´m sure some of you followed the movement towards the Generic Kernel Image (GKI) and Qcoms adaption to it called QGKI.
You can find more information about GKI following this link.
What does that mean for custom kernels and this custom kernel?
The last few years the kernel on android devices was more or less compiled as a monolith. That means the kernel is in the zImage with all (most) drivers compiled inline.
However with GKI this changed. There´s the base kernel image while vendor/device specific drivers are compiled as dynamically loadable kernel modules.
On last years devices like the Pixel 5 (using a 4.19 kernel) and this years devices with SD888 on a 5.4 kernel base, there was the possibility to change the QGKI kernel back into a monolithic kernel image. (building the drivers that are on stock kernel external modules back into the zImage to end with a monolithic kernel)
On the Pixel 6 I wasn´t able to achieve this yet. Same goes for the Pixel 7. But during my tries I also wondered if maybe finally the time has come to follow suit, instead of trying to enforce old ways, when there´s a new way going forward.
What does that mean. This means that at this point the kernel is shipped as images that are to be flashed via fastboot. At a later stage I´m sure we can modify anykernel3 to allow flashing zips again, but at this early stage fastboot flashable images will be provided.
Those images can be flashed the same way the device is rooted, therefore I think everybody should be able to flash it easily since the device can´t be rooted any other way.
The kernel was compiled using the aosp kernel build environment. Information about it can be found on the documentation page from google.
This kernel needs to be compiled in the aosp kernel build environment just like the stock kernel. All necessary and modified repos are available on my github. Otherwise please refer to the aosp build environment and the instructions there.
Fastboot commands:
This serves just as a reference to restore the images via fastboot. This is not to install the kernel.
Flash the images in this order:
Boot to bootloader:
Either select Reboot to bootloader option via magisk manager, use the button combinations or run the following command while in the OS:
or type:
Code:
adb reboot bootloader
Now in fastboot flash boot.img, dtbo.img and vendor_kernel_boot.img
Commands:
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_kernel_boot vendor_kernel_boot.img
Now boot to fastbootd
Code:
fastboot reboot fastboot
Once in fastbootd:
Code:
fastboot flash vendor_dlkm vendor_dlkm.img
4. Reboot either via buttons
or by typing
Code:
fastboot reboot
5. Profit!
Prebuilts for custom roms.
last one I promise
So glad to see you here
Woowoo, let's GOOOO
Kiri is here! Thanks for this awesome kernel!
So unfortunately we´re at the moment out of ideas and options for the vbmeta verity/verification disable requirement. @tbalden and me tried a few things and failed with our final idea this morning, which worked on a similar device.
Maybe somebody finds a way so we can actually flash custom images with the avb/vbmeta flags enabled, but at the moment not. I didn´t want to delay the release any further so here we go.
I understand this is a pain for many, but unfortunately that´s how it is now. It was a pain for me too, because on the final test, we really hoped it would work, but we we´re trapped in the wipe ourselves.
Anyway, have fun everyone with the release. It basically includes everything from the Pixel 6 kernel, as they branches are similar.
Well this is awesome. Haven't modified my phones since Pixel 4 but this is very enticing
This made me smile. Loved your kernel on the P6P. So glad to see it available for my P7P.
QQ: Is High Brightness Mode (HBM) supported in this kernel?
nice to see you on here
I do hope its a firmware issue and next month update fixes issue and then workaround you guys been testing for flashing without disabling verity and verification works
@Freak07
Thank You very much for this kernel!
May I ask if this one from CleanSlate is included? How is this works?
VoLTE call properties patched in - no root/magisk needed for non supported carriers/countries and VoLTE calls.
Duuuuude! This kernel sounds amazing. And the Powerhint module? WHAT?!
Probably moving to the 7 Pro this weekend so this is very welcome!
Thanks
Edit: I'm a little confused: should we flash the zip as usual through EXKM/Kernel flasher or use the fastboot commands from post #4??
Because the OP also mentions the usual way of flashing...
Very excited for the kernel, thanks for your hard work!
Ghisy said:
Duuuuude! This kernel sounds amazing. And the Powerhint module? WHAT?!
Probably moving to the 7 Pro this weekend so this is very welcome!
Thanks
Edit: I'm a little confused: should we flash the zip as usual through EXKM/Kernel flasher or use the fastboot commands from post #4??
Because the OP also mentions the usual way of flashing...
Click to expand...
Click to collapse
I think that was just a copy and paste from the older P6 thread (also now deprecated for that device, from what I understand). Just use EXKM or Kernel Flasher and you'll be good to go!
Edit: and the companion zip in Magisk Manager. Whoops. In other words, you don't need to manually flash each image to install the kernel.
i5lee8bit said:
I think that was just a copy and paste from the older P6 thread (also now deprecated for that device, from what I understand). Just use EXKM or Kernel Flasher and you'll be good to go!
Click to expand...
Click to collapse
Nope,
The powerhint module was never actually depreciated, on P6 he was able to have it included in the kernel zip and it auto-installed into magisk at the same time.
That isn't working here at the moment so you have to manually flash it yourself again
i5lee8bit said:
I think that was just a copy and paste from the older P6 thread (also now deprecated for that device, from what I understand). Just use EXKM or Kernel Flasher and you'll be good to go!
Click to expand...
Click to collapse
Sorry, maybe I wasn't being clear: should I use quote #1 or #2 down there?
Freak07 said:
How to flash the Kernel:
1a. Make sure you tick all the requirements above
1. Download the kernel.zip (unified for both devices) and the correct powerhint module depending on your device (Pixel 7 = panther || Pixel 7 Pro = cheetah)
2. Flash the powerhint module via magisk manager as you would any other magisk module
3. Flash the kernel.zip via EXKM, FKM or kernel flasher. Root will be preserved.
4. Reboot and profit.
Click to expand...
Click to collapse
Freak07 said:
Fastboot commands:
Flash the images in this order:
Boot to bootloader:
Either select Reboot to bootloader option via magisk manager, use the button combinations or run the following command while in the OS:
or type:
Code:
adb reboot bootloader
Now in fastboot flash boot.img, dtbo.img and vendor_kernel_boot.img
Commands:
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_kernel_boot vendor_kernel_boot.img
Now boot to fastbootd
Code:
fastboot reboot fastboot
Once in fastbootd:
Code:
fastboot flash vendor_dlkm vendor_dlkm.img
4. Reboot either via buttons
or by typing
Code:
fastboot reboot
5. Profit![/SPOILER]
Click to expand...
Click to collapse
Ghisy said:
Sorry, maybe I wasn't being clear: should I use quote #1 or #2 down there?
Click to expand...
Click to collapse
The fastboot commands are for if or when you want to return to stock.
so yeah, i trying to build lineage os 20 to boot on both xperia 1 and 5, but right now it didn't boot. based on testers
here's the proof
xperia 5 :
https://github.com/lolipuru/device_sony_bahamut
https://github.com/lolipuru/vendor_sony_bahamut
xperia 1 :
https://github.com/lolipuru/device_sony_griffin
https://github.com/lolipuru/vendor_sony_griffin
kumano common tree :
https://github.com/lolipuru/device_sony_sm8150-common
https://github.com/lolipuru/vendor_sony_sm8150-common
kernel :
https://github.com/lolipuru/kernel_sony_sm8150
these tree is very different than currently tree, due to no longer rely on stock vendor. and camera already fix to works with newer android
first time i tried it give me black screen , with hwcomposer 2.4 not running. but with rebased tree it didn't boot at all (and both tree are rebased on same pdx206, which i currently own.)
without pstore or console ramoops it's hard to know the real issues
should i open donation to buy device (xperia 1 or 5 is fine, since it share same hardware) to fix the issues? (i already have tester, but seem like i need ramoops or console ramoops log for point out the real issues)
actually i didn't want to open for donation, until ferdian (who maintain xperia 1 twrp), told me to try)
I build kernel for griffin with both your kernel source and Sjll's kernel source.
I found a strange(?) thing: If I build kernel without "techpack/audio", everything works well expect audio (Yep, drop audio kernel so audio dead), but If I build kernel with "techpack/audio", then I got bootloop, surfaceflinger and hwcomposer dead.
This is TOO Strange.....I tested on my Xperia 1 (802SO), not only your kernel source but also Sjll's kernel source have this issue.
And another strange thing is that the kernel source is working well for bahamut (Xperia 5) :\
Okay, I just find that two strange things.So I guess here are something strange with Sony's Open Archive
Do you need dmesg or something else? I got griffin but I have no idea with this issue.
RealNoobKanger said:
I build kernel for griffin with both your kernel source and Sjll's kernel source.
I found a strange(?) thing: If I build kernel without "techpack/audio", everything works well expect audio (Yep, drop audio kernel so audio dead), but If I build kernel with "techpack/audio", then I got bootloop, surfaceflinger and hwcomposer dead.
This is TOO Strange.....I tested on my Xperia 1 (802SO), not only your kernel source but also Sjll's kernel source have this issue.
And another strange thing is that the kernel source is working well for bahamut (Xperia 5) :\
Okay, I just find that two strange things.So I guess here are something strange with Sony's Open Archive
Do you need dmesg or something else? I got griffin but I have no idea with this issue.
Click to expand...
Click to collapse
Sjll source have main issues,
first, it's mostly modify kernel with stock dtb (due to rom built "without" vendor at all, so it still using stock vendor)
second, even you manage to fix it. but most of blobs are pretty outdated now (espepcially camera blobs, you still need to do a manually patch)
i tried with full source build, yea. it booted but blacked screen due to hwc 2.4 isn't running at all. (when i was address all missing blobs, it doesn't boot)
* kernel is pretty fine, it can boot to twrp but i didn't want to use it (due to nature of a/b twrp, so it broke many things if you use with sjll source.) so i tell ferdian to do an installer script
i already have a chat with creamdraft and bbn about this, seem like that issues isn't easy to deal with