yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] spinkick:
I have msm_hsic turned off completely with no issues. Have you guys tried that?

What are you guys running for wlan_rx ? I'm running at 8 with no issues that i know of.

Im getting some pretty big drain, looks like its coming from bluetooth share for some reason. Could killing these wakelocks cause an issue with that?
[Nexus 6  Original Android Development] Damon13:
I disable Msm_hsic_host in Lkconfig and set the time interval for wlan_rx to 1,000, so far everything is working fine (phone calls, MMS, Mailbox).
[Nexus 6  Original Android Development] Imoseyon:
v1.14.7 in the testbuilds folder is attempt #2 on getting CM12 superuser working. If you're on CM12 please give it a shot and report back?
[Nexus 6  Original Android Development] daleski75:
Will Euphoria suffice as this uses the same root method as CM12?
[Nexus 6  Original Android Development] Imoseyon:
yes i believe so - thanks
[Nexus 6  Original Android Development] daleski75:
Just flashed it on the latest Euphoria build and no dice, the option for root is under developer settings but it does not work on apps which require root.
[Nexus 6  Original Android Development] mugendon:
I have a problem: When turning off the screen while an app (e.g. chrome) is opened, the screen won't turn on for incoming phonecalls (which means I have to press the power button and unlock the phone before I can answer the phone). Can this be a kernel bug?

If I turn the screen off while on the homescreen, everything works just fine if a call is received.

I am on stock rom with lk 1.12.1 (so no hsic_host manipulation).
[Nexus 6  Original Android Development] slekkas:
I'm running 1.14 stable but my phone shuts down at 17% battery. Did I miss a test version that fixes that?
[Nexus 6  Original Android Development] Imoseyon:
Thanks for testing - any chance you can grab logcat or dmesg?
[Nexus 6  Original Android Development] IAmAN00bie:
Does the new color service work properly yet? I can only set RGB values.
[Nexus 6  Original Android Development] daleski75:
Do you want it from boot-up or when I try and load an app which requires root access or both?

*Edit*

Just thought when I flashed it I lost adb access completely so would a logcat work to a point or not at all?
[Nexus 6  Original Android Development] eep2378:
Love this kernel since the beginning. 4hrs SOT and I'm still at 40% left :) kudos to [MENTION=3357040]Imoseyon[/MENTION]
[Nexus 6  Original Android Development] Imoseyon:
oh damn without adb logcat is harder. You'd need some sort of an app. If can you manage it, as much logcat as possible please.
[Nexus 6  Original Android Development] daleski75:
Just charging my phone and will see what I can grab for you.
[Nexus 6  Original Android Development] Krunk83:
Anyone else experiencing the screen not responding when trying to wake? It seems to be happening a lot lately whether it be s2w, dt2w, or the power button.

Nexus 6
[Nexus 6  Original Android Development] manup456:
I just flashed your last test build and lost root, but all I needed to do was flash the latest su zip from chainfire and I have root no problem. Are people saying its kernel related because it's fine for me.
[Nexus 6  Original Android Development] daleski75:
Managed to pull dmesg out from recovery and no logcat apps would work without root.
[Nexus 6  Original Android Development] daleski75:
[MENTION=4899017]LMose[/MENTION]yon is trying to get his kernel working with the built in superuser on CM12.
[Nexus 6  Original Android Development] jiv101:
Could you share settings
[Nexus 6  Original Android Development] manup456:
Well mine works I'm on Temasek ROM and SU works just fine.
[Nexus 6  Original Android Development] slekkas:
Anyone?
[Nexus 6  Original Android Development] beyeond:
I have a bad signal most of the time and usually average 4 hours screen time... Last cycle I was at 3.5 with 52% remaining. I'm still on the 1.13.3 build. Very happy with my numbers now. It's amazing what a third party kernel can do.
[Nexus 6  Original Android Development] poczynek:
At moment I use the elementalx app to control my sweep to wake gestures because my number one way to wake up my phone is to sweep up. To me it's more intuitive than double tap to wake. But I'd rather use lk config. Is there any way for lk config to have the option of the sweep to wake gesture up?
[Nexus 6  Original Android Development] wrongway213:
It's there under wake gestures.
[Nexus 6  Original Android Development] poczynek:
Yes but there's no option for sweep up to wake. There is only sweep across bottom of screen.
[Nexus 6  Original Android Development] wrongway213:
Derp, re-read your post a little slower and I now understand your question.. that is definitely not there (yet, Imoseyon does have the tendency to ad 178 features a day so I'm not guaranteeing it won't be implemented by the time I hit "Submit Reply")
[Nexus 6  Original Android Development] PhilDX:
I think you can enable this using terminal emulator and the syntax is provided in the OP in flar2's kernel thread.

post #2 here:

http://xdaforums.com/showthread.php?p=57079194
[Nexus 6  Original Android Development] poczynek:
Yes but it doesn't stick on reboot.
[Nexus 6  Original Android Development] droidguy22:
that's awsoome battery life, which Rom and what Kernel settings you are using?
[Nexus 6  Original Android Development] smclaughlin3:
Anyway to make the battery last till.zero? Mine dies at about 2%
[Nexus 6  Original Android Development] eep2378:
Simple AOSP. Min 300 max 2265. Mpdecision and CPU boost off. msm_hsic disabled. Screen off max freq at 1.2ghz.
[Nexus 6  Original Android Development] Imoseyon:
testers needed!

I had to make some drastic changes in ramdisk to get superuser and adb working on CM12 (and Euphoria too i think) in v1.14.8. This one was a doozy.

Seems to boot fine on stock as well but I want to make sure that it boots all the way on other ROMs as well. I need as many of you on custom ROMs as possible to flash and boot v1.14.8! (Not necessary for stock - I run stock). Thanks :)
[Nexus 6  Original Android Development] jackpollard:
Flashed and running great on Resurrection Remix V5.3.5. When I tried 1.14 I did have issues. So far, so good. Root looks great. Thanks as always!
[Nexus 6  Original Android Development] Krunk83:
Booted for me on chroma fine but had no signal. A simple reboot fixed that though.

Nexus 6
[Nexus 6  Original Android Development] jiv101:
Working good on blisspop sabermod
[Nexus 6  Original Android Development] poczynek:
Yes I also had no signal on bliss pop but reboot and ok.

However I changed enforcing to permissive in lkconfig but it's not sticking and is showing as enforcing.
[Nexus 6  Original Android Development] Imoseyon:
bliss pop uses chainfire, and not cm's superuser right? If so, I may have broken selinux mode control - will take a look.
[Nexus 6  Original Android Development] BRKotucs:
Works great on LiquidSmooth... Booted just fine.
[Nexus 6  Original Android Development] jiv101:
Those are my settings on blisspop sabermod

---------- Post added at 01:40 AM ---------- Previous post was at 01:38 AM ----------
[Nexus 6  Original Android Development] dsmitty166:
Working on Euphoria, thanks man!
[Nexus 6  Original Android Development] Krunk83:
Same here

Nexus 6
[Nexus 6  Original Android Development] Imoseyon:
Confirmed - will be fixed.
[Nexus 6  Original Android Development] franciscofranco:
Fix now plz.
[Nexus 6  Original Android Development] smclaughlin3:
Is the msm_hsic supposed to be there after i disabled it in lk config? Thanks
[Nexus 6  Original Android Development] Krunk83:
Is anyone else having issues waking the phone on sleep like I am? Sometimes it takes several attempts to get the screen to come on.

Nexus 6
[Nexus 6  Original Android Development] flyinj54:
Randomly it is slow to wake but for me this kernel had almost completely eliminated this problem vs stock or other kernels. It seems to be a problem with something that hopefully is fixed with the update whenever that comes from Google. I hope anyways
[Nexus 6  Original Android Development] Damon13:
I have msm_hsic disable and It doesn't appear on mine, I checked via Lkconfig and wakelock detector.
[Nexus 6  Original Android Development] Krunk83:
Sometimes the phone doesn't wake at all so I just give up. It's pretty frustrating.

Nexus 6
[Nexus 6  Original Android Development] smclaughlin3:
Ok i just and i entered 0 which says its to disable guess a higher number is what helps eliminate it.....just set it to 9 gonna test further and see if that was it...
[Nexus 6  Original Android Development] Damon13:
Here is a quote that I got from Imoseyon regarding whether the msm_hsic wakelock can be disable:

yes for msm_hsic, the value is 0 (there's no such option for other wake sources). You can see it in lkconfig as well.

Edit: you can probably also set it to something like a 1000 (yes you can actually go higher than 8), if you still want to allow kernel to instantly hold this wake source and release.
[Nexus 6  Original Android Development] Franzie3:
Just going on note to say I've crack flashed this kernel more then ROMs since I got this phone...
[Nexus 6  Original Android Development] Cy_n_ic:
No doubt. Kernel game is on point and roms are a lot slower to implement nifty features and worthwhile updates. Still worth the wait though
[Nexus 6  Original Android Development] slekkas:
My battery dies at 17%. Asked a couple of times but no one answered :(.
[Nexus 6  Original Android Development] Cy_n_ic:
I have no idea how they know where 100 and 0 are lol. Removable battery phones iv had could wipe battery stats in recovery and u do the charging/discharging dance to calibrate it for a new or extended battery. I would suggest looking further into how they calibrate phones now days. Sorry i cant help more. i doubt ur being ignored its just something you expect a phone to do right on its own and that info just isnt that common of knowledge i imagine.
[Nexus 6  Original Android Development] slekkas:
It is actually a kernel issue. Franco kernel had it and he fixed it. It something to do with the phone entering battery saving mode and not having enough power to stay on.
[Nexus 6  Original Android Development] daleski75:
[MENTION=4899017]LMose[/MENTION]yon all working good here with 1.14.8 and euphoria and it keeps root and adb works now :D
[Nexus 6  Original Android Development] ambichetan:
Hello all, I am new to this kernel. Do we have any updater like franco kernel updater for this one?
[Nexus 6  Original Android Development] daleski75:
Not for this kernel no.
[Nexus 6  Original Android Development] worstenbrood:
Changing GPU governor to simple_ondemand reboots the device.
[Nexus 6  Original Android Development] Damon13:
I will let you know soon regarding battery, I am on V1.14. Battery life has been amazing but I am starting to wonder if I will encounter the same problem as you. I am 2 days and battery still at 44% with light using (Texts, MMS, phone calls and receiving and sending emails, light browsing)
[Nexus 6  Original Android Development] manup456:
I'm on on the latest version he posted and my phone dropped to 10% battery and the phone was still on.
[Nexus 6  Original Android Development] Damon13:
So far the battery has been depleting gradually, But since a few people have reported issues with battery being volatile and unpredictable I am being vigilant. I will keep you updated.
[Nexus 6  Original Android Development] Mistertac:
AFAIK.... That's because that gov isn't truly in the kernel. Vindicator which uses this as it's base just added it back in as to avoid that.

Not sure the advantages of that gov vs stock and not saying IMO should do the same either... Just pointing it out.
[Nexus 6  Original Android Development] Cheater912:
My battery died at 5% last night. Not a major problem for me, but I don't know if that's what happens on stock.
[Nexus 6  Original Android Development] Franzie3:
Do you have battery saver enabled?
[Nexus 6  Original Android Development] smclaughlin3:
Anyone notice data drops 14.4 ànd later?
[Nexus 6  Original Android Development] __NBH__:
On stock the battery seemed normal, it went down to 1% then turned off.

After flashing some custom ROMs and kernels it started turning off at 4%.

Lately it's 7%, seems like the more I flash and punch big holes in the battery chart my battery gets less calibrated. I rarely get down to low battery but I haven't looked into how to calibrate it back to normal.
[Nexus 6  Original Android Development] Cheater912:
No, never used it.
[Nexus 6  Original Android Development] Franzie3:
ok nevemrind then, I read somewhere about a bug in battery saver mode where using it and hitting a % would cause a shutoff condition. Might of been fixed alreayd or something.

Sounds like it could be a newer CM bug or something from a recent commit. Honestly i dont let my battery go lower then 10% so i dont know. maybe i'll try it today. I'm running Validus with lk
[Nexus 6  Original Android Development] franciscofranco:
No.
[Nexus 6  Original Android Development] slekkas:
I thought I read in your thread that some of the users encountered this and you fixed it.
[Nexus 6  Original Android Development] worstenbrood:
Hmm, i thought these were enumerated like on cpu governors, so only the available are shown in kernel manager apps.
[Nexus 6  Original Android Development] Imoseyon:
1) Those of you having phone shut down early while in low battery, can you power it back up (before charging again)?

2) Speaking of GPU governors, does anyone use anything other than stock (which is what qualcomm and google want you to use)? I should probably remove the rest, or at least most of the rest.
[Nexus 6  Original Android Development] natezire71:
I had the same issue a few weeks ago. I don't remember what version of LK I was on. I haven't gotten that low since then.

Battery Save is setup to enable when my battery level reaches 5%. My phone turned off at 3%, and I was unable to power it back up unless I plugged it in.

edit: I am also on stock with LK. Nothing else.
[Nexus 6  Original Android Development] Cheater912:
I can't. It shows the low battery icon. I'm on (and always been on) stock ROM btw
[Nexus 6  Original Android Development] Mistertac:
Yeah you got me.. I'd have thought the same but I guess not.
[Nexus 6  Original Android Development] MadBrad11:
I am seeing massive kernel wakelocks for "bluesleep", "msm_serial_hs_dma", and "msm_serial_hs_rx" (slightly less for this wakelock). I see that these are all related to bluetooth and only activate while connected to certain bluetooth devices such as my LG G Watch. Is there any way these wakelocks can be lessened or turned off in a similar way as the other wakelocks? I don't mind if I don't get immediate notifications on my smartwatch, I would just rather not have to constantly turn bluetooth on and off when I want to use it in my car. Thanks!!

Anybody else seeing this same issue?
[Nexus 6  Original Android Development] Cy_n_ic:
Stock here. Also let my phone drain to 2% and all was good. Im not brave enough to go lower than that. I had a really bad experience completely draining a previous device and a nand restore saved me. In my opinion its just not something you should do on a regular basis. Yes its good to discharge them to keep them conditioned but not so much that it dies.
[Nexus 6  Original Android Development] akellar:
By massive are you looking at time spent or number of locks?
[Nexus 6  Original Android Development] old_fart:
The google sez its your sony bluetooth headset driver/software/app . . .

What have you done lately with bluetooth ?
[Nexus 6  Original Android Development] akellar:
He already said it's his smartwatch
[Nexus 6  Original Android Development] MadBrad11:
The amount of time spend in mainly the "bluesleep" and "msm_serial_hs_dma" wakelocks is very high. The number of locks varies.

I don't have a sony bluetooth headset. This always seems to happen when I am connected to my Android Wear LG G Watch but also happens with my built in car bluetooth. If I turn bluetooth off the wakelocks go away completely. Doing a quick google search shows that other people have had this problem with bluetooth devices (mostly smartwatches) on other phones but I couldn't find a fix. My previous phone, the Galaxy Note 3 used to connect to these same bluetooth devices and I never had these wakelocks so something must be different with the Nexus 6. I've tried different kernels and roms but the same wakelocks keep showing up and are keeping my phone out of deep sleep for long periods of time.
[Nexus 6  Original Android Development] EniGmA1987:
I just use stock. I think only stock and performance should be left in because the rest seem pretty pointless
[Nexus 6  Original Android Development] akellar:
Still curious what exactly you quantify as "very high"? Screenshot? I also have a smartwatch and connect to my car. Never turning bluetooth off, I do not have deep sleep issues of any kind. Yes, those wakelocks appear but not in any time consuming way.
[Nexus 6  Original Android Development] grisha1:
When I started to change wakelock settings in lkconfig, this same wakelocks started to become massive for me aswell. As soon as going back to stock, all good again. I anyway never suffered from too high wakelock, so this is fine for me.

I'm also running a smartwatch (360), so it seems that's a side effect of ramping down other wakelocks.
[Nexus 6  Original Android Development] Imoseyon:
Those of you with shutdown issues on low battery, make sure you haven't made any tweaks with thermal characteristics of the phone (thermal engine, etc.). If you did, revert those changes.

This will be a tough one for me to track down. I can't afford to let my battery drop that low, since I rely on this phone for work. :|
[Nexus 6  Original Android Development] nazzo123:
what you mean you had issues with 1.14? which build are you running with resurrection remix then because i really want to flash it.
[Nexus 6  Original Android Development] slekkas:
I haven't touched anything. All I did is install the kernel, install Trickster Mod. Disable the wakelocks and use 2 core option in lkconfig. That's it.
[Nexus 6  Original Android Development] Imoseyon:
Thanks for the report. I just fixed this (this problem also exists on stock) - will go out in the next release. This was an easy one to fix since the problem was easily reproducible.

Speaking of GPU governors, I'm probably going to remove at least half of them and maybe just leave a few interesting ones.
[Nexus 6  Original Android Development] jackpollard:
I had issues with Lean 1.14 and RR mainly due to losing root after the flash. Between RR and Lean, there was a lot of movement regarding root. I didn't have time to see where the specific issue was, so I restored my nandroid and tried it with Lean 1.14.8 and its been purring ever since. Backup and try RR and of course Lean, they are great together; feature rich, great devs and excellent battery.
[Nexus 6  Original Android Development] Beukhof1:
What are the recommended setting?
[Nexus 6  Original Android Development] spinkick:
I'm having the exact same issues. I also have a moto 360 watch.

---------- Post added at 03:53 PM ---------- Previous post was at 03:52 PM ----------

Can you post your wakelock settings that you use in LKconfig?
[Nexus 6  Original Android Development] Franzie3:
Turbo charger that bad boy....lol 5% - 45% in 15 minutes
[Nexus 6  Original Android Development] slekkas:
This is what Flar2 is writing on his last changelog posted a few minutes ago. This might help:

"And reverted the custom thermal, as there were reports of reboots at low battery levels in franco's thread. I've been meaning to revert it anyway. I added it a while back thinking it might solve some problems, but it didn't and it probably does other important stuff. So you will again notice frequencies throttled at low battery levels, which seems to be necessary on this device. Probably some edp thing."
[Nexus 6  Original Android Development] dcd17:
I've got the same issues, Bluetooth device is moto360. I'm going to switch the wakelock back to stock and see if that helps. Also wondering if using amplify to slow down bluedroid_timer would help, it would probably have adverse effects though.
[Nexus 6  Original Android Development] Imoseyon:
This doesn't apply to leanKernel, which uses stock thermal code. But if you guys are coming from one of these custom kernels with thermal tweaks - make sure that they didn't disable any ROM thermal components like thermal-engine.
[Nexus 6  Original Android Development] slekkas:
So why are so many of us have this problem? [emoji20]
[Nexus 6  Original Android Development] dcd17:
I was on N-N-8-8, I just switched to N-N-1-1 to see if it has any effect. If not, I'll go to Y-Y-1-1, but I'd swear I wasn't having bluedroid_timer issues on 1.13.
[Nexus 6  Original Android Development] akellar:
I have had bluetooth on consistenly and watch connected the whole time. My longest wakelock for bluesleep is 65 seconds. That is not an issue. Again, please post data to go along with "huge wakelock issues". Nobody can know if you are actually having an issue or just that your definition of huge is misinterpreted.
[Nexus 6  Original Android Development] Imoseyon:
Not sure. I'm not even sure how prevalent this issue is. I haven't heard about it until very recently - I wonder if there's a reason why there's a sudden surge of reports.
[Nexus 6  Original Android Development] slekkas:
I hope it's not a hardware issue...

I just installed elementalX latest update to test. I'm at 14% battery now. I will drain completely and let you know.

My battery and overall phone experience finally is great with your latest kernel and wakelock tweaks. Is just my luck that always something has to go wrong [emoji2]
[Nexus 6  Original Android Development] Imoseyon:
Are you saying it was reproducible every time on my kernel? I certainly hope that's not the case - I haven't run into this myself. Plus if that's the case we'd have a lot more reports.
[Nexus 6  Original Android Development] slekkas:
I'm not saying that. I've had it with Franco kernel as well. There was some kernel versions that caused the phone to shut down at 5% and some others at 17% . I drained it 3-4 times just to make sure it always shut at the same percentage and it did. Now about the battery reports not a lot of people drain their phone that much I suppose. Like you said you need your phone for work so you make sure you charge whenever you get the chance. Soon we will know. With your latest test version the phone shut down on me 3 times. Now I'm 11%.
[Nexus 6  Original Android Development] Franzie3:
everyone gotta be a crackflasher.....I personally havent not seen this issue and I have only used your kernel. I tried elementalX but that was very early on and I did not such tweeking. i too will test this theory and see if i can get a drain all the way to 1%
[Nexus 6  Original Android Development] old_fart:
Even if the kernels are supposed to be swappable and play nice together . . . I'm guessing that they ( different kernels ) can and will mess with each other through the shared areas. System ? Ram drive ? It is fortunate that a 'total wipe' takes minutes !
[Nexus 6  Original Android Development] dcd17:
I'm at 51 minutes for today.
[Nexus 6  Original Android Development] akellar:
How's that relate to deep sleep? Meaning, this is a wakelock that will occur at any time. Doesn't necessarily mean it's been keeping your device awake that entire time. Lots of notifications? Google fit active? There's a lot of things the watch syncs back to the device for. Wakelocks aren't inherently bad.
[Nexus 6  Original Android Development] wind784:
I usually don't let my phone go past 10% before charging, few times I did it was on Franco, phone would always turn off at 5% and be unable to turn on with the battery indicator popping up drained. Haven't tried with stock kernel or this, just odd that I found at 5% it would shut down and remain off until plugged in or charged.

I assumed it was a moto feature to prevent damage from excessive battery depletion, due to mine always occurring at 5%. Odd to see reports of numbers higher than that, 17% in one comment, something is up.