yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
It would be unreasonable, but rest assured; i'm not and that's not really how it works anyway...

PUBG Mobile is also still launching/relatively new - I'm expecting that they will improve their game and that most of the issues cited, very much have to do with the game, not android userspace or the kernel, specifically. ( I've checked this game out and this is the impression that I've gotten )

I have patched and tuned the kernel (and userspace) for specific applications in the past; but that happened for something very niche and a specific use-case; I've built a couple of VST soft-synth modules (to hook up to my midi keyboard and/or my DIY bluetooth pedal board)... ~ In this kind of situation it 100% would be reasonable....

However, Android is a very broad, has many applications/use-cases and everything has to work correctly, so I definitely can't be optimizing for any one specific app....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
[MENTION=1007992]everyone[/MENTION]

I won't be updating for April until tomorrow - busy day, busy night / not home until late.... but I would assume that both builds from March will work on April update.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Overclock96:
waiting for updates :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ayylmaomyman:
When you do have time to release the build, will it be similar to march as in is just a stable+monthly update, or will it be the complete overhaul build you've been working on?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
it'll be both...

...except that I've fixed a few issues in the v3.x build. tbh, for me the v3.x build is now pretty stable.

no random reboots, no hangs and no FCs... only issue is that it sometimes can still hang on boot, but that doesn't happen very often, either... I was also running it without zram and came up with a script to better test the oom_reaper - which seems to be working fine, after an initial issue that I've sorted out... lastly, when I rebuild the v3.x branch I'll be disabling some debugging, re-tuning rcu slightly and also try to improve battery life vs. the previous build).

stable will remain the same, but I might cherry-pick a few commits from the v3.x branch, but they won't be big functional changes, just a few bits that should be in that branch too...

both builds will have LTS + April patches.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Overclock96:
this is very good news! I'm already looking forward to
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
man, I just can't catch a break! .... Finally sitting in front of my machine...

compiling the v3.x branch now (after updating it all. which took far longer than I expected, as there were a couple of conflicts taht I actually had to think about how to resolve)... I'll flash that and run some tests on this build, while I catch up the stable build to LTS (which should be straight-forward).

may not have the builds up for another hour or two ~ sorry for the delays.

btw, March builds work fine on April firmware. (tested)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] almightysiman:
Been running the 3.x build since released,and it's really stable.Can't wait to try the upcoming release!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] noidea24:
i decided to fully switch to your kernel at the release of last months factory images, and its the best thing i ever did. fast, stable, decent battery, etc.

Take your time man, no rush.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Yeah, when I pushed it out; I somewhat exaggerated it's issues. It should be reasonably stable, next build should be a bit better on battery, less debug, etc.... but still very similar (no new functionality).

Cool. Glad to hear that it's working well for you....

Yeah, unfortunately; I ran out of time last night. I didn't even get cracking on updating both builds until 10 or 11pm. (Google pushing updates the last 2 months hasn't lined up well with my schedule. lmfao)... The good news; I'm off of work early today and both branches are pretty much caught up to LTS and android commits on my github, So i just need to give the stable build a test run, when I get home.... * I am already running the v3.x branch on my device (which seems to be just fine, although it needs a rebuild, as i forgot to change a couple of kernel configs (that are compile-time options).

so both builds will for sure be up in a couple of hours.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
home early, but now experiencing a power outage. crazy wind today.

I was in the middle of compiling both builds, when we lost power ?... soooo, I'll have builds up, a.s.a.p - but I need power, first. ROFL.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
UPDATES:

Stable build v2.7

https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_v2.7_9ffe076.zip

Changes:

- 3.18.102 (lts updates)

- android / april updates

no other changes for now, although I am going to be cherry-picking a few commits from the v3.x branch, for the next build.

Dev branch v3.2

https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_v3.2_ee40fa5.zip

Changes:

- 3.18.102 (lts updates)

- android / april updates

- various fixes and tweaks

I still have some work to do for the next build; reviewing/pulling in some linux-4.4/4.9 LTS patches (this is something that I always have to do, as the 4.4/4.9 kernels sometimes have fixes that are applicable to my kernel, but not vanilla Marlin sources).... I'm also in the process of backporting some cpufreq related code. (will start testing locally, now that I've pushed a build for April / you guys).

IMPORTANT NOTE:

I need someone to post the marlin april boot.img, so that I can update the OP with it....

thx
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] i42o:
hey man, im sure this has been answered before but i cant seem to find anything on it, ive tried running your kernel on Lineage with no avail, is this kernel compatible with LOS or is it the way that i am flashing that makes it not work??? sorry if the question is redundant
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I've PM'd you... get back to me and we'll see if we can resolve that.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Bryanx86:
here is April boot.img
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
thanks. pushed it to my github and updated the link.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Overclock96:
I put the latest version of the kernel.very good battery life, I'm amazed at the speed of work, but I have a lot of problems. 1) my phone rings for too long, I click on the phone sign, and the call starts only after 10 seconds. 2) sometimes it is difficult to unlock the phone screen. 3) And in general, sometimes it becomes very slow with a specific application

4)Problems with sound, sometimes the sound is added or decreased very long,

With a stable vertex core such is not present. Waiting for fixes and release :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
...and you are under the impression that the kernel controls how long your phone rings? (it doesn't). I haven't experienced any delays when receiving calls and certainly not a 10 second long delay.

you are going to need to verify this doesn't happen with the stock kernel, before I can look into this.

that's a known issue that has NOTHING to do with the kernel.

What specific application??? being vague isn't helpful.

Also, please verify this doesn't happen with the stock kernel.

I have no idea what you mean here. Can you please explain in more detail, using concise language?

NOTE: not all bugs in android are fixable via the kernel. problems in userspace; I can't do anything about. I also can't look into bugs if I don't have specifics / am lacking info.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bbender716:
Just wanted to report in that the latest 3.2 build working great on P with Magisk installed. I love this kernel. Rock solid.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] vijogape:
LOS Compatibility and LOS derivated ROMS

Hi nine7nine, could you post how to flash on lineage OS, i think that the problem is the custom recovery that is in LOS for deafult. i tried flashing stock boot.img but brick the devices
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Dachfenster:
In my experience it doesn't work on lineage based ROMs any longer. Sadly, I don't remember since which version it stopped working. It ends with Error 1 (which is insufficient size?) when flashing. But this has been pointed out before in the thread. LOS is just not "officially" supported by nine.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Craz Basics:
You actually flash twrp? Or just boot it?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
Flashing TWRP often results in low memory errors.. it's not recommended.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DR3W5K1:
I have been using stock Android for sometime now. I have been flashing twrp with the process exactly as described above.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
This kernel can conflict with having TWRP and Magisk installed alongside it. It may work fine, depends on a few factors.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
[MENTION=914288]joeeboogz[/MENTION] advice is plain wrong...

...As I've now had to say over and over and over and over again; the kernel must be installed after magisk to apply certain settings on boot.

if you guys aren't going to RTFM (read the OP) or listen to my instructions; fine, then you can do your own thing - but no one should be following your instructions, nor should you be telling others to do what you are doing....

and... fun fact, without applying my settings on boot; RCU behaves differently, there's no input boosting, etc... and on the v3.x branch - you may end up with page faults that wouldn't normally happen...

but hey; what do I know, right? ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DR3W5K1:
You do know. That's a given.

Maybe I didn't read his instructions properly.

I flash magisk-kernel-twrp-magisk.

It is incorrect?

---------- Post added at 09:24 PM ---------- Previous post was at 09:22 PM ----------

Just re-read his instructions. They are incorrect!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
cool. just curious;

could you post the top of init.rc???

specifically, I'd like to look at the lines that start with "import".

yup. very much incorrect ?

as for flashing twrp, sure. but It's not something I'll support. it may or may not work properly, or break at any point.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DR3W5K1:
I completely understand. Thanks for your work man!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bbender716:
import /init.magisk.rc

import /init.environ.rc

import /init.usb.rc

import /init.${ro.hardware}.rc

import /vendor/etc/init/hw/init.${ro.hardware}.rc

import /init.usb.configfs.rc

import /init.${ro.zygote}.rc
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
That's not good :(
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bbender716:
Yeah my system was weird for a while. Actually interestingly,something about the security patch or doing a full data wipe messed up my system on P and April O. I ended up full wiping and going back to Feb and then upgrading straight to P with a factory reset and all the problems have shook out.

---------- Post added at 02:22 PM ---------- Previous post was at 02:20 PM ----------

Now I have:

import /init.magisk.rc

import /init.environ.rc

import /init.usb.rc

import /init.${ro.hardware}.rc

import /vendor/etc/init/hw/init.${ro.hardware}.rc

import /init.usb.configfs.rc

import /init.exnoshadez.rc

import /init.${ro.zygote}.rc

But with his March version. Too nervous to update.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bnmEEFaej:
I have the same top of init.rc, I haven't installed a custom kernel (unsure if it will work properly on lineage, so I'm sticking with stock kernel for now), but I have installed magisk. I'm on April unofficial lineageos update. Could this be normal, or is there just an incorrect line in init.rc that you're observing?

Here's mine for reference:

import /init.magisk.rc

import /init.environ.rc

import /init.usb.rc

import /init.${ro.hardware}.rc

import /vendor/etc/init/hw/init.${ro.hardware}.rc

import /init.usb.configfs.rc

import /init.${ro.zygote}.rc
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
that's normal....

My question; asking to see the import lines from android P's init.rc was to verify that they were the same as on Android Oreo (and would patch the same).

See how magisk has an entry / it's own init script? => my kernel does too.

As for LOS + my kernel. I'm not sure what the issue is.... maybe they've broken support for custom kernels recently (?), maybe there is some other issue.... If someone running LOS can catch what is happening on boot, I'd be more than willing to take a look ~ however, I'm not wiping my device to test LOS (or any ROMs other than Stock).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
is it possible that you previously just flashed in the wrong order? (it happens. I've done it, more than once. lol). your previous init.rc post would indicate that it should patch the import line in, just fine...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] almightysiman:
I can't tell there's any improvement cosz I never encounter drop out before.maybe the improvement is really hard to notice.:D
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
lol. It would be hard to know ~ I can only tell by reading commit logs, for Wahoo/Pixel 2 and a few other devices that are using the patches or a subset of them.

I wouldn't expect you to notice, necessarily... The important thing is that things are working well.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] spr33:
Sorry to thread jack but how do you go about getting fastboot on a Chromebook? I've been looking for this for so long!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
rather than thread jacking and apologizing... google how to do it, search XDA or pm him... that would make more sense, yes? ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] spr33:
I had already did a Google search, specific to my actual Chromebook which is where I may have been going wrong as it may be standard across all.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stryker09:
Confirming latest test build boots! :D time to get on the fast lane! Also BT user here without issues
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
ya. I doubt it's specific to your model. I seem to recall, reading about doing this on chromeos or chromiumos before, something about putting it in developer mode, zips being available for adb/fastboot, running a couple of shell commands. profit...

either way. don't thread jack. pm him or try following the many guides on how to do it.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
cool. yup. it boots. glad we figured that out.

I hate bootloops. lol.

yup. Bluetooth seems to be fine (I wasn't worried, just hadn't tested beyond pairing devices, file transfers).

thanks, man.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stryker09:
All good man, happy to help where I can! Excited for full EAS 1.4, also has anyone tested the Dynamic Stune Boost yet? If not I might give it a go and report back based on settings from the RenderZenith thread
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Yeah, I've talked to Josh and Zacharia (Renderbroken). the devs of the OP5 kernel in that thread / the devs at Project-EAS. at length - you know; because I was interested in using Dynamic Stune Boost in my kernel and had some questions... Josh also follows me on github... we've chatted a few times about DSB, EAS, Voxpupoli, how they setup cpusets on OP5 etc.... stuff they are working on...

Also, minus a couple of cherry-picked 'fromlist' patches for EAS, that aren't doable right now on Marlin. we are basically at v1.4....

I've tried lots of settings with dynamic stune boost... including theirs... you will find though, on the current builds (will be fixed in the next build) that the top-app value is being overwritten to 10 (caused by an setting in /vendor new in Nov images).. I just noticed a couple of days ago, also why I didn't set presets on these builds... so your settings won't be persistent, until I fix that.... normally, having the topapp boosted to 10 would cause additional drain ( DSB v2 patch addresses drain over v1, but it's not really an issue on my kernel anyway).

so yeah. report back, if you like. but I already know all about it... i may set defaults on the next build. or put a sticky with some on the OP
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stryker09:
I did noticed that top-app would always default to 10 yup, I think it's awesome that you guys collab on these projects :D looking forward to the next test build!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Well, When I decided to pick up EAS changes, AOSP/kernel_common and their OP5 kernel were the best candidates... ~ Although, those are much never kernels - RenderBroken had backported some stuff from android-4.9 to android-4.4 ~ but I still ended up having to backport some of his backports LOL (*different function names, arguments, things in android-3.18 kernels being structured/placed differently, etc... and there were other bits I needed, from elsewhere)...

So I touched base with them and asked a few questions. I always ask questions = learning ;)

Collaboration is the cornerstone of opensource software.... Although, I wouldn't say there is a ton of collaboration or anything.... They are good guys though -> and chatting with them was informative, helpful and appreciated. I think if/when they get Voxpopuli on Oreo ~ I might have an opportunity to test that - maybe get involved in some way... But for the most part, I just check their github, occasionally... Most of my current pulls come from Wahoo and AOSP/kernel_common and Mainline linux.

ya, next build. Not sure when I'll push it - I'm hacking on the audio driver and some of it is trial and error, a bit of a guessing game in some spots, while I figure it all out.... I've got some other changes to pull in too ~ and I will need to test them for a bit, plus iron out any kinks.... But the stable build is good and the current test build isn't bad either.... just a few details to work out / fix up, so far..
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stryker09:
Very cool! Do you plan on possibly looking at Pixel 2? I know you don't have the device but I'd be willing to test if you'd be willing to try :D just a thought though, but it would probably be difficult to test changes without the device itself
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Nope. I won't be looking at the Pixel 2... That's not how this works ~ I would have to own the Pixel 2. You couldn't help me at all. (that isn't a knock against you or anything - but I don't think you understand what's actually involved). 100% non-starter.... it wouldn't be "difficult", it would be pretty much impossible for me to work on, support, etc...

And If I had a Pixel 2 - my kernel mods would be quite different, Than what I'm doing with Marlin.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stryker09:
Cool I thought as much, kernels are always device specific, no worries man, happy to be part of this :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Ya, kind of device specific, but even more so; chipset/soc specific + linux version (major) specific.... the vendors spinkle on their own code, cherry-pick / backport, etc ~ but even when you look at across devices (that share the same kernel - the base kernel itself is often largely the same, give or take a few chunks - it's the drivers that vary a lot....

I probably will never own a Pixel 2. I'll probably skip it and get a Pixel 3, I would think.... I like my pixel and by the time I am done with my kernel. It'll be like having an android-4.4+ kernel anyway... On top of that; I just won't be ready for a new Phone for another year or more, so by then - the Pixel 2 probably won't appeal to me (I don't find it compelling now. It's not nearly a big enough upgrade, for me anyway.).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
NEW STABLE UPDATE: * OP download link.

Changes:

- Linux3.18.84 lts

- Audio driver tweaks

- init rc no longer sets io scheduler persistently

- a few other misc cleanups in the init rc

- Dynamic Stune / Cpu-Boost Defaults:

# Cpu-boot / Dynamic Stune Boost

write /sys/module/cpu_boost/parameters/dynamic_stune_boost 15

write /sys/module/cpu_boost/parameters/input_boost_enabled 1

write /sys/module/cpu_boost/parameters/input_boost_freq "0:0 1:0 2:0 3:0"

write /sys/module/cpu_boost/parameters/input_boost_ms 1500

These are persistent on reboot, but only for the next few releases ~ I need to be able to gauge Battery usage and If I don't set defaults - people will be reporting all sorts of conflicting results.... but yeah, this is temperary. NOTE: you can still change them, but they will reset on boot && don't report BatteryStats in the thread, if you have changed them or mention that fact.... * because, the gist is;

the higher the Dynamic Stune Boost and input_boost_* values - the more you are biasing performance

The lower the values; the more you are biasing Battery life.... So no need to point that out (I just did. lol).

I'm still working on the test build - I've resolved a couple of issues but there are other things to address yet. This build is NOT based on the test build ~ It's the stable build with LTS and a few tweaks. I'm just pushing it, because it mainly addresses some init rc stuff and has the latest LTS.... thanks
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ChongoDroid:
I'll flash this right now, saw a bit of a hit in the battery department on the short time I was using the test kernel compared to the previous release. I'll charge her up and start testing this one.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
cool. if it reboots or bootloops, just reboot. might be quirkyness coming from the test build...

ya, with the cou boost changes, there could be a bit of a difference in battery life... I'm just starting with these defaults as a baseline...

AccuBattery guesstimates similar battery life, but I've flashed a couple different builds, before having this run all day... so things need to settle here, for me. I think....

either at though. it's pretty much the previous stable build. minor tweaks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stryker09:
Nice! I'm about halfway through my power cycle on the latest test build, so I might just wait for the next one
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
From my testing, your kernel works fine on Lineage 15.1 (ExNoShadez 2.7)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bbender716:
I flashed magisk, rebooted fully, then booted back into recovery, flashed kernel. This is what I did for my latest Import output

---------- Post added at 01:39 PM ---------- Previous post was at 01:37 PM ----------

I flashed magisk, rebooted fully, then booted back into recovery, flashed kernel. This is what I did for my latest Import output posted...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
good. thanks for speaking up...

I would've expected that it should work with LOS, but Alas; I can only go by user reports - so the report of it having stopped being compatible, is obviously incorrect...

anyway, good to hear it's working fine.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
I can't get 3.2 to work properly, causes visual glitches, then the phone force soft-resets and never finishes booting back up.

I can try to get some logs or something.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] i42o:
Can you please elaborate on your flashing process?