yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] pkgnex:
Nathan,

I never had a crash or performance issues from your kernel before version 3.02. After 3.02 I noticed app opening and such seemed slower. I had changed nothing else since 9.0 FK 3.0 dropped and I have had two crashes - one on 3.03 and one on 3.05.

I've been running stock Android P since DP2, usually with your kernel (occasionally EX), without ever having a crash. I've been on Magisk 16.7 (1671) for what seems like forever, and I run no modules except osm0sis' busybox. It's just about as stock as a rooted system can be, aside from a custom kernel. I have not had the crash with EX, but that could just be because I use your kernel more often.

This seems to only happen when I have at least 12 hours without a reboot, and am using a memory intensive app - I think it was Chrome browsing in both cases, but the first one may have been something else. I don't game, so it may have been Netflix or Google Play News or something. This time I was shopping on Amazon through Chrome and when I went to my cart, a pop-up window came up, my device froze, and then rebooted.

That's really all I can think of. Let me know if there's anything else I can look for or do to help out.

---------- Post added at 10:24 PM ---------- Previous post was at 10:18 PM ----------

Also, I just re-traced the steps that caused the last crash exactly - I got a little bit of the hang-up when the pop-up came up, but no crash, so I'm not sure I'll be able to reproduce it.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] nathanchance:
Thanks, that should hopefully help me reproduce the issue when I get my device back. Just to confirm, 3.01 is good as well?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] nathanchance:
Update to 3.06!

Remember any and all bug reports need to include logs and clear steps to reproduce (see the info in the OP). You should also know what version it started with. If you want to be a tester and get builds before they are released here or just hangout, feel free to stop by Telegram!

Short changelog

Linux 4.4.153

Downloads

Primary: https://nathanchance.me/downloads/kernels/wahoo/9/stable/

Mirror: https://github.com/nathanchance/fk-zips

Remember it can be auto-flashed with FK Kernel Manager!

Commits

Kernel: https://github.com/nathanchance/wahoo/commits/pie

AnyKernel2: https://github.com/nathanchance/AnyKernel2/commits/wahoo-flash-9
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sublimaze:
Nothing against EX Kernel Manager, but I use Franco's apps whenever possible because he is a phenomenal dev and I support his work :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] pkgnex:
Yes, I had no issues on 3.0 or 3.01.

I noticed performance took a hit starting with 3.02, and I've had the crashes on 3.03 and 3.05.

Thanks for looking into it and maintaining a great kernel for wahoo.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Nekromantik:
Nathan I see that you have got backlight dimmer enabled on the kernel and in Pie for some reason the auto brightness is messed up. When in low light area it dims it quite low now so display unreadable. Is it possible to add minimum brightness setting? Or is this a franco app feature?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] srqrob:
I second this. Pie dims way too far for me and a minimum would be great. I was fine in 8.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] milestone2mod:
I've just come back to Flash Kernel after a long time of abstinence due to Google Pay not working with an unlocked bootloader. I followed the most recent installation guide woth FK manager, no permanent TWRP installation and you're Magisk build, Nathan. Everything works fine so far, except I just can't get my Pixel to connect to a WiFi network. It keeps hanging on the IP adress-check without any progress. This is on P with August security updates and kernel version 3.06. Any way to solve this?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sublimaze:
I just noticed this too. Over the last couple of days I've had to adjust the brightness manually, usually when I walk out of a dark room into more light and the screen remains dark. I rarely had to adjust manually on Oreo. Not a "dealbreaker" level issue, but a noticeable change from before. I think the brightness AI needs remedial classes.

Does this happen with *every* network, including open public networks?

I assume you have already reset network preferences in Settings.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
I've tested this 3 different times between Stock and Flash kernel, and it seems to only appear on Flash.

When the phone is powered off and charging, when on stock, the screen goes off after like... 5 seconds when showing the giant battery icon. But when using Flash kernel, the screen will stay on forever, and won't even show an animation that the battery is charging, just a frozen image.

Can anyone confirm?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] KHold01:
Noticed this today. Not a big deal to me. Stock Pie with Nathan's latest magisk
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] nathanchance:
Fairly certain this is a Magisk issue since I'm almost positive I experienced this on the stock kernel but I'll try to investigate further tomorrow.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Valeriuz:
Maybe this is off topic, but can anyone share some settings to improve multitasking?

I think in this phone multitasking is poor, maybe for the " few " 4 gb of ram.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
Sure.

Extract the script, then enable it/make it run at each boot with the "help" of EXKM;

EXKM > Tools > Script > Script Manager > Add Script.

I would though recommend you to download the 'Busybox for Android NDK' Magisk module before fully applying my script, so all the settings/parameter changes get applied w/o any issues.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Valeriuz:
Thank you. What does this script do exatcly? And then how to revert back to stock?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
Improves battery life (both active and idle battery drain), improves system responsivness and reduces overhead whenever possible.

If you want to remove it, go to Script Manager inside EXKM, click on the tree dots to the right of the script and click 'Delete'.

Then reboot your phone, so stock values gets applied again :)

EDIT: Some of the credits for this script should go to [MENTION=4793042]pkgnex[/MENTION], mainly because of recommendations on various enhancements and changes to the various parameters that I should add, and what not, that can be found and discussed in this thread;

https://xdaforums.com/pixel-2-xl/development/mod-pks-tuning-script-t3702834
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Valeriuz:
Applied but it gives me an error message, " not found ", already installed the magisk suggested module. Suggestions?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Did you extract it with your root explorer type app, then enable it in EXKM? If so, just tap the scrip and it should run.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
As [MENTION=3730810]Badger50[/MENTION] mentioned, you have to extract the ZIP file for getting access to the init.d script.

For this, I would recommend the use of FX File Explorer (with the FX File Explorer Root addon installed). Works like a charm every time, at least for me and my taste/desires/needs.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] pkgnex:
If you look in my "PK Tuning Script" thread and read the OP instructions, you can follow the best practice of just placing the (unzipped) script in the /sbin/.core/img/.core/service.d folder. Magisk will then run it at boot time automatically as a late-start service and you won't have to fiddle with init.d (which has long been deprecated) or depend on a kernel app or script manager to run it.

As an aside, neither my script nor xFirefly93's really addresses anything related to multi-tasking (memory management), which I believe was your original question.

I know Sultan is working on some improvements in that area on his kernel, but I'm not sure what they are.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Likkleskip:
I flashed it haven't changed anything.. This is how it's performing.. I think it's running well.. btw new member guys ? just sold my s8 and bought the pixel and loving it ?❤️
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sublimaze:
SOT 3 hrs 43 mins, so you are on track for 6-7 hrs total, which is awesome :good:

That's what I would average if I let the battery discharge completely. But I try to keep my battery between 40-60% to preserve battery health.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] joedajoester:
I'm running stock with flash kernel with the GPU underclocked with Franco kernel manager. Thinking of doing the same to the CPU too

I raise you these screenshots:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] lscheres:
I just got my phone, only had it a week, stock with pie, stock kernel. Im getting MUCH better battery life then this. Yesterday was 4 hours on screen time, 45 min playing pubg, 18 hours since last charge and still had 39% when i plugged it back in.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
Then I would recommend you to underclock only the big/performance cluster by using this parameter in a init.d script/script file that "force downclocks" the big cores to 1958Mhz w/o any real noticeable performance regressions;

echo "Y" > /sys/module/cpufreq/parameters/enable_underclock
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] cd993:
Lag...

This may not be a kernel issue but I would really appreciate if someone who's good at reading logs could take a look at this...

I've just updating the Resurrection Remix rom (wiped cache etc) and the dirty flash went fine and apps were all good. Then I flashed latest flash kernel and magisk and since then I've been experiencing big lag.

I've checked the Catlog and don't know really what I'm looking for, but here are a few things which could be regarding the lag and maybe Ram/Cache/kernel related? Seems to be a few entries relating to Swap and JIT?

08-30 22:21:22.436 I/zygote (12188): Deoptimizing boolean android.text.TextUtils.isEmpty(java.lang.CharSequence) due to JIT inline cache

08-30 22:21:18.338 I/zygote (12188): Increasing code cache capacity to 512KB

08-30 22:21:23.231 I/Choreographer(12188): Skipped 47 frames! The application may be doing too much work on its main thread.

Again, sorry if this is off topic and I'm just calling upon some technical expertise, based off the seemingly apparent rerfences to ram stuff here, and so the potential link to kernel behaviour.

Log attached (cleared the log, went to home screen, clicked Play Store, waited for it to load (took around 7 seconds which is unusually slow), went back to Catlog and paused/saved the log.

I've noticed the same lag with Chrome too, so something funky is going on somewhere...

I've tried rebooting and clearing caches as initial troubleshooting, but that made no difference.

Any help appreciated!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] def-g:
I can confirm. Happens on Sultan's Kernel also. Hoping for a fix.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Likkleskip:
Honestly how do I do this? Where do I copy and place these lines?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] def-g:
Try different Kernels first. Or tweeking apps. Get familiar with the device before messing with under/overclocking. That's advanced stuff.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] nathanchance:
For what it's worth, I've been using my device all day and haven't had any performance issues...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
Not for being rude but..

If you don't know what you are doing, I wouldn't recommend you to play with this kind of stuff.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] cd993:
Update: somehow fixed this....

I repeated my exact steps and dirty flashed latest RR again (removed security, uninstalled substratum theme, rebooted to recovery, flashed magisk uninstaller, rebooted system, rebooted to recovery, wiped caches, flashed rom and twrp, booted system, enabled security, rebooted to recovery flashed kernel & magisk, rebooted system and reinstalled substratum). The only thing I did differently this time was freeze (the attached) some system apps instead of remove them with Titanium Backup, which I normally do, and no lag....

Alls well that ends well eh!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bobbarker2:
As others have stated this doesn't affect multitasking issues. Also the script is applying parameters which are already set to the value you're trying to set them to and to devices that don't exist, at least on mine. SDG is the only block I have on my device and your script as setting sda through sdf. And the only setting it's actually changing is rqaffinity.

Also turning off IO stats across the board may have negative effects elsewhere, EG won't be able to retrieve stat information on io operations..

And some of the battery-saving tweaks are trivial... Disabling OTG wakelock? How is that going to save battery life? If anything this could interfere with OTG devices.

Lastly applying it in script manager will not apply the settings on boot. must follow the directions other have stated with placing it in the correct Magisk directory.

Where did you get the script from?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
1) Have you checked all the stock values on the parameters that I have modified/tweaked/adjusted?

2) Strange and bad for you then, because I got those following SDx blocks on my device (see attached screenshot).

3) Turning off IO stats isn't causing any real harm, I have already checked it out.

4) It is pretty easy to revert my adjustments, you just have to remove the specific part of the script that is echoed. If you need OTG wakelock enabled - just remove that whole line and reboot, voilá.

5) Adding this script through Script Manager (inside EXKM) does automatically "push it" to the Magisk directory where all the script(s) is stored. And yes, it does run without any issues at boot.

And at last..

6) I did not mention my script would fix the multitasking issues on the Pixel 2 (XL) line-up. Or.. Did I?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] azpatterson3:
Agree somewhat but you learn by doing new things. So if your willing to make some mistakes along the way, Read up and go for it.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] aymenus:
hello i've 2 questions

i've pixel 2 with android 9 kernel 4.4.116-gcff1ae5

1 question is there any kernel that works on the pixel 2 which has external wireless card installed if not

2 where i can get my own kernel source to compile it and edit it to install modules

and there's possibilities that external could be reconized after compiling the kernel

because i'm planning to use kali nethunter. thanks for your support
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] :
And you're happy with the memory management ?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] nathanchance:
I've not noticed anything out of the ordinary.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Hormesis:
Testing the latest beta, no issues so far.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] franciscofranco:
Looks fine here.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] MrMeeseeks:
The gods have spoken. End of discussion, guys and gals. Lol.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] praveen6585:
Latest beta seems to be noticeably snappy.. seems like the Optimization patches from Sultan seem to be working nice :D
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] infamousvincci:
HA! Franco! Lol
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bobbarker2:
1. Yes I did check stock values. Most are already set the way your script is setting except for disabling iostats and setting rqaffinity to 2. I'm not sure if setting affinity to 2 is a benefit or not over 1. 1 means completed request will be migrated to the CPU group that originally submitted it. 2 Skip's the CPU group logic and forces the migration to the specific CPU.

But you disable iostat, so we have no empirical way of testing the two options.

2. My mistake was think of dev/block.

3. So how do you know that these Block Level modifications are of any benefit if you disable iostats?

5. As others have pointed out it's best just to put the script in the correct folder for magisk as applications can fail to push it properly or with the correct permissions (like exxm did for me)

6. So why did you reply to someone asking for better memory management and saying to try your script?

also I'd like to add that underclocking the CPU isn't necessarily going to help anything. Is it better to run the processors at a higher speed for less time or a lower speed for more time? There are performance and battery life implications in this.

---

There's lots of people who put out scripts with minor modifications to sysctl/build.prop/etc. A lot of the times there's little-to-no actual gain, besides placebo. And I've seen many scripts which change settings without the author having known what they were actually changing.. not saying you are one of those, I'm just making a general statement.

I'm inclined to trust Google engineers and linux kernel maintainers to take care of these matters for the most part. . They are much more knowledgeable than us and have put countless hours into research and testing.

the Linux kernel is written for many platforms and many Hardware configurations.. so there will be knobs we can turn and I'm all for experimentation, though I personally like seeing factual data showing how turning knob X improved Y.

Overall I think people put way too much water into tunables thinking they are going to be a magic solution to whatever their issue is.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sublimaze:
Can we get back to discussing Flash Kernel?

Script discussion belongs in its own thread.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] def-g:
Only issue I had with this kernel was the slow screen wake up (compared to Sultan). Fixed in 3.05. Fantastic Work Nathan. So good not gonna even try 3.06.....For Now, lol.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bobbarker2:
You're right of course.. Nathan doesn't mind slight OT but probably went too OT. Apologies.

So yeah, discussing flash kernel... my theory is that nathan is actually a made-up persona, acting as a front for a dedicated group of Google Android engineers who are enthusiasts and in their spare time use us as an 'engineer's playground' so to speak. Thoughts?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] praveen6585:
So for anyone using TWRP to flash stuff yet, the new version 3.2.3.1 finally decrypts even with a pattern set for lockscreen.. tested and confirmed. So no more incorrect pin issues in TWRP

Btw, i read the latest OTA tutorial by topjohnwu and it sort of appears to support the monthly OTA updates from v17 of magisk..

https://github.com/topjohnwu/Magisk/commit/1b79a3ddbf21c3d1e1cb57ac84894de515ae5a5f

Is my understanding correct? There is a part that says **NOTE: In order to apply OTAs, you HAVE to make sure you haven't modified `/system` (and `/vendor` if available) in any way. Even remounting the partition to rw will tamper block verification!!**

Is having a custom kernel changing any of the parameters above?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
No.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] def-g:
Nice. Been using Franco mainly cause I couldn't handle resetting my Finger Prints each time I wanted to flash something using TWRP.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
I am going to end this discussion once and for all..

I am no expert, I can make mistakes like everyone else (if that happens, I hope someone can give me some justified feedback/response) but I am confident enough to know that I am not sharing placebo modifications/scripts/advices.

If I had the time and the patience, I would rather release a custom kernel with my specific changes and what not. But until that happens, I do rather keep myself at this level and "type of playground".

Let us get back to the topic now, shall we? If you want to continue this discussion, then PM me and we may continue from there instead.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Just a little FYI for you all you Flash users. No doubt you have seen that [MENTION=4470081]topjohnwu[/MENTION] has released his stable magisk 17.0 version, as well as Magisk Manager version 5.9.0. If you want to upgrade to both, it was as simple as updating both from within the magisk manager app itself. Cts and SN both pass as well. So you OCD users will be happy I'm sure! That is all :cool:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jr67:
I switched from Nathan's Magisk builds to the official one by uninstalling Nathan's Magisk Manager app and installing the official app then simply updating within the app.

I was thinking about just sticking with Nathan's builds but it's very easy to switch back if I was to.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] xflowy:
where can i find nathan's builds?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] praveen6585:
https://nathanchance.me/downloads/magisk/
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] nathanchance:
The only reason I started doing builds was so people could have access to the bug fixes not publicly available. Now that they are, there isn't much reason to use my builds (which I will still be doing because I can).
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
If there were an award for the most humble, helpful, highly respected Dev, and just all around good ol boy, you sir, would win hands down! And considering the company you keep....that is saying something my friend. It is truly an honor and privilege having you on XDA :good::cool:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] xflowy:
does one need to uninstall magisk via zip prior to switching from your version to the "official"?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] MrMeeseeks:
You will have to uninstall nathan's Magisk Manager apk because it has his own signature but I don't think you will need to flash the uninstaller.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
You ain't too shabby yourself Mr. Franco! :cool:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] fearfighters:
I think this is a magisk issue as I am on stock kernel and this issue started happening to me when I upgraded to magisk 17.1 from 16.4.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
I'll check it out more later... When I first tested, I didn't have Magisk installed because I was in the process of turning my device off to install it, lol. Could be a weird Pixel issue. ?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bobbarker2:
this ^^

That's not to say we don't have other great devs on the pixel 2 that deserve recognition.. flar2, fraps129, sultanxda, freak07 :cough: franco :cough: to name a few.. but nathan is great with his support, guides, community requests, frequent updates.

[MENTION=6842057]nathanchance[/MENTION] btw, why have you decided to keep maple in the kernel? It was initially committed in December and as far as i can tell, fraps's repository is inactive and maple was last updated a year ago. Any testing I've done using fio or just time has shown maple to be a good deal slower than cfq or noop. Are you just letting it be because no reason to remove it? Not advocating for a new scheduler, just wondering why maple has been left in and (at least in my tests) has shown to be slower than noop or cfq.