I'm running fauxs kernel, and in his op it says for battery life to turn mpdecision off. When I leave it on only the first 2 cores run and idle at 384mhz, but when I turn it off all 4 cores are running constantly, and the 3 & 4 core idle at 702 mhz. Maybe I'm missing something, but how can turning mpdecision off be better on battery when you have all 4 cores running constantly instead of 2?
Sent from my Nexus 4 using xda app-developers app
Sounds like you're running his enhanced stock kernel, the recommended settings only apply to faux kernel
Michealtbh said:
Sounds like you're running his enhanced stock kernel, the recommended settings only apply to faux kernel
Click to expand...
Click to collapse
No, I'm using the 008 mainline
mpdecision kicks in when you touch the screen it ramps the min cpu speed to 1026 so it uses more battery but increase responsivness
DynamicRam said:
mpdecision kicks in when you touch the screen it ramps the min cpu speed to 1026 so it uses more battery but increase responsivness
Click to expand...
Click to collapse
See, that I knew already, and it does make sense. But when I turned mpdecision off, it was doing the exact same thing, but instead of only having the first two cores online, it had all 4 cores online constantly with the last 2 at 702mhz. From what I read, people are saying turning mpdecision off is better for battery but I just don't understand how it could be with 4 cores running constantly instead of 2, unless I'm doing something wrong (which I probably am lol)
Sent from my Nexus 4 using xda app-developers app
Related
So I was trying to mess around with CPU profiles and I noticed that the low end of the CPU is clocked at 1GHz. If I lower it with Rom Toolbox, it just goes right back up after I leave the menu. the profiles won't stick, governors don't make a difference, and I'm a little confused.
Can someone shed some light on this for me?
I thought the lowest speed was 384 MHz? Install CPU Spy and check what it says.
It is 384MHz. The lower frequency change because of project butter that make the cpu run at a higher frequency when you touch the screen.
Sent from my Nexus 4 using xda app-developers app
Dont you need a custom kernal in order to change the clock speeds?
sent via xda premium with nexus 7
No, we can already change it but it won't stick since it has its own frequency management.
Sent from my Nexus 4 using xda app-developers app
Is this somewhat similar to perflocker in HTC devices? It had to be disabled to change any cpu settings AT ALL with the stock kernel.
hervelo said:
No, we can already change it but it won't stick since it has its own frequency management.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
That is why..
sent via xda premium with nexus 7
ed10000 said:
I thought the lowest speed was 384 MHz? Install CPU Spy and check what it says.
Click to expand...
Click to collapse
You're right. I guess it just has its own profile to set at 1GHz when the screen is on, because the CPU Spy showed it in Deep Sleep/384Mhz for the majority of the night.
test1
Is it ok for me to have a task in Tasker that changes the governor everytime the phone sleeps and wakes? Is that harmful to my device?
not sure about if it's dangerous or not but I am curious a to why you would want to... sleep is sleep not much of anything happening to warrant a change
Sent from my Nexus 4 using xda premium
QUIETLYloud said:
not sure about if it's dangerous or not but I am curious a to why you would want to... sleep is sleep not much of anything happening to warrant a change
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well, I've found that my battery lasts a lot longer when the powersave governor is on, even while in sleep. When the screen is on I have it change to ondemand so i get a nice smooth UI. When in sleep with ondemand on, it drains faster than when I have powersave on and have it clocked to 288000 MHz.
Brendan12695 said:
Well, I've found that my battery lasts a lot longer when the powersave governor is on, even while in sleep. When the screen is on I have it change to ondemand so i get a nice smooth UI. When in sleep with ondemand on, it drains faster than when I have powersave on and have it clocked to 288000 MHz.
Click to expand...
Click to collapse
You have it clocked at 28.8 GHz? Pretty sure you're going to melt your phone. (I kid)
I believe he meant 288 GHz. He's from the future and is trolling us.
Sent from my Nexus 4 using xda premium
Branden pls
Sent from my Nexus 4 using xda app-developers app
Totally fine, but you might encounter stability problems.
Lol. My bad, was just copying what Trickster Mod said.. :/ I have the min at 288 MHz so when power save is on it underclocks to that.
I just don't want to screw up the hardware by jumping back and forth between ondemand and powersave.
Sent from my Nexus 4 using Tapatalk 2
Try out this Tasker script : http://forum.xda-developers.com/showthread.php?t=1018245
OK when I run CyanogenMod and change performance. It always goes back to the original setting. And 1 more question why is the min CPU frequency at 1026
Sent from my Nexus 4 using xda app-developers app
Try applying "set on boot"
mattoaida said:
OK when I run CyanogenMod and change performance. It always goes back to the original setting. And 1 more question why is the min CPU frequency at 1026
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure about the settings not sticking, but I can explain the min frequency thing. If you're running the stock CM kernel, or a kernel that uses MPDecision, upon touching the screen, it locks the minimum frequency to 1ghz for about one second to aid project butter. This allows for smoother transitions and faster loading, as events such as animations and applications opening usually occur as a result of you poking something on the screen
Connor Baker
Connor Baker said:
I'm not sure about the settings not sticking, but I can explain the min frequency thing. If you're running the stock CM kernel, or a kernel that uses MPDecision, upon touching the screen, it locks the minimum frequency to 1ghz for about one second to aid project butter. This allows for smoother transitions and faster loading, as events such as animations and applications opening usually occur as a result of you poking something on the screen
Connor Baker
Click to expand...
Click to collapse
OK but does this drain a lot of battery
Sent from my Nexus 4 using xda app-developers app
Ive been getting smoother results underclocking the G2 at either 1.7 or 1.9 and knock on seems more quick to response, but when I tried video recording the 60 fps isn't smooth when you are clocked at the regular speed.. beware...I ran a benchmark on quadrant standard and got 17,250 constantly so it is underclocked per core... I want to hear your opinion on this and do you plan to underclock or already are. I feel like the ability to be more smooth within the UI helps a lot more now..let me know your thoughts!
bencozzy said:
From using trickster mod and setcpu to underclock they only underclock cpu0 the other three still use the full frequency range.
What app are you using?
Click to expand...
Click to collapse
No frills CPU control :0
At 1.9 my Antutu was the same add the One and oddly the graphics test dropped 15-20 frames even though we are not under clocking the GPU.
Sent from my VS980 4G using XDA Premium 4 mobile app
That's really odd tbh o.o did you try quadrent as well? :0
jrgilbert79 said:
At 1.9 my Antutu was the same add the One and oddly the graphics test dropped 15-20 frames even though we are not under clocking the GPU.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I got way higher even at 1.7ghz :0
jrgilbert79 said:
At 1.9 my Antutu was the same add the One and oddly the graphics test dropped 15-20 frames even though we are not under clocking the GPU.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
HeXaLox said:
I got way higher even at 1.7ghz :0
Click to expand...
Click to collapse
You're saying that by underclocking, you're getting a smoother UI but lower benchmarks?
No i got a higher benchmark than the guy who replied on my post. I did get a smoother UI and everything is less laggy. Ill post a pic of 2.3ghz idk if its actually at 1.7ghz or 2.3ghz ill do another test
whittikins said:
You're saying that by underclocking, you're getting a smoother UI but lower benchmarks?
Click to expand...
Click to collapse
All this is true. Just tried. It might be a TINY bit slower ui THOUGH
Sent from my LG-D800 using Tapatalk 4
What settings did toy use? Deadline? Noop? Interactive gov?
Sent from my VS980 4G using XDA Premium 4 mobile app
I am using the app called No-frills CPU Control and for 1.7ghz I am using row and Ondemand as the I/O governor and same settings for the regular clock as well..
jrgilbert79 said:
What settings did toy use? Deadline? Noop? Interactive gov?
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Underclocked at 1.7ghz first then regular clock at 2.27ghz
jrgilbert79 said:
What settings did toy use? Deadline? Noop? Interactive gov?
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am tending to believe that the regular clock speed is actually overclocked...just like how the galaxy s4 is overclocked 200mhz more than normal...however I could be wrong..
If you really want to see if this odd issue is actually happening download an app called Multicore CPU Control (the only app of its kind that seems to work with the LG G2). I use this to save battery by turning off all but one core, but it allows you full control over all your cores.
Download it, create a profile, and set each core to what you want. I had to save the profile first, then go back in to edit the latter 3 cores' frequencies.
I would suggest setting the min and max to the same and choosing Performance for the governor. Use a different app to set the scheduler.
Be sure to have something like Kernel Tuner to ensure that all your cores are running as you intended. If not, go back into Multicore CPU Control and re-save your profile again.
Would love to hear the results afterwards!
I used Multicore CPU Control.
The only way to set clock to CPU 1,2,3 is let them always active. If I leave dynamic for these cores, they still go up to 2,26 GHZ. I think this the reason why HeXaLox have a little decrement when underclock because it only did for one core.
So I have a very thought out question now I have a 4 core phone right? Well my battery life is below average and I was wondering if I had all my cores running at once would it balance out battery life? I just need some help from someone who knows about all this and are all cores mandatory?
Sent From My Liberated E970
You can select how many active cores are activated with trickster mod and (necessary!) a kernel that supports this.
Sent from my Nexus 7 using Tapatalk 4
I know how to and can with my kernel but I need to know if more cores are activated if the battery life will be better or worse
Sent from my Optimus G using XDA Premium HD app
I would definitely take a look in to what my batter usage is and how to control that before I worry about the cores. Just my two cents.
P.S. I am sorry but I believe the Multi-core in the title is spelled wrong.
mr turtle droid said:
I know how to and can with my kernel but I need to know if more cores are activated if the battery life will be better or worse
Sent from my Optimus G using XDA Premium HD app
Click to expand...
Click to collapse
More cores active would mean more processing power, and more processing power requires more energy(atleast on the same cpu), so disabling most of your cores would result in better battery life, maybe by a little bit though.
Hahaha I didn't realize it said mulit
Sent from my Optimus G using XDA Premium HD app
useful topic
It seems to me that by disabling cores wont make a difference to your battery life, only to your performance. It doesn't matter if 2 cores work for 5 seconds or 1 core works for 10 seconds, it is practically the same power consumption
Play around
I would say download CPU-Z from the Play Store and look how much Cores are active and which clock they're at.
Then flash a custom Kernel, which lets you control the clock, govenor and how much cores are active, undervolting may increase your battery life too.
Play with the settings (PLEASE DO NOT RAMP UP THE CLOCKS or set the voltage to the lowest point you can, it may break your phone, stay reasonable, it's not my fault if your phone bricks) and look what's best for you.
Pro Tip: Take a look at the different govenors and look what they do. Google them!
Greetz Leevee33
I hope I could help you a little
Im using trickster mod and I know about all of this I studied up and have undervolted by 200 MV stable but I'm using the hotplug settings to 1:2 so not all 4 cores are active and I get almost two days on one charge!so I guess that does mean less cores use less power
Sent from my Optimus G using XDA Premium HD app