yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] numerouknow:
totally agree with [MENTION=662522]slekkas[/MENTION].

it is not clear yet whether this is an issue with kernel or rom or device. its random. fortunately, [MENTION=3357040]Imoseyon[/MENTION] phone also has this issue. i used the word 'fortunately' cuz now the dev has a hands-on experience of the said issue and i am sure its a lot better this way than facing a problem that the dev cannot reproduce.

i get what you are saying about draining the battery till 5%, recharging and repeating it next day; its not gonna happen that often but users have reported different numbers at which their phone went off. if am not wrong someone said his phone turned off at 13 or 14% and thats scary lol. on one hand people are using powersaving mode/uv to save every bit of juice they can and on the other, their phone can only use as much as 85-90% of the full battery (assuming the battery % is reported accurately).

ps: of course i was wrong. user reported that his phone died at (not 13%, not 14%) 17% battery. and it was none other than the one i quoted below.
[Nexus 6  Original Android Development] mugendon:
Just upgraded to 1.14 and the issue is gone. Don't know what you have done [MENTION=3357040]Imoseyon[/MENTION] but maybe you accidentially fixed this ;)
[Nexus 6  Original Android Development] __NBH__:
This might be coincidence but since limiting the wake locks via lkconfig, the time on my lock screen is very slow to update. My time is set via the mobile network so I was wondering if limiting one of the wake locks is stopping it from updating as often. I will do some testing and see.
[Nexus 6  Original Android Development] cam30era:
I've been seeing the same thing since 1.13. Really, it's just an observation, no big deal though.
[Nexus 6  Original Android Development] wrongway213:
Understood - just wondering if there was a reason people think its kernel related even though its happened to Franco users as well.

Ah, Imoseyon himself is our proof it happens on stock - forgotten he runs stock as it wasn't mentioned since he obviously doesnt need to turn in detailed error reports to himself lol

.
[Nexus 6  Original Android Development] bradputt:
[MENTION=3357040]Imoseyon[/MENTION] ,the Kcal color control V2 is out. nexus 6 is now supported.

could you please take a look?

http://xdaforums.com/showpost.php?p=58987156&postcount=53

[YOUTUBE]zHBtmYPy4MM[/YOUTUBE]
[Nexus 6  Original Android Development] Imoseyon:
[MENTION=5964313]wrongway213[/MENTION], congrats on your baby! [MENTION=2662403]bradputt[/MENTION], I'll see if I can include it in v1.15.
[Nexus 6  Original Android Development] Imoseyon:
v1.15 is up.

I was going to release this last night but then I went out drinking instead and kinda got wasted. :D I'm glad I waited because it looks like savoca figured out hue/contrast/sat control for shamu. So I added that fix like 5min ago - hopefully it doesn't cause issues.

Lots of changes in this release. Most notably, ramdisk changes for compatibility with CM12 (and other ROMs like Euphoria which users superuser instead of supersu), KCAL control code switched to [MENTION=4316709]savoca[/MENTION]'s (thx) implementation, and the usual Linux, CAF updates and fixes. Full changelog here: https://github.com/imoseyon/leanKernel-shamu/wiki/Lollipop-ChangeLog

Oh yeah i snuck in a fix for simple_ondemand gpu governor so it doesn't crash your phone anymore.
[Nexus 6  Original Android Development] italia0101:
Holy crap it works, and it's awesome! So. Much. control
[Nexus 6  Original Android Development] djcsurf:
Not sure if related to 1.15 kernel but I flashed it earlier, since then Ive booted into recovery to flash a couple of things and it doesnt reboot properly, stuck on boot animation. I have to hold down power button to force reboot then it boots fine.

Nexus 6

Would anyone mined checking it's not just issue my end, thanks.
[Nexus 6  Original Android Development] ZiggSVO:
What app is being used to control all the values?

Sent from my Nexus 6
[Nexus 6  Original Android Development] wrongway213:
I didn't have anything to flash, but I am able to reboot from recovery on 1.15 with no issues on my N6.
[Nexus 6  Original Android Development] italia0101:
http://downloads.codefi.re/savoca/kcal/re.codefi.savoca.kcal-v1.1.apk
[Nexus 6  Original Android Development] Krunk83:
Thanks.

Any way to fix the phone not waking up while sleeping using either the power button or gestures? Sometimes it doesn't respond at all and I have to reboot. Thanks.

Nexus 6
[Nexus 6  Original Android Development] ZiggSVO:
Just found this a second ago thanks!

Sent from my Nexus 6
[Nexus 6  Original Android Development] wrongway213:
I've heard that some users have FC issues with that app - for those that do have issues with FCs it's been recommended to use Kernel Adiutor,
[Nexus 6  Original Android Development] natezire71:
You using the powersave option in lkconfig?
[Nexus 6  Original Android Development] Imoseyon:
[MENTION=2687578]wrinklefree[/MENTION], calibration please! :)

I've not been able to reproduce this even once (and I've been trying for weeks). It's gotta be a condition specific to some combination of hardware, app installed, ROM, and/or kernel. And i think you said you don't OC or UV so that's not it either.

Edit: this is a long shot but what you may want to try is boost your voltage for just 300mhz or across all frequencies.

I like this app. It's simple and minimalistic. :D

I'd be interested to hear if this happens on my kernel too but not likely a kernel issue.
[Nexus 6  Original Android Development] wrongway213:
I haven't a clue - honestly I don't know the difference between KCAL and RGB calibration. I just know Code Blue users experienced FCs with the coda app and were using Kernel Adiutor instead, as it's the only free kernel app that was suggested with KCAL support. It's kind of ironic now that I think of it that I am advising people about something, yet I genuinely do not even know what it is.
[Nexus 6  Original Android Development] Johnny424:
well done imosey.
[Nexus 6  Original Android Development] jackpollard:
Thanks for the suggestion of the Kernel Auditor app, I tried loading the coda app 3 times and keep getting a parse error. No big deal, KA worked like a charm.
[Nexus 6  Original Android Development] Krunk83:
Is there a way to restore defaults on all settings using lkconfig? Where do I change the voltage?

Edit: I think I got it. 1 for CPU control and then 1 for min frequency? Then I chose 3(653mhz) to test. Thanks again.

Nexus 6
[Nexus 6  Original Android Development] old_fart:
nope, i have not seen one. they do persist.

trickster. 3C tools. Kernel adiutor.

i was a just in there and ( for me ), i could not get the min and max to stick ! so i am now doing a FULL wipe . . . .
[Nexus 6  Original Android Development] Krunk83:
Sticking for me. Are you on 1.15?

Nexus 6
[Nexus 6  Original Android Development] dsmitty166:
FYI Euphoria-OS is aosp based, we just have some cm additions

[emoji3]
[Nexus 6  Original Android Development] Amaze209:
Anyone have any recommended settings for kcal?
[Nexus 6  Original Android Development] rignfool:
You restore defaults by deleting /data/data/leankernel

For voltage... You have to download a third party kernel app... Or... Set your voltage table in sysfs...

I recommend a kernel app
[Nexus 6  Original Android Development] Imoseyon:
1) there's a zip file in the util folder that will clear all lkconfig settings. Or just remove the folder like [MENTION=3290808]rignfool[/MENTION] suggested.

2) lkconfig does not configure voltage at all. But what you're doing is one way to raise voltage by raising the min freq. Let me know how that works out.

Ah that's right - will fix my release post to reflect that.

Yeah there is a bunch out there. Trickster, kernel tweaker, etc.
[Nexus 6  Original Android Development] funcrusher:
Do you know what version of lk that problem started for you?
[Nexus 6  Original Android Development] Krunk83:
So far so good.

Nexus 6
[Nexus 6  Original Android Development] rignfool:
Interesting question....

To anyone having the 'early' shutdowns... Are you using battery saver...

People who can get their phones down the 1 & 2%... Are you using battery saver?
[Nexus 6  Original Android Development] BrianTX:
My battery goes all the way down, and no I don't use battery saver.
[Nexus 6  Original Android Development] Krunk83:
I do not. Recently though. I'm going to delete my data folders and start over. Go from there.

Nexus 6
[Nexus 6  Original Android Development] wrongway213:
I'm gonna laugh hard if it''s battery saver.. so, so hard.

Finally got a chance to read a little on KCAL - sounds awesome. That said, unfortunately it sounds like a good lot of us are gonna have to wait for a calibration guru to come in (like the guy who came with the 237 235 255 RGB values), as it sounds like KCAL settings are incredibly sensitive to the device you're on - either way, I'm excited to see we're about to get even more color control, although I still don't know what it's gonna do yet - I'd rather wait on someone who knows what they're doing than make my screen look worse, and if I'm not mistaken I believe Imoseyon already tagged someone about it.
[Nexus 6  Original Android Development] jiv101:
I don't have battery saver on and mine dies at 4%
[Nexus 6  Original Android Development] wrongway213:
I don't know that I think any of these 5% or under shutdowns are errors or issues though - I'm worried about people shutting down at 17, 10- I don't think dying at 5% or below is unusual behavior for this hardware. Maybe I am wrong, but that's the impression I have gotten from flashing... well, a good majority of what there is to be flashed at least once.. but I could be wrong, maybe shutting down shouldn't happen before 1%.
[Nexus 6  Original Android Development] mugendon:
Since deep discharge can damage the li-ion batteries, I think it could be a feature (for 5% and less).
[Nexus 6  Original Android Development] rignfool:
From what I understand...

Our batteries 'die' at around 40% voltage... Any less than that... And you start to damage the battery
[Nexus 6  Original Android Development] wrongway213:
I think you're somewhat correct but the wording sounds a bit harsh for my understanding.. what I've gatherd is that 40 - 80% is the "sweet spot", you don't wanna stay below 50% often but you don't wanna plug in at 80+ either just because it's the time you normally would charge - if you're worried about degradation to your battery afaik you wanna keep it between 40 and 80%... I was of the impression this 40% think was very, very minimal though, unless you habitually drop lower.. it's hard for me to say definitively because no two battery articles I've ever read seem to quite agree with one another fully lol.
[Nexus 6  Original Android Development] rignfool:
I have almost the same understanding...

However....

From what I've read... That 40%-80% is the 100%-0% that we read on the fuel gauge...
[Nexus 6  Original Android Development] wrongway213:
yikes - that seems kinda contradictory to the rest of the understanding, inasmuch as 0 - 100 on a fuel gauge is the opposite of minimal.. the rest of it is all.. well, minimal. I'm curious as to what the real true "right" way is with modern batteries such as our Shamu.. my instincts tell me they've evolved far enough that it's really just "dont be an idiot and overheat/let die", but hopefully something will come up to read that will give us both and everyone else a more definitive understanding at some point.
[Nexus 6  Original Android Development] jiv101:
How do you set intelliplug instead of mpdecesion with lean kernel
[Nexus 6  Original Android Development] wrongway213:
You don't - there is no intelliplug or hotplug replacement on leanKernel - just either mpdecision or userspace defined values - and I do not understand it a bit but it functions simply lovely that way in my opinion.
[Nexus 6  Original Android Development] akellar:
Intelliplug isn't in lean
[Nexus 6  Original Android Development] jiv101:
I only ask cause when I go into my elementalx app it shows

I sent that as an attachment also don't know why two showed up
[Nexus 6  Original Android Development] old_fart:
Hmm.

Well, the complete wipe fixed my little glitch. . And it is a wtf kind of a thing because I've been staying with the same rom and kernel for quite a while. ! . . Miss-behaving app ?

.

I'm reminded that part of my job ( way back when ) was to process ( with visual studio 6 apps ) all incoming data for the center. Data would be dropped into a sub directory. This robo task tool would be in a constant loop, looking in directories, looking for something to do. Windoze server was really dumb back then . . Then it evolved with wmi services / triggers and no more looking and looping. . If something changed in the directory, boom, it got picked up.

.

( I am finally getting to my point now . . . old people are long winded . . . ) .

Can there be a watchdog or monitor on the settings for leankernel so you would know when something touched it ?
[Nexus 6  Original Android Development] wrongway213:
The screenshot doesn't show Intelliplug -or is that why you are confused, you're used to seeing it there? If so, it's simply not there because it's not available on leanKernel - in any kernel control app it simply won't display. However, If the screenshot is supposed to show something else, could you tell me what it is? I'm not seeing anything unusual at all assuming you chose to lower you max freq

Edit: now I see the second screenshot. As there is no Intelliplug/hotplug replacement in leanKernel, kernel control apps usually show mp-decision enabled even when it's not. As long as you're min freq sticks at 300 and doesn't change, mp-decision is disabled - if your freqs don't stick then mp-decision is really not disabled.
[Nexus 6  Original Android Development] jiv101:
I've disabled mpdecesion in lkconfig but it still shows enable in my kernel app
[Nexus 6  Original Android Development] wrongway213:
Yeah, you either edited post or my internet didn't load second image the first time. See edited reply above
[Nexus 6  Original Android Development] old_fart:
Ah, read that the "cracker jack" devs behind the euphoria rom gives you the choice of using 'blue plug' ? ? ?
[Nexus 6  Original Android Development] wrongway213:
I believe that's the hotplug variant from Code Blue kernel.. would be interesing to see that on lk.. now that you mention it I knew I had seen mention of this somewhere but could not place it. For all intents and purposes other than Euphoria, though, there is no hotplug replacement for mp-decision.. just kill it and profit.
[Nexus 6  Original Android Development] jiv101:
When I turn off mpdecesion in app all 4 cores activate at my minimum 300.that's what it's suppose to right?
[Nexus 6  Original Android Development] wrongway213:
depends what you're doing - you selected option 1, two cores, so four cores should only kick on when load is heavy.
[Nexus 6  Original Android Development] grayskul:
I'm having problems unlocking the phone. It hangs at the lockscreen for a second or two then I can unlock it. I'm not sure of this would be a kernel issue or not. I'm running 1.15 on Dirty unicorns.
[Nexus 6  Original Android Development] suku_patel_22:
Do you have that "Prevent accidental wake" turned on? I was having similar issue on Chroma. Disabling it fixed it for me. I don't use wake gestures anyways.

Sent from my Nexus 6
[Nexus 6  Original Android Development] grayskul:
Where would I find that setting? I've never heard of it.
[Nexus 6  Original Android Development] jiv101:
In settings under display
[Nexus 6  Original Android Development] dsmitty166:
You're right. That crappy kernel let's you use mpd, inteliplug, or blu_plug.
[Nexus 6  Original Android Development] poczynek:
Yes I have been getting a few times where I cannot unlock my screen. Will not wake up. Then I have to hold the power button for a good 5 seconds or more and it comes on. Sometimes from a deep sleep but sometimes not. Can't work out what causes it be it rom or kernel or my own settings. I do use wake gestures and have used all manner of kernel settings - battery saving or more performance type - and it still happens.

I think it has to be in wake gestures somehow.

Anyone else get this?
[Nexus 6  Original Android Development] Imoseyon:
I believe (at least) some of the kernel apps do not truly disable mpdecision. All they do is change the permission of the sysfs nodes so that mpdecision cannot modify them - so if the permissions are the same the kernel apps may still think that mpdecision is enabled. Lkconfig truly disables it.
[Nexus 6  Original Android Development] Imoseyon:
You know your description reminded me that I have run into this before. Only a couple of times total - both times I was away from computer so I could not pull logs. And it's been a long while since I've seen this. Is this what some of the other folks are running into? It would be good if someone can pull dmesg (or logcat) right after it happens.

I've let the phone shutdown several times in the last couple of days, they were all under 5%. The consistency of this makes me think that this is probably by design. 17% definitely isn't normal and I don't think others have seen that.

I did manage to grab logcat right when it was shutting down tonight. I will look through it but it may take me a while especially since I don't know much about ROMs.
[Nexus 6  Original Android Development] poczynek:
Tried these values recommended in the chroma thread and they are seriously very very good:
[Nexus 6  Original Android Development] poczynek:
Man you've got to try those values above! Like a new phone almost! Slight exaggeration but they are great.
[Nexus 6  Original Android Development] elijahah:
What app is that?
[Nexus 6  Original Android Development] poczynek:
http://downloads.codefi.re/d/6E5L78...93/savoca/kcal/re.codefi.savoca.kcal-v1.1.apk
[Nexus 6  Original Android Development] grayskul:
It's not there.

Same as above. I'm on Dirty unicorns.

---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------

Link isn't working for me.
[Nexus 6  Original Android Development] smclaughlin3:
Does this override lkconfiglkconfig color settings and shamand change them or lk config conkeep those oon top of those values? Thanks
[Nexus 6  Original Android Development] poczynek:
Overrides.
[Nexus 6  Original Android Development] nobnut:
Only if the user selects 'Set on boot' in the app (which you hadn't in your screenshot). Otherwise it obviously defaults to the lkconfig settings after a reboot.
[Nexus 6  Original Android Development] poczynek:
Oh yep sorry!
[Nexus 6  Original Android Development] Remoteconcern:
Does anyone have any good calibration values yet? My number one annoyance about this phone was how different photos looked on it versus everything else so I'd love to shoot for some more colour accuracy.

The settings posted above look absolutely terrible on my screen though, which I guess is going to be the problem
[Nexus 6  Original Android Development] numerouknow:
v1.15 (powersaving) + croma rom

at this rate i shud get thru the day with 8hrs sot :o

never expected to get over 6hrs sot

no stutters, no lags... i dnt see any drop watsoever in performance after switching to powersaving.

keep up ur great work [MENTION=3357040]Imoseyon[/MENTION]

thanks for your time n effort... much appreciated.
[Nexus 6  Original Android Development] savoca:
Naw it's an SELinux issue - happens only when you use a ROM that had RGB control all context'd up in initramfs like CM - why? Because I suck at Android apps.
[Nexus 6  Original Android Development] Mistertac:
Considering you've done a thing or two before to help us all out... The Android Community forgives you.
[Nexus 6  Original Android Development] wrongway213:
The Falls huh? Small world man - got neighbors out here fixing color calibration for all of us and I didn't even know it lol
[Nexus 6  Original Android Development] purian23:
Your app & this kernel work great! Thank you :)
[Nexus 6  Original Android Development] slekkas:
I'm very sad now. I installed 1.15 all working fine and decided to test the power saving mode in lkconfig after reading a few posts back that it has great results. My phone this time shut down at 29% [emoji20].

So apparently my problem is some how related to power...
[Nexus 6  Original Android Development] purian23:
Random Reboot

Hey [MENTION=3357040]Imoseyon[/MENTION] I unfortunately just had a random reboot on 1.15. I have all stock settings on the kernel with the only difference is I had the gov set to OnDemand. I pulled the log as soon as it booted back up.

I have no other mods/Xposed etc installed. Stock/CleanROM. Might not be kernel related but I wanted to send your way! I was on chrome browsing movies when this lockup and reboot occurred. Thank you sir!
[Nexus 6  Original Android Development] Remoteconcern:
I haven't checked the log, but did you turn off CPU boost? Ondemand is highly (all the governors are apart from interactive) unless you turn it off. If you did, maybe someone can read the log :)
[Nexus 6  Original Android Development] jackpollard:
http://xdaforums.com/showpost.php?p=57265483&postcount=620
[Nexus 6  Original Android Development] Imoseyon:
Unfortunately your log does not show that the phone rebooted due to the kernel. I would not recommend ondemand on shamu either way - it's not as stable as interactive.

This part seems interesting. Do you have an app called LGColor (or something similar)? Also for me dmesg is more useful - it would at least tell us whether kernel has anything to do with your issue or not. "adb shell dmesg > dmesg.log" would do it.

That's definitely not normal. I suspect you got a hardware issue. I'd first wipe data, reflash stock ROM, and then try draining battery first before you do something about it at the hardware level though.
[Nexus 6  Original Android Development] old_fart:
[MENTION=2906672]dsmitty166[/MENTION], please accept my apology for implying a wrong/bad phrase. You and your team do "outstanding" work !

RE: << http://www.answers.com/Q/What_is_a_cracker_jack_team >>
[Nexus 6  Original Android Development] dsmitty166:
Lol I was replying with sarcasm. No offense taken. Were good man lol
[Nexus 6  Original Android Development] purian23:
Thanks for your reply. I just checked as I wasn't aware of that. It looks like CPU Boost did indeed turn off by default once I selected OnDemand. I use the ElementalX app to control the kernel and double check CPU Boost being off.

Edit: Thank you [MENTION=3357040]Imoseyon[/MENTION] for your reply and looking into the logs. I will stick with Interactive as advised!
[Nexus 6  Original Android Development] slekkas:
I got scared for a second. I tried installing another kernel that I already had in my phone but after boot the phone would shut down. Tried fk, elementalX but no luck. I downloaded the lk cleaner I installed it and now it booted fine. Could it be that there was some left over files causing the problem? Now I'll drain to see what happens...
[Nexus 6  Original Android Development] Remoteconcern:
Thanks. That takes care of the colour part. Just need someone to help us out with saturations.
[Nexus 6  Original Android Development] wrongway213:
That was very nice of you to post that link - XDA being an international site like it is, I feel like sometimes total confusion happens based solely on things not translating - I know this particular case was sarcasm and not a language barrier issue, but I appreciate that you took the time to make sure it was clear to everyone that you had nothing but respect for the developers in question - if all language confusion situations were handled with this kind of etiquette XDA would have a 99.9% reduction in flame wars. Thanks for providing a good example to the community as a whole - I appreciate when I see posts like this of people going out of their way to be respectul.
[Nexus 6  Original Android Development] Imoseyon:
oh wow I thought crackerjack had a negative connotation as well and I speak english. lol