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.
What is the max overclock in this phone?? tnx!
Differs on every phone, most go to 940 or 902 stable, if you go higher you will get crash and reboots, but it is possible your gio is not stable above 883 , just try it out, it wont get it bricked
Sent from my GT-S5660 using xda premium
844
844 is the highest stable you can get, but you can go up to 921 mhz but you can get screen freeze and you will have to remove your battery and restart.
I've had problems with over 806, but recently I put it up to 825 and it's stable so far. I really don't understand how some can go over 900, the phone will become unusable. It also seems to be more stable with minimum freq being set to 122 not 245. Currently I have 122-825 with smartassv2 scaling and it's working fine.
One more thing. I have more luck oc'ing with cyanogenmod built-in CPU governor, setCPU with different profiles seemed to crash my call answering dialog too easily. So if you use smartassv2, there isn't much point to use setcpu for screen-off profile.
overclock
in my opinion best clock for daily usage is 806MHz
voetbalremco said:
Differs on every phone, most go to 940 or 902 stable, if you go higher you will get crash and reboots, but it is possible your gio is not stable above 883 , just try it out, it wont get it bricked
Sent from my GT-S5660 using xda premium
Click to expand...
Click to collapse
This.
Others are just stating their own experience.
True, everyone has other mhz that is stable, you just need a bit luck
Sent from my GT-S5660 using xda premium
Just a quick question:
I know how to adjust my Min and Max frequency, but which governor should I use?
My ROM is GalaxyICS-KANG-beta3, and the default governor is ONDEMAND. Max CPU frequency is set to 902 MHz and Min is 122 MHz, the default.
Which of these settings, if any, would you recommend I change? I'm a little intimidated by the sheer amount of governors available to me...
Alucai Vivorvel said:
Just a quick question:
I know how to adjust my Min and Max frequency, but which governor should I use?
My ROM is GalaxyICS-KANG-beta3, and the default governor is ONDEMAND. Max CPU frequency is set to 902 MHz and Min is 122 MHz, the default.
Which of these settings, if any, would you recommend I change? I'm a little intimidated by the sheer amount of governors available to me...
Click to expand...
Click to collapse
I'm not entirely sure how all of them work, but ondemand is the most neutral choice, that's why it is the default governor on most roms.. it chooses CPU workload according to need (on demand).
Smartass is similar, except it keeps CPU usage to minimum when screen is off (it has a built in screen-off profile). SmartassV2 is an upgraded version of smartass. It's based on Interactive governor, but there are differences on how cpu usage scales up and down.
Minmax uses only minimum and maximum values. When your phone is idle, it uses minimum.. when it's not idle, it's always at max value.
Performance keeps CPU at max all the time. Powersave does the opposite - keeps at minimum. Conservative avoids using high values when possible.
So if you don't need anything special, then ondemand or smartassv2 are the best choices with compromise between performance and battery life imo.
my gio is 940MHz
失败的中国人正在尝试提高！
it seems that my gio is stable at 940Mhz, it got one day 1Ghz but over a day he crashd and i could not set it back to ghz... xD
This is really strange and probably even stranger to complain about but I want to understand.
I UV on my Note and so far managed to drop to levels I find hard to believe.
200MHz - 600mV
300MHz - 600mV
400MHz - 600mV
500MHz - 600mV
600MHz - 600mV
700MHz - 600mV
800MHz - 600mV
900MHz - 600mV
1000MHz - 600mV
1100MHz - 600mV
1200MHz - 975mV
1300MHz - 975mV
1400MHz - 1000mV
1500MHz - 1050mV
1600MHz - 1100mV
Why is my note able to run at 600mV on all frequencies up to 1100MHz??? At first I thought it was a reporting error and It wasn't really running on those voltages but found breaking points on higher frequencies so eliminated that theory. :silly: Would be to be able to test these frequencies at even lower levels. Anybody know a tool that can do it?
This is the process I followed:
Set the voltage value in STweaks,
Set the max MHz in STweaks to the frequency for which I just dropped the voltage ,
Close STweaks,
Open Voltage Control to confirm that the voltage and max frequency has really been set,
Close Voltage control,
Reboot,
Open Voltage Control again to confirm that the voltage and max frequency is really set,
Close Voltage control,
Reset timings in Android Tuner Free,
Start Stability - Classic Test and verify that the Note is running at the max frequency,
Open some other apps and play around for a while,
Get Stability Test back to foreground and go to sleep (if it is time to sleep)
For all of the above frequency values i ran the Stability Test overnight for at least 4 hours plus for a couple hours while using the phone. Didnt get a single freeze or reboot. The only issue was that while I had it on max 200 MHz the Note was not usable while the 300 and 400 MHz frequencies were annoyingly slow. 500 MHz and up is bearable even with Stability Test running.
Attached are the last status and test screenshots. The Stability Test has been running while I been also using it for calling, messaging, adjusting other app setting and taking screenshots.
I check the frequency timings in Android Tuner Free and it is usually 1-4% on offline, 95-98% on the tested frequency and sometime 1% on the frequency just above the tested one. All other frequency times usually 0%
Any ideas if something funny is going on or is this Note just unbelievably under-voltable???
MutantWizard said:
This is really strange and probably even stranger to complain about but I simply need to understand.
I UV on my Note and so far managed to drop to levels I simply cant believe.
200MHz - 600 mV
300MHz - 600 mV
400MHz - 600 mV
500MHz - 600 mV
600MHz - 600 mV
700MHz - 600 mV
800MHz - 600 mV
Rest of the frequencies are still at stock values
First I copy pasted some UV setting from another post and the Note ran without Issues. Then I started dropping a little bit here and there and at some point got some freezes and reboots but couldnt figure out which frequency was the issue so I returned all to stock and started one by one from 200 MHz. The above is where I got to so far and simply need to understand why or what is happening.
This is the process I followed:
Set the voltage value in STweaks,
Set the max MHz in STweaks to the frequency for which I just dropped the voltage ,
Close STweaks,
Open Voltage Control to confirm that the voltage and max frequency has really been set,
Close Voltage control,
Reboot,
Open Voltage Control again to confirm that the voltage and max frequency is really set,
Close Voltage control,
Reset timings in Android Tuner Free,
Start Stability - Classic Test and verify that the Note is running at the max frequency,
Open some other apps and play around for a while,
Get Stability Test back to foreground and go to sleep (if it is time to sleep)
For all of the above frequency values i ran the Stability Test overnight for at least 4 hours plus for a couple hours while using the phone. Didnt get a single freeze or reboot. The only issue was that while I had it on max 200 MHz the Note was not usable while the 300 and 400 MHz frequencies were annoyingly slow. 500 MHz and up is bearable even with Stability Test running.
Attached are the screenshots of the process at 800 MHz and the Stability Test has been running for almost six hous while I been also using it for messaging, adjusting other app setting and taking screenshots. After about 5 hours of 100% CPU load at 800 MHz the Note is down to 80% battery. Not really sure but it seems quite low power consumption.
I just checked the timings again in Android Tuner Free and 12% on offline, 86% on 800 MHz. All other frequency times 0%
Any ideas if something funny is going on or is this Note just unbelievably undervoltable???
Click to expand...
Click to collapse
1st thing, my STweaks is ver 1.1 but looks a bit different than your screenshots, pls confirm that.
2nd, I too like to underclock but had no idea you could push it as far as you . It's kind of like driving a car low on gas to see how far you can go.
3rd What ROM & kernel you on? I'm on X-Note 3.3 with Adam kernel.
Last, here's a screenshot of my undervolting...I'm kinda embarrassed compared to yours Note the differences in layout of STweak menu.
I'm inspired to go even lower now, my battery life is pretty awesome but I think I can squeeze it more.
tweeny80 said:
1st thing, my STweaks is ver 1.1 but looks a bit different than your screenshots, pls confirm that.
2nd, I too like to underclock but had no idea you could push it as far as you . It's kind of like driving a car low on gas to see how far you can go.
3rd What ROM & kernel you on? I'm on X-Note 3.3 with Adam kernel.
Last, here's a screenshot of my undervolting...I'm kinda embarrassed compared to yours Note the differences in layout of STweak menu.
I'm inspired to go even lower now, my battery life is pretty awesome but I think I can squeeze it more.
Click to expand...
Click to collapse
My STweaks is also 1.1 and guessing the menu difference might be due to different kernel. I am on RedPill, stock ROM and probably irrelevant but TWERP as well.
I have mixed feelings about the achieved UV. Very happy if it is true but suspicious that there is some kind of a reporting error and that I am actually not under-volting it at all.
I will soon update the OP since I have now been now testing the 900 MHz for the last 3 turns. Started at 900 mV then droped to 800 mV and now already running it for a couple hours at 700 mV. I just cant believe that its actually at at this voltage and running without issues.
MutantWizard said:
My STweaks is also 1.1 and guessing the menu difference might be due to different kernel. I am on RedPill, stock ROM and probably irrelevant but TWERP as well.
I have mixed feelings about the achieved UV. Very happy if it is true but suspicious that there is some kind of a reporting error and that I am actually not under-volting it at all.
I will soon update the OP since I have now been now testing the 900 MHz for the last 3 turns. Started at 900 mV then droped to 800 mV and now already running it for a couple hours at 700 mV. I just cant believe that its actually at at this voltage and running without issues.
Click to expand...
Click to collapse
Hmm yes, because you're going so low, it begs the question is the app reading accurate? I mean, you're reeeaaaal low. Would be good for a more knowledgeable person to chip in and give us feedback.
One thing - in your screenshot it shows your max frequency capped at 800MHz. To me that reads you are running only at 50% power. If so, that explains your insane battery life. From steps 900 and above you've left voltage at stock because they're unused. right?
tweeny80 said:
Hmm yes, because you're going so low, it begs the question is the app reading accurate? I mean, you're reeeaaaal low. Would be good for a more knowledgeable person to chip in and give us feedback.
One thing - in your screenshot it shows your max frequency capped at 800MHz. To me that reads you are running only at 50% power. If so, that explains your insane battery life. From steps 900 and above you've left voltage at stock because they're unused. right?
Click to expand...
Click to collapse
Yes higher frequencies still at stock and not used but will be getting to them at their own time. Fact though is that even with cap at current 900 MHz and with Stability test running I can still use the Note normally for any regular tasks. If I don't play games I would never need more speed.
Now updating the OP with the 900 MHz setting and screenshots.
BTW I just realized I added to battery life when transferring screenshots by connecting the Note to the laptop by cable. Battery life still remains to be seen.
Updated the OP with the full range of voltages 200-1600. I don't OC so those will not be doing. But I still have the original question.
Is it possible???
Gets more and more strange. GPU under-clocking and under-volting of following frequencies working for days without any usage issue. I changed the minimum and maximum MHz to include the below frequencies and didn't notice any difference in the Note behavior / performance. When running the stability test with GPU testing included I don't get any errors if running under 2 hours but if I leave it overnight the test does crash at some point in time without any other ill effect. I only know that it crashed coz it disapears and it tells me it crashed when the next day I re-start the test.
54MHz - 600mV
108MHz - 600mV
160MHz - 600mV
266MHz - 600mV
350MHz - 600mV
The fact though is I don't understand what to expect as an issue when under-clocking or under-volting the GPU.
Mate, you're still at it!?
Rereading your data, I strongly suggest you post these stats in whatever thread belongs to the kernel and/or tuner app you're using.
My overseas Singaporean work colleagues would say 'cannot be, cannot be.....'
tweeny80 said:
Mate, you're still at it!?
Rereading your data, I strongly suggest you post these stats in whatever thread belongs to the kernel and/or tuner app you're using.
My overseas Singaporean work colleagues would say 'cannot be, cannot be.....'
Click to expand...
Click to collapse
Yea slowly trying one by one new settings and letting it run for a while so that when I go to the next setting and experience an issue I am sure its the newest setting that's causing it.
Thanks will do as suggested.
Has anyone tried to undervolt his Note 8?
I'll be undervolting my N5110 soon...
So, am I the first one to it or what?
Please share your sets.
Here's my settings. I run CivZ ROM with built-in kernel
I messed with the same rom... yes I undervolted and overclocked and done as much as I could do. Went back to 4.2.2 stock and still get about the same performance, and battery life. One thing that I could not live without, is my 64gb SD card. Too many issues with FAT32 and my music and video files. EXFAT is the only way to go with 64gb SD cards. With my stock ROM, I get 8 to 10 percent every hour, and 15 percent every hour playing HD video through miracast to my TV.
I'm doing it right now, following this guide (not as closely as I should, most likely).
@Alastor_ru : how did you get your values? Mine are generally lower, besides the fact that Voltage Control allows 850 mV as a minimum.
Thanks, but what about the higher freq's voltages
I think that you have up to 1.9 GHZ or 1.8 at least
@bradipovsky, that's the same guide I will follow
bradipovsky said:
@Alastor_ru : how did you get your values? Mine are generally lower, besides the fact that Voltage Control allows 850 mV as a minimum.
Click to expand...
Click to collapse
I use SetCPU, it has 600mV as a minimum.
I perform several steps while set voltage to lower and lower values and stop to play with it, when I get my current settings. As I noticed, the biggest power eater is the screen, so undervaluing doesn't bring the big savings
AhmadLight said:
Thanks, but what about the higher freq's voltages
I think that you have up to 1.9 GHZ or 1.8 at least
Click to expand...
Click to collapse
I don't use the highest freq's, cause it's not needed for me. I limit the highest CPU freq to 1GHz.
Alastor_ru said:
I use SetCPU, it has 600mV as a minimum.
I perform several steps while set voltage to lower and lower values and stop to play with it, when I get my current settings. As I noticed, the biggest power eater is the screen, so undervaluing doesn't bring the big savings
I don't use the highest freq's, cause it's not needed for me. I limit the highest CPU freq to 1GHz.
Click to expand...
Click to collapse
Well, 8" of screen of course don't help the battery I'm doimg it mainly to limit the heating, so high frequencies are the most important. I think it's a better option than underclocking, but that's just my opinion.
I'll share my values later, but I don't think they're ideal yet.
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...