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?
Related
This is based on the cyanogenmod kernel, with the main change being the smartass governor has been added and is default.
The zip file is in koush's anykernel format, so it can be flashed just like a rom.
Changes:
Smartass governor by erasmux is default
extra overclock enabled
patch #22 by farmatito
disabled CONFIG_SERIAL_MSM
NO SUPPORT WILL BE GIVEN. ONLY FLASH IF YOU KNOW WHAT YOU ARE DOING. NO ONE IS RESPONSIBLE EXCEPT YOU. BLAH BLAH BLAH.
Newest
2.6.35.14-oc-cm-smartass_g0dd6e8c.zip
source: http://github.com/dumfuq
old versions: http://www.mediafire.com/dumfuq
What does the smartass governor do?
mackster248 said:
What does the smartass governor do?
Click to expand...
Click to collapse
smartass governor - is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works - by taking over the idle loop - is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the "old" minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 - why?! - it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!
i googled it lol, seems like its a bit more responsive then interactive, and it ramps down quickly too. could give some battery savings
What ROM's will this work with?
keeps cpu at/above 768mhz, will not go below until you switch off smartass gov.
liking the "sleep" enhancement, but seems like it should let the processor scale on down to 245 when idle with screen on
I'm running this with CM7 Nightly #16 and it's running really well. I'm getting a little more battery consumption than I do with zinx's kernel, but that could just be because I've only been using the kernel for around 2-3 hours. It may need a little more time to settle? I'm not sure, but it is definitely snappier! If it does scale down the cpu during screen off, you can't tell at all! It doesn't have any lag when unlocking like setting profiles usually does. So I'm really stoked about this kernel! Great work as always Dumfuq! This will be my new kernel for at least a few days to give it more of a chance.
PS: I'm only getting around 29 on linpack at 1.017 GHz, where as with zinx's I was getting 38's. Smartbench scores are at 1320's for productivity and 1869 for gaming. So those both beat out zinx's kernel. Just wanted to put those out there so people have some kind of a comparison point.
posted a v2. The difference is frequencies are changed to match glacier frequencies instead of hero's.
The only noticable difference here is that when the screen is off the frequency scales between 245 and 368 instead of being stuck at 245.
dumfuq said:
posted a v2. The difference is frequencies are changed to match glacier frequencies instead of hero's.
The only noticable difference here is that when the screen is off the frequency scales between 245 and 368 instead of being stuck at 245.
Click to expand...
Click to collapse
Damn. Nice!
Works with evil's MIUI 1.1.26 r2..Hopefully battery life will increase now.
Edit: breaks video playback in miui
sl1k1 said:
Works with evil's MIUI 1.1.26 r2..Hopefully battery life will increase now.
Edit: breaks video playback in miui
Click to expand...
Click to collapse
Smartass is already compiled in.
Sent from my HTC Glacier
I use this on my GF's Mytouch Slide and she gets 20+ hr's on a charge overclocked @ 825. Was so hoping someone would port the kernal to this phone. thx dumfuq ^^
Trying to decide if I want to flash this over the stock cm7 kernel.
Has anyone noticed any gains from doing this? what about compared with the stock cm7 kernel + setCPU?
flashed this over build 16, cm7. I still use setcpu. no problems, everything is smooth like butter. Definitely smoother than it was before. no wake up problems, no play back problems. thanks for this =]
Does wifi calling also work with this? Anyone know?
brian6685 said:
Does wifi calling also work with this? Anyone know?
Click to expand...
Click to collapse
You could always flash it and find out, and if not, just restore the backup you made prior to flashing it. ;] I don't see why it wouldn't it hasn't broken anything for me.
K ill try it out later when I get home from work. Thanks
whats the mhz setting on this by default? not super fond of setcpu. though i do like this idea of a custom throttle and logic. so i figured if the mhz is high enough then i'll give it a shot.
brian6685 said:
K ill try it out later when I get home from work. Thanks
Click to expand...
Click to collapse
let us know what happens
here's my initial test of the v2 as far as battery goes...
looks like wifi calling works ;]
I've had great battery life with this kernel so far.
I have recently rooted my dhd and currently running CM7. Using the cpu setting within the performance menu I am wondering what peoples thoughts are on a noticeable but safe increase of cpu speed. its set as 1017MHz which i believe is default. I am told I can run anything up to 1500 safely. can anyone confirm this and also tell me what kind of result (performance and battery life) i should expect.
thanks
Well, I use Android Revolution HD (a sense rom, meaning heavy UI!) and i overclock to about 1.3GHz. In terms of battery life when it's awake, it seems a drain a teeny bit more readily, but I've never had a freeze on sense (quite rare)
On stock it underclocks to let the processor max at around 400MHz when the screens off, so that helps to really save a lot of battery on standby. On CM, I'd expect it'd feel more or less the same in terms of performance after you hit 1.2/1.3GHz
hmohammed43 said:
Well, I use Android Revolution HD (a sense rom, meaning heavy UI!) and i overclock to about 1.3GHz. In terms of battery life when it's awake, it seems a drain a teeny bit more readily, but I've never had a freeze on sense (quite rare)
On stock it underclocks to let the processor max at around 400MHz when the screens off, so that helps to really save a lot of battery on standby. On CM, I'd expect it'd feel more or less the same in terms of performance after you hit 1.2/1.3GHz
Click to expand...
Click to collapse
thanks for the reply mate. going to try out revolution HD soon i think. have you overclocked using a third party app or is there one built into that rom?
also im a little confused by the governors. 'on demand' is the default governor. Does that mean it will only use the max selected cpu speed when necessary? would you recommend using a difference setting?
cheers
rhodri11 said:
thanks for the reply mate. going to try out revolution HD soon i think. have you overclocked using a third party app or is there one built into that rom?
also im a little confused by the governors. 'on demand' is the default governor. Does that mean it will only use the max selected cpu speed when necessary? would you recommend using a difference setting?
cheers
Click to expand...
Click to collapse
The CPU is managed by the ROM itself. You can tweak it yourself by using setCPU (or similar), but I can advise you not to. Can't help you with the governors buddy, since I dunno what it is
Cheers
darude0306 said:
The CPU is managed by the ROM itself. You can tweak it yourself by using setCPU (or similar), but I can advise you not to. Can't help you with the governors buddy, since I dunno what it is
Cheers
Click to expand...
Click to collapse
nice one dude
I'm running cm7 and I'm overclocked to 1.5 ghz. It's been totally fine for months.
Sent from my Motorola Startac running Atari 2600 software!
rhodri11 said:
thanks for the reply mate. going to try out revolution HD soon i think. have you overclocked using a third party app or is there one built into that rom?
also im a little confused by the governors. 'on demand' is the default governor. Does that mean it will only use the max selected cpu speed when necessary? would you recommend using a difference setting?
cheers
Click to expand...
Click to collapse
Lucky you picked a linuxhead!
The system itself has a daemon (background process built into the system) that handles overclocking. It's all explained on the page and also on this thread:
http://forum.xda-developers.com/showpost.php?p=14638641&postcount=34279
You can use another app (like SetCPU) but the daemon usually handles screen off's quicker. The governors basically determine how the processor frequency is changed. I'll explain the common ones:
Performance - Runs at highest speed, so if you have a range of 200 to 1.3G, it'll stay at 1.3G all the time, not usually the best
Ondemand - The universal default for phone overclocking, it only changes the speed up after a certain percentage of the CPU is used, and it switches on the fly, so if the CPU is used too much at 400MHz, it'll ramp it up to maybe 600 or 800, and if it's still overused, it'll put it up to maybe 1 or 1.2G
Conservative - This is like ondemand, except it makes the changes more gradual. It can give noticable lags in the foreground at times, so this is mainly used when the phone is asleep (screen off)
Smartass - This governor is like ondemand, except it'll less readily switch frequencies to higher values when it detects the screen off. This isn't really used because the overclocking daemons take into account the phone being awake or not
Basically, there isn't really a need to change governors, only really frequencies if anything. The thread, however, does tell you how to change governors.
Im using latest LeeDroid GB 3.2.1 and to be honest with the work he's done with the Kernal (3.1.8BFS) I have found that the ROM is a lot MORE responsive without me overclocking the CPU.
Im not really sure how it all works, but I guess doing this on different ROMS has its own different out comes.
overclocking has me confused too, is there really that much of a benefit in it? how much will i gain from it?
toby_lerone said:
overclocking has me confused too, is there really that much of a benefit in it? how much will i gain from it?
Click to expand...
Click to collapse
There is a benefit when you use certain apps, or even sense itself. For example, I've never had sense ui freeze, or go slow. The under clocking helps to improve the rubbish battery life when your phone is asleep.
In terms of measuring the gain, I have no idea. Really, I'd think you could use a process heavy app, or benchmarking app and see.
There's also loads of guides on overclocking to help out! (that's how I got the hang of it! )
Sent from my Desire HD using XDA Premium App
For the need on OC, it depends on the kind of apps u're using. If u're happy w a non OC DHD, its totally up to u.
But for the UC, it works as a terrific battery saver, mich better/effective than other battery saver soln on market
The safe range depends on the DHD as the manufacturing changed even though same part, i'm OC 1.5GHz "On Demand" profile and under clock 245MHz on screen off "Power Save" profile.
Getting approx a day usage on Lee 2.1.
I was wondering which governors and schedulers are the best for say performace or battery? I've done a little research on my own, but what do you prefer on your HTC One V? I've got aokp JB running on my cdma one v
Thanks!
I am a kernel dev, so naturally I know whats behind this code Lionheart is my favorite as it has aggressive scaling. No lag is also good, in some cases. On demand is great with battery though. I can get roughly 8 hours mid use with on demand. I hope this helps with deciding your governors.
Sent from my One V using Tapatalk 2
simonsimons34 said:
I am a kernel dev, so naturally I know whats behind this code Lionheart is my favorite as it has aggressive scaling. No lag is also good, in some cases. On demand is great with battery though. I can get roughly 8 hours mid use with on demand. I hope this helps with deciding your governors.
Sent from my One V using Tapatalk 2
Click to expand...
Click to collapse
Hey Simon! I'm actually running your 3.0.46 sick kernel JB with AOKP. It's wonderful!! haha so far, I've been running OC at 1708 with the performance governor and noop scheduler... it's lasted 11 hours and I'm at 73% battery, medium to light use with wifi on the whole time, but it's pretty snappy!
Is Lionheart pretty much a performance governor? You mentioned aggressive scaling, so it's snappy when it needs to be, but saves for battery when you're not using it?
BTW I didn't see a "no lag" governor... not sure what that is, so can you clarify? Also, is performance actually the best for snappiness, or will lionheart be even better? I used to use [email protected]$$v2 on my optimus v, but I'm just not sure what's best here?
Nolag is a new addition. I have been hard at work removing even more htc things Lionheart is a bit nicer on battery then performance, because it will scale to your minimum of its not needed. Perfoance stays at full no matter. Cpu spy will be a good tool to help with battery as well
Sent from my One V using Tapatalk 2
Oh kool! Well I don't see it in the latest kernel, so will it be in the next kernel? Thanks dude, you're awesome!
I'll fill everyone in on this thread on the work.
We are :
Patching to Linux 3.0.49
Removing htc additions that are hacks and ics specific.
Cleaning Bluetooth and header files up
Updating WiFi drivers
Updating GPU drivers
Overhauling the mmc drivers
We also have a driver dev that's working on camera and maybe eventually an lcdc driver which will allow us to use the experimental caf display needed for cyanogen mod10 and full project butter
Sent from my One V using Tapatalk 2
Wow that sounds ridiculously awesome!!
Hey guys
Before rooting my tablet I want to know something. Whats the fuss about this specific kernel? I literally see it everywhere ( well done to the dev )
I kinda want to overclock my nexus too 1.7ghz but Im not sure that kernel can do it? I also want amazing battery life I get around 7.5 already so by no means is it bad
J
Sent from my Nexus 7 using xda app-developers app
I've got elementalx on my nexus 7 2013 : it works perfectly on 1.7ghz... And this kernel has some cool features like double tap to wake... For the battery, you can underclock but while you overclock just a bit, the battery life will be OK
So, flash it ! ?
Térence
Sent from my Nexus 7 using xda app-developers app
JackHanAnLG said:
Hey guys
Before rooting my tablet I want to know something. Whats the fuss about this specific kernel? I literally see it everywhere ( well done to the dev )
I kinda want to overclock my nexus too 1.7ghz but I'm not sure that kernel can do it? I also want amazing battery life I get around 7.5 already so by no means is it bad
Click to expand...
Click to collapse
I didn't know there was any kind of a fuss! I think that we are all lucky in the sense that we have multiple good choices for kernels on the Nexus devices and most others in general.
It goes without saying that any custom kernel is going to give you the ability to overclock and it just boils down to what the max MHz is that any specific device can handle. Not that I've tried it but I've seen claims of 1.9 MHz and higher (ElementalX) running fine but each device is going to be different and I personally don't see the point of overclocking that high. I've had mine at 1.7 and 1.8 MHz to run some benchmarks, try different governors (elementalX & ondemand) and get an idea about battery life at those frequencies. Did all that so I can get a comparison to what I see running 1.6 MHz which is what I use everyday, that plus the gpu is set at 450 MHz while using the ondemand governor for both cpu and gpu. I do have to say that my N7 ran very well at 1.7 and 1.8 MHz but "my" goal is to get the best combination of performance and battery life, for my use. I generally see 7- 10 hrs of screen on time which includes watching video and some gaming. Not using any third party apps to control the kernel, mostly default settings when using the aroma installer, slight undervolt for 384 MHz, I don't use DT2W or S2W,. Basically... it's just too easy to install the ElementalX kernel, not worry about having to dial it in and still see a noticeable improvement in performance and battery life. No fuss, no muss!
What are your settings?
!PimpedOutNexus7!
shaolinz said:
What are your settings?
!PimpedOutNexus7!
Click to expand...
Click to collapse
Aroma installer;
Set each core separately = no
Max Cpu Frq = 1620Mhz
L2 cache and bus = elementalx
Undervolt = 850 min
Thermal = run hot. Mine never gets hot at 1.6 MHz and this way you don't have to worry about thermal throttling.
Max GPU = 450 MHz
Gpu governor = ondemand
i/o scheduler = deadline.
Sleep/wake settings = None
Other settings = use stock ondemand settings. enable max screen freq, enable usb fastcharge, disable magnetic screen off, disable fsysnc, all other options unchecked,
---------- Post added at 06:51 PM ---------- Previous post was at 06:42 PM ----------
You can use the elementalx governor which does a great job and does improve battery life. In the other settings page leave "use ondemand governor' unchecked and check the box for "gboost." For gaming I personally like to leave mine set up with the ondemand governor, seems just a little bit smoother with less frame drops. You can try both to see which works better for you.
Thanks a lot in will let you know how it goes ....great help +1
!PimpedOutNexus7!
Hmmm feels like its running hot
!PimpedOutNexus7!
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...