yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] KonoeKyon:
It's something that has to be done by the dev, if you just want to disable it completely, I was able to disable it via terminal emulator, so I think the scripts should work also.

For anyone else reading, the following can cause instability or sudden shut downs, so I do not recommend doing it. If you do then do so at your own risk and don't bother the op about crashes or issues when it's disabled.

The script command is

#!/system/bin/sh

echo disabled > /sys/devices/qcom,bcl.39/mode

If you want to try it in terminal emulator, type

su

echo disabled > /sys/devices/qcom,bcl.39/mode
[Nexus 6  Original Android Development] urnamese3:
Oh ye, I knew about this script since I got it a while ago from a post of yours in the despair kernel thread. I was curious about the modified driver and disabling online the hotplug component of the bill driver.

Still, thanks :)
[Nexus 6  Original Android Development] Imoseyon:
I will probably introduce ocuc build along with v3.1 or v3.2. I'd like to keep the ocuc build separate to minimize risk of instability for folks who don't care for OC.

I recommend using init.d. I will consider disabling hotplug within BCL driver for marshmallow if there's enough demand.
[Nexus 6  Original Android Development] Yank555:
[quote name="Imoseyon"]I recommend using init.d. I will consider disabling hotplug within BCL driver for marshmallow if there's enough demand.[/quote]

I have been running into those random shut off's lately (2-3 months), mostly when stressing my shamu, be it by taking photosphere on photoshpere or being impatient swiping nervously or stuff like that, and it shut off even on levels as high as 60% battery ... when other times it would be steady til 1% battery.

Tested both with and without bcl, and honestly found it be NO difference whatsoever.

As such on my end I decided to die with glory, if it has to shut off on me, at least at full steam and all cores on ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.4 kernel.
[Nexus 6  Original Android Development] KonoeKyon:
I have been running into those random shut off's lately (2-3 months), mostly when stressing my shamu, be it by taking photosphere on photoshpere or being impatient swiping nervously or stuff like that, and it shut off even on levels as high as 60% battery ... when other times it would be steady til 1% battery.

Tested both with and without bcl, and honestly found it be NO difference whatsoever.

As such on my end I decided to die with glory, if it has to shut off on me, at least at full steam and all cores on ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.4 kernel.[/QUOTE]

My experience was different. With our disabled I can run with no issues unless I really stress the hardware. Easiest ways to invoke it would be to do something such as generate a bunch of thumbnails while scrolling. With it enabled I've never had an issue with any shut downs, be it with the stock version, or the modified version with hotplugging disabled.

IMO, for the sake of stability, it would be best to leave it enabled, and maybe add an option to lkconfig to disable it. Or of course just use an init.d script.
[Nexus 6  Original Android Development] mflow:
My SOT's been insane for today. Plugged out back at 11AM ish, heavy usage with lots of camera, chats and spotify until 9PM, and until now 1.30AM still got 30% left. Bluetooth was on the whole time for my Fitness Tracker to work.

SOT is 4hr 40mins (and counting). Pretty sure it can hit 5hrs easily.

Thanks imsoyeon for the amazing work!
[Nexus 6  Original Android Development] Imoseyon:
Did you remove BCL support completely from kernel or disable it in userspace?

i'm thinking about making it configurable. The issue is that this is sort of a pain to test. We'll see.

You on M?
[Nexus 6  Original Android Development] Yank555:
I haven't done it "propely", just a hack to test this, and since I really can't see ANY difference in behaviour, I left it for the time being.

I disabled it by default, that's fine as you can enable it again via sysfs, but I commented out :

qcom,bcl-hotplug-list = <&CPU2 &CPU3>;

As it kept messing with cores...

In fact, I've rebased the SlimLP kernel to pure LP-mr1 again heading to push a "stable" labeled SlimLP (so no BCL at all) and it runs just as good if not even better (talking about SlimLP, not M, haven't played with M much yet).

But I had been runinng SlimLP with m-preview based kernel for weeks before that.

JP.
[Nexus 6  Original Android Development] Imoseyon:
Yeah I saw that, so with that commented out cpu2 & cpu3 no longer offlines at 40% battery (which I think was the behavior in LP)? Then that's easy, I'll just make that configurable via sysfs, unless a sysfs node exists already (i'll check that too).
[Nexus 6  Original Android Development] Yank555:
Yes, that makes cores stay online till the bitter end.

Well if you code it, lazy me will shamlessly use your proper implementation, then :angel:

JP.
[Nexus 6  Original Android Development] Imoseyon:
Implementation finished - testing now. Should go out in v3.1 this weekend.
[Nexus 6  Original Android Development] urnamese3:
[quote name="imoseyon" post=63466352]

Implementation finished - testing now. Should go out in v3.1 this weekend.[/QUOTE]

What about the LP version? :(
[Nexus 6  Original Android Development] mflow:
[MENTION=3357040]Imoseyon[/MENTION] yep, I'm on M. Final SOT was 5hrs 30mins before it gave up to Power Saving mode (15%). That was the best battery life i ever had.

*this XDA app doesn't allow me to quote, duh*
[Nexus 6  Original Android Development] SunamY:
I've got a problem with latest lk 3.0M. All 4 cores are always online. Is there a way to fix this?

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6  Original Android Development] hellsgod:
Nothing to fix, thats normal.

hells
[Nexus 6  Original Android Development] epagib:
Dumb question: is the current 3.0 release for stock based M rom?

Or is it for aosp based M?

Thanks.
[Nexus 6  Original Android Development] :
Stock and/or aosp just not cm from what I understand. I've been using on Cat rom and works wonderfully. :)
[Nexus 6  Original Android Development] Imoseyon:
Possibly if I have some time. Just curious.. any reason why you haven't upgraded to M? I guess you must be on CM (or another CM based ROM).

hehe yeah you must be new to nexus 6 - that is normal for this device.
[Nexus 6  Original Android Development] urnamese3:
Yup, I'm on Temasek's ROM which is based on CM 12.1. I'm patiently waiting for CM 13 :angel:

If could add it to the LP version I'd really appreciated it :highfive:
[Nexus 6  Original Android Development] Imoseyon:
v3.1 is up: https://github.com/imoseyon/leanKernel-shamu/wiki/Marshmallow-ChangeLog

Marshmallow only!

This release includes:

1) some interesting cherry-picks from motorola shamu branch including red push at low brightness fix

2) some selinux policy fixes (viper4droid, gsm, and more)

3) a way to disable the cpu hotplugging feature of BCL via lkconfig/sysfs
[Nexus 6  Original Android Development] :
Thank you [MENTION=3357040]Imoseyon[/MENTION] !! Running great on Cat rom!!
[Nexus 6  Original Android Development] franciscofranco:
Don't forget "allow untrusted_app sysfs_mmi_touch:dir search" for double tap to wake.
[Nexus 6  Original Android Development] akilger14:
Has anyone tested ViPER4Android on 3.1? I can't get it to process. I've installed to system/priv-app. I set the correct permissions. Also added the modifications to build.prop and deleted/disabled MusicFX. App opened and installed the drivers correctly. Just doesn't process. The only thing I haven't done is set SELinux to permissive, but from what I understand we don't need to do that with the patched SELinux policy, correct?

Driver status reads:

Driver version: 2.3.4.0

NEON Enabled: Yes

Enabled: Yes

Status: Normal

Audio Format: Supported

Processing: No

Sampling Rate: 48000
[Nexus 6  Original Android Development] DatDude123:
[MENTION=6896047]akilger14[/MENTION] You're playing music while checking for processing right?

D
[Nexus 6  Original Android Development] akilger14:
Yup, right after I change the state of the device (ie. unplug headphones while music is playing, or if I plug them in) it quits processing completely until I totally reboot the device. Then it will work up until I change states again.

EDIT: I should mention I tried reinstalling drivers after changing SELinux to permissive, didn't solve the problem either. I also put up a post in the official V4A xda page as well after testing this with permissive. Not sure exactly whats the problem anymore, I originally suspected it was the kernel, but that doesn't seem to be the case anymore.

EDIT 2: I renamed the priv-app apk folder and the apk, reset permissions again and rebooted now its working. I just cannot unplug headphones with music still running otherwise the driver quits. If I pause music, close out both GPM and viper and then unplug headphones or plug them in, the driver will work after re-opening GPM. If I change songs, it seems to kill the driver also. It's very difficult to get consistent results from this. But its very obvious when its working.
[Nexus 6  Original Android Development] zgow:
What does this mean? Is this a terminal command for end users?
[Nexus 6  Original Android Development] franciscofranco:
No, it's for imoseyon.
[Nexus 6  Original Android Development] bradputt:
[MENTION=3357040]Imoseyon[/MENTION]

possible to add kexec support for V3.1?

thanks!
[Nexus 6  Original Android Development] Imoseyon:
Ah damn, i forgot to do that. I just added that to v3.1.1 - would be great if someone can test that for kexec.

http://renderserver.net/?dl=0bde31b35c691d8ee240827ae1d31342
[Nexus 6  Original Android Development] bradputt:
Working great! Thanks, you're a great guy!
[Nexus 6  Original Android Development] epagib:
Just want to report something:

With 3.1 release, when I clear dalvik and cash, all the settings from lkconfig reset.

I think with past releases, the settings were retained with reboots

Thx
[Nexus 6  Original Android Development] Mach3te:
Has leankernel been tested with the latest Pure Nexus rom release?
[Nexus 6  Original Android Development] daheazle:
I have been running them both since pn dropped. Nothing but pure lean awesomeness.
[Nexus 6  Original Android Development] bradld:
Min freq not sticking?

Just noticed today that despite using SetCpu and having active profiles my min frequency doesn't seem to be sticking with M. CPU seems to drop below the min frequency set point but not sure why. Has anyone else seen this or is there something I could be flat out missing?
[Nexus 6  Original Android Development] d u o XIV:
It's the CPU hotplug "mpdecision" that's doing that. Anyone else can feel free to correct me if I'm spreading false info, but I think what the hotplug does is ramp up the CPU to 1458MHz for a quick second upon touch (or basically when you're using it), then it drops back down to 300MHz when nothing is going on.

You have two choices: find an app that gives you more control over the kernel (like Kernel Adiutor from the Play Store - https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor&hl=en) and turn off mpdecision, or just leave it alone. I say you're better off with the latter. Both Imoseyon and Franco leave it intact, even with all their mods and tweaks to the kernel, so I'd trust their judgement.
[Nexus 6  Original Android Development] bradld:
Is this the same as the newly added BCL hotplug disable in lkconfing. Apologies for the continued question...:silly:
[Nexus 6  Original Android Development] d u o XIV:
Sorry...that, I don't know. This is the first time I'm hearing about BCL...
[Nexus 6  Original Android Development] vt0r:
No, it's not. The setting that forces the min freq to 1458 on touch events is called touch boost or input boost, depending on the kernel.
[Nexus 6  Original Android Development] ihancioglu:
Hi [MENTION=3357040]Imoseyon[/MENTION],

I was using leanK at Lollipop just installed at Marshm but a lot of feature is not included.

Do you implement these features at future releases or just thinks that not useful a lot?

Thanks.
[Nexus 6  Original Android Development] Freak07:
Hey guys.

Maybe someone is able to help me :) When I open terminal and trying to configure lkconfig I get an error.

Tmp-mksh: lk: not found

I'm using Cataclysm rom as primary along with multirom and lk 3.1.1.
[Nexus 6  Original Android Development] KonoeKyon:
Go into preferences in terminal emulator and uncheck verify PATH entries.
[Nexus 6  Original Android Development] provolinoo:
hi guys, is this kernel compatible with new systemless root by chainfire?
[Nexus 6  Original Android Development] KonoeKyon:
No it is not
[Nexus 6  Original Android Development] mascian:
Sorry, too me have this error and your solution don't resolved (Stock MRA58N [Lite] rom).

Thank you.

Problem fix: installed Busybox.

Thank you.
[Nexus 6  Original Android Development] d u o XIV:
Silly question: what's been added to lk v3.1.1? I haven't flashed it because it's in Test Builds and I don't see anything about it in the changelog. Is that the version with the lower minimum and higher maximum CPU frequencies?
[Nexus 6  Original Android Development] spoudumen:
Exit terminal and try again after unchecking
[Nexus 6  Original Android Development] Freak07:
Multirom support was somehow broken. 3.1.1 has proper kexec patch :)
[Nexus 6  Original Android Development] mp3geek:
Would be nice to include "USB FASTCHARGE", from Heaven Shall Burn kernel, benzocore and other kernels, so much quicker to charge especially via wireless.
[Nexus 6  Original Android Development] rauschkugl:
I think it's already there or not needed anymore with marshmallow. All it did was to use the data wires for charging when you're connected to a USB port. There can't be any difference in wireless charging.
[Nexus 6  Original Android Development] PJcastaldo:
Yeah, pretty sure any increase you noticed in anything other than usb charge speed would be purely a placebo .
[Nexus 6  Original Android Development] vt0r:
Since I really feel like the modifications to this kernel make a noticeable difference in performance (no matter how lightly it's been touched), I went ahead and repacked just the boot.img with the ramdisk modifications Chainfire recommends in his WIP thread + a few other changes detailed below.

This is not a flashable zip as usual, so you'll need to flash it via fastboot or in TWRP as an image rather than a zip.

To make absolutely certain /system is not being modified, I removed the lkconfig and post install scripts, as well as the init script that does most of the setup work for lk/lkconfig. I'm well aware this removes lkconfig entirely, but this was a quick and easy way for me to be able to use leanKernel again and still have systemless root.

Anyone hoping to use this boot.img should follow all the instructions in the SuperSU WIP thread, especially the part where you reflash the system partition with the factory image.

This boot.img is based on v3.1.1, so it should include full kexec support as well for MultiROM users. If I get some free time over the next few days, I'll look into possibly adding lk/lkconfig back in via some bind mount or overlayfs solution in a /su/su.d script, but I'm not making any guarantees here. This of course assumes [MENTION=3357040]Imoseyon[/MENTION] has no objections to me doing so and that he considers this help and not harm :)

Anyway, I'm attaching the boot.img to this post, and I'll gladly remove it at [MENTION=3357040]Imoseyon[/MENTION] 's request.
[Nexus 6  Original Android Development] vampire36:
[MENTION=3357040]Imoseyon[/MENTION] : First of all thanks for all your work...Would be great if you can bring this masterpiece to 5x as well :) I hope you will give us some 'Lean Love' as well :)
[Nexus 6  Original Android Development] seti007:
Just wanted to say thanks for the hard work. Also wanted to report that my N6 had the screen split issue with pretty much every rom and combo I tried including my current xTrasmooth. However, after installing lean kernel, I haven't had any issues with the split screen. In the past, it was happening randomly almost hour but I haven't had even a single issue for several days (knock on wood). I think I've found a great rom/kernel combo. Being lean is not only good for us, but also our phones, who'd have thunk that!!!

Thanks again
[Nexus 6  Original Android Development] ihancioglu:
Hi, is this latest leanKernel compatible with f2fs? I just formated data/cache with f2fs , but as soon as booted the device that partitions formated as ext4..
[Nexus 6  Original Android Development] ihancioglu:
Hi [MENTION=3357040]Imoseyon[/MENTION], would you please add following patch on next release?

https://github.com/atl4ntis/kernel_msm/commit/bebe80d82d7a5da743bd67f274993b6624998982

This will be allow volume/power keypress while screen off.

Thanks.
[Nexus 6  Original Android Development] angourakis:
I second that. Everytime I changed to F2FS and started the ROM, the partitions changed automatically to ext4. I am not sure if it really happens (because we have to format the partition to change the filesystem) or it´s not showing correctly when running "mount" from terminal (although using another kernel I don´t have such issue, it stays as f2fs).
[Nexus 6  Original Android Development] bradld:
Running latest version of Chroma and get battery displaying thousands of %. ROM info states it's because of Chainfire's/custom kernel sepolicy.

Question: @Imoseyon Will LK be able to get an update to solve this issue? Can't see myself not running this Kernel. :p
[Nexus 6  Original Android Development] Imoseyon:
No problem at all - thanks for doing this. Once Chainfire says that the new root method is stable, I will incorporate the ramdisk changes myself as well.

Sorry bro, I only develop kernels for devices I own and use...

I can add this to v3.2. Will need a couple of testers for this though. Email me at imoseyon@gmail.com if you're interested.

Interesting patch. Any adverse effect at all with this patch?

hmmm... can you pull logcat of dmesg while on my kernel? I may be able to fix this by patching the policy live.
[Nexus 6  Original Android Development] KonoeKyon:
Some other kernels have been reverting this patch since they started having 'reboot' issues that look like they are user initiated.
[Nexus 6  Original Android Development] vt0r:
Yeah no problem. I did it for my own use anyway, so I figured I might as well share. And I figured you were just waiting for the Chainfire seal of approval to integrate it officially.
[Nexus 6  Original Android Development] daheazle:
I got the same on pure nexus, beanstown said it was because his latest build is based on the latest r23 source and kernels will need to be built from it as well. Others said it was in chainfires boot.img and if you use a permissive kernel it wouldn't happen. Not sure if that is any help, but if nobody can get it or you still need it tomorrow night I will get that log.
[Nexus 6  Original Android Development] SunamY:
[MENTION=3357040]Imoseyon[/MENTION] to fix the battery error on latest PureNexus, chroma and so on, you have to use the latest aosp kernel source for 6.0r26
[Nexus 6  Original Android Development] knitler:
[MENTION=3357040]Imoseyon[/MENTION] I know you said you plan to get a 6P and start to dev for that. Do you have any kind of time frame? Just got my 6P and feeling naked. :P
[Nexus 6  Original Android Development] Imoseyon:
http://renderserver.net/?dir=devs/imoseyon/angler/

I will be opening an xda thread soon. :)
[Nexus 6  Original Android Development] knitler:
Wow, are any of these ready for testing? I'd be happy to give them a run.
[Nexus 6  Original Android Development] SunamY:
Ok... After trying and trying... Latest lean kernel 3.1.1 didn't work on all android 6.0.2r26 based roms. I've flashed the permission.zip with this kernel... Nothing work....

Now... Waiting for update :)

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6  Original Android Development] natezire71:
I see you've pushed out two updates to the angler kernel. What's included? You didn't create a thread on the Nexus 6P forums.
[Nexus 6  Original Android Development] fhem:
We are waiting LOL
[Nexus 6  Original Android Development] knitler:
I am running .2 now with no issues noticed. lkconfig is not in it yet, but stable and decent battery life. from about 11:30PM last night till now I have only used 24%
[Nexus 6  Original Android Development] daheazle:
[MENTION=3357040]Imoseyon[/MENTION] here is that dmesg log, its a day later but life happens xD. This is on pure nexus rom and lk 3.1.1, battery % reads 3700% or so. Hopefully it doesn't have too much garbage in it, if it does and you have a suggestion to remove it I will get another cleaner log.

dmesg.log
[Nexus 6  Original Android Development] SunamY:
[MENTION=3357040]Imoseyon[/MENTION] can't download the latest test build!

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6  Original Android Development] Fuse8499:
Lol yeah my battery is crazy on Pure Nexus too. Don't really notice any other problems though. Running nice and smooth!
[Nexus 6  Original Android Development] adm1jtg:
Same battery issue on mine as well, tried all kinds of things cant seem to work around it. REALLY want to use this as DD and will once battery issue is resolved. Keep up the great work.
[Nexus 6  Original Android Development] Imoseyon:
v3.2 is up: https://github.com/imoseyon/leanKernel-shamu/wiki/Marshmallow-ChangeLog

Sorry guys i haven't had a chance to look at PureNexus yet. Will take a look soon...
[Nexus 6  Original Android Development] adm1jtg:
Checked 3.2 this morning battery issue still present but otherwise that kernel flies was very impressed.
[Nexus 6  Original Android Development] Imoseyon:
Thread for angler opened here: http://xdaforums.com/nexus-6p/orig-development/kernel-leankernel-builds-t3248389

Been out of town for a few days so haven't had too much time on it yet.
[Nexus 6  Original Android Development] daheazle:
It isn't just pure nexus, it is anything build from r26 source. Beans says the problem is with the ramdisk and it needs to be built from the r26 source as well. Chainfires boot.img for enforcing uses the outdated ramdisk so when enforcing kernels are used that use it, it causes the battery bug.

For what it's worth, it seems like the battery % displayed with the bug is the actual battery voltage instead of the remaining charge level. So in this line of dmesg.log

[ 340.889161] healthd: battery l=44 v=3703 t=33.5 h=2 st=3 c=-720 chg=

My battery shows 3703% instead of 44%
[Nexus 6  Original Android Development] vt0r:
And the systemless root boot.img for 3.2:

https://www.androidfilehost.com/?fid=24269982086995597

I made just one change from [MENTION=3357040]Imoseyon[/MENTION] 's ramdisk outside of the usual SuperSU changes, and that was to change both of the "f2fs" entries to "auto"

Though the mountpoints do seem to work when they're formatted as ext4, even when the fstab entries are explicitly labeled as f2fs (not sure why...), it's recommended to use "auto" so mount can decide based on the fs header. At the very least, this works on ext4, so please report any bootloops to me if using f2fs for data and/or cache partitions, and I'll revert it.
[Nexus 6  Original Android Development] Imoseyon:
Can someone link me to pure nexus latest build?

Is systemless root stable now? Maybe i'll switch my ramdisk to that.
[Nexus 6  Original Android Development] demlv:
Latest pure nexus build for shamu:

https://www.androidfilehost.com/?fid=24269982086995479
[Nexus 6  Original Android Development] jejecule:
Just fingers crossed a cm version will come. This kernel is just the best for our device.

Cheers
[Nexus 6  Original Android Development] KonoeKyon:
I think it's still on the initial release/proof of concept.
[Nexus 6  Original Android Development] fhem:
FWIW -- It appears to me that most, if not all, the ROM devs are using SuperSU 2.52 for rooting.