yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] boype:
r30 available now

Hi all,

thank you for staying with me and reporting and testing things out. Here's the result. I hope it's good.

Change log:

updated to Linux 3.0.81

increased display brightness by 5% (previous values were a little too dim for outside-usage)

control groups (cgroups): make systemui real time, move kswapd to a cgroup with less cpu shares and rt runtime (smoother experience with long system-up-times)

launcher whitelist: fixes on kernel level to make launcher truly unkillable

ondemandplus governor: implement adaptive timer_rate (save some battery in continuous low-usage and idle?!)

reverted to bfqv5 i/o scheduler (v6 was unstable)

applied proper bfqv5 tunables (thx thanks pkgnex & Khrushy from Franco dev team and sajty for telling me)

enabled CFQ i/o scheduler

WiFi drop fix from terminal (disable WiFi first, then type 'fixwifi' in terminal; reverted automatic WiFi suspend drop workaround)

updates from CM10.1 RAMDISK

some other small improvement(s)

Let's see how it goes! I'm quite satisfied so far.

Best regards
[Samsung Galaxy Nexus] boype:
Knowledge base: launchers on the whitelist (-> unkillable)

Yet another post to be linked to the OP. Here's the list of whitelisted launchers and some information on what whitelisting does.

What does the launcher whitelist do?

The launcher whitelist makes your launcher unkillable, so that it won't be 'thrown out of memory' when you are running other memory-hungry apps. This is supposed to effectively eliminate that the launcher has to be re-loaded when returning to the home screen.

Launchers on the list and their process names

360 Launcher (com.qihoo360.launcher)

Action Launcher Pro (com.chrislacy.actionlauncher.pro)

ADW Launcher (org.adw.launcher, org.adwfreak.launcher)

Android Stock Launcher (com.android.launcher)

Apex Launcher (com.anddoes.launcher)

GO Launcher EX (com.gau.go.launcherex)

Holo Launcher (HD) (com.mobint.hololauncher, com.mobint.hololauncher.hd)

LMT Launcher (com.android.lmt)

MiHome Launcher (com.miui.mihome2)

Next Launcher (com.gtp.nextlauncher)

Nova Launcher (com.teslacoilsw.launcher)

Trebuchet (com.cyanogenmod.trebuchet)

TSF Shell (com.tsf.shell)

Zeam Launcher (org.zeam)

Do you want to disable the whitelist?

This can be helpful if other apps close, even if they shouldn't (like running media players or games).

In a terminal, do this:

su
touch /data/nowhitelist

This will create an empty file named 'nowhitelist' in /data. If this file is present, the whitelist will not be applied. The file will remain in place, even after boot. So you only need to do this once, unless you wipe your /data partition.

Want your favorite launcher added? Do this:

Open a terminal, type

ps -p

Look out for the process name of your launcher and post it in this thread. I'll add it in a future release then.

Best regards

P.S.: Sorry for double post, but I wanted this information seperated.
[Samsung Galaxy Nexus] n2rjt:
Give a man a fish, feed him for a day.

Teach a man to fish, feed him for a lifetime.

How could we add our own launcher etc to the whitelist?
[Samsung Galaxy Nexus] stuffynet:
How long does the reboot takes? 5 min and still the bootanimation.
[Samsung Galaxy Nexus] apophis9283:
This is the finest kernel I have ever used on any phone. I recommend this to all the users of my AOKP kang.
[Samsung Galaxy Nexus] pcphobic:
Thanks for the update. Will flash R30 now!
[Samsung Galaxy Nexus] boype:
Create an init.d file with this content:

#!/system/bin/sh

sleep 30

procname=YOUR_LAUNCHER_PROCESS_NAME_HERE

if [ $(pgrep $procname) ] ; then
pid=$(pgrep $procname)
until [ -e /proc/$pid ] ; do
sleep 1
done
echo -17 > /proc/$pid/oom_adj
chmod 100 /proc/$pid/oom_adj
fi

There have been reports of times up to 20 minutes. I know it's long :) Typically it takes like 3 - 10 minutes.
[Samsung Galaxy Nexus] not balanced:
I agree, I have tried just about every ROM and/or kernel combo for the Nexus and this kernel is the best. Snappy performance and great battery life all wrapped up in one package. Thanks Boype for all your hard work!
[Samsung Galaxy Nexus] sajty:
I hope,that users of BFQ will be satisfied.

Thanks for that.

Is recommended to execute this command?

Strange.I have never had longer booting time than 2-3 minutes (even after flashing ROM),common booting time is definitely shorter than 1 minute.
[Samsung Galaxy Nexus] Lancez:
I think r30 is not as smooth as r29 or r28. It feels a little laggy compared to r29 and r28. Just my 2 cents tho
[Samsung Galaxy Nexus] zoomy942:
I'm finding it very very smooth so far.
[Samsung Galaxy Nexus] apophis9283:
It might be helpful is you named the rom you were using vs smooth/laggy. Im on my own build and its flawless.
[Samsung Galaxy Nexus] zoomy942:
I'm on Tiny Linaro ROM.
[Samsung Galaxy Nexus] billouetaudrey:
What is this rom ?

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] cuboc:
There is no way to solve the problem wi fi without resorting to the terminal?
[Samsung Galaxy Nexus] zoomy942:
http://xdaforums.com/showthread.php?t=2235365
[Samsung Galaxy Nexus] AznInertia:
I'm using Atom 6/8 with R30 and I see no lag whatsoever! Great job!
[Samsung Galaxy Nexus] boype:
You can use an app that manages shell scripts, so you can execute the fix with just a few touches. I use $cripter, but only because I'm too lazy to look for another app. I'm sure there's one that lets you shortcut scripts via widget on the home screen. All you'd have to put into the script is this:

#!/system/bin/sh

fixwifi

Only when you are facing WiFi drops with screen off.
[Samsung Galaxy Nexus] sajty:
Is there any UV maniac like me?If yes,post your settings,i would like to compare results :).
[Samsung Galaxy Nexus] Tortuga52:
I am on Mirage ... for now and at first it is very fast and responsive, but with time the system gets laggy :/.

Also could you do a version with 230MHz min? The last times I used kernel with 192 my phone freezed and I honestly assume the use of 192 is a reason I get powerdrains. I tested the stock settings on plaine-mode over night and I lost 10% in under 8 hours. Most times like 6+ hours CPU was in deep-sleep, but like 1:30h CPU Speed was 192...
[Samsung Galaxy Nexus] Edward Stanbury:
Check out my sig :P
[Samsung Galaxy Nexus] Pelide:
Check for rogue apps with betterbatterystats or with wakelock detector and use greenify to temporary ibernate apps you don't need in background ;)

Tapatalkeggiato - Improve SwiftKey http://goo.gl/xKYfc
[Samsung Galaxy Nexus] namtombout:
7175 settings have done right by me but I do a little adjusting as I see fit.

http://xdaforums.com/showthread.php?p=42148618

U.O.E.N.O
[Samsung Galaxy Nexus] zoomy942:
Min screen on is 384 right?
[Samsung Galaxy Nexus] chikimonke:
Bumping this once because I'm curious and I think it got buried pretty quickly the first time. Thanks:D
[Samsung Galaxy Nexus] namtombout:
It's in the OP but here is the link

http://xdaforums.com/showthread.php?p=41552443

Bottom of the post

U.O.E.N.O
[Samsung Galaxy Nexus] chikimonke:
Thank you sir, my bad for not seeing it in the OP.
[Samsung Galaxy Nexus] klobkelosh:
Running r30ext, I set the clock speed to the highest setting (multitasking while streaming baseball audio). Never had problems on other kernels at high speeds, but got some real bad performance, stuttering, lag. Otherwise stock settings. Set clock back down to the 10k setting where I usually leave it and all is well.

Otherwise all is well.Despite my abuse launcher was not killed.
[Samsung Galaxy Nexus] pcphobic:
R30 ext seems pretty good. Very smooth.

Overnight drain seems normal to me.
[Samsung Galaxy Nexus] jeffcavicchi:
R30 working great for me. Thanks for continuing to improve an already awesome kernel!
[Samsung Galaxy Nexus] lesp4ul:
I was curious about this kernel then i tried r30. Everything running great & smooth. No problems so far. Great job!
[Samsung Galaxy Nexus] modernbummer:
This seems to be the best kernel so far for RootBox on toro. Thank you.
[Samsung Galaxy Nexus] Orsini:
very smooth great kernel.
[Samsung Galaxy Nexus] iferlive:
The new r30 is awesome, my launcher used to restart every time i get back to it but with the new whitelist that doesn't happen anymore, [MENTION=4615478]boype[/MENTION] is there any way to add our own apps to the whitelist?
[Samsung Galaxy Nexus] branedamig:
What launcher? Is action launcher working better now?

Sent from my Fancy AXI0M Gnex on Tap2
[Samsung Galaxy Nexus] iferlive:
I have used tsf shell and apex launcher, both work great no more reloads and everything is smooth as always with this kernel. If action launcher is in the whitelist it should work better.
[Samsung Galaxy Nexus] manolone:
Action launcher works better but Sometimes it redraws

I'm thinking to switch launcher : which is less ram consuming? Nova or apex?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] sajty:
Nova should be winner.
[Samsung Galaxy Nexus] klobkelosh:
Hate to report it, but the launcher (apex on cm10.1 for Toro with stock settings) got killed after two days running r30. Actually the whole system lagged to a crawl street streaming a podcast. I closed as many apps add I could but system wouldn't recover. Restart did the trick.

Please don't take this as a complaint, I love this kernel, just wanted to report my experience.
[Samsung Galaxy Nexus] n2rjt:
I use standard ROM too. It does get laggy on second day. Rebooting regularly at night is a good cure. I don't think you can blame the kernel. I love this kernel. R30 is wonderful.
[Samsung Galaxy Nexus] natezire71:
Set up Tasker to perform a reboot every night. That's what I do. :D
[Samsung Galaxy Nexus] wisefreakz:
Re: [KERNEL][4.2.x] Fancy Kernel (Rel. #5) (FEB-10-2013)

Boype, you think it could be rom related?

I use xylon...
[Samsung Galaxy Nexus] Lancez:
Re: [KERNEL][4.2.x] Fancy Kernel (Rel. #5) (FEB-10-2013)

I'm on AK purity 021, would like to give this a shot. Should I clean up anything before installing this? Thanks in advance.
[Samsung Galaxy Nexus] bigknowz:
Settings outside of Trickster

In terminal emulator, I changed /sys/devices/system/cpu/cpu0/cpufreq/screen_on_min_freq to 19200, which worked fine. When I did the same for cpu1, both cpu0 and cpu1 only dropped as low as 384. Can you only set cpu0?

Also, what can I echo to /sys/devices/system/cpu/cpufreq/ondemandplus/[...] that is not in trickster?
[Samsung Galaxy Nexus] boype:
It's possible, even though I don't know for sure, since I don't know anything about that ROM :x Sorry I can't tell you more.

Wipe dalvik would not be bad I guess, but it's not really necessary.

Only set the one for cpu0, cpu1 will play along then ;)

/sys/devices/system/cpu/cpufreq/ondemandplus/freq_step_stay_cycles can be set to a value from 1 to 5. It controls how many timer cycles (one cycle = 30ms if you did not change it) the governor should remain on the intermediate frequency before scaling to the maximum frequency. But this only works in combination with freq_step set. If freq_step is 0 or 100, the governor will scale straight up to max frequency. I'm really curious why this won't show up in trickster... Maybe the variable's name is too long or something?!

[EDIT]

I should probably add some governor basics to the OP :D
[Samsung Galaxy Nexus] agnostic900rr:
giving #5 a try, cause #4 was a real disaster for me, so I went back to #3
[Samsung Galaxy Nexus] bigknowz:
init.d question

I set up init.d file to change min screen on. Is there a way to add something to the script to ask if it should run? Asking because if I set ondemand plus settings, but I am not running that governor, there is potential to mess with the phone.

ex.

#!/system/bin/sh

read -p "Run script? (y/n) " DOIT

if [ "$DOIT" = "y" ]; then

echo "19200" > /sys/devices/system/cpu/cpu0/cpufreq/screen_on_min_freq

fi
[Samsung Galaxy Nexus] Doublewise:
Re: [KERNEL][4.2.x] Fancy Kernel (Rel. #5) (FEB-10-2013)

@boype

Release 3 default governor is pegasusq and I think its battery friendly (but probably tend to freeze system sometimes?) Recent release you focus on another governor? Not try to fix and optimize pegasusq that proven to be quite snappy and low battery drain?
[Samsung Galaxy Nexus] lippol94:
R: [KERNEL][4.2.x] Fancy Kernel (Rel. #5) (FEB-10-2013)

He explained clearly that nothing he did on pegasusq made it more stable. As many other kernel developers, he realized that Omap cpu isn't hotplug friendly. Hence no more pegasusq.

Easy peasy.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Doublewise:
Re: [KERNEL][4.2.x] Fancy Kernel (Rel. #5) (FEB-10-2013)

Hmm I'm afraid this will become never ending release, try this.. fault there and so on... Probably this is why many people back to stock because of its stability and tired flashing. Not to disrespect devs, but this is android world, I know that :)
[Samsung Galaxy Nexus] boype:
I disagree to some extent. Sure a lot of people are tired of 'neverending releases', because some devs pull in every little modification they find and make new releases almost every day. But then again, there are also many who like frequent updates and new stuff. Also, if you don't update your kernel every once in a while, many people will feel they have been abandoned and lose interest.

Anyway, this is not what I want to do here. Sure, the kernel is still pretty fresh and one or two bugs had to be fixed. But that's about it. When all bugs are resolved (of which I'm positive they are), I'll only release updates if the CM10.1 kernel upstream is changed or if a new kernel version (3.0.xx) pops up.
[Samsung Galaxy Nexus] bolanrox:
I could see nightly kernel updates being a bit much, but a weekly or bi weekly update is not that big of a deal. I wouldn't call it a never ending release, it is just normal updates, same as any other comp related product, they go with the territory.
[Samsung Galaxy Nexus] bigknowz:
Fixed my music problems

I listened to music this morning without stutter for the first time in over a month. Thanks boype.

I did notice something strange yesterday, a couple of times when I hit the power button, the screen would turn on, but it was very dark. I almost mistook it for SOD. Another 2 presses brought things back to normal.

Here are my settings:

CAB on, cubic / sio / 2048 read ahead / 192 / 1420 / 1420 / 192 screen on (now works in trickster)

interactive 15k / 80 / 1420 / 45K / 15K

colors -5 / 0 / 4 / 0 / 2 / 215 / 200 / 222

So far today, no issues with the screen.

I see trickster update also has new option, specifically for fancy:

Try to group tasks into least cores possible and it is on by default. Is that correct?
[Samsung Galaxy Nexus] bolanrox:
Been off charge since 6:30am (was at 98%) - 100% on 4 g data. Still at 90% battery it just keeps getting better!
[Samsung Galaxy Nexus] I Am Marino:
Using this on my toro, and let me say, excellent kernel.
[Samsung Galaxy Nexus] ptmax13:
Noob question ahead:

I have franco kernel currently... What should I do to install Fancy instead?

Flashing Fancy over franco and wiping cache/dalvik is enough?
[Samsung Galaxy Nexus] boype:
Don't use the 'group tasks' option in trickster, because the author has implemented it incorrectly. group tasks is set by the kernel on boot on its own already. I think I will contact the trickster author...

Yes, that's enough ;)
[Samsung Galaxy Nexus] gwindlord:
And what does this group tasks mean - try to balance tasks between CPU cores?..
[Samsung Galaxy Nexus] boype:
Knowledge base: multi core power savings / scheduler

It schedules CPU load among the cores to keep one core idle to save energy if the load is small enough for that. It is somewhat like hotplugging in terms of energy savings, with basically no downsides. Next release will include many fixes and improvements for sched_mc ('group tasks').

The feature has now been named correctly 'Multi core power saving' in Trickster MOD.

In case you're interested, here's some more on that:

http://lists.linaro.org/pipermail/linaro-dev/2011-October/008337.html

and

https://wiki.linaro.org/WorkingGroups/PowerManagement/Specs/sched_mc
[Samsung Galaxy Nexus] gwindlord:
Thank you for the detailed reply :)

BTW, I've heard that 4.2.2 update contains kernel as well, so it will be necessary to update kernel sources to the latest ones from stock in the near future.
[Samsung Galaxy Nexus] boype:
When the CM kernel source has it, I will have it :cyclops:
[Samsung Galaxy Nexus] branedamig:
I have used all 3 and so far apex had been the smoothest launcher I've used on any ROM and this kernel. Action launcher is the biggest resource hog and nova isn't far behind.

You on r30?

Sent from my AXI0M Gnex with AK Kernel on Tap2
[Samsung Galaxy Nexus] pcphobic:
Super smooth on LiquidSmooth ROM.
[Samsung Galaxy Nexus] jesssiii:
I used to use Nova, but find Apex far superior!

Toro GNex
[Samsung Galaxy Nexus] agritux:
guys, this topic isnt for launcher discussions

thanks
[Samsung Galaxy Nexus] adamczyk777:
Great Kernel! Switched to Fancy from AK since r27. Keep up great work boype!
[Samsung Galaxy Nexus] dandwhelan:
Hey, I have been having countless problems with my jawbone up being killed in the background then starting up and cutting out my headphones audio. Can you please add com.jawbone.up onto your whitelist? I know it's not a launcher but it will save me loads of aggravation. Also your kernel rocks, but can rock even more with this change :)
[Samsung Galaxy Nexus] zoomy942:
Been running great all day. I moved the brightness via trickster up another 10 or 15% and it's perfect. Bright Idaho sunny days
[Samsung Galaxy Nexus] ToMeRv32:
What app do you guys use with this kernel?

Trickster?
[Samsung Galaxy Nexus] NateK:
Trickster!
[Samsung Galaxy Nexus] matson36:
I have a little problem with fuss, it wont give any feedback after I typed the command

and it seems I am root user by default already, the username starts with u0 when I open the terminal emulator since when I type

id root -> uid=0(root)
[Samsung Galaxy Nexus] manolone:
I'm on r30. So u advice me apex instead of nova regarding ram consumption? Is there a sure way to measure ram occupancy?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] ToMeRv32:
And do you say the consumption is kernel depended? Or you didn't tried with other kernels?
[Samsung Galaxy Nexus] pcphobic:
Yes u can see for yourself using SystemPanel Lite app.
[Samsung Galaxy Nexus] motorazrv3:
Or you can use os monitor. Looks like this.

Launcher is using a good amount of ram.
[Samsung Galaxy Nexus] gwindlord:
Could you please define the exact steps sequence - what do you do and what happens? Also you say that you open terminal, see # prompt and your 'id' says 'uid=0', am I got it right?..
[Samsung Galaxy Nexus] splus:
I did some tests for RAM usage with SystemPanel Lite as well. For my home screens setup Nova uses 40 MB, whereas Apex uses 50 MB RAM.

That's why I use Nova.

But regarding the killing of launcher when low on memory - for me it's not a big deal if there's truly not enough memory.

But what I noticed with SystemPanel Lite app, whenever I'm doing some heavy browsing many, if not all, apps and services get killed, but SwiftKey ALWAYS stays in memory. I don't know how they managed to make it to always survive but I'd rather that SwiftKey gets killed than some other services or a launcher.
[Samsung Galaxy Nexus] matson36:
Normal sequence...
[Samsung Galaxy Nexus] gwindlord:
Crap and weird... Could you please do 'which fuss' and 'which sh' there?
[Samsung Galaxy Nexus] wai10691:
Sometimes more widget on the home screen require more RAM. Make sure both Apex and Nova launcher have the same configuration when compare. =)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] splus:
Of course I had identical configurations when I did the tests.

There would be no point comparing if I didn't... :rolleyes:
[Samsung Galaxy Nexus] pcphobic:
I am also using Nova launcher. No issues with it.
[Samsung Galaxy Nexus] lesp4ul:
This is my Nova 2.1.1 ram usage, aospal 9 + fancy r30
[Samsung Galaxy Nexus] sym_m:
how many screen you have on nove ? i have 3 screen with 5 widget+ alot of folder+apps and it use 77MB
[Samsung Galaxy Nexus] lesp4ul:
3 screens, uccw clock, uccw minimal weather, gmail widget and volume bar. I also have 4 folders and some app icons. Check your widgets bro, on some apps if you add their widget it automatically open the app too in the background. Some of them could suck out your RAM. Correct me if I'm wrong :)
[Samsung Galaxy Nexus] shawnaye:
Guys enough with the nova discussion really.

Any feedback about r30?

Sods, slowdowns after some time?

Battery or wifi behaving weirdly?

Data drops?
[Samsung Galaxy Nexus] BOY_:
Boype, there was some chatter a few days ago about adding frandom to the kernel. Have you had a chance to look into it yet? I may try pulling a module from another kernel and attempt a pubchmod but I'm reluctant. Having it baked in would be much preferred.

Thanks!
[Samsung Galaxy Nexus] sym_m:
i don't know but my free ram is 284 :laugh: i am happy for that
[Samsung Galaxy Nexus] matson36:
u0_a124@android:/ $ which fuss

/system/bin/fuss

u0_a124@android:/ $ which sh

/system/bin/sh

u0_a124@android:/ $
[Samsung Galaxy Nexus] zoomy942:
Honestly I felt like battery was a bit less than previous versions.
[Samsung Galaxy Nexus] lesp4ul:
If you don't experienced any slowdown then so nothing to worry. 284MB free ram is very good.

I also use r30 whitelist for nova, it really works. :)
[Samsung Galaxy Nexus] Inpain:
When i do the fixwifi workaround, this is what i do

i go into my Terminal

su then ENTER

fixwifi then ENTER

i get this msg:

rmmod: chdir(/system/lib/,odules): No such file or directory

insmod: can't insert '/sbin/bcmdhd.ko': File exists

Does that mean the fix has been applied ?

Thanks
[Samsung Galaxy Nexus] Pelide:
Try this way: Power off wifi, reboot, retype fixwifi on terminal and power on wifi

Tapatalkeggiato - Improve SwiftKey http://goo.gl/xKYfc
[Samsung Galaxy Nexus] Inpain:
Same msgs :(
[Samsung Galaxy Nexus] Pelide:
I'm sorry but I don't know what else to say... Wait boype or some other skilled user ;)

Tapatalkeggiato - Improve SwiftKey http://goo.gl/xKYfc
[Samsung Galaxy Nexus] lesp4ul:
I don't know but have you tried reinstalled the kernel?
[Samsung Galaxy Nexus] Inpain:
Yes, still the same :(
[Samsung Galaxy Nexus] lesp4ul:
Well if you need a fix so much then wipe dalvik/cache, flash another kernel first, boot, wipe again, flash r30. If not helping, clean install rom :p
[Samsung Galaxy Nexus] boype:
Could you check if there's a folder named 'modules' present in /system/lib ?? If it is not, create it and reboot. Afterwards you should be fine
[Samsung Galaxy Nexus] motorazrv3:
Maybe i am wrong, the directory name written at the error msg is ,odule

Is that a write error or the correct name?
[Samsung Galaxy Nexus] osm0sis:
Hey guys. Just a heads up that those bfq values for flash storage optimization aren't from sajty, in fact he was in our thread asking about tunables and took them from [MENTION=4793042]pkgnex[/MENTION] and [MENTION=647743]Khrushy[/MENTION]'s posts (who are part of Franco's Dev Team). Please correct the credit in the OP at least. Preferably the commit as well if that's possible.

Not your fault [MENTION=4615478]boype[/MENTION], clearly sajty didn't tell you where he got "his ideas" from...

http://xdaforums.com/showpost.php?p=42395899&postcount=42127

http://xdaforums.com/showpost.php?p=42308502&postcount=42092
[Samsung Galaxy Nexus] sajty:
Lol,i didnt say,that i discover them.I wrote to boype,that i found them in franco thread.So please,dont post those stupid things.
[Samsung Galaxy Nexus] osm0sis:
Excuse me? Credit where credit's due. End of story.
[Samsung Galaxy Nexus] sajty:
I dont care about credits.I clearly wrote,that i found those tweaks at franco thread,not that i discovered them!So dont tell,that i am taking someones ideas.I only wrote to boype about implementing them.
[Samsung Galaxy Nexus] osm0sis:
Fair enough. I'd still like to see the credit changed on the changelog and the commit however.

You didn't put a week of your life into researching and running statistical analysis on the bfq values to determine the most significant changes were the two listed. [MENTION=4793042]pkgnex[/MENTION] did. Franco's Dev Team does due diligence for every tweak we "publish".