OK changing the question: what are the differences between 729 and 787 as Max for you? Don't answer if your phone crashes! What are the differences for performance/battery between them?
The highest level you can OC is 864Mhz. It affects CPU life and battery life A LOT!
Decrease the CPU speed can save the battery, but it also can make your phone slower...
thachtunganh said:
The highest level you can OC is 864Mhz. It affects CPU life and battery life A LOT!
Decrease the CPU speed can save the battery, but it also can make your phone slower...
Click to expand...
Click to collapse
Hehe you answered exactly how I expected the answer... I expected, but not wanted, already knew
Does setting to 787 decrease CPU life (heard of any G1/G2 with burned CPU?)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Seek the signature below the line
In my opinion I think after some time over clocking your going to come across some problems like battery frying phone over heating I haven't heard of anyone's CPU frying yet but it can happen but I think by the time you have used a few roms and done some experimenting and something dose go wrong a new p500 only going to cost u around £30 just take the risk
> about OC'ing, it affects diode life, chips are made with diodes, and it is computer related aswell, overclocking causes cpu diodes life to be shorten out, overclocking means more current, more current means more heat, more heat will cause diodes to be busted out easily, but I never head anyone here complained about a bricked O1 becoz of over clocking.. this is as far as i know, I also want to know if 600 and 806 are in same voltage? ta kernels had this undervolt features.. it means lower voltage some frequencies isn't it? but undervolt causes more heat, why?
I have a 787 MHz maximum stable frequency. In the matter of performance / battery life to save the answer is simple:
The higher the frequency of the processor, the better the performance, but consumes more battery power, as well as its temperature rises. To play well, the battery is bad
Related
Im using SiyahKernal and I'm curious about undervolting.
I want a safe/ok combo that will be smoothish and fastish but good for battery.
I'm currently running the cpu at 900mhz using extweaks.
Any suggestions? what're your settings?
Undervolting takes time and patience.
Start with -25 first and test if it is stable for a day or two.
If it is, move on to the next step.
Personally I didn't undervolt yet because it seemed to lower my average benchmark scores. Overclocked to 1704 and get 63k average in quadrant!!! (Not that it really matters in daily use...)
Yes do it in steps. The only danger is too low a voltage will cause a reboot when idle if theres not enough power to keep going.
I got mine to -100 for every step, stable. This means Samsung were generous with their voltages IMHO, but OEM's generally are. HTC are the same.
rootSU said:
Yes do it in steps. The only danger is too low a voltage will cause a reboot when idle if theres not enough power to keep going.
I got mine to -100 for every step, stable. This means Samsung were generous with their voltages IMHO, but OEM's generally are. HTC are the same.
Click to expand...
Click to collapse
Thats amazing! how was your battery?
So the only danger is a reboot? no damage? apart from the obvious loss of work unsaved or game etc.
Not really bothered about benchmarking. just battery life with at least an 'ok' performance. i can easily set it up later when i need performance.
Just really love this phone and am mosty working all day.
Not really for undervolting. Its over volting that causes damage. Battery is ok. Not amazingly better. Cell Standby is killing me.
rootSU said:
Not really for undervolting. Its over volting that causes damage. Battery is ok. Not amazingly better. Cell Standby is killing me.
Click to expand...
Click to collapse
yeah cell standby is a big hog. it drains more than 45% of my battery every charge
Only posted yesterday on Jayce Ooi's Paradise
How to undervolt Samsung Galaxy S3?
http://www.jayceooi.com/2012/06/20/how-to-undervolt-samsung-galaxy-s3/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i m using cm7 stable rom on my p500........with overclocking min 480/max729 ,governor-performance,scheduler-cfg.....
is there any effect of overclocking on battery life or performance on mobile?
more performance but lower battery life.
Mmm ok I have some questions, what is a normal overclock to improve battery life but without sacrificing a lot of performance.
And the other way around, an overclock that improves some performance without sacrificing too much battery.
What are the "optimal" values of an overclock (Without making the phone unstable)
I would just overclock until you get phone instability or you go as far as you can for the current kernel (I'm on AOKP 4.0.4 and it's 787 max which is what I'm at).
Battery life doesn't get affected that much because it's mostly drain when playing games where it ramps up to the max clock speed, at which point you're draining a lot of battery anyways.
Koraboros said:
I would just overclock until you get phone instability or you go as far as you can for the current kernel (I'm on AOKP 4.0.4 and it's 787 max which is what I'm at).
Battery life doesn't get affected that much because it's mostly drain when playing games where it ramps up to the max clock speed, at which point you're draining a lot of battery anyways.
Click to expand...
Click to collapse
Thanks, I also have AOKP so I'm going to work around it a bit, how can I test stability?
Go to Rom Control.. Performance.
Remember to UNCHECK " Set at boot" option.. so that if anything happens.. it can return to default value after a reboot.
If random reboots or white screen appears or phone hangs.. its not stable.
I'll rephrase my question, what type of test can I do to ensure I have a stable overclock. I don't want to find my phone turned off out of the blue and maybe missed an alarm or what not. Thanks anyhow for the tips
Just do general usage. If it works fine for 2 weeks at a specific clock, it's likely to be okay.
kibaruk said:
I'll rephrase my question, what type of test can I do to ensure I have a stable overclock. I don't want to find my phone turned off out of the blue and maybe missed an alarm or what not. Thanks anyhow for the tips
Click to expand...
Click to collapse
You will only know by using. The CPU manufacturers label a chip ancertain speed because it fails a test at the next level. That means that some chips can handle faster than others. They are guaranteed to be stable at the rated speed.
There is no formula
Sent from my LG-P500 using xda app-developers app
Thank you everyone who helped me in here
Overclocking kills lifespan of processor...
Dwars said:
Overclocking kills lifespan of processor...
Click to expand...
Click to collapse
Not necessarily. Voltage and heat are usually what kills electrical components. Since our device can't change voltage for the CPU, that point is irrelevant. However, heat is a factor but AFAIK the heat from overclocking doesn't increase that much for this device, unlike something like PC CPUs so that's fine as well.
Koraboros said:
Not necessarily. Voltage and heat are usually what kills electrical components. Since our device can't change voltage for the CPU, that point is irrelevant. However, heat is a factor but AFAIK the heat from overclocking doesn't increase that much for this device, unlike something like PC CPUs so that's fine as well.
Click to expand...
Click to collapse
No, you can damage it. If it heats up, then:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is unfortunate, it is not even hot so I don't know what's up.
Sent from my LG-E970 using xda premium
There is the temp as says setCPU
Whats your max. level?
My one going only till 63%
Oh there a screenshoot attached.
Anyway its far higher than the 63% at 39C
Tim4 said:
Whats your max. level?
My one going only till 63%
Oh there a screenshoot attached.
Anyway its far higher than the 63% at 39C
Click to expand...
Click to collapse
I am unsure if this is just over caution on their part of if this is something we need to be worried about... honesty even yours at 39c is not that hot 102 F which for a computer is whatever... but I thought this chip was supposed to run cooler and everything being the new architecture.
I have been doing a lot of CPU testing and noticed a couple of things:
First of all the issue with the screen not turning brighter is simple: the heat within the device reached a certain limit that could potentially damage it.
the CPU, RAM and the screen light are the main culprit. Especially the CPU and RAM, try CPU stats and after heavy use you will notice the phone gets warm/hot and the freq gets capped out at 1.1 GHz by the kernel. This is mainly to reduce the heat obviously....I guess keeping the phone running at 1.5 GHz with all 4 cores and the screen cranked up to max will definitely turn the phone into a Coleman stove in no time.
So i guess this powerful CPU doesn't do any better than any dual core running constantly and stable for the same amount of time to crunch performance levels. Sigh...I guess until they wont figure out to make things run cooler powerful CPU's wont get far-only on paper
Just my 2 cents
gafalas said:
I have been doing a lot of CPU testing and noticed a couple of things:
First of all the issue with the screen not turning brighter is simple: the heat within the device reached a certain limit that could potentially damage it.
the CPU, RAM and the screen light are the main culprit. Especially the CPU and RAM, try CPU stats and after heavy use you will notice the phone gets warm/hot and the freq gets capped out at 1.1 GHz by the kernel. This is mainly to reduce the heat obviously....I guess keeping the phone running at 1.5 GHz with all 4 cores and the screen cranked up to max will definitely turn the phone into a Coleman stove in no time.
So i guess this powerful CPU doesn't do any better than any dual core running constantly and stable for the same amount of time to crunch performance levels. Sigh...I guess until they wont figure out to make things run cooler powerful CPU's wont get far-only on paper
Just my 2 cents
Click to expand...
Click to collapse
You are right on point. I have seen it drop (I believe to 1180) when running a bunch of benchmarks. The manufacturer sets the heat threshold at a very safe level. Kernel devs are usually able to safely bump that up another 10 to 15 degrees. I am one of the lucky ones that got the variant 3 of the international One X. Variant 3 was the strongest version and I ran all 4 cores at 1600 with 51 minimum. Faux usually figures out how to uncap and raise the throttle temperature... but he's on a N4. I am going to keep an eye on the kernel threads there and see how far they push things. Chainfire's "PerfMod" app is perfect to watch this while running different apps
Sent from my LG-E970 using Xparent ICS Tapatalk 2
So I open an app like the play store or chrome in the screenshots and get 100% load for 10 seconds or more. I noticed this behavior on different roms and kernels/governors.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's only 51% maxed out would be BOTH CPUs at 100% so really your concern is?
Sent from my Nexus 10 using XDA Premium HD app
Because it's a waste of energy.
reborn90, sorry for the off topic question but what are those system widgets (CPU, Disk I/O .. etc)?
Perfmon its the app
Sent from my Nexus 10 using xda app-developers app
reborn90 said:
Because it's a waste of energy.
Click to expand...
Click to collapse
Without accounting for exactly what the CPU is doing you really can't make this assertion.
Me neither, that's why I ask. It just looks buggy when the cpu starts scaling to max frequency (for a long time) because a new app is started.
reborn90 said:
Me neither, that's why I ask. It just looks buggy when the cpu starts scaling to max frequency (for a long time) because a new app is started.
Click to expand...
Click to collapse
Try a different governor, or maybe increase/decrease the refresh rate of your resource monitor? (BTW, scaling to max speed on load is actually better for battery life in some cases, as the task energy required can be sometimes be lower when you burn more juice but complete a given task in a shorter period of time).
The cpu (core) load shoud be independent from the governor, apart from the current frequency of course. I still have the feeling that it is some kind of "phantom load" but actually I have no idea. I switched from an ASOP rom to CM10.1 and I haven't seen the problem yet. :fingers-crossed:
reborn90 said:
The cpu (core) load shoud be independent from the governor, apart from the current frequency of course.
Click to expand...
Click to collapse
Its true that load wouldnt be caused by the governor, but the governor you run does affect how load is handled and whether there averages more or less load on the system. By running at a higher speed the system load is decreased because the processor is going through its tasks much faster. If the governor is keeping the speed lower while doing a task then the system load will be much higher because the CPU cant complete things as fast. So load and governor are linked together, but it is the tasks being run that cause any of the load in the first place.
Since the problem hasnt come back since switching to CM10.1 it was probably something in the system that got bugged and caused this behavior.
Yes I agree, but in this particular case I have maximal frequency and core load. It's much better now with cm10.1. :good:
I am not sure if it is confirmed issue. I remembered quite a number of report of early variance of kenzo owner found the phone be quite hot even it is idle.
I am also experiencing this issue. Idle temperature easily goes up to 65 degree (pa_therm1).
I don't think it is normal for an idle phone. Another some other users having this value as low as 35 so I thought it could be hardware issue. Can anyone confirm this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is mine with only wifi and browsing...
If only one sensor reads high value it can be just showing you incorecctly
mcdull said:
I am not sure if it is confirmed issue. I remembered quite a number of report of early variance of kenzo owner found the phone be quite hot even it is idle.
I am also experiencing this issue. Idle temperature easily goes up to 65 degree (pa_therm1).
I don't think it is normal for an idle phone. Another some other users having this value as low as 35 so I thought it could be hardware issue. Can anyone confirm this?
Click to expand...
Click to collapse
I don't know if you use any kernel tweaking apps, but the cpu sometimes tends to be stuck on performance governor.
Sent from Note 3, Xiaomi Redmi Note 3.
No. I did not. And I have left the phone overnight idle and just recorded 55C pa_therm1
And most time it was in deep sleep.
Denis:) said:
This is mine with only wifi and browsing...
If only one sensor reads high value it can be just showing you incorecctly
Click to expand...
Click to collapse
Your pa_therm1 is strangely low as well...
Nah thats fine..if the phone is not hot dont worry
if something is running that hot around 65c you will feel it through the metal chassis, if you phone is cold to the touch all around then I don't think there is anything to worry about, it could just be a fake unhooked up sensor, or uncalibrated even defective, as far as I know the pa_therm is related to the voltage regulator, and most often quality vregs can handle very high temps.(140~c)
My worry would be unnecessary thermal throttling that would affect performance.
mcdull said:
My worry would be unnecessary thermal throttling that would affect performance.
Click to expand...
Click to collapse
man mine sometimes heats up to 41 deg celcius on 2.3 ghz oveclocked kernel but i can feel it goes warm on my hand , so if you can't tell if its heating by holding it then no need to worry.
perhaps if yours IS really heating up you should go find the cause , ie the app that goes on infinite loop of restarting its service .