I'll always love reading that x thing has improved with an update, flashing nowTest Release 1.0.5_6
Hey everyone,
so it seems the probability of the crash is greatly reduced again, but it can still happen. The problem is I don´t understand why it crashes exactly yet. I changed a few things again, which I suspect could be connected, but I´m relying on logs from you.
Also thanks to @ada12 who spotted a missing piece for teo util awareness, this should improve performance/efficiency starting with this test release as welkl.
Thanks to everyone for flashing all those tests, keeping up with me, providing logs and feedback! all of that is valuable to me, since I still can´t reproduce the crash on my end.
So I´d like to ask, just like the last time:
I´d appreciate if as much users as possible could flash and run this. (especially @michaely123)
I´d appreciate if those that suffered regular crashes before could flash as well.
In case you get a random reboot please zip up and share the contents of sys/fs/pstore once you phone booted up again just like so many did before, which is great for me to see!
Thanks to everyone flashing those tests and providing logs in case of a crash, you guys absolutely rock!
Development [Kernel][08.08.2023][Android 13.0.0]Kirisakura 1.1.3_Raviantah for Pixel 6/Pro aka "RAVIOLE"
- Thread starter Freak07
- Start date
wow, ive been getting crashes so frequently. will update to 5_6, the logs attached are for 5_3 just now
Hmm, might be a though one.
The Bluetooth driver on my kernel is exactly stock. Most stuff is happening elsewhere in the Bluetooth firmware though, just like radio.
Does this issue happen on stock kernel too?
I'd try to use better battery stats, maybe you'll see something more detailed than the kernel keeping the phone awake, maybe a specific kernel wakelock or a partial wakelock contributing to power manager etc.
Because if anything asks to keep the phone awake it will be always shown as the kernel does this, even when it's a service or an app. (in this case Bluetooth Hal/service most probably)
Framework/Hal/service asks for resources because it wants to do something so it thinks it can work properly and the kernel grants it. (the kernel can't know what's happening in userspace/framework)
Hmm, might be a though one.
The Bluetooth driver on my kernel is exactly stock. Most stuff is happening elsewhere in the Bluetooth firmware though, just like radio.
Does this issue happen on stock kernel too?
I'd try to use better battery stats, maybe you'll see something more detailed than the kernel keeping the phone awake, maybe a specific kernel wakelock or a partial wakelock contributing to power manager etc.
Because if anything asks to keep the phone awake it will be always shown as the kernel does this, even when it's a service or an app. (in this case Bluetooth Hal/service most probably)
Framework/Hal/service asks for resources because it wants to do something so it thinks it can work properly and the kernel grants it. (the kernel can't know what's happening in userspace/frframework
Thanks! I'm not sure if it's a problem on the stock kernel, I've been running your kernel since I bought the phone 7 months ago!
BetterBatteryStats is showing 2 kernel wakelocks that do not show up at all when BT is off:
odm:btbcm (100% of the time over a few min test)
bthal_wakelock (98% of the time over a few minutes test)
The wakelock times drop to 10-15% when BT is on but not connected to the problematic device.
I can block odm:btbcm with EX Kernel Manager's wakelocks blocker tool, but bthal_wakelock doesn't show up there! How can I try blocking it manually?
I've actually been blocking odm:btbcm for a few days now and although it's now able to sleep, it only sleeps about 60% of the time. If not connected to the problematic device I see sleep of 90-96%. I'm including this just as an aside as I shouldn't have to be manually blocking BT wakelocks! Hopefully we can figure out what triggers this or how to fix it permanently.
UPDATE: I left the phone connected overnight with odd:btbcm blocked and bthal_wakelock kept the phone awake 36% of the time. I have seen no downside to blocking odd:btbcm so far. Everything works like before.
Last edited:
I'm not sure if this gonna help, but did you try updating your headunit to the latest version ?Thanks! I'm not sure if it's a problem on the stock kernel, I've been running your kernel since I bought the phone 7 months ago!
BetterBatteryStats is showing 2 kernel wakelocks that do not show up at all when BT is off:
odm:btbcm (100% of the time over a few min test)
bthal_wakelock (98% of the time over a few minutes test)
The wakelock times drop to 10-15% when BT is on but not connected to the problematic device.
I can block odm:btbcm with EX Kernel Manager's wakelocks blocker tool, but bthal_wakelock doesn't show up there! How can I try blocking it manually?
I've actually been blocking odm:btbcm for a few days now and although it's now able to sleep, it only sleeps about 30-50% of the time. If not connected to the problematic device I see sleep of 90-96%. I'm including this just as an aside as I shouldn't have to be manually blocking BT wakelocks! Hopefully we can figure out what triggers this or how to fix it permanently.
You can check these links :
Alpine - Headunits
Alpine - Bluetooth Compatibility Charts
I'm not sure if this gonna help, but did you try updating your headunit to the latest version ?
You can check these links :
Alpine - Headunits
www.alpine-electronics.co.za
Alpine - Bluetooth Compatibility Charts
Thanks for the suggestion. It's already been updated to the latest version (1.5).
Ok, here i am.
Back again and trying to figure how to flash kiri kernel. Been debating for months, but now that ProtonAOSP is finally dead i went back to Stock.
Just flashed latest A13 tq2a (stable) extracted 'boot.img', uploaded it to the phone and patched it using magisk.
I put the patched img back on my computer and used 'fastboot boot boot.img', but i can't get temp root so that i can flash it using an app, since manual doesn't seem to be a thing anymore.
Output goes like
It just won't accept the boot.img. I heard about fastboot/adb changes incoming, so is this it?
after all i need root (at least temp) to be even able to flash it in the 1st place. kinda feel like what was there first,... the egg or the hen?
i must've missed something and granted, it's been a while so plz bear with me and help me out on this one.
regards
Back again and trying to figure how to flash kiri kernel. Been debating for months, but now that ProtonAOSP is finally dead i went back to Stock.
Just flashed latest A13 tq2a (stable) extracted 'boot.img', uploaded it to the phone and patched it using magisk.
I put the patched img back on my computer and used 'fastboot boot boot.img', but i can't get temp root so that i can flash it using an app, since manual doesn't seem to be a thing anymore.
Output goes like
Code:
.\fastboot devices
18211FDF60020H fastboot
.\fastboot boot boot.img
Sending 'boot.img' (65536 KB) OKAY [ 1.449s]
Booting FAILED (remote: 'Unrecognized command boot')It just won't accept the boot.img. I heard about fastboot/adb changes incoming, so is this it?
after all i need root (at least temp) to be even able to flash it in the 1st place. kinda feel like what was there first,... the egg or the hen?
i must've missed something and granted, it's been a while so plz bear with me and help me out on this one.
regards
Are you in fastboot mode or fastbootd mode ?
To be sure do this :
Code:
adb reboot fastboot
phaino00
Senior Member
You have to patch the boot image in magisk first and then flash the magisk patched image in fastboot to gain root.
The command is "fastboot FLASH boot xxx.img" , where xxx is your patched image - something like magisk_patched-26101_AAAAA.img.
Then reboot, let magisk update everything, then reboot and flash this kernel.
Last edited:
you use updated fastboot tools in computer ? here from fastboot & fastbootd command fastboot boot boot.img work
kevp75
Recognized Contributor
tx to everyone that took the time to reply to my post. actually i can only think of me doing the wrong things (what else). i just took a chance and flashed the patched bootloader and i had root. What'S life without taking risks,eh?
And after that i flashed kranul (kernel i know). all seeme to be working so far. now i need a few days to see how it feels (smoothness, battery etc). so far i can't say anything negative.
regards
Hey guys, I really need your help. My Pixel 6 Pro just started freezing up after booting. I think it's probably unrelated to this kernel so I started another thread. Please have a look:
forum.xda-developers.com
[HELP] Pixel 6 Pro freezing shortly after booting [SOLVED]
Hey guys, Need some help troubleshooting what's going on with my Pixel 6 Pro. Short version: It's freezing up ~30-60s after booting and unlocking the phone, and then soft-rebooting some time after. If i don't unlock the phone it doesn't...
forum.xda-developers.com
Last edited:
Test Release 1.0.6_3
Hey everyone,
so it seems the last test finally got rid of the issue. No more crashes reported.
This release adds some of the stuff back I removed in order to being able to better understand the crash. If I´m correct those pieces of code which are added back now should not be responsible for the crashes.
So please everyone: Flash, test and report back. Especially those that suffered from the crashes in the past.
Thanks to everyone for flashing all those tests, keeping up with me, providing logs and feedback!
Without all the logs and users willing to flash and help I´d have never been able to debug this.
So I´d like to ask, just like the last time:
I´d appreciate if as much users as possible could flash and run this. (especially @michaely123 )
In case you get a random reboot please zip up and share the contents of sys/fs/pstore once you phone booted up again just like so many did before, which is great for me to see!
Thanks to everyone flashing those tests and providing logs in case of a crash, you guys absolutely rock!
Hey everyone,
so it seems the last test finally got rid of the issue. No more crashes reported.
This release adds some of the stuff back I removed in order to being able to better understand the crash. If I´m correct those pieces of code which are added back now should not be responsible for the crashes.
So please everyone: Flash, test and report back. Especially those that suffered from the crashes in the past.
Thanks to everyone for flashing all those tests, keeping up with me, providing logs and feedback!
Without all the logs and users willing to flash and help I´d have never been able to debug this.
So I´d like to ask, just like the last time:
I´d appreciate if as much users as possible could flash and run this. (especially @michaely123
)In case you get a random reboot please zip up and share the contents of sys/fs/pstore once you phone booted up again just like so many did before, which is great for me to see!
Thanks to everyone flashing those tests and providing logs in case of a crash, you guys absolutely rock!
No issues for me at all on 1.0.6.3 but I also stopped having reboots 2-3 updates ago after resetting EXKM and freezing it after flashing the kernel.
Top Liked Posts
-
There are no posts matching your filters.
-
6
I was feeling brave, so jumped ahead anyway.
If anyone else was thinking about trying, I can confirm that the 1.1.3 kernel works with the latest September stock firmware update and Magisk canary 26301.1So the rumor is that the Pixel 8 may run significantly cooler (please lord be true)
What are the chances we see kirisakira over there? Haven't run a single pixel without being spoiled by your work I think ever1 -
121Kirisakura-Kernel for the Pixel 6/Pro
Hello everyone,
To keep it short: Here is Kirisakura - Kernel for the Google Pixel 6 Pro aka Raven and the Pixel 6 aka Oriole, together Raviole.
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.
The kernel includes a lot of improvements and contributions from other developers as well. Without this kernel would not exist.
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
- Linux-Stable-Upstream included to 5.10.188
- Compiled with prebuilt Google clang 17.0.3
- 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
- make TEO-Cpuidle util-aware (improves latency, performance and decreases energy consumption for certain workloads, more information here)
- introduce runnable boosting, wire it up with pixel_sched
- FHD Support for Pixel 6 Pro (display is able to run at 1080p), more info here and here
- 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
- improvements to uclamp, prevent capacity inversion (reduce missed frames)
- greatly speed up camera launch time!
- Utilize an additional kswapd thread to increase throughput for memory reclaim
- 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
- improve trusty driver performance which connects to fingerprintscanner-hal by using high perf wq during fp unlock
- restrict maximum CPU-Freqs during screen off/ idle to 1.1GHZ 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 updates from linux-main
- use improved energy model for exynos cpu cooling/thermal control
- allow GPU to scale down to 150mhz, but boost to higher value in case of interaction via powerhal
- 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
- Include LRNG, see here and here for more info, bump to v45 with 3.0.0
- important patches from kernel/common for 5.10 (here are more details)
- 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)
- dirty pipe exploit fixed
- supports direct usb access for hi-res playback over USB-C DACs
- 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
Various Optimizations:
- update several drivers to use power efficient workingqueues (for example wlan driver)
- kernfs: use buffer from the stack space
- printk: use buffer from the stack space
- kthread: use buffer from the stack space
- bpf: avoid dynamic memory allocation for small value buffers
- binder: Reserve caches for small, high-frequency memory allocations
- kernfs: use kmem_cache pool for struct kernfs_open_node/file
- cgroup: use kmem_cache pool for struct cgrp_cset_link
- f2fs: reduce timeout for uncongestion
- f2fs: Demote GC thread to idle scheduler class
- f2fs: set ioprio of GC kthread to idle
- mm: vmstat: use power efficient workingqueues
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
AK3 Helper Module:
- restrict little cluster to 1,19ghz mid cluster to 1,19ghz and big cluster to 1,1ghz during screen off, to reduce battery usage for example during music playback
- only use little cores during screen off/device suspend
- 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)
- dynamically adjust target load for memory interface during interaction
- boost memory interface controller during interaction (decreased missed frames, improved soc efficiency according to google docs)
DOWNLOAD:
Download is always located in this folder:
4.2.0, 4.3.0, 4.4.0, 4.4.1, 4.4.2 are attached to the release posts linked below as AFH is wonky at the moment.
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes...www.androidfilehost.com
Changelog:
Android 12.0.0
1.0.0 Initial Release
1.0.2 https://forum.xda-developers.com/t/...r-pixel-6-pro-aka-raven.4358435/post-85910621
1.0.5 https://forum.xda-developers.com/t/...r-pixel-6-pro-aka-raven.4358435/post-85924419
1.3.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-85976139
1.4.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86109665
1.5.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86259863
1.7.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86390563
1.8.4 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86541727
Android 12.1.0 Stable (March feature drop and more recent)
2.0.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86617873
2.0.1 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86637233
2.1.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86695911
2.3.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86821331
2.4.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86834981
Android 12.1.0 Stable (June feature drop and more recent)
3.0.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86992705
3.0.1 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86996237
3.0.17 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87127695
Android 13.0.0 Stable (not QPR beta!)
4.1.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87290247
4.1.6 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87399635
4.2.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87524609
4.3.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87697425
4.4.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87823333
4.4.1 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87944879
4.4.2 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-88118201
Raviantha 1.0.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-88316223
Raviantah 1.0.2 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-88399941
Raviantah 1.1.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-88645115
Raviantah 1.1.2 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-88719665
Raviantah 1.1.3 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-88847787
Android 12L QPR Beta - Deprecated
Build for Android 12 QPR Beta: https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86857033
Requirements
- the kernel is made for the stock firmware provided by Google, pay attention to flash a kernel release matching the firmware (flashing on custom roms might work, but you may need workarounds!)
- 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 stable in case you want to be absolutely safe)
- IMPORTANT: Unrelated to the kernel, but update both slots of your phone to A13! (take a look here)
How to flash the Kernel:
1a. Make sure you tick all the requirements above
1. Download the correct kernel.zip depending on your device (Pixel 6 = oriole || Pixel 6 Pro = raven)
2. Flash the correct kernel.zip via EXKM, FKM or kernel flasher. Root will be preserved. The AK3 magisk helper module will be automatically installed during flashing the kernel.zip and be present on next reboot.
Do not remove or disable the AK3 Magisk Helper Module otherwise the device will bootloop.
3. Reboot and profit.
Manual installation is no longer supported starting with release 3.0.0, as there´s a free open-source option to flash kernel.zips now.
Instead use the free kernel flasher, which can be found here.
Manual installation without relying on paid apps like fkm/exkm:
Please have a look at the linked post.
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 pixel 6!
@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/freak0744Update to 4.1.0
Hey guys and girls,
I hope everyone started into a good week. Here´s the next release. It´s for stable Android 13.
Thanks to Google releasing the kernel source for the previews and the betas I´m able to push this update out very quickly. As in the past, the code didn´t change between last beta and stable release.
There are again a lot of changes in this release. I´ll try to keep the release post short as I don´t have that much time lately.
FHD/1080P Support for Pixel 6 Pro
The biggest change is FHD support for the Pixel 6 Pro. If you follow twitter you might have seen this tweet from @MishaalRahman.
Instead of using the display driver that´s supposedly for the Pixel 7 Pro, FHD support was added to the Pixel 6 Pro display driver. There were a few obstacles to make it run properly on the Pixel 6 Pro, but I got it working nicely so far. If anyone has more experience than me regarding panel timings, display drivers etc, feel free to push any improvement as a pull request to my github or point me towards any improvement.
As a result you can now select 1080p resolution from settings after flashing the kernel. Dynamic refresh rate works, brightness scaling works, no tints, colour shifts or contrast issues either. AOD has a 1080p Low-Power timing as well.
You´ll find a few more infos with a short video on my tweet here:
It´s perfectly usable on a daily basis so far. I ran it for a few days without issues on my end. While the advantage might be debatable (saving battery, less load on GPU, still needing to drive the same amount of pixels in the end even on lower resolution, etc etc) having options is nice and this is why I decided to ship it.
Apps need to redraw after switching resolution, sometimes 1080p on big display size selected in settings the UI looks a bit sketchy. So I think Google is still working on that.
There´s however one bug I found so far that makes me believe this is still very much a WIP from google. If having the "show current refresh rate" option from dev settings enabled while switching resolutions, the display will black out and a restart needs to be forced by keeping the power button pressed or using adb interface to restart the phone. This is not due to the kernel, but display settings in framework getting scrambled as it´s not yet implemented 100% on googles end. So be warned.
MM Subsystem Rework
MM subsystem was completely reworked including many improvements from linux-mainline. During this MGLRU was also reworked a bit and works better now. I´ll include links to a few of the improvements/patchsets in hide-tags below, if you´re interested beyond that please check out my github.
links:
Additionally tie in a few of the MM changes into the powerhal. For example Proactive compaction is more aggressive during screen-off/device suspended operations to improve long term-performance.
Other changes:
Also tune the powerhal and implement all A13 changes, according to the changes that were already present on A12.
Latest changes from f2fs-stable are included, which include several bugfixes and small improvements.
Binder improvments/fixes, scheduler improvements from kernel/common, performance for exfat formatted storage device improved (niche use case, but still nice) and other little improvements.
For other changes and details please take a look at github.
I wish everyone a nice day.
If you´re one of the unfortunate ones that suffer from the device is corrupt bug on pixel 6 series please take a look at the FAQ at the beginning of this thread it contains a solution. The issue is probably caused by a bug that affects pixel 6 devices and has nothing to do with magisk or a kernel, it just happens to get triggered when using any of those.
Changelog:
- Rebase kernel fully on A13 trees
- Linux-Stable bumped to 5.10.136
- FHD/1080p support for Pixel 6 Pro
- all previous features and improvements kept intact
- bump f2fs-stable to latest available
- rework mm subsystem (check git for more details)
- scheduler improvements
- binder improvements from kernel/common
- improve exfat performance (if someones uses exfat formatted devices)
- loads of other changes from kernel/common
- update powerhal to account for a13 changes and port existing changes over
- loads of other changes, please check github
Download:
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes...
If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img before flashing. Thank you.
I wish everybody a great day/evening!
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/freak0743Update to 4.2.0
Hey guys and girls,
I hope everyone started well in the new week. Here´s the next release and it´s a rather big one with lots of under the hood improvements.
We already had all the changes in from the October security patch release released, due to merging linux-stable stable and kernel/common in advance.
The kernel is now at 5.10.146 way ahead of the stock kernel. To further emphasize the importance of this. About 90% of kernel security issues are solved in linux stable. While I didn´t check the actual number myself, I´d have estimated about the same (80-90%) before actually reading the slides from @arter97 presentation.
What also needs to be kept in mind is that a big part of those security issues are resolved in linux-stable sometimes months ago before those patches end up in a monthly security patch. Additionally to that the security patches are about 3 months behind the discovery of those vulnerabilities.
Amongst linux-stable upstream there are a few other not minor updates in this kernel.
Clang
The kernel is now compiled with the latest prebuilt Clang from Google. This was quite a journey as this is a pretty big update to clang. This is quite experimental to be on googles side of a "bleeding" edge compiler, but after fixing several issues that originated from the new compiler it ran stable for over 2 weeks.
There´s a potential for CFI failures that originates from that new Clang rather than a "real attack", due to the changes in clang.
Short reminder what CFI actually does: Control flow integrity (CFI) is a security mechanism that disallows changes to the original control flow graph of a compiled binary, making it significantly harder to perform such attacks.
A typical crash (that´s not wanted and originates from compiler changes rather than an actual attack, which is already resolved of course ) would look like the following: Open camera app, due to compiler changes CFI is accidentally tripped every time this code is executed.
I think we catched all of these newly CFI failures and everything is nice and stable. In case you discover such a behaviour please send me the contents of sys/fs/pstore, once the phone booted back up.
There´s always the possibility of a "real" attack in which CFI will crash the phone, before the attacker can compromise the phone. That´s why keeping subsystems updated is important.
Powerhal
The powerhal was retuned due to changes to the scheduler introduced. It should work even better now, regarding efficiency and performance. Of course I try to tune it also to my personal needs, while trying to keep it working for all workloads. The changes are not drastic, so please don´t post after several hours you see drastic differences.
Other improvements
Several other improvements from kernel/common (for higher branches than 5.10) and linux-main were backported to this branch so we can benefit from those improvements. For details please check my git.
I´d like to write all of this with more detail, but at the moment I lack the time to do so.
Kernel is compiled for stable A13, not A13 QPR Beta!
I wish everyone a nice day.
If you´re one of the unfortunate ones that suffer from the device is corrupt bug on pixel 6 series please take a look at the FAQ at the beginning of this thread it contains a solution. The issue is probably caused by a bug that affects pixel 6 devices and has nothing to do with magisk or a kernel, it just happens to get triggered when using any of those.
Changelog:
- Linux-Stable bumped to 5.10.146
- kernel is compiled with latest prebuilt google clang 15.0.2
- improvements from linux-mainline
- locking subsystem
- memory management
- more details please check github
- updates from kernel/common to several subsystems
- tweak powerhal for improved performance/efficiency
Download:
Attached to release post as AFH is currently down.
I´ll push to AFH once it´s back up.
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes...
If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img before flashing. Thank you.
I wish everybody a great day/evening!
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/freak0737Update to 1.8.4
Hey guys and girls,
So here´s the next update. It´s kind of an off schedule update, as I planned to update the kernel with the next security update/feature drop.
But in the light of recent events regarding the new exploit called "Dirty Pipe" (more info here), which is similar to the "Dirty Cow" exploit from a while ago, but easier to exploit this time, I decided to release an update ahead of schedule.
This exploit was fixed in linux-stable 5.10.102, as opposed to a single commit in AKC (android kernel common, commit here). This shows once more why merging linux-stable is beneficial as explained in detail in the OP.
Since one of the key aspects of this kernel is security and staying on par with upstream (which often fixes exploits way ahead of android security bulletin updates, even before an exploit is even known or fixed via a patch on the security bulletin) I decided to release this update as quickly as possible, so this exploit is fixed on devices running this kernel.
Several other notable improvements and changes in this release:
Bring in scheduler updates from Android 13 Developer Preview, which aim at improving task placement. (adjust powerhal accordingly)
BFQ IO-Sched is now on par with linux-mainline.
Several fixes to mm subsystem, f2fs and others.
Several other improvements are included as well. More details in the changelog.
Download is below.
Updated instructions in the OP!
Changelog:
- linux-stable 5.10.103
- contains fix for the dirty pipe exploit
- built with clang 14.0.2 prebuilt by google
- improvments from kernel/common
- fix memory leaks
- security related patches
- mm improvments
- f2fs fixes
- scheduler fixes
- for details please check github
- built with improvements from A13 Dev Preview to display driver
- other changes please look at my github
Download:
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes...
Instructions can be found in the OP! Please follow the instructions to avoid any issues.
If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img before flashing. Thank you.37Update to 1.7.0
Hey guys and girls,
So here´s the next update. It includes the february security update. Most of the changes brought by the February kernel source drop, were already included in this kernel by merging kernel/common and linux-stable.
Several other notable improvements and changes in this release:
Improve f2fs performance by merging a patchset to prevent writer starvation for the checkpoint thread. This was discussed this month in the f2fs mailing list and is already merged to the kernel/common tree. It´ll improve performance under heavy I/O utilization.
You can find more information following the discussion here.
Necessary backports were brought to the kernel and the platform specific f2fs-implementation was also adjusted.
Latest f2fs-stable was also merged to the kernel.
Update the patchset to prevent frequency spikes caused by small tasks as well. Tie those new changes into the powerhal. (That means users not flashing the kernel.zip, but instead use the manual installation method, which are only a handful from the download count, need to flash the updated magisk helper module. Users that flash the kernel.zip via FKM/EXKM have to just flash and forget)
Several other improvements are included as well. More details in the changelog.
Download is below.
Updated instructions in the OP!
Changelog:
- February Security update merged
- linux-stable 5.10.96
- include latest f2fs-stable
- improvments from kernel/common
- fix memory leaks
- security related patches
- mm improvments
- for details please check github
- introduce unfair f2fs rwsems to prevent writer starvation and improve IO perf
- update patchset to prevent freq spikes caused by small transient tasks (also tie this into powerhal)
- give pelt multiplier power hint for scheduler performance boost during fingerprint unlock
- 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
- update LRNG implementation (thanks to arter97 )
- improvements/fixes for CleanSlate features
- other changes please look at my github
Download:
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes...
Instructions can be found in the OP! Please follow the instructions to avoid any issues.
If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img before flashing. Thank you.
