So I recently been running KT747 kernel on my GS3 with AOKP JB M1. Battery life is ok (all settings default except for I/O=noop, Governor = Ktoonservative). I found out that the T-Mobile GS3 LeanKernel also works on this. Has anyone tried it? Is it good? Heard most people get good battery on it, but then again it varies from user to user.
Edit---*
Tested out a few different settings. I under volted using the mv's listed in the original KT747 thread... phone rebooted constantly, guess my phone can't go volt down too much . I'm going to run deadline + ktoonservative for a day and see if it's any better.
In all reality no one can answer this for you. If you think about it, we all have different settings, different apps on our device, we live in different locations, and we all use our phones differently. So one guy could say he gets awesome battery life on ktoonsez's kernel while the next guy says it sucks. That's just the name of the game. All devices are not created equally especially in realm of the kernel world. There are just too many variables. So asking this unfortunately will not get you any closer to your answer. You just gotta take a few minutes to try them out for yourself to figure out which works best for your device.
Do you know the difference between Ktoonservative and Conservative Governor?
DarthDerron said:
Do you know the difference between Ktoonservative and Conservative Governor?
Click to expand...
Click to collapse
I definitely do. You should also. You just need to take a little time and go through the OP of the kernel thread. All the information you need/want is right there. look here dude
I've tried a few kernels and I always go back to the CM10 kernel it gives me by far the best battery life out of every kernel out there that I have tried.
Even with the SGS2 i9100, CM9 kernel was always my favorite, just because of how superior the battery life was.
task650 said:
I definitely do. You should also. You just need to take a little time and go through the OP of the kernel thread. All the information you need/want is right there. look here dude
Click to expand...
Click to collapse
Thanks so much, didn't read his Extras post. I also looked up what each governor does earlier, and realized that there was also Ktoonservative which wasn't on the list I was reading. Thanks for the answer You're one of the nicest and most helpful dev's out there task.
I found CM10 kernel's battery life to be a hit and a miss. Some days it would be good, others would be bad. KT747 has been more consistent for me
Sent from my SGH-I747 using xda app-developers app
DarthDerron said:
I found CM10 kernel's battery life to be a hit and a miss. Some days it would be good, others would be bad. KT747 has been more consistent for me
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Battery life is only OK on kt747 because your running noop and ktoonservative. I'm running deadline and abyss and getting great results. If you would like these settings let me know, these screenshots will say it all:
AT&T SGS3
ParanoidKangDroid 1.1.0 ROM
KT747 10/31 OC'ed & UV'ed
Medical MJ Supporter
Dankest said:
Battery life is only OK on kt747 because your running noop and ktoonservative. I'm running deadline and abyss and getting great results. If you would like these settings let me know, these screenshots will say it all:
AT&T SGS3
ParanoidKangDroid 1.1.0 ROM
KT747 10/31 OC'ed & UV'ed
Medical MJ Supporter
Click to expand...
Click to collapse
Definitely not true. Those settings are good for your device. It doesn't mean it will be good for him. Every single device reacts differently to different settings. I've gotten horrible results with those settings if that says anything. That's the thing about this device and kernels. They all take well or worse to different governors, schedulers, voltages, etc...
task650 said:
Definitely not true. Those settings are good for your device. It doesn't mean it will be good for him. Every single device reacts differently to different settings. I've gotten horrible results with those settings if that says anything. That's the thing about this device and kernels. They all take well or worse to different governors, schedulers, voltages, etc...
Click to expand...
Click to collapse
That's an interesting post to mull over. One would think because Samsung rolls out the same Chips with the us version that you would get roughly the same results, I had heard about the voltage differing (because of the silicon thickness). but not about phones reacting differently to schedulers and governors. This will require more looking into! I do enjoy a good read. Thanks for correcting me, I do like to get the facts straight before helping others.
But putting user use aside(what you do on your phone), if your phone was 100%-0% idle you should expect the same (roughly) result when using the same govs& schedulers as someone else with the same phone correct?
AT&T SGS3
ParanoidKangDroid 1.1.0 ROM
KT747 10/31 OC'ed & UV'ed
Medical MJ Supporter
Dankest said:
That's an interesting post to mull over. One would think because Samsung rolls out the same Chips with the us version that you would get roughly the same results, I had heard about the voltage differing (because of the silicon thickness). but not about phones reacting differently to schedulers and governors. This will require more looking into! I do enjoy a good read. Thanks for correcting me, I do like to get the facts straight before helping others.
AT&T SGS3
ParanoidKangDroid 1.1.0 ROM
KT747 10/31 OC'ed & UV'ed
Medical MJ Supporter
Click to expand...
Click to collapse
Yep. It kinda sucks that they differ so much between devices. It varies so much that some people can't even use ktoonsez's kernel at all. Some of those that couldn't use his kernel in particular returned their device for a replacement and then were able to use it with their replacement. Its pretty unfortunate in my opinion.
task650 said:
Yep. It kinda sucks that they differ so much between devices. It varies so much that some people can't even use ktoonsez's kernel at all. Some of those that couldn't use his kernel in particular returned their device for a replacement and then were able to use it with their replacement. Its pretty unfortunate in my opinion.
Click to expand...
Click to collapse
Yes I've heard a few people saying the exact same thing, its unfortunate that you think your buying a quality device when in fact were buying a hunk of metal and plastic. Guess I just drew the long straw when it comes to luck.
AT&T SGS3
ParanoidKangDroid 1.1.0 ROM
KT747 10/28 OC'ed & UV'ed
Medical MJ Supporter
ComradeNF said:
I've tried a few kernels and I always go back to the CM10 kernel it gives me by far the best battery life out of every kernel out there that I have tried.
Even with the SGS2 i9100, CM9 kernel was always my favorite, just because of how superior the battery life was.
Click to expand...
Click to collapse
The CM Kernel SUCKED for me!!! My phone ran really hot w/ not too much of a load on the CPU & my battery life sucked!!! I use KT 747 w/ some undervolting & it runs GREAT now!
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
I am giving Lean Kernel a shot after having ran KT747 for a few days. Not sure why but my phone didn't take too well with KT747. Too many random reboots and what not. However my battery life (even with the reboots, etc) was awesome. I say give both kernels a try. That's the only sure-fire way to see if you device likes one better than the other.
Dankest said:
Battery life is only OK on kt747 because your running noop and ktoonservative. I'm running deadline and abyss and getting great results. If you would like these settings let me know, these screenshots will say it all:
AT&T SGS3
ParanoidKangDroid 1.1.0 ROM
KT747 10/31 OC'ed & UV'ed
Medical MJ Supporter
Click to expand...
Click to collapse
Sorry been sorta AFK with this post, man those are some crazy results. But as Task said, differs from every device. I've used other people's settings and have gotten horrible results in terms of battery life and random reboots. I only get around 3 hours of onscreen time which makes me a sad panda, but I'm still changing the effects constantly. I found that leaving stock voltage actually got me better battery life.
I've tried both kt747 and leankernel and found both seemed better than whatever the stock kernel in Slimbean is. For me, LK seems to work better and I am getting great performance and battery (15 hrs battery with 4hrs of screen, 24+ hrs with light usage). LK uses SIO/InteractiveX.
Thinking of trying out ktoonsez and task's AOKP...hearing good things and have not tried an AOKP ROM yet since rooting my phone.
12packabs said:
I've tried both kt747 and leankernel and found both seemed better than whatever the stock kernel in Slimbean is. For me, LK seems to work better and I am getting great performance and battery (15 hrs battery with 4hrs of screen, 24+ hrs with light usage). LK uses SIO/InteractiveX.
Thinking of trying out ktoonsez and task's AOKP...hearing good things and have not tried an AOKP ROM yet since rooting my phone.
Click to expand...
Click to collapse
I've used both task's AOKP and the official rom, both are good. For me, LK+KT seemed to be almost the same, but I believe LK had lower idle consumption, despite KT having a limited mhz while screen is off option. I don't like slim bean too much though, just preference.
DarthDerron said:
I've used both task's AOKP and the official rom, both are good. For me, LK+KT seemed to be almost the same, but I believe LK had lower idle consumption, despite KT having a limited mhz while screen is off option. I don't like slim bean too much though, just preference.
Click to expand...
Click to collapse
I see you are runnnig LiquidSmooth which I haven't tried. What do you like about that ROM? I keep trying other ROMs and going back to Slim.
DarthDerron said:
Sorry been sorta AFK with this post, man those are some crazy results. But as Task said, differs from every device. I've used other people's settings and have gotten horrible results in terms of battery life and random reboots. I only get around 3 hours of onscreen time which makes me a sad panda, but I'm still changing the effects constantly. I found that leaving stock voltage actually got me better battery life.
Click to expand...
Click to collapse
Undervolting isn't meant for battery though, people who undervolt usually do so for two reasons.
One, extending cpu life span
Two, less generation of heat for overclocking.
Yes undervolting does effect battery life but it is so small that is really wouldn't make a big difference.
As for adjustment results yes there are a lot of factors. they mainly have to do with what the users does while using the phone. As well as settings for brightness, backlight buttons, etc. That is how everyone differs. If your phone sat idle 100 to 0% you should (roughly) get the same results as someone else running the same set up. But then again who the hell does that anyways?
AT&T SGS3 Marble White
Team AoCP The Collective ROM
KT747 10/31 OC'ed & UV'ed
Medical MJ Supporter
12packabs said:
I see you are runnnig LiquidSmooth which I haven't tried. What do you like about that ROM? I keep trying other ROMs and going back to Slim.
Click to expand...
Click to collapse
I enjoyed LiquidSmooth a lot, but I wanted to try Paranoid Android for a bit, so I'm running that now. Forgot to update my signature. LS is really smooth, one of my fav's next to AOKP.
Related
Im stone stock right now. Do you see an actual improvement in apps that need the extra O/C HP? I have one game I bought that seems to be a little choppy at times, 9mm HD, and Im not sure if its the games coding, the fact that it maybe having a problem with ICS, or just not enough hardware HP to be fluid.
I OC'ed when I first got the phone but quickly dropped it back to 1200. This phone doesn't need overclocking and if you are noticing lag in games it is most likely due to poor coding by the dev for either ICS or dual core phones or both. If it is lagging on a 1.2 GHz dual core and it is our hardware think about people running it on the Inc 2 with a 1 GHz single core processor and basically last years tech. Our phones should be fine to run most if not all games for about a half year or maybe a year before OCing will really be needed.
Why don't you just do it and find out? It's really hard to tell because no kernel is a stock kernel with 1.35 GHz / 1.4 GHz.
All these kernels featuring OC have additional features which means that it could be the features/tweaks that are fixing it rather than the OC itself.
zephiK said:
Why don't you just do it and find out? It's really hard to tell because no kernel is a stock kernel with 1.35 GHz / 1.4 GHz.
All these kernels featuring OC have additional features which means that it could be the features/tweaks that are fixing it rather than the OC itself.
Click to expand...
Click to collapse
Well,...Im just pretty content with how it performs in every other aspect, except for this one game bugs me a little. Ive been ROMed and O/Ced on this not too long ago, and TBH, theres always some sort of little thig that turns me off about it. A spontaneous reboot here, a F/C there, and I find myself going stock again. I would do it in a heart beat if it didnt mean having to set every last detail back up again when I unlock the phone.
And yes, being virtually OCD about this phone sucks, lol.
I have a question as well!
For those under-clocking or using UV kernels, do you see a noticeable improvement in battery life? I have a GSM sock GNex and the battery life is atrocious.
stevessvt said:
Well,...Im just pretty content with how it performs in every other aspect, except for this one game bugs me a little. Ive been ROMed and O/Ced on this not too long ago, and TBH, theres always some sort of little thig that turns me off about it. A spontaneous reboot here, a F/C there, and I find myself going stock again. I would do it in a heart beat if it didnt mean having to set every last detail back up again when I unlock the phone.
Click to expand...
Click to collapse
Should of unlocked the bootloader day one before playing with the phone your phone still remains stock. Just the bootloader is unlocked, you'll virtually feel no difference. Except the fact that you have to relock for warranty purposes later but you'll wipe everything so that is always good because you don't want to exchange a phone with all of your passwords.
@andythefan: Yes there is a huge battery difference. Visit the Franco Kernel thread in GSM forums for people's images of battery history.
Flash the James Bond kernel so your gpu will be upped to 384mhz. It is in the development section.
My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.
@rbiter said:
Flash the James Bond kernel so your gpu will be upped to 384mhz. It is in the development section.
My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.
Click to expand...
Click to collapse
Other kernels also have this feature. A lot of them do.
@stevessvt: In the myriad different combo's I've flashed (ARHD, Franco kernel, APex Kernel, bigxie ROM, AOKP rom, stock kernel, OC/No OC, Unvervolting, and 1 other kernel I can't even remember) I've yet to encounter a single random reboot, FC, or battery pull. I've also flashed countless different mods and basebands, etc.
It's all about doing your homework and really reading through threads before flashing and making sure different stuff is compatible and doing nandroids.
I can honestly say running a non-stock rom/kernel makes a noticeable difference in response and performance in daily use. Its really all the Kernel IMO, ROM's just give you features. I've however never noticed anything from OCing.
@andyfan: what build are you on? 4.0.2 has the hands down best battery life, and 4.0.3 with the Franco Kernel is nearly as good as 4.0.2 was (4.0.2 for me meant ~3% drain in 8 hours)
andythefan said:
I have a question as well!
For those under-clocking or using UV kernels, do you see a noticeable improvement in battery life? I have a GSM sock GNex and the battery life is atrocious.
Click to expand...
Click to collapse
For now any phone usage will give you terrible battery life due to the high power consumption of the screen especially if when it displays white onscreen content. Average CPU usage is very low unless you're running benchmarks consistently. Therefore UV tweaks have low impact on usage battery life.
With that said if your battery is irregularly draining while idle something may be active in the background.
Franco has made many tweaks to his kernel to reduce idle power consumption. He's gotten it down to about less than 1% drain per hour which can give you over 2 days of idle battery life. Just for ****s and giggles I have achieved that with less than 30 minutes of screen time with LTE enabled.
Franco's kernel is the best I've used in terms of overall battery life but none of the OC/UV kernels have significantly increased my usage battery life.
Sent from my Galaxy Nexus using XDA App
Which one do u perfer guys ? Both are awesone and cant make a decision Battery life ? Hotplug efficiency? Performance ?
Sent from my Galaxy Nexus using XDA App
I'm getting crazy good battery life and performance on lean kernel and AOKP. Franco is good too, but I think I'm getting much better battery life on lean.
Each phone is different find out your preference on your own
Sent from my Galaxy Nexus
James Bond kernel.
I've seen what franco has done with the nexus s kernel, realiable, smooth, and constant updates, it was always my choice. So as soon as i get my GN its the first kernel i'm going to flash and hopefully it won't ever disappoint
same for me. I have a freaking good battery life on lean but better performance with Franco
cvbcbcmv said:
I've tried both for a great while. Battery life with interactivex on lean and hotplug on franco lean is definitely better, on my phone Lean runs a little bit better. on my phone.
Click to expand...
Click to collapse
Sent from my Galaxy Nexus using XDA App
I found a few kernels in the dev section but couldnt find the lean one. Can you guys posts the link or more info on it. Nothing i found says lean on it. Please and thank you
GeLopez said:
I found a few kernels in the dev section but couldnt find the lean one. Can you guys posts the link or more info on it. Nothing i found says lean on it. Please and thank you
Click to expand...
Click to collapse
its Imoseyon kernel on Rootzwiki. btw, Ive tried both Lean and Franco kernel, I still prefer Ezekeel Glados kernel though. amazing smooth and friendly battery life.
I was using franco's kernel, but with all the hourly updates lately, it spooked me a little, so now Im on trinity inferno512 kernel, and wow games run fluid with the GPU at 512mhz.
im still debating... im jumping back and forth but i need to stick to one for a week and try it out!
leankernel has updates just as much as franco... i say thats a good thing
i say take a week long test and run some benchmarks with each of those kernels, take a screenshot, and come back with what you like.
Im working on that now.
GLaDOS is by far the best kernel for my phone. No lags whatsoever and four hours of screen on time with the stock battery
I'm starting to lean toward glados myself. I've had a lot of issues with Franco's 14.x kernels.
I've also found lean kernel to be a bit choppy. Shadow gun runs really choppy w lean kernel, but ultra smooth w either Franco and glados. It could be that I'm not using the correct governor though.
I have tried both back and forth. AS of last update I've tried franco 14.4 (deep sleep ~50%) which is good but has a much better battery life (deep sleep at 91%) on hotplug of lean 1.8.0.
+1 for lean
I have used lean kernel for a while now. I used to get lots of lock screen lag with Franco. Which I don't with lean.
Sent from my Galaxy Nexus using xda premium
Im on Leankernel 1.7.3 right now. Used Francos way before, but after Version 13.1 i started to get battery drain issues. So i switched over to Glados which seemed to have a good battery life to me, but was very choppy overall on Wheatley Gov'.
Lean is the best for me at the moment, almost 4 Hours Screen on time isnt a problem for me, i use the build in InteractiveX Governour, with some heavy undervolting. Data, Sync, Wifi , ... everything enabled. Screen Brightness ~ 35%
I gonna try Lean 1.8.0 Later that day. But i have to admit that Franco's next upcoming with Turtle Governor might be an interessting choice either.
For me, both devs are doing a really great job, both Kernels are good.
I've used three different Franco kernels and had freezing and reboot issues with all three of them. Never had an issue with Lean Kernel.
I don't care what kernel I have. If:
1.At the end of the day on my normal usage phone has less than 60% of battery left it means that the next day I won't manage
2. I have less than 60% I have to recharge overnight
3. Phone can get me throughout the day on heavy usage ...
Don't need any fancy kernels if they don't tick the first box
Edit:
Just tried lean kernel and its way to slow. Scrolling in text app or anywhere really isn't even half as smooth as Franco ....
Sent from my Galaxy Nexus using xda premium
After trying many kernels... I always come back to Faux123's kernel (Currently 011b10u). It's just such great battery life... idle battery drain is just a horizontal line on the battery graph for hours. LOVE IT. (P.S. Ultra-liquid-smoothness too). http://rootzwiki.com/topic/12512-kernelgn-lte3017ics4023uvgpucpu-occifsslqbotgfiopsv010jan-17/page__st__930
MattSkeet said:
Just tried lean kernel and its way to slow. Scrolling in text app or anywhere really isn't even half as smooth as Franco ....
Click to expand...
Click to collapse
Which text app are you referring to that us siow? I'm using the LeanKernel and not really noticed anything.
jhericurls said:
Which text app are you referring to that us siow? I'm using the LeanKernel and not really noticed anything.
Click to expand...
Click to collapse
Stock.... smooth as butter on Franco's. Lean even on home screen wash stuttering ...
Sent from my Galaxy Nexus using xda premium
Hey I want to know how KT747 kernel works with AOKP Ktoonsez and Task650. From what I hear its pretty good. My main concern is battery life. I heard some people get around 5 hours of onscreen time which is incredible. If you are running these two together, what are good settings for good battery life? I'm using KT747 with CM10 M2 and Ktoonservative/noop but battery life is kinda bad. Thanks
I'm running that setup and although i can't really compare my battery stats to your as i have a 4400mah battery, i can say that for my phone atleast the battery life is superb. I actually just plugged it in after 67 hours, with about 7 hours screen on time. Obviously this isn't going to happen on a stock battery (mine came with a 2100mah), you could realistically expect a little less than half these numbers. I would suggest taking a look at this thread, which discusses overclocking and undervolting settings. I have posted pics of my personal undervolting settings (page 15, post 150), however your device may differ. I discuss why and my suggested method to finding the best value's for your device in the same thread, post 152 on page 16. Of course the discussion has many other opinions and suggestions as well so try them out until you find the one that works best for you. One thing i didn't mention is to disable the cpu settings in the settings>rom control>performance menu as it will conflict with the settings in ktweaker and can actually drain the battery much faster than normal.
dntesinfrno said:
I'm running that setup and although i can't really compare my battery stats to your as i have a 4400mah battery, i can say that for my phone atleast the battery life is superb. I actually just plugged it in after 67 hours, with about 7 hours screen on time. Obviously this isn't going to happen on a stock battery (mine came with a 2100mah), you could realistically expect a little less than half these numbers. I would suggest taking a look at this thread, which discusses overclocking and undervolting settings. I have posted pics of my personal undervolting settings (page 15, post 150), however your device may differ. I discuss why and my suggested method to finding the best value's for your device in the same thread, post 152 on page 16. Of course the discussion has many other opinions and suggestions as well so try them out until you find the one that works best for you. One thing i didn't mention is to disable the cpu settings in the settings>rom control>performance menu as it will conflict with the settings in ktweaker and can actually drain the battery much faster than normal.
Click to expand...
Click to collapse
Thanked*. Will take a look at the thread. Last time I undervolted I used some guys settings which were extremely wonky and cause a lot of mishaps. I'm still looking for good ones so I might try yours. Thanks.
DarthDerron said:
Thanked*. Will take a look at the thread. Last time I undervolted I used some guys settings which were extremely wonky and cause a lot of mishaps. I'm still looking for good ones so I might try yours. Thanks.
Click to expand...
Click to collapse
Sounds like too much undervolt.
jethro650 said:
Sounds like too much undervolt.
Click to expand...
Click to collapse
Just tried it, it was a little to much so I bumped everything up a little bit. Seems fine now. Going to flash AOKP later today.
Thats actually how i got those settings, i used what someone said was stable on theirs. It wasn't, playing pretty much any game on my phone would cause a reboot in less than 5 minutes. I think i ended up about 20 mv higher on all steps than his settings. You just have to find what works for you phone.
dntesinfrno said:
Thats actually how i got those settings, i used what someone said was stable on theirs. It wasn't, playing pretty much any game on my phone would cause a reboot in less than 5 minutes. I think i ended up about 20 mv higher on all steps than his settings. You just have to find what works for you phone.
Click to expand...
Click to collapse
Indeed. I have AOKP with Ktoonsez/sio and voltage a little higher than yours. Works fine, battery is good.
I have recently switched to the noop scheduler after an article i read which basically said there is no need for a scheduler using flash memory. All the other schedulers are designed for physical hard drives which have seek times, flash does not. Using these schedulers actually creates an artificial seek time, thereby wasting cpu clock cycles and burning precious energy in the process.
dntesinfrno said:
I have recently switched to the noop scheduler after an article i read which basically said there is no need for a scheduler using flash memory. All the other schedulers are designed for physical hard drives which have seek times, flash does not. Using these schedulers actually creates an artificial seek time, thereby wasting cpu clock cycles and burning precious energy in the process.
Click to expand...
Click to collapse
Was always on noop and ktoonservative. Most people recommend those two together
Boss-njo said:
That rom is no go.
Click to expand...
Click to collapse
Care to elaborate?
Boss-njo said:
That rom is no go.
Click to expand...
Click to collapse
I think its pretty good. I find it more stable than other roms, imo.
KT747/Cm10 m2
Hi,
I installed Cm10 m2, then ran it, rebooted, and installed kt747, cleared caches and fixed permissions, could not boot afterwards, Anyone else have this problem?
Mitch.sc said:
Hi,
I installed Cm10 m2, then ran it, rebooted, and installed kt747, cleared caches and fixed permissions, could not boot afterwards, Anyone else have this problem?
Click to expand...
Click to collapse
Hmm, I've never had that problem with KT. Make sure you have correct version, AOSP JB. I would recommend flashing CM10.0.0, the latest CM10 stable build.
Hi guys,
I've got a Galaxy S3 via Rogers, rooted, running the rom Triune II, I haven't messed around with custom Kernals (tbh haven't figured that out really), I recently installed SetCPU to overclock my S3 for running graphic intensive/slow loading games like Asphalt 7, etc.
So far for that purpose it's been amazing, the games literally open twice as fast. I've setup SetCPU for a variety of CPU changes, ie. higher speeds for graphic intensive games, lower speed for screen off while charging (ie. overnight) and it seems to be working great.
My questions are:
Can "overclocking" damange my device? Ie. I know that obviously overclocking shreds through battery life, but is playing a game at the top speed available on SetCPU (1512 Mhz) bad over a prolonged period?
Also, am I not reaping the full benefits of over/underclocking having a custom kernal installed?
Also...nother totally n00b one, if the S3 is capable of reaching the "overclocked" max speed, why doesn't it in the stock ROM? I just don't quite get that....is it because the battery life would be terrible and people would blame Samsung for it?
Never had a issue overclocking. And I've overclocked every phone I've owned beside the iPhone.
As far as how much better it will make your phone it depends. Depends on the rom too. I've noticed better benchmark results yet not always better real world results.
I use it more for the ability to underclock, and overclock when necessary.
Sent from my SGH-I747 using xda app-developers app
a little off but do you know of a way to measure the temperature of the phone (when you overclock/or even normally) ?
My phone does heat up sometimes
For over/underclocking there must be support for it built in kernel ! So if stock kernel doesn't support it you cannot probably change frequencies without changing kernel on stock Rom !
Also read the kernel's documentation - stable frequencies will be listed there - jumping back and forth these frequencies won't cause any troubles apart from the obvious battery drainage depending on your settings
Sianspheric said:
Hi guys,
I've got a Galaxy S3 via Rogers, rooted, running the rom Triune II, I haven't messed around with custom Kernals (tbh haven't figured that out really), I recently installed SetCPU to overclock my S3 for running graphic intensive/slow loading games like Asphalt 7, etc.
So far for that purpose it's been amazing, the games literally open twice as fast. I've setup SetCPU for a variety of CPU changes, ie. higher speeds for graphic intensive games, lower speed for screen off while charging (ie. overnight) and it seems to be working great.
My questions are:
Can "overclocking" damange my device? Ie. I know that obviously overclocking shreds through battery life, but is playing a game at the top speed available on SetCPU (1512 Mhz) bad over a prolonged period?
Also, am I not reaping the full benefits of over/underclocking having a custom kernal installed?
Also...nother totally n00b one, if the S3 is capable of reaching the "overclocked" max speed, why doesn't it in the stock ROM? I just don't quite get that....is it because the battery life would be terrible and people would blame Samsung for it?
Click to expand...
Click to collapse
Yes overclocking can damage your cpu from overheating, some even believe it may reduce the lifespan of you cpu.
If you are running 1512 max you are running stock mhz, that isn't overclocked. You cannot run a stock Sammy kernel and overclock it unless it's been recompile..to be overclocked.
I recommend ktoonsez kernel it can be overclocked to 2106mhz and underclocked to 96mhz. As well as undervolting support which is pretty much essential for overclocking because an undervolt will make your phone produce less heat by lowering the voltage your phone requires when running.
To answer your second question, yes you are not reaping any benefits without a custom kernel, this is evident.
To answer the last. The stock kernel is maxed at 1512 because that is the best mhz for the STOCK Sammy kernel performance and battery wise. Also its possible that overheating happened when they set the max at higher mhz during their tests.
Some good general knowledge if you decide to overclock, would be learning how to and what undervolting does for your phone. You can read up on that here:
http://forum.xda-developers.com/showthread.php?p=33282284
Ktoonsez kernel thread: http://forum.xda-developers.com/showthread.php?p=28399829
Make sure you download the right one for your rom!
If after reading about undervolting and installing kernel and would like some safe undervolting and gov/scheduler settings let me know! You can also find many other settings here:
http://forum.xda-developers.com/showthread.php?p=31539830
AT&T SGS3 Marble White
Team AoCP The Collective ROM
KT747 10/31 OC'ed & UV'ed
Medical MJ Supporter
Sorry that kernal thread is a bit confusing.
Does that Kernal only exist for the stock carrier ROM and CM?
I'm using Triune II, if the kernal doesn't exist for that ROM then I take it I have to change ROM's?
Sianspheric said:
Sorry that kernal thread is a bit confusing.
Does that Kernal only exist for the stock carrier ROM and CM?
I'm using Triune II, if the kernal doesn't exist for that ROM then I take it I have to change ROM's?
Click to expand...
Click to collapse
No. Triune is a TW based ROM. Therefore, you need to download KToonsez TW kernel. Keep in mind there is a ICS TW kernel, and then there is a JB TW kernel.
There are other kernels out there. Faux123 has a good one. It is capable of OC to 1.8Ghz, I believe.
Sianspheric said:
Sorry that kernal thread is a bit confusing.
Does that Kernal only exist for the stock carrier ROM and CM?
I'm using Triune II, if the kernal doesn't exist for that ROM then I take it I have to change ROM's?
Click to expand...
Click to collapse
Download the one titled touchwiz and whatever version you are running be it ice cream sandwich touchwiz, or jellybean touchwiz.
AT&T SGS3 Marble White
Task & Ktoonsez AoKP ROM
Ktoonsez 11/13 Kernel OC'ed
Medical MJ Supporter
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.