yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] boype:
I really appreciate your work, it's great :)

Why I chose the other binaries is simple: I could not get yours to work. Unpacking gave me some 'segmentation fault' message when I tried to unpack the dd'd cm11 stock kernel. The binaries I use now work just fine.

So you're saying that for you it is the exact opposite? osm0sis' binaries work and the other ones don't?
[Samsung Galaxy Nexus] Alkemix:
Yes.. I wanted to try using your RAMdisk whole, but in the end I found after booting the stock rom kernel not the Fancy kernel ! This means that the boot.img was not generated correctly ... I put on the ramdisk that I sent to You by private message and everything is ok, even on Cyano11. I do not know why but the two files update works badly for me.
[Samsung Galaxy Nexus] thomstrack:
I'm on Shiny ROM. I need flash ROM again, or i can flash the stock Shiny kernel (developer have a flashable) and after flash fancy?

Thanks in advance.

Sent from my Galaxy Nexus 4.4.2
[Samsung Galaxy Nexus] ashclepdia:
Just kernel should be fine.

But don't even need to do that if you've not flashed other kernel since install of shiny
[Samsung Galaxy Nexus] dharmabm:
For those of you having issues, it might be helpful to post some logs instead of just complaining
[Samsung Galaxy Nexus] cujo6801:
But it's so much easier just to complain.... Lol

Sent from the "DOG" pound
[Samsung Galaxy Nexus] klobkelosh:
Boype, those default minfree values, as you know from all the comments, aren't optimal for multitasking. In trickster, 10,14,18,22,26,46 are faring much better.
[Samsung Galaxy Nexus] osm0sis:
I'd like to track down that issue. Can you point me to the exact cm11 boot.img and the recovery you're using so I can try and replicate?

Were you using the latest binaries from my AnyKernel2 Github or the outdated ones from the DirtyV repo? I use those same binaries in my Android Image Kitchen Mobile Edition (AIK-mobile) with no issues. :confused:

Thanks for the help. :)

Edit: [MENTION=4615478]boype[/MENTION] The only unpackbootimg segmentation fault error I've ever seen occurs when the specified output directory doesn't exist. That's why my script makes split_img first. Did you use the script when you were testing or just the binary commands?
[Samsung Galaxy Nexus] paarthdesai:
new version is lagging as hell on my phone...launcher getting killed...brower killed when browsing ...back to r45
[Samsung Galaxy Nexus] Piti8576:
With this values all my apps restart every time, the values from Boype are the best no problems since over 12h.
[Samsung Galaxy Nexus] klobkelosh:
Guess I should mention that I'm running omni rom official nightly. What ROM are you using?
[Samsung Galaxy Nexus] Piti8576:
4.4.2_r2 [KVT49L] TREX 13.04.2014 is my rom.
[Samsung Galaxy Nexus] Ashtrix:
I'm on Slim v4.0 and the new r49 is " Rock Stable ". I don't have trickster paid version to edit the values tho we can do them from /sbin maunally there u can find the boype's scripts with new values for the LMK maybe u can tweak them for your needs, the stock ones he posted are just perfect for my nexus :good: .
[Samsung Galaxy Nexus] victor2868:
My launcher is always be killed after opened an app, need to wait the launcher loading
[Samsung Galaxy Nexus] zofox:
Try this values

⛔ I'm a Jedi ... be careful ⛔
[Samsung Galaxy Nexus] Alkemix:
these values ​​are too low ... in the long run the phone will become slow enough
[Samsung Galaxy Nexus] siealex:
These settings work much better.
[Samsung Galaxy Nexus] zofox:
I know but they work much better for the most of the users... We should start from these and study the perfect sequence :P

By know I found this values very comfortable .... With an entire day of usage I haven't had any problem... I can't confirm that if u don't reboot the device for more than a day it will Starr to slow down performances .... :S

⛔ I'm a Jedi ... be careful ⛔
[Samsung Galaxy Nexus] Teemoo:
I got a weird bug with >45, I don't know if its kernel or rom.

I can't enter my pin, so I am stuck at lock screen. Dots don't appear when I put my pin in lock screen after boot, but I can put my sim-lock pin in.

And with r49, my home soft button doesn't work. Using a few days old cm11 nigthly, encrypted, xprivacy. r45 works great though.
[Samsung Galaxy Nexus] fleischbanane:
I'm on r49 and CM11 M5 and everything works perfect with the build in settings. Nothing changed. Using Nova Launcher and having no problems.
[Samsung Galaxy Nexus] Ashtrix:
Hello guys hows your battery with the new r49, SOT and total uptime.. ?

Edit : Mine's just sucking up the battery very fast :(
[Samsung Galaxy Nexus] TheGeekRedneck:
Lots of weird lagging with R49... sometimes the phone will just totally freeze for like 15 to 30 seconds and then be fine again. For example just now it froze at the lock screen and wouldn't respond to swipes or anything... after about 30 seconds it was fine again. This is on the latest nightly builds of CM11...

I hadn't experienced anything in the way of apps getting killed unexpectedly though.

I did check and the proper minfree values were in effect according to those posted by Boype in the R49 release post.

Back to R45 for me for now... but I'm ready to try new builds as soon as they're available! :)
[Samsung Galaxy Nexus] werewolfo:
I'm sticking to r45 too. I'm also having troubles with r49 and freezes, they appear when i try to swipe down the notification menu. Also, when i go to settings > apps the back button stops responding.

I'm on the latest nightly of CM11, no problems yet with r45.
[Samsung Galaxy Nexus] galaw007:
I'm getting the same with r49. Rolled back to r45

Sent from the Toaster in The Restaurant at the End of the Universe.
[Samsung Galaxy Nexus] RevengeFNF:
I guess the new LowMemoryKiller is far from being perfect.

It would not be better to revert to the old one and optimize the minfree values?
[Samsung Galaxy Nexus] movelbit:
hi.

My phone freezes for a minute or two everytime my phone is not used for 20/30 minutes. Sometimes it reboots when i try to "awake" the phone.

This happens only since when I installed fancy kernel.

I am using CM11, and I can post a log if needed (and if someone tells me how to get it).

Thanks.

RevengeFNF: sou o crux :)
[Samsung Galaxy Nexus] RevengeFNF:
Boas Crux ;)

Flash the r45 version to check if the problem persists.
[Samsung Galaxy Nexus] paarthdesai:
soo many people with problems... please revert the changes... :(
[Samsung Galaxy Nexus] klobkelosh:
On the other hand, I'm up for keeping the new minfree code and working collectively on optimal settings. I need to do some research on what exactly foreground app, visible app, secondary server, hidden app, content provider, and empty app seems refer to. I've read that launcher force close may be prevented by lowering secondary server. I've been pretty happy with 10 14 18 22 26 46 and 8 12 18 30 38 56 (in trickster), but launcher does close too often (lower secondary server) and my auto scheduled 3am titanium backup (lower visible app?) will not run because of insufficient free memory available.

So, perhaps I'll try 6 8 12 30 36 56

---------- Post added at 09:45 AM ---------- Previous post was at 09:20 AM ----------

A little info found whilst googling:

How Android manages Memory

Android groups all apps into 6 groups, from highest priority to lowest:

Foreground app*- you see this app on screen, currently running, but also includes the system itself and "phone"

Visible app*- the app is running and visible, but due to multi-tasking or such is not currently "on top"

Secondary server*- services that stay in background and apps such as Launcher (or other home replacements). Most services go here, like music player, clock updater, background sync, and so on, that's not built into the OS.*

Hidden Application*- apps not visible, but still running in the background

Content Provider*- process that provides content to the foreground, such as "contacts content provider", "calendar content provider", and so on. May also known as "storage".*

Empty App*- the app is in standby, not being used, but is still in memory.

How to manipulate this to get the best performance

We can manipulate our OOM values for each of these categories using Trickster Mod Donate and other apps. Having a lower OOM value for a category, means android will wait longer until killing apps from that group.

From what I have experienced, the more open apps in the "Empty App" category, the slower and more sluggish the phone. Having these apps open is basically a waste of memory, because they are in standby and not being used.*A high OOM value should therefore be set for "Empty App".

Processes that fall into the "Content Provider" category are also a waste of space; they only actually get used when running the application that service belongs to. This means that often the service will be running in the background when it doesn't actually need to be.*A high OOM value should therefore be set for "Content Provider".

The other four categories all contain apps actually being used by the user. When multitasking you want these apps to stay open.*A low OOM value should therefore be set for "Foreground App" "Visible App" "Secondary Server" and "Hidden Application"
[Samsung Galaxy Nexus] ashclepdia:
Why?

Doesn't everyone realize that if you aren't up for trying to help fix it, just install r45.

Simply saying "screw it it doesn't work let's give up" makes moving forward with development impossible. Of COURSE there are going to be issues with something that's not been tried before lol
[Samsung Galaxy Nexus] L-ViZ:
for me everything seems fine, only got one issue.

if transfering data from pc to phone the transfer just stops (in my case after about 100mb// 100 of 1000mb // music -> small files // happened 2 times, didnt test more, but if kernel related i t should be reproducable)

using fancy 49 with slim rom.

only changes i made:

-fsynch disable

-2048 RAB

-deadline

not sure if rom or kernel or just unlucky^^
[Samsung Galaxy Nexus] siealex:
Is it possible to make an application to stay as visible or hidden, but not empty?

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] n0ve:
Many people w problems are ROM related... Zero issues on latest vanir stock settings + OC max 1.34 UC Min... Minfree -2.. MCPS set to 0 for gaming 2 for all others..RAB raised to 896+ neph colors

Thanks [MENTION=4615478]boype[/MENTION] gr8 kernel.

O ya I use ART as well.
[Samsung Galaxy Nexus] zofox:
i can't understand people who are arguing/complaining for everything. Yes there are some problems related to minfree but [MENTION=4615478]boype[/MENTION] is trying to do his best to solve them :D

i already suggested a different configuration that you can simply apply from trickster or kernel tweacker or similar apps, yes [MENTION=4615478]boype[/MENTION] said that different and lower values can cause lag on an high end usage, but i'm using this settings since lastest kernel release, and they are working very well. I think that we must let him the time necessary to solve the problem (he's doing all this for passion). meanwhile we have to adapt.... :D
[Samsung Galaxy Nexus] n0ve:
That's normal.. Not kernel related.. Try moving smaller amounts of files at a time, you'll eventually find whats causing it to stop...also browse thru and delete unnecessary files such as thumbnail cache and files w no names but strange .extensions
[Samsung Galaxy Nexus] siealex:
When I try to run a heavy app or game (not very heavy, even subway surfers) already running Chrome or Browser, the system hangs up completely. This did not ever happen on pre45-2. Looks like minfree does not work. But if I run subway surfers and minimize it, it terminates in 1..3 minutes. My OOM settings are 2 4 6 8 12 20.

---------- Post added at 07:42 PM ---------- Previous post was at 07:41 PM ----------

Use ADB, not MTP. There is a very convenient plugin for Total Commander.
[Samsung Galaxy Nexus] L-ViZ:
never happened before on my maguro

+the transfer stopped at different files, so the fc hasn´t been caused by a specific file.
[Samsung Galaxy Nexus] n0ve:
Happens to me alot...then either try adb or recheck your drivers. There may be many specific files as well...go look deeply at the files your pulling choose let's say for music only the mp3...not pregenerated thumbnails.. Hey I'm just tossing out what worked for me hope to help.
[Samsung Galaxy Nexus] mangusZen:
No problem here on carbon, stock settings light usage , no gaming

Half battery (2000mah)

All work as expected
[Samsung Galaxy Nexus] siealex:
MTP is very buggy, use ADB.
[Samsung Galaxy Nexus] nozz93:
Are you on VanirAOSP? I have the same problem on Vanir 040414.
[Samsung Galaxy Nexus] klobkelosh:
Zofox, your values are hitting the mark just right! 2 4 6 8 12 20. Bsmitty is using 2 5 10 15 20 25, but folks there say it's killing launcher, so bsmitty's secondary server value of 10 is too high, but zofox's 6 send on the mark. So, i think the first three values need to be 2 4 and 6. The last three can be set higher than zofox's if you want more free RAM or left low for better multitasking. With these settings I can't force close Google now launcher and retain about 200mb free memory.

Still a work in progress...
[Samsung Galaxy Nexus] siealex:
Is it possible to prevent a particular app from being killed explicitly? Like Phone or Launcher on stock ROMs.
[Samsung Galaxy Nexus] zofox:
try out supercharger script :D it allows you to bulletproof an app :P
[Samsung Galaxy Nexus] JoSch68:
Hey folks, my new minfree values works very good for me... try it

In Trickster: 2,4,6,12,32,48

Script: 512,1024,1536,3072,8192,12288
[Samsung Galaxy Nexus] osm0sis:
There's a donotkill patch that can be added to LMK that [MENTION=4615478]boype[/MENTION] could commit which allows this. :good:
[Samsung Galaxy Nexus] boype:
https://www.dropbox.com/s/3jyr49h01vnzml8/fancy-kernel_tuna_4.2+_pre50.zip

For for those willing to try ?
[Samsung Galaxy Nexus] cujo6801:
Like I always say

what the hell...

I'm down...

Let me dirty flash ROM w/ new kernel

Sent from the "DOG" pound

---------- Post added at 01:12 PM ---------- Previous post was at 01:00 PM ----------

We have boot w/ 4/14 pac-toro

Now to test...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] siealex:
Any changelog? Can this zip be flashed over r49?
[Samsung Galaxy Nexus] osm0sis:
You see my post regarding the seg faults? :)
[Samsung Galaxy Nexus] cujo6801:
Running smooth so far...

Just tried one of my games

(Mem.hog).

Everything still running.

That's supposed to be..

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Teemoo:
Home button and screenlock pin works as expected now (coming from r45, r49 broke it), pre50 looks good. Memory management looks ok so far. Though the colors look a bit dark/weird than usual. Thanks.

edit1: Can't torrent, after playing around and opening the torrent app, my phone is frozen, restarted itself after ~a minute. after the restart, says system.ui is fc'ed, can't use my phone, restarted.

By the way, I still can't put my screen pin on the first try, I turn the screen off and on, than I can put it, but I belive this is related to the ROM I use, cm11 nighty.

If cm11 = VanirAOSP, yes I am on VanirAOSP.
[Samsung Galaxy Nexus] klobkelosh:
Ditto. So far so good.
[Samsung Galaxy Nexus] nozz93:
I think VanirAOSP is based on CM11 so the bug could be in both ROMs. I had the same problem with the SmittyV kernel so I thought it would be a ROM problem, but you state that the problem is gone in the latest Fancy Kernel. Although I have no idea how a kernel could create such a problem.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] namtombout:
I think you missed the AOSP attached to Vanir

All seems well with pre50 on the latest LS and default minfree. Opened playerpro mxplayer Tapatalk settings and 7zipper no restarts and launcher was not killed
[Samsung Galaxy Nexus] Teemoo:
It might be related to kernel's memory management aspect, I don't know..

Keyguard.apk is doing weird things lately (like for a few months), it doesn't accept my pass on first try, its name is blank/weird/null, it throws ANRs sometimes, even while I am browsing, gaming..

Or keyguard and some kernels simply don't like each other :)
[Samsung Galaxy Nexus] infectedorganism:
With pre50, I'm still having the issue where flashing makes my internal storage inaccessible.

Running Slimbean 4.2.2 build 8.
[Samsung Galaxy Nexus] osm0sis:
Sounds like an fstab issue.
[Samsung Galaxy Nexus] infectedorganism:
Thanks. I'll see if replacing it with my current fstab has any effect.
[Samsung Galaxy Nexus] boype:
Thanks, I did not see. I'll check out the new binaries, since I used the ones from the master package from the thread. I let you know if they work
[Samsung Galaxy Nexus] aamadorj:
Test build pre50 is running excellent with latest Paranoid Android. I didn't change minfree values from the ones built-in.
[Samsung Galaxy Nexus] Loureiro:
Pre50 running like a champ here.
[Samsung Galaxy Nexus] galaw007:
THANK YOU!!!!

Huge shoutout to [MENTION=4615478]boype[/MENTION] and all you other wizz kids, who have the brains, knowledge and aptitutde to make our aging Nexus's run like the wind. As a non technical user (i.e. aging dinosaur) of the Fancy Kernel, I appreciate all of you who know how to "tweak" (i.e. minfree etc) the kernel and get it right for all of us.

I am very patient to sit back and wait for you guys to sort out the little glitches. :good:

Thanks for all your committment and passion, I for one really appreciate it. :victory:

Cheers

Guy
[Samsung Galaxy Nexus] tostep:
Add your app's internal name to list variable at /sbin/fancyinit2 script (for r49). Default value of list is

list="com.cyanogenmod.trebuchet com.android.launcher org.adw.launcher org.adwfreak.launcher com.anddoes.launcher com.gau.go.launcherex com.mobint.hololauncher com.mobint.hololauncher.hd com.teslacoilsw.launcher org.zeam com.chrislacy.actionlauncher.pro com.android.lmt com.tsf.shell com.miui.mihome2 com.qihoo360.launcher com.gtp.nextlauncher net.alamoapps.launcher"

That allows to keep most of the launchers in memory.
[Samsung Galaxy Nexus] Ashtrix:
Can i know are the minfrees on pre50 are same as r49 ? If not please post em :)

Thanks !!
[Samsung Galaxy Nexus] movelbit:
Hi. Regarding the quoted issue, it may be fixed in pre50.

Phone just woke up from a big sleep and it didnt lock at all.

Thanks

Enviado do meu Galaxy Nexus através de Tapatalk
[Samsung Galaxy Nexus] tostep:
r49: "3072,4096,6144,7680,9216,14436".

pre50: "2560,3584,4608,5632,6656,11776".
[Samsung Galaxy Nexus] cujo6801:
Or r50 in trickster

Sent from the "DOG" pound
[Samsung Galaxy Nexus] boype:
Those values are not the secret, though. I changed the kernel boot parameter to vmalloc=496 (MB) instead of the stock 768.

I'm not a mega geek, so finding that this is related to issues with the new lmk was something I had to think about for a bit.

For me personally, my gnex never had such good multi tasking. Your experience may vary, ofc.

Fun fact though: my former lg p970 (gingerbread) had multi tasking that was equally good. But that device only had half the ram the gnex has ;)
[Samsung Galaxy Nexus] SirOch:
Hi,

Thank you boype for this new kernel.

The pre-R50 works like a charm for me.

No more applications which restarted every time like the R49 which take my phone unusable.

My gnex is smooth like butter ;)

Cheers

Envoyé de mon Galaxy Nexus en utilisant Tapatalk
[Samsung Galaxy Nexus] boype:
pre50 now available from the OP

I hope it stays that way. Also, I hope for similar reports from the ones having trouble with r49.

I'll look into this when the lmk issue is fixed, which might be the case now :) Thanks for posting the ROM. Because I'm so lazy, could you please also post a direct link to it?

On another matter: I'll check out the newer mkbootimg / unpackbootimg binaries [MENTION=4544860]osm0sis[/MENTION] mentioned. I really want to make a solid r50 - because 50 is such a nice number for a release :)

[edit]

pre50 is now available from the OP
[Samsung Galaxy Nexus] siealex:
Can I do this with e.g. Skype? Skype is often oom'd when running Browser or Email on top of a video call.
[Samsung Galaxy Nexus] tostep:
I think so. list variable is commented as "low memory killer whitelist for common launchers" at /sbin/fancyinit2 script. Just insert "com.skype.raider" into list variable at /sbin/fancyinit2 script and reboot your device.

list="com.skype.raider com.cyanogenmod.trebuchet com.android.launcher org.adw.launcher org.adwfreak.launcher com.anddoes.launcher com.gau.go.launcherex com.mobint.hololauncher com.mobint.hololauncher.hd com.teslacoilsw.launcher org.zeam com.chrislacy.actionlauncher.pro com.android.lmt com.tsf.shell com.miui.mihome2 com.qihoo360.launcher com.gtp.nextlauncher net.alamoapps.launcher"

P.S. I guess, you also have to change line Don't change this line:

echo -17 > /proc/$pid/oom_adj

to

echo -18 > /proc/$pid/oom_adj

I though it is count of processes in list variable, but really it's a oom class, thank's boype for explanation:
[Samsung Galaxy Nexus] boype:
I'm rather sure this will not be working, because the process needs to be started to be whitelisted. Since the whitelist script executes shortly after boot, you won't have any luck here I suppose (Skype is not yet started).
[Samsung Galaxy Nexus] tostep:
Why are you sure, that launcher was started, but Skype wasn't yet at the moment of execution? Isn't Skype started at boot? I guess Skype has time to start during 20 sec. delay at /sbin/fancyinit2:

sleep 20
[Samsung Galaxy Nexus] boype:
Nonono, don't touch that :) It's the oom class. -17 is "unkillable", -18 does not exist

Okay then... If skype starts on boot, you're probably fine. I don't have it installed and thought that it had to be loaded manually. If you had to do this on every boot, this would hardly be a good solution for the problem.
[Samsung Galaxy Nexus] JoSch68:
Hi,

thanks for this new kernel. :good:

The pre-r50 works really good with vanir-rom-041014.

No more apps which restarted every time like the R46-R49. :D

best regards

JoSch
[Samsung Galaxy Nexus] tostep:
:good: Ок, I got it. Just corrected my previous post.

I don't have installed Skype on my Nexus too. I only guessed, that Skype is autostarted at boot like other messengers (Viber, What's up, etc.)
[Samsung Galaxy Nexus] gautam_nexus:
No skype does not auto start...unitl you login
[Samsung Galaxy Nexus] tostep:
Of course, it starts during every boot. Why does Skype need permission to "Run at startup"?
[Samsung Galaxy Nexus] boype:
Just checked the slimbean 4.2.2 build 8's fstab, there's nothing strange there I guess.

We probably have an selinux issue here. I'll test this later. If that's the case, I'm happy anykernel2 offers a solution via cmdline concatenation :)
[Samsung Galaxy Nexus] gautam_nexus:
only if you are logged in and you rebooted your phone.
[Samsung Galaxy Nexus] pvkiniyan95:
how to set vmalloc via terminal or where to set it, i m planning to try it in dirtyv:p
[Samsung Galaxy Nexus] boype:
you can't. It a hard-coded kernel parameter.
[Samsung Galaxy Nexus] werewolfo:
Well, it came out the notification menu problem, causing the freeze of the device and a reboot (with a system.ui fc), comes from the new theme manager of CM11, not from the r49 of fancy. I flashed the apr-11 nightly to fix that.

By the way, i'm trying the pre50 and the system seems flying with no other fcs, so far.

Thanks to Boype for supporting this kernel!
[Samsung Galaxy Nexus] Alkemix:
I've changed vmalloc value to 496 and LMK problem seems to be solved! Great Boype ! :good:
[Samsung Galaxy Nexus] bsmitty83:
Are you still using the lower minfree values with the decreased vmalloc ?
[Samsung Galaxy Nexus] Alkemix:
echo "2560,3584,4608,5632,6656,11776" > /sys/module/lowmemorykiller/parameters/minfree;
[Samsung Galaxy Nexus] aosp:
[MENTION=4615478]boype[/MENTION] [MENTION=4608636]bsmitty83[/MENTION]

remove hardcoded vmalloc setting from cmdline · 951cba7 · KFire-Android/kernel_omap_bowser-common · GitHub - http://goo.gl/Y57bMX
[Samsung Galaxy Nexus] DR3W5K1:
I added 100mb swap. Lmk issue solved
[Samsung Galaxy Nexus] Grarak:
This doesn't do anything. The device will generate a vmalloc value anyway, which doesn't improve anything