yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] magnum870:
I have been running it for a day and a half. I had noticed over the last week and a half before this latest test that I was getting a max of 2.5 hrs screen on time, but never looked at wakelock sources. Just for fun I flashed the test yesterday when I was at 75% battery and then got 3.5hrs screen on time after. Today has been great too, already with 2.5 hrs screen on time (60% battery left). So apparently I suffered from the issue many people have been mentioning without me knowing it haha.

All things seem to work for me too. Ambient, Google now at all times, etc. Thanks for the work you do! Its been fantastic.
[Nexus 6  Original Android Development] rignfool:
[MENTION=3357040]Imoseyon[/MENTION]

Would it be possible for you to work your selinux magic for Viper4Android?
[Nexus 6  Original Android Development] Imoseyon:
I don't know anything about viper4droid. What's going on? you have to put selinux in permissive mode to get it to work?
[Nexus 6  Original Android Development] merouleau:
I'm running ViPER4Android. I installed SELinuxModeChanger from the Play Store and used it to set permissive mode. I guess it would have been easier if LK had a way to do that.
[Nexus 6  Original Android Development] rignfool:
Yes sir... There's more as well... But it requires a permissive kernel to work
[Nexus 6  Original Android Development] smclaughlin3:
Turned off mp decision in terminal command with lk config , but had to turn it off In trickster mod too is this normal? Also I always thought there had to be an alternative to mp decision to turn it off what's the alternative here? Thanks ...I'm always trying to learn,apologies if redundant
[Nexus 6  Original Android Development] Imoseyon:
Link me to the apk or the xda thread for viper4android?

You want to restore your mpdecision settting in trickster (re-enable it) before you run lkconfig core control.
[Nexus 6  Original Android Development] rignfool:
http://xdaforums.com/showthread.php?t=2952137
[Nexus 6  Original Android Development] Imoseyon:
Ok try v1.12.7 in the testbuild folder?

viper4android is pretty cool - what advantage does faux sound have over this?
[Nexus 6  Original Android Development] rignfool:
Its a little late for me to be making noise tonight... I'll try tomorrow and report back unless someone beats me to it
[Nexus 6  Original Android Development] resynx:
Just flashed v1.12.7, hoping to see death to sensor_ind XD
[Nexus 6  Original Android Development] Imoseyon:
Ah v1.12.7 has sensor_ind wake source enabled by default - you need to run lkconfig to disable it.
[Nexus 6  Original Android Development] frenchy714:
If using option 1, is flashing the nofreqmpdecision zip still required if you don't want freq's to jump around?

I pooped my pants once, it's a long story....
[Nexus 6  Original Android Development] buggerthis:
Viper4android is incredibly cool.

Will it work on 1.12.7 without the need for the selinux mode changer app?
[Nexus 6  Original Android Development] Damon13:
I am Wondering the same thing as frenchy174, If we choose option 1 or 3 do we still need to flash nofreqmpdecision zip still as to avoid freq from jumping around?
[Nexus 6  Original Android Development] wrongway213:
No, you don't. LK Core Config options replace the no-freq-mpdecision zip as the way to natively disable mp-decision from Lean Kernel without a hotplug replacement needing to be added to make it stick.
[Nexus 6  Original Android Development] jackpollard:
Imoseyon you asked; "viper4android is pretty cool - what advantage does faux sound have over this?"

V4A is more a fully featured equalizer, it has a very nice feature where you can load pre-set eq settings to get different sounding playback. They have 100's of these .irs file. They really work excellent, you can everything from a Teac tube sound to expansive crystal sounds with extra bass.

It's one of the most feature rich sound enhancers i've used. It does need permissive.
[Nexus 6  Original Android Development] wrongway213:
Does the change you made simply set kernel to permissive by default, or is there more to it than that? I'm a V4A die hard so I always set kernels to permissive with SELinux Mode Changer, however if there's more to what you did I am quite curious. V4A has quite a few strange little quirks on Lollipop.. wondering if the change you made could allow it to process outside of compatibility mode or if it simply makes the kernel permissive so you don't need the app.

As for your question, it's a sound mod that seems to defy hardware limitations. It basically makes my car sound like I have a system in it on stock speakers, the enhancement is that strong - no other sound mod I've tried compares and are actually so far off the mark they generally somewhat irk me due to inferiority.

This explains what it is quite well... I elaborated a bit in my post because the main difference compared to say, AudioFX, is the intensity of the sound modification. AudioFX is a 2 at absolute best to V4A's 10, no exaggeration at all.
[Nexus 6  Original Android Development] Imoseyon:
v1.12.7 should not require permissive mode for viper to work. Give it a shot.
[Nexus 6  Original Android Development] smclaughlin3:
This is what I got after going back into trickster and reenabling mp decision and then running lk config to choose option 1. What should I do it gives error?
[Nexus 6  Original Android Development] wrongway213:
Two questions:

Are you just gonna fix everything on this device? Can Google just let you design the next Nexus so we can avoid you fixing everything?

More serious note: Is this something you'll include in future releases like the sensor_ind wakelock disabler, or just for the test kernel? This kernel just gets better and better...
[Nexus 6  Original Android Development] merouleau:
Under 1.12.1 with V4A installed and SELinuxModeChanger set to Enforcing, Google Play Music will not play music streams. Under 1.12.7, it works like a champ. Guess I can uninstall SELinuxModeChanger. :)
[Nexus 6  Original Android Development] Imoseyon:
When you re-enable mpdecision in Trickster, it doesn't actually re-enable until after you reboot. I'm not sure if that was intentional or a bug.

Haha. Everything in v1.12.1 and v1.12.7 should go in the next release (v1.13). I'm still trying to decide whether I should disable sensor_ind by default or not (it's already a configuration option in v1.12.7).
[Nexus 6  Original Android Development] smclaughlin3:
OK even with the error I'm good to go if I reboot ? Any way I'll reboot and see what happens. Thank you probably have to redoit after flashing you newest kernel anyway?
[Nexus 6  Original Android Development] slekkas:
If you could really find out if something is broken or not with sensor_ind disabled than it would be easy to decide. I've been testing it from day 1 you released it and I can't find anything broken but I don't use ambient display or hangouts. Someone with this setup should tell us if something has been malfunctioning. If not then you should just have it disabled by default.
[Nexus 6  Original Android Development] arcanexvi:
I haven't had any issues with my setup. Ambient on.
[Nexus 6  Original Android Development] wrongway213:
Excellent news. I would suggest making it an option until we figure out definitely what exactly the wakelock does, as there will probably be people who will be OCD about it and worry.. if you can't take the six extra seconds to use lkconfig you can deal with the wakelock and I won't feel bad for ya:p However, once we know what exactly it is, I say kill it with fire and never look back. That being said, should you choose to just kill it entirely I won't be complaining, just think others might be is all.

Edit: Or possibly disable by default with the option to enable.. that may satisfy everyone.
[Nexus 6  Original Android Development] tysonwald:
Disable by default please. I've seen no I'll affects. I've tried ambient display and adaptive brightness. All seems fine.
[Nexus 6  Original Android Development] smclaughlin3:
Viper4android!

[MENTION=3357040]Imoseyon[/MENTION]

just tested viper4android on my lg bluetooth headphones and it works! dude! no need for an app!. dont have a choice now but to stay on leankernel as no other dev has managed your level of awesomeness, what can i say. and am thinking about setting up donation just because i try to be a conscious person,either way thank you!

and by the way love the terminal options. not to mention my gf is running leankernel on the note 3 i passed down solid!
[Nexus 6  Original Android Development] kmaner:
I am also a V4A user and this is just awesome! Thanks for LK it is the best.
[Nexus 6  Original Android Development] j.bruha:
I swore I saw somewhere that this feature would require a ROM that supports init.d support but I can't find where I read that both here or in the Reddit post about this. Can someone confirm or deny whether or not that's true? About to start from scratch today and will be basing my ROM choice on the ability to use this kernel and feature.
[Nexus 6  Original Android Development] tysonwald:
Today i tried a different kernel and boom sensor_Ind came back and has been going for hours. Going to be flashing lk again. Thanks for that fix!
[Nexus 6  Original Android Development] wrongway213:
I can't confirm or deny, but I can tell you there's an app on the Play Store called Universal init.d that allows for you to test if your ROM nd kernel have init.d support. If they don't have it, the app allows you to enable it.
[Nexus 6  Original Android Development] nobnut:
What?

This kernel supports init.d. The ROM is irrelevant.
[Nexus 6  Original Android Development] wrongway213:
I thought the same until I saw the vomertweaks conversation in the Franco Kernel thread. FK also has init.d, but for certain ROMs vomer suggests people use universal init.d.. definitely not a kernel issue as that script is only for Franco Kernel. I don't know quite how it works, but I have tested myself when on FK and some ROMs had init.d support, others did not on the very same kernel. I would imagine that app would only work on a kernel that has init.d support, but I could be wrong there, just speculating.
[Nexus 6  Original Android Development] Imoseyon:
init.d support is built into leanKernel but it does need a valid busybox install. Most (if not all) ROMs should have busybox as part of /system. If not you can just install busybox from play store.
[Nexus 6  Original Android Development] beyeond:
msm_msic_host just started killing me out of nowhere today. Last night I (re)decrypted, wiped, and flashed a Slim build with newest LK. Not sure what changed but my phone had been sleeping like a baby.
[Nexus 6  Original Android Development] wrongway213:
I believe flashing the latest radio should fix this unless you simply have poor signal, IIRC.
[Nexus 6  Original Android Development] grayskul:
Where's the latest radio at?
[Nexus 6  Original Android Development] frenchy714:
I've been running the latest test kernel with sensor_ind disabled for the better part of the day and I use both hangouts and ambient display, and haven't had a single issue; everything is working as intended.

On another note it felt good uninstalling SELinux Mode Changer. ;)

I pooped my pants once, it's a long story....
[Nexus 6  Original Android Development] Smallsmx3:
[MENTION=3357040]Imoseyon[/MENTION] do you have encrypted data? I've been decrypted since the beginning and I'm thinking of encrypting. Your kernel has some patches that increases I/O? I honestly don't think I'll even notice a difference
[Nexus 6  Original Android Development] rignfool:
I was in unencrypted... Flashed haphazardly... Wound up encrypted... Haven't cared since...

Boot up to system or recovery have slowed by enough for me to notice... That's the only difference....
[Nexus 6  Original Android Development] Imoseyon:
I've been encrypted ever since I accidentally encrypted a couple of weeks after I first got the phone. I think performance is good enough especially after the performance enhancements I've made to encrypted i/o, but it's still not going to be as fast as unencrypted.
[Nexus 6  Original Android Development] arcanexvi:
I've basically had the same experience. Accidentally flashed stock kernel and ended up encrypted. Haven't looked back.
[Nexus 6  Original Android Development] TJKV:
Hi! Would you mind pointing me to the commit(s) that enable this? :) I would like to see if I can hack them into the kernel I use and compile it for myself (franco, on hammerhead) :p
[Nexus 6  Original Android Development] PhilDX:
http://xdaforums.com/nexus-6/general/ref-nexus-6-modem-collection-t2969380
[Nexus 6  Original Android Development] jackpollard:
Using v4a with 1.12.7 and its working Great! No doubt the best kernel I've used.
[Nexus 6  Original Android Development] smclaughlin3:
I'm not sure what is wrong it won't stick max at 2649 now. I enable mpdecision than went into lkconfig and chose option 1 also am at performance in lk config anyone know why I'd thus happening to me? Thanks
[Nexus 6  Original Android Development] buggerthis:
It's because low battery.

This has happened to me before. I don't think it has anything to do with the kernel. Charge up past 20% or 25% and check again, everything should be back to normal.

---------- Post added at 11:56 AM ---------- Previous post was at 11:50 AM ----------

Has anybody ever told you that you're an amazing dev and a generally really cool guy?

Mosey on, dude, mosey on.
[Nexus 6  Original Android Development] smclaughlin3:
Cool your right just charged full 28 percent toggled the hell out of it and it stayed on 2649 for max. Just to be clear having mpdecision enabled within the trickster app with that option 1 in lk config is normal? Toggling mp decision off in the app is incorrect just get confused sometimes when I know mpdecision is disabled and not scaling anything but enabled in the trickster app. Thanks. It could be that its late lol
[Nexus 6  Original Android Development] dorioo:
OMG. I've been reading it as: E-mo-sai-on all this time.

I can only see "I mosey on" now. Fantasy shattered but you're absolutely right.
[Nexus 6  Original Android Development] Fauert:
Hi, can i use the "lkconfig_cleaner" too clean up, before flashing new kernel ?
[Nexus 6  Original Android Development] grinchyyy:
Could the sensor_ind have anything to do with keeping Ambient Display from turning on when the phone is in your pocket?

I use Tasker to log in pocket screen on instances and the amount of screen on while in pocket is much higher since flashing the test build.

I use dt2w as well, maybe it's just the pants I'm wearing ?
[Nexus 6  Original Android Development] mugendon:
I don't think so, because sensor_ind is no problem for me when ambient display is on, but will arise when ambient display is off.
[Nexus 6  Original Android Development] mclisme:
Has 1.12 got any tweaks that prevent face unlock during calls? I noticed this annoying behaviour hasn't shown up lately, or maybe it is random?
[Nexus 6  Original Android Development] grinchyyy:
I do think maybe it was just dt2w in combination with what I'm wearing and activity. Depending on the material that my pockets are made of and if my leg is a little sweaty it makes dt2w more responsive.

I switched to s2w and notice a considerable decrease in pocket events ?
[Nexus 6  Original Android Development] sn0warmy:
This was fixed a couple of revisions ago. I had the issue you are talking about but it was gone with 1.10 I'm still rocking 1.10 and loving it. I haven't switched to 1.12 yet, simply due to being lazy and having no issues to complain about.
[Nexus 6  Original Android Development] knitler:
I'm not sure if this is related to 1.12.1 or not, but after flashing to it when I turn my car off the audio from the Bluetooth then starts to play through the phones speakers instead of pausing like it should.

If I move back to 1.12 this stops happening. I am using Stock ROM. 5.0.1
[Nexus 6  Original Android Development] wrongway213:
I'm fairly confident a lot of instances of sensor_ind are directly related to phone call time - since I have been watching this wakelock I have observed that with ambient display on and adaptive brightness off, often times sensor_ind will kick on when I begin a phone call, and kick off right after it ends. It is not the only event that kicks the wakelock off, but I have not ever seen sensor_ind go above 32 seconds with adaptive brightness off and ambient display on, except during phone calls. It always, thus far, stops itself when the phone call ends. It seems the difference in call length and wakelock time is generally about 40 seconds, sometimes less but always under a minute. I have been using this config of ambient on and adaptive off for going on four days now and these observations have held true. It basically appears to keep my phone from deep sleeping during phone calls and nothing more with ambient display on and adaptive brightness off. I'm not sure what to do with this information, so I am sharing it in hopes that maybe this will be a jumping off point for someone else.

Also, man is having V4A in enforcing awesome!

Edit: I did not specify, but just so there's no confusion, this wakelock does not occur every time I have a call. It's simply that it seems to be triggered when I do on certain occasions, and to end when the call ends. It seems to me that sensor_ind kicks on for extended periods of time much more frequently with longer conversations. If I'm on the phone for longer than like 5 minutes, it often holds awake for the length of conversation. On the other hand, for instance, my last call was about 3 minutes long.. only registered 4 additional seconds of sensor_ind.
[Nexus 6  Original Android Development] rignfool:
What music app?
[Nexus 6  Original Android Development] Damon13:
I def agree with you, Sensor_ID seems to come to kick in once a phone call occurs, ambient display seems to be the key factor in the wakelock.
[Nexus 6  Original Android Development] spinkick:
Can you guys point me to some good settings for v4a? Also, i have to run it in compatibility mode to get it to play via google music. Do you guys? I dont want to take the thread too off topic, just pm if youd like
[Nexus 6  Original Android Development] knitler:
Google Music, which i just noticed was also recently updated, so it may just be the App and not the kernel, I'll install an older version of Google Music and test.
[Nexus 6  Original Android Development] sn0warmy:
For what it's worth, with version 1.10.1 of this kernel, I do not have that issue with Bluetooth and the latest Google Play Music. As soon as I turn the car off, the phone disconnects and the music does not start playing through the phone's speakers. I'm about to upgrade to v 1.12 but it looks like I'll be avoiding 1.12.1.

Also keep in mind that I do not tweak the kernel at all. So if you performed any tweaks, you may want to revert those first, before moving on to see if another revision corrects it.
[Nexus 6  Original Android Development] Imoseyon:
Yessir, but it's not necessary.

If this is true I think it could be good news for us. Sensor_ind couldn't be the only thing keeping the phone awake during phone calls and I can't imagine phone going into sleep during a phone call with or without this wakelock. Still it's probably worth testing some more.

I'll try to release v1.13 today and the changes will be up on my github repo. The fix is not in the kernel, but in the ramdisk.
[Nexus 6  Original Android Development] grinchyyy:
Xposed is coming...

http://www.androidpolice.com/2015/02/10/xposed-framework-android-5-0art-just-around-corner/
[Nexus 6  Original Android Development] sosquidtaste:
Wrong thread, mate?

Slightly more on topic, I'm excited to try out 1.13 whenever it's ready. I've missed the heck out of V4A, and am hesitant to use the SELinux switcher app out there just to get it working.
[Nexus 6  Original Android Development] Smallsmx3:
I agree... Could care less about xposed mess
[Nexus 6  Original Android Development] smclaughlin3:
Go to v4a thread look for an audiomod.zip that a user posted, it allows you to use v4a with any app i forgot to ask him where he or she got it from. if need be ill try and attach it after im not so busy.....
[Nexus 6  Original Android Development] Remoteconcern:
I think sensor ind wakelock probably gets triggered a lot, because it seems to be something needed to poll the sensors. I think it isn't released sometimes causing battery drain, but ambient display works to stop it because its consistently accessing the sensors and so it probably prevents it being held for a long time without being released. I'm not a technical guy, but that seems to make sense to me.
[Nexus 6  Original Android Development] wrongway213:
That.. actually makes a lot of sense to me. Assuming ambient display is disabled during phone calls, that makes a LOT of sense to me... I'm sure it's more technical than all that but based on the behavior I'm observing I could definitely, definitely see this being a simplified explanation for the issue.
[Nexus 6  Original Android Development] grinchyyy:
No, just excited. Thought maybe others might be interested in the news.

Yes, off topic sorry ?
[Nexus 6  Original Android Development] warrenis1234:
even with the sensor gone by using lean, I still get the Wi-Fi and data wakelocks

1. I've gotten less data msm host wakelocks by changing LTE to 3g. I rarely need that much speed when I'm on the road, the 8 to 15 mb down on 3g is more than enough and the 3g signal strength is so much better, dark greens on the battery chart

2. i basically turn the Wi-Fi off every time I turn off the device. the Wi-Fi off during sleep option doesn't seem to stop the wlan wakes. has anyone changed the Wi-Fi scan internal? changing it in the past had some odd results on it for me, like delayed messages
[Nexus 6  Original Android Development] Cy_n_ic:
Do you have scanning always available turned on in wifi settings? That will keep it active even when toggled off. Also if ur device switches back and forth between 3g and 4g alot thats the msm host wakelock. Really all u can do about that is what u did, keeping it on 3g
[Nexus 6  Original Android Development] Imoseyon:
v1.13 is up.

Notable changes are 1) controlling sensor_id wake source (via sysfs/lkconfig) - wakelock disabled by default, and 2) selinux fixes for viper4android.

Full changelog here: https://github.com/imoseyon/leanKernel-shamu/wiki/Lollipop-ChangeLog
[Nexus 6  Original Android Development] old_fart:
I have been seeing the same thing also. At work I get three to five bars, and then at home I get zed naught to one bar. I was 'trying' to get an app which will automatically kill / 'turn the cell radio power off' at all times that I am not at work . . . Still looking.
[Nexus 6  Original Android Development] tysonwald:
Thanks for keeping it disabled by default! Flashing now
[Nexus 6  Original Android Development] Damon13:
Thanks so much for listening to our petitions, This kernel is great with battery and Lkconfig is a great addition that compliments this kernel so well.
[Nexus 6  Original Android Development] franciscofranco:
People, I have to raise some awareness about the OP. He's a shady guy, you cannot trust him! I received this e-mail from him today:

How can you tolerate to use someone's work when he's trying to sabotage mine?

Treachery! Heretic!

/s
[Nexus 6  Original Android Development] Imoseyon:
LOL, you should use my kernel as your base! That will definitely fix some of your issues. :silly:
[Nexus 6  Original Android Development] kmaner:
Loving this kernel...no wonder others are envious...lol
[Nexus 6  Original Android Development] bigant262:
When I go to a new version, is there anything I need to do in lkconfig if I messed with some settings?
[Nexus 6  Original Android Development] Imoseyon:
You shouldn't have to. The settings will be retained in between versions, unless I made a bug somewhere. :)
[Nexus 6  Original Android Development] wrongway213:
I always have to reset min value in Trickster (not on boot, just when flashing a new version of kernel), lkconfig values all stick for me though.
[Nexus 6  Original Android Development] funcrusher:
I didn't start using lkconfig until a couple weeks ago, but I have to say, I love it. ;)