Hi guys,
I have the 855 version of this phone, and I have noticed that, even if Antutu scores are spot on (44k), in games such as GT racing 2 or similar I get a lot of lag.
Now, everyone will think "there are 1000 threads about lag, stick to those". Unfortunately, tricks such as getting rid of the thermal protection are really not good options, as the phone temperature will start to skyrocket.
There's a much easier and safer solution: root the phone and change the governor from interactive to conservative.
With interactive gov and CPU temp open in the background, I have noticed the CPU frequency bounces continuously up and down between 300mhz and 2400, even if the CPU temp is only 55c or so. This is causing the lag! Interactive governor is severely bugged, and this happens with any rom (I have tried both the stock 20h and the ChupaChups 4.2) and kernel (non AOSP at least).
Then, I switched to conservative, launched the game again, and guess what....now the frequency is nicely stable at 2457mhz throughout the entire gameplay and lag is gone completely. Temperatures? Totally fine: max 60c while playing and usually between 35 and 40 while whatsapping.
I literally tried everything to get rid of this damn lag, and the only thing that worked before this solution was to use a different kernel (chupa chups 2.1) and changing the governor...but I was getting crazy high temperatures, that sometimes touched 80c, and this was with a very heavy undervolt too! So I recommend to use the stock kernel, because it's the only one - for me at least - that grants good performances (and by that I mean no lag in games whatsoever and constant 2450mhz while playing) with good temperatures.
Any other option, including undervolting and trying different kernels didn't work for me, because either the CPU frequency kept shifting up and down every second causing lag, or - when I managed to keep it stable using different kernels and undervolting - the CPU temperature while playing got way too high (70c+, touching 80c sometimes).
To sum it up
1) Stick to stock rom and stock kernel (because of temperature issues)
2) Root
3) Change governor from interactive to conservative with Trickstermod (busybox required)
4) Enjoy smooth gaming experience and very good temperatures, with no significant throttle whatsoever!
Hope this helps!
as far as i know, conservative puts the cpu speed into the lowest possible, thus i thought won't be good for gaming performance.
nevertheless, i'd try for a few days and see if there's any noticeable difference.
thanks for sharing the knowledge, OP!
superbonto said:
as far as i know, conservative puts the cpu speed into the lowest possible, thus i thought won't be good for gaming performance.
nevertheless, i'd try for a few days and see if there's any noticeable difference.
thanks for sharing the knowledge, OP!
Click to expand...
Click to collapse
Theoretically you are right. But...interactive is bugged. Ondemand doesn't work (it will make your phone freeze) and performance will drain too much battery. So we are pretty much left with conservative.
Give it a try, and when you do, make sure you have CPU temp open to monitor both temperature and cpu frequency!
Let me know
Thank you! It really did the trick, gaming became MUCH better.
I tried RR3 - it became a lot better. On interactive it lags even in menu, on conservative it's rendering at 23-30 fps with slight not-game-breaking lags.
Battery
And about the battery? Will drain more in conservative than interactive? And will speed up the phone in all app or only in heavy games, when cpu is more active?
YaDr said:
Thank you! It really did the trick, gaming became MUCH better.
I tried RR3 - it became a lot better. On interactive it lags even in menu, on conservative it's rendering at 23-30 fps with slight not-game-breaking lags.
Click to expand...
Click to collapse
Cool! Glad this worked for you. What's your full load cpu temp?
Delgadovsky said:
And about the battery? Will drain more in conservative than interactive? And will speed up the phone in all app or only in heavy games, when cpu is more active?
Click to expand...
Click to collapse
I wouldn't worry about battery life..
It seems that this working generally, phone is much snappier and smooth for me than on interactive.
Yeah...the reason is that LG did an awful job with the interactive governor, and what's even worse is that it's actually using it as the default one.
Pretty incredible how bugged this is.
Yes but I think it's possible to make script in init.d folder to run conservative on boot as default. Maybe someone make one.
I Will try this ☺only for curiosity! I need busybox installed too or trickstermod only?
I've been doing the same thing for a long time now. I use SetCPU to automatically switch to the performance governor whenever the screen is on, and interactive whenever the screen is off.
You may also want to consider disabling mpdecision and thermald also. One of the two (probably mpdecision) will regularly change the governor back to interactive if you don't.
gianrond said:
Cool! Glad this worked for you. What's your full load cpu temp?
I wouldn't worry about battery life..
Click to expand...
Click to collapse
about 80°
I'm running Rin kernel with Lionheart governor on stock kit kat on a D850. It's ages better than interactive. I have plenty of governors to choose from, I'll slowly try them all.
omegajester said:
I'm running Rin kernel with Lionheart governor on stock kit kat on a D850. It's ages better than interactive. I have plenty of governors to choose from, I'll slowly try them all.
Click to expand...
Click to collapse
That works to get rid of the lag...but my phone was reaching easily 80c.
Now, with everything stock, the frequency stays nicely at 2457mhz with no throttle at all and the in-game temperature only maxes out at 63/64c.
Thanks for sharing this brother...just switched to conservative in trickster and I'll see how it goes.
I'm on crash Rom stock kernel with thermal mod activated...
Don't have any temperature issues till now expert while playing heavy games for some time.
Thanks again
Are the settings in trickstermod applied as you change the setting ? Or do you need to apply them manually ?
Also, do they apply on boot ?
I will try that, thx for the info.
Now how i can put it to change on boot?
Sent from my LG-D855 using XDA Free mobile app
JohnRM said:
Are the settings in trickstermod applied as you change the setting ? Or do you need to apply them manually ?
Also, do they apply on boot ?
Click to expand...
Click to collapse
On the latest trickster version you hit the upper right settings icon and the first four option that appear are under the set on boot part.check the kernel setting to be set on boot and you are done.
Of course after changing the governor that is...
danielferrari said:
I will try that, thx for the info.
Now how i can put it to change on boot?
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
I tested the "on boot' options and didnt work here.
Someone can run a benchmark with this mod? Mine was 38880 in interactive and 23000 with conservative lol
Sent from my LG-D855 using XDA Free mobile app
danielferrari said:
I tested the "on boot' options and didnt work here.
Someone can run a benchmark with this mod? Mine was 38880 in interactive and 23000 with conservative lol
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
41k with conservative here, and latest v20i. Everything stock.
Related
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.
After reading through the Thread for the Pre Release of FuguMod Ultra in the development section of this forum I thought I would post some info up for people who are wondering why it doesn't work with their phone, and just some general info on overclocking.
- First off, not all phones will be able to run at 1366MHz. Every CPU made has a range of freuqencies it will work at, and it is different for every single one. So some may be able to handle 1366MHz and above, others may max out at 900MHz. If you are getting black screens, freezes, or random behaviour, then your CPU doesn't like the frequency you have it at, try a lower frequency.
- Always keep an eye on the temp of the CPU when testing overclocking, if the CPU gets too hot, and fail safes don't work, there is a chance you could fry your CPU.
- With the FuguMod Ultra kernel, you must also be aware that gpu bus frequencies have been changed, so if your phone is not happy with that it will black screen. (as bus speeds are like cpu speeds, every different device can handle different clock speeds)
- plls values have been changed, and these may cause problems on your phone.
So if you want to have a go at overclocking your phone, back it up, and then give it a go. Select a frequency, and test with something pretty cpu intensive (3d game, multiple quadrant passes) and see if there are any bugs/overheating during a 15min time period. If you notice any problems/too much heat, try a lower frequency, and try again. And if for some reason your phone doesn't like the kernel, you can reflash with your previous kernel or a new ROM as you have already backed up your data.
If you have any other questions about overclocking, feel free to post here and I will try my best to answer them.
--- Samsung G3, InDroid 4.3, FuguMod 2.4 B3 800MHz ---
How can you check the CPU temperature? I thought it was only battery temperature.
Sent from my GT-I5800 using XDA App
dilzo said:
How can you check the CPU temperature? I thought it was only battery temperature.
Sent from my GT-I5800 using XDA App
Click to expand...
Click to collapse
The battery temp is a good representation of how hot the processor is getting as it is right next to the battery (only a thin sheet of metal seperating it) If the battery rises in temperature by a few degrees, then you can summize that the cpu is probably getting a few degrees hotter than that. I really wouldn't recommend letting the battery get above 55degrees (celcius) as this means the CPU may be getting up close to 65degrees (celcius) which is a very bad thing.
Good post.
Note that if you want to make some stress-tests, you have to put "PERFORMANCE" governor and set the max freq you want to test.
marcellusbe said:
Good post.
Note that if you want to make some stress-tests, you have to put "PERFORMANCE" governor and set the max freq you want to test.
Click to expand...
Click to collapse
Yes, Very true!!
Must also say, Your kernels are pretty legendary! Waiting patiently for the offical release of your FuguMod Ultra
m not able to see time in state with both setcpu and cpuspy and it seems deep sleep is also not working.
Piyush Rawal said:
m not able to see time in state with both setcpu and cpuspy and it seems deep sleep is also not working.
Click to expand...
Click to collapse
How have you got your phone set up? i.e. what ROM are you using etc.
I am using stock jpq with app2sd, swap, zipalign, ramhack and stuff. Setcpu is installed with default min/max freakquency, No profiles in use and undervolt a bit.
Ok,
This may be an issue caused by XXJPQ, as it is a new release there may be some sort of conflict. Have you tried asking if anyone else has this issue in this thread? http://forum.xda-developers.com/showthread.php?t=1132697
I haven't played around with JPQ yet so don't know what the bugs are yet.
Also, are you running a stock kernel? Have you confirmed that the phone has been rooted properly as well?
It's definitely a bug in Kernel. I tried three different roms and i wasn't able to check time in state in any of them (I am talking about fugumod ultra prerelease kernel here).
With previous versions of fugumad kernel everything is fine. So definatly a bug in kernel.
Piyush Rawal said:
It's definitely a bug in Kernel. I tried three different roms and i wasn't able to check time in state in any of them (I am talking about fugumod ultra prerelease kernel here).
With previous versions of fugumad kernel everything is fine. So definatly a bug in kernel.
Click to expand...
Click to collapse
Ok cool, I'll report the bug to the developer so that he can have a look into it. Thanks for testing and proving to the kernel.
Little bit of info some might find helpful. After some recent testing, I have found that some people might experience a black screen freeze when phone is in standby for a while with 83MHz min setting and on demand governor. I am not sure of the exact reason for this, whether it is a bug, or that the processor just doesn't like going that low for extended periods of time. If you experience this type of error, just hard reset the phone then open setcpu after phone has loaded and change the "standby" profile minimum to at least the next step up on the slider. Personally I use 223 setting as it provides a smoother lock screen animation, and no significant difference in battery drain.
Sent from my super smooth GT-I5800 using XDA App
Please share
1. your favorite governor (do you use any different governor on different profiles?)
2. your voltage parameters
3. Your benchmark using quadrant
Thanks
No one wants to play?
Maybe like me, they have no idea what you are talking about
What is a governor?
What voltage do you mean?
My quadrant score is 3900 ish
Thanks for the reply, I don't think I'm good enough to explain but, in a nutshell,
A governor is a a piece of code in the kernel that decides on the cpu speed. each kernel has multiple governors
voltage is where you can decide what voltage is delivered to your cpu at certain frequency. undervoltage will usually help you save battery. we have to pay attention not to go too low or it phone will freeze
download setcpu it will all become clearer
I will give this another bump before letting it die
Even I would be intrested in sharing this
currently I am using CF root with ondemand and its working all good
FM kernel with interactive. I find my phone snappier with this governor. I liked it the most with smartassv2 on Abysssomething (don't remember now) kernel, but too many teething problems with this one, had to revert to FM. I'll give it another shot soon though.
pjm77 said:
FM kernel with interactive. I find my phone snappier with this governor. I liked it the most with smartassv2 on Abysssomething (don't remember now) kernel, but too many teething problems with this one, had to revert to FM. I'll give it another shot soon though.
Click to expand...
Click to collapse
Do you use any additional profiles with Interactive?
Nope, I like the way it is.
pjm77 said:
Nope, I like the way it is.
Click to expand...
Click to collapse
Have you tried InteractiveX? Or, better yet, know the differences between the two? I am currently using smartassv2, FM kernel and have no complaints but would be interested if there was something a bit snappier when opening an app (I still get a bit of lag if I quickly select an app after unlocking the phone).
Yes, I've tried InteractiveX and OndemandX - they're both absolute rubbish (at least from my point of view). Both responsiveness and benchmark results were dismal (2800-3300 quadrant advanced). These are governors for anally retentive battery life lovers. Nothing wrong with that itself but beats the purpose when buying state of the art top shelf performance smartphone IMO.
Good to know. I appreciate the advice. Does that mean you also tried smartassv2 with the FM kernel? Any discernible difference between that and interactive, if you have? And sorry for all the questions but it saves me the trouble of trying them!
I just flashed the 1.3 FM a moment ago. Now running 100-1704 smartassv2, haven't played with voltages yet. Responsiveness in terms of screen scolling, lags & stutters seems better than 200-1400 interactive. Performance in Quadrant Advanced and Nenamark2 seems a tiny bit worse (but I don't really care about that, I use benchmarks only to roughly estimate, smoothness is what I'm after). I can't give you direct sources because I don't remember, but having spent several hours digging last weekend I concluded that for people who put performance slighly over battery life governors to be considered are interactive, smartass(v2), savagedzed and performance. Funny enough - I'm getting consistently worse benchmarks on performance governor on all kernels. I wonder why?
Thanks again. I will play around with some of the governors and settings to find the right fit. I think I will try savagedzen next but I am pretty happy with smartassv2 and may just stick with it.
Handy explanation of most of the governor options available in custom Note kernels: http://forum.xda-developers.com/showthread.php?t=1369817
AND
http://forum.xda-developers.com/showthread.php?t=1242323
Smartassv2 and vr. After reading a bit about it they seem to be the best for performance and balanced battery life.
i share with you my SetCPU config, voltage ...
it's very stable for me. It's not performance oriented but battery friendly.
what you think ?
EDIT : I use AbyssNote Kernel 1.2
I'm getting nice results here on FM Kernel 1.3. 1704mHz (1375mV) - 100mHz (775mV), lulzactive governor. 5000-5872 in Quadrant advanced, 32-35 in Nenamark2. Battery life good with low to med usage, poor when playing games, running satnav etc. - hardly a surprise We'll see about stability but so far so good.
This thread is finally picking off ! thank you all
I am currently on FM 1.3 and preferring lulzactive
I don't use any over clocking I guess I don't dare. is it safe?
I think i'm pretty aggressive with under voltage i'm running 1175mv at 1400mhz and 775mv at 200mhz. For some reason my phone freezes any time I use the 100mhz no matter the voltage .
Can you share the whole voltage for a comparison ?
with all this I can hardly get a full day of use with my battery but I guess I'm a pretty heavy on usage. no gaming or anything extensive but wifi-browsing-emails-3g-bluetooth all day
ArcticCat said:
For some reason my phone freezes any time I use the 100mhz no matter the voltage .
Click to expand...
Click to collapse
I read on some other kernel thread that Samsung's implementation of the 100mhz step is incomplete/buggy. That's probably why it doesn't work properly.
Hey everyone, just wanted to post this to see what cpu speed works best for you guys.. Im using these preset things with the program like performance or power saver etc but i dont seem to notice a difference all of them seem to be the exact same.. Wondering how to make it good for like 50% power and 50% performance, basicly balancing the 2 out as long as its better than stalk and not burning out my cpu.. so thanks, let me know what works for you guys as ive heard its slightly different for everyone else
(HTC EVO 4G)
I use the standard "ondemand" governor with a 998max-245min, but the thing I found makes the most difference are the settings under "Advanced".
I use the below "Advanced" settings along with a 245-245 screen off profile.
Seems to get me the best battery and cpu scaling.
It also helps to use an undervolting kernel like Freedom-More.
Try that for a couple days.
NOTE: click the apply button a couple of times (might be bug but they sometimes don't take on 1 button click). Try them as is without "Set on Boot", until you are sure that your phone likes them. Plus, check after a reboot that you verify/reapply them.
Sampling rate: 20000
Up Threshold: 85
Ignore nice load: 0
Powersave Bias: 14
I'm at 691200 on smartass governor with 245000 as min on Rcmix rom
Sent from my PC36100 using XDA App
ReapersDeath said:
Hey everyone, just wanted to post this to see what cpu speed works best for you guys.. Im using these preset things with the program like performance or power saver etc but i dont seem to notice a difference all of them seem to be the exact same.. Wondering how to make it good for like 50% power and 50% performance, basicly balancing the 2 out as long as its better than stalk and not burning out my cpu.. so thanks, let me know what works for you guys as ive heard its slightly different for everyone else
(HTC EVO 4G)
Click to expand...
Click to collapse
The "presets" are how the cpu scales i'd use "interactive" or "smartassv2" 245 min and max at 998+ then search around for here for various profile set-ups
I'm running the Gingerbread-Evo-Deck 1.3 with a Savaged Zen 2.2.1 CFS HAVS Kernel. I'm also undervolted 50mV, and using the interactive x governor set at 128MHz-768mhz. Running a few other simple tweaks learned from Carhauler, and I've got excellent battery life and great performance.
I currently run mine on an ICS rom & it comes standard with a tiatmat 4.1.0+ kernel & the cpu is running at about 245mhz-1036mhz with smartass governor(I usually set it to smartass v2 but it switches back to smartass haha). My battery life for me is enough to get me thru the day.
vulcan001 said:
I currently run mine on an ICS rom & it comes standard with a tiatmat 4.1.0+ kernel & the cpu is running at about 245mhz-1036mhz with smartass governor(I usually set it to smartass v2 but it switches back to smartass haha). My battery life for me is enough to get me thru the day.
Click to expand...
Click to collapse
Which ICS rom are you running?
I currently running RCMix3d Runny® Sense 3.5. Should I just got with ICS to overclock or just find a kernel that allows it?
oidrtybtrd said:
I currently running RCMix3d Runny® Sense 3.5. Should I just got with ICS to overclock or just find a kernel that allows it?
Click to expand...
Click to collapse
Get a new kernal. Try Tiamat 4.1
I have my SetCPU at 128min 1152max smartassV2(i CAN overclock up to 1267) with 1 profile:
Screen Off 128min 245max
My battery life is extremely good.
Hello Everyone.
As we know that CPU Governors are the ones that tell the CPU to do what in what situation and are largely responsible for battery and performance. Applying different governors can save battery or enhance performance depending on the type of governor.
There are a lot of governors available. The traditional like interactive, ondemand, powersave etc. and custom made like smartass v1 and v2, ondemand+, inteliactive etc.
This thread is meant for all of us to try different governors for approximately a day and then report the battery stats and performance levels . I could have done this alone using different governors each day and finally reporting all of the stats. But dude, haven’t you seen Hackers? All of us together can do it better and faster and cover a larger range.
So as I said the plan is that people try different governors and report and then we make a final report.
The number of governors you can test depends on the number of governors you have in your kernel . No seriously, more the number of kernels you use, more the governors you can test since different kernels have different governors. (many kernels are available in the xda Original Android Development thread)
I use Linaro(Insanity) kernel ( http://forum.xda-developers.com/moto-g/orig-development/kernel-falcon-t2868126 ) that has 14 custom governors along with the 5 traditional governors out of which I will test intelliactive, intellidemand, ondemand+, lionheart, hyper, adaptive, abyssplugv2 and wheatley along with interactive, ondemand, powersave, performance and users
You can also test the governors I do or someone else does as it will help in crosschecking.
It will be very helpful if someone can test other popular governors like smartass v1 and v2, min max, scary, lagfree etc. (more the better)
The most important thing...What to post?
1) Battery Stats...use the app Battery Stats Plus and the inbuilt battery stats shower to know the stats. (dont forget to reset the battery stats when starting a new stats)
2) Overall speed of phone.....like time taken when switching apps or opening recent tasks.
3) CPU Stats....You can check these from TricksterMod in the'info' menu. (Don't forget to check the "warp counters" when starting a new test)
Please follow these few rules while testing (these are no hard and fast rules but try to follow them)
1) Keep the phone usage and settings same during all the tests
2) Keep the screen brightness as minimum as possible
3) Don’t use batter saving or performance enhancing apps.
4) Test for atleast a day.
Recommended app for kernel tweaking and viewing the performance – Trickster Mod Kernel Settings. https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod&hl=en
Yup…try to follow these and we are cool.
I am posting this thread for the sole reason that we can know how our phone reacts to different governors and to know the clear cut stats so that we can use different governors as desired.
I know it will be irritating to use a sluggish Governor for a whole day but please bear with it for 24 hours..
For newbies like me..be ready to see somewhat a big difference.
I hope that everybody participtes. :fingers-crossed:
Posting starts tomorrow.
Tommorow i will test intelliactive.
ondemand, change down_differential to 70 .. this slows down the 'race to zero' effect of the governor.. setting can be changed easily with an app like trickster, the default setting on kitkat is 10
this will smooth stuff right out, especially games and general scrolling.. unfortunately will eat battery a bit
try a simple game like original temple run to see the difference before and after
meangreenie said:
ondemand, change down_differential to 70 .. this slows down the 'race to zero' effect of the governor.. setting can be changed easily with an app like trickster, the default setting on kitkat is 10
this will smooth stuff right out, especially games and general scrolling.. unfortunately will eat battery a bit
try a simple game like original temple run to see the difference before and after
Click to expand...
Click to collapse
Yes, I am a noob...
'change down_differential to 70 .. this slows down the 'race to zero' effect of the governor.. '
Whaaaat?
Meuuks13 said:
Yes, I am a noob...
'change down_differential to 70 .. this slows down the 'race to zero' effect of the governor.. '
Whaaaat?
Click to expand...
Click to collapse
basically it makes the cpu governor wait longer when cpu usage is lower before clocking down the cpu.. remember this happens in milli seconds.. sometimes jumping/jerking/lagging in a game can be because the cpu is constantly being down and up clocked.
meangreenie said:
basically it makes the cpu governor wait longer when cpu usage is lower before clocking down the cpu.. remember this happens in milli seconds.. sometimes jumping/jerking/lagging in a game can be because the cpu is constantly being down and up clocked.
Click to expand...
Click to collapse
Oh..I got it..I appreciate your effort but here we are looking for exact battery and CPU stats