yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Darian71:
This is odd. I've not experienced any hanging on the splash screen. Actually boots pretty quick for me. Phone personality I suppose. My 6P was always exhibiting something different than others on the same kernel we were always testing. I wouldn't think carrier would matter so hopefully you can get it all patched up for the awesome rebase. First run on the 2.1 /2nd test version seemed like it drained battery quickly. But I'm not concerned. 3 kernels in 3 - 4 days (long week, don't even remember lol), I figure I'm gonna need a couple runs to see the consistency. Thanks again. 10:12pm here. Bout time to ?. Have a good night guys.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
it's not odd. the issue they have described isn't something that is consistent or easily reproduced. things need to poked a certain way on boot for it to splat and it was easier to do on the stable build than test builds... on my local build, I think it's fixed... carrier could matter; I don't know how carrier specific bits might influence things...

both the test builds do drain a bit more, not by much though. maybe 15min difference... by the time I push a build; I've already run thru it a couple of times... any slight drain will be corrected later, after I'm done fixing things up... as at that point, I can merge some patches directly that should impact efficiency.

the rebase won't happen right away and likely won't have any affect on users... it will largely be housekeeping for me and cleaning up ordering/grouping of commits, getting rid of any cruft...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] greyhd:
I just flashed your second test kernel, I will report back.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
cool. thanks
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] natri23:
The 2nd beta is very good on performance and battery life as tested in android Safe mode.

But in Normal mode, something seems to prevent my phone from entering Doze and I lost alot of battery life when idling. Is there a way to check for that? I turned of all background app but it doesn't help
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] montbazon:
Turn off means nothing. You should erase them all
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ChongoDroid:
Why would it mean nothing? Freezing/disabling with adb would suffice no? ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I'm not entirely sure what on your system would be causing the problem ~ but it IS something on your system. By running in Safe Mode => You've just verified that it likely isn't the core OS, but something else (that's not allowed to run in safe mode)... you shouldn't need anything fancy to track down the root cause ~ if a particular app is the problem.... or even android itself; it will show up in Settings/Battery, if you leave the phone for hours to discharge. (say, overnight).

There's nothing in the new test build that's changed that would cause excessive drain.

What are you talking about? That's bad advice and impractical... People use the apps on their phone - suggesting that someone is to delete them is silly.... secondly, disabling an app from running in the background works as it should.... I appreciate you wanting to help and voicing your opinion, but in this case; it's not helpful or what should be prescribed. thanks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] montbazon:
I thought you meant just force close.

In normal build in apps don't cause battery draining
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
NEW TEST BUILD: https://github.com/nine7nine/Apps/raw/master/TEST-v2.1_62f9440.zip

Ya, I know - crazy short window before posting a new test build, Am i right? ;)

A few reasons;

#1 A handful+ commits that I worked on yesterday fix a long-standing live-lock / crash that I could easily trigger/produce when applying a particular patch (that I've been waiting to include for a while, EAS code) - but this required getting all of the scheduler / locking code upgraded && fixing some related code paths, first.

I've resolved this now (as well as a couple of potential other splats / bugs), It eems to be quite stable.

#2 I've pulled in last remaining EAS commits present in aosp/kernel_common/android-4.9-eas-dev ... that weren't present in my kernel. AOSP only committed them on Dec 1st, but the 3 troublesome patches (for me) had been floating around for a while. I had tried to integrate them previously, but failed... But now having recently reworked my kernel significantly; addressing the related issues ~ it seems to be fine now, working very well on my phone.

#3 Lastly, I also restored a couple of commits, that shouldn't have been reverted (much like others that I've been reviewing and fixing). One of these not being there could have definitely caused a splat / random reboot, being as it fixes a race condition in the cpufreq driver....

anyway, pretty valid reason to push a new one. critical bug fixes and EAS integration.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Darian71:
Thanks boss! Double tap to wake works beautifully on the last build. Had to restore a nandroid this morning because of Substratum. I'm deleting that friggin app and everything I've bought for it. Smh ?*♂️. Flashing now.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Why would you need to restore anything due to substratum? I can't think of a single scenario where one would need to do that.

EDIT: You can PM me about this, if you like. I know all about troubleshooting this kind of thing - but I don't want pollute the thread, since it's off-topic
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ayylmaomyman:
gonna flash this beta rn

previous beta performance was solid, and dt2w functioned perfectly

however doze didnt really kick in overnight; battery graph looks like this: https://photos.app.goo.gl/6PmPn65JQJfgrHPA3
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Interesting. yeah, try the new one...

I'm not sure what the deal is there - but doze worked fine for me during testing that build.... and does on the latest build too.... hmmm.....

I would say, try the latest and see if that persists... get back to me on that when you can / have more info....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ayylmaomyman:
will do, ill have results by tomorrow
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Do I just flash update over later update then reflash magisk ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
you always flash magisk after a kernel flash. otherwise you lose root.

EDIT: you flash the kernel zip, then magisk right after (no reboot in between needed)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Bryanx86:
I am really enjoying the performance of this kernel, and a little satisfaction for my prior crack flashing behavior. I love the updates, very fast, and everything is working so we'll together on the OGPixel with your kernel. Thank you sir!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Cool. thanks!

Still work to be done though; These latest test builds still need a bit of TLC and getting to the bottom of a few issues before I can push another stable release (but hey; a couple hundred changes later, there's bound to be the odd issue / 100% expected. lol).

I may still have to end up reverting the troublesome EAS commits -until I get it sorted out... I have at least one scenario where I can make things explode with those commits added in....

but the previous test build is still available and so is the stable build, so it's not like anyone is stuck, if they have issues on a particular build... What i'll probably do, as well ~ update the stable build with just fixes... possibly later on or tomorrow (so at least the DT2W and a splat or two are fixed, while I work on the test builds)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kentexcitebot:
Off-topic, but I absolutely like how you're communicative to XDA members about their questions and dedicated to clear any confusions. I can't say the same for many of developers who go silent on the forums. Huge props to you, and keep up the great work! Gonna test your next test build :good:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Well, I think it's important to communicate with users.... that doesn't mean I don't have moments when people drive me up the wall, asking the same stuff over and over again - or not following instructions, etc ~ but I just ahve to remind myself to be patient... We all have different levels of knowledge and understandings... so it is what it is...

SIDE NOTE: (at everyone kind of)

While I didn't update the link - i did update the zip itself a while ago ~ I had to revert the troublesome 3 EAS patches - I can make them explode, badly and somewhat easily.... So I don't want them in that 2nd test build. If i can do it easily - someone else will probably bump into it too...

a nice side effect though ~ I noticed the pstore driver was failing to decompress the /dev/pstore/dmesg-ramoops-N logs (which I needed to look at to see what happened)... anyway, now my builds won't fail on that step ~ so I can quickly look right from my phone at the logs and see what happened (or get someone to send me theirs, if they had a crash, panic or boot loop ~ and I wanted to take a look)....

not sure if google intentionally keeps these compressed (or just never applied a patch from 2014 to fix this), but it's easier for me, if they can be read plainly (by root user only, of course).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
so a couple of things;

#1. I've restored the smpboot code to Marlin -mr1 vanilla kernel sources (some upstream/mainline commits had made some modifications). I'm hoping that this solves any of the sporadic boot hangs or resets that people have mentioned. ~ I did this because I bumped into a couple of them today, on my newer builds and became motivated to try and address it... I haven't had a boot hang or reset (on boot) since and i've cold booted, flashed multiple builds, reboots, etc... So hopefully that is the end of that... who knows though; I've never been able to reproduce it reliably. time will tell, with the new commit...

#2 - I've merged in more locking code; a few bits were missed, while others I needed to enable a compile time locking feature. (I think this is what caused me to see the boot hangs / reboots today.)

#3 - If you've experienced any hangs or anything not-so-good on either of the last test builds ~ as mentioned above I did revert some problematic code (2 EAS commits) and I also have a v2.3 test build on my github. You can flash that one, if you like ~ It's the build that I've been using all day/evening (minus a handful of commits that I'm testing).

https://github.com/nine7nine/Apps/raw/master/TEST-v2.3_97d7ede.zip

#4 - I've been looking into the whole "contact your manufacturer warning" - as It's getting old, really quick. lol .... It used to be that you could modify the vendor build.prop (commenting out just 3 lines) and it would stop issuing that warning... however, that doesn't seem to work anymore... sigh....

Next I did a bit of googling to see what I could turn up. I was already vaguely aware that the init binary also does verity checks, but I didn't know much about the specifics. I came across this; https://gist.githubusercontent.com/...ab04ecd21c3e0176ee12f46579554c0653cf/foo.diff ... You can see invisiblek is bypassing safetynet checks in the init... So, it's very possible that the check giving us the warning is done in there, but idk ~ and we have a binary init anyway.

I also looked to see if there was possibly a new kernel cmdline that was the cause (that could be removed, just like how the safetynet is handled in the kernel). Sultanxda has a newer patch that allows removing multiple flags, but I have committed that patch (today) - it doesn't make a difference + I don't see anything that "pops out" like it too should be handled...

so no dice on fixing that yet. :( fun stuff.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] greyhd:
Thank you for the quick updates and sharing your hard work. Will flash this latest update.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
sure. go for it.

it's been working well, here. I can't really evaluate battery, as my stats are way off right now; too much flashing and many reboots, while testing.... but it's been stable for me, no funnyness after ditching the couple of EAS commits that caused problems...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] -iNSiGhT-:
Quietly waking up on morning.... Then...

Oh...!! A new test build to flash!!!

Flashing the new test build...

... No hang at boot (I didn't have that much)...

It'll be a good day. :D
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] greyhd:
Working good so far. Stand by time overnight is not the same compared to the previous build but 2% over night is still great, previous build was 0%. Keep up the great work, thank you again for sharing your work.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
the whole hang/reset on boot is sporadic. but, we'll see as we go, if it shows up....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
what was the 2% from?. .... I ask because part of the night my phone was unplugged, I didn't seem to be getting any drain... not a consistent 2%, either...

sometimes syncing & notifications, etc can influence that, so I'm just curious. thanks
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] greyhd:
Thank you for the quick reply. Looking at the battery stats it only has G+(2%) and GMail(1%) but this is the first charge, I will see how it does on the second.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
exactly, apps with notification, syncing and that run in the background...

you can't really say last time was 0% and this time is 2% drain... you haven't run it long enough and other factors are going to influence things... I don't even try to evaluate battery until either #1 I've been through a few cycles OR #2 my stats are consistent across several builds ... and even then; averages are more useful than any individual run....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] greyhd:
True this is the first cycle, I will run it through my regular use as I use it throughout the day. Thank you for the tips.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
NOTE: The latest TWRP supports decryption on 8.1 now.

Installing my kernel and magisk works fine with it too. ~ tested.

I've updated the twrp link in the OP, as well.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Bryanx86:
SS from accubattery. Speaks for itself.:)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Yeah. it's doing alright - slight regression from the stable build (on SOT) ~ but I'm working on fixing that. I have no real (personal) complaints with Battery life or SOT on my pixel / kernel.

So I'm probably going to push a stable build tomorrow -> 3.18.88 + exns-eas-v2.3 (actually v2.4) + some other block code and a few fixups. Should be good though.

I've got some other stuff that I'm working on now, but I won't push it in the stable build - I'll wait until I have it all worked out / well-tested ` as the code I'm working on is a bit touchy...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] SubnormalNebula:
So I have been using this kernel for like a week now but I've noticed quite high screen on battery drain and significant heat on the phone. I thought it might be an app or something but it was the same in safe mode as well. I also tried a factory reset and it still but that didn't help either. Going back to the stock kernel has fixed it so it seems to be something with the kernel (?). I was using the latest stable build.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
That doesn't seem consistent with my experiences or anyone else that I know of... Unfortunately, you didn't really give me any useful information or anything that I could even look into, so I can't really say much, look into it, etc ~ might have been better to bring this up 1/2 a week ago.

What I can say; I've never had "quite high screen on battery drain", nor a "significant heat on the phone".... and I think if you read through the thread - the consensus is no one is having a bad SOT experience / excessive drain ... so no idea why you would be experiencing excess drain with the screen on.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Watchyv2:
noticing some heat on some games, with the latest stable, might try the test build, or should i wait for the new 2.4?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
give me an example that I can reproduce/test myself... Also, I want more context, like is this hotter than it would be on stock by how much?

you can use the latest test build, the next build isn't hugely different. but a few changes.

stable vs. the test builds are big though
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Watchyv2:
just when playing games like Marvel Contest of Champions, War heroes, for a period of time bout 10 mins phone gets a little warm more than stock, but bearable to keep using
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] SubnormalNebula:
Ok sure, that's what I thought. Like if these were actual problems with the kernel I'd imagine more people would be reporting it. I can provide details/logs and stuff if that would help any? But yeah, if it is just a problem with my phone specifically I don't expect you to debug my problems for me, I'm sorry if that's how it sounded.

Regardless, thanks for the reply.

---------- Post added at 10:51 AM ---------- Previous post was at 10:49 AM ----------

For me heat was 40-50° compared to 30° on stock.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
No no. I didn't think you meant anything by it. All I was saying, is that it's hard for me to know, without more info - or something that I can test / verify for myself... But yeah, your situation does sound a bit atypical... I get 6hrs or more of SOT everyday with moderate to heavy use (heavy use means heavy applications, cpu intensive/ lots of processing, etc).... and on lighter use (like yesterday / overnight), I had 7 1/2 hrs (SOT). plugged it in at 9% to charge when I got home this afternoon...

Doing what? ... please be specific and are these numbers that you actually verified / checked or are you just throwing numbers at me / guessing?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] SubnormalNebula:
Oh ok, all good. That's pretty awesome though, and if that's the full potential of the kernel I think I'll keep digging and see if I can get to the bottom of the issue.

---------- Post added at 11:12 AM ---------- Previous post was at 11:09 AM ----------

They are verified numbers, 40° was average with just normal use, browsing, etc. And it would reach 50° with playing games (the room 2) and watching YouTube

I'm currently on stock and normal use temp is 30°
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Well, I'm generally pretty happy as long as I'm getting 6hrs SOT...anything less than that kind of bugs me, tbh....

I would say maybe try the last test build I posted, or wait until tomorrow ~ I'll be posting a new stable build tomorrow...

I'm also going to run some temp monitoring stuff under some different works loads and document Stock kernel VS. mine. Maybe tomorrow night.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
What are you monitoring temp in realtime with?

anyway, I'm going to do some monitoring tomorrow via adb shell, rather than trying to do it on my phone; running under various workloads on both stock kernel and mine - for comparison... I would expect mine to run a bit hotter, but not 10-20 degrees as you are saying....

no real point in you and I comparing our device temps - as we live in different climates... But I should be able to generate a whole bunch of data / stats comparing kernels.... So I'll get back to you on this.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] SubnormalNebula:
I was going of the CPU temp in the EXKM app.

(I've just realised that's probably not the most accurate)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
k. good to know. Yeah, I'll be going the real-time monitoring route and maybe a bit of sampling it into logs or something like that... I'd like to get a more accurate read of peak and idle temps....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] almightysiman:
just find out test build v2.4 has been uploaded,flash right away:good:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
EXKM simply shows the temperatures reported by the sensors. You can select from about 20 different sensors on the CPU->CPU Temperature screen

Nobody knows which sensor is which because it's different on every device. Sometimes you can figure it out looking at the thermal-engine config, which will often use a skin temperature. EXKM tries to report CPU core temperature, which fluctuates rapidly and can get very high. Most other apps report the first temperature sensor, which is usually a sensor located inside the case. These temperatures will go up and down more slowly.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] -iNSiGhT-:
Hi,

Had a hang at boot this morning (cold boot, phone was charging, switched off, during night).

Sorry... :D
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
which build? ... you always need to be specific. I don't keep track of of who's using what.

please send me contents of /sys/fs/pstore

put it in a zip and upload it somewhere with a download link, if you want me to look at this. thanks

EDIT: you can also create a bug report in developer settings and email it to me, PM me to do that though....

NOTE: this is is the kind of thing that you want to do right away, not after a bunch of reboots, etc.. Additionally, these are things that you pretty much need to do, if you are going to be reporting issues ~ I can't do anything to fix problems, if I can't trigger them myself, nor have any idea of what is happening...

So users expecting me to try and fix issues, really need to realize that it's pointless to point out issues / bugs, if you can't also provide as much information, as possible...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] -iNSiGhT-:
Sorry,

I'm on your latest Test Kernel (v2.3).

Can't access to the root of my Pixel with Solid Explorer (don't know if it's because of 8.1). Will look if another file explorer can access.

EDIT : Succeeded with ES File Explorer, will send a PM.