yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
I'm running my **** with a few filesystem mounting options for the EXT4 partitions for better performance and reduced system latency, and if I could do the same for the data / F2FS partition on my Pixel 3 - I would do ofc do it, but that non stop "Invalid argument" output message no matter which supported F2FS mounting option I've tried with made me just remove the specific mounting syntax line during the current creation process of BlackenedMod v1.3 for good.

Gentle_fair_sleepers is a golden classic from the past, which works IMO even today to some percent and overall extent when being "mixed together" with EAS - the general impact and difference, when it is coming to UI responsivness with gentle fair sleepers disabled, is just not as big as it was during the pre-EAS days.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
did you already forget? I answered you twice on gentle fair sleepers in the past already.

https://xdaforums.com/showpost.php?p=78262607&postcount=276

Some goes for the other sched_features ;) Until I actually see a "real" improvement, these stay default in the release kernel here.

I´m currently experimenting with this:

https://github.com/freak07/Kirisakura_bluecross/commit/00c143ed899c5ab3defdb2e03aa946d8c3fdf01c

coupled with a few additional commits on my personal build. It´s just hard to notice a difference.

My device handles scrolling in XDA, Gmail, Google photos and most apps I use with constant 60fps. That´s all I ask for :) Apps open fast and it gets the job done.

I won´t play with mounting options unless I absolutely need to. Google put quite some work into f2fs, fs-verity, and UFS performance on this device.

I´m in no way an expert on these mount options. Usually they contribute to safety and file system integrity in case of an uncontrolled shutdown. I like my data to be kept intact as good as possible in case something unexpected happens.

It´s not worth to gain a tiny bit of "even more" IO performance (that won´t be noticeable in "real world" usage) at the cost of stability. At least not for my kernel here.

It seems nobody noticed the fs performance regression from the february security update at all, when actually using the phone. Since it´s affects the stock kernel too, this might tell us something about "real world usage" vs "synthetic benchmarks peak performance".

Though everyone is free to play with these. If something goes wrong and gets corrupted you read the warning here :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
On a side note 4.9.157 and 4.9.158 dropped a few hours ago. I´ll release the update kernel later this evening, when I return home.

4.9.158 consists of just one commit that is a hotfix revert for a commit introduced in 4.9.156!

Have a nice day everyone!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
i did more testing, F2FS has better seq writes with FSYNC off compared to EXT4 with fsync off

i did notice though if i remove verity and format data (which also formats /metadata and wipes the titan chip)- i lose wifi and internet connectivity - somehow /data /metadata and the Titan M chip are all linked somehow - and im assuming disabling verity / avb and formatting breaks internet connectivity and wifi (you cant connect to anything options cant be enabled)

im assuming this is one "feature" of the titan chip? not sure what google are doing, decrypting breaks fingerprint and lockscreen pin, and removing verity breaks internet and wifi?

if someone can confirm this

boot into twrp

then in terminal echo KEEPVERITY=false>>/data/.magisk

flash magisk (you should see it say removing dm(verity)

then format /data (you should also see it say formatting metadata and wiping titan)

boot

do you have cellular data? are you able to connect to wifi? if you still do - go to /vendor/etc and edit the fstab to remove "avb" from /system and do the process again (echo, flash magisk, format)

trying to pin point whats causing network issues, if its avb or the fstab changes

needless to say this phone is challenging, things were so much easier with the oneplus phones haha
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Komodoketavaran:
Wow... Thank you very much I will try asap

Gesendet von meinem Pixel 3 XL mit Tapatalk
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] boostedduece:
Running great on 1.5.0, can already see a difference in performance, thanks for the great kernel, MAC randomization is cool too.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] airmaxx23:
Thanks for the update, do you plan on adding High Brightness Mode at some point?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ridobe:
[MENTION=3428502]Freak07[/MENTION]. Wow. What a release. I just flashed it and can't wait to play with the tunables. FYI, I had to flash Magisk afterwards as I did lose root.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
I restored stock boot image and installed magisk 17.4 in TWRP and rebooted to confirm root. Then flashed 1.5 in EXKM and maintained root. Wonder why you lost it? What were your steps?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rohmbd:
I flashed via Franco App....lost root....reflashed November patched boot image then flashed This kernel again via Franco App....reflashed magisk via magisk app and rebooted. Good to go.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sevael:
Same here. Regular (non-XL) Pixel 3. Flashed stock boot.img, flashed Magisk, flashed kernel, reboot, no root. Flashed Magisk again (via TWRP), root now working.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] old_fart:
fyi, no big deal, i lost root too. . . . i used franco's app. . should i have used the "other guy's" ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rohmbd:
You lost root for sure when you flashed stock boot.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] airmaxx23:
I flashed this to my active slot (a) in TWRP, changed slots (to b), rebooted recovery, flashed to the new active slot (b), changed slots (back to a), rebooted to system and kept root.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
I think you should have flashed the kernel before magisk.

Are those steps in order? If you flashed magisk last, how did you flash the kernel in franco app without root?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rohmbd:
I flashed this kernel in the Franco App, didn't reboot, flashed magisk via magisk app then rebooted.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
Flashing in TWRP and EXKM seems to keep root, maybe not Franco?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ridobe:
To answer your first question regarding steps, I flashed the kernel then rebooted. Since I was already on this kernel, I saw no need to flash the stock boot.img. It didn't stay rooted. Booted into TWRP then flashed magisk.

When I'm flashing without recovery, I flash the kernel using Franco/exkm without reboot. Then I flash magisk with a reboot.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
Don't you need root to flash in Franco?

Cuz I juat tried flashing a kernel without root..nothing happened AND how did you flash magisk in the magisk app with out root? Dude, you were already rooted or your process didn't do anything... I am confused

---------- Post added at 07:59 PM ---------- Previous post was at 07:55 PM ----------

I don't flash stock boot image when not needed, but I was testing and wanted a clean start. Not sure it matter in this case... BUT did you use franco or EXKM? I did not try franco but EXKM worked...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ridobe:
Haha. Download the new kernel zip. Flash directly with kernel app of choice with a reboot. Boom, no root. Boot into TWRP and flash magisk, reboot, rooted.

On a kernel that doesn't maintain root: download zip and flash directly with kernel app without reboot. Reflash magisk from magisk app, reboot=rooted.

edit: to answer your edit. I've successfully done both scenarios with Franco. I used exkm to flash this kernel then rebooted to no root.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sevael:
As I mentioned in my post, I flashed Magisk after flashing the stock boot.img. So I had root back. Then I flashed the kernel and root was gone.

The kernel's instructions specifically say that it detects if you were already rooted and maintains said root when the kernel is flashed. The only reason we're posting about this is because this is not actually happening in practice.

Sure, we can flash the kernel first and then Magisk after, but we were testing the claim that if you flash the kernel while already rooted, root persists. At least for my attempt, root did not persist. It's not a big deal, just pointing it out so that the OP can either fix whatever the issue is or change the instructions to recommend re-flashing Magisk after flashing the kernel.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rohmbd:
Ok....so I initially flashed this kernel when I had root.... rebooted, lost root. So I reflashed the rooted patched stock boot image in fastboot rebooted and was rooted, flashed this kernel via Franco App, didn't reboot, reflashed magisk via magisk app direct install, then rebooted with root and this kernel
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Update to 2.0.9

Hey guys and girls,

So here is the next update. Included are changes from 4.9.157 and 4.9.158. As already said 4.9.158 was a hotfix to revert a commit introduced in 4.9.156 and got pushed together with 4.9.157 as it seems.

I wish everyone a nice weekend :) enjoy your pixel 3/xl with latest linux-stable-upstream!

Changelog:

- Linux Stable bumped up to 4.9.158

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

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:
Definitely noticed the regressions from Feb patch

Which is why I stayed on the Jan patch, I remember your comments on sched feats just thought you may have changed (since blackened mod changes these)

Definitely noticed better performance with 208 than anything before, even before the commit that caused regressions.

Thank you for your work :))
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
There is a reason why I have changed them, and it's not for screwing up the user experience or causing issues further down the road, so..

:highfive:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
:highfive:

209 even better

This phone has come a long way from those ram management issues
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] c_86:
Getting better and better

Great job Freak07! And thank you!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] smartymcfly:
209 vs 208

209 getting considerable lag when apps and keyboard is kind also kind reacting slow. These are not usually present.

208 apps and keyboard we're smooth.

207 was kind of laggy like this too but this feels worse.

No benchmarking done, just the way the phone is working.

Reflashed 208 and lag is gone. If you need logs, let me know and I will send them.

Edit: it may have been a heat issue causing the lag. Will try 209 again later today.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] i42o:
Has to be yourset up. I just flashed this kernel and I have NO issues whatsoever.

Thanks for a great kernel !!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] c_86:
I have to somewhat agree to this.

I'm having some micro lag when scrolling. Like in apps like Facebook and amazon
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] exile1ck:
Is there any point of using L Speed with this kernel?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] hilla_killa:
Honestly it will cause more problems than help
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
i notice apps open faster on 209 but i do notice microlag.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] duminduweera:
Any reason why I would get half your random speeds with the latest version.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Mine look more like [MENTION=3428502]Freak07[/MENTION]
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I´m not using the facebook app for various reasons so I can´t comment on facebook.

But I have no lag on my device when scrolling.

As [MENTION=6314281]hilla_killa[/MENTION] already said it is recommended to use the kernel without any scripts or tweaks that aim to improve battery/performance.

You are free to use mods/tweaks/scripts, but if you face issues you´re most probably on your own. The default values are tested and have been proven to yield the best stable results for a long time.

Nothing in 2.0.9 was introduced that could cause this.

It may be due to thermal throttling, to prevent damage to your UFS chip. Some very resource heavy background process might be eating a lot of available IO performance.

I´d restart my device, let it sit for a while and see if this issue solves itself.

very good :good:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
4.9.159 dropped a few hours ago.

Kernel will be updated probably later today with latest linux-stable!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Just another ditto on both benchmarks coming in consistent with Freak's
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Update to 2.0.10

Hey guys and girls,

It´s update time again :) Includes a bump up to linux-stable 4.9.159, which dropped today!

Currently there are some very interesting things in testing so stay tuned :good:

Changelog:

- Linux Stable release 4.9.159

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

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] hilla_killa:
Yours are better than mine
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Golf c:
I think there is a procedure. You can put it right to performance gov and blow everything away or you can clear all apps and reboot, and wait a few and benchmark. Please, someone chime in.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] hilla_killa:
Yea buts that not really real world usage, kind of cheating is u do all that
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Golf c:
Exactly. Doesn't surprise me that we're all different. That's why it's meaningless
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Golf c:
Performance gov rebooted, apps cleared.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Golf c:
Oh. BTW. That's on DU. Despair kernel. Performance gov. Magisk. 111 apps and who knows what settings. See what I mean. Meaningless. Real world performance is everything.

Edit : We all run different. It matters
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] zandander:
Y'all's are much better than mine!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Golf c:
Well that no good. Lol
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] hilla_killa:
Yea if u clear everything out any device is good also that app hasnt been updated in ages so who knows
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Golf c:
Ugh.Back on stock. praise the Lord. Hallelujah. That was painfull
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
It was not my intention to start a contest on whos got the fastest IO performance on my thread. There may be some tricks to achieve higher scores but I don´t really care about them. All the benchmarks I posted are done without any further tweaks, than running my kernel at stock settings. So no governor changing, no explicit reboot and clearing all apps before running the benchmark, no airplane mod, no funky other sysfs paths changed etc. If somebody changes stuff it should be mentioned, as it´s just confusing and completely irrelevant otherwise.

The benchmarks I posted were more of a guideline on what the results should look like. If somebody gets a bit higher or lower scores with just one run of androbench, it doesn´t really matter or (most probably) impact real world usage. Somebody has many background services running, which may impact the result, some may have none apps open and get a slightly better result. This is expected. Keep in mind pixel 3 and pixel 3 xl are different devices and some results between the devices may differ.

When I did post the benchmark scores along with the release of 2.08, my intention was to show the big impact on IO performance, the commit I decided to revert, had. After all, random read speeds (which have the biggest impact on "real world usage") got reduced by half and random write speeds to less than 1/6 of the original performance, when peak performance is measured via a synthetic benchmark.

Although the app androbench was not updated in a long time it´s a very good tool to measure IO performance. If something is working as expected and fulfills its duty why update it for no reason?

The regression before I reverted the commit in question, could also be observed in other benchmarking apps.

If somebody decides to run androbench and the results are much lower than expected:

Make sure you are using the latest kernel posted here (the first update with february security update suffered from IO perfromance regression)

Make sure to use no mods, tweaks or scripts

Your device may be hot and throttle itself to keep all internal components functional

There may be work scheduled in the background, which may interfere with the benchmark. Try it a few times. Scores may normalize after a few attempts.

When I do testing for myself I do multiple benches and average out the scores
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] zandander:
I was just messing around with it lol. To me a benchmark means very little. Real world usage is it what counts, not some strange get number. One of the best kernels I've used on any device hands down. You've done very well and I am impressed and happy! Thank you for your time and hard work bud :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] yung40oz84:
To update to the newer version can I just flash the kernel in TWRP and I'm good? Or do I need to restore stock I'm good and all that goody good?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DvLAx3l:
Flash latest update in twrp or use the ex app
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
4.9.160 dropped today. I’ll upload the updated kernel tomorrow!

Have a nice weekend everyone!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Update to 2.0.11

Hey guys and girls,

So here we go with a sunday release :) 4.9.160 dropped yesterday. Here´s the update for you all!

Everyone a nice weekend!

Changelog:

- Linux Stable release 4.9.160

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

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:
[MENTION=3428502]Freak07[/MENTION]

what are your thoughts on mounting /data with nolazytime?

i couldnt find much information about it - but ive mounted it as nolazytime without adverse affects

i remember that noatime/nodiratime was used to make performance alittle better - is it true with nolazytime? (havent used it long enough to notice)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
lazytime will give you better performance.

Note that lazytime and noatime are not mutually exclusive.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jbarcus81:
One of my top 2 Kernels for Pixel 2 XL and now that my 3 XL has arrived today, I found you here!?! AMAZING!!! OT I know.. #sorrynotsorry
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Jiggs82:
Just got my 3xl last week coming from 2xl and was happy this kernel existed here too :D lol
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
Check your PM(s) when you have time for it.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Hung0702:
Hey, thanks so much for your contributions to the community. Would you mind listing your changelog in the OP by recency? It's not a big difference and wouldn't make the thread any easier to read, it's just a thing I see other changelogs do. 1st entry is the most recent.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
What if we use nolazytime?

Does that mean atime, etc aren't updated at all? Shouldn't that be better for performance
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
And now, I'll call you Notch Man! ???
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
No. It means we go back to before lazytime became a thing and we update all the timestamps the way we always used to. atime will get updated depending on if noatime or relatime are set. ctime and mtime are updated as usual.

The biggest hit was always atime. It also wasn't used that often, which is why noatime was created. Problem was twofold. 1) Not that often does not equal never. 2) noatime isn't POSIX compliant.

Problem 1 was solved, for the most part, with relatime. Lazytime solves problem 2, but only if you don't use noatime or relatime.

In any case neither problem 1 nor 2 are really important for Android. So, by default, Android runs with noatime. That leaves relatively minor overhead with ctime and mtime. Lazytime minimizes even that overhead.

See https://lwn.net/Articles/621046/
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] OGTempest:
How many SOT and geekbench 4 you got with this kernel?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Screen on time will vary from user to user as it’s entirely dependant on the usage.

I just did a quick run of geekbench 4. See the screenshot for results.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Announcement!

Update with 4.9.161 will drop probably later today! :good:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Update imminent :cool: