[hlte][2014/DEC/07][CM11/12] Yank555.lu kernel v1.1c-beta6

[yank555]

Ehr. I don't get quite what you're asking here. A cm12 kernel for a cm11 rom?

There is cm11 kernels in this thread as well.

I was looking topic that says CM-11, in this write CM-12 and so went astray.
If writing CM-11 & CM-12 I would simply look for the link CM-11.
Sorry my english is not good, I use google translate.

I've updated the thread title to CM11/12 ... but you need to pick the one for your ROM version.

JP.

Sent from my Nexus 5 running SlimLP 5.0-alpha5 on Yank555.lu SlimLP v1.1-beta3 kernel.

[lambik333]

is youre kernel also suitable for temasek CM12 V1???

[Raver099]

Yep it is

[scoobyjenkins]

Yep it is

Totally, battery life is insane!

[yank555]

Beta CM12 Kernel Update

OK, so here's a tiny changelog for a more than worthy addition, welcome faux's latest intellimm governor. I really like it ... like ... a lot ! It really makes a very ballanced use of the CPU freqs, keep an eye on them using cpu spy or similar apps. I guess if you're on the highend gaming trip, this may not be for you, but you can try, the browsing users like myself will very likely be VERY pleased with it !

Changelog CM12-full hlte v1.1c-beta1 (01/12/2014)

• added intellimm governor (faux123)

• Yank555.lu-hlte-CM12-v1.1c-beta1+.zip

  (MD5 8afc2c4e4a387f7f5c03491cf7fddcb0)

  (10.33 MiB) Downloaded 800 times

[yank555]

Wait, there is an issue with intellithermal in my settings script generator...

Let me reupload the fixed zip.

Sorry for that !

Sent from my Nexus 5 running SlimLP 5.0-alpha5 on Yank555.lu SlimLP v1.2-alpha1 kernel.

It is fixed in the v1.1c-beta1+ in the post just above.

JP.

[n3mo]

Hi, it's me again, about the "settings has stopped" issue with the CM11 kernel. I tried a clean install, I even redownloaded the latest nightly. Still getting the exact same error, here's the log:
I'm out of ideas. Happens when trying to enter "Display and lights" in settings, or with every notification, LED doesn't work.

Code: Select all

java.lang.RuntimeException: Unable to start receiver com.android.settings.cyanogenmod.BootReceiver: java.lang.NumberFormatException: Invalid int: " "
at android.app.ActivityThread.handleReceiver(ActivityThread.java:2452)
at android.app.ActivityThread.access$1700(ActivityThread.java:144)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1281)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5146)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:732)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:566)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.NumberFormatException: Invalid int: " "
at java.lang.Integer.invalidInt(Integer.java:137)
at java.lang.Integer.parse(Integer.java:374)
at java.lang.Integer.parseInt(Integer.java:365)
at java.lang.Integer.parseInt(Integer.java:331)
at org.cyanogenmod.hardware.AdaptiveBacklight.isEnabled(AdaptiveBacklight.java:50)
at com.android.settings.DisplaySettings.restore(DisplaySettings.java:674)
at com.android.settings.cyanogenmod.BootReceiver.onReceive(BootReceiver.java:81)
at android.app.ActivityThread.handleReceiver(ActivityThread.java:2445)

[yank555]

No idea what that could be, sounds like a Java code error, an int defined as " " makes little sense, but I don't quite see how the kernel can be the cause of this ?!

JP.

[ryanrazer]

Hey yank. 1 question. What is that touch wake option in Aroma? By default it's set to 5 mimutes i think.
I tought I'd be like touch 2 wake thing.

[yank555]

Hey yank. 1 question. What is that touch wake option in Aroma? By default it's set to 5 mimutes i think.
I tought I'd be like touch 2 wake thing.

Touchwake (I should take it back to 5 or 10 seconds by default since I don't use my Note 3 as daily driver anymore) is not tap or double-tap to wake, which is kind of a power button replacement.

Touchwake is just a thingy that allows, after the display times out (cause you're reading sth etc.), to touch the display anywhere to bring it back on, but just for a short time.

I had set it to 5 minutes as I use a flipcover, which triggers the power button, hence doesn't let the display time out, and in that case, touchwake is not activated at all.

So if you turn the device off by pressing the power key, touchwake will not work, that is intended that way by design.

JP.