yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
unrelated to kernel development, but;

gravitybox xposed module is running on Oreo now... I've been testing xposed, just to make sure and see if it runs OK. ....it's kind of nice to have a few of those custom ROM features back; 4x4 quick tiles, statusbar brightness control, better media/volume controls, statusbar icon colours/tweaks, battery settings, ram/memory bar on recents, etc, etc...

definitely, a few nice extra bits. beta software, but I guess I'll see how things go.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Wrong thread
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
off topic, yeah... not wrong thread - it's my thread ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I know lol
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
ROFL. thanks! I needed that
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Dont let it happen again lol no prob
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
thanks for setting me straight. won't happen again. ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Why ur add it from now on we expect a update every 20 minites lol thanks
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] TotoBerto02:
U use Xposed with ur kernel? Works good? And with Xposed you get better battery or the same or less battery life? Because with the beta1 I got battery drain caused by xposed
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DR3W5K1:
Reporting to OP and mods
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
yeah, i'm testing out xposed, anyway. I wanted to see if there were any issues or not, if it causes battery drain or if there were any incomptibilities (with some of the hardening kernel stuff, or generallly)...

i'm on beta2. mainly using gravitybox, since it pulls all the good usability options in).... I took a look at xprivacylua, as well - but xposed can only hook Java, not native code, so it's limited in what it can do, compared to what I already use.

I haven't noticed excessive battery drain. but I'd probably need to give it another day or two... I don't expect that I would get better battery life with xposed. but if it's stable with no drain - I'll probably keep it around for Gravitybox, since GB gives me the majority of custom ROM type features, that I'd actually want to use.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
thanks. ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] muppetmaster916:
Does GB allow icon packs on stock launcher?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] TotoBerto02:
Ok, notify pls if there are bugs or drain of battery or things like that with Xposed and ur kernel plz
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DR3W5K1:
Looks like you opened up a can of worms lol
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Donric13:
For me xposed and gb makes me feel the device not as snappy as pure stock with your kernel. Anyway in actual days xposed isn't offering much more possability to me than alteady implemented on stock, substratum themes and apps (centet clock, 3minit, autonotification etc.). So i am back on stock with your kernel...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
AFAIK, no. GB is more about making aosp / stock have a lot of cm/lineageOS and other typical rom customizaations..

will do. I kind of imagine, that at some point (or even now) people might be using xposed + my kernel. so it doesn't hurt for me to check it out, prolly good to know..

also, i've just been curious, as I haven't used xposed in years - my s5 was running my own ROM which was 100% incompatible with xposed, so I had ported n pulled a few xposed plugins into the ROM itself, rather than hooking thru zygote... which was better than using xposed, anyway.

Meh. sometimes things go off topic. I don't care, within reason. all good ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
true, xposed isn't offering much on Oreo. too early on... I also expect that xposed probably isn't that well optimized yet, either. probably room for improvement and things to be fixed... that said GB does actually offer a ton over stock (for me), all tiny usability features that I've missed from custom ROM days on my s5. it's all stuff that I can live without, but also nice to have...

I haven't noticed any slow downs (other than boot, after adding a module), but who knows. any combination of settings could have some undesired effect like that, or break things. i'm nit surprised really.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] -iNSiGhT-:
Hi [MENTION=7810360]nine7nine[/MENTION] ,

Had two hangs today and yesterday :

- yesterday, the phone didn't wake up with power button nor fingerprint sensor. Had to reboot by long pressing power button.

- today as I was using the phone, the screen freezes and the phone rebooted by itself.

Had no problem until here, running you test 3, no new app or setup.

A link for the pstore folder if it can help : https://mega.nz/#!gscgXALD!sGXNLX3kY11C0Y6KAx1aTr9OXJG6gsKYhCUQ4OgV2OM
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
cool. I'll look, but my next release won't actually be based on that test3 kernel (although some code from it will be). I rolled some stuff back, so I could make some changes/updates in full + it makes merging some other stuff easier, later....

you might just want to stick with stable or deal with a hang or two, until I push the next update. if I have time, I may try n pull one update before the Feb update... I'll see what I can do.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] -iNSiGhT-:
No problem to deal with this, i knew it was test builds, and it's only a reboot each last 2 days.

Thanks for the reply.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kingbri:
It depends on your phone, sched works best for me, but I have other apps such as amplify and greenify working as well. Schedutil could work best for you

And sched is on boot for me by default, not schedutil
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
well, I left sched available, since it's the default cpufreq governor for the Pixel (no real reason to remove it, either. imo)...

I do think schedutil is better under some workloads that I've encountered. It seems to be better on battery in some scenarios too (and i don't use greenify or amplify to compensate). but both are fine cpufreq governors ... so the option is there, whatever works best fir you.

FYI, if sched is defaulting on boot (without you setting it to),

then it would indicate to me that magisk wasn't present when u flashed the kernel. (since the kernel zip installation won't patch init.rc and apply some settings on boot, if magisk isn't present).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
no probz...

that's kind of interesting that it just started happening, or rather didn't happen sooner... anyway, i'm reasonably sure that the change responsible won't be present in the next build...

thanks for your patience.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] borxnx:
I am also having the unresponsiveness issue others have described using Test 3. Once or twice a day, my phone will just remain black until I hold power to reset. At first I thought it was because I had changed some settings in EXKM, so I reverted to all default settings. It seems to happen less over the past few days since I reverted the settings, but does still happen at least once every 24 hours.

Otherwise I dig the kernel, and can patiently await your next update. Thanks for all of your hard work, nine7nine.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Blue305:
Happened to me as well but only for 2 times in the last 2 days. Strange cuz I'm using the test 3 since you released it and only happened now. Also I'm using closed too with quite a few modules and that might have caused the error. Anyway that's not a problem for me.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bkkzak:
What order did you flash to get twrp to stick? If I flash TWRP, then Magisk then EXNS; TWRP gets wiped out (just reboots to stock recovery). If I install Magisk then EXNS, then TWRP; it won't boot into system (every reboot brings me to recovery).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] TotoBerto02:
Full Wipes except internal storage

Flash CrDroid

EXNS

Magisk

Twrp
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] muppetmaster916:
You should be flashing magisk before exno. It detects magisk and adds extra features, it'll work your way, but be missing tweaks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] TotoBerto02:
So you say i have to flash it like this:

Full Wipes

Rom

Magisk

EXNS

Magisk again because the root disappears

Twrp

Reboot
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] muppetmaster916:
ROM, magisk, exno (root doesn't disappear).

---------- Post added at 02:41 PM ---------- Previous post was at 02:40 PM ----------

I don't install twrp, I just boot it. But if you read in the exno thread, he says specifically to flash magisk first, for his tweaks involving anykernel2 to be effective.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] muppetmaster916:
Here you go, a bit more detail.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] TotoBerto02:
but twice I did as you say (flashing magisk before the kernel) but in the app magisk manager tells me that I do not have root
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] muppetmaster916:
My steps.

1. Fastboot boot twrp.img

2. Wipe.

3. Install ROM.

4.reboot system.

5. Fastboot boot twrp.IMG

6.flash magisk

7.flash kernel

8. Reboot system.

NOTE: sometimes, just in general my phone gets stuck at boot, and I hold power and vol down until it boots bootloader then press power to start and it's all good.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ayylmaomyman:
Anyone here tried a custom rom with this?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
there's a patch in aosp that I think resolves this. it's in my local build already. will be in next build... I hadn't had that happen in a long time, so I haven't been able to verify the hang on boot is fine (I guess I'll know, if/when I get a hang? ?

anyway, I'll be posting a new build soon (and obviously for Feb update).... just finalizing a few last bits and giving things a good run.

ya. lots of people have. mileage may vary... as of a few days ago, i'm actually running my kernel on a custom ROM.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kingbri:
I am running it on a custom rom as well and [MENTION=7810360]nine7nine[/MENTION], can you update the op to show the installation with twrp installed

1. Install twrp

2. Install kernel

3. Install magisk

4. Reboot

5. Open ex kernel manager or other app and make sure no options say apply on boot

6. Reboot to twrp

7. Install kernel

8. Reboot

9. Profit $$$ (even though this forum is free)

This takes advantage of magisk's high compression mode because twrp and the kernel take up a lot of space then the anykernel tweaks are applied
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ayylmaomyman:
Which rom?

---------- Post added at 04:19 AM ---------- Previous post was at 04:17 AM ----------

Wait so you managed to install both the kernel and twrp?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Bryanx86:
I think the idea behind this kernel in particular is only fastbooting twrp, then flash what is needed. Some people have managed to install also twrp on top of kernel, but it is not recommended by OP.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kingbri:
Yes, with the anykernel tweaks
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kingbri:
The OP is ok with the changes described, but I use magisk's high compression mode so that the kernel installation doesn't fail after installing magisk
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
i rolled my own... aosp with some extra stuff added in. utilities, test-suites/benchmarking. stuff that exists in aosp, but usually wouldn't end up in a stock ROM... more standard linux utilities/binaries, stuff that I want/need, but again; rarely ends up in a ROM... easier to build this stuff with aosp build system., most of the time...

also i'm working on some software. combination of kernel module, middleware and ROM integration (and I want to test it on my pixel, aside from my Dev boards).

android by default is missing stuff that I would have on my linux box - it creates a lot of hassles/headaches... so i'm putting together a toolset for myself... I'll be going back to stock though. no plans of maintaining a ROM for the pixel.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
yup. I don't care one way or the other. if it works: cool. if it doesn't or breaks, oh well... ? ... the kernel is smaller than it used to be and with nagisk's high compression mode, it seems to work OK now'

that said, it'll never work for me personally, due to some local differences to my builds and configuration... so it's not something I will ever want to test against, really.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
so Feb update is out, but I likely won't push an update until later tonight or tmrrw morning (I have some tech support work to do after work tonight)...

my plan is to push a stable build, based on the stable build (+ Feb patches). for the 1st update..

the reason being is that yesterday I triggered that bug from the test build where the device doesn't wake up, on my local build - but I did this via messing with the IRQ thread priorities - which sheds light on why the device wouldn't wake up; a thread was being blocked... so i'm going to recreate the issue, verify what's being blocked and also enable lockdep to verify locking behaviour... this way I can be sure that I've fixed the issue, before pushing a more substantial update...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
in other news;

1. google appears to have broken encryption for twrp again (so flashing will require either putting zips onto a usb stick and flashing them that way... or disabling your screen locl to decrypt and read/access the zips from internal storage).

2. my stable kernel from Jan 5th seems runs fine on with Feb 5th (unsurprisingly, but obviously will be missing any updates, until i update ;))

3. Google appears to have listened to me, when I complained to support last month over that stupid 'stage light' shadowing that you see when pulling down notifications or when you are on the lock screen ~ It looked brutal with a black background and dark theme ~ they have significantly reduced the opacity of the grey shadow / overlay....

Frick, they actually listened for once! => and all it took was me (and a hundred other ppl) complaining, then screen-sharing with their support person and her getting me into contact with with the development team and explaining to them why it looked terrible. LMFAO.

4. Magisk works fine && so does xposed, AFAIK / no issues yet.

5. I haven't noticed anything else new or different (although, I don't have too much time to explore && I don't use many google apps or pixel launcher)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I haven't noticed any changes but magisk and Xposed is so fluid now it's unbelievable. Gravity box is working great. Substratum themes are good also I'm using 19 with Gaia icons. everything is so smooth. Can't wait for this kernel lol. Also found a launcher called flick launcher which makes Nova and action launcher look like they are featureless this thing is packed with customizations. Just thought I'd share my experience and can't wait for this kernel to be updated think for the first time in my long grumpy life I'm happy with stock..........

PS. I got so excited I took my case off then realized that was dumb and put it right back on lol
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
yeah, flick launcher looks good, if you like aosp launcher 3 / pixel launcher paradigm.... definitely has lots of customization. I still prefer apex launcher... I also noticed flick doesn't seem to allow flicking up anywhere on the screen to bring up the app drawer. that's a bit annoying... maybe i'm missing something... no idea. doesn't matter... yeah, it's nice to have gravitybox, fixes a lot if stupid little issues in stock / aosp + adding a few nice bits in... it's pretty much the only reason I have xposed installed. (aside from curiousity and general testing).

well, like I said, I'll try and push an update later tonight, but if not. in the morning, for sure. ... i'm running my own local build with Jan 5th patches, but on Feb 5th update... so I would imagine my Jan 5th stable will work with today's firmware until I update, if u are in a rush...

still hoping I can iron out my local build, after some debugging in the next few days (just todo with fuxing the wake up bug)... I've changed, reworked and updated lots of stuff...

interestingly, i'm getting a marked improvement in battery life like +1hr... so i'm averaging 8hrs SOT now... so it would be gold to get this updated kernel into stable shape, available for use.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Blue305:
Omg I don't even get close to 8hr sot :( I use to get 5 / 5:30 but now I'm struggling to reach that number :(
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Actually flick does have a gestures panel. So u can flick up down left right lol and they have the blur option for app drawer like lawn chair. It also has integrated plugins now check it out
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
you can't really compare SOT to other people. there are too many variables;

- how your device is setup / configured

- apps installed and how they interact with the system

- usage / habits ...

I typically had been getting 6-7hrs for a long time (like the last few months anyway), but my current local kernel vs. Jan 5th stable kernel gets another +1hr ... so it lands at 8hrs (averaged).

previously, it was always around 7hrs, which was consistent with my SOT, when I monitored it, day to day use...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Blue305:
Yes you're absolutely right. But crazy stats nonetheless :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I did just check it out.... I know it has gestures, but in order to reveal the app drawer, by default I had to flick up from the bottom (vs. anywhere)... maybe you can change that, but i don't care, really. not invested in using flick, but to each their own. ?

honestly, I dislike the pixel launcher, lawnchair and all launchers based on aosp launcher 3...although flick is probably the best out of them, afaict... like I said; I prefer apex. it has had customizeable gesture support for years and years, has all of the customization, animation controls, etc that I would ever want. (and my home screen is minimalistic to begin with; no dock, no launchers, no widgets, etc. just a black/black screen.)..
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
well, when I get this last little issue sorted with my local build and can get it out as a stable build - maybe instead you will be talking about how you can't push your SOT over 6½-7hrs?? ?

crazy stats, I guess... it's not like i'm not a heavy user. I mean I run some heavy apps, etc... but at thr same time, I have gone through and tried to configure my system in ways that improve my battery life, fir sure....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kingbri:
[MENTION=7810360]nine7nine[/MENTION], twrp needs to up their game. This 3.2.1 recovery was a joke. You couldn't even flash ROMs!

And also, does the February security update give better battery life? Or is Google pulling an apple

(I do understand that the makers of twrp worked very hard in making their recovery, this is just my criticism and I am very grateful that twrp is available)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
well, twrp devs have to deal with lots of technical difficulties... google and other vendors don't exactly male it easy on them. Google seems to like to break things frequently.... so I don't really have anything negative to say or criticism of twrp, it's a constant moving target to keep up with Google's changes...

I was happy with 3.2.1 for the most part; because decryption worked fine, so it mostly served it's purpose... i'm not overly concerned about having to disable my screen lock for now to flash... i'm sure they'll get things resolved...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kingbri:
Hopefully they do soon! Can't wait for the stable release!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sapphirecoupe:
Does this kernel work with crdroid? I'm getting a softbrick
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I've heard so, yeah..... but it's nothing that I can personally verify or look into, since i'm not running that ROM....

the best thing would be to ask about custom kernels in that ROM's thread, or possibly someone in this thread, who may be running that ROM might speak up (?).

soft-brick, as in....? ....that term can mean various things. do you mean bootloop?

myself, I only test against stock + magisk. well, and recently I built aosp (but I've switched back to stock today).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Homeboy76:
Has twrp developers been notified encryption is broken?

[URL"https://xdaforums.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312"]TWRP 3.2.1-0 for Pixel Devices by Dees_Troy[/URL]
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
thanks, but i'm talking about twrp 3.2.1 + the Feb 5 update. does not decrypt on my pixel... worked fine on January, but not Feb update...

a couple people have mentioned/reported this in twrp pixel forum, including myself; https://xdaforums.com/pixel/development/twrp-alpha1-pixel-devices-t3500314/post75460142#post75460142
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bbender716:
Can confirm this behavior on sailfish fwiw.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Homeboy76:
Me too! Thanks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kingbri:
It does work, I've tried it myself, if you have twrp installed, follow my steps a few posts back. To get out of your bootloop, just clean flash
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I'm sure it will be resolved soonish and thanks for also mentioning it... I just pointed it out in this thread, so everyone would be aware :)

thanks for pointing this out! I knew it worked, but it's hard for me to get someone sorted out, when I'm not running that rom. very helpful and I appreciate it !
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
FYI, I got home late last night and ran out of time this morning to update the stable build for Feb 5th.

No worries though - tonight I'll have time when I get home from work! 100%

sorry for the delay.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bbender716:
Life comes first. Thanks for all your hard work man.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] AlkaliV2:
[MENTION=7810360]nine7nine[/MENTION] February Stock Boot Image for Marlin: https://www.androidfilehost.com/?fid=818070582850490923
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
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...