Trying to gauge this.
Please say how high you can go, how stable it is, what ROM you are on, whether you have JIT installed and if you know it tell me the heap size.
no matter what rom i use, or if jit is enabled or not (it's not anymore, i hate the thing), my phone freezes at 806, I apparently got one of the lesser phones. 768 (or whatever) is what i normally set as my max.
768 is my max as well. I can run on 787 for a little while before it locks up but 768 is the highest stable speed. I don't use JIT
My max is 748, after that will freeze.
Sent from my Eris using XDA App
806 for me. No jit. I'd try higher but the next highest I have is 844 and its an instant freeze and reboot. Im on white widow 4.4.
Sent from my Eris using XDA App
suave smush v2
jit enabled
oc'd to 768
Can you overclock any higher when you disable JIT?
I run at 768/768 when the screen is on and 528 /245 when the screen is off with EE 3, and I would say it is really stable. Out of the 30 or so hours that my Eris is off the charger, Sense crashes maybe 4 or 5 times at max. Almost forgot no JIT.
806 on FroyoEris v20. Its the highest I've ever seen on my Eris. Usually with other roms I got to 710 without any issues.
Sent from my FroyoEris using XDA App
806 max / 604 min (screen on), 480/245 (screen off); no JIT; EE3. Quite stable at this, but any higher and it's an instant freeze. This goes for all other ROMs I've had with or without JIT. No clue what "heap" is, lol.
So you're saying you get 806 with or without JIT?
I can get my Eris to do 825MHz but currently use 806MHz just to be safe. My min is 160Mhz. Im using stock OTA 2.1 ROM with root. The only files I flashed were the kernel-overclock-update-v3.zip and eris21official-root.zip and I used the new root method.
wtf 825mhz? O_O That is insane! >_<
i immediately freeze on 825mhz, but run stable on 806mhz (with the exception of games, but i dont play any games). using froyoeris, v20, jit enabled. 5.6 mflops.
anyone designed a cooling system yet ?
if you did...dont answer plz
I run 768/480 (740/19 sleep,charge, or <30 battery) stable on ELB 2.7 @ 5.2 mflops. I can run 787 but sometimes freeze. I have seen 5.44 mflops at 806 but freeze after 10 minutes....instant freeze at 825. I think this rom has JIT.
Hungry Man said:
So you're saying you get 806 with or without JIT?
Click to expand...
Click to collapse
Yes
Sent from my Eris using XDA App
Stable @ 806. KaosFroyo v23.
You guys are lucky you can get to 806...
Lovin 806 @ 5.6 mflops
Sent from my FroyoEris v23
Related
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.
Can the X10 be overclock yet? I have rooted the phone and running 2.1. When I try the overclock all, it won't go past 1ghz
Thanx
Sent from my X10i using Tapatalk
Not yet. Apps like Overclock widget etc won't work, tried it myself numerous times but to no avail. We have to wait for the bootlocker to be cracked.
Sent from my X10i using XDA App
i dont believe that is correct in a way, technically, even though you can not pass 998mhz, you can set it so that it runs at 998 constant, rather than dropping down while in sleep mode. you can set as low as stock 246 and 998, or set low and high at 998 and check the difference. full exploration is needed to test where it runs best for you with options available. i am running the 2.2 zbuild.darkstyle with quadrant of over 1300 and mflops at 40.xx. havent tried to install JiT or JiTv2 on it yet but going to soon
True. I tried the overclock widget a few months ago without success. But set cpu, tho it doesn't increase cpu speed, does set a minimum frequency, which is pretty effective.
Sent from my X10i using XDA App
I've Perfmod enabled on Streakdroid 1.9 and I can take the setCPU to 1.5ghz. For the first time I isntalled the ROM, I was running stable on 1.35ghz for a day.
All of a sudden device started freezing and when I see the logcat they claim that the device's CPU voltage change failed.
Now whenever I push the overclock above 1.192ghz, the phone starts rebooting after a while. Is there a solution to stay stable on 1.3ghz+ ?
No. 1.19 has been the fastest stable speed the whole time.
Sent from my Dell Streak using XDA App
taranfx said:
I've Perfmod enabled on Streakdroid 1.9 and I can take the setCPU to 1.5ghz. For the first time I isntalled the ROM, I was running stable on 1.35ghz for a day.
All of a sudden device started freezing and when I see the logcat they claim that the device's CPU voltage change failed.
Now whenever I push the overclock above 1.192ghz, the phone starts rebooting after a while. Is there a solution to stay stable on 1.3ghz+ ?
Click to expand...
Click to collapse
Never mind
1.19 is as high as I can safely go without reboots also
i could max overclock it to 1.1 above which my phone strted rebooting randomly
It seems that each Streak has different limits on the maximum overclock. Some will run faster than others. You just need to experiment to see what your Streak can do. What someone else's Streak is capable of is meaningless.
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