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...
Related
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,
I have made a lot of searches and read a lot about battery calibration... and of course i know what the hell is kernel panic, its definition and its symptoms.
However I still have some confusions and I hope some of you may be able to solve them
Maybe some of them are noobie questions but I honestly sorry for that also this may help others who has these confusions too
My situation:
The system stats are shown in my signature.
on 5/9 I have flashed franco.Kernel v19.4 bfs and then started a lot of OC tests,
finally I was stable on stress test (SetCPU) 729mhz for 2 hours non-stop,
and also I used the phone stably for over 24 hours without reboot.
However I faced a problem which is related to Darktremor scripts.
I used 2 weeks to solve it and finally it is gone now.
I started battery calibration which is the final process before I use my phone normally in my daily lives.
But in these two days, my kernel panics after ~4 hours of usage of 729mhz max CPU frequency.
without the need of advice, surely i have downclocked to 710mhz max and its all good. but however i am super curious about why 729 becomes from stable to unstable before and after.
1) Does battery stats related to kernel panics in ANY extent? if yes, how?
Ignore all questions under 1 if the answer is No.
1.1) Does wiping battery stats before flashing a kernel helps you OC higher?
1.2) Does wiping battery stats before flashing a ROM helps you OC higher?
1.3) Does wiping battery stats (for calibration purposes) has possibilities to produce kernel panics?
2) Why is there a sudden drop of battery level (~4-5%) after kernel panics?
3) Is there any other possible causes of kernel panics BESIDES overclocking too high?
3.1) *2sd scripts?
3.2) ext4 barrier = 0?
3.3) inputting EXT4 data writeback?
(tune2fs -o journal_data_writeback /dev/block/mmcblk0p2)
4) Is SetCPU the problem?
Some says "dont use SetCPU when you can overclock using CM7 settings."
Is that true?
5) BESIDES the max speed, does it also depends on Governors?
Ignore powersave governor or others which forces the clock to the minimum frequencies.
So, is there any difference between setting the same maximum speed, different governors?
(for example) Would smartass gives a panic at 729mhz but ondemand doesnt?
6) Does the "change of frequencies" gives easier kernel panics?
Situation A: 729min, 729 max
Situation B: 480min, 729max
In situation B, the system makes the frequencies change due to load, means it may switch from 480 -> 600 -> 729 -> 710 -> 691 -> 480 etc.
so does this "change of frequencies" makes the kernel loads more and finally gets it to panic?
Thanks for your time reading and answering my questions!
Please just quote one of them if you would just like to answer one of the above
Thank you very much!
1) no.
2) It happens when u remove the battery and put it back.
3) There are some strange reports of kernel panic at 600Mhz which are weird. Sometimes Roms/kernel play a part(unknown).
4) it is because you can overclock in Cm7 settings menu, so no need to install another app such as SetCpu
5) Maybe, a governor who stays more on the highest frequencies i think are easy to panic because hardware can't handle it.
6) for me, i would say situation A would be easier to kernel panic, as it is constantly on the highest frequency and stressing your cpu too much that it can't handle it.
Since you get stable at 729mhz for 2h and panicked when 4h of use, that means the cpu can't handle 729mhz for above 4h.
@terratrix
thanks for your reply!! at least im not using my stupidity to wipe battery stats and trying to avoid kernel panics, lol.
@info update and conclusion after 1 more day of testing
And there, after some readings on the forum and the experiences myself, i think i have found the critical point already - QUESTION NO.5
Conclusion : kernel panics are related to governors, at least, our new amazing profiled one - SmartassV2!!
On the thread of Franco's .35 v1 kernel, there are some users reporting the panic issues faced with ONLY SmartassV2.
And me myself, has joined the party as well
Smartass(v1) has been my best bud all the time at 729mhz or even higher for more than 6 months. And when I left it and went to choose his next generation, my phone got a generation gap with Mr.V2, lol.
On my phone: (Franco.kernel 19.4bfs and no any reflash or stuffs between testings)
SmartassV2 ---
very unstable panics AND random shutdowns at random times
729mhz - sometimes 2 hours, sometimes 4 hours
710mhz - yeah I justnow kernel paniced with this also, you know how long after boot? 30minutes!!!
Why 30minutes? I suspect that it.is related to franco's network speed hack. I'm on EDGE data plan and because of Franco, I can enable HSDPA with 4x more speed.
On 710mhz, my phone was stable for over 8 hours with EDGE on (I intended to save battery), but after a reboot (manual one for some other purposes) I started to use (the hacked) HSDPA. After 30 minutes, panic. I remembered when I was at 729 on smartassv2 I panicked after 3 hours and at that time I was using HSDPA too.
Smartass (v1) ---
Well now I'm on smartass v1 at 729mhz stably typing this message. Funny huh...?
Results:
Franco's network speed hack
OR
3G network/HSDPA network
OR
Even just because of specific phone hardwares
IS NOT COMPATIBLE WITH THE ALMIGHTY SMARTASS-V2 GOVERNOR AND WOULD RESULT IN KERNEL PANICS AT THE FREQUENCIES WHERE THE PHONE CAN BE STABLE WITH OTHER COMMON GOVERNORS.
If I am wrong or you can confirm this by testing yourself, please let me know!!! thanks and hope I have provided some useful information
Goodnight and I'm going to continue working with my old friend smartass-v1 despite v2 has better profiling tweaks, lol
Sent from my LG-P500 using XDA Premium App
Dude, as i had mentioned earlier in franco's thread, that it had to do with the governors... cause i usually try and find out the cause of the issue myself before posting a bug..
SO all i tried were playing around with the performance settings... and i start off with changing the governors... the best targeted experimental ones are MINMAX (my personal fav), SMARTASS, SMOOTHASS (now removed but one AWESOME governor), and INTERACTIVE-X (rewritten by franco i guess).... About the frequencies... from what i have observed so far apart from reading stuffs is that, at 729 Mhz our optimus DOES pretty much stay stable even in the ****TIEST devices.. LOL i can say that cause we indians get the crappiest hardware of all... the point is... if you got a kernel panic at 729, it is most likely that you would get it again at 600 Mhz too cause its not overclock related..!!!
Bottom-line: Avoid SmartassV2 unless your phone is made of the finest hardware i.e. you can easily overclock it to 806 Mhz (ive seen some users using it at this frequency without any issues at all .. :O ) Use Smartass older or Minmax instead...!! And avoid overclocking above 729..!!!
P.s.: mine works fine even at 768 BTW....
We have to wait for Franco's next release for more smartass2 updates
Sent from my LG-P500
SmartassV2 is kind of strange, at least in my phone. I notice my battery draining faster while I use it, and it's probably because it stays in the max frequency longer for some reason, despite screen off. I use NoFrills for my CPU setting and it has the ability to view stats, and when I'm using V2 it stays longer at the max than at the min (65 vs 35%). The opposite is true for Smartass v1, which to me makes more sense because my phone stays at standby more often than being used.
As comparison data, my phone with smartass v1 can typically be OCed up to 787 MHz. 748 MHz on v2 is stable, but I haven't extensively tested higher freqs.
I have a Indian phone , smartass v2 oc to 768 stable xD
Sent from my LG-P500
I installed Icecream Sunday Final (very nice rom btw), but the phone lags often. For example, when I unlock it, it can be frustratingly long to be able to launch any applications right away. There is always at least 100mb of ram free, so I am not sure what causes this.
Does anyone have any advice? Has this happened to any other ICS users?
Are you using an OC Kernel?
If so, I read around here on the forums that you should increase your minimum CPU speed a bit and that should clear up the lag when unlocking the phone. Haven't tried it myself since I am running theMyth - ICS Lite, but am going to go back to Cyanogenmod (once of the things that peeved me on Cyanogen was exactly this; lag after unlock).
Hope this helps
Gooner88 said:
I installed Icecream Sunday Final (very nice rom btw), but the phone lags often. For example, when I unlock it, it can be frustratingly long to be able to launch any applications right away. There is always at least 100mb of ram free, so I am not sure what causes this.
Does anyone have any advice? Has this happened to any other ICS users?
Click to expand...
Click to collapse
hi you have to flash a kernel (you ll find all the information needed in the ic sunday topic)
i did do that and its far better
Either you set your min. frequenzy to 245Mhz or just use smartass gov. @ 122Mhz. I prefer smartass @ 122Mhz and there no lag.
PS: I´m using the same rom but with SlaidFastMod V2
I'm having wake-up lag too! But I already gave up thinking that the SGA's CPU just sucks. Thanks for this info GerasVille, I did not think to tinker with the System settings of CyanoGen because of the "Dragons Ahead" prompt. I will try this smartass setting to see if the wake-up lag will be removed. It sucks when I have to send an emergency SMS and my phone is lagging like hell.
Anyway so let me get this straight. Does having the minimum CPU clocked at 122mhz mean that if the device is inactive, it dynamically clocks down the CPU to 122mhz to save battery? Hence the wake-up lag is caused by the CPU being clocked back up?
I'm also gonna try out slaidfastmod to see if it makes it even better.
You can put up with the lag and save a tiny bit of battery life, or speed up the CPU and lose some battery life. Whichever you feel is more useful. Personally I don't mind the small unlock delay. Happens on most phones low powered anyway.
Sent from a phone with an app.
Eniac77 said:
Are you using an OC Kernel?
If so, I read around here on the forums that you should increase your minimum CPU speed a bit and that should clear up the lag when unlocking the phone. Haven't tried it myself since I am running theMyth - ICS Lite, but am going to go back to Cyanogenmod (once of the things that peeved me on Cyanogen was exactly this; lag after unlock).
Hope this helps
Click to expand...
Click to collapse
The kernel that is currently installed is "2.6.35.7-perf-CL562111" Ketut-lenovo #4. I am not sure if it is an OC kernel.
GerasVille said:
Either you set your min. frequenzy to 245Mhz or just use smartass gov. @ 122Mhz. I prefer smartass @ 122Mhz and there no lag.
PS: I´m using the same rom but with SlaidFastMod V2
Click to expand...
Click to collapse
I installed SlaidFastMod v2, set governor to Smartass and min CPU frequency to 245 MHz and this fixed the issue! It's much smoother when unlocking.
Is it safe to tick the "Set on boot" setting for CPU settings?
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
Hi there to all!!! I've been flashing various Android Roms for a few yrs now & really enjoy trying out new custom roms etc... Now i have a weird problem, Most customs Roms I have tried for my S3 i9300 are great & most 4.3 Roms come with a Custom Kernel such as Beoffla, GoogyMax, devil kernel & so on.... Now the problem is when leaving the CPU at defualt governer & settings everything is fine eg: min 200 & max 1400 but games lag now & again, When setting the CPU min & Max settings to 1400MHz, the results are much better but not for long, The CPU always drops to 800MHz when gaming as i notice the lagg, I've noticed this same thing with just about every kernel & rom ive tried wether its set to 1400 or even overclocked to 1500 or 1600max, I've also tried every trick to make them settings stick , like trickster mod etc, none seem to work for long, its like another system service is interfering with the settings or so.....im pulling my hair out to figure out what this is, I just want the CPU min & max to stay firmly at 1400Mhz or 1500 etc....without changing at all!!!
Any help or suggestions would be really appreciated.... FlashJunkie83
Sent from my NeatRom'ed Galaxy S3
CPU/GPU can under-perform if they get too hot from playing resource-intensive games or apps. Maybe this is the issue.
~ RazorMC
RazorMC said:
CPU/GPU can under-perform if they get too hot from playing resource-intensive games or apps. Maybe this is the issue.
hey yea would make sense but when running rooted stock 4.1.2 with stock kernel, this doesnt happen at all, i can set performance governer in set cpu & it stays at 1400 Mhz throughout, also i would of thought a Cpu thats ment to run at 1400 would be fine to do so all the time as its ment to be able to... even with a little heat behind it... its still only doing what its ment to lol, i remember in the days of my s2, i could push the cpu to 1200mhz & it would happily stay there even tho it got hot lol, im really sure its a system thing that upsets the cpu frequency, other than that there must be a way to stop the cpu/gpu from under-performing with a little heat..... thanks for reply tho dude....
Sent from my NeatRom'ed S3 i-9300
Click to expand...
Click to collapse
@FlashJunkie83
- High temp will always cause freq throttling since this is how devices are designed. This over-rides whatever the max freq the cpu was designed to run on.
- try undervolting from the boefla config app (if you use the boefla kernel). I use -25mV with almost no difference to performance. Some users have gone on to -50mV but that gave me random freezes and massive lags sometimes.
- Test different governors. I mostly use the default pegasusq and it works well enough. Constantly high freq can affect the CPU in the long-term. So I use max freq of 800mhz and increase it to 1400mhz only when I play games.
- I'm not a fan of SetCPU. It's a great app but i find specific apps (like boeffla config) for kernels to be more precise.
- You can also try a different battery and borrow one from a friend to test it out. I had slight heating issues long ago and changing the battery reduced the heat for me somehow. It was not much, but it was enough for me to notice.
~ RazorMC
RazorMC said:
@FlashJunkie83
- High temp will always cause freq throttling since this is how devices are designed. This over-rides whatever the max freq the cpu was designed to run on.
- try undervolting from the boefla config app (if you use the boefla kernel). I use -25mV with almost no difference to performance. Some users have gone on to -50mV but that gave me random freezes and massive lags sometimes.
- Test different governors. I mostly use the default pegasusq and it works well enough. Constantly high freq can affect the CPU in the long-term. So I use max freq of 800mhz and increase it to 1400mhz only when I play games.
- I'm not a fan of SetCPU. It's a great app but i find specific apps (like boeffla config) for kernels to be more precise.
- You can also try a different battery and borrow one from a friend to test it out. I had slight heating issues long ago and changing the battery reduced the heat for me somehow. It was not much, but it was enough for me to notice.
~ RazorMC
Click to expand...
Click to collapse
thanks mate will give it a go
sent from my NeatRom'ed S3 i9300
finally fiqured it out, it seems that cynogenmod has a diffrent approach to thermal throttling as ive flashed CM10.2.0 Android 4.3.1 along with Boeffla 2.1 for CM & the issue seems to have gone completely, have been running a performance test on games for best part of the day at 1600MHz with 4 enabled cores & just going back to normal settings for normal daily use, & not 1 issue with throttling, so now im very happy with the smoothness in games although its gets warm, but most high performance CPU's do anyways,So ive come to the conclusion that thermal throttling must be handled more by sammy roms it seems, but got the result i wanted in the end, thanks for all replies tho guys
Sent from my blazing S3 i9300 now running CM10.2.0