Related
Hello - this is a pretty n00bish question but I have had a hard time finding the exact answer I was looking for on this threads and on Google. The Thunderbolt is my first Android phone, and I got it last week and already rooted it with Das BAMF Remix 1.6.3. I also have WidgetLocker, Launcher Pro, and other programs to really customize the phone. I was playing around with the DAS Bamf Toolkit and I was noticing the CPU and governor settings. I was wondering what CPU settings and governor settings people use? Right now I have the default, which is 1.037 Ghz at max frequency, 245 Mhz at min frequency, and using the ondemand governor. I have seen a lot of people use the smartass governor, and I was wondering what the difference does - especially between interactive and conservative (powersave and performance I can guess at what they specialize in). What would be the best settings for optimizing battery life while still having good performance? I know a lot of people say to do your own testing and find out what works best for your phone and your needs, but I am just curious at what other people work at and how they like their settings.
Another question I have it about different kernels. Right now I am using the kernel that came with Das BAMF Remix 1.6.3 (2.6.32.21.bamf_4.4.7-g21c0620-dirty (by a adrynalyne #1)), but I know some people have been using Imoseyon's kernels. Do people find their phone more or less stable when using Imoseyon's kernel on Das BAMF instead of using adrynalyne's kernel? (I figured since he was one of the people who developed Das BAMF, his kernel would work best, but it seems to me a lot of people have been mixing/matching).
One final random question that I thought of while writing this thread, I also only ever flashed Das BAMF Remix 1.6.3; I never flashed any new radio or anything like that because at first I assumed it came with the ROM, but reading some threads on the forum, it seems that comes separate, and I am not sure if the stock/leaked radio is better/worse for battery or if it works with the ROM.
Again, sorry if these sound like very amateur questions but I just want some clarifying on these things and any help would be greatly appreciated. Thank you very much!
Other information about my phone:
Android Version: 2.2.1
Baseband Version: 1.16.00.0402w_1
Kernel Version: 2.6.32.21.bamf_4.4.7-g21c0620-dirty (by a adrynalyne #1)
Build Number: 1.13.605.7_Das_BAMF_Remix_1.6.3
Software Number: 1.13.605.7
Expiramenting with what combination works for you is the best idea, HOWEVER, always backup what works, and make sure you have the right radio for the ROM you're flashing. Three quarters of what makes this fun is funding out what will and will not make your phone better. The other half is learning how to fix what you just broke.
Also, In my expierience, overclocking to anything over 1.6ghz causes problems.
Sent from my super duper deluxe rooted re-romed Thunderbolt. ( and yes, it can also wash my car AND do the dishes)
heres a list of readios ---> http://forum.xda-developers.com/showthread.php?t=1045081 im on das bamf 1.6.3 with the first one on this list and it works great. also im on that same kernel overclocked to 1280 max and 368 min and i have great speed and battery life (also using setcpu and underclocking to 368 max when screen off so thats probably why ). using the ondemand governer. never tried smart ass but heard good things. the conservative is good for saving battery i use it on my screen off profile.
Awesome, I am going to try to flash that radio... Is it bad that I am not flashing it around the time I flashed the ROM, or would that still be fine? And again, I am sorry if this next question sounds amateur, but to flash it, I would just copy the PG05IMG.zip to my SD Card, reboot my phone in Bootloader (or Recovery?) and install the radio from there (assuming I first wipe the cache/dalvik, or do I need not to do that for radio?).
My battery life is fine, I have the extended battery and I get about 31 hours (but I am on Wi-Fi a lot instead of 3G, which I heard is better for battery, and I am not that heavy of downloading/games), but I heard people getting 2+ days, so maybe flashing this newer radio may show improvements, who knows, ha.
I will have to download SetCPU, because at first I thought you can only change the CPU settings on the Das BAMF Toolkit, but it looks like SetCPU has a lot more options. Dak_181, when you say you have great battery life/speed, how much out of your battery do you get?
BACKUP when making these changes. 10 minutes can save you an hour.
Right, I use Nandroid and Titanium Backup - if I were to flash a new radio as well as Imoseyon's 2.5.1 kernel, should there be an order I do it in (radio first, then kernel, or kernel first, then radio?), or does it not matter?
smartass is interactive gov with some tweaks (interactive makes the CPU clock up faster when you interact with the screen) and basically does a conservative screen off automatically. i think the max clock speed on the TB Is like 400 while the screen is off. i might be wrong on that number but you get the idea.
Zepius said:
smartass is interactive gov with some tweaks (interactive makes the CPU clock up faster when you interact with the screen) and basically does a conservative screen off automatically. i think the max clock speed on the TB Is like 400 while the screen is off. i might be wrong on that number but you get the idea.
Click to expand...
Click to collapse
InteractiveX sets the cpu @ about 250 ish when the screen is off. That is the lowest idle state for the most part, I did however see some testimg trying to get 184mhz to work.
Sent from my ADR6400L using XDA App
Aup808 said:
Awesome, I am going to try to flash that radio... Is it bad that I am not flashing it around the time I flashed the ROM, or would that still be fine? And again, I am sorry if this next question sounds amateur, but to flash it, I would just copy the PG05IMG.zip to my SD Card, reboot my phone in Bootloader (or Recovery?) and install the radio from there (assuming I first wipe the cache/dalvik, or do I need not to do that for radio?).
My battery life is fine, I have the extended battery and I get about 31 hours (but I am on Wi-Fi a lot instead of 3G, which I heard is better for battery, and I am not that heavy of downloading/games), but I heard people getting 2+ days, so maybe flashing this newer radio may show improvements, who knows, ha.
I will have to download SetCPU, because at first I thought you can only change the CPU settings on the Das BAMF Toolkit, but it looks like SetCPU has a lot more options. Dak_181, when you say you have great battery life/speed, how much out of your battery do you get?
Click to expand...
Click to collapse
it doesnt matter when you flash the radio, and you dont need to wipe data or cache. to install put it on the root of your sd card and reboot into.. recovery? whichever one you get to by powering off then holding down volume and power untill it starts up. it will find the update and install it automatically then reboot. make sure to delete it from sd card right away or youll get problems next time your flash anything. and i got about 15 hours with the stock battery and pretty consistence use in a low coverage area (bouncing between 1x and nothing all day).
15 hours with NO 4G I presume? I got about 8 hours of medium use in a good 4G coverage area. I am running BAMF 1.63 with BAMF Toolkit CPU on SmartAss gov. No overlooking.
Does it make a big difference to install the kernel first or the radio first? Also, does anyone think they find better results using Imoseyon's 2.5.1 kernel on Das BAMF Remix 1.6.3, or do they find using the stock kernel for that is best since it was made for that ROM?
And thanks for all the help about installing!
I am getting ridiculously good battery life and performance with Das Bamf 1.6.3 and Imoseyon's leankernel 2.5 running on extreme with custom undervoltage and interactiveX governor.
One of the key contributors to my battery life is the custom undervoltage. The leankernel extreme is already undervolted, but to be compatible with more TBs it isn't undervolted as much as it can be. After the tweaks i made, which included setting the min clock speed to 368 since I have it using the same low voltage as 245 (750 mv).
I have heard that smartass also gives great battery life with imoseyon's kernel, but since interactiveX has been so good I have had no desire to switch.
I hope that helps!
lanwarrior said:
15 hours with NO 4G I presume? I got about 8 hours of medium use in a good 4G coverage area. I am running BAMF 1.63 with BAMF Toolkit CPU on SmartAss gov. No overlooking.
Click to expand...
Click to collapse
thats right. it was part wifi and part 1x/nothing. i have crappy service in my area. also recently learned that having task killers is useless on the thunderbolt and its actually draining my battery. gonna see if it changes without it today
If I were to install the radio using ClockwordMod Recovery (I guess the option to install .zip from SD Card), and it happens there is something wrong and I want to go back to the stock radio I had, would that be where Titanium Backup/Nandroid comes in play, or do they not backup radio stuff, and I would have to find another .zip of the stock radio?
(Again, sorry if this sounds n00bish, I am just very new to this and I want to be sure I know what I am doing, I appreciate all the help I am getting here, it is awesome )
thegeebo said:
I am getting ridiculously good battery life and performance with Das Bamf 1.6.3 and Imoseyon's leankernel 2.5 running on extreme with custom undervoltage and interactiveX governor.
One of the key contributors to my battery life is the custom undervoltage. The leankernel extreme is already undervolted, but to be compatible with more TBs it isn't undervolted as much as it can be. After the tweaks i made, which included setting the min clock speed to 368 since I have it using the same low voltage as 245 (750 mv).
I have heard that smartass also gives great battery life with imoseyon's kernel, but since interactiveX has been so good I have had no desire to switch.
I hope that helps!
Click to expand...
Click to collapse
I know about managing the CPU clock, but what is undervolting do? I don't have that option in my ROM, so do I have to download it somewhere?
What exactly the SmartAss governor do?
Yeah, I second lanwarrior, I am confused at how exactly to undervolt my phone? Is that just in the CPU settings when you go and change them in SetCPU or Das BAMF Toolkit?
Radios, have to be renamed to that special name(PG..... Whatever it is lol) and on the root of the SD card. Then you go to hboot (power + volume down when booting) and it will automatically scan for the file and ask to install if it does.
Trying to install the radio from recovery won't work to my knowledge because it can't update the radio that way I believe, only through hboot.
And to revert back to an older radio, there is plenty of radios out there to try and see which one works. If you are planning to upgrade to the new gingerbread radio that was leaked, I'd highly suggest you wait as because of the recent(today) rumors of it super bricking phones. If I left anything out about the radio, feel free to ask.
About the kernels, I'm not too sure about. I do know about the governors mostly, as for the underclocking , it just means that people are making their lowest CPU speed (the Min CPU setting mostly) go lower than normal, pretty much like the concept of overclocking. Kernels tend to be the same but tweaked in many different ways, like how the voltage is and how specific you can be with setting a specific CPU speed.
Some kernels also have more/better tweaks making them faster and more battery efficient.
Best thing to do, is mix and match these things to find the one that you find that works best.
And one last note: ALWAYS MAKE BACK UPS.
I have learned that multiple times by now, especially when screwing around with that stuff
Sent from my ADR6400L using XDA App
Awesome, thanks so much for your help. I just recently found this thread as well that gives good explanations on how to flash using ABD (I am not using their radio, but their instructions are nice: http://forum.xda-developers.com/showthread.php?t=1048128). I still might just copy it on my SD card and then try through Bootloader, the way you described (sounds a little easier to do). And no no, I was not planning on doing the GB radio - I am staying away from GB ROMs and that of sort until the actual release of it and people have been using the ROMs for a bit and know it is stable/will not brick the phone - I am fine with Froyo for now. I plan on just installing the first radio link here (http://forum.xda-developers.com/showthread.php?t=1048128, which is the 1.13.605.7 CDMA/LTE radio combo - I have been told that works fine, but knowing my luck, something might go wrong, ha).
Based on some threads I have been reading, Imoseyon 2.5.1 kernel seems to work very well and seems to have no problem with Das BAMF Remix 1.6.3. I think I might try installing the radio tomorrow, then the kernel, then installing SetCPU and playing around with the SmartAss governor a bit since that also seems to be popular (even though I am not 100% on what it does yet, ha, but I guess I will find out).
I currently get around 31 hours of battery life (with extended battery) on mainly just Wi-Fi and doing minimal downloading and doing some texting/calls, which seems good, but I feel there are a lot of people getting even more so I might try to get more out of my battery.
Well like I said, find what works best and always backup! Haha. I went through a couple different radios to find the best one for me. The other one I tried, would make me reboot a couple times a day randomly. And now the one I'm on, not a single reboot since it has been installed.
But others say it the other way with this one rebooting and the other working, so just gotta find the best.
And don't forget to delete the radio off the SD card root ASAP just in case you get stuck rebooting and need to go to recovery. (Only way to get in without fully booting is through hboot, which will try to install the radio every time only unless it is deleted. ) believe me I have been stuck in a bootloop with a radio on the SD card lol. Only way around it was use my sisters phone to delete the radio from the SD card
Sent from my ADR6400L using XDA App
Oh jeez, thanks for the advice. If you do not mind me asking, which radio are you using/which one gave you the random reboots a day one? Which ROM are you on (if you are rooted)?
So the usual - CM7.1.0-RC1.4; imoseyon's leanKernel, but I barely get 12 hours. Any suggestions?
have you tried nerozehls dreamkernel yet? i thought it was pretty damn sweet. fast and good on battery. i have liquids thunderbread 2.5. had cygenmod7 1.4 also but ended up changing back. im big on aosp now because i dont give 2 ****s about sense and battery wasting crap. but the dreamkernel worked pretty well for me. after u do it id suggest wiping battery stats after a full charge and wait a day or two. usually i notice a difference after that. hope something in that helps you in some way
Nerozehls kernel is Imoseyons kernel with just a few things added to it.
Battery life depends on a lot of things. Are you using speedtweak.sh to set the profile to batterysaver or are you overclocking? Also you have to be mindful of how often things sync and things like that.
Yeah, I ran spedtweak.sh and set it to battsaver, to no effect. I guess I'll try dreamKernel and follow the advice from the first reply.
Many thanks
Just looking for some clarification, maybe tips...
I went from ViperROM to Synergy about a week ago and flashed a couple nightlies of Synergy. I like Synergy, but I'm way too used to the battery life I got from Viper and I feel like I'm stuck between a rock and a hard place deciding...
Is it the dual-core forcing one of the main causes to the battery drain? If so, can that be reverted while keeping the rest of Synergy?
Can Vipers processor control script be ported/used with Synergy? Is it already there? Maybe I'm even misunderstanding this whole thing in general.
I know about calibrating the battery, plan to do that very soon but just haven't had a chance. How likely is this going to help? Or better, how much will it?
I also changed the dconfig profile to battery saver yesterday in Synergy and I don't really notice a difference.
As a base... I used to get 20-24 hours battery on ViperROM with moderate use... I get closer to 12-16, maybe a little more, on Synergy with the same usage. Usage means hour or so of web surfing, not all at once but throughout the day, dozen or so texts, one or 2 calls, maybe 30 min to 1 hour gaming, that's about it.
Not sure what nightly of Synergy you are on but you can certainly us the OC Daemon with it. If you are on a revision after 318 then you are on a 2.3.4 rom and will not be able to overclock but you can underclock with the screen off just fine. Check this thread for a nice flashable that includes some presets and the OC daemon. You won't have the Viper Control script but you can edit the setting with root explorer as described in the thread. If you check the OP's other threads he also has another that includes dual core support.
http://forum.xda-developers.com/showthread.php?t=1212462
Not sure if that will show up as a link or not but that's the thread.
3VO Sent
Hey guys, anyone have a good idea of what some safe undervolting values would be? I was just going to play around with them and not set it on reboot so I could just pull the battery, but I am unsure of how irreversible the damage could possibly be, if any.
I am running: Senseless 1.0
dsb's kernel
I actually have it underclocked slightly because I don't play games, and when I do they are something like Angry Birds, or Words when I am bored.
Bump, out of all of you who have undervolted none of you know any good values?
AtLemacks said:
Bump, out of all of you who have undervolted none of you know any good values?
Click to expand...
Click to collapse
Well, since no one will answer, I will
I generally only keep it undervolted -50mV across the board. That's just my usual set up to get a tiny bit more from the battery. The furthest I've gone is -200mV at the top. I didn't keep it like that for long, but everything seemed to run smoothly still. I'm sure I could go much lower, but I'm kind of afraid to until I know more about it.
I'm just starting to work on undervolting today since I found a kernel that works really well. I'll let you know what my phone is stable at.
WasabiWa83 said:
Well, since no one will answer, I will
I generally only keep it undervolted -50mV across the board. That's just my usual set up to get a tiny bit more from the battery. The furthest I've gone is -200mV at the top. I didn't keep it like that for long, but everything seemed to run smoothly still. I'm sure I could go much lower, but I'm kind of afraid to until I know more about it.
Click to expand...
Click to collapse
Cool, I didn't know what was "too much". How much better battery life did you see from -50?
Evo4gLI said:
I'm just starting to work on undervolting today since I found a kernel that works really well. I'll let you know what my phone is stable at.
Click to expand...
Click to collapse
Which Kernel are you running?
At -50mV across all frequencies, it reeeally varies. I never have a "normal" day with this phone. But, the shortest I've had using Ziggy's kernel from 192-1836gHz with on demand governor is around 7 hours. That was pretty heavy usage for me. Some games like Dead Space and Captain America, tons of internet, Pulse, texting, a few phone calls, music, and a little Netflix at night. The longest I've had has been 20+ hours. That's with very little gaming, a little internet, and mostly just texting. Stock battery, bump charged.
I'm really afraid to go too low, though. One time I was just seeing what would happen if I kept lowering it across all of the frequencies and it froze, then crashed. Had to battery pull to get it to work again.
I run DSB Kernel with SmartAssV2 underclocked to 1296, and before undervolting on my OEM battery I got 13 hours with a little over normal usage. Screen was on for about 2 hours total. On my extended battery I got like 27 1/2 hours, but obviously some of that time was overnight.
2 hours later I am still above 90% this is what I like to see! If I can get 15 hours on OEM battery, my extended battery will stay in my truck as my backup!
AtLemacks said:
2 hours later I am still above 90% this is what I like to see! If I can get 15 hours on OEM battery, my extended battery will stay in my truck as my backup!
Click to expand...
Click to collapse
Might mess with this, I am running same kernel same governor. How much did you undervolt in the end? I was gonna push-100 on each and see how it goes...
Sent from my ADR6425LVW using XDA App
I went -50 across the board, using dsb kernel, underclocked to 1028, and everything is stable.
Sent from my HTC Rezound via Tapatalk
nosympathy said:
Might mess with this, I am running same kernel same governor. How much did you undervolt in the end? I was gonna push-100 on each and see how it goes...
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Just -50, but I updated the kernel and forgot to remove the PH98IMG prior so I set the phone into bootloops. Had to factory reset(after trying everything else) and start over from backups.
Evo4gLI said:
I went -50 across the board, using dsb kernel, underclocked to 1028, and everything is stable.
Sent from my HTC Rezound via Tapatalk
Click to expand...
Click to collapse
See, I don't get the overclocking hype. It isn't hard to overclock when needed, so I feel underclocking is the better choice for battery life. The phone is fast as hell no matter what.
I may try to do some undervolting...but I am running clean rom 1.3 and dsb's smartass kernel, and I have been getting good battery life for what I use my phone for. I do have it overclocked though (on demand).
You won't damage the phone with undervolting. I mean a lockup might be a pain, but it won't damage the phone. Overvolting on the other hand could ruin the phone.
I will probably just stick with -50 across the board for now, I am tempted to pay for the full version just so I can save profiles and not have to set on boot.
Late reply but running AOKP w/ frAnco I UV -100 with no issues at all.
Running -75 on everything with incredikernel
bendirkss said:
Late reply but running AOKP w/ frAnco I UV -100 with no issues at all.
Click to expand...
Click to collapse
You sir must be using a Gnex. LOL
I just installed the new Siyah 3.2b1 kernel to run my ShoStock 2.2.2 ROM last night and everything was working fine. I didn't make many changes other than switching the governor to lulzactive and the i/o scheduler to noop.
It was running fine over night (lost 0% battery).
Then today after I used the phone for a few minutes the battery seemed to drain a little quicker. I know its too early to complain about battery life but I decided to investigate. When I checked cpuSpy it showed that all of the frequencies were barely used (mostly spent in deep sleep over night) but the 1200 mhz frequency was used most after that (significantly more than the others). When I went back into voltage control (same thing with setcpu) I noticed that it seemed to be stuck at 1200 mhz. The only thing that fixed it was changing the governor.
Does anyone have any ideas on whats causing this and how to fix it (I had great battery performance on lulzactive before so would like to use it again)?
Just try clearing app data rebooting and reinstalling the app. That problem has happened to me every once in a blue moon and that fixed it for me.
Sent from my SGH-I777 using Tapatalk 2
Thanks, I'll try reinstalling the kernel.
Which app are you referring to? because I had this problem no matter which app I used to change the governor (Extweaks, voltage control, setcpu).
Use Jivy's Kernel cleaning script prior to flashing, and try again.
http://forum.xda-developers.com/showthread.php?t=1428530
Ive used the kernel cleaner every time I installed a new kernel. It didn't seem to work this time. But thanks for responding.
bacon_n_icecream said:
Ive used the kernel cleaner every time I installed a new kernel. It didn't seem to work this time. But thanks for responding.
Click to expand...
Click to collapse
It's the lulzkernel for some-reason :|
I have problem goto smartassv2 it's ok just steps heavy
Thanks for your suggestion. I just moved over to ondemand and its been ok for me. Too early to make any judgments but I'll try smartassv2 next.
Not that I'm glad to that you're having problems, but I'm glad I'm not the only one with this issue. Thanks for the response
Winklie said:
Use Jivy's Kernel cleaning script prior to flashing, and try again.
http://forum.xda-developers.com/showthread.php?t=1428530
Click to expand...
Click to collapse
DONT use kernel cleaning scripts. They cause more problems than good.
Sent from my AT&T I777 running AOKP build 3X
I haven't had any issues with using the kernel cleaning script thus far.
What kind of harm can they cause? and do you have any recommendations on how to clean up before switching kernels or is just flashing them over ok? (A lot of people recommend the script cleaner and it seemed to have solved a lot of peoples issues kernel issues)
bacon_n_icecream said:
I haven't had any issues with using the kernel cleaning script thus far.
What kind of harm can they cause? and do you have any recommendations on how to clean up before switching kernels or is just flashing them over ok? (A lot of people recommend the script cleaner and it seemed to have solved a lot of peoples issues kernel issues)
Click to expand...
Click to collapse
Wipe cache, wipe dalvik. I've read more problems with the cleaning script than good.
Sent from my SGH-I777 using Tapatalk 2
thanks, I generally do that any way along with the script cleaner
K Rich said:
Wipe cache, wipe dalvik. I've read more problems with the cleaning script than good.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Lol what exactly have u heard? If it was causing problems it would get pulled. The only thing I can foresee happening is someone flashing it and then not flashing a kernel or something. Which would be user error.
Sent from my SGH-I777 using Tapatalk 2
CPU related as well...
Hi Guys,
My first post here. I am total noob. I rooted and installed the newest ShoStock2 on my at&t galaxy s2. Everything works perfectly. I couldn't be happier. I also went bought the setCPU for overclocking it. That too seem to be working fine.
My question is. I didn't set up any voltage requirements. The only thing I did was to set it to 1600 MHZ and 200 min and change the governor on the bottom to Lulzcrative. Will this work? Do I need to actually do something with the voltage? am I really on 1600 right now? I cannot tell.
I ran a quad test (I now it is meaningless in real world) it came 2818 yesterday. I ran it again this morning ..... It froze and took my battery from 45 to 9 in less than 3 mins!!!!!! The phone got really hot. I took out the battery right of way. The battery life showed 23 percent this time.
I got little afraid of the quadrant testing ... The phone seems to run good without that but I am not sure if it is set up how it is suppose to.
Could someone help me out please? I tried reading the forums and that is where I got the idea in the first place to overclock it.
So to summarize it, I guess phone is fine right now but I am not sure if I set up setcpu out properly.
I am on the newest shostock2. I have galaxy s2 on att. I am pretty good with computers and phones but not sure about voltage and other problems with relating to setCPU.
Thank you advance for helping me out.
kbulut said:
Hi Guys,
My first post here. I am total noob. I rooted and installed the newest ShoStock2 on my at&t galaxy s2. Everything works perfectly. I couldn't be happier. I also went bought the setCPU for overclocking it. That too seem to be working fine.
My question is. I didn't set up any voltage requirements. The only thing I did was to set it to 1600 MHZ and 200 min and change the governor on the bottom to Lulzcrative. Will this work? Do I need to actually do something with the voltage? am I really on 1600 right now? I cannot tell.
I ran a quad test (I now it is meaningless in real world) it came 2818 yesterday. I ran it again this morning ..... It froze and took my battery from 45 to 9 in less than 3 mins!!!!!! The phone got really hot. I took out the battery right of way. The battery life showed 23 percent this time.
I got little afraid of the quadrant testing ... The phone seems to run good without that but I am not sure if it is set up how it is suppose to.
Could someone help me out please? I tried reading the forums and that is where I got the idea in the first place to overclock it.
So to summarize it, I guess phone is fine right now but I am not sure if I set up setcpu out properly.
I am on the newest shostock2. I have galaxy s2 on att. I am pretty good with computers and phones but not sure about voltage and other problems with relating to setCPU.
Thank you advance for helping me out.
Click to expand...
Click to collapse
Lots of questions there. Phone overclocking is the same and at the same time different than PC overclocking. I too bought SetCPU and due to bugs and problems have completely abandoned it. Honestly with the exception of running an epeen benchmark there is little incentive to overclock. Find a newer Kernel (I use NEAK which has no overclocking ability) and install it, performance is stellar. You really have to ask yourself, is my phone slow enough that I need more CPU power to make it faster?
To see what time your CPU is spending at a given clock speed, download CPUSpyhttps://play.google.com/store/apps/details?id=com.bvalosek.cpuspy&feature=nav_result#?t=W251bGwsMSwyLDNd, you will be surprised to see your phone spend very little time at it's max clockspeed.
Due to the immaturity of the fab process for our CPU's (well SoC), what is a stable overclock for one person might not even load for another. These CPU's are not like an Intel Sandy Bridge, with 1Ghz of free overclocking, nearly guaranteed. You can certainly play with voltages to try and attain a higher overclock, but at the expense of CPU lifetime, as well as battery.
Additionally, it takes a new Kernel 3 or so full charge, discharge cycles on a phone to really 'settle in' and 'learn' a particular phones battery, while yours got hot, which to me indicates an endless loop of some kind running in the background.
My advice would be as follows: Choose a ROM you like, feel free to play with different Kernels, again, I use NEAK, which does not work for some folks, or crashes or whatever. Give it several days to 'settle in' and if your still not happy with performance or have stability problems, try a different governor/scheduler. You really need to establish a good, solid baseline of your phones performance and make small changes and give them long enough to establish any changes to your phones overall stability. Basically running cowboy through your phone and making changes will have a negative overall outcome. Make small, documented changes, test and see what overall effect this has to your phone's stability and battery life, and make another change.
bacon_n_icecream said:
I just installed the new Siyah 3.2b1 kernel to run my ShoStock 2.2.2 ROM last night and everything was working fine. I didn't make many changes other than switching the governor to lulzactive and the i/o scheduler to noop.
It was running fine over night (lost 0% battery).
Then today after I used the phone for a few minutes the battery seemed to drain a little quicker. I know its too early to complain about battery life but I decided to investigate. When I checked cpuSpy it showed that all of the frequencies were barely used (mostly spent in deep sleep over night) but the 1200 mhz frequency was used most after that (significantly more than the others). When I went back into voltage control (same thing with setcpu) I noticed that it seemed to be stuck at 1200 mhz. The only thing that fixed it was changing the governor.
Does anyone have any ideas on whats causing this and how to fix it (I had great battery performance on lulzactive before so would like to use it again)?
Click to expand...
Click to collapse
Lulz has known problem in 3.2b2-1
Gokhan has fixed it in 3.2b2 - 2
Wait for ktoonsez to update it for us
Sent from my SGH-I777 using Tapatalk 2 Beta-6
Thank you so much for the information. Could I simply uninstall the setcpu and go back to normal? Simply reflash the rom and/or kernel? I really like shostock2 with the cherry picker kernel for now. I want to give them a week of try to make my mind. Before the setcpu I think.I was better off
Thanks for the help by the way. I appreciate it.
Thanks for the update about the new siyah kernel. Glad it wasn't just me with the issue. I was going to post this question in the siyah thread but am new to the site so didn't have permission so thanks for finding me all the way over here
Phalanx7621 said:
Lol what exactly have u heard? If it was causing problems it would get pulled. The only thing I can foresee happening is someone flashing it and then not flashing a kernel or something. Which would be user error.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I'm just going off what I've seen in the Siyah/NEAK threads. Most of the lock-ups/random reboots I've heard people having had used the cleaning script. Either that or its just coincidence.
I may be wrong but I think that using the kernel cleaning script actually solved most of the lockups. Perhaps I misunderstood the threads.
bacon_n_icecream said:
I may be wrong but I think that using the kernel cleaning script actually solved most of the lockups. Perhaps I misunderstood the threads.
Click to expand...
Click to collapse
Hmm, well I've just manually wiped cache and dalvik and have never had problems between roms/kernels.
Sent from my SGH-I777 using Tapatalk 2