yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Pilz:
I just tried it again and I got a boot loop becusse I set the delay to apply the setting sin tickster mod as 0. I took it off and put interactiveX back.

Does your SOT go down after a reboot? Mine lost "30minutes" in the battery stats.

Also my uc isn't sticking for some reason now I may flash back to the beta3 build.
[Nexus 6  Original Android Development] simms22:
usually no, but sometimes it does. thats because the battery stats for android arent really accurate. its accurate enough to get an idea of where your battery is, but it will very a little bit(sometimes more accurate than other times). oh, and i always apply my settings manually, after boot up.
[Nexus 6  Original Android Development] Pilz:
I usually do the same, but I didn't realize that I hit the "apply on boot" box. Its always fun watching it loop and trying to be fast enough to stop it. I flashed beta4 again and now my settings are sticking s little better.
[Nexus 6  Original Android Development] wrongway213:
Nothing makes me happier than opening this thread and seeing Franco, Yank, Imo all posting back and forth. I don't understand hardly a word that's being said, but I always know when this happens that my device is going to be better in some way in the near future so I do not care... it's quite nice to see all these great minds coming together to help us all. The fact that it happens in this thread like several times a week is just awesome :)
[Nexus 6  Original Android Development] old_fart:
Motorola Finally Posts Kernel Source For Lollipop On 2014 Moto X

http://www.androidpolice.com/2015/02/23/motorola-finally-posts-kernel-source-lollipop-2014-moto-x/

.

Is good ?
[Nexus 6  Original Android Development] mugendon:
Will be testing that @ nbh
[Nexus 6  Original Android Development] resynx:
Agreed, it's awesome seeing friendly devs interacting :D
[Nexus 6  Original Android Development] wrongway213:
The amount of friendly devs on the N6 is awesome in general too compared to pretty much anything else - what an amazing device to own for power users.. we are SPOILED rotten in terms of development, let alone developer collaboration like this. So happy I went with my Shamu man..
[Nexus 6  Original Android Development] Guitarfreak26:
You make the forums even friendlier mate! Its deffo nicer over here than some of the samsung threads i used to be on lol
[Nexus 6  Original Android Development] fitz420:
True story
[Nexus 6  Original Android Development] ZeppelinJ0:
Hi guys I'm getting some random phone lockups and full reboots to safe mode and JM not sure if its the ROM or kernel.

I'm using the latest Chroma with this kernel. Is there some way for me to grab a log or dump of the event that causes my issue?

Thanks!
[Nexus 6  Original Android Development] spinkick:
Why not flash the stock kernel and see if it still blows up?

Are you undervolting at all? If you are, remove that and see.
[Nexus 6  Original Android Development] akellar:
Good for moto x owners, no impact for us
[Nexus 6  Original Android Development] franciscofranco:
You wish! You gotta up your game a little bit to be worthy of that :angel:
[Nexus 6  Original Android Development] supercluver:
It is that I wasn't rooted. I finally rooted tonight and everything works (adb, file browsing, etc...).
[Nexus 6  Original Android Development] apascual89:
Without getting all sentimental, it's a beautiful thing to see :laugh: :highfive:

But seriously great stuff on this thread....
[Nexus 6  Original Android Development] ptesmoke:
[MENTION=3357040]Imoseyon[/MENTION] I have a interesting tidbit for you, pm sent ;)
[Nexus 6  Original Android Development] HTC_Phone:
Does lk support gamma control? Couldn't figure out for sure, and I'm away from computer all day to find out.
[Nexus 6  Original Android Development] ballaz:
Lean Kernel support gamma, lkconfig only supports RBG settings. There is an app a couple pages back for gamma control.
[Nexus 6  Original Android Development] knitler:
Anyone else starting to see battery life fluctuate build to build?

I use my phone the same way every day. Some builds I get amazing life (1.0-1.3 and 1.13 for example) and some are better than stock but not amazing (1.4-1.12, 1.14) but for me 1.15 hasn't really been any better than stock. I'm not sure what causes these changes. I am Stock ROM + Root and nothing else really going on. modification wise. I am not seeing high wake-locks or odd battery usage.

Any ideas?
[Nexus 6  Original Android Development] old_fart:
Is odd. . Do you always go into setup ( ie. su/lkconfig ) and set the things the "same way" ? ? ? . . You know, like option eight - power savings mode for cpu scheduler. Imoseyon was saying ( a few pages back ) to run the 'clear utility' to 'reset' everything to 'defaults' before setup if you're not sure . . . . it will make the ubiquitous functions like 'core configurator' work the way they're intended to. That utility has a link on the OP. You click on 'stable releases' and then click on the blue 'utility' rectangle, and grab the lkconfig_cleaner . . .

hth.
[Nexus 6  Original Android Development] knitler:
I always use the same setup using lkconfig. Everything is defaults except the color configs and disabling 1 wake-lock.
[Nexus 6  Original Android Development] Smallsmx3:
I notice sometimes that the settings in lkconfig don't stick between ROM and/or kernel flashing.
[Nexus 6  Original Android Development] Imoseyon:
I don't have gamma control in lkconfig yet. Waiting for [MENTION=2687578]wrinklefree[/MENTION] to give us the professional calibration data... :)

Two ways I can think of that could cause this. 1) you're wiping data - I store config settings in /data/data/leankernel, so if you're wiping data the settings won't survive, and 2) something else is overriding it - lk-post-boot runs immediately after init so if there are other kernel tweaking apps that have boot settings those will run after lk-post-boot and override lkconfig settings.
[Nexus 6  Original Android Development] wrongway213:
Until we get that, this might help. [MENTION=5263625]neriamarillo[/MENTION] got 6500k and 7500k down with his colorimiter, here's the post where he links his settings.. 7500 looks really good on my device. http://xdaforums.com/showpost.php?p=59042968&postcount=148
[Nexus 6  Original Android Development] Smallsmx3:
Not wiping data, using slim rom ... When I update I wipe cache, davlik(art) cache, and system. Then I flash ROM,gapps, SU ,LK
[Nexus 6  Original Android Development] jiv101:
So wiping system in advance wipe in twrp won't delete storage.
[Nexus 6  Original Android Development] old_fart:
So the answer is "yes" if that was a question. And you use the clean tool if you ( on purpose ) wish to reset the kernel operation.

.

Um. . . twrp lets you wipe data and it excludes local storage ( like where all your music and downloaded roms/kernels sit )

.

But "formatting" data ( to remove encryption ) clobbers it all ! ! !

hth.
[Nexus 6  Original Android Development] mugendon:
Using trickster mod only for undervolting and have kernel settings on boot enabled. Will this still mess with lkconfig settings if no other changes were made in trickster?
[Nexus 6  Original Android Development] semdoc:
Can I ask what is the difference between LCD_KCAL Color Control for shamu and savoca's KCAL pp control adapted for shamu from the end user side? What are the expected benefits?

Asking be'coz I saw that you reverted LCD_KCAL changes by flar2?

Thanx in advance :)
[Nexus 6  Original Android Development] Imoseyon:
If you're only setting voltage via trickster, you should be ok as long as you're not setting anything else. If there's a conflict between trickster and lkconfig, trickster will *always* win since it takes effect after lk-post-boot.

Well one big obvious difference is that savoca's implementation does saturation, hue and contrast in addition to RGB. It also stays entirely inside mdss driver so it's going to be a bit easier to maintain.
[Nexus 6  Original Android Development] purian23:
That's it, we need to make you a Lean Config app, it's time! What do you need from me? I'm near java clueless and can donate lol. Thanks Imoseyon
[Nexus 6  Original Android Development] wrongway213:
As nice as this offer is, there's a part that wonders if it contradicts with the minimalistic spirit of the kernel to require an app to control it. I always assumed that was why this kernel had no dedicated app, could be wrong though, regardless that's quite a nice offer.
[Nexus 6  Original Android Development] purian23:
I've used his kernels off and on since the Galaxy Nexus days. Then I had some Windows Phone time and G2/G3 ONLY because Verizon is jerks against the Nexus line until now! But the best in my area. I would welcome it but more than likely is time as well as it may not be needed as you said. Sure would be cool though!
[Nexus 6  Original Android Development] michmeister:
Which option is best for core control? Disabling mp decision with all 4 cores online ? CPU boost yes or no? Any suggestions which of the Four options is best?
[Nexus 6  Original Android Development] wrinklefree:
Color Calibration Part Deux

Got a chance to calibrate the display for a few hours and here's what I came up with

Reference Calibration

Goals - As close to reference as possible. D6500k color temperature and natural colors

Calibration notes - Unfortunately the color controls don't help in reigning in the over-saturated primary colors. I had the best luck tuning the tint control enough to help the primary colors (R,G,B) with a small sacrifice in the secondaries.

If you've become accustomed to the color "pop" of the N6 OLED screen, the saturation setting of 20 might seem a bit washed out at first. I encourage you to give it some time to adjust to a natural setting. However in the end everyone's different so treat this setting as your "season to taste".

Settings:

Red: 250

Green: 250

Blue: 255

Saturation: 20

Value (Gamma): 123

Contrast: 128 (default)

Hue: 1515

Color Before:

Color After:

Color temperature:

Gamma:

Cool color setting

Goals - Cooler D7500 temperature with a bit more "pop".

Red: 232

Green: 228

Blue: 255

Saturation: 26 (again season to taste)

Value (Gamma): 126

Contrast: 128 (default)

Hue: 1515

Color temperature:

Enjoy everyone!
[Nexus 6  Original Android Development] poczynek:
Thanks so much!

What should contrast be?
[Nexus 6  Original Android Development] wrinklefree:
Contrast only made the measurements worse, so I kept it at the default of 128
[Nexus 6  Original Android Development] Imoseyon:
This guy ---> [MENTION=2687578]wrinklefree[/MENTION] <--- awesome
[Nexus 6  Original Android Development] Remoteconcern:
Wrinkle free, that's great! Thanks so much. I had noticed the saturation control didn't turn down the primaries but hue seems to do the trick.
[Nexus 6  Original Android Development] semdoc:
All clear :good::good:
[Nexus 6  Original Android Development] mimsiroll:
Can i ask a suggestion regarding kernel app? May i suggest synpase by apb axel its a really nice app.
[Nexus 6  Original Android Development] slekkas:
I'm posting here the solution to my problem regarding the phone turning of at 50% battery or 37% etc because I've read a lot of people complaining about it. You will see after applying the settings the battery percentage will change and show the real battery life.

1) Power off your phone.

2) Press and hold the Power and Volume Down buttons. This will put the phone in fastboot.

3) Use the Volume buttons to scroll through the menu until you see "Bootloader logs"

4) Press and hold the power key for a long time (7+ seconds) until the phone reboots.
[Nexus 6  Original Android Development] cd993:
Interesting, what exactly does this do? A form of battery calibration?

Sent from my Nexus 6
[Nexus 6  Original Android Development] slekkas:
Yes... My battery was showing 37% and after I did it it showed 14%...
[Nexus 6  Original Android Development] akellar:
Pretty sure all you are doing here is going into the bootloader and rebooting. The battery percentage will often change during a reboot or bootloader session.
[Nexus 6  Original Android Development] slekkas:
No. I've even done a full reset and rom change and gotten in the bootloader a dozen times. Problem was still there. Not only for me but for many people. I think my battery calibration problem started when I started using wireless charger.
[Nexus 6  Original Android Development] akellar:
Very well may be but you're still not doing anything other than rebooting from the bootloader
[Nexus 6  Original Android Development] slekkas:
Regardless I've been trying to find a solution about this for over 15 days now and no one came up with this solution.
[Nexus 6  Original Android Development] Jubei527:
Hi,

Do I have to flash no-mpdecition every time I update this kernel.

Thanks
[Nexus 6  Original Android Development] Berlino:
No, it's not necessary to flash nofreq-mpdecision.zip anymore...you can configure it via terminal/lkconfig.
[Nexus 6  Original Android Development] Mervingio:
Are this OK not sure if I turn off or what?
[Nexus 6  Original Android Development] Krunk83:
Notice how it says "use at your own risk"?

Nexus 6
[Nexus 6  Original Android Development] wrongway213:
I can't confirm or not whether it's OK, but I can confirm that error is not typical lkconfig behavior. I haven't ever gotten that error myself.. hopefully Imoseyon or at least someone a little (lot) smarter than I can shed light on that. It's definitely not an error message I get with lkconfig , though.

I mean, lkconfig always says that - I'm assuming he is referring to the error portion of the screenshot, lol
[Nexus 6  Original Android Development] Imoseyon:
Ah yeah [MENTION=3871605]Mervingio[/MENTION] and [MENTION=5964313]wrongway213[/MENTION], you can ignore that error. It just means that those cores are offline at that moment. I will see if I can silence them in v1.16.
[Nexus 6  Original Android Development] wrongway213:
Ah - I always only enable 2 cores, suppose it makes sense I'd n ever have seen the error. I assumed it was abnormal as I've flashed this kernel 100+ times (quite literal) and have never seen it. I'll never select anything other than 2 cores, though, so I could flash this kernel 1000 more times and I would have never seen that error - funny how much experience you can have with something and not know basics about it depending on how those "basics" pertain to you. As for 1.16.. good luck finding things you haven't already fixed between you, Yank, Franco, flar and the rest of the brain trust around here, haha.
[Nexus 6  Original Android Development] djcsurf:
One thing I noticed since using option to turn off mpdecision, 2 cores and boost off is there seems to be a slight lag when wanting to unlock the phone after s2w. I have to wait a split second to unlock after waking the phone. On AICP ROM so if no one can confirm may just be me.
[Nexus 6  Original Android Development] Imoseyon:
Yup I believe my kernel is pretty mature now for 5.0.x. Stability/performance should be optimal - feature-wise I'm not looking to add much more, if any. Once google releases 5.1, there will be a whole lot of work to do.

That's probably expected. Some of the "butter" is gone when you disable mpdecision and cpu-boost.
[Nexus 6  Original Android Development] wrongway213:
I honestly have never noticed the smoothness drop in any way when I disable mp-decision, I don't use cpu-boost either... weird. I have never noticed anything other than worse battery life with mp-decision enabled on my device
[Nexus 6  Original Android Development] randomnoob83:
Between this kernel and code blue which do you guys feel give better battery and performance? Or is it more about the settings? And recommendations? Running euphoria os
[Nexus 6  Original Android Development] poczynek:
Um in this thread what answer ya reckon people will give?

LK of course. Although I've never used the other...
[Nexus 6  Original Android Development] wrongway213:
Both kernels are top notch - more about settings. If you want certain customizations like wakelock blocking and the option to switch SELinux permanently to permissive (and back) on the fly, leanKernel is going to be a better bet. If you don't care about either of those, features, though, it's simply personal preference - both give great performance and battery life. just depends what you like/how you use your device. I personally use lean - permissive kernel and wakelock blocking (and general spirit of being first to test new fixes - I like cutting edge) are important to me.. however, as far as simple battery and performance.. that's a tough call. Both are good enough I'd recommend trying both to see what you like, unless of course you want a permissive kernel or one with wakelock blocking.

---------- Post added at 11:07 PM ---------- Previous post was at 11:05 PM ----------

Lol truth.. tried to keep bias out of my answer because Code Blue is awesome too though
[Nexus 6  Original Android Development] Imoseyon:
Yeah it's subtle at best. I don't really notice the difference either.
[Nexus 6  Original Android Development] jeromechrome1:
Having God awful battery life on latest build of chroma rom + lk latest stable build. No rogue apps freezed errthang i n greenify, better battery stats doesn't pickup any thing out the ordinary in settings screen is the highest burner but that's normal, any ideas? All stock settings BTW,

Sent from my Nexus 6
[Nexus 6  Original Android Development] s2d4:
Use wake lock detector, better battery stats is wrong most of the time.

Then use myandroid tools to disable or use amplify to limit control it. Done.
[Nexus 6  Original Android Development] Franzie3:
I actually just switched to Chroma after a stint on Validus. I havent had any issues so far. Running wiht LK and a bunch of config options. I will say that this time i did not restore any of my app data. only for certain apps that i felt i needed to that i didnt want to set up (msecure, qloud, BoA, etc) anything that was just a login i go as needed (instagram, facebook, etc). now i was at 97% last night at just before 2AM at home on wifi and couldnt sleep so my phone got a lot of use. some games, videos, fb, instagram, tapatalk, chrome beta web use, forum reads, etc. as of right now (turn off wifi at 9AM on LTE at work). im at 49% remaining with 2 16min SOT. i think my phone is in a happier place right now.
[Nexus 6  Original Android Development] akellar:
I stopped reading at "errthang"
[Nexus 6  Original Android Development] nobnut:
I beat you by one word. I stopped at 'freezed'. Maybe I'm a traditionalist, but I prefer 'frozen'.
[Nexus 6  Original Android Development] wrongway213:
This should not have been even a tenth of as funny as it was.. I just completely lost it for some reason reading this response.:D
[Nexus 6  Original Android Development] Imoseyon:
[MENTION=4321985]jeromechrome1[/MENTION], try some of the following (in addition to suggestions above):

1) Turn off screen, wait like a min, and then go back in to check if your phone is sleeping. You can use an app like trickster or kernel tweaker to check.

2) Were you in an area where data network coverage was bad? This will do it.

3) Make sure your screen brightness is not too bright - this will also do it too.

4) Could be the ROM too - flash the previous nightly or the next nightly.
[Nexus 6  Original Android Development] _invader_:
Posting my experience with an oddity with Wireless Display adapter discovery when running the 1.15 kernel series...

I have a Tasker task that uses Secure Settings to launch the [Cast screen].Settings$WifiDisplaySettingsActivity and then waits 3 seconds to send Dpad events to select and start casting to my adapter. This has worked successfully 95+% of the time while running LK <= 1.14.

After recently updating to 1.15, I started experiencing failures to connect. I've found that the *first* time after rebooting that my device opens the Cast Screen menu and everything works...but...from that point forward, the Cast Screen menu takes an extra 2 seconds to identify my device. I've increased my Tasker wait time to 5 seconds and things are working again (though I've only tested a few times...not enough to see if that delay time continues to get worse).

I did roll back to LK 1.14, changed my timeout back to 3 seconds, and confirmed that the device is quickly identified and everything worked again (ran for around a week to make sure) and that upgrading to LK 1.15.5 (not sure what's changed with the .5, but just decided to use the newest test build) it would connect the first time but not on subsequent attempts when using the 3 second delay.

I'm going to continue to run LK 1.15 to see if the timeout requirement stays consistent or if the delay varies any over subsequent runs (whether the delay increases over time). I'll report back if this varies at all...
[Nexus 6  Original Android Development] badpanda:
HI! sorry for this question... how do I exactly do this? is there an app? or within tricksterMod? Thank you so much :fingers-crossed:
[Nexus 6  Original Android Development] wrongway213:
This thread: http://xdaforums.com/android/software-hacking/dev-kcal-advanced-color-control-t3032080

This app: http://downloads.codefi.re/savoca/kcal/re.codefi.savoca.kcal-v1.1.apk

Holy wow @ the size of the post you quoted, lol

Enjoy!
[Nexus 6  Original Android Development] badpanda:
Excellent thank you so much! looks great with the settings.

I had one more question, what is Minimum? is set to 35 now I believe.:highfive:
[Nexus 6  Original Android Development] wrongway213:
I have no idea what any of it means - I just know wrinklefree has professional calibration tools and I don't, and when I put in the numbers he suggests my colors look great, so I don't ask questions lol.
[Nexus 6  Original Android Development] galaara98:
May I just say that was the most honest and humble statement while giving credit where do I have read/heard in a long time. Well said..

Well said.
[Nexus 6  Original Android Development] oak:
Wow! Wrinklefree's colors are fantastic. Amazing really. Thanks very much. I do not usually mess with the colors, just for the heck of it, gave it a try. I am glad I did.

LeanKernel is great, as always, too.
[Nexus 6  Original Android Development] SilkyJohnson:
Dude, don't ask questions like this is any thread. Incredibly poor taste and disrespectful to the thread owner.
[Nexus 6  Original Android Development] Franzie3:
Hey all....quick question. Besides greenify, and obviousky uni stalling..what else can you do to limit the battery consumption by Facebook?
[Nexus 6  Original Android Development] SilkyJohnson:
Did you do the top of bottom settings? I did the bottom one and it looks great.
[Nexus 6  Original Android Development] oak:
I tried both and both are great, but I like the top settings best.

Oops, meant to quote [MENTION=5950417]SilkyJohnson[/MENTION]
[Nexus 6  Original Android Development] wrongway213:
Limit permissions in app ops

Limit permissions in My Android Tools

Use Facebook Lite/Tinfoil/insert third party here

Personal recommendation: Use your mobile browser, place a Bookmark on your Homescreen and name it Facebook, edit the icon to the FB icon from your icon pack of choice and uninstall the mobile app. If you want push notifications, install IFTTT and configure via the RSS feed on your Facebook profile - you will still get push notifications that way and it is MUCH easier on battery. This is what I do, minus IFTTT as I do not care about push notifications.
[Nexus 6  Original Android Development] blakmazk:
Just Wanted to appreciate the results... Thanks a lot for this awesome kernel...
[Nexus 6  Original Android Development] NikWillOrStuff:
bit of a late response, but it simply limits how low you can set the RGB values. because if all three RGB values are 0, the screen is off. and you can't see anything on your phone anymore.
[Nexus 6  Original Android Development] arcanexvi:
I see 1.16 on the server so... Gonna go ahead and grab it even though I dunno what's in it. What could possibly go wrong! ?
[Nexus 6  Original Android Development] badpanda:
Awesome! Looks great with this settings...!