Ok. i have refraind from asking questions for quite some time. I have lurked, and read and read and read. i learned how to flash roms and kernels and most otherthings i want to do without bothering anyone with noob questions...up until now.
I flashed the suckerpuch #50 kernel in attempts to try out 1.4ghz, but unless im completely missing something my phone dosnt ever seem to go above 1 ghz on this kernel. im not positive this is the case, but heres what leads me to beleive it:
cpu usage widget on my screen never shows above 1ghz, while a different 1.2ghz OC i tired shows it peaking up to 1.2 right after boot, and if i exit quadrant it shows 1.2 for a sec before dropping back down, same with any 3d game, when i quickly close it and look at the widget, it will show running at 1.2. Yet suckerpuch never shows above 1.0 UNLESS i run CPUsetting and set it to "performace" which it then appears to be running at 1.4 AT ALL TIMES, and the phone isnt stable so thats a no go.
am i missing some key piece of information here? did i flash it wrong? is there some other type of modification i need to do to get it to actually run at 1.4?
ive read through the suckerpunch #50 opening posts multiple times and i believe it tells me i need to modify some file or other, possibly, but im not understanding.
any info/help would be much appreciated!
P.S. this forum, the devs, and all the things supplied to make my phone awesome are absolutley great.
I believe SuckerPunch is set to 1Ghz as default unless you change the setting with Voltage Control (or SetCPU). Mind you that 1.4Ghz is not run well on a lot of devices and may cause freezing. And I'm glad some people take up reading before asking questions
p.p.s- im aware not to use set CPU.
honestly i cant see the point of it with any kernel. dosnt seem to do anything.
koreancanuck said:
I believe SuckerPunch is set to 1Ghz as default unless you change the setting with Voltage Control (or SetCPU). Mind you that 1.4Ghz is not run well on a lot of devices and may cause freezing. And I'm glad some people take up reading before asking questions
Click to expand...
Click to collapse
yeah im using voltage control- minus 125 on all and the phone seems to work well.
i just find it weird that the kernel peaks at 1ghz, where as another peaks at 1.2ghz (both without use of setCPU, and WITH use of Voltage control)
when i was using setCPU and putting it on performance, i could see it was running at 1.4, pretty much at ALL TIMES. MOST things ont he phone worked well, ultra fast. the problems i noticed is that neocore would freeze (which i understand to be a sign of instability) and speedtest would either give me REALY slow speeds, or force close every time. were as set on conservative it would work perfectly and neocore wouldnt freeze.
oFUNGUSo said:
yeah im using voltage control- minus 125 on all and the phone seems to work well.
i just find it weird that the kernel peaks at 1ghz, where as another peaks at 1.2ghz (both without use of setCPU, and WITH use of Voltage control)
when i was using setCPU and putting it on performance, i could see it was running at 1.4, pretty much at ALL TIMES. MOST things ont he phone worked well, ultra fast. the problems i noticed is that neocore would freeze (which i understand to be a sign of instability) and speedtest would either give me REALY slow speeds, or force close every time. were as set on conservative it would work perfectly and neocore wouldnt freeze.
Click to expand...
Click to collapse
I guarantee you you cannot run -125 at 1.4GHz, unless you have some kind of wonder-phone.
In Voltage Control, you're set to 1.4GHz, correct?
If you are, have you made sure to enable the 1.4GHz state in Voltage Control via the bottom menu as well? If you don't, even though you're set at 1.4GHz it will not run at that.
Auridran said:
I guarantee you you cannot run -125 at 1.4GHz, unless you have some kind of wonder-phone.
In Voltage Control, you're set to 1.4GHz, correct?
If you are, have you made sure to enable the 1.4GHz state in Voltage Control via the bottom menu as well? If you don't, even though you're set at 1.4GHz it will not run at that.
Click to expand...
Click to collapse
my bad, im running -125 on i think its the gb 1.2ghx kernel. thats working fine.
im going to reflash #50 and try what you said.....though im pretty sure i already had it set. i know i was setting the mv from 100 up to 1400
ok i flahsed back to #50, and went into voltage control. it DID cap my freq at 1000, i changed it and set 100 through 1400 to -75mv.
i ran stress test for about 30 seconds and exited, and my CPU widget shows 99% usegage at 1ghz
hmm
i flashed back to gb reorient 1.2ghz and during boot up as soon as the CPU widget loaded it shows 1.2ghz. ran stress test again and exited in the middle of it, widget showed 99% usage at 1.2ghz.
i realyl dont know what im missing here, but it does seem as thought the suckerpunch #50 is not running above 1ghz for me.
comparing all forms of benchmark type tests between the two kernels, everything EXPCEPT necore is scoreing better on the 1.2 kernel. neocore onthe 1.3 kernel is giving me 55.4 fps, whereas on the 1.4 kernel its giving me 65 and some change fps. i know benchmark scores arent that meaningfull in some cases, and on the #50 thread it even states that some may be lower on that kernel.......but i swear ive done something wrong because i dont see how it can be running at 1.4
oFUNGUSo said:
ok i flahsed back to #50, and went into voltage control. it DID cap my freq at 1000, i changed it and set 100 through 1400 to -75mv.
i ran stress test for about 30 seconds and exited, and my CPU widget shows 99% usegage at 1ghz
hmm
i flashed back to gb reorient 1.2ghz and during boot up as soon as the CPU widget loaded it shows 1.2ghz. ran stress test again and exited in the middle of it, widget showed 99% usage at 1.2ghz.
i realyl dont know what im missing here, but it does seem as thought the suckerpunch #50 is not running above 1ghz for me.
comparing all forms of benchmark type tests between the two kernels, everything EXPCEPT necore is scoreing better on the 1.2 kernel. neocore onthe 1.3 kernel is giving me 55.4 fps, whereas on the 1.4 kernel its giving me 65 and some change fps. i know benchmark scores arent that meaningfull in some cases, and on the #50 thread it even states that some may be lower on that kernel.......but i swear ive done something wrong because i dont see how it can be running at 1.4
Click to expand...
Click to collapse
Like I said in my previous post, are you actually enabling the frequencies or just selecting 1.4GHz as the max in Voltage Control?
You have to enable 1.4GHz in the "states" menu of Voltage Control for it to work, as well as set 1.4GHz as the max in Voltage Control. SuckerPunch does not overclock by default because a lot of phones do not play nicely with 1.4GHz.
Auridran said:
Like I said in my previous post, are you actually enabling the frequencies or just selecting 1.4GHz as the max in Voltage Control?
You have to enable 1.4GHz in the "states" menu of Voltage Control for it to work, as well as set 1.4GHz as the max in Voltage Control. SuckerPunch does not overclock by default because a lot of phones do not play nicely with 1.4GHz.
Click to expand...
Click to collapse
ha. this had me confused......there was no "states" menu. that got me pokeing around and then i realized i didnt have the newest version of voltage control(had 2.0 instead of 3.0). i do NOW. and i see the option to select the states. so, i selected 7 states up to 1400. and selected the max frequency of 1400. set a voltage for all, and applied.
still the same result. lol. its not running over 1ghz according to cpu stats. it SAYS it frequency range is from 100 to 1400. but it aint going over 1000.
*sigh* there has to be something else im missing
For suckerpunch's new builds, it's set to startup at 1ghz. After like 15mins. you can run some tests and it should be at max clock.
YESSSSSSSSSSSSS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
ITS WORKING! and dayum i see and improvement in stats! benchmarks look fantasitc, neocore isnt freezeing, phone isnt freezing on lockscreen.....will have to run stress test for a while to see for sure but it appears stable!
1400 -50
1300 -50
1200 -75
1120 -75
1000-75
800- 100
600-100
400-100
i really cant figure out the right way to do that, but it seems to be working so far
for one, i needed the newest version of voltage control.....for two, im thinking that i was supposed to wipe the davik cache before install, because it did a different song and dance when i did that. for three.....for whatever reson the 1000hz version didnt seem to want to work for me....and finally....waiting for a while after the phone booted up i did see the CPU start to jump up to 1.4.
thanks guys!
Related
Hey everyone, there is an overclocking app in the market, anyone care to give it a try?
Edit: So I downloaded it lol. Here are some screenshots. BTW, is there anyway I can verify that the cpu freq is actually being adjusted?
*Just for fun I ran neocore to see if it would raise my FPS. lol.
just notice the difference in speed. If you notice please post. And its not overclocking its just clocking. Overclocking will be beyond 528 MHz
Gameloft said:
just notice the difference in speed. If you notice please post. And its not overclocking its just clocking. Overclocking will be beyond 528 MHz
Click to expand...
Click to collapse
The app is called Overclock, you can argue with the developer about the name not me.
Anyways, I do notice a very nice speed increase.
For example, atrackdog would take me at least 20-30 seconds to load my full app list (184 apps)
After installing overclock, it loaded in under 5 seconds.
i'll run other programs, and post my results.
I ran droidgear (game gear emulator) before and after, and I can honestly say it was faster (not a placebo affect).
-Before: droidgear would take over 4 minutes just to get to the menu screen
-After: i was actually able to load a game in under 1 and a half minutes, I even let it sit to run the demo, and it is the fastest ive ever seen an emulator run on this device (compared to NesEmu, and GB emu)
It would probably actually be playable if tweaks were made to the application codebase, and android Open GL stack.
Also, the camera loads instantly after pressing the camera button and via the icon in the home screen.
well, i was too, and then i downloaded it and said "aahh, what the hell, if i break mine, ill just take my wifes haha..." probably not the best of plans but i installed it anyway
sooo i havnt burnt up my phone yet, but here is my issue with the app, does the app only work untill you reboot your phone?
because when i reboot my phone, it goes back to the default speed according to the app
also, my phone tends to hang up (stuck on the apps screen, no buttons work, screen wont rotate, power button wont shut screen off) when using the 528MHz
so far, i havnt found a reason to pay a dollar for it, but ill keep testing
[UPDATE]
resolution for all below tests is 320 x 480
i tried neocore like posted above, using the mid level setting, and i actually did raise my fps from
DEFAULT CPU (248 MHz): 20.5 (with sound off)
384 MHz: 25.0! (with sound off)
DEFAULT CPU (248 MHz): 14.5 (with sound on)
384 MHz: 20.8 (with sound on)
still havnt gotten the fast speed to work yet, but im still trying to figure that out, on another note, sweeter home does seem to load a little faster
[UPDATE]
Incase you didnt see my sig, im not running on a ADP1 phone, so that might by why the fastest setting doesnt work for me, but so far 384MHz is making a noticeable difference with NEOCORE and SWEETER HOME
andonnguyen said:
The app is called Overclock, you can argue with the developer about the name not me.
Anyways, I do notice a very nice speed increase.
Also, the camera loads instantly after pressing the camera button and via the icon in the home screen.
Click to expand...
Click to collapse
i use snap photo, which used to take FOREVER to load up on my g1 using the camera button, its significantly faster using the 384MHz setting, good observation
Ok, so so far here is a list of things ive noticed (using 384MHz vs 248MHz):
-FPS in NEOCORE increased on adverage 5 to 6 fps
-Sweeter Home doesnt lag NEARLY as much as it used to (ALOT less force closes)
-Snap Photo doesnt take a month to load using the camera button
-G1 Wakes up properly which was a issue my g1 (and others on this forum) had
-Even though the app says it will "kill" the battery, using 384MHz during normal use of the phone isnt "killing" my battery, however, doom (while runs better (even with sound on)) seems to be dropping my battery level faster, but the game is running faster, which is the trade off id expect when running these apps together
At this point is there really a need? My phone doesnt lag that much that I need to over clock not to mention my battery life sucks already.
speoples20 said:
At this point is there really a need? My phone doesnt lag that much that I need to over clock not to mention my battery life sucks already.
Click to expand...
Click to collapse
all of our battery life sucks unless you have the extended battery, im not getting THAT big of a battery drain according to the system monitor app, and it DOES make a difference on g1's that have lag issues (running tons of apps like i do)
in other threads, people have complained about the g1 not waking up quickly sometimes, ive yet to have that issue since ive clocked mine up to the 384MHz setting
@woot, you do know that the default cpu freq on the G1 is ~384mHz. So you might want to change in your sig that you're overclocked to 384mHz lol.
The program installs a script on your sd card called ocx_tmp.sh and adjusts it that way, it'll write to /system as -rw (from what I've discussed with someone) would probably cause instability.
The program will reset the cpu freq back down to 384mHz after the phone sleeps. You can verify this in terminal emulator by typing:
$su
#cat /proc/cpuinfo
Try it before and after setting the cpu freq in overclock and you'll see what I mean =)
I thought the the CPU ran at 528 MHz by default? Or is it clocked dynamically and this forces it?
Gameloft said:
just notice the difference in speed. If you notice please post. And its not overclocking its just clocking. Overclocking will be beyond 528 MHz
Click to expand...
Click to collapse
andonnguyen said:
@woot, you do know that the default cpu freq on the G1 is ~384mHz. So you might want to change in your sig that you're overclocked to 384mHz lol.
Click to expand...
Click to collapse
im not as familiar with clocking/overclocking so i wasnt sure if i was clocking it to 384, overclocking it to 384, or what, so what would be the proper thing to put in my sig? lol because according to my first quote, true overclocking wouldnt be untill i went beyond 528, so from the view of my first quote, im not OVERclocking, im clocking, wheras your saying im overclocked
andonnguyen said:
The program will reset the cpu freq back down to 384mHz after the phone sleeps. You can verify this in terminal emulator by typing:
$su
#cat /proc/cpuinfo
Click to expand...
Click to collapse
so is it infact the program thats changing the cpu freq or is it the phone? if its the program, is this to avoid overworking the cpu without the demand?
andonnguyen said:
.
The program will reset the cpu freq back down to 384mHz after the phone sleeps.
Click to expand...
Click to collapse
by sleep do you mean turning the screen off using the power button? because i saw no change in my cpu freq when doing so using your commands
ivanmmj said:
I thought the the CPU ran at 528 MHz by default? Or is it clocked dynamically and this forces it?
Click to expand...
Click to collapse
dont know, but i found this over at the android community:
Technical Features
Supports WCDMA/HSUPA and EGPRS networks
Multimedia Broadcasting Multicast Service (MBMS)
Integrated ARM11™ applications processor and ARM9™ modem
QDSP4000™ and QDSP5000™ high-performance digital signal processors (DSP)
528 MHz ARM11 Jazelle™ Java® hardware acceleration
Support for BREW® and Java applications
Qcamera™: Up to 6.0 megapixel digital images
Qtv™: Playback up to 30 fps VGA
Qcamcorder™: Record up to 24 fps QVGA
Up to 4 million triangles per second, and 133 million depth-tested, textured 3D pixels per second fill rate
gpsOne® position-location assisted-GPS (A-GPS) solution
Support for third-party operating systems
Digital audio support for MP3, aacPlus™ and Enhanced aacPlus
Integrated Mobile Digital Display Interface (MDDI), Bluetooth® 1.2 baseband processor and Wi-Fi® support
maybe that info will help? if not sorry
I remember reading somewhere by someone that it runs at 384 by default, and I think the post above confirms that...
ivanmmj said:
I thought the the CPU ran at 528 MHz by default? Or is it clocked dynamically and this forces it?
Click to expand...
Click to collapse
no, it runs at 384 by default, and clocks down even lower in the idle loop.
i am curious how this program works, as the normal cpufreq interfaces are not compiled in the kernel.
i've been running my phone for several months now at 528mhz, at a fairly minimal detriment to battery life.
i did however notice that without modifying the idle loop, the amount of cpu frequency switches even while the phone is not sleeping drops your average clock within a 10 second period to somewhere closer to 400mhz.
after modifying the idle loop to not switch frequency so often, i was able to get 27.4fps out of neocore w/o sound, and 22.7fps w/ sound.
my overall caffeine benchmark score was 582.
battery life impact is there, but fairly small. phone lasts for about a day and a half now where it used to last for sometimes 2. under heavy use, this is of course dramatically reduced.
gui fluidity is definitely increased, and sluggishness between app switches and when the translucent app drawer opens up is gone. i like it, but to the average person there probably is no need to do it.
keep in mind this is also not overclocking the cpu, it's clocking it to its default spec. as it is an embedded arm, it is designed to run hot, so i guarantee you are in no danger of hurting your phone.
also, do not listen to people that claim there could be no gain from overclocking, just because the bus speed is slower than the cpu speed does NOT mean there will be no improvement in system performance. if that were the case, there'd be no use for 4ghz desktop processors.
cache still runs full speed, and common execution paths stay in cache meaning no prefetch from system memory, meaning BIG improvement in many cases. (that's why cache exists.)
damnoregonian said:
no, it runs at 384 by default, and clocks down even lower in the idle loop.
i am curious how this program works, as the normal cpufreq interfaces are not compiled in the kernel.
i've been running my phone for several months now at 528mhz, at a fairly minimal detriment to battery life.
i did however notice that without modifying the idle loop, the amount of cpu frequency switches even while the phone is not sleeping drops your average clock within a 10 second period to somewhere closer to 400mhz.
after modifying the idle loop to not switch frequency so often, i was able to get 27.4fps out of neocore w/o sound, and 22.7fps w/ sound.
gui fluidity and responsiveness is greatly improved. sluggishness if app switching and the translucent app drawer are completely gone.
for many i imagine this means there isn't really any reason to clock the cpu up to its stock speed, but to each their own.
my overall caffeine benchmark score was 582.
battery life impact is there, but fairly small. phone lasts for about a day and a half now where it used to last for sometimes 2. under heavy use, this is of course dramatically reduced.
Click to expand...
Click to collapse
care to write up a how-to for getting the 582 consistantly and changing the idle loop?
Holy crap. Used this @528MHz with Haykuro's version 4.5 apps to sd ROM and the osk works SO MUCH BETTER!!!! Also I got 25.6 fps on neocore... very smooth
wootroot said:
care to write up a how-to for getting the 582 consistantly and changing the idle loop?
Click to expand...
Click to collapse
writeup? no. it's a big process involving the android dev environment, a modified version of mkbootimg and unyaffs.
i will gladly post the kernel modifications for those who want to recompile the kernel to do so.
the bootloader sets the clock speed, and the idle loop simply clocks down to a preset and back up to whatever it was previously after x milliseconds of inactivity (not to be confused with sleep) it's kind of a poor man's cpufreq arbitrator.
so on top of tweaking the idle loop to not drop down as often, you also have to explicitly set the frequency in the kernel upon bootup, or it will bet set at what it thinks is full speed, which is 384.
A modded version of JF's ROM would ROM.
I DO notice the sluggishness and it bugs the heck out of me. (I switched from a WING with a 200MHz CPU, and although it IS faster than the wing, it doesn't seem significantly faster and seems to much slower when I open up the camera...
damnoregonian said:
writeup? no. it's a big process involving the android dev environment, a modified version of mkbootimg and unyaffs.
i will gladly post the kernel modifications for those who want to recompile the kernel to do so.
the bootloader sets the clock speed, and the idle loop simply clocks down to a preset and back up to whatever it was previously after x milliseconds of inactivity (not to be confused with sleep) it's kind of a poor man's cpufreq arbitrator.
so on top of tweaking the idle loop to not drop down as often, you also have to explicitly set the frequency in the kernel upon bootup, or it will bet set at what it thinks is full speed, which is 384.
Click to expand...
Click to collapse
that involved eh?
thanks for this post though, now i understand more about the idle loop and why the cpu freq resets with each reboot
maybe someone can take this stuff further like he said, that kind of stuff would be worth the dollar, imo more than a dollar
well... i don't mind providing basic procedure and source, i just don't want to get dragged into level 1 support of the procedure.
i'll go ahead and package up some source, prebuilt boot images based on JF's RC33 (which is what i run) and a basic procedure.
I've done numerous tests with and without OC and on different kernels (both normal and custom). So far SetCPU have only given me headaches. Random crashes, unable to wakeup, kernel panics... The list goes on.
According to these tests I've come to the conclusion that SetCPU is very unstable on Galaxy S and should not be considered supported at all.
What's your experience with SetCPU on Galaxy S? Is it conclusive with mine? Do you experience the same problems with Overclock Widget, or is it more stable?
after using setcpu for a few weeks and getting similar problems, i removed it.
There is pretty much no use in it for this phone, they allready scale from 100mhz - max speed (even oc if you have one) automatically
mekwall said:
I've done numerous tests with and without OC and on different kernels (both normal and custom). So far SetCPU have only given me headaches. Random crashes, unable to wakeup, kernel panics... The list goes on.
According to these tests I've come to the conclusion that SetCPU is very unstable on Galaxy S and should not be considered supported at all.
What's your experience with SetCPU on Galaxy S? Is it conclusive with mine? Do you experience the same problems with Overclock Widget, or is it more stable?
Click to expand...
Click to collapse
Are you using a task manager? I had the same problem as you until I removed the auto task killer I had previously installed. Now I can set setcpu to 100000 min 1000000 max ondemand for main with a profile of screen off 100000 min 1000000 max conservative.
mekwall said:
I've done numerous tests with and without OC and on different kernels (both normal and custom). So far SetCPU have only given me headaches. Random crashes, unable to wakeup, kernel panics... The list goes on.
According to these tests I've come to the conclusion that SetCPU is very unstable on Galaxy S and should not be considered supported at all.
What's your experience with SetCPU on Galaxy S? Is it conclusive with mine? Do you experience the same problems with Overclock Widget, or is it more stable?
Click to expand...
Click to collapse
Yes. I have the same problem on my stock SGS.
Setcpu is not working good on sgs. Try to remove it, and you'll get better battery life.
Sent from my GT-I9000 using Tapatalk
I don't know of anyone who has tested it on the I9000 (and there may even be alternatives or the same thing floating around the development subforum), but they claim to have a 1.2ghz overclocked kernel here for the I9000. Maybe best to be avoided, but a 100% use at your own risk alternative, especially if you're a bit unsure on any of the translated steps, is available here.
http://translate.google.com/transla.../matpclub.com/board/index.html?id=tipn&no=144
been using it on a vibrant for about 10 days and had my first issue last nite - it froze the phone - had to remove battery to reboot, tried again, froze it again
i thought it was the last two apps i'd installed so i removed them, then there was an update, downloaded and installed, so i did a number of settngs changes, closing setcpu, running benchmark quad, reopening & changing settings etc
about half dozen times
and it's been fine so far -
I had the same issue. I would pull my phone out of my pocket and it wouldn't wake up. I could call my phone and it would ring but my phone would do nothing until I removed the battery and re-booted. This happened numerous times until I uninstalled SETCPU and it stopped doing that so I knew I found the culprit and haven't tried it again since (I need to receive calls as priority 1)
doesnt anyone search anymore i posted this issue over a month ago. setting cpu mode to anything on than conservative can cause freezes as the system doesnt get enough cpu to wake up.. it is even mentioned in set cpu to use conservative.
lgkahn said:
doesnt anyone search anymore i posted this issue over a month ago. setting cpu mode to anything on than conservative can cause freezes as the system doesnt get enough cpu to wake up.. it is even mentioned in set cpu to use conservative.
Click to expand...
Click to collapse
I have it set to Conservative on my Vibrant, and I'm having the same issues as the OP.
Edit: When I go into SetCPU after pulling the battery and resetting, it shows it's limiting my CPU to 19.2 MHz. Yes, 19.2. Insane.
tt4079 said:
Are you using a task manager? I had the same problem as you until I removed the auto task killer I had previously installed. Now I can set setcpu to 100000 min 1000000 max ondemand for main with a profile of screen off 100000 min 1000000 max conservative.
Click to expand...
Click to collapse
I killed my task manager service, and it didn't freeze up! I'm going to uninstall the task manager and see if I have any more freezing issues in the future.
Edit: Nope, didn't work. Removing SetCPU.
mekwall said:
What's your experience with SetCPU on Galaxy S?
Click to expand...
Click to collapse
I have the Vibrant version with T-Mo. After rooting, Titanium, Barnacle and Root Explorer all seem to be working fine.
After a few minutes of installing SetCPU, my phone wouldn't wake up. Rebooted twice, same results.
Removed SetCPU and the phone's working fine again. Maybe the minimum speed should be set at 250 or so?
George
To begin with, you don't even need SetCPU
SGS phone automatically regulates the speed of the CPU depending on your usage.
most of the time in Stock ROM it hover around 200 Mhz, very few times it uses the max 1000 Mhz
only when there are lots of background apps running
when you runt he CPU at 1000 Mhz it gets hot fast, and it consumes more battery
good thing is it drops back down to 100~200 Mhz as soon as it's done with the heavy tasks
so having the SetCPU installed will defeat the whole purpose of power saving and CPU cycle on demand
mekwall said:
I've done numerous tests with and without OC and on different kernels (both normal and custom). So far SetCPU have only given me headaches. Random crashes, unable to wakeup, kernel panics... The list goes on.
According to these tests I've come to the conclusion that SetCPU is very unstable on Galaxy S and should not be considered supported at all.
What's your experience with SetCPU on Galaxy S? Is it conclusive with mine? Do you experience the same problems with Overclock Widget, or is it more stable?
Click to expand...
Click to collapse
I don't even remember the last time where we had a fixed clock on a cpu Allgamer. The point of setcpu is to either downclock or overclock your cpu. You might want to limit your clock to 0.6GHz just to save some juice.
Anyway, after a few hours of head scratching and 2 reboots, I uninstalled and refunded it.
I agree. Setcpu is rather unstable. I have feeling lots of the kernel overclockers have problems but blame the kernel while they should blame setcpu
i have just installed setcpu. it's probably been about a day or so now and i have not experienced any problems?
i have an Australian model (I9000) just flashed to the canadian firmware for the 3br fix.
Is it just generally not recommended to use setcpu on my SGS?
please advise. Thanks
toansta said:
i have just installed setcpu. it's probably been about a day or so now and i have not experienced any problems?
i have an Australian model (I9000) just flashed to the canadian firmware for the 3br fix.
Is it just generally not recommended to use setcpu on my SGS?
please advise. Thanks
Click to expand...
Click to collapse
It depends on what you're using it for. If you know what you're doing, it can be a useful tool. If you want to overclock, you'll want setcpu. If you want to underclock (lets say you're out and about, with 40% battery), then you can set the maximum cpu speed lower so that the battery will last longer.
You don't need setcpu if you're simply going to tell it that you want your max speed to be 1ghz, with a min of 100mhz and you want it to be "conservative". Your phone does that by default, and frankly the SGS is pretty good on its own when it comes to battery management.
thanks reuthermonkey, i will keep that in mind.
What are the perfect setcpu 2.0.3 settings for froyo JP6 I9000 rooted? Thanx in advance
Telanis said:
I have it set to Conservative on my Vibrant, and I'm having the same issues as the OP.
Edit: When I go into SetCPU after pulling the battery and resetting, it shows it's limiting my CPU to 19.2 MHz. Yes, 19.2. Insane.
Click to expand...
Click to collapse
Menu and rescan the device should restore the normal values. those values are not the ones actually used!
Suckerpunch Kernel on Serendipity 6.2
I was playing around with OCing to 1.3 after achieving a stable 1.2 OC, and stupidly set to boot settings instead of applying on accident. Had to turn phone off for a bit to save power, fast forward an hour when I turn it on; get a kernel panic on boot, do a battery pull & reboot; get to homescreen, fiddle around a bit, freezes, batt pull again, eventually (after 2 more kernel panics) figure out that I had stupidly set the settings to boot instead of applying. Could this have caused any damage or added any sorts of instabilities to my phone?
No it should be fine. As long as you put the OC level down to 1200 or 1000 (and also the Undervolt (UV) settings if you messed around with those) and to save that as the new boot setting, it should be alright.
venomio said:
No it should be fine. As long as you put the OC level down to 1200 or 1000 (and also the Undervolt (UV) settings if you messed around with those) and to save that as the new boot setting, it should be alright.
Click to expand...
Click to collapse
Yep, done that. I do have a question about the active states, though; are those the frequencies which the phone will utilize?
Typically yes, getting to 1200Mhz should be easy and no problem... It's really a balancing act.
http://forum.xda-developers.com/showpost.php?p=10936691&postcount=1102
This guide helped me get started at first, and it will definitely help you optimize your OC/UV settings.
venomio said:
Typically yes, getting to 1200Mhz should be easy and no problem... It's really a balancing act.
http://forum.xda-developers.com/showpost.php?p=10936691&postcount=1102
This guide helped me get started at first, and it will definitely help you optimize your OC/UV settings.
Click to expand...
Click to collapse
I've read that, yes, that's where I got started as well. However, I don't understand fully what the States option in Voltage Control does.
snapplefish said:
I've read that, yes, that's where I got started as well. However, I don't understand fully what the States option in Voltage Control does.
Click to expand...
Click to collapse
Selecting states in VC is what allows the phone to use that state. So if you set your max clock to 1200, but 1000 is the max state you have checked, the phone will only ever use 1000 as the max. You need to set both options.
Hi there,
really sorry if this has already been around, but i've been searching this forum up and down and didn't find a thing.
Anyways, i was wondering how i could enable overclocking under cm11 nightly? Could anyone point me towards a solution? Thanks
Well ...
http://forum.xda-developers.com/droid-4/development/5-0-custom-oc-kernel-t3041512
It should work (in the past it works)
Install it on your Cyanogenmod Rom
Fervi
ferviverus said:
Well ...
http://forum.xda-developers.com/droid-4/development/5-0-custom-oc-kernel-t3041512
It should work (in the past it works)
Install it on your Cyanogenmod Rom
Fervi
Click to expand...
Click to collapse
There's a guy who said that that kernel doesnt work on cm11...it work's for you in the past?
For CM11 and other AOSP 4.4 ROMS, the most fully-featured and overclockable kernel is JBX. You can use the one intended for the RAZR.
Joojoobee's is good, and certainly the best for Lollipop, but due to its extra voltage management stuff the JBX kernel has a higher overclock ceiling.
Use the newest kernel from here.
Boot into Safestrap, make a backup in case something goes horribly wrong, then flash the package to start up the installer. In the installer, don't install any of the tweaks, at least a couple of them cause instability for our phone, and don't bother with the init.d stuff. Just install the kernel itself and Trickster Mod. Trickster, FYI, is probably the best app for managing JBX, but other apps can as well.
Done. Reboot phone, hopefully it won't bootloop, once back up increase speed until it starts freezing when you try to use it, bump voltage 10-20mv, find ceiling again. I think the JBX thread has better/more detailed instructions, but that's about the gist of it.
Maximum advised voltage is 1490mv iirc, don't try to even approach that unless you want to cook eggs on the back of your phone.
Thanks a bunch!
After messing around with both solutions, Jojobee's solution gave me a bootloop but the other one worked.
However i can't seem to get past 1300mhz when overclocking, that seems to be the limit. I was aiming to try to reach 1400, any idea how i could go about that? I can't seem to find an option to set the max frequency higher than 1300.
Well i was playing a little with JBX kernel..these are my conclusions:
- Kernel install/works fine if you don't install 10% battery mode..otherwise you are goingo to have android crashes
- Kernel performance it's below than current cm11 m13 stock kernel...i believe is due to full scale freq that it has...cpu spend a lot time switching from one freq to another...if you overclocked you will have almost the same performance than NON-OC stock kernel..that's why stargo applied and later reverted full scale on stock months ago...meaby if JBX kernell would have support to boost driver (like cm12 OC kernel) it would be better...but it hasnt...
So my conclusions...dont waste time on JBX kernel...sorry my 4 my english
Enviado desde mi XT894 mediante Tapatalk
Milp said:
However i can't seem to get past 1300mhz when overclocking, that seems to be the limit. I was aiming to try to reach 1400, any idea how i could go about that? I can't seem to find an option to set the max frequency higher than 1300.
Click to expand...
Click to collapse
I don't think you can set the CPU higher than 1.3ghz, at least not in the way you're thinking.
In the case of the JBX kernel, you overclock the Main Processor Unit (MPU) speed. I don't remember what tab it's under in Trickster, but it should be the same one as the voltage settings. I couldn't even begin to guess where it'd be as far as other apps.
The default is 100mhz. This is multiplied by each frequency step; e.g. 1.3ghz is actually a 13x multiplier of the base 100mhz.
So to obtain 1.4ghz(ish), simply increase the MPU clock from 100mhz to 108mhz, since 108*13=1404.
If you're lucky, you'll be be able to do this without needing to touch the voltage, if not...read the FAQ in the JBX post, because I don't remember offhand exactly how to set voltages :v
Once you know how, I would think a 5-10mv bump would be all that'd be needed to stabilize most CPUs for 1.4ghz.
fyi, ignore if you already have stuff for these:
Antutu is a decent app for both testing stability and checking to make sure you're not hitting the heat throttle.
Cooltool isn't a bad thing to use either, if configured to show CPU speeds, since it'll show you if the CPU has been forcefully throttled back (if the CPU gets too hot, it'll forcefully change the maximum multiplier to 10x/11x to protect itself from baking; if it does, back your voltage off and be happy with whatever speed you've attained).
dear modders
i just want to say i overclocked my htc one m7 cpu from 1.7ghz to 2.1 GHZ
with a custom kernel called ElementalX-m7-22.3-Sense
is this save can the phone run this without any stability issue's or shall i downclock it to 1.9
i use M7_Sense7_artmod_10.0 rom Lolipop 5.0.2 with sense 7 cause this is the only one without any bugs like no sound when you got called or sms sound's no boot sounds
i fixed my boot sound anyway on this rom
so my question is wont my phone be fried by this overclock cause i saw in the aroma installer that it can be overclock till 3 GHZ
greets Rubenownz
Overclocking the CPU in any system usually results in 2 main things:
a. Significantly shorter battery life.
b. heating issues.
sometimes (less frequently) you might experience a crash and fc here and there.
So yeah, it won't be all rainbows and butterflies.
PS: you probably won't reap the benefits of your now overclocked CPU without an app like no frills CPU or kernel Aduitor. Your device's performance isn't just about its CPU frequency, there's the min Max frequency your system is allowed to utilize, the CPU governor, and the I/o scheduler..
and
PPS: don't and I repeat DO NOT go anywhere near 3 GHz.
good luck.
I'm runnimg 2.1 Ghz OC for over 2 years without any issues. I would like to note that 2.1 Ghz on Elemental was not too stable for me, so I ran that on 2.0 Ghz. Anyway - i don't have any issues with my kernel, no overheating, battery lasts 100% same as stock frequency, no reboots, everything works as it's ment to work. If you really want to run on that frequency, make sure you set your voltage table to match your CPU clocks. Undervolting is not a good idea on such high clocks, so you might want to raise your voltages for higher frequencies a bit
monrokhoury said:
Overclocking the CPU in any system usually results in 2 main things:
a. Significantly shorter battery life.
b. heating issues.
sometimes (less frequently) you might experience a crash and fc here and there.
So yeah, it won't be all rainbows and butterflies.
PS: you probably won't reap the benefits of your now overclocked CPU without an app like no frills CPU or kernel Aduitor. Your device's performance isn't just about its CPU frequency, there's the min Max frequency your system is allowed to utilize, the CPU governor, and the I/o scheduler..
and
PPS: don't and I repeat DO NOT go anywhere near 3 GHz.
good luck.
Click to expand...
Click to collapse
ok mate
yeah i could raise also min clocks might turn that a noch up
just was wondering if it was possible without any harms
there are now on 384mhz 1 core is always active and 3 others are sleeping aid64 tells me
the temps are now 29 celcuis for 2.1 ghz
donkeykong1 said:
I'm runnimg 2.1 Ghz OC for over 2 years without any issues. I would like to note that 2.1 Ghz on Elemental was not too stable for me, so I ran that on 2.0 Ghz. Anyway - i don't have any issues with my kernel, no overheating, battery lasts 100% same as stock frequency, no reboots, everything works as it's ment to work. If you really want to run on that frequency, make sure you set your voltage table to match your CPU clocks. Undervolting is not a good idea on such high clocks, so you might want to raise your voltages for higher frequencies a bit
Click to expand...
Click to collapse
yeaah the kernel has those options in aroma installer it set it safe i ques
ill post later some picture's of what ive been doing
good nites
here are some pictures of my sense 7 5.0.2 android system dump of htc one m9 for htc one m7 xD overclocked
some temps and cpu tweaks and ofc of the system (dont mind about the girl on the screenshot its my girlfriend not me iam a boy
btw i removed phone number on call menu cause it's private
Greets Rubenownz