yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] cmo220:
Edit: Phone just froze up on me. Not sure why, wasn't AA. It probably had just switched network type. I had taken it off the charger less than five minutes earlier though.

/sys/fs/pstore contents attached. console-ramoops-0 is too large to attach, here's a link:

https://drive.google.com/open?id=1rmCdvMqifdxLQbAKcYtdVcOEKPQx5wsU

I was having reboot issues with all of your kernels since you added in the Q stuff, until this latest version. It usually happened while charging, but not always. Around 90% of the time it was while charging or right after taking it off the charger.

The other problem I had, that is also gone now, is that my phone would freeze up when I connected it to Android Auto. Everything seemed to work fine, but I would have to force a reboot to do anything else with the phone,even after unplugging Android Auto.

I was never fast enough, or knew how to get logs so I had no reason to post anything. Now I figured out how but it stopped!

This is on Blueline by the way. Both March and April builds. I had tried it after a clean flash (with -w) and with only a few apps, mainly Android Auto, and it still happened. With and without Magisk and modules, with and without a kernel manager.

When I flashed another kernel the reboots and freezing would stop right away.

Sorry for the wall of text, but hopefully this can help in some way.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
Deleted
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
[MENTION=3428502]Freak07[/MENTION]

Hope this helps

Had a random reboot
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Couple of questions.

Was this with the latest kernel?

You charged a short while ago or was the device charging when it rebooted?

Are you using Google charger?

What modifications do you use? Mods, magisk modules etc? stock rom?

There is no kernel panic in the log but it reminds me of an earlier log I saw.

Maybe something on the rom side isn’t playing nice and causing a reboot with an incompatible kernel change.

I might have a few ideas.

Thanks for the log.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] odontastic:
People on Pie enabling Private DNS with Adguard's DNS over TLS experience such behavior (others work, like dns.quad9.net). Google had fixed it but hadn't included it in any updates yet .
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
Yes latest kernel

Stock rom with magisk and only YouTube vanced installed

Was in my car charger, navigating with hot spot on when it restarted
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 21cdb:
I never used Adguard, and I explicitly turned off private DNS. I actually got it to happen without installing Kirisakura, and I just got it to happen with a completely fresh AOSiP install with Kirisakura but almost no other apps installed. Not sure what's going on.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DeeZZ_NuuZZ:
Then it might be a problem with AOSiP. Can you fresh install another rom and see if it still happens there?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 21cdb:
Just happened on Bootleggers ROM as well, and someone else said it happened to him on Scorpion ROM. It didn't use to happen until the last couple of versions as far as I can remember. I'm guessing it's a ROM issue, maybe related to the April update.

Edit: I just switched back to fully stock with Kirisakura kernel and Magisk. So far it hasn't happened at all, and everything is running extremely smooth. Smoother than the custom ROMs, actually.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DeeZZ_NuuZZ:
I'm using DU now for a couple days with kirisakura and never had this issue...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] #Teampixel:
Must say I do find stock overall smoother with this kernel. To my surprise DU with it's stock kernel was actually pretty stuttery and Laggy. Better now with this kernel, but I do find stock smoother than any rom I've tried. Been surprised by that
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 21cdb:
I tried DU as well for a bit yesterday, but it had very little configurability compared to other ROMs and I didn't really like the way it looked, so unfortunately it didn't last long for me. I didn't run into the issue while I tried it, though.

---------- Post added at 06:18 AM ---------- Previous post was at 06:14 AM ----------

I agree, I've found the custom ROMs with their stock kernels to be pretty painful to use. Stock without a custom kernel is very smooth, and with Kirisakura it absolutely flies. I'm missing out on some configurability with stock, but honestly I think it may be worth it for how completely stutter free it is.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] #Teampixel:
Yeah I was surprised. DU has always been very good. But disappointed on the pixel 3. Scorpion and a couple others were pretty good. But again still can't get it as smooth and stutter free.

Also for some reason if I use a gesture app from the play store it completely lags up any rom
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 21cdb:
I believe the gesture apps use accessibility services which for some reason can cause lag on Android. I'm not sure if any of the gesture apps avoid that somehow or if they're all like that.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] #Teampixel:
Think there all like that. Was using scorpion ROM with vivid gestures and it seemed ok but some roms like DU any gesture app makes it go painfully laggy and choppy
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] SacredDeviL666:
Shouldn't we let the thread get back to the discussion of Kirisakura kernel/its development/support/bugs, just as an user i am trying to point it out as i use a pixel 3 along with this kernel.

Last few pages gets confusing with the topic discussed and what has that got to do with this kernel so thought of asking. My bad if i interrupted.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
side question: how do you flash-all.bat for both slots?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] infamous84:
shouldnt need to, running the script will take care of everything
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
It just flashes the needed stuff to the other slot if you are checking the output log during the flashing process, in case of that you are flashing with the -w(ipe) flag.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bleez99:
fastboot --help. There's a command line arg that does both sides. Modify your batch file accordingly.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MonztA2:
I just noticed I cannot enable my flashight when recoding a video. When I tap the icon, it says "Device is too hot. Flash has been turned off." while it's not hot at all, just 33° celsius according to EXKM. Flashlight works fine btw. Could this be a kernel issue? I'm on Pixel 3, Kirisakura 2.2.0 and Android 9 April update.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] c_86:
Read the thread please. Or search. Talked about already and with fix posted.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] smartymcfly:
Not sure if you can help [MENTION=3428502]Freak07[/MENTION] but the big cluster seems to be pretty much staying at 2803 or whatever the highest frequency is for a majority of the time. I can't seem to find anything in betterbatterystats either. Is there any log for debugging thatight help explain this behavior?

It only shows for a limited time but this has been going on for some days now and figured it would work itself out.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Flyer66:
Mine is doing the same thing.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ridobe:
I just noticed this too. Thanks for pointing it out.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I don’t think that’s kernel related.

It might just be an app or a system service requesting horsepower, which has gone rogue. (play services I’m looking at you?)

What also comes to my mind. If you made a lot of videos, and have a not extremely fast connection google Foto backup might need power in the background for quite some time depending on the connection speed. ( Easter and making some family videos maybe?)

what you all can do:

Open up a terminal app and type ( without the “ “)

“su”

And then:

“top”

Let your phone idle for half a minute. Check what the top processes are. I’ll attach a screensjot how it looks for me currently (how it should look like).

I’ll also attach a screenshot from my frequency distribution graph.

There are no recent scheduler changes that might introduce this behaviour all of a sudden. If it didn’t happen immediately after flashing it’s most likely not the kernel.

It would be great if all of you could answer a few questions please:

Are you on stock April? do you run any mods, scripts, etc? (I mean every mod and be it even a very little mod ;) )

Do you run my latest kernel? did it happen on another kernel too? Does a reboot solve the problem?

Is your deep sleep fine?

Are you using stock charger? Are you using pixel stand? ( I don’t have one so if it’s caused by that I would never know).
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MonztA2:
Whoops, sorry guys!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] #Teampixel:
Great kernel by the way. Definitely get better battery life compared to stock.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Flyer66:
Hey Freak07... First, Happy Easter and thank you for all the time & hard work you put into this fantastic kernel!

I rebooted my phone this morning and let it idle for awhile after finishing the boot up process. It seems to be running better but it's still spending very little time in deep sleep. I've attached a screen shot terminal running top processes.

I'm currently on the latest stock Pie version (April) and running your latest kernel.

I'm on the Canary (Debug) version of Magisk and the only modules I'm running are Busybox, Substratum, and Systemless hosts.

I'm not running any scripts and I run your kernel with all the default settings.

It's been a few months since I've tried any other kernels. I've strictly been using yours and I flash your new updates via EX kernel manager within a day of you uploading them.

I'm not sure if a rogue app is causing the increase and sustained performance or not. I haven't shot any videos or used the camera in a few days. Better Battery Stats does really show anything. I'm about ready to just back up everything and factory reset the phone and start over from scratch to hopefully fix the performance and increase battery life.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] smartymcfly:
"magiskd" was the process that was causing the problem.

I did flashall and then started fresh with your kernel. Went from magisk 18.1 and it was working. So tried beta and same and now back to canary and it is working fine again, in fact I don't see a process for "magiskd" at all.

Thank you for the help [MENTION=3428502]Freak07[/MENTION] the top command showed me right away, even after 5 minutes with screen timeout off, the process was still going and remained at the top of the list the whole time
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Flyer66:
That's interesting because when I first ran "su" and "top" in the terminal app as per Freak07's instructions, "magiskd" went right to the top on mine too and stayed there even after letting it run idle for 5 minutes. I did this before rebooting the phone.

I wanted to run a before and after reboot to see if anything changed. When I ran the process again after letting it fully reboot, "magiskd" did not appear anymore. I'm not sure what changed after rebooting but I went ahead and started fresh with Flash-all and set everything up again. Flashed Twrp, Magisk, and Freak07's latest kernel and now deep sleep is working as it should. ??
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Flyer66:
I spoke too soon. After a full wipe and clean install, "magiskd" is back and maxing out both my big & little clusters!

I'm running stock Pie, canary version of Magisk (no modules), and the latest kirisakura kernel.

Not sure why this is happening??
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
You can try to run the magisk uninstall zip and then install latest magisk stable zip. Maybe you installed the canary with logging enabled and it’s going havoc?

I remember some people facing exactly this on pixel 2. Search a bit around may you’ll find something that’ll help :) “magisk high you usage”

I’m also running latest canary and everything is fine for me.

I suggest you try to open up a thread in Q and A or try to find help on the magisk forums now that you have identified the issue.

When the issue is present try to gather a logcat and a dmesg.

A magisk.log might also be helpful.

Here’s all info how to do it:

https://www.didgeridoohan.com/magisk/MagiskHelp
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] c_86:
Idk what the issue is you are having but no such issues here with this kernel aosip and magisk 19.0-8
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Flyer66:
Thanks! I'll search around for more info.

Just curious... Are you running Canary or Canary (Debug)?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Canary without debug
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] exile1ck:
What font are you using?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Flyer66:
That may be my problem. I'm on the Debug version. I just switched to the non-debug Canary channel so hopefully that will correct the problem. Thanks.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nycdiplomat:
I'm having the same exact issue with "magiskd" maxing out cpu. I had no idea until I checked with the "top" command. Had been trying to figure out why tf my battery was draining so fast and wouldn't deep sleep properly. I'm not running the canary version though. Just beta. I'll flash stable to see if that makes any difference.

Edit: just noticed my OP6 is doing the same thing running magisk 19.0.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
did fastboot --help and not seeing a cmd line that provides the ability to flash both slots?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LimitsX:
Only google apps I deleted was music, video, file, and andriod transfer app. Nothing else.

My brightness is usually less than 45%.

I am using a different kernel and did same stuff. I get 7 hours 25 min SOT, super fluid performance, no lag, no stuttering.

It is the kernel draining, not what i change or did. Cause the things I changed mattered, then it would happen in other kernels, but it doesn't.

i use whatsapp and samsung internet beta lol. I did enough testing, its the kernel that is causing issues. Other kernels aren't causing such a drain. And most of my screen is black, to help with battery life.

All apps are black (not even dark). I don't use any magisk module or anything.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bleez99:
Try fastboot --slot all. It may have been removed, but I did see it in the source code.

Latest fastboot code in Google's git.

" --slot <slot> Specify slot name to be used if the\n"
" device supports slots. All operations\n"
" on partitions that support slots will\n"
" be done on the slot specified.\n"
" 'all' can be given to refer to all slots.\n"
" 'other' can be given to refer to a\n"
" non-current slot. If this flag is not\n"
" used, slotted partitions will default\n"
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
okay got you, so where do i put this? in the flash-all.bat using notepad?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bleez99:
I can only speak for the FreeBSD/Linux version, but yes, you would need to modify the flash-all.bat to suit your needs.

Big disclaimer, I have always manually switched slots and then after I would run flash-all .sh

I have never used the --slot all command.

It might be easier for you to try this:

fastboot --getvar current-slot will reveal the current slot you're booting from.

Then I would flip flop my current slot each month.

So, for example, if I was currently on slot a from the above getvar command I would:

Run flash-all.

Run fastboot -ab, to switch the active slot.

Run flash-all again.

I alternate the active slot each month, because I'm OCD like that. :D
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] smartymcfly:
"Files" app is a system app that can not be removed safely. The other Google files app is not a preinstalled app. The files app is essentially the system download manager.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Bryanx86:
Fastboot flash "whatever you're flashing " --slot-all
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] quan0509:
Folks!

Do i need to root my device after flashing this kernel to get the best it's experience & features?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DeeZZ_NuuZZ:
No it's like flash and forget, no need for root rights ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
the font is called san francisco

I usually don´t really mind a bit of off-topic in my threads, but in the last time it took a bit overhand.

Most of the posts on the last pages have absolutely nothing to do with the kernel.

Don´t worry about the posts it´s fine, I just want to encourage everyone to stay a bit more on topic.

Helping other people is fine, but with the topic being so far from the goal of this thread, even if that´s valuable info right here, nobody will find it, because it´s not expected to be here.

The guide thread from homeboy would be a good place for this, as this info might be very useful in his thread! But here it gets buried and no one will ever benefit from it.

As [MENTION=1205214]SacredDeviL666[/MENTION] already pointed out a few days ago, this clutters up the thread and makes it more difficult to find actual kernel related posts!

Just a hint for the future, as I don´t want the thread to derail completely! (no need to post and apologize or adress my post now ;) )

You don´t "need" root to run the kernel. All in build kernel improvements will work for you.

However without root, you won´t be able to activate/change features like wake gestures, sound related settings, vibration level, KCAL, KLAPSE etc.

Everything you would set in a kernel manager needs root!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] geeksammao:
Can't wait for the next release!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 123SIT:
Went in to take my final this morning, left phone in car, came back out after and phone froze then rebooted. Pstore folder in link below.

https://www.dropbox.com/s/y0bpa71h4i9a18h/pstore.zip?dl=0
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HiM@L:
where did you get this?

magisk module for SF font gives me lockscreen boxes.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Porogami:
Will the l speed battery tuner and governer provide worse battery life with this kernel?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] lssong99:
Got a strange issue here. After switch from stock root to 2.2.1, I can no longer get fast charge from genuine Pixel stand.. it sometimes go into fast charge but after 5 minutes it went back to slow charging, most of time just went into slow charge.

Any one has similar issue?

It seems normal with USB charge.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Face_Plant:
Just had a random reboot while the phone was in my pocket. I probably never would have known if I hadn't taken it out of my pocket just as it was finishing its reboot. Details of my 3 XL:

- April update

- Rooted with latest stable Magisk (18.1)

- v2.2.1 of the kernel

- No sketchy mods like Greenify, wakelock blockers, Xposed, etc

- Magisk modules: Active Edge Mod, GMS Doze, systemless ad blocking hosts, and NotchKiller.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Thanks for the logs! I found time to take a look at them.

It seems the logs posted by you two seem familiar when a reboot occurs. The logs are also similar to the ones posted previously. It looks like the phone is charging and suddenly the log stops.

No kernel panic is involved. Maybe it’s because of some changes from the Q base. I never experienced this reboot and currently I’m a bit in the dark.

I’ll try to change something in the next release and we see what happens.

Sorry for the reboots but thank you very much for the logs and reports!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
4.9.171 got released few hours ago.

I’ll merge 4.9.169, 4.9.170 as well as 4.9.171 and prepare a new release.

I’ll revert one little thermal change from the Q base, that might or might not be related to the reboots.

I guess I’ll release the new kernel tomorrow on Sunday.

I hope everyone has a nice weekend!

Stay tuned everyone :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Update to 2.2.2

Hey guys and girls,

so here is the next update. It includes latest upstream up to 4.9.171.

The kernel is now being built with latest Clang 9.0.3 from Google.

I reverted another small change from Q in the defconfig. Maybe it interfered with some Pie related stuff and solves the reboots.

The logs show no indication of a kernel panic so it makes it harder to debug or find the root cause.

I wish everyone a nice sunday :)

Changelog:

- Merge linux stable upstream 4.9.169, 4.9.170 and 4.9.171

- kernel is being built with Clang 9.0.3

- revert a thermal change from Q

- disable logging introduced from Q merge

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

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] EMJI79:
Updated easily with EXKM.

Works great as usual. Thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DvLAx3l:
With 2.2.2 the behavior of the pixel stand seems working like it should, give it a try!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
EXKM can't see the Kiri zip, can't figure out why. I still need to flash away from from the new TWRP, since it can't decrypt storage
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Face_Plant:
Their lasted release (3.3.0-1) is capable of decrypting internal storage now.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DeeZZ_NuuZZ:
3.3.0-1 should work fine now

edit: ah ninja'd now xD
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Yep, got it flashed. For some reason it killed my root.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Flashing TWRP will kill root since they both get flashed to the same location
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dd805bb:
Move it to elemental folder. Mine wouldn't see it either. Moved it and bingo. Saw it.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] geeksammao:
Hi, [MENTION=3428502]Freak07[/MENTION], I remember you said there will be several releases which each introduce some non-upstream changes since 2.2.0. Will these releases be published recently?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DvLAx3l:
[MENTION=3428502]Freak07[/MENTION] Seems I was wrong, it's just "fresher" so the fast charge last a little longer ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Please try to take a dmesg when this happens. maybe it will give me a clue.

Is the phone any hot when this happens?