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.
Related
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
I'm running the awesome das BAMF ROM 2.0-5 with the MR2 radio. The camera on this ROM runs much smoother when max CPU frequency is set at 1.4 ghz. Is it generally safe to leave my phone overclocked at 1.4 GHz indefinitely? Particularly for a daily driver/ primary and only phone? It seems to run this so far, but I don't know enough about long term effects of overclocking. Thanks everyone.
I overclocked my Eris for over a year. 1.4 ghz is safe as a general rule because it can run stable up to 1.8. If you use SetCPU you can set profiles to underclock when the screen is off, below a certain battery level, etc. Just remember that if you flashed imoseyon's kernel, you need to run the speedtweak.sh script in a terminal emulator and run option 13 if you are using SetCPU after selecting voltage options.
Sent from my ADR6400L using XDA App
I'm thinking I'll stick to whatever kernel is in the das bamf 2.0-5 ROM. Easy drop down menus
Also, if a kernel runs stable at a certain frequency (say 1.8 ghz), does it follow that the processor hardware itself will also be OK? In other words, if I can run at 1.8 ghz stable and deal with the battery life associated with it, will my phone last through my two-year contract or will I wake up one morning a year from now and find the phone has turned into a marshmallow?
Well obviously there is risk involved, but a processor either runs fine, or it wont run at all. Personally I run at 1.6 Max right now, only because its not worth the risk, with the minimal gains to run it at 1.8. In terms of the longevity, well sometimes you gotta just take the plunge bud, that's the fun in android.
Sent from my ADR6400L using XDA App
You won't really notice any performance difference with anything over 1.4 ghz.
I have been running imoseyon's kernels at 1.4 max & 245 min ever since he implemented speedtweak. No overheating, reboots or other weirdness. Ymmv, each phone has different tolerances. But as long as you don't o/c the min frequency (i.e., you're not constantly at 1.9 or 1.4 ghz) you will probably be fine.
Sent from my ADR6400L using XDA App
sublimaze said:
I have been running imoseyon's kernels at 1.4 max & 245 min ever since he implemented speedtweak. No overheating, reboots or other weirdness. Ymmv, each phone has different tolerances. But as long as you don't o/c the min frequency (i.e., you're not constantly at 1.9 or 1.4 ghz) you will probably be fine.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
same here, imo's kernels have made this phone what it should be. it has incredible battery life compared to stock.
but to answer the OP's question, i can't see why leaving it o/c'ed to 1.4 indefinitely will harm anything. like sublimaze mentioned, as long as you don't bump up the min freq, your phone won't be running at 1.4 the whole time. it only gets up that high when an app or system function needs the processing power.
on a side note, even if you did put your min freq at 1.4, i still don't think it would hurt anything, it would just murder your battery quickly
Im running Cm7 withh Imoseyon's kernal. Every time i oc to 1.9 phone will freeze almost instantly any suggestions to fix this
Sent from my ADR6400L using Tapatalk
Yep, slow the overclock to 1.5 your phone can't handle it, neither can mine. Some can and some can't but other than running a nice CPU test to show off to your buddies you don't want to push your TB like that on a daily basis. I have mine set to 368/1.02 and happy as can be with the extra battery life I get from my phone.
If I helped you in any way please use the thank you button
Alrighty i have mine set to 1.4 extremely undervolted and i get 9-10 hours battery life with heavy use thank you
Sent from my ADR6400L using Tapatalk
Hello,
I have a few issues with IMO's lean kernel that someone might can help with. 1) Extreme settings 2 and 4 cause instant phone freeze and reboot. 2) Option 3 works for the first minute or two after boot but then freezes (CPU spy shows 1.92 GHz runs smooth through boot). I believe it to be caused by the ramp up/down of the governor or possibly a script/setting messing with my system.
I am able to run very stably and smooth with a top CPU speed of 1.6 GHZ( 1.593 GHz on A05P). Any ideas on what I can do to increase the CPU speed so that the system stays stable? Your input is much appreciated. Thank you again for helping this poor noob.
Veltar said:
Hello,
I have a few issues with IMO's lean kernel that someone might can help with. 1) Extreme settings 2 and 4 cause instant phone freeze and reboot. 2) Option 3 works for the first minute or two after boot but then freezes (CPU spy shows 1.92 GHz runs smooth through boot). I believe it to be caused by the ramp up/down of the governor or possibly a script/setting messing with my system.
I am able to run very stably and smooth with a top CPU speed of 1.6 GHZ( 1.593 GHz on A05P). Any ideas on what I can do to increase the CPU speed so that the system stays stable? Your input is much appreciated. Thank you again for helping this poor noob.
Click to expand...
Click to collapse
Don't OC that high, simple as that. There is no need to run the phone constantly at 1.9ghz.
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...
so...my note is rooted with OC and on CWM beta 3. i even have flashed a battery percentage status bar mod (after many tries and lots of FC's issues) i finally got everything stable on a stock rom oc'd at 1.8 and this thing was sick dude...i mean so fast and big and bright and perfect...no problems except for 1...was getting random reboots...3 a couple days ago while using boat browser every mtime so uninstalled and started using dolphin. worked great until 1 rando reboot today while on dolphin browser...i figure no big deal it happens when you tweak your phone...but then all of a sudden it did something different just now it did...it just randomly rebooted while toggling wifi on except after it booted back up i couldn't unlock the screen or get into the launcher and the screen went black and unresposive. power button did nothing even holding it down...i pulled the battery out and then back in and restart and phoone booted up normally. clear as a bell and lightning fast...
so i just dialed down the oc to 1700...hope it's all good though...can't think why it would do this...
thanks?
Your phone can't handle the 1.8 ghz overclock.
When overclocking, no 2 chipsets will perform the same. Some will be able to overclock to 1.8 and some will not.
zer0nine said:
Your phone can't handle the 1.8 ghz overclock.
When overclocking, no 2 chipsets will perform the same. Some will be able to overclock to 1.8 and some will not.
Click to expand...
Click to collapse
So then is this OK?
Well anyway I guess I'll post back with the results. Cuz I'm running that way now. Hope I don't brick this beauty.
All opinions welcome.
Sent from my SAMSUNG-SGH-I717 using xda premium
You won't brick by overclocking. If you run it at an unstable clockspeed for your phone, you'll just be getting constant reboots.
1782 mhz should be fine. Try benchmarking your phone using Quadrant and Antutu from the market to stress test your phone at that new CPU speed.
zer0nine said:
You won't brick by overclocking. If you run it at an unstable clockspeed for your phone, you'll just be getting constant reboots.
1782 mhz should be fine. Try benchmarking your phone using Quadrant and Antutu from the market to stress test your phone at that new CPU speed.
Click to expand...
Click to collapse
Thanks. I'm at 3723.....phone feels good.
Sent from my SAMSUNG-SGH-I717 using xda premium
yup, sounds like classic too-overclocked symptoms to me. Back it down a notch like you have already done and try again...