If i overclock but only when need more perform power whats the adverge life i ll get out my phone?
First of all how much do you want to overclock: 1,1-2,0 ghz ?
If you overclock to 2 ghz ( if you're phone is stable ) you will be sure you get a huge drain in lifetime. I have my phone overclocked to 1.4 ghz as I think this frequency doesn't harm your phone.
Second is not all the cpu's are the same, for me every frequency is stable, but maybe youre phone is only stable up to 1,4 ghz ( for example ). So keep that in mind.
The fact is you can't exactly say how long youre phone will last at what frequency as every phone's cpu is different. But I suggest, don't go over 1,5-1,6 ghz as you won't get any noticeable performance boost after that and at higher frequencies it does harm your phone.
So make a profile in "setxperia" and call it power or something you like, set it to 1,4 ghz max and threshold to 99 governor ondemand. This works the best for me, and if you don't need the power ( not gaming ) then switch it back to your normal profile i.e default.
Related
Hello Everyone
Is overclocking the defy to 1GHz is ok?and by ok i mean stable for a long time....and not for few months and then the phone is dead or something
thanx in advance
Many have been OC-ed to 1 ghz without any issue.
I'm running with 1000/52 in setvsel.
Overclocking doesn't harm unless the voltage is correct and not too much. OC to 1 GHz and see the lowest voltage that you can run stable on. Set it as the setting.
Also, CPU scales as per demand so your Defy will not run at 1 Ghz all the time, only when it requires that muscle...
And CPU's do last a long time, my 8 year old Pentium 4 just refuses to die...LOL
Running the Defy at 1000/52 and 75% with Setvsel. No problems and battery-power for full 3 days including a 6 hour geocaching trail. That's ok.
my defy can handle 1,2ghz long term, so you should be fine with 1ghz just make sure you set the vsel right, setting it too high could damage the cpu, setting it too low causes reboot, but no damage. so you can start by setting it to 50vsel, and if your phone is instable (i recommend setvsel and stability test for testing) set it a bit higher!
ok
thank you so much guys
Seriously no one knows, as no one has been owning and overclocking defy for over half year. But I think 1g is fine. Mine can easily go to 1.4g at 7x vsel, though I'm using 1.2g at 62 vsel.
mine maxed out on 1.37ghz, but im still using [email protected] theres nothing i use 800mhz cant handle, and with undervolting i can seriously lower battery consumption.
Mine is OC'd to 1ghz with Milestone overclock with no problems, and it's super fast also.
What is the highest MHz that i can go up to without risking my phone too much? My ROM and Kernal lets me go up to 1920 but thats probably not the best idea.
Scottymeuk said:
What is the highest MHz that i can go up to without risking my phone too much? My ROM and Kernal lets me go up to 1920 but thats probably not the best idea.
Click to expand...
Click to collapse
you have reason.... NO GOOD IDEA lol
in a kernel thread (a lot of time ago...) i was read... that was not recomended overclock avobe of 1600 Mhz... And atention important!!! don´t underclock down 170Mhz more or less (because can be the devece cannot exit from standby mode when you unlock the screen....) i cannot remember what was be the thread but i really believe that there is not a concret limit for overclock....
sure that it´s not good any tipe of overclock for improve the performance...
but i have a hero overclocked at 714 mhz (factory stock at 525 mhz) since 2009 and NO PROBLEM never,,,,
and my DHD overclocked at 1200 mhz (with a quality kernel in mode smartass)
and underclocked at 245 mhz more or less and no problem....
judge by your self but use the common sense... cheeeers
At the moment i have it on smartass to 1459 max and 230 min and it seems fine. Do i just judge it on the CPU temp, and if it stays quite low (Around 30c) then im fine?
Scottymeuk said:
At the moment i have it on smartass to 1459 max and 230 min and it seems fine. Do i just judge it on the CPU temp, and if it stays quite low (Around 30c) then im fine?
Click to expand...
Click to collapse
it depends buddy...
maybe its well.... the normal temp. of my batt. in use is 33-35º (but here in spain we are now at 30º !)
but my question is... are you really sure about its neccesary overclock our DHD?
I think that still DHD supports well all kinds of software with 1 GHZ of power...
maybe for a future thinks....or for gamming but always u can overclock for use a game and then return to 1ghz...
it´s only a suggestion... maybe another OP uses the processor of different mode...
The overclocking limit differs from device to device, so there is no general answer.
As a rule of thumb, when you start getting random revolts or crashes, you have gone too far.
If you want a more professional way, just slowly turn the clock of your CPU up and run a stress test after each time. It takes a bit more time but should get you pretty good results.
How long should i leave the stress test running for?
The reason i want to overclock it a little is that it just runs a bit more smoothly with it over clocked a bit. Just everything in general seems a bit better to use, its not really for gaming etc.
i dont want to under or overclock my defy...just want it as it is !!
What will happen if i install any custom rom ??
Will it O/C or U/C my defy ?? What r pros and cons of both ??
Not every custom rom, just some.
A developer usually write if the rom will under/overclock your device.
Despite this you can always choose to disable it.
CM7 will overclock and undervolt your CPU, so you should have more battery life and notice an increase in performance/general responsiveness. There's no risk in that, those values (300, 600, 1000 - I forgot at what voltages they are) are safe for daily use.
I know that MIUI e.g. bumps up your maximum clock speed to 1GHz (instead of 800MHz).
But I don't know why you don't like overclocking/undervolting, I use setvsel for some time (mainly to save battery because I have set pretty less vsel rates and when the screen is off it goes down to the lowest value) and normally you can't break your phone unless you set it to 2GHz and let it boot from start.
And when there are some settings included in a ROM you can be pretty sure that they won't be totally bad for your device.
what abt J boogie 3 liquid arc ??
Arjoma said:
I know that MIUI e.g. bumps up your maximum clock speed to 1GHz (instead of 800MHz).
But I don't know why you don't like overclocking/undervolting, I use setvsel for some time (mainly to save battery because I have set pretty less vsel rates and when the screen is off it goes down to the lowest value) and normally you can't break your phone unless you set it to 2GHz and let it boot from start.
And when there are some settings included in a ROM you can be pretty sure that they won't be totally bad for your device.
Click to expand...
Click to collapse
vap_66 said:
CM7 will overclock and undervolt your CPU, so you should have more battery life and notice an increase in performance/general responsiveness. There's no risk in that, those values (300, 600, 1000 - I forgot at what voltages they are) are safe for daily use.
Click to expand...
Click to collapse
Will jboogie3 liquidarc over or under clock ??
LiquidArc is based on CM7, so that is overclocked to 1GHz as well.
But if you really don't want that your ROM is overclocked you can still install it and then reduce the clockspeed to the standard 800 MHz yourself (Milestone overclock should be able to do that)
is it possible to overclock above 768mhz? my phone never gets warm and battery lasts 2+ days, completely stable at this speed, i want to learn how i can edit a kernel and increase the cpu voltage ever so slightly and increase max cpu clock and see whats stable, could you help me?
i think you will just start to get kernel panics if you try to go much higher .
i have another phone (lg 500) also with the same arm6 cpu that comes clocked at 600 from factory. i have the option to oc to 825 with custom kernel but it always panics at 806 and is stable at 787.
So i think if you want a faster phone go buy one
massigann said:
i have another phone (lg 500) also with the same arm6 cpu that comes clocked
Click to expand...
Click to collapse
Nope.
P500 has an ARM11 MS7227 processor
Wildfire has an ARM11 MS7225 processor.
http://xi0.info/qualcomm-chips-kernel-arm-phones_7000.html
lol the chipset for the wildfire is MSM7225 but the cpu is arm6/11? on half of the sites is arm6 the other arm11..
Hi I have mine set to 710 and any higher starts getting random reboots.
But overclocking any higher than 768, your risking a chip melt or definitely shorting its life.
This is really strange and probably even stranger to complain about but I want to understand.
I UV on my Note and so far managed to drop to levels I find hard to believe.
200MHz - 600mV
300MHz - 600mV
400MHz - 600mV
500MHz - 600mV
600MHz - 600mV
700MHz - 600mV
800MHz - 600mV
900MHz - 600mV
1000MHz - 600mV
1100MHz - 600mV
1200MHz - 975mV
1300MHz - 975mV
1400MHz - 1000mV
1500MHz - 1050mV
1600MHz - 1100mV
Why is my note able to run at 600mV on all frequencies up to 1100MHz??? At first I thought it was a reporting error and It wasn't really running on those voltages but found breaking points on higher frequencies so eliminated that theory. :silly: Would be to be able to test these frequencies at even lower levels. Anybody know a tool that can do it?
This is the process I followed:
Set the voltage value in STweaks,
Set the max MHz in STweaks to the frequency for which I just dropped the voltage ,
Close STweaks,
Open Voltage Control to confirm that the voltage and max frequency has really been set,
Close Voltage control,
Reboot,
Open Voltage Control again to confirm that the voltage and max frequency is really set,
Close Voltage control,
Reset timings in Android Tuner Free,
Start Stability - Classic Test and verify that the Note is running at the max frequency,
Open some other apps and play around for a while,
Get Stability Test back to foreground and go to sleep (if it is time to sleep)
For all of the above frequency values i ran the Stability Test overnight for at least 4 hours plus for a couple hours while using the phone. Didnt get a single freeze or reboot. The only issue was that while I had it on max 200 MHz the Note was not usable while the 300 and 400 MHz frequencies were annoyingly slow. 500 MHz and up is bearable even with Stability Test running.
Attached are the last status and test screenshots. The Stability Test has been running while I been also using it for calling, messaging, adjusting other app setting and taking screenshots.
I check the frequency timings in Android Tuner Free and it is usually 1-4% on offline, 95-98% on the tested frequency and sometime 1% on the frequency just above the tested one. All other frequency times usually 0%
Any ideas if something funny is going on or is this Note just unbelievably under-voltable???
MutantWizard said:
This is really strange and probably even stranger to complain about but I simply need to understand.
I UV on my Note and so far managed to drop to levels I simply cant believe.
200MHz - 600 mV
300MHz - 600 mV
400MHz - 600 mV
500MHz - 600 mV
600MHz - 600 mV
700MHz - 600 mV
800MHz - 600 mV
Rest of the frequencies are still at stock values
First I copy pasted some UV setting from another post and the Note ran without Issues. Then I started dropping a little bit here and there and at some point got some freezes and reboots but couldnt figure out which frequency was the issue so I returned all to stock and started one by one from 200 MHz. The above is where I got to so far and simply need to understand why or what is happening.
This is the process I followed:
Set the voltage value in STweaks,
Set the max MHz in STweaks to the frequency for which I just dropped the voltage ,
Close STweaks,
Open Voltage Control to confirm that the voltage and max frequency has really been set,
Close Voltage control,
Reboot,
Open Voltage Control again to confirm that the voltage and max frequency is really set,
Close Voltage control,
Reset timings in Android Tuner Free,
Start Stability - Classic Test and verify that the Note is running at the max frequency,
Open some other apps and play around for a while,
Get Stability Test back to foreground and go to sleep (if it is time to sleep)
For all of the above frequency values i ran the Stability Test overnight for at least 4 hours plus for a couple hours while using the phone. Didnt get a single freeze or reboot. The only issue was that while I had it on max 200 MHz the Note was not usable while the 300 and 400 MHz frequencies were annoyingly slow. 500 MHz and up is bearable even with Stability Test running.
Attached are the screenshots of the process at 800 MHz and the Stability Test has been running for almost six hous while I been also using it for messaging, adjusting other app setting and taking screenshots. After about 5 hours of 100% CPU load at 800 MHz the Note is down to 80% battery. Not really sure but it seems quite low power consumption.
I just checked the timings again in Android Tuner Free and 12% on offline, 86% on 800 MHz. All other frequency times 0%
Any ideas if something funny is going on or is this Note just unbelievably undervoltable???
Click to expand...
Click to collapse
1st thing, my STweaks is ver 1.1 but looks a bit different than your screenshots, pls confirm that.
2nd, I too like to underclock but had no idea you could push it as far as you . It's kind of like driving a car low on gas to see how far you can go.
3rd What ROM & kernel you on? I'm on X-Note 3.3 with Adam kernel.
Last, here's a screenshot of my undervolting...I'm kinda embarrassed compared to yours Note the differences in layout of STweak menu.
I'm inspired to go even lower now, my battery life is pretty awesome but I think I can squeeze it more.
tweeny80 said:
1st thing, my STweaks is ver 1.1 but looks a bit different than your screenshots, pls confirm that.
2nd, I too like to underclock but had no idea you could push it as far as you . It's kind of like driving a car low on gas to see how far you can go.
3rd What ROM & kernel you on? I'm on X-Note 3.3 with Adam kernel.
Last, here's a screenshot of my undervolting...I'm kinda embarrassed compared to yours Note the differences in layout of STweak menu.
I'm inspired to go even lower now, my battery life is pretty awesome but I think I can squeeze it more.
Click to expand...
Click to collapse
My STweaks is also 1.1 and guessing the menu difference might be due to different kernel. I am on RedPill, stock ROM and probably irrelevant but TWERP as well.
I have mixed feelings about the achieved UV. Very happy if it is true but suspicious that there is some kind of a reporting error and that I am actually not under-volting it at all.
I will soon update the OP since I have now been now testing the 900 MHz for the last 3 turns. Started at 900 mV then droped to 800 mV and now already running it for a couple hours at 700 mV. I just cant believe that its actually at at this voltage and running without issues.
MutantWizard said:
My STweaks is also 1.1 and guessing the menu difference might be due to different kernel. I am on RedPill, stock ROM and probably irrelevant but TWERP as well.
I have mixed feelings about the achieved UV. Very happy if it is true but suspicious that there is some kind of a reporting error and that I am actually not under-volting it at all.
I will soon update the OP since I have now been now testing the 900 MHz for the last 3 turns. Started at 900 mV then droped to 800 mV and now already running it for a couple hours at 700 mV. I just cant believe that its actually at at this voltage and running without issues.
Click to expand...
Click to collapse
Hmm yes, because you're going so low, it begs the question is the app reading accurate? I mean, you're reeeaaaal low. Would be good for a more knowledgeable person to chip in and give us feedback.
One thing - in your screenshot it shows your max frequency capped at 800MHz. To me that reads you are running only at 50% power. If so, that explains your insane battery life. From steps 900 and above you've left voltage at stock because they're unused. right?
tweeny80 said:
Hmm yes, because you're going so low, it begs the question is the app reading accurate? I mean, you're reeeaaaal low. Would be good for a more knowledgeable person to chip in and give us feedback.
One thing - in your screenshot it shows your max frequency capped at 800MHz. To me that reads you are running only at 50% power. If so, that explains your insane battery life. From steps 900 and above you've left voltage at stock because they're unused. right?
Click to expand...
Click to collapse
Yes higher frequencies still at stock and not used but will be getting to them at their own time. Fact though is that even with cap at current 900 MHz and with Stability test running I can still use the Note normally for any regular tasks. If I don't play games I would never need more speed.
Now updating the OP with the 900 MHz setting and screenshots.
BTW I just realized I added to battery life when transferring screenshots by connecting the Note to the laptop by cable. Battery life still remains to be seen.
Updated the OP with the full range of voltages 200-1600. I don't OC so those will not be doing. But I still have the original question.
Is it possible???
Gets more and more strange. GPU under-clocking and under-volting of following frequencies working for days without any usage issue. I changed the minimum and maximum MHz to include the below frequencies and didn't notice any difference in the Note behavior / performance. When running the stability test with GPU testing included I don't get any errors if running under 2 hours but if I leave it overnight the test does crash at some point in time without any other ill effect. I only know that it crashed coz it disapears and it tells me it crashed when the next day I re-start the test.
54MHz - 600mV
108MHz - 600mV
160MHz - 600mV
266MHz - 600mV
350MHz - 600mV
The fact though is I don't understand what to expect as an issue when under-clocking or under-volting the GPU.
Mate, you're still at it!?
Rereading your data, I strongly suggest you post these stats in whatever thread belongs to the kernel and/or tuner app you're using.
My overseas Singaporean work colleagues would say 'cannot be, cannot be.....'
tweeny80 said:
Mate, you're still at it!?
Rereading your data, I strongly suggest you post these stats in whatever thread belongs to the kernel and/or tuner app you're using.
My overseas Singaporean work colleagues would say 'cannot be, cannot be.....'
Click to expand...
Click to collapse
Yea slowly trying one by one new settings and letting it run for a while so that when I go to the next setting and experience an issue I am sure its the newest setting that's causing it.
Thanks will do as suggested.