Related
Hey,
So I'm on the fence about perma rooting and over clocking my G2, but i have a few questions:
1) Will my battery life suffer greatly due to over clocking say to 1Ghz or 1.4Ghz?
2) Are there any real world noticeable real world performance gains besides benchmark scores?
3) Will perma-Rooting it decrease performance? (Back when i had the mytouch 3g, the phone never felt as snappy after i rooted and installed custom roms, as compared to stock).
Thanks
1) battery life is the same if not better when overclocked with setcpu in ondemand mode at 245/1100mhz
2) there is a definite performance increase
3) custom roms can decrease performance depending on the rom and ui (sense is a bit heavy). Just simply rooting will not decrease performance. Also, CM6.1 is super snappy, especially using Launcher42
DO IT!
Sent from my T-Mobile G2
thedarkpassenger said:
1) battery life is the same if not better when overclocked with setcpu in ondemand mode at 245/1100mhz
2) there is a definite performance increase
3) custom roms can decrease performance depending on the rom and ui (sense is a bit heavy). Just simply rooting will not decrease performance. Also, CM6.1 is super snappy, especially using Launcher42
DO IT!
Sent from my T-Mobile G2
Click to expand...
Click to collapse
Launcher42? that's a heck lot of upgrade from Launcher2 I'd like to check it out
but he's right overclocking is not going to eat up your battery much. Heavy graphic ROMs do however suck up battery and performance. I personally like to stick to rooted stock roms and tune up here and there to fit my personal needs.
You should however read carefully and make sure to understand every steps you're doing if you want to root your phone.
androidtoy09 said:
Launcher42? that's a heck lot of upgrade from Launcher2 I'd like to check it out
but he's right overclocking is not going to eat up your battery much. Heavy graphic ROMs do however suck up battery and performance. I personally like to stick to rooted stock roms and tune up here and there to fit my personal needs.
You should however read carefully and make sure to understand every steps you're doing if you want to root your phone.
Click to expand...
Click to collapse
thedarkpassenger said:
1) battery life is the same if not better when overclocked with setcpu in ondemand mode at 245/1100mhz
2) there is a definite performance increase
3) custom roms can decrease performance depending on the rom and ui (sense is a bit heavy). Just simply rooting will not decrease performance. Also, CM6.1 is super snappy, especially using Launcher42
DO IT!
Sent from my T-Mobile G2
Click to expand...
Click to collapse
Alright I'm going to give it a shot later tonight probably, i forgot about the SETCPU profiles where you can have the phone under clocked while the screen is off. That should definitely give me better battery life. Ill be back to post results
kcm117 said:
Alright I'm going to give it a shot later tonight probably, i forgot about the SETCPU profiles where you can have the phone under clocked while the screen is off. That should definitely give me better battery life. Ill be back to post results
Click to expand...
Click to collapse
Good luck and I'm sure you will enjoy your G2.
Oh, and don't forget to show it off to your friends. Let them see how this thing "Fly"
I oc to 1.4+ with setcpu and a few profiles set up i get much better bat life then stock. Im also running a sense rom which feels sluggish until you oc. At 1.4 it runs smooth as can be with live wallpapers plus all the pretty sense animations. The only problem i have is i hate the sense dialer and msg system also i want to change the "personalise" tab....do people really change theyre settings everyday that they need a dedicated button for it? Anyway i digress
Sent from my HTC Vision using XDA App
Excuse me, since when does increasing the clockspeed of your CPU INCREASE battery life?!
convolution said:
Excuse me, since when does increasing the clockspeed of your CPU INCREASE battery life?!
Click to expand...
Click to collapse
No, that's not entirely true BUT with SetCPU you can profile it with different mode which can benefit the battery life.
kcm117 said:
Hey,
So I'm on the fence about perma rooting and over clocking my G2, but i have a few questions:
1) Will my battery life suffer greatly due to over clocking say to 1Ghz or 1.4Ghz?
2) Are there any real world noticeable real world performance gains besides benchmark scores?
3) Will perma-Rooting it decrease performance? (Back when i had the mytouch 3g, the phone never felt as snappy after i rooted and installed custom roms, as compared to stock).
Thanks
Click to expand...
Click to collapse
I don't notice any difference in battery and I have the 1.9ghz kernel. I normally keep it at 1ghz though. I enjoy it overclocked. My games run incredibly smooth, when navigating my phone it literally almost feels like it knows what i'm pressing a split second before i do and benchmarks rape the face off anyone else I know with an android phone. It's just sooo smooth. It really boils down to being the kind of person who likes to hold a powerhouse of a phone in the palm of their hand. (Literally) with even just the 1.4ghz OC you'll never have to ask yourself "can my phone run this without being sluggish?" because the answer is yes, it can probably even run two or three instances of whatever made you question yourself in the first place without being sluggish. Any if you're worried about custom roms from the past, just remember how outdated your old android is compared to this one. No offense because I can relate, I used to have a G1 that is now a hand-me-down to my brother and whenever he asks me to mod something on it, I'm just amazed at how slow it is and really don't know how I tolerated it for the last 2 years. I mean I'd score a 150 quadrant on the G1 (on a good day) but with my full OC on, the G2 scores 3000~3100. That's roughly 20 times faster...
Bottom line is that you won't need to worry about "will this make my device sluggish?" for quite some time.
Hey
Alright guys i got the phone perma rooted now, but i havent installed an OC kernel yet, two questions.
-Which kernal should i install if i want 1.4Ghz? there seems to be two threads with 1.4ghz kernels
-Do i need to install Bacon Bits for the kernel?
kcm117 said:
Alright guys i got the phone perma rooted now, but i havent installed an OC kernel yet, two questions.
-Which kernal should i install if i want 1.4Ghz? there seems to be two threads with 1.4ghz kernels
-Do i need to install Bacon Bits for the kernel?
Click to expand...
Click to collapse
just install cm6.1 and setCPU and you will be fine, then you can tweak it up to 1.42 if you like or whatever you want it at
Any heat related issues? Let's say I get into a zone and play some graphics intensive game 6 hours straight on USB power at 1.4Ghz? Wouldn't that put out more heat then the G2 was design to handle possibly shortening its life span?
convolution said:
Excuse me, since when does increasing the clockspeed of your CPU INCREASE battery life?!
Click to expand...
Click to collapse
It doesn't. However, overclocking is misnomer. What we really mean is over and UNDER clocking. For example with SetCPU is can create a profile that greatly slows down my CPU when the screen is off. This saves the battery a lot, since my screen is nearly always off.
Also, I can create profiles that slow down the CPU as the battery lowers in order to offset the fact that I overclock the CPU when the battery is fuller.
manvstech said:
Wouldn't that put out more heat then the G2 was design to handle possibly shortening its life span?
Click to expand...
Click to collapse
Probably could shorten the life span. I keep phones for a year or two, though, and shortened life span for me isn't an issue. The phone becomes outdated before the CPU gives up.
cparekh said:
It doesn't. However, overclocking is misnomer. What we really mean is over and UNDER clocking. For example with SetCPU is can create a profile that greatly slows down my CPU when the screen is off. This saves the battery a lot, since my screen is nearly always off.
Also, I can create profiles that slow down the CPU as the battery lowers in order to offset the fact that I overclock the CPU when the battery is fuller.
Click to expand...
Click to collapse
^This.
I've gone a full 10 hours with my battery still reporting 100%.
Sent from my HTC Vision using XDA App
my default sense rom does not feel sluggish at all.
this oc is not really required from my point of view. and it also does not increase battery. the thing what increased is the underclocking when screen is off.
and this you can do even without overclocking. and THEN it brings even more gain.
an example of "real world" for me is how well my g2 plays PSX games on the emulator. I have it overclocked at 1.5 on setcpu and it runs chrono cross pretty much flawlessly with no noticeable slow down.
i use setcpu for underclocking since i don't do enough just yet to overclock, i haven't noticed any battery increase just yet and i've been using it for a few days now. i almost questioned my self if i was losing battery life due to my system mhz always fluctuating? is this a possibility? i just added a profile for screen off 245/245 but i still had to choose on demand? what should i put there. thanks for ur help everyone
I installed the bacon bits 1.4ghz kernel and setup some setcpu profiles.....battery life is much better now.
Sent from my T-Mobile G2 using XDA App
screen off profile doesn't work with G2
noone has any proof it does change anything.
with or without widget running
As the title sugests one of the main goals for everyone who scrolls and uses his OPO either to avoid awkward situations, for work or simply to check social networks etc, you want to have the best GOD DAMN Battery life you can possibly squeeze from your 3.1k mAh battery !
I am not responsible for any damage to your phone. Read before downloading or posting in the thread. Proceed with caution if you have no experience.
So to start off, i'm already assuming you have your OPO rooted, which is a must for this guide.
So you can go for any custom ROM of your choosing as long as it supports the Kernel of your choosing.
Before trying to say which Kernel is best, i'd like to state that I have a really simple philosophy which is,If it ain't broke don't fix it, so I go with the AK Kernel because it never failed me, has a really good comunity to back it up and is the only tested kernel for the OPO in the UKM Thread.
( Don't worry i'll paste the links to all of these things that I'm speaking of )
After you got your Kernel up and going you're gonna download the UKM ( Universal Kernel Manager ), which will enable you to use Synapse on your device.
So now you have the Kernel and UKM, which means it's time to flash them all.
Now flash your UKM file and after installing it flash the Kernel and you should be set!
Once the Phone has booted, just make sure to download Synapse from the playstore. I wouldn't recommend changing the voltajes on your cpu because you can really **** your **** up which no one wants!
I'm running with this profile for over 3 months and it has done me wonders ( pics below )
Synapse Screenshots
This means your CPU will be running 1.3 GHz less about 80% of the time, the suspended Cpu frequency will be 300-400 MHz lower and the GPU which goes to an all time high of 578 MHz every time you install a new custom rom will be lowered to 200 MHz. This will result in about 40% more battery AT LEAST.
I don't have any photos showing my battery time because i'm a bit stupid, but the next week i'll try to screenshot my battery life and show you, however, I do know that i'm averaging about 6 hours SoT with both Wi-Fi and Data turned on 24/7.
Also a really good and must have App that goes really well with this is Leandroid which makes your Data shut off after X minutes of the device being disabled. If you feel you're device is running low on battery because of uknown sources, I advise you to download Wakelock Detector to check if there is something keeping your cpu ramping up when it shouldn't be.
This is not optimal for a 3.1k mAh battery but, keep in mind that the memory leak issue is still in the works and this is the best I could do in the given situation.
Another point I would like to focus before ending this post is the screen brightness. We all know that Android L stock Brightness control sucks ( if you don't now you do ), so I recomend using Lux Lite, which controls your screen brightness by adjusting it whenever it receives more or less light in the sensor, and it has worked wonders for me, it you're interested in a profile I will link mine
Now I won't bore more, I hope this "guide" was helpful to you and if you liked it don't be shy to press the thanks button.
Links
Kernel
UKM
Synapse
LeanDroid
Wakelock Detector
Lux lite
THIS DOES NOT WORK WITH OXYGEN OS
TL;DR - limit all your frequencies to 1/2 of what your phone is capable of.
Theoretically it makes sense. But in real world if you do some thinking - the phone would do task X in 5 seconds @ max frequency then go to sleep. If you limit the clock to half of the original value - it doesn't use 2 times less power, it uses slightly less than max. However, you are forcing it to do that task in 10 seconds @ half frequency before going to sleep. This means that it will use more power to achieve the same goal.
I would advice you to find a suitable governor rather than deliberately making your device slower than necessary.
nitrobg said:
TL;DR - limit all your frequencies to 1/2 of what your phone is capable of.
Theoretically it makes sense. But in real world if you do some thinking - the phone would do task X in 5 seconds @ max frequency then go to sleep. If you limit the clock to half of the original value - it doesn't use 2 times less power, it uses slightly less than max. However, you are forcing it to do that task in 10 seconds @ half frequency before going to sleep. This means that it will use more power to achieve the same goal.
I would advice you to find a suitable governor rather than deliberately making your device slower than necessary.
Click to expand...
Click to collapse
In all my runs with 2.5 GHZ and 1.2 GHZ I noticed a lot more difference running it with a lower clockspeed. ( 1- 1.30 hours more SoT )
I do know that the device requires more cycles to open an app while it's underclock however, i'm passing on what worked for me ( through some tests )
Hey can you tell me the procedure to flash on 05q??
I am trying to get good battery, now I am running franco kernel it does not give good battery. So if you can then please post the instructions.
Do you have root and recovery already installed?
Is it safe to change my CPU governor to "performance" to force max clock speed?
I don't want to overclock my Note 4, don't worry, not talking about that. But I am talking about MAX clocking it - forcing it to run at maximum rated speed. I've already tested out SetCPU and used it to change my governor to performance which forces the clock to max, and it nearly doubled my framerate in many games, especially the ones that struggled to play on this device like Xcom:EW.
But I quickly turned it off because I wasn't sure it was safe to do in the new era of smartphones, what with their DVFS and all. I'm worried that I'm going to overheat the CPU, and it's not going to be able to downclock because of temperature anymore. I'm only modifying the governor, but what if I actually used SetCPU to just change the CPU clock to max, without even touching the governor?
Can I hurt my phone by doing this? Can I safely start forcing my CPU to run faster while playing games, knowing that the only thing I risk is my battery draining faster, or am I actually risking damaging components by doing this?
Hello and thank you for using Q/A,
your CPU will not be damaged, but the battery life time will be shorted.
Regards
Trafalgar Square
RC
I personally have used Performance governor on Moto X 2013 for almost the whole 8 months I had it, 24x7 I mean. Never had a problem, yeah maybe battery life was little less than normal but I never did really care about it. Then I ran the same governor for a good period of time on my Note 3 too, same, no problem at all. Like you said, in games the frame rate difference is massive, but I don't play much games, I simply used that governor because it gets rid off all those micro lags and jitters which are Android's trademark, I simply can't them, with default Interactive the micro lags are very apparent.
However with Note 4 I am pretty happy with the BluActive governor, it makes most of the micro lags to go away, so sticking with it.
In any case unless you plan to use a mobile phone for maybe 5 years or so, I don't see any problem at all with it, other than a slightly increased heat, and maybe a little less battery backup, but you will find so many comments which might scare you, that chip burns off if you run it and all that, but those mainly are BS.
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!
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 ?