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

[yank555]

Found the issue, stupid in fact, it's caused by SlimKat's ramfs

I've reverted to Temasek's v75 (yeah, pretty old) and the issue is gone...

This should teach me a lesson about "I always use the ramfs of the ROM I'm using" ... didn't I post quite a few time that :

If it ain't broken, don't fix it ?!

Oh well, I've learned a small lesson (again), good reminder

I'll test it tomorrow, if it's confirmed working, I'll upload it here. In doubt, use beta5.

JP.

[zancum]

Hi


My first post on this forum, I have to start by congratulating you for this wonderful forum.


In your last commit, about the new version of Led extended control 1.2, it's not possible to set 0, for divider led on.
I think it is necessary to add the line, case 0, corresponding:

Code: Select all

switch(new_led_speed_on) { /* Accept only if 1 - 5 */
      case 0:


am i right?



regards

[yank555]

Hi


My first post on this forum, I have to start by congratulating you for this wonderful forum.


In your last commit, about the new version of Led extended control 1.2, it's not possible to set 0, for divider led on.
I think it is necessary to add the line, case 0, corresponding:

Code: Select all

switch(new_led_speed_on) { /* Accept only if 1 - 5 */
      case 0:


am i right?



regards

Well yes, with the idea to never light up on notifications ... but ... it will blink super fast, so still blink, not stay plain off ...

I had it that way initially, but since it didn't work as expected, that's why I actually didn't leave it in.

It's doable to never light up the LED, but I didn't have time to add this, and I didn't see much point either tbh

JP.

[ezaechiel]

Hello, a little thing, I have a problem with phone applications on every rom I tested when I call and the screen is off due to proximity sensor, when I pull back the screen of my face it doesn't power on and no action could help.

In the beginning I thought it was due to rom but aosp or cm have the same problem. Could it be kernel related?

Btw I'm back on Cm nightly with Android 4.4.3 and all is working fine for me (except this phone problem).


Envoyé de mon SM-N9005 en utilisant Tapatalk

[yank555]

Hello, a little thing, I have a problem with phone applications on every rom I tested when I call and the screen is off due to proximity sensor, when I pull back the screen of my face it doesn't power on and no action could help.

In the beginning I thought it was due to rom but aosp or cm have the same problem. Could it be kernel related?

Btw I'm back on Cm nightly with Android 4.4.3 and all is working fine for me (except this phone problem).


Envoyé de mon SM-N9005 en utilisant Tapatalk

Habe you checked using stock CM kernel, in case, to exclude that as a cause ?

Sensors sometimes misbehave, had that with screen rotation...

You can use AndroSensor to check you sensors.

JP.

Send from my 'proudly eFused' Note 3 (n9005) running SlimKat 5.6 Weekly on Yank555.lu htle v1.0b-beta7 (3.4.91) kernel.

[ezaechiel]

Apparently no problem by now with stock kernel . I'll give you feedback in two or three days

Edit : first test : a phone call, I call my mom, no problem the sensor works well with stock cm kernel.



Envoyé de mon SM-N9005 en utilisant Tapatalk

[yank555]

CM11 Beta Kernel Update

Well, the switch to SlimKat's ramfs was quite a bad idea as it turned out, as it produced a draining wakelock, solved by switching back to CM (Temasek v94) ramfs.

On user request, I added a mode to replace LED blinking by plain LED on for LED eXtended Control.

CPU Hardlimit underwent a major rework, internal, but also screen on & off CPU min is now supported, and userspave dvfs interference can be locked now (last Aroma option in CPU screen).

userspave dvfs lock means, once activated, that nothing from userspace, neither ROM nor any app (including Trickster, SetCPU...) will be able to change CPU min/max, only CPU Hardlimit will be able to do this, this is the proper fix and replacement to the previous "quick & dirty hack" to avoid CPU min getting stuck at high freqs.

Screen off min may be useful for those using sound mods like viper, which may stutter due to too low CPU during screen off.

Changelog CM11-20140517-hlte v1.0b-beta7 (07/06/2014)

• updated CPU freq. HardLimit to v2.0 : completely new sysfs interface / added CPU min. screen on & off controls / added kernel-side userspace dvfs lock (Yank555.lu)
• updated LED eXtended ConTRoLs to v1.2 - allow to set off delay to 0, so LED is always on instead of blinking on notification (Yank555.lu)
• ramfs replaced by Temasek v94 (CM11 nightly 20140606) - fixes bluetooth msm_serial_hc_dma wakelock

• Yank555.lu-CM11-hlte-v1.0b-beta7.zip

  (MD5 965d9bd66d928ab07ae493970cc1fc09)

  (10.14 MiB) Downloaded 682 times

[yank555]

Edit : first test : a phone call, I call my mom, no problem the sensor works well with stock cm kernel.

Just made a quick test, working fine on my end (SlimKat).

JP.

[ezaechiel]

Edit : first test : a phone call, I call my mom, no problem the sensor works well with stock cm kernel.

Just made a quick test, working fine on my end (SlimKat).

JP.

OK very weird,but I didn't have the problem every time, only sometimes. I didn't change anything else on phone application. I came back to you if I have the problem again on beta 7 .

Envoyé de mon SM-N9005 en utilisant Tapatalk

[yank555]

Edit : first test : a phone call, I call my mom, no problem the sensor works well with stock cm kernel.

Just made a quick test, working fine on my end (SlimKat).

JP.

OK very weird,but I didn't have the problem every time, only sometimes. I didn't change anything else on phone application. I came back to you if I have the problem again on beta 7 .

Envoyé de mon SM-N9005 en utilisant Tapatalk

Install AndroSensor and when you have the problem again, check if all sensors are still working...

Sensors still are a bit unreliable, like temp & humidity won't work after deep sleep

JP.

Send from my 'proudly eFused' Note 3 (n9005) running SlimKat 5.6 Weekly on Yank555.lu htle v1.0b-beta7 (3.4.91) kernel.