>>107255366
Yeah, CPU governors are a bit of a relic from the early days of mobile Linux (and even desktop power management), but they still have their place if you're chasing marginal gains in battery life or thermal throttling—especially on older hardware or custom ROMs like LineageOS.

Modern CPUs (Intel/AMD on desktops, or Qualcomm/MediaTek on phones) do a shit ton of dynamic scaling out of the box via P-states, C-states, and scheduler tweaks in the kernel. Stuff like `schedutil` governor in recent Linux kernels is pretty smart and adaptive, pulling from hardware telemetry to balance perf vs. power without much user intervention. So for most folks, yeah, the DE's built-in power profiles (e.g., GNOME's balanced/power-saver modes) or Android's adaptive battery modes cover 90% of the use case without diving into sysfs tweaks.

That said, if you're on something like a PinePhone, old Nexus, or just love CLI fiddling, governors can be fun.

I tinker occasionally on my Framework laptop running Fedora—switch to `schedutil` + TLP for workdays, or `powersave` when traveling. Tools like `cpupower` or `stress` help benchmark the delta. What's your setup like, and what battery gains are you hoping for? Worth a shot on conservative; worst case, reboot and laugh it off.

>>107255463
Interesting, thanks for the explanation. My battery life is already quite solid (18-20 hours of SOT, then again I don't have GMS installed). It's also a decently power-efficient chip; Dimensity 6300, 2x A76/6x A55, TSMC N6, yada yada yada.

I'm just an autist when it comes to battery life. My Pixel 6a was basically toast after 300 cycles, don't wanna make that mistake again. I was initially considering disabling the two Cortex-A76s entirely but it just seems too risky. The powersaver governor isn't good because then I'd have cores locked at... 650 MHz. So I just went for conservative since it's aggressive but not ridiculous.

Applied the ADB commands a few minutes ago and verified everything's configured right. I'm actually typing this on my phone right now. So far smooth sailing.

>>107255366
I have a script I run whenever I remember to set everything to "performance" mode.

#!/bin/sh
cpupower frequency-set -gperformance all
x86_energy_perf_policy --all performance

It makes all cores idle at the full turbo frequency instead of 800 MHz, but it doesn't make a huge performance difference.
Setting everything to "powersave" makes a huge difference in battery life and performance though. It'll lock all your cores to 800 MHz, probably doubling your battery or more, and still acceptable performance for browsing the net.

>>107255366
Whats are the most likely reasons that an IC chip for the lightning port on an iPhone 7 would fail? Louis Rossman's site sells them and claims its possibly from faulty third party cables somehow fucking the chip
Some type of dis regulation in the overly complex iOS battery charging system
My problem is a shitty battery that drains stupid quick within 1 - 1:30 hours of heavy use (typically >1:30 w several tabs open video playing while browsing i.e.) unless brightness is low and there is minimal user input so no heavy browsing on the fly unless its tethered to an outlet
Real Pain in the taint

>>107255599
Even better, iOS claims battery is at 100 percent charging capacity even though its been weird af for at least a few years now
Shiver me timbers im not shelling out 1K for new consumer goyslop