yashsingh1/xdaforums huggingface dataset:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
ya, even not updated it's fine on the Feb firmware. ran it for over 24hrs....

that said, I'll be updating in an hour or three - i'm running the Feb 5th stable build on my device right now... just wanna run it fir a bit and also run some tests...

are you sure that you installed the kernel after magisk?. ... because it always runs my init script and applies my settings on boot.... should be easy to tell;

in the root of your file system, open init.rc in a text editor and you should see;

import /init.exnoshadez.rc

along with the rest of the imported scripts. near the top of the file). lemme know.

and yeah, update will be soon, as mentioned above.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Ok, so updated for Feb 5th firmware... No major changes (yet).

- 3.18.93 LTS

- Feb patches

- a few misc patches.

I'll be updating this again, in the next couple of days / asap ~ The reason?

Currently, there is a minor issue with i2c bus, i2c devices and suspend. I'm in the process of sorting it out, but I didn't get finished with it tonight (I was trying to get it sorted, but ran out of time, so I've pushed the update anyway)...

Users of DT2W will notice the bug ~ as when in deep sleep / suspended - it won't always wake and may require an extra tap or two (sound familiar? - well, it's not the same issue, as when I switched to using CONFIG_HZ_1000 .... it is however; directly related to the wake up bug in the test builds)... I will get it fixed though, working on it. no worries ;)

other than that - I haven't noticed any issues and I haven't changed much beyond LTS, so all should be good.

After I get this resolved, I should be able to start merging in a bunch of code that I've been running for a month or so on my device...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
well, if i were u, i'd another shot at installing the kernel, since magisk is already installed (which on a kernel update, is going to be the case anyway... because, you won't be installing magisk on subsequent updates of the kernel..)... if it bootloops, try just rebooting again -> hold vol. down + power button... see if it booots after that...

um, AFAIK. you can't actually modify init.rc directly on a systemless / magisk system... it would be easier, if we can just get things to work properly, without you having to do that...

I guess the only exception here, is that I am thinking about adding a shell script, for custom ROM users, in the case where they aren't using magisk / prefer their integrated root... I've been asked about this - so that might be an alternative, but if I do that. it'll just be placed in the zip... users would still need to add it as an init.d style startup script...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
wrong order.

1. install Feb update (reboot into system, finish system update)

2. reboot into twrp

3. install magisk, followed by kernel

4. reboot
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Glad, it's sorted. you probably just flashed in the wrong order. it happens. no big deal! ;)

100% right. those settings are supposed to be set, as they are. wq_power_saving allows the scheduler to make decisions on how/where to schedule workqueues (well, power efficient workqueues anyway).... perfd is needed by android userspace for power-hints (boosting an app on startup, when to bias performance, using the power-saving feature, etc)...

you could disable wq_power_saving, but I don't think there is a real measurable benefit in doing so.... Never disable perfd though - it's 100% needed by userspace.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
cool. well beyond the monthly firmware bit, any other kernel updates can be flashed without needing to worry about magisk...

battery should be reasonably good... I haven't noticed any regression or improvement with android this month. although it might take a few days to get good estimates... we'lll see...

if you bump into any issues, or have questions. let me know
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
just a wee update on progress... i'm still working on fixing the one issue that i mentioned before; DT2w related (sort of, not really)... I also believe that the sleep / screen off bug that was in my test builds is NOT present in my current local build...

I'm doing a lot of stress testing && have actually fixed a few splats that I wouldn't have hit, had I not been using hackbench and a few other utilities...

there should be some good improvements that come out of this effort. i'm already seeing improvements to SMP performance... just for kicks;

sometimes the single-threaded performance is closer to 1900/2000 - just not on this particular build or run...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
lol. no. Anytime you see a # in a shell script at the beginning of a line; that means it's commented out.

While, I do appreciate the effort of trying to double-check things; I don't need you to do that; I know what's going on in there ;) (those lines don't exist anymore either / next build).
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
[MENTION=7810360]nine7nine[/MENTION]

So since this kernel saves on battery, does that mean it sacrifices performance? Also, my earbuds and headphones are getting a lot of static with this kernel.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
energy-saving vs. performance it's always a bit of a balance. Sacrificing performance might not be the right way to think/look at it. energy Aware Schedulers like sched && schedutil will consider energy efficiency vs. performance cost, so ya - they can help save battery....

but on the other hand; you haven't sacrificed anything - You can easily switch to the performance governor, for performance critical applications.... Plus, these days on android; (good) app developers should be using 'sustained performance mode', for performance critical applications (which reduces cpu frequency scaling")....

ear buds? what kind of earbuds? static? please describe in more detail; as I've heard people use the term to describe all sorts of things, so it would be helpful to have more specifics.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
[MENTION=7810360]nine7nine[/MENTION]

Thanks for the clarification. So if you know the android touch sounds, like if you tap the home button? Well after a touch sound plays, some static/feedback plays for about 5 seconds. The static always plays when there is sound, it's just very noticable with touch sounds. By static it sounds like a car radio that's cutting out. It happens on multiple audio devices too so it's not my earbuds. This has happened to me on multiple custom kernels, but it doesn't happen on ex or stock.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
hmmmm.... My phone definitely doesn't do what you what you are describing. touch sounds are clean, no static or degradation in sound quality... Interesting that it doesn't happen on stock or EX ~ but there are differences in how I've setup a few bits (a couple of things come to mind) ~ I can't say whether or not that is true of other custom kernels.... *BUT* I can have a look and get back to you on that...

are their any other scenarios where you get poor audio? .... I use a lot of audio apps; but they are all pro audio apps and therefore, tend to be using different APIs than system sounds / audioflinger...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
[MENTION=7810360]nine7nine[/MENTION]

It seems like all the kernels that let me adjust the analog gain give me this static. With ex and stock, you can't adjust the analog gain in ex kernel manager I don't think. I don't use any audio modifications, just magisk and a few modules that aren't related to audio. I can hear static all the time when sound is playing if my volume is low. Besides the sound, this is the smoothest this phone has ever been.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Yeah, I don't use any audio mods, either - I just wanted the option to... lol... Have you tried adjusting any of the sound settings to see if you can get a bit better of an experience? .... I generally leave those settings be (and my device doesn't seem to be affected); but maybe something might help? (also makes me wonder if there are differences in quality with ADC/DAC chips in the Pixels... hmmmm).

Smoothest eh? well, that's good! ;) .... That's one metric for gauging performance. lol ~ due to the nature of me using a lot of multimedia / pro audio apps (playing instruments, etc), That's kind of something I aim for - responsiveness, somewhat deterministic behaviour && bound latencies (even though it's difficult / not really possible on Android... yet)... But I don't mind burning through a few extra cpu cycles to reduce unbound latencies...

anyway, I'll look into this; I'm working on some scheduler / locking stuff right now. But I'll take a look at other kernels and go back through my own commits too - maybe I can sort this out for you - or give you something to test... gimmme a day or two (and feel free to remind me, if I forget! :))
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
[MENTION=7810360]nine7nine[/MENTION]

I've messed with the settings, but it just won't go away with the gain settings. Thanks for helping out! I also should say I am on the pixeldust Oreo rom, but all of this was exactly the same on stock.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aLPaSLaN07:
Anyone having issues with Yandex navigator? It closes at the first initialization.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
good to know and yeah, I'll look into this, as mentioned.

thanks, I'll look into it, as discussed. I have a feeling I know what the problem might be, so I might get you guys to test something in the next few days...

I tried it, briefly. I didn't have a problem getting it to load up - That said, even with location services enabled - it still complained that it needed them.... once it stopped doing that - it still wouldn't find my location.... Seems like a pretty buggy app (first time I've every seen that with any app).

So I'm not sure what the deal is there. I only had a quick minute to look - but I'll look later in more detail see if anything pops out at me.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
the update via magisk manager should work fine, *** but IIRC updating magisk doesn't retain the init changes applied by flashing the kernel zip....

I typically don't use magisk manager to update ~ all I do with it is download the magisk zip (which provides magisk manager and patches the boot.img). I flash magisk, then the kernel zip.... Part of the reason I do it this way - is do to having magisk manager updates break magisk manager for me a few times (like it would just crash every time I opened it)... So I've gotten use to just flashing it....

That all said, I can inquire to the magisk dev ~ maybe there is a way for it to retain/restore those overlay settings, but I don't know off hand.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
I don't touch perfd at all (this wouldn't be a bug with anything that I've done)... Perfd should be running by default (on Stock rom it does && It's setup on init by a service in /vendor partition. IIRC). I can't imagine why it would be disabled; unless you're running a custom rom and they are/have disabled it for some reason....?

and Yeah, perfd should be enabled for performance and power-saving reasons. Switch it on.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
I have no idea, but all three pixels that I have physical access to (meaning mine and my friends) all have perfd enabled by default.... and since I don't touch it - it can't be my kernel or zip that would be disabling it on your end...

I suspect maybe another app or something, maybe?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
[MENTION=7810360]nine7nine[/MENTION]

Found any fixes to the audio static yet?

---------- Post added at 09:14 PM ---------- Previous post was at 09:14 PM ----------

[/COLOR [MENTION=7810360]nine7nine[/MENTION]

Found any fixes to the audio static yet?

---------- Post added at 09:15 PM ---------- Previous post was at 09:14 PM ----------

[/COLOR [MENTION=7810360]nine7nine[/MENTION] found a fix for the audio static yet?

---------- Post added at 09:16 PM ---------- Previous post was at 09:15 PM ----------

Found a fix for the audio static yet?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
I won't know until I get you to test a build, but I have to finish up on a few things, before I can post a build for you to test ~ but I suspect I know what the problem is.... As soon as I resolve an issue in my current build - it should be good enough to throw out for a test run... I'll post it, and you can see if it fixes audio...

Yeah, something must have been turning off perfd. IIRC, some people use to do that, as some sort of optimization - but on Oreo/Pixel - it's definitely not an optimization, perfd is needed unless you're going to have the kernel handle dealing with cpusets/stune stuff, power-hints, etc...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Nil253259:
Been on a long vacation with family, didn't get time to update to Feb security. I might flash it tonight.

Just an observation- I realised that for the last 1 week my phone cannot detect wifi signal. It could hardly detect my hotel wifi and could never connect, while wife's iPhone 7 has full signal strength. Definately not kernel related. Hope wiping system and flashing Feb would resolve it. Till now I have 1 GB per day data plan, so not a big deal, but still a bit annoying.

Just an aside, what could be the possible reasons? Related to Google play service?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
No idea. yeah, I doubt it's the kernel/ not sure what the deal is... jealous of the 1gb per day data plan though ;)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jmiller3342:
Dude why don't you just flash it and find out?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
iirc, someone else was running it with that ROM....

there's no real reason it wouldn't run with custom ROMs... unless, they've patched their kernel or somehow broken things / don't support custom kernels...

it's not that it requires stock ROM, but that is all that I use of test against (well, I have aosp kicking around too - but i'm normally running stock... only have aosp for some benchmark and testsuite stuff baked in)....

if ur really paranoid, I'd ask about custom kernels in the ROM's thread. users and the Dev should be able to answer your question...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
progress is a mixed bag; I have a few splats to clean up, before I can push a build to test... One example, I was unaware of a problem with the devfreq code (that's doing unsafe memory ops that could lead to deadlocks - although I haven't hit one, afaik...) that I have only become aware of due to backporting some code that can detect such issues ~ so I need to fix that, on top of a few splats...

I've done a pretty massive rework of my scheduler, locking, futex code and some related machinery. The gist is that I'm getting pretty close to being in sync with android-4.9-eas-dev (the state of the art for EAS). I'm actually running all of the latest patchwork for EAS on my device. (but I still have a few bits that I need to get caught up, pertaining not to EAS but related scheduler code).... I don't have any good stats on battery life yet (for comparision) ~ as I had been running so many torture tests, hackbench, etc.... I also ran sultanxda's kernel module for detecting instability in snapdragon 820/821 processors (one of the reasons, why overclocking can be crap on some CPUs and other instabilities) ~ So yesterday, I finally reset Accubattery, won't be running those kinds of battery killing tests and will evaluate over the next couple of days how battery life is...

I'm also working on generalizing some code that speeds up synchronization (and is insanely noticeable / very responsive. it's f@%ing awesome)... Once I've reworked the code a bit, it should be applicable to any 3.18-4.4 android kernel that is running an 8.x+ version of binder (ie: binder with fine-grained locking), but requires an additional patch for binder to make use of it... I'll probably setup a repo with patches and info on that... *On my kernel (with said patches), binder also needs a slight rework on a couple of locks for it to play nicely....

So lots going on, but no build until I've fixed the splats ~ although, I will probably push one before I clean up my patches/commits and make some of that stuff available separately...

So no ETA, but I'd like to get a build out ASAP.... Today, I'm going to work on fixing a few splats, hopefully that goes well - but with this type of thing - it can either happen quick and be resolved, or dragged out and super frustrating...lol ;)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Yash rivankar:
Does it support for Oreo 8.1 on lenovo vibe k5 ??

And also gv the best option to download
[Google Pixel ROMs, Kernels, Recoveries, & Other De] siheals:
The update looks very promising, and a lot of work involved.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] siheals:
https://androidmodguide.blogspot.co.uk/p/io-schedulers.html?m=1
[Google Pixel ROMs, Kernels, Recoveries, & Other De] almightysiman:
what can I do to improve fluency？
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Warrimonk:
Hey [MENTION=7810360]nine7nine[/MENTION] , what substratum theme do you use?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Jank4AU:
Installed on VZW Oreo 8.1 beta (sailfish-opp5.170921-factory-47da29c4). Looking forward to seeing how well this performs. I ran into a few install issues (all user errors I'm sure), but after install it seems to be running very smooth. I had to revert to the stock boot images, very easy. Then I just kept forgetting that TWRP won't decrypt this version yet and I totally forgot about the OTG cable. So, once I came to that realization, mounting the OTG drive allowed me to flash the kernel. Had to do the same to get root.

I'll post back after a day or so with battery and performance observations. Thanks a ton for your effort and for posting this publicly!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
depends what u mean, more specifically, but(?)

if u mean smooth ui, make sure u aren't reducing animation speeds, if u have... the natural thing is to want to reduce them, but it always makes android janky... I know L Speed app has some settings to make scrolling and the ui smoother, maybe I can investigate how they are doing that?

you can try different io schedulers, as they may affect responsiveness / smoothness...

I will eventually be tuning the io schedulers in my init rc, but it hasn't been top priority vs. a lot of the kernel. so u may need to be a bit patient on that front.

you could also try adjusting dynamic_stune_boost. but do note; the higher u increase this value, the more battery it may consume. it's kind of a energy vs. performance bias.

this is an area that I'm looking into myself. there are some changes to the kernel that I would like to merge in, that will likely help, but it's an ongoing processs and hasn't been a top priority, compared to say; eas, schedutil, etc.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
That's very interesting and somewhat funny (from my perspective, here's why;)

It's funny because I know another guy who flashed his custom kernel and it blew up on 8.1.... In all honesty, I wouldn't have expected it to work on 8.1 reasons:

- I have no way of knowing what changes google has made to the kernel sources (it's an early ev preview / no available source code)

- I won't be testing (personally) against 8.1 until it's officially released

So, just keep that in mind - I can't fix issues, when I don't have access....okay? ... But I am super interested, so DO keep me in the loop ;)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Substratum Swift Black... I've tried out a ton of the dark themes (I refunded about a dozen. lol).... Swift Black is my favourite; consistent updates, supports a lot of apps / customizable... But I also use N Navbar (navbar icons) + Custom Navigation bar (button placement), which is why my navbar looks the way it does.

EDIT: Sometimes Google apps can break / FC after an update, so I uninstall the overlay for XYZ google app (usually phone or gmail breaks), then I re-appply the overlay for said app(s).... then they work again...

still kinks with OMS on Oreo, I think.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Experiments:

So This is more a fun aside than anything. But I am experimenting with backporting CONFIG_ARM64_LSE_ATOMICS .... This is an Arm64 cpu instruction set (enabled by default on v8.1, but the instructions exist in v8-a, aka our CPU). This code is NOT present in linux-3.18 and wasn't merged until linux 4.2/4.4... This is kind of a crazy thing to try to merge into my kernel and likely I wouldn't make an official release with it. Mainly because the locking infrastructure isn't nearly as proven or rock solid in 3.18 as later kernels....

Interestingly, I have a (semi) working backport of this code (99% of the way there) and benchmarks were quite impressive. (like I smoked every pixel benchmark in Geekbench by 300-500 in multi-threaded performance and my compute performance was 3x that of the Galaxy s7....

but then of course, a half an hour later - my system became very unstable (LOL).

It could be the LSE instructions are just unstable on our processor (hence not being enable until the next gen processors), or it could be that I'm missing some fixes and also need to pick up a few other patches to improve locking stability.... It's nothing that I'm adamant about having in our kernel - more of a research project, but who knows; If I was able to stabilize the code and after a lot of testing and vetting it could happen one day ;)

EDIT:

That said, It does appear that through messing around with this; I have picked up a handful of patches for rtmutex and rcu code that will probably apply to exNoShadez-eas, as they are valid fixes, AFAICT.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Jank4AU:
[MENTION=7810360]nine7nine[/MENTION] - looks like I got excited a little too early. WiFi is broken, although bluetooth still works. LTE works fine and I don't see any other issues. :cowboy:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
The Wifi issue I suspect I know why, However; We'll have to wait for the november updates / kernel sources to see If I'm right. (there was a well known CVE to be patched, a very serious one and it required both patch ing android and AFICT also the kernel - maybe We'll get lucky and it gets fixed. time will tell).

yup, cowboy! ;)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] siheals:
I hope your experimenting goes well. I wish we could get the 4.4 kernel for our pixel. The current kernel is awesome.