yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ridobe:
So, I reflashed the stock boot image via fastboot. Booted into TWRP and flashed TWRP/Magisk. Everything booted up fine. Went into EXKM and flashed 1.8.5 and it worked. Now, I know this should work, even before the issues were discovered since I flashed Magisk via TWRP. So, then I reinstalled Magisk (latest canary) via MM just to make it my latest install method in order to test. I used EXKM once again to flash 1.8.6 and was successful. Well done gents, well done.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] swieder711:
Is the adjustment to the Speaker gain only for the built in speaker? What about on Bluetooth or with a USB-C headset?

I would love an adjustment for the MIC gain, especially when using a USB-C headset.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Chronzy:
1.8.6 on top of 18.0 flashed fine in twrp ✔️
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DougMG:
Is anyone else using Wireguard. I have been troubleshooting for the last couple of days trying to chase down what has been causing my phone to reboot every couple of minutes once I get it all set up and finally figured out that it happens whenever I bring up a tunnel. If I turn the tunnel back off the phone is fine. I have had this occur with ElementalX as well. It doesn't happen on Proton though. [MENTION=3428502]Freak07[/MENTION] I am wondering if perhaps the Wireguard portion of the kernel isn't building correctly. Any insights into this problem would be greatly appreciated as I really like this kernel and would like to utilize it fully.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Please get me a ramoops after booting up when the phone crashed. Otherwise I cannot provide any help.

It’s probably due to the security features lto or cfi which are disabled on proton as far as I know. Just my guess but I need s log to confirm!

here is a good guide :

https://github.com/nathanchance/Android-Tools/blob/master/Guides/Proper_Bug_Reporting.txt
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
I had the same problem with Wireguard. I had to delete it to stop the reboots.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
See the reply above. That’s my best guess currently
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
Mine was rebooting even without the tunnel. I Switched to ExpressVPN.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DougMG:
I have the files. I will try to upload them tonight when I get home. I can't get them to upload right now.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] swieder711:
I see that FKM got updated today to 3.8.5.

Change log says "more reliability updates for Auto-Flash" Does that mean it has the fix for updating the Kernel without Magisk issues?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ridobe:
Yes but it was actually fixed in the update prior to this. I had no errors this morning.

edit: I got confused. It was exkm that was fixed earlier.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] swieder711:
I see that the speaker, earbuds and mic can all be adjusted in EXM. I am using FKM. Not sure that it is worth switching apps for the added feature.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
FKM dynamically adds options if they're available on the kernel. Previously there was no option to adjust speaker gain, now it shows up.

Also there's an option to add your own settings if there's something you want to change and know where to change it. (Look at the top of the kernel settings screen "Add a new tunable +")
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] swieder711:
Thanks for pointer. Found the audio adjustments in FKM.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DougMG:
OK it's stupid question time. How do I upload the file? When I try to add it as an attachment XDA say it is an invalid file.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DougMG:
Here is the file.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Chronzy:
I gotta say this kernel and DU is absolute butter.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
No flashing this kernel wasn´t fixed in FKM by the update prior to this! It was an attempted fix but didn´t fix all issues completely! I think you got it mixed up. You said you flashed via EXKM this morning not FKM. See your post above!

I also said to not use FKM in my release post of 1.8.6.

If you would have flashed via FKM prior the the most recent update, you´re still on the old kernel and the flash wouldn´t have been successful via FKM. With the most recent FKM on 3.8.5 the kernel will flash fine! I just tried and verified it.

yes the most recent update fixed flashing the kernel via FKM.

All other instructions in the release post from 1.8.6 are still valid. Regardless of flashing with EXKM, FKM or TWRP. If you already flashed a clean stock boot.img, redownloaded magisk and reflashed the new magisk.zip you can flash 1.8.6 or an update via FKM. If you didn´t do the procedure flashing via FKM alone will not solve the issue. At some point you have to flash the clean stock boot.img and follow the instructions from the release post of 1.8.6

The audio options available in the kernel will be exactly the same in FKM and EXKM. See Screenshots linked here.

On a device with USB-C Audio instead of 3.5mm jack headphone gain may not be possible as the dac is sitting in the usb c earbuds or the usb c dongle and not the device itself.

Thank you very much!

as expected it is a CFI failure

[ 2071.503311] c7 0 CFI failure (target: [<ffffff9f1813ff44>] wg_expired_send_keepalive+0x0/0x4):
[ 2071.503361] c7 0 ------------[ cut here ]------------
[ 2071.503371] c7 0 kernel BUG at ../kernel/cfi.c:32!
[ 2071.503392] c7 0 ------------[ cut here ]------------
[ 2071.503400] c7 0 kernel BUG at ../kernel/cfi.c:32!

see more info about CFI on the following links:

https://security.googleblog.com/2018/10/posted-by-sami-tolvanen-staff-software.html

https://source.android.com/devices/tech/debug/kcfi

Proton Kernel has most of the security features, this as well, disabled, so the reboot isn´t getting triggered on proton.

I won´t disable any security features, in fact one of the next few releases may have a big bunch of additional security features implemented :)

I´ll try to contact the wireguard dev and see if we can fix the issue :)

same experience here on a home brewed DU build :victory:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DougMG:
Thank you for looking into the wireguard issue. Hopefully they can make it work on kernels with security features intact. Stripping out most security features is the main reason I didn't stick with Proton and I would never ask any Dev to remove security features just to make an app work.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ridobe:
edit: quoted wrong post.

---------- Post added at 09:15 AM ---------- Previous post was at 09:11 AM ----------

You're correct. I confused fkm with exkm. Post updated.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paradoxxx:
Hey, I'm not 100% sure backlight dinner actually does anything. When enabling or disabling it I do not see any difference. Can anyone else confirm ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
You have to toggle the screen on and off for backlight dimmer to kick in.

do it like this. Set autobrightness to lowest. Go to a dark room. Now enable backlight dimmer. Turn the screen off.

Turn screen on again and your screen will be really dim now ;)

In fact it's to dim for me then ;) definitely works.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gogoffm:
Morning! Received my Pixel3XL some days ago and i am not really satisfied with the battery. I used custom kernels on other phones and made some good experience with them. My question is following, can i just boot TWRP and flash your kernel and leave it like it is ? Would this already be a benefit in battery (perfomrance) or do i need an app like ExKM to tweek the kernel for the performence. I don't want to install Magisk or root the phone but as far as i know to use ExKM full you have to be rooted. Thanks for the help. Cheers
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
You can just flash the kernel without root in twrp.

The kernel is already set up at compile time. So you get most of all benefits. It’s true to change options you need root. That’s true for any method, be it a script, terminal, FKM or EXKM app.

The only thing you Miss without root are the wake gestures as they are disabled by default. But other than that everything is set up as intended when you flash it.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gogoffm:
Thanks for the prompt reply!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paradoxxx:
Indeed works ! I forgot about the power cycle thingy. Thanks :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
You might try CF.lumen it's one is the only reasons I root anymore

---------- Post added at 06:50 AM ---------- Previous post was at 06:49 AM ----------

Do you have edge sense working on DU?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
No and I’m not sure if that will ever work as it requires a ton of reverse engineering they way it’s implemented. Same story for pixel 2/xl.

Maybe it will at some point maybe it won’t.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
Q:

Now that i'm comfortable with this kernel on stock settings, what should I adjust to squeeze more battery life out of it in EXKM?

I\O is on maple right now (not sure if that's recommended) but i got nothing else changed
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
[MENTION=3428502]Freak07[/MENTION] has it on Fiops, so that's what I keep it on, otherwise default settings. I also enable randomize mac address.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] zx2c4:
Thanks. Would somebody competent who can reproduce the issue reliably confirm to me whether or not https://git.zx2c4.com/WireGuard/patch/?id=92926ffbfe1bb1a3f9056f952fb2a07a9f5476d7 fixes the issue? Perhaps [MENTION=6842057]nathanchance[/MENTION] can intervene here?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I can reproduce the issue myself and I’ll compile a new build hopefully this evening!

Thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
when charging the phone while off, there used to be an animation that gives you percentage, now it just shows a charging logo with battery on it.

What gives?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DougMG:
Assuming that you have Magisk installed it is an issue that showed up a while back then was fixed and has now returned.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
yes I do. i don't recall that being the case under 17.3 but thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I sent you a PM
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DougMG:
It showed up in the early canary builds and then was fixed and now appears to be back in 18.0
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
Has anyone tried proton? Unsure which to stick with, both this kernel and proton are my top 2 for battery/performance but unsure which to stick with
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
sort of in the same boat as you.

Kirisakura is consistent in terms of results, and dev is responsive, well so is the dev for proton.

I wish HTML5 was updated more often or more timely because if it was it would be between kirisakura and html5 lol

Franken is also good too but again not updated often -

I sent u PM about this earlier today lol

---------- Post added at 02:03 AM ---------- Previous post was at 01:37 AM ----------

another strange behavior i've noticed when charging in TWRP or when phone is off , is it'll turn itself back on, and it won't be at 100% either , no rhyme or reason to this behavior
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
Strange

I found proton better than HTML5 is every aspect

Elemental was faster but drained more

Kirisakura and proton have better battery results and equivalent speed (maybe proton is smoother) unsure

But Ive yet to make a decision on my DD
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
ive been trying to format /data as EXT4 and doesnt boot not sure why and i cant get it working
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] matssa:
A custom ROM might be necessary to do what you want, I'm sure there I something that changes back to the original format (titan chip?).
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] _LLJY:
Why would you want to?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
Testing purposes

---------- Post added at 02:01 AM ---------- Previous post was at 01:59 AM ----------

Strange

If the kernel supports ext4 I would think adding a support line in the fstab and formatting as ext4 would be enough
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] airmaxx23:
This is running great, the only thing I've noticed is that in Graphics>Color Control nothing sticks after a reboot.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] crossen0:
Just asking because I'm not near a computer, can I flash this through Franco's app overtop HTML kernel?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] superchilpil:
Yeah it should work just fine, I did the same thing over the despair kernel
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Roll3r:
What are you using to change the color values? Are you setting it to apply at boot? I'm using EX kernel manager and it's working fine.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Remove EXKM app from battery optimization in settings. Works for me I just tested it.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
It should work fine, however I wouldn’t tinker without a PC nearby if you absolutely need your phone to be working!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] crossen0:
Sound logic. Will wait it out until I'm back from vacation on Thursday ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
do you think maybe you can assist?

i have suspicions that EXT4 may perform better than F2FS on the /data partition
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ridobe:
I'd say this kernel is pretty good on battery.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ART:
What's your app usage like?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ridobe:
I play online games, poker etc... browse XDA, Reddit, blogs, etc. I downloaded 6 movies for an upcoming trip. I have all settings on as well ie. location, WiFi on always, etc.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Roll3r:
EXKM was working fine for me, but just updated to the November release and now my color profiles aren't applying at boot either. Battery isn't being optimized, I've set it to wait to apply boot settings for 45 seconds, etc.

On the Pixel XL I used to just use Tasker to write values directly to kcal_ctrl.0, but can't find them on Pixel 3 XL, and I have no clue where to look.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] airmaxx23:
I'm using the + to change Saturation to 36 and have "apply on not" enabled. I do have a message after a reboot saying that settings have been applied but it's not sticking.

That didn't seem to help but thanks for the suggestion
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ART:
What is sociopath good for? Performance or battery? Couldn't find any info on it, even in that xda thread with all the governors and tcp stuff.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I remember seing some changes in the CAF sdm845 codebase for F2FS and encryption specifically.

Did you try to decrypt and change afterwards?

could also be that you need some more changes to kernel, recovery etc to get it working.

This is very good considering your usage!

you´re looking for:

/sys/module/msm_drm/parameters/kcal_hue
/sys/module/msm_drm/parameters/kcal_green
/sys/module/msm_drm/parameters/kcal_red
/sys/module/msm_drm/parameters/kcal_cont
/sys/module/msm_drm/parameters/kcal_blue
/sys/module/msm_drm/parameters/kcal_sat
/sys/module/msm_drm/parameters/kcal_val

:good:

can you do me a favour?

in EXKM app.

go to tools -> user setting.

hit the plus button to create a new entry.

as file you select:

/sys/module/msm_drm/parameters/kcal_sat

the value of the file will now show as 255!

this is the same as saturation at 32 in the color control tap.

now change the value to 259 and activate the little blue arrow right to the entry you just created.

reboot and see if it´s still at 259.

worked for me too.

well I don´t think TCP congestion algorithms have a big impact on battery life. there may be a few scenarious, especially with wonky networks/providers where you can get better data connection (to put it simply) which will maybe result in better battery life.

Have a read here for TCP congestion control in general

take a look at RENO in particular.

here is somewhat more detailed info about RENO

and SOCIOPATH is:

TCP Reno with no slow start and a much more

aggressive ssthresh recalculation (lowers it by 5% instead of 50%).
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
Hmmmm I'll try decrypt and changing again

edit:

eventhough it wont boot, i can see files created in TWRP on /data partition.

but it just loads on the google logo with the loading symbol going on and on.

looks like i might have to give up trying to get /data on EXT4 :(

now another issue i have found

if you decrypt the phone - you can no longer set a fingerprint, and any PIN you create to unlock will be wrong if you try and change it. strange first time ive seen this behavior.

not sure if its related to the Titan M chip or whatever.

i wonder if its possible to disable the Titan M chip somehow.

strange - i had the oneplus 6 with Pie and was able to decrypt without any ill effects.

very strange behavior by google.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bggold:
I have been running proton since it was first released and switched to it after running the others. Cant say today if the others are better now but have stuck with proton. No issues and the dev is responsive.

It is one of those things for me, I find something that works and isn't broken why switch. That's my opinion others may vary.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
My problem with Proton is "performance takes priority over security". That makes it a nonstarter for me.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
I dont mind this

By removing some security features battery performs better too.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
New update with Wireguard fixed, latest upstream which dropped 3 hours ago, and a few upstream patches will most probably drop today :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] flar2:
You can remap active edge with Button Mapper, if that's what you're asking.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I guess he was referring if active edge is working on my own Dirty Unicorns build.

Active edge is not working on any custom rom.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] edopa:
How do you install over DU? Mine gets bootloop everytime..
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
Q: Pretty certain it isn't kernel related but is anyone else experiencing stuttering and lag in the camera app? Even pressing the shutter button causes major lag and stuttering in daylight.

I think it started after the last camera update on playstore but i cannot be certain 100%
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Chronzy:
Gotta be on December

Twrp

Factory reset

Flash rom

Couldn't be easier, I don't understand why some ppl are having problems. This is OT though and you might want to direct any other questions to their discord.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
I haven't been able to find anything to read up on the Anxiety I/O scheduler. Is it similar to Fiops?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
From the author of anxiety:

The Anxiety I/O scheduler prioritizes latency over everything	else. When a request comes in, it will use a lighweight	selection algorithm to swiftly process the current pending task.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] airmaxx23:
I flashed 1.8.7 through TWRP and had no issues. As always, thank you and I appreciate your work.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
[MENTION=3428502]Freak07[/MENTION] you may want to edit the instructions for fixing the ramdisk error in the latest release post and remove the statement about FKM not being fixed yet. Otherwise I guarantee some people will get confused ??
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
Wireguard is working great. No more reboots, thanks. ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] kdrag0n:
I worked with the developer of Anxiety. It looks like your version doesn't have most of my edits, but the gist of it is the same.

It's a minimal scheduler that is just a simple first-in-first-out queue of requests, but handles reads before writes if there are reads in the queue. Basically, it's biased towards reads because it's more likely a read will block the UI than writes. Because the algorithm is so simple, it's likely better on battery as well (even though I can't imagine I/O schedulers using much battery)

If max_starved_writes reads have been processed and no writes, writes get a turn to be dispatched. My default for that value is 8, yours is 32. This number is tunable.

Another nice thing is its simplicity. It's tiny in terms of kernel code, weighing in at only 123 lines of kernel code. To put this into perspective, CFQ is 3340 lines of code and Deadline is 298. Note this is counting actual lines of code, not blank/whitespace lines and comments.

That being said, if you're looking for balanced overall performance use CFQ. Anxiety was made for low latency and UI to an extent, and was benchmarked with SQLite as a test. Due to the simplicity, it will not perform well under load.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Thanks for the heads up! It´s fixed!

You´re very welcome :)

That´s because I didn´t find the IO Scheduler on your git but someone else´s. :)

I´ll take a look at your git and the additional commits. Thanks!

As I said it´s included for those who want to experiment. CFQ stays default in my kernel.

Thanks for the heads up!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
[MENTION=3428502]Freak07[/MENTION] Will you be making BBR the default TCP congestion algorithm?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] yanowman:
My dumb question of the day....

Let me just prefice my question by saying I FLASH STUFF FOR NO REASON (much of the time). However with the Pixel 3 and the ram management, I flashed these different kernels to try to get it to be less buggy, and more RAM friendly, and its been great! However, what MORE can I do to speed up my device, and extend battery life?

Q) What easy kernel tweaks can we do AFTER flashing to really make our new devices shine while running this kernel?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
No not for now. It´s mostly a TCP congestion control that benefits the sender. It works really good for me (using it currently myself, trying to evaluate any gains in conjunction with maybe wireguard etc) but westwood stays default for now.

You can actually try to measure it yourself with a row of speed tests to see if bbr works good for you. But do a bunch of tests for each TCP and not just one ;)

No easy kernel tweaks are needed after flashing, as I set most of the settings the way I intended them to be at compile time ;)

It´s really just flash and forget maybe except the wake gestures.

However you certainly can experiment with different IO Schedulers or TCP protocols. Don´t change the default cpu governor schedutil! That´s important or you´ll basically lose every single CPU optimization on your pixel.