yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] PeenX2:
Just wanted to do my own little review of this Kernel. I've always been a fan of tweaking PC's etc, and have dabbled in phones a bit too. I try not to get too carried away since I need my phone to work.

But anyways, I've tried a few ROM's and decided the Pure Shamu 3.97 is best for me.

I've tried Franco's Kernels up to R10 w/purchased app

ElementalX up to v22 w/purchased app (also OC'ed and stock)

SenseiR52 w/purchased Tweaker

LK1.9 w/oc w/purchased Tweaker and terminal emulator

I even tried all of these with fresh ROM wipes etc, and I've found Lean Kernel to be the best overall performance and battery life so far.

FrancoKernel) Franco's was good battery life, but benchmarking scores are much lower then everyone elses? Tried messing around with paid app...and still low no matter what I tried.

ElementalX) I get really bad battery life, seems to not want to enter deep sleep. Also, would crash at 2.88ghz no matter what even with same voltage as Lean Kernel OC settings.

Sensei) was the same thing, OC'ed too much and would crash on every bench

LeanKernel) By far the highest consistent bench scores, even with 2.88ghz , with what seems like the same battery life as Franco's. Enters Deep sleep within 10s of screen being off which is nice!

I would like LeanKernel much better with a little more control. And I don't mean an app, but just a few more options. For example it would be nice to be able to disable Fsync. And maybe be able to change from stock 2.65ghz up to 2.88ghz in same kernel.

---------- Post added at 10:09 PM ---------- Previous post was at 10:05 PM ----------

And since I can't seem to edit my post, there is one thing that I noticed with all the custom ROM's and Kernels. After some hard resets, my cell network can randomly change from MetroPCS LTE, T-Mobile LTE and V6....it's kind of all over the place.

But anywas, just realized this was my first post and I signed up in 2010 :o
[Nexus 6  Original Android Development] jackpollard:
If your encrypted it will leave you encrypted, if your not encrypted, it will leave you not encrypted.
[Nexus 6  Original Android Development] flyinj54:
In order to unencrypt you will have to flash lean kernel and format data. You will lose EVERYTHING included sdcard contents keep that in mind. I used fastboot to do mine so I'm assuming this method should work. I remember flashing an unencrypted stock kernel using fastboot then formatted data using fastboot but I think using twrp format data should work correct me if I'm wrong.

This is the method I used below.

http://xdaforums.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
[Nexus 6  Original Android Development] Imoseyon:
As for the smb135x_wake wakelocks, it's actually in part of the kernel i'm not too familiar with. It looks like kernel holds that wakelock when battery driver is waiting for APSD (automatic power source detection) work to complete. Disabling this wakelock altogether could severely delay power detection, but let me experiment with that a little bit.
[Nexus 6  Original Android Development] tom.lockhart:
Thanks!

In what order did you go? Did you remove encryption and then flash lean or vice versa? I will be using the toolkit as this is the first time I've done anything like this.
[Nexus 6  Original Android Development] beyeond:
No, I don't. Matter of fact I don't sync anything at all. I don't even use Facebook notifications or anything.

Thanks for looking into it Imo. It's showing as the top wake lock but I really don't pay much attention to that stuff usually. I unplugged at 8am est and I'm at 71% right now after my normal usage so I don't get too concerned with wake locks. I just happened to be messing with lkconfig and thought I'd take a look.

I am still getting a slight delay when pressing power to wake up the screen occasionally. No idea why.. It started with 1.9, but also coincides with when I enabled power save so maybe that might be why.

Again, not too concerned about it. Very happy with the kernel.
[Nexus 6  Original Android Development] adrman:
Imoseyon, sorry to go ot. A USB otg and twrp can make life much easier. Do a nandroid with twrp, then copy your entire sdcard to a USB otg. Once you're sure everything has successfully copied, format user data from twrp. Once complete, restore your nandroid from the USB otg and boot your rom. Then go back to recovery and restore your sdcard. Reboot to system. Done. Make sure to boot your rom before copying back your sdcard, otherwise the directory structure will be incorrect when you do boot.
[Nexus 6  Original Android Development] tom.lockhart:
The phone is essentially brand new, I haven't done much on it - I did backup with Helium to try to restore my sms and app data, would I still need to do the above steps or can I disregard?

I was planning on doing the following once I get home from work:

1. Unlock Bootloader

2. Root + Custom Recovery

3. Nandroid Backup

4. Flash no force encrypt

5. Flash Leankernel

Going to do all of this with Wug's toolkit.

Does this seem like it should work, and give me leankernel, with no encryption, on stock ROM?
[Nexus 6  Original Android Development] flyinj54:
I myself removed encryption before I did anything else.
[Nexus 6  Original Android Development] adrman:
I should have added the step of flashing LK and booting it before you made your nandroid. That way you can eliminate Step 4 as LK does not force encryption. As far as helium and a toolkit, I can't speak to either as I don't use them.
[Nexus 6  Original Android Development] flyinj54:
Running 1.9.4 with no issues. Seems a bit quicker as well but of course this is probably placebo.
[Nexus 6  Original Android Development] tom.lockhart:
Thanks for the response.

One last thing I'm confused on, from what I've read, LK will keep the encryption mode on the phone. If I don't ever turn encryption off, wouldn't LK just keep it on? How would I then go about turning it off?
[Nexus 6  Original Android Development] adrman:
Yes, you will just stay encrypted. To decrypt, you will still have to format user data and everything will be wiped. I'm sorry, I didn't notice that you hadn't unlocked or rooted yet. My method with the USB otg assumed that you were. As a last comment, I would suggest that you forgo the toolkit for those procedures and learn how to perform them without it, in case something goes wrong. There are stickies that outline everything in the general and q&a forums.
[Nexus 6  Original Android Development] flyinj54:
Yes lean kernel will just keep the encryption on your device if you do not go through the steps to unencrypt the device. If you wait and you wanted to unencrypt the device you would have to go through the same steps and format all your data on the phone. It's best to do it when you first get the phone so you're not losing everything. You should just go ahead and do it as that's what everyone is doing and gaining the performance of course which is the reason behind it
[Nexus 6  Original Android Development] tom.lockhart:
Thank you!!!!!! You've been a huge help in this process.

I have been reading loads and loads over the last few days and am excited to get down and dirty. I will forgo the tool and use all of the great stickies around here. I'm going to follow my original plan of unlocking, rooting, custom recovery, backup, remove encryption, flash LK.
[Nexus 6  Original Android Development] PhilDX:
I'd like to know this too but for a different reason… flip cases with auto screen on ehen opening have a tendency to randomly and frequently turn the screen on while the case is closed. really annoying. would be nice to be able to disable it.
[Nexus 6  Original Android Development] Imoseyon:
So I built v1.9.5 (and put it up on testbuild folder) with the smb135x wakelock disabled, and so far it's not obvious to me what this breaks. Granted it's only been a few min - lol. But charging works fine. Anyway perhaps you guys will be able to find what effect not having this wakelock has - it has to be something power/charging related.

Also, I think 5-10 pages back some folks asked for a "no force encrypt" stock kernel, so I put it up on the main folder.

[MENTION=3528164]magnum870[/MENTION] & [MENTION=3065937]PhilDX[/MENTION], I will look into what you want but I'll probably need to pick up a flip case so could be a while...
[Nexus 6  Original Android Development] franciscofranco:
Maybe that lock is for wireless charging?
[Nexus 6  Original Android Development] Imoseyon:
Tried that too - works fine. :)
[Nexus 6  Original Android Development] PhilDX:
I'll be happy to give you one of mine if you PM me an address to mail it to
[Nexus 6  Original Android Development] fitz420:
Does anyone know if there's a way to raise the overall output gain since fauxsound isn't supported with lk. On my nexus 5 my favourite kernel had it implemented and I'm used to having the boost to drive my headphones. This is my favourite kernel on this device and I really don't want to switch just for the output boost.
[Nexus 6  Original Android Development] Cy_n_ic:
Everything i find on smb135x is related to qualcom quick charge. Idk if that helps any
[Nexus 6  Original Android Development] old_fart:
You "may" know this already . . . . . the euphoria rom ( http://xdaforums.com/showpost.php?p=57077499&postcount=1 ) grabs the latest leankernel and then adds / hooks in the faux sound plus some other stuff . . .

hth.

---------- Post added at 10:37 PM ---------- Previous post was at 10:31 PM ----------

I have zero of those particular wake locks ? ? ? . hmm, it must be something I immediately and consistently disable in my setup. . I'm digging . . .
[Nexus 6  Original Android Development] magnum870:
I would greatly appreciate it. You could always just use a fridge magnet (or hard drive magnet if you have one lying around) and place it near the position of the "M" (from the front or back) :) But I can also understand wanting to do it with a real case. Thanks for the time you put into all the requests here.
[Nexus 6  Original Android Development] fitz420:
Yeah......I really don't want to have to run a certain ROM just to have fauxsound. Thanks though.

[MENTION=3357040]Imoseyon[/MENTION]........is there any chance you would consider adding fauxsound or compiling a separate build with it? I'm missing it and really prefer this kernel.
[Nexus 6  Original Android Development] fitz420:
That's a pretty good idea. So I would extract the boot.img and flash via fastboot? Also, do you know if that's the only thing added.
[Nexus 6  Original Android Development] fitz420:
That works but lkconfig isn't included.
[Nexus 6  Original Android Development] oak:
1.94 running great as always. This kernel has great performance and ridiculous battery life and I do mean ridiculous in a good way.
[Nexus 6  Original Android Development] doitright:
Check if your CPU deep sleep increments while the phone is ON, SCREEN OFF, PLUGGED IN.
[Nexus 6  Original Android Development] Imoseyon:
Ah.. let me give this a shot. This will probably be lower on my priority list though..

This is on the list! I've been waiting for someone to send me a github pull-request for it, since I prefer not to look at other devs git repos if I can avoid it. :)

Ah yeah I just checked this for USB charging. The behavior doesn't change whether the wakelock is enabled or disabled. I will check the fast and wireless chargers when I get home tonight.

If I can't find any issues with this (and not hear any reports of breakage on 1.9.5), I may just disable this wakelock for the next release.
[Nexus 6  Original Android Development] franciscofranco:
Don't lie, stop stealing my open source innovations!!!
[Nexus 6  Original Android Development] Imoseyon:
Lol, your repo is the last one on my list to look at!
[Nexus 6  Original Android Development] Cy_n_ic:
Heres a screenie not long after unplugging from being charged all night. Smb135x is on top and i can confirm it was not present before i plugged in. Moto turbo charger was used but i have seen it on others as well. Are you sure it would be ok to completely disable? Im just concerned cuz we still haven't come to a consensus on what its actually for
[Nexus 6  Original Android Development] jfcooley:
Maybe its just me, but on 1.9.5 with the turbo charger the remaining time until charged didn't show at the bottom of the lock screen.

Went back to 1.9.4 and it returned. Don't know if that helps determine what the wake lock does or doesn't do, just thought I'd mention it.
[Nexus 6  Original Android Development] franciscofranco:
Did the device actually charge as fast as before without the wakelock?
[Nexus 6  Original Android Development] jfcooley:
I really can't say.

I had to leave for work and just noticed it didn't say how long until charged.

I don't think it did. I gained 3% on the short ride to work (maybe 5-10 min) and I believe only gained 1% while on 1.9.5.

Sorry, I just didn't think to note specifics. Was in small hurry.
[Nexus 6  Original Android Development] Cy_n_ic:
Ok so maybe we need to time them both and see what happens. Time left on the lock screen was a good find. I dont use one and i never even knew it was a thing lol
[Nexus 6  Original Android Development] Imoseyon:
Interesting. If the smb135x wakelock happens only while the phone is charging then there's no need to mess with it. I am pretty sure that this wakelock is held even while the phone is not charging though. I'll try to investigate that angle a bit tonight as well. I can probably make the wakelock active only while charging to but that's a lot more work. :)
[Nexus 6  Original Android Development] Cy_n_ic:
Its definitely active while not charging. 3 hours unplugged since my last screenie and the left column is still going up. Not as aggressively as while charging i dont think. Maybe not even enough to become an issue. I would bet those that report it as an issue arent realizing its only like that while charging and not really loosing any battery life because of it.
[Nexus 6  Original Android Development] spinkick:
Its my top wakelock but not an issue at all, I dont think its keeping the phone awake or anything like that as far as I can tell.
[Nexus 6  Original Android Development] tom.lockhart:
are you running stock lean, or have you configured it at all? Trying to get a feel for the best tweaks to really get the most out of LK on n6.
[Nexus 6  Original Android Development] Imoseyon:
Looking at the code a bit more, this wakelock clearly has to do with automatic power source detection. What puzzles me is that the power source detection seems to work fine even with this wakelock completely disabled, so my guess is that the wakelock handles some edge case that I haven't been able to trigger.
[Nexus 6  Original Android Development] Cy_n_ic:
Automatic power source detection huh...like it could be checking if you are using a turbo or standard charger, via usb or if you are even below 15% to activate the turbo charging feature?

---------- Post added at 05:39 PM ---------- Previous post was at 05:34 PM ----------

Google searches for smb135x like i said before show relations to Qualcomm quick charge 2.0

The spec page on the moto turbo charger state Qualcomm quick charge 2.0 tech is inside it.

Im starting to lean toward this having something to do with turbo specifically. Not just any ol charging method.
[Nexus 6  Original Android Development] Imoseyon:
Yes but this lock is designed to prevent the phone from going into sleep while apsd runs are running. So something is still broken if it's showing up often on the top ten list. These apsd runs are very quick. I'll figure out a way to deal with this one way or another.
[Nexus 6  Original Android Development] tom.lockhart:
What is everyone's take on clearing cache or wiping prior to flashing?

I've heard different things from so many different sources.
[Nexus 6  Original Android Development] lainemac:
I always wipe the cache. Doesn't affect the apps so why not?
[Nexus 6  Original Android Development] franciscofranco:
Caches and the Kernel have absolutely no correlation.
[Nexus 6  Original Android Development] lainemac:
You learn something new everyday...

So when people say to "clean install" a kernel, what do they mean?
[Nexus 6  Original Android Development] franciscofranco:
I don't know what people call it these days. But from my understanding it's flashing your rom first (without wipes), then the Kernel. It's pretty stupid if you ask me, there are no Kernels at the moment (that I know off) that mess with system files, so one would be happy so simply re-flash stock boot.img first, then the custom Kernel. If the custom Kernel is a whole boot.img you don't need to flash stock. If the custom Kernel is packaged into a zImage flashable zip, then you would need to flash stock boot.img first.

TL:DR flash stock boot.img first, then the custom Kernel.
[Nexus 6  Original Android Development] lainemac:
Would flashing the stock kernel zip suffice as well?
[Nexus 6  Original Android Development] Imoseyon:
This is true but there's a possible and rare exception. Some custom kernels come with their own Android app (ahem), which could store some data in the cache. Or out of million kernel tweaking apps out there, there may be some that store data (from previous kernel) in the cache which may be incompatible with a new custom kernel you flash. This is rare but I've seen this happen and when it happens it's super annoying.

But yeah in general you don't need to wipe anything.
[Nexus 6  Original Android Development] sir*mez:
Wakelock

I don't seem to get this wakelock at all. I charge wireless and wired.
[Nexus 6  Original Android Development] Smallsmx3:
On the latest test and Frank 12. Having issues waking up the phone sometimes. It will be fine for hours. Then every once in awhile it's like a SOD but wakes up eventually
[Nexus 6  Original Android Development] old_fart:
I nice troubleshooting step would be to put back in the lk1.9 and see if the SOD disappears. Oh . . . Or you know that already . . .
[Nexus 6  Original Android Development] Smallsmx3:
Actually it started happening when I started using Frank ROM. I was using lk on cm and slim with no issues on 1.9. Used 1.9 on Frank since I installed it. If I use FK I don't have this issue... Mr cynical
[Nexus 6  Original Android Development] Cy_n_ic:
I notice this every so often. Not even once a day usually. I just brush it off as a fluke. Ill take a heavy sleeper over a wide open wake lock any day.
[Nexus 6  Original Android Development] Smallsmx3:
Yeah that's exactly it. Odd though... Power save maybe?
[Nexus 6  Original Android Development] Imoseyon:
I've never had a single sod ever since I've had this phone. I've always used stock rom.
[Nexus 6  Original Android Development] Cy_n_ic:
Nah. Happened before power save was implemented. Also i dont run stock. Bear in mind these are heavily modified custom roms running kernels not built inline so some weirdness should be expected, and if all you get is a little laggy screen on once or twice a week id say thats acceptable. To me at least
[Nexus 6  Original Android Development] flyinj54:
I was having slow to wake moments and a few sods on stock rom with stock kernel. Since switching to lean kernel I haven't had one Sod or slow to wake. Not sure what the difference is but it fixed my phone.
[Nexus 6  Original Android Development] old_fart:
I have no sods or slow to wake EVER until recently. Am running the euphoria rom and they plugged in "themes" ! Well, so I bellied up to the bar ( pun ) and plugged in some ( tasteful and artful ) themes . . .

And . . .

The themes has introduced instability into my phone ! ! !

I'll like it when they ( the rom devs ) go to themes engine , version 2, or is it 3 ?
[Nexus 6  Original Android Development] slickie88:
I does happen with stock ROM. I've had it occur with both lean and elemental, both on stock settings and stock ROM.
[Nexus 6  Original Android Development] Imoseyon:
What governor are you on? And are you undervolting at all? If you're running interactiveX, what's your screen off frequency?
[Nexus 6  Original Android Development] Smallsmx3:
I've only had it happen on lk and Frank.... I've had my phone since launch... Used mainly you're kernel
[Nexus 6  Original Android Development] Mocheen:
recently started flashing again, but i noticed that light flow had stopped working from version 1.8 to 1.9. Anyone know a fix to this?
[Nexus 6  Original Android Development] mugendon:
Was discussed a few pages before. A reinstall of lightflow should fix this.

Btw. I found this reddit post where the topic is about some kind of fix for the double 2 wake feature. Anything you could use from this [MENTION=3357040]Imoseyon[/MENTION]?
[Nexus 6  Original Android Development] Franzie3:
"One way or another"....sounds mischievous
[Nexus 6  Original Android Development] slickie88:
I've been on all of the latest builds of FK, LK and elemental recently. I've experienced the very occasional slow to wake issue on both LK and Elemental. I didn't stay on FK more than 48 hours and don't recall having it happen there. My point is that to me this seems like it's not dependent on stock vs custom ROM or which kernel we're running. It's just started happening to me in the past 2 weeks maybe, perhaps once or twice a day.

As for my settings on LK1.9, at the time I was using 100% stock settings. InteractiveX, no OC, no UV, mpdeceision enabled, no changes to screen off freq.
[Nexus 6  Original Android Development] Imoseyon:
I'm confused about what "Vomertweaks" is - sounds like it's one of many kernel tweaker apps out there. Based on the thread and the video, it sounds like [MENTION=1978554]zephiK[/MENTION] recompiled Franco's kernel to enable flar2's gesture controls. Leankernel already has this support. I did hear that gesture control sometimes is slow or fails - I will add this to my list of things to look at but as I don't use this feature at all and I tend to believe messing with it for performance could have an adverse effect in battery.

You're not talking about using gesture to wake the phone? Just using the power button?

:) I can't really fix APSD without some intimate hardware knowledge, so the next release will have a "workaround" fix.
[Nexus 6  Original Android Development] slickie88:
Yes, power button to wake. I thought that's what others had been referring to. Hope I didn't derp. :D

Press power button to wake, it doesn't wake, mash on the button a time or two and it eventually does wake. No way to reproduce it and I wouldn't know what to look for in terms of logs. First couple of time it happened on ElementalX was what prompted me to come back to LK to see if that might help. I've had it happen 2 or 3 times in the past few days on LK. I didn't notice it on FK either, but that's hardly conclusive considering I didn't run it that long.
[Nexus 6  Original Android Development] oak:
Sounds like hardware??
[Nexus 6  Original Android Development] ScumDroid:
I think its one of those superdupercharger init d scripts. Not sure exactly what it does.
[Nexus 6  Original Android Development] Imoseyon:
I've never seen that happen on my phone. If that were to happen this issue would go straight to the top of my todo list. :) I suspect it's caused by something outside the kernel - hardware, ROM, or a misbehaving app maybe.
[Nexus 6  Original Android Development] mugendon:
Unfortunately I misunderstood the reddit posting. I thought it was about fixing the d2w, so that it will work 100% of the time (or atleast almost), but it seems it is only about an issue with franco kernel and chroma rom... Sorry for bugging you with this, you can cross it from your list.
[Nexus 6  Original Android Development] beyeond:
Yeah I think I was the first person in the thread to report this issue. Just for comparisons sake I am running an unofficial slim build on a PVS 2 if that matters. Issue started with 1.9. I'm not saying that because I think it's the kernel causing it, but just to give a time frame.

I could revert to 1.8 for a few days and see if that changes anything, but the issue is kinda rare.
[Nexus 6  Original Android Development] Mocheen:
Thanks for the reply, tried to reinstall still didn't work. I'll do some more research.