Recommend some good overclocking number for p500. Mine is 710/480
Sent from my LG-P500 using XDA App
hellodzulz said:
Recommend some good overclocking number for p500. Mine is 710/480
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
It is not a static value across devices. Test it out yourself and use the one which is stable for you. Some guys have it stable even at 806 while my phone freezes at anything above 768.
hellodzulz said:
Recommend some good overclocking number for p500. Mine is 710/480
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
My o1 freezes at abt 800Mhz...
If you want to play safe, keep it under 720... after this it starts becoming unstable....
Press Thanks If I helped...
i would not set anything more than 768
and i like to set it one level below the max I think I can go.
so i set it at 480/748, and it is stable
varies...im pretty stable at 480/844
Depends on your Hardware
Try frequencies from 729 to 806 , but remember to uncheck the "Set on boot" option. (Just in-case to avoid boot loops)
I've set mine at 787
Thanks guys! I will try!
Sent from my LG-P500 using XDA App
What about the lower end of the freq?
I see some people cost 245 while some post 480.
I'm thinking 245 give it a better battery life since its lower but I've also read somewhere that 245 is too low and it causes the cpu to ramp up and down.
My phone gradually increases the chance of receiving a kernel panic starting at 768 MHz.
geeyoupee said:
What about the lower end of the freq?
I see some people cost 245 while some post 480.
I'm thinking 245 give it a better battery life since its lower but I've also read somewhere that 245 is too low and it causes the cpu to ramp up and down.
Click to expand...
Click to collapse
I've been reading a lot about battery saving in our P500 and it seems that power consumption is the same for frequencies of 480 mhz and below, so in the end, the phone sleeping at 245 consumes the same battery as when it's sleeping at 480.
With that in mind, it's much more convenient to set the clock at 480 mhz at it's minimun since it provides a better response and wakes the phone faster, ending up in less processing time with same battery consumption.
I using 320\748 SmartassV2
480/600 and im still sometimes getting random shut downs and KP's...
I use 480/864 running smartassV2
729/480 onDemand
Kernel: fserve 18c
Governor: minmax
Min: 480
Max: 600
Is my screen too bright, or am I just too ASIAN?!
I forgot to say my chipset config.
I am currently using Franco Kernel along with Andy's Phoenix ROM.
Max 748 MHz
Min 480 MHz
Governor SmartassV2
Used SetCPU for this matter. I'm actually getting an awesome battery life and excelent performance. I'm usually exigent, but this time I can say I'm satisfied.
InfiniteRisen said:
Kernel: fserve 18c
Governor: minmax
Min: 480
Max: 600
Is my screen too bright, or am I just too ASIAN?!
Click to expand...
Click to collapse
Probably, for me it looks too bright at 40% and I had to put it to 25%.
729(max) and 480(min) with SmartassV2 governor is the best
Sent from my LG-P500 using XDA App
NonCrowd said:
I use 480/864 running smartassV2
Click to expand...
Click to collapse
which rom and kernel are you using...
I'm pretty noob at making overclocks. How do I know the overclock I'm using is crashing/bugging/killing my phone? I'm using mik Cyanogenmod 6.6.1 480/748.
Related
i'm using SetCPU:
governor: conservative
freq range: 200-1,200 mhz
undervolted
have tried various kernels (ninphetamine, speedmod, ragemod - current, mirage) and roms (cognition, solarflare, and leomar -current)
one thing in common is that it in doesn't keep the freq at the minimum for a longer period. even after an 8 hour idle time at night, my phone's at 30% on the 200 mhz, and at about 35% at the 800 mhz.
anyone with the same problem?
i'm using only the setCPU widget and no other downloaded/installed apk's which run in the background (i.e. ATK, etc)
The phone will clock up as and when required, this is normal, it won't stick to the lowest unless you clamp the scaling down, also the phone will clock up on touch inputs to keep things smooth.
Sent from my GT-I9100 using xda premium
thanks!
+1
poch_1421 said:
i'm using SetCPU:
governor: conservative
freq range: 200-1,200 mhz
undervolted
have tried various kernels (ninphetamine, speedmod, ragemod - current, mirage) and roms (cognition, solarflare, and leomar -current)
one thing in common is that it in doesn't keep the freq at the minimum for a longer period. even after an 8 hour idle time at night, my phone's at 30% on the 200 mhz, and at about 35% at the 800 mhz.
anyone with the same problem?
i'm using only the setCPU widget and no other downloaded/installed apk's which run in the background (i.e. ATK, etc)
Click to expand...
Click to collapse
Aren't you using a Screen Off profile...? A powersave bias value could also help
What are the best settings to have you phone's CPU speed set at? I'm looking for both good performance and good battery. Also I am using the default overclocker, what is the best one? Thank you guys for your time.
Sent from my LG-VM670 using XDA Premium App
I use SMARTASS as my CPU speed governor and I set my CPU to 480-748 MHz, seems pretty stable for me.
Sent from my LG-VM670 using xda premium
thaunknownartist said:
What are the best settings to have you phone's CPU speed set at? I'm looking for both good performance and good battery. Also I am using the default overclocker, what is the best one? Thank you guys for your time.
Sent from my LG-VM670 using XDA Premium App
Click to expand...
Click to collapse
Overclocking values differ from phone to phone. Test it out with different values and use the one which is stable for you.
This was just discussed in the IHO technical-discussion thread, as a matter of fact.
My phone is stable for most stuff at 806 MHz, but sometimes the camera will cause a freeze/reboot. So I run at a 786 MHz max. Your phone will be different; this has to do with minute physical differences between individual chips.
The thing to keep in mind when overclocking is that the processor in our phone (unlike those of many other phones) does not make use of dynamic voltage scaling. There are only two voltage levels: a lower one if the phone is running at or below (or is it just below? correct me if I'm wrong, guys) 480 MHz, and a higher one if the phone is running above. So below 480 MHz, the system will give the processor a certain amount of voltage (period), and above, the processor will get a certain higher amount of voltage (period).
Because of that, the tests that have been done indicate that 806 MHz is the sweet spot for battery efficiency when the phone is in use--and the closer you get to 806, the better. Thus, I've had the following settings for quite some time:
786 MHz min
786 MHz max
Performance governor
which has treated me pretty well. On a day of light to moderate use, I'd end up with 65-75% battery left (occasionally more like 80%), depending on cell signal where I am et al. And it gives me probably the best performance I'm gonna get out of this phone.
However, I very recently decided to change the minimum to below that 480 MHz threshold and see what a lower voltage when idling would do for my battery life. My current settings are:
320 MHz min (may change to 480)
786 MHz max
Smart*** governor
There is actually a noticeable performance decrease when I first wake the phone up, so I may switch governors as well. In any case, I've had those settings for only one full day now, but for that one day the battery life was noticeably better. I'll post an update when I've had a few more days to test.
As always, it's difficult to quantify battery life in a reliable/rigorous manner (much less a universally applicable one), so YMMV.
Is overclock make battery drain?
are you overclocking ? as in are you using frequencies higher than 998MHz?
pheel said:
are you overclocking ? as in are you using frequencies higher than 998MHz?
Click to expand...
Click to collapse
i overclock to 1113MHz
Sent from my X10i using xda premium
Yes sure it will consume more battery if you overclock it,but better performance
derrickrs said:
Yes sure it will consume more battery if you overclock it,but better performance
Click to expand...
Click to collapse
thank for ur answer
Sent from my X10i using xda premium
That's not 100% correct. if you download an app like CPU Spy you can monitor how much time your phone spends on each CPU state. unless you do a lot of gaming and other CPU intensive activity your phone will spend most of it's time in lower CPU states. unless you specify that you want it to run at 1113 MHz at all times which yeah, would kill your battery faster. just looking at CPU Spy on my phone OC'd to 1228 MHz it has spent 70 hours in Deep sleep and 25 hours on 245 MHz. only 3 hours at 1228 MHz.
So unless you do CPU intensive things on your phone you shouldn't notice an overly dramatic change in battery life.
is overclock brick my phone ?
pourya-man said:
is overclock brick my phone ?
Click to expand...
Click to collapse
If your motherboard got burnt by overclocking, your phone is bricked.
thank's
if i set cpu Frequency to 900 Mhz haven't problem for my phone
pourya-man said:
thank's
if i set cpu Frequency to 900 Mhz haven't problem for my phone
Click to expand...
Click to collapse
NO problem. The best CPU frequency is either 864mHz or 883 mHz. Up to you!
No kernels we have will do that I'm pretty sure because we haven't entered the wonderful world of voltage changes. Just keep the bat temp under 50 degrees
Sent from my GT-S5830 using xda premium
Which software shows the CPU temperature
Ah its maybe brick some phones
But its power off immadietly when got high temperature
Sent from my GT-S5830 using xda premium
Overclocking too much like more than 900 Mhz may get your phone in high temperature. Also continuous overclocking can reduce your processor's remaining life span. So if you're planning to use your phone for long time. I'd suggest to not to.
PS:
1) I have overclocked to 864Mhz for normal use (Using SetCPU), Priority: 50%
2) To stay away from heating, given max Clock to 640Mhz when Temperature is >39%, Priority: 75%
and there are some other profiles too but irrelevant to this topic.
Siyah kernel + Checkrom...
Tried Voltage control, setcpu....
So, for specific frequency under performance governor, i can set any voltage...
Under all other governors it work ok...
Please help.
Sent from my GT-I9100 using XDA
mad_max911 said:
Siyah kernel + Checkrom...
Tried Voltage control, setcpu....
So, for specific frequency under performance governor, i can set any voltage...
Under all other governors it work ok...
Please help.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Performance governor uses only one single frequency (min freq = max freq) and is only useful for testing (benchmarks).
Do not use this governor for daily usage.
Select another governor, such as Ondemand.
You can still set min freq = max freq, if you want your phone to run on only one single frequency.
Thank you. Very good point to use, let say ondemand and min/max at same frequency... why didnt i think of that??... About performance governor, it does feel "snapier" in day to day usage, deep sleep still works and battery is not much worse as screen still uses 60% of battery.... only time when performance governor uses much more battery is if u are using gps or some background task that is preventing phone from going to sleep while screen is off...
Sent from my GT-I9100 using XDA
UPDATE: After some more research i conclude: problem is NOT due performance governor or kernel... Same think happens on any kernel and governor if you set min and max frequencies same(custom voltage set in any program will not apply). Solution is to have minimun 2 steps( for example 1200 min and 1400 max mhz in my case). Further, you can use setcpu profiles for "screen off" etc., and battery loss due this performance governor imitation gets minimal....
Sent from my GT-I9100 using XDA