yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] vt0r:
Seems stable enough for me, but Chainfire still has it listed as a WIP, so maybe wait until he comes back around and see whether he's ready to promote it? Not sure.

I don't mind making these in the meantime, though if it helps anyone. Only takes a few minutes to unpack, patch and repack.
[Nexus 6  Original Android Development] Maikeu Locatelli:
Using Chroma rom and I have the same issue, 3674% instead of around 44%

As you already know, this is the tension, 3.670V, I'm sure won't be difficult to you find the error.

Enviado de meu Nexus 6 usando Tapatalk
[Nexus 6  Original Android Development] shadowdrag96:
Hey sorry for the noob question haven't been in the game since getting the phone. So from what I read following this http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344/post63168310#post63168310 should be my best bet to root or is the other way by flashing a kernel then SU better. been rooting since droid 1 days but just haven't been up to date since getting the nexus 6.

Edit:bootloader is unlocked already
[Nexus 6  Original Android Development] smclaughlin3:
Is there better battery life with the bcl hot plug or without the bcl hot plug option? Thanks
[Nexus 6  Original Android Development] daheazle:
If you are on stock MM, which I would assume you are. You will need to first flash twrp recovery with fastboot. Then flash the latest lean kernel build followed by SuperSU v2.52 or higher in recovery

TWRP: xdaforums.com/nexus-6/orig-development/recovery-twrp-2-8-2-0-touch-recovery-t2946534

SuperSU: xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
[Nexus 6  Original Android Development] shadowdrag96:
Yeah stock MM. Awesome thanks. I'll try it now. time to find a good rom.
[Nexus 6  Original Android Development] shadowdrag96:
sorry one more question dont mean to jack the thread but whats the reason to do systemless root vs traditional. been reading saw some mention of being able to OTA update easier but if you're using a rom wouldnt that kinda be useless. Also android pay works on systemless root. which I dont use atm
[Nexus 6  Original Android Development] daheazle:
I believe the goal is just that, ota's and reduced impact on system components. At this point in time I would suggest not messing with it unless you plan to stay stock and are willing to sort through problems it may have. If you are on a custom rom there is no benefit from it far as I can tell.
[Nexus 6  Original Android Development] KonoeKyon:
The OTA thing is only if you reflash stock kernel and don't do any modifications at all to system, I think just mounting system rw is enough to prevent it from successfully taking the OTA. So the only thing that makes it easier is you only have to flash stock kernel instead of stock kernel + system, provided you haven't messed with system at all.

The other reason people are interested in it for is because it has the unintentional side effect of Android pay working with root, which chainfire said will likely get patched and he isn't interested in trying to make it work.
[Nexus 6  Original Android Development] :
I guess it's not compatible with unofficial cm13 yet then? Eagerly waiting for the nightlies and lean kernel to start rolling at full throttle!!

Nexus 6 64gb - CyanogenMod 12.1 (Android 5.1.1) [MENTION=3705640]520[/MENTION] dpi

LG G watch R
[Nexus 6  Original Android Development] adm1jtg:
Any luck finding and resolving the issue with battery stats on pure nexus rom? I am more then willing to help in any way I can.
[Nexus 6  Original Android Development] :
Love it
[Nexus 6  Original Android Development] guitarshredder87:
Jumping the gun (hope you don't mind imoseyon) but a fix should be available soon. Working on chroma and PN but still some testing left.
[Nexus 6  Original Android Development] Imoseyon:
Yup thanks to [MENTION=4234873]guitarshredder87[/MENTION]'s help in testing, v3.2.7 should fix battery stats for chroma and purenexus:

http://renderserver.net/?dir=devs/imoseyon/shamu/

No other change from v3.2.
[Nexus 6  Original Android Development] :
Thank you alot imo!!!!! Back on good ole LK. :)
[Nexus 6  Original Android Development] swapnilsathe:
worked perfectly !

Just the thing which was needed ! Thank you sir !

good to back on lean kernel.
[Nexus 6  Original Android Development] fhem:
I just looked at your commit ---- anyway to make that generic for the rest of us poor souls that want to build at 6.0.0_r26??? :D:good::good:

I don't suppose a wild card would work for the build.flavor? on your end LOL
[Nexus 6  Original Android Development] Imoseyon:
I thought about going the other way, ie. make the aosp healthd default and then for stock ROM use the stock healthd. But I didn't want to create any additional risk for stock. Not sure.. perhaps there's a better way to do this anyway. Maybe I throw in my towel and go anykernel. :)

For now, send me the getprop output from your favorite ROMs with the battery stats problem.
[Nexus 6  Original Android Development] fhem:
only one for me -----> ro.build.flavor=noobbuilds_n6-userdebug

Thank you kind sir --- no hurry I'm back and forth between my n6 and n6p.
[Nexus 6  Original Android Development] cr4ck3r4lif3:
I'm on the latest version of Benzo. I have the odd battery reading but also notice the notification light stays lit as well.

I'll pm my getprop. Thanks IMO!
[Nexus 6  Original Android Development] guitarshredder87:
The notification light is the battery light letting you know it's full since its reporting over 100%. You can disable battery notification however you won't be able to determine your battery's level. Pm imoseyon your getprop from your rom and he should be able to fix it for you.
[Nexus 6  Original Android Development] Imoseyon:
I put up v3.2.8 in the testbuilds folder. Should handle benzo and noobbuilds.
[Nexus 6  Original Android Development] cr4ck3r4lif3:
Worked like a charm. Thanks!
[Nexus 6  Original Android Development] fhem:
Same here worked great on my noobbuilds-- thank you very much.
[Nexus 6  Original Android Development] Raymondlikesroot:
Is there a guide for lkconfig? I'm not very familiar with terminal emulator.
[Nexus 6  Original Android Development] guitarshredder87:
You type su hit enter and type lk and hit enter. You will be presented with a list of settings menus. Select the setting you would like to change by typing the corresponding number and pressing enter. You will be presented with the available options for this setting. Select your setting by again pressing the corresponding number and pressing enter. Once finished editing settings, press enter to exit the lean kernel menu. Type reboot and hit enter. (rebooting isn't necessary however it allows you to ensure the settings have stuck at boot. If they haven't there is potentially an issue)
[Nexus 6  Original Android Development] Raymondlikesroot:
Thanks! while choosing rub/picture control, I tried to follow accurich according to this post http://xdaforums.com/showpost.php?p=59009298&postcount=4268. However, the saturation values range from 224-383 for lkconfig but the post asks for 55 sat. What should i do?
[Nexus 6  Original Android Development] tornido067:
can we make it blink for notifications when screen is off instead of it keep lit all the time ?and btw when i have more than one notifications it is showing me weird colors :( why ?it is like 3 or 4 colors together :( am on latest AOSIP .
[Nexus 6  Original Android Development] nathanchance:
The LED hardware does not support blinking. I have heard Light Flow can do it but it is inconsistent and has a wakelock.

It shows you weird colors because some apps use a custom LED color but the Nexus 6 only supports a few solid colors. When you try to do a custom color (either with your ROM or an app tries to do it), it blurs because the LED hardware tried to make that color but it can't handle the request. It is weird that Motorola even added it if they weren't going to properly support it.
[Nexus 6  Original Android Development] Freak07:
Hey [MENTION=3357040]Imoseyon[/MENTION]

On dirty unicorns the battery reading bug is also present. Would be great if you could look into this as well

ro.build.flavor=du_shamu-userdebug

Thank you very much for the kernel!

Kind regards
[Nexus 6  Original Android Development] yungman:
[MENTION=3357040]Imoseyon[/MENTION]

Battery stats bug also present for AOSiP:

ro.build.flavor=aosip_shamu-userdebug

It would be awesome if you could add this in at your convenience. Thanks
[Nexus 6  Original Android Development] Nikki1993:
Seems like 3.2.7 didn't fix the battery stats for me. Running latest on purenexus and still have 4,374% number :D
[Nexus 6  Original Android Development] MaLiXs:
Personally this kind of bug made me revert to stock! Now I'm enjoying perfectly stable mm with gravity box module and this kernel
[Nexus 6  Original Android Development] nodnarb91:
That's weird, for me before the .7 and .8 update I got the over 9,000 battery issue but now everything is fine. Running smooth, battery and performance is great.
[Nexus 6  Original Android Development] swapnilsathe:
With the latest update this issue has been cleared for me
[Nexus 6  Original Android Development] Nikki1993:
tried 3.2.8 same issue on latest PureNexus.
[Nexus 6  Original Android Development] daheazle:
The bug on pure nexus was fixed with 3.2.7. If its still there for you I suggest you dirty flash the latest version of the ROM and LK 3.2.7 and nothing more. Boot up and check it out.
[Nexus 6  Original Android Development] Nikki1993:
Did that, still there.
[Nexus 6  Original Android Development] swapnilsathe:
Reflash the ROM that will solve the issue
[Nexus 6  Original Android Development] daheazle:
Looks like its time for you to do a clean flash then, I assure you the battery bug has been fixed. I am using LK on pure nexus currently and have no issues
[Nexus 6  Original Android Development] Imoseyon:
ok v3.2.9 in the testbuilds folder should take care of dirty unicorn and aosip.
[Nexus 6  Original Android Development] Shaglok:
Why are you people using aosp roms in a nexus? I don't understand the beneficts of that. The main advantage of a nexus is having optimized stock builds (and roms) given by google for these specific phones.

Aosp is great for no Nexus or older phones. I'd kindly thank a good explanation of using these. Is like buying a Ferrari diesel ;)

Enviado desde mi Nexus 6 mediante Tapatalk
[Nexus 6  Original Android Development] Freak07:
Working great on du. Thank you sir.
[Nexus 6  Original Android Development] Nikki1993:
It's a clean flash already... I had this bug when I clean flashed the PureNexus.
[Nexus 6  Original Android Development] yungman:
Speedy work as always! I can confirm that aosip no longer suffers the battery bug with 3.2.9. Many thanks
[Nexus 6  Original Android Development] Nikki1993:
Here is the pic of the battery bug. Doesn't matter, 3.2.7, 3.2.8, 3.2.9 all have that. Again, I repeat, it's a clean flash. Although I am compiling purenexus from source myself, but I am not adding anything. It's a pure source compilation as if I downloaded from the purenexus XDA thread.

No need for generic troubleshooting steps please, like cache cleaning or clean install, been there done that. I always go through these steps before posting to forums.
[Nexus 6  Original Android Development] yungman:
I'll bet your ro.build.flavor is different to standard purenexus
[Nexus 6  Original Android Development] Nikki1993:
ro.build.flavor = nexus_shamu-user

Someone can check what their ro.build.flavor?

P.S. it seems like ElementalX doesn't care what kind of build it is. I read the post about battery issue on r26 revision but it seems weird to me to "selectively" fix those based on values in build.prop

May take a look at method, even though it's against kernel philosophy :D, how ElementalX universally fixed the issue?
[Nexus 6  Original Android Development] nodnarb91:
This is mine.

ro.build.flavor=nexus_shamu-userdebug

Still pretty strange that you're having this issue. Best of luck trying to fix it.

Also, Happy Thanksgiving to everyone! [emoji1]
[Nexus 6  Original Android Development] Nikki1993:
From manifest file it shows 2 options how to build from source

and I assume User Builds are the one you need to build not UserDebug?
[Nexus 6  Original Android Development] :
Your build flavor doesn't match.

https://github.com/imoseyon/leanKernel-shamu/commit/ac3cd6ab1c20dc7b3798918f0d41841ca2f69b0f

You should probably be able stop healthd and start healthd2 from the shell to see if that's your issue.

It would probably be universally fixed by just stopping healthd and starting healthd2 universally. But it might break backwards compatability or something

You mentioned about flar2 fixing it globally... But that's a hard comparison to make. Elementalx uses the anykernel install method, which preserves the roms ramdisk as much as possible. This kernel provides a boot image such does not.

If I recall correctly, when people were asking flar2 what he did to fix it be told them that he didn't do anything... And indeed there wasnt anything committed to that effect.
[Nexus 6  Original Android Development] Nikki1993:
I've been building regular user builds since day one. I wonder why regular PureNexus builds are userdebug...

Thanks for the info on health service. I will try it once I get home.
[Nexus 6  Original Android Development] daheazle:
Well that's not really the latest build of pure nexus at all...

Why dont you at least recompile using source from the newest PN release? Other than that I would guess imoseyon would have to fix it for your build
[Nexus 6  Original Android Development] Nikki1993:
The build date is wrong. It doesn't seem to change when I dirty flash or clean flash the new build. I compiled the build yesterday. I can even upload the zip file if you don't believe me.
[Nexus 6  Original Android Development] daheazle:
That's odd, I do believe you though. Did you try to change your build flavor in build prop to userdebug? I just changed mine to user, rebooted and had the battery bug, changed it back to userdebug and all was well
[Nexus 6  Original Android Development] Nikki1993:
Will do. Seems like a hassle though to change that with each flash.
[Nexus 6  Original Android Development] daheazle:
Not much of a hassle, just open build prop and add debug to one line. If you make a userdebug build next time I doubt you will have an issue. With a debug build you also will get the multi window option i believe
[Nexus 6  Original Android Development] Nikki1993:
So what's the deal between user and userdebug builds? I was under the impression I was suppose to make user builds as they are "production" builds.
[Nexus 6  Original Android Development] daheazle:
Im not completely sure, but I think the difference is very minor.
[Nexus 6  Original Android Development] :
It's a bit Off Topic for this thread.

http://stackoverflow.com/questions/13950589/difference-between-eng-and-user-debug-build-in-android

Basically, userdebug just adds adb being enabled by default and some debugging stuff.
[Nexus 6  Original Android Development] Nikki1993:
Cheers, then request to [MENTION=3357040]Imoseyon[/MENTION] to add user builds as well to the patch :)

---------- Post added at 06:13 PM ---------- Previous post was at 06:03 PM ----------

Solved!
[Nexus 6  Original Android Development] ghostspectrum:
Never mind lol
[Nexus 6  Original Android Development] frenchy714:
OK, never had this problem before, but lkconfig isn't working for me. I tried both lk and lkconfig after typing su. Running 3.2.7.
[Nexus 6  Original Android Development] demlv:
Uncheck verify path entries option in the terminal settings, then try lkconfig again.
[Nexus 6  Original Android Development] tornido067:
this kernel looks pretty stable :D

if i want to flash on AOSIP Rom (android M 6),should i dirty flash the rom again ?should i flash anything else but this kernel ?(modified boot or something like this) .

thanks and would appreciate any answer .
[Nexus 6  Original Android Development] swapnilsathe:
A dirty flash will do the work
[Nexus 6  Original Android Development] :
Doesn't matter. This kernel flashes a boot image. It doesn't use the existing boot image for anykernel.

So whatever is in your boot image is irrelevant as this will overwrite it.
[Nexus 6  Original Android Development] smclaughlin3:
What's in 3.2.9? Thanks love this kernel
[Nexus 6  Original Android Development] :
Nothing to see here, except a useless post. Sorry for this. Can be removed as soon as a mod passes by!
[Nexus 6  Original Android Development] Freak07:
[MENTION=3357040]Imoseyon[/MENTION]

Hey again :)

I'm still on dirty unicorns and the kernel is running great but I have a problem. With lean kernel the design/cm theme engine apk crashes. When I switch back to the du kernel or elite the problem is gone. So basically if I want to change my theme I have to flash another kernel.

Is that something you could look into?

I will provide logs of the crash if you need them.

Maybe some other user can confirm this issue.

Regards
[Nexus 6  Original Android Development] :
Take a logcat and dmesg when it happens.

Are you running in enforcing? If so, its probably a selinux avc denial.
[Nexus 6  Original Android Development] TransportedMan:
Did you guys personally tweak the interactiveX governor in this kernel? All interactive governors normally males frequencies bounce all over the place and fire up cores constantly but this one sits at 300hmz most of the time when I'm not doing anything on the phone?
[Nexus 6  Original Android Development] Freak07:
Okay I did take the logs. [MENTION=3357040]Imoseyon[/MENTION] maybe you could take a look at this when you find time. But no hurry :)

Kernel was already set to permissive.

https://drive.google.com/file/d/0BxbxiBXaZVu-dDBPWERGc2F4VlU/view?usp=docslist_api
[Nexus 6  Original Android Development] Imoseyon:
Looks like dirty unicorn is CM based (well at least the theme engine is). Marshmallow?
[Nexus 6  Original Android Development] Freak07:
Yes it's marshmallow.

Their source is here: https://github.com/dirtyunicorns

And I'm using the 27th test build from this folder, didn't try lk on 28th:

http://download.dirtyunicorns.com/files/shamu/Test/
[Nexus 6  Original Android Development] Imoseyon:
v3.3 is up. A relatively small update. https://github.com/imoseyon/leanKernel-shamu/wiki/Marshmallow-ChangeLog

I will work on making it CM13 compatible (and hopefully other CM based ROMS as well) next.
[Nexus 6  Original Android Development] scandalousk:
Seems both the main and mirror links are down. Guess it's gonna have to wait until tomorrow.
[Nexus 6  Original Android Development] rmiles7721:
Same
[Nexus 6  Original Android Development] Imoseyon:
haha what the heck. That doesn't happen often.

Here's another mirror: https://github.com/imoseyon/leanKernel-shamu/releases/tag/v3.3
[Nexus 6  Original Android Development] rignfool:
[MENTION=3357040]Imoseyon[/MENTION]

Have you done work on the audio systems...

For the first time ever... I had low battery and no audio fade using Spotify

It's almost witchcraft... No other setup... Not even stock has yielded this result...
[Nexus 6  Original Android Development] TransportedMan:
What's been updated in this version? Any reason to upgrade from previous version? Also when I read your OP I couldn't find the kernels where you can overclock to like 2900mhz and under clock to like 223mhz. You said they were experimental separate builds yet I can't find them browsing through all your Kernel files. Thanks and this rocks in battery life.
[Nexus 6  Original Android Development] Nikki1993:
How about you click on the link in the post you quoted? It's literally a changelog for the current release.
[Nexus 6  Original Android Development] TransportedMan:
How about you relax more so you don't come off as a prick in the future. Not everyone is as tech savvy as you. The changelog is there but if I don't understand what's been changed then I'll ask the guy who created the thing. Thank you I guess, for pointing out the obvious though.
[Nexus 6  Original Android Development] Nikki1993:
I am not that tech savvy. I don't understand many things in changelog. I am chill as I can be. Your question was, what has changed not could you explain the changelog in a more readable format for regular users. Big difference. I only answered the question that you asked. My apologies if it came out in a wrong tone, although that wasn't what I implied.

---------- Post added at 09:56 AM ---------- Previous post was at 09:39 AM ----------

To answer your implied question of readable changelog.

view commit • defconfig: disable CONFIG_SYSVIPC - no idea what this is for. Some kernel config switch

view commit • f2fs: updated to "fix to skip shrinking extent nodes" - F2FS is a filesystem developed by Samsung for mobile devices. Nexus 6 is not using it anywhere (it's using ext4) so unless you formatted your partition in f2fs and have ROM that supports it, it's irrelevant for you. Essentially it's just a fix for an issue in F2FS.

view commit • ramdisk: handle more custom ROMs for battery stats - Battery Stats (the battery icon with percentage in status bar) multiple ROMs had this issue since update to source revision 26. This supposedly fixes battery stats issues where it displays weird number like 4,743, which is current level or smth like that.
[Nexus 6  Original Android Development] gatorz77:
So when using a kernel I usually like to leave all the settings as they are when I flash the kernel and I'm just curious if the min cpu freq is supposed to be 1497. Most kernels I see it's at 300.
[Nexus 6  Original Android Development] Imoseyon:
hmmm are you saying i fixed something? :)
[Nexus 6  Original Android Development] rignfool:
Running all other kernels... I have a real bad audio throttle that happens at low battery...

I could actually force it to happen by rotating the screen...

Interestingly enough... Your kernel does not do it... At all... I just tried to force it to happen as I am typing this message... And I am at 25% battery
[Nexus 6  Original Android Development] daheazle:
I've never actually noticed it, probably because I don't have audio on all that much, but have heard it mentioned over and over again. I have never heard anybody mention it was fixed though. If it is indeed fixed I'm guessing [MENTION=3357040]Imoseyon[/MENTION] is going to get a lot of pm's on what he did.
[Nexus 6  Original Android Development] Imoseyon:
hmmm did it get fixed with a specific version of my kernel?
[Nexus 6  Original Android Development] TransportedMan:
It did. Also I'm sorry for leaving this kernel. I left to try Hydra and just like you said in your OP, I came back to lean eventually. I have just one question, how is it that your interactiveX governor keeps the CPU frequency at their lowest when no input on screen? Its literally like a conservative governor. Did you tweak it to make it work that way. I'm very curious because I was sure my battery life was going to be worse with your kernel because it didn't have the usual conservative governor I love but I couldn't have been more wrong. What sort of sorcery is this?
[Nexus 6  Original Android Development] rignfool:
I do not know... I haven't run your kernel since 1.something...

And boy... Do I feel like a dumbass...
[Nexus 6  Original Android Development] MrBrady:
I just installed this kernel and couldn't get lkconfig working either. It would just say not found.

Changing that terminal setting didn't help, until I tried just lk and then the tuning script launched.

Pure Nexus MM
[Nexus 6  Original Android Development] foshozee:
Thanks for the great kernel. For some reason I can't get into lkconfig. I'm using terminal emulator and this is what I get

u0_a82@shamu:/ $ su

root@shamu:/ # lk

tmp-mksh: lk: not found

127|root@shamu:/ # lkconfig

tmp-mksh: lkconfig: not found

127|root@shamu:/ #

Thanks in advance for any help
[Nexus 6  Original Android Development] Freak07:
Uncheck an option called verifiy path entries in terminal emulator
[Nexus 6  Original Android Development] rauschkugl:
When you rotate your screen the phone switches to stereo mode. That's why there's a little audio lag.