yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Alcolawl:
I did not intend to make it look like I was calling anyone out for having crashing/bootloop/random reboot issues. Was just reporting my experience. I understand not all CPUs are created equal, and that a non-OC kernel is necessary. I run stock, so I thought maybe it was a ROM issue as well. My bad dude.

My experience with SoT has been, at least with the super mega thread for the Nexus 5X Interactive Governor Tweaks, that people will just throw out a number "5 HOURS OMG" and then not explain what their setup is. Even if they do, their usage most likely differs to another user. Combine this with different WiFi and Cellular reception and you now have two users running the same settings in two completely different settings and they're both expecting 5 hours of SoT. So, in that way, it's a useless metric. The only way SoT is really useful, in my eyes, is when you're comparing it against yourself.

I agree that the EAS governors are incredible. The fluidity and performance they provide is just incredible when compared to other devices I've used. I have a feeling I'll be switching back to Schedutil in a few days if I don't get bluactive where I want it.

Sounds intriguing. When using non-EAS governors, I find input boost necessary. I flashed the schedtunefix800.zip which you've stated sets input boost to 800 (844 MHz?). Can you clarify which boost you're referring to? It sounds like you're talking about Touchboost, which I loathe. Input Boost is usually a boost to a semi-low clock speed for like 40 milliseconds. Unless they changed things with the Pixel...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Ofthecats:
No, no worries buddy, I didn't take any offense. At the time, i just thought we had some counter points with our experience. I take a logical approach, and felt the need to justify my claims, especially about the nonOC because it's extra work for Freak07.

I sympathize in that SoT is abused, and that it's only valid if other variables are largely unchanged.

My experience with EAS is that, thus far in my Android modding history, they've provided the best battery/performance balance.

So what is everyone's opinion about the additional governor's?

What IO schedulers do people use?

What are your setups on kirisakura?

I'm trying darknessched

top-app boost 10

gpu simple_ondemand, UC to 510, initial frequency 133

Zen 1024

Zram disabled, swappiness 1

Before trying Kiri, I used to change memory more, but stopped
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] CHANGiism:
just wondering, where in EX Kernel Manager are you guys setting top app boost? I am using schedutil and I do not see setting for top app boost anywhere..
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] joetheshmo:
You have to add the value /dev/stune/top-app/schedtune.boost to exkm yourself under tools -> user settings
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
I thought that maybe 2,2ghz would be tolerable for all chips. Mine crashes at 2,3 ghz. I didn´t see anyone reporting any crashes due to OC so I left it at 2,2ghz.

Also there are different revisions of our soc as you might be aware. OP3T has another one that can achieve higher clockspeeds but the frequencies can´t be sustained for to long. I wonder if all chips of sd821 are maybe exactly the same. I took a brief look over the voltage tables and there are indeed some differences.

So there are 2 roads I can take. Actually 3. Remove CPU OC alltogether, compile 2 versions or try to understand [MENTION=4684315]flar2[/MENTION]´s aroma script so one can have choice when flashing it.

take a look here, line 412-461, especially 429 and 451-456.

https://github.com/DirtyUnicorns/android_device_google_marlin/blob/n7x/power/power.c

schedtunefix 800 sets it from 1100 to 800 (844mhz).

I could reproduce this quite easily, when not flashing the schedtunefixnohint at all or using a rom with the hint completely removed.

I enabled the CPU overlay within devcheck from flar2, went to a screen where I knew all cores should drop to 307mhz rather consistent. Whenever I would have touched the screen all cores scaled to 1132mhz for 1,5 secs.

Personally I would recommend FIOPS or deadline as IO schedulers.

My setup is:

OC Kernel

schedutil

all values from schedutil to 500

CPU scheduler options > sched_migration_cost_ns to 0

GPU to 652mhz

msm-adreno-tz

GPU boost to medium or high

inital freq 214

zram disabled

IO > deadline

schedtune boost top app: 6

schedtune boost foreground: 6

oh and schedtunefixnohint :)

additionally to top-app boost you can also set schedtune boost for background,foreground, and general schedtune boost.

I will add this piece of information to the OP so it is easily accesible.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Ofthecats:
[MENTION=3428502]Freak07[/MENTION] I would suggest removing OC altogether to keep stability across a greater number of devices, while not compromising performance significantly and reducing the amount of work.

I never noticed a great difference between IO schedulers.

Would you mind sharing the logic behind your setup?

I tend to tweak for battery life improvements.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] BHermes211:
Does resurrection Remix not use schedtune boost?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DespairFactor:
There is a bug in init for lineage based ROMs. They create a boostgroup for system-background which causes issues with top-app boostgroup being mounted.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] BHermes211:
OK, thanks

How much does that impact Lineage ROMs?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DespairFactor:
Depends if you boost top app or not really.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] BHermes211:
I haven't changed any settings, what's the default?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Alcolawl:
Hard reboot when waking screen

No battery gains to be had from running blu_active. I switched back to Schedutil this morning and, with similar use, came home with about the same battery percentage, maybe even a bit more. The experience is much more fluid as well.

However, I've run into a new issue with 0.12 that I have not previously experienced. The phone will sometimes crash when attempting to wake the screen. I haven't experienced this issue enough to determine whether or not it happens solely when pressing the power button or when using the fingerprint scanner as well. Upon attempting to wake the phone, the screen stays black (usually causing me to press the power button a second or third time). The notification light will keep pulsing, notification sounds will still play (if there are any ones received during this time), but nothing else will happen. Eventually the phone will reboot.

Anyone else experiencing this exact issue? Figures I say I'm not getting random reboots and now this happens lmao. I will grab logs when I can.

EDIT: Running NOF27B
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Ofthecats:
My issues weren't similar to yours, but I'd say try the nonOC and see if you can get the same issues
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] CHANGiism:
I actually ran into couple of what Alcolawl has described and this was with nonOC. So you aren't alone!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
A log would be great yes. In the meantime maybe it will happen to me too.

Did you experience this only on 0.12 or also on kernels before?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] CHANGiism:
I experienced it for couple recent versions. I will try to grab a log as well. Would last_kmsg be enough? I never grabbed a log before.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hellsgod:
I experience this error since around a month or so. It does wake up most of the times I press the power button a second or third time. I'm using my own kernel, but it seems the issue is the same. It happens around once or twice a week on my device. I looked at the log and the only thing I saw was a DSP error on my device.

hells

---------- Post added at 05:14 PM ---------- Previous post was at 05:02 PM ----------

Here's what the log captured:

[49640.865958] c0 0 Report pwrkey press event

[49640.971476] c0 0 Report pwrkey release event

[49641.163748] c0 25625 [AUD] snd_soc_qdsp6v2: ASM_DATA_EVENT_WRITE_DONE_V2

[49643.110076] c0 0 Report pwrkey press event

[49643.295675] c0 31050 Report pwrkey release event

[49644.055327] c0 28641 Report pwrkey press event

[49644.293458] c0 0 Report pwrkey release event

[49644.696852] c0 0 Report pwrkey press event

[49644.990178] c0 1413 Report pwrkey release event

[49647.723738] c0 0 [AUD] snd_soc_qdsp6v2: ASM_DATA_EVENT_WRITE_DONE_V2

[49648.998773] c0 0 Report pwrkey press event

[49649.005643] c2 11197 FG: fg_is_batt_id_valid: fg batt sts 0x2c

[49649.515675] c0 0 [KEY] gpio_keys_gpio_isr: key 1-74, (40) update debounce mode

[49649.515743] c0 0 Report pwrkey release event

[49650.568883] c0 0 Report pwrkey press event

[49650.737123] c0 0 Report pwrkey release event

[49651.000788] c0 0 Report pwrkey press event

[49651.121528] c0 0 Report pwrkey release event

[49651.328989] c0 0 Report pwrkey press event

[49651.473272] c0 0 Report pwrkey release event

[49654.273719] c0 0 [AUD] snd_soc_qdsp6v2: ASM_DATA_EVENT_WRITE_DONE_V2

[49659.993743] c0 25625 [AUD] snd_soc_qdsp6v2: ASM_DATA_EVENT_WRITE_DONE_V2

[49661.363680] c0 0 [AUD] snd_soc_qdsp6v2: ASM_DATA_EVENT_WRITE_DONE_V2

[49662.173640] c0 7399 [AUD] snd_soc_qdsp6v2: ASM_DATA_EVENT_WRITE_DONE_V2

[49662.180450] c0 0 Report pwrkey press event

[49662.337641] c0 0 Report pwrkey release event

[49664.436746] c0 8229 [AUD] q6asm: q6asm_callback: cmd = 0x10bce returned error = 0xa

[49664.436888] c1 11914 [AUD] q6asm: __q6asm_cmd: DSP returned error[ADSP_ENOTREADY] opcode 68558

[49665.633315] c0 0 Report pwrkey press event

[49673.158974] c1 478 [TP]:synaptics_rmi4_fb_notifier_cb, event = 16 blank = 4

As you can see, I had to press several times to wake the device up, not only two or three times.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Ofthecats:
It has come to my attention that default bfq settings may be out of date, as well as bfq itself. Unfortunately i don't have references to link ATM. But to show an example, slice_idle should be 0 for bfq.

Other devs may have helpful information on this.

So far, with my usage on Kiri, it has been on par with Sharkey in terms of efficiency and performance.

Good work.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Alcolawl:
I experienced it again today. Had the phone in my pocket while at work, talking to a fellow staff member. I received a text and I reached down to grab my phone and check the notification quick. I pressed the power button, nothing. Pressed it again and again in rapid succession. I just realized while typing this that pressing the power button twice like that launches the camera. When this works normally the phone vibrates for a split second, wakes the phone, and launches the camera app. This time, however, the vibration motor got stuck on and vibrated for about 10 seconds straight until I got fed up and manually shut off the phone by holding the power button. Kind of frustrating because I was going to pull my phone out anyways to give my colleague a server address they needed for work. So we just stood there for 30 awkward seconds while the phone restarted.

Anyways, because I reset the phone myself, no last_kmsg was generated but it definitely has something to do with waking the phone. This issue did not happen on 0.11. I'll grab a last_kmsg the next time it happens.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DaveHTC200:
I did too experience a few freezing with screen off and reboots but on 0.11 however i couldn't get a log (not much use i know) but wanted to feed back info.

This was limited to overclocking through EX app.

Now on O so can't be more help, just wanted to say it didn't appear limited to 0.12

Thanks, and really appreciate your work!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
Information about the Update that is going to drop

So this one will be pretty big update.

The recommendation is still to flash the schedtunenohint zip which disables qualcomm´s/google min freq boosting when interaction with the phone completely.

However to counter any stutters I added sultanxda´s CPU_Input_Boost which will be disabled by default. This input boost is much more subtle. You can simple activate it via EXKM in case you need more smoothness.

I added in another EAS governor made by [MENTION=4388232]ZeroInfinity[/MENTION] that focuses on maximal efficiency and battery life. Information about all governors based on sched and schedutil can be found in the second post.

I tried to tune the WALT settings again. Please report back when the kernel is released.

Oh and bfq will be updated as brought to my attention by [MENTION=5315603]Ofthecats[/MENTION], thanks to [MENTION=5169465]DespairFactor[/MENTION]

about the reboots. once I will get the reboot and myself a proper log I will definitely look at it. Until now the reboot did not happen for me. Maybe I´m just lucky or I don´t know.

Stay tuned all

P.S.: I added a whole lot of information about our EAS governors on the second post. Please read it and if you have time try to tweak the **** out of those governors and share your settings with us all here. Thanks for the support to all that leave some nice words. I really appreciate this.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Alcolawl:
The phone randomly rebooted 2:30 this morning while I was asleep. The startup sound scared the **** out of me. When I woke up for work, the first thing I did was roll over and check for a last_kmsg file and none was created. Why is this so? [MENTION=3428502]Freak07[/MENTION] Is there another log file that I can grab instead that would be beneficial to getting to the root of this issue?

Don't mean to be annoying about the reboot issue. It's really not that big of a deal but it's frustrating to me that I can't grab a log for you because coming on here and complaining about it certainly doesn't help.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Ofthecats:
Note that there is an sepolicy issue with tuning BFQ. The latest that despair merged, I think v8r6, would cause a kernel panic upon trying to change BFQ settings. It is only tunable while selinux is permissive at this time.

Thanks to [MENTION=5169465]DespairFactor[/MENTION] for reading my logs and finding the cause lol
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DespairFactor:
Actually, it isn't fully isolated, I noticed it later on with it still permissive, and also toggled fsync which allowed me to tune it again. Also, this caused a reboot later on, it seems spurious accessing of the sysfs for iosched causes reboots for BFq v8r6-8. I am looking at getting us bfq-mq for 3.18.y from the 4.11.y implementation.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Eyalkn:
I wonder if it is connected to the same reboot issue I had on my old G3 phone which was caused from in low reception areas cause I also had a reboot yesterday with my pixel on 7.1.2 with franko kernel
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DespairFactor:
You'll never find a last_kmsg on this phone, you need sys/fs/pstore/console-ramoops
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Alcolawl:
Thank you, sir. You are a gentlemen and a scholar.

[MENTION=3428502]Freak07[/MENTION] - Console-ramoops is attached.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] CHANGiism:
And here is mine after it rebooted just this morning.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
Update

an Update is in the air ;) stay tuned :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
Update to 0.13

Hey guys and girls,

here is the promised update to 0.13. As already mentioned I implemented CPU_Input_Boost by sultanxda.

So recommended is:

To flash the schedtunenohint.zip from despair to get rid of qualcomm´s/google´s boost

To enable Input boost in the CPU Tab in EXKM

I also implemented a new governor. You can find information about it in the second post. The governor is made with efficiency in mind. the scaling is really great however schedutil is a tiny bit smoother but not as efficient, so it is up to you. Governor is called energy-dcfc (Dynamic Capacity and Frequency Capping)

Changelog for 0.13

- Implemented CPU_Input_Boost by sultanxda <--- disabled by default, if you experience scrolling lag activate it in EXKM, CPU Tab

- Implemented a new sched governor called energy-dcfc (Dynamic Capacity and Frequency Capping), more information in second and third post

- Some adjustements for schedutil

- Updated helix_schedutil

- some improvements to alucardsched and darknesssched

- adjusted WALT to final parameters

- bumped up and improved BFQ, thanks [MENTION=5169465]DespairFactor[/MENTION] <-- new default

- introduced Maple I/O scheduler

- updated sdcardfs

- please check this post prior to flashing: https://xdaforums.com/showpost.php?p=71502126&postcount=241

Please test, try everything and report back :) Thank you guys and girls.

As always there will be an oc and a nonoc version.

Downloads:

OC: https://www.androidfilehost.com/?fid=817550096634757912

NONOC: https://www.androidfilehost.com/?fid=745425885120719943
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
I forgot to add. 0.13 with schedutil, cpu input boost and schedtunenohint is extremely smooth for me.

You can also try to set the governor for one cluster to energy dcfc.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] biggiesmalls657:
How can I tell before flashing the zip if my CPU can handle the over clock part. I know on my Nexus 6 there was a code that would tell me what it can do.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Ofthecats:
No way. Trial and error.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
Updated the third post with some information on how to gather logs
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] 水攸月羽:
Same issue here, happened 4 times since 0.12 but never happen before 0.11. Seems like it failed to wake up because it happened at the moment I want to unlock phone or the moment of the first alarm at morning. I did a clean install without any mod, just PN+kiri(nonOC)+root.

Will try to grab a log next time if it reboot again.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] CHANGiism:
Attached are all the logs plus console-ramoops as instructed in your third post. I had a reboot while on a call, and I am on 0.13 nonOC.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Alcolawl:
Got two more reboots today. One while using the fingerprint scanner to wake the phone and one took place while it was just sitting idle on my desk. Took a shower, came back, and checked my phone to notice that I had to enter my PIN due to a reboot. :/

Running 0.13 OC. Logs attached and named appropriately.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DaveHTC200:
Hopefully the reboot issue can be addressed in time, as with the new energy gov I'm finding the battery life is in my usage amazing!!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DaveHTC200:
I have tried this since going away from root! However it even then still will not boot for reference :svetius:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
could you guys please tell me your exact configuration?

Like ROM, build date of the rom, tweaks mods etc flashed?

selinux permissive/enforcing?

it could be something that my be caused by the rom but I am not sure. I am running a self compiled DU from 30 march and did not have a reboot since flashing it. Please gather logs if you get more reboots, I might catch it.

I also have a test version, I will upload it in a bit. it might adress an error I found in the logs but I am not sure if this caused the reboots.

It will be in the testing folder located here: https://www.androidfilehost.com/?w=files&flid=163259
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
Test kernel Uploaded

Test kernels are up. Look one post above for the test folder link.

thank you for reporting back :)

edit: don´t hesitate to flash the test kernel. It can only be more stable than before. :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DaveHTC200:
Personally i was on stock B version of 7.1.1 with no adjustments aside from the energy gov, however i only noticed one reboot whilst it was sat doing nothing.

Is there any chance you can look at being able to flash without SU please?

Many thanks!!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DR3W5K1:
Has anyone been able to pass safety net with this?Im running du stock because I get cts profile mismatch when I tried. I really want to use this instead.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Alcolawl:
I'll flash the test version right now and report back if I get any other Random Reboots.

My Exact Configuration:

ROM: Stock (NOF27B)

CPU

CPU Governor (little): Schedutil

CPU Governor (big): Energy-dcfc

Input Boost: Enabled

Little Cluster Max Freq.: 1593 MHz

Big Cluster Max Freq.: 2246 MHz (Underclocking has not fixed the issue)

Perfd: Enabled

wq_power_saving: Enabled

Graphics

GPU Max Freq.: 652 MHz

GPU Governor: msm-adreno-tz

GPU Initial Frequency: 214 MHz

GPU Boost: Low

Memory

zRAM: Disabled

Dirty Ratio: 20

Dirty Background Ratio: 15

I/O Stuff

I/O Scheduler: Maple

Readahead kb: 1024

TCP Congestion: Westwood

All other settings are default.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
Just to make sure. Sdcardfs enabled?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] -DarkKnight-:
Is the test kernel only for the Pixel XL, because I can't seem to flash it on my Pixel
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] liam_davenport:
Pixel XL only buddy
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Alcolawl:
Yes, I have sdcardfs enabled. Sorry I forgot to mention that.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
Edit the anykernel.sh inside the zip to allow the zip to be flashed on sailfish.