hello,
i don´t think any app uses all cores at the same time, so is it possible to turn off for example 4 of 8 cores, in order to increase batterylife ?
dont do it, ALL the cores are been used almost ALL the time.
Even if an app dont uses all the cores, there are a looot of apps that running at the same time.
if you monitor your cores activity you will see that all core are being used.
If you turn off some of them you will increase the load on the remaining cores, so finally you
wont have saved any battery.
Related
I would like to know if it is safe to change the max cpu lock from quad core to single core mode when in need of battery or even other modes? How about for daily use but still needed battery life?
BelJanss said:
I would like to know if it is safe to change the max cpu lock from quad core to single core mode when in need of battery or even other modes? How about for daily use but still needed battery life?
Click to expand...
Click to collapse
you can find more information about this in Siyah's Kernel thread.
I locked mine to 2 cores. After researching about turning off cores, it's mentioned that it's best to just leave all 4 cores on and let android manage the power. I will turn all 4 cores on later because i'm testing dual core mode for personal reference but it maybe void because i've under volted my cpu along with turning off the 2 cores. So far my battery is draining less and i'm using my phone more this morning. I don't even notice a performance drop. My phone is still smooth..but then again i do not use my phone to play games that require a lot of performance.
Thanks for your response. I'm now testing my s3 in a single core mode and battery draining is less also. For the performance I can say that it is not bad. However, what I'm afraid of it is if has bad effect on the cpu itself.
Hi Guys,
I am a noob here. I have never used a android phone before, not even a iPhone - so basically no smart phones.My first smart/android phone would be Nexus 4 which would be coming tomorrow.
I have been reading threads to understand andriod architecture and believe have understood to certain extent.
I have a question in clocking the CPUs and Voting.
As I understand, we have 3 states -Max, Min and Sleep for a single CPU core
Max - The frequency (clock speed) which CPU executes or maximum speed which CPU sends signals to its components and get the response back. This would be used when the system is on - which means when user is doing some process.. like texting, video chat, gaming (this case GPU is also involved) etc.
Min - This would be for background process when the user/phone is idle - that when screen is off (eq - gmail sync, facebook sync etc..)
Sleep - Screen off and no background process , the core will be in sleep.
And the battery level will be directly propotional to speed of CPU with respect to the volting.
Now lets say there is a single core processor in a phone which can clock upto 1.5GZ. and the stock kernel comes up with Max - 1.3GZ and MIN -0.5 GHZ.
Question is abt overclocking minimum frequency
1. why not overclock the Mn frequency to 1.3Ghz? because the backgroundprocess would be fast and phone/core will be sleeping after that,
which means process consumes more battery at that particular time but overall baterry should be efficient as there would be more sleeping time.
2. About volting, so far I have not seen min and max volting. So is there only one voltage/power drawn for max and min CPU speeds by CPU?
Please correct me if any of my statements is wrong.
Appreciate your help,
Thanks,
Franklin B.
Overclocking the minimum frequency to 1.3ghz would probably decrease your processor's life if you use your phone too much but I have been actually increasing my phone even 200mhz more than it was in stock ROMs, i've been using my device for more than 2 years and it still works perfectly. Finally, it all depends on how much your phone is good.
I also decreased the cpu min and max frequency when phone sleeps to 256 mhz which decreased a lot battery consumption.
Hope i helped !
Don't forget the THANKS button
1.you can but your battery life will be drastically reduced! There is a good amount of time after the screen is off and before the phone sleeps! So if over clock the min to 1.3Ghz, the processor will be running at 1.3Ghz till it goes to sleep! But if that's what you want you can do that!
2 . I'm not so sure about this topic either but I think the processor operates at a particular voltage and I could be wrong!
Sent from my GT-P3100 using Tapatalk 2
Thank you Guys
Franklin Bernard said:
1. why not overclock the Mn frequency to 1.3Ghz? because the backgroundprocess would be fast and phone/core will be sleeping after that,
which means process consumes more battery at that particular time but overall baterry should be efficient as there would be more sleeping time.
2. About volting, so far I have not seen min and max volting. So is there only one voltage/power drawn for max and min CPU speeds by CPU?
Click to expand...
Click to collapse
Hi, I received your PM. I agree with the guys about the heat issues, longevity, and battery life etc. The answer to your question #2 will help you better understand things.
In all kernels, there are frequency/voltage scaling tables. For every frequency step (clock speed) in the table, it corresponds to a specific voltage. It gets a bit more complicated than this of course, but that is the basic way things are setup in the kernel. The higher the frequency, the higher the voltage is required to be to keep the CPU (or GPU, bus, RAM etc.) stable at a given clock speed. The more voltage, the more current, and the more heat is generated. The longer you stay at higher clock speeds/voltages, the better the cooling system you need to have. Supply regulators are defined to feed the core and rail voltages so that the processor can live in a happy environment no matter what it is being asked to.
As far as power consumption, it's all about getting a unit of work done in a timely/efficient fashion using the least amount of power consumption. If the phone is sleeping, the word "timely" takes on a different meaning so then it is mostly concerned with power consumption and getting the background tasks completed effectively without having the phone experience the sleep of death (SOD). What you are talking about is the theory of "race to sleep" so that the work can be done quickly and the phone can go back to sleep where it uses the least amount of power (clocks actually turn off during deep sleep and cores are turned off). However, there is a happy medium to this theory and heat and battery consumption are the main enemies. Heat can also rob efficiency, more current is required when a circuit heats up. The more a phone wakes up to do syncs for email, apps, social networking, missed calls etc., that work can stack up throughout the day. The question comes down to how can the device get this work done using the least power and keep the device cool. On the N4, the lowest frequencies can use ~700-800mV per core while the highest frequencies can use ~1100mV. There is a drastic difference in the amount of heat generation between this range.
I think this should give you the general idea and maybe more that you wanted to know! Here are some links to check out if you are interested. Google and you will find many many more articles and research papers.
http://en.wikipedia.org/wiki/Voltage_and_frequency_scaling
http://atrak.usc.edu/~massoud/Talks/Pedram-dvfs-Taiwan05.pdf
Thanks a ton !!!
I just wanted to know if its normal for a galaxy s iii to turn off 2 cpu cores when it gets "hot"?
Or when playing games like n.o.v.a 3
CPU throttling is possible, yes, but I don't think it disables cores. From what I can tell, it clocks down the cpu.
Theshawty said:
CPU throttling is possible, yes, but I don't think it disables cores. From what I can tell, it clocks down the cpu.
Click to expand...
Click to collapse
Im running Perfmon while running a game 2 see my cpu usage, after some time the phone gets hot and 2 cpu cores turn off.
Hey guys
I was looking over the power saving options and theres not that much in there, it just disables some stuff which you could do manually and I started thinking about my Galaxy S3
with power saving on it would underclock from 1.4 too 1.0 and save around 1 hour of screen on time, but did lag a bit
Sony should have done the same and underclocked it from 2.2 to 1.5, I say this because 1.5 is really enough anyway, and the amount of battery it would save would probably be a lot!
What do you guys think?
J
JackHanAnLG said:
Hey guys
I was looking over the power saving options and theres not that much in there, it just disables some stuff which you could do manually and I started thinking about my Galaxy S3
with power saving on it would underclock from 1.4 too 1.0 and save around 1 hour of screen on time, but did lag a bit
Sony should have done the same and underclocked it from 2.2 to 1.5, I say this because 1.5 is really enough anyway, and the amount of battery it would save would probably be a lot!
What do you guys think?
J
Click to expand...
Click to collapse
I do not understand your reasoning... You are assuming that a device that is able to do 2.2Ghz, is running at 2.2Ghz all the time?
Normally, when you task the CPU 100% -> 2.2GHz
But it uses different profiles. So a 10% task, will maybe run the cpu at 800Mhz
Please note: i do not know exactly how many power profiles are in the Snapdragon 800.
But if you perform x task in 10 second at 800mhz, or 3 second in 2.2Ghz ... in battery level its not to make a big difference ( unless your task is going for hours ).
Also remember, your S3, used a 1 + 4 configuration. That means, minimum tasks are run on the slower core. Large tasks it activates the 4 core setup. Its possible on the older Tegra3, that the 4 cores may not be powered gated, and you are activating too many cores, for the task your running. Or its leveling the power profile on all the cores, when running a single task. So that is why you get a hour more battery life ( i assume again, you mean on-screen battery life ).
The Snapdragon unlike the Tegra3, runs in a 4 core configuration with power-gating the idle cores. So it does not need to constantly switch between little.big configurations ( that little.big is designed to safe power, but it also costs power when it needs to do a lot of switching ).
If you deliberately slow things down, yes, you can save power. But you also wait longer for the task to finish. Unless somebody can show conclusive evidence that locking your CPU down, has a advantage, i will more or less state, that under normal situation ( surfing, chat, email whatever ), your screen is actually the biggest power drainer. I see this clearly also on my device, with it draining over 50% on a 5h+ on-screen time.
Unless people have done some experiments, i assume that any advantage of lower clocking your cpu, will be minimalism. Unless you lower clock your CPU, AND also under-voltage your CPU.
I think you will see much more energy gain, from lowering your screens brightness ( and disabling the automatic screen strength adjustment ), especially with this big 6.4" screen. Or just get a Power Jacket...
http://shop.brando.com/Power-Jacket-with-cover-For-Sony-Xperia-Z-Ultra-4500mAh_p10103c1591d003.html
That gives you a nice 80 a 90% extra charge on the road. Or install a USB-lighter plug in your car, and voila. More mobile power source *lol*
Hi XDA folks! Sorry if this has been posted before, I looked and can't find any information.
----
I installed CPU memory monitor on my Note 3 and closed all background applications in "active applications". I also greenify literally everything that doesn't cause a problem. However, the CPU usage on my android device, with absolutely nothing open except the CPU monitor, is about 10%.
On my PC, when idle, the CPU usage never goes above 3% (i7 @ 4.5ghz), however shouldn't my phone do the same? The most resource intensive process is cpumonitor itself - using 2% CPU. System stays about .5-3%.
My theory is that, because the phone is underclocked to a very low frequency when idle, any little task will use a bit of CPU percentage. Is my theory correct?
I also noticed a lot of RAM is used idle, but this is no problem to me. I know unused RAM is better, it is good that Android caches everything it can.
Thanks a lot