I'm not sure this tracker corruptions are caused by FasterN9, but it is possible. This problem has been rarely reported, so it's difficult to say for sure. The problem of having a GUI is that editing the system file that controls the priorities is dangeours (and requires a reboot). There would be a risk of malf after every edit. That's why I never did it. I found a way sometime ago to reduce the side effects of FasterN9 a lot by tweaking the processes IO priorities, so I wouldn't need to change the CPU priorities so much. The problem is that aegis won't let me do that in not open-mode phones, and don't have the time to learn how to work arround that, so it's very frustrating.