After restoring to stock from dags oc kernel. I noticed the stock processor freq. Is 810mhz...is this right? Seems low for a advertised 1.5 GHZ.. I had to restore due to fc's, is there another method to get Overclocking?
Sent from my SGH-I717D using XDA
crielstar said:
After restoring to stock from dags oc kernel. I noticed the stock processor freq. Is 810mhz...is this right? Seems low for a advertised 1.5 GHZ.. I had to restore due to fc's, is there another method to get Overclocking?
Sent from my SGH-I717D using XDA
Click to expand...
Click to collapse
Download CPU spy from the market. Play some games then open the CPUSpy to see if it's still 810Mhz
Played GTA 3 for a couple mins, its still at 810Mhz!...
i can confirm this....
i have 2 notes, one ROMed and the other stock. just downloaded CPU SPY and with a 261:42 time in state, 40% goes to 810, 52% 384, and deepsleep is 40%.
now, it does show 1512, 1458, 1404, 1350, 1296, 1242, 1188, 1134, 1080, 1026, 972, 918, 864, 810, 756, 702, 648, 594, 540, 486, 432, 384, 192...... other then the ones listed above, they all show 0%, and less then 5 minutes. i think the best was 4:30 something in state and that was 1512.
On my stock Note, disabling the system power savings brings the higher cpu freqs into play.
Ipaqman01 said:
On my stock Note, disabling the system power savings brings the higher cpu freqs into play.
Click to expand...
Click to collapse
Thanks!!, I owe you a beer!
.def wont turn that on again, made it so slow lol.
Is it possible that the FC's were caused by the Power Saving feature being active when you were trying to overclock? Maybe now that you have that feature disabled, you can try it again. Couldn't hurt.
Related
Thats right, just loaded it up after rooting this bad boy and it is working just fine!
I am not responsible if you brick your device in the process.
UPDATE!
Ok so here is what is needed to run this badboy without problems.
Use only the conservative option (least problematic and no sleep comas)
I dont use the widget, i already know the speeds i set it at.
The settings stick even after a reboot, but when you click on the setcpu icon they revert back and you lose your settings. If that happens just go back and click on detect auto speeds and set up your speeds again.
Happy clocking!
what version? 2.0.1?
Were you able to overclock it past the 1ghz?
I rooted mine today and installed setCPU which worked flawlessly but I am not able to move the slider past 1ghz.
I loaded it on mine and while it *appears* to work, it doesn't seem to effect the clocks any.
heck just underclock your phones to save battery lol
I can only seem to clock mines to 800? hmm. I noticed when i first opened setcpu it was clocked to 384/245!! wow so low
edit: setting it to nexus one/snapdragon Qsd it clocks to 1ghz exact. not really sure it's working though
jroid said:
I can only seem to clock mines to 800? hmm. I noticed when i first opened setcpu it was clocked to 384/245!! wow so low
edit: setting it to nexus one/snapdragon Qsd it clocks to 1ghz exact. not really sure it's working though
Click to expand...
Click to collapse
To see if it's working set it to underclock and then get into an adb shell and run the command: cat /proc/cpuinfo
It should display cpu data that includes the current clock speed.
I don't know if this helps but when I was in the Quadrant Standard app it has the system info. I hit it, scrolled down to cpu and it said
Current: 400 mhz, Max: 1000 mhz, Min: 100 mhz,
and I just checked it now and it said my current clock was 800 mhz, so i guess the cpu scales dynamically based on what the load is and what we are doing, thats a pretty great power saving feature.
Select 'Auto Detect'.
I believe you need an oc'd kernal to be able to move the slider past 1ghz.
Also, the dev has stated that it should be set to 'conservative', not 'ondemand'. 'Ondemand' was causing random shutdowns on the Galaxy S.
I installed SetCPU on my Vibrant too but removed it because it appears that it caused the phone to power off.
Does there need to be device specific support for a processor/device or does the auto-detect work on any processor?
Koblek said:
I installed SetCPU on my Vibrant too but removed it because it appears that it caused the phone to power off.
Does there need to be device specific support for a processor/device or does the auto-detect work on any processor?
Click to expand...
Click to collapse
Look at the post before yours.......from me.
SetCPU needs to be set to 'conservative' on the Vibrant, not 'ondemand'. Also, per the dev in the "Random shutdowns?" thread: "You can "simulate" ondemand by changing freq step in Advanced to 100%"
Has anyone noticed any significant battery conservation with this?
MINUS Stl said:
Look at the post before yours.......from me.
SetCPU needs to be set to 'conservative' on the Vibrant, not 'ondemand'. Also, per the dev in the "Random shutdowns?" thread: "You can "simulate" ondemand by changing freq step in Advanced to 100%"
Click to expand...
Click to collapse
Hey, sorry if this sounds like a stupid question, but why does it max out at 800,000?
i am still having problems with setcpu even on conservative mode. i have stopped using setcpu completely for now.
wbexpress said:
Hey, sorry if this sounds like a stupid question, but why does it max out at 800,000?
Click to expand...
Click to collapse
Auto detect...
Sent from my SGH-T959 using XDA App
i have this on my rooted vibrant. Max is 1000 and Min is 100. My battery life has doubled. I have not experienced any force closes, no slowness and no freezing. the phone is running super fast and smooth. Love it. After looking at the stats, it seems like the CPU uses 400 and 800 a lot.....thats probably where the extra battery life comes into play. 1000 is used when on full load.
mygti02 said:
i have this on my rooted vibrant. Max is 1000 and Min is 100. My battery life has doubled. I have not experienced any force closes, no slowness and no freezing. the phone is running super fast and smooth. Love it. After looking at the stats, it seems like the CPU uses 400 and 800 a lot.....thats probably where the extra battery life comes into play. 1000 is used when on full load.
Click to expand...
Click to collapse
What are your exact settings in profiles, advanced and overview?
any one running their phone at 1Ghz all the time?
+1, hah2110 please post your settings if they're working for you so a noob like me can learn some things!
I had my S2 set to 1.6GHZ and noticed very little battery drop compared to 1.2ghz (stock) so now I am just wondering if it would help me save battery if I set it to 800mhz?
Anyone know if this will help?
And for some reason SETcpu only detects the S2 as 1 core. So hopefully thats just an error and I hope I really have a dual core phone.
Which kernel are you using?
I am on Light'ning 6.1 (2.6.35.11 ninphetamine-2.0.5+)
XXKH3
Changing CPU speeds will not help you save battery. Undervoltaging (UV) will, however. UV only works on certain kernels, and you MUST know what you're doing before attempting to overclock and undervoltage simultaneously. Read up OC/UV guides around the forum to know more and the recommended speed/voltage pairings.
Sent from my GT-I9100 using XDA App
darylimjz said:
Changing CPU speeds will not help you save battery. Undervoltaging (UV) will, however. UV only works on certain kernels, and you MUST know what you're doing before attempting to overclock and undervoltage simultaneously. Read up OC/UV guides around the forum to know more and the recommended speed/voltage pairings.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
I'll be staying far away from that then. Thanks!
of course underclocking will give you a bit more battery life. even if you don't undervolt.
underclocking it to 800 simply forbids the processor to go up to 1 or 1.2ghz and it doesn't need as much power as in the higher states.
a normal desktop cpu also gets hotter if its overclocked with its stock voltage. But if you crank up the voltage too, to keep it stable it will get even hotter.
Sent from my GT-I9100 using XDA App
Well, Nordic hardware has done some tests. Undervolting CPU and GPU will not save your batterylife significantly.
http://www.nordichardware.se/test-l...kt-pa-laengre-batteritid.html?start=3#content
The article is in Swedish, but all graphs are in English.
supermult said:
of course underclocking will give you a bit more battery life. even if you don't undervolt.
Click to expand...
Click to collapse
Actually it shouldn't. A faster speed allows the CPU to finish the task faster and then go to sleep...
Cane Phoenix said:
Actually it shouldn't. A faster speed allows the CPU to finish the task faster and then go to sleep...
Click to expand...
Click to collapse
Yes, exactly!
Sent from my GT-I9100 using xda premium
NoOneCanHelpMe said:
Yes, exactly!
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
That may be true, but higher frequencies have a higher power draw, the phone at lower speeds should be able to manage with whatever the task is, assuming it's not a extensive app. If you're not a power user you don't need the phone to be clocked at the max freq, you can lower it and you see minor changes in battery life. With dual cores task are handled must better so 1.2ghz+ shouldn't really be needed, TouchWiz can't be as bad as Sense, where you actually need it to be clocked higher.
Oh man, Undervolting is OK but why would you Underclock a CPU? Now don't tell me it's too fast, don't need that speed in real world, you won't notice any difference and etc..If you are gonna Underclock it why did you purchase it on the first place?
Besides, that article said it all.
Regards.
For me I think underclocking + undervolting does indeed save battery life.
What I mean is that in my sig '1.6Ghz - 1325 mV' an at '800Mhz -950 mV' you see a difference of 375mV which I think can save your battery life for a couple of good minutes + 800Mhz is enough for my needs along with playing games (Only a tad slower at loading).
That's not necessary true. Yes at a higher frequency the task would complete faster but at the same time the processor with use more current and or increased voltage at the same time. That's why cpu's level up and down. Otherwise why not have the CPU set at 200Mhz-1200Mhz instead of 200-400-800-1000-1200Mhz.
Sent from my GT-I9100 using XDA App
Cane Phoenix said:
Actually it shouldn't. A faster speed allows the CPU to finish the task faster and then go to sleep...
Click to expand...
Click to collapse
Please set your computer on fire and never return to the internet ever again so it doesn't have to be filled with your stupid statements.
Also yes underclocking saves battery, anyone who says it doesn't is dumb, you wanna see for yourself? set your phone to 1.6 GHz all the time, according to you people this wouldn't significantly drain the battery any more right?
Undervolting saves slightly more battery than underclocking.
Also why would you underclock + undervolt the phone? Because it saves battery and you won't find any noticeable performance gains between 800 MHz and 1.6 GHz.
seshmaru said:
Please set your computer on fire and never return to the internet ever again so it doesn't have to be filled with your stupid statements.
Also yes underclocking saves battery, anyone who says it doesn't is dumb, you wanna see for yourself? set your phone to 1.6 GHz all the time, according to you people this wouldn't significantly drain the battery any more right?
Undervolting saves slightly more battery than underclocking.
Also why would you underclock + undervolt the phone? Because it saves battery and you won't find any noticeable performance gains between 800 MHz and 1.6 GHz.
Click to expand...
Click to collapse
underclock + undervolt = winning !
Jigsy75 said:
underclock + undervolt = winning !
Click to expand...
Click to collapse
My phone is running at 751mv at 200mhz on tick-over and is ok. Lots of battery life!
Sent from my GT-I9100 using XDA Premium App
darylimjz said:
Changing CPU speeds will not help you save battery. Undervoltaging (UV) will, however. UV only works on certain kernels, and you MUST know what you're doing before attempting to overclock and undervoltage simultaneously. Read up OC/UV guides around the forum to know more and the recommended speed/voltage pairings.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Changing cpu speed upwards will use more battery life.
Sent from my GT-I9100 using XDA Premium App
http://forum.xda-developers.com/showthread.php?t=1239176
this is another topic discussing its effect on heat generation
so whats ur opinion ???
Damn right underclocking is saving battery, just doubled battery life with setcpu @ 500 max settings try it you will see
jody2k said:
Damn right underclocking is saving battery, just doubled battery life with setcpu @ 500 max settings try it you will see
Click to expand...
Click to collapse
SetCPU to 500
Sent from my GT-I9100 using XDA Premium App
Is it safe to overclock the Touchpad using setcpu? I have it at 1.5 ghz and it seems to be working fine.
kscully said:
Is it safe to overclock the Touchpad using setcpu? I have it at 1.5 ghz and it seems to be working fine.
Click to expand...
Click to collapse
I have been reading about this all day. Some people have claimed that once your device goes to sleep it does not wake up unless you press the POWER + HOME buttons at the same time for 30 sec. I guess YMMV.
Overclocking so far works well. I see no problems as of yet. Just make sure you OC with setcpu; frequencies do not show up in cmsettings when you try to OC there.
Sent from my HTC Glacier using XDA Premium App
atapia984 said:
I have been reading about this all day. Some people have claimed that once your device goes to sleep it does not wake up unless you press the POWER + HOME buttons at the same time for 30 sec. I guess YMMV.
Click to expand...
Click to collapse
mines not overclocked and has happened 4 times today. So, obviously not an overclock only problem. I will tinker around with it, but ive yet to tell myself...man, this needs to be speedier. Its run QUICK. far quicker than WebOS and its many 10second pauses (OCed to 1.7 and patched to boot..)
atapia984 said:
I have been reading about this all day. Some people have claimed that once your device goes to sleep it does not wake up unless you press the POWER + HOME buttons at the same time for 30 sec. I guess YMMV.
Click to expand...
Click to collapse
Haven't tested it yet, but some say it's a problem due to the "minimum cpu speed" setting when it goes to deep sleep. Something about it being too low and thus can't get out of sleep and setting the minimum higher (not sure of they value) should remedy that.
I'm using SetCpu with a OC of 1.5 and a minimum of 384 with no issues.
my question is should I click the box for set on boot?
i do. set on boot, min 384 max 1512, ondemand tcl
no sleep death, no lag, working great! (mind you im still on CM7 A1, by preference)
What is the difference between ondemand and ondemandtcl settings? Also, any problems encountered running 1.7g I've only read people running 1.5g...
There's a fix to the Sleep of Death issue and that worked for me. I thought using SetCPU caused the sleep problem but that doesn't seem to be the case. I'm going to see how far I can overclock my TouchPad now
link
I'm running Setcpu at 384/1.7 with zero problems.
I was having issues at first with failure to wake from sleep but after I changed my min to 384 It has not failed once. All my little problems went away when I made this change. Been running for 12 days without a single need to reboot.
butikofer08 said:
What is the difference between ondemand and ondemandtcl settings? Also, any problems encountered running 1.7g I've only read people running 1.5g...
Click to expand...
Click to collapse
i run 1.5 purely for performance/battery conservation but it goes to 1.7 just as easily too.
also traditionally:
Ondemand - Both CPU cores freely move up and down as needed.
Ondemandtcl - prefers the use of CPU0 unless CPU1 is absolutely necessary for use, then it will kick in. otherwise it will remain idle
does anyone try alpha 3?
I saw people said touchpad freeze when using setcpu. Does it work well?
im oc with 1728 max and 192 min ondemand. no issues or sleep of death. im thinking of bumping it up to 1.8ghz like i have in webos.
hey guys.
i have been wondering about this problem for a long time, and i could not find a solution to it. Thus, i wanted to ask you guys about it. The max i can overclock my phone to is 748. whenever i try to raise it to about 768 or 787, the phone will freeze and restart. is it due to the hardware limitations of my phone? or isit due to some software limitations?
Please help.
Just Hardware.
(I can overclock to 729 )
Hi. I'm still using Gingerbread stock rom 2.3.3 but with latest franco's kernel. My max. clock is 710Mhz. Anything above that, my phone will get freeze very often. Is there any recommendation on what should i set for my min. clock as well as the Governor?
SacredGuy said:
Hi. I'm still using Gingerbread stock rom 2.3.3 but with latest franco's kernel. My max. clock is 710Mhz. Anything above that, my phone will get freeze very often. Is there any recommendation on what should i set for my min. clock as well as the Governor?
Click to expand...
Click to collapse
I use the performance gov. and it's worked well.
SacredGuy said:
Hi. I'm still using Gingerbread stock rom 2.3.3 but with latest franco's kernel. My max. clock is 710Mhz. Anything above that, my phone will get freeze very often. Is there any recommendation on what should i set for my min. clock as well as the Governor?
Click to expand...
Click to collapse
I use stock 2.3.3 v20g + franco kernel and set max clock at 729Mhz, sometimes it freeze, but normally work fine (with any gov).
Each CPU is a little different. My OV is stable at 600 with smartassv2 but once I step it up to 729 the phone will randomly freeze or reboot.
Sometimes you get a good cpu that can be OCed a bit, and sometimes you get one that can go no further then stock. If you can OC then consider yourself lucky.
Whenever you try to increase the max frequency beyond a certain limit the CPU can not handle that and tells the kernel about that and kernel starts to Panic... (reboots or freeze)
For example My phone remains stable upto 768 MHz (usually i keep it at 748Mhz....)
but if i increase it to beyond 806 MHz it starts to panic...
Hardware
Has differences on hardware, already tried with 2 differents P500, one could overclock to 768 Mhz, the other can reach 800Mhz without freeze.
karven said:
Has differences on hardware, already tried with 2 differents P500, one could overclock to 768 Mhz, the other can reach 800Mhz without freeze.
Click to expand...
Click to collapse
Since all the p500 have same hardware, they can be OC to same max frequency if they have same software config...
806! never freezes but she gets warm! can get over 40 celcius
EDIT
Mind you i only get about 16 hours of battery life LOL
shubhamjain001 said:
Since all the p500 have same hardware, they can be OC to same max frequency if they have same software config...
Click to expand...
Click to collapse
where did u get ur facts?
are u smart or just effin noob?
yours preferred governors????
actually the best one is....
Dude keep it around 652 and interactive otherwise UR Battery will drain fast
depends on ur ROM+kernel combo.
on oxygen v1.1 i smoothly ran on 480-768 and battery lasted around 2 days with average use.
Now on Cm7 nightly, equally smooth at 729-480 and battery is awesome too..
Overclock
Ohhh!!! lucky guys.. my phone only accepts 672Mhz at max or anything above that value leads to rebooting or freezing.
Rom: Cyanogenmod 9 (Android 4.0.3)[BETA4]
Kernal: Franco Kernal - 4
OC: 480/672 Max
I get 748MHz completely stable when pushing "performance" governor with franco #4.
But irrespective, this is not about bragging...one would see LITTLE real life difference (save for frying the CPU faster) going above 672MHz. Don't just look at synthetic benchmarks...feel your phone.
Oh...and it was mentioned multiple times that 600->806MHz uses the same voltage hence the same power consumption for Sidestep CPUs.
I am running max CPU @ 729 and it has been running smooth for days with no freeze/reboots, I also noticed having the Governer on Performance has helped my battery life and such, i havent noticed the phone getting any warmer whatsoever so no problems with heat, Also I am using a LG-P504 Optimus One which Ive heard is the final release for this phone, so maybe its more stable than the pervious versions.
My p500 can handle 768 max. With some kernels 787mhz. But i am running 245-710 with miui v4: lol:
Sent from my LG-P500 using XDA App
Yea mine can handle that too but it drains my battery faster I've noticed. So now I run Max @ around 720 which seems quite stable!! Only time I use the nitrous feature also is with playing more top end games which I otherwise wouldn't be able to play without really low fps.
Sent from my LG-P504 using XDA App
Im using cyanogenmod nightly 7.2.0 build 34 on 748 mhz with any governer and it's working very well.OC also depends on ROM's.each ROM has different capabilities to OC...
http://www.tomsguide.com/us/overclock-android-device,review-1762.html#xtor=RSS-998
Opinions from people who really know? I can't imagine that overclocking increases battery life.
It doesn't. At least from my understanding. In fact as I understand it running at higher clock speeds would decrease your battery life no? I usually under clock, so...
Sent from my SGH-I777 using xda premium
The theory is that overclocking allows you to complete processes quicker, which in turn allows the processor to go back to a idle/deep sleep faster. In practice it doesn't really work that way though.
ryude said:
The theory is that overclocking allows you to complete processes quicker, which in turn allows the processor to go back to a idle/deep sleep faster. In practice it doesn't really work that way though.
Click to expand...
Click to collapse
doesn't the increase in voltage also come into effect?
They did talk a little about undervolting to increase battery life. Personally I don't worry about it. I'm not using my phone to sort out heavy algorithims at the moment, so running how it does is fast enough for what I use it at. Just found the article interesting.
K Rich said:
doesn't the increase in voltage also come into effect?
Click to expand...
Click to collapse
They say the undervolting on lower clocks should balance out the higher voltage on overclocks.
stalked_r/t said:
They did talk a little about undervolting to increase battery life. Personally I don't worry about it. I'm not using my phone to sort out heavy algorithims at the moment, so running how it does is fast enough for what I use it at. Just found the article interesting.
Click to expand...
Click to collapse
Undervolting rarely makes a difference on mobile SoC's, but on the desktop/laptop CPUs you can really save a ton of power with undervolting and underclocking.
Why to overclock and understand it?
Here is a good reason to know what you are doing..
and the battery avg's lasting at least through the day, but most of the time, I have a charger near me...
EDITED: because it won't accept my screenshots HTML Probably cause I have n00b status on this account name.
AnTuTu Benchmark v.2.8
Total Score: 7446
RAM: 1201
CPU Int: 2264
CPU Float: 1767
2D: 295
3D: 1148
Database: 450
SD W 11.8MB 118
SD R >50MB 203
1600mhz
2012-05-23 18:17
You can view this SN here: Screenshot
Fluxi Kernel/My own OOM settings/AOKP/my own XXTweaker settings
The article says its not the actual overclocking that is saving battery life. When you put SetCPU on your phone not only can you overlock but you can underclock and set different voltages. I'm not 100% sure how the voltages play into it but you can set the processor to run at really low speeds during certain acts ei. when the screen is off, or any other time you don't necessarily need alot of power. That's and I changed all the voltages (I got them from a post where the guy knew what he was doing and tested them). I get almost 2 days moderate browsing, apps and text. If I talk alot or use my hotspot I only get 1.5 days. It is a little time consuming to get everything just right but when you do you really see it.
icyhandlz said:
The article says its not the actual overclocking that is saving battery life. When you put SetCPU on your phone not only can you overlock but you can underclock and set different voltages.
Click to expand...
Click to collapse
This isn't a SetCpu feature there are other programs that can do this as well. It just so happens SetCpu has it built into the program. I bought SetCpu back in my Atrix days and loved it so it does work great for a simple tuning program.
Sent from my SGH-I777 using Tapatalk 2
Many of the kernels these days have their own tweaks and mod apps as well
Sent from my SGII AOKP Fluxi i777 running Beastmode OOM using Xparent Sky Blue Tapatalk 2
I'm running a kernerl and a custom ROM that allows me to underclock and overclock.
I tried it out both ways and the battery lasted for almost the same amount as on the stock option. As I tend to play games a lot on my phone, the underclocking ran into some issues with stuttering and sometimes force close of a couple of games.
Personally, I've never been a big fan of either .