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:
Related
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
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"
}
What exactly happens when the energy saving mode is enabled?
I know in the settings it tells you some points, like display freq, brightness, haptic feedback, but how far is the CPU getting underclocked exactly?
800mhz
Sent from my GT-I9300 using Tapatalk 2
How does the phone perform? The us model specifically. Does it seem to slow down a bunch?
800mhz is international. Maybe us is different. No idea how either perform
Sent from my GT-I9300 using Tapatalk 2
Yeah it is noticeably slower on some Apps, and even on Opera mini when I'm going back and forward through loaded pages it looks easily a third slower, but going through the phone menus and system internet browser seems about the same.
Thank you! Does it use all cores at ~800Mhz or just one or two?
I'm on power saving all the time (int version) and no slowdown for me, even when gaming, and it seems to save a lot of battery, the only slowdown is sometimes on wake-up when I swing to unlock it like slowmo waves on the screen but it is not happening every time (only when sleeping for a long time).
I live in SA and when i ran a benchmark, i was running at 1ghz on pwr saving
Sent from my GT-I9300 using xda premium
shaneel1491 said:
I live in SA and when i ran a benchmark, i was running at 1ghz on pwr saving
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I did a simple test. I use set cpu. When I open set cpu and touch the screen and move my finger around, the CPU will ramp up to 1700Mhz (Overclocked).
I then set power saving mode on and tested it and it wouldnt surpass 800Mhz.
I tested this as although I had read it was 800Mhz, I wasn't sure so I tested it for myself and it yielded the same results.
It's hard to perceive that it's running slower, but benchmarks are very low in power saving mode. According to Quadrant, it runs at 1Ghz in Power Save Mode.
Normal Mode
{
"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"
}
Power Save Mode
I just tried to play N64oid on power saving mode and it's really slow, so yeah for really demanding apps you'll see a differences but for normal games / apps there is no problem at all.
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"
}
Mine is -100mv on blu.spark and Ashwin's CM13. Never had any problems with this voltage.
{
"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 always using - 100 undervolt.
Sent from my ONE E1003 using Tapatalk
I'm stable at - 95
-100 was unstable for my OPX
Working on Swell-V8... I'm quite happy with this setup
It depends on individual phone. Subjective
Here is my setup. Using Boeffla's kernel and his app. Also, with this uv profile there are no more overheatings. The phone stays quite cold even on gaming and stuff like that.
-75mV overall. 100 was a bit unstable, maybe 90 could work but this way I'm completely safe.
As I already said, I'm on -100, but I still have high heating... 55°c when playing Minecraft for 20 minutes.
RJDTWO said:
Working on Swell-V8... I'm quite happy with this setup
Click to expand...
Click to collapse
Did you undervolt to an overall value or different for different frequency?In OOS, I had freezing even with - 25 mV.
saurabh40629 said:
Did you undervolt to an overall value or different for different frequency?In OOS, I had freezing even with - 25 mV.
Click to expand...
Click to collapse
Different for frequency
RJDTWO said:
Different for frequency
Click to expand...
Click to collapse
How do you do that? Once i tried, hit one wrong voltage, and phone never booted to system.
saurabh40629 said:
How do you do that? Once i tried, hit one wrong voltage, and phone never booted to system.
Click to expand...
Click to collapse
Patience. You find the lowest for each in 25mv increments and from there tune them. It's tedious. Obviously if you enter a random voltage then it don't work. If you don't entirely unfetdtand PLEASE read up on it or you will fry your phone
Currently at -100 to -125mv on Boeffla. No fc's or reboots since I started using these voltages.
-100mV on BluSpark kernel, no freezes, no reboots.
If you use Kernel Auditor, "Boot on system start" gets activated several seconds after the phone has started, so you can revert any errors in normal cases.
I can go -60mV, no more on bluespark v128.
If i go more than -60mV, i get reboots sometimes after 12hours or after 2-3 days