Yank555.lu Android Stuff

FauxClock can control every feature of this kernel except your Hardlimit? Or is there anything else I forgot?

Mojo wrote:FauxClock can control every feature of this kernel except your Hardlimit? Or is there anything else I forgot?

Including Hardlimit's original function, capping CPU max, not supported from the current Hardlimt are :

- hardlimit screen off
- wakeup kick
- touchboost frequencies

Hardlimit seems to have an issue in the new Samsung source, limiting below stock 2.26GHz has been reported not work perfectly, occasional jumps up to stock 2.26GHz appear to happen.

I was able to reproduce this on my CM kernel and made a fix, which works perfectly fine in my CM kernel...

But I will upload 001a5, which has that fix, hopefully it will work fine on TW as awell...

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Temasek v75 on Yank555.lu htle v1.0a (3.4.90) kernel.

Edit : And touchwake, but that's not working yet, as of now that should be the only thing left to fix, if Hardlimit works correctly now, to get the kernel out of alpha.

Alpha Kernel Update

Hardlimit has been reported to not work properly if under clocking, as in setting CPU max in faux clock below the stock 2.26GHz, some spikes would still be going up to 2.26GHz.

I was able to reproduce this in my CM kernel, and the new Hardlimit v1.7 fixed it completely in my CM Kernel.

Could you please report back to let me know if it does its job correctly in this kernel as well ? Thanx !

Changelog 001a5 (17/05/2014)

• Hardlimit is fixed, under clocking below 2.26GHz should work now
• touchwake isn't working yet
  
  Make a Nandroid before flashing this...

• hlteeur-faux123-yank555.lu-U7-ND3-001a5.zip

  (MD5 e7db1f3252e3277eb820d33e3f01f5d8)

  (6.75 MiB) Downloaded 581 times

No more jumps higher than max frequency now

I see the latest kk kernel is based on ND3. Is it still safe to run it on ND5 bootloader?

EDIT: Found out. Just a little bit new to all this bootloader compability stuff, but figured it out. Latest version running fast and smooth so far.

Yank,

a5 unable to activate intelliplug after mpdecision is off

EDIT: seems to be ok after a reboot. Shall monitor it again

Wondering why you do not implement the latest Linaro and Linux versions on your kernel ?

Hello, a quick return on a5. All is working fine with fauxclock and a stock firmware using xposed.

As I said before benchmark are quite under other kernel but strangely the phone is more reactive and smooth, battery friendly, no overheating for me, so as yank said bench are not worth the time we used it.

Thanks a lot for your hard work guys. I'll try it with my own custom as soon as I finish it

Lodix wrote:Wondering why you do not implement the latest Linaro and Linux versions on your kernel ?

Linaro is snakeoil (at least for kernels), makes no difference. I made blind tests, same sources compiled with different toolchains, linaro ended up way behind google.

As for upstreaming, that's faux's decision. Yes it's not a bad idea, but it's not so important either, many of the relevant patches are in Samsung's sources, and 80-90% of the Linux patches are not even compiled on our devices.

My own CM kernel is upstreamed, because I started it and just go on with it.

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Temasek v75 on Yank555.lu htle v1.0a (3.4.90) kernel.

Ok thanks for the answer.