yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
just a heads up, for those not subbed to my sailfish exns-eas thread... I may seem radio silent here, but rest assured; I have been quite busy this month working on my kernel... for those interested, you can pop over to the other thread - as a few things that I've been working on have been discussed over there;

https://xdaforums.com/pixel/development/kernel-oreo-exnoshadez-v1-0-beta-t3698709/page80

the last two pagesc over most things, but the gist;

#1 - I've been working on getting some more aggressive GCC optimizations working; the next builds will use GCC's Link-Time Optimzation (and eventually I'll be testing Profile-Guided Optimization, it's still WIP).

#2 - still tinkering with my boosting driver, but put it aside for a bit for two reasons (#3 && #4), not sure when it will be enabled by default, but when I finish #3 and #4 - I'll come back to it..

#3 - I've just completed overhauling the RCU subsystem (v3.x), which now based on linux-4.4, not 3.18 (not including any downstream/out-of-tree changes that I also use). this was significant work, completed over yesterday and today.

#4 - last, but not least. With #3 being completed - I will now be gearing up for Official Android P support (both kernels). the rcu stuff was the last big rework before P...

P should be released on the 20th, which I will be ready for (i'm flashing P tonight or tomorrow + adding all related kernel patchwork). that gives me a bit of time to test && also move some code from v.3.x to v2.x, before publishing builds...

there is more detail about this stuff in the other thread, but thought I should notify you guys, since I've been pretty quiet over here.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] borxnx:
The 20th huh? ;)

edit: Not insinuating that I'm rushing you or anything. Just a joke. I'm kinda (and pleasantly) surprised that Evan Blass's leak was off by two whole weeks. I'll be holding off on updating to Pie until you release your updates, and it's definitely worth the wait for me. Thanks for all you do, brother
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Every other year has been launched around the 20th (you can look it up yourself).

They are starting to roll 9.0 it out, but go and read the announcement - they cite "in the coming weeks"... but yeah; the 9.0 firmware images are available ~ I'll be posting new builds either later tonight or tomorrow (depends on my free time), but I'm mostly ready to go...and:

I'm already running the official 9.0 firmware already.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
sooo...

Just in the process of migrating Marlin Pie kernel sources/repo to gitlab (something I can do, while not home). Then when I am home, I'll get all of the rebase stuff merged/ready on android-msm-marlin-3.18-pie branches (both of my kernels), followed by grabbing some bits from v3.7 over to v2.9...

So hopefully, late-late tonight (if the last bit goes smoothly) I will have updated builds or possibly tomorrow (after work, worse case scenario), *if* I run out of time today.

in the meantime, the v2.x should be fine (while v3.x shouldn't be used ~ as there is a "showstopping" bug currently; but I do know the cause of it - so will be addressed / fixed in the next/official P build).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
HEADS UP: I won't post builds until tomorrow, so sorry for any inconvenience, but here's why; (and the state of things)

#1 - I've rebased all of my patchwork for v2.9, from scratch (tonight) on the vanilla Marlin/P sources (1000's of commits to go through)

#2 - I had to make a few small changes, as there were some differences in a few places (not unexpected, but I do want to test)

#3 - I've pulled in all of the changes to /drivers/staging/android/* drivers (binder, ion, etc) from v3.x => 2.9 + made a few small changes, reverting a couple of specific changes not applicable to v2.9 kernel. (differences in MM subsystem in v3.x).

#4 - I've added back && squashed in all LTS (3.18.100 => 3.18.117).

#5 - compiler fixes, bug fixes, etc.

While v2.9 is running on my device, I do need to give it a good run, due to the above (although, it does seems to be working great, thus far!) and also finish up the last few bits.... I've been at it since just after 5pm and its now almost 11pm... Sooooo! ~ i'm taking a bit of a break, then I'll came back and try to smash all of v3.7 off, before I go to bed tonight ~ it will be a lot less work, but still enough that it'll take some time (and I want it running on my device over night, during day).

* then publish builds and kernel sources when I get home tomorrow.

I could've probably just grabbed/merged in just the P changes, However, I was long overdue to just redo everything. I did do this like a month ago (and I actually used that as a reference), but I still did everything from scratch. ~ on the bright side, it should be dead simple to maintain now; 1000s of commits boiled down into 16-18 commits (upto 2v.9), not sure what v2.9=>3.7 will add upto - but probably a similar amount, a bit less.

anyway, no worries, there will be new builds tomorrow.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dark2099:
For the time being, did you say 2.8.2 will work on Pie or no?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
From what I've heard from others, leading upto the Official Pie firmware, yes ~ but I only briefly tested v2.9.2 (but it seemed fine), but I know v3.7 isn't (and i know why. it'll be a non-issue on the next build).

So i'd say, go for it (v2.8.2), worst case scendario; you encounter an issue and re-flash the stock boot.img from the Pie firmware image.... or just wait until tomorrow ~ as I will have them up tomorrow, just not until after work.

your call.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
Yes, it works great on latest P
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
So, I just flashed the rebased v3.7 to my device ~ finished up the rebase this morning and on my lunch.

Assuming, it holds up (it should now that the show-stopper bug is fixed), I'll be able to post builds an hour or so after I get home.

The only todo's left are to clean up a few commits, pull a commit from v3.7 back to v2.9 that fixes a bug, rebuild both kernels and make my new kernel sources publicly available....

Frickity-frock; v3.7 turned out to be as much or more work than v2.9 ~ I think I forgot just how much of the kernel has changed. LMFAO.

and on that note (read next post),
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bnmEEFaej:
[MENTION=7810360]nine7nine[/MENTION] No rush needed! I'm running your kernel on 8.1 stock and I just wanted to say thanks for doing a bunch of hard work! My games run much faster and opening apps is way smoother! Don't forget to take a break!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
LOL. Oh the rush is needed; Pie is officially out! ;)

It's cool though, I stayed up until 3am / followed by some early morning hacking, followed by afternoon hacking to get v3.7 running.... and when I get home, I'll finish up on both kernels.... so I'll push builds in a few hours.

only break will be dinner time. I can sleep, after I've pushed builds. LMFAO.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bbender716:
At least make it more than ramen microwave before getting back at it!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Ok, sooo..... delays, delyas, delays..... but some progress; (I've commented in the sailfish thread, but forgot to here.... I ran into some issues and couldn't push Pie updates, yesterday - I went to bed instead, super frustrated.)

So I haven't been able to push Pie builds due to some (subtle) conflicts that are causing me grief.... This is compounded by the fact, that while i do have some off-time/away from work ~ i have some other personal stuff going on (nothing bad) that is occupying a lot of that time, so it's slowing me down a lot.... by the end of the week, I am going to get really busy ~ so I basically need to get these issues resolved before then, but finding the time is difficult.... So it may be a couple days before I can get P builds up, but obviously v2.8.2 will work until then....

Now, onto the progress; I believe I've narrowed down the changesets on Pie (from the DPs) that are the cause of the problem. Currently (as in the last 10min), I've got my v3.7 kernel (the 8.1 kernel) working on Pie, just as the v2.8.2 has been (at least, it appears that way - I'll know for sure by tomorrow).... If v3.7 pans out, I am going to do the following;

1. publish the v3.7 build that works on Pie, which was for 8.1, but has a lot of changes since the July build. (that I'm testing now)

2. Then I'll Selectively revert/cherry-pick through all of the android Pie Marlin commits, avoiding the problematic commits...

3. I'll take all of those (non-problematic) commits and (re-)apply them to both kernel trees + LTS patchwork

4. Then build + Publish both v2.9 and v3.7 for you guys

The problematic stuff will get resolved (100%), but I see this as the best compromise and way forward, with limited time / resources.... Then I can work on the tricky bits and commit them back later (in a few weeks), when I have more time to do so...

again, sorry for any inconvenience ~ but it hasn't been too fun for me, either! ROFL. I wanted to smash things yesterday, today a bit better.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
deleted - double post
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
So v3.7 seems to be running great, I did hit one bump ~ but a patch that I haven't applied yet from Pie kernel will fix it, other than that I haven't noticed any problems (just minor bits that should be addressed when I add Pie's patchwork"....

So, when I get home I'm going to try and get that stuff merged - give both kernels another whirl and hopefully post new builds. So barring any issues ~ at the very least I will have a new v3.7 build up that works on Pie ~ and if I can scrape together enough time, I might be able to get actual Pie builds up (We'll see, could happen late tonight, or maybe not until tomorrow ~ it all depends on timing and if I hit any issues).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
OK, so after some headaches and distractions:

i appear to have fixed the crash that has been blocking me releasing Pie kernels... it was a bit of a pain to fix, because the crash exposed other kernel bugs, so it was unclear, at first, what the actual problem was (and it's a bit specific to my kernel. ie: non-issue on vanilla marling sources...).

the crash was happening when using USB/otg... due to differeneces in the MD, block and driver/base of my kernel, i had to backport some code + fix the issue itself... but USB/otg seems to be working, as expected now...

so, I'm going to test over the next 24hrs + import the needed changes for v2.9 (and give it a run too).

the upside here (bug fix aside) is that i also (as mentioned) pulled in the Pie related changes + LTS 3.18.118 *and* I've updated Swait (simple workqueues) to match the never mainline implementation && i think I'm ready to enable boostbox for v3.7 too...

anyway, assuming no mor problems; tomorrow tonight I'll try to get Pie builds up...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Glad I'm not the only one lol.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
yeah, not sure what the deal is there, just hit it. I'm sure it's something simple/overlooked, or a bug (i haven't used / generated debug info from AK2 yet - one of tomorrow's todo's)...

I'll let you know what i find.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] almightysiman:
I just flash 3.8.1p and the kernel version show as below,Is that somthing went wrong?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
frick, something got mixed up, fixed now.

amn, I'm glad that notification woke me up ( so thanks!).

re-download flash. it should be corrected, should read

3.18.118-exNoShadez-v3.8.1

gcc version 8.2.1 201808
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
also, hold up ~ you-re on 8.1 ??? I haven't tested this with 8.1 ~ stock ROM is Android 9.0, so there is lots of code brought in that is either for Pie ~ or stuff that I didn't use on 8.1....

I guess let me know, what happens. yer probably getting close you upgrade time though, with 8.1 pretty much being done, no?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] almightysiman:
Thanks,glad to know that.I'll find time upgrade to Android 9 and reflash your kernel!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
no probz... yeah, 9.0 was a bit of an adjustment for me, but some of the redesign is pretty decent...

for the most part I've got it setup to my liking though; ditched the pixel launcher, setup Apex v3.3.3 and resigned the Apk with my own keys, so that playstore can't update it.. put my pixel in full immersive mode, which seems to work nicer on 9.0...

and of course, got v3+ kernel running. although, i still have a long list off TODOs... and of course; get v2.9 up and working.... although I'm hoping more people switch to v3.8.1, as beyond maintenance, i don't plan on adding new features to v2.x... i plan to continue to evolve v3.x, around android 9.1 / v4, i hope to drop v2.xentirely, that's my goal anyway..
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Just a couple things that I didn't mention about v3.8.1 that I posted yesterday.

ref: https://xdaforums.com/showpost.php?p=77328332&postcount=837

ref: this build; https://github.com/nine7nine/Apps/raw/master/exns_eas_v3.8.1p_b325e69.zip

There are a couple of things that will seem wrong, or like a bug in EXKM.

#1 - under CPU section, you may have noticed that the min CPU freq isn't correct; e.g: showing a previously cached value or doesn't reflect what cpufreq is doing ~ this doesn't matter && is entirely normal / expected... You also cannot manipulate the min/max CPU values, either ~ userspace has been blocked from doing such things (this includes crippling msm_performance, as well).... Boostbox manages this stuff. it controls the min boosting values and handles boosting events. (it's the entry point, to change these types of settings).

#2 - You may have noticed that there is no traditional touch-boosting on v3.8.1 ~ this is very much intended. Perfd/msm_performance does crazy ***, like boosting the big cores to 1363mhz for a second or two, which is quite excessive... I've found that it just isn't really needed due to a few different factors on v3.8.1. (where threads/tasks are placed, which cpus they run on, boostbox, etc).

#3 - Currently there is some spam in logcat to do with Perfd being disabled (and also some other unrelated warning/errors that will be fixed soonish / A.S.A.P.... Some of it has to do with a few bits for P that I haven't pulled in yet, while there are other bits relating to my kernel ~ most are NOT critical issues, which is why I haven't dealt with them yet, since my time has been limited.).

anyway, no one has mentioned noticing any of these differences, aside from someone PM'ing me about #1.. But I thought I would point these out, for the observant / curious.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
Delete
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Yes. It should be pretty stable... I haven't had any issues after fixing the initial big problems, when I first started using Pie... It should be in reasonably good shape && to be honest; I would prefer that you/everybody gives it a try.

The sooner that I can focus on just one EXNS/Marlin kernel - the better it will be for everyone. Right now, I'm wasting a ton of time working on a 2nd kernel that I don't use (aside from testing).... Maintaining v2.x has become burdensome (but it has been necessary, I'm not sure how necessary it is now though). It's not a huge burden for "month-to-month" patchwork ~ but when bigger changes drop (like in P), it becomes a real headache.

I'd love to never look at it again, tbh ~ and put all of that energy, time and resources into making v.3x better.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Why delete? seems like it was a valid question...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
Did you read it lol? I just came to my own conclusion it wasn't as you've disabled a lot of stuff, i.e. govorners.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I thought so;

"So, is 3.8.1 stable for the most part?? I'm still on 2.8.2" ~ you.... I was replying when you deleted it.... So there was more to it, about governors?

I've disabled all of the useless CPU governors, yes. correct. ;)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
No, nothing more to it. I just wanted to know if it was stable enough for everyday use. School starts back up soon and I don't have time to mess with it 24/7 lol.

---------- Post added at 01:31 AM ---------- Previous post was at 01:30 AM ----------

No, nothing more to it. I just wanted to know if it was stable enough for everyday use. School starts back up soon and I don't have time to mess with it 24/7 lol. By the sound of it I should wait for 2.9?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I think I covered that in my other reply above (post #1135)

but yes, it's been pretty stable since I fixed some of the initial issues... I think you should give it a try....

I also need my phone functional all of the time (for work, especially), so I can appreciate where you are coming from (it's also why i forked 2.x in the first place to work on v3.x - I needed to provide a stable kernel while I did a lot of the drudgery in the new kernel)... I believe that any big issues are resolved, what remains shouldn't cause you issue ~ some of which I've already fixed (for the next build).

No, you should try the v3.x kernel... the worst thing that can happen is that you switch back over to v2.8.2/v2.9, if something is wrong ~ The longer people cling to v2.x means that neither kernel will get the work, time or energy put into them that they deserve ~ I really would like people to try v3.8.1 ~ rather than wait for v2.9.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
Will probably give it a whirl tonight... After this episode of Breaking Bad of course ;) Thanks
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Cool. That would very much be appreciated. Thanks, Craz...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
Oddly, the volume rocker is unresponsive.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
That's odd. Given that mine works just fine.

Are you using any thing that you can think of that might be playing an issue here?

(like a magisk module or something like that?)

...because not only does mine work fine, I just texted my friend and he hasn't had any issues with it, either. (and I'm sure I would've heard about it, if he had ~ as he was the first person, aside from me to use 3.8).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
This used to happen to me too (but I've had audio issues with multiple kernels, lol, probably a hardware thing). I'll flash this later on tonight and give it a good run, though. It's not really fair of me to report a potential bug and not even be using the kernel atm ;)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
Ran into a few problems actually, just flashed back to 2.8.2. After a few reboots the volume rocker problem sorted itself out, but system crashed a couple times, it would do a soft reboot sorta thing... Brightness would turn up all the way and a few seconds later it would bring the "Pixel is starting" screen like it just rebooted. Did that twice. My service wouldn't always be connected, and when it did it would be super terrible.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bbender716:
Rock solid today so far. Mostly browsing, music streaming and watching Netflix but running smooth!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
So it just did that reboot thing on pie. I'm gonna flash stock factory image and try the later one
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Well, that sucks.... I wonder why it is so unstable on your device (?) ~ yet not unstable for other people that I know... I haven't experienced any of those issues, nor problems with service (you mean data/LTE, right?)... I've tested nfc / google pay, bluetooth (car and speakers), etc, etc... all that jazz

Can you please check /sys/fs/pstore for logs ~ and upload them to me? that could be incredibly helpful.

Irony. lol..... don't you think? (given the comment above yours)... Keep me posted on anything else, observations, etc (you probably won't get a feel for battery until you go through a cycle or two, with similar usage.).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bbender716:
Weird! Fwiw, I'm on sailfish, flashed via FK's app.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
Yes, LTE. And I pulled the pstore folder via adb and nothing's there
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Out of curiosity, who is your carrier?

The only time Ive ever had issues with LTE on the Pixel, was during 7.1/Nougat and a bit into 8.0 ~ there was a bug report, where there was a problem where you would lose data connection and it wouldn't turn back on until rebooting the device (but I stopped experiencing this early on after 8.0 release).

The lack of pstore having any of the dumps is annoying (that can happen, but it's somewhat rare). hmmm....

Well, you mentioned doing flashing stock images (which isn't a bad idea, just make sure that you hose magisk too)... I would say beyond that ~ maybe next time, if it happens again see something will show up in pstore, we may get lucky. you could also try and generate a full bug report and send it to me (in developer options)...

also, just an fyi ~ I've technically updated the build too ~ so grab it, not the old build. (it's the same link though)

https://github.com/nine7nine/Apps/raw/master/exns_eas_v3.8.1p_b325e69.zip

it's not hugely changed, but it has some && I also had updated the build lastnight (due to a mix up), so in the off chance the build you are using was that build (shouldn't be, as i replaced it quickly, but...) ~ it would crash, but it also wouldn't be the correct version of the kernel which is;

3.18.118-exNoshadez-v3.8.1 / built with gcc-8.2.1 ~

the borked one / mixed up files was a v3.6.x / built with linaro
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Interesting, thanks... ya, take a look, shag.

idk, I have never (ever) had issues with the volume rocker being unresponsive...

but then again; we all know that the OG pixel's hardware was kind of a flop ~ lots of RMAs, mic/speaker issues, silicon issues and poor Quality Assurance, in general....

I do know that I've got one of the good ones, no real H/W issues at all, I can overclock it, all that jazz ~ without losing stability...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Yeah, it is weird.

Something is going on with his device ~ but without any additional info I have no idea...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
AT&T. And after flashing stock P, and flashing 3.8.1, the only error was the reboot error. And once again, nothing in pstore :/ I'm on 2.8.2 and all seems well. I actually don't have WiFi rn so I'm not gonna grab that latest version yet, sorry. I'm gonna stick where I'm at unil 2.9 I think.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] AllusionPDX:
I'm waiting for the final bug fixes then I'll be swapping back to this kernel. Does anyone have a recommended app to update this kernel?

installed: can confirm playstore bug. magisk works with the beta version, and can also confirm volume rocker bug. swapping back to elementalx until update
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kingbri:
Auto flasher on EX manager works well
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] roblav96:
[MENTION=7810360]nine7nine[/MENTION] In the OP you recommend `write /sys/module/cpu_boost/parameters/input_boost_ms 100` but the default setting is `1000`. Should this be `100` or `1000`? Thanks mate =]