yashsingh1/xdaforums huggingface dataset:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
stable v2.7 build should probably be fine. it seemed to work for DP1...

3.x build worked fine for most people (on DP1 and 8.1), but a few people had issues - still not sure why that is, could be something as simple as needing to wipe caches to resolve... or a specific app or carrier related difference may have been causing issue - I did look.at some logs from someone's device (who hit probz), but they weren't conclusive as to what the issue was...

I'd say try either build or both. (as u say, you can always reflash the firmware, if you have issues.).. you could also just wait until I update and try then (that will at least make sure that any needed fixes/commits are in).
[Google Pixel ROMs, Kernels, Recoveries, & Other De] phishfi:
I'll go this route. Thanks again!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BarackMitzvah:
No need for apologies, do what you can. I'm sure i speak for most that we just appreciate you sharing your efforts with us :)

On a secondary note: for the new May build, should v3.3 be considered stable as of yet? Absolutely love v2.7, and the crackflasher in me is always eager to try new features
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
[MENTION=7810360]nine7nine[/MENTION] I know I'm probably driving you crazy about this and if you want me to I can drop it but I have to ask, anything about the sound issue? I know it's not schedutil, I compiled my own kernel with most of your schedutil commits and audio was fine. Again, sorry if I'm driving you crazy with this lol.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Read a couple of posts up, regarding the v3.3 build.... I'd say try it out for yourself, when I've updated (you can always switch back to v2.8). for me, v3.3 has been rock solid, no crashes/FCs, no random reboots, etc - it's been working well and is my daily driver.... and for the most part that is true for the vast majority of people using it - BUT a few people had issues (cited in a previous comment), it's something that still needs to be addressed (but I have a few ideas on that, so once I get my builds updated; I'll take a closer look and get people to try a few things).

My schedule has been very hectic lately, I haven't looked into this further. You're not driving me crazy, but for now - I can't do much about it. TBH, it probably won't be addressed until I rebase for Android P - going through every commit, do a number of cleanups, drop some patches and revise some others... If i get some free time before then, I can have another stab at trying to sort out your audio issue on 8.1 - but like I say; things have been hectic lately and I haven't had a ton of time to be working on your specific issue (that I can't even reproduce - making it even harder to address)...

and yeah; I already know it has absolutely nothing to do with schedutil. There's no reason that it would... a cpufreq driver could have an effect on audio - but not that kind of issue (more likely cpu frequency scaling could contribute to buffer underruns, not some kind of actual distortion or gain).

...and just a general update: (as to why there is no build up yet.)

- typically, I always rebuild my toolchain before compiling the kernel (to pull in all of the latest code / fixes).

- the scripts / repo that I use to build my toolchain was out of date and maintainership has switched hands (back to it's original author, *which i didn't know*). Due to this; compilation failed and it was 2am, so I had to get to bed.

- this morning before leaving for work - I enabled NoMachine on my linux box so that I have remote access and get my toolchain built + the kernel builds (I've already committed/applied the May patchwork to my kernel sources, both branches. yesterday).

- Due to switching to the new repo - I have to (re-)download/clone all of the sources for building the toolchain (gigs of data) before I can rebuild it. So now, I am just waiting for that to finish. (it's going to take a while to pull)

the good news is that once I have my toolchain rebuilt, I shouldn't have any issues with compilation. I can push builds to github; flash the stable kernel (at work) and run some tests (before updating the links on the OP. Note: I've already tested the v3.3 build, but I do need to rebuild with the updated toolchain, regardless)...

So sometime today, I will have builds up. (probably in the afternoon. It's morning still here).
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
UPDATED builds.

Changes (both builds):

- May patchwork

- linaro gcc-7.3.1 (for now). building gcc-8.1 failed compiling, so I went the path of least resistance ;)

NOTE: I'll be doing another build with gcc8 (on the weekend) and at that point I will add in the remaining few LTS patches, as well.

Stable Build is v2.8 on OP link (and here: https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_v2.8_8dbed4.zip )

Beta v3.3 build is here: https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_v3.3_34eda3c.zip

NOTE: If you are flashing the v3.3 build, I would ask that;

#1 - you also wipe your cache in twrp before rebooting (your next boot will take a while - so be patient).

#2 - if it doesn't boot, try force rebooting (even multiple times, if necessary)

#3 - if v3.3 still doesn't boot, please run adb shell + logcat on boot (connected to a PC);

you will have to first execute "adb shell", sometime just after the G logo appears (you may need to execute the command several times). After that execute "logcat" and watch the output (until it stops or keeps spinning on the same error(s). -> from there, you need to copy/paste that into a text file (as much as possible) and send it to me (either as an attachment or using a service like pastebin and linking to it)...

NOTE: As most of you know, I don't really support anything but stock 8.1. If it works on P or custom roms, then awesome. it it doesn't. not much I can do.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] almightysiman:
3.3 is working well with Du unofficial build!Thanks nine7nine!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Cool. glad to hear it... DU = Dirty Unicorns, right?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Nick80835:
Yes.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BarackMitzvah:
Been trying to boot 3.3 on stock 8.1 with magisk + Xposed.

Sometimes it boots, but then becomes unstable and all the sudden it hot reboots back to the white G logo (so I never see the warning boot message).

When it doesn't boot, it gets stuck on starting the audio service; see attached text file.

To clear up any possible confusion and highlight how I go about installing the kernel,

-I flash the full May factory image without wiping.

-Let it boot

-Boot into Twrp 3212 using fastboot

-install magisk over stock boot.img

-let it boot

-boot back into twrp using fastboot

-install the kernel

-wipe dalvik/cache

-boot

I'll try and capture a log during a hot reboot and attach it to a later reply.

Hope this helps!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BarackMitzvah:
Find the full hot reboot log at the following link: https://www.zerobin.net/?44d1b30a44407eee#OnWLdSPRxbW44/CHf25IE+wgh9w8GyB4h8cu7TsFdQA=

Wasn't sure how much of it you wanted, so I waited until the phone was unlocked and then I took the full log.

If there's any way I can get you a more useful log, just let me know!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
[MENTION=3209043]jimbub[/MENTION]

thanks. i'llhave a look at this lateron tonight, when I'm at home - I have a work thing i'm headed to now.

it would be good to know what mods you are using with magisk and xposed, as well...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BarackMitzvah:
Find attached both my Magisk + xposed Modules

Fwiw I did try and turn off xposed and reboot thinking that it may not be playing nice, but still no luck.

If you can think of anything I could do to help you, don't hesitate to ask. Thanks again, back on 2.8 for now and it runs beautifully ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] HudanAchmad:
its ok ,if I want to back to stock rom with flash-all ? thanks
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BarackMitzvah:
If you mean the Google Factory image "flash-all.bat" then yes. It should bring you back to stock no problem.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] almightysiman:
June update is out:laugh:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
yeah, I noticed. I'll have alook at it tonight, when I get home... so late tonight or tomorrow at lunch I will have June builds out.

I'd imagine until then current kernels will be fine.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] almightysiman:
Yea,current bulid is running fantastic!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BarackMitzvah:
Lol, don't pester the man. He's sharing his time and work with us for free.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
all good, he wasn't pestering me at all... was just pointing out the June builds were up...

[MENTION=1007992]everyone[/MENTION]

busy day, so I didn't have a chance at lunch to finish up. 4pm here now, so after dinner sometime - I should have the June kernel builds up... possibly, a general update on things to come n on a few issues, as well.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BarackMitzvah:
Just checking :) Appreciate what you do for us.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
UPDATES:

Stable v2.8.1: https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_v2.8.1_8f17e96.zip

Dev branch v3.4: https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_v3.4_13ec666.zip

It's getting late here, so I'll post some notes and updates tomorrow.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
OK, so I ran out of time lastnight, but wanted to give an update / discuss a couple of things, so here goes;

Android P support.

I had mentioned that I would be trying out P sooner than later - and I now have. however, due to bugs and incompatibilities - I wiped it and won't be switching back until it's officially released... so while I had considered supporting it earlier, i'm definitely not doing it...but as most of you know; stable v2.8 works fine...

I'm Moving all development to Gitlab.

with Microsoft's aquisition of github, it's time to move on... this probably won't happen for a week or two, but I do plan on migrating away from 'winhub'...

Dev branch troubles

to those few people who have had issues or instability... last week a friend of mine tried the v3.3 build and experienced similar problems... we did eventually get it running with stability, but not before wiping the device...

i'm not sure why that instability happens on the odd device, but I think it may be some kind of 'saved state' / saved data by some system apps or possibly within gapps... it's odd, but I've seen similiar issues in the past...

since wiping, my friend hasn't had any issues with the v3.x builds at all... now, obviously, i'm not recommending that you wipe your device - that's a hassle... instead, I would say that when I release my Dev branch kernel for android P - try it again, at that point (when you'll likely be starting with a fresh install anyway)...

lastly, I'll be pushing out updated builds on the weekend. they'll contain the mssing LTS + I have some patchwork for the Dev branch that I've been testing for a few weeks, which I think is probably ready to land...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BarackMitzvah:
Experienced exactly that. Fwiw, I noticed whenever I had the dev kernel installed, the "Finishing Android Update" notification never progressed.

I apologise if I'm telling you something you already know, but it's my understanding that that progress bar indicates the progress of cache generation. So maybe it's some issue with that?

In addition, the new stable kernel's running great ?

Expect a beer or two's worth coming your way ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
could be (I thought this previously, at one point), but in this case I think it may be something different. i'm not exactly sure yet, but I do know that it didn't persist on a fresh install - it's been working smoothly ever since... it's interesting and very annoying. lol

thanks man, that's very much appreciated!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Hey nine7nine, if you remember I'm the guy that always annoys you about the audio issue that happens to me while running your kernel lol. Its been bothering me that I haven't been able to run your kernel. I flashed the dev branch (with no problem on my aex build) and while the audio issue was still there, I was able to tinker around inside of the ex kernel manager app to get it to go away (see the screenshot). I assume it's still a hardware issue or something, maybe I got a poor quality something in my phone. I appreciate your work. Thank you!

Edit: for everyone reading this, this audio issue has only happened to me. You won't experience an issue with the audio while using this kernel.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
nah, yer not annoying me. you just having an annoying issue! ? ... I think it may be a subtle hardware issue too, but not positive... i'm not sure if that's actually making it go away, or just making it inaudible (?)...

when android P drops (and my kernel for it), I'll be interested to see if it's still an issue (#1 I have a patch to update the affected driver #2 I don't think i'm going to apply any downstream mods, at least not one initial release)...

BTW, what's your aex build? (a rom?)... sound issue aside, how is the v3.4 kernel working for you? any observations?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Aex = AospExtended, it is working well so far, very smooth. Haven't noticed any other bugs.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
cool. glad yo hear it keep me posted!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
An update on the above, as I've had a bit of switch in plans and will be holding off on new builds, for (at least) a few days...

the reason? -> I've decided to rebase my kernel. I have a few motivations here;

#1 - I want to start with fresh && up-to-date vanilla Marlin sources (with LTS included)

#2 - I want to review all of my patchwork (1600 commits, give or take 50 patches)

#3 - I want to re-organize and group patchwork that could/should be applied together

#4 - I'll be removing/omitting any hacks, dropping unwanted patchwork and/or reverted code

#5 - rework some patchwork to include fixes that were applied much later in development.

#6 - simplify certain groups of patchwork via squashing commits && documenting revisions.

#7 - to help simplify (future) rebasing and help with code portability, in general.

#8 - preparation to more easily support Android P on release (and future releases)

The good news; As of today, I've mostly completed the first few steps, which were fairly straightforward... However, in general this whole thing is a bit of a daunting task, tbh (steps #4-6, especially #5) - so it'll take a a bit of TLC and time to finish up... When I do finish, i'll push new builds for everyone. The stable v.2.x kernel shouldn't change much at all (beyond some bug fixes added from step #5). While the v3.x kernel will include some EAS && scheduler changes (which is running on my device already).

that's it for now!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BarackMitzvah:
Fwiw, I noticed today audio popping in all of the music I was listening to. Was able to fix it by turning high performance audio off in EX kernel manager.

Maybe it's somehow related?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
what audio player and is this preproducible?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BarackMitzvah:
Haven't tried to reproduce it yet. Was using soundcloud via my aux Jack in my car.

Tried it twice without a reboot in between:

- heard the popping

- turned off HPM

- Unplugged an replugged in my aux cable

- issue was gone

- Turn it back on

- Remove and reinsert cable

- Slight audio popping was back

- turn HPM back off

- cycle aux cable

- popping gone again
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
cool. i''ll see if I can reproduce and fix. thanks for letting me know. I'll get back to you on this in a couple of days... still working on my rebase... and on that note;
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BarackMitzvah:
Awesome. Keep in mind, the popping was very subtle. Almost sounded like the Jack inside my port was able to move around slightly, and the HPM amplified that signal noise to the point where it was audible
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
ah good to know (on the details). I'll still have a look n listen though...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
so, a bit of a progress update;

I've done the vast majority of the work rebasing the v2.8 kernel (as in, it's running on my device, image included ?)...

there's still a handful of features to merge and also a few bits/fixes to pull in from the v3.x kernel, but all of the heavy lifting is actually finished. ~ v3.4 patchwork should be less work, in comparision. (I figure another 1-3days, depending on free time, and I'll have it all done).
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
July firmware is up, however;

I have a huge family bday thing today (grandma's 91St bday, also my nephew and a neice's bday)... it's very unlikely I will have time today to update ~ so it'lll probably be tomorrow...

it'll have LTS caught up (already done), Google's monthly stuff, etc..

anyway, i'm sure (like always) you can use the June kernel until I update.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BarackMitzvah:
With the upcoming releases, in your opinion, do you think its worth the full wipe for your 3.x kernel?

Still haven't gotten around to trying it and figured I'd be able to handle a full wipe and reinstall if I should expect noticeable improvements over the 2.x.

As always, thanks for your work! Tell grandma happy 91st for me ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
I think in your case, just wait until android P - when you will be wiping anyway ( and it's getting close to release). there's going to be some changes and also fixes to v3.x P kernel - but I don't plan on adding these to the July v3.x build (it's ongoing development on the rebase, but it's not ready to push out yet.)...

some workloads are better under v3.x - but it'll be more pronounced on the P kernel.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
updates in a few hours;

=> LTS is all caught up (3.18.114) on both builds.

=> I'm running july firmware + exns-eas-v2.8.2 since lastnight.

=> flashing v3.x shortly (to run for the rest of the day).

=> when I get home this evening - I'll push updates
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
UPDATED / JULY BUILDS:

exns-eas-v2.8.2 stable kernel: https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_v2.8.2_f94351f.zip

exns-eas-v3.5 dev kernel: https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_v3.5_108688a.zip

-> Both kernels latest LTS (3.18.114)

-> Both kernels annoying manufacturer warning on boot is gonzo ;)

v3.5 has a few differences, but nothing to write home about. This is because neither of these (July) kernels are the rebase => I'm publishing them for android P (but doing the work now) && the v3.x kernel for P (although running on 8.1 on my device) has a bunch of changes landing that aren't quite fully backed and ready to use yet.

Examples; rework and porting (more); sched/locking code (much closer to linux/android-4.9, but I'm still chipping away at it), I have some changes coming for MM, rcu, etc... I'm working on improving the use of threaded IRQs (via (re-)prioritizing a few interrupts ~ the benefit here being that this can help avoid potentially contentious situations && also reduce the changes of buffer underruns happening with audio... other stuff. (it's all shaping up nicely, but I still have a todo list).

....

Note: I also update the OP download links (including the latest twrp boot.img).
[Google Pixel ROMs, Kernels, Recoveries, & Other De] La Yung:
This kernel compatible with custom rom?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
hey shag, a bit late, but;

could you try this build; https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_v3.5_wcd9335.zip

...and tell me if it gets rid of or reduces the audio distortion issue for you?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Hey ninez :) Just tested it on P, the audio distortion is worse, now only the audio distortion is present in most cases. No other audio or anything can be heard, most of the time. I grabbed a logcat/dmesg for you to take a look at, let me know if you would like anything else.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
cool. thanks. just an experiment (not in the official builds or anything). Just to clarify, You're talking about nothing being heard over headphones correct? (the latter is expected, I should've mentioned that - really just curious if it had reduced the distortion on touch sounds thru speaker...

anyway, doesn't really matter - as this is a temp commit...

EDIT: I'll probably get you to test the rebase soon to see if this problem still exists, I'll lwet you know when though.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Yes, no audio is being heard through headphones (except the distortion), I did not really hear any difference in the volume of the distortion. If you have anything else to try in the future just let me know :good:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Will do. Like my "EDIT" says, I'll probably get you to try the rebase sometime before release ~ as I'm curious if it will still happen for you. thanks man
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BarackMitzvah:
Killer release this month, not sure if it's placebo, but the kernel feels smoother than ever ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] almightysiman:
I feel the same,smoother than before.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
yeah, it's not a placebo. July firmware seems to be better... like userspace improvements, maybe.

kernel-wise on the v2.8, I haven't changed much. however, there may be a patch or two in LTS or from google that could be contributing a bit too. off hand, only one patch in LTS comes to mind, beyond that. not too sure...

I am playing around with some performance related patches on my device right now though. also will be testing another method of cpu-boosting...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Love4Taylor:
Schedutil is still not the default on Android P, even i flash Magisk before Kernel.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
post the stock boot.img for P and I can have a look, I have a hunch as to what the problem may be...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
This was happening on the kernel I am messing around with as well, for some reason the settings in the init.rc aren't being applied, I'll get the P boot.img up in a few if no one else does
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
yeah, post it and I will have a look
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Here ya go
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
I'll have a look at this later on today/tonight... I kind of ran out of time last night.

also, I was super burnt out. long couple of days/nights between work, life and implementing and testing a new "perfd" replacement that's going to be in v3.6 ....