yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] mugendon:
The wakelock is not nearly as bad as the sensor_ind was. I am like 95% on 2g with perfect signal and after two days getting about 1 hour of wakeup time because of it. It is just the last little thing which makes my awake stats a little more longer than screen on time.

So if it can be reduced it is nice to have and no other wakelock to kill is left. If not I won't mind because bartery without sensor_ind is awesome already :)
[Nexus 6  Original Android Development] daleski75:
I have the same issue so doing a personal build of Euphoria for today 12/02 and going to flash 1.13.2 again to see if it fixes it also by some chance do you lose root as well?
[Nexus 6  Original Android Development] SilkyJohnson:
http://goo.gl/2AkOGp

Sent from my Nexus 6
[Nexus 6  Original Android Development] jackpollard:
[MENTION=3357040]Imoseyon[/MENTION]; I've attached 2 screen shots from before and after I flashed the test build I had just turned on my phone so they are both roughly 25 minutes worth of test No issues with anything on the build
[Nexus 6  Original Android Development] cam30era:
FWIW: I'm on stock ROM like you. Running 1.13. And I can access my SD card via Windows File Explorer. And ADB devices recognizes my device. Only apparent difference is my N6 is rooted. It must be something on your end.
[Nexus 6  Original Android Development] supercluver:
[MENTION=3357040]Imoseyon[/MENTION] I'm on Stock 5.0.1 and the computers I'm using are both running windows 7. [MENTION=1637948]daleski[/MENTION] glad to hear it isn't just me, and I'm not actually rooted. [MENTION=3209971]cam30era[/MENTION] I'm guessing it is something on my end, but I haven't really done anything that should mess this up. And if I simply flash a different kernel (franco for instance) then it works. I flashed [MENTION=220328]paulobrien[/MENTION] MCR mod, but I did that before I even tried leanKernel and didn't see this issue. And that mod is systemUI, so I wouldn't think it would break something like my USB.

Imoseyon, one thing I noticed. If I'm on leanKernel, and I'm in the bootloader and I type 'adb devices' it doesn't return anything. Just a blank response, not device not found like I would think. On a different kernel if I do the same it returns my device serial number... Any thoughts?

FWIW I'm still running leanKernel 1.13 and it is great, best battery life I've had, and I don't really use/need USB all that often so at least I'm lucky that way.
[Nexus 6  Original Android Development] cam30era:
If you are in the bootloader and type ADB devices, you will get the response, "waiting for device" on any phone/rom/kernel. In bootloader you have to type fastboot devices. ADB devices only works if you are booted up or in recovery.
[Nexus 6  Original Android Development] supercluver:
Strange, I could swear I typed adb devices and got a response of the serial number on a different kernel, and a blank response on LK. I don't know, I'll check it later, but thanks for the info.
[Nexus 6  Original Android Development] inzaghi75:
If I enable faux sound via terminal must I reboot my phone?
[Nexus 6  Original Android Development] italia0101:
Considerable drop in the msm_hsic wakelock for me on that test build, my deep sleep has crept into the 92%s . looking great!
[Nexus 6  Original Android Development] wrongway213:
Any other effects? How's mobile data?
[Nexus 6  Original Android Development] italia0101:
So far can't see any, i'm on mobile data constantly too, its not gone completely which is probably a good thing, but right now my idle drain right now is 0.7%
[Nexus 6  Original Android Development] wrongway213:
Awesome news, been on here alot the last day so out of thanks, but thank you for informing me.
[Nexus 6  Original Android Development] __NBH__:
Been running the test kernel since this morning and the wakelocks are definitely lower according to BBS. However I don't really see any improvement on battery life, I normally get 1hr screen on doing general things like XDA, Facebook etc from 14-15% battery and it's still about the same.

Msm hsic wake lock was 15 mins from 2 hours off charger on the old kernel, now it's 13 mins from 7 hours.
[Nexus 6  Original Android Development] italia0101:
Its going to help the idle time if anything imo, not really screen on time.
[Nexus 6  Original Android Development] wrongway213:
Idle time is my concern - sounds like it should help that a lot as mentioned in the post above.
[Nexus 6  Original Android Development] franciscofranco:
The thing is that having a very high wakelock count doesn't mean it's bad for your battery life. There is a difference between constant 2h straight wakelock being held, and a 2h wakelock count. The first will rape your battery life since it keeps your device awake for a constant 2h period, so no suspend at all, most hardware internals are not on power saving. A 2h wakelock count is different, it can mean that, for example, the lock can simply held for 1s each time it's requested, but then the device goes back to suspend.

It's important to know the difference. Simply reading the wakelock period isn't enough to see the full picture. Obviously less time wakelocked is good, but most of the time, if a lock is being held, there must be a reason for that, unless it's a blatant bug like the sensor_ind being stuck forever.
[Nexus 6  Original Android Development] __NBH__:
My usage was fairly normal, 1 hour screen on time from 7 hours so 6 hours standby time, if there was any battery saving it's very minimal so far
[Nexus 6  Original Android Development] wrongway213:
I think the point is it isn't gonna change SOT, it's not meant to. It is meant to reduce idle drain..
[Nexus 6  Original Android Development] Imoseyon:
Sounds like I'm somewhat on the right track with respect to the wlan and the hsic wake sources. The nice thing is that those two wakelocks are now (almost) infinitely user configurable/adjustable - more on this later. :)

I looked at the code for the hsic wakelock. It's doing what it's supposed to do - it's holding the wakelock when it needs it and releasing it when the phone suspends. So I suspect that something else is causing this component to misbehave and misuse the wakelock. Either way, by making this wakelock user-configurable and adjustable, we should be at least be able to workaround the issue somewhat. I would not disable this wakelock completely.

Another note about kernel wake sources in general. There are a ton of these wake sources scattered throughout the kernel and the ROM. Do you think all these kernel and ROM programmers coordinate with each other and makes sure that they all play nicely with each other (and with the phone)? I think not. This has obviously not been an exact science, and that's why you see that disabling wakelocks like sensor_ind and smb135x do not have apparent drawbacks.

I did mess with adb quite a bit in my ramdisk to get insecure adb to work exactly how I wanted it. I think a side effect of my change is that it requires root. I will revisit that implementation at some point because it could ultimately prove to be more troublesome.

You shouldn't have to...
[Nexus 6  Original Android Development] djcsurf:
Couple of quick question please,

I just flashed latest version after a full wipe and clean install of AICP using f2fs recovery.

I checked in settings under security and it still says phone is Encrypted, do I need to format data again and reboot to unencrypt?

Will my file system now be f2fs?

TIA
[Nexus 6  Original Android Development] warrenis1234:
this is from bed time at around 4a to wake up at around 10a. 1% drain with only data on (3g) but WiFi off when screen off

still a bunch of wakes seemingly from powermanagerservice and msm, but of course that's fine if its only 1% drain
[Nexus 6  Original Android Development] smclaughlin3:
Im going to add to the positive consensus...msm wakelocks have gone down to 8-10min compared to 30-50 min the question for me is ok what does this mean for me?

For some reason i notice faster internet

Less drain on standby

Better battery life overall

Powermanager service is there but i guess that ones necessary?

Will continue observations..........

---------- Post added at 05:32 PM ---------- Previous post was at 05:31 PM ----------

Oh forgot better overall signal in an otherwise bad signal reception experience....
[Nexus 6  Original Android Development] garyd9:
[MENTION=3357040]Imoseyon[/MENTION]

Decided to play with 1.13 this morning (I don't know why.. I think I was on 1.9 previously) and had what appeared to be a "soft" reboot a couple hours later. (Using google's stock firmware w/ root and a screen density change...) I say a "soft" reboot meaning that I saw the google boot animation, but it didn't appear that the kernel itself rebooted. (dmesg didn't show a kernel start, there was no google logo before the animation, etc)

I'd tell you my lkconfig settings, but the truth is that I haven't touched them. Whatever you set as defaults is still there.

I had just backed out of the google play store app and started google's newsstand app (while on LTE data - wifi/bt turned on, neither connected) - and boom.. instant boot animation (not even the google logo.)

I haven't been able to repeat it, but will keep an eye out.

Something else that's bothering me is that settings->battery is only showing the graph and "battery usage data isn't available." At the same time, BBS is showing data just fine.
[Nexus 6  Original Android Development] wrongway213:
You will definitely need to format userdata to decrypt as you are definitely encrypted if it says encrypted. However, I cannot speak for f2fs recovery, so I do not want to advise as I may end up steering you wrong, but yes, you will need to format your userdata to decrypt your device.
[Nexus 6  Original Android Development] warrenis1234:
"If you suspect a misbehaving app on your device, check for the*PowerManagerService*listing. This is a catchall for so-called partial wakelocks caused by apps. Rooted users can see the partial wakelocks in the app, but everyone else will have to do some detective work by comparing recently installed apps and the onset of thePowerManagerService*issue.*"

I remember reading this a while ago in my research.. is it relevant at all? lol
[Nexus 6  Original Android Development] smclaughlin3:
Wondering if the reduction of these wakelocks is where the benefit lies, like is the greedy wakelock time a bug if so imoseyon is causing more efficiency?
[Nexus 6  Original Android Development] madAdam6LOVE:
I also had a problem with 1.13 that I haven't had on 1.12.

I'm running stock ROM, and before installing LK I would get random reboots and also Gmail would freeze quite often.

I started running LK and no more RRs and Gmail ran perfectly, until 1.13.

Trying 1.13.2 tedt build, so far so good.
[Nexus 6  Original Android Development] Franzie3:
Dude....how are you not working with Google right now making the stock kernel....they need to pay you that kanye west yeezy shoe money....(sneaker heads will know what i mean)
[Nexus 6  Original Android Development] wrongway213:
If he wasn't an actual Linux developer I'd wonder this myself :p
[Nexus 6  Original Android Development] abrsea:
wlan_rx

First off, I want to say that this is an INCREDIBLE kernel. I installed this kernel the instant I got my N6 and I plan on staying on it for the foreseeable future! Thanks for the hard work :good:

Currently, I am on 1.13 and it is solid. I read about the test build 1.13.2 disabling (or drastically reducing) the wlan_rx wakelock. Can this affect hotspot tethering? I use it almost every day and this is usually my top wakelock for that reason (I think...). If you aren't sure, I can test it and let you know my results if that would be beneficial in any way!
[Nexus 6  Original Android Development] spinkick:
if he were working for gewgle he'd probably be hamstrung and not allowed to do the optimizations that he does. They would have to validate every single change with tests...tests....tests... and progress would be incredibly slow. At least, I would think this is how it works.

---------- Post added at 02:36 PM ---------- Previous post was at 02:35 PM ----------

I would like to know this too
[Nexus 6  Original Android Development] Franzie3:
I only say that because i know most of the good security experts have been picked up for those great jobs. I know geohot did once he rooted the S5. but seriously the optimizations that most of the nexus kernel devs (not just imoseyon, but even franco and Faux too) have done huge things. And alot of this recent work with the wake lock clean up has me thinking that google is eventually looking and will implment some of this stuff themselves if not now then in future developments maybe with project volta which was supposed to save so much battery.

Anyway, enough banter.... back to regular programming....lol
[Nexus 6  Original Android Development] wrongway213:
Good point about geohot - I know if I was Google I'd be watching this forum like a hawk for possible employees.. some of the more experienced developers on here are definitely more skilled than a lot of the people Google is currently employing.. those of us who have seen bugs in stock that devs have squashed for us can attest to that.
[Nexus 6  Original Android Development] rauschkugl:
Well maybe that's true but it's something different to write a kernel from scratch than improving a given source. We really have great devs on XDA but you shouldn't underestimate the Google devs.

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6  Original Android Development] franciscofranco:
No one writes a Kernel from scratch.
[Nexus 6  Original Android Development] arcanexvi:
Well someone did at the start ?
[Nexus 6  Original Android Development] spinkick:
one does not simply.... :D
[Nexus 6  Original Android Development] ezy1022:
So when I flash the regular stable v .13 everything works fine, however when I flash the over clocked version after it boots I will get system has stopped and acore process has stopped and a bunch of other things...I'm running sinless ROM.

Any help on how to get that oc'd version to run smooth would be appreciated

Sent from my Nexus 6
[Nexus 6  Original Android Development] mrizvi66:
just installed v1.13 let's see if this changes anything.

for some reason my battery life has gone to crap...i'd get like 1.5 hrs SOT and and be at like 50% battery remaining.
[Nexus 6  Original Android Development] rauschkugl:
Yeah it was magically there without anybody doing something.

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6  Original Android Development] wrongway213:
Great point.. I would never have thought of it that way, but simple logic tells me you're absolutely correct.
[Nexus 6  Original Android Development] rub1k:
Been a while since I switched kernels frequently, so I forgot... if I want to switch from FK to leanKernel, should I flash the stock kernel first or is it safe to go straight from FK to leanKernel?

Thanks in advance.

EDIT: Nevermind, flashed stock kernel first just in case. Please ignore.
[Nexus 6  Original Android Development] Cy_n_ic:
And from upon high, the lord sayeth let their be kernel! And it was good.
[Nexus 6  Original Android Development] nobnut:
It may have been good, but it was still an alpha release :p
[Nexus 6  Original Android Development] jackpollard:
For next time, no need to flash stock, just flash whatever kernel you want.
[Nexus 6  Original Android Development] ezy1022:
So is anyone able to run the over clocked version without any system ui or other apps stopped errors? It happens every time I reboot and then eventually calms down

N6
[Nexus 6  Original Android Development] Imoseyon:
Warn boots are always tough (for me) to troubleshoot, since typically they're not caused by the kernel and you won't see any pstore/crash logs. Next time see if you can spot anything out of ordinary in dmesg when it warm boots? Better yet try to catch logcat in the act. :)

As for battery settings, that's strange, I don't think I've run into that myself.
[Nexus 6  Original Android Development] cavalier11:
First, thanks for the great kernel. It's by far the smoothest and battery friendly one I've ran so far. I'm having an issue with v1.13 which I also had issue on v1.11, but it disappeared on v1.12. Whenever I enable fauxsound and use his app to increase the headphone gain, the sound goes in and out constantly. I'm running stock Rom and tried flashing the lkconfig cleaner, and then the kernel again but I'm still having the same issue. When I flash faux kernel, the issue goes away and everything works properly. Has anyone else experienced this problem?
[Nexus 6  Original Android Development] Imoseyon:
Hmmm did you enable faux sound via lkconfig? It comes disabled by default on leankernel.
[Nexus 6  Original Android Development] cavalier11:
---------- Post added at 09:53 PM ---------- Previous post was at 09:52 PM ----------

[/COLOR]

Yea, did that first then installed the faux sound app and made the adjustments.
[Nexus 6  Original Android Development] Imoseyon:
Darn ok I will see if there's anything I can do to reproduce this on my end without the faux app.
[Nexus 6  Original Android Development] bigant262:
If I choose option 3 in core config in lkconfig, are all 4 cores supposed to stay on all the time? Reason I'm asking is because I flashed the latest build of Euphoria and when I choose option 3, all 4 cores online and no cpu boost, 2 of the cores are offline, but when I flash lk kernel by itself, all 4 cores stay on.
[Nexus 6  Original Android Development] garyd9:
It's not just you. They are a royal PITA to troubleshoot without being able to repeat. So far, no repeat. Perhaps a one-off thing. As I said, I'll keep an eye out for it. (Ironically, I might actually put in the AT&T boot sound just so I know if it reboots again.. I'm usually not staring at my phone.)

After leaving it off the charger last night, the battery data seems to have come back. Seems odd that it was gone for about 90 minutes after removing it from the charger last time, but I've been so damn busy lately that I might have missed something obvious.

Thanks - and take care

Gary
[Nexus 6  Original Android Development] italia0101:
So a little update on the latest test kernel :

Wakelock time held:

1.13.1 - 6 hours 17mins

1.13.2 - 26mins

Over a days usage on both, around about 25 hours,
[Nexus 6  Original Android Development] beyeond:
Apologies for the off topic question, but I was hoping someone might be able to assist... I use Swype but every time I set it as the default keyboard, it reverts back to google keyboard once I open the keyboard. Anyone else have this issue?
[Nexus 6  Original Android Development] natezire71:
Nothing to do with LK.

However, you could try disabling the Google Keyboard.
[Nexus 6  Original Android Development] wrongway213:
WOW - dramatic reduction. Still no other noticeable effects (mobile data, etc.) other than just lower wakelock? Has your idle drain improved significantly? That's a much larger reduction than I had expected to see..
[Nexus 6  Original Android Development] italia0101:
Haven't seen any negative effects [emoji4], yea seems to help idling the most, stays in deep sleep for longer and loses less juice, doesn't overall help with SOT, but then I didn't really expect it to. Screens still the biggest overall killer.
[Nexus 6  Original Android Development] djcsurf:
I tried 1.13 yesterday and was very happy with out :D

When I installed a theme I got systemUI fc. I read around a little and it appears (but may be wrong) to be a problem with some custom kernels compatibility with the theme engine.

Is there any workaround or possible fix without reverting to stock theme.
[Nexus 6  Original Android Development] wrongway213:
Download SELinux Mode Changer from the Play Store and change from enforcing to permissive. leanKernel is fully theme engine compatible.
[Nexus 6  Original Android Development] djcsurf:
Thanks,

It's getting a regular occurrence you answering my post's :)
[Nexus 6  Original Android Development] wrongway213:
You'll have that - I'm not one of those "you didn't search/read every single post, you don't deserve to know the answer types" - when I came to XDA I did not even know how to root with a one click tool. Unless the question you are asking has been discussed in the preceding several pages, is very very common knowledge or is in OP, I will generally always just answer people's questions if I know the answer, as I am not a developer and that is my way of giving something back to this community that gives so much to me and to others around me and asks nothing in return.
[Nexus 6  Original Android Development] lifeisfun:
I was pleasantly surprised that S2W is implemented on this kernel but sad to discover that S2S is not :( Any chance this will change in the future?

Thanks
[Nexus 6  Original Android Development] ezy1022:
I get the system ui fc only when I use the over clocked kernel version, its very frustrating and I can't figure out what is changing that is causing it

N6
[Nexus 6  Original Android Development] Mistertac:
Pretty sure he's exploring the possibility of adding S2FUD ( Sweep To Format User Data )

... Coming to a Kernel near you...
[Nexus 6  Original Android Development] Imoseyon:
If you're getting FCs on CM's theme engine, and if you're somewhat proficient with grabbing logcat/dmesg, please contact me via PM or email (@gmail.com)? I'm going to see if I can figure this out once and for all without having to flash CM myself. It would be nice to get it working without having to put phone in permissive mode.

S2S is actually supported but not via lkconfig. I think there are apps like trickster that can configure s2s....

I have no idea what's going on here. The only difference between ocuc version and normal version is the addition of the new frequency slots. Limit min to 300mhz and max to 2.6ghz, and see if it continues to happen?

[MENTION=5500746]Mistertac[/MENTION], how did you get your username to show up in green?
[Nexus 6  Original Android Development] PeenX2:
3 wakelocks killed with no ill effects. msm wakelock barely is even on anymore, and still get great signal.
[Nexus 6  Original Android Development] lifeisfun:
Thanks for the reply!

I'm using Trickster, and enabled S2W+S2S but only S2W is working for me.
[Nexus 6  Original Android Development] wrongway213:
I might be able to try to replicate the error a bit later - are you just looking for systemui fc's or failed to install theme in enforcing erros, or both? I have been experiencing both intermittently since I switched to enforcing on 1.13 but thought it was normal so I just set back to permissive.. if you are looking to replicate certain behavior I could probably do it for you. I get errors installing themes in enforcing (some themes, sometimes) and also some systemui FC's - you want logs of both or just themes failing to install?
[Nexus 6  Original Android Development] Imoseyon:
Yeah I'm seeing the same. On v1.13.2, wlan_rx_wake and msm_hsic_host drastically reduced with no ill effects. I may leave it like that for v1.14, but will test for a day or two more first, especially hotspot tethering.

The cool thing will be that it's going to be adjustable so you can reduce the wake times even more if you want to or easily revert to stock.

I remember someone saying that S2S is tricky. You need a rather specific motion to trigger it...
[Nexus 6  Original Android Development] Imoseyon:
Yeah i'm looking for specifically SELinux related messages, especially if you suspect that the problem is fixed by going permissive. First put the phone back in enforcing mode, then:

adb shell dmesg | grep avc

or

adb logcat | grep avc

(or any other method you may have in grabbing those logs is fine).
[Nexus 6  Original Android Development] lifeisfun:
Interesting, didn't think of that since on ElementalX it was working fine.

I'll check

Thanks