yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
A kernel with 4.9.165 included will probably drop later today :svetius:

[MENTION=668224]GollyJer[/MENTION] I sent you a pm regarding your request.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Hey guys and girls,

As announced earlier today here is the next release. It includes 4.9.165 and a few other fixes, changes and improvements. Details in the changelog.

Have fun flashing and a nice day everyone :)

Changelog:

- Linux-stable bumped up to 4.9.165

- Reworked f2fs integration (fixes two kernel WARNs)

- Sync f2fs with Google Q source drop

- Merge latest f2fs commits from the stable f2fs repo (tested for over a week and stable!)

- Remove rapid GC, use default f2fs implementation instead (quite some improvements in the not so far past, hence the switch) but might be reintroduced at a later stage again

- Remove RT patch from CAF (picked in a few months ago) in favor of Googles solution (dropped in Q source code)

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=1395089523397924999

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] c_86:
Edit

Nevermind. I'm an idiot
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Jiggs82:
You a beast lol thanks as always [MENTION=3428502]Freak07[/MENTION]
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] SinisterXReaper:
Another great update. No issues thus far, all is smooth. I appreciate all of the hard work you put into giving us a great kernel!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] NOTilyass:
Why is it so damn laggy on pubg and yet it was silkly smooth playing on my previous phone the OnePlus 6 ?! They both use the snapdragon 845 with a 1080p screen ?! And the UI on the pixel 3 is tremendously smoother than op6 ! So why cant this goddamn phone run pubg without lagging ! I am using smooth+extreme settings to get the 60fps going ! I am seriously considering going back to the op6 ! Please help ?!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Bryanx86:
Well there's twice the ram on op6, maybe that's it? But I'm sure the kernel has not a thing to do with it.? Thanks [MENTION=3428502]Freak07[/MENTION] for the great kernel and fast updates. Always appreciated.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] NOTilyass:
Funny enough I just tried the last sultan kernel and it magically fixed the pubg lag ! Sure the phone is a bit hotter but nothing that bad !
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Bryanx86:
Well good deal then, there's your solution
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 1002776470@qq.com:
每当运行pubg的时候刚开始很流畅，然后在手机发热之后就会掉帧，可不可以增加一个游戏模式，我测试过是因为发热降频导致的游戏帧数下降---我是一个中国新手
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] c_86:
Delete
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
You’re not correct. Only the OP 6/T has a 1080p screen.

OP 6: 1080 x 2280 pixels

Pixel 3 XL: 1440 x 2960

That’s nearly double the amount of pixels.

Glad you found a solution :svetius: Looking at the git from sultan kernel max frequency is capped from 2,8ghz to 2,5ghz because freqs above 2,5ghz may actually perform worse (performance not efficiency wise) than 2,5ghz according to sultan.

maybe that’s your solution.

Could be also due to a bit less aggressive throttling. Every degree the phone is hotter, shortens the lifespan of your battery by a bit. Since the pixel 3 xl has a battery, which is not so easy to replace, it may be good to keep that in mind.

you’re very welcome :svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] geeksammao:
Just be curious, Sultan seemed to add many improvements recently, what do you think about them and will you merge them?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] old_fart:
I too would like to run hot and cold. . Maybe a toggle to flip back and forth between two modes. . A dummy switch because I'm a dummy... . :) . When I know I will be running something demanding that'll make it hot. I'll be sure to grab a squishy, blue-ice bag out of the freezer to plop the 'thermally challenged' hardware down on the cold pillow.

As far a 'poor' hardware design that can't handle the heat... . Maybe the google engineers will get it right on the 'pixel 4' ? ? ? . . . . Maybe ? ? ?

But I bought this thing for the camera.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
With FK Manager you can set maximum CPU frequency per app.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
[MENTION=3428502]Freak07[/MENTION]

Any idea what this is?

Keeps coming up in kernel logger

[ 253.285413] HTB: quantum of class 10010 is big. Consider r2q change.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Some of them.

Yes you can do that indeed. Just keep in mind the powerhal will reset the maxfreq eventually to another value on certain actions like screen on/off. So if you check used frequencies you might see frequencies used you excluded.

It´s a warning from net scheduler. Nothing to worry about. It occurs on stock kernel and my U12+ to which is also running a 4.9 kernel.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Update

Tomorrow morning a new update will probably drop, which will have 4.9.166 included.

Also a few other goodies. A few commits from sultan will be included as already mentioned. (not the ones that limit the device to 2,5Ghz)

Quite a few binder patches from kernel/common. binder is basically responsible for processes communicating between each other.

Here´s more info:

https://elinux.org/Android_Binder

see you all tomorrow/today! Have a good day/night!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
oh ok

im curious, can we stop all kernel logs? may it improve CPU-over head?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Update to 2.1.3

Hey guys and girls,

As announced here is the next update :)

It includes 4.9.166 as well as binder updates and more upstream goodies from kernel/common.

Included are a few optimizations from [MENTION=4800121]Sultanxda[/MENTION] as well.

Have fun flashing and a nice day everyone :)

Changelog:

- Linux-stable bumped up to 4.9.166

- Binder patches from kernel/common

- Upstream patches from kernel/common

- Changes from [MENTION=4800121]Sultanxda[/MENTION]:

- mm: Boost when memory pressure becomes high

- kernel: Improve performance critical IRQ framework

- improve touchscreen driver and hopefully enhance touch latency

- touchscreen: sec_ts: Fix horrible strncat usage

- Boost whenever a zygote-forked process becomes a top app

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=1395089523397927638

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] Paz9:
Testing now
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] qualitymove13:
Will this work on Q? I am about to root now that I see Magisk now has Q support.

Edit: Magisk not ready for 3/XL just yet but its not close.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Jiggs82:
Yes it will
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
No this kernel will not work on Q! even if root for Q existed at this point.

Search the thread. I mentioned it in the release post when the Q merge happened and I also mentioned that there probably won’t be a kernel that can boot pie and Q at the same time due to substantial internal changes on Q!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Jiggs82:
Oh ok my bad
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TheMorpheus:
I've update my Pixel 3 to the last DU rom and then I've flashed 2.1.3, rebooted the phone and everything seems to work fine until the touchscreen stops working... I thought it was the last version that had a problem so I've flashed 2.1.2 (that I was using without a problem before updating the rom) but same problem. I had to re-flash the rom to get the phone working again. How can I be useful? How can I take a log considering that the touch isn't working?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 12Fully:
I've had random times where Magisk is usually the culprit. If it is, leaving your screen on for like 15-30 seconds while Magisk boots will fix it. Don't shut your screen off right after boot.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] muttonhead411:
Thank you for your work. Love this kernel
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Yes it’s a kernel boot order/magisk timing issue unfortunately. Sometimes it happens to me too.

Just force reboot your phone with the buttons or connect it to a OC and do “adb reboot” in case it happens. Watch it boot and when lockscreen appears just touch the screen and let it on for 2 minutes. Problem shouldn’t occur then. I think the probability of this happening increases with some modules like vanced Youtube.

Hopefully that helps.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TheMorpheus:
Thank you, that helped! Running smoothly 2.1.3!!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] kaicat:
Are U using the DU RC version or weekline?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Spannaa:
Not sure that you can flash official or weeklies with the current TWRP but RC and unofficial are fine.

DU 13 unofficial works really well with this kernel ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Golf c:
Where's the bugs? This is so boringly stable. Yummy. Lol Great job, legend. Balanced between performance and battery. Duh! These other MOMOS don't know what their doing.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TheMorpheus:
I'm on RC, we can't flash weeklies without an updated TWRP
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] exile1ck:
Not sure if this is a bug but why is my min CPU freq set so high? I tried setting both the small and big cluster minimum to the lowest but it just stays the same
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] joetheshmo:
Those frequencies are high because your phone boosts when you touch the screen to click into cpu. If you check the graphs you'll see it's using lower frequencies
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
I have googled it and I can't find what is DU and RC please?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
DU = Dirty Unicorns. It is a popular custom rom which can be found when you just google it.

RC means Release Candidate. there are three main groups of build. Official, weeklies and release candidates.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] yaking39:
Can i get a better Battery Performance with this Kernel?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Probably
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rspkt:
Been using 2.1.3 since it was released and I think this is the best battery life my device has seen thus far. Right now I'm getting approximately 7h28m SOT, 104h12m screen off time, and combined use at about 37h32m via AccuBattery Pro using Stock Pie with the March update. Pretty impressive. Thanks again, [MENTION=3428502]Freak07[/MENTION]!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Another ramoops. Was pulling the phone out of my pocket when I saw it was rebooting.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] i42o:
That's weird im on weeklies using this kernel now... ???*♂️
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] SinisterXReaper:
I'm interested as to why some individuals are having random reboots ? I'm on stock and never had a random reboot with this kernel.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
They've been very few and far between. 2 that I know of, with one other possible before I was looking for them in about 4 months. And I still don't think it's necessarily the kernel causing it.

I'm also on stock, with a bunch of Google beta apps, plus Canary Magisk. In any case it's not even close to being problematic
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Your ramoops is spammed with stuff that usually happens when your phone is charging. I took a quick look while mobile. I’m trying to investigate tomorrow.

still there are no signs of a kernel crash or a kernel panic that would cause a reboot. The warns I resolved with one of the last updates seem to be gone which is nice. Although they were probably not connected to your reboot.

Sorry for the reboot... Thanks for the log though! :svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Charging - yeah I took it off the charger just before I stuck it in my pocket, which was one or two minutes before I pulled it out.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Announcement

Hello everybody,

There were no kernel side changes in the april security update from google for my bluecross kernel.

So just flash 2.1.3 away on April Release :)

Enjoy!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
Well this is wrong. I'm on weekly build. Just you can't flash it over RC as it's signed by a key. It's all explained on their website.

Edit: been informed that it's fine for Crosshatch not Blueline.

Kernel runs fine on it as usual. Good work [MENTION=3428502]Freak07[/MENTION].
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TheMorpheus:
Do you have a Pixel 3 blueline, or do you have a Pixel 3 XL? They are not the same thing!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
Good point, I'm on Crosshatch. Didn't realise blueline didn't have an updated TWRP. Apologies.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Horoscope:
I am currently on March image with Kirisakura 2.1.3 kernel,

can someone help me with the procedure to flash April update along with Kirisakura & Root ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
This is the method I use on my P2XL

Remove all substratum themes, and set screen lock security to swipe.

Fastboot the factory image with the -w removed and let it boot up.

Go back to bootloader mode and fastboot into twrp.

Once in twrp, flash the twrp installer zip if you want to retain twrp, then flash magisk, then flash your kernel, boot up, and done :good:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HiM@L:
this works too.

remove any themes and set set security if not.

Flash

April OTA, Kiri, TWRP and Magisk, in that order.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Make sure you remove "-w" from the right file X^D

I won't tell you how I know
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dd805bb:
Way quicker method.

In magisk uninstall and just restore image not full uninstall.

Removing themes does nothing.

After it reboots take the OTA. No need to flash the whole image. Once you take the OTA via system update.

Fastboot twrp.

Flash twrp if you want it. Then magisk. Then this kernel. It will recognize magisk and root. Some kernels don't. After that reboot. And substratum and all themes if you didn't remove them will be there. Go in substratum and enable them. Reboot. Enjoy. The flashing a whole image is not needed. OTA is fine if your system is fine. And this works on

Pixel

Pixel XL

Pixel 2 XL

Pixel 3 XL.

Been doing it this way for at least a few years. Many put extra steps in or do things not needed. After you uninstall magisk and it reboots, you are basically on a stock everything. Root is gone. So the OTA will work. Reboot and profit.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] SinisterXReaper:
I truly appreciate y'all replies. One thing I love about XDA is when DEVs, or those with vast knowledge, share tidbits of their knowledge for others to learn. I know when individuals start having issues with their phones, it may not be the kernel/rom itself. There's variables at play that can cause said issue. With the two known cases, my mind started to ponder as to what was causing the issues. Could it be an app they installed? A module? In any case, once again, I appreciate the insight, and this amazing kernel.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gvsukids:
Just to clarify, this will also work on the Pixel 3 non-XL? You just have the XL versions listed.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jd1639:
You're going to feel stupid, but read the title of the thread.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gvsukids:
Thanks, very encouraging
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dd805bb:
i would assume so. they little difference in the two. kernels are the same for some the these. i only say from first hand knowledge the pixel an pixel xl are the same to a point. pixel 2 and xl idk, never had them side by side. but this has been my method for months until this morning.. so new april update even though i did it yesterday, worked all night. went to bed around midnight. have my phone auto airplane and restart every night. well today i get a message when it goes to boot with a red flag, system is corrupt, wont let me boot. stuck in fastboot. after playing around all morning, figured out you can go back to pie. you can but cant. q uses the new partition scheme, mount points are different. i kept getting a flashing error saying partitions dont exist. well long story short, manually flashed every image inside the update zip. used a method from the pixel 2 but modified it for the 3. got it runing without two different boot warning screens. so even if you go back to pie, your partitions will stay the way q put them on the pixel 3 xl. once you go q, you are screwed om the pixel 3 xl. so either rma or use q till it has root which anyday week and or month. but tjw has his in hand as a daily driver so i bet q is itching at him.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Golf c:
I have zero problems going back and forth from Pie to Q and back. Your definitely doing something wrong. I only flash factory images. I have up to date platform tools.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
No, the partitions is not staying the same if you go back to Pie. Why spread all this nonsense?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dd805bb:
Non sense?? Tell me why tjw can not root the pixel 3 xl? Because the mount point changed from mounting in boot.img to system.img. there is a device mapper and partition checker now. Go read about Q. Nonsense? No ignorance is bliss for those that are ignorant.:laugh:

---------- Post added at 09:16 PM ---------- Previous post was at 09:11 PM ----------

When you revert, check that last partition check. It says what when flashing back to pie after always after you updated to Q.. partition not available. Why? There is now a device mapper in there. Reverting only tells it to run the system as it would the Q. From here on out if you took the beta update, the system is now system as root only. Pie on the pixel 3 xl to the pixels is different. I do have all three in hand. Q on pixel XL and pixel 2 did not launch with pie therefore can not update to the new style partition mapping. Yeah a whole lot of nonsense found on Android source page and TJW Twitter page. He always posts crap and Android source, not. Lol. You really need to research before inserting the foot in the mouth.

---------- Post added at 09:18 PM ---------- Previous post was at 09:16 PM ----------

https://source.android.com/devices/bootloader/system-as-root.

Non-sense... Straight up. Read now. read the diagram "before pie 9.0" , "after 9.0"... 9.0 can run both ways.. hnce why the pixel 3 xl switches and stayes that way. once you force it to the new style, it will not revert deep down in the way the system, ramdisk and kernel are. boot doesnt contain those. system does. that is why also many problems after flashing back. i know if you really want to revert you have in essence drop a grenade off. flash both slots same time is the way i found to truly revert back.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
1) Bluecross can't be rooted (yet) because of the shift to logical partitions on Q (+the device-mapper and the rest of all the additional stuff you mentioned, which I'll give you some credits for).

2) I have flashed latest 9.0 only on / to slot A without any issues when I decided to revert from Q to Pie on my Pixel 3. What kind of reverting issues are you even referring to?

3) There is no issues at all with going back to Pie if anyone wants to (this may change once Q reaches a official stable state, who knows), which you can see for yourself if you are signing up to anyone of the Telegram groups that 'targets' anything related to Pixel 3 (XL).

Most likely it's you that is doing anything pretty wrong when trying going back, which I can't really understand how it's possible because shifting between Pie and Q is like a ordinary walk in the park. It doesn't require that much of a personal effort or time at all from my own experience.

Enough said.

EDIT: I've already seen the stuff in the link you shared, so your point is?

:)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dd805bb:
Many problems, read threw here and the dp1 forum. Many problems reverting back. Try flashing a patched_boot.img to boot.img. doesn't work. You can still root via twrp and flashing that way because magisk will pull the boot.img itself and patch it. Fastboot starts to not work right after updating to Q. Also fastbooting a factory image will fail. Hnce the same problems I ran into weeks ago goin back to pie. This is not a new problem. One that isn't seen if you use twrp. Fastboot mainly. Twrp does sometimes not catch the metadata and doesn't know how to handle that. Metadata is different too. There is a lot more to. This is way watered down.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dd805bb:
Start reading around of people that think they bricked their phone after reverting. Why? Fastnoot and avbverifybootimages kicks. I have a solution that fixes that. Does anyone else?

If anyone has a problem flashing back from Q, let me know and I can give a detailed description of how to get back to pie the right way. It involves flashing each image from the image zip. But if no one has a problem then I dont need to prove to myself that I am right and you are right too. Because many views in life. I have provided details as to why it is this way. When yours fails reverting, please do ask. I will help. I have reverted successfully more than once. Sometimes cleanly sometimes to goes south.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ridobe:
Many problems reverting back? I reverted by doing a clean flash as always. I have zero problems. Fastboot starts to "not work" on Q? Worked fine for me. Fastbooting a factory image will fail? Lol. Ok. I didn't seem to have any problems with it. You're doing something wrong.