Hi,
Ive noticed that i get horrible scrolling lag, however if I set the min cpu frequency higher it's fluid.
Ive read up on mpdecision which sets the min cpu freq when the screen is touched, and this is 800mhz for the S3. However, this is not smooth, and if I set my min freq to 1.1ghz its nice and smooth. However, I don't want it at 1.1ghz all the time since it'll drain battery.
So, is there a way of editing mpdecision values? I can't find anything on google.
Thanks,
Jack
Related
I was just wondering what people get for battery life with miui 1.7.8 and OTB .13 kernel.
Also, what does overclock actually mean? Does it mean that setting the min and max to 1400Mhz in Voltage Control or remain the min to 100 and max to 1400Mhz?
I'm currently on noop, ondemand and min=100Mhz, max=1400Mhz with nothing UV'ed.
Please help me to get better battery life!!!!!!!!
Your CPU by default can do, unmodified, a certain number of commands per second. These commands are measured in Hertz, thus a 1GHz processor does about 1 billionish commands per second. Overclocking means you allow your processor to do more commands in the same time frame. The downside to this, however, is that more electricity is flowing through the CPU, thus draining the battery more. Having a lower clock speed will save some battery life.
That being said, I have kept my CPU clocked at maximum of 1GHz, with the I/O Scheduler set to deadline and the CPU Governor set to smartass, and I'm getting about a day out of my battery, maybe a little less. I have no idea if that's the "optimal" battery saver setting, but it works for me.
I do have a question, though... What do those two settings mean, anyway?
1n73rn37_j3d1 said:
Your CPU by default can do, unmodified, a certain number of commands per second. These commands are measured in Hertz, thus a 1GHz processor does about 1 billionish commands per second. Overclocking means you allow your processor to do more commands in the same time frame. The downside to this, however, is that more electricity is flowing through the CPU, thus draining the battery more. Having a lower clock speed will save some battery life.
That being said, I have kept my CPU clocked at maximum of 1GHz, with the I/O Scheduler set to deadline and the CPU Governor set to smartass, and I'm getting about a day out of my battery, maybe a little less. I have no idea if that's the "optimal" battery saver setting, but it works for me.
I do have a question, though... What do those two settings mean, anyway?
Click to expand...
Click to collapse
What do you mean by two settings?
Like, what are I/O Schedulers and CPU Governors? That last question was me hijacking the thread.
As I understand solution for "998 MHz with screen on" bug is found: http://forum.xda-developers.com/showthread.php?t=1225411&page=17#post16944722
We need to replace only one governor.
I don't want to play with different ROMs and kernels and I'm looking for simplest solution.
Is it possible to compile it as a module ("ondemand_mod" for ex.) and add it to stock ROM?
Or any other (simple) way?
Wrong section ...
Sent from my X10i using Tapatalk
Why wrong Section, this is Development to get the CPU Governor working correctly
Wolfbreak said:
Why wrong Section, this is Development to get the CPU Governor working correctly
Click to expand...
Click to collapse
Exactly, this is the right section for such request.
However, I can't help but wonder: is this really a "problem"?
No offence to anyone, but I find that the phone is very snappy
when on max frequency... The big problem for me, would be if it
didn't go into Deep Sleep immediately after turning the screen off
and stayed at min frequency for an extended period.
When the screen is on (aka using the phone) I'd like it to be as FAST
as possible. That's the reason I use the minmax governor.
Anyway, again, I don't mean to argue with anyone, I am just
presenting my point of view.
My_Immortal said:
However, I can't help but wonder: is this really a "problem"?
No offence to anyone, but I find that the phone is very snappy
when on max frequency... The big problem for me, would be if it
didn't go into Deep Sleep immediately after turning the screen off
and stayed at min frequency for an extended period.
When the screen is on (aka using the phone) I'd like it to be as FAST
as possible. That's the reason I use the minmax governor.
Anyway, again, I don't mean to argue with anyone, I am just
presenting my point of view.
Click to expand...
Click to collapse
Yes, it's really problem.
Higher frequency - higher power consumption. Moreover - with higher frequency CPU used with higher voltage so consumption is even more higher. So at 998 MHz CPU eats about 5 times more battery than on 246MHz.
With properly tuned governor I don't feel any real lags or slowdowns.
And, when screen is on CPU load is usually is lower than 20% at full frequency. So I don't want to waste my battery.
As I see it's possible to compile and use governor as module.
Could someone compile it? And assemble as xRecovery package?
Or point me where to read about compiling for arm, where to get tools and so on...
Karlson2k said:
Yes, it's really problem.
Higher frequency - higher power consumption. Moreover - with higher frequency CPU used with higher voltage so consumption is even more higher. So at 998 MHz CPU eats about 5 times more battery than on 246MHz.
With properly tuned governor I don't feel any real lags or slowdowns.
And, when screen is on CPU load is usually is lower than 20% at full frequency. So I don't want to waste my battery.
Click to expand...
Click to collapse
The thing is, on 245 MHz, you can't get any kind of decent performance.
Try this: set the minimum and maximum CPU frequency with SetCPU to 245 and attempt to use the phone normally.
Also, you might be right about voltage, but if the CPU is forced to work on lower freqs when it actually needs higher, there's definitely stress and increased battery consumption.
My phone lasts for more than 24 hours and it's always at max frequency when the screen is on. No lag, no freezes, no drain.
I do agree that the ondemand governor might not function as expected but I fail to experience the actual problem. That might be just me though.
Xperia X10i via Tapatalk
My_Immortal said:
The thing is, on 245 MHz with high load, you can't get any kind of decent performance.
Try this: set the minimum and maximum CPU frequency with SetCPU to 245 and attempt to use the phone normally.
Also, you might be right about voltage, but if the CPU is forced to work on lower freqs when it actually needs higher, there's definitely stress and increased battery consumption.
My phone lasts for more than 24 hours and it's always at max frequency when the screen is on. No lag, no freezes, no drain.
I do agree that the ondemand governor might not function as expected but I fail to experience the actual problem. That might be just me though.
Click to expand...
Click to collapse
There is no need to work on 245MHz as proper governor rise frequency automatically when it's necessary.
And really no stress for CPU to work an low frequency at full load. Moreover - CPU will consume more power at 500Mhz with 45% load than at 250Mhz with 95% load.
Sometime I use phone for navigation - long time with screen on and very low load. In this scenario battery drains very fast.
And last one - I like to have everything working properly. In case that I'll really need high frequency all the time I'll use other governor. I just want to have a choice.
I need a simple solotion for this too..I use z kernel and I found that Thego2s kernel fixed this problem..I was going to flash that kernel but think that has a bug and stoucks on logo ..can some one sayas a simple way?
Yes, I think a lot of people would prefer to use just small and simple fixes rather than replacing the whole kernel with a lot of nice but (personally) unnecessary features.
I am waiting for developers to release a fix for this problam
I'm using the Oxygen ROM on an HTC Desire HD. When I leave my phone alone for a while and come back to unlock it, performance is often slow for 20 seconds to the point where swiping between launcher screens is sluggish. After this time it goes right back up to normal speeds.
Is this possibly related to the CPU settings in my ROM? The settings are available governors - interactive, min CPU - 245MHz, max CPU 1024 MHz. My guess is that when the phone's idle it goes down to 245MHz and takes a while to get back up to regular speeds. Am I looking in the right place and how much would increasing min CPU frequency affect my battery life?
Thanks
It relly shouldn't affect battery life that much. You could try raising the Min speed to the 300's.
As I noticed, when I change governor in setcpu to anything except hotplug the system information states that: We have only one core! WHAT? WHY?
I know, it can be a delay between measures, and some of the governors are reducing freq and so on. I know how could that work. Hot plug can disable the second core, and when i measured MFLOPS with linpack (gov: performance) that clearly shows same score with multithread maybe a bit less than single thread. I had only one active core... Something not clear sometimes. I repeated the tests with every governor and I don't have any idea whats wrong with them, sometimes the second is just out of usage, sometimes working well.
Sorry if that not enough clear.
Anybody else can check that?
I just benchmarked with linpack and also get about the same scores for multi and single-Thread performance. That is indeed very strange. I tried changing back to hotplug but still got the same score for multi and single-Thread performance.
edit:
I removed "set on boot" in SetCPU and rebooted, THAN i got dual core performance again with a score of about 55 MFLOPS. I replaced SetCPU with no-frills CPU control, changing back to hotplug allways seem to work there instantly. Hotplug makes the device freeze randomly and anything else makes it half as fast. I'm beginning to dislike my Archos Tab...
Just finally got around to rooting my USA SGP 5.0 yesterday and download SetCPU 2.24. I set the max clock to 400MHz but noticed that it would periodically jump up to 800MHz. Am I to conclude that it is not properly setting the max speed? ie. not doing anything at all?
thanks!
No, this is normal for this device. When you touch the screen, the driver or the kernel increase the speed to 800MHz, but when you let it go, it will jump back to whatever you set in SetCPU. The driver or kernel overwrites the settings, this is done by Samsung to increase the responsiveness of the device. There's nothing you can do about it.
Interesting... So I want to be able to set a profile so that when the screen is off, the max speed is 200MHz. I am assuming that listening to music does not require the CPU to be clocked at max speed. That said, do we know if the CPU automatically clocks down when not needed? If it does, then does that mean that SetCPU is doing nothing to help with battery life?
I don't know how well the CPU clocks down when not needed. Run some tests with and without caping the CPU and see what SetCPU shows you in terms of clock speed. I have SetCPU on my device because i like to set exact limits to my CPU and not rely on some algorithms to figure it out.
It seems to work whenever I switch the governer to ondemand. Conservative, not so often.
Sent from my YP-G70 using xda app-developers app
If you can buy tegrac overclock..you can undervolt any FQ and overclock how many you want.
Sent from my Nexus 7 using xda app-developers app
Nevermind... I just uninstalled SetCPU. I had set it to max out at 400MHz. I surfed the web for a while and then watched youtube for 1.5 hours and noticed that I dropped from 70% to 45% battery life. I've never seen my battery drain so fast, even when watching full movies. I might give Tegrak a try but I think I'm done with SetCPU for now...