yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] mastamoon:
Last night I looked over and saw my phone at the boot animation. First time I have ever seen a random reboot with my Nexus6. Im on v2.8 with no other mods on a stock rom. I went to grab a last kmesg and noticed the option is greyed out in syslog which usually means the kernel doesnt support last kmesg.. is this right or did the reboot I had just not produce one?
[Nexus 6  Original Android Development] lainemac:
ZenKernel has what he's calling zen decision, which by default is enabled leaving MP disabled.
[Nexus 6  Original Android Development] funcrusher:
Hmmmm...

Coming from lK 2.8 I dirty flashed my rom then flashed Zen and when I booted up mpdecision was still enabled, so it might actually be something with Kernel Adiutor. I certainly didn't enable hotplug settings on boot, so I'm not sure why that would happen.
[Nexus 6  Original Android Development] GuyInDogSuit:
Works fine for me.
[Nexus 6  Original Android Development] Luke2508:
Ok, so I uninstalled Trickster mod, I don't have any other apps that could be changing it/ Then I checked your testbuilds folder and installed 2.8.3 . After that when I tried to set min freq, I no longer had the 233MHz option either (which I had before, even when 2.9 wasn't present) so I reflashed 2.8.2 and it still was no longer there. So my guess is that maybe once flashing a none OC/UC kernel (which I did for 2.6 I think by accident) it removes the option for you. Is there a file I can delete or something that has all the lkconfig settings, so it's like wiping it without me having to do a clean install.

Thanks so much for the help bro. I appreciate the time you take out of your day to help people like me with problems, never mind the time it takes to develop such a great kernel, THANK YOU!
[Nexus 6  Original Android Development] bradld:
[MENTION=371565]LordDeath[/MENTION]: Same Here...no boot on the latest nightly.
[Nexus 6  Original Android Development] lainemac:
That could have something to do with it. I use the same app, unless I'm running lean. Then I tend to use lk config
[Nexus 6  Original Android Development] Rebel908:
Is there a recommended app to tweak voltage? Been using Kernel Aduitor, but I'm also seeing drastic benchmarking drops.

I would hazard a guess that the universal voltage offsets are the cause, and wondering is there a recommended voltage drop for those looking to tweak that?
[Nexus 6  Original Android Development] niko2931:
Are you encrypted?
[Nexus 6  Original Android Development] droid fetish:
Nothing but boot loops on Chroma with Leankernel for me, I used these together in the past an worked fine. I'm really in a pickle, I love them both, but I guess the ROM will have to go cause I don't like Franco's stuff. Yes I am encrypted, No I don't want to go unencrypted.
[Nexus 6  Original Android Development] mastamoon:
Just had another reboot while watching a video. Guess ill flash back to v2.7. Still no last kernel message to look at.. not sure why.

[MENTION=3357040]Imoseyon[/MENTION]
[Nexus 6  Original Android Development] niko2931:
I have a question, i wanna go back to stock rom, but still want to flash custom kernels ;)

But what if i'd want to switch between custom kernel, what would be the procedure? :)
[Nexus 6  Original Android Development] jkc120:
You just dirty flash the kernel zips to go from one to another. But why you'd flash LK then go to anything else is beyond me :p
[Nexus 6  Original Android Development] niko2931:
It's a just in case question ;)

So i would be able to go from Franco to Elementalx to Lean to Zen kernel?

If it came to that ;)
[Nexus 6  Original Android Development] jkc120:
AFAIK, yes. The only thing to be careful of is if you have kernel settings being done on boot by an app and an option were not compatible with the newer kernel. But I could be wrong, I'm not really a crack flasher anymore :)
[Nexus 6  Original Android Development] Imoseyon:
Those of you running the latest nightly ROMs, give v2.8.4 a shot?

http://renderserver.net/devs/imoseyon/shamu/testbuilds/lk_shamu_lp-v2.8.4.zip

[MENTION=2963287]mastamoon[/MENTION], are you seeing a cold reboot? Or just a hot reboot with the spinning circles only? If cold reboot, grab files from /sys/fs/pstore?

Totally fine to do this but my issue is how they disable mpdecision. If they disable it in the ROM then you're touching stuff outside the kernel and forces folks to dirty flash the ROM when they switch kernels. Most people won't even know to do that and will be wondering why things don't work right after flashing another kernel.
[Nexus 6  Original Android Development] mastamoon:
The one while watching a video was a hot reboot, just back to the boot animation I believe.. but now im second guessing that answer, but I want to say just a hot reboot

I pulled that file, but it looks like a current log, so im assuming whatever was written to it during the crash has been wiped or overwritten. But here it is if you want to take a look. This was a few hours after though fyi.. https://www.dropbox.com/s/877xhhws0nak2el/console-ramoops-0?dl=0

Thanks for the info.. if I have another reboot ill grab this file much sooner. Any reason why your kernel doesnt write out a last kmesg?
[Nexus 6  Original Android Development] bbedward:
I just call stop mpdecision in the init.rc, won't stick after flashing another kernel ;)
[Nexus 6  Original Android Development] Imoseyon:
Somewhere between Linux 3.4 and 3.10, mainline developers deprecated last_kmesg in favor of pstore.

Bingo, that's exactly what you should be doing. :)
[Nexus 6  Original Android Development] mastamoon:
OIC. Is pstore a snapshot like last_kmesg was or is it a rolling log ala dmesg? Is last_kmesg something you wouldnt want to turn on (if its just a kernel buildtime option, or is there more code missing along with the switch turning it on/off)?

Thanks!
[Nexus 6  Original Android Development] omvir:
Not working. System UI crashes. On latest CM nightly..
[Nexus 6  Original Android Development] 530farm:
still Bootlooping w/ 2.8.4 and chroma. FYI
[Nexus 6  Original Android Development] droid fetish:
I had to finally ditch chroma, if they don't want to make it so we can run leankernel then I'm not interested. I inquired about it in the chroma post, and they acted like appleites! "if you run our ROM, you must run our kernel"! No thanks!
[Nexus 6  Original Android Development] papikev:
Well, that's not entirely true. The perspective is that if you run Chroma and install another kernel outside of what it is built with, then don't report issues should you have any. More often than not, it is user error and I believe the developer is just trying to avoid needless headaches. After all I always run Zen flawlessly with Chroma. (No disrespect to lean kernel. Awesome kernel as well :)
[Nexus 6  Original Android Development] rauschkugl:
It's no user error. It's a rom bug.
[Nexus 6  Original Android Development] papikev:
It was just a general statement and most assuredly not addressing your ROM issue since I have no idea what that was or is.
[Nexus 6  Original Android Development] GuyInDogSuit:
No. Every time I flash an update to Chroma I make sure to flash LeanKernel as well, because it stays unencrypted.

That's probably why.
[Nexus 6  Original Android Development] Imoseyon:
You got a PM. I'm guessing others are having this problem on latest CM nightly?
[Nexus 6  Original Android Development] omvir:
Sorry I had notifications off.
[Nexus 6  Original Android Development] Ortanon:
Did anything ever come of this? I'm trying to use a magnetic car mount and I want to pull my hair out.
[Nexus 6  Original Android Development] bradld:
Not anymore. 2.8.5 works great!!
[Nexus 6  Original Android Development] nalrodriguez:
That explains it, i thought the beta ones were the experimental for the min - max frequencies. LOL ooops

Just saw the OCUC in the beta folders too, lol i guess i should go to bed after this .. Thanks
[Nexus 6  Original Android Development] ryude:
I'm glad that it is doing what you want, however, the way it works is exactly as I described. The lower up_threshold is, the more frequently it will use max frequency. The higher it is, the more frequently it uses low frequencies.
[Nexus 6  Original Android Development] simms22:
you are talking conservative governor, not ondemand. i do not ever use conservative. again, look at my screenshots.
[Nexus 6  Original Android Development] Mistertac:
The way I understand it is the way [MENTION=2672440]ryude[/MENTION] has been explaining as well. And from reading here under the OnDemand section not too far down under that parameters description.. That still makes sense.

https://www.kernel.org/doc/Documentation/cpu-freq/governors.txt

Although [MENTION=1811927]simms22[/MENTION] I also see where you're coming from with your logic, so basically... Not sure really lol
[Nexus 6  Original Android Development] ryude:
You are correct.

Also, there are many theories on what is best for battery life. Some believe that Performance is the best, since it allows the task to be completed faster and then the cpu can enter deep sleep more often.

However, the actual definition of up_threshold is not a theory. It's job is simply to define the cpu usage at which the governor will increase clock speed.
[Nexus 6  Original Android Development] simms22:
funny thing, thats trinity kernels(n4, n5, n7) default governor and governor settings. one thing trinity is known for, is not that its slow, its quite the opposite. only thing i can say is try it, set your governor/scheduler to ondemand/deadline, set up threshold to 98, then check out the fequency of your cpu speeds. most will be the lowest, then the highest, then all else in tiny amounts. reset the counter first :)
[Nexus 6  Original Android Development] wrinklefree:
This kernel is solid enough for daily driving. If we can only get color control my life would be complete :)
[Nexus 6  Original Android Development] hsj1906:
Aside from these changes, have you made any other changes? And are you running the OC beta 5 or just the regular beta 5?
[Nexus 6  Original Android Development] ryude:
I'm running beta 5 ocuc. Mpdecision off, minspeed 223Mhz, maxspeed 2.265Ghz, undervolt -25, noop i/o scheduler, and that's pretty much it for kernel tweaks.
[Nexus 6  Original Android Development] Imoseyon:
LOL. Today i flashed the stock kernel just to test a few things and forgot about the whole encryption thing, so as soon as it booted it encrypted userdata. Rookie mistake. The whole nandroid backup and restore thing is such a pain when you're formatting data/sdcard.

Anyway, I put up the stock kernel in the main download folder - just remember what to expect if you're decrypted. :)

Thanksgiving weekend is over, and I'm back at work so I'll have less time to work on kernels (at least until the weekend). I plan on coming out of beta by the weekend. Thanks so much for testing everyone.

As for color control - it's definitely near the top of the list. I wanted to look at it over the thanksgiving weekend but I ended up spending most of my time on governors, mpdecision and such.
[Nexus 6  Original Android Development] Steve Lazarus:
^

This would be outstanding :thumbup:

Sent from my Slim Nexus 6
[Nexus 6  Original Android Development] natezire71:
I'm a tad confused.

I just wanted to flash the base leanKernel. I don't care for setting custom frequencies. (I'm trying to take a different approach with Lollipop and let it do it's thing). I want the version of leanKernel that is as close to stock as possible.

Which one is that?
[Nexus 6  Original Android Development] old_fart:
Beta 5
[Nexus 6  Original Android Development] natezire71:
Well, yeah. But there are two versions and something to do with disabling mdpdecision.
[Nexus 6  Original Android Development] Mistertac:
You want the Beta 5 version, not the beta 5 with OC/UC. And if you want it as close to stock as possible don't worry about the mpdecision file either.
[Nexus 6  Original Android Development] natezire71:
Awesome! Thank you.

---------- Post added at 01:53 PM ---------- Previous post was at 01:44 PM ----------

One more thing. I'm currently using the decrypted stock kernel (I flashed the image).

I want to remain decrypted, so this kernel will be fine. However, how do I flash this properly? I want to stay on the stock ROM and use this kernel; do I just flash in TWRP and wipe cache?
[Nexus 6  Original Android Development] simms22:
just flash it, dont wipe a single thing. when you flash a rom, dalvik and cache automatically get wiped. and for flashing kernels, dalvik and cache have absolutely nothing to do with kernels, so never needs to be wiped.
[Nexus 6  Original Android Development] Mistertac:
If you're already decrypted then you're golden, just flash in recovery and that's it. No real need to wipe cache or anything just flash and go.
[Nexus 6  Original Android Development] natezire71:
Really? Whenever I flashed kernels on my Galaxy Nexus, I was always told to wipe dalvik and cache.

Obviously, there is no more dalvik cache in Android Lollipop, so that's pointless to wipe.

I appreciate the help! I haven't flashed stuff in over a year since I had a MotoX (locked bootloader) to tie me over until the next Nexus. Got rusty.
[Nexus 6  Original Android Development] Mistertac:
I think some kernels like KToonsez kernel for Galaxy S4 and S5 the Dev requested you wipe cache because he bundled his kernel with his own kernel tweaking app. And some would run into minor issues if they forgot to wipe caches.... Anyways I think this is maybe why a lot of people think they must wipe caches with every kernel they flash. Just my guess.
[Nexus 6  Original Android Development] PhilDX:
yeah, I bought a new case without a magnet, very happy with it :)
[Nexus 6  Original Android Development] Imoseyon:
So you're on CM12 5/14 nightly or newer and 2.8.5 does not cause systemUI crashes?
[Nexus 6  Original Android Development] bradld:
20150516 and 2.8.5, no problems yet.....
[Nexus 6  Original Android Development] Darian71:
I flashed 2.8.5 this morning running 05/13/15 Liquid Smooth 4.1 AOSP based and have no issue with system UI Fc's or crashes. Seems to be doing fine. I did notice however in my Kernel Auditor, even on Performance governor, only 3 cores are kept at the 2265MHz.(where in the past versions of LK all 4 were kept at that MHz on performance governor) Can't seem to even get core 4 online. Gonna test today and see how it goes. Great work again sir! ??
[Nexus 6  Original Android Development] Darian71:
ScreenShot
[Nexus 6  Original Android Development] Darian71:
Update : After running LK 2.8.5 a few hours I went back into my Kernel Auditor and tried to check core 4 and this time it come online and is working almost in unity with core 2. 1 and 3 seem to work about the same as well.
[Nexus 6  Original Android Development] Darian71:
Man! This Kernel is something else Bro!! Ran a couple AnTuTu Benchmarks. First with InteractiveX at 2265MHz. (First pic) 2nd Pic and test done at Max MHz setting with Performance Governor. Not only did it blow away every other device, but the core CPU temp wasn't even warm enough to feel! (3rd pic) Thoroughly impressed with 2.8.5!!
[Nexus 6  Original Android Development] Imoseyon:
That's most likely your thermal engine trying to cool down the phone. Should be normal.
[Nexus 6  Original Android Development] Darian71:
I'm sure you're right. The last temp check on all 4 was immediately after running the benchmark. I watched it and within 5 seconds it had cooled to 115°F. That never happened on the stock kernel on this version of LS 4.1. Currently running 96.0F /35.0C with normal use.
[Nexus 6  Original Android Development] LordDeath:
Same here. I am on the 5/17 nightly and I have no SystemUI crashes with 2.8.5. :)

Did anyone else notice a strange behavior with the clock scaling after rebooting the phone while it is connected to a charger?

According to my observation CPU 4 stays offline all the time while the other cores are scaling normally. As soon as the battery is fully charged and after that when I unplug the phone only CPU 1 scales its clock dynamically down to 300 MHz. The other three cores remain at the full 2.6 GHz clock all the time.

The only way to get back the to normal behavior (all cores are always online, dynamically scaling) is to reboot the phone while it is not connected to a charger.
[Nexus 6  Original Android Development] MeestaAytch:
Wow... That's all I have to say about this kernel. I've been plagued with the frozen split screen issue on my device for the longest but endured it because I totally felt it had to be software related... I came across on Google today that your kernel fixed it...sure enough after flashing it I am unable to recreate it. Thanks man. I did read in earlier pages you have no idea which commit it would be and finding it is a needle in a haystack but dang. It works perfect now so IDC I'm happy.
[Nexus 6  Original Android Development] xpdragon:
Where can I download 2.8.5 or latest version? I saw zip file 2.8, but not sure it is 2.8.5. Thanks.
[Nexus 6  Original Android Development] Tylog:
Klick in the OP on main download, then go to test Folder
[Nexus 6  Original Android Development] xpdragon:
I got systemUI crashes with 2.8.6 on CM12.1 build 5/18.
[Nexus 6  Original Android Development] Imoseyon:
Yup this is a known problem still. For some reason this doesn't happen to everyone - just some. I will fix this.
[Nexus 6  Original Android Development] Darian71:
LK 2.86t1 wouldn't boot for me on my XT1103. It made it passed the Google splash screen, then the AT&T logo splash, but hung in the circling colors. Finally booted to Recovery, wiped cache and dalvik then flashed 2.8.6 and all is well. No crashes or Fc's so far. Will test all day tomorrow and report back. (Running Liquid Smooth 5.1 5/18 nightly.) Thanks!
[Nexus 6  Original Android Development] xtzz:
I can confirm the nightly from 5/21 works okay with LK 2.8.6t1.
[Nexus 6  Original Android Development] Darian71:
Which Rom? I'm using Liquid Smooth 5/18. Their latest.
[Nexus 6  Original Android Development] xtzz:
CM12.1 nightly for Nexus 6.
[Nexus 6  Original Android Development] Imoseyon:
Those of you still having system UI issues try v2.8.6t2 (not t1): http://renderserver.net/devs/imoseyon/shamu/testbuilds/lk_shamu_lp-v2.8.6t2.zip
[Nexus 6  Original Android Development] tapalief:
aicp_shamu_lp-9.0-NIGHTLY-20150520 for me.

No system UI issues and very good performances.

Thanks a lot !!!
[Nexus 6  Original Android Development] apascual89:
I hope you're enjoying your Memorial day weekend! Do you mind telling us common folks how you fixed the system ui fc! [emoji2]
[Nexus 6  Original Android Development] Tylog:
Edit: I like ignorance.
[Nexus 6  Original Android Development] Imoseyon:
Is it fixed with 2.8.6t2 on latest CM nightly? No more systemui FC?
[Nexus 6  Original Android Development] Typis:
T2 works

im using 2.8.6t2 with cm-12.1-20150523-NIGHTLY-shamu.zip currently with no real issues.

settings crashed once on first boot in place of systemui, no idea if that was caused by cm rom itself, or the gapps package i used (Delta Gapps 22.05 for 5.1), or the kernel and since it only crashed once on first boot and never again i didnt really bother looking into it..

i also used the past few nightlies with t2 with no systemui crash looping or any issues other than the same settings crash on first boot.

i never actually tried t1 but earlier versions were giving me systemui crash loops at 13.05 and newer cm12.1 nightlies, thought id share this aswell since im not sure if someone said it didnt affect everyone.

currently also using xposed framework for 5.1 with no issues aswell, mainly for youtube adaway i guess.

not sure if ur interested but i noticed that cm12.1 performance profile would lock cpu frequency at like 1.9ghz for some reason, but i didnt really look into that either since i dont usually keep the "auto performance profile for apps" setting enabled in the end, atleast not when using a kernel that wasnt part of the rom

just throwing that out incase someone wants to actually try and see if it truly is happening or if whatever i was using for seeing max frequency at the time lied, or if it was just affected by my cpu temperature or battery level, tho it went back up on "balanced". i was messing around with antutu seeing if anything changed there over time

im pretty sure i also enabled the option in lkconfig that says it prevents the lowering of maxfreq, to see if hat would make a difference.

but is that mainly related to temperatures lowering maxfreq after a certain point, or should it also prevent lowering maxfreq at low battery?

anyway, the maxfreq stuff didnt really bother me so i didnt run proper tests (not gaming on the phone atm)

just reporting whatever crossed my mind since i bothered logging in
[Nexus 6  Original Android Development] apascual89:
Yes it is.
[Nexus 6  Original Android Development] Imoseyon:
Nice I had to do some ramdisk init hackery to make it compatible with both stock and cm.
[Nexus 6  Original Android Development] lainemac:
Hey imo, any kernel changes in the 5.1.1. That just dropped?
[Nexus 6  Original Android Development] Danvdh:
yes there will be

1) T-mo wifi calling needs something in the ramdisk I believe

2) The kernel causes the "Android is upgrading" optimizations on every reboot
[Nexus 6  Original Android Development] r1ndr3w:
lk 2.9rc1

Seems like this build does an optimization on every boot.

EDIT: Happens on AOSP ROMs. Doesn't happen on CM12.1 ROMs but reboots right after initial boot and is ok.

Does this even make sense?
[Nexus 6  Original Android Development] riqdiq:
I had this issue on my Nexus 6 running CM 12.1 (latest nightlies 5/25) but the latest test build fixed it for me, thank you!
[Nexus 6  Original Android Development] paroulis:
Hi. In lkconfig script I see that has three fixed values ​​for temperature adjustment of colors. How can I put my own values ​​?
[Nexus 6  Original Android Development] jkc120:
There's an option for simple with those 3, and the advanced one lets you set rgb and saturation, hue and contrast for full gamma control. Or you can use an app to adjust them.
[Nexus 6  Original Android Development] lainemac:
Optimization happening for me as well on stock LYZ28E 5.1.1
[Nexus 6  Original Android Development] jkc120:
Weird, so 5.1.1 re-optimizes on every boot, even with a completely stock device? Or is it the combination of 5.1.1 and 3rd party kernels? I hope that's not done on purpose on Google's part, that would mean a significant battery drop and wait every time the phone reboots.
[Nexus 6  Original Android Development] Smallsmx3:
Battery drop? Your rebooting your phone that much? Don't get me wrong I flash allot of stuff but usually when I'm home and connected to a charger
[Nexus 6  Original Android Development] jkc120:
No, I'm not rebooting that often. However, depending on how many apps people have, it consumes quite a bit of both time and battery to rebuild/optimize things, and there's no need to do it so not only is it redundant but wasteful. So I am hoping it's a bug.
[Nexus 6  Original Android Development] natezire71:
Early reports would suggest that flashing any custom kernel breaks wifi calling in 5.1.1 for T-Mobile. I have T-Mobile, but am holding off on 5.1.1 until issues get sorted out.
[Nexus 6  Original Android Development] jkc120:
The question is whether there are some binary blobs or other things that would prevent using a custom kernel. Do you know for other devices that support T-mobile wifi calling, is it possible to have a 3rd party kernel? I'm not on T-Mobile, but I'm hoping you Tmo folks don't have to choose between an awesome kernel like Lean Kernel and wifi calling :/
[Nexus 6  Original Android Development] natezire71:
I wouldn't know about other devices; however, I assume most of the other devices that do support it are typically locked down by the manufacturer.
[Nexus 6  Original Android Development] jkc120:
Well yeah, I'm talking about devices that either have an unlockable bootloader or have had exploits to allow flashing a custom recovery, kernel, etc.
[Nexus 6  Original Android Development] lainemac:
No I meant stock rom and this kernel.