yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
You are probably right; their shouldn't be issues with ASOP - but I just can't test against it, is all... I could be wrong here; but IIRC - their build of chromium is dependent on a patch of two in their AOSP sources. the rest shouldn't be though.

Building roms can be tough sometimes for sure. Back a couple of years ago, I had to add undocumented symlinks && hacks into the sources to even get it to build on Archlinux (that's changed now)... And AOSP is so huge that there are a million of things that can go wrong.... Especially, anyone in the position of maintaining a large delta of patches/commits against it (I was, like 50+ patches)... I had things working quite well and became pretty familiar with AOSP, the build process, etc...

After CM-14.1 was released I started hitting problems to do with Odexing my rom (Previously, I had been using it but it stopped working / broke... A while later my phone was damaged, so I bought the Pixel ~ decided I was done with baking ROMs, at that point.... The kernel is more of a "must have / must do" scenario, for me.

As mentioned, I did build AOSP for the Pixel, but I only ran it for a day, before switching to stock ~ Also, I do use Google Play, Google Earth, Maps, etc + I tend to buy apps, including any opensource / free stuff (where I'm not obligated to) - I always buy the donate version too because I think it is important to support developers of all kinds; writing apps, modifying our devices, etc - is hard stuff. So for me, Gapps has actually become important. (plus, there's just too many good apps not available anywhere else).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ChongoDroid:
Same here, I've got hundreds of dollars in paid apps. I remember how frustrating ROM building can be. My first and only real project was aospa with -O3 flag enabled for everything and no build errors which was absolutely impossible for a n00b like myself.

It's my birthday today and I've got the day off so I'm bored and I wanna tinker lol.

Theoretically kernel testing on a device without gapps should eliminate complications with misbehaving apps

---------- Post added at 09:12 PM ---------- Previous post was at 09:07 PM ----------

Anyways, I won't go off topic anymore, just thought there should be at least one 8.0 rom on XDA. Even if it is plain stock.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Well, -O3 optimization is often a bad idea - lots of code does NOT benefit from turning on -O3 .... In fact, it can often be harmful ~ depending on how the code is written. I'm betting using less optimization actually produces a faster & more stable ROM. If -O3 was well-suited for AOSP, they probably would be using it already.

HAPPY BIRTHDAY! ;)

Well, in theory, yes ~ but misbehaving apps can sometimes reveal problems/issues, so I'm all for them. lol... But yeah; Gapps, in general - has a crap ton of stuff in it and obviously can/does make a rom more bloated, for sure...

No worries, while slightly off-topic; It's an interesting topic, so I don't mind. (plus, it's your b-day, sooo.....) ... I only care when people go off topic (the last time) when they are actually hi-jacking the thread to get help / support for stuff that's irrelevant to the discussion (*and could easily be addressed by going through the proper support channels/threads ~ or using google. lol)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ChongoDroid:
Haha thanks man!

Yeah I mean it was lightning fast on my Nexus 5 but you're probably right. A lot of the patches back then were placebo effect. I think it's one of the reasons development is slow on the pixel is because everything is already optimized quite well. I also added support for OpenVPN before Android added it.

The OP is so embarrassing now, my God.

https://xdaforums.com/google-nexus-5/development/rom-codename-fr05ty-aospal-o3-odex-t2865962

?

Source is almost done downloading! Time for some coffee and cake! Haha ??
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
[MENTION=1007992]everyone[/MENTION] - I'm probably going to add WireGuard (VPN) to the kernel;

https://www.xda-developers.com/wireguard-vpn-project-support-android-roms/

I've actually already added kernel support / commited in github.... and all of the userspace configs / binary are in place - just gotta find a VPN that supports WireGuard and give it a good test... Pretty cool stuff
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ChongoDroid:
Wow that sounds fantastic. I would actually use always on VPN with this.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Well, so far - It's been a bit of a pain to setup. (not the kernel module, that part was easy)...

But I had to manually install a few userspace bits and configuring th VPN (manually) for AzireVPN has been a bit annoying, actually just waiting for some help with that / info. I'm semi-stuck, ATM...

But if I can get that resolved and WireGuard tested; I could probably provide a flashable zip for the userspace parts and possibly a template for AzireVPN.... But end-users would still need to generate their keys and manually edit the template... not much I can do there....

I also wouldn't be able to help with setting up any other VPNs or general use with WireGuard ~ I'd pretty much be providing the kernel support... It's like my BINFMT_MISC support - it works, but still requires the user running some commands to mount and enable that support (to use with say; Linux Deploy)... This kind of thing goes beyond me enabling kernel support, so I'm likely not going to spend time helping users setup this kind of thing; when I have already done my part (making it available in the kernel).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
So, Audio driver hacking, some interesting results;

I'm currently testing some of my audio driver backports / improvements. It's hard to do laboratory type tests, but I can do more real world tests, that involve hitting the audio stack pretty hard on the Pixel.... The real word tests are probably more important anyway - since they also include interactivity (meaning surfaceflinger could be sucking up some cpu-time, touch inputs, etc.... For my tests, I'm using Beatonal - for two reasons;

1. I can measure xruns (buffer underrruns) in realtime

2. It is an app that uses a boatload of cpu / processing

I set my device in Performance mode with the Performance CPU governor set as the cpu governor ~ this is to avoid any cpu scaling; I'm after sustained performance and CPU scaling degrades performance, in particular for proaudio apps (and games to some degree)... Audio is very sensitive and cpu scaling causes audio glitches.... So the cpu frequencies are spiked to max (note: this obviously causes battery drain)....

Additionally, I am running an app in the background that is using "background playback" ~ to further strain on audioflinger / audio driver. The results are quite excellent, aside from a few initial xruns when loading some files, no more xruns occur. The screenshot is Monitoring in beatonal for buffer underruns

In the test, I am using the maximum amount of voices + effects that I could produce = very high load. NOTE: While the screenshot says 14 voices - it actually spikes @ 20+ voices, the same applies to CPU - it using much higher than 1.05.... effects are set in such a way that they are chewing through buffers (long very reverb times, sustained delay effects, modulators, etc, etc).

* this is much better than Stock.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Homeboy76:
3. clean flashed OP build over stock boot image - success

3. flashed magisk 14.5 over OP build - success

Is there a 'reboot recovery' after flashing the custom kernel

before flashing Magisk?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
No. I always flash my kernel, then magisk (I use "add more zips to flash magisk), then reboot to system.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Homeboy76:
Please look at #10 - Root with Magisk - Pass Safety Net without installing TWRP here
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
that's Cool. Looks like a pretty full howto guide for the Pixel.

I see you added my kernel as an optional step (custom kernel)... I get the impression that lots of people are using it, just based on traffic here, github statistics, messages, emails, etc... and since you've linked this thread; they should know where to come, if issues crop up or to give feedback/comment, so that's good. thanks!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
So not going to update the stable build quite yet, but I've been getting it prepped;

=> lts 3.18.85

=> WireGuard (VPN) Support

It's merged and will be supported. I'm still having a bit of trouble with the one userspace piece/script - but I've manually verified that WireGuard works, so getting the last bit working shouldn't be too hard. I just gotta hop on IRC and ask a few questions... I also chatted with the WireGuard Developer today; I pointed him to code to get The WireGaurd app to not crash on boot; on Oreo (like Kernel Aduitor and other apps do/did), I may give a hand with that and also give a hand in packaging the userspace parts into a proper flashable android zip... ~ I'm going to look at that tomorrow.

=> I've pulled in some crypto patches

These have been floating around for a long time, not a big deal - but I'm also thinking about improving the optimizations flags used by them.

=> I've updated all of the VDSO && some timekeeping code to match asop/kernel_common/android-3.18

This kind of is a big deal, as it's setting me up to use some code that I've been sitting on, but haven't been able to use ~ Tonight, I went through a year+ worth of commits in AOSP and found all of the needed bits....

=> Audio driver patches

A few will be merged into stable, while others I'm still working on. There is one set of changes in particular; that is a game changer - but hard to get up and working... however, the chunks I have working are useful, for sure....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ChongoDroid:
Is this available on the test link?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Nope. It'll be in the next stable...

I haven't posted another test build - a new test build won't be available for a bit, I have work to do on it yet.... I'll always mention in the thread when a new test build is available.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ChongoDroid:
Roger that.

Patient bear will be here, ready when you are. ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I''l wait until I have WireGuard sorted out OR until the December firmware images arrive - whichever comes first... beyond the WireGuard support, the Stable build is largely the same, as far as anything that a user would notice.

Most changes are under the hood and incremental - the timekeeping code that I merged does actually touch a lot of files in the kernel sources, but again - shouldn't make any noticeable/measurable difference to you or anyone else... There is an added benefit of some hardening to the timekeeping code (read-only after init) and it also brings my kernel close in-line with AOSP's timekeeping code - which is helpful. (especially for the changes I'm going to make eventually)...

So no big rush for a stable push...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Just a note on WireGuard progress;

So it turns out that (for now) We need the bash interpreter to run the userspace utility for WireGuard. This presents a minor problem, as Our Stock Rom does not come with Bash ~ That said, I do have a working bash binary on my device ~ and I think the plan is to have a statically compiled version of bash included with wg-tools (the userspace parts)... This is something that I've been discussing with the WireGuard Dev...

I'm at the last steps of getting a working wg tunnel on my Pixel, but I still need to get the WireGuard app setup + get a flashable zip for wg-tools sorted out...

but progress is being made here...

I've also helped another dev in getting WG compiling in his ROM; https://xdaforums.com/oneplus-3t/development/rom-lineageos-14-1-t3547024/post74713326#post74713326 (scroll up to read/see)

...and reported the issue to the WireGuard dev. WireGuard is very new to the android platform, so getting all of the kinks worked out and lowering the bar to entry - is a work in progress...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ChongoDroid:
Very exciting stuff. I would use my VPN a lot more with something like this. Right now the PIA client works well for temporary usage but always on VPN would be nice without the added drain.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Another WireGuard update:

I've got my interface and Tunnel for AzireVPN working... The one AzireVPN founder walked me through configuration, helped me get setup for the Toronto servers + keys and getting the config working in the WireGuard android app... there is still a couple of issues;

1. the WireGuard app, quick tile and wg-quick script (wg-quick is the culprit) aren't disabling the tunnel when I disable it. (not sure about this one, going to talk with WireGuard dev) ... but enabling it works fine. The tunnel is nice and fast too ;)

2. the Wireguard app still crashes on boot (I still need to muck around with it's source code and see if I can fix it)

3. I still need to get Bash and the userspace tools packaged as a standard flashable zip...

But genuine progress here ~ as I now at least have a working configuration for WireGuard.... So kinks aside; very promising, indeed.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
another WG update:

the wireguard app no longer crashes on boot on Oreo. I chatted with someone who was looking into it, he used the commit from Kernel aduitor as a ref (that I had pointed out), he hadn't been able to test the code; but I rebuilt the app, tested/verified that it works; no crash on boot ?

the tunnel still can't be disabled; investigating...

after that, it's just a matter of packaging WG-tools & bash.

in the process of testing WG, I also ran into some instability (a random reboot and my device almost freezing; lock contention)... however, it turns out that I already had some code commuted to my old kernel / other branches that I suspected would fix the instability; 24hrs later, not a single hiccup - so looks like 'problem solved'... so we'll see if the timing works out on getting WG ready for the December firmware / release...

it'll be in the kernel enabled, just not sure if the other issues will be sorted by then or not...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
now that I've been running WireGuard with my VPN always enabled - I can tell u that it does impact battery life slighty - but not to the point where I care or that it affects my daily use....

I can't really compare to regular VPN or what ur are using, but I think some drain would be expected. that said, the impression that I've gotten is that WG should be more battery friendly...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
so... most likely 8.1 will be released in the next day or two..

I'm going to push another stable 8.0 release, when the December firmware images are available.... and then I'm going to start looking at 8.1 ~ no asking for ETA on 8.1 support, OK?

it might take me a day or three to sort out.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
So, 8.1 support;

There are for sure some hassles / manual intervention required migrating over / rebasing my kernel on the new sources..... Honestly, I'm not feeling very motivated to do it today; it's work, time, energy and effort - So this might wait a few days before I really try to dive into it....

I have a few other projects that I'm working on, as well / paid work - so I'll be prioritizing them before spending my time updating my kernel, since the changes needed are manual - it's not a quick job ~ even if still somewhat trivial to do. Sorry, if that's a bit of an inconvenience, I will get this updated - but like I said it might be a few days...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ChongoDroid:
Take your time man, real life always takes priority.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Thanks, just an fyi - it looks like some of the security patches for December are already in my kernel, so no worries there.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] SanJoseCA:
Bootloops confirmed.. Reverting back to 8.0
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
LOL. my kernel is for *8.0* ~ not 8.1 and I've already said that I won't be releasing an 8.1 kernel for a few days....

There was literally no point in testing 8.1 with my kernel .... all custom kernels need to be rebased / update against the new kernel sources....

my mention of the december security patches is refering to fixes that google has applied for things like CVEs ~ NOT me supporting 8.1, just to clarify... (meaning fixes already exist in my Stable release for 8.0)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] SanJoseCA:
Totally get it.. Was feeling a little lucky. Thought of trying .. :laugh: But yeah.. was hit with reality soon.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
ya, all custom kernels are going to break on 8.1 - it's NOT the same kernel/branch as 8.0 - lots of changes ~ So this isn't exactly an 'incremental update' apply a few patches and off-we-go. lol... That said; It's not abnormal or anything like that either for android kernels... 8.1 is a big enough change, where there are updates in the kernel; drivers, bug fixes, etc. (which means I get to drop some commits that I already had)

For me / work I have to do;

1). setup an entirely new clean branch (import the new kernel sources onto my github too)... which I've done.

2). Rebase all of the patchwork against it;

Any extra downstream features (wake gestures, etc), All of EAS changes and then I have to merge in my own changes, newer EAS code, etc too.... Which means walking through commits and fixing things as I go. I already know where the problems are going to be / require manual intervention (it'll be early on in the process with EAS, scheduler stuff, etc.... but by the time, I start to hit most of my own patches (and later EAS patches) ~ it will smooth out.

3). Then apply all of the LTS patches that are missing (this will be smooth)....

4). I actually have to test it too. (as I go and especially after I'm caught up).

it looks like people are having problems with TWRP + supersu on 8.1 anyway. So i imagine it'll take a day or two for things to catch up. (substratum and other apps may have issues too. lol... we'll see)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ChongoDroid:
It'll be really interesting to see what battery is like with your patches applied to 8.1 kernel. Also it's interesting to see that Google is including gcc information in the string
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I doubt battery life will be all that different... While some things have changed in the kernel - not much to do with that kind of thing, AFAICT.... they use Sched Scheduler and their set of patches to optimize battery - kernel's using EAS (never versions) use the upstream SchedUtil scheduler, revert a bunch of google's patches, then apply all of the Needed EAS code to getit working.... idk, maye some drivers are better optimized or something in 8.1 ~ but no idea until I look through + actually start using 8.1

anyhoo - I am actually getting things on the go. lots of commits and code merged... won't test anything until tomorrow, getting later in the evening here and I don't want to be flashing / wiping my phone for 8.1 right now... but I'll probably end up doing that tomorrow ~ getting my first boot on 8.1 with my kernel - then I have some more code to commit....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ChongoDroid:
Thanks on behalf of everyone here. We appreciate the work you do.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
thanks man. I'm working on it before bed (12am here, as you would know 3hr time difference between us).

I've got most of the code merged, had to fix up a few spots / one or two bad commits... all caught up on on EAS and LTS too.... Still need to merge in some audio scheduling code, a few commits that I set aside (doing at the end, as I am going to squash some commits, rather than applying a bunch; since they affect just 1 file), and a few other bits....

The kernel builds now, just fine - probably runs (although, I won't test/boot it until tomorrow)....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Working, seems stable, so far...I'll test battery, stability, etc tomorrow... I still have a few things to merge in & currently having an issue with AnyKernel2 - but I've made an inquiry about it to the dev && I'm not in a rush to push this out anyway - unfinished
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ChongoDroid:
If you want a private test group, I'm sure we could figure one out lickety split. If not, we patiently await your 8.1 release whenever it's ready.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
lol. ... no, I don't need a private test group. ???

there's stuff that needs to be sorted out before I post a build; right now, due to having issues with AnyKernel2. ... and kind of a nasty hack; I'm just repacking the stock boot.IMG with my kernel; so now customized settings on boot, I lose some settings on reboot, etc.... plus, I still have stuff to merge in, albeit small stuff, mostly.... and wireguard...

binder_rt has been added in now too (since posting pix)... 8.1 is a better userspace for running binder_rt... logcat doesn't spam anymore, Google's added an stune tunable for RT tasks, etc... (they upgraded binder too, their driver is different than what's in AOSP..... but still much better than the old driver)... anyway, it looks like my implementation is reaping the benefits, so far.... performance is excellent in 8.1...

anyway, assuming I can get AnyKernel2 sorted out and the kernel is stable... it's possible I might have a build out, sooner than later.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
[MENTION=4685802]AlkaliV2[/MENTION] - can you please upload the December Marlin Boot.img

I am gearing up to post a build for 8.1 ;) I have a workaround for the issue I was having with AnyKernel2; have succefsully flashed zip for Sailfish... I've also merged 99% of the code into the new branch and I think I haven't missed any user-facing features (just a coule bits in the kernel to touch up. small stuff).

I'll post a changelist, once I have a flashable zip for Marlin.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] xonelith:
Here you go:

>>Clicky<<

I'm not AlkaliV2 but have been using your kernel since you released it.:)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Hey Thanks! ... Yeah, I recognize your username. (thanks on posts)