[Kernel][04.01.2021][4.14.213] Kirisakura 6.6.6 for Pixel 4/XL aka FLORAL

[rob_z11]

Any good app to access this forum now that since they have moved?

 

[Badger50]

Any good app to access this forum now that since they have moved?

Not until they release the new XDA app which hopefully will be soon. Until then, the new forum actually works pretty good using your mobile browser.

 

[Freak07]

Not until they release the new XDA app which hopefully will be soon. Until then, the new forum actually works pretty good using your mobile browser.

I agree, except for several months of content missing in all OPs of my kernels

It's faster as well. Hopefully all the bugs will be fixed

 

[RogerF81]

Puh, I really have to get used to the new design

 

[CROCOLR]

Hi, i have got Pixel 4(smaller), and I’m on latest version Android 11.
I want to install this kernel and the latest version of magisk,how do I have to proceed?
thanks...
I am on locked bootloader too

 

[rob_z11]

I agree, except for several months of content missing in all OPs of my kernels

It's faster as well. Hopefully all the bugs will be fixed

I think you still can get to the old content using browser, but not using the XDA app.

 

[rob_z11]

Hello Freak07,

I was able to get your kernel build using the method you have described into IMG to flash, and it was booted and everything works except no KCAL support and power HAL didn't get installed in magisk like you have mentioned in your OP page. Am I missing anything to get KCAL support? KCAL gives me bit of cold color that I enjoy..

 

[Freak07]

Hi, i have got Pixel 4(smaller), and I’m on latest version Android 11.
I want to install this kernel and the latest version of magisk,how do I have to proceed?
thanks...
I am on locked bootloader too

That´s not really subject of this thread. The initial step is to unlock your bootloader.
There´s a very good guide thread in the general section on how to unlock and root the phone, if I´m not mistaken.
Afterwards follow the guide in the OP.

I think you still can get to the old content using browser, but not using the XDA app.

Yes old posts are now visible in the thread when accessed via browser, however the OP misses several months of content. You can see when checking the links to the release posts in the OP. The last release was 6.2.4, which is now not present there along with any other changes made to the OP, since the link to the 5.x.x update, that´s still accessible there.

Hello Freak07,

I was able to get your kernel build using the method you have described into IMG to flash, and it was booted and everything works except no KCAL support and power HAL didn't get installed in magisk like you have mentioned in your OP page. Am I missing anything to get KCAL support? KCAL gives me bit of cold color that I enjoy..

Unfortunately the module for the powerhal change won´t be created when not flashed via the .zip method.
For KCAL access you have to install the CleanSlate Config app. Links to those apps can be found either in my thread or the cleanslate thread.

 

[Freak07]

Hey everybody,

So here´s the deal about the XDA Migration. While I welcome the change to basically get a faster and more modern forum there are also some problems that happened during the migration.

The biggest problem right now is that all of my OPs got reset several months back and I currently have lost the content of these months. That means all changes I added during that time (most obviously changelogs, but feature updates/additions etc, repair broken links) are missing completely.

It seems there is still work being done in the background, but all of those threads have not been repaired or showed any signs of changes during the last week while the migration happened.

I got not very clear replies when asking for help in the thread we all were supposed to reply to in case certain parts are broken or missing. I had hoped XDA would fix my threads in time for the security updates on the Pixels at least. But with today being patchday (probably), I don´t have high hopes it´s going to happen.

It´s unfortunate, because I think my OPs contain a lot more information or links when compared to other OPs. In the end this is a loss not only to me, but mostly the whole forums and its users. So I really hope it will be fixed soon.


But what I will do is the following:

I´ll just change the thread title to reflect the correct date and kernel version. I will not update the OP until there is clear information that either the content will not or will be restored.
I´ll just put a release post here in the thread once the new update for this months security patch is ready or I will update the kernel.

Until then I link the latest download here, which is 6.2.4 that is intended for November Firmware:

Kirisakura-FLORAL_6.2.4.zip | by Freak07 for Generic Device/Other

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

www.androidfilehost.com

The release post for 6.2.4 can be found here:

[Kernel][04.01.2021][4.14.213] Kirisakura 6.6.6 for Pixel 4/XL aka FLORAL

Kirisakura-Kernel for the Pixel 4 and Pixel 4 XL Hello everyone, After rising to the most popular kernel on the Pixel 3/XL forums, here is Kirisakura-Kernel for the Pixel 4 (FLAME) and Pixel 4 XL (CORAL), together FLORAL. Kirisakura - Kernel is...

forum.xda-developers.com

Once the release post for December Update is ready I´ll just post it here and update the thread title.

 

[Utini]

@Freak07 if you "only" need the text from the OP then you could try google cache or web.archive.org ?

 

[Freak07]

Update 6.6.0

Hey guys and girls,

Alright here´s the update for December. Quite a few changes. Google merged another round of linux-stable upstream it seems, which puts them now at 4.14.191. It´s nice to see google still follows this read, even though the pixel 4 xl is a year old device now.
There are a few more things merged in the December Update, we already had quite a while. For example freezer v2 backports.
Google worked on other parts of the kernel in December as well, so this is again a rather big kernel release.

Fix for WiFi on A11 custom roms is included as well.

I experimented a bit the last month, hence the rather big version bump. But it fits the feature drop and the size of the update quite well.

I wish everybody a great day.
Enjoy the device and the kernel, because I certainly do

Before troubleshooting and reporting any issues make sure to not use any additional mods, scripts or tweaks. This includes all mods, even the tiniest modification you did.

big thanks to all my testers again:

@Mrcactuseater
@MArtyChubbs @ilal2ielli
@toastyp @Alcolawl


Detailed changelog below.


Changelog:

Kernel Base

- Merge December Security Update
- Linux-Stable-Upstream to 4.14.210
- patches from kernel/common
- CAF Upstream merged
- Backport to enable CONFIG_HAVE_MOVE_PMD (see here) , thanks @arter97
- arm64: lse: Prefetch operands to speed up atomic operations, thanks @kdrag0n
- fix WiFi on custom A11 roms
- other changes please take a look at github

Magisk Module:
- Reintroduced with November 2020 Update. After flashing the kernel, you will see a module called AK3 Helper Module in Magisk Manager. This will fine tune the power-hal.

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

Why is linux-stable important?

I wish you all a nice day/evening!


Download is below

Download:


Kernel: https://www.androidfilehost.com/?fid=10763459528675599863



How to flash the Kernel:

1. Make sure you are rooted, are using the latest magisk suited for your OS version and a kernel manager capable of flashing a zip is installed. If available you'll can use TWRP as well. Download the kernel.zip to your device.
1a. If you used the SQLITE3 Magisk Module and the GPay Fix Magisk Module in the past (prior to 2.0.0) look at this post: click me

2. Flash kernel zip in via your favorite method. Kernel Managers and Recoveries need to be updated to work with a specific Android Version. It's your job to ensure compatibility! Root will be preserved! (Make sure to be on the latest firmware the kernel is made for)

3. Reboot and profit! Before reporting any issues make sure to read the first three posts of this thread!
Instructions can be found in the OP too!


Have fun, enjoy the kernel and your phone.


If you like my work please consider a donation.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea: http://paypal.me/freak07

 

[RogerF81]

Runs very well, as always! Thanks for your work @Freak07

 

[sylikc]

Update 6.6.0

Hey guys and girls,

Alright here´s the update for December. Quite a few changes. Google merged another round of linux-stable upstream it seems, which puts them now at 4.14.191. It´s nice to see google still follows this read, even though the pixel 4 xl is a year old device now.

@Freak07 thanks for getting to this so quickly! Less than a day after the official OTA update, WOW! and it's nice to see you're supporting this device actively even though it's a year old

Long live Pixel 4!

 

[sharpz811]

Does anyone who uses this kernel on stock firmware also own a pair of pixel buds 2? Any issues? I'm just trying to narrow down the current issue I'm having which I won't discuss in efforts to avoid spamming the thread unless someone asks lol

 

[murphyjasonc]

Does anyone who uses this kernel on stock firmware also own a pair of pixel buds 2? Any issues? I'm just trying to narrow down the current issue I'm having which I won't discuss in efforts to avoid spamming the thread unless someone asks lol

I do and haven't had any problems at all. I am curious about the problem though. PM me if you want to discuss.

 

[Freak07]

@Freak07 thanks for getting to this so quickly! Less than a day after the official OTA update, WOW! and it's nice to see you're supporting this device actively even though it's a year old

Long live Pixel 4!

You´re very welcome.
It´s still my daily driver along with the Rog Phone 3. Can´t decide between the 2 phones really. Ideally I´d like them to be fused together.

Does anyone who uses this kernel on stock firmware also own a pair of pixel buds 2? Any issues? I'm just trying to narrow down the current issue I'm having which I won't discuss in efforts to avoid spamming the thread unless someone asks lol

I do and haven't had any problems at all. I am curious about the problem though. PM me if you want to discuss.

@sharpz811 I´m using my pixel buds 2 just fine without any issues. the latest firmware update 552 fixed basically all the issues I experienced with them. though it´s around for quite a while so I´d assume you´re running it already.

What´s the issue you´re experiencing?

 

[Freak07]

I also updated the OP. All my threads were restored yesterday so we´re back on track now. Proper changelog etc.

 

[sharpz811]

You´re very welcome.
It´s still my daily driver along with the Rog Phone 3. Can´t decide between the 2 phones really. Ideally I´d like them to be fused together.





@sharpz811 I´m using my pixel buds 2 just fine without any issues. the latest firmware update 552 fixed basically all the issues I experienced with them. though it´s around for quite a while so I´d assume you´re running it already.

What´s the issue you´re experiencing?

Thanks for reply and I hope I'm not spamming but I'll be glad to tell you my issue. So basically this happens every single day at any given random time so things like location and environment have been ruled out. Here's exactly what happens. "Hey Google, text Nikki" (chime sound) "ok, What's the message?" (Chime sound) "how's your day?" "Here's what I heard, how's your day? Do you want to send it or change it?" Then there's no chime sound and the PIXEL BUDS disconnect from my phone for about 15 seconds then automatically reconnects. So I summon Google one again, "hey Google" (chime sound) "do you want to send it or change it?" Then it'll either disconnect again or it'll actually work like it should. I'm currently running the latest pixel buds firmware 552. On the latest December release for Coral and latest kiri kernel. All Google apps are up to date with the exception of YouTube vanced. I'm not saying it's the kernel but I've ruled out all other fixes and possibilities so now I'm just looking at the modifications I've done with my phone. I still don't believe it has anything to do with this amazing master piece that shouldn't be for free lol.

 

[Freak07]

Thanks for reply and I hope I'm not spamming but I'll be glad to tell you my issue. So basically this happens every single day at any given random time so things like location and environment have been ruled out. Here's exactly what happens. "Hey Google, text Nikki" (chime sound) "ok, What's the message?" (Chime sound) "how's your day?" "Here's what I heard, how's your day? Do you want to send it or change it?" Then there's no chime sound and the PIXEL BUDS disconnect from my phone for about 15 seconds then automatically reconnects. So I summon Google one again, "hey Google" (chime sound) "do you want to send it or change it?" Then it'll either disconnect again or it'll actually work like it should. I'm currently running the latest pixel buds firmware 552. On the latest December release for Coral and latest kiri kernel. All Google apps are up to date with the exception of YouTube vanced. I'm not saying it's the kernel but I've ruled out all other fixes and possibilities so now I'm just looking at the modifications I've done with my phone. I still don't believe it has anything to do with this amazing master piece that shouldn't be for free lol.

hmm I just tried the same a few times and all messages went through just fine. very strange issue though. I´ll try it a few more times over the next days and see if anything pops up.

if you want you can try to take a dmesg and logcat when the issue happens and send it to me either here or via pm.
maybe the logcat sheds some light what´s causing the issue. Though I´m not the best at reading logcat, so if anybody else wants to chime in here, feel free

the logcat preferably only when the issue happens. when connected via pc do

adb logcat -c

before

adb logcat

so we preferably only have that scenario on there.

 

[sharpz811]

hmm I just tried the same a few times and all messages went through just fine. very strange issue though. I´ll try it a few more times over the next days and see if anything pops up.

if you want you can try to take a dmesg and logcat when the issue happens and send it to me either here or via pm.
maybe the logcat sheds some light what´s causing the issue. Though I´m not the best at reading logcat, so if anybody else wants to chime in here, feel free

the logcat preferably only when the issue happens. when connected via pc do

adb logcat -c

before

adb logcat

so we preferably only have that scenario on there.

You sir are probably the nicest young man on the planet! This issue has nothing to do with your kernel considering no one else including has this issue yet your still out here helping me when you don't have to! Thank you so much @Freak07. As son as I get home and have time (gotta run errands lol) then I'll try to recreate the issue while generating a logcat.