yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] xonelith:
I have this same thing; not sure if it is kernel related though, i haven't checked with another 8.1 kernel. I did try with the stock kernel (just Magisk installed) and was successfully able to access the root folder.

I did find a free explorer though (MiXplorer :)) so I've been using that. Honestly thought it was just me so didn't report it.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
A file manager breaking on an update would have absolutely ZERO to do with a kernel. It's probably just poorly developed and/or needs updating... I'm not sure why it broke / don't care, either... you guys should be reporting this kind of issue to the dev through the proper channels, if this is software that you use...

it's kind of off topic too....

but to add; honestly, I've yet to find a better File Manager than FX File Manager. The pro version costs money; but most of the pro features have to do with cloud / network file-system access ~ for the basics + root. The free versions is still better than most other file managers.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Bryanx86:
MiXplorer is the most thorough and has the most options of any file explorer I've ever found. Hootan Parsa is a Dev here at XDA, and has a few dedicated threads to his file explorer. Also add-ons available. Definetely worth checking out. It's the only one I use and I've used every one of them. Sorry for the Off topic...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
meh... on to file manager talk we are. lol

ya. it seems good. I doubt I personally would be able to get use to the UX. I don't like it... feature-wise it does seem to have a lot going for it though... definitely a decent option...

but I like the UX, speed/performance, binary viewer, app management, etc in FX. stuff that I have gotten quite used to having at my finger tips.... if I wasn't using to FX, this would probably be a good option.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Running test v2.4 everything seems to be running smooth thanks
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] almightysiman:
is there any difference between test build V2.4 and exNoShadez-eas_1ac9db8.zip?Thanks
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] greyhd:
One is a test build and the other is the stable version.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
yes. there are differences. lots... I also made no mention of the downloading/using the test build that I think you are using (?).....

mauhahahaha. Pure genius! ;) luv it!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
UPDATE: Stable build => https://github.com/nine7nine/Apps/raw/master/exNoShadez-eas_1ac9db8.zip

Also available on the OP download

- 3.18.88 lts

- a bunch of misc changes

- some fixups/changes to scheduling code.

it's largely based on the last test build, but I also touched a lot of scheduling code to workaround some issues && improve a few things. I didn't bother with making them into nicely formatted commits. for a couple of reasons;

1. I'm in the middle of getting a clean repo / rebase together.

2. I'm trying to best figure out how to manage / deal with my non-public/unavailable features, that doesn't create a lot of extra effort for me... so it's taking up time / planning...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] greyhd:
I wasn't trying to be a smart ass, but you have been great at explaining what is and what is not included in your kernels both stable and test, reading a few pages or even the OP would have sufficed.

Thank you for the update to stable build, I am running your test build and hit 7 hrs with heavy use(FB,Twitter, Email, Spotify).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I legitimately laughed out loud when I read your response. smart ass or not, it was great. ?

nice. well, I think you may find that the next build may be better. I didn't really get into specifics on what changes I made to the scheduling code, but some of them should improve SOT... as well, as potentially avoiding a spat or two...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ayylmaomyman:
This screenshot was the previous test build but standby battery is great so far

Gonna try new stable tonight
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] グリッチ:
First of all, sorry nine7nine for posting off-topic content, but as a Solid Explorer user myself, I figured I'd help them. So I had that same thing where root explorer would be blank, the fix is to go into Magisk Manager > Superuser and click on Solid Explorer, DELETE the entry, then run Solid Explorer again and click root. Then it can reauth with Magisk, there was an update on Solid Explorer recently that probably messed it up.

Now for the on topic (and semi off-topic) sorry for posting here in XL instead of regular, but as you, I read both threads to see what other users comment as well :)

I flashed the latest stable and while there are many changes in the back end, I notice not many changes in the users side. Meaning, everything is A-OK! Thanks again
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
no apology, all good.... and ya know what? => I think I had that happen once with AFwall and had to do the same thing that you describe (in magisk/superuser) - I didn't even consider that one...lol

that's good -> you shouldn't notice too much of anything, at least not without a close look and a day or two of use. I haven't evaluated battery too much with it yet, but I expect it to be a bit better than the test builds....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
UPDATE: Stable build: https://github.com/nine7nine/Apps/raw/master/exNoShadez-eas_62eb178.zip

you most likely won't necessarily need to update to this one, if already running the new stable build, although there are some differences... Most of the changes come down to re-organizing scheduler code and related headers... functionally, the changes shouldn't be noticeable, although they do exist...

Side note / fun fact; I'm toying around with the idea of porting marlin to android/linux-4.4 ~ I currently have a 4.4 kernel for marlin that boots - it has other problems, instabilities (as expected), but hey; that's not surprising.... it required some ugly hacks and a bit of forward-porting to get it booting, but interesting that it was doable at all.... I haven't decided whether or not this is something that I actually want to pursue, release or support; it would be a lot of work and added stress in my life.... Something that probably isn't worth doing, unless it was a legit paid gig... ~ It's kind of a similar situation to a couple of valuable && unique features (not from mainline or available in any android kernel) that I use, but won't be adding to my public builds, either; I'm not spending months implementing stuff; only to have kangers and vendors pick them up for free. that would be silly/dumb...

but I digress - anyway, I'm house-sitting over the holidays and xmas is busy - So, I may not push another build for a bit, unless I need to.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] -iNSiGhT-:
Just enjoy this time with your family and friends ! You've already done a lot for all of us.

Time to flash the new stable build. ;)

[MENTION=5930088]グリッチ[/MENTION] , your trick didn't work for me. FX Explorer installed...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ayylmaomyman:
Nah you're good with what you have now. Standby battery is incredible, sot is solid. Really I'd argue the kernel is almost perfect, maybe add hotplug support? But with schedutil, are custom hotplugs even necessary? I remember on Shamu I used AutoSMP and that was fantastic- but this is the pixel so I don't really know.

But you should def take it easy, enjoy the holidays. We're not going anywhere and the stable build yesterday is insanely efficient so I think that should hold everyone over for the time being (unless there's a critical bug)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
nah. we don't need autosmp and yeah, pixel / big.little is a bit different. we don't want to be messing with hotplugging... code that in older kernels tends to be notorious for being a bit of a big ball of duct tape and workarounds. the preempt rt guys highlighted it's shortcomings with their patchset ....and it's largely been fixed it in newer kernels... I've noticed some folks are moving some kthreads and workqueues to the little cluster, but I tried this and didn't like the result, so I didn't commit said changes... I'll find other ways to improve power savings...

my kernel isn't perfect though, although I'm glad it's working well... I've been cross compiling some tools to stress test, analyze my kernel. I've fixed some issues, but there is still stuff to do (stock and other kernels have issues too), I may submit a few patches to AOSP in the new year...

today's build does actually fix a few corner cases, over yesterday's build, which is why I pushed it. but most fixes would go unnoticed. although, I did get one report where it fixed a kernel panic / on boot.

you enjoy the holidays too! thanks
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] almightysiman:
no matter what has change,I always flash the latest:laugh:.nine7nine,Marry Christmas and have a good holidays!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
my last cycle on the latest stable build...I would say not too bad.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] -iNSiGhT-:
6+ hours of SOT over 11 hours...

You don't let your phone sleep that often... ^^
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
the only part to note; I would've had 7+ hrs of SOT, if I didn't charge... time span vs. SOT is irrelevant.

i shouldn't have to explain, but; I was on my phone all afternoon / evening. it's getting into the holidays; lots of phone calls and i was using my phone to cast videos, while using the browser, catching up on email, etc.... so yeah, it wasn't sleeping
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] -iNSiGhT-:
You can say that because your kernel sleeps well... ;)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
no, I can say that because SOT is a metric that has nothing to do with how well a kernel sleeps or when my last full charge was....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ayylmaomyman:
Yo dude newest update is actually fantastic!

???????
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
thanks. yeah, your SOT is similar...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] YzY_0505:
Can not access system?

I FINISHED YOU KERNEL BUT I REBOOT SYSTEM CAN NOT ACCESS IN. TRY ANYMORE WISH YOU CAN EXPLAIN thx!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] -iNSiGhT-:
If you don't use your phone as intensively (with much more idle/sleep time) as you do, SOT will be affected by "how well the kernel handles sleep", no ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nil253259:
My point is if you discharg your device in a small time span (like yours), there is less scope to drain battery while sleeping or being idle. On the contrary, if you would've used the sane SoT in a 24 hours span, it's even better as during those 18 idle hours your phone consumes same battery as those 5 hours for you. SoT to battery cycle duration is important of course
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
my view on this is that a device shouldn't be causing drain, when sleeping and since it doesn't on my kernel; it's not something that factors when evaluating SOT......

so when it comes to SOT, I evaluate based on how it drains while the screen is actually on and the phone is in use. obviuosly, different workloads are going to affect SOT more profoundly than drain while sleeping anyway.. how the scheduler behaves, how tasks/threads are placed / managed across CPUs, migration, sleep and idling (in the context of threads/tasks), frequency scaling, etc... these are bigger factors...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
bold text not needed. I can read.

I'm not following what ur saying... could you explan in better detail?. ... kernel should boot up fine, no reason you wouldn't be able to access the system, if u followed instructions properly...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] GizmoTheGreen:
does this kernel have ntfs/exfat?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
yes.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] YzY_0505:
Marlin_EXNS_eas_98adabe.zip everything be fine but exNoShadez-eas_62eb178 and exNoShadez-eas_1ac9db8 I finished The same way as before as a result Restart again and again,I can‘t access system，i don't know what's happen I ALWAYS Follow you method can you explain these？
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Mrfluffy2000:
I ran into the same issue. I fixed it by flashing the kernel then restarting. Then I went back into TWRP and flashed magisk and that seemed to fix the issue.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I have no idea why ur flashing any build, but the one linked to on the OP... I also don't know what u mean by 'can't access the system'.... if u mean that it boots into recovery after flashing, u didn't flash magisk after and without following that step, it won't boot... I don't support non rooted phones...

you don't need to reboot between flashing the kernel and magisk. you flash magisk right after flashing the kernel... then reboot
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
that extra reboot isn't necessary; you flash magisk right after the kernel... this is written in the OP.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ayylmaomyman:
Heres what you do:

1. revert everything to stock because you clearly fugged something up

2. go to fastboot mode

3. open a command prompt window in adb folder and fastboot your pixel

4. boot to twrp

5. flash the latest version of this kernel

6. flash magisk IMMEDIATELY after

7. reboot to system

it's not that hard
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] natri23:
Got this problem b4 when I tried to flash YouTube Vanced after Magisk.

Try re-flash this kernel and Magisk only
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] YzY_0505:
I MEAN HOPE YOU CHECK IT exNoShadez-eas_62eb178. Marlin_EXNS_eas_98adabe All normal version but i flashing you exNoShadez-eas_62eb178 follow you OP then reboot can't operation，system restarting again and again. i don't know i always follow you tips .BTW i flashing 62eb178 immedially flash magisk unfortunately can't normal access system
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dark2099:
I'm going to guess you've done this, but have you re-downloaded the kernel? Might be a bad download.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] YzY_0505:
impossible eas_1ac9db8 same issuse Do you have the same problem?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
again. you don't need to write in bold text. I can read. please stop doing that. it's annoying.

but there is a language barrier here; you hope I check what? 62EB178 build which myself and lots of other people have been running for days?

the only thing that I can suggest is, either;

1. follow this post; https://xdaforums.com/showpost.php?p=74922951&postcount=479

maybe something is messed up on your system. a fresh start may help.

2. or send me the contents of /sys/fs/pstore ....

to do this, you will need to first use the latest build which is bootlooping for you, then flash a kernel that boots and copy /sys/fs/pstore contents, upload it and I can have a look..

3. I don't know whatelse is running on your system, maybe something else is causing the bootloop. it does seem strange that you are the only person that I know of getting a bootloop on the latest build.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Donric13:
What further posts said should help. I had this problem when flashing arise mod before (system was booting before i flashed the kernel) . When i flashed this kernel i had constant bootloop. Had to reflash factory image (with - w in flash-all.bat) and then start again with flashing this kernel. You sincerly messed up your system with something you flashed before. BTW i don't even know if arise works properly (flash it after v4a in magisk). Bit i feel somehow sound through headphones is better after flashing arise mod.... (placebo?). But when updating kernel i have to flash factory image everytime before i can flash a kernel...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] -iNSiGhT-:
Don't know how arise works but maybe it's modifying something inside the kernel.

Did you try to flash arise again after you flashed a new kernel (like we do with Magisk) ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Donric13:
Yes. After installing v4a through magisk module i flashed arise stock (only core). It works but i don't know if it's really processing arise or only v4a... At least i feel it sounds better after....

Sorry for beeing ot.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] YzY_0505:
Please forgive my rudeness sorry! i fresh star erasing userdata but i try flash kernel again bootlop still it. i am helpless.................
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] YzY_0505:
sorry thx！
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
OK. so just to verify, you didn't just clear userdata, but actuallly flashed the system.img too, correct?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] YzY_0505:
absolutely! i always follow you op .....................
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
well, I don't know what the problem is and because I'm housesitting over the holidays; I have no access to my computer, so I can't test anything, nor post a build for you to test...

unfortunately, I can't reproduce your lack of being able to boot and I flash build, after build, after build. without issues...

whenever, I do manage to get home and have a few hours where I can look into this; I will... but until then... not much I can do to help you. sorry, but this is a busy time of year and I'm away from home.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] YzY_0505:
Thank you so responsible for the players, I love your KERNEL very much, if you do not like your kernel will be so concerned about it.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
hey, I'm wondering if you have themes installed for twrp?

I'be been pm'ing with someone who had a twrp theme installed to their sdcard (twrp folder). after deleting the twrp folder his bootloops stopped and it boots fine...

he was the only other person I know with the bootloops reboot issue... so I'm wondering if deleting your theme and/or the twrp folder fixes your problem....?

let me know.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] YzY_0505:
The key is i am fresh flash my device all the data something erasing........ i direct twrp.img access in. NOT TWRP.ZIP Did you mean to delete files after I finished your kernel on twrp?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
no. I'm asking;

1. if you have a theme installed for twrp to your sdcard?

2. if u do have a /sdcard/twrp folder, could u try removing it and then flash the kernel, magisk and reboot.

I'm assuming you don't have a theme installed, but idk. wouldn't hurt to delete twrp folder to check/test... maybe some other setting in there is an issue. idk...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] greyhd:
From his last post, I think he is flashing your zip via permanent twrp instead of doing it through fastboot twrp.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
no. I don't think so. he specifically says he's using the .img not. zip for twrp... he's using fastboot...

but generally, I'm having a very hard time understanding his posts. a bit of a language barrier for sure.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] greyhd:
Maybe a troll since he only has 10 posts and other people have given him step by step and your OP is very clear.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] YzY_0505:
i am sure not installed theme with twrp ....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] greyhd:
You should flash the December Google image without the -w and then fastboot twrp and install the zips from there.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] YzY_0505:
I do not have time to chat here, you do not understand my situation，I can do that I do not need you to remind
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
OK. do you want to delete the twrp folder anyway, just to see?. ... then flash kernel, magisk and reboot?

there's something not right on your device... that other people aren't hitting and the only person who had something similar. it was due to twrp...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
just an fyi; I don't understand your situation, either...

no one else is having your issue... there's something different on your system or something.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] xonelith:
Ya, try deleting the twrp folder as the dev mentioned. It was either the theme I had installed or some pre 3.2.1 setting that was saved. Removing the folder worked for me.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] droidfta:
I know its an issue about the message of "there is an internal problem with your device contact your manufacturer", I also want to add whatever this integrity check does even though magisk does still pass safetynet, my adtpulse app that use to work for my home security system no longer works saying that the operating system on this device has been modified, so this nag message/integrity check makes it so I can no longer arm my security system from my phone, albeit I hope they find a fix soon as magisk hide doesnt resolve the issue either.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
not sure that quote really applies to your situation, regardless;

the latest magisk beta can workaround the nag message. the method is a bit convoluted. requires flashing the kernel, backing up the boot.img, then renaming the backup from twrp, because twrp renames and puts it's own extension, rather than keeping it as a .img file.... then you have to use the latest magisk manager to patch, enabling an advanced option or two, etc... you'll have to head to the magisk beta thread on steps though... not sure if that'll fix your issue or not...

I can't really test, as I'm not home over the holidays, don't have my computer with me...

your app could also be detecting magisk manager. some apps do that now. that's the reason magisk manager can also hide itself (under settings).

I'm not sure how your app is detecting modifications or root, but you could try both of the above and see if it makes a difference...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] droidfta:
Thank you. I read the there is part that states to have the preserve avb 2.0 /dm verity box and reinstall. That still gives me the error on boot and the application adtpulse still refused to boot. I thank you for all the help

---------- Post added at 09:38 PM ---------- Previous post was at 09:28 PM ----------

1. Flash to stock

2. Set up with PIN, etc.

3. Boot into TWRP

4. Flash ElementalX

5. Make a backup of boot

6. Copy boot.emmc.win file to root and rename to exboot.img

7. Copy Magisk Manager app to phone

8. Reboot to OS and install Magisk Manager app

9. Open MM, check to preserve verity, then patch the exboot.img

10. Copy down the patched_boot.img MM made

11. Reboot to bootloader and flash the patched image to boot

I will try these steps later found what you think you were talking about, holidays are keeping me busy will try it later tonight thank you :)