yashsingh1/xdaforums huggingface dataset:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
if your bootloader is unlocked, all you have to do is flash magisk (lattest beta, linked to on the OP) via twrp, after flashing the kernel zip...

if you haven't unlocked your bootloader, then u would need to that first...

please note: don't thread Jack like this. it is expected that u already know how to unlock your bootloader, use twrp, root, etc.... there are dedicated threads for rooting, etc. go there for help.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] buddyb0i:
gotcha, sorry for the thread jacking nine! Thanks for the response!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
not a problem at all. I'm just pointing out forum etiquette.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
so that kmsg was useless (not your fault though). the call traces seem to be from twrp, not actually my kernel... might be due to the subsequent reboots, no idea.... but the call traces point to scheduler code that doesn't even exist in my kernel...

so maybe better luck next time. I wish I could reproduce these random reboots, but I've had zero luck... I've also read in the pixel forum a thread on random reboots, people not using my kernel... it makes me curious, if there may be something else going on, but until I can either trigger it myself or get more useful logs; not much I can do
[Google Pixel ROMs, Kernels, Recoveries, & Other De] almightysiman:
Thanks for your effort,since it's all fine now,I hope it won't happen again!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
thanks. yeah, it's an odd one.. if everyone was experiencing the random reboots, I probably would've heard about more, but that doesn't seem to be the case....

there are also a lot of potential variables here, some not even having to do with the kernel; it could be a userspace issue, a hardware error (which I know there are some current bug reports with random reboots)... and obviously it very well could be a kernel issue... who knows...

it's one of the reasons I wish I could reproduce it. so I could rule a few things out and have a better look at the cause.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] buddyb0i:
if i am on OPM1 build dec 5 patch would that be giving me an issue with the twrp img not flashing in adb and allowing me to flash kernel and magisk?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
no. everyone is using OPM1. .... you don't use adb with twrp img, you use fastboot...

fastboot boot path/to/twrp.img

that'll get you into twrp, then u can flash the kernel and magisk...

that said, this is a noob type question and I think you should read through threads on adb and fastboot, so that u know the difference / what they do.... and maybe read one of the installtion guides for the pixel.. I don't really want to be spending time on these types of questions...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sgace:
Hi,

Thnx for you're great work.

Is running the standard setup the way to go when flashing this the first time?

Cheers
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
'standard setup'? what do you mean?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] alladinscastle:
Yes, this i am going to use. Yes
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sgace:
The basic settings as you implemented them, like frequencies and stuff.

Cheers
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
well, shouldn't need to touch cpu frequencies, the cpufreq governor manages that... just make sure ur using schedutil (you will be by default), as not using schedutil defeats the purpose of using an eas kernel... only time I change frequencies, is if I'm using the performance governor in performance mode to disable frequency scaling - but I only do that for a couple of applications, where its beneficial...

and just a side note; I don't / won't support overclocking. I know some people do that on android kernels. it does give a performance boost. but I'm doubting the msm8996 SOC was really intended to be overclocked and I'd rather not put people's devices at risk... on a PC if you Cook your CPU; it can be replaced... on an SOC - you're screwed... I'm also guessing OC probably degrades, causes additional ware to the battery over time...

not sure what other settings you want to know about or change. but the defaults should generally be good
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sgace:
Thnx for you're detailed reply. Am rocking it with defaults for the coming days and it's great till now:svetius:

I'm in noway looking for overclocking and am glad you won't support, cause the risk is just to great for the small benefits and it's always somehow unstable for me as the past has proven me.

Cheers
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
I try to keep good defaults. imo, it seems silly to leave it to or expect users to have to configure things to get a good experience...

cool. didn't think you were, just came up because of the cpu frequency mention... yeah, I wouldn't add overclocking, there are other ways to improve performance, rather than OC. far less riskier ways...

I may add a patchset that I have kicking around that yields some significant boosts in performance, but it's not quite ready yet. in the new year I'll iron it out.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sgace:
Cool, looking forward for things to come:cool::svetius:

Happy holidays.

Cheers
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
thanks! you as well!

ya, I have a number of things that I'm working on. so there will be some changes coming in the new year with my kernel.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sgace:
Thank you.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sgace:
So, rock solid after 4 days. No problems at all.

Battery is slightly better as stock for my usage:laugh::good:

Cheers
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bladels:
I noticed performance seems to take a hit when battery goes below ~30%. Anyone else has this problem?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
please provide data that supports this claim / observation.

there's nothing in place that throttles your performance at < 30% in the kernel or userspace.... that only happens with battery saving feature in android.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bladels:
It's just my observation, I don't know how to prove it. I notice slight stuttering when battery is below ~ 30%, everything else has been really good so far.

Like I said before, I'm a performance freak so maybe it's just in my head :P
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
ya, idk. tbh, your description of 'slight stuttering' lacks any context and is pretty vague / non descriptive...

my device was well below 30% earlier; videos, no stuttering... switching apps, animations, etc smooth...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] slanidracula:
Running stock 8.1 with magisk15 then fastboot flashed the stock boot.img in both a and b slots. Then fastboot booted into twrp3210, then installed the kernel and magisk linked from the OP. Now I get the "no command" android. I've repeated this four times. Any suggestions?

UPDATE: I went the nuc option and flashed the ./flash-all.sh script of the dec update image (instead of a fastboot flash of a and b), then boot twrp, install kernel and magisk. A boot loop, then it booted into system with the manufacture warning.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
hey all,

I know the Jan 2018 release is out today, however ~ I won't push any update until tomorrow. * That's the first chance I'll have to be at home, in front of my linux box, to patch the kernel and update. ~ My holiday / housesitting gig isn't done until tomorrow.... At that point, I will push a quick update fo Jan 2018, but after that I'll be doing a rebase and numerous updates to my kernel... So within a few days of that; I will likely push a bigger update.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
hey all (again. lol),

So I'll have an update in a couple of hours (i just want to run it for a bit) ~ I've updated to Jan 2018 firmware, have updated the kernel with the latest Jan patches, LTS 3.18.91 and have also updated Anykernel2 / flashable zip (integrating the latest changes for Magisk / overlays and Pixel changes).... The updating process going forward will be slightly different. (but a bit better, in a couple of ways).

When i push the update - I will update the OP instructions and post here too.

In a couple of days, as I mentioned; I will be doing a bigger kernel update, as well. But I just wanted to get a Jan 2018 kernel up, asap.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
UPDATE: https://github.com/nine7nine/Apps/raw/master/exNoShadez-eas_595ec20.zip

No major changes, beyond Jan 2018 patches, LTS 3.18.91 and updating the AnyKernel2 flashable zip. I do have kernel changes coming, but I wanted to quickly push this update out to go with the Jan 2018 firmware. No time to work on kernels until the weekend.

Ok, so from now on - do NOT flash magisk zip after the kernel, instead magisk should be installed before-hand (the flashable zip will detect it's presence).... So, if you've just flashed the Jan 2018 firmware (with the stock boot.img), you will need to flash Magisk first ~ followed by my kernel zip.

This is now the process, whenever coming from stock or a monthly firmware update (where you've lost root). NOTE: On subsequent kernel updates, with Magisk already installed (between Monthly firmware updates), you can just flash the kernel (you won't lose root/magisk).

Please also be using the Latest Magisk Beta (v15.2); https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
just as an aside, things to come:

I have a bit of time tonight. so I'm going to work on some changes for the next build... I've got some changes to binder_rt coming, a number of one-off cherry-picks; stuff that I just didn't have time in December to merge, I'm going to have a stab at improving the locking stuff that I mentioned in this post; https://xdaforums.com/showpost.php?p=75076353&postcount=581 (XL forum). Some updates to a few drivers (that I'm going to break to upgrade some other kernel stuff), some scheduler code upgrades..... I'm going to ditch zram and have some other bits that I'm working on too.... some of the mentioned stuff is already implemented and running on my device, while others I'm just digging into now.

I'm working off my current/local kernel tree, but on the weekend - I'm hoping to rebase the whole thing, with all of the new changes integrated, lots of cleanups, etc too... Then I should be able to push a more substantial update, that's largely been tested for at least 48hrs.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Bryanx86:
When fastbooting boot.img reboot once before flashing magisk and kernel. This solves your problem.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
If anyone is interested of feeling the need to flash a new kernel. While, I haven't finished with my new kernel tree, nor published it on github, I am testing code and therefore pushed a build. ( and just lumped in a 1000 patches into a couple of commits, with a shell script and committed them to github )

https://github.com/nine7nine/Apps/raw/master/exNoShadez-eas_952eb59_test.zip

the changes are numerous; FS, VM, Block, Memory Management, Binder, etc. Because I touched MM, I had to bump up zram too (also I've reduced swappiness... and it's rarely used anyway.) ~ so I matched zram to the msm8998 version (I'm lazy, so it took all of 5seconds / drop-in replacement. lol). This build is also not using Linaro GCC 7.2.x ~ It's using GCC 8.

I still have a lot of code to merge in, but I'm running this build for now, While I continue to work on code, integrate changes and test (with my current tree)... Other stuff I'm working on; Schedutil, scheduler and energy aware changes, I have binder_rt changes that haven't landed yet (but are running on my device), pulling KSLR changes that landed in AOSP today and as soon I i finish unbreaking the last few drivers, I should be able to remove a rather large bottleneck in I/O performance (present in all older kernels).

I also have a ton of Memory Management commits to go through (and some supporting/related code), as I have plans of getting some code to run with concurrency, that currently does not (on any android shipping device ...and only works on semi-new mainline kernels). I took a look at other custom/android kernels, thought maybe I could speed the process along, but even the ones that have some newer MM commits; are missing a crap ton of commits, brutally so ~ so not really helpful / better off just doing it myself...

So I'm guessing, It might be a few more days before I get a fresh kernel tree on github + a new stable build. But hey, I can still post a test build or three, in between ~ for those who like tinkering.... I expect there may be the odd rough edge on this posted build, although it's been running fine for me, thus far. ~ lots of new code, switching compilers, etc => so if the stable one is working fine; Don't feel the need to switch or anything like that, I just know some people like to, so I'll post a couple until I get everything merged in / a new stable build.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] KittyRgnarok:
Found a solution to not being able to have twrp n the kernel not compete with each other for space while messing with custom ROMs. The PixelDust rom seems to have twrp integrated as part of the rom. it requires twrp to be installed as opposed to fastbooted when flashing the rom, and flashing this kernel on top of the rom seems to also keep twrp
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
meh. ... that's not really a (general) solution, necessarily. given that it requires flashing a custom rom, right? ?

still cool that it's working for you... but I'm really not overly interested in having twrp work instaled, on stock.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] KittyRgnarok:
Ye no I totally agree it's not a kernel based fix or anything but since everyone was requesting kernel+twrp I figured I'd post this here for them to find.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
agreed. thanks for posting.

good for people who might be using that to know.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
another test build (still a work in progress), but flash if you like.

https://github.com/nine7nine/Apps/raw/master/exNoShadez-eas_test3.zip

lots of changes;

- scheduler code

- serial/tty drivers

- rt/mutex && (pi)futex updates

- locking updates / fixes

- workqueues updates

- misc fixups and changes

any instability, either report (including a full bug report and contents of /sys/fs/pstore) or switch back to the stable OP build, until I've finalized all of my commits (which will likely still be a few days... busy week).
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sgace:
For a little positivity:laugh:

This is what I managed to get with the test1 build from a few days ago. For my usage this is huge! Thnx alot!

I had 15% battery left so dont mind the 56% in the screenshot as it was charging for a little while.

Also; no strange things or crashes or something like that, just rocksolid.

Keep it up:good:

Now testing testbuild 3

Cheers
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maielsboy:
I keep getting "No command" error after flashing

What I did:

- flash full stock jan 8.1 image

- booted intro android, skipped everything in setup until i could use the phone

- booted into bootloader and did command "fastboot boot twrp 3.2.1-0.img"

- from twrp installed kernel.zip, it said succesfuly installed

- reboot system

bum, "no command" error and loops
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sgace:
Enter fastboot again right after the no command screen and flash kernel a second time, then reboot. Worked for me this way.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
why you didn't install magisk before the kernel?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maielsboy:
I thought magisk was not mandatory to install, or is it?

I just wanted to test another kernel, not for permanent usage, because I have some troubles with fingerprint on stock 8.0 and 8.1 and maybe will get fixed.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Sigh... I really wish people would read the OP;

I did make a comment a couple days ago about how AnyKernel2 detects root or non-root cases ~ but I never said that I was interested in supporting non-rooted devices and the OP makes it very clear that i, in fact, do not....

....and fyi; I don't do anything with the fingerprint sensor in the kernel. I've seen other kernels, for various devices where people use boosting ~ but I don't see the point. My device unlocks quickly, on every try.... I don't know the nature of your problem - but if it's that it takes multiple tries to unlock, that's usually pretty easy to fix;

1. register the same fingerprint more than once

2. when registering a fingerprint; make sure you are capturing it from all angles/portions
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maielsboy:
Oh, rip. Sorry, my bad

The problem with fingerprint is that it crashes the phone whenever I use it, like 4 seconds freeze and a reboot. Stock 8.0, 8.1 does not work for me, tested like 5 different images. But, working fine on latest 7.1.

I will leave a link to another thread I opened with this problem. There are 2 bug report logs in comments, if you want to take a look https://xdaforums.com/pixel/help/google-pixel-setting-fingerprint-causes-t3733136

I found this in last kernel log, right at the end of file, and thought that it is some kind of kernel error

SMMU GLOBAL CLIENT SEC FAULT: bit mask=0x00000200
[40] SMMU:>> ANOC1 Sec Global Fault:
[40] sGFSR=0x00000004
[40] sGFAR=0x000000000b151404
[40] sGFSYNR0=0x00000000
[40] sGFSYNR1=0x00940094
[40] sGFSYNR2=0x00000004
[40] SCR0=0x00200626
[40] SCR1=0x00013207
[40] Fatal Error: NOC_ERROR
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Hmmm.... yeah, iommu code. 'll have a look at your full logs in the other thread later....

Off hand, it's unclear whether this is an actual kernel bug or a subtle HW defect/issue. It could easily be either... You might have luck trying another kernel, but it also could be that the older version of android, paired with an older kernel - just doesn't hit this issue (if it is a hardware issue)....
[Google Pixel ROMs, Kernels, Recoveries, & Other De] willyumlu:
when we update magisk, do we have to flash the stock boot.img first before installing the new magisk zip?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
no.

but sometimes I use the magisk uninstaller zip, as I've found that some magisk updates end up crashing magisk manger, unless I remove it before updating....

another thing; I also tend to disable update notifications from magisk and manually update (rather than being nagged to).

anyway. that's more of a magisk question, which there are other threads for....
[Google Pixel ROMs, Kernels, Recoveries, & Other De] willyumlu:
sorry, i meant after we have your kernel installed, what's the process to update magisk? is it simply just flashing the new magisk zip?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
read what I wrote.

I'm talking about updating magisk, with my kernel installed.... yeah, it's usually that simple (you can do it in magisk manager.

too), but as I mentioned ~ sometimes magisk breaks in updates, so if that happens, you may have to uninstall magisk and re install it....

anyway, as I said; visit the magisk threads fir magisk understanding and support... that's why they exist, right?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] willyumlu:
i didn't know if the process to update magisk was different for your kernel, and wanted to ask people who were familiar with yours. thanks for the help and developing this awesome kernel
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
no. it wouldn't b a different process... magisk just patches the bootl.img, installs magisk manager, etc... kernel doesn't matter.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Nil253259:
A pitch black theme can really make difference in terms of screen on time. I got Swift black installed, SoT is 5 hours from 90% to 15, that too on full data (no WiFi).

There might be other reason as well, as I just clean flashed stock from crDroid and changed things a bit as my daily driver ( installed Nova again, been on pixel launcher for quite sometime, uninstalled few apps which I don't use frequently and moved to Hermit (loving it), deactivated Google feed (not useful at all, I use foss app feeder to just read things which I'm interested in),

P.S. I'm on test 3 and have never had a single issue, so never went back to last stable :)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
so Feb update is out, but I likely won't push an update until later tonight or tmrrw morning (I have some tech support work to do after work tonight)...

my plan is to push a stable build, based on the stable build (+ Feb patches). for the 1st update..

the reason being is that yesterday I triggered that bug from the test build where the device doesn't wake up, on my local build - but I did this via messing with the IRQ thread priorities - which sheds light on why the device wouldn't wake up; a thread was being blocked... so i'm going to recreate the issue, verify what's being blocked and also enable lockdep to verify locking behaviour... this way I can be sure that I've fixed the issue, before pushing a more substantial update...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
in other news;

1. google appears to have broken encryption for twrp again (so flashing will require either putting zips onto a usb stick and flashing them that way... or disabling your screen locl to decrypt and read/access the zips from internal storage).

2. my stable kernel from Jan 5th seems runs fine on with Feb 5th (unsurprisingly, but obviously will be missing any updates, until i update ;))

3. Google appears to have listened to me, when I complained to support last month over that stupid 'stage light' shadowing that you see when pulling down notifications or when you are on the lock screen ~ It looked brutal with a black background and dark theme ~ they have significantly reduced the opacity of the grey shadow / overlay....

Frick, they actually listened for once! => and all it took was me (and a hundred other ppl) complaining, then screen-sharing with their support person and her getting me into contact with with the development team and explaining to them why it looked terrible. LMFAO.

4. Magisk works fine && so does xposed, AFAIK / no issues yet.

5. I haven't noticed anything else new or different (although, I don't have too much time to explore && I don't use many google apps or pixel launcher)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] siheals:
Can't wait to try it but the previous kernel had been great.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
cool, thanks, siheals!

yeah, I just really need to verify the wake up bug is resolved before I push the bigger update... once, i'm reasonably sure, I'll throw a build up...

my local kernel has some nice improvements though. I've reworked some if the scheduling and locking (both core locking and file locking), there's a few new features (although, they should go unnoticed / no config involved) and SOT for me, has increased by about an hour...

on the Jan 5th stable kernel, I'd average 7hrs or just under. now i'm getting 8hrs (based on the last few weeks of use).
[Google Pixel ROMs, Kernels, Recoveries, & Other De] siheals:
Well that looks like a very nice and significant improvement.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
so I didn't get home until late lastnight and ran out of time this morning to update the stable build, but tonight / after work I'll get it updated. shouldn't be an issue.

sorry for the delay!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] siheals:
No problems so far