Related
I've used SetCPU in the past and have determined that my max stable clock speed is 113600; I've also read that using SetCPU to control clock speed can create some problems.
How would one go about manually overclocking the phone without using SetCPU? I was looking around in /sys/devices/system/cpu/cpu0/cpufreq and it looks like there are kernel settings there, just want to make sure I don't bork anything in the process
Thanks in advance!
From my understanding is that if you get an overclock kernel it will basically run in the same fashion as your current kernel (as far as governing speed goes) except you'll have a higher max frequency.
Rrrracer said:
I've used SetCPU in the past and have determined that my max stable clock speed is 113600; I've also read that using SetCPU to control clock speed can create some problems.
How would one go about manually overclocking the phone without using SetCPU? I was looking around in /sys/devices/system/cpu/cpu0/cpufreq and it looks like there are kernel settings there, just want to make sure I don't bork anything in the process
Thanks in advance!
Click to expand...
Click to collapse
SetCPU is the GUI to do what you are talking about... Are you looking to go past 1.113? I can only get to 1.113, but if I run Hyrda's OCOV kernel I can get to 1.15.
I would say if you don't know what you are doing, I wouldn't mess with it. Nandroid is handy if you do.
I'm running invisiblek's #16 kernel but max clock speed is showing 998. Not trying to go over 1.13 but thought I read somewhere about being able to manually change it in the system files somewhere without using SetCPU.
IIRC the idea was to use SetCPU to determine your max stable clock speed, then change it manually in a system file somewhere and then not use SetCPU.
Sent from my ADR6300 using XDA App
Try uninstalling/reinstalling setCPU. I've had issues every once in a while when flashing a new ROM, then doing the app only restore from a TI backup cause issues.
Personally I can't say I've ever had any problems using SetCPU, but if there's a way to make it default to 1.13 without having another process running then I am all for it, thus my question. Just don't know where to change it
I can tell you i am 99.9% sure that you were right with the file location in your first post.
If you check chads thread SOMEWHERE in there i think its mentioned... Sorry to say but i have no idea where.
Here's a script that Ziggy wrote, you can edit it to your needs and flash it and fix permissions. Without editing it's set at 1.113GHz Interactive screen on and .384GHz Ondemand screen off if I remember correctly. It also has another tweak (memory management I believe?). But hey, it's a start.
Much appreciated guys, I will check out Chad's thread again and look at that script. I just don't see the need for SetCPU if I can just plug in my known stable values and roll it like that Thanks again!
Fixed lol sorry
Sent from my Droid Incredible running Myn's Warm Two Point Two RLS4.
LOL Blah! :-D
I have tried editing those files and it does not seem to change the clock speed. Anyone who has successfully done it manually could you please list all the specific files. Also im going to examine the script that was linked and see if i can tweak it a bit. Ill post any findings here.
I use the custom kernel #18 and setcpu, clocked to 1.115 easily with cm6.1. works awesome and smokin fast.
trunksta said:
I have tried editing those files and it does not seem to change the clock speed. Anyone who has successfully done it manually could you please list all the specific files. Also im going to examine the script that was linked and see if i can tweak it a bit. Ill post any findings here.
Click to expand...
Click to collapse
I edited Ziggy's script using EditPad lite (free, just Google it) since I'm on Windows so as not to change the format. Flashed from recovery then fixed permission in Root Explorer. Worked like a charm.
This is stock ROM.
Every time I flash bacon bits to overclock my phone I always noticed that my screen flickers when I turn off the phone's screen or press the button to wake up.
Sometimes it just gets stuck and it stats flickering like crazy and I can't unlock my phone because of it.
This only happens when I OC my phone. When I wipe the phone it works fine but no OC which is what I want.
Any way to fix this issue?
I don't use Bacon Bits, but I have experienced the flickering you speak of. It seems that happen when you go too far with the OC process. What happens if you were to lower your clockspeed a bit? Does it continue to happen for you?
dustrho said:
I don't use Bacon Bits, but I have experienced the flickering you speak of. It seems that happen when you go too far with the OC process. What happens if you were to lower your clockspeed a bit? Does it continue to happen for you?
Click to expand...
Click to collapse
Actually I OC my phone, but it's still set on 806MHz so even at lower clockspeed it still flickers. It's bugging the hell out of me.
EDIT:
Switched over to pershoot's kernel: http://forum.xda-developers.com/showthread.php?t=847672 I can now overclock to 1.5 gHz with no problems anywhere. Aweseome.
I have this same problem and am bumping this thread.
I'm running stock rom with bacon bits v 0.3 - and my screen flickers when turning off so much that it won't turn off fully and opens the lock screen. I have to just try and try repeatedly to get it to work.
Any suggestions?
captainreynolds said:
EDIT:
Switched over to pershoot's kernel: http://forum.xda-developers.com/showthread.php?t=847672 I can now overclock to 1.5 gHz with no problems anywhere. Aweseome.
I have this same problem and am bumping this thread.
I'm running stock rom with bacon bits v 0.3 - and my screen flickers when turning off so much that it won't turn off fully and opens the lock screen. I have to just try and try repeatedly to get it to work.
Any suggestions?
Click to expand...
Click to collapse
Yeah, I have flashed all the kernels even pershoot's and it still flickers. I'm using the original ROM that came with the phone not the original one posted on the forums. Maybe if I use the one posted on the forums that will work?
I have the stock rom as well - I first flashed baconbits kernel, but when that flickered, I flashed pershoots most recent kernel in recovery. No flickering anymore - sorry to say I don't know what's wrong. Try posting in the thread of the kernel you are currently running!
Sent from my T-Mobile G2 using XDA Premium App
captainreynolds said:
I have the stock rom as well - I first flashed baconbits kernel, but when that flickered, I flashed pershoots most recent kernel in recovery. No flickering anymore - sorry to say I don't know what's wrong. Try posting in the thread of the kernel you are currently running!
Sent from my T-Mobile G2 using XDA Premium App
Click to expand...
Click to collapse
Well you know what I flashed an older version of pershoot mayeb I should try the newer one. I'll let you know what happens...
I had trouble flashing it with ROM Manager. Clockworkmod it. Here's the link to pershoots blog with the latest update links: http://droidbasement.com/db-blog/
Good luck!
Sent from my T-Mobile G2 using XDA Premium App
Just tried it and nope... it's still doing it maybe it's just my phone.
Bring it up in this thread:
http://forum.xda-developers.com/showthread.php?t=847672&page=103
Pershoot is always monitoring it along with a bunch of other smart devs. Maybe they'll have a better idea - don't give up hope!
what app are you guys using to manage your OC?
if it's setCPU, set your scaling to Interactive on the main screen and in any profiles you're using.
also, if you are using any screen on/off animations, disable them (just to see, for troubleshooting purposes, if that might be the culprit)
pmcqueen said:
what app are you guys using to manage your OC?
if it's setCPU, set your scaling to Interactive on the main screen and in any profiles you're using.
also, if you are using any screen on/off animations, disable them (just to see, for troubleshooting purposes, if that might be the culprit)
Click to expand...
Click to collapse
Yeah, it's set on Interactive and so are the profiles. As for the screen on and off animation I believe that's in the CM7 RC1 ROM. I'm using the stock ROM so there's no option for that.
jjuice525 said:
Yeah, it's set on Interactive and so are the profiles. As for the screen on and off animation I believe that's in the CM7 RC1 ROM. I'm using the stock ROM so there's no option for that.
Click to expand...
Click to collapse
hehe, didn't even read what rom you were using. my bad.
kernels aside, it is very possible, as you mentioned earlier, that you guys got the chips in the stash that don't take to overclocking very well. even on a device like the G2/DZ that seems to take to higher clock speeds relatively easily, there are bound to be some that aren't as happy with the increased workload.
if I think of any other bright ideas, I'll let you know. I haven't played with baconbits a lot.
pmcqueen said:
hehe, didn't even read what rom you were using. my bad.
kernels aside, it is very possible, as you mentioned earlier, that you guys got the chips in the stash that don't take to overclocking very well. even on a device like the G2/DZ that seems to take to higher clock speeds relatively easily, there are bound to be some that aren't as happy with the increased workload.
if I think of any other bright ideas, I'll let you know. I haven't played with baconbits a lot.
Click to expand...
Click to collapse
Actually, after installing Pershoot's most recent kernel, I have no problems. Maybe I just got lucky here.
I specified SetCPU to have my speed at 245 min 768 max. It stays there, but then with time goes back up to 998 max. I disabled perflock, should that fix the problem?
what kernel? what ROM?
disabling perflock should fix that
i have some issues also, my evo cant take anything over 998,,it reboots but my brothers work perfect with high setup.. why could that be
elvelozpotosino said:
i have some issues also, my evo cant take anything over 998,,it reboots but my brothers work perfect with high setup.. why could that be
Click to expand...
Click to collapse
There were a few different evos made so not all of them can handle oc'ing there was hw0001 - hw0004 do to the high demand of the evo when it came out something like that.
Edit: Also even the same hw version can be different.
Sent from my PC36100 using XDA App
Stock kernel with stock rom (but removed bloatware/rooted system tweaks). Perflock disabled appeared to have fixed it. Thanks!
If you haven't tried this app already, definitely give it a shot. So many features. It basically incorporates Titanium, Root Explorer, Voltage Control, SetCPU, SD Card Boost, ROM Manager, TMobile ThemeChooser (for CM7), Terminal Emulator, Ad Blocker, Rebooter, V6 Supercharger, Autokiller, Font Installer, Custom Boot Animations, Battery Icon Changer, Boot Logo Changer, and probably several other common Root apps all-in-one. You can mess with Build.prop tweaks, vm heapsize, sysctl tweaks, and more. AND it lets you Apply any changes you make on Boot.
And the best part.....ALL FREE!!!! (though there is a donate version, not sure what the extra features are - but all I mentioned above is in free version)
Let me know what you think:
ROM Toolbox Market Link
Check out Imoseyon's recommended settings/tweaks as well here.
great app
Thanks for the tip...I just got it and MAN is it amazing! I'll play around with it some more, but if it holds up...I'll buy the donate version. Really good app!
Just found this today as well. Super useful.
FrankyFiggz27 said:
If you haven't tried this app already, definitely give it a shot. So many features. It basically incorporates Titanium, Root Explorer, Voltage Control, SetCPU, SD Card Boost, ROM Manager, TMobile ThemeChooser (for CM7), Terminal Emulator, Ad Blocker, Rebooter, V6 Supercharger, Autokiller, Font Installer, Custom Boot Animations, Battery Icon Changer, Boot Logo Changer, and probably several other common Root apps all-in-one. You can mess with Build.prop tweaks, vm heapsize, sysctl tweaks, and more. AND it lets you Apply any changes you make on Boot.
And the best part.....ALL FREE!!!! (though there is a donate version, not sure what the extra features are - but all I mentioned above is in free version)
Let me know what you think:
http://bit.ly/rhxwX5
Click to expand...
Click to collapse
Thanks for the tip! I like the app, with no reliable data connection I'm out of the loop on most things great to have them here when I do get data!
Sent from my Samsung Legen-wait for it-dary! 4g
It will not change your boot animation if your on ei22
Sent from my SPH-D700 using Tapatalk
I used this app. The paid version provides the ability to set most of those functions to apply at boot
Sent from my SPH-D700 using XDA App
slayer450 said:
It will not change your boot animation if your on ei22
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
It will, but only if you are using a kernel that supports then
Sent from my Samsung Legendary 4G, a Universe UTES phone, running "two.three.five"
nicenice19 said:
I used this app. The paid version provides the ability to set most of those functions to apply at boot
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
what other things can you set at boot in the paid version that you can't in the free version? cuz u can set governor, sd card read speed, and other things at boot for free..
possibly a result of some tweaks i just made using Rom Toolbox, I'm flying right now. Faster than ever. Here's what I changed, just in case anyone can point out if I did anything bad:
Auto memory manager
6,8,24,30,40,50 (same as Aggressive 1 settings in V6 Supercharger)
vm heap size = 32
sd boost = 3072
Min Free KBytes = 4096
Dirty Ratio = 90
Dirty Background Ratio = 70
VFS Cache Pressure = 5
Oom Kill Allocating Task - SET ON
Applied everything at boot, obviously. I did a little research on what to change these values to, and so far these values have definitely sped me up considerably.
__________________
How has battery life been with those settings?
interfreak said:
How has battery life been with those settings?
Click to expand...
Click to collapse
Great so far. The improved performance is even more noticeable, however. only thing you might want to change, if you know what it is, is the oom kill allocating task setting. a lot of people seem to leave it off, but from what i understood it did, keeping it on should save more battery and just operate more efficiently (makes the killing off of tasks to regain ram less random). so far there's been no downside to having it on. also, you might want to test out putting the vfa cache pressure setting to 1. many people do that, too.
It requires the pro version to freeze apps
hey just want to ask a simple question ....
i am having samsung galaxy s2 and i had update it with 2.3.6 stock rom KK5 and i want to change the battery icon on the taskbar. but as i change it. my phone didn't boot and stuck on sangung galaxy s2 logo. even didn't find the boot animation or sound..
i didn't make any changes except the battery icon.
even my phone is root.
please check it and revert what i have to do to change the battery icon ...
thanx ..
waiting for +ive response
Rg.
Sachin...
sacmat said:
hey just want to ask a simple question ....
i am having samsung galaxy s2 and i had update it with 2.3.6 stock rom KK5 and i want to change the battery icon on the taskbar. but as i change it. my phone didn't boot and stuck on sangung galaxy s2 logo. even didn't find the boot animation or sound..
i didn't make any changes except the battery icon.
even my phone is root.
please check it and revert what i have to do to change the battery icon ...
thanx ..
waiting for +ive response
Rg.
Sachin...
Click to expand...
Click to collapse
I think you're in the wrong forum
Sent from my SPH-D700 using XDA App
IronReaver17 said:
I think you're in the wrong forum
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Well, he did make the change with Rom Toolbox. To the guy with the battery issue, I think you need to be on a deodexed rom to change the battery.
WOW!!! The speed change is amazing!!!! hard to believe that just a few tweaks did that!
Bought the pro version of this. Tried to change battery icon and it froze on boot logo on reboot. Tried to refund and it won't refund. Will be emailing the developer.
Sent from my SPH-D700 using Tapatalk
Zeinzu said:
Bought the pro version of this. Tried to change battery icon and it froze on boot logo on reboot. Tried to refund and it won't refund. Will be emailing the developer.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Man, Android and you sure have a strange releationship...
..... you always get the wierdest issues....
Hope you get a good response from the dev
This Epic post as brought to you via Tapatalk
Yea... don't get me wrong I'm sure all the functions work great, and it's not like I tried anything else with it. Having one freeze was enough for me to stick with the ways of doing things that I know I never have issues with. But knowing me I'll just keep the paid version and try again at some later date. Maybe something just glitched during the reboot.
Sent from my SPH-D700 using Tapatalk
Zeinzu said:
Yea... don't get me wrong I'm sure all the functions work great, and it's not like I tried anything else with it. Having one freeze was enough for me to stick with the ways of doing things that I know I never have issues with. But knowing me I'll just keep the paid version and try again at some later date. Maybe something just glitched during the reboot.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Not sure if this will help, but I have the pro version as well and was able to successfully change the battery icon. I liked having the number off to the side so since I have the ICS theme on my phone, I used that battery icon. I think it's 'Bar Ice Cream Sandwich'.
Alright so I am using KT747 Kernel with Ktoonservative/Noop, 1512-384mhz, screen off 486mhz. I was given an option to Lock frequencies which disallows apps to modify the speed. However I noticed after I checked this some of my apps started crashing. I want good battery life (forget to mention I undervolted) and want to know if locking frequencies is what is making the apps crash. Any help would be great, and feel free to post some good settings for the kernel for optimal battery life with pretty decent clock speeds as well. Thanks again.
If your apps crash it is more likely to be caused by your undervolting.
And for the setting go there:
http://forum.xda-developers.com/showthread.php?p=31539830
Sent from my SGH-I747 using xda app-developers app
liltitiz said:
If your apps crash it is more likely to be caused by your undervolting.
And for the setting go there:
http://forum.xda-developers.com/showthread.php?p=31539830
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah I read your post earlier in that thread and was using your settings. I've come across a newer problem, my phone randomly reboots. I don't know what was causing this so I restored default settings.
When you change kernel or kernel setting it is usual that your phone may need a few reboots before stabilizing
Sent from my SGH-I747 using xda app-developers app
Unlock the frequencies and run the app that causes the reboot. If it doesn't reboot that was the problem. More likely its too much under volt. The table in the link is some pretty severe undervolting. 740 is a long way down from the stock 925. That's great if your phone can handle it, but can cause problems if it can't. Piece of advice, never use any set on boot settings if your not sure it will. You may find yourself in a bootloop and have to reflash the kernel to get out of it.
DarthDerron said:
Alright so I am using KT747 Kernel with Ktoonservative/Noop, 1512-384mhz, screen off 486mhz. I was given an option to Lock frequencies which disallows apps to modify the speed. However I noticed after I checked this some of my apps started crashing. I want good battery life (forget to mention I undervolted) and want to know if locking frequencies is what is making the apps crash. Any help would be great, and feel free to post some good settings for the kernel for optimal battery life with pretty decent clock speeds as well. Thanks again.
Click to expand...
Click to collapse
I doubt locking the frequencies has anything to do with your reboot problems, this simply dissallows any apps that are capable to override the voltage settings for any particular frequency step. In fact, unchecking this may actually give you a false positive of it 'fixing' the problem when it is actually just using the default (or higher) voltages, burning up more battery in the process. As mentioned by jethro and liltitiz its more likely your UV settings, keep playing with them until you find the happy spot (works on other things too....:silly.
jethro650 said:
Unlock the frequencies and run the app that causes the reboot. If it doesn't reboot that was the problem. More likely its too much under volt. The table in the link is some pretty severe undervolting. 740 is a long way down from the stock 925. That's great if your phone can handle it, but can cause problems if it can't. Piece of advice, never use any set on boot settings if your not sure it will. You may find yourself in a bootloop and have to reflash the kernel to get out of it.
Click to expand...
Click to collapse
Or just move the ktweaker apk from the /system/app directory from a recovery based file manager. This will keep it from launching on startup and then can either be moved back or ran to reinstall. This way you dont have to cleark the dalvik cache, which should be done any time a kernel is installed, eliminating the extra long boot time when this is done. Either the built in TWRP explorer or the Aroma File Manager which can be 'flashed' in recovery. It doesn't actually flash anything, just unpacks, runs, and then is dumped from memory on reboot...very handy if you dont have TWRP or can't get into android.
liltitiz said:
When you change kernel or kernel setting it is usual that your phone may need a few reboots before stabilizing
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I was wondering what was going on. I restored stock Voltage and realized that it was the problem.