yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jd1639:
A logcat could be helpful in determining where Kirisakura and blackenedmod aren't playing nice together. If someone could get that.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Please don´t report any issues when you´re running mods, be it magisk mods, scripts like blackened mod, other mods you found on XDA. I just cannot support them. If you´re using them and don´t actively face any issues it´s fine by me. But please don´t report issues.

Try it on a clean environment and see if the issue persists. Then head to post #3, gather me logs and give as much details as you can, what issue do you face, steps to reproduce!

This kernel is now far away from stock and many little tweaks are already changed in the kernel at compile time and will conflict with other settings set by other mods or scripts.

I´m running the kernel myself without any further mods that aim on improving battery life or perfomance. It is just not needed the way the kernel is designed. I get excellent battery life and performance on this device. I lose 1-2% over 7-8 hours overnight and easily get through the day even if I push the phone a lot. It just gets the job done.

I respect the work done on blackened mod and the many hours put into it. But I feared sooner or later one setting that is changed by the script will interfere with the kernel.

I´m for example not fond of changing the cpu sets. Google designed the cpusets and the EAS implementation around each other. They didn´t do it brainlessly and did not use just the standard setup. There are many small connections that correlate to these conjucntion.

Blocking wakelocks is also something I used to do myself quite a lot. But it doesn´t improve things in the end. It took me quite a while to come to this conclusion. The phone needs some awake time to get the job done. And Pie is now extremely efficient with it. Take a look at this article. It gives good insight on android, battery life, wakelocks and real day usage in correlation to wakelocks.

https://arstechnica.com/gadgets/201...sts-tracks-and-improves-android-battery-life/

Wakelocks should never be just blocked to "improve" battery life. They have a reason. If a wakelock requests the phone to be awake, it serves a purpose. And this purpose is not to deliberately destroy battery life. WLAN wakelocks for example are important, because you want to receive messages. If you block them maybe the data will get through with another wlan wakelock that doesn´t serve that purpose. So in the end nothing was gained.

The only valid reason for disabling wakelocks I can think of are firmware incompatibilities. If you´re phone is 100% of uptime held awake by (for example) a wlan wakelock caused by your router´s firmware you might be better of to block it. But not block a wakelock that´s active for 3 minutes of an 8 hour period.

If you block a wakelock and face an issue with the kernel it´s nearly impossible for me to debug it even with a log.

Maybe ask the authour of blackened mod for help. He is a very nice guy. Maybe he can isolate the setting that is causing issues with my kernel, but I cannot provide any help here. Sorry about it!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] hilla_killa:
Latest kernel working on dec update? I dont wanna go through my themes and all that again.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Pretty sure it should. No guarantee though. Make a backup of boot.img in twrp so you can easily restore! Be sure to report back if it worked out so maybe other can benefit too :svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Kernels (up to a point - don't expect a Pie kernel to work for Oreo) are relatively independent of the release version, they just happen to be released at the same time. So it should work.

Then again that's why the gods invented backups. But I'd still update to January, substratum themes probably won't be effected since all the app updates live in /data/

Edit: There's a ninja running around masquerading as a kernel developer! ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] newkydawg:
I'm on Dec build and 2.0.0 works great!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] hilla_killa:
So i can flash jan update without disabling my themes? It just took me a while to get my phone to look how i like
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] smartymcfly:
Scrolling is smooth for me.

On a side note, pretty much any app that is using a webview has been randomly refreshing without me refreshing and then going to the top of the page. I believe this began when I updated from December to January. Is anyone else experiencing this. This absolutely has nothing to do with kernel, just asking if anyone else getting this random refresh.?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
You should be able to. Make a backup, just in case - but I suspect you'll have minor, if any, inconvenience. (Just make sure you're not wiping /data/ so either sideload the OTA or run the factory image install after removing -w)

---------- Post added at 12:53 AM ---------- Previous post was at 12:51 AM ----------

Webview, by default, is using Chrome so updates to Chrome can effect webview performance.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rspkt:
Update to 2.0.0 went flawlessly. No issues at all from install to usage thus far.

My steps:

- Backup via Titanium Backup

- Boot to recovery for TWRP backup

- Reboot bootloader

- Restore stock boot.img to both slots

- Reboot to system

- Reboot to bootloader

- Flash TWRP 3.2.3-3 + Kirisakura 2.0.0 + Magisk v18.0 (all at once via "add more zips")

- Save logs

- Reboot

- Profit

Hope this helps anyone having issues. Thanks again for your hard work, Freak07!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Fwiw I just flashed Kiri 2 in TWRP and rebooted. Smooth sailing, Magisk modules running just fine
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] newkydawg:
I use EXKM to flash these kernels. Never had a problem and super easy....
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dukat0s:
Version 2.0 is the fatest and smoothest version I flash on my phone :)

Benchmark agreed for my sayings ?

Thanks for all your hard work

Really appreciate it [MENTION=3428502]Freak07[/MENTION]

??
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gogoffm:
On which Rom are you?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] swieder711:
Im on the Jan update with stock. 2.0 is running great.

Wonderful work. Thanks.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] suzook:
Running bootleggers rom, with 2.0. Battery life has improved drastically! Great job op.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcrompton:
"stock" settings after kernel install? or any changes?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] suzook:
Left everything alone, except for color controls.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jblanko6:
Hello, what app do you use to mess with the color control ?

Thanks.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
Probably Ex Kernel Manager?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] suzook:
Yup
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] hilla_killa:
Can confirm working fine on dec update. Thanks
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bemagrp:
Did anyone use print hand app? Couldn't connect to any printer after flash 2.0. Working fine with stock and elemental kernel.

Besides that, runs smoothly with no problem.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] evilryry:
Been a user since the beginning on this kernel and I love it!

However, with the last couple releases and the current one, I have started having random trouble with my camera. It will work fine and then when I go to use it again at some random point it will not work. By not work I mean, stock camera will be black front and rear camera and then the app will close itself after a few seconds. Any other app utilizing the camera will just open to a black screen. Reboot always fixes it till it occurs again. I am on the latest stock January build no mods besides the kernel. I didn't start noticing this issue till around the 1.9 build, possibly a little earlier I am not 100% sure, I don't take a ton of pictures. I didn't fully keep track of it timing wise because I thought it was a fluke little glitch but it's been consistent every 2 days or so now. Other than that everything is great. Is there anything I should try to resolve the issue with? Im not sure if it's kernel related or software glitch, I am only posting now because I know of past camera issues in the thread so I just wanted to see. Thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
No there were never camera issues in the past with this kernel. Just a few users complained about slow camera, laggy camera etc. This was the reason for the camera driver "update" which was released with 2.0.0.

If you faced the issues you are describing prior to 2.0.0, which you seem pretty sure of, it´s most probably not kernel related. The camera driver changes are only in there since 2.0.0.

I snap quite a few pictures and never experienced what you are describing. It´s probably a camera software fluke.

You could try to clear cache and data of the camera app and see if it still happens.

You could try a full wipe and see if it persists. Are you on stock or custom rom? Any other mods, such as sound mods, magisk mods?

If it happens again maybe try to gather a dmesg and a logcat shortly after it happens. That might be helpful! Information on how to do so are in post #3! :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TheMorpheus:
I'm on Proton Kernel and I want to switch to this one, do I need to flash stock boot.img before flash this?

Can I do it from twrp or I need a pc? Flashing stock boot.img will delete twrp?

Thanks
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jsauder2:
You probably don't have to flash stock boot.img but it would be a good idea. You can do that from TWRP, use the install image option instead of zip.

Flashing the stock boot.img will remove TWRP, so make sure you have the zip for that and flash it second.

Then flash this kernel and you should be good.

If you have magisk, flashing the stock boot.img will remove that, just a heads up.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] brandonpa:
I honestly do not remember the version I was using but I had a similar event with my camera that the program would just force close itself despite attempts to get into it. I ended up rebooting my phone a couple of times and it seemed to correct itself. Camera works great. Not sure why it happened.

---------------

Been using your kernal since the beginning and seems to be working great, thanks freak and I bought you a couple cups of coffee (I think, not sure who much coffee is where you reside).

It is sort of funny, I go into xda forums sometimes just to see if there is a update to this kernal....
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TheMorpheus:
If someone needs it, here is the steps I did:

Flashed boot.img + TWRP installer

Reboot to recovery

Flashed boot.img + TWRP installer (don't know if needed two times for the a/b slot)

Reboot to recovery

Flashed Magisk Unistaller + Magisk v18

Reboot to system

Reboot to TWRP

Flashed kernel

Reboot

Here is the boot.img for blueline Pixel 3 https://drive.google.com/open?id=1eGB2BboY3JHJGRZbUIpDbgsmg1tgPNKL
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] hilla_killa:
I never flashed stock between kernel flashs, i went from stock to ex to kiri back to ex then proton and finaal back to kiri without once flashing stock. No issues either! So either way your fine but you dont need that extra step
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ahh123:
I'm getting some random shutdowns since flashing 2.0.0. Any idea why?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
We need more information. What rom are you on, do you use any mods, scripts or other things besides the kernel?

Did you come from another kernel? did you restore stock boot.img?

Can you provide me a ramoops if the reboot occurs again? It has to be taken right after the phone reboots. Instructions are in post #3.

Earlier versions of blackened mod seem to have caused issues. Maybe you´re using it?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
if anyone else experiences anything similar, quickly go to EXKM app and take a dmesg and logcat in the tools section. Maybe the logs will provide a clue.

Thank you very much for the donation! It means a lot to me. It is also a reward if someone appreciates the work one does by saying nice and kind words like you just did!

Thank you very much for this, have a great weekend and enjoy the kernel!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] c_86:
I seem to be doing OK...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
This! ^

[MENTION=4011641]ahh123[/MENTION] If you maybe are using any older versions of BlackenedMod at the moment together with Kiriskura - update in that case to the latest release. It includes a "hotfix" (originally caused by me and my lust for experimentation beyond the borderland) that purges the reboot issues on Kiri all the way back to Siberia.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Looks like good results!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Guessing you were sleeping for a good part of this?

Still 5hrs sot and that much battery left is money
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] c_86:
Nope

Unplugged again 9am and using it until I posted that screen shot
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Impressive. What's your setup?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
I have had better off screen drain since I am using Greenify Magisk module (on my HTC U12+ sd845 Kirisakura kernel). Something like 0.5% per hour. The curb is nearly flat when I don't use the phone.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] c_86:
How. The module doesn't install...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gogoffm:
You also getting the downgrade message?

Edit: is there a difference between Magisk Module and App from Playstore?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] c_86:
Ya. Says my api is too high
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
Yes. I have got quite a boost in idle drain since I have added the Magisk module to the app I was using.

---------- Post added at 12:02 PM ---------- Previous post was at 12:02 PM ----------

I am on Oreo, maybe it doesn't work on Pie yet?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] smartymcfly:
What phone do you use? This is pixel 3 xl forum? There has never been anything except Pie released on it.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] c_86:
Exactly. Obviously in the wrong forum...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
I had mentioned I used Kirisakura kernel on an HTC U12 +

I didn't think Greenify module wasn't working for Pie.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
Damn

Flash and go or are you changing anything
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] c_86:
Nope no changes.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] David B.:
I have heard this elsewhere but I do not understand why this is the case. Aren't the proprietary blobs from here enough? - https://developers.google.com/android/drivers
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] c_86:
So taking off greenify has increased my stand by drain by about 15 Min's so far versus before.

Normal day drain wake would be under 1 hour over 17 hour day. However today I'm at over an hour 7 mins
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
[MENTION=3428502]Freak07[/MENTION] Are you still on DU?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
So you're on stock with Kiri and Greenify?

You on wifi all day with good reception?

Bluetooth on/connected?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] c_86:
Yesterday's was WiFi on all day connected about 90% of the days. Bluetooth is always on (android wear). Connection is decent normally

And I'm using DU Rom with Kiri and was using greenify. Just took it off on Monday night and ran all of Tuesday without it. Doing the same today.

Also note that I am running sys config on magisk
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
if it was just a matter of simply copy pasting blobs it would already work. As I understood it’s linked into system and would require a lot of reverse engineering.

somewhere buried on the pixel 2 xl forum is a good explanation.

yes i am :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Tomorrow the update with 4.9.152 and a few other improvements will probably be released :svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Update to 2.0.2

Hey guys and girls,

As promised here is 2.0.2 with 4.9.152 included! Several other changes included, which enhance experience further.

Changelog:

EAS and GPU updates:

EAS implementation got a few patches, which should help with performance and efficiency!

Disable autogroups and use only cgroups. This ensures enhanced task placement!

GPU profiling should be improved a bit as well.

General Changes:

We already used [MENTION=4800121]Sultanxda[/MENTION] ´s input boost for various scenarios.

Update the changes already made in the kernel to be inline with sultanxda´s latest release for pixel 3! Thanks to [MENTION=4800121]Sultanxda[/MENTION]

Bump minimal backlight, when using backlight dimmerd, a bit! Dimmest state as it was before was unusable, in case blacked out apps where used. (thanks to [MENTION=7291478]kdrag0n[/MENTION])

Security and stability:

Upstream to linux stable 4.9.152 Included

Stay inline with kernel/common 4.9

Camera driver:

Update the Camera driver again to the latest CAF state. This update dropped only a few days ago.

F2FS-Implementation:

- Improve Garbage Control (credits to [MENTION=4898097]arter97[/MENTION] !)

See here for details:

https://github.com/freak07/Kirisakura_bluecross/commit/e41097039890303163f45ab4ca541fb7c1f075f3

https://github.com/freak07/Kirisakura_bluecross/commit/adb98c5bf07d4217768b1e1578e4e96bca94929a

CAF updates:

Updates to various drivers!

UFS driver, display driver, TCP

And a few other things that can be found on my github :)

Important :)

All flashing errors are now fixed. If you experience the ramdisk error please take a look at the FAQ.

Have fun flashing and enjoy your device with latest linux-stable :)

Why is linux-stable important?

I wish you all a nice day/evening!

Download is below :)

Download:

https://www.androidfilehost.com/?fid=11410963190603908291

or following the link in the op to the correction version

Instructions can be found in the OP!

But look at this post too :)

Have fun, enjoy the kernel and your phone.

If you like my work please consider a donation.

Donations are not mandatory but very welcome.

If you like my work and want to buy me a coffee: http://paypal.me/freak07
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcrompton:
[MENTION=3428502]Freak07[/MENTION]

First of all thank you so much for the update. You sharing your work is greatly appreciated.

I saw some post to go that you apparently personally use DU. I was wondering if you have tried any of the other ROMs and if there was a specific reason why you settled on the DU. I always get a little nervous when I see foreign characters within a ROM

Feel free to p.m. me if you'd rather
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Golf c:
Best kernel for this device. And their is alot. Continuously impressed with devs growth. Kind, knowledgeable, and consistent. Rarely any bugs. Might have to break my ethic and donate some American cash. Not a big believer in money. But if anyone deserves my reciprocation it's this man.

Edit: I'm a kernel freak. Tried them all. No more custom roms. Done my time
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] alkeshgamer:
Thanks for the update will try it on my Pixel 3(blueline). One thing that's happening to me is that whenever I'm on a custom kernel, I experience random reboots - well, not exactly reboot also but the screen goes black for few seconds and I'm back to the lock screen with message saying "Unlock for all features and data" indicating that device rebooted and requires manual unlock rather than fingerprint. Initially I though it would be because of root or themes, so I tried removing magisk and substratum themes but the issue still persisted. So I had to go complete stock with flash-all. Then I kept the stock kernel with magisk and themes, here there were no random reboots. So from this I've come to find that it surely has something to do with custom kernel.

Now I'm not specifically targeting Kirisakura as I tried Proton kernel too, where I observed similar behavior. I'd like to help figure out and fix this issue. Currently I'm rooted with stock kernel, gonna try 2.0.2 and revert back with more details. Just to confirm what is needed to debug the issue is logcat, dmesg and ramoops, right?

Update:

Just after installing the kernel and rebooting to system, as soon as I unlocked the phone, in few seconds the screen went blank and it happened. Was unable to get the logcat but attaching the dmesg and console-ramoops-0 files I obtained.

Update 2:

Happened again, forgot to start Matlog this time, but attaching dmesg and console-ramoops-0
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Thanks for the kind words! :)

what do you mean by "foreign characters" within a ROM? I don´t get the hint or what you mean by this.

I build DU myself, whenever I feel I have a need for a new build, which is usually every month when the security updates drop. I like the approach the DU team takes on development, that it´s not overloaded with features and some members of the team helped me build it in the past when I faced issues :)

That doesn´t mean I don´t appreciate or don´t like the other ROM´s available here! It just fits my needs :)

Additionally my available storage on the PC is limited (cannot store the source of various ROMs) and besides developing the kernel, I don´t have that much time for ROM jumping ;)

Everyone should try available options and settle for what works best for the usecase!