yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Alright, So I am posting an v3.x build, for those interested;

https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_v3.x_unstable.zip

IMPORTANT / PLEASE READ

:

=> I largely suggest staying on the stable build, it works well. The v3.x kernel isn't (yet) a replacement for the stable build. However, I think going forward I'll post snapshots every few days, but they will be marked "unstable" for good reason. So consider all of the below, before flashing;

#1. I'm still working on / ironing out various changes; this means that there are / may be regressions, quirks and bugs.

#2. There is a known critical bug (but hard for me to trigger) that will cause a kernel panic / crash your device (I've triggered it twice over about a month or so). I forgot to save the traces (the one and only time I had a good trace. Grrr?!#%!) and thus haven't had a chance to attempt to fix the issue yet...

#3. There is potential to bootlooping... Specifically; after flashing the kernel, it may bootloop (just restart your phone again, it'll boot)... Additionally, If you happen to crash your device; it will probably bootloop on next restart / power on. This is flaky right now -> I'm aware of the problematic code, but it's going to be a bit tricky to fix (and time-consuming); I need to sit down and play a game of "git blame" on mainline and android-4.4 kernels and make some local comparisons/adjustments/decisions to fix this up properly...

#4. Don't report crashes without logs to go with it (it really isn't helpful). /sys/fs/pstore, kmsg and/or full bug reports are helpful. (for full bug reports you can PM me, rather than posting publicly)... and/or if you've found a way that I can reproduce your crash - that is even better.

#5. Don't focus on OR report your SOT / batteryStats to me, or in the thread.... Why???

- you wouldn't be showing me anything that I'm not aware of - I run the kernel on my device, right? ;)

- these builds are NOT biased towards battery saving or well-tuned. (there are reasons for that).

- I'm still working on ironing out some PM-related code (yes, PM = Power Management), RCU and scheduler code (all of which can/will/do have an effect on battery life).

- I'm currently testing/using some settings that may actually impact performance and SOT negatively.

- I won't focus on fixing or improving SOT or anything like that, until after I've resolved other more critical issues that are higher priority (see: #1, #2, #3)....

Last, but not least;

If your big concern is SOT, stability / mission critical use and/or if you are inexperienced with debugging, dealing with "alpha grade software", etc => then please just use the stable build.... At some point, when I feel the v3.x branch is ready; I will promote it from "unstable" to "beta", which will be a better point to have a wider audience of users...

I'll write up another post about changes, as there are lots. But i'll do that later though, no time just now.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Overclock96:
Have you or someone else tested on android p?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
Try it yourself.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
No. I don't run P on my device, it's only @ DP1 stage. I won't support it in any official way until P is released. if it works, cool.

Stable works on P, this should too, but yeah;

pretty much.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Overclock96:
I'm waiting for at least 1 or 2 people to write about the performance on the Android P, if all is well - I put myself
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ayylmaomyman:
Sounds comfy, unfortunately this phone is my main phone so I can't alpha test to help you. Maybe for the beta me and more of the others can be of help.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
cool. sounds good.

it's mainly for those who have been asking, who are interested... i wasn't asking you (or anyone else, in particular) to test for me...

laid out the state of things, so there are no surprises... and some ground rules, if they do plan to test or report issues back...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
OK, so more details about the v3.x build (that I posted today);

Changes;

=> various subsystems updates and rework; FS, File locking, VM, vfs, Block, tracing, etc.

=> Introduce simple work and wait queues -> implemented in bock, rcu, sched/completion, elsewhere.

=> introduce and implement rcu_sync infrastructure && rework && tweaks to RCU and rcu_sync

=> Scheduler, locking and futex rework and updates. (several iterations)

=> lockdep pinning rework / update && load balancing rework.

=> Introduction of locallocks (essentially annotated locks. implemented and used in various places)

=> EAS updates from android-4.9-eas-dev (My kernel is caught up to this branch)

=> MM subsystem updates (several *painful* iterations. lol), locking changes && introduction of the oom_reaper

=> Binder, Ion, msm_ion, etc -> updates and reworks

=> driver updates and reworks (synaptics_dsx, i2c, msm-i2c, etc.... work in progress)

=> Workqueues: updated to 4.4 + backports. decoupled worker accounting from scheduler, locking/rcu rework.

=> genirq, forced threaded irq handling changes/improvements.

=> tty updates and fixing all related drivers.

=> introduce pm_wakeirq && implement it in various drivers (work in progress)

=> PM updates and rework (work in progress)

=> Introduce soft && hard lockup detector watchdogs

=> Introduce Hardware Latency detector

=> fixing references to HZ in various places.

=> lots of bug fixes; compiler fixes, upstream/backports, driver fixes, backports from newer msm kernels.

=> debugging and instrumentation added in a few spots, that will be removed later.

I've probably forgotten a few things. any questions, ask... Also, re-posting the original post, with status/warnings && download link to v3.x build below;
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
The 3.X test build works fine on P by the way, been running it since last night.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
thanks, Nick. I figured you were probably running it on P. No reason it sh/wouldn't work ;)

keep me posted; any issues, observations - good or bad.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bbender716:
Weird. I get "new image larger than current boot partition." Error

Running P with magisk 16.1
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
Google has released a new P preview branch for the kernel on GoogleSource.. r0.2? What's up with that? :eek:

https://android.googlesource.com/kernel/msm/+/android-p-preview-1_r0.2

Note: This is on the wahoo kernel, not marlin.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Do you have twrp installed? ...or maybe some other mod that touches the boot partition?

People are using it on P, seems like it might be an issue on your end....? How are you installing it?

not our device. N/A
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bbender716:
Ah yeah I have twrp installed. That the reason?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
Yes, that is certainly why.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kingbri:
Reflash the boot.img on BOTH slots in twrp and re-install twrp. I have it installed and the kernel is running seamlessly with magisk installed. If you want my steps, ask again

The defaults on the kernel aren't sticking for me, even rooted. I'm on P and the governor is still sched. Yes... I flashed it over magisk
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] vidfinnx:
All the game stuttering gone in March update Awesome work! So happy with this kernel now
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DR3W5K1:
[MENTION=7810360]nine7nine[/MENTION]

This is running very well ty!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Queentus:
forgive me if this is a dumb question: can i flash the latest kernel on Oreo November 8.0 or should I install the version of that time?

( rolled back to 8.0 because of the multi touch issue on 8.1 and P
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Glad to hear it ;)

Now, do you mean the March stable or the new v3.x build??

cool.

No dumb questions.... better to ask questions, right?

No, you shouldn't use the latest build on older versions of android. It will most likely bootloop (like not boot at all)...

btw, to what multi-touch issue are you referring? ... just curious.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] vidfinnx:
March stable build, I have no used v3 because bootlooping and crashing isn't something I'm particularly fond of hehe, hey have u heard of this poor wifi performance without Bluetooth enabled bug, I get what's called wifi jitter and ping is all over the place unless I have Bluetooth enabled, is there a way I can log it, it's been over a year and Google has yet to fix it or even look at it probably
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
lol. fair enough. I just needed to know for clarification (gets confusing when I have different branches/builds available). No worries; I'm not fond of bootlooping and/or crashes, either. ;) .... My hope is that the crash I did encounter (weeks ago) is gone && I'm looking at the bootloop issue today, to see if I can't get it resolved. We shall see. :) (the bootloop thing is pretty minor though, just requires a reset, then it boots - which is why I haven't fixed it yet (lower priority).

Yes, I'm aware of the wifi / bluetooth issue .... I'm not sure if that is something that can easily be solved. My observation is that enabling bluetooth actually doesn't solve anything - it just reduces the issue a little. you're still going to have jitter, interruptions / spikes in latency / unbounded latencies....

it's also inconsistent because sometimes with bluetooth disabled; my ping times are actually the same as when bluetooth is enabled, which is typically around 20-30ms with spikes around 100-200ms. Now, compare that to my i7 Archlinux box (*on the same network*) => 17-18ms, no spikes => however, unlike the google Pixel, my i7 has ZERO shared interrupts, isn't an SOC and has significantly more CPU power.... idk, I don't think the latencies and jitter you see with the Pixel are super abnormal... I also suspect that you would see something similar on other msm8996 SOCs. (and probably a lot of other devices. my hikey arm board has spikes like that, for example).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] vidfinnx:
Yeah people with pixel 2 are experiencing this issue as well, it's ridiculous really and Google has just stayed silent on it and told people to factory reset, I have photos showing with Bluetooth off and then on but I don't really have a good testing app that shows ping over and over, I doubt it's an easy fix but it has been happening no matter what I do, there is tons of threads on it if u Google pixel Bluetooth wifi performance. It's probably a hardware defect I'm guessing. The jitter literally goes to zero with Bluetooth enabled the whole time consistently, I've noticed the wifi signal is erratic without Bluetooth enabled and then when it's enabled it's consistently full strength and distance from router doesn't matter, I am not smart enough on programming and code to possibly fathom what is going on, also holy moly man this kernel is murdering anything else for SOT, I played lineage 2 for an hour this morning on a fresh Oreo 8.1 with swift black substratum and was at 69% from a full charge, that is better than I have gotten on anything ever.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] vidfinnx:
I've observed using one app the ping go all kinds of crazy before zeroing in on a low latency with Bluetooth disabled which is probably the jitter which causes enormous amounts of warping and annoying delays when gaming. So the first picture is Bluetooth disabled, second one with Bluetooth enabled ping will always be 24ms with zero jitter and consistent performance. Really annoying haha damn u Google, wish I didn't have to enable it I need to save as much battery as possible

---------- Post added at 06:43 PM ---------- Previous post was at 06:42 PM ----------

My computer doesn't show me wifi jitter it is getting on the test, it doesn't even show that statistic and it's an I7 with an Intel WiMax adapter
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Queentus:
That's very kind of you! :victory:

Here's the post of the multi touch issue on 8.1: https://xdaforums.com/pixel-2/how-to/multi-touch-issues-8-1-0-dp2-t3711649

And here's the issue tracker: https://issuetracker.google.com/issues/70344455

It's kind of sad that Google hasn't fix it since 8.1 DP2. It's not a big deal for daily use, but for gamers like me( I play PUBG mobile lately), it's a devastating bug.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Haha. cool... yeah, I wouldn't really know, as I don't test any kernel, but my own (usually against itself, as I go) and sometimes stock kernel. no time or interest to test against anything else...

it could be a hardware defect or design limitation. it could be an issue elsewhere.

* the ping command displays in a loop by default, can't you just use it?

not sure it's a google problem, at least not directly. it sounds like a Qualcomm problem, maybe.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
interesting. maybe later, I'll have a test of this for myself. try n do a screen capture of it too... i'm curious.

I thought you referring to something else.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
I have this issue too randomly when aiming while running in-game, it's seriously irritating when the screen just flips out when you're trying to snipe. :crying::(
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I wonder if there is anything in the commit log during 8.1 developer preview cycle that sticks out as possibly being the culprit?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Queentus:
Someone in the issue tracker said the Flash kernel of Pixel 2 XL got a fix: https://xdaforums.com/pixel-2-xl/development/taimen-flash-kernel-1-00-t3702057
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
noted. ?

i will look into it. thx
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Queentus:
I'm sorry that I wasn't patient enough. The one who said tjr Flash kernel fix this issue just confirmed that it wasn't fixed after all.

The problem still exists. Even in Android P DP1.?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
all good, man.

When it comes to bugs, this is kind of expected, to some degree, imo. ~ He/she probably just didn't encounter or possibly the effects of the bug weren't pronounced (at first), so they thought it was fixed... Sometimes that's just how things go....

I tested this bug on my device last night (v3.x kernel) and I did observe that the pointer jumped a bit. However, it seemed less pronounced than the example that I saw in the bug report - that could mean absolutely nothing; as I only tested and messed around for about 10-12min....

When i tried it, the jumps were so small that I would've been surprised on it messing up game play. I probably need to run it for much longer && also try out a game that really shows off the crappy impact.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
Hey, just a curiosity. Is the charging overcurrent bug on the Pixel XL fixed in your kernel? It's been making a bit of a stir in the community as it has an effect on a bunch of people. Google has said they're going to release a fix sometime soon. :p
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Google marked the bug report fixed yesterday. Afaict, April build should include the fix... Google also addressed this and gave an update on Reddit too.

I personally wouldn't be able to observe the bug because AFAIK it's an XL only bug. I didn't see any patch/commit on the bug report, so I have no idea if it's a kernel bug and/or userpsace issue that is at fault... But We''l be getting the April update soon, so I'm not about to dig around for a fix - when the work has been done and will land soon.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
I think it was an issue with the charging driver in the kernel, I'm not sure. Anyway, good thing it's fixed I suppose.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Overclock96:
I play in PUBG and in this connection I would like to ask if you can add control of the overheating sensor? Well, or work in this direction
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
why?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Overclock96:
I would like to turn off throttling

I advise you to play 20 minutes in PUBG mobile, and you will all understand :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kingbri:
I know what you're talking about, I am using ex kernel and it hasn't happened for me
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DR3W5K1:
[MENTION=6389797]Queentus[/MENTION]

[MENTION=7810360]nine7nine[/MENTION]

Modify this one line "touch.pressure.scale"to the value in my screenshot. This has made my phone awesome again. Sweep to sleep is back to the way it used to be also lockscreen shade pulldown!!

[EDIT] SRY FORGOT PATH

/system/vendor/usr/idc

Also it may be beneficial to add a zero to the value I posted if you have a glass screen protector.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] almightysiman:
what was wrong with the sweep to sleep before you modified this file?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DR3W5K1:
Every since I got 8.1 I have had a really hard time sweeping to sleep. Not to mention swyping had become ridiculous every text I would have to correct. Not anymore
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
This would help if you wanted to cause an explosion.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
busy weekend, slow reply ?

IMHO, this would be a very bad idea... thernal throttling happens to reduce heat and to protect the processor from damage. so personally, i'm not interested in enabling users to do that... I'd rather be cautious and avoid cooking someone's device....

this semi-relates to why I don't support overclocking. these devices don't have the luxury of good cooling and can get hot - I've done (OC'd) tests where my device is fast charging, while running stress tests and the thermal throttling wasn't enough - the device actually shutoff due to dangerously high temps. (which will likely be the result of disabling throttling, afaict)...

..well, and I won't support overclocking because SD821/MSM8996 Pro-AB used in the pixel wasn't downclocked by Google, nor was it intended to be run at higher clock speeds - it's also well-established that some pixels will become unstable using OC.

I think it is wise to avoid putting our devices at risk of damage and/or unnecessary ware... I get that you are trying to squeeze some extra performance or to smooth things out, but I think we may need to explore other options - I'll look into it, see what i can come up.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Overclock96:
thank you, you explained it well to me :)

my love for mobile Pubg is growing, but optimizing this game ... I think if you looked at free time, you would have something come up, this is a very popular game now will be

but what about lowering the voltage? You could add a voltage drop for better energy saving
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kentexcitebot:
This is also a bad idea. Every SOC is binned differently, so while lowering the voltage table may be fine on your Pixel XL, someone else's Pixel XL could get unstable, crash, or may even be unbootable depending on how agressive the undervolt is. Lowering the voltage will also NOT increase battery life! The only benefit gained is thermald won't throttle your CPU speed as quickly because of *slightly* less heat on the SOC; however, keep in mind: instability as a result of lowering the voltage will raise the CPU, hurt performance, and drain battery. It's just not worth the trouble unless we overclock, which the OP repeatedly mentioned he won't do.

If whatever game -- PUBG -- is running poorly for you, it's either running poorly for everyone or there's something in the background on your device that's using the CPU; it's most commonly the latter. PUBG does have performance regressions as it's a very big game, but it's unfortunately up to the publisher to fix the regressions.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] vidfinnx:
frankly its because android has sub par game optimization due to the huge amount of devices, while most gaming software was written in IOS first and only has to be optimized for like 10 devices if that. Its just the nature of android and it sucks, i still cannot bring myself to join the apple crowd instead i will opt for a even more powerful android device to basically compensate for the crappy programming. IOS holds the market for games, ive dealt with a bunch, do i find it unacceptable that a flagship device only a year old performs like this, absolutely, which is why pay to win mobile apps dont get money from me
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
No. I'm not doing that... while I do appreciate input/feedback, I've very consciously decided to NOT support crap like this, nor am I giving users the option to screw around with settings that may cause instability, harm and/or even damage their device, permanently.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DR3W5K1:
Has anyone else given this a shot? jw
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
I think iOS started off in a much better, more cohesive position. it inherited quite a lot of good stuff from MacOS (xnu kernel, cocoa, Objective-C, etc)... unlike android, iOS is mostly compiled/native languages, none of this 'VM + Java/cotlin + jni + native code spaghetti'... they also control their hardware and software, while android is really fragmented (as u mentioned)...

I think even ignoring android fragmentation, iOS had many advantages (from the start) and in a lot of ways, iOS must be easier to target && is likely more performant, even before much optimization...

I actually despise android userspace... I wish Google had taken a more similar approach to mobile, as Apple; Google could've stuck with mostly native languages, not used Java at all and shared more code, libs, etc with Desktop Linux ~ but Google doesn't like the GPL, at least not in userspace. (and they bought android / did not create it).

I would say (not defending Google, but) I don't expect a flagship from 2016 to be able to compete with a flagship from 2018... I also expect that heavy games written in 2017/8 may have sour spots on older devices.... that said; I would expect that game developers would optimize for this and/or have settings to improve performance on slower devices (kinda like how Minecraft allows you to not render certain elements - which really sped the game up on my neice's older tablet)...

anyway that's a bit of a rant, but also my 2 cents on the subject...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Queentus:
Yep. Stuck at bootanimation first. Long press power botton and the phone booted successfully.

But, it doesn't fix the multi touch issue. Tested with PUBG Mobile myself.

BTW, I don't think the dev should do anything to optimize specially for a mobile game. It's unreasonable.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DR3W5K1:
Well I agree
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Queentus:
It seems that Google finally comes up with a fix for the multi touch bug, just found this: https://android-review.googlesource.com/c/platform/frameworks/native/+/640606

:laugh::laugh::laugh:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nick80835:
Thank the heavens.