yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] gigi944:
DT2W

This kernel enables dt2w, but with this kernel the app WakeGestures says that wake gestures are not supported... how can I solve it? The feature that prevent the unlock when the smartphone is in your pocket (using the proximity sensor) is extremely useful... any suggestions?
[Nexus 6  Original Android Development] gitchrodd:
Everyonce in awhile I'm getting a bit of lag. When I checked log I got the attached.

Running temasek latest clean flashed and latest of blu
[Nexus 6  Original Android Development] eng.stk:
Thats normal, not an issue, just an info from mpdecison binary since service is disabled.

I only use stock ROMs and sometimes test out AOSP ones like Purity and PA. Can't replicate that.

Some people still have memory leaks in certain conditions, good news is that M is in a good path to improve that.
[Nexus 6  Original Android Development] Othoric:
Been bouncing around different kernels since Code Blue. Glad to see your back here on XDA. It's running very well and I couldn't ask for more. Awesome job!
[Nexus 6  Original Android Development] Clark Joseph Kent:
Enough. There will be no threats or invites for threatening. Now if you need to provide something for development, then provide it in a form of a logcat. Anything else, is just that, a post....

Thread cleaned and consider this a warning.....
[Nexus 6  Original Android Development] eng.stk:
I only use dt2w which is stock from Google, no other wake gestures.

You can enable it on Kernel Adiutor.
[Nexus 6  Original Android Development] gigi944:
Thanks for the answer.

Yes, I can enable from kernel Adiutor too, but if I would prevent the unlock when the phone is in my pocket, using the proximity sensor, how can I do it? :/
[Nexus 6  Original Android Development] urrgevo:
Gravity screen or wake gestures app in the play store work for this
[Nexus 6  Original Android Development] gigi944:
Wake Gestures doesn't work... Gravity Screen seems work for now. Thanks
[Nexus 6  Original Android Development] backdown00:
First I want to say the battery use of this kernel is the best I've ever had and I've used Franco, vindicator, hells core and elemental. Extremely well done on the kernel!

My questions is I know you don't have faux sound, is there anyway with this kernel to modify volume on headphones and such?
[Nexus 6  Original Android Development] onestoploser:
Viper works with this kernel.

Sent from my Pure Nexus 6
[Nexus 6  Original Android Development] backdown00:
What is viper? I've never used that heh
[Nexus 6  Original Android Development] onestoploser:
http://xdaforums.com/showthread.php?t=2952137 ;)

Sent from my Pure Nexus 6
[Nexus 6  Original Android Development] backdown00:
Last question hehe, is this kernel permissive?
[Nexus 6  Original Android Development] onestoploser:
I'm pretty sure it is, but I'm not running it at the moment so I'm not sure.

Sent from my Pure Nexus 6
[Nexus 6  Original Android Development] Othoric:
Yes it is set to permissive. So no issues with Viper.
[Nexus 6  Original Android Development] backdown00:
What kernel are you running? :)
[Nexus 6  Original Android Development] onestoploser:
Now we're getting off topic. Lol You can pm me if you want but let's keep this thread blu. ;)

Sent from my Pure Nexus 6
[Nexus 6  Original Android Development] urnamese3:
This kernel is soooo good until 30 %, no lag at all.. But after that it gets a bit laggy but hey its the best kernel I've tried so far.

I haven't been able to play the only game I've installed (which is fun run); it gives me some connection errors and im 100% sure thats because only a few CPUs work at that percentage with a not-so-high freq, it also happens some other times when the CPUs are running low freq.. Sometimes it doesn't work with higher percentages too but whatever

Anyway, this kernel works really good! Thanks OP for your work on this

Edit: another thing I noticed is that even though on kernel auditor the option for preventing the msim_hsic_host wakelock is enabled it still comes up on BBS.. For example today my phone was on for ~8 hours and I had ~40 minutes of that wakelock

Here's some screenshot of the kernel auditor settings and BBS stats of today, msim_hsic_host wakelock still shows up when though it shouldn't. [MENTION=3873953]eng.stk[/MENTION] why don't you add a setting to block wlan_rx and bluesleep wakelock? I had them blocked with some other kernels and the device was working flawlessly.. Maybe the wlan_rx wakelock is needed but last time I had it disabled the WiFi always worked.

http://imgur.com/TrYjIci

http://imgur.com/97DJx1x

Edit2: here's also a screenshot

http://imgur.com/k0mW8Cj

showing that only 2 cores work with the max freq locked at 1.98 Ghz when the device is charging (at any % only 2 CPUs were working) and thats when I can't play my favorite game because it's too laggy, here's also a logcat

http://pastebin.com/BCUeNWy3
[Nexus 6  Original Android Development] :
Answer is quoted. I love this kernel most of all. :)
[Nexus 6  Original Android Development] Krayvon:
Going to flash on latest pure nexus. Staying positive and hoping for magic :)
[Nexus 6  Original Android Development] eng.stk:
What ROM you're in?

Those mitigations are disabled when you flash official kernel zip.

Either you have something setting the thermal bin to active or using an unofficial version.

That logcat is not from kernel, doesn't have any useful info.

The wakelock blocker doesn't work 100%, I think some radio state bypass it in some situations.

These are the wake locks block available, some will be present in Auditor, Grarak already merged them.

https://gitlab.com/engstk/shamu/commit/5843a189e85840c55a3228850243c9539f741dbf
[Nexus 6  Original Android Development] urnamese3:
Temasek's CM 12.1

Where do I look for that thermal bin option? I reflashed the ROM before flashing the kernel so idk maybe I still didn't flash it properly.. What do you think?

I was using the catlog app from the play store to gather logs.. What do I've to use to gather kernel logs?

I remember having less active time of the msim_hsic_host wakelock with LK kernel but maybe im wrong.

Oh so the wlan_rx_wake wakelock is already limited by default, right?

Thanks for the reply
[Nexus 6  Original Android Development] JayDream:
Having the same problem with euphoria rom. It's only this kernel that's acting up. The rom runs flawlessly on stock kernel tho...
[Nexus 6  Original Android Development] SeVIIn:
CM based ROMs don't play nicely with some kernels, just the way it is, at least from my experience. Anyway, this Kernel runs well with all of the AOSP ROMs I've tried it on.
[Nexus 6  Original Android Development] eng.stk:
See if you have these files:

/system/bin/thermal-engine-bak

/system/bin/mpdecision-bak

That is a CM based ROM right?

They do some changes to the power hal, power profile stuff, etc, maybe that forces some settings idk.

EDIT: also check if you have any init.d/su.d scripts and/or apps changing settings.
[Nexus 6  Original Android Development] eng.stk:
addon folder doesn't matter, all the rest shold not be of any issue.

Keep in mind that some root apps pegs cores and it get stuck, xposed is a pit of trouble.

My advice: ditch xposed and choose a good custom ROM with the options you need.

Good luck on the troubleshooting, kernel wise there's nothing else to do.

edit: also disable auto battery saver and per app power profiles (or similar, don't remember exactly the name)
[Nexus 6  Original Android Development] urnamese3:
[quote name="eng.stk" post=62599262]addon folder doesn't matter, all the rest shold not be of any issue.

Keep in mind that some root apps pegs cores and it get stuck, xposed is a pit of trouble.

My advice: ditch xposed and choose a good custom ROM with the options you need.

Good luck on the troubleshooting, kernel wise there's nothing else to do.

edit: also disable auto battery saver and per app power profiles (or similar, don't remember exactly the name)[/QUOTE]

I need xposed for a few modules.. there is no rom that has those features though.

I disabled the per app power profiles setting and now the phone is super smooth again even on fun run. Thanks a lot mate!

Edit: I noticed that under 30 % only two cores work (sometimes...) and after a while (whenever the phone wants) all the cores start working properly again :( what could be causing this? How do I gather useful logs?

Im 100% sure that, as you said, there is something interfering with the kernel.. Here's a picture to show you the settings my phone has in certain moments (when it's laggy)

I got it in kernel auditor when the % was under 30 %

The automatic battery saving option was already disabled

PS: I removed the two files from drive since I guess they are useless
[Nexus 6  Original Android Development] TransportedMan:
Can someone explain exactly what the blu active governor and the Blu_Plug hotplug does and how it compares to Mako Hotplug?
[Nexus 6  Original Android Development] NYCHitman1:
Read... https://gitlab.com/engstk/shamu/commit/24616595364e7b0fe06071e34152a02301f6c441 and https://gitlab.com/engstk/shamu/commit/f2c1de3cc661a5960675bbb462da9a7d8a9147eb
[Nexus 6  Original Android Development] eng.stk:
Idk mate, but there's something there for sure.

I was on CM a day and a half, today I'm on EOS (to test derived CM work) and no weirdness at all, running great.
[Nexus 6  Original Android Development] urnamese3:
I see.. Even under the infamous 30 %? Until that percentage everything is so good man.. And then weirdness starts :/

How do I get useful logs?
[Nexus 6  Original Android Development] GavinMazey:
With your kernel on eos everything was working great but suddenly it would hard freeze just sitting in my pocket. Not sure if its kernel or rom issue but the ROM dev doesent support alt kernels so I figured I'd post here. He also mentioned that having no signal could cause the freeze which last time it happened I was at my moms house where I have no signal so idk. Just wanted to give you my experience. Great kernel BTW running the m version right now and its great thank you.
[Nexus 6  Original Android Development] eng.stk:
Signal has nothing to do with kernel and probably not even your freeze.

But since you haven't a log...

One thing seems to emerge: issues arise from CM based stuff and/or xposed.
[Nexus 6  Original Android Development] jamiethemorris:
Dumb question, how do I enable blu_plug? I normally use trickster, but I couldn't find it in kernel aduiter either. Mpdecision is enabled by default and I see intelliplug, msm_hotplug, and mako_hotplug.
[Nexus 6  Original Android Development] urnamese3:
Umm, when I first switched kernel I didn't have the option to turn off wakelocks in kernel auditor (there's like 5 of them but I could only see one) too. I don't know how you can make kernel auditor to show them without clean flashing BUT correct me if I'm wrong OP, this kernel comes with Blu plug as default hotplug when your first flash blu spark.
[Nexus 6  Original Android Development] eng.stk:
You can't, the hotplug is always enabled and mpdecision is completly disabled.

trickster is too old nowadays, my official kernel app is Kernel Adiutor.

To have those on Adiutor you're not using blu_spark.
[Nexus 6  Original Android Development] jamiethemorris:
OK I just checked and yeah, it's not running your kernel... It's still on the stock dirty unicorns one. No wonder. I was super confused.

It seems it doesn't like being flashed to a secondary ROM or something so I guess I'll swap it to the primary.

Thanks for the help!
[Nexus 6  Original Android Development] eng.stk:
Noting wrong there, only the latest Adiutor 0.9.1.1 has them all, your app just updated ;)
[Nexus 6  Original Android Development] jamiethemorris:
Well, I switched Dirty Unicorns to my internal ROM slot and flashed the kernel and it seems they don't play well together because it doesn't boot. :( I'm guessing it has something to do with the fact the ROM has a custom kernel in the first place.

Edit: disregard, I didn't realize there were 2 doesn't versions of the kernel. It's working very smoothly now.
[Nexus 6  Original Android Development] nixie2121:
I just installed in benzo ROM. before I flashed I cleared kernel auditor data. on 1st boot the gov was set to conservative, I thought blue active was the default? thanks
[Nexus 6  Original Android Development] Lesser Version:
Check your pm
[Nexus 6  Original Android Development] resynx:
This kernel gives me the best battery life I've been able to experience. It's so nice to finally not have to worry about my battery running out before the day is over. Thanks eng.stk :D
[Nexus 6  Original Android Development] nixie2121:
anyway to get dt2w to work?
[Nexus 6  Original Android Development] resynx:
Turn it on using a kernel app.
[Nexus 6  Original Android Development] eng.stk:
Just a heads up:

For you on M Preview 3 and having trouble with USB OTG drives with 3rd party explorer apps, know that you can access OTG data on /mnt/media_rw/#usb_serial#.

Probably just a permission issue on M3, as you know in M2 it mounted perfectly on /storage/#usb_serial#
[Nexus 6  Original Android Development] g2uzer:
Getting ready to flash this for the first time running PureNexus. Just want to Thanks you for your time and work
[Nexus 6  Original Android Development] Eris _2.1_2010:
So far running wonderfully with DU 5.1.1
[Nexus 6  Original Android Development] gigi944:
Enabling Via kernel Adiutor, it unlocks itself when the phone is in the pocket...

It would be great if the developer adds a feature that prevents the unlock when the proximity sensor is covered... a simple GREAT feature
[Nexus 6  Original Android Development] eng.stk:
I always have it enabled with the glass on the leg and I can't turn it on. dt2w on the N6 is actually 3 or 4 taps to wake, the sensor is not that sensible.

What happens most of time os Ambient Display and movement sensors turining screen on and get the screen unlocked.

Some ROMs have prox sensor optinos for that situation, but not always work that well.

I will not change nothing regarding wake gestures on kernel, sorry.
[Nexus 6  Original Android Development] gigi944:
That's why I disabled Ambient Display, but I can confirm that the phone unlocks itself when in the pocket, it happened few seconds ago.

In this conditions dt2w is unusable :/
[Nexus 6  Original Android Development] hellsgod:
Looks like its the bcl driver, did you disable it [MENTION=3873953]eng.stk[/MENTION]?

hells
[Nexus 6  Original Android Development] eng.stk:
What you mean bcl driver?

Most mitigations and manipulations are done by mpdecision and and thermal deamon which are completely disabled.

Also some stuff comes from power hal, some ROMs have some modifications to it like bat thresholds, power profiles, etc
[Nexus 6  Original Android Development] rignfool:
I think that's his version of the default shamu battery/thermal throttle...

It appears that at around 30% off power... The phone goes to 2 cores and 2ghz max... Hence why everyone is complaining that it lags...
[Nexus 6  Original Android Development] hellsgod:
This one: https://github.com/android/kernel_msm/commit/f559c4ee68eb141dcd3ae5461c349dc53454bf3b - As you can see, if a certain battery threshold is reached, it'll kick out two cores and limit max freq to 1958400, like we saw in the screenshot.

hells
[Nexus 6  Original Android Development] eng.stk:
Ah I see, on Lollipop that was all in userspace binaries, it seems like they force that enabling it on kernel in M code.

Going to revert it on next build, good find mate.
[Nexus 6  Original Android Development] hellsgod:
It was bugging me since a while lol - I only disabled its hotplug ability for quite some time, but now I disable it completely in my init.shamu.power.rc

write /sys/devices/qcom,bcl.39/mode disabled

Or you can remove it from the kernel, sure :D

hells
[Nexus 6  Original Android Development] resynx:
1900mhz throttle doesn't happen to me when I drop under 30%. Is that really kernel related?
[Nexus 6  Original Android Development] hellsgod:
Its doesn't happen on a certain battery percentage, it happens if the voltage in the battery drops to a threshold, which can also happen on higher percentage.

hells
[Nexus 6  Original Android Development] urnamese3:
Can a normal user like me disable it?

For example by adding an init.d script?
[Nexus 6  Original Android Development] hellsgod:
Yes, just use this one:

echo disabled > /sys/devices/qcom,bcl.39/mode

hells
[Nexus 6  Original Android Development] urnamese3:
Danke :) :highfive:
[Nexus 6  Original Android Development] eng.stk:
blu_spark r32

All right crew!

New build is up, enjoy!
[Nexus 6  Original Android Development] S0UTHPAWK1LLA:
So no more Linaro base?
[Nexus 6  Original Android Development] nodnarb91:
Yeeee. Thanks!
[Nexus 6  Original Android Development] eng.stk:
I prefered SM 4.9 for this release, specially because now the available cortex-a15 and vfp4 extensions, pretty happy with the results.

On next builds we'll see.
[Nexus 6  Original Android Development] S0UTHPAWK1LLA:
Just curious, I don't see a huge performance difference between GCC and Linaro.. Maybe a few extra fps on a game. Thanks for the response...
[Nexus 6  Original Android Development] fhblake04:
Is there any advantage of using the M kernel on 5.1.1? I tried searching, but I don't think what I was using is specific enough. Thanks!
[Nexus 6  Original Android Development] eng.stk:
Don't flash the M zip on 5.1.1 ROM or it will boot loop, use the 5.1.1 zip in 5.1.1 ROMs.

The source in both branches is from M3 source, which have newer stuff added over 5.1.1.
[Nexus 6  Original Android Development] xRamz:
Yo, gave this a shot, also tried write instead of echo. Neither worked :(

EDIT: Not using blu kernel btw
[Nexus 6  Original Android Development] Mervingio:
[MENTION=3873953]eng.stk[/MENTION] latest update r32 have Faux Sound or not?
[Nexus 6  Original Android Development] TransportedMan:
I cant change the sound on this kernel in Kernel Auditor. On the latest 5.1.1 build. Did I flash wrong or something? I don't even see the setting to change it. How else can I tweak the sounds?
[Nexus 6  Original Android Development] eng.stk:
http://xdaforums.com/showpost.php?p=62279464&postcount=311

http://xdaforums.com/showpost.php?p=62282578&postcount=314

Nothing changed.
[Nexus 6  Original Android Development] TransportedMan:
Alright I really miss those sound tweaks I had in other kernels. What a bummer, but your kernel is awesome so I can deal with low headphone volumes. Great work. Hey if you don't mind could you tell me how does bluactive scale CPU freq? Is it like conservative or something else?
[Nexus 6  Original Android Development] jtwlbz:
Same here. The phone keeps waking up in the pocket. No ambient display.
[Nexus 6  Original Android Development] S0UTHPAWK1LLA:
This is why Google disabled it.

---------- Post added at 07:51 AM ---------- Previous post was at 07:48 AM ----------

Viper works. Faux is really redundant if your using viper4android.
[Nexus 6  Original Android Development] BoOsT:
Use a Rom with prevent accidental wake. Problem solved :) no more waking in pocket. Or gravity box has it. Or gravity screen from play store. Still loving the kernel bud!
[Nexus 6  Original Android Development] gigi944:
[OT] I'm PureNexus now, and there isn't a prevent function... what are u using? Because Gravity Box is a xposed module, but xposed is in alpha3... and gravity screen use so much battery... [/OT]
[Nexus 6  Original Android Development] urrgevo:
Of you turn off ambient display it really helps a lot with that. I'm on pure also, and since it doesn't come with a pocket mode to prevent ambient display from waking the screen on every notification and every few minutes as a reminder (or whatever you have it set to) as well as any time the phone changes angle more than 15 degrees I think it is, the screen will come on in your pocket. I turned it off and have had no issues since then as the built in tap to wake from the room takes three to four taps to do so. This can also be disabled in kernel audiutor. If you leave ambient display on you will still likely have issues.

That said this has literally nothing to do with this kernel, sorry OP
[Nexus 6  Original Android Development] TransportedMan:
Woah this kernel was better than I expected. Charged to 100% unplugged at 5:40am. Woke up at 2:00pm. Phone is at 98%. I have no idea what it does still, but I'm using bluactive governor. I'm surprised to be honest. If you want my settings just ask.
[Nexus 6  Original Android Development] wase4711:
sure, what are your settings?

thanks
[Nexus 6  Original Android Development] TransportedMan:
Didn't do much to be honest this kernel is that good. Global undervolt of -30, didn't mess with tunables. Messed with BluPlug a bit you can see there but that's it.
[Nexus 6  Original Android Development] jon.s.nelson:
Just wanted to say thanks for the awesome kernel. The native governor and hotplug provide an amazing smooth balance of performance and battery. Lowering my brightness helped too, but with blue spark I'm reaching 4.5 hrs. SOT for the first time ever! And that's with full cpu until 25%, and then only minimal cpu throttling, from 25% and under. (I was getting only 3 hrs SOT until recently)
[Nexus 6  Original Android Development] BoOsT:
I run Twisted and Slim rom by Yank. I used gravity box on pure. It's been in alpha all year and I've never noticed an issue. With this kernel everything seems flawless.
[Nexus 6  Original Android Development] ieatacid:
I've tried a lot of kernels and have settled on this one. It's stable as hell, has awesome battery life and performance. Nice work, sir!
[Nexus 6  Original Android Development] farahzadfarahzad:
I've been running your kernel along with chroma rom but some how i lost the wifi connection it happened two time during a day , it shows my wifi concretion into the wifi setting but it kept shows obtaining ip address and i had to turn off wifi on my phone and on again then it worked

Update : something wrong with my router i guess your kernel works well thanks
[Nexus 6  Original Android Development] eng.stk:
blu_spark r36

All right crew!

New build is up, go get it!
[Nexus 6  Original Android Development] Smallsmx3:
No idea what any of that is but my guess is it's more awesome than r32
[Nexus 6  Original Android Development] resynx:
Sweet, flashed this 1 as well as an Omni nightly during class :D Thanks!
[Nexus 6  Original Android Development] eng.stk:
Nice, on my time there wasn't anything to flash. Basic calculator programming was the thing ahaha

All good in omni? I tried it a couple times, but the low volume kept me away.

Only happens with that ROM,don't know if it's because of their DSP manager or something.
[Nexus 6  Original Android Development] Trina9:
Dumb question, I'm still a newbie at this. I'm thinking that all I have to do is boot into recovery and flash this. Or is anything else needed. Just never updated a kernel before.
[Nexus 6  Original Android Development] wase4711:
that is correct..
[Nexus 6  Original Android Development] resynx:
Well at least you didn't have to worry about flashing distracting you from your studies :D and here I am responding while I'm in class again haha :laugh:

But yeah Omni is 100% solid for me. It's the only ROM I've been on that doesn't give me the low ringtone volume issue. Completely bug free :good:
[Nexus 6  Original Android Development] TransportedMan:
Didn't know new build was out.

Here are my results from build 32. Pretty good, didn't charge it once all day. Hoping for better results with new build. Will report back!
[Nexus 6  Original Android Development] jussaren:
Wow, what are you settings please..