yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] khanam:
For me the dd+ version worked, the atmos one doesn't have the script we need
[Nexus 6  Original Android Development] elkay:
The Atmos one installed fine and ran for me, but the audio was littered with random static as if the processor couldn't quite keep up. Turning off Atmos and just using the Viper audio settings brought the sound back to normal.
[Nexus 6  Original Android Development] Zaf9670:
Are you suggesting to install the kernel, boot into Android, and then download SuperSU?

I haven't tried that but I can on my next update soon.
[Nexus 6  Original Android Development] rignfool:
This was in reference to all the reports of screwed up flashing...

I prefer to use leankernel... But there is an selinux policy issue with pure nexus...

The worst part is it would have no bearing on my usage... But I just can't have things not work...

Also... The tendency of this kernel to need a reboot to turn cpu2 and cpu3 back on after a low battery episode is annoying as well...
[Nexus 6  Original Android Development] Zaf9670:
I either haven't noticed the core 2/3 issue or it isn't affecting me on the cm builds.

Is there not a way to manually adjust the selinux policy post boot? I know there used to be an app for that used in Lollipop.

I'm just having issues with SuperSU installing sadly... I have lost root access for the moment but it's not crippling me yet.
[Nexus 6  Original Android Development] rignfool:
I don't mess with enforcing vs permissive...

I leave that alone... I don't really understand it...

And for me... 100% repeatable... Run leankernel... Run battery to about 10%... Charge to 100%... Using kernel adiutor... See what cores are online... And then try turning the 2 that are off on...

Only solution is a reboot
[Nexus 6  Original Android Development] holeindalip:
Ive said this before in this thread Franco solved the cores offlining and not coming back online, be said its when the battery hits 36c the only solution like you said is to reboot or see if imoseyon can update the kernel
[Nexus 6  Original Android Development] chrisram88:
So this is why my phone lags when it's down to 10% per say. I was wondering what was going in. Thanks for the heads up. Lean still gives me the best results per my usage
[Nexus 6  Original Android Development] :
Enforcing VS permissive

Enforcing: Stops things from running out of context (check your logcat for AVC denials)

Permissive: Log things that try to run out of context, but let it happen (still gets logged as a denial)

The 10% thing sounds like BCL kicking in. It's broken. While LeanKernel allows for disabling BCL from hotplugging, I find it's better to just break the BCL workque completely if you want userspace control.
[Nexus 6  Original Android Development] KonoeKyon:
It might just because at 15% and bellow it unplugged cores like stock kernel does, it drops 1 core at 15% and a second core at I think 8%. For whatever reason mpdecision seems to not bring cores back online from time to time. You can see it in the thermal-engine-shamu.conf file in /system/etc/. You can also modify the file if you want to prevent it from doing that among other things such as CPU throttle and GPU throttle at certain battery levels. Although BCL could be the issue if he doesn't enable to option to disable the hotplugging.
[Nexus 6  Original Android Development] rignfool:
It is not BCL...

I know its not BCL...

(I should make a macro)

It cannot be BCL... Because I have 2 cores online... At 2.7 ghz... With full battery...

If it was BCL... the cores would be at 1.9 ghz...

Also... BCL eventually shuts off... This... Does not...
[Nexus 6  Original Android Development] KonoeKyon:
Well it does kick off cores by default when bcl gets triggered, which happens more often at low battery levels, if the cores got stuck offline that would cause you to have only 2 online at full charge with 2.7GHz. But again I also said it's likely the cores going offline as per what the thermal-engine-shamu.conf file calls for at low battery, and just getting stuck in an offline state. I've seen the cores stuck offline happen on stock kernel after hitting low battery and charging, and I seen it on other kernels that respect the throttling from that conf file. But I don't have that happen every time like what you said. It's random if they get stuck offline.
[Nexus 6  Original Android Development] smclaughlin3:
Is there the ability to prevent cores lowering on low battery or vice versa like on lp? Thanks
[Nexus 6  Original Android Development] bchaney16:
Looks like some of these numbers are not in the range allowed in lkconfig. Anyone have a conversion to the new numbers?
[Nexus 6  Original Android Development] derdjango:
Here you go.
[Nexus 6  Original Android Development] adm1jtg:
Just came back to lean kernel and am a little confused..... I have 3.4 and been running it just fine.... I see now there is a 3.5 Great I thought lets see what changed.... Looked at the changelog which didn't say very much so went to the source link.. Well the source link lists the last commit as December... Is there a new source link I checked all three branches and dont see anything for 3.5 at all. What am I missing?
[Nexus 6  Original Android Development] droidroidz:
I don't think he pushed it yet to github is all.
[Nexus 6  Original Android Development] :
Download server is down! :(

Nexus 6 64gb - AOSiP Rom 6.0.1 [MENTION=3705640]520[/MENTION] dpi

LG G watch R
[Nexus 6  Original Android Development] Lawlrus:
Use the mirror?
[Nexus 6  Original Android Development] clothednblack:
Latest Su installed, busybox says it's installed and su in terminal was done.

Posted from a Nexus 6 running Slim Rom

Edit: I didn't mean to sound rude, I was making fun of myself because the instructions say what to do but it wasn't working, and it's still not working.

Su version 2.37

Free busybox from the market

I see the config but typing a number and enter doesn't do anything, I will try a different busybox
[Nexus 6  Original Android Development] Mistertac:
Hey it's all good!

Maybe check your SuperSu log just to be sure your terminal didn't get it's Superuser rights denied. Side from that, not too sure.
[Nexus 6  Original Android Development] clothednblack:
Well, I will look at su, in the mean time, I installed busybox pro and I got an error

Posted from a Nexus 6 running Slim Rom
[Nexus 6  Original Android Development] clothednblack:
Got it. I was using terminal emulator from within another app (3c toolbox) now it's working because I downloaded just straight terminal emulator apk. Still trying to find out why busybox failed yet still works

Posted from a Nexus 6 running Slim Rom
[Nexus 6  Original Android Development] old_fart:
The code cooker [MENTION=2906672]dsmitty166[/MENTION] over in Euphoria posted beta 0.4 a little while ago. Very cool. Hmmm, what does the "Support alarm in power off charging mode" do ? ? ? I'm going to have to plug mine in a have a look see. Well, there's a green led and an amber led lit. Their brightness seems a-okay. . [MENTION=3357040]Imoseyon[/MENTION], sir. . . are you and the rom maker working on the same LEDs ?

Amber's gone and all I got is green now.
[Nexus 6  Original Android Development] carlz28:
So lets say I used the lkconfig to change RGB. And by accident, lets also say I hit "0"...zero..... Which turned the screen black. Assuming this set all values to zero or something weird. I was able to boot back into bootloader and flash the stock-noforce_encrypt kernel. All booted up fine again. Decided to reflash LK and upon boot screen went black again. Can you tell me where to look to wipe the data I entered in the lkconfig so it goes back to default settings when LK is flashed again?

I know I can fix this by doing a factory reset, but rather not go that step. Kinda like LK cleaner...
[Nexus 6  Original Android Development] eL_777:
Yeah... I just did this too and decided to restore back to my beginning point. I was showing my wife the color temperature differences and my thumb slipped and I hit enter before I finished typing all the numbers. I'm such a cotton headed ninny muggins... On another note, I found 245 245 255 to be a good setting... not too cool or too warm, at least for my eyes.
[Nexus 6  Original Android Development] Johnny424:
lol that makes three of us. had to restore backup to get straightened up
[Nexus 6  Original Android Development] zephiK:
Probably means when the phone is turned off, it will still ring your ringtone for your alarm. This was a feature on the OPO.
[Nexus 6  Original Android Development] natezire71:
In the future, you can plug it into a computer and use "adb shell" to access the phone like you would via the Terminal app.

On an unrelated note, how do I turn down the LED brightness? I know it was reduced to 40, but I need it dimmer.
[Nexus 6  Original Android Development] dsmitty166:
Ditto, if this is 40, i cant imagine 100!
[Nexus 6  Original Android Development] old_fart:
Ah, thank you sir. Then my guess about Light Emitting Diodes was WAY off ! Ya.
[Nexus 6  Original Android Development] eL_777:
Yeah I tried that but couldn't get SU through my PC so I had to resort to a restore. Oh well...everything is pretty much back to normal now.
[Nexus 6  Original Android Development] carlz28:
Figured it out. Flashed the stock kernel. Booted. Deleted /data/data/leankernel folder. Reflashed LK and all was good.
[Nexus 6  Original Android Development] Imoseyon:
Correct

cpu-boost is codeaurora's attempt at boosting performance. Aside from boosting performance it does two additional things: 1) messes with your minimum frequency when mpdecision is enabled, and 2) makes kernel unstable when ondemand runs on cpu1-3. This is why I give an option to disable cpu-boost via lkconfig. Honestly I can't tell difference whether cpu-boost is enabled or disabled. Here's the initial description of cpu-boost straight from caf:

cpufreq: cpu-boost: Add cpu-boost driver

When certain bursty and important events take place, it might take a while
for the current cpufreq governor to notice the new load and react to it.
That would result in poor user experience. To alleviate this, the cpu-boost
driver boosts the frequency of a CPU for a short duration to maintain good
user experience while the governor catches up.

Specifically, this commit deals with ensuring that when "important" tasks
migrate from a fast CPU to a slow CPU, the frequency of the slow CPU is
boosted to be at least as high as the fast CPU for a short duration."

Yikes, sorry about that. Let me add this to the FAQ but all you gotta do is go into recovery, mount /data, and delete everything in /data/data/leankernel, and then reboot.

EDIT: I also uploaded lkconfig_cleaner.zip to the "util" directory.

adb shell and running lkconfig again will also work. Actually I set the brightness to 4 (even 40 was too bright). You can try 1 by running this command:

echo 1 > /sys/class/leds/charging/brightness

as a matter of fact i will change it to 1 in beta8.
[Nexus 6  Original Android Development] garyd9:
For the charging LED, I believe that 40 is the max (100%.).

[MENTION=3357040]Imoseyon[/MENTION], are you doing anything to keep the brightness below 40? If I remember from playing with triggers, the kernel trigger will always set the brightness to max whenever it turns it on (from an off state.) So, in the case of a kernel trigger that turns it on while charging, the brightness will go back to 40 if you unplug the charger and plug it back in again (assuming the phone isn't fully charged.)

Sent from my Nexus 6
[Nexus 6  Original Android Development] dsmitty166:
Dropping to 1 only seems to temp drop it for me. It drops for a few seconds, then bumps back up
[Nexus 6  Original Android Development] Imoseyon:
Shoot I think you're right - I'll just do it in kernel space then. To be continued in beta8...

EDIT: or you can just set max_brightness

echo 1 > /sys/class/leds/charging/max_brightness
[Nexus 6  Original Android Development] garyd9:
That works? I never even tried and just assumed that max brightness was ro

Sent from my Nexus 6
[Nexus 6  Original Android Development] Imoseyon:
It does:

root@shamu:/ # ls -l /sys/class/leds/charging/max_brightness
-rw-r--r-- root root 4096 2014-12-02 22:33 max_brightness

However, it's not owned by system. Would you like me to change that? :)
[Nexus 6  Original Android Development] ronyclau:
Can't get 3.5 to work with systemless SuperSU (both 2.67 and 2.65) on CM.

Anyone have the 3.4cm version and can upload it?

RenderServer (i.e. main dl site) shut down last week and the mirror in OneDrive doesn't host that version. :(
[Nexus 6  Original Android Development] akanealw:
https://www.dropbox.com/s/3g4fq6ju849iqdq/lk_shamu_m-v3.4cm.zip?dl=0
[Nexus 6  Original Android Development] ronyclau:
Many thanks! Will try right away.
[Nexus 6  Original Android Development] Zaf9670:
This is only a test using 3.4cm. But the current CM13 nightly boot loops. I reverted the the previous nightly from 3/4/16 and it works fine with 3.4cm.

I haven't been able to use 3.5cm because I can't find a SuperSU before the systemless update.

The current CM nightly from 3/05 had some source kernel updates and I'm assuming it has some conflicts in the lk ramdisk or something along those lines. Like I said I didn't try it with 3.5cm so if someone has tested it and it works let me know. Or I'll just await an update to LK.

Edit: I didn't really test to see if it could be xposed or SuperSU as other potential problems but since it never completed a boot I assumed it was the kernel.
[Nexus 6  Original Android Development] randiye:
what SOT do you guys get?
[Nexus 6  Original Android Development] Talvathir:
About 5 hours.
[Nexus 6  Original Android Development] randiye:
Anyone used both franco r42 and lean kernel and can give a review for both? I'm just tryna use the one that gives the best SOT
[Nexus 6  Original Android Development] nathanchance:
Or you could try them both. Flash one, try it for a few days, then dirty flash your ROM and flash the other one, and try it for a few days. Nobody can simulate your usage and environment but you since everyone uses their phone differently and lives in different places. It's insanely easy to change kernels and test them out, I'd recommend taking initiative on your own since I have seen you asking about kernels for a while now.
[Nexus 6  Original Android Development] junioramboy:
Is this kernel still updated?
[Nexus 6  Original Android Development] Talvathir:
Chances are it can't get any leaner until N is out ?
[Nexus 6  Original Android Development] rignfool:
No... But... We could have some kind of anykernel script packaged with the kernel so I don't lose lockscreen wallpaper and the NFC tile in PureNexus

Edit: orrr... If someone knows the SELinux 'command thingy' so i can put an exception in the su.d directory... I'd be just as happy
[Nexus 6  Original Android Development] smclaughlin3:
is this still up?
[Nexus 6  Original Android Development] gabethepiggy:
not sure, this thread has been dead lately
[Nexus 6  Original Android Development] derdjango:
I guess [MENTION=3357040]Imoseyon[/MENTION] moved on to the 6p.
[Nexus 6  Original Android Development] rignfool:
Now... Normally I would agree with you...

But he still supports the samsuck GS3...

So I think we need patience...
[Nexus 6  Original Android Development] leondestiny:
this kernel works really wonders for me, i flash it over every frikkin Rom that i use.

why ? simply because alone from flashing this kernel it kills the "Split Screen Glitch" for me, many thanks to the Op.
[Nexus 6  Original Android Development] McMannes:
İs this kernel work on marsmallow?
[Nexus 6  Original Android Development] rignfool:
Yup
[Nexus 6  Original Android Development] McMannes:
can anyone send me latest version zip? i cant download from the links.
[Nexus 6  Original Android Development] benleonheart:
Same here. Fully default settings, the only difference is that the 2.6ghz core shifts between cores as in CPU 0, then CPU 1, then 3, and so on.
[Nexus 6  Original Android Development] droidroidz:
Imoseyon ~

Not sure if you plan to update shamu anymore but any chance you can push the 3.5 changes to github for us ? Thank you!
[Nexus 6  Original Android Development] benleonheart:
Anyone? Honestly this gets annoying. :(
[Nexus 6  Original Android Development] paour:
Just in case not everyone is subscribed to the PushBullet channel, here's what [MENTION=3357040]Imoseyon[/MENTION] posted yesterday:

Good luck to you and don't worry about us: I've used Lean for over a year and it's always been stable and fast, and until N Roms become widely available, there's not much I need in terms of kernel updates.
[Nexus 6  Original Android Development] TonyApuzzo:
I seem to be having issues with Strava (GPS sports tracker) with leankernel and default settings. The issue is that the GPS misses many points and thinks I'm stopped for ~50% of the time so my track is very inaccurate. If I use my ROM's default kernel (OmniROM 6.x nightly) then I usually get good tracks.

Any troubleshooting advice or settings that I should try?
[Nexus 6  Original Android Development] derdjango:
Well, for proper troubleshooting, I'd flash another custom kernel since lean kernel hasn't been updated since January.
[Nexus 6  Original Android Development] TonyApuzzo:
I came to LeanKernel from ElementalX which seems to be as bad or even worse with Strava, and has other even more problematic issues on my N6 (lag + battery drain == no bueno.)

OK, back to LK discussion... LK with Strava, the first ~10 minutes works great (updates every 1-5 seconds) but after that, the GPS track only is updated every several minutes. Could this have something to do with Doze? I didn't think it would since the phone is in my pocket while riding a bike, so the stationary trigger should not fire.

Again, this behavior does not happen on stock kernel.
[Nexus 6  Original Android Development] leondestiny:
anyone getting LK work with CM based roms ?

LK always works wonders for me with AOSP based Chroma :)

but i get stuck on the bootanimation with CM based Roms, e.g RR/Bliss.

edit: i have the normal one 'lk_shamu_m-v3.5' and the one 'lk_shamu_m-v3.5cm' i flash the one with 'cm' with the cm based Roms.

but i flash it right after i flash Rom/Gapps then after Gapps i flash the kernel i guess that is not the issue of me hanging on the bootanimation? (and is a wipe cache dalvik needed after flashing LK?) i never needed it after Chroma/Gapps>LK always works for me.

only with CM based i get stuck on bootanimation.
[Nexus 6  Original Android Development] ozzmanj1:
I had the dreaded split screen issue and this kernel fixed it. Major thank you to the OP.
[Nexus 6  Original Android Development] mikeprius:
how does that happen ? I've never had that before
[Nexus 6  Original Android Development] ozzmanj1:
It's actually a common issue on both Google and Motorola forums, lebovo forum now. For me it was causing this issue when playing a YouTube video and them rotating the phone. But LK fixed it.
[Nexus 6  Original Android Development] leondestiny:
split screen issue annoyed the sh** out of me at times, cause it was totally random with every Rom/Kernel combo even trying different Governors etc. nothing helped !

then i crossed with LeanKernel and i have to do nothing, just flash the LK and bam byebye to the split screen glitch never happening not even once with LK , much love.
[Nexus 6  Original Android Development] alphamale:
delete
[Nexus 6  Original Android Development] adm1jtg:
guessing ops issues ended up being far more serious then he first anticipated. hope he comes back
[Nexus 6  Original Android Development] supasanch24:
Has anyone found an alternative kernel that helps with the split screen issue?
[Nexus 6  Original Android Development] droidroidz:
someone just needs to recognize the commit that fixed it and spread the word
[Nexus 6  Original Android Development] rignfool:
It's not a commit...

Your issue is a hardware issue...
[Nexus 6  Original Android Development] supasanch24:
It very well may be a hardware issue, but this kernel definitely makes a difference.
[Nexus 6  Original Android Development] flar2:
That's because it uses interactive governor and doesn't disable mpdecision. The problem is less likely to occur with this setup.
[Nexus 6  Original Android Development] ozzmanj1:
I was on elemental before lean kernel and had the split screen issue, see photos. OK fixed the issue. Does this mean on elemental I can use it but change settings to prevent the issue?
[Nexus 6  Original Android Development] benleonheart:
Stock.

---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------

Theoretically yes

Edit at 05/27/16 7:48 a.m. CST -

[MENTION=2857649]ozzmanj1[/MENTION] Flashed ElementalX 4.04, switched CPU governor to interactive and disabled hotplug for MPDECISION...

Been testing it all afternoon yesterday, all night; cold morning (which seems to trigger screen tearing sometimes), and I get no tearing at all.
[Nexus 6  Original Android Development] bchaney16:
I'm having trouble accessing lkconfig. When I type su in Termux it takes me to root@shamu:/data/data/com.termux/files/home and it can't find lkconfig in there. If I type cd I can get into root@shamu:/ but it can't find lkconfig there either. I have tried reflashing the kernel and the issue persists. Is it a problem with the kernel or my SU? Thanks for any help.
[Nexus 6  Original Android Development] twcobra:
Just a comment on this Split screen issue. I have been having it lately. It seams to happen when my now failing battery gets hot during heavy use or charging. I have a new battery coming in sometime This week. I will share if the new battery resolves the issue. I am sure that excess heat from a failing battery can cause the GPU and CPU to nuts.
[Nexus 6  Original Android Development] rignfool:
You have a path issue...

Uhh...

Iirc

/sbin/lkconfig
[Nexus 6  Original Android Development] bchaney16:
You're right I can see it's in there in my file explorer. Strange thing - even when I have Termux in root@shamu:/sbin and type lk or lkconfig it can't be found. idk what's going on.
[Nexus 6  Original Android Development] xeharo:
Uncheck "Verify PATH entries" under the preferences.
[Nexus 6  Original Android Development] bchaney16:
Where can I find the preferences menu? I don't see that option in the menu when I longpress the screen.
[Nexus 6  Original Android Development] droidroidz:
in the terminal application
[Nexus 6  Original Android Development] adm1jtg:
As much as I LOVED this kernel I have to ask why people are still using it as there have been at least 3 months where security patches affecting kernel code have been released. This kernel hasn't been updated since January and appears to be abandoned.
[Nexus 6  Original Android Development] rignfool:
The best part about this post...

Is that it's just wrong...

Mosey posted overnight in the angler thread... :highfive:
[Nexus 6  Original Android Development] adm1jtg:
I would love to be proven wrong and go back to this kernel myself but until he updates it I cannot and looking at git for shamu so far there has been no activity.

Here is to gladly eating crow when he DOES update our kernel
[Nexus 6  Original Android Development] nathanchance:
Just throwing this out here: http://xdaforums.com/showpost.php?p=67323444&postcount=563
[Nexus 6  Original Android Development] khanam:
Didn't know anything from the security patches pertained to kernel code. Thought all of those related to the android platform?
[Nexus 6  Original Android Development] Droidphilev:
I still use it as it seems to be the only 'full' kernel with it's own ramdisk etc. I need it to let some streaming tv app work with custom roms :(

Would love to see updates!
[Nexus 6  Original Android Development] danmaman:
Not bad this kernel... Love it

Latest krexus rom with lean kernel

Cheers
[Nexus 6  Original Android Development] zymphad:
You'll have to ask imoseyon for his build script and update the ramdisk

But here it is, you can build it inline with it, updated to 101 and latest security patches

https://github.com/zymphad/leanKernel-shamu/commits/lk-m
[Nexus 6  Original Android Development] danmaman:
If you meant me?

I don't have plan for building kernel