yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Imoseyon:
Your stuttering may be due to apps being killed in the background. There appears to be some issues in lollipop memory management.
[Nexus 6  Original Android Development] lainemac:
Makes sense. Lollipop is really new. Plus, this is Google....
[Nexus 6  Original Android Development] hidea:
I've been having issues connecting to ADB when using this kernel with an unofficial CM12 daily build. ADB can't detect the device, and on top of that the CM ROM lost its builtin Superuser.

I'm assuming it's a requirement for CM ROMs to be on CM kernels for adb/built-in superuser to work? Unless I've done something wrong…
[Nexus 6  Original Android Development] Imoseyon:
Nope I don't have a note 4 - sorry

I would recommend flashing patched mpdecision and not disable it completely. It is useful in many different ways.

That seems odd - any other Verizon users with the same issue?

Outside of lkconfig, if you make any custom changes you'll have to come up with your own init.d script to persist on boot. Or use an app like trickster.

Hmm.. I've made changes to how adb works in my kernel ramdisk. So the chance of adb issues on CM is definitely there. I will have to look into this.
[Nexus 6  Original Android Development] Cy_n_ic:
Thanks imoseyon. I read up on how to make an init.d script and wrote one real quick that does everything i want. Easier than i thought and i learned something today! Cheers and keep up the great work!

Via A Rooted Glade PlugIns
[Nexus 6  Original Android Development] hidea:
Let me know if I can be of any help!
[Nexus 6  Original Android Development] Pilz:
Is there a way to have s2w without haptic? I've tried all of the options in lkconfig but they have have haptic even the stock d2w
[Nexus 6  Original Android Development] monkboy24:
Omg this kernel is getting better and better every build!! v1.5 FTW
[Nexus 6  Original Android Development] jackpollard:
One of the things I've loved about being a programmer for 30+ years is the truth of programming, ittt works the exact same way every time, regardless of time, place, mood, etc. So why does a kernel have to "settle in"? I see it all the time, when I update or load a kernel for the 1st time, it seems to always need a few days for optimum performance and battery life. Is it learning from cpu cycles? or power cycles? Programs don't need time to settle in, they do exactly what they do, every single time. What would be the rough optimum time for the rom to settle in? I'm usually around 2-3 days.

Lean is always great out of the box, but when I wait a few days, I'm always surprised how much better my battery life gets. Lean 1.3 was great, I was not on 1.4 long enough and 1.5 is seeming to be even better then 1.3, so whatever your doing, thanks as always!
[Nexus 6  Original Android Development] grunt6:
I'm on Verizon and not experiencing this on 1.5. I usually set up and configure the ROM, backup, then flash lk just in case. Working great!
[Nexus 6  Original Android Development] r1ndr3w:
What basic settings are you using? Frequencies? Governor?

I kind of figured it should be working. Thanks for confirming. This kernel is amazing. I want it on my N6.

Thanks.
[Nexus 6  Original Android Development] Remoteconcern:
Anybody else totally plagued by two wakelocks, sensor_ind and msm_hsic_host?

These aren't lean kernel related but are kernel wakelocks. I wonder if anything can be done about them?
[Nexus 6  Original Android Development] grunt6:
I just flash the kernel, no changes from stock for now.
[Nexus 6  Original Android Development] xterra91:
I'm on Verizon also flashed 1.5 no data flashed Franco kernel data instantly?
[Nexus 6  Original Android Development] mugendon:
This might be true for single threaded programs, but not for multithreaded ones (=> raceconditions).
[Nexus 6  Original Android Development] ScumDroid:
sensor_ind is Hangouts, uninstall it, and msm_hsic_host is, i think your Data connection. You will always see that wakelock while connected to data.
[Nexus 6  Original Android Development] grunt6:
Maybe how the Rom interacts with the kernel??? I'm on Terminus Rom with 1.5 since yesterday morning and no issues with Verizon.
[Nexus 6  Original Android Development] Cy_n_ic:
Yes. Same as i did. An init.d script for sys/android_touch/vib_strength that sets it to zero on every boot. Its not daunting at all. All the info on how its done can be found here on xda. Look for an init.d script tutorial and good luck

Via A Rooted Glade PlugIns
[Nexus 6  Original Android Development] r1ndr3w:
[MENTION=3357040]Imoseyon[/MENTION]

Just coming to update the issue. I reflashed kernel by extracting boot.img from zip file and flashing via fastboot. It took about 10-15s after boot and device found the Verizon network. I guess it could have been a bad initial update.

I've rebooted the phone several times and toggled data off/on many times. Data is working.

Thanks for your help.
[Nexus 6  Original Android Development] pantmunu:
Had the msm_hsic_host wakelock .. Its very weird. Tried 2 different Roms and in both of them my phone was awake more than 60% of time. Read a few interesting topinc on reddit and found out its coz of the low signal or something like that. Back on stock with Franco r4 and it's gone. I do have my data turned off ATM and the wakelock is pretty much unnoticeable. U can Google it and check of out yourself.

http://www.reddit.com/r/nexus4/comments/199bd3/a_great_explanation_of_the_msm_hsic_host_wakelock/

Here is a link to reddit.
[Nexus 6  Original Android Development] Remoteconcern:
Interesting. That is for the nexus 4 which actually had a tablet SOC and therefore hack to attach a modem which resulted in those problems. I had no idea the N6 would suffer from the same problem - it's killing me at the moment.

As for sensor wake lock, I can't uninstall hangouts as I actually use it. Very frustrating.

Thanks for the info though guys.
[Nexus 6  Original Android Development] Pilz:
Thank you I'll give it a try :)
[Nexus 6  Original Android Development] Imoseyon:
There are a couple of old caf commits that address the msm_hsic_host wake locks. I assumed that shamu would have included them already. I'll check.

Edit: confirmed that those commits are already in the kernel.

I'm guessing you guys are using GSM to look at your wakelocks. I don't agree 100% with how GSM counts wakelocks - in fact, what I see in the kernel counter is different than what it's reporting. I don't think msm_hsic_host wakelocks is an issue in shamu.
[Nexus 6  Original Android Development] pantmunu:
The only conclusion I have came to so far is that this wake lock is caused by having a poor data signal. I might flash slim lp and try to reproduce this problem. Let's see.

I live in ridgewood NY and signal here specifically around my apartment seems to be well kinda wonky.

---------- Post added at 12:33 AM ---------- Previous post was at 12:24 AM ----------

I was using better battery stats and was using slim ROM . didn't take a screen shot to show u guys. But will be flashing back to slim soon and if it happens i will post a screen shot here . only a very few are having this issue I guess.
[Nexus 6  Original Android Development] oak:
LK 1.5 is great I think. Smooth as silk and though I am not through a full battery cycle, I can tell battery will be very good. I am currently at 71% remaining with 3 hours and 4 minutes SOT. Thanks Imoseyon.
[Nexus 6  Original Android Development] beyeond:
Yeah nothing to report here. Running great. I run the kernel as is.. I have a 2 for whatever you guys call that number between 1-13 that effects voltage so I don't want to mess with it too much.

I have a horrible signal where I live so I don't expect to get the battery life some of you get, but I'm fine with 5 hours SOT.

On the list of things I use my phone for, making calls ranks near the bottom so the signal doesn't bother me much. The pros of my old T-Mobile jump plan outweigh the cons.
[Nexus 6  Original Android Development] Gungrave223:
its official I have zero reason to use any other kernel Thanks Imoseyon :D
[Nexus 6  Original Android Development] Remoteconcern:
Hmm, do you feel the same about better battery stats? The thing is I'm getting awful standby time with the battery chart in Android reporting the phone being near constantly awake. The only thing in BBS is often msm wakelock.
[Nexus 6  Original Android Development] mugendon:
I have the problem, that sometimes my phone does not go to deep sleep. It can only be fixed with a reboot. When looking at wakelock detector, I can only see wakelocks that kept the device minutes awake (e.g. google services with 2m36s), but the device was hours awake. Could that be a kernel issue? (Screenshot is from lk 1.2)
[Nexus 6  Original Android Development] eep2378:
Sounds like a rogue app keeping your device awake. You can use app ops from the playstore to prevent certain apps from keeping you device awake.
[Nexus 6  Original Android Development] Gungrave223:
You were right it was super easy..Thnaks :highfive:
[Nexus 6  Original Android Development] oneandroidnut:
Any chance you will be making one? it is my favorite kernel!
[Nexus 6  Original Android Development] Langduscher:
What are your settings please?
[Nexus 6  Original Android Development] JManekia:
Running great for me also with the combination of Terminus rom. I only kept the DTW with feedback, enabled the charging LED and changed the RGB to cool setting.
[Nexus 6  Original Android Development] oak:
Default LK settings. Stock rom, encrypted. Google apps such as sheets and slides converted to user apps and Greenified. Some other apps Greenified too. Ambient display on. Auto brightness on at about 45%. Location services off. Wifi on. Horrible cell signal. That's about it.
[Nexus 6  Original Android Development] jjhiza:
Did you mean 4 HOURS of SOT? Nearly 30% idle drain during a 3 hour time frame would be pretty bad if you really only have 4 minutes of SOT. The N6 battery definitely takes about 4 or 5 full cycles to catch its stride, but after that, battery life is very, very good,but if you've already broken in the battery, and you're still experiencing that kind of idle drain, your battery may be bad. Hopefully I'm wrong, and you meant 4 hours. [emoji6]
[Nexus 6  Original Android Development] oak:
I meant 3 hours and 4 minutes or 184 minutes of screen time, which is excellent on 30% battery drain.
[Nexus 6  Original Android Development] Imoseyon:
I don't have BBS - I'd imagine both apps just look at the kernel counters in /sys/kernel/debug/wakeup_sources. There are so many different counters there so it's possible that the reporting is not consistent across the board. I've been thinking about this and I think i'll switch my counting to use "total time" (similar to GSam) instead of "total count". The former I think makes more sense as it represents how long the wake source has potentially kept the phone awake.
[Nexus 6  Original Android Development] natezire71:
Is anyone else having difficulty with the dt2w option staying enabled? It seems like the option resets after reboots. I'm only using Terminal to set it via lkconfig. I have option 1 enabled.
[Nexus 6  Original Android Development] old_fart:
Please search the thread. Well, I believe it has been covered. My poor small brain . . . I believe it has to do with 'kernel side' versus 'rom side', and our ( really great ! ) kernel cooker wishes to keep his code pure and not cross the boundary ( to rom ) . . . So, I believe a script -or- an app needs to toggle it 'on' when you recycle / turn on . . . . . hth.
[Nexus 6  Original Android Development] natezire71:
Is this any different than using this? https://play.google.com/store/apps/details?id=com.codechron.n6doubletapunlock
[Nexus 6  Original Android Development] old_fart:
That looks like the ( pay a dollar ) app that does the toggle -AND- persists thru a reboot. Yaa ! . Please be aware there is the app/rom side of all this which is basically doing a 'flip of a switch' . . . versus the real code doing the real work. . And I believe the factory image rom has the real working code, but our kernel people ( double ) improved on the performance / reliability / current_draw of the working software .
[Nexus 6  Original Android Development] natezire71:
There is a free version of this on XDA, that is just a donate version.

Should I use that app or use lkconfig in conjunction with with a script? Which is better?
[Nexus 6  Original Android Development] LordDeath:
Is this kernel using a more aggressive power saving mode? Afair Lollipops built-in power saving mode did not lock the CPU cores to 730 MHz but with the leanKernel it doesn't go higher than this value and the device feels laggier than my old Nexus 4.
[Nexus 6  Original Android Development] Cy_n_ic:
If i get a few minutes tonight ill whip up a script and post here for anyone that wants their wake/sleep gestures to persist through reboot.

Via A Rooted Glade PlugIns
[Nexus 6  Original Android Development] wilson289:
Does LK now have USB fast charge capabilities?
[Nexus 6  Original Android Development] Cy_n_ic:
Here is a script to make the sleep/wake gestures, dt2w and vibration strength persist through reboot for those that do not use the defaults from lkconfig. Imoseyon you are more than welcome to add in the OP if you feel so inclined. Simple instructions to configure the script to your liking are included in the script. Hope this is satisfactory as its only my second script and the first i have ever shared.
[Nexus 6  Original Android Development] Imoseyon:
Depends on what you mean by "USB fast charge". ;) My tweaks allow you to charge 700-800mA while retaining the USB data connectivity (instead of the usual 400-500mA).
[Nexus 6  Original Android Development] wilson289:
Awesome, I am sold :D.
[Nexus 6  Original Android Development] Zaf9670:
Just to share. I'm also on Verizon and after flashing 1.5 my service wasn't connecting.

I then turned on airplane mode which still didn't resolve the issue. Then I went to the mobile settings and changed LTE to global and then back again.

Everything is working now. I'm on stock 5.0.1 for reference.
[Nexus 6  Original Android Development] mclisme:
Hi,

Is there a need to wipe data and cache before/after flashing the kernel for the 1st time on a decrypted and rooted 5.0.1 N6? Will the kernel install correctly if I don't? I know I should have learned by now (5th modded device) what does "Wipe Data/Cache" actually mean/do... :p

Also: The whole configuration process is taking place after we've actually installed the kernel and is applied by changing the values appropriately and rebooting or we have to save the modded kernel version and re-flash?

I've been away from modding for some months and I'm a little rusty...

Thanks!
[Nexus 6  Original Android Development] Nalix:
Thanks for a great kernel. I've been running the stable kernel since 1.2 without issues. How does the ocuc kernel work? Do I have to do something extra or is it just a flash without extra settings? My PVS is 5 if that matters.
[Nexus 6  Original Android Development] natezire71:
I can tell you that wiping dalvik does nothing on Lollipop.
[Nexus 6  Original Android Development] Cy_n_ic:
I believe it does. Its just not labeled correctly anymore was my understanding. Nobody says wipe art cache because you wouldnt find the option. Correct me if im wrong please but runtime cache still exists just under a different name

Via A Rooted Glade PlugIns
[Nexus 6  Original Android Development] PeRKoniX:
Is there any way you can tweak the global vibration strength with this kernel? If not are there any plans do add it as a feature in the near future?
[Nexus 6  Original Android Development] natezire71:
Dalvik isn't a thing anymore. The runtime was replaced by ART. ART doesn't have a cache (to my knowledge). TWRP can't remove wiping dalvik cache, because the majority of devices are still on 4.4.4 (KitKat) or below--which still uses the dalvik runtime.

Clearing the regular cache does actually clear a cache; just not the runtime cache.
[Nexus 6  Original Android Development] Cy_n_ic:
From what i have been reading art does have a cache and its even a larger footprint than dalvik. So it would need wiped. Data/dalvik-cache/arm is full of dex files. Not sure if thats it or not. But just because recovery SAYS wipe dalvik doesnt mean its not wiping art is my conclusion. In the future recovery could say wipe runtime cache to cover both bases without confusion. idk but were getting quite far off track of the thread lol. Appreciate the witty banter though. Feel free to pm me if needed

Via A Rooted Glade PlugIns
[Nexus 6  Original Android Development] Remoteconcern:
If you press wipe cache, the phone definitely does all its ahead of time compiling again. It's similar to a first boot when switching to ART on KitKat.
[Nexus 6  Original Android Development] Franzie3:
If you give it 3-5 minutes it will kick in without having to change settings. usually only happens on first boot from flash of LK. After that any other reboots behave as normal. That's at least what I have seen with the 3 roms i've used with LK
[Nexus 6  Original Android Development] Imoseyon:
Hmm i'd be interested to see if this happens to my kernel only. That would actually surprise me...
[Nexus 6  Original Android Development] HaRdC0r3:
[MENTION=3357040]Imoseyon[/MENTION] are you using f2fs on any of your partitions? And if so how?
[Nexus 6  Original Android Development] monkboy24:
Nope with the ocuc kernel all u have to do it flash it boot it and enjoy. It's awesome
[Nexus 6  Original Android Development] natezire71:
For whatever reason, I have vibration set to zero, but when i dt2w, it still vibrates.
[Nexus 6  Original Android Development] Blaze420916:
Can you tell what PSV value you have base off stock voltage?
[Nexus 6  Original Android Development] buzzwyzr:
Confirmed that this works.
[Nexus 6  Original Android Development] Blaze420916:
I did the same thing and mine also shows 9 but my stock voltage levels indicate I'm PSV 13
[Nexus 6  Original Android Development] Xileforce:
Fauxclock doesn't seem to work for changing voltages. I try to adjust but it doesn't show anything changing where it displays the voltages. Anyone else have this issue?
[Nexus 6  Original Android Development] zephiK:
Its possible that that the app doesn't work on leanKernel as FauxClock is for Faux Kernel.
[Nexus 6  Original Android Development] Xileforce:
Yes SetCPU seems to be working. I've used fauxclock with a lot of different kernels before. Maybe it needs an update or something.
[Nexus 6  Original Android Development] zephiK:
Are you using the latest version of SuperSU, 2.35? You can give that a try and see if that resolves the issue.
[Nexus 6  Original Android Development] Mr. Steve:
When you restore from your previous backup, should you restore just the /data portion or both the /system and /data portion?
[Nexus 6  Original Android Development] simms22:
no root? neat :)
[Nexus 6  Original Android Development] Blaze420916:
Seems to run get at this voltage
[Nexus 6  Original Android Development] buzzwyzr:
Crap...I missed that part of your post. This with root access.
[Nexus 6  Original Android Development] b.huss2:
I only restored data. Should be all you need.
[Nexus 6  Original Android Development] Xileforce:
Updating fixed it! Thanks man!
[Nexus 6  Original Android Development] simms22:
lol
[Nexus 6  Original Android Development] gamewarden234:
Since flashing this kernel twrp gets stuck at backing up system. Won't go farther.
[Nexus 6  Original Android Development] :
Marking Calendar for February

We don't want you to leave so soon [MENTION=1050103]sykopompos[/MENTION] :p

February! :crying:

Frank is going to die of old age! And I might not have any hair by then :silly:

Oops! Edit where do I read up all this talk about PVS?
[Nexus 6  Original Android Development] Blaze420916:
There was an old thread in n5 forum that was made a long time ago but seeing this kernel released got me curious you can find all the info you need in here.
[Nexus 6  Original Android Development] :
Need to Read

Well, I read this, and immediately my brain went to well why is my number so low :(

So, needed more reading material.
[Nexus 6  Original Android Development] brizey:
I had a monster chip in my Thunderbolt. People used to not believe how low I could go. It was still a crapola phone. My S4 had crappy binning, and I used it for 18 months and never once ran out of juice. I never bothered to undervolt beyond what kernel devs did because, well, why would I if my battery lasted all day? Got really crappy binning here, too. Don't care. Not planning to undervolt anyway.
[Nexus 6  Original Android Development] joackie27:
It didn't worked coz you've typed PSV instead of PVS (dmesg | grep PVS).
[Nexus 6  Original Android Development] Nalix:
Nice, I'll try it. So what is the benefits of the ocuc kernel (i.e. what is different from the "stable" leanKernel)? I'm guessing it stands for over clocked, under clocked? Is it just a bigger span between idle and boosted modes?
[Nexus 6  Original Android Development] Franzie3:
To be honest, yours is the only one i have used since I got my nexus 6. I havent tried another one yet. I can try franco, see what happens on boot, then reflash yours and let you know. Idk if it is a rom thing because it happened on Stock, Rastapop, and Pure.
[Nexus 6  Original Android Development] arcanexvi:
There are other options? Who knew? ?
[Nexus 6  Original Android Development] Zaf9670:
Maybe it has to do with the way the phone initializes the wireless chip.

IIRC it was slow to begin with. I thought I cut my Sim card wrong on my first boot because of how long it took to find signal. No custom kernels or anything.
[Nexus 6  Original Android Development] mugendon:
From the features list of the first post ;)
[Nexus 6  Original Android Development] Franzie3:
Yea that could be too that i have a cut SIM card. But like i said it didn't happen without flashing the kernel so im stumped. I'm going to try my test in a little bit. Just busy at work trying to find credit card settlement data for a customer. (insert gun here....)
[Nexus 6  Original Android Development] Imoseyon:
ahhh that's a bug in my code. For now, use the stock dt2w option if you don't want vibration. I will fix this soon.

I did for a while when I first got the phone. I had to convert manually since the recoveries out there didn't support f2fs yet. Also my testing at the time showed that there weren't any performance advantages in going to f2fs. Any recoveries supporting f2fs nowadays?
[Nexus 6  Original Android Development] Franzie3:
[MENTION=3357040]Imoseyon[/MENTION] - I think it might have been a fluke thing. Either that or maybe something that happens on first flash of a kernel after the rom. I'll test it out again next time I flash a new rom. i tried both LK and then Elemental X. After flashing one LTE came within seconds. Flashed the other...Same result. When i had flashed LK right after flashing my rom it took roughly 3 minutes until service showed up. Liek i said, probably a fluke thing. I wouldn't worry too much. Keep cookin my man
[Nexus 6  Original Android Development] Nalix:
Hehe, thanks. I missed that :)

I do however have one more question. I'm new to Android customization and I'm curious about how this uc/oc thing works. Is it underclocked when "idle" and overclocked when the phone has a high load (e.g. playing a demanding game) or is it overclocked over 50% battery and underclocked below 50% battery?
[Nexus 6  Original Android Development] GPS3:
Quick question: Does the above feature have to be enabled somewhere? I notice when plugged into usb 2.0/3.0 it still says "Charging over USB". Is this feature working properly?
[Nexus 6  Original Android Development] flyinj54:
Are you talking about plugging into a usb on your PC? If so then absolutely that's exactly what It should say. Basically the developer just raised the speed/mah of charging over USB. This will not affect when you're charging on the wall socket whatsoever. This is just when you're charging on your PC.
[Nexus 6  Original Android Development] GPS3:
Yeah. While plugged into the computer it still says "Charging over USB".

I did notice on my way home that while on my car charger it says "Charging over AC". It must be my PC ports acting funky.

Thanks.