yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] shadowam:
Hey bsmitty83, sorry to be the noob, but could you or someone else with knowledge explain a little more about this? Which file do I need to edit to put the process I want on the whitelist?
[Samsung Galaxy Nexus] bsmitty83:
the files are under sys/module/lowmemorykiller/parameters/

in "donotkill_proc" set to 1

in "donotkill_proc_names" add whatever proc you want , eg. "com.android.launcher" , "com.cyanogenmod.trebuchet"

im still learning the whitelist myself but thats how I know it to be

Edit there is also the same 2 files but for system processes that you want whitelisted as well , like system.ui
[Samsung Galaxy Nexus] osm0sis:
I think commas in between is all you need. :good:
[Samsung Galaxy Nexus] zzpianoman:
where did you get your lowmemorykiller module with the whitelist?
[Samsung Galaxy Nexus] bsmitty83:
https://github.com/bsmitty83/Kernel_Tuna_AOSP/commit/d9b6d83cd4d032e8cab8fc6aa749f65993a579a9
[Samsung Galaxy Nexus] zzpianoman:
Awesome. I'll have to try this out.
[Samsung Galaxy Nexus] Syakir Imran:
Anyone got problem with fml??? hmm after I turn on my gnex until at the homescreen/lockscreen and need to wait around 2 minute to start all things and set on boot kernel setting (It kernel problem or ??? ) anyone pls suggest me good setting for fml/full auto kernel/trikster
[Samsung Galaxy Nexus] Rushead:
Lol!

I love the South
[Samsung Galaxy Nexus] PainFly23:
The wait time for processes to start is normal, and the delayed application of the kernel settings is actually intended. In case you accidentally set bad settings that would normally bootloop your phone, you have time to go change the settings before they're applied.

As far as good settings go, most people have been using Nephilim's, myself included. You should be able to find them pretty easily in this thread or the toro FML thread.
[Samsung Galaxy Nexus] Syakir Imran:
Can you give me a link .. I found but it 4.4 Below ..
[Samsung Galaxy Nexus] Nephilim:
http://xdaforums.com/showpost.php?p=57955568&postcount=12928
[Samsung Galaxy Nexus] trzesickipiotr:
Do we need to set permissions to 0755 for these files? Are they write only same like for adj and minfree ?

PT
[Samsung Galaxy Nexus] bsmitty83:
No , only the 2 files are set write only. The whitelist isn't stock south permissions are fine
[Samsung Galaxy Nexus] trzesickipiotr:
Strange... I can't load them into editor (I'm using Text editor from Astro File Manager). Maybe, I'll try another editor app...

PT

Edit: It was the Text editor. I've managed it with Root explorer editor.

Testing now...
[Samsung Galaxy Nexus] Scandy:
[MENTION=4608636]bsmitty83[/MENTION] I was using Leankernel for a while in the past. There was one interesting governor called "hotplugx". But I see only regular hotplug in your kernel.

So, could you tell the difference between these two governors?

Is it truth, that hotplugx is much effective (to the battery) than a regular governor?
[Samsung Galaxy Nexus] bsmitty83:
I doubt it , maybe a little , but I think we have enough governors , especially when most use interactive or on demand , it sounds like a hotplug gov with early suspend .
[Samsung Galaxy Nexus] CoDe LaZaRuS:
Off topic but i really need to buy a new battery for my Galaxy Nexus gsm i9250

I am not looking for oem replacements but extended battery of about 3500 (the higher the capacity the better) mah or more from 3rd party manufactures.

I want a battery which will last a long time not a cheap chinese knock-off. Nfc dosent matter cause i dont use it and probably never will.

Also I am also looking for an external charger cause i will keep more than one battery. I've had a bad experiance with cheap external chargers destroying my batteries :(

Since amazon and ebay dont ship to my country I am going to use an importing service which will add to the costs. So i want my first experience buying online to be good

Amazon links are preferred and thanks in advance
[Samsung Galaxy Nexus] JST99:
[MENTION=4608636]bsmitty83[/MENTION]

Thanks for the great kernel. I have had no problems so far.

I would like to make 2 suggestions though.

1) Diverse options (BigMEM and what not) once kernels get stable.

2) Touch control, such as Double Tap to Wake. Our device is old, and its hardware is running out. For example, my phone's power button works only when I press it hard. This is not merely a matter of convenience but a matter of maintaining hardware.

These are some little suggestions. Again, thanks for your work and hope you consider them. It would be really appreciated :)
[Samsung Galaxy Nexus] hardstyle86:
I know it is a deprecated app, but is there any possibility to have TouchControl working with this kernel?

Thanks.
[Samsung Galaxy Nexus] tiagofernandex:
You can enable wake with the volume buttons, i use it a lot.

But yes, double tap to wake will be great ;)
[Samsung Galaxy Nexus] RW-1:
Hi all, hope everyone's day has gone well.

I'm stable, though I have to admit I decided on westwood and sioplus (because my phone was liking this on mpokang and fancy).

Of course as I say this I realize I rebooted on purpose and didnt have kernel settings applied, have to re-setup.

But, so far, it flies, until; I try to do anything in chrome or chrome beta, especially opening this site for example, and upon getting chome not responding after a bit, I get a light flow crashed message as well.

If I stay off the browser, I don't seem to get into as many lag issues, but it could be me, thoughts?
[Samsung Galaxy Nexus] bsmitty83:
Chrome is definitely a known resource hog . I notice the same besides the anr toast you get , I personally use zram for this single reason , I believe it helps , minfree tweaking will probably help as well as memory management updates , but I think chrome will always suffer on a one-gig of ram device .
[Samsung Galaxy Nexus] bsmitty83:
Touch control is a closed source app , the developer used to use peoples open sourced kernels to build his kernel modules , not the other way around. I've done everything I can on my end to try to make it compatible ( which isn't a lot that can be done ) so barring a new touch control interface or new builds from the dev , you won't be able to use touch controls with this kernel .
[Samsung Galaxy Nexus] bsmitty83:
Its still not f2fs compatible tho , so be sure you are on full ext4 if you use it . I'll try to build us one that is
[Samsung Galaxy Nexus] zzpianoman:
TouchControl works with my ROM/kernel - but I'm using the older GPU drivers.
[Samsung Galaxy Nexus] jguerdat:
Thank you! I've whined about this for some time with no luck. It doesn't matter what browser I use - stock, Chrome or Firefox. They all do the same thing. I can get a few pages and then things slow down to pull-the-battery time. Stuff in the notifications disappear but at no point have I seen less than about 150-ish MB free. My app I use to monitor cpu and memory disappears, too, so I'm not sure what happens after that.
[Samsung Galaxy Nexus] christianpeso:
Try Naked Browser:

https://play.google.com/store/apps/details?id=com.fevdev.nakedbrowser

Very light on resources and gets the job done quick.
[Samsung Galaxy Nexus] motorazrv3:
Sad to read! Has the KK to LP kernel changed so much that TC isn't compatible with none of the modules? I had always luck with cm11 module from TC.

No I haven't tried myself. Still on KK.
[Samsung Galaxy Nexus] Airlibik:
[MENTION=4608636]bsmitty83[/MENTION] and what about this one?
[Samsung Galaxy Nexus] jguerdat:
Thanks. So far it seems to be fine. However, it begs the question as to what's so broken that causes the mainstream browsers to barf so badly.

Edit: Naked is doing the same thing, just a bit less. Notifications are occasionally missing but come back more quickly. It's usable but not right.
[Samsung Galaxy Nexus] zzpianoman:
Mainstream browsers are insanely bloated and require a ridiculous amount of resources to run properly. Why? Who knows.....there are a ton of both technical and philosophical explanations for it, but no need to bring down the mood!
[Samsung Galaxy Nexus] jguerdat:
Ok but why no issues in KK, only in Lollipop?
[Samsung Galaxy Nexus] CYoung234:
Still boot looping......

Bsmitty, thanks for all of the hard work on our almost 3-year old device! I must have a phone with a hardware problem though, as I still cannot get your kernel to boot with either FML or CM12. In the old days, I had the same type of problem with Android 4.1. I could always run Franco kernel, but could never get Trinity to work.

What I am seeing is the same, stuck at the Google logo, or boot looping there. For the CM12 variant of your kernel, I removed the file from /system/lib/modules as instructed, but no change in behavior. Is there any type of configure file that I can edit from TWRP, or is there a way to capture an error log from TWRP to show what might be happening? If not, I will just be content to keep using the stock kernels, I guess.....

Edit: my device is maguro, and even on Franco kernel in the past, it had trouble above 512 MHz. So, I guess from an overclocking standpoint, my phone has always been a dog.... Reliable phone, though.
[Samsung Galaxy Nexus] lrochfort:
[MENTION=2853378]Nephilim[/MENTION], your Lollipop specific settings are working very well for me on my maguro with the exception of undervolting by 25; things got very choppy then!

Could you please tell me what the benchmarking app you're using is, and how to interpret the results? How much deviation from what you show on your posts is considered normal?
[Samsung Galaxy Nexus] JST99:
This is mere speculation, but the boot loop may be occurring due to the default GPU frequency, which is 512MHZ. So if your phone doesn't like 512HZ, that might be causing the boot loop.

EDIT: Thinking about it again, I'm not sure if the default is set to maximum frequency. Someone correct me if I am wrong.
[Samsung Galaxy Nexus] Nephilim:
At work right now. Will help you out when I get home if someone else doesn't beat me to it. :)
[Samsung Galaxy Nexus] CoDe LaZaRuS:
Yea undervolting by 25 caused choppy performance for me too and the name off the benchmark app is antutu
[Samsung Galaxy Nexus] Syakir Imran:
Anyone got problem hot problem?? (trickster and using hand to feel the temperature really hot) my battery 48 celcius my cpu 52 - 60 celcius
[Samsung Galaxy Nexus] lrochfort:
Thank you, [MENTION=5106132]CoDe LaZaRuS[/MENTION] and [MENTION=2853378]Nephilim[/MENTION].

Setting the MPU voltages back to normal caused my immediate problem, however I find that the phone is really only usable for about 2-4 hours, whereupon the responsiveness such as responding to touch and switching between apps degrades to a point where it's pretty much unusable by 8 hours uptime.

Do you guys have the same thing happen? Any suggestions?
[Samsung Galaxy Nexus] Heart1010:
+1 exactly the same here on my device unfortunately (also when I don't undervolt) :(

I also tried to not undervolt and set GPU to 386... but again very laggy responsiveness after a few minutes / an hour or so.

It must be something else which causes this laggy responsiveness in Nephilims settings on some devices.

(with default R5 kernel settings I don't have that big laggy responsiveness but in comparison with FML default kernel the R5 kernel with default settings is at most as fast as FML default. I would say R5 default settings are a little bit slower then FML default here on my device...)
[Samsung Galaxy Nexus] smiskkissen:
Same for me. Unusable arter an hour.
[Samsung Galaxy Nexus] Fenix46:
I tested the kernel f2fs, with full auto R1 performance is good, but with the full auto r5 performance are higher by at least 20% ... I use my ROM version compiled from source FML...

[MENTION=4608636]bsmitty83[/MENTION] one questions... When I flashed my version ROM compiled with the latest version of your kernel, why go into bootloop in f2fs? Should be equal to the full auto r5, I'm wrong? In Ext4 no worries
[Samsung Galaxy Nexus] bsmitty83:
I'd have to see a last_kmsg to be sure , but I'm using R5 with f2fs on data and cache no problems
[Samsung Galaxy Nexus] Fenix46:
I understand, however, I also am using the R5 version with the cache and data in f2fs problems and not even I ;)

EDIT: Perhaps the problem and the RAM disk, I would try to join the RAM disk kernel R1 with the R5 version that I compiled with the ROM, when I place the PC, because yesterday and burned the HDD And I lost all my work :((
[Samsung Galaxy Nexus] bsmitty83:
The ramdisks should both be the same from r1 to r5 , they are just the stock FML ramdisk. So there must be something else giving you troubles .
[Samsung Galaxy Nexus] lrochfort:
That's a good point. I should say that even when I don't undervolt I get degrading responsiveness with [MENTION=2853378]Nephilim[/MENTION] settings.

I haven't tried comparing an untouched R5 kernel with default FML kernel. Do I just flash boot.img from the FML thread to install the FML kernel?

EDIT: I just ran an AnTuTu test and when using Nephilim's settings on R5 I got 20233, however with stock R5 I get 14213. So it would seem that whilst a dumb horsepower/throughput benchmark gives better results with Nephilim's settings, real world responsiveness is much better with stock R5

EDIT: Of course, this is just on my particular UK gsm maguro.
[Samsung Galaxy Nexus] Fenix46:
then I do not know what can be...
[Samsung Galaxy Nexus] xaifer:
U're using R5 with f2fs on data and cache with CM12 or FML?
[Samsung Galaxy Nexus] Nephilim:
Wow, none of you know how to read apparently, 4 posts I've seen of people crying about my settings not being fast after ONLY AN HOUR!!!! If you are so impatient as to judge my settings after an hour then just go back to stock kernel and be done with it. You have to give far more than an hour for a kernel or settings to settle. My settings have no slowdown for me at all besides sh*tty chrome, which always causes a problem.

Seriously, I have bit my tongue for too long, it pisses me off to see that the hard work and time I put in on my free time is thanked by people whining after only an hour of use, especially when I just posted a comment stating you have to let the settings have time to settle to see proper results.

Maybe from now on I'll just keep my settings to myself.

P.S. redraws and lag are going to happen on occasion no matter what with lollipop, we do not and will not have the proper drivers for our device and it only has one gig of ram, if you are looking for a perfect experience go back to Jelly Bean or get a new device.
[Samsung Galaxy Nexus] Heart1010:
[MENTION=2853378]Nephilim[/MENTION] If you mean me... you missunderstand me... what I've tried to tell is, that when using your settings everything is perfect after a reboot for about a few minutes (until max an hour) and then my maguro gets really unresponsive/laggy. (e.g. a simple touch to the display to click a button is taking sometimes >30s for it to be executed). As said I've also tried to not undervolt and set GPU to 386... with no effect (and I had this settings active for >1 day).

So I tell this in order to "be a help for you" (I respect your work!) because as you see it looks like there are maguros out there which have such problems with these settings. So I'm trying to help to find usable settings for such devices too.
[Samsung Galaxy Nexus] Nephilim:
Dude, I just said it a second time in my last post, you cannot just give it a couple minutes to an hour and judge, let the settings settle for like half a day without rebooting and then see what your results are, I understand most of the issues are coming from those using maguro but that is also the case with people having issue with simply using Smittys kernel, which leads me to believe maybe maguro just isn't perfected on the kernel side in general. Either way, Smitty's kernels for lollipop and my settings are almost always a work in progress and Lollipop has only really been available as daily driver on the Gnex for a few months so there is still a ways to go on improvements and refinements.
[Samsung Galaxy Nexus] Tolazace:
CM12 with this kernel and Nephilim's settings works perfect o.O It's very smooth but settings not save after reboot :/ I tried Tricked (donate) and Kernel Adiutor but default settings restore after reboot :/
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4608636]bsmitty83[/MENTION] where is the gpu oc control? /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc is missing, as is gpu_cur_freq.
[Samsung Galaxy Nexus] Heart1010:
...as I said

The problems begin after a few minutes up to an hour and don't stop although I had that settings/phone present/active for >1 day. (english is not my native language so I hope now it's clear what I'm trying to tell ;))
[Samsung Galaxy Nexus] lrochfort:
Hi [MENTION=2853378]Nephilim[/MENTION]. I've tried your settings on my maguro all week, rebooting in the morning and leaving it all day, and my experience is that the phone is fine for around 4 hours uptime, but from that point on responsiveness goes down until around 8 hours uptime when it becomes unusable. I don't use the phone for browsing personally, so we're talking gmail app, a couple of forum browsers.

Please understand we're not complaining, we're very much appreciative, it just seems that there is something funky with some maguros and your settings and we're trying to figure out what it is.
[Samsung Galaxy Nexus] Nephilim:
There has to be some sort of memory leak going on with maguro, it's the only thing I can think of that would slow down the device after continued use but have it work well again upon reboot. Although, just like with my real computer I reboot once in awhile and use a cleaner to remove junk, free ram and block constantly restarting apps. This may also be a factor. I noticed that I had a bit more lag before I started using cleanmaster to block apps from restarting constantly I have 19 apps blocked right now and they still function properly but the don't keep waking my device for no reason, which means less resources used and better battery as well. Its also good to clean the junk. Anyone that has a regular PC will know what I mean, on my regular home computer I usually clean up to about 3gb+ of useless temp files, cookies and cache once a week from casual use. On my Gnex its between 80mb and 150mb a day.

Maybe take those things into consideration.

Also, I'm working on my settings once again, running them on sioplus for a bit to see how much that works out since I've seen some good comments about it. Also a few other changes that I may or may not announce depending on if they yield positive or negative results.
[Samsung Galaxy Nexus] pkgnex:
I don't think it is Neph's settings specifically that cause the lag... I get this after extended up-time with any settings, on both FA kernel and the stock FML one. I just reboot my device when it gets laggy - it takes 3 minutes out of my day, tops. I personally think it's the infamous "memory leak issue" that blew up the Google issue tracker and is supposed to be fixed "in a future release" (rumored to be 5.0.3 or 5.1) which is causing these issues.

So, just hang in there, guys! I think everyone needs to take a deep breath and relax... as Neph said, we're running a software version 2 full generations newer than anything our devices were designed to support.
[Samsung Galaxy Nexus] bsmitty83:
Good question buddy , I never added the sysfs hooks that we used to need for the GPU oc , since it was already present in the new ddk , I just added the 512mhz slot again . if I add the sysfs stuff back it will be a duplicate check box in Trickstermod
[Samsung Galaxy Nexus] osm0sis:
Ah cool, how does Trickster hook it if not through sysfs? Is there a command line we can use for init.d scripts?

It'd be cool to get the gpu_cur_freq back to match the iva one at least. :)
[Samsung Galaxy Nexus] bsmitty83:
Definitely on my to do list [emoji13]
[Samsung Galaxy Nexus] osm0sis:
So is it like a command sent to pvr that would lower the oc or what? :confused:
[Samsung Galaxy Nexus] bsmitty83:
Well there is this file that's new

https://github.com/bsmitty83/Kernel...fml/drivers/gpu/pvr/omap4/sgxfreq_userspace.c

As well as the sysfs stuff that used to be defined in omap2plus-cpufreq.c is now defined in drivers/gpu/pvr/omap4/sgxfreq.c so its still sysfs , and I don't know where the path is , if at all . I never looked hard at it , but like I said its on my to do list , as soon as I can sit down behind my laptop lol
[Samsung Galaxy Nexus] osm0sis:
Thanks! Founds it: /sys/devices/platform/omap/pvrsrvkm.0/sgxfreq :good:
[Samsung Galaxy Nexus] bsmitty83:
Thank you for bringing it up ,I've been so busy lately working on crypto I Havent looked at stuff I noticed before but forgot about . right now I'm trying to figure out why my sdcard isn't being located by the downloads .apk , or any other app like camera etc. Only it works through a root browser or adb . good thing I haven't let this one out in the wild yet
[Samsung Galaxy Nexus] RW-1:
Neph,

Calm down, I'll buy you a drink of hemlock .... :) As I've been told in my IT side of the work I do, it's not personal, nor a personal attack on you if it isn't working out as well for us as you. (No one ever seems to try to make it personal in the heli, it's not like I'd toss em out or .... :) ) But I know how you're feeling, you do great work and the negatives are hard, but it isn't you my friend. No one has come in here saying that you suck, far from it, they hope you plunked the magic twanger (find that reference smitty, Ghoul anyone? :) ) and they want a piece of it.

Assorted musings:

I've had the same experience as most others, after a bit it just drags, and have left it on, problem is that for some of us by the time 8 hours hits on it, you have to batt pull or you want to throw the phone into orbit hehehe ...

For myself, I'm playing with fire, if a small explanation on making minfree adjustments or a good link to it (are higher numbers better, or the thresholds, etc) could be posted

I might be coaxed into playing with them, as it is since I have no clue, I leave them at your settings. Since I don't know, I don't want to make them worse.

Chrome, while I totally agree it is a resource hog, it lived in the last KK iteration ok, so what is different here?

Also, I'm on ext4, not F2FS, really from ignorance, don't know how to set it up beforehand, and never thought about it.

I also agree with PKG, because after looking at Trickster when my phone felt really hot, it wasn't reporting it was that hot, and that large mem leak could fit the bill , depending...

Besides we're all awaiting MW's latest, if we could lose that damn charge light ..... Lastly, for guys like you and I. the N6 might only be less than a month away, then we can complain about lollipop and encryption removal, lost storage space, possible burn in at an early time, networking issues, and the ever popular "It's so damn big that I ________" :)

No matter the frustration, no matter what - I'm not taking my GNex back to KK, because the end result as we move forward is totally worth it, and why we all do it in the first place.
[Samsung Galaxy Nexus] osm0sis:
I had that happen before with permissions issues and f2fs failing to mount it.
[Samsung Galaxy Nexus] bsmitty83:
Well all I can say is that android 5 is a major version change. It will take time to have it work correctly , no matter what device it is . look around other device threads , you will see most devices suffer exactly what we are .

I've never gone back to an older version of android , ever . I'm not gonna start now. I'm sure that most of the major issues will be resolved . I'm very happy with how the gnex has handled lollipop so far . to me the major issues are more of annoyances than anything
[Samsung Galaxy Nexus] bsmitty83:
Yea and I just switched back to f2fs too. I hope its not the commits I made for crypto ,I don't want to revert them . I got some cool features backported and as long as I can get sdcard fixed I'll leave it .

.

If you remember ,What did you have yo do to fix the issue ?
[Samsung Galaxy Nexus] osm0sis:
I ran my sdcard Fix Permissions Script zip to make sure everything was media_rw, etc. Pretty typical issue if you adb pushed your sdcard contents back on.
[Samsung Galaxy Nexus] bsmitty83:
Ahh lol , yep sure as $h!t , I forgot all about adb pushing my data back .......lmao I'm losing my mind