does this app work on Streak?
I tried out and nope, it don´t work how it should. It says the Streak is running with 998 Mhz and you can´t overclock it. Waiting for update...
crazy cat said:
I tried out and nope, it don´t work how it should. It says the Streak is running with 998 Mhz and you can´t overclock it. Waiting for update...
Click to expand...
Click to collapse
998Mhz is the limit for the kernel. you need a kernel that can be overclocked for that option....
it works fine. at this moment in time you can not overclock but it auto detects settings just fine and you can set screen off speed/battery low speed to extend your battery life.
crazy cat said:
I tried out and nope, it don´t work how it should. It says the Streak is running with 998 Mhz and you can´t overclock it. Waiting for update...
Click to expand...
Click to collapse
Wait, u know there are three levels of clocking, right? one is under clock, one is clocked and one is over clock. There are two frequencies when u turn on the setcpu, one is max and one is min...but i would like to know if u r able to make the max and min both up to 998mhz so that it can run at full speed at all times
zgmf-x322a said:
Wait, u know there are three levels of clocking, right? one is under clock, one is clocked and one is over clock. There are two frequencies when u turn on the setcpu, one is max and one is min...but i would like to know if u r able to make the max and min both up to 998mhz so that it can run at full speed at all times
Click to expand...
Click to collapse
yes you can bro. both max & min are customizable from 24500Mhz upto 99800Mhz. however, ive found that having the streak running totally max when the screen on will simply drain your battery, there are no real speed improvements to be seen. a good compromise to combat lag would to be to set screen on: 76800 - 99800Mhz.
i completely downscale mine when the screen is off and although the battery life on the streak is good, doing this makes it even better. no lag when switching screen on either (frequency change)
Works great for me too! I don't see any need for overclocking a phone (unless you don't use it as a phone..)
I unplugged mine from the charger about 1.5 hours ago, still 100% battery..
thanks guys for the reply, appreciated it alot!
it does and very well
to get interactive setting you must at least have performance fix and it will let you overclock and add interacting setting i just did perf. fix and setcpu settings and now quadrant score of 1700+
Works great for me. Flash smokku and fard's djsteve kernal perfmod using clockwork or streak mod and then you can overclock using setcpu. Look at my signature line below.
Dell Streak, 2.2 froyo (318), custom kernel, OC to 1.2ghz, quadrant 2002, hspda signal mod,
Related
Hi all,
I have been browsing this forum for a while now and finally decided to register.
After getting incredibly frustrated waiting for HTC and T-mobile to get their act together and release 2.1 I followed the guides on here and rooted my G2.
I originally flashed VillainROM10.3 and then upgraded to VillainROM12. Both of which are great!
I have since been playing with the CPU speed. I see many people on here claiming CPU speeds of ~750Mhz, however the most I seem to be able to get out of my phone is ~650Mhz (I'm using OverclockWidget from the market to set the frequencies). Is this a problem anyone else has experienced? If so is it down to my phone having a duff CPU or could the problem be with the ROM or the widget I'm using. Whenever I set the phone to anything higher than 650 it either just freezes or reboots itself.
Thanks Guys (and girls?)
hopoffbaby said:
Hi all,
I have been browsing this forum for a while now and finally decided to register.
After getting incredibly frustrated waiting for HTC and T-mobile to get their act together and release 2.1 I followed the guides on here and rooted my G2.
I originally flashed VillainROM10.3 and then upgraded to VillainROM12. Both of which are great!
I have since been playing with the CPU speed. I see many people on here claiming CPU speeds of ~750Mhz, however the most I seem to be able to get out of my phone is ~650Mhz (I'm using OverclockWidget from the market to set the frequencies). Is this a problem anyone else has experienced? If so is it down to my phone having a duff CPU or could the problem be with the ROM or the widget I'm using. Whenever I set the phone to anything higher than 650 it either just freezes or reboots itself.
Thanks Guys (and girls?)
Click to expand...
Click to collapse
It's as simple as; some phones simply can't handle higher MHz
So if I flash for example SuperHero which is supposed to be clocked by default at 691Mhz will my phone freeze on boot or is it smart enough to figure out its max speed.
hopoffbaby said:
So if I flash for example SuperHero which is supposed to be clocked by default at 691Mhz will my phone freeze on boot or is it smart enough to figure out its max speed.
Click to expand...
Click to collapse
It will probably freeze but there are kernels the isn't overclocked that high by default
So I don't mean to keep going on about it but when I flashed VR12 the description said:
...
- 19MHz to 748MHz OC kernel
...
However when I run it the default speed its using is 619? Is that normal?
hopoffbaby said:
So I don't mean to keep going on about it but when I flashed VR12 the description said:
...
- 19MHz to 748MHz OC kernel
...
However when I run it the default speed its using is 619? Is that normal?
Click to expand...
Click to collapse
Yes. Many ROMs aren't set to the highest available clock speed by default because there are phones like yours that can't handle it
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 just put tazz 14 on and set my Max at 768... is that too much... I have read so much on what clock speeds to set but I still don't know what's best.. also... what is Eris stock clocks?
Notxok said:
I just put tazz 14 on and set my Max at 768... is that too much... I have read so much on what clock speeds to set but I still don't know what's best.. also... what is Eris stock clocks?
Click to expand...
Click to collapse
If your phone is running ok and getting too hot then 768 should be fine, many of us run 806 without a problem. I think stock CPU is set at 528 (maybe lower, I don't remember)
BTW this should probably be in Q&A board
Sent from my nonsensikal froyo
I run 768 with no problems.
SikYou said:
If your phone is running ok and getting too hot then 768 should be fine, many of us run 806 without a problem. I think stock CPU is set at 528 (maybe lower, I don't remember)
BTW this should probably be in Q&A board
Sent from my nonsensikal froyo
Click to expand...
Click to collapse
806 are you ****ting me?... is it set to performance?
Notxok said:
806 are you ****ting me?... is it set to performance?
Click to expand...
Click to collapse
Interactive
Sent from my nonsensikal froyo
Hmmm. I'm trying 806 now.
SikYou said:
Interactive
Sent from my nonsensikal froyo
Click to expand...
Click to collapse
806 in interactive rebooted for me.. I might have to reflash a ROM now LOL... lucky I wish I could run 806 efficiently
You should never try clock speeds without disabling "Start on boot" or you can really screw yourself over....
Anyway, 768 is a very common speed for people to be able to hit. I personally become unstable at 806 (especially with JIT on) and I stick to 787.
Hungry Man said:
You should never try clock speeds without disabling "Start on boot" or you can really screw yourself over....
Anyway, 768 is a very common speed for people to be able to hit. I personally become unstable at 806 (especially with JIT on) and I stick to 787.
Click to expand...
Click to collapse
Your 486 Makes me Envious.. Would you mind PMing m your set-up ( ROM Set CPU info and current task killer? )
My 486 was a while ago and doesn't really reflect the overall performance of my phone; as in my phone is currently faster but I get lower quadrant scores (440-450)
I was on Tazz V6 I believe, clocked to 768mhz performance, with BFS V2 or V3. After rebooting and flashing the kernel I was getting high 470's and mid 480's so I took a picture with my girlfriend's Incredible.
JIT was at 16m and I'd just switched from 24 to 16 and wiped dalvik. This is significant because anytime you switch your dalvik heapsize and reboot your quadrant scores will be at their highest, not sure why, probably has to do with RAM allocation.
Hungry Man said:
My 486 was a while ago and doesn't really reflect the overall performance of my phone; as in my phone is currently faster but I get lower quadrant scores (440-450)
I was on Tazz V6 I believe, clocked to 768mhz performance, with BFS V2 or V3. After rebooting and flashing the kernel I was getting high 470's and mid 480's so I took a picture with my girlfriend's Incredible.
JIT was at 16m and I'd just switched from 24 to 16 and wiped dalvik. This is significant because anytime you switch your dalvik heapsize and reboot your quadrant scores will be at their highest, not sure why, probably has to do with RAM allocation.
Click to expand...
Click to collapse
I don't get above a 415-420 really.. any suggestions or help?
Notxok said:
806 in interactive rebooted for me.. I might have to reflash a ROM now LOL... lucky I wish I could run 806 efficiently
Click to expand...
Click to collapse
806 seems to be running a fraction faster but to me it is hardly noticeable coming from 768.
Notxok said:
I don't get above a 415-420 really.. any suggestions or help?
Click to expand...
Click to collapse
Don't read too much in the benchmarks . I usually run happily around 430.
I use SetCPU (interactive 768 / 245)
I don't run any task killers, in my experience they are more trouble than they are worth.
The other thing IMHO if you don't use an app, get rid of it.
Task killers are in fact more trouble than they're worth, especially automatic ones. I use advanced task killer and I only ever kill tasks right after my phone has started up/ when my phone is plugged in. Task killers hurt battery life and performance.
Hungry Man said:
Task killers are in fact more trouble than they're worth, especially automatic ones. I use advanced task killer and I only ever kill tasks right after my phone has started up/ when my phone is plugged in. Task killers hurt battery life and performance.
Click to expand...
Click to collapse
Thanks Guys... Ill keep that in mind.. I was using auto memory killer
Notxok said:
I just put tazz 14 on and set my Max at 768... is that too much... I have read so much on what clock speeds to set but I still don't know what's best.. also... what is Eris stock clocks?
Click to expand...
Click to collapse
In my personal experience, I would disable set on boot in SetCPU and start gradually bumping the speed up. Usually at 787 my phone runs best (fastest and most stable). Then, I'd go back and bump it to 806. It WOULD run but after about 5 minutes of playing with my phone it typically causes it to lock. 825 Causes an immediate lock. So I typically leave it at 787 and all Froyo roms seem to run fine at that for me. I don't even test anymore...just restore SetCPU app and data with Titanium on initial boot of a new rom. So far, no problems.
Sent from my ERIS using XDA App
What's the best setting? Ondemand? Interactive? Prefermance..etc
Sent from my VANILLA TAZZ using XDA App
806 no problem using the Collins script.
Anything higher than 710 on my phone locks it up.
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...
Hey guys I know this was already asked but still i didn't found an answer . Is there anyway to incrase your CPU limit . Mine it's at 729 . If i set it to 747+ it will block and reboot . So is there a way to incrase it ?
I'm using Kernel roq XIII+ .
The cpu in this phone is what I believe to be an Arm v6 Adreno GPU. The max overclock we can get on the phone (whilst stable 100% of the time) is around 748mHz. I've seen people with 806mHz at certain times using Rom and kernal mixups, like once when I used PerfectPeso and Francos Kernal. Weird occasions...
I'd say max for speed and so on, go 100mHz or around that for lowest, and 728mHz for highest clocks.
Sent via Tapatalk for Android (T-Mobile HTC MyTouch 3G Slide running HTC Update #5)
CJJames said:
The cpu in this phone is what I believe to be an Arm v6 Adreno GPU. The max overclock we can get on the phone (whilst stable 100% of the time) is around 748mHz. I've seen people with 806mHz at certain times using Rom and kernal mixups, like once when I used PerfectPeso and Francos Kernal. Weird occasions...
I'd say max for speed and so on, go 100mHz or around that for lowest, and 728mHz for highest clocks.
Sent via Tapatalk for Android (T-Mobile HTC MyTouch 3G Slide running HTC Update #5)
Click to expand...
Click to collapse
Dont underclock below 448MHz. All frequencies below that have the same voltage so its pointless as power consumption will be same. If you clock too low, it'll take more time to come out of sleep. And don't overclock above 748Mhz. If you consistently clock above 748, there is a high chance for kernel panics. I know a guy who did so and now even 748 isn't very stable for him.
That is not totally correct. 122 MHz uses a lower voltage than 245-480.
Sent from my LG-P500 using XDA
NeuDLi said:
That is not totally correct. 122 MHz uses a lower voltage than 245-480.
Sent from my LG-P500 using XDA
Click to expand...
Click to collapse
However it's slow and there is a reason why LG chose not to you it by default
Sent from my LG-P500 using XDA
So no one know if it's posible to incrase that limit ..?
Cresqo said:
However it's slow and there is a reason why LG chose not to you it by default
Sent from my LG-P500 using XDA
Click to expand...
Click to collapse
You mean in the same manner LG chose to use crappy default kernels with defective touchscreen driver, or a crappy GB firmware, yes? Sorry but what LG does or not does is simply irrelevant.
And I did not tell anyone to use 122 MHz, but it is possible and at least with screen off can't hurt. If you don't like it don't use it! But don't act like you knew better.
Sent from my LG-P500 using XDA
I use 480-748 with no problems on my current rom (Lupo's CM9 test), if your phone is unstable or simply reboots then you may wanna try another rom/kernel
With popdog's Oxygen rom (version 2.5 at least) I also had no problems with the same range.
See what CPU we have it's one 600 very stable. if you are clocking it more it will heat up that's why it reboots and some time it freezes. I would suggest you you to use it at 600 or you can go little upper side. But if you really want to over clock it high then it has some issues. There are extreme heat. battery drain. reboots. hang. it can break you sound and VGA chip...so do it wisely. in 600 LG P500 is very good.
Every combination will be different. Some CPU will handle higher clock speeds than others. The manufacturer only lets it pass inspection if it exceeds their minimum specs. That means there will be some that can handle more.
You will find out with use.
Your kernel and governor will also make a difference. So will the rom depending on the tweaks used.
Do you really need to clock it faster than that? The faster you go, the hotter you go, which shortens the life of the chip. Heat is the enemy.
Sent from my LG-P500 using XDA