yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] zymphad:
If someone wants to test it: https://www.androidfilehost.com/?fid=24588212152303971

Updated leanKernel w/ imoseyon's merges to 3.10.101 and pull from google's latest security patches.
[Nexus 6  Original Android Development] khanam:
Tried it on chroma. Zip flashes without warning but settings about phone displays original rom kernel?
[Nexus 6  Original Android Development] danmaman:
Yes for me too

I've installed latest test version over my stock krexus backup, and nothing happens... It shows stock kernel from my rom
[Nexus 6  Original Android Development] coremania:
Same here, latest krexus with blackbird, still blackbird after

flash
[Nexus 6  Original Android Development] Droidphilev:
AFH says for 6p
[Nexus 6  Original Android Development] danmaman:
Oh okay

Sorry I haven't seen that....

Maybe [MENTION=612901]symphad[/MENTION] can build it for shamu too

But it's curious.... The first 2 pics from left are original lean kernel zip

The other from zymphad
[Nexus 6  Original Android Development] Droidphilev:
It's np. was only for your info. I shamu build would be VERY nice indeed!
[Nexus 6  Original Android Development] zymphad:
Sorry, was an attempt at anykernel2, I'll build Krexus w/ leanKernel instead.
[Nexus 6  Original Android Development] danmaman:
Great news... Mate

But will lean kernel works with systemless Root?

Because lean comes with its own ramdisk.

Just a question

Cheers
[Nexus 6  Original Android Development] rignfool:
Mosey would have to place systemless root into his compiled ramdisk... chainfire's SuperSU patcher would overwrite all his ramdisk changes
[Nexus 6  Original Android Development] danmaman:
Hopefully comes an update soon
[Nexus 6  Original Android Development] ozzmanj1:
Really would an updated leankernel. Only kernel to resolve the occasional split screen issue.
[Nexus 6  Original Android Development] MrBrady:
+1
[Nexus 6  Original Android Development] Semetery:
I get the absolute best battery life out of this kernel for my phone but I haven't been able to use it on the ROM's I've used lately. And on my other N6, yes, it does fix the split screen issue and that alone makes it priceless.

I, too, miss it in a big way! I'd love to see it back moving forward but regardless, thanks for it.
[Nexus 6  Original Android Development] :
can we flash this kernel on last security patch
[Nexus 6  Original Android Development] danmaman:
I miss that kernel on my shamu...:(:(:(:rolleyes::rolleyes:

---------- Post added at 06:59 PM ---------- Previous post was at 06:56 PM ----------

I miss that kernel on my shamu...:(:(:(:rolleyes::rolleyes:

Has anyone the knowledge to build this kernel from github source? With latest patches?
[Nexus 6  Original Android Development] :
thats will be great if someone can help us with that :)
[Nexus 6  Original Android Development] lifeisfun:
Yup, same here
[Nexus 6  Original Android Development] lifeisfun:
Did anyone find other kernel that would prevent screen split issue like lean kernel did?

Thanks
[Nexus 6  Original Android Development] lazyb421:
I have the same problem with my N6. The only other kernel I've found that prevents the split screen issue for me is B14ckb1rd kernel using nightmare governor.
[Nexus 6  Original Android Development] lifeisfun:
Just testing ElementalX with interactive governor and 24 hours later no split.
[Nexus 6  Original Android Development] lazyb421:
Oh yeah, I had heard that interactive governors help with the splitting issue. I just prefer ondemand-based governors as they seem to play better with the sound mods I have on my phone. Glad you found something that works for you as that screen splitting is a PITA. :good:
[Nexus 6  Original Android Development] mnsiw:
Hi :) I'm on AICP 8.0, getting these color values in thousands, how to get similar result with these values, any idea?
[Nexus 6  Original Android Development] runekock:
I guess that you just multiply the values by 128. Try that.
[Nexus 6  Original Android Development] mnsiw:
I've switched to Sigma Kernel, now it shows correct values, but seems like no kernel manager support apply on reboot on Oreo, some crash on boot, others do nothing on reboot.

Edit: Finally got it working with EX Kernel Manager.
[Nexus 6  Original Android Development] xshallowgrave:
Is this kernel 7.1.2 compatible?
[Nexus 6  Original Android Development] Black_Hat01:
Nope, only goes to 6.0.1 I think.
[Nexus 6  Original Android Development] xshallowgrave:
Shame, wanted to try it out. Any suggestions for a minimal kernel? I'm using ElementalX right now.
[Nexus 6  Original Android Development] Black_Hat01:
Franco or ElementalX are pretty much the only minimal kernels around now.
[Nexus 6  Original Android Development] garyd9:
No need... The liblights I'm working on scales the 0 through 255 value from android to a 0 thru 40 value. At least that's my interpretation of how the HAL should handle it.

Of course, my code never expects the max value to change at runtime... Having to read max brightness each time android sets the light would suck...

Sent from my Nexus 6
[Nexus 6  Original Android Development] Drefsab:
Not sure if you have seen this or not http://xdaforums.com/htc-one-s/deve...linanddart-t2948552/post57208917#post57208917 people are raving about intelliplug plus intellimm from faux. His code is available and from what I read it should work on any of the snapdragons 800's and up. Would it be worth looking at for the nexus 6?
[Nexus 6  Original Android Development] housry23:
Faux bought a Nexus 6 and he's waiting on it to ship. We will have faux kernel soon enough. Just let imoseyon do his thing. If he wants to implement faux stuff he will, but he states right up front that if you like tons of settings and options in your kernel, that this probably isn't the one for you. I'm not sure I'd you're new to the nexus scene or not, but if you are, you're in for a treat. Roms and kernels will be abundant and you'll have a hard time choosing what to run!

Sent from my Nexus 6
[Nexus 6  Original Android Development] Drefsab:
Yup I saw that faux is still waiting for his to ship like me, I was just thinking more to bring it to Imoseyon's attention so he can assess it and see if its something that he would like to investigate given that faux has only just pushed out the the source for its on this git.

I am new to the nexus devices however the old HTC one X scene was great loads of devs etc, I was a little disappointed there was not the same on the One X+ when my device had to be replaced hence why I chose a nexus this time around wanting to get back to a device with a really active dev scene.
[Nexus 6  Original Android Development] natezire71:
Even when my phone is fully charged, the LED remains on.
[Nexus 6  Original Android Development] h3ckman:
Same for me too, it is green.
[Nexus 6  Original Android Development] mjohnson4580:
If I wanted to change the color for my screen using init.d. where can I locate the files so I can write the script for init.d.
[Nexus 6  Original Android Development] natezire71:
When I unplugged, the LED was still on. I had to reboot to turn it off.
[Nexus 6  Original Android Development] h3ckman:
Oh nice, that fixed it for me.
[Nexus 6  Original Android Development] Imoseyon:
leanKernel philosophy

Ok I think it's time for this post. :)

Those of you who used my kernels in the past on thunderbolt, gnex, galaxy s3, note 3, nexus 7, etc. already know what leanKernel is all about.

I develop leanKernel *almost* in a total vacuum. I rarely ever look at other devs work, nor do I visit their threads. In fact, I don't even know who most of them are. It's been this way for years (yes i've been doing this for a while). The only time I ever collaborated with another community dev was with [MENTION=3292224]franciscofranco[/MENTION] - great guy, I highly recommend his kernels if you're not on leanKernel.

This is what makes leanKernel unique. Aside from my usual desire to keep the experience as stock and as lean as possible, I didn't want leanKernel to be like other kitchen sink custom kernels out there. This also limits leanKernel users obviously, as it's targeting a smaller niche group of users. I believe android kernels actually should do as little as possible, and let the ROMs do their thing, but at the same time there are tons of enhancements are optimizations that can be done to stock kernel.

I have a very demanding full time job (I work with Linux) and a family, so this philosophy actually kinda works out for me due to my limited time for kernel development. :)

So what does this mean? I encourage everyone to try other custom kernels - tons of great smart devs out there like faux, franco, flar2, etc (especially on a nexus device). I think a lot of you will come back to lean. :D
[Nexus 6  Original Android Development] Imoseyon:
take a look at /sbin/lk-post-boot.sh and /sbin/lkconfig. You will want to do something similar for your init.d script.

I will take a look at that today.
[Nexus 6  Original Android Development] zephiK:
Good to hear that Imoseyon follows his stance and doesn't change for others. Remembered the old days when Franco kernel updater app included lean kernel in the updater :D enjoying b7 and really appreciate that you don't add features other people do and keeping it minimalistic as possible.
[Nexus 6  Original Android Development] rignfool:
Is it just me... Or is lkconfig screen off freq not set up for our device?
[Nexus 6  Original Android Development] Imoseyon:
For those of you with LED not turning off issue, PM me? I can't for the life of me reproduce it on my phone - perhaps it's because i'm on a different build.

Should work.. Make sure you're on latest beta?
[Nexus 6  Original Android Development] ChaosMinionX:
[REQ] - Would it be possible to add some more TCP congestion algorithms? I saw much better throughput in Boston, MA area using the Illinois algorithm.
[Nexus 6  Original Android Development] Imoseyon:
That's interesting. Send me a PM and maybe we'll do some testing with a custom build. :)
[Nexus 6  Original Android Development] garyd9:
When in that state, I'm curious the output of "cat /sys/class/leds/charging/trigger" and "cat /sys/class/leds/charging/brightness"

It might also be useful to know if they have replaced the lights.shamu.so with the one I provided in the dev discussion thread. If they have, it might be related: My shared lib gives android control of the "charging" LED as android's "battery" indicator (but doesn't change the trigger.) So, the kernel and the userspace could be fighting over the LED.
[Nexus 6  Original Android Development] rignfool:
My bad... Sorry... Works as prescribed...
[Nexus 6  Original Android Development] brizey:
My crappy binning has me volting to 1210 for 2.9, but it works, lol.

Any thought to reduce frequency steps? Most never really get used anyway. IIRC, you did that on your thunderbolt kernel.

I do have an oddball question. One thing I have never understood is how exactly frequency changes help with battery. The power consumption would have to be massively nonlinear vs voltage squared for it to work. Example: 2880 MHz @ 1210 MV is 3.84 times more efficient per clock cycle than 223 MHz @ 660 MV in terms of voltage squared. So the current draw would have to be much larger, too. Is it just the thermal differential causing a much higher effective resistance? Sorry about the of topic question.
[Nexus 6  Original Android Development] eL_777:
Is it possible that this kernel has disabled the ability to see the screen on time in the battery settings? For some reason it isnt showing up in the settings anymore and I'm trying to narrow down the issue. Also, I'm able to see SoT in gsam battery monitor.:confused:
[Nexus 6  Original Android Development] brizey:
It's working for me on rastapop.
[Nexus 6  Original Android Development] natezire71:
I'm on beta7 and I'm able to see the SoT
[Nexus 6  Original Android Development] digweed4me:
has anyone tried beta 7 on latest LRX22C BUILDS?
[Nexus 6  Original Android Development] eep2378:
Yes. No issues. I don't believe much was changed on the rom side.
[Nexus 6  Original Android Development] Imoseyon:
I talked to one person having this issue and I don't believe this is the case. It's still a bit of mystery for me - I can't repro.

You used my kernel on thunderbolt? A blast from the past. I actually did remove some slots - but I stopped doing it after thunderbolt. There were just way too many questions from users whether any particular problem they were running into was due to not having enough freq steps.

As for your question, I'm not sure if I understand... Are you asking why we don't simply run it at max frequency at all times due to its better voltage efficiency?
[Nexus 6  Original Android Development] brizey:
Yeah. Pretty much. You do use more power at higher speeds due to the increased voltage required to maintain enough current. But you also get a lot more done because the clock speed is so much higher. Your clock speed spread is about 15x, but the voltage squared spread is less than 4x. So the only way you save if there is nothing to do (sleep), or if the current draw rises as well as clock speed increases, which it probably does. Basically I an making the performance governor argument. I think all we really need is sleep, idle, and max. Everything else over complicates with little to show for it. Figured you kind of thought the same way given the way that the X governors work and the fact you have dropped slots before.

Edit: Just read though a few decks and a whitepaper on this. The current DOES go up. The voltage increase is needed to drive more current so that the logic gate's capacitors charge more quickly since it is effectively a little RC circuit. Since you are charging more capacitors per unit time, the current increases. So the power is not proportional to V^2.

Thanks for listening, lol.
[Nexus 6  Original Android Development] Imoseyon:
Ah yeah this has been brought up before. It's the classic race to sleep argument (to an extent at least). There's definitely a case for that.

Simply put though, over 90% of the time the phone isn't doing anything. You're staring at the screen while it's sitting idle. At the same time there will be some small workloads because Android is a multitasking OS - these small workloads won't tax the CPU much (ie. you're listening to music, etc.). So even if you average it all out I'm sure having freq steps is hugely beneficial over something like Performance.
[Nexus 6  Original Android Development] Imoseyon:
Beta8 is up.

1) Cleaned up lkconfig quite a bit. Should be less prone to mess up your phone. ;)

2) I removed a ton of unnecessary kernel crud. Beta8 should be quite a bit leaner than beat7. Do let me know if you notice something that suddenly stopped working though.
[Nexus 6  Original Android Development] Xileforce:
Testing now! I'm always game for even leaner lean kernel!

---------- Post added at 07:48 PM ---------- Previous post was at 07:40 PM ----------

So far so good! Up and running just fine

---------- Post added at 07:49 PM ---------- Previous post was at 07:48 PM ----------

It seems like Ondemand governor is similar to what you are looking for. It always ramps straight to max speed and then slowly ramps back down. Unlike interactive which slowly clocks up to max. At least that's what my understanding is.
[Nexus 6  Original Android Development] EniGmA1987:
Interactive can ramp up pretty quick, depending on how it is tuned.

Anyway though, I thought OnDemand was having issues on this phone?

Ill be testing the new build a bit later tonight when I get home :D
[Nexus 6  Original Android Development] zephiK:
ondemand has been fixed since b5
[Nexus 6  Original Android Development] EniGmA1987:
Cool. Didnt realize that.

---------- Post added at 09:56 PM ---------- Previous post was at 09:47 PM ----------

I understand your thinking on this, but the main issue with only needing sleep, idle, and max is that you can have a game that only puts 70% load on the chipset because it is not the heaviest graphics. So to run 100% speed would be a waste because to run perfectly smooth it only needs to ramp up to 75%, that extra 25% is wasted battery. In another situation, we may be reading a text and the phone is technically not doing anything, but there could be things going on in the background such as syncing, playing music, disk cleanup, etc. This would give bad performance at idle speed because it needs a bit more power to do the task, but nowhere close to 100% speed. So we need a frequency step just a few hundred MHz up to do the task efficiently. So the different steps are very useful. The one thing that is the most important to do is the tuning of the governor. With proper tuning we can get just the performance we need to maintain perfect smoothness, without overshooting and wasting battery. This is the best thing for the phone in all situations, but the tuning has to be just right.

Also Id like to point out that the power equation is actually p=v2*f*c. This is the power use, is equal to the voltage squared, times the frequency, times the capacitance. So as we go faster, not only is the voltage going up which is a huge change in power cost, but we also draw more simply from frequency being higher, and then we also must figure capacitance but that is pretty hard since we have no idea of the internal SoC design and all that. This is why hotplugging is so good, because not only does frequency drop down to nothing or close to it for most of the circuit, but the voltage is also lowered because so many things are not even used anymore, and the things being shut down also lowers capacitance.
[Nexus 6  Original Android Development] Imoseyon:
So I managed to enable the qualcomm hardware crypto engine tonight. I can see that it's being used:

Qualcomm crypto accelerator 1 Statistics
ABLK AES CIPHER encryption : 49275
ABLK AES CIPHER decryption : 2067622
ABLK DES CIPHER encryption : 0
ABLK DES CIPHER decryption : 0
ABLK 3DES CIPHER encryption : 0
ABLK 3DES CIPHER decryption : 0
ABLK CIPHER operation success : 2117055

But either I failed somewhere (which is very likely), or it's just really badly implemented because androbench says i'm now about 4 times slower than I used to be. lol. Maybe this is why google decide to use software encryption. I'll keep digging a bit.
[Nexus 6  Original Android Development] Media_Blitz:
Can't make higher frequencies stick

Im on beta 7. This has happened two times already: after a while, the higher frequency lowers itself to 1.7ghz. After it does this, i cannot go any higher than that frequency. It always goes back immediately. I can, however, go lower than 1.7ghz. The only way to make frequency stick to the higher ones is if i restore my nand backup. Reflashing any beta kernel doesn't fix it. Nor does rebooting. I deleted mpdecision with root explorer. You think this is causing it? Also using Trickster Mod. Thanks.
[Nexus 6  Original Android Development] zephiK:
Go to OP and use the Patched MPDecision. Also be sure you're on the latest SuperSU 2.37.

Also beta8 is out ;)
[Nexus 6  Original Android Development] Xileforce:
Very interesting. I remember seeing a G+ post by faux and he had managed to make io speeds with encryption enabled pretty much normal as I recall but he didn't say how. Will be interesting to see what you find as you keep playing with it!

---------- Post added at 10:41 PM ---------- Previous post was at 10:40 PM ----------

Also, I would be interested in seeing how OnDemand compares to Interactive in terms of performance and battery. I would Imagine OnDemand would perform marginally better, but its effect on battery life seems less certain.
[Nexus 6  Original Android Development] bradputt:
Damn, Google should employ you guys
[Nexus 6  Original Android Development] ryude:
I remember on the Galaxy SII they removed a ton of steps and the performance/battery life gains were pretty big. Not to mention you can undervolt a little bit more due to that.

Just a thought.
[Nexus 6  Original Android Development] brizey:
I have been using ondemand... Pretty much always do. In terms of the 70% load...I think it depends on the overhead cost of switching click speed... You can run 100% for 70%of the time and get the same amount of work done, and you won't be able to tell the difference if your clock speed change rate is fast enough (low sample interval). But there is some cost to switching. I think a few steps with a fast sample interval may work better because you get more time at the low frequencies. Similar (not a perfect analogy) to why a digital amp is more efficient.

I would have to do the math at some point. I'm sure it's been done, buy I like to understand things myself, lol.
[Nexus 6  Original Android Development] Tommy-Geenexus:
It's bad implemented and really slow.

This is the same on all qc devices using hw encryption.
[Nexus 6  Original Android Development] jimmydigital00:
I got a stinkin 2

Should I be concerned? Should I try to get a different phone?
[Nexus 6  Original Android Development] eep2378:
Ah nice! I'm decrypted so I'm good to go with this :) What you guys using to control, Trickster? Any other apps that have been updated for 5.0? [MENTION=1811927]simms22[/MENTION] is that carlo's second build? I had FC's that didn't subside.
[Nexus 6  Original Android Development] gamewarden234:
Got a 6. Not much better. Wife got a 6 also so I don't feel so bad.
[Nexus 6  Original Android Development] Imoseyon:
So pvs2 means your factory default for 2.7ghz is most likely at 1.13V. In comparison mine (pvs6) runs it at 1.09V. See if you can undervolt to match PVS7 (which is somewhere in the middle):

< 300000000 740000 76 >,
< 345600000 750000 88 >,
< 422400000 760000 109 >,
< 499200000 770000 130 >,
< 576000000 780000 151 >,
< 652800000 790000 172 >,
< 729600000 800000 194 >,
< 806400000 810000 217 >,
< 883200000 820000 239 >,
< 960000000 820000 260 >,
< 1036800000 830000 282 >,
< 1113600000 840000 306 >,
< 1190400000 850000 330 >,
< 1267200000 860000 354 >,
< 1344000000 870000 378 >,
< 1420800000 880000 402 >,
< 1497600000 890000 428 >,
< 1574400000 900000 453 >,
< 1651200000 910000 479 >,
< 1728000000 920000 504 >,
< 1804800000 930000 531 >,
< 1881600000 940000 558 >,
< 1958400000 950000 585 >,
< 2035200000 960000 613 >,
< 2112000000 975000 642 >,
< 2188800000 990000 675 >,
< 2265600000 1005000 708 >,
< 2342400000 1020000 742 >,
< 2419200000 1035000 777 >,
< 2496000000 1050000 813 >,
< 2572800000 1065000 849 >,
< 2649600000 1080000 886 >;

If you can match, then you're good. (2nd number is the voltage)
[Nexus 6  Original Android Development] simms22:
a fc? where? i get them at the very beginning that go away asap, and when opening the settings, 3 times.
[Nexus 6  Original Android Development] zephiK:
That's the same build simms posted from the other thread. I'm using trickster for now.
[Nexus 6  Original Android Development] jimmydigital00:
Nice performance boost

Just installed this kernel ran a few benchmarks and am seeing a 15% increase on multiple benchmarks.

I can also feel that the phone seems to be running more fluid.

I did a universal -24 undervolt and everything is running perfect.

Thanks for this!!!

---------- Post added at 05:33 PM ---------- Previous post was at 05:27 PM ----------

Tried your settings and the phone reboots.

I will see how low I can go. Thanks for sharing.
[Nexus 6  Original Android Development] eep2378:
I didn't try the second build, but I was getting the fcs in the settings like you mentioned also messenger fc and on most google Apps. Clean flash.
[Nexus 6  Original Android Development] simms22:
if you do get a fc with messenger, uninstall it, then reinstall. that fixed it for me. give me a few minutes, ill upload the second build and pm you :)
[Nexus 6  Original Android Development] sn0warmy:
No worries, take your time. I appreciate the effort.
[Nexus 6  Original Android Development] eep2378:
PVS 6 here too :)