msm-dcvs vs ondemand CPU governors - Sprint Samsung Galaxy S III

Between these 2 governors, has anyone noticed a significant advantage as far as battery life goes?

shinesthru said:
Between these 2 governors, has anyone noticed a significant advantage as far as battery life goes?
Click to expand...
Click to collapse
Hopefully more people respond to this, as I'd like to know more details around the msm-dcvs governor. I had it enabled in Clark's 0.0.6 ROM, and I noticed it was pretty much locked at right around 1000-1500mhz. It wouldn't scale below that. I don't know if it was something in the ROM or not, but I used Voltage Control to scale the min down to 352mhz or whatever it is.
I changed the governor to ondemand and set as boot as service (was getting errors creating the init.d script) and it seems to be functioning fine now.

I've been using the msm-dcvs governor in CyanogenMod, and I've actually been having the opposite experience. It seems to max out around 1134MHz most of the time, though CPU Spy shows that higher clock speeds are being used, but rarely. The rest of the time is spent mostly around 384MHz. I haven't really tested it fully yet, let alone against ondemand. I'm going to keep using msm-dcvs since Qualcomm made it specifically to take advantage of our processors' scaling and voltage features. I haven't had any problems.

EndlessDissent said:
I've been using the msm-dcvs governor in CyanogenMod, and I've actually been having the opposite experience. It seems to max out around 1134MHz most of the time, though CPU Spy shows that higher clock speeds are being used, but rarely. The rest of the time is spent mostly around 384MHz. I haven't really tested it fully yet, let alone against ondemand. I'm going to keep using msm-dcvs since Qualcomm made it specifically to take advantage of our processors' scaling and voltage features. I haven't had any problems.
Click to expand...
Click to collapse
What has your battery life been like?

jhavron said:
What has your battery life been like?
Click to expand...
Click to collapse
Well, I've actually been forced away from msm-dcvs because there is a bug in the AOSP Jelly Bean implementation, and none of the devs involved with either CM or other AOSP projects will acknowledge that the problem exists, let alone fix it. So, I've been using the Ktoonservative governor. It's working pretty well for now, but I'd prefer if msm-dcvs just got fixed instead

EndlessDissent said:
Well, I've actually been forced away from msm-dcvs because there is a bug in the AOSP Jelly Bean implementation, and none of the devs involved with either CM or other AOSP projects will acknowledge that the problem exists, let alone fix it. So, I've been using the Ktoonservative governor. It's working pretty well for now, but I'd prefer if msm-dcvs just got fixed instead
Click to expand...
Click to collapse
Out of curiosity, what problems were you having? I have Voltage Control set to apply noop/ondemand at startup, but I just temp changed it back to msm-dcvs for kicks to see how it goes. I know it's the stock governor that came with the phone, so I'd like to stick with that if possible.
I thought I remembered seeing the speeds always be towards the higher end before, but I'll run it again now and see what happens. I'm using FreeGS3, v0.1.1 right now for what it's worth.

hayzooos said:
Out of curiosity, what problems were you having? I have Voltage Control set to apply noop/ondemand at startup, but I just temp changed it back to msm-dcvs for kicks to see how it goes. I know it's the stock governor that came with the phone, so I'd like to stick with that if possible.
I thought I remembered seeing the speeds always be towards the higher end before, but I'll run it again now and see what happens. I'm using FreeGS3, v0.1.1 right now for what it's worth.
Click to expand...
Click to collapse
With the stock CM10 kernel, as soon as I touch the screen, the frequency jumps to 1134MHz and stays there until you turn the screen off. Then, it drops to the min. speed until you turn on and touch the screen again, at which point it jumps back to 1134MHz and locks itself there.
With the KT747 kernel, the speed more-or-less limits itself to 702MHz, and it's nearly impossible to make it scale any higher. KToonsez refuses to acknowledge the problem, so it won't be fixed anytime soon.
I've gotten CPU Spy graph screenshots to illustrate the problems (comparing the stock ROM to AOSP ROMs while doing the same task), but all parties still deny the problems exist. I don't really know what to do to get them to fix it at this point, so I just gave up. I'm hoping it's just some JB driver issue and it'll be fixed when the official JB kernel source is released.

Related

[KERNEL] smartass cmkernel 11/26/11]

This is based on the cyanogenmod kernel, with the main change being the smartass governor has been added and is default.
The zip file is in koush's anykernel format, so it can be flashed just like a rom.
Changes:
Smartass governor by erasmux is default
extra overclock enabled
patch #22 by farmatito
disabled CONFIG_SERIAL_MSM
NO SUPPORT WILL BE GIVEN. ONLY FLASH IF YOU KNOW WHAT YOU ARE DOING. NO ONE IS RESPONSIBLE EXCEPT YOU. BLAH BLAH BLAH.
Newest
2.6.35.14-oc-cm-smartass_g0dd6e8c.zip
source: http://github.com/dumfuq
old versions: http://www.mediafire.com/dumfuq
What does the smartass governor do?
mackster248 said:
What does the smartass governor do?
Click to expand...
Click to collapse
smartass governor - is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works - by taking over the idle loop - is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the "old" minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 - why?! - it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!
i googled it lol, seems like its a bit more responsive then interactive, and it ramps down quickly too. could give some battery savings
What ROM's will this work with?
keeps cpu at/above 768mhz, will not go below until you switch off smartass gov.
liking the "sleep" enhancement, but seems like it should let the processor scale on down to 245 when idle with screen on
I'm running this with CM7 Nightly #16 and it's running really well. I'm getting a little more battery consumption than I do with zinx's kernel, but that could just be because I've only been using the kernel for around 2-3 hours. It may need a little more time to settle? I'm not sure, but it is definitely snappier! If it does scale down the cpu during screen off, you can't tell at all! It doesn't have any lag when unlocking like setting profiles usually does. So I'm really stoked about this kernel! Great work as always Dumfuq! This will be my new kernel for at least a few days to give it more of a chance.
PS: I'm only getting around 29 on linpack at 1.017 GHz, where as with zinx's I was getting 38's. Smartbench scores are at 1320's for productivity and 1869 for gaming. So those both beat out zinx's kernel. Just wanted to put those out there so people have some kind of a comparison point.
posted a v2. The difference is frequencies are changed to match glacier frequencies instead of hero's.
The only noticable difference here is that when the screen is off the frequency scales between 245 and 368 instead of being stuck at 245.
dumfuq said:
posted a v2. The difference is frequencies are changed to match glacier frequencies instead of hero's.
The only noticable difference here is that when the screen is off the frequency scales between 245 and 368 instead of being stuck at 245.
Click to expand...
Click to collapse
Damn. Nice!
Works with evil's MIUI 1.1.26 r2..Hopefully battery life will increase now.
Edit: breaks video playback in miui
sl1k1 said:
Works with evil's MIUI 1.1.26 r2..Hopefully battery life will increase now.
Edit: breaks video playback in miui
Click to expand...
Click to collapse
Smartass is already compiled in.
Sent from my HTC Glacier
I use this on my GF's Mytouch Slide and she gets 20+ hr's on a charge overclocked @ 825. Was so hoping someone would port the kernal to this phone. thx dumfuq ^^
Trying to decide if I want to flash this over the stock cm7 kernel.
Has anyone noticed any gains from doing this? what about compared with the stock cm7 kernel + setCPU?
flashed this over build 16, cm7. I still use setcpu. no problems, everything is smooth like butter. Definitely smoother than it was before. no wake up problems, no play back problems. thanks for this =]
Does wifi calling also work with this? Anyone know?
brian6685 said:
Does wifi calling also work with this? Anyone know?
Click to expand...
Click to collapse
You could always flash it and find out, and if not, just restore the backup you made prior to flashing it. ;] I don't see why it wouldn't it hasn't broken anything for me.
K ill try it out later when I get home from work. Thanks
whats the mhz setting on this by default? not super fond of setcpu. though i do like this idea of a custom throttle and logic. so i figured if the mhz is high enough then i'll give it a shot.
brian6685 said:
K ill try it out later when I get home from work. Thanks
Click to expand...
Click to collapse
let us know what happens
here's my initial test of the v2 as far as battery goes...
looks like wifi calling works ;]
I've had great battery life with this kernel so far.

overclocking dhd

I have recently rooted my dhd and currently running CM7. Using the cpu setting within the performance menu I am wondering what peoples thoughts are on a noticeable but safe increase of cpu speed. its set as 1017MHz which i believe is default. I am told I can run anything up to 1500 safely. can anyone confirm this and also tell me what kind of result (performance and battery life) i should expect.
thanks
Well, I use Android Revolution HD (a sense rom, meaning heavy UI!) and i overclock to about 1.3GHz. In terms of battery life when it's awake, it seems a drain a teeny bit more readily, but I've never had a freeze on sense (quite rare)
On stock it underclocks to let the processor max at around 400MHz when the screens off, so that helps to really save a lot of battery on standby. On CM, I'd expect it'd feel more or less the same in terms of performance after you hit 1.2/1.3GHz
hmohammed43 said:
Well, I use Android Revolution HD (a sense rom, meaning heavy UI!) and i overclock to about 1.3GHz. In terms of battery life when it's awake, it seems a drain a teeny bit more readily, but I've never had a freeze on sense (quite rare)
On stock it underclocks to let the processor max at around 400MHz when the screens off, so that helps to really save a lot of battery on standby. On CM, I'd expect it'd feel more or less the same in terms of performance after you hit 1.2/1.3GHz
Click to expand...
Click to collapse
thanks for the reply mate. going to try out revolution HD soon i think. have you overclocked using a third party app or is there one built into that rom?
also im a little confused by the governors. 'on demand' is the default governor. Does that mean it will only use the max selected cpu speed when necessary? would you recommend using a difference setting?
cheers
rhodri11 said:
thanks for the reply mate. going to try out revolution HD soon i think. have you overclocked using a third party app or is there one built into that rom?
also im a little confused by the governors. 'on demand' is the default governor. Does that mean it will only use the max selected cpu speed when necessary? would you recommend using a difference setting?
cheers
Click to expand...
Click to collapse
The CPU is managed by the ROM itself. You can tweak it yourself by using setCPU (or similar), but I can advise you not to. Can't help you with the governors buddy, since I dunno what it is
Cheers
darude0306 said:
The CPU is managed by the ROM itself. You can tweak it yourself by using setCPU (or similar), but I can advise you not to. Can't help you with the governors buddy, since I dunno what it is
Cheers
Click to expand...
Click to collapse
nice one dude
I'm running cm7 and I'm overclocked to 1.5 ghz. It's been totally fine for months.
Sent from my Motorola Startac running Atari 2600 software!
rhodri11 said:
thanks for the reply mate. going to try out revolution HD soon i think. have you overclocked using a third party app or is there one built into that rom?
also im a little confused by the governors. 'on demand' is the default governor. Does that mean it will only use the max selected cpu speed when necessary? would you recommend using a difference setting?
cheers
Click to expand...
Click to collapse
Lucky you picked a linuxhead!
The system itself has a daemon (background process built into the system) that handles overclocking. It's all explained on the page and also on this thread:
http://forum.xda-developers.com/showpost.php?p=14638641&postcount=34279
You can use another app (like SetCPU) but the daemon usually handles screen off's quicker. The governors basically determine how the processor frequency is changed. I'll explain the common ones:
Performance - Runs at highest speed, so if you have a range of 200 to 1.3G, it'll stay at 1.3G all the time, not usually the best
Ondemand - The universal default for phone overclocking, it only changes the speed up after a certain percentage of the CPU is used, and it switches on the fly, so if the CPU is used too much at 400MHz, it'll ramp it up to maybe 600 or 800, and if it's still overused, it'll put it up to maybe 1 or 1.2G
Conservative - This is like ondemand, except it makes the changes more gradual. It can give noticable lags in the foreground at times, so this is mainly used when the phone is asleep (screen off)
Smartass - This governor is like ondemand, except it'll less readily switch frequencies to higher values when it detects the screen off. This isn't really used because the overclocking daemons take into account the phone being awake or not
Basically, there isn't really a need to change governors, only really frequencies if anything. The thread, however, does tell you how to change governors.
Im using latest LeeDroid GB 3.2.1 and to be honest with the work he's done with the Kernal (3.1.8BFS) I have found that the ROM is a lot MORE responsive without me overclocking the CPU.
Im not really sure how it all works, but I guess doing this on different ROMS has its own different out comes.
overclocking has me confused too, is there really that much of a benefit in it? how much will i gain from it?
toby_lerone said:
overclocking has me confused too, is there really that much of a benefit in it? how much will i gain from it?
Click to expand...
Click to collapse
There is a benefit when you use certain apps, or even sense itself. For example, I've never had sense ui freeze, or go slow. The under clocking helps to improve the rubbish battery life when your phone is asleep.
In terms of measuring the gain, I have no idea. Really, I'd think you could use a process heavy app, or benchmarking app and see.
There's also loads of guides on overclocking to help out! (that's how I got the hang of it! )
Sent from my Desire HD using XDA Premium App
For the need on OC, it depends on the kind of apps u're using. If u're happy w a non OC DHD, its totally up to u.
But for the UC, it works as a terrific battery saver, mich better/effective than other battery saver soln on market
The safe range depends on the DHD as the manufacturing changed even though same part, i'm OC 1.5GHz "On Demand" profile and under clock 245MHz on screen off "Power Save" profile.
Getting approx a day usage on Lee 2.1.

[Q] Decks or Cm7's best kernel (SVZ vs Tiamat vs Godmode)

Hi guys, i've been looking into many threads and reading a lot of posts and asking a lot of questions. however i know that their is not for sure answer to this but i would like to see what you guys believe to be your best kernel for battery and performance. i have seen people say it is Godmode (v9), Tiamat v4.1.0, Tiamat v3.3.7, and Savaged-zen v2.2.1. (ALL of these ARE with SBC-OFF). i just want to know what is you best kernel at the moment for your evo with decks or cm7.
Side Question: what is the difference between the governors: (Interactive, InteractiveX, Smartass, SmartassV2, Savaged-zen, and Lag Free)?
- Thank You
I like Tiamat 4.1.0, but I can't help you for your side question. I'm still new to development and rooting
kendallc123 said:
I like Tiamat 4.1.0, but I can't help you for your side question. I'm still new to development and rooting
Click to expand...
Click to collapse
i know you said your new but im just wondering have you tried any other kernels?
and what is your battery life with Tiamat 4.1.0
I've used damn near every kernel available for CM7. And by far the BEST kernel for battery life is Savaged Zen. I'm on a stock battery and it just seems to last forever. Add to that the fact that the battery lasts all day without sacrificing performance at all. Every phone is different and you may or may not see the same results. This is just what has worked for my phone. Honestly, your best bet is to get flash happy with various kernels until you find one that gives you the performance and battery life that you're looking for. By the way, I use SVZ Manager with my kernel so that I can toggle SBC on and off as I please. It's a nice apk that gives you some flexibility.
**CLICK HERE**
Green_Arrow said:
i know you said your new but im just wondering have you tried any other kernels?
and what is your battery life with Tiamat 4.1.0
Click to expand...
Click to collapse
I've tried Tiamat 4.0.8 and a Savaged Zen kernel (can't remember which version). They both gave me about 12 hours of battery life on an average day(for me). But an average day for me is going to school, so I'm not on my phone as much. I haven't gotten to really test the battery life because I haven't looked at it on the weekend when I'm not at school. But like Concordium said, every phone is different! Try them all!
Tiamat 3.3.7 sbc
Sent from my PC36100 using XDA App
Concordium said:
I've used damn near every kernel available for CM7. And by far the BEST kernel for battery life is Savaged Zen. I'm on a stock battery and it just seems to last forever. Add to that the fact that the battery lasts all day without sacrificing performance at all. Every phone is different and you may or may not see the same results. This is just what has worked for my phone. Honestly, your best bet is to get flash happy with various kernels until you find one that gives you the performance and battery life that you're looking for. By the way, I use SVZ Manager with my kernel so that I can toggle SBC on and off as I please. It's a nice apk that gives you some flexibility.
**CLICK HERE**
Click to expand...
Click to collapse
at the moment i am using the latest svz kernel with the svz manager as well. i have been flashing many kernels and for a while i was happy when i used the godmode kernel my phone lasted me 1 day and 6 hours, however he is no longer updating his kernels =( i'm hoping to find another kernel such as that one that will give me around the same results ^_^
Green_Arrow said:
at the moment i am using the latest svz kernel with the svz manager as well. i have been flashing many kernels and for a while i was happy when i used the godmode kernel my phone lasted me 1 day and 6 hours, however he is no longer updating his kernels =( i'm hoping to find another kernel such as that one that will give me around the same results ^_^
Click to expand...
Click to collapse
I liked Godmode. But it didn't seem to give me as good battery life as savaged zen has given me. Each phone is different though.
Concordium said:
I liked Godmode. But it didn't seem to give me as good battery life as savaged zen has given me. Each phone is different though.
Click to expand...
Click to collapse
well im testing this one out at the moment and it has given me so far 17 hours and 20 mins, still at 31% battery, im just not sure if it'll do better than godmode did, at the moment im running it on the smartass kernel and i ran godmode on interactive so maybe that is the prob... however another issue is i've heard that svz is no longer updating as well... do u know if this is true? and one random thing that only a few people have told me is that they run on performance and overclock their phone and get the best battery from it, is that possible or a lie?
Edit: it lasted 20 hours and 53 mins, so since it didn't do as good as GodMode did then im gonna try the tiamat 4.1.0 now cause it has first place in the poll atm.
Green_Arrow said:
well im testing this one out at the moment and it has given me so far 17 hours and 20 mins, still at 31% battery, im just not sure if it'll do better than godmode did, at the moment im running it on the smartass kernel and i ran godmode on interactive so maybe that is the prob... however another issue is i've heard that svz is no longer updating as well... do u know if this is true? and one random thing that only a few people have told me is that they run on performance and overclock their phone and get the best battery from it, is that possible or a lie?
Edit: it lasted 20 hours and 53 mins, so since it didn't do as good as GodMode did then im gonna try the tiamat 4.1.0 now cause it has first place in the poll atm.
Click to expand...
Click to collapse
Its true that its not being updated anymore. It sucks but I plan to ride it out as long as the kernel functions properly with CM. Once it starts screwing up then I'll switch.
Those who say they get the best battery life by overclocking and putting their phone on performance are full of crap. Performance governor is basically the polar opposite of Powersave. Performance keeps your cpu constantly running at a high frequency. Logic states that overclocking to 1.13 ghz and perpetually running at that frequency requires more power than running at 245 mhz. The more power required the less time your battery will stay alive. Powersave gives you best battery life but gives you crap performance. Interactive, Smartass, and Ondemand give you a balance of performance and battery life. Performance gives you the best performance but crap battery life.
By the way, do you really need a phone that can stay off the charger for more than 21 hours? :-x
Concordium said:
Its true that its not being updated anymore. It sucks but I plan to ride it out as long as the kernel functions properly with CM. Once it starts screwing up then I'll switch.
Those who say they get the best battery life by overclocking and putting their phone on performance are full of crap. Performance governor is basically the polar opposite of Powersave. Performance keeps your cpu constantly running at a high frequency. Logic states that overclocking to 1.13 ghz and perpetually running at that frequency requires more power than running at 245 mhz. The more power required the less time your battery will stay alive. Powersave gives you best battery life but gives you crap performance. Interactive, Smartass, and Ondemand give you a balance of performance and battery life. Performance gives you the best performance but crap battery life.
By the way, do you really need a phone that can stay off the charger for more than 21 hours? :-x
Click to expand...
Click to collapse
no i do not but! 3 days of the week im at school doing nothing for 8-10 hours so... i think if my phone can run longer than a day w/o charging then it mean i can play games on my phone while waiting and by the end of the day i'll still have battery. and does it make sense for someone to get better battery life on interactive than on smartass?
Green_Arrow said:
no i do not but! 3 days of the week im at school doing nothing for 8-10 hours so... i think if my phone can run longer than a day w/o charging then it mean i can play games on my phone while waiting and by the end of the day i'll still have battery. and does it make sense for someone to get better battery life on interactive than on smartass?
Click to expand...
Click to collapse
Well Smartass, as I've heard it described, is sort of like Interactive 2.0. It's basically the interactive governor but better. Unfortunately, I do not know enough of the exact specifics of the governors to tell you which SHOULD be getting better battery. I would just run each of those governors and see which one works better for you.
And I thought your phone already lasted 21 hours with a decent amount of usage. You need to test the governors/kernels in the exact situation you are going to be using the phone. Interactive, Ondemand, and Smartass would all manage the phone pretty much the same if you just leave it alone and let it sit till the battery drains. but they each manage the power allocation supplied to the cpu very differently during actual use. One ramps up the voltage quickly while one scales it up more gradually. So take your charger with you to school, in case you run into trouble, and use the phone as you believe you will be using it in the future. Then you'll have a more accurate idea of which setup works best for you.
Concordium said:
Well Smartass, as I've heard it described, is sort of like Interactive 2.0. It's basically the interactive governor but better. Unfortunately, I do not know enough of the exact specifics of the governors to tell you which SHOULD be getting better battery. I would just run each of those governors and see which one works better for you.
And I thought your phone already lasted 21 hours with a decent amount of usage. You need to test the governors/kernels in the exact situation you are going to be using the phone. Interactive, Ondemand, and Smartass would all manage the phone pretty much the same if you just leave it alone and let it sit till the battery drains. but they each manage the power allocation supplied to the cpu very differently during actual use. One ramps up the voltage quickly while one scales it up more gradually. So take your charger with you to school, in case you run into trouble, and use the phone as you believe you will be using it in the future. Then you'll have a more accurate idea of which setup works best for you.
Click to expand...
Click to collapse
just wondering what do you keep your cpu settings at: the governor, cpu min & max?
When I am plugged into my wall charger I keep it at 1113/245. I use Performance for benchmarking and testing since I don't need to worry about battery life and Smartass when doing everything else. For normal every day use I have it at 1036/245/Smartass, Interactive, or Ondemand. I don't really have a preference between the three governors since they all make my battery last more than long enough. So it usually comes down to whichever my clumsy finger happens to accidentally select first. If I happen to not go home and need more life then I'll drop to 729/245/Conservative or Powersave. I use conservative if I still need to be able to use the phone a bit and powersave if I want my phone to just sit there and look pretty till I get back home.
Concordium said:
When I am plugged into my wall charger I keep it at 1113/245. I use Performance for benchmarking and testing since I don't need to worry about battery life and Smartass when doing everything else. For normal every day use I have it at 1036/245/Smartass, Interactive, or Ondemand. I don't really have a preference between the three governors since they all make my battery last more than long enough. So it usually comes down to whichever my clumsy finger happens to accidentally select first. If I happen to not go home and need more life then I'll drop to 729/245/Conservative or Powersave. I use conservative if I still need to be able to use the phone a bit and powersave if I want my phone to just sit there and look pretty till I get back home.
Click to expand...
Click to collapse
why is ur lowest 245 and not 128? sorry if im bugging you
Green_Arrow said:
why is ur lowest 245 and not 128? sorry if im bugging you
Click to expand...
Click to collapse
You're not bugging me man. This place exists so people can ask questions and get help.
I keep my min at 245 because I've read, in multiple places, that allowing it to go any lower is not something your cpu really appreciates. Just like there is such thing as too high with your clock speed there is also a too low. And everywhere I have seen 245 is the preferred low end. I am not 100% sure as to why but I would assume that it is because your cpu needs at least a certain amount of power to run the basic processes required to keep your phone functional. Similar to a computer. Lower the cpu too much and it just can't do what it needs to.
Concordium said:
You're not bugging me man. This place exists so people can ask questions and get help.
I keep my min at 245 because I've read, in multiple places, that allowing it to go any lower is not something your cpu really appreciates. Just like there is such thing as too high with your clock speed there is also a too low. And everywhere I have seen 245 is the preferred low end. I am not 100% sure as to why but I would assume that it is because your cpu needs at least a certain amount of power to run the basic processes required to keep your phone functional. Similar to a computer. Lower the cpu too much and it just can't do what it needs to.
Click to expand...
Click to collapse
i see do u happen to know of a good thread that talks about this? cause i keep mine at the lowest because i read that its better for battery life, but they never said anything about it being bad
Green_Arrow said:
i see do u happen to know of a good thread that talks about this? cause i keep mine at the lowest because i read that its better for battery life, but they never said anything about it being bad
Click to expand...
Click to collapse
I don't remember there being a thread dedicated to this. I just remember it from posts I saw within different OC/UV threads. Do a Google search for it and see if that returns any results. Like I said, I doubt you'll find a full dedicated thread. But you may be able to find the individual posts where it's mentioned.
Concordium said:
I don't remember there being a thread dedicated to this. I just remember it from posts I saw within different OC/UV threads. Do a Google search for it and see if that returns any results. Like I said, I doubt you'll find a full dedicated thread. But you may be able to find the individual posts where it's mentioned.
Click to expand...
Click to collapse
thank you, you have been really helpful ^_^
With Tiamat 4.1 and juicedefender I get the best battery performance and v6 supercharger I have a smooth screen with no problems or lag at all.

[Q] Underclocking not effecting battery life?

I thought I would try CPU Master Free to underclock as I don't game or do anything CPU-intensive often, and I don't really notice much change. I have it set to 800mhz max, set at boot, and it doesn't seem to have improved overall battery. Am I doing something wrong? Is it moreso a voltage thing?
There are so many different things that effect battery life. The cpu might have not been sucking down that much juice as it is. Could be your screen, brightest, an app in the background, etc that's giving you bad battery life.
What did it for me was setting the cpu idle setting in juice defender ultimate to 500mhz, with ondemand.
I guess you can use any program, but this was the setting that finally gave me all day battery life.
new57 said:
What did it for me was setting the cpu idle setting in juice defender ultimate to 500mhz, with ondemand.
I guess you can use any program, but this was the setting that finally gave me all day battery life.
Click to expand...
Click to collapse
What ROM are you running? I read on the Calk forum that in FC24 he removed the Tegrak power saving settings because the phone likes to lock up below 800 MHz on ICS.
Speaking of which, it seems opening my camera freezes the whole phone now. I wonder if thats related...
Edit: Set it back to 1200mhz max, and the camera works fine again -_-
Apk07 said:
Speaking of which, it seems opening my camera freezes the whole phone now. I wonder if thats related...
Edit: Set it back to 1200mhz max, and the camera works fine again -_-
Click to expand...
Click to collapse
The release notes here for Calk's v1.3a mention that he removed the 800 MHz underclocking due to a kernel issue.
NoSpamDan said:
The release notes here for Calk's v1.3a mention that he removed the 800 MHz underclocking due to a kernel issue.
Click to expand...
Click to collapse
Ah. I'm running the FC22 repack, not FC24. Guess it happens on all the kernels thus far
Apk07 said:
Ah. I'm running the FC22 repack, not FC24. Guess it happens on all the kernels thus far
Click to expand...
Click to collapse
Yes, I believe that. Calk didn't say new kernel issue... I think it is ICS in general.

Ktoon's KT747 2/8/13 Kernel vs Task650's 2/10/13 Kernel

What are your guys' opinions on the performance of these two kernels? From what I've gathered it seems like KToon's kernel is meant for overclocking, but then what would one use task's for?
Task's recent update to his kernel makes me want to try it because I've been using KToon's kernel with the ktoonservative governer and row scheduler UV'ed a little bit but unlocked to 2.1GHz and have been having some pretty bad battery life in mu opinion, do you think switching to task's kernel would be better on the battery?
Well what do you guys think?
Fun Fact for the day. Versus threads get shut down in no time here on XDA.
P.S- Why wouldn't you just try it first before making a thread about it? Kernels take about 3 seconds to flash. Also. No one can tell you that you will get better battery life on one or the other considering all of the variables. We are all in different locations, use different apps, have different settings, and we all use our devices differently. You need to try them both out and see which one works better for YOUR device.
Man why are ya giving me a hard time? You kicked me out of your thread, which I understood and respect, but then you come here and tell me the same thing you told me before and that my thread's gonna go to the bin in no time.
I'm just trying to find out what the DIFFERENCES between the kernels are, because it isn't very clear in reading the descriptions/OP's,
They wouldn't co-exist if they were exactly the same.
I'm not too interested in tweaking the hell out of my device nor do I care too much about overclocking...I just want a lot of screen time and the ability to play games and SMS with little lag.
I have tried out both kernels and didn't really notice much difference because I didn't really know what to look for.
Like, okay or example, it seems to me that your kernel is less for tweaking and isn't for overclocking (max 1.6GHz or something?) while KToons can go to 2.1.
berryman13 said:
Man why are ya giving me a hard time? You kicked me out of your thread, which I understood and respect, but then you come here and tell me the same thing you told me before and that my thread's gonna go to the bin in no time.
I'm just trying to find out what the DIFFERENCES between the kernels are, because it isn't very clear in reading the descriptions/OP's,
They wouldn't co-exist if they were exactly the same.
I'm not too interested in tweaking the hell out of my device nor do I care too much about overclocking...I just want a lot of screen time and the ability to play games and SMS with little lag.
I have tried out both kernels and didn't really notice much difference because I didn't really know what to look for.
Like, okay or example, it seems to me that your kernel is less for tweaking and isn't for overclocking (max 1.6GHz or something?) while KToons can go to 2.1.
Click to expand...
Click to collapse
I'm not giving you are hard time. I'm just telling you the facts here. If you're not into tweaking and messing with things then this is simple and really shouldn't make a difference to you which one you use other than battery life, less lag, ect... Which no one can tell you one is better than the other for. Flash one and don't touch the settings for it and use it how you normally would for a day or two. Then do the same for the other kernel. See which one gets you the best results. Its the only way to find out. Not quite sure why you're refusing to take my advice here. Its pretty straight forward.
There's kernel source in both threads that explain in DETAIL all the DIFFERENCES between the two. It literally only takes seconds to flash and see for yourself. This shouldn't be a big deal at all.
I think they re two of the same.Task just doesnt want KT to know he borrowed his kernel...lol jk. But seriously,they're pretty similar.KT seems better on the performance end but I never got the exceptional battery stats that ppl keep posting,IdK it may be something on my end. On the other hand, task's seemed better on my battery as I could not noticeably see my battery drain during use as I did on Kt's. Furthermore my phone does get hot really fast on task kernel,I'm guessing its cuz we use performance control and can't really play in the voltages as much.
gilo123 said:
I think they re two of the same.Task just doesnt want KT to know he borrowed his kernel...lol jk. But seriously,they're pretty similar.KT seems better on the performance end but I never got the exceptional battery stats that ppl keep posting,IdK it may be something on my end. On the other hand, task's seemed better on my battery as I could not noticeably see my battery drain during use as I did on Kt's. Furthermore my phone does get hot really fast on task kernel,I'm guessing its cuz we use performance control and can't really play in the voltages as much.
Click to expand...
Click to collapse
Or all or any of that could be due to the apps your have on your device, the settings you choose, ect...
P.S- My phone has never gotten hot. Probably due to what I mentioned above.
task650 said:
If you're not into tweaking and messing with things then this is simple and really shouldn't make a difference to you which one you use other than battery life, less lag, ect... Flash one and don't touch the settings for it and use it how you normally would for a day or two. Then do the same for the other kernel. See which one gets you the best results. Its the only way to find out. Not quite sure why you're refusing to take my advice here. Its pretty straight forward.
There's kernel source in both threads that explain in DETAIL all the DIFFERENCES between the two. It literally only takes seconds to flash and see for yourself. This shouldn't be a big deal at all.
Click to expand...
Click to collapse
I have flashed both kernels. And I don't mean that I am not planning on doing ANY tweaking whatsoever, I just don't mean like messing with voltages adding or subtracting 25 at a time until my CPU crashes so I can find the under/overclock limit...that's the kind of tweaking I have no interest in trying. I'm not gonna look through he sources of both kernels, come on dude you know I'm not a dev and that level of detail is un-necessary.
Your kernel being capped at 1.6GHz probably is better on battery but I also have a sixaxis controller and like to game, does it affect 3D performance at all?
gilo123 said:
Ithey're pretty similar.KT seems better on the performance end but I never got the exceptional battery stats that ppl keep posting,IdK it may be something on my end. On the other hand, task's seemed better on my battery as I could not noticeably see my battery drain during use as I did on Kt's. Furthermore my phone does get hot really fast on task kernel,I'm guessing its cuz we use performance control and can't really play in the voltages as much.
Click to expand...
Click to collapse
This is the kind of posts I'm looking for in this thread. Do you personally find task's kernel's performance to be any worse than KT's? Cause you said bettery life seemed better.
Also, are the same governers and I/O schedules available between both kernels? The only settings I'm used to using is ktoonservative and row, I wouldn't really know what to do in performance control to emulate what I've done in KTweaker.
berryman13 said:
This is the kind of posts I'm looking for in this thread. Do you personally find task's kernel's performance to be any worse than KT's? Cause you said bettery life seemed better.
Click to expand...
Click to collapse
He cannot answer this question honestly. He doesn't have your device. You're not understanding. He can have the best battery life possible on my kernel but if you use it, you could have the worst battery life possible. IT'S DEVICE DEPENDENT. Will you please just do yourself a favor and take 3 seconds, flash the kernel, and see. You say you've tried them both, but you are also asking about playing games and what not with them? You would know if you had tried them dude. Same goes for the governors & schedulers. You would also know that if you had actually tried them both. I need to ask you this. Why won't you just try them and see for yourself. Are you really the type of person to flash what people tell you to your expensive device?
Look dude. I'm only trying to help you here. I'm not quite sure why you wouldn't just take my advice here. I have quite a bit of experience with this stuff and I'm trying to help you get the best experience possible. But it seems as though you think that personal opinions of others are whats best for your device when in all reality they are not. Real life testing is what will prove to be best for your device. Trust me.
berryman13 said:
I have flashed both kernels. And I don't mean that I am not planning on doing ANY tweaking whatsoever, I just don't mean like messing with voltages adding or subtracting 25 at a time until my CPU crashes so I can find the under/overclock limit...that's the kind of tweaking I have no interest in trying. I'm not gonna look through he sources of both kernels, come on dude you know I'm not a dev and that level of detail is un-necessary.
Your kernel being capped at 1.6GHz probably is better on battery but I also have a sixaxis controller and like to game, does it affect 3D performance at all?
This is the kind of posts I'm looking for in this thread. Do you personally find task's kernel's performance to be any worse than KT's? Cause you said bettery life seemed better.
Also, are the same governers and I/O schedules available between both kernels? The only settings I'm used to using is ktoonservative and row, I wouldn't really know what to do in performance control to emulate what I've done in KTweaker.
Click to expand...
Click to collapse
What You won't have on underwear kernel vs kt747: ktoonservative gov, vibration strength control, screen off max freq control, screen off gov control, fast charge, MHz range from 96 to 2106, undervolting capabilities and adjustments to governors and schedulers.
If you don't want to undervolt or tweak anything, I recommend you use underwear kernel. It is stable fast and oc to 1674mhz is alright for any gaming and it doesn't affect 3d performance.
If you wanna use ktoonservative governor then you will have no choice but to use kt747.
But anyway, what you really need is to try both and familiarize yourself with their features.
Sent from my SGH-I747 using xda app-developers app
liltitiz said:
What You won't have on underwear kernel vs kt747: ktoonservative gov, vibration strength control, screen off max freq control, screen off gov control, fast charge, MHz range from 96 to 2106, undervolting capabilities and adjustments to governors and schedulers.
If you don't want to undervolt or tweak anything, I recommend you use underwear kernel. It is stable fast and oc to 1674mhz is alright for any gaming and it doesn't affect 3d performance.
If you wanna use ktoonservative governor then you will have no choice but to use kt747.
But anyway, what you really need is to try both and familiarize yourself with their features.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Comprehensive list. I like it. Now I gotta figure out which gov I'm gonna use when I flash the underwear kernel.
Thanks everybody for their input, if anyone else has anything to say then please go for it!
Wiping cache + dalvik and flashing underwear kernel then fixing permissions and rebooting and gonna take a look around performance control to see whats up.
task650 said:
Or all or any of that could be due to the apps your have on your device, the settings you choose, ect...
P.S- My phone has never gotten hot. Probably due to what I mentioned above.
Click to expand...
Click to collapse
Ohh Thnx man. While you're here any suggestions as to how I go about fixing/finding out which apps are responsible? Also,any combinations/settings you might recommend trying with your kernel,despite the phone dependent variables and what not. Thnx )
Running the underwear kernel today, changes frequencies min and max to the farthest it can go. Will report back with my results.
Sent from my SGH-I747 using xda app-developers app
Sorry man, but no need to report back here as it has already been stated that each User's experience will differ upon usage, apps, personal habits, planet alignment,... Boils down to a flash and see type thing.
Thread Closed
Here is some info on Governor and I/O schedulers. Obviously it isn't going to include Ktoonservative or ROW but you get the idea.

Categories

Resources