Related
i heard/read about it in my SGS2's time... It was implemented by Gokhan in his kernel but later stripped out because of some problems. PegasusQ is said to be made to handle Quad-core like our One-X, and SGSIII is said to be using this governor by default... Will we be able to see this governor in future Kernel build? or its not compatible technically with Tegra-3 since its a 4+1 setup? Can someone with the knowing enlighten us?
it seems that no one is interested with this
The latest Siyah kernel for SGS2 actually uses pegasusq by default.
jaytana said:
it seems that no one is interested with this
Click to expand...
Click to collapse
Murag wala gyud intresado.which is better for sgsII in terms of battery life?this governor or the hotplug?
I'm afraid I can't help with this, sorry, I do have a Question however.
I've seen people talking about Governors etc, is that something to do with the Chips in the Tegra 3?
The-Last-Hylian said:
I'm afraid I can't help with this, sorry, I do have a Question however.
I've seen people talking about Governors etc, is that something to do with the Chips in the Tegra 3?
Click to expand...
Click to collapse
A governor changes when the CPU changes frequency. More time spent at lower frequencies will, of course, mean better battery life - but lower performance. The trick is to find one you like.
Read this: http://forum.xda-developers.com/showthread.php?t=1369817
It is missing a few governors I've seen (such as PegasusQ) but is fairly complete.
Check this post Pegasusq Governor
Hi guys,
I'm new to android and I just flash a cook rom with custom kernel to my phone.
I use Kernel Tweaker to set some variable to make it use less battery and smoothly but I see an option called Intelli-plug.
I google this and see it complete replacement for MP-decision.
So what is best of them for battery life and performance at cook rom?
(I think MP-decision is best for Stock rom, correct me if I am wrong )
Intelliplug is a replacement for mp decision implemented by faux123 if im not wrong . It determines the behaviour of the cpu and gpu. Stock nexus and OG only have mp decision. Intelliplug is a better option
Sent from my Nexus 4 using XDA Premium HD app
mp-decision is better.
The only thing the Intelliplug do is causing lags, freezes and other annoying strange things.
imho.
There's also msm_mpdecision (not to be confused with the mpdecision binary) by showp1984, which is pretty good. It has input boost and is the smoothest I've tried. I'd give that a shot depending on what kernel you're running. In trickster, it'll be a menu in specific called MSM-MPDECISION control (or something like that). CPUQuiet is supposed to be good as well, but I haven't personally run it. Auto_hotplug and mako_hotplug in faux and matr1x are typically better for battery than others, but are not quite as smooth.
xboxfanj said:
There's also msm_mpdecision (not to be confused with the mpdecision binary) by showp1984, which is pretty good. It has input boost and is the smoothest I've tried. I'd give that a shot depending on what kernel you're running. In trickster, it'll be a menu in specific called MSM-MPDECISION control (or something like that). CPUQuiet is supposed to be good as well, but I haven't personally run it. Auto_hotplug and mako_hotplug in faux and matr1x are typically better for battery than others, but are not quite as smooth.
Click to expand...
Click to collapse
I wanted to know wat type of decision is used in Nexus4 and 5....coz wen i compare OG nd MAKO using perfmon app i can able to find the difference.... And it looks lyk mako one ia bettr than ours...!!... Am i ryt...
Sent from my LG-E975 powering Stock 4.1.2
hasan4791 said:
I wanted to know wat type of decision is used in Nexus4 and 5....coz wen i compare OG nd MAKO using perfmon app i can able to find the difference.... And it looks lyk mako one ia bettr than ours...!!... Am i ryt...
Sent from my LG-E975 powering Stock 4.1.2
Click to expand...
Click to collapse
If you are comparing stock vs N4, yes, they are different; stock should actually be a bit better since Qualcomm doesn't include certain things on Nexus devices. On CM, the mpdecision binary used I believe is from N4 4.2.
Tim4 said:
mp-decision is better.
The only thing the Intelliplug do is causing lags, freezes and other annoying strange things.
imho.
Click to expand...
Click to collapse
Any evidence / proof of this "claim"?
Destroyedbeauty said:
Any evidence / proof of this "claim"?
Click to expand...
Click to collapse
Well he wrote "In my honest opinion" so i dont think any proof is needed
Sendt fra min LG-E975 med Tapatalk
Liindberg said:
Well he wrote "In my honest opinion" so i dont think any proof is needed
Sendt fra min LG-E975 med Tapatalk
Click to expand...
Click to collapse
I don't see anything that is making Qualcomm MP-Decision better than Faux123 custom Intelliplug driver His hotplug driver is everything that MP-Decision is lacking of + more battery friendly and less heat generating..
MPDecision is much more aggressive in terms of changing CPU frequency (automatically goes to 1026 when input is detected). IntelliPlug is more for battery than performance. For performance, I suggest MSM-MPDecision from showp1984 (it's on most of my kernels and a couple others), which performs similarly to the mpdecision binary in terms of boosting frequencies and raw performance, but is customizable. You can change the frequency for input boost or turn it off altogether. There's a bunch of different settings you can play around with.
CPUQuiet also is one of the better performing hotplug drivers. I don't know quite as much about how it works, but it was made by NVidia and ported to Snapdragon by maxwen and has a set of governors which keep the CPU running at optimal frequencies for battery and performance.
In my opinion Intelliplug is extremely finicky and unpredictable. I get much better battery life with mpdecision.
I am a little newbie on this, so may i ask a question?
How can i install MP-decision?
Is it built-in on a kernel or do i have to download it seperately?
any body can completely explain what relay MP-decision and Intelliplug do? or any body know where I can read complete documentation of those?
smart8bits said:
any body can completely explain what relay MP-decision and Intelliplug do? or any body know where I can read complete documentation of those?
Click to expand...
Click to collapse
Google is your friend
http://androidmodguide.blogspot.ca/p/blog-page.html
MPdecision
Guys,
In my humble opinion what i have noticed is - when you enable a mpdecision i.e.on in the cpu, based on your cpu gov settings say for performance - one core of your cpu will always be at 100% and based on the activities it will switch on or off, the other cores.
When your cpu gov settings are interactively managed, again one of your core will be working and based on the certain % say 79 or 80,it will switch on the other cores.
If you deactivate mpdecision then almost all your cores will be active at any given time. But may not run as high as in enabled state.
So if you are one of those who cares about your cpu heating and don't use cpu tuners or sleepers. Set it off.
If you are into gaming and very smooth ui experience and doesn't bother about battery drain, switch it on.
I have enabled the settings and use custimized task scripts to reduce the frequency of the core as soon as i switch off the screen.
[email protected] said:
So if you are one of those who cares about your cpu heating and don't use cpu tuners or sleepers. Set it off.
If you are into gaming and very smooth ui experience and doesn't bother about battery drain, switch it on.
Click to expand...
Click to collapse
based on what you said on the rest of the post, shouldnt it be the opposite?
Hi, I need some info from all the Project T users out there (both phone models).
As I made some tests I discovered that the OC code in ZE551ML doesn't seem to work consistently (or not at all according to some users).
I know that UC works, but depending on your feedback I will just continue with one UC'ed build or keep the normal and the OC/UC build
So here my Poll question:
Who has real performance improvements with the OC code?
1) ZE551ML and OC does work
2) ZE551ML and OC doesn't work at all
3) ZE550ML and OC does work
4) ZE550ML and OC doesn't work at all
Thanks!
I can see the phone running at 2000mhz in the freq table... But no much performance boost...
550ml
It doesn't improve performance but yes showing 2ghz in 1.8ghz..
And as I said I can test any build which have 1.8ghz to 2.3ghz if you want and zenfone zoom is going to have 2.5ghz, gpu @640mhz, if they released source, try to implement what they did in that, becoz basically all are same hardware with different clock,. .
It shows 2.5GHz, but geekbench score is not higher than using 2.33GHz. The score for 2.5GHz is even a little bit lower. Tested with performance governor.
Yeah, I feared that...let's see what this poll says, then I can decide if I at least keep the underclocking and keep only the UC version
Intel processors are probably well locked. If tdp throttling is an issue, that can be worked with, but playing with the multiplier is probably out. If anything building a kernel with support for implausibly high frequencies could be a good test. If the phone "works" at 4ghz....
Sent from my ASUS_Z00A using Tapatalk
As I sayed in the Kernel-Thread, all my testing makes clear, that on my phone OC doesn't really work. I see the higher clock used in CPU Spy / Kernel Adiutor but there is no performanceimprovement (551ML).
Thank you for your work. And maybe, there is a solution to unlock the SoC.
I recently rooted and installed a custom Rom and ElementalEx Kernel. I noticed that the default profiler for the Pixel XL is something called sched which appears to be a fairly conservative governor. I changed it to interactive which I normally use on other phones and battery life suffered considerably. I switched it back to sched and cpu frequencies are much lower but I don't notice any drop in performance. I tried researching sched but haven't found much. Anyone know how this governor works?
Sched is the most efficient governor for our pixel.
The real question is why do you want to change the governor? If you really want some things to mess with to increase battery and/or performance then check out "L speed (boost&battery)" in the play store. And No, this isn't shameless advertising either, the dev is right here in our forums.
noidea24 said:
Sched is the most efficient governor for our pixel.
The real question is why do you want to change the governor? If you really want some things to mess with to increase battery and/or performance then check out "L speed (boost&battery)" in the play store. And No, this isn't shameless advertising either, the dev is right here in our forums.
Click to expand...
Click to collapse
It was a reflex reaction because I'm used to using Interactive and the CPU frequencies seemed really low compared with what I would see on the 6P. Those frequencies on the 6P would result in a noticable performance lag. But I guess the phone design is really different so you can't compare them that way. I'll check out L Speed. Never heard of it. Thanks.
jhs39 said:
It was a reflex reaction because I'm used to using Interactive and the CPU frequencies seemed really low compared with what I would see on the 6P. Those frequencies on the 6P would result in a noticable performance lag. But I guess the phone design is really different so you can't compare them that way. I'll check out L Speed. Never heard of it. Thanks.
Click to expand...
Click to collapse
Same. Coming from the 6p / 5x scene. The best governor was interactive, especially due to all the tweaks and changes that could be applied to the governor (like on ElementalX).
But no, pixel is almost dedicated to sched. I honestly don't think anyone else is running anything else and getting decent results from it
Pixel/XL Uses EAS so governors like Sched, Schedutil etc etc. Meanwhile every other Android device uses HMP your regular governors like Interactive, Ondemand, performance, conservative etc
So it's recommended to use Sched as the defualt but you can learn more about EAS here Also Freak07 has some great info on EAS and it's govenors here
jhs39 said:
It was a reflex reaction because I'm used to using Interactive and the CPU frequencies seemed really low compared with what I would see on the 6P. Those frequencies on the 6P would result in a noticable performance lag. But I guess the phone design is really different so you can't compare them that way. I'll check out L Speed. Never heard of it. Thanks.
Click to expand...
Click to collapse
Same. Coming from the 6p / 5x scene. The best governor was interactive, especially due to all the tweaks and changes that could be applied to the governor (like on ElementalX).
But no, pixel is almost dedicated to sched. I honestly don't think anyone else is running anything else and getting decent results from it
noidea24 said:
Same. Coming from the 6p / 5x scene. The best governor was interactive, especially due to all the tweaks and changes that could be applied to the governor (like on ElementalX).
But no, pixel is almost dedicated to sched. I honestly don't think anyone else is running anything else and getting decent results from it
Click to expand...
Click to collapse
All kinds of us are running schedutil gov on custom kernels. It's the next iteration of EAS sched gov. Better performance than sched.
Yeah same here, I would always use L Speed or some different governor on previous phones than default, cause default was always not the most efficient, both performance and battery backup wise, but on Pixel there is no need. In fact devs have suggested us to use the default Sched governor, so I am sticking with it.
Anyone on ElementalEx change any settings other than the governor to improve performance on the Pixel XL? A lot of the available settings are different than I'm used to.
Hi, everyone I'm s7edge owner would like to use a the Google pixel governor, can someone show me the direction please? Thanks
lovetv said:
Hi, everyone I'm s7edge owner would like to use a the Google pixel governor, can someone show me the direction please? Thanks
Click to expand...
Click to collapse
Not possible without an EAS compatible ROM/Kernel
ithehappy said:
Yeah same here, I would always use L Speed or some different governor on previous phones than default, cause default was always not the most efficient, both performance and battery backup wise, but on Pixel there is no need. In fact devs have suggested us to use the default Sched governor, so I am sticking with it.
Click to expand...
Click to collapse
I think the devs suggest using the sched governor because they are either too lazy or not knowledgeable enough to create other governors that are compatible with the Pixel. The sched governor is far from efficient. It's clearly a performance based governor and it allows the Pixel battery and CPU to get very hot very quickly. The Pixel CPU can get to 130F just performing what most people would consider standard tasks on their phones. I'm not even talking about gaming or anything remotely CPU intensive. How long do you think these phones are actually going to last when they heat up so much?
What's the difference between sched and schedutil? I saw schedutil is default on the ElementalX for !y Pixel 2 XL.
Which kernel is best for performance?(for Whyred)
1. Black box
2.no name
And many out there???
Suggestions please.
Thanks in advance.
Deep.cdy said:
Which kernel is best for performance?(for Whyred)
1. Black box
2.no name
And many out there???
Suggestions please.
Thanks in advance.
Click to expand...
Click to collapse
You should try them and find out the most suitable for you, use them for 1-2 days, you'll see the difference.... personally, I'm using NoName kernel with RR
NoName for Lineage based.
Deep.cdy said:
Which kernel is best for performance?(for Whyred)
1. Black box
2.no name
And many out there???
Suggestions please.
Thanks in advance.
Click to expand...
Click to collapse
i think currently is noname.
we hope a bunch of recognised developers in the near future as franco as many others.
Kirks, for battery...
Dude unlocked the lower cpu freqs...
m666p said:
Kirks, for battery...
Dude unlocked the lower cpu freqs...
Click to expand...
Click to collapse
It operates on lower Volts using this unlocked freqs?
peter-k said:
It operates on lower Volts using this unlocked freqs?
Click to expand...
Click to collapse
God knows, but what I do know is that it should produce less heat at the very least and it performs pretty gud on powersave governor. The gpu on the other hand is garbage at min freq (160mhz), even the launcher lags....
peter-k said:
NoName for Lineage based.
Click to expand...
Click to collapse
But after flashing no name 1.3 the WiFi doesn't work for me on rr 12th June
Deep.cdy said:
But after flashing no name 1.3 the WiFi doesn't work for me on rr 12th June
Click to expand...
Click to collapse
Mine was fine but now I'm on Aosip.
i think for now the best is to use a stock kernel, be careful with the charging limits.
peter-k said:
It operates on lower Volts using this unlocked freqs?
Click to expand...
Click to collapse
m666p said:
God knows, but what I do know is that it should produce less heat at the very least and it performs pretty gud on powersave governor. The gpu on the other hand is garbage at min freq (160mhz), even the launcher lags....
Click to expand...
Click to collapse
Of course it operates at lower voltage as it's a lower frequency and requires less power draw. Lower voltages should mean lower heat, however you don't magically get that lower freqs to operate, you need to tweak the interactive governor to make use of them all efficiently. So far I'm on Kirks kernel and AOSiP and it's a quite good combo.
The lag is not caused by low GPU freqs, it's because of low CPU freqs for that particular load, so governor tweaking is needed.
Cirra92 said:
Of course it operates at lower voltage as it's a lower frequency and requires less power draw. Lower voltages should mean lower heat, however you don't magically get that lower freqs to operate, you need to tweak the interactive governor to make use of them all efficiently. So far I'm on Kirks kernel and AOSiP and it's a quite good combo.
The lag is not caused by low GPU freqs, it's because of low CPU freqs for that particular load, so governor tweaking is needed.
Click to expand...
Click to collapse
Lol, I tested what you said out. Because you said it with such confidence...
I changed the cpu governor to performance and set the gpu to 160mhz max...
That made the experience a bit better but it would still lag a lot in recents and app launcher scrolling...
I've attached a screen shot to prove it too...
Another thing, just because the clock is lower does not mean that the voltage is lower as well, many devices that ive owned over the years have had the same voltage's for lower clocks( moto g2, Sony xperia z1)
And lastly, you should "magically" get those lower frequencies(if they are truly unlocked) since governors will always operate within the min/max frequencies that are set by the user or by default(unless it reverts parameters back to stock, like our device does on interactive)...
Forgot screenshot....
m666p said:
Lol, I tested what you said out. Because you said it with such confidence...
I changed the cpu governor to performance and set the gpu to 160mhz max...
That made the experience a bit better but it would still lag a lot in recents and app launcher scrolling...
I've attached a screen shot to prove it too...
Another thing, just because the clock is lower does not mean that the voltage is lower as well, many devices that ive owned over the years have had the same voltage's for lower clocks( moto g2, Sony xperia z1)
And lastly, you should "magically" get those lower frequencies(if they are truly unlocked) since governors will always operate within the min/max frequencies that are set by the user or by default(unless it reverts parameters back to stock, like our device does on interactive)...
Click to expand...
Click to collapse
First of all, we are talking here about difference in voltage between stock minimum freq for big cluster, which is 1.1ghz and actual possible minimum which is 300mhz, and there is a difference in voltage, that was the point. The devices I owned, S5 and Z3compact had more CPU steps, therefore the difference between some of the steps was really small or there wasn't any, but the CPU scaling made a jump to the freq with bigger difference (higher or lower, that was the stock behavior so some freqs weren't used). Here it might use all of the freq steps as there are less of them and the difference in voltage is significant enough, which might be the case, I said that because of my experience with previous devices. But you've missed the point anyway, I have said that even if unlocked, some freqs won't be used just because they are there if the governor parameters aren't set properly (or will be barely used). That was my point, I said that as a general note, so users won't jump the gun and blame devs for whatever.
And another one, regarding your test and lag with GPU, now I'm confused why would you set your max at 160mhz? I know it was for testing purposes in this case, but you did complain about it in original post and I said it won't lag because the max would still be set to 430mhz in which case the GPU freq scaling would do the job which it does very good so far. It would lag of course if you set max GPU freq to 160, but that's not what would you do for daily usage, right? Sorry if I misunderstood something.
Cirra92 said:
First of all, we are talking here about difference in voltage between stock minimum freq for big cluster, which is 1.1ghz and actual possible minimum which is 300mhz, and there is a difference in voltage, that was the point. The devices I owned, S5 and Z3compact had more CPU steps, therefore the difference between some of the steps was really small or there wasn't any, but the CPU scaling made a jump to the freq with bigger difference (higher or lower, that was the stock behavior so some freqs weren't used). Here it might use all of the freq steps as there are less of them and the difference in voltage is significant enough, which might be the case, I said that because of my experience with previous devices. But you've missed the point anyway, I have said that even if unlocked, some freqs won't be used just because they are there if the governor parameters aren't set properly (or will be barely used). That was my point, I said that as a general note, so users won't jump the gun and blame devs for whatever.
And another one, regarding your test and lag with GPU, now I'm confused why would you set your max at 160mhz? I know it was for testing purposes in this case, but you did complain about it in original post and I said it won't lag because the max would still be set to 430mhz in which case the GPU freq scaling would do the job which it does very good so far. It would lag of course if you set max GPU freq to 160, but that's not what would you do for daily usage, right? Sorry if I misunderstood something.
Click to expand...
Click to collapse
I kinda get what you mean, but the min freqs should kick in by default. They don't though on kirks, you need to change the governor to something like alucard or zzmove once before it actually starts clocking down to 300mhz...
On a side I would just disable the big. Cluster if I could, I don't really need that much cpu performance...
I was trying to find the min gpu freq that would be usable and I was disappointed, cuz my Sony z1 had a smooth ui experience with the gpu clocked at 200mhz max and that thing had a sd800...
Btw, I do all this to get better battery life...
I found out something else, I can't use power save governor any more because it can't handle audio processing(ainur, v4a) when the screen is off...
Just like my old z1, Lol...
Makes me think that the performance is really identical to the snapdragon 800...
I wonder how pissed I would be if a I got the redmi 5 plus, the 625 would have been even worse...
m666p said:
I kinda get what you mean, but the min freqs should kick in by default. They don't though on kirks, you need to change the governor to something like alucard or zzmove once before it actually starts clocking down to 300mhz...
On a side I would just disable the big. Cluster if I could, I don't really need that much cpu performance...
I was trying to find the min gpu freq that would be usable and I was disappointed, cuz my Sony z1 had a smooth ui experience with the gpu clocked at 200mhz max and that thing had a sd800...
Btw, I do all this to get better battery life...
Click to expand...
Click to collapse
m666p said:
I found out something else, I can't use power save governor any more because it can't handle audio processing(ainur, v4a) when the screen is off...
Just like my old z1, Lol...
Makes me think that the performance is really identical to the snapdragon 800...
I wonder how pissed I would be if a I got the redmi 5 plus, the 625 would have been even worse...
Click to expand...
Click to collapse
Yeah I agree, it should, but how much it stays on minimum freq is dependent on couple of governor parameters (talking about interactive). On mine though it does stay on 300mhz when idling, on stock Kirks settings. Big cluster can be disabled through new hotplug solution, like Intelliplug, which I used on my old devices, and it performed great, 1 core was active when screen was off, screen on and light usage required only 2 cores, while all 4 were active under heavy load. Here however there is only Qualcomm's hotplug solution, until that changes, no luck. Regarding GPU freq, I don't think any device would work smoothly under 200mhz, you can set 266mhz here, it will be smooth, I've tested today, on my old SD801 it performed at 233mhz IIRC.
I've seen that, V4A requires higher freq than 300mhz, or even 422mhz which SD801 had, it's more about the freq rather than the chipset, as I've read on multiple threads that even the devices with SD820 were struggling a lot when processing audio at 300mhz when the screen was off. Don't worry, it's a general issue. There is also the optimization of the rom and audio mods as well, background tasks, kernel, it all goes into the mix.
This is actually a very good chipset, it's technically SD660 just with lower clocks on both CPU and GPU.
EDIT: I forgot, this is my usage on AOSiP + Kirks, stock interactive tunables, min freq 300mhz (big/little), GPU initial/min freq 160mhz, max 430mhz. Using microG instead off GApps, I have used FB, Instagram, Messenger app for 1,5h each, Viber was couple of hours, Chrome some 30mins, Panini sticker album 30+ minutes, 30 minutes of 2G calls. Network mode was LTE, though I was on wifi on whole charge.
Started measuring from 92%.
Thanks bro, that explains a lot...