So here is the situation. On my s5 901f
The kernel + rom combo I use sets noop as default governor confirmed by the dev androidgx.
If I boot the phone e.g. 10 times, about 70% of time it boots with noop, the other 30% with cfq.
Even if it boots with noop or I change to noop, eventually it changes back to cfq (without rebooting, so e.g. if I check day later its back to cfq).
The only 2 apps I have that by design can adjust the io scheduler are trickstermod and setcpu.
If i remove trickstermod the issue still occurs.
If I remove setcpu, the issue still occurs.
I have never removed both at once tho as I need an app to show me the governor in use.
Is there anyone else who has ever had this issue and knows how to resolve? is there a log I can do which shows what is changing the io governor?
The kernel + rom combo I use sets noop as default governor confirmed by the dev androidgx.
If I boot the phone e.g. 10 times, about 70% of time it boots with noop, the other 30% with cfq.
Even if it boots with noop or I change to noop, eventually it changes back to cfq (without rebooting, so e.g. if I check day later its back to cfq).
The only 2 apps I have that by design can adjust the io scheduler are trickstermod and setcpu.
If i remove trickstermod the issue still occurs.
If I remove setcpu, the issue still occurs.
I have never removed both at once tho as I need an app to show me the governor in use.
Is there anyone else who has ever had this issue and knows how to resolve? is there a log I can do which shows what is changing the io governor?
Last edited:
