yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] pkgnex:
I haven't ever tried lmk slots where the 5th one is lower than the 3rd and 4th, so I can't comment on that arrangement except that it seems to go against the way Google meant Android to handle things (more background-ish stuff gets killed off first, and in a specified order).

The settings the Dev Team worked out are still as good as I have found. My personal set-up varies only slightly from that:

16,32,48,64,96,160 MB (or 4096, 8192, 12288, 16384, 24576, 40960 pages if you are using a script in init.d)

I've tried increasing the last number to ~192, and it works ok with ASRAM or SUPER-RAM kernels, but not enough better than 160 to make a much of difference. My testing seemed to show that keeping the increments in multiples of the same number (8, 12, 16) seemed smoothest. Mine use 16 as the base and multipliers of 1, 2, 3, 4, 6, 10. You can play with different integer multiples of 12 (stock Google set-up from 4.3 onward), forcing a top number of 144, 156, or 168, and get substantially similar performance.

The most important thing I have found is increasing the last number to be at least 50 or 60 MB higher than the one below it. This seems to allow more overhead for quickly launching large or memory-intensive apps (think Chrome, for example), without having to wait for android to kill off all the empty apps sitting around. A top number in the 160 - 190 range also isn't so aggressive as to always be killing stuff you might want to keep open for a bit, including background processes you don't want killed.

In the end, the Dev Team agreed that the LMK values are kind of a personal thing - you can set it up to keep everything open for good multi-tasking OR having a lot of RAM overhead for quick opening of new apps, but not both (at least not on G-Nex with 700MB).
[Samsung Galaxy Nexus] osm0sis:
Lately this has been in my init.d script, but I can't say I notice a substantial difference with KitKat on the FDT experimental over the other stock or rounded stock values I have commented out there.

# lmk tweaks
#minfree=12134,15175,18216,21273,24314,30382;
#minfree=12288,15360,18432,21504,24576,40960;
minfree=6144,8192,12288,16384,24576,40960;
lmk=/sys/module/lowmemorykiller/parameters/minfree;
minboot=`cat $lmk`;
while sleep 1; do
if [ `cat $lmk` != $minboot ]; then
[ `cat $lmk` != $minfree ] && echo $minfree > $lmk || exit;
fi;
done&

---------- Post added at 06:15 PM ---------- Previous post was at 06:06 PM ----------

P.S. yours would be

minfree=2560,5120,25600,30720,24320,49920;

I'll try them for a bit, but honestly the latest Chrome update just ****ing murders everything when it's open and even GEL has to redraw.
[Samsung Galaxy Nexus] pkgnex:
I concur. Both that Chrome is murderous, and that LMK changes don't seem to make as much difference in 4.3+ as they used to.

Boiling down my previous essay into a single sentence... In Android 4.3+, the only LMK tweak that still seems to help performance a little on the G-Nex is raising the empty_apps (last number) to 40960 pages (160MB), or there-about.
[Samsung Galaxy Nexus] Ashtrix:
Settings on Mpo v1080 for 1.5GHz

RAB - 1024

Governor - Hyper

Scheduler - BFQ

MinFreq - 384MHz

MaxFreq -1536MHz

MaxScreen off - 384MHz

MinScreen on - 537MHz

GPU OC - 384MHz

SRMPU - off

Voltages - MPU (These freq steps are exactly the same from Trinity's steps, I'm using my Nexus on 1.5GHz since those TNP's came out and runs pretty stable though minor freeze up & SoD's are very rare depending on your SoC temp and the environment temp ;))

1536 - 1305

1420 - 1240

1344 - 1200

1228 - 1160

1036 - 1120

729 - 1040

537,384,192 are stock Mpo's....

I use similar uv voltages for Mpo's and Trinity's as they share similar steps usually my old Trinity's uv steps are more accurate (Unfortunately, those settings are gone with my old 4.3 ROM ) than my custom ones for mpo's, plus my nexus never kicks in that 1420 clock step at all when i'm on 1.5G's on this Mpo and trinity avoids middle steps in an OC kernel, maybe a governor or the programming itself. Though my Nexus runs blazing fast on these settings and on heavy gaming it gets hot and I don't mind the battery as i might need to charge it 2 times a day on heavy usage like Playback, Gaming, BT & wifi for hours. Otherwise once in 2 days will do the job.

Didn't mess with those others IVA's and Voltage regulators !!

Screen settings

The colors on Mpo are diff sue to the purple tint fix so I had to change my values a bit (screenshot below) to maintain similar balance between my sig values and these new ones exclusive for Mpo's.

Thanks !
[Samsung Galaxy Nexus] noseph:
Tunable Settings

Can we continue the Tunable Settings discussion here, since the main Mpokang thread has been locked by the mods?
[Samsung Galaxy Nexus] Nephilim:
I'm not sure how long this thread will stay open since it is a reference to Mpokang but I don't see the problem while it is still active. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] gautam_nexus:
[MENTION=2853378]Nephilim[/MENTION] Just flashed Mpokang CM version ( came from dirty just to check what Mpo's hype is all about never flashed the v10 version on 4.3 ).

I was trying your settings for Mpokang are those settings updated? can I use your DirtyV interactive tunables on Mpokang CM version?

Thanks
[Samsung Galaxy Nexus] Nephilim:
Yep, you shouldn't have a problem doing so. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] noseph:
[MENTION=3777325]wavedashdoc[/MENTION] are you still around?
[Samsung Galaxy Nexus] wavedashdoc:
Yeah lol. Been busy the last few days. Just getting back into the forums...I jumped onto 395 Franco for the last 2 days. Haven't been overly impressed. Might jump back to Mpokang. Might test out Dirty again too.
[Samsung Galaxy Nexus] noseph:
I am still rocking your last posted tweaks. You were very excited about some new ones just before the other thread was locked, did you get any where with them? Thanks.
[Samsung Galaxy Nexus] audit2:
Using your setting with LIquid ROM getting my best BM.
[Samsung Galaxy Nexus] wavedashdoc:
And I'm back to MPK_SR. After jumping ship to try out Franco's latest and greatest kernel (about 3 days) and ALL of the recent Dirty V offerings, I can confidently say that this kernel is the king. Don't get me wrong, those other kernels are great and its awesome to see the GN threads alive again. Currently though this kernel just trumps them. I swear there is no lag when touching the screen, no hesitation of delay and what's going to keep me on the GN for a while longer. You can't beat the feeling when you try someone's GS4 or Note3 and you're launching apps, multitasking faster or just as fast as they are on a dual core out dated phone 8)

More tweaking to come. For now, enjoy the current tunables. Pm me if you have any questions or comments.

Wavedashdoc.
[Samsung Galaxy Nexus] antypas:
Totally agree with you man. I try many other kernels and I always get back to mpokang. Performance is unbeatable...
[Samsung Galaxy Nexus] aaron13:
I am on Franco's R395 right now with governer interactive and scheduler row. What's the Mopang's one?
[Samsung Galaxy Nexus] noseph:
Very glad to have you back.
[Samsung Galaxy Nexus] [sito_web]:
Hi everyone, I've been a bit absent from this thread and I do not know what's going on. this awsome kernel is ended or has just finished? Why there were no more updates?

Thanks!
[Samsung Galaxy Nexus] Nephilim:
This kernel has been discontinued for a very long time.

Sent from my Android 4.4 Galaxy Nexus
[Samsung Galaxy Nexus] Nephilim:
Spoken like a true fanboy. There are many kernels out there that are better. There isn't even any proof at this point that Mpokang actually increases ram performance outside benchmarks. There never will be either until Mpokwths decides to stop violating GPL policy and share his v10 code. Im on DirtyV 2/8/14 right now and it dances circles around Mpokang. The benchmarks don't mean jack when the daily usage proves otherwise. This does not mean DirtyV is the best there is, nor are any other kernel, I am simply relaying that their are other kernels out there that can compete and go beyond what is possible with Mpokang. No one kernel is the best for everyone, they can only be the best personally to each depending on what each individuals personal preferences are.

If any of you can provide factual evidence that there actually is a 50% boost in ram performance I'll eat my words, but that is not likely.

Mpokang is a good kernel, but certainly not the best. His base came from AK to begin with.

P.S. This is coming from someone that used to only use Mpokang SuperRam. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] jhonnyx:
I think the other developers deserve respect, you shouldn't say that as a statement.
[Samsung Galaxy Nexus] xzilem:
The only problem with mpo kernel is there's no network arrow in status bar.
[Samsung Galaxy Nexus] maximh23:
please help me. i try to flash the mpokang kernel with the newest cm 11 nightly , but i have everytime status 7 error, set_perm: some changes failed
[Samsung Galaxy Nexus] jhonnyx:
hi there maximh23, please try to re-download and, if possible, check MD5 hash after downloading.
[Samsung Galaxy Nexus] maximh23:
this is the hash numer F4E71A65F7CD3AE7E19EDC18F3F7AE0C where can i find the original one?
[Samsung Galaxy Nexus] jhonnyx:
have you re-downloaded it and tried to flash it again?
[Samsung Galaxy Nexus] scarcry:
You're probably using latest CWM recovery (6.0.4.7). If so this is not the advice I should give you because the kernel maintainer should fix his install script (learned that from [MENTION=4544860]osm0sis[/MENTION])but when you downgrade to CWM 6.0.4.6 flashing mpokang will probably succeed.

Sent from my LiquidSmooth maguro
[Samsung Galaxy Nexus] büscher:
Or you can open the zip and search the updater script and just delete the lines with "dump_image" inside. (There schould be 2 files inside the zip containing this line)
[Samsung Galaxy Nexus] demlv:
This thread seemingly survived. It was started because someone who updated the kernel to make it compatible with 4.4 wanted to share his work. The orig. kernel developer evidently violated the GPL by failing to share the source, but everything thing done since to make it compatible with later versions of Android has been shared properly, so far as I know.

While it is now a bit dated, I still find that this kernel works best for my device. I will undoubtedly move on when I find something that works better. In the meantime, this seems like the right place to discuss the 4.4 version of the kernel. So I personally hope they don't close this particular thread. My $0.02, fwiw.
[Samsung Galaxy Nexus] Nephilim:
It is not an Open Source rule. Just look up GPL policy and you will see he is directly violating it by withholding his source. As for life event keeping him from posting, nope, if that were the case he would have not been active only a few weeks ago here on XDA and he would have responded to the senior mods pm's about posting his source, which he did not and that is why his main thread is closed.

I think you are doing a great job wavedashdoc and I even have your minfrees posted in my OP on my settings thread. (credit given)

I will now stay silent to avoid the pitchforks and torches.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Haha yeah. It's not some made up "rule book".

The GNU Public License under which kernel source is published clearly states that if you use the source you must also publish everything you base on it.

Those are the rules of GPL. Period. Violating it is actually technically breaking the law.

It's not hard to type "git push origin", mpok just never released the source because he wanted to keep it secret for whatever reason, and then promptly disappeared.

This is not kernel favoritism. You can come find me in the DirtyV thread just as easily as the franco.Kernel thread I'm more directly involved in. I support devs who support the community.
[Samsung Galaxy Nexus] Inferno7202:
So this kernel is included in the op of omnimetal. Since it was i assumed it would work, but everytime i try to flash the kernel on omnimetal, it would say installation aborted. Can anyone help?
[Samsung Galaxy Nexus] maximh23:
ui_print("Mpokang Kernel...");

show_progress(0.1, 0);

package_extract_file("boot.img", "/dev/block/platform/omap/omap_hsmmc.0/by-name/boot");

show_progress(0.2, 10);

ui_print("Mount /System Folder...");

mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system", "/system");

ui_print("Extracting System Files...");

package_extract_dir("system", "/system");

ui_print("Setting File Permissions...");

set_perm(0, 0, 0644, "/system/lib/hw/power.tuna.so");

set_perm(0, 0, 0644, "/system/etc/media_profiles.xml");

set_perm(0, 0, 0755, 0755, "/system/lib/modules");

unmount("/system");

i cant find anything with dump_imgae

---------- Post added at 09:55 AM ---------- Previous post was at 09:36 AM ----------

yes i did, but without succes
[Samsung Galaxy Nexus] büscher:
my bad

change this line:

set_perm(0, 0, 0755, 0755, "/system/lib/modules");

to this

set_perm(0, 0, 0755, "/system/lib/modules");

set_perm: chown of 0755 to 0 0 failed: No such file or directory
set_perm: chmod of 0755 to 755 failed: No such file or directory
script aborted: set_perm: some changes failed
[Samsung Galaxy Nexus] maximh23:
wonderful, it works:good:
[Samsung Galaxy Nexus] a.cid:
Thread under review.

I request everybody to stop commenting on each other's opinions. Unless you have something that contributes to the progress of this thread, please avoid posting.

And if there is an issue, please use the report button (the yellow triangle on top of every post). Us moderators cannot possibly read and monitor every single post made in these forums, which is where we rely on fellow members to help keep the forums clean.

So the next time you read something that makes your blood boil and you think of spewing hatred all over the dev threads, take a step back and hit that tiny little button and move on.

A.cid

Forum Moderator
[Samsung Galaxy Nexus] aaron13:
After flashing mopang cm on my cm11 rom and modifying it with the wavedashdoc settings I benchmarked 12713

After updating cm11 to 11Febr. the cm kernel gave the same score with a little bit less ram. However it feels snappier.

Franco"s kernel gave a score of 12215 but is more battery friendly.

Did someone experienced this also? http://img.tapatalk.com
[Samsung Galaxy Nexus] wavedashdoc:
Going to do some more tweaking and testing tonight. I think I will have 2 profiles for you guys. A "on the go" profile (using GPS, on 4g mainly while running apps like GPS smoothly) and a "Max Performance plus Battery" for at home on wifi and better battery life. Speaks for its self, stay tuned.

Wavedashdoc.
[Samsung Galaxy Nexus] cmoG530:
I have to say, I'm curious about using this kernel again. Lol
[Samsung Galaxy Nexus] wavedashdoc:
Pushing the ram speed to its limits 8) best score yet.
[Samsung Galaxy Nexus] pmbabu:
Wow, that's an awesome score. Give us the settings please!
[Samsung Galaxy Nexus] wavedashdoc:
Soon...
[Samsung Galaxy Nexus] antypas:
Another good benchmark, optimized for dual core devices is Mozilla Kraken benchmark: http://krakenbenchmark.mozilla.org/

It measures processing power CPU + RAM. As it depends on the browser it makes sense to use it with the same ROM and browser.

Anandtech uses it as one of its benchmarks. I went ahead and tried Dirty V 10/2 and Mpokang v10 with EXACTLY the same governor settings @ 1.5 Ghz and the same ROM.

I have been hearing b***** about faking benchmarks and stuff...

This is a benchmark that cannot be really fooled, it uses only the browser. LOWER values are better:

Dirty V: 14058 ms

Mpokang: 13086 ms

I will upload screens later.
[Samsung Galaxy Nexus] aaron13:
Is it possible for you to test Franco"s also?
[Samsung Galaxy Nexus] audit2:
I'm jealous. :crying:

---------- Post added at 07:13 AM ---------- Previous post was at 07:11 AM ----------

Can't wait. Your previous settings made my phone smoke, :laugh:
[Samsung Galaxy Nexus] papatsonis:
That's right.. because i am enough of B.S... about faking benchmarks, and the "Grief" of [MENTION=2853378]Nephilim[/MENTION], in a manner "If he doesnt want to release his source, the kernel doesn't reserve the fastest or one among the fastest kernels"... i will simply attach the latest antutu i run minutes ago (i really was surprized myself..

Interactive

governor, GPU 512, Fsync disabled).

p.s.> neither i like mpokwsths' behaviour, of not releasing the latest source but, you judge without having a clue.. to be somekind of advocate, have you ever considered ,for example, an HDD failure..? all you do (Nephilim) is complaining.. instead of just use kernel as is.. and enjoy it. The only think some ppl might miss is OTG but even this if i remember correctly [MENTION=4328678]metalspring[/MENTION] is easily corrected..

p.s.> has anyone really checked the memory benchmarks, of V9 in a 4.3 rom (which source is available.. ) if they are any different than V10's..? because i

suspect

V9 will score the same.. and really if i was mpokwsth's i would sit in a corner and laugh... (cause these "holy grail" tweaks will be in front of our eyes...)
[Samsung Galaxy Nexus] eagleeyetom:
If the thread is closed and until investigation that doesn't give an excuse to open a new one. In fact it's the best way to find a way out from XDA in the hard way.

Hopefully this won't happen again and we won't have to use the "more convincing methods" to respect moderator's decisions.

If you have a question, please contact any moderator, but don't open a new thread just like that.

Thank you.
[Samsung Galaxy Nexus] Nephilim:
At first everyone thought it was the ramdisk that was the culprit for Mpokang not working with the 12/15 CM11 Nightly and every one after but it was a binary file called "healthd" that was updated in CM11's code on 12/15 Nightly.

Metalspring is the one who found this file to be the problem and swapped it in Mpokang SuperRam but Mpokang CM version and Mpokang 1080p version still have the old healthd binary file so they will still cause issues on any of the CM11 Nightlies starting with 12/15
[Samsung Galaxy Nexus] AbhishekS:
Neph already answered it. :P

DELETED
[Samsung Galaxy Nexus] TheMan0790:
Completely random from this thread (my bad), but is anyone having problems with Greenify lately (if you use it)? For me, Greenify will not auto-hibernate at all. Thinking I need to install Xposed Framework to enable the boost performance experimental feature, unless someone knows a fix...

---------- Post added at 08:08 AM ---------- Previous post was at 08:07 AM ----------

Oh, and I'm on CM 11 Nightlies with Superram kernel (latest nightlies and MetalSpring's fixed Superram kernel).
[Samsung Galaxy Nexus] hepi_hape:
Thank you bro... You make all easy to reach KK kernel update

---------- Post added at 10:08 PM ---------- Previous post was at 10:04 PM ----------

Same here...

If not so bothering can you (OP) post newer kernel update with date release..

Thank you :D
[Samsung Galaxy Nexus] Nephilim:
The 4.4.2 SuperRam updated kernel is ONLY MEANT FOR CM11 Nightly builds from 12/15 and after as well as any rom using CM based code from 12/15 or after.

This means if the rom you are using is CM based check the release date of the most recent update, if it was updated on or after 12/15 you use the new 4.4.2 SuperRam kernel. If it was updated before 12/15, you stick with one of the 4.4 Mpokang kernels.

If your device IS NOT cm based you will stick with one of the three 4.4 Mpokang kernels, the updated 4.4.2 SuperRam won't work.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] marcocsh:
Anyone has the .img of v10 1080p?

Or how can I extract it from the .zip?
[Samsung Galaxy Nexus] akash3656:
Or if the other versions cause you issues, just use the 1080p version. The 720p CM/gay version caused reboots with dolphin browser (trying to get Flash Player working) for me.

Otherwise, it was perfectly fine as a daily driver.

Since then, I rather stick with the 1080p version as it doesn't reboot.

And i have the *old* 1080p variant, it works perfectly on latest cm nightly as of 17th Dec build (no battery derp) and earlier cm nightly (Around early December)
[Samsung Galaxy Nexus] akash3656:
The 1080p variant doesn't come in a .img

Its using the anykernel format.
[Samsung Galaxy Nexus] danvrez:
so with v10 SuperRAM (for newer builds - fixes broken battery) the 1080p is fully working? in theory yes because KK uses less RAM, but i don't know if thats true...¿?
[Samsung Galaxy Nexus] Nephilim:
No, the issue is the updated "healthd" binary in all CM based roms after 12/15, the only differences between 1080p version and SuperRam version is 1080p is in anykernel format so it has no ramdisk and is able to utilize 1080p recording and playback with the expense of less free ram. It still has the old "healthd" binary so it won't work on new CM based roms built on 12/15 or beyond, only the updated 4.4.2 SuperRam kernel will.

Sent from my Android 4.4.2 Galaxy Nexus

---------- Post added at 12:48 PM ---------- Previous post was at 12:42 PM ----------

Are you speaking of the 4.3 1080p variant of Mpokang? If so, I don't understand how it does not cause battery status issues since it does not have the updated "healthd" binary, which was the cause of the battery issue to begin with.
[Samsung Galaxy Nexus] Nephilim:
Hey guys, just an important Heads-Up, Looks like CM reverted back to their old "healthd" binary. When I flashed today's official Nightly for Toro (which just came out a half hour ago) I flashed it with the fixed 4.4.2 SuperRam, that borked the battery bigtime.

So just as a quick test before restoring my nandroid I rebooted into recovery and flashed the original 4.4 SuperRam kernel that was previously working before the 12/15 build and it fixed the battery no problem.

So, long story short. As of today, the original 4.4 SuperRam is the one to flash on all CM based roms again.

This means that CM Gay Kernel and 1080p Kernel should work fine again as well.​

So DO NOT use the 4.4.2 SuperRam kernel on any CM Based roms updated as of Today, it will have a reverse effect and mess up all your battery stats and functionality!!!​
[Samsung Galaxy Nexus] AbhishekS:
That's great! I guess I can safely remove the link for the battery fix kernel version from the OP then. :)
[Samsung Galaxy Nexus] Nephilim:
I'd hold onto a copy of it on your pc just in case you have to re-add it though. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Klejdi90:
Good news do you know if its fixed for maguro?
[Samsung Galaxy Nexus] Nephilim:
Try it out on the new build. Worst case scenario you'll have to boot into recovery and flash the 4.4.2 version. I'd imagine that it'll work though since CM's buildbot compiles Maguro before Toro.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] n0ve:
Thanks for the heads up neph...always helpful man greatly appreciate.
[Samsung Galaxy Nexus] hepi_hape:
Im using omnimetal updated 13-12-2013... It seem the 4.4.2 lernel cant inserted.

Ok i revert to askp for safety :D

Ok, will try using old 4.4 kernel on 4.4.2 omnimetal 13-12-2013 update
[Samsung Galaxy Nexus] akash3656:
I guess it is because its an anykernel kernel which basically uses the ROM's ramdisk? Trinity (which also uses anykernel) just worked on the newer cm11 nighly for me where everyone was complaining that battery was broken on kernels that come with a ramdisk (boot.img)
[Samsung Galaxy Nexus] Nephilim:
Lol, read a couple posts above, the newest CM11 Nightly is working again with the normal 4.4 Mpokang kernels, that's probably the reason why 1080p worked for you and Trinity. ;)
[Samsung Galaxy Nexus] cujo6801:
Hey bro

Off topic here...

But I tried your color settings and all I can say is WOW...

My phone looks great..

Thanks bro....

sent from the DOG pound
[Samsung Galaxy Nexus] akash3656:
Maybe haha. Can't exactly keep track of all changes CM is doing honestly..... Recently, they just reverted many commits related to Bluetooth out of the blue.