yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] nachiket_xda:
@ boype could it be possible to hardcode these minfree values in kernel itself? Also u can disable crc by default as people tested it.
[Samsung Galaxy Nexus] infectedorganism:
How crucial is the ramdisk to the kernels performance?

I apologize it that is a ridiculous question. I am just curious because I am still on android 4.2.2, using the ramdisk from r36 (4.2.2) while using the latest r45 kernel.

While everything is seemingly running fine, I'm just curious what role the ramdisk plays.

Thanks in advance.
[Samsung Galaxy Nexus] erghetto:
disable crc by default not.. because boype has advised us that could however be some problem for data (losing them). it's rare, but could happen.

so i don't think it's a good idea disabling it by dafault
[Samsung Galaxy Nexus] SoftWord:
All virtual variables from sysfs have a default.....I think that is only a security reason

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] CommanderDuplex:
and you will lost what ??... if you are writing something may it creates an error and you have to repeat the operation , not more ... there is nothing risky on this features , pls enable it
[Samsung Galaxy Nexus] erghetto:
[MENTION=1902369]CommanderDuplex[/MENTION] there could be problem.. so who wants, activate it. why other users have to risk because you want it?
[Samsung Galaxy Nexus] CommanderDuplex:
Yeah :D
[Samsung Galaxy Nexus] erghetto:
lol, now we know your intelligence's level XD

edit:

personally i trust people like Charmacas who know what says and what do. i'm sure that you don't know what crc effects. maybe you have read in some page that is good for performance and now as a baby you want it.
[Samsung Galaxy Nexus] CommanderDuplex:
I`m just kidding ^^
[Samsung Galaxy Nexus] sero86:
hello guys! I've a problem with the latest release,indeed even with the "old"...for the kernel settings I'm using trickster mod,but,even with the extend version of fancy I don't see the toggle for disable fsync!! someone have any suggestion? thanks!

regards
[Samsung Galaxy Nexus] tsabasid:
Anyone here faced severe Bluetooth audio breaks using r13? Tried it, went back to AK and problem was solved.
[Samsung Galaxy Nexus] namtombout:
Did you flash the revert file that is needed when going to a different kernel from ak?

Thanks Boype. Flashing now
[Samsung Galaxy Nexus] ak:
Revert files are for WiFi :thumbup:
[Samsung Galaxy Nexus] agritux:
what do you mean by break?

my english is bad but i try to explain what i facing

while copying a file pc to phone or phone to pc, also sending or recieving a file with bluetooth if music player playing, it plays laggy.
[Samsung Galaxy Nexus] tsabasid:
Sometimes this happens too, but in my case it happens even when the phone is with screen off only playing music or podcasts.
[Samsung Galaxy Nexus] agritux:
yes sometimes it happens too. but is it releated bluetooth? i think it is poweramp (i am using it) or sdcad read speed or etc releated issue
[Samsung Galaxy Nexus] tsabasid:
Hadn't thought of read speed. But when playing just music how much read speed was you need anyway? You think is could be improved by turning fsync off?
[Samsung Galaxy Nexus] TCattd:
Testing.

So far, so good :)
[Samsung Galaxy Nexus] goorek:
After weekend home test, 24h on battery and 4h screen on time, with WiFi and 2g.

I have one small issue - when i unlock phone from deep sleep and turn WiFi on, it gets laggy for one minute. Dunno if it is sync, or fsync, but it is annoying a little bit.

Also, when trying to unlock screen gets black for half a second, and then it shows lockscreen. You can see it in dark room.

What are your CPU temperatures?

Besides that, wonderful work!
[Samsung Galaxy Nexus] bigknowz:
Black Screen

Wondering if this is related to the issue I'm having with super dim screen waking the phone (almost black) and then needing to turn screen off / on for brightness to be normal.
[Samsung Galaxy Nexus] bolanrox:
I know there was an issue with the auto fstrim running when the phone wakes (which cased the same issue), but I have not had it happen for a few versions back now.
[Samsung Galaxy Nexus] goorek:
that's not my main concern, more important problem is the Wifi for me, when you want sth and you turn the phone to check it, it could be unusable for some time.

Also, is the cpu at 58 degrees Celsius when browsing web on 3g a normal thing? and battery at 39 degrees.
[Samsung Galaxy Nexus] gwindlord:
Experiencing the same, but I thought it was ROM auto-brightness settings, and you made me unconfident :D
[Samsung Galaxy Nexus] ciprianruse88:
If you are on a rom that has the new superuser try disable log on superuser and reboot.see then if you get anymore lag when u unlock the screen

Sent from my Shining Nexus using AK DIAMOND ED.
[Samsung Galaxy Nexus] bolanrox:
That is a good idea, I am using SuperSU and have not had any of these issues.
[Samsung Galaxy Nexus] ciprianruse88:
That's why I talked to the dev of Purity rom(my favorite) to keep super su:)

Sent from my Shining Nexus using AK DIAMOND ED.
[Samsung Galaxy Nexus] zoomy942:
Is there a flash able stock kernel from the vzw stock image?
[Samsung Galaxy Nexus] kevdliu:
i think it's just the boot.img. someone correct me if im wrong.
[Samsung Galaxy Nexus] jesssiii:
You could just put the boot img into a flashable zip.
[Samsung Galaxy Nexus] erghetto:
ok, all ok ;)
[Samsung Galaxy Nexus] CommanderDuplex:
Boypes face right now :laugh: :laugh:
[Samsung Galaxy Nexus] cujo6801:
Too funny..... :thumbup:

Sent from the "DOG" pound
[Samsung Galaxy Nexus] paarthdesai:
he might be busy with some personal works.... if he said he will give an update today there's no hard and fast rule on it that he should.. he isn't working in a firm where you need to submit your projects on time or you might be kicked...
[Samsung Galaxy Nexus] pvkiniyan95:
true that
[Samsung Galaxy Nexus] aamadorj:
New version is up. Check OP.

Can't wait to test it!!

Update: new version is working fine with PA 4.2 BETA 3. Thanks [MENTION=4615478]boype[/MENTION].
[Samsung Galaxy Nexus] boype:
r46

... Not even midnight: :p:p

r46 is available from the OP. Change log:

drivers/staging/android: update lowmemorykiller and other android memory management subsystems from hammerhead repo

sioplus: adjust a tunable to play nicer with new memory updates

cpufreq: ondemandplus: add missing 'else if' in scaling code

ramdisk: added script by osm0sis to set minfree values on boot, minfree values made up by myself

ramdisk: added pac framework to prevent FCs

ramdisk: fix renice on boot (input format changed)

The focus in the release is better memory management, which aims to give you a consistently good performance over longer uptimes.

Have fun:good:
[Samsung Galaxy Nexus] RevengeFNF:
[MENTION=4615478]boype[/MENTION] Many thanks for the updated kernel. Gonna try it right now ;)
[Samsung Galaxy Nexus] thomstrack:
After update the minfree values says this, is normal?

Sent from my Galaxy Nexus 4.4.2
[Samsung Galaxy Nexus] boype:
Not cool, thanks for reporting. Will fix tomorrow. Meanwhile, the kernel seems to work just fine, even with a value missing.

However, if you manually do this:

echo 10240,13312,16384,18944,21504,36864 > /sys/module/lowmemorykiller/parameters/minfree

... the phone will be quite a bit faster. That's what I'll be putting in tomorrow's bugfix.
[Samsung Galaxy Nexus] RevengeFNF:
Something is not working correctly with the new minfree values.

I can't use anymore the Live Wallpaper 500px Firepaper for example, it get killed.

I tried Spotify, im listning to a song and after some seconds the song stops cause it was killed.

I go to the Applications Settings and i noticed that most of the apps are being killed, even the Google Service is being killed.
[Samsung Galaxy Nexus] thomstrack:
The value missing is hidden app.

This is the correct values.

Anyway, the new version working very fine! I'll try the new memory management optimization. I used the custom minfree by Nephilim, now I'll try the new default. :)

Thanks for the new great update! ;)

Sent from my Galaxy Nexus 4.4.2

---------- Post added at 07:58 PM ---------- Previous post was at 07:51 PM ----------

Read in last page, be missing one value on minfree. Boype will fixed tomorrow. But if you can change by himself.

if you manually do this:

echo 10240,13312,16384,18944,21504,36864 > /sys/module/lowmemorykiller/parameters/minfree

TricksterMod (need donation)

Sent from my Galaxy Nexus 4.4.2
[Samsung Galaxy Nexus] RevengeFNF:
Ok, i've done that with TricksterMod.

Lets test it again ;)

PS: Test it with the new values and apps are being rebooted.

I can't use Spotify for example.

What are the default Minfree values to put those until this is fixed in the next version?
[Samsung Galaxy Nexus] infectedorganism:
Is there any point in using these new minfrees if I'm stuck using an old ramdisk (r36 - 4.2.2); I am not sure of the ramdisks role. I am using the newest kernel, however.
[Samsung Galaxy Nexus] boype:
I'll fix you an updated ramdisk in a bit. Why are you using 4.2.2? ;)
[Samsung Galaxy Nexus] infectedorganism:
I've had data handoff issues on anything > 4.2.2. I'm hoping that will soon change as I would love to upgrade.

With that said, your kernels perform the best for me so I try to keep up with your development as much as possible.

And, thank you! That would be greatly appreciated!
[Samsung Galaxy Nexus] Godra:
Can I flash Fancy over ASKP since Im not sure ASKP has a ramdisk?
[Samsung Galaxy Nexus] SoftWord:
[MENTION=4615478]boype[/MENTION] have u fixed 46 for new minfree?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] boype:
r47

Hi,

real quick: Here's the fix (r47).

fixup lowmemorykiller derp from r46

Download from the OP.
[Samsung Galaxy Nexus] spirit1002:
Lowmemorykiller kill everything. r47 version.
[Samsung Galaxy Nexus] garyngkt:
I had error after flashing to r47, some calendar storage thing. Home button did not work properly.

I did a reboot and everything seems fine now will continue to monitor.
[Samsung Galaxy Nexus] hardstyle86:
Flashed r47, wiped cache and dalvik and the phone has been very slow and laggy for about 5 minutes.

Now all seems to be OK.
[Samsung Galaxy Nexus] redj12:
Stock calendar ? I have an issue with the back button, with all kernel and 4.4 ROM. So this is not a Fancy bug.

Envoyé de mon Galaxy Nexus en utilisant Tapatalk
[Samsung Galaxy Nexus] revanmj:
Yep, r47 kills too much - for me it practically makes lock screen disappear (after pressing power button Gnex goes straight to launcher).
[Samsung Galaxy Nexus] erghetto:
i'm using r47 on latest beanstalk and all seems to be ok.
[Samsung Galaxy Nexus] SoftWord:
Boype. Why put that minfree values? Leave stock simply

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] paarthdesai:
new version up ...:D
[Samsung Galaxy Nexus] garyngkt:
I think it's better after letting the device settle down for a while. I'm on Vanir ROM. Just did antutu test only getting 10xxx was 11xxx last time
[Samsung Galaxy Nexus] spirit1002:
i use default kernel settings.

the new r47 version kill everything.

this is the dmesg log. the lmk kill a lot

https://www.dropbox.com/s/s6wkwvv01yncyfj/2014-04-06_21.01.zip
[Samsung Galaxy Nexus] drmxmyt:
phoe is really unstable with r47. launcher restarts everytime i unlock the phone..
[Samsung Galaxy Nexus] wasdf:
As the others say, r47 is unstable :crying:
[Samsung Galaxy Nexus] RevengeFNF:
Flashed r45 again. R46 and r47 lmk kills everything.

Even if i put the minfree values from r45 in r47, it kills anyway. So the problem is not on the minfree values but in something else.
[Samsung Galaxy Nexus] Charmacas:
This is normal. The phone needs time after a restart to settle down. Try monitoring your CPU and start to test after it settled.

Because there's space to tune. He integrated some lmk features from hammerhead. Maybe this is to blame.

For me nothing is unstable. Everything is running fine. Thanks boype! ;)

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] erghetto:
same for me :) i've changed from beanstalk to liquid and all is good.

thanks boype :D
[Samsung Galaxy Nexus] RevengeFNF:
Things i noticed...

When i want to write something, swype will take about 5 seconds to load instead of being instant.

If im listening to Spotify in the background, after some minutes the music stops because the process got killed.

My live wallpaper is being killed.

I can see Google calendar service being killed also.

Every app in cache got killed.

Thats not normal... I suppose the new minfree value should kill apps on cache, not everything. It's impossible to use the phone like this.

Ps: I know its not boype fault, andi love is kernel ;)

Ps2: In dirt_v kernel thread I've seen people complaining about this same issue and eventually they sort it out.
[Samsung Galaxy Nexus] boype:
I agree this is not looking very good. I might have to revert the lmk changes.
[Samsung Galaxy Nexus] thomstrack:
The 2 new versions have killed all cache apps. Even changing the minfree values this keeps happening. So I think it is some other change that is causing this.

Sent from my Galaxy Nexus 4.4.2
[Samsung Galaxy Nexus] garyngkt:
I should revert back to r45 first then thanks for everything [MENTION=4615478]boype[/MENTION]
[Samsung Galaxy Nexus] thomstrack:
I went back to version r45 with minfree (wavedashdoc/Nephilim) and for me, this combination is perfect.

With this minfree i have best multitasking ever had!

Foreground App: 10
Visible App: 20
Secondary Server: 100
Hidden app: 120
Content Provider: 95
Empty App: 195
[Samsung Galaxy Nexus] siealex:
195 for empty apps??? I set 128 maximum. Remember, most keyboards and launchers are empty apps.
[Samsung Galaxy Nexus] thomstrack:
I never had any issues with keyboard or launcher. About launcher, I keep Apex always on memory.

The higher value for empty apps reduce rouge apps from staying in background based off infrequent use.

Sent from my Galaxy Nexus 4.4.2
[Samsung Galaxy Nexus] SoftWord:
Back key and home something don't work for me too and kill all....

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Alkemix:
So do I ... uhmmm I thought it was the rom but instead the culprit is the kernel... r45-pre2 better release for me...

something into lowmemorykiller doesn't work well ...
[Samsung Galaxy Nexus] SoftWord:
In fact I'm on latest 45:)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Godra:
Fancy r47 forgets all my Wi-Fi passwords after every reboot :( But I switched to franco so I cant post any logs, sorry boype
[Samsung Galaxy Nexus] aliesz:
I think everybody is agreed with me that r46 and r47 are not working as well as r45.
[Samsung Galaxy Nexus] Merio90:
r46 was a disaster. I think something was broken in the kernel or something. I flashed r46 last night with CM11 M5 and my music player would just get killed after several seconds. My launcher would also restart ever time I would press the home button from another app. I thought it was the ROM but it turned out to be the kernel. Hope this gets fixed soon, this is one of the better kernels.
[Samsung Galaxy Nexus] erghetto:
well.. back to r45 waiting for a fixed release. however thanks boype for your work :D
[Samsung Galaxy Nexus] boype:
I'm on it and already found the issue responsible. Sorry for ****ty releases
[Samsung Galaxy Nexus] klobkelosh:
No worries boype. We can take it! We all appreciate your efforts!
[Samsung Galaxy Nexus] ashclepdia:
thank you for this info, I never knew that before, very useful to know!

---------- Post added at 02:52 PM ---------- Previous post was at 02:50 PM ----------

we will never find better things if we dont wade thru the stuff that doesn't work first.

never apologize for trying new things, EVER
[Samsung Galaxy Nexus] shag_on_e:
I really enjoyed the bigmem builds for the simple fact I never had lag issues. Every kernel I've seen with these new minfree settings has had some strange stuff happening constantly. I am all for new things though and always support development for the greater good. I love fancy kernel, turns for the work boype

~~~~There is no spoon~~~~
[Samsung Galaxy Nexus] boype:
Thanks man :)

Just a few lines to explain what is going on:

As you all know, I implemented an update for the lowmemorykiller, which is a key component for system performance of android kernels.

I took a closer look at the updates. They improve the logic of evaluating the current state of memory occupancy at the time a process is selected to be killed. The changes are not just "some minor optimizations". In my opinion, the whole new lowmemorykiller routine is _way_ better and more effective than before.

Now the problem is this: the minfree values we used to set prior the update DO NOT translate to the ones we need after the update. minfree has to be set to considerably lower values, approximately only 1/3 of the values we used to have. But if done right, the new LMK kicks major ass. I'm still testing a few things, but I think I'll have the most important part figured out.

So as you may already have understood, the current minfree values are too high, causing all kinds of processes to be killed. Because the phone tries to load them again and again every time it needs those processes, everything is slow and jerky. Also foreground apps are killed because of this.
[Samsung Galaxy Nexus] ashclepdia:
yea from the screen shot someone posted of their running apps I had figured that apps were having some issues staying up.

it reminded me of how it looks and behaves if you mess with the "background process limit" in dev settings. and also this past week I was trying to actually force that same exact situation to happen by ramping up my minfree values via trickster to insane values(300+400s for EACH LOL) and saw that same exact thing happening paired with major lags(all of which I expected due to values entered)

I think I might flash that latest one you have up that has this new lmk changes and play around with different values to see what happens.

thank you not only for the information on WHAT happening, but ALSO having the mindset of wanting to see WHY it didn't work and digging deeper instead of just "it didn't work, I'll just revert and forget it". THAT is greatly appreciated by everyone I'm sure
[Samsung Galaxy Nexus] boype:
r48

... is up. I hope I got it right. Tell me if there's still apps closing when they shouldn't.

From my point of view, the trouble was worth it :)

I'll upload sources tomorrow. Good night
[Samsung Galaxy Nexus] agritux:
Boype, you are amazing!

One day 3 build. You never gave up! Thanks. Flashing now!
[Samsung Galaxy Nexus] infectedorganism:
Could someone post the minfree values from this latest build? I won't know what they are otherwise.

Thanks in advance.
[Samsung Galaxy Nexus] agritux:
it says it is donate version feature

i didnt bought trickster mods

sorry

but it is working fine

there is no bug which is present in r46 or r47
[Samsung Galaxy Nexus] motorazrv3:
Just flashed latest kernel. Booted fine. Here are the values and ram management right after first boot.

No issues so far. Kernel feels great.

Thx boype.

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] aamadorj:
So far, I haven't seen any of the problems that were notorious with the previous version (r47). All apps in my device are behaving as they should.

Thanks for all your hard work, [MENTION=4615478]boype[/MENTION].
[Samsung Galaxy Nexus] ashclepdia:
was the ONLY change in this latest version the hardcoded minfree values? just curious if you had to tweak anything else also :D [MENTION=4615478]boype[/MENTION]

edit::

also, thanks of course AGAIN and hope ya get some good sleep(aka turn OFF notifications cuz we all just keep mentioning you anyways lmao)
[Samsung Galaxy Nexus] Alkemix:
echo 3072,4096,5120,6144,7168,12288 > /sys/module/lowmemorykiller/parameters/minfree;

Trickster (minfree) ... order from top to bottom:

12

16

20

24

28

48
[Samsung Galaxy Nexus] RevengeFNF:
I made the same test that I did with the previous two versions.

I opened a lot of apps, including chrome and facebook, and then started Spotify.

I'm listening for about 10 minutes without any problem. Lmk is not on a rampage killing, it's only killing some cache apps.

I will test further, but for now everything seems fine.

Many thanks Boype, for your dedication :)
[Samsung Galaxy Nexus] wasdf:
r48 seems not longer killing anything, thanks Boype :fingers-crossed:
[Samsung Galaxy Nexus] garyngkt:
Yeah so far things are much better on r48 :good:
[Samsung Galaxy Nexus] ashclepdia:
hmm

I just took a looksie at dmesg, noticed huge chunks of repeating error that was mentioned lately in dirtyV thread, the omapdss dispc sync_lost errors.

am I the only one getting this? is this known? I'm not experiencing issues though that I've noticed at least(no lags or anything out of ordinary)
[Samsung Galaxy Nexus] shag_on_e:
Wow, 48 is freaking amazing! LMK seems to be killing junk off nicely without killing SystemUI or anything important. Tons of free RAM consistently with no lag and great gameplay. Good stuff here!

~~~~There is no spoon~~~~
[Samsung Galaxy Nexus] tostep:
r48 is slower than r45

Hm... I found out, that Subway Surfers on r48 is a little bit slower than r45 (on CyanogenMod 11 M5).
[Samsung Galaxy Nexus] revanmj:
I can also confirm that r48 is working really well. Good job!
[Samsung Galaxy Nexus] swedkg:
r48 is awesome on Shiny Rom , as was r46 actually :)
[Samsung Galaxy Nexus] SoftWord:
[MENTION=4615478]boype[/MENTION], please I have send u a private message.
[Samsung Galaxy Nexus] xmaciek82x:
Seems like viper4android and dsp is getting killed while being used. Anyone what having this issue? Seems like all the newer kernels I tried do this. Older ones did not.
[Samsung Galaxy Nexus] SoftWord:
Mmmmmmmm, I think that kernel kill everthing........my PROCESS CACHE is empty, is right ?
[Samsung Galaxy Nexus] Max94h:
I've the same problem, all the apps get killed even the launcher and keyboard... For now I reverted to r45

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] erghetto:
flashed r48 and all seems ok now. cache process are always there
[Samsung Galaxy Nexus] JoSch68:
After flash all seems ok, but now more than 12h on R48 - the same problem, all the apps get killed and restarted even the launcher and keyboard...

For now I reverted to r45

Best regards
[Samsung Galaxy Nexus] DR3W5K1:
Does this kernel have hotplug governor?
[Samsung Galaxy Nexus] RevengeFNF:
Im not having that problem.

Here is mine:
[Samsung Galaxy Nexus] DR3W5K1:
Figured it out
[Samsung Galaxy Nexus] Merio90:
r48

Still a work in progress. Launcher (Go Launcher Ex) keeps getting killed. Tons of free ram but some apps wanted or unwanted are being stopped, no worries though Boype take your time with this one. I'll just flash DirtyV in the meantime.
[Samsung Galaxy Nexus] boype:
I guess I need some days to figure out the correct lmk settings. If you want to help: lower minfree and test if the new values are any better
[Samsung Galaxy Nexus] SoftWord:
r48 problems found for me:

* battery drain: after 10hours ramain only 32%

* kill all

* random reboots in this 10 hours

I'm try nephilim minfree values now
[Samsung Galaxy Nexus] infectedorganism:
Read the post above yours by boype. We will need to lower the deafult minfree vaules from r48. Looking at Nephilim's settings, those minfree values are too high and will cause the problems you are experiencing to worsen. If I am wrong, I apologize. I'm just trying to save you a potential headache.

With that said, while I am experiencing minor issues such as apps restarting and no/minimal cached apps, this is the best my phone has ever ran. Even while still running the r36 ramdisk, I am pleased with the performance and battery life thus far. Thanks, boype!

I am currently testing some lower minfree values and hope we all can find the right ones to eliminate these minor problems.
[Samsung Galaxy Nexus] redj12:
ROM ? I am on SlimKat and r48 with all stock settings. The battery life seems good and there is no reboots or kill app.

Envoyé de mon Galaxy Nexus en utilisant Tapatalk