Database Users

oc'd phone heating up during normal use and poor battery life

Well ill start off by saying I'm new here and this is my first post. I'm also very new to this stuff and have a lot to learn. A buddy of mine recently rooted and overclocked my phone using the sense 2.6.32.21 1.5ghz oc/uv kernel. I currently have it set to 1.19 max 768 min and am experiencing temps above 107 running emulators and just web browsing.. I am also seeing pretty poor batt life even using battery booster and advanced task killer.. any help is greatly appreciated!

Battery apps and task killers tend to have the opposite of their intended effect on battery. Android has a built in utility to watch battery usage, why do you need a 3rd party one? Also do some reading on task killers, you will see why they are unnecessary on Android. I've stopped using one and my phone runs faster and more stable than before.

768 min is VERY high. Might explain the heating and battery life drain quite a bit.
Try this for me, please. Set your governor to interactive and drop your min down to 245. Run that for a whole charge. You may be surprised.
Sent from my PG06100
Also, I second the post above me. Advanced Task Killer and anything like it ultimately cause more harm than good. Battery apps, such as Juice Defender, also shouldn't be necessary. Although, it is YOUR phone.

Thanks a lot for the replys. I set the min to 245 and am seeing serious changes in temps. I also uninstalled atk but installed appkik. I am also still running battery booster but may get rid of it soon.. I feel like this phone should have better batt life. Any suggestions?

bearsblack said:
Thanks a lot for the replys. I set the min to 245 and am seeing serious changes in temps. I also uninstalled atk but installed appkik. I am also still running battery booster but may get rid of it soon.. I feel like this phone should have better batt life. Any suggestions?
Click to expand...
Click to collapse
well they gave some suggestions. which it seems you dont want to listen to. you dont need task killers of any kind

Sorry I'm stubborn. Uninstalling now

No disrespect here, but seriously, if you don't know what and why you're overclocking, don't know the inherent risks, etc, why are you doing it?

Compusmurf said:
No disrespect here, but seriously, if you don't know what and why you're overclocking, don't know the inherent risks, etc, why are you doing it?
Click to expand...
Click to collapse
because all the cool kids are doing it smurf...duh.
But seriously, min. should not be set at anything greater then 245. Only use performance if you are benchmarking. Default at the moment should be interactive.

Just gonna add my 2 cents in from personal observation....after doing some reading on overlooking and stuff I've noticed when going into the different ## modes, the shift usually drops its processor cycles to pretty low numbers in the 200-300 mhz range when its just in standby or not doing anything...it only kicks it up when you need the power. So the heating up is probably caused by constantly running at what used to be its max territory...PLUS youre going above and beyond the original limits/specs at a constant so it never gets to relax even when the phone is idle...I hope that makes sense. So as one poster mentioned keep the min at the stock setting and if you really want to/need to then raise the max mhz to whatever your phone can handle reliably. Correct me if I'm wrong anyone who is more into the overlooked setups. Me personally, stock has been able to keep up with whatever I have thrown at it after 30 days and still getting 25+hrs on one charge.
Sent from my PG06100 using XDA App

I currently have it governed at 245 max screen off. Running 1.2ghz max interactive with no task killers or batt savers. Batt life seems to be somewhat better but temps still creep past 105. Thanks a lot for the info

alittle off of the beaten path, but i tried runing 245/1801 interactive on evervolv and noticed alot of random reboots. set it back at on demand and am having good luck with that. why is everyone leaning towards interactive??

Excuse me if I am wrong it's early and im too lazy to reread up on it but I believe the difference is with on demand there is a slight delay(second or two) and it gradually kicks up to where it needs to be where is interactive is a spike the second you need it...

JAREDR said:
alittle off of the beaten path, but i tried runing 245/1801 interactive on evervolv and noticed alot of random reboots. set it back at on demand and am having good luck with that. why is everyone leaning towards interactive??
Click to expand...
Click to collapse
Interactive is, usually, a lot better for battery life.
If you look at your cpu's scaling history when on the two, TYPICALLY, you'll see a whole lot more time in higher frequencies using ondemand.
That's not to say, however, that with some devices and some kernels they will act the same.
Sent from my HTC Speedy

SetCPU vs. CMSettings Built-in CPU manager

For those of you on CM7 (preferably RC2 or later nightlies), are you using SetCPU or the built in CMSettings CPU manager? Which is giving you better performance/battery life?
I can't help but think that the built in CM Settings CPU tuner is going to be conflicting with my SetCPU profiles.
Been using nightlies since #30 or so, and I currently run SetCPU with a normal profile, a screen off profile, and a profile for <10% battery and haven't touched CMSettings' CPU manager.
I'm contemplating just uninstalling SetCPU for a day or two and seeing what a 1017max / 245min Ondemand or Powersave governor via CMSettings ends up doing to my battery life considering there will be no screen off profile.
Any thoughts?

I dumped setCPU after a lot of testing (and even bought it on market)
I'm finding I'm much happier using inbuilt CPU settings. I think battery life is the same but performance is better due to the fact that SetCPU would sometimes get stuck in my screen-off profile when turned on causing the phone to be really slow.
I recomend uninstalling setCPU, set your ONDEMAND governor with ~1Ghz and run it... You'll find your battery about the same but much less hassle.

I have yet to try that, I somewhat feel obligated to use SetCPU since I purchased it lol. But it probably won't be the last time I waste money at the market.

Neither. CPU tuner works best for me.
Sent from my HTC Vision using XDA Premium App

Utorrent76 said:
Neither. CPU tuner works best for me.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
its the same thing :facepalm:
Try the inbuilt one... I think its way easier

I've been wondering about this too. I don't quite understand how it works. Can I just set the frequency higher till a certain point without changing the voltage and get the same battery life?
What's the best way of doing this? Just change the clock speed or do I need to change something else or update the kernel?

Whatever you tell SetCPU to do, you'll see the same settings mirrored in the CM settings.

I say setCPU cuz as battery gets lower... I have my CPU speed lower also. Basically, 15% battery lasts me forever :] lol
Sent from my T-Mobile G2

DJAeroX26 said:
I say setCPU cuz as battery gets lower... I have my CPU speed lower also. Basically, 15% battery lasts me forever :] lol
Sent from my T-Mobile G2
Click to expand...
Click to collapse
Definitely. This is the one thing I like about SetCPU is having the 10% and 5% profiles so that I can get the last few % to last forever if I need it. Although in normal day-to-day use I'm never pushing it below 20%.

ScooterG said:
Whatever you tell SetCPU to do, you'll see the same settings mirrored in the CM settings.
Click to expand...
Click to collapse
Yea I see this, as far as the governor changing etc.. This is why I'm wondering if it would be easier on my phone to just run only the CM Settings one.
I notice that every 5th or so time I unlock the phone, there is an obvious lag switching from the screen off profile, and my unlock sliders jitter around and it takes 4-5 tries to unlock the phone. I think this is probably partially due to both settings switching over trying to change.
I think I might try backing up and uninstalling SetCPU for tomorrow to see how it goes.

colonelcack said:
I've been wondering about this too. I don't quite understand how it works. Can I just set the frequency higher till a certain point without changing the voltage and get the same battery life?
What's the best way of doing this? Just change the clock speed or do I need to change something else or update the kernel?
Click to expand...
Click to collapse
I've read on here that overclocking the Vision's CPU up to 1 GHz requires no over-volting, and in theory should not affect battery life (but not sure exactly where that information originates from). But there has been lots of debate on these forums on whether the SetCPU app helps or hurts battery life depending on screen-off profiles (underclocking to save battery) or its constant polling of the CPU clock (possibly killing the battery faster).
A kernel that supports overclocking is already part of the CM ROM. If you are on CM, you can just adjust the clock speed under Settings>CM Settings>Performance>CPU settings. Or set the CPU clock using an app like SetCPU. Choosing one method over the other is what is being asked/debated here. If you are on the stock ROM, you need to be rooted, flash a custom kernel that supports overclocking, then install an app such as SetCPU or CPU Tuner to set the CPU clock to your liking.

redpoint73 said:
I've read on here that overclocking the Vision's CPU up to 1 GHz requires no over-volting, and in theory should not affect battery life (but not sure exactly where that information originates from). But there has been lots of debate on these forums on whether the SetCPU app helps or hurts battery life depending on screen-off profiles (underclocking to save battery) or its constant polling of the CPU clock (possibly killing the battery faster).
A kernel that supports overclocking is already part of the CM ROM. If you are on CM, you can just adjust the clock speed under Settings>CM Settings>Performance>CPU settings. Or set the CPU clock using an app like SetCPU. Choosing one method over the other is what is being asked/debated here. If you are on the stock ROM, you need to be rooted, flash a custom kernel that supports overclocking, then install an app such as SetCPU or CPU Tuner to set the CPU clock to your liking.
Click to expand...
Click to collapse
I'm not sure about CM's kernel with the over-volting but I do know that Pershoots kernel can be overclocked to 979mhz without over-volting (Pershoot told me himself).

At 1.8Ghz, I find the temp settings in SetCPU very useful.
Vision rooted, booted and scooted

Daughain said:
At 1.8Ghz, I find the temp settings in SetCPU very useful.
Vision rooted, booted and scooted
Click to expand...
Click to collapse
Well obviously.... But why the hell would you ever need to be running at 1.8ghz? The fact that you are always using a temp-specific profile method should show you that consistent 1.8ghz isn't good for the phone...

Okay so I uninstalled SetCPU last night and I'm going to run just the CM Settings CPU manager all day to see how it goes. Running like this:
ONDEMAND governor
Min CPU: 245 mhz
Max CPU: 1017 mhz
On nightly #19 also.
Okay so its midnight almost, and I'm at 13hrs unplugged and 52% battery still. Pretty general/light use, phone is just as snappy and the lack of a screen off profile doesn't seem to effect battery at all. Liking it so far! very interesting to see the screen off profile not mattering much.

SetCPU for me. I like to have a temperature and charging profile, to prevent the phone from overheating. Even at 1ghz the possibility exists, nice to have a backup incase.

I'm thinking set cpu conflicting with the cm built in caused my ****ty running problems. I have not used setcpu since and been good so far
Sent from prison

tackleberry said:
I'm thinking set cpu conflicting with the cm built in caused my ****ty running problems. I have not used setcpu since and been good so far
Sent from prison
Click to expand...
Click to collapse
With multiple tries... If you change the settings on one, it cancels the settings on the other... Maybe it's because you had set on boot enabled on both?

im going to run the CM tuner and uninstall Setcpu and see how it runs. i never thought about this but i do get that lag when i turn my screen on sometimes. im gonna miss having the profiles but ill see how it runs over the coarse of a couple days.

SetCPU app and it's effectiveness? Syndicate Frozen ROM

Hey there, I just a few days ago rooted and flashed the Syndicate Frozen rom and am not getting such good battery life...
I was wondering how big of a difference SetCpu makes on battery life/performance in general? With moderate/heavy use (internet browsing, facebook, email, txt messaging) how much should it improve battery life? am getting around 10hours at the moment with moderately light use... Is there any free alternative app that runs comparatively well?
I guess what I'm really asking is: is it worth it to buy setcpu, and will it make a dramatic difference on my battery life? This Rom is supposed to improve battery life, and I think I read is overclocked to 1.2... Will setcpu let me set this underclocked to 1,0 and then like 800 with screen off, 600 idle? Am new to the android thing [have had my EPIC only around 2 weeks today]
Thanks for any help!

Overclock widget does pretty much the same thing, and you're going to want to set something like
20mhz min 1 or 1.2ghz max
Then 100mhz min 400mhz max for screen off.

You can set the speed to.anything you want. If you want battery to be the best then.set it to 100/1000 on demand. If you emwant performance then 100/1200. Also I don't set profiles cause I was reading somewhere that they aren't good to use on any galaxy phone.
Sent From My Evo Killer!

http://www.setcpu.com/
Nice info read up on it and yes you can set it anyway you want like stated above. I bought mine from the market to support the dev for the hard work involved in making setcpu, dont know if you know but it is free for xda members just search for setcpu. It is only $2.00 well worth the price so please support the dev if you can.

063_XOBX said:
Overclock widget does pretty much the same thing, and you're going to want to set something like
20mhz min 1 or 1.2ghz max
Then 100mhz min 400mhz max for screen off.
Click to expand...
Click to collapse
20Mhz would freeze the phone. :O
I personally like running it @ 100 Mhz when screen is off and 1Ghz when screen is on.

Overstew said:
20Mhz would freeze the phone. :O.......
Click to expand...
Click to collapse
I am pretty sure XOBX meant 200, cause your right 20 is pretty much crawling...

Yep, I meant 200, the damn autocorrect kept changing mhz to Hz and I must've clicked backspace one too many times.

Thanks, so it would make a big difference in battery life?
Sent from my EPIC 4G FROZEN and Syndicated

androikid said:
Thanks, so it would make a big difference in battery life?
Sent from my EPIC 4G FROZEN and Syndicated
Click to expand...
Click to collapse
Don't expect it to magically give you another 4 hours up time. 1 extra hour would be high hopes.

I use SetCPU with the CPU set to 200/1000 and ondemand, and the battery life has improved GREATLY, well worth the $2 to support the Dev, IMO, even though XDA members get it free.

I've abandoned SetCPU and uninstalled it. Unnecessary consumption of system resources.
Same with any other user-space app/widget to control CPU speed scaling.
In the Bonsai ROM, the exact same capability, sans the profiles which I (and most people) don't use anyway, can be achieved by setting clock range and governor in /etc/init.d/24-cpufreq script. I expect that all the other OC kernels, if not every custom kernel, has a similar way to set CPU clock governor.

I have mine set to 100/1200 on demand, and it works well for the demands I put on it. Way low consumption at idle, but when I need something it instantly responds.
I routinely get 16-18 hours off the charger, and put it back on the charger with sometimes as much as 40% remaining, but as always YMMV. A lot of it has to do with the ROM, but I'd say that CPU scaling has realized a tangible gain for me.

dwallersv said:
I've abandoned SetCPU and uninstalled it. Unnecessary consumption of system resources.
Same with any other user-space app/widget to control CPU speed scaling.
In the Bonsai ROM, the exact same capability, sans the profiles which I (and most people) don't use anyway, can be achieved by setting clock range and governor in /etc/init.d/24-cpufreq script. I expect that all the other OC kernels, if not every custom kernel, has a similar way to set CPU clock governor.
Click to expand...
Click to collapse
Talking about Bonsai ROM tweaks on a Syndicate thread would be like me talking about BMW mods on a Honda forum. Either way, I looked around in the system folders and I can't find the 24-cpu file you're talking about. I upgraded yestereday from the 2.1 SyndicateROM to this, and for the first few hours, the ROM itself was definately quicker...I don't know if that's just because I came from 2.1 to 2.2, not to mention all the other 2.2 tweaks. After a few hours, I completely forgot that I could overclock this to 1.2Ghz. Installing SetCPU and bumping it to 1.2Ghz felt like just another jump. System resource consumption aside, it makes the phone all that much quicker while going between screen, apps list, closing apps, etc.
I could care less about battery life because I've learned to always have a charger around me since my days of the Moment, of hell, even my Treo's. I want fast, SetCPU is something I can see the difference in just from turning it on and off and seeing the differences.

Speed and Battery tweaks.

So I've been following this section for months and just got my a2017u 2 weeks ago. I'm rooted with tenfars tool still locked on b20. I've noticed in the last few weeks a tapering off of new and useful info for this phone and would really like to see what and where everyone is with it? LSpeed? Kernel Auditor? Or any tweaks that have helped either performance or battery life!!! Looking for anything to make this already great phone better!!! TIA

I have been using EX Kernel manager to tweak the settings as kernel auditor was not working properly with the big.LITTLE arrangement. I have upped the readahead value and underclocked the cpu to 1036mhz on the little cores and 1401 mhz on the big cores. working still as snappy and getting +2h SOT. I'm a heavy gamer and Asphalt 8 still plays as fluid as before, even better tbh due to less heating.
If you don't like to underclock, you could try these:
http://forum.xda-developers.com/htc-10/development/pnp-tweak-custom-butterfly-ghostpepper-t3431307

+2h? That's really good! I know overclocking can/could/might damage the CPU. Does underclocking have any of the same risks? I'm rooted and unlocked atm. So no warrenty anyway

aPexalpha said:
+2h? That's really good! I know overclocking can/could/might damage the CPU. Does underclocking have any of the same risks? I'm rooted and unlocked atm. So no warrenty anyway
Click to expand...
Click to collapse
Overclocking can't really harm anything. The excess heat might but it would take a long time and really high temps (you couldn't keep the device in your hands). The only thing you risk by overclocking is a system crash. Just reboot, lower the clock values and voilà ! So no, underclocking can't hurt anything. Overvolting however poses a real threat to the integrity of the components. It's quite the same thing as in computers (except for the heat, you don't always realize it's too hot in a computer).
That being said, is overclocking still even possible on smartphones nowadays ? Just for the fun of it because it's not needed in the least on the Axon 7 .
That's impressive results ! Not sure those hours are needed since the battery is doing well with the software power saver but still a good thing to know.

Still any extra sot is welcome. I'm not a gamer, don't really have any apps that truly need the full power of the sd820 so might give it a shot. Greenify does wonders for standby time.
Not sure if the built in 'intelligent country control' does anything tbh

I'm on my phone most of the day whether it be YouTube play music, texts,calls,etc.. I'm just hoping to find a balance between battery and my multitasking ADHD LOL

Nik2424 said:
I have been using EX Kernel manager to tweak the settings as kernel auditor was not working properly with the big.LITTLE arrangement. I have upped the readahead value and underclocked the cpu to 1036mhz on the little cores and 1401 mhz on the big cores. working still as snappy and getting +2h SOT. I'm a heavy gamer and Asphalt 8 still plays as fluid as before, even better tbh due to less heating.
If you don't like to underclock, you could try these:
http://forum.xda-developers.com/htc-10/development/pnp-tweak-custom-butterfly-ghostpepper-t3431307
Click to expand...
Click to collapse
Mine keeps switching back to 'normal' modes with CPU full on. Any idea how to fix that?

aPexalpha said:
Mine keeps switching back to 'normal' modes with CPU full on. Any idea how to fix that?
Click to expand...
Click to collapse
Yup, I had that problem too initially.
First, I made system changes persistent upon reboot by running this command in Terminal emulator(you can also use adb shell):
reboot disemmcwp
Secondly, you have to disable smart power in the quick toggles.
Once this is done, set your new max values, select the arrow next to it to make it applied on every boot and then reboot your device. It should work.
Note: Everytime you open the EX Kernel manager you will see the speeds jump to max for like 1 sec but if you actually check the cpu statistics you'll see that your settings are sticking and the max clock speed was just for everytime you open the app.

The smart power! I forgot that thing controls the CPU.
So that round arrow thing means apply on boot? I selected that, figured it meant something like that.
Cheers!

[OFFICIAL] GlassCannon - Interactive tweak port N5X l G4

Following the advice of @shadowstep and @Davey126 I have created a thread to separate this from the whole Interactive guide thread by @soniCron. This is due to (1) one, the thread is no longer updated for almost a year and (2) two; to explain the tweak, establish baselines/guides for testers and to gather more interested individuals to try it out.
-------------------------------------------
Introducing GlassCannon!​
Description: A sound modification to the famous interactive parameters. Provides the smoothest interface, great performance while bestowing the lowest frequencies available. Ramping up quickly to maximize "inputs" from I/O overheads then immediately ramping down once tasks are done. The perfect balance between lowering down your frequency, and finishing up tasks quickly.
Why Glasscannon? Why not?
Who am I? I came from the hammerhead scene. I have been modding interactive parameters for more than 2 years and owns a community called: Android Battery Community whom has its own fair share of followers but has been quite stagnant for almost a year ever since my hammerhead broke. Though, I have been tweaking things with other devices; LG G4, Samsung Note 6, OPO and other smartphones that I got my hands on. Now I think it's time for me to get into the Nexus 6P scene. And after just literally 2 days after I posted the tweak, there are messages and posts tempting me to port it to N5X and LG G4, and with enough encouragement as well as a promise of testers; I edited the values matching my GlassCannon tweak with the former LG G4 .txt file I have in my desktop and here it is!
The difference? After years of being a paranoid about my battery (literally looking at dashboards, cpu cycles etc. you know, that guy who just tends to not be satisfied about everything) I finally settled down and read a lot of things and made it as my basis. Most tweaks in here uses target load as an optimal way to force cores to stick into lower frequencies but we won't be doing that with GlassCannon. We will be using two underrated tunables: above_hispeed_delay and input_boost. This two underrated tunables are being neglected for years, though some used it quite efficiently; I have yet to see a tweak that maximizes the two tunable's potential. We would be using above_hispeed_delay as a substitute to the unpredictable target_load. Instead of assigning too much within a tunable that we can't even lay our finger on how it works properly, why not let the SoC handle it and assign a delay along with timer_rate so it can run efficiently? And let input_boost jump up here and there to provide quick surge whenever there are tasks running under the hood.
Look under (Version: N5X l G4):
Code:
[COLOR="Gray"]/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor interactive
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 384000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 1440000
/sys/devices/system/cpu/cpu0/cpufreq/interactive/go_hispeed_load 93
/sys/devices/system/cpu/cpu0/cpufreq/interactive/above_hispeed_delay 0 600000:19000 787200:20000 960000:24000 1248000:38000
/sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_rate 50000
/sys/devices/system/cpu/cpu0/cpufreq/interactive/hispeed_freq 600000
/sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_slack 380000
/sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads 29 384000:88 600000:90 787200:92 960000:93 1248000:98
/sys/devices/system/cpu/cpu0/cpufreq/interactive/min_sample_time 60000
/sys/devices/system/cpu/cpu0/cpufreq/interactive/boost 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/align_windows 1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/use_migration_notif 1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/use_sched_load 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/max_freq_hysteresis 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/boostpulse_duration 0
/sys/devices/system/cpu/cpu4/cpufreq/scaling_governor interactive
/sys/devices/system/cpu/cpu4/cpufreq/scaling_min_freq 384000
/sys/devices/system/cpu/cpu4/cpufreq/scaling_max_freq 1824000
/sys/devices/system/cpu/cpu4/cpufreq/interactive/go_hispeed_load 150
/sys/devices/system/cpu/cpu4/cpufreq/interactive/above_hispeed_delay 20000 960000:60000 1248000:30000
/sys/devices/system/cpu/cpu4/cpufreq/interactive/timer_rate 60000
/sys/devices/system/cpu/cpu4/cpufreq/interactive/hispeed_freq 960000
/sys/devices/system/cpu/cpu4/cpufreq/interactive/timer_slack 380000
/sys/devices/system/cpu/cpu4/cpufreq/interactive/target_loads 98
/sys/devices/system/cpu/cpu4/cpufreq/interactive/min_sample_time 60000
/sys/devices/system/cpu/cpu4/cpufreq/interactive/boost 0
/sys/devices/system/cpu/cpu4/cpufreq/interactive/align_windows 1
/sys/devices/system/cpu/cpu4/cpufreq/interactive/use_migration_notif 1
/sys/devices/system/cpu/cpu4/cpufreq/interactive/use_sched_load 0
/sys/devices/system/cpu/cpu4/cpufreq/interactive/max_freq_hysteresis 0
/sys/devices/system/cpu/cpu4/cpufreq/interactive/boostpulse_duration 0
/sys/module/cpu_boost/parameters/input_boost_freq 0:600000 1:600000 2:600000 3:600000 4:960000 5:960000
/sys/module/cpu_boost/parameters/sync_threshold 1248000
/sys/module/cpu_boost/parameters/boost_ms 40
/sys/module/cpu_boost/parameters/migration_load_threshold 15
/sys/module/cpu_boost/parameters/load_based_syncs Y
/sys/module/cpu_boost/parameters/shed_boost_on_input N
/sys/module/cpu_boost/parameters/input_boost_ms 300
/sys/module/cpu_boost/parameters/input_boost_enabled 1
/sys/module/msm_performance/parameters/touchboost 0
/sys/module/msm_thermal/core_control/enabled 0
/sys/module/msm_thermal/parameters/enabled Y[/COLOR]
Explanation:
go_hispeed_load: Anything between 85-94 is average by my tests, it tends to stick to hispeed_load 40-60 which is what I think would be "optimal" for our cat.
above_hispeed_delay: The most important part of our tweak along with input_boost. This should set up the perfect "delay" so cpu cores could adjust and decide before ramping up to higher frequencies. Our frequency set as hispeed from little cluster is 600000.
target_loads: We won't be dwelling much in this. We put a small amount so that our frequency could ramp up if needed and take a pause on frequencies we deemed to be really significant; 600mhz, 672mhz, 960mhz and 12348mhz. Along with hispeed_delay, it should provide low consumption and tend to stick on 384mhz and 600mhz 89% of the time.
timer_slack: Put it to 380000, just trust me.
max_freq_hysteresis: Asking why theres jitters and a bit of stuttering on your screen? this is the culprit. Turn it to 0 and you will be fine as long as you correct the other tunables. This is because hysteresis actually uses "former" frequencies to calculate which frequency would be best to ramp up to next. If you tend to stick to lower frequencies more, with this on then you will be sticking at low frequencies almost forever, which obviously isn't something good.
input_boost: Now, to explain why this is important; there are two things I would like to emphasize. (1) One, this value was made so that under the hood tasks as well as simple bumps to your frequency if there is a notification, sync etc. would be possible. (2) this value is extremely useful to provide that quick boost to complete tasks with ease. The big clusters would have an input_boost of 633000 which was supposed to be the stock mhz. Why? I deemed that the big cluster isn't that necessary unless you are running an extremely graphic heavy game. So tone it down to 384mhz underclocking it and provide input boost to the mhz that was supposed to be the stock frequency, increasing battery life without sacrificing anything.
Will this be updated? NO, NEVER. I am asking myself why does this other "tweaks" update from time to time if there are no kernel parameters that are changing? Aren't all those tweaks supposed to be tested hundreds of times before releasing? Then why change the parameters again? Am I asking too much? Am I fat? NO. Just NO. EXCEPT if there will be changes within the interactive parameters then sure.
Maximal, Minimal and Nominal Frequencies? Not to hurt anyone's heart but I personally think that this is a retardified(if that is in fact a word) version of "I shall say something smart". I don't see the point of determining what the nominal, maximal and minimal frequencies are as we can't even put a finger what they literally mean. This is actually "subjective" and I really find this so called nominal frequencies irrelevant. Please don't hate.
Do note that most of the explanations above were not edited and is still pretty much the same as N6P description because I'm lazy af.
​Credits: @soniCron, @xSilas43, @shadowstep for pointing out the missing timer_slack and input_boost, google for many things to read, this website for music while typing, that website for providing me more things to read, a bucket of fries and two chickens to make me company.
Go ahead and feel free to download the .txt file below and happy tweaking!
======================​A SINCERE THANKS TO EVERYONE WHO TESTED AND PARTICIPATED
Tips Hat​
After many things happening and after more than a month, I am really glad that we have succesfully ported GlassCannon to N5X and LG G4 (or any other device with same cpu structure). I am proud to present to you the fruits of the small labors of both me and the team as well as others behind the scene testing GlassCannon for your devices.
What has been the verdict? Overall, via landslide; the GlassCannon's Beta2.0 has come out on top. I figured and of course realized after the alphatest that people in N5X community complained (though in small dose) about stutters and a small lag in some apps. Most were debunked especially if you are using an online app but I had to wrap around everything and investigate further. Even though I promised that the Beta would be more battery efficient, I adjusted it so that it should provide a much better performance and smoothness without compromising the battery life of our cats. And thus, the verdict is Beta 2.0 *autistic screeching*
Special thanks to: @Curlyfry2121 @shadowstep @crian @spartan268 @IcyGlacial @Lazerlord
Just a headsup, I will be leaving the Alpha below for other people to download if they still want some!
Grab a copy below! Enjoy!​

Official Testers:
@shadowstep N6P
@Lazerlord
@Curlyfry2121
@mesmurized
@@spartan268
@deani77 N6P
@igoorsoouza
@CazeW
Credits to:
Everyone whom are secretly using the GlassCannon profile. To my Kentucky Fried Chicken for keeping me company. @Davey126 for encouragement and other stuffs, @The Flash because you are the fastest man alive, @shadowstep for being a MTG fan, @flar2 for being an awesome developer and supporting this kind of tweaks, @soniCron for starting this and many more. Huge thanks! and I hope this will go on for the better!

Thanks
Sent from my Pixel using Tapatalk

Firefox, Google plus, and Snapchat, with a little Hangouts during school where the data connection is little to none half the day.

Curlyfry2121 said:
Firefox, Google plus, and Snapchat, with a little Hangouts during school where the data connection is little to none half the day.
Click to expand...
Click to collapse
Thanks for the second full cycle *takes notes*
Well thats a huge steep slope we have. I can see where thise battery drains come from and you really have to do something about those. Have you ever considered airplane mode while you are at an area where there's little to no signals? Those red marks should have drained your battery like crazy! At first I was skeptical when you said you have a bad signal lol.
Now about the cpu times etc.:
(1) One, that is pretty much a great cpu stats for both little and big. I can see that it sticks to 600mhz the way I tuned it too. Those little percentage above 600mhz are pretty nice, that means thst they never got stuck in that number for more than 30-40ms (above_hispeed_delay and timer_rate) doing the trick. (2) Two, I can even see the big cluster's cpu5 off, what more can I ask for? (Purely intentional to set a really high ts
Arget_load and go_hispeed_load at lowest frequency to make this happen) this means everythung works fine as intended (the way I tweaked it to be.)
Anyway this is to be expected for light usage. Btw could you please install accubattery for me and turn on "cpu core" on the overlay settings within the app? There should be 6 overlay batteries at your bottom right continuously changing to see cpu frequencies. Now with thst try a full cycle again and note this:
*At what apps does most of the cores get to red (above 3/4)
*In your observation, how long does it stick to yellow (1/2 above) and red frequencies? (Above 3/4)? Please tell in miliseconds e.g. red at 20ms most of the time etc.
You will see what I'm talking about when you install the app
Anyways continue again with a normal full cycle bro and I'll be waiting for the next update!

phantom146 said:
Thanks for the second full cycle *takes notes*
Well thats a huge steep slope we have. I can see where thise battery drains come from and you really have to do something about those. Have you ever considered airplane mode while you are at an area where there's little to no signals? Those red marks should have drained your battery like crazy! At first I was skeptical when you said you have a bad signal lol.
Now about the cpu times etc.:
(1) One, that is pretty much a great cpu stats for both little and big. I can see that it sticks to 600mhz the way I tuned it too. Those little percentage above 600mhz are pretty nice, that means thst they never got stuck in that number for more than 30-40ms (above_hispeed_delay and timer_rate) doing the trick. (2) Two, I can even see the big cluster's cpu5 off, what more can I ask for? (Purely intentional to set a really high ts
Arget_load and go_hispeed_load at lowest frequency to make this happen) this means everythung works fine as intended (the way I tweaked it to be.)
Anyway this is to be expected for light usage. Btw could you please install accubattery for me and turn on "cpu core" on the overlay settings within the app? There should be 6 overlay batteries at your bottom right continuously changing to see cpu frequencies. Now with thst try a full cycle again and note this:
*At what apps does most of the cores get to red (above 3/4)
*In your observation, how long does it stick to yellow (1/2 above) and red frequencies? (Above 3/4)? Please tell in miliseconds e.g. red at 20ms most of the time etc.
You will see what I'm talking about when you install the app
Anyways continue again with a normal full cycle bro and I'll be waiting for the next update!
Click to expand...
Click to collapse
Gotcha! And yeah I did use airplane mode one time but I forgot to today lol. I will install it and I'll follow your instructions for tomorrow's cycle, and yeah now you get what I meant ?

phantom146 said:
Thanks for the second full cycle *takes notes*
Well thats a huge steep slope we have. I can see where thise battery drains come from and you really have to do something about those. Have you ever considered airplane mode while you are at an area where there's little to no signals? Those red marks should have drained your battery like crazy! At first I was skeptical when you said you have a bad signal lol.
Now about the cpu times etc.:
(1) One, that is pretty much a great cpu stats for both little and big. I can see that it sticks to 600mhz the way I tuned it too. Those little percentage above 600mhz are pretty nice, that means thst they never got stuck in that number for more than 30-40ms (above_hispeed_delay and timer_rate) doing the trick. (2) Two, I can even see the big cluster's cpu5 off, what more can I ask for? (Purely intentional to set a really high ts
Arget_load and go_hispeed_load at lowest frequency to make this happen) this means everythung works fine as intended (the way I tweaked it to be.)
Anyway this is to be expected for light usage. Btw could you please install accubattery for me and turn on "cpu core" on the overlay settings within the app? There should be 6 overlay batteries at your bottom right continuously changing to see cpu frequencies. Now with thst try a full cycle again and note this:
*At what apps does most of the cores get to red (above 3/4)
*In your observation, how long does it stick to yellow (1/2 above) and red frequencies? (Above 3/4)? Please tell in miliseconds e.g. red at 20ms most of the time etc.
You will see what I'm talking about when you install the app
Anyways continue again with a normal full cycle bro and I'll be waiting for the next update!
Click to expand...
Click to collapse
Accubattery requires me to pay to use the overlays, and I have no money what so ever on my play account :crying: is there anything else I could use instead?

Curlyfry2121 said:
Accubattery requires me to pay to use the overlays, and I have no money what so ever on my play account :crying: is there anything else I could use instead?
Click to expand...
Click to collapse
I forgot about all of that ? well I dont really recommend the other alternatives since most are outdated. Though cpu float should do the trick

I'm going to start all over with my testing again in case my previous one was skewered for some strange reason. Downloaded gboard instead of bb keyboard and rebooted my phone. I'll reset the CPU stats as well after my app updates are done since that'll likely tax things a little too much. I'll have proper results probably 24 hours from now.
My main culprit right now is that the g4 skin is more heavyweight than thought to be so a nudge more CPU power is needed for general tasks to account for it if that makes any sense. Otherwise i run my phone fairly lean as it's debloated and i make use of greenify, amplify, and powernap so there's minimal services and apps in the background at most times.

spartan268 said:
I'm going to start all over with my testing again in case my previous one was skewered for some strange reason. Downloaded gboard instead of bb keyboard and rebooted my phone. I'll reset the CPU stats as well after my app updates are done since that'll likely tax things a little too much. I'll have proper results probably 24 hours from now.
My main culprit right now is that the g4 skin is more heavyweight than thought to be so a nudge more CPU power is needed for general tasks to account for it if that makes any sense. Otherwise i run my phone fairly lean as it's debloated and i make use of greenify, amplify, and powernap so there's minimal services and apps in the background at most times.
Click to expand...
Click to collapse
Not to jump on some hate-wagon here but I am really against powernap, thought that's just me.
I have gboard as well and has chosen a substratum dark overlay for it (if you don't have a substratum support just get the material black theme) also, gboard consumes battery a little tinsy bit than your normal keyboard, don't forget to disable the snippets and share to google statistics in the preference tab to avoid continuous syncing. I'll be waiting for the results and if everything still seems to lag, I might cook something different especially for you

Reasons for new thread:
3) This is a different method to the once described before.

Android O, Naptime FORCE DOZE, My previous stats are as follows;
(This was using my custom governor tweaks and the skipped/unknown lost battery in the middle is a bootloop)

Forgot this xD

After 2-3 days on the latest version, I continue to see overnight battery usage (sleep+doze+battery) trending a bit lower then with my prior profile HawkFlyv1.2. This along with a noticeable increase in responsiveness, puts GlassCannon at the top of my current list.
Good work @phantom146. I'll try to work on providing details for this alpha test in the next day or so

LazerL0rd said:
Reasons for new thread:
3) This is a different method to the once described before.
Click to expand...
Click to collapse
LazerL0rd said:
Android O, Naptime FORCE DOZE, My previous stats are as follows;
(This was using my custom governor tweaks and the skipped/unknown lost battery in the middle is a bootloop)
Click to expand...
Click to collapse
That instagram... :laugh:
LazerL0rd said:
Forgot this xD
Click to expand...
Click to collapse
Any stutters or jitters? phone freezes etc.?
About the battery life, any comments on that? and the one we talked about the pm (regarding the ramping down and input_boost) any thoughts after this cycle?
Will wait for your answer
Mesmurized said:
After 2-3 days on the latest version, I continue to see overnight battery usage (sleep+doze+battery) trending a bit lower then with my prior profile HawkFlyv1.2. This along with a noticeable increase in responsiveness, puts GlassCannon at the top of my current list.
Good work @phantom146. I'll try to work on providing details for this alpha test in the next day or so
Click to expand...
Click to collapse
I am glad you are liking this profile and will wait for more results, also; it would help me if you can try GlassCannon with heavy usage using heavy graphical games such as need for speed asphalt, nba etc. I really want to see if we have any kind of lags or stutters using high performance games. Thanks for the continuous support!

phantom146 said:
That instagram... :laugh:
Any stutters or jitters? phone freezes etc.?
About the battery life, any comments on that? and the one we talked about the pm (regarding the ramping down and input_boost) any thoughts after this cycle?
Will wait for your answer
I am glad you are liking this profile and will wait for more results, also; it would help me if you can try GlassCannon with heavy usage using heavy graphical games such as need for speed asphalt, nba etc. I really want to see if we have any kind of lags or stutters using high performance games. Thanks for the continuous support!
Click to expand...
Click to collapse
Was getting stuttering with Geo Dash ?? but I think it's just the settings I've enabled and or it's bad optimisations. Battery is equal to or slightly less than my previous governor. After a while I don't see much stuttering (btw i had stuttering before on Geo Dash too xD). There's one thing I enabled that you didn't though. And it's a value called fast_ramp_down. I'm gonna try without it now and see if there's still stuttering.

Just checked and stuttering is MASSIVELY reduced by disabling that option. Well, I thought it would be good. Anyway here are today's stats;
PS - I've decided to keep it, with a few of my own changes xD and sorry about the recharging, I was watching some TV shows ?

LazerL0rd said:
Was getting stuttering with Geo Dash but I think it's just the settings I've enabled and or it's bad optimisations. Battery is equal to or slightly less than my previous governor. After a while I don't see much stuttering (btw i had stuttering before on Geo Dash too xD). There's one thing I enabled that you didn't though. And it's a value called fast_ramp_down. I'm gonna try without it now and see if there's still stuttering.
Click to expand...
Click to collapse
LazerL0rd said:
Just checked and stuttering is MASSIVELY reduced by disabling that option. Well, I thought it would be good. Anyway here are today's stats;
PS - I've decided to keep it, with a few of my own changes xD and sorry about the recharging, I was watching some TV shows
Click to expand...
Click to collapse
well thats good to hear I was really wondering why you were getting stutters as 4 of my testers never got them. Its cool it is your phone to begin with so just tweak away but thanks for keeping the tweak it means a lot to me that somebody will use them as a daily profile :good:
Btw, those stats are crap hahahaha I can't even see where to begin with those charging cycles haha :silly:

phantom146 said:
well thats good to hear I was really wondering why you were getting stutters as 4 of my testers never got them. Its cool it is your phone to begin with so just tweak away but thanks for keeping the tweak it means a lot to me that somebody will use them as a daily profile :good:
Btw, those stats are crap hahahaha I can't even see where to begin with those charging cycles haha :silly:
Click to expand...
Click to collapse
Tomorrow I'm trying a mix of yours and a few I've created before. I done a little research and it seems my idea should work. But it's more experimental than Android O :laugh:
---------- Post added at 07:41 PM ---------- Previous post was at 07:40 PM ----------
The day after I'll test yours again, and I'll stay with whatever is better ?