Related
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.
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.
Ok im looking at kernels and im not going to ask "whats the best?" but im really not understanding the difference.
What im looking for is a kernel thats stable (that seems like all of them), one that allows under-clock/volting (and any other batter saving tricks) and one that will work well with my rom (XenonHD rc3) as most of the kernels seem to be using anyrom i dont think this is an issue.
i have been using the stock kernel then tinys kernel but im wondering if Zen or Air are going to serve me better?
Here is the order im looking at things
Stability
battery
speed
cosmetics
From what i can tell the governors dont seem to matter much as long as there are a few available (performance, interactive, conservative, power-saver) and the schedulers are even less important as they can handle normal use just fine. SIO or no-op or CFQ all work just fine for me. never tried FIFO but it seems kinda restrictive when multitasking
So from a development standpoint could someone explain whats so different in TINY, ZEN, and AIR i would much appreciate your input. They all seem to start from google source, are the compiled different?
Ok so i am trying Zen and i like that the CPU can be clocked lower. but im still not sure about whats best for me. A comparrison chart would be grand but i have no idea what to compare
The major differences between kernels are what kernel version they're compiled from, what modules are compiled into the kernel, which I/O schedulers are included, and which CPU governors are included. Depending on what the kernel dev has included, the kernel tends to run better or worse on specific devices. Unfortunately, it tends to vary quite a bit even within a single device line.
Zen is the best one I've found yet for my device. Others swear by Franco, Air, Trinity, etc. It's really a matter of trial and error on a device-by-device basis.
Finally, your statement about governors and schedulers not being that important is a bit wrong, in my opinion. Schedulers are definitely the lesser of the two, but depending on your usage, you can get a little bit of an I/O performance increase by using the "right" scheduler. The same thing goes for governors. A properly tweaked governor can save a bit of battery and/or boost your performance. Just like the kernels themselves, though, it would vary device-by-device and based on the user's usage type.
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.
I recently rooted and installed a custom Rom and ElementalEx Kernel. I noticed that the default profiler for the Pixel XL is something called sched which appears to be a fairly conservative governor. I changed it to interactive which I normally use on other phones and battery life suffered considerably. I switched it back to sched and cpu frequencies are much lower but I don't notice any drop in performance. I tried researching sched but haven't found much. Anyone know how this governor works?
Sched is the most efficient governor for our pixel.
The real question is why do you want to change the governor? If you really want some things to mess with to increase battery and/or performance then check out "L speed (boost&battery)" in the play store. And No, this isn't shameless advertising either, the dev is right here in our forums.
noidea24 said:
Sched is the most efficient governor for our pixel.
The real question is why do you want to change the governor? If you really want some things to mess with to increase battery and/or performance then check out "L speed (boost&battery)" in the play store. And No, this isn't shameless advertising either, the dev is right here in our forums.
Click to expand...
Click to collapse
It was a reflex reaction because I'm used to using Interactive and the CPU frequencies seemed really low compared with what I would see on the 6P. Those frequencies on the 6P would result in a noticable performance lag. But I guess the phone design is really different so you can't compare them that way. I'll check out L Speed. Never heard of it. Thanks.
jhs39 said:
It was a reflex reaction because I'm used to using Interactive and the CPU frequencies seemed really low compared with what I would see on the 6P. Those frequencies on the 6P would result in a noticable performance lag. But I guess the phone design is really different so you can't compare them that way. I'll check out L Speed. Never heard of it. Thanks.
Click to expand...
Click to collapse
Same. Coming from the 6p / 5x scene. The best governor was interactive, especially due to all the tweaks and changes that could be applied to the governor (like on ElementalX).
But no, pixel is almost dedicated to sched. I honestly don't think anyone else is running anything else and getting decent results from it
Pixel/XL Uses EAS so governors like Sched, Schedutil etc etc. Meanwhile every other Android device uses HMP your regular governors like Interactive, Ondemand, performance, conservative etc
So it's recommended to use Sched as the defualt but you can learn more about EAS here Also Freak07 has some great info on EAS and it's govenors here
jhs39 said:
It was a reflex reaction because I'm used to using Interactive and the CPU frequencies seemed really low compared with what I would see on the 6P. Those frequencies on the 6P would result in a noticable performance lag. But I guess the phone design is really different so you can't compare them that way. I'll check out L Speed. Never heard of it. Thanks.
Click to expand...
Click to collapse
Same. Coming from the 6p / 5x scene. The best governor was interactive, especially due to all the tweaks and changes that could be applied to the governor (like on ElementalX).
But no, pixel is almost dedicated to sched. I honestly don't think anyone else is running anything else and getting decent results from it
noidea24 said:
Same. Coming from the 6p / 5x scene. The best governor was interactive, especially due to all the tweaks and changes that could be applied to the governor (like on ElementalX).
But no, pixel is almost dedicated to sched. I honestly don't think anyone else is running anything else and getting decent results from it
Click to expand...
Click to collapse
All kinds of us are running schedutil gov on custom kernels. It's the next iteration of EAS sched gov. Better performance than sched.
Yeah same here, I would always use L Speed or some different governor on previous phones than default, cause default was always not the most efficient, both performance and battery backup wise, but on Pixel there is no need. In fact devs have suggested us to use the default Sched governor, so I am sticking with it.
Anyone on ElementalEx change any settings other than the governor to improve performance on the Pixel XL? A lot of the available settings are different than I'm used to.
Hi, everyone I'm s7edge owner would like to use a the Google pixel governor, can someone show me the direction please? Thanks
lovetv said:
Hi, everyone I'm s7edge owner would like to use a the Google pixel governor, can someone show me the direction please? Thanks
Click to expand...
Click to collapse
Not possible without an EAS compatible ROM/Kernel
ithehappy said:
Yeah same here, I would always use L Speed or some different governor on previous phones than default, cause default was always not the most efficient, both performance and battery backup wise, but on Pixel there is no need. In fact devs have suggested us to use the default Sched governor, so I am sticking with it.
Click to expand...
Click to collapse
I think the devs suggest using the sched governor because they are either too lazy or not knowledgeable enough to create other governors that are compatible with the Pixel. The sched governor is far from efficient. It's clearly a performance based governor and it allows the Pixel battery and CPU to get very hot very quickly. The Pixel CPU can get to 130F just performing what most people would consider standard tasks on their phones. I'm not even talking about gaming or anything remotely CPU intensive. How long do you think these phones are actually going to last when they heat up so much?
What's the difference between sched and schedutil? I saw schedutil is default on the ElementalX for !y Pixel 2 XL.