Database Info

[Q] Optimum "LOW" setting for performance based overclocking

I am loving my Android experience so far coming from and iPhone 4. I am running LeeDroid and have been playing around a lot with SetCPU. At this time, I am not concerned about battery as of yet. I am asking this question in regard to optimal, blazing fast performance with minimal hiccups.
I have done Quadrant testing at various min/max CPU levels. I had excellent results at 1804 high 904 min. However I had to yank the battery after not being able to unlock the device.
For profiles, real basic, again I am not concerned about battery charge life ATM. I have it set to revert to stock performace (1036/245) if the battery temp reaches 100F.
With the screen locked, I have it set to 499/245. All of my settings are using the "ondemand".
I would like to know what an ideal minimum is for PERFORMANCE as well as ideal max (1804? Highest might not always be fastest?). I got amazing results with Quadrant full benchmark with settings of 1804/499. This also caused a lockup when trying to unlock the device though. Maybe because there was a conflict with my lockscreen max setting? I would think the app would put priority to the lock profile though.
Also, does this phone have a built in CPU temperature sensor that I could utilize with a CPU temp widget?
Thanks for reading my lengthy ramblings.
Ray

Not all Processors are created equal and therefore some can OC to 1900+ and some cant overclock at all. Most will be in between. Sounds like you are over doing it. I clock mine to about 1400 when charging. I have had it to 1700 without an issue at all, but I don't find a need to be faster then 1400. When screen is off I actually tell it to go to 250MHz. Sometimes its alittle slow to "wake". But it saves mucho battery. When just on battery I am running at about 1250. Been this way for about 3 weeks. Not an issue.
I have never had to yank my battery and quite frankly if I did I would never run it that high again. You are going to burn it up running it at that speed. Nothing over 1500 for extended periods. 1800+ for showing off maybe? But that's kinda dumb too.
I have not read about any built in temp thing so can't really answer that.

I don't know what kind of power hungry apps you guys are running, but I run mine underclocked to 906MHz. Snappy as ever.

Thoughts on OverClocking Sensation

Hey guys,
Ive been using SetCPU since it was fixed for the sensation. I am curious about what others have observed as far as battery life and performance goes.
I am running 1.8Ghz with a cpu voltage of 1.265V (1265000uV).
My battery doesnt last all that long despite all the profiles I have in place. I guess thats expected when you overclock by that much, huh? Is it worth it though?
Im sure more of you out there have experience to share. Im not talking Quadrant and benchmark scores, Im talking REAL use!
I am beginning to feel that dropping the frequency down may be in order since I cannot find anything that needs 1.8Ghz to work on this phone. Plus, less frequency means less required voltage. That would mean more battery!
Anyone care to chime in with their overclock frequency + voltage and experience?
Matt

I'm also interested in getting some input from other users, without having to clog up the respective overclocking threads in the Development section.
Yesterday after work, I set up the 1.5Ghz Undervolted option using utking's tool (http://forum.xda-developers.com/showthread.php?t=1168707). I didn't see too much need to push my CPU too hard, and a stable UV always piques my interest.
I created a couple of basic SetCPU profiles (screen off, battery below 20%, temperature < 50C), and scaling on demand up to 1512Mhz, my phone took about another 7-8 hours of moderately heavy use (Navigation, Maps, Yelp, photos, etc.) before it was on its last legs.
Bear in mind that I've been using the Anker 1900mAh battery. But even after the OC-UV that I set up, this was at least as good of battery usage as before without any SetCPU or overclocking, and actually seemed to be a little bit better to be honest.

I just dropped down to 1.6Ghz @ 1.26V...
I couldn't keep my phone from freezing with anything less than 1.26V @ 1.6Ghz. We will see how this goes for a few days and compare to my previous 1.8Ghz @ 1.265V.
So far, speed seems to be FASTER than 1.8Ghz. My Quadrant score (only being used here for comparison reasons) was 2700 right off the bat, whereas 1.8Ghz would peak around 2700-2800 after several tries.
The carousel works much better! I can swipe through quickly and have it scroll with zero lag. I can also fast swipe and watch is spin nicely!
Google Earth and Maps is about the same as 1.8Ghz.
Before, at 1.8Ghz, I could probably get 16 hours out of my phone with VERY LIGHT use. (A few 2min phone calls, check mail throughout the day, check the web a little). I am charging the phone up and will report back later.
Matt

I went down from 1.62 UV to 1.5 UV,because I could not see any difference in general use nad in benchmarks(except Quadrant) and battery consumption is much bigger with 1.62 with exact same profiles on setCpu.I think that this is best compromise between speed and battery life and as far as I know this is native clock speed of 8260 Snapdragon.

mrg02d said:
I just dropped down to 1.6Ghz @ 1.26V...
I couldn't keep my phone from freezing with anything less than 1.26V @ 1.6Ghz. We will see how this goes for a few days and compare to my previous 1.8Ghz @ 1.265V.
So far, speed seems to be FASTER than 1.8Ghz. My Quadrant score (only being used here for comparison reasons) was 2700 right off the bat, whereas 1.8Ghz would peak around 2700-2800 after several tries.
The carousel works much better! I can swipe through quickly and have it scroll with zero lag. I can also fast swipe and watch is spin nicely!
Google Earth and Maps is about the same as 1.8Ghz.
Before, at 1.8Ghz, I could probably get 16 hours out of my phone with VERY LIGHT use. (A few 2min phone calls, check mail throughout the day, check the web a little). I am charging the phone up and will report back later.
Matt
Click to expand...
Click to collapse
How simple is it to temp-root and overclock? I am really only interested in overclocking to speed up Sense, and you said it performs better with a speed boost.
Sent from my HTC Sensation 4G using XDA Premium App

Very,very easy,just read this tread :http://forum.xda-developers.com/showthread.php?t=1168707

I have mine undervolted at VDD_1175000 and 1500MHz. I like it very much...makes a big difference in quadarant score, but not sure in reality how much faster. Battery life is fine (when the phone is on). Have not experiened FC's
I have modified eugenes batch file to push my kernel file and preferred speed after perma-temp-root and now is all in one click...

So here is a little update:
Its been about 8 hours since full charge and I am at 55% battery left.
1.6Ghz @ 1.26V, On Demand.
Ive been checking email, making a few calls, and surfing the net with both wifi and GPRS (was out of the network, away from 4G). I also played Angry birds for a little bit and showed off Google Maps and Earth to my Mom.
Now that Im back home, ive turned back on 4G...
Ive noticed a slight amount of hesitation while opening and closing things, but nothing bad.
I havent had any profiles kick in yet, but they will soon with the battery getting low. I will resist charging the phone and see if I make it through the night, using it as I need it. I will report tomorrow.
Matt

I must be doing something wrong.
I am rooted and running LeeDriods 1.2 Rom. When I launch setcpu the only options i have are 1000 mghz? WTF am i doing wrong?

i think at LeeDroid 1.2 you must not use setcpu but Demon control?

BigBoppa said:
i think at LeeDroid 1.2 you must not use setcpu but Demon control?
Click to expand...
Click to collapse
Hmmm, okay. I saw where set cpu was updated for the sensation in the latest release but it doesn't seem to support overclocking with this rom.

Shame that as i was about to get that rom and flash it onto my phone, glad i came in here now
Running Leedroid 1.0
Kernel @ 1.7ghz max, i have it set to 1.5ghz and 192mhz
Runs hot when i play finger racing or reckless racing or modern combat 2 or something intensive, but besides the heat, it drains just like it normally would to be honest, maybe a little quicker, definite speed increase in overall user experience, without an OC the rom just flops, better than stock but just crap, OC is needed.

CPU Freq: How do you keep yours?

This is a question I've never seen asked, but it's an important one. What are you phones CPU Freqs? What Govs do they have, and what Profiles do you use?
Rom: PyroIce
Main: 192 Min, 918 Max. OnDemand.
Screen Off: 192 Min, 384 Max. PowerSave.
InCall: 192 Min, 540 Max. Interactive.
Time 11pm-7am: 192Min/Max Powersave.
Sent from my HTC myTouch_4G_Slide using Tapatalk

that's cool, i might start using profiles again. from fiddling around i've noticed the difference between the ondemand and conservative governors- with ondemand, the processor seems to go from min. to all the way to max. and back down to min, and doesn't use the middle frequencies as much, while on conservative, the processor doesn't shoot up to max. as easily and seems to meander thru the middle frequencies a lot more. it makes sense too, because i've noticed that the phone seems snappier with ondemand.
i noticed you're using some of the others... i'll have to check them out as well.

ondemand
Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed. - SetCPU website
conservative
Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery. - SetCPU website
performance
Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking. - SetCPU website
powersave
Available in some kernels. It will keep the CPU running at the "min" set value at all times. - SetCPU website
userspace
A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor. - SetCPU website
Interactive
The 'interactive' governor has a different approach. Instead of sampling the cpu
at a specified rate, the governor will scale the cpu frequency up when coming
out of idle. When the cpu comes out of idle, a timer is configured to fire
within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer
fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the
last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down
to

so, I bought set cpu about 3 phones ago, but I never really saw a differnence, can it be used with the stock kernel?

yellowjacket1981 said:
so, I bought set cpu about 3 phones ago, but I never really saw a differnence, can it be used with the stock kernel?
Click to expand...
Click to collapse
Yeah Plus there's a huge difference with the Battery. I you use my CPU Settings, you should gain 3 hours Min on your phone. Also dropping the CPU in call is great, helps for longer calls and less overheating. If your S-Off you should use a custom kernel. UV Kernels are great.

AgentCherryColla said:
Yeah Plus there's a huge difference with the Battery. I you use my CPU Settings, you should gain 3 hours Min on your phone. Also dropping the CPU in call is great, helps for longer calls and less overheating. If your S-Off you should use a custom kernel. UV Kernels are great.
Click to expand...
Click to collapse
I actually just got an uv kernel, I am about to flash it, I will use your settings too, thanks.

yellowjacket1981 said:
I actually just got an uv kernel, I am about to flash it, I will use your settings too, thanks.
Click to expand...
Click to collapse
If you run a Sense 3.6 Rom, boost the CPU to 1Ghz. 918Mhz Lags.
Sent from my HTC myTouch_4G_Slide using Tapatalk

yellowjacket1981 said:
so, I bought set cpu about 3 phones ago, but I never really saw a differnence, can it be used with the stock kernel?
Click to expand...
Click to collapse
Yes.
You cannot use anything the kernel doesn't already serve as an option, though.
SetCPU doesn't create options - it allows you user-level access to the ones already existing.
Normally you have no control over your clock speed but with it you can...say... limit the maximum clock speed to only be two-thirds of the stock speed.
Since it doesn't ramp up all the way, it doesn't drain as much power.
If you are playing games and stuff that needs a lot of resources, then the slower clock speeds cost you battery since it takes more effort to get the same work done. But if you don't do much with your phone, and don't need a lot of high-end CPU ability, why let it run flat out?
You can also set it to be like that only sometimes, and maximize battery savings by telling your device to chill out when it doesn't have to be awesome.
Now, if you get into custom kernels where you or a dev has opened up more options, SetCPU will again give you user level control over them.
Especially once you get into overclocking beyond manufacturer(s) recommendations, not having some end-user level control over the processor like this is irresponsible.
If you think I run a 1.7 or 1.9 or 1.5+anything on the device flat-out balls-to-the-wall all the time, I would ask you if you drive your car with the gas pedal smashed to the floor all the time. (it's a fitting analogy)
No, again, that would be irresponsible abuse of the hardware for no good reason.
If not SetCPU, then there would be something else to use, but SetCPU is a great interface that not only works well but is maintaned within the XDA community by a member here.
I will always go for the XDA community member version of any app first - it's usually a problem solved from a perspective very near the way I am perceiving the issue, supports the community, and is always easier to find help on if necessary.
What's even cooler is SetCPU is given away free by the dev to XDA members.
I did go ahead and buy it anyway to support the dev. It is a fantastic tool at my disposal, and I have come to realize just how much time and energy goes into making this kind of stuff.
Beyond all that, though, there are a ton of crap apps and software out there slapped together by people who don't care or didn't put the right level of effort into their work. When I find something that actually works and works well after sifting through a sea of garbage, if there is a paid version of the app i'll usually buy it not only as a thank you but also to encourage that particular person to keep working. They - unlike many, many others (in my opinion) earned it.
I know i'm drifting off topic a bit, sorry for that - I just really appreciate quality work and SetCPU falls in with that crowd nicely.
Even without a custom kernel providing options beyond stock, there is still a lot of value this app can hold for anyone with root level access to their device.

Blue6IX said:
If you are playing games and stuff that needs a lot of resources, then the slower clock speeds cost you battery since it takes more effort to get the same work done.
Click to expand...
Click to collapse
Is this true? in my mind, I feel like it will take longer/not be as smooth, but wouldn't necessarily be worse for battery than a higher clock speed.

On a one-for-one comparison it leans more towards an even playing field, until you add that it's a dual-core processor and it very heavily skews the results towards less battery at higher clock speeds for complex operations.
Faster CPU speeds process the actions more quickly, and when you have to crunch a lot of numbers real quick like you do for most games the higher clock speed (especially on the dual core we are using) will complete the act with less power used. It is able to keep up with and/or outpace the flow of data being thrown at it.
If you are just using a notepad or browsing some forums maybe...sending a few texts? Then the higher clock speeds show a negative return on battery usage - you don't need it and it's wasteful.
But when the data has to stay buffered because the CPU is taking it's time working with it, not only is there more electricity consumed by keeping the processor alive longer but also the juice spent on keeping the data buffered.
The data computed is the same data computed at any speed (unless you lose data along the way...) but the power spent on completing that operation is not equal - not by a long shot.
On single core older processors where you are talking about a couple hundred megahertz one way or another the equation is much different, significantly diminshed returns on electricity invested, but with higher quality and multi-core processors especially they can cut through the data with significant ease when sufficiently powered.
But this is on processor intensive activities, and gaming is the first thing that comes to mind. For most other use of the device it's worth underclocking it and you will see battery gains.

[Q] Screen doesn't turn on

I am having some screen issues with my doubleshot. Basically my screen would not turn on but I know everything still works. I am able to listen to music, pick up calls, unlock the phone, etc.
It seems to happen randomly. Pressing the middle button or the power button only makes the buttons glow but doesn't turn on the screen.
Pulling out the battery and forcing the phone to restart solves the problem. Is there a solution or a more graceful way of getting the screen to come back on?
Edit:
Forgot to mention that it happens to my on JellyBean DS and KitKat DS by Emmanuel U.
Was using CM 9.1 by scverhagen and the issue doesn't happen as often. Once a week where has the JB and KK happens atleast once a day.

I have the same problem too. For awhile thought it was to an app I moved to sd card (walgreens). Wasn't as often moving app off sd card.
Sent from my MyTouch 4G Slide using Tapatalk

m3gz said:
I am having some screen issues with my doubleshot. Basically my screen would not turn on but I know everything still works. I am able to listen to music, pick up calls, unlock the phone, etc.
It seems to happen randomly. Pressing the middle button or the power button only makes the buttons glow but doesn't turn on the screen.
Pulling out the battery and forcing the phone to restart solves the problem. Is there a solution or a more graceful way of getting the screen to come back on?
Edit:
Forgot to mention that it happens to my on JellyBean DS and KitKat DS by Emmanuel U.
Was using CM 9.1 by scverhagen and the issue doesn't happen as often. Once a week where has the JB and KK happens atleast once a day.
Click to expand...
Click to collapse
I've seen this happen as well with various roms as well (including 9.1). I currently am using tbalden's 10.1, and haven't seen it in forever. I don't know if he fixed it, or I've just been lucky.

I have a feeling that it might be the minimum frequency processor settings. The default settings that Emmanuel set seem pretty aggressive.
I am going to:
increase my minimum frequency to 540MHz (and incrementally lower it until it becomes unstable)
keep my maximum frequency at 1512 MHz
set CPU governor to ONDEMAND
Battery shouldn't be too much of a problem for me since I upgraded to 3500 mAh.
daswerk, have you tried playing around with your processor settings?

m3gz said:
I have a feeling that it might be the minimum frequency processor settings. The default settings that Emmanuel set seem pretty aggressive.
I am going to:
increase my minimum frequency to 540MHz (and incrementally lower it until it becomes unstable)
keep my maximum frequency at 1512 MHz
set CPU governor to ONDEMAND
Battery shouldn't be too much of a problem for me since I upgraded to 3500 mAh.
daswerk, have you tried playing around with your processor settings?
Click to expand...
Click to collapse
540 minimum sounds a bit high to me unless your phone wasn't stable on stock ROM either. Maybe try 192? You could also try lowering your max to the stock 1.2ghz

I keep mine at 1512 too. Low at 192, going to try 384 for a bit. I have not had the problem for awhile though.
Sent from my MyTouch 4G Slide using Tapatalk

Ziida said:
540 minimum sounds a bit high to me unless your phone wasn't stable on stock ROM either. Maybe try 192? You could also try lowering your max to the stock 1.2ghz
Click to expand...
Click to collapse
Thanks for the advice.
I remember having my max frequency at 1512 MHz before so I thought that wasn't a problem.
So far 540 MHz minimum has kept my phone from going blank. I'll try 192 Mhz next

I've tried to set 192 Mhz as a minimum rate - and got black screen anyway.

Saem persun said:
I've tried to set 192 Mhz as a minimum rate - and got black screen anyway.
Click to expand...
Click to collapse
192 MHz worked for me. You can try doing something extreme like what I did to see if it's the minimum frequency. It may decrease battery a bit but it's better than having the annoying black screen. I tried 540MHz as a test frequency.
Not all processors are the equal. So what may work for some may not work for others.

Same problem here. Black screen on Doubleshot with CM 10.1. Made me really concerned when it happened, as I was was reading the hardware maintenance thread earlier today (for fun) so I thought the LCD went.
This is the first time this has happened in the three weeks I had this phone, and I've been on 10.1 for almost a week now.
Because battery life[1] is an issue for me as well, I edged things up only slightly (from 96 MHz to 128), hopefully that will do to the trick. If not, I will try 192 MHz.
[1] Speaking of which, any tricks on keeping battery usage low? I use Deep Sleep Battery Saver which helps out a lot. And I'm selective about my apps (removed Songza because it was hanging around while closed, eating up battery life). GPS stays off, although I keep Wi-Fi and 3G on. It looks like the screen becomes the biggest draw at this point. Any advice would be appreciated.

Since the problem in March, I have upped the minimum frequency to 192mHz. For the longest while I haven't had any issues.
But since I installed my new Anker battery (was on a half-in-the-bag EZO Power 1900mAh), the problem came back, happened twice now, a week apart.
I'm trialing KitKatDS right now, but will probably go back in a week or less due to wakelock (Android OS) issues. Judging by above, when I do I will bump up the minimum even higher. Hard to see the correlation with how the battery will be causing it, but I see no other change.

Upping the lower end frequency seemed to work for a bit but i'm still getting the screen issues. I'm using a 3500mAh battery from China but I'm just doubting that the battery affects the screen.
The correlation of frequency to screen issues could also be coincidental.

m3gz said:
The correlation of frequency to screen issues could also be coincidental.
Click to expand...
Click to collapse
I wonder if the scheduler has anything to do with screen as well, that is, if CM uses a different one from stock?
Sent from my MyTouch 4G Slide using XDA Free mobile app

Moto X Pure Battery Performance and Replacement

So my Moto X Pure only gets around 5 hours SOT and around 2-3 hours playing games. I seen a 3200 mAh battery replacement on Amazon and I'm wondering if anyone has tried it? I'm using the Resurrection Remix OS with my CPU set to power save in the battery options. Please post your battery stats and ROM information so I can see if my phone would benefit from a battery change.

Hybrid Theory said:
So my Moto X Pure only gets around 5 hours SOT and around 2-3 hours playing games. I seen a 3200 mAh battery replacement on Amazon and I'm wondering if anyone has tried it? I'm using the Resurrection Remix OS with my CPU set to power save in the battery options. Please post your battery stats and ROM information so I can see if my phone would benefit from a battery change.
Click to expand...
Click to collapse
LoL... With your SOT and game times, your battery is holding up pretty well. I would not expect much of an increase from any battery replacement you may get.
Regarding batteries from Amazon, be wary-especially of those claiming more mAh. Typically higher mAh means a larger battery so be skeptical. Based on what I have read in forums and reviews, it seems many of the batteries for this phone from Amazon, regardless of advertised mAh, have been hit or miss. Some manage to do well for 3 to 6 months then problems start.

aybarrap1 said:
LoL... With your SOT and game times, your battery is holding up pretty well. I would not expect much of an increase from any battery replacement you may get.
Regarding batteries from Amazon, be wary-especially of those claiming more mAh. Typically higher mAh means a larger battery so be skeptical. Based on what I have read in forums and reviews, it seems many of the batteries for this phone from Amazon, regardless of advertised mAh, have been hit or miss. Some manage to do well for 3 to 6 months then problems start.
Click to expand...
Click to collapse
I lowered my GPU frequency to 300 MHz that seemed to help a lot especially when playing games my battery doesn't drain as fast. I even lowered my screen resolution to 720p and set my GPU frequency to 180 MHz. The OS is smooth but when I start playing some 3D games you can definitely notice FPS drop so I put it back at 300 MHz. I couldn't increase my battery by lowering my CPU frequency for some reason my battery life seems worse when I try to mess with the CPU. The only thing I managed to do was disable my big cores in kernel auditor when they aren't needed and setting my low memory killer to aggressive in kernel auditor seemed to help my battery as well. That's just my personal experience hopefully someone will get something out of it.

Hybrid Theory said:
I lowered my GPU frequency to 300 MHz that seemed to help a lot especially when playing games my battery doesn't drain as fast. I even lowered my screen resolution to 720p and set my GPU frequency to 180 MHz. The OS is smooth but when I start playing some 3D games you can definitely notice FPS drop so I put it back at 300 MHz. I couldn't increase my battery by lowering my CPU frequency for some reason my battery life seems worse when I try to mess with the CPU. The only thing I managed to do was disable my big cores in kernel auditor when they aren't needed and setting my low memory killer to aggressive in kernel auditor seemed to help my battery as well. That's just my personal experience hopefully someone will get something out of it.
Click to expand...
Click to collapse
The CPU for the most part does pretty well scaling up and down based off processing needs. You probably just don't have CPU intensive apps so didn't notice much. You notice the GPU while playing games though. I think for the most part setting to a lower resolution might help with games at lower frequencies on the GPU in terms of maintaining higher fps at lower frequencies, but a 5.5 2K screen with simulated 720p probably doesn't net much battery life in other usage areas.

aybarrap1 said:
The CPU for the most part does pretty well scaling up and down based off processing needs. You probably just don't have CPU intensive apps so didn't notice much. You notice the GPU while playing games though. I think for the most part setting to a lower resolution might help with games at lower frequencies on the GPU in terms of maintaining higher fps at lower frequencies, but a 5.5 2K screen with simulated 720p probably doesn't net much battery life in other usage areas.
Click to expand...
Click to collapse
Right I am able to keep my GPU on power save and it'll sit on 180 MHz and the OS is still smooth on 720p if I bump it up to 1080p I'll have to put the frequency at 300 MHz or else it'll lag. I noticed when I move through the OS the GPU will jump to unnecessary frequencies like 300 MHz or even 450 MHz. Keeping it locked to 180 MHz while using Firefox or watching YouTube helped a little bit. The main problem for me is the lack of kernels to choose from. I used this tutorial https://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557 to tune my CPU governor since the Nexus 5X has the same SOC but my rom Remix OS has a feature called CPU boost that I can't turn off unless I flash another kernel. The problem with the Moto X Pure is that it doesn't have many custom kernels. I managed to find one that works with my rom but the camera doesn't work. I could simply go to another rom but they lack the customization Remix has and some of them have SeLinux set to permissive and I don't really feel like dealing with escalation attacks and having my bank information stolen.

Hybrid Theory said:
Right I am able to keep my GPU on power save and it'll sit on 180 MHz and the OS is still smooth on 720p if I bump it up to 1080p I'll have to put the frequency at 300 MHz or else it'll lag. I noticed when I move through the OS the GPU will jump to unnecessary frequencies like 300 MHz or even 450 MHz. Keeping it locked to 180 MHz while using Firefox or watching YouTube helped a little bit. The main problem for me is the lack of kernels to choose from. I used this tutorial https://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557 to tune my CPU governor since the Nexus 5X has the same SOC but my rom Remix OS has a feature called CPU boost that I can't turn off unless I flash another kernel. The problem with the Moto X Pure is that it doesn't have many custom kernels. I managed to find one that works with my rom but the camera doesn't work. I could simply go to another rom but they lack the customization Remix has and some of them have SeLinux set to permissive and I don't really feel like dealing with escalation attacks and having my bank information stolen.
Click to expand...
Click to collapse
Wow. Since I first got the phone 3 years ago, i personally just have had very little time to delve much into doing custom ROMs and kernels for this device due to work scheduling I'm moving to a new job this month and should have more time on my hands. I'm probably going to get back into things.

aybarrap1 said:
Wow. Since I first got the phone 3 years ago, i personally just have had very little time to delve much into doing custom ROMs and kernels for this device due to work scheduling I'm moving to a new job this month and should have more time on my hands. I'm probably going to get back into things.
Click to expand...
Click to collapse
I'd compile a kernel for lineage based roms with the nougat modem but I'm not that smart I don't even have a computer to do it with lol.

So I went ahead and installed the EX Kernel Manager app and I downloaded the Hawktail governor profile. After doing that my battery went from 2-3 hours SOT to 4-6 SOT from 100%. When I play slither.io on the default CPU setup my battery would drop 10% every 10-15 minutes. With the Hawktail profile it drops 10% every 30-40 minutes. I thought this was incredible because NFC and Bluetooth was still on. I also found that the Alucard CPU governor gave me similar results during my observations. I really hope somebody else can benefit from this thread.
Here is the download link https://androidfilehost.com/?fid=24686679545610694
Remove the .txt extension and put it on your micro SD card or in the ElementalX folder. From the Ex Kernel Manager app go to CPU>Governor Options>Load then load the HawkTail file then click apply on boot.