Now about the development:

I am learning a lot about Linux and mobile/embedded Linux while I develop FasterN9, and I make some discoveries in this process. I realized there are some things I still have to do to improve the user experience, stability and performance. There are 3 major changes in the way:

1) Create a daemon to change kernel parameters when the context changes. The first implementation changes the parameters to one set when the phone is locked and to another set when the phone is unlocked, and this will allow more aggressive performance settings when unlocked. The daemon should be event based - that means it will sleep almost all the time and will never wake up the processor, so minimal impact to the battery life. An initial (and functional) version of this daemon is included in UNSTABLE version 1.1.4 and is working very well for me.

2) Create a "Settings" plug-in to enable/disable and configure FasterN9. This will enable fine tunning of the settings (but unfortunately every change will require a reboot to take effect). This is also mandatory to give users a better control of their phones.

3) FasterN9 is currently a white list: all apps have low priority when not in foreground and some apps are in a list (white list) of high priority apps. This requires me to manually write the name of the processes of all apps that require high priority in the list and release a new version whenever a new app needs to be included. So, the step 3 is to transform FasterN9 in a black list: all apps have normal priority and only some apps that are in a list (blacklist) have reduced priority. This will make the list short and solve the problem of apps that shouldn’t be laggy when in the background.

I'll take some time to do all that, but I think I can do it before January ends.