Re: [KERNEL][GPL][JB] FuguMod kernel (open, stable, reliable and secure)

---

Originally Posted by renaud

r1095 will only work on 4.2.2
r1093 is the latest iteration of 4.1 and 4.2.1/4.2.0 I make because the source changed in non backward compatible way. The only difference between r1093 and r1095 is the 4.2.2 compatibility.

Can't wait for more of your kernel goodness.

Sent from my Galaxy Nexus using Tapatalk 2

Re: [KERNEL][GPL][JB] FuguMod kernel (open, stable, reliable and secure)

---

Originally Posted by unforgivenmercy

Can't wait for more of your kernel goodness.

Me too, lol
Does anyone think deadline is better than CFQ?

R: [KERNEL][GPL][JB] FuguMod kernel (open, stable, reliable and secure)

---

Originally Posted by renaud

Me too, lol
Does anyone think deadline is better than CFQ?

I always use deadline system appears more quick

Inviato dal mio Galaxy Nexus con Tapatalk 2

Deadline win ....

Re: [KERNEL][GPL][JB] FuguMod kernel (open, stable, reliable and secure)

---

Originally Posted by renaud

Me too, lol
Does anyone think deadline is better than CFQ?

Deadline is overall better for me.

Sent from my Galaxy Nexus using Tapatalk 2

r1100 is using a newer (linaro) gcc toolchain

I'm really glad that this kernel is secure(so I can use apps with root detection)
but it seems to be preventing Kindle from launching
hope there would be a fix

Originally Posted by a4840639

I'm really glad that this kernel is secure(so I can use apps with root detection)
but it seems to be preventing Kindle from launching
hope there would be a fix

You will need to send me at least dmesg and logcat after it failed, so I can check why it fails. Please use pastebin or attachments, do not paste directly in the forum.
Also note that the problem is probably in the app itself though.

Renaud,


what is your opinion on the target_loads interactive parameter? Your default values are not quite good, that is at least according to 0smosis and others who tested different values for interactive. If target loads is set higher then hi speed_frequency, the governor will supposedly continuously switch between hi sped and target_loads. When hi speed is reached at say 50 governor than targets the target_load so instead of maybe increasing the frequency it will actually decrease it in order to achieve higher load.


For me personally the best option would be to remove the thing.

---------- Post added at 07:39 PM ---------- Previous post was at 07:27 PM ----------

To correct my self, I was talking about go hispeed freq, and not about hispeed_freq value, which is not determined by percentage of load but with frequency.

And I am sorry for my bad English

Sent from my GT-I9305 using xda premium

It is normal for a governor (except performance) to try to lower the frequency on some circumstances, this is why they have been created in the first place. Maybe you could elaborate a little bit more on why this is worse on interactive?