yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Imoseyon:
Yeah 1.13.4 doesn't have it disabled by default. I will try to release 1.14 today which will have the options to disable (or dial down) in lkconfig.

The reboots shouldn't be there. See if you can pull logs from /sys/fs/pstore right after the reboot?
[Nexus 6  Original Android Development] bradputt:
i need both the kernel to be permissive and with the wakelock fix. however i can wait.

xposed comes first...... :good:

Imoseyon ,you're the best!!! :good::good::good:
[Nexus 6  Original Android Development] IAmAN00bie:
Hi imoyosen have you seen this yet? http://xdaforums.com/android/software-hacking/dev-kcal-advanced-color-control-t3032080.

Would be amazing for the Shamu!
[Nexus 6  Original Android Development] bradputt:
[YOUTUBE]FSgPUN05I90[/YOUTUBE]

I SEE SATURATION SLIDER......:eek:
[Nexus 6  Original Android Development] Imoseyon:
v1.14 is up.

Notable changes are the controls for msm_hsic and wlan_rx wake sources that were much talked about earlier in the thread. I've introduced a concept called "time divisor" for those two wakelocks. For instance divisor of 1 is stock (fully enabled), and as you set this to a higher number the time that wakelock is held is reduced further.

Use lkconfig for controlling the above wake sources.

Speaking of lkconfig, there are tons of changes to it: 1) selinux mode, 2) wakelock control, and 3) cpu frequency control. There may be a bug or two, which I'll fix as I discover them.

Oh, I also noticed that there were some sensors.qcom related SELinux denies during boot (also present in stock), so I fixed that as well.

Full changelog: https://github.com/imoseyon/leanKernel-shamu/wiki/Lollipop-ChangeLog

--

Oh, I'll take a look at the new kcal controls, as well as cm12 superuser stuff with [MENTION=5169465]DespairFactor[/MENTION].
[Nexus 6  Original Android Development] DespairFactor:
It looks like flar already is looking at KCAL as well as franco, let's race them to it!
[Nexus 6  Original Android Development] Damon13:
Hello Imoseyon and thanks again for a wonderful Kernel, I am currently on V1.13.3 with msm_hsic disable and It has been amazing in performance as well as battery. I see that you have introduced a time devisor (the higher the less we see of the wakelocl) to limit the wakelock in intervals, is there an interval to disable it completely. V1.13.3 has been really good in battery and everything is working fine (text, MMS, calls, data) not a single issue.
[Nexus 6  Original Android Development] Remoteconcern:
I think it's 8.
[Nexus 6  Original Android Development] Imoseyon:
yes for msm_hsic, the value is 0 (there's no such option for other wake sources). You can see it in lkconfig as well.

Edit: you can probably also set it to something like a 1000 (yes you can actually go higher than 8), if you still want to allow kernel to instantly hold this wake source and release.
[Nexus 6  Original Android Development] simms22:
if you are watching your cpu control app(probably trickster), dont. install an app like perfmon, and open it to cpu after disabling mpdecision. then youll see your actual cpu speed.
[Nexus 6  Original Android Development] Johnny424:
Good to see you imosey ..just picked up my n6 today. Haven't seen you sense the gs3
[Nexus 6  Original Android Development] BDR456:
Installed perfmon and it's no different after turning off mpdecision. Max/min is all over the place.
[Nexus 6  Original Android Development] simms22:
well of course. what, do you expect it to stay at one speed? thats not how cpus work. they will use whatever speed is needed at the time, the speed will be in between what you set as max and min. if you want your phone to only at one speed, then set min and max at that same certain speed that you want.
[Nexus 6  Original Android Development] BDR456:
I dont think it's good for the min to be stuck at 1728 when it can go lower and waste less battery. When i set the max/min and hit apply it just changes to whatever it wants.
[Nexus 6  Original Android Development] caspersfi:
I THINK what BDR is saying is even if he sets his CPU to a minimum of say 652 it'll still jump past.
[Nexus 6  Original Android Development] old_fart:
Thank you ! plugged it in and "taa daa" !

um, sadly the score went from ( around ) 50K to 45K ? ? ?

but a bigger surprise / shock was that it broke TiB . . . . yipes !

.

please be advised, with my black slab of plastic ( which keeps falling out of my front pocket when I'm in my car ( unlike the nexus 5 ) ! ! ! ), I backed down from the 'beta3ocuc' to the plain old 'beta3', ( yeah ! ), TiB is working again . . . and the antutu score is back to normal - 50186 . . . . .
[Nexus 6  Original Android Development] BDR456:
Not that it still jumps passed, but goes below or above whatever settings i put. I know the cpus use what they need but those settings are there for a reason.
[Nexus 6  Original Android Development] old_fart:
um, more data please . . . specifics. ah, the perfmon output . . . yeah. maybe 'cpu monitor' ?
[Nexus 6  Original Android Development] Imoseyon:
mpdecision will read and/or manipulate the following kernel sysfs nodes:

cpufreq/scaling_governor
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
/sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
/sys/devices/system/cpu/cpu3/cpufreq/scaling_max_freq
/sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq
/sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
/sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq
/sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq

I had to put in a lot of hacks in my kernels in the past so users modifying these values will still stick even when mpdecision is running. For now, it's best to keep mpdecision disabled (i.e rename /system/bin/mpdecision and reboot) *if* you want to set these to custom values. That should work for sure for max_freq - custom min_freq may still be a little wonky (for now).

EDIT: Oh, make sure you don't use init.d for values to stick at boot. Init.d support ain't there yet. :)
[Nexus 6  Original Android Development] simms22:
no, its not good to be stuck at 1728. you said you set you set min/max and it was just all over the place, i had no idea its at 1728 for a min. what are you using for a terminal app? also, you can use trickster to disable mpdecision just as well, you just have to set it as off.
[Nexus 6  Original Android Development] BDR456:
I disabled it a couple builds back and every time i change the max/min but it still acts up. I'm sure imoseyon will get it squared up.
[Nexus 6  Original Android Development] Circaflex:
mine is also doing the same, used trickster to turn mpdecision to off, trickster still reports its stuck at that level and perfmon shows it sticking

hmm now all seems normal, I flashed the b3ocuc kernel and now everything seems to be correct with it disabled :)
[Nexus 6  Original Android Development] Pilz:
Just flashed the b3occu, will it automatically use the lower clock or do we need to manually set in in trickster.

Edit:

I just set my min as 233mhz in trickster mod so let's see how this goes for battery life.
[Nexus 6  Original Android Development] clothednblack:
I started with the first release of this kernel, and updated with every new release, but something got weird. I could make and receive calls but couldn't hear the ringer through the ear piece when making a call and couldn't hear the person on the other end but could hear me. I have since then re-flashed the rom I'm on and no issues. Can a kernel cause this or would it be related to kernel/rom compatibility?

Running slim rom, AT&T, and decrypted.

TIA

Sent from my Nexus 6
[Nexus 6  Original Android Development] Steve Lazarus:
Where did you get Slim from? Beta build ? If it's not a beta for the Nexus 6, probably ROM related...

Sent from my Nexus 6
[Nexus 6  Original Android Development] clothednblack:
[emoji1] http://xdaforums.com/nexus-6/general/nexus-6-sprint-users-thread-t2949996/page6

Post 54

Sent from my Nexus 6
[Nexus 6  Original Android Development] clothednblack:
It was alpha when I started using it, then flashed latest kernel from here and that's when the problem started

Sent from my Nexus 6
[Nexus 6  Original Android Development] Steve Lazarus:
Not surprised, seeing a lot of compatibility issues. All these ROM's and kernels are still in alpha/beta build stages... I'd stick with stock kernel on custom ROM's for now and Lean on stock...That is until it's confirmed working one way or the other...

Thanks for the heads up on Slim:thumbup:

Sent from my Nexus 6
[Nexus 6  Original Android Development] zephiK:
I'm personally use Minimus and it works great with Lean Kernel, no problems. Been running it since noon
[Nexus 6  Original Android Development] rignfool:
How awesome is this...

Imoseyon... The mad scientist...

And DespairFactor... The code machine...

Working together...

I think I'll go play the lottery!
[Nexus 6  Original Android Development] Imoseyon:
Here it is (v1.14.1): https://onedrive.live.com/?cid=F1ED4BADFEE3FC02&id=F1ED4BADFEE3FC02!440

Did I win this race? lol. I don't even know how well it works. I had to spent some time adapting savoca's work since it was originally written for 3.4 kernel and not for shamu.
[Nexus 6  Original Android Development] purian23:
LOL you win! Nice work
[Nexus 6  Original Android Development] DespairFactor:
Well, I thought I was going to have to do work, I guess not[emoji14] too fast for me haha, I am also starting to work on the Yureka Yu tonight:)
[Nexus 6  Original Android Development] Damon13:
Thanks Imoseyon for taking your time to explain thoroughly this interval process. If I understood correctly I will just set mdm_hsic host to 0 to completely disable it and for the wlan_rx as well as others, I will set them manually (maybe 1,000) .

Damn I can't keep up, now we have V1.14.1
[Nexus 6  Original Android Development] Imoseyon:
Still gonna need your help on cm12 superuser stuff - will ping you via PM. Let me download cm12 kernel and take a look first though.
[Nexus 6  Original Android Development] franciscofranco:
Only RGB and Inverted colors work with the initial patchset.
[Nexus 6  Original Android Development] DespairFactor:
I am not home until about 5 hours from now, and only have a couple hours to work on stuff when I get home, mind you I tend to remote to my PC to do stuff when I'm at work. I actively monitor my stuff though, so I will get back to you almost instantly.

---------- Post added at 03:27 PM ---------- Previous post was at 03:24 PM ----------

Is this using both of the commits?
[Nexus 6  Original Android Development] Imoseyon:
Looks that way to me as well. A small bummer. Let me look through the patchsets more carefully..
[Nexus 6  Original Android Development] franciscofranco:
He posted an experimental patch for our device revision. I'm merging it all over again to test.
[Nexus 6  Original Android Development] Imoseyon:
This one? https://github.com/savoca/kernel-msm/commit/7dbc9ba0fd18279cde564c1631e52b448b39fc98

That's already in my v1.14.1 but sat/hue/etc still doesn't seem to work.
[Nexus 6  Original Android Development] franciscofranco:
Right. You just saved me the trouble!
[Nexus 6  Original Android Development] old_fart:
Is it a divisor ? . ie. if you put a seven in there, then one in seven gets through ?

As I'm typing this - I did a reboot and "by gosh o golly" its stuck. . Haven't seen this in a long, long time . . .

Pressing and holding in power to do a reboot ( again ) and this time it came up.

.

btw, er just a minute ago - i checked the lk settings and they had changed . . . . all on their own accord. hmmm, 'stuck on boot up' equates to reaching in there and fiddling with the setup ? ? ?
[Nexus 6  Original Android Development] Steady Hawkin:
I don't remember ever having a device with such great support, and people who work so well together. Hat's off [MENTION=3357040]Imoseyon[/MENTION] [MENTION=3292224]franciscofranco[/MENTION] [MENTION=5169465]DespairFactor[/MENTION] , we appreciate it!
[Nexus 6  Original Android Development] wrinklefree:
Color Calibration

I've got my calibration tools ready once the code is cracked :)
[Nexus 6  Original Android Development] CatInTheHat422:
This may seem like a silly question but it's driving me nuts. If I set a wake lock to "disabled" does that mean it's back to stock or does it mean it's shut off from waking the kernel?
[Nexus 6  Original Android Development] natezire71:
What's a good divisor value? I don't want to disable it entirely, but I don't want to keep it in its current state.
[Nexus 6  Original Android Development] Gnex1:
[MENTION=3357040]Imoseyon[/MENTION] I installed v1.14 today. What settings should I change the wakelocks to in order to match those on v1.13.2? Battery life on that version was amazing.

Also, thanks for all your hard work with leankernel. You have made 6+ hrs of SOT a reality.
[Nexus 6  Original Android Development] Imoseyon:
Good question! It's a bit more complex than that. The formula looks something like this:

default timeout / divisor = new timeout

So if the default timeout is 2000 milliseconds, then using a divisor of 1000 will yield a new timeout of 2 msec. This means that the kernel will hold the wakelock for 2 msec instead of 2000 msec.

Things are actually even more complicated than that but you get the gist. When I have some time I can get into this a bit more.

Disabled means wake source is completely disabled - that's the opposite of stock behavior.

Start with 2, and increase it. I'd play around with it to see what works best for you. I think everyone's usage case is different - for instance, the amount of time you spend on wifi may be vastly different than me.

v1.13.2 had divisor of 4 for both wlan_rx and msm_hsic wake sources.

You... you're famous!

While we're waiting for hue/contrast/saturation post processing to work, you may want to re-validate your calibration with the new implementation in v1.14.1. I do believe the same RGB values are used in both but it won't hurt to verify.
[Nexus 6  Original Android Development] Gnex1:
Thanks again Imoseyn :good::good::good:
[Nexus 6  Original Android Development] ezy1022:
I couldn't find this previously discussed here, but can someone give me a quick explanation on "power saving mode for cpu scheduler" and the difference between power saving and performance as the options? For example when are these changes making a difference? And why is performance the default option?

Thank you

N6
[Nexus 6  Original Android Development] spinkick:
What does Wlan_Rx do, anyway? I've put it to 8 and I dont see a difference in connectivity.

---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------

This should help

http://xdaforums.com/showpost.php?p=58313978&postcount=1651
[Nexus 6  Original Android Development] Damon13:
I think this particular wake lock is triggered any time the phone is awoken from deep sleep to send or receive data on wifi, I have mine set up to 1,000 and so far so good. I have gotten my emails on time and MMS is working via wifi and off.
[Nexus 6  Original Android Development] jiv101:
Sorry for the question but where do I find lkconfig_cleaner.zip I searched around but can't find it
[Nexus 6  Original Android Development] urnamese3:
Hey [MENTION=3357040]Imoseyon[/MENTION] can you please have a look at this? http://imgur.com/AdL9ZLM

I was trying to edit the RGB control values and I realized an noticed an error came up
[Nexus 6  Original Android Development] BrianTX:
It's in the "util" folder on his download page
[Nexus 6  Original Android Development] jiv101:
Ahhh thanks

Edit: also getting this error when trying to apply my min. CPU freq to 300
[Nexus 6  Original Android Development] rignfool:
Actually... That's not an error...

Its that cpu2 and cpu3 are offline...

Well... Maybe it an error...

Are you using mpdecision? How many cores online did you choose in lkconfog?
[Nexus 6  Original Android Development] jiv101:
Well I just changed it to only 2 cores with mpdecesion off which I doubt know is a good idea
[Nexus 6  Original Android Development] rignfool:
That explains that... Can't set frequencies on a core that's offline
[Nexus 6  Original Android Development] jiv101:
Is it safe to run the 2 cores only without mpdecesion
[Nexus 6  Original Android Development] purian23:
Yeah I'm running Lean Kernel v1.14 so what? Lol

It actually works very well with the ElementalX app since it has built in settings for s2w and dt2w!

Thank you [MENTION=3357040]Imoseyon[/MENTION]!
[Nexus 6  Original Android Development] rignfool:
Of course its safe...

You might get some lag when doing serious gaming... But otherwise... You should notice no difference
[Nexus 6  Original Android Development] wrongway213:
I think Imoseyon said before that if the load got too high all four cores still automatically kick on even in the two core option - or could you still notice gaming lag even if that's the case? (Asking purely to learn, I don't play many games and I'm happy with 2 cores lol)
[Nexus 6  Original Android Development] rignfool:
Hmmm... I didn't think [MENTION=3357040]Imoseyon[/MENTION] had any kind of kernel based hot plugging...

I can only speak to unplugging since I run all 4 cores on and shut 2 off with tasker at screen off

I will say I've noticed at 15% battery... The SoC unplugs cpu3

*shrug*
[Nexus 6  Original Android Development] samdroid24:
Don't know if this was discussed already, but how come when I turn off dt2w in the display settings and Terminal Emulator, it turns back on after a little while? How can I make it stick?
[Nexus 6  Original Android Development] rignfool:
You're running slimlp... They have the adjusted power hal...

Use this init.d script I stole from [MENTION=2033478]Yank555[/MENTION]

Disable d2tw

echo OFF > /sys/bus/i2c/devices/1-004a/tsp

chmod 444 /sys/bus/i2c/devices/1-004a/tsp

The chmod makes it so the powerhal doesn't turn back on double tap to wake
[Nexus 6  Original Android Development] samdroid24:
Currently on LiquidSmooth ROM, which runs SlimLP, correct? And I have to type in that command on terminal emulator?
[Nexus 6  Original Android Development] tom.lockhart:
To all those running 1.14 - any issues with completely disabling the msm_hsic_host or wlan_rx_wake?

What divisor is everyone using, I'm still on 1.13 and loving life, but wlan_rx and msm_hsic are my two biggest wakelocks other than PowerManagerService ones. Don't want to lose any functionality.

Thanks in advance.
[Nexus 6  Original Android Development] datajosh:
My divisor is at 4 for both right now, no issues so far.
[Nexus 6  Original Android Development] Damon13:
I disable msm_hsic_host and set the divisor for wlan_rx_wake to 1,000, so far I have no issues with making calls, MMS, or receiving emails via WIFI or LTE.
[Nexus 6  Original Android Development] madAdam6LOVE:
My phone is finicky so I dialed back to 3. When I went to 5 I got a reboot during a phone call. At 4 I get Gmail freezes.
[Nexus 6  Original Android Development] DespairFactor:
You guys are posting so much, I can't keep up.

[MENTION=3357040]Imoseyon[/MENTION] and I are still looking into superuser support, don't worry you guys
[Nexus 6  Original Android Development] Imoseyon:
In the test folder, v1.14.5 is a test kernel for superuser selinux fixes. If you're on CM or a ROM with integrated superuser (not supersu) please give it a try to see if root works.
[Nexus 6  Original Android Development] ballaz:
What is implemented in test version 1.14.4? I see discussions on 1.14.1 and 1.14.5 but no mention of 1.14.4
[Nexus 6  Original Android Development] BrianTX:
I had set msm_hsic_host to 1000 also, were you able to receive calls while your phone was in deep sleep? My gf tried calling me a bunch of times earlier, and my phone never rang. I have since set it to 100, but she's at work and haven't tested since.

Edit- Call received no problem with it set at 100, will test again with it at 1000 to see if the calls don't come in again or if it was just a network issue earlier.
[Nexus 6  Original Android Development] bradputt:
I'm at 1000, receive calls no problem
[Nexus 6  Original Android Development] Damon13:
Hello Brian, I disable Msm_hsic_host in Lkconfig and set the time interval for wlan_rx to 1,000. My battery has been superb, I just had a 19 min conversation with no problems. I also received a few phone calls and send a few MMS to friends. I used mailbox and not Gmail for emails and so far I have received my emails on time.

By the way I have DT2W and S2W disable. I also set the power saving mode in LKconfig as well as option 1 under core control configuration.

Hope it helps!
[Nexus 6  Original Android Development] Imoseyon:
Ok finally back home from a long day at work. Let me see if I can respond to most of the questions here.

You must be on v1.14.1. That's ok, the new KCAL implementation doesn't use that sysfs node. It should still work fine.

That's normal as well. That just means that your other cores are offline. I thought I silenced those errors in the script but apparently not - i'll fix that.

Ok, here's the breakdown:

1) 1.14.1 = savoca's KCAL implementation (with previous rgb control implementation reverted)

2) 1.14.4 = Linux 3.10.69 and a bunch of CAF commits merged

3) 1.14.5 = attempt to fix superuser on CM12

4) 1.14.6 = attempt to auto-mount f2fs filesystems (data and cache)
[Nexus 6  Original Android Development] ballaz:
Thanks, so 1.14.5 can be flashed by those using SuperSU? Apologize for so many questions

Edit: Disregard, flashed 1.14.6 and all is fine.
[Nexus 6  Original Android Development] bradputt:
just a question, sorry if this is asked before

Are RRO Layers supported in this kernel?
[Nexus 6  Original Android Development] mimsiroll:
OP, good day. I'm just curious about these two wake locks. Can you tell me what those are and are those hogging my battery?? Or is it just normal?? My phone doesn't seem to go on a deep sleep.

Here's the pic
[Nexus 6  Original Android Development] Damon13:
I am currently on Chroma with LK and RRO layers are indeed supported. USAN03 has a sweet theme as well as Synergy V4
[Nexus 6  Original Android Development] rignfool:
Layers is all ROM... And kernel agnostic
[Nexus 6  Original Android Development] smclaughlin3:
Is 1000 hold the wakelock less than 8. Thanks
[Nexus 6  Original Android Development] daleski75:
Turn off ambient display
[Nexus 6  Original Android Development] Smallsmx3:
So is everything built up in the test kernels meaning the last has everything merged in previous tests?
[Nexus 6  Original Android Development] smclaughlin3:
Stops wakelock more than 8?
[Nexus 6  Original Android Development] Damon13:
According to Imoseyon, you can probably also set it to something like a 1000 (yes you can actually go higher than 8), if you still want to allow kernel to instantly hold this wake source and release.
[Nexus 6  Original Android Development] old_fart:
I keep that off and the pesty, kernel "PowerManagerService.Display" is still the 'numer uno' bad boy on my list. . I read somewhere that it is a 'catch-all' for many sources ?
[Nexus 6  Original Android Development] Imoseyon:
Yes so v1.14.6 for instance has everything that previous test kernels have.

yeah those wakelocks are a collection of ROM/application wakelocks and mostly have nothing to do with the kernel itself. Here this should help: https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/PowerManagerService
[Nexus 6  Original Android Development] smclaughlin3:
With these new screen options is there a app to configure it or how to access the extra screen configurations? Thanks
[Nexus 6  Original Android Development] mugendon:
Uh, "PowerManagerService.Display" is just the wakelock for keeping your display on ^^ Check your screen on time, it matches the time the ""PowerManagerService.Display" wakelock was held ;)

I think the catch all is "PowerManagerService.Wakelocks" :)
[Nexus 6  Original Android Development] Imoseyon:
Yup PowerManagerService.Display should be a collection of display related rom/application wakelocks.