yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] MaLiXs:
I dont know why but I'm unable to have pc connection and phone won't stay in charge... then concoction is don but it automatically disconnect by itself (the charge status just blinking on the lock screen...

I just don't know what to do with that...
[Nexus 6  Original Android Development] cr4ck3r4lif3:
Absolutely!
[Nexus 6  Original Android Development] grayskul:
Yes!
[Nexus 6  Original Android Development] pkgnex:
Will the next version of the kernel go back to selinux = enforcing since chainfire's root now allows it?
[Nexus 6  Original Android Development] umpireflux:
Sorry [MENTION=3357040]Imoseyon[/MENTION], it turns out that it was a problem with Xposed, which has since be updated. Thanks to [MENTION=5936642]Plifispen[/MENTION] for pointing it out to me!
[Nexus 6  Original Android Development] xtzz:
I understand that you're shifting focus on Android M and nothing new should be expected for LP.

Does that mean that at least you will support the changes going on in CM?

I'm asking this, cause the CM nightly from 10/08 won't boot at all with lk 2.14cm.
[Nexus 6  Original Android Development] umpireflux:
Did you read my post directly above yours? Do you have Xposed, and if so have you updated to v75? 20151008 with 2.14cm worked for me
[Nexus 6  Original Android Development] mathow:
I had this problem too. I was able to get it to boot by formatting the system partition, then flashing the rom, the kernel, gapps, and xposed in that order. Also make sure you're on the latest version of xposed. The first boot was painfully slow, FYI.
[Nexus 6  Original Android Development] Shadester9:
I want to flash this with M but I see you guys are saying flash version 2.5. However, in the download link in the first post, the latest version I see is 2.14.
[Nexus 6  Original Android Development] KonoeKyon:
If you are on M you want 3.0b1, click the main download link on first post, and it should be at the bottom.
[Nexus 6  Original Android Development] cr4ck3r4lif3:
Anyone running 3.0b1 on aosp? When I type lk in the terminal, it says lk not found.
[Nexus 6  Original Android Development] instinctkiller:
Type:

#su

then:

#lkconfig

It will do the job :)
[Nexus 6  Original Android Development] DatDude123:
Are you on PureNexus by chance?

D
[Nexus 6  Original Android Development] cr4ck3r4lif3:
It no longer works. I'm stumped!

---------- Post added at 03:30 PM ---------- Previous post was at 03:30 PM ----------

Yes
[Nexus 6  Original Android Development] DatDude123:
Me too. Same issue. Weird.

D
[Nexus 6  Original Android Development] pkgnex:
You could try this:

su (enter)

setenforce = 0 (enter)

lkconfig (enter)

This is based on my theory that lk v3.0b1 is selinux permissive and your rom is selinux enforcing... and that setting everything to permissive might allow lkconfig to work for you while it isn't currently doing so (since lkconfig is in the /data partition, I believe). If this doesn't work, it's only a minute out of your life, if it does work, please report back so that others can benefit.

Thx.
[Nexus 6  Original Android Development] KonoeKyon:
Go into preferences of terminal and unchecked verify PATH entries then it will work using lkconfig, lk doesn't work on 3.0b1
[Nexus 6  Original Android Development] cr4ck3r4lif3:
Bingo! That did the trick. I remember doing this awhile ago but completely forgot.

Thank you!
[Nexus 6  Original Android Development] DatDude123:
Tried this first. Thanks for the info but it didnt seem to work.

This worked for me as well. Thank you too.

D
[Nexus 6  Original Android Development] pkgnex:
Yep. My theory was wrong.

Glad KonoeKyon pointed out the solution for you guys and you're up and running again!
[Nexus 6  Original Android Development] rui.ddevil:
[MENTION=3357040]Imoseyon[/MENTION]

Could you please add these features:

1 - FIOPS I/O scheduler

3 - selinux "Enforcing"

4 - Working F2FS

Also a question... if you use "Kernel Adiutor" in GPU settings the "Adreno Idler" is available but the, toggle on, does not stick when you change tab?

Thanks
[Nexus 6  Original Android Development] solo16:
Hi Imo,

I'm a bit confusing here, I already flashed and using LightRom Marshmallow right now, I wanna to flash your kernel but do I need to flash SuperSu after flashing the kernel?

Thanks!
[Nexus 6  Original Android Development] scryan:
SuperSu just gives you the ability to grant administrative rights to programs... If you don't want root, you shouldn't need to flash it... Root access and a custom kernal are two different things. How ever you will need root access to be able to make changes to kernel parameters as a stock user.

If you already had supersu jnstalled, and were asking if you need to reflash it, a new kernel shouldn't require this, only if you wrote over the system partition... Most of the kernel is in boot partition, with a couple files like init.d setting and what not written into system.
[Nexus 6  Original Android Development] :
Just delete all files in your system/etc/init.d folder using root explorer (or any root file manager) and reboot recovery and flash LK. You'll be good to go then. You don't want left behind scripts interfering with your setup after you install LK. That's what I've always done. :)
[Nexus 6  Original Android Development] ezy1022:
I cant get lkconfig to come up in the terminal no matter what settings I change, I am running the latest light rom m version.
[Nexus 6  Original Android Development] solo16:
Thanks! understood now, much appreciated!

---------- Post added at 02:52 PM ---------- Previous post was at 02:49 PM ----------

I am running light rom as well and I'm able to run lkconfig all you need to do is to uncheck a setting in Terminal Emulator - Verify PATH entries, close it and run it again you are good to go.
[Nexus 6  Original Android Development] Imoseyon:
hey guys, been out of town and just came back. Will work on releasing v3.0 soon - did chainfire fix supersu? I probably won't come out of beta until selinux can be fully enabled with root.
[Nexus 6  Original Android Development] KonoeKyon:
I think 2.52 of SuperSU has some updates to better work with selinux, more so for root app comparability. I think it still needs a patched sepolicy to work right though.
[Nexus 6  Original Android Development] xtzz:
What I did was:

- wipe cache/dalvik cache (It's ART, but the recovery option says so :p)

- install CM nightly

- install LK

- install Xposed

- reboot.

Ended up in a boot loop, the dots were flying around for eternity.
[Nexus 6  Original Android Development] KonoeKyon:
I think the latest cm has issues with xposed, not the kernel.
[Nexus 6  Original Android Development] pkgnex:
Imoseyon,

I think selinux can be fully enabled with root using chainfires latest supersu (2.52).

You would just need to make the same patches in LK that chainfire did in his LATEST stock boot.img files in his 6.0 WIP thread (they've changed at least once but were not renamed), Flar2 made in the latest Elemetal X, etc.

I've been running your beta with SU2.52, and I just type "setenforce = 1" in a terminal after every reboot. I'm still on LK, still rooted, and selinux is enforcing ;)
[Nexus 6  Original Android Development] fhem:
Still need modded K http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
[Nexus 6  Original Android Development] rrrrrrredbelly:
Which xposed version did you flash? Sorry if this is a stupid question but make sure you flashed v75
[Nexus 6  Original Android Development] vt0r:
SELinux enforcing is working fine for me on stock Marshmallow with leanKernel 3.0b1 and SuperSU 2.52. No corrupt system message, either.
[Nexus 6  Original Android Development] ihancioglu:
Hi [MENTION=3357040]Imoseyon[/MENTION], why I could not connect adb via wifi with leanKernel?

Thanks in advance,
[Nexus 6  Original Android Development] knitler:
3.01 has been great for me. I can't wait to see what 3.02 brings.

Just wish Imoseyon did a nexus 9 kernel also.
[Nexus 6  Original Android Development] ihancioglu:
Hi [MENTION=3357040]Imoseyon[/MENTION],

What do you think about the following commit?

https://github.com/MotorolaMobilityLLC/kernel-msm/commit/1643ef2ebc18bbe7d01a027b4e9e2afa0319a68d
[Nexus 6  Original Android Development] knitler:
Isn't that already in Android since 5.0.2 or 5.1?
[Nexus 6  Original Android Development] Imoseyon:
ok 3.0 release is almost ready with selinux enforcing. Should be up tomorrow morning. Thanks for being patient guys - i've been swamped with work since returning from my mini-vacation.
[Nexus 6  Original Android Development] golfgtiedition30:
Surely that can be avoided with changing your rgb settings....
[Nexus 6  Original Android Development] Imoseyon:
I will have this commit in a future test build (probably 3.0.1). I don't really understand the dt code for this so it will more or less be a blind mod.
[Nexus 6  Original Android Development] Imoseyon:
v3.0 is up: https://github.com/imoseyon/leanKernel-shamu/wiki/Marshmallow-ChangeLog

This is for Marshmallow AOSP only. SELinux is in enforcing.

(there is a testbuild v3.0.1 also up in testbuild folder with the motorola display dt changes mentioned above as well).
[Nexus 6  Original Android Development] pkgnex:
This made my day!

Both versions working great for me. When I turn screen brightness all the way down on 3.0.1 it might look slightly less reddish and more grayish. It's hard to be sure it's not just placebo, though, because the difference isn't much. It's definitely not worse, though.

Now I'll just be holding out for an ocuc version :)

Thanks, Imoseyon!
[Nexus 6  Original Android Development] knitler:
im confused how 3.0 comes after 3.0.1
[Nexus 6  Original Android Development] pkgnex:
Uhm, it doesn't. 3.0.1 (current test build) came after 3.0 (current first release build for 6.0). Both dropped today.

Before that, you may have been running 3.0b1. The "b" is for "beta", meaning still in testing and not an official full release.

Seems pretty straight forward to me.
[Nexus 6  Original Android Development] solo16:
I also notice that right after i finished installing lk and booted up the color at low brightness is much better now:good::good:

Thanks Imoseyon!
[Nexus 6  Original Android Development] jkc120:
Widgetsoid brightness doesn't work with the 3.0.1 test build. It changes the brightness, then goes back to full brightness. Manual brightness change works fine.

*edit* I take it back, it's acting REALLY strange. It will go back to the brightness I set manually in Tapatalk, then I go back to nova desktop and it goes back to full brightness. Weird.

---------- Post added at 12:54 PM ---------- Previous post was at 12:52 PM ----------

Never mind, seems like display tester app being open was the cause.
[Nexus 6  Original Android Development] jkc120:
Seems to be some lag for me on 3.0.1 (scrolling, typing, switching apps) compared to Elite kernel I was running while waiting for the 3.0 release. Anyone else? With no lk script yet maybe I need to tweak some settings in trickstermod?
[Nexus 6  Original Android Development] motorator:
Does the new 3.0 M build require Chainfire's modified boot.img?
[Nexus 6  Original Android Development] SubwayJrd:
Imoseyon's kernel is also a boot.img, so no it does not.

I'm sure he has cherry picked the mods that chainfire made to his boot.img so that things will work.
[Nexus 6  Original Android Development] solo16:
guys just wondering what's your idle battery life with the M and lk? when i'm still on LP with LightRom and LK I'm able to achieve 0.3-0.4/hr using wifi at idle, but with M using LightRom and LK it's about the same, 0.3/hr at idle.
[Nexus 6  Original Android Development] fhk:
Wow, first kernel that got me through a bat cycle without one single random reboot. Congrats lmoseyon!
[Nexus 6  Original Android Development] Stephen:
[MENTION=3357040]Imoseyon[/MENTION] Hey, I was wondering why you have decided to go down the route of enforcing SELinux? I have found that a lot of apps dont play well with root in M. Even using latest 2.52 SuperSU zip file.

Also what version do Android M users us who are using factory base image?
[Nexus 6  Original Android Development] Imoseyon:
I'm not entire sure... There was a discussion a while back about another custom kernel which seemed smoother due to it using a different cpu scheduler. I opted to stick to stock cpu scheduler. Maybe that's it. Try playing with various governor settings in cpu tweaking apps.

Yes my kernel includes ramdisk modifications necessary to accommodate chainfire's supersu.

For higher security. I don't generally recommend putting selinux to permissive mode, but you should be able to use an selinux app to do this if you want.
[Nexus 6  Original Android Development] Stephen:
No worries, I use an .sh script to enable it.
[Nexus 6  Original Android Development] Hen Ry:
v3.0 and v3.0.1

Sweep2wake bit "sluggish" in both, depends

CPUFreq <300MHz possible?

GPU remains constant at 240 Mhz?

otherwise very good :good:
[Nexus 6  Original Android Development] aktnmh:
Cant run lkconfig, but i found lkconfig in sbin. So i type ./lkconfig and i got the configurator menu came up. If i do the tweaks from here, the results will be the same right? And sorry, i m a noob. Running on leankernel shamu 3.0 and sock rom.
[Nexus 6  Original Android Development] MaLiXs:
Open terminal emulator

Go to settings

Untick check path option

Close the terminal

Go back to it

Type su and enter

Type lkconfig

Profit!

Envoyé de mon Nexus 6 en utilisant Tapatalk
[Nexus 6  Original Android Development] Imoseyon:
BTW, what are some of the apps that behave badly when selinux is in enforcing mode? I may be able to address some of them by patching policy in ramdisk.
[Nexus 6  Original Android Development] neobuddy89:
One example is Titanium Backup not able to restore app if SELinux is enforcing.
[Nexus 6  Original Android Development] Imoseyon:
ah i believe TB fixed that in the latest release. I just tested that and it worked fine. I think the new update just came out like yesterday.
[Nexus 6  Original Android Development] galaxys:
This is true, TB update came out a few days ago.
[Nexus 6  Original Android Development] bdivs11:
Can you patch viper4android or is it already patched?
[Nexus 6  Original Android Development] Imoseyon:
Will be patched for v3.1.
[Nexus 6  Original Android Development] berto1014:
I read the last few pages but is lkconfig not available in 3.0m and 3.0.1?
[Nexus 6  Original Android Development] rauschkugl:
Use search. It has been answered often enough now. Also in the last couple of pages.
[Nexus 6  Original Android Development] berto1014:
Yeah I tried that before I posted, forgot to reboot the terminal to put it into effect then reverted the setting when it did nothing. My mistake haha
[Nexus 6  Original Android Development] daheazle:
That's also the only reason I use permissive.

Is kexec hard boot patch going to be put back in?
[Nexus 6  Original Android Development] drivel2787:
Nice... So what's the story? LOL
[Nexus 6  Original Android Development] Imoseyon:
That is correct, and that's why it's enabled by default. Maybe I should put up a big warning sign, but from what I can gather no one's experienced actual data corruption or loss due to disabling CRC (and this feature has been available on many phones, kernels, including leankernels on other devices). My recommendation? Leave it enabled.

I'm on Sprint. :)
[Nexus 6  Original Android Development] frenchy714:
Oh very cool!

I pooped my pants once, it's a long story....
[Nexus 6  Original Android Development] remag6383:
Awesome, just installed frankened and lkb6, signal ok. now to set up everything else and see how it goes. Thx again.

edit: did not need sprint.zip

---------- Post added at 03:55 PM ---------- Previous post was at 03:50 PM ----------

not to be rude, I was talking about a rom that was posted if you did not know. But if you did know, my bad and yes I did not need sprint.zip for it.
[Nexus 6  Original Android Development] frenchy714:
Np lol, we were both talking about the same thing ;).

I pooped my pants once, it's a long story....
[Nexus 6  Original Android Development] remag6383:
:good::)
[Nexus 6  Original Android Development] dadsterflip:
Cool to flash beta7 ? Glad to see you imoseyon and still rocking out kernels. I was on the Samsung side for a long time and finally a nexus on vzw lol. Excited to flash your kernel again!
[Nexus 6  Original Android Development] Imoseyon:
beta7 is up!

1) RGB control (thx to flar2 for porting code to nexus6) - configurable via lkconfig

2) Charging LED support (thx to garyd for the idea) - configurable via lkconfig

3) other minor optimizations and fixes.

As for RGB control, I prefer warmer displays so I personally like how the default colors look. If you think stock colors are too warm, I think "240 240 255" would be a good setting for you.
[Nexus 6  Original Android Development] Xileforce:
I downloaded it before this post was even up! Flashing now!
[Nexus 6  Original Android Development] poczynek:
Brilliant! Thanks. Do you think via the great work garyd is doing that LED notifications will be baked in at some point?
[Nexus 6  Original Android Development] Imoseyon:
So the kernel already provides LED support via sysfs. I'm sure someone out there already published all the sysfs nodes that are available to manipulate the various LEDs. If not, i can post the list.

Charging LED seems to have built in support for the battery-charging trigger, so I added that option to lkconfig as a convenience. There may be a couple of other LEDs with built in trigger support, but overall I believe the implementation should be done in userspace and not kernel space. I'm happy to link to [MENTION=487933]garyd[/MENTION]'s thread from my OP of course.
[Nexus 6  Original Android Development] Xileforce:
Running 231,247,251 ATM. Seems nice and cool...but I kinda got used to the warm colors now...
[Nexus 6  Original Android Development] dirtbikerr450:
how do i get the lkconfig app?
[Nexus 6  Original Android Development] Mistertac:
Open up Terminal Emulator on your phone.. Type "SU" enter, then type "lkconfig" and hit enter.
[Nexus 6  Original Android Development] poczynek:
Thank you. There is a 'sort of' way to do it via Light Flow but it doesn't work that well. If it was actually baked in then that would be ideal! Still can't understand why Google chose not to do it when there is bloody LED there in the first place!!
[Nexus 6  Original Android Development] dadsterflip:
Yea I tried this. I tried IMO suggested and seems pretty decent. 240 240 255.
[Nexus 6  Original Android Development] shane1981:
I just flashed and everything seems to function in terminal emulator except enableing the led doesnt work. What am i doing wrong?
[Nexus 6  Original Android Development] dadsterflip:
No way to adjust the purple tint ? Just curious.

When you pull down the notification bar.
[Nexus 6  Original Android Development] garyd9:
Quick question: Is anything (that you know of) broken in your kernel? (My reason for asking was that my "quick" kernel compile resulted in not getting any vibrations from the booted system.)

As for the rest, I'm talking (mostly to myself) about it in a dev discussion thread here: http://xdaforums.com/nexus-6/devs-only/enabling-charging-notification-led-t2960135

Things _should_ be done in userspace (android-space), but there will need to be some kernel mods done to empower userspace. In particular, it would be a Bad Thing for the userspace to keep the device in a perpetual wakelock in order to blink the LED's. ;)
[Nexus 6  Original Android Development] zephiK:
Suggested values are nice. I'm finally content with the phone being cool colors instead of warm.
[Nexus 6  Original Android Development] Berlino:
[MENTION=3357040]Imoseyon[/MENTION]

Will there be an oc/uc-version for the M-Kernel?
[Nexus 6  Original Android Development] pkgnex:
I second this!

In fact, did anyone ever have a problem with the ocuc version? If not, then maybe just make all builds ocuc (even setting the min and max same as stock upon intial flashing so they have to be changed lower / higher in lkconfig) to save having to do all the different builds!
[Nexus 6  Original Android Development] ezy1022:
I have always had issue with ocuc, i get reboots and problems with booting. Started with the first version and have tried every after that, always same issues...

N6
[Nexus 6  Original Android Development] JRJ442:
It's because of your device and not the kernel. Same thing with mine. My phone can handle 2800ish, once I go to 2880 I get reboots all the time.
[Nexus 6  Original Android Development] pkgnex:
That's too bad. I've found 2880 works for me, but anything higher doesn't. I know it's device dependent, but I hadn't heard too many people having issues with 2880 and down until now.

I still think ocuc could be the standard build... it could just default to the stock max until a user changes it.

Just tryin' to save Imo some work (and still get ocuc versions coming!).
[Nexus 6  Original Android Development] ezy1022:
I agree with it defaulting to stock max and min, and being able to change it, I would love to be able to drop my min and leave my max.

N6
[Nexus 6  Original Android Development] Franzie3:
[MENTION=3357040]Imoseyon[/MENTION] on 3.0.1 test build with Snapchat any recorded videos do nothing play back. Was working fine earlier today
[Nexus 6  Original Android Development] urnamese3:
Hey @Imoseyon can you please disable the bcl driver in the 2.14 version for lollipop 5.1.1?

http://xdaforums.com/showpost.php?p=62686536&postcount=492
[Nexus 6  Original Android Development] KonoeKyon:
I think they later on re-enabled the driver. There's the possibility of instability with it disabled, it's meant to prevent sudden **** downs due to too much draw placed on the battery. I usually run with a init.d script to disable it, but I've been able to cause the phone to crash and shut down with it disabled, with stock settings. It's easier to make it happen at lower battery levels.

Although I don't think lollipop had that driver in the stock kernel, it just throttled bellow like 40% battery. In marshmallow it only throttled the cpu bellow 20% and when the bcl driver kicks in for a short while.
[Nexus 6  Original Android Development] urnamese3:
Yeah it happened to me once or twice too but that's it; I noticed it happened with moderate cpu usage.

Blu spark kernel has the bcl driver disabled by default and having the last 30% of battery with 4 cores running makes a big difference IMO.

When battery is around 25-30% with LK only two cores are running with the max frequency locked at 1.7 Ghz as you may know meaning some apps or games will run sluggishly.

For example one of the 3 games I've installed which is called fun run gets extremely laggy at times thus making me unable to play.
[Nexus 6  Original Android Development] KonoeKyon:
If it's stuck at 1.7 then it isn't there driver, the driver limits at 1958MHz and only kicks in temporarily. It is annoying but as I mentioned completely disabling it does cause some stability issues. Might not affect everyone though since we all use or phones differently. Maybe having an option to disable it would be a way to go, but completely removing it by default wouldn't be a good idea.

Edit - have you tried disabling it using an init.d script? I haven't tried it on leankernel yet, but it's what I did on other kernels when I wanted to disable it.
[Nexus 6  Original Android Development] urnamese3:
Ahh my bad, I thought they got locked at 1.7 GHz but they actually get locked at 1.958 GHz and it's obviously the bcl driver doing that. I used Blu spark for ~3 months and the phone crashed once or twice. I'd rather have it crashing once or twice than having 30 % of battery where the phone is almost useless but as you said peoples have different usage patterns and some peoples might not think at this the same way I do.

I guess I'll just add an init.d script
[Nexus 6  Original Android Development] KonoeKyon:
I will say, i didn't notice any instability with the modified version of the driver, that only disables the hot plugging portion, not the throttling.
[Nexus 6  Original Android Development] urnamese3:
Could you please explain me how to do so?