yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] flyinj54:
I'm pretty sure when you're plugged in the computer the phone saying charging over USB is completely normal because that's exactly what it's doing. I don't think you have any issue whatsoever and they believe everything is acting as it should.
[Nexus 6  Original Android Development] Zaf9670:
He's the Walter White of kernels.
[Nexus 6  Original Android Development] redsmith:
Funny thing, I just found out that while the phone is off, charging it will make the LED glow red. Is that expected behavior? It looks beautiful.
[Nexus 6  Original Android Development] GPS3:
Nice! I will have to try that out.
[Nexus 6  Original Android Development] old_fart:
And I think some stuff got tweaked / patched last week cuz lightflow "NOW" lights up a small green light when gmail sends me something. Hasn't till now worked for me on the N6. . Always had it working on the N5, but it was running 4.4.4 !

It's the small things, like a itty bitty tiny little green light that makes you happy and feel you're getting your money's worth on a $700 phone / toy . . .
[Nexus 6  Original Android Development] Langduscher:
Phone shuts down when battery drops below 10%. Feature or..?
[Nexus 6  Original Android Development] jjhiza:
No. Do you have battery saver enabled? Idk, but that, combined with bad UV settings might cause issues.
[Nexus 6  Original Android Development] Langduscher:
I flash-n-forget. No UV, no batterysaving. Doesnt happen on FK.
[Nexus 6  Original Android Development] Smallsmx3:
Battery saver is a Lollipop feature, not an independent feature of a kernel

It kicks in when you're battery is below a certain percent
[Nexus 6  Original Android Development] Imoseyon:
v1.6 is up: https://github.com/imoseyon/leanKernel-shamu/wiki/Lollipop-ChangeLog

Includes some fixes and enhancements for the display driver. Hopefully display driver will run smoother and more efficient than previous versions (and stock).
[Nexus 6  Original Android Development] HTC_Phone:
Weird reaction... After installing 1.6, my phone would boot up and sit on my homescreen for 4-5 seconds, and then randomly reboot.
[Nexus 6  Original Android Development] Imoseyon:
That is... not a good reaction. lol. Does it continue to happen after reboot? Also does it go away if you flash v1.5.?
[Nexus 6  Original Android Development] HTC_Phone:
Yes, and yes. It did it 5 times in a row until I managed to boot it into recovery during a reboot and flashed a different kernel.
[Nexus 6  Original Android Development] Imoseyon:
Hmm i wonder if you're running into a strange reaction with a previous kernel you had installed on it. Anyway, if others are having this issue let me know.
[Nexus 6  Original Android Development] oak:
1.6 running fine here on stock rom. No negative issues whatsoever.
[Nexus 6  Original Android Development] Pilz:
I came from 1.5ucoc and 1.6ucoc is running just fine here. So I have to flash the custom mpdecision for each new update? I do or anyway but I'm curious.

Edit

Also where can we change the vibration strength for dt2w and s2w?
[Nexus 6  Original Android Development] HTC_Phone:
Not sure what did it... But we're all good now! Great work.
[Nexus 6  Original Android Development] lainemac:
No issues here. Using 1.6 with cm12
[Nexus 6  Original Android Development] vergilbt:
Hi guys, is in this kernel an option to change strength of vibration (eg by trickster mod)?

Thanks in advance
[Nexus 6  Original Android Development] Nalix:
Can you (or someone else) explain to me why I need the mpdecision patch? I'm all lost and confused about this ocuc kernel, mpdecision patch, CPU boost and min/max frequencies. If I patch ocuc kernel without the mpdecision patch - will I have the ocuc kernels default min/max frequencies? Is the mpdecision patch only needed when I want to customize the min/max frequencies further than the ocuc kernel does per default? Should I have CPU boost enabled with ocuc kernel?
[Nexus 6  Original Android Development] mclisme:
Excuse my ignorance but when I enter:

root@shamu:/ # cat /proc/cpu/msm_acpu_pvs

the result is:

2root@shamu:/ #

Is that "2" in front of the command prompt my PVS value and how bad is it considering 0 equals returning it and 15 being the best? I expected something around 7, kinda worried now... :rolleyes:
[Nexus 6  Original Android Development] oak:
Yes, it's 2. Same as mine and my device is awesome. I don't sweat it a bit.
[Nexus 6  Original Android Development] Pilz:
You don't need it necessarily. I use it because I like to set my frequencies a certain way and some times without the fix it won't stick. The custom mpdecision patch allows you to set the frequencies without having them revert back to what the kernel wants them to be. (Its call make poor decision for a reason)
[Nexus 6  Original Android Development] old_fart:
And just to add . . I read 'somewhere' that if you use the 'over-clock, under-clock' version of the kernel, then you're supposed to turn "OFF" the cpu boost. . . So the bottom line is that the small changes is a psychological thing, which is alright ! ! ! . . It's a segway to bragging right. . . Most everyone like to do that.

.

And I must admit that I thought that the changelog entry - 'fix watchdog bark issue' was a joke. . . But I googled it and there was a ton of hits - something to do with stopping the re-booting.
[Nexus 6  Original Android Development] Pilz:
Yeah I think my CPU boost is off by default because I'm running elemental X currently. I'll double check but I usually make sure its off. We all have those little things that we do subconsciously :)
[Nexus 6  Original Android Development] GPS3:
If I understand correctly, the mpdecision patch allows you to push the minimum & maximum frequencies beyond the kernel's defaults.

Stable/stock default minimum is ~1.4ghz (if I remember correctly); maximum is ~2.6ghz.

OCUC default minimum is 223mhz; maximum is ~2.9ghz.

If you are happy with those frequencies, no need for mpdecision patch. If you want to adjust the frequencies, you need mpdecision patch.

CPU boost: http://xdaforums.com/showpost.php?p=57215289&postcount=535
[Nexus 6  Original Android Development] Imoseyon:
I realize the FAQ entry probably isn't detailed enough but here's a copy and paste from post #2:

I can't seem to get min and max freq to stick! What are these mpdecision zip files in the util directory?

This is actually by design of mpdecision. If you want this behavior to change, I recommend that you 1) flash latest stable leankernel, 2) flash the custom no-freq mpdecision, and then 3) disable cpu-boost via lkconfig. Do not disable mpdecision if you go this route. Also, if you flash ROM, you must re-flash custom mpdecision. To go back to normal, flash the stock mpdecision file.

---

Basically the custom mpdecision disables its ability to set max and min frequencies, allowing users to set those (otherwise stock mpdecision will mess with them).
[Nexus 6  Original Android Development] Smallsmx3:
Like the new update.... All good on this end. What is the camera update all about?
[Nexus 6  Original Android Development] datajosh:
Any chance you'll add the adjustable vibration strength that flar2 and Franco have added to their kernels? I keep going back and forth between your kernel and Franco's, but that stock vibration setting kills me :laugh:
[Nexus 6  Original Android Development] GPS3:
Loving the stability.

My best score so far.

Stock 5.0.1

LK 1.6ocuc
[Nexus 6  Original Android Development] Imoseyon:
I'll add to my todo list. Stock vibe strength hasn't bothered me at all but maybe there's a case to make it adjustable.

The camera code updates so far have been to deal with edge case bugs - you really shouldn't notice any difference, IMO.
[Nexus 6  Original Android Development] Smallsmx3:
The only time vibration strength bugs me is when my wife sits next to me on the couch. It drives her nuts which means she drives me nuts. Can you add something to lower her whining?
[Nexus 6  Original Android Development] JManekia:
I am unable to get the settings from lkconfig to stick. They don't persist after reboot.
[Nexus 6  Original Android Development] Cy_n_ic:
Read back till you find my post with the attachment.

Via A Rooted Glade PlugIns
[Nexus 6  Original Android Development] mzimand:
1.6 running great on Verizon with CleanRom. I have tried several other kernels but prefer LK.

My LTE came up immediately after first reboot.
[Nexus 6  Original Android Development] strikerdj2011:
been using elementelx kernel but fancied a change flashed this one but got stuck on google logo do i nee to flash stock kernel 1st before i flash this one ? :)
[Nexus 6  Original Android Development] demonsgalore:
Is it flashable over the TWRP recovery? TWRP getting an zip error while trying to install. Can somebody tell me how to flash it please?
[Nexus 6  Original Android Development] lainemac:
I always use twrp. Probably a bad download. Try downloading again.
[Nexus 6  Original Android Development] Imoseyon:
This is odd. I imagine it's something to do with the elementalx kernel. My kernel should be completely safe to flash on top of stock.
[Nexus 6  Original Android Development] pantmunu:
Flashed elemental on top of yours and no such issues. Then flashed Franco's and still no such issue. And flashed lean on top of Franco and I'm still fine.

Today was a good day.
[Nexus 6  Original Android Development] strikerdj2011:
dirty flashed my rom and now works great cheers
[Nexus 6  Original Android Development] Imoseyon:
LOL
[Nexus 6  Original Android Development] Pilz:
Have you thought about adding s2s? Those are two of my favorite things about Elemental X but I still prefer LK because it runs better in my experience. I can't run Elemental at 2.8 without crashes (on antutu) even st the same voltages that I use for LK. Keep up the great work :D

Edit: I meant s2s not s2w because that's already here :)
[Nexus 6  Original Android Development] DroidOnRoids:
I doubt he will. As said in the OP, this kernel strives to be minimal that's targeted towards selected users - Hence the name, minimalistic kernel.

In other news, just received the Shamu and haven't touched or installed LK since the Toro. About to flash for the first time! Thanks Imo!

EDIT: Derp.
[Nexus 6  Original Android Development] Pilz:
It does has some small things added in already (s2w and dt2w with haptic) so that's why I asked. I still love this kernel hands down the best for use as a DD.
[Nexus 6  Original Android Development] DroidOnRoids:
True true. I normally don't use all those gestures anyways. But since the Shamu is so big, dt2w is the only useful feature for me so any more gestures would be bloat in my book lol
[Nexus 6  Original Android Development] ScumDroid:
Hey guys, I know this is likely nothing to do with the kernel, but my wifi is shutting itself off after long periods of time (like 8 hours maybe). Its not anything in the settings i checked battery saver, and wifi advanced settings. Anyone have any ideas as to what could be causing this? Everything else is 100%. (Stock w/leankenel)
[Nexus 6  Original Android Development] Imoseyon:
Actually s2s support is enabled in the kernel, just not supported within lkconfig. You should be able to use an app like trickster or write your own init.d script.
[Nexus 6  Original Android Development] Pilz:
Thank you for the response :) I tried using trickster to enable it but it didn't do anything. If enabled which way to do swipe the nav bar?
[Nexus 6  Original Android Development] old_fart:
There is some automatic things in lollipop, like : https://support.google.com/nexus/answer/6090612?hl=en
[Nexus 6  Original Android Development] PhilDX:
if it makes you fell any better, i've been trying to figure out how to use sleep2sleep too...

Based on flar2's post here, i tried enabling sweep2sleep in terminal emulator as follows:

echo 3 > /sys/android_touch/sweep2sleep

i've tried all sorts of swipe motions across the navbar but i haven't been able to get the phone to sleep. i have successfully enabled dt2w and sleep2wake in a similar fashion so i dunno what i'm doing wrong.

BTW, [MENTION=2942485]Cy_n_ic[/MENTION] posted an awesome init.d template in this post, just follow the included instructions and modify to your liking and the selected features will be enabled on reboot.
[Nexus 6  Original Android Development] Pilz:
Did that work for you? It didn't work for me when I tried it.
[Nexus 6  Original Android Development] Imoseyon:
If anyone's in testing mood, v1.6.9 in the testbuild folder (https://onedrive.live.com/?cid=F1ED4BADFEE3FC02&id=F1ED4BADFEE3FC02!440) has vibe strength control. (Use Trickster to control). There are other optimizations and updates in there as well - if things blow up let me know. :)

Vibe strength control is my own implementation so may need some testing.
[Nexus 6  Original Android Development] Cy_n_ic:
Sweep2sleep works across the navigation bar. It can be left to right, right to left, or both if you so desire. It can be touchy so you gotta do it just right till you train yourself. But i just tested it and it does work in both directions.

Via A Rooted Glade PlugIns
[Nexus 6  Original Android Development] PhilDX:
yup, I was sweeping too fast... i have it working now but some more finger training will be required for consistency.

---------- Post added at 04:04 PM ---------- Previous post was at 04:02 PM ----------

yeah, both sweep2sleep across the navbar (when I swipe slow enough) and enabling at boot via the unit.d script (I had to create the unit.d directory since it didn't exist).
[Nexus 6  Original Android Development] Pilz:
I'll give it another go. What do you name your folder that the script was in? Could you post some screenshots of how you did it? I just want to double check what I have right now.

Also how hard would it be to merge flar2's commits into this kernel if I wanted to do it? I know some C/C++ but I've never tried to mess with a kernel before. I just think it would be a fun thing to try.
[Nexus 6  Original Android Development] prbpci0:
I can't find the setting within Trickster: can you point me in the right direction? SysCtrl Editor somewhere? Thanks!
[Nexus 6  Original Android Development] Imoseyon:
Hmm I see it under "Specifics" - "Vibrator Strength". On command line, you can adjust via /sys/vibrator/pwmvalue
[Nexus 6  Original Android Development] PhilDX:
oh dude, sorry but I can't code, I leave that to the professionals... besides, [MENTION=3357040]Imoseyon[/MENTION] already did it :)

just extract and place the file in the zip linked earlier in /system/etc/init.d. if the init.d folder doesn't exist, create it. set permissions like the other files and folders there and reboot.

don't forget to enable the options in the file the way you want, instructions are in post #2 in flar2's thread I linked.

here is an example:

#!/system/bin/sh

#

echo 5 >/sys/android_touch/sweep2wake

#

echo 3 >/sys/android_touch/sweep2sleep

#

echo 1 >/sys/android_touch/doubletap2wake
[Nexus 6  Original Android Development] prbpci0:
Ah, my fault. I was looking for it *before* I updated to 1.6.9. Updated, and it's there now (duh!). Thanks!
[Nexus 6  Original Android Development] Pilz:
I appreciate it, I like to try new things and possible break my phone by being dumb because its good learning experience.
[Nexus 6  Original Android Development] icon123:
When I tried to use this method, I got dt2w to work but s2s only seems to work from right to left even though I picked (3) both.
[Nexus 6  Original Android Development] prbpci0:
I tried a really low vibration setting (40) and a reasonable one (100) (the scale is 1-127). Both worked well. I think I'll leave it at 100 (the default on the current Franco kernel). Thanks for this! Great work as always.
[Nexus 6  Original Android Development] Imoseyon:
v1.7 is up: https://github.com/imoseyon/leanKernel-shamu/wiki/Lollipop-ChangeLog

This is a big update. A lot of the driver/soc fixes and optimizations from Codeaurora are fully adapted for shamu, and mostly up-to-date with the latest from CAF. What this means is that your phone should run smoother, be more stable, and more power efficient.

Vibe control is my own implementation and is compatible with Trickster. I will modify lkconfig (in 1.8) to be able to configure it though. I also fixed wakelocks output from lkconfig for the results to be more compatible with apps like GSam, etc.
[Nexus 6  Original Android Development] EvoRocker:
Is this kernel noticeably better than stock if I just flash and don't tweak it? Just feeling lazy these days lol running latest Clean Rom.
[Nexus 6  Original Android Development] tysonwald:
flashed and testing now
[Nexus 6  Original Android Development] Smallsmx3:
So [MENTION=1050103]sykopompos[/MENTION] has found an issue with the CPU not scaling properly during some games. Any chances of adding his fix to your kernel if you haven't already done so?
[Nexus 6  Original Android Development] Imoseyon:
CPU frequency scaling is a function of your cpufreq governor (kernel), mpdecision (rom), and thermal-engine (rom). I've yet to see any scaling issues with leanKernel and stock ROM. Granted the only two games I play are Darkness Reborn and Words with Friends. :) I will keep an eye on it though.

I think so. :D The nice thing about leankernel is that it's a drop in replacement for stock. Give it a shot, flash it, run it for a couple of days. If you don't like it flash stock kernel and you'll be back to where you were two days ago.
[Nexus 6  Original Android Development] shelooga:
Words eh? PartyNakedAlaDroid will give you a good run
[Nexus 6  Original Android Development] lainemac:
Ok sorry for the n00b questions, but I'm a little confused about the mpdecision zips. Do you guys recommended flashing the patched version?
[Nexus 6  Original Android Development] darshilshah87:
Few Quetions (Noob User)

1.I flashed Cyanogenmod 12 recently. Will this kernel work with it?

2.If it works i want to max battery life as possible by tweaking the cpu .. can some please teach me how to tweak it without messing up my phone system.
[Nexus 6  Original Android Development] lainemac:
It does work with cm12. As far as battery life goes, this kernel is more of a flash and forget type kernel.

---------- Post added at 03:04 PM ---------- Previous post was at 03:00 PM ----------

Imoseyon are you running this using the stock rom?
[Nexus 6  Original Android Development] Imoseyon:
hehe one of these days i'm going to rewrite this entry in the FAQ. Could you take a look at question #1 on the FAQ section (post #2) first? I know it's probably not written very well.

Yup, as a kernel dev, you pretty much have to run stock to guarantee that your modifications are at least compatible with stock. Unless you have multiple devices. :)
[Nexus 6  Original Android Development] jackpollard:
If your tweaking for battery life, try it for a few days before doing anything, its that good as a drop in. When I first got the N6 the battery life really concerned me. After using Lean since its been out, I don't even think about it anymore. I also use Greenify, keep off location services unless I need it and keep off unnecessary syncs.
[Nexus 6  Original Android Development] :
The post isn't very clear on the benefits of flashing the patched mpdecision(at least for me). Does it offer better performance, better battery life? Do you use it? Or just flash your kernel and let it be
[Nexus 6  Original Android Development] wrongway213:
Mpdecision stops your min and max frequencies you set from sticking. It basically forces stock behavior on this lovely custom kernel.. Flashing no freq mpdecison stops that from happening. Mpdecision is awful IMO.
[Nexus 6  Original Android Development] rebretz000:
Thank you. I hate it also.

Sent from my Moto Nexus 6
[Nexus 6  Original Android Development] Damon13:
If I flash LK V1.7 OCUC then I must flash no freq mpdecision along with it? If I decide on the LK v1.7 then there is no need to, I just want to let it be and not do much tweaking.
[Nexus 6  Original Android Development] wrongway213:
no freq mpdecision isn't something that's gonna require a bunch of tweaking.. it will simply allow you to tweak, change your min and max frequencies and make them stick without mpdecison resetting them.
[Nexus 6  Original Android Development] Imoseyon:
custom mpdecision

(I think i wrote a similar post or two in this thread already but what the heck, I'll link this one to the FAQ)

If you're like a lot of people and want to flash leanKernel without having to tweak anything, then you don't need to mess with mpdecision. Just flash the latest stable leanKernel and you do not need to read further.

There are three main use cases for flashing custom (nofreq) mpdecision when running leanKernel:

1) You want to set your minimum frequency higher than kernel default, and/or if you want to set your maximum frequency lower than kernel default. Without flashing nofreq mpdecision, stock mpdecision will eventually reset these back to kernel default.

2) You don't need #1 above but you're kinda obsessive compulsive :p and bothered by your favorite cpu control app (kernel tweaker, trickstermod, etc.) showing something like 1.4Ghz has your minimum frequency. These apps are not showing your true minimum frequency - they're simply showing the temporary minimum frequency set by mpdecision (or cpu-boost, more on this later) when launching the app.

3) For whatever reason you think that mpdecision is doing a poor job in scaling your cpu frequencies. Believe it or not, Google put it in there after extensive testing because they felt that mpdecision aids in usability and increases user-perceived performance of the OS (mostly UI performance). You'd rather stick to kernel governor scaling your CPU alone rather than something in userspace messing with it (ie. mpdecision).

If you fall into one or more of the above categories and want the benefits of the nofreq mpdecision, you need to do two things:

1) Flash the nofreq mpdecision from recovery, and

2) Go into lkconfig and disable cpu-boost, which is a kernel feature which will also mess with your min/max frequency settings.

Going back to stock configuration is simple, flash stock mpdecision and re-enable cpu-boost. Also, if you want to to stay on nofreq mpdecision, you must flash it every time you upgrade your ROM, as mpdecision is part of the ROM.
[Nexus 6  Original Android Development] Silentsoul:
Short feedback. 1.7 runs snappier than ever. Will talk about battery later, but it feels fantastic on broken 1.1 build. Thanks!
[Nexus 6  Original Android Development] Imoseyon:
I've also been hearing from other users that v1.7 is the best so far. Thanks.
[Nexus 6  Original Android Development] linuxares:
I don't know what voodoo you manage to do but man the phone is snappier and uses a lot less battery. Normally I'm on 70% by now. I'm still on 78% and I used it even more than I used to in the morning.

Great work and thanks for the kernel :D
[Nexus 6  Original Android Development] sykopompos:
It is issue with selinux letting it play right with it and actually causing random behavior like sticking on one core and running everything on one core and not letting the app/game use the other cores (yes I noticed it on your kernel too)

The problem is that when contexts are set, the CPU gets thrown into the sysfs instead of sysfs_cpu context which is what the system is supposed to set it as but doesn't. This just tells it to resotecon those files so the rest of the system can properly interact with it.

This same fix is in place on the n5, n4, n9, n10 and n7. The only one that did not have it was the n6 and it was probably just missed
[Nexus 6  Original Android Development] rebretz000:
I fall into #2, OCD and bothered by what is shows. Used T.E. for the first time to disable CPU boost. First day it does seem to run better.
[Nexus 6  Original Android Development] ZiggSVO:
So how do you run your own device :p

Sent from my Nexus 6