yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] g2uzer:
So this kernel going back to permissive is not a big unsecured issue? I asked about permissive on another forum and the way it was explained is that is easier to get malware but is it that easier to get? I really enjoy this kernel! Just got a little nervous after that answer. Thanks for the hard work and time you put in to this Kernel. I might end up flashing it again!
[Nexus 6 Android Development] buckmarble:
Honestly, you opened up the biggest security hole by rooting your device. IMO, se permissive is nothing after rooting. I wouldn't concern yourself with permissive vs enforcing. From a technical stand point, yes enforcing does give you a more secure environment, but all of these aosp roms that are enforcing by default have had so many sepolicy exceptions put in place just to make root functions work, that they've reopened up all the holes in selinux that they tried to close by going enforcing.
[Nexus 6 Android Development] Vortex1969:
I built Bliss_bacon for over a year. Setting my kernel to build in permissive mode. Enforcing after your rooted is not going to add much security.

Enjoy this great kernel. Its one of the fastest.
[Nexus 6 Android Development] Freak07:
Hey [MENTION=2967322]buckmarble[/MENTION] :)

I'm using your kernel and it's a great pleasure! Thanks for the hard work you put in.

I have the feeling you're open to requests. So here's mine: would you consider to add elementalx cpu gov? :) I just like to experiment a little bit and I'm curious how it would work with your kernel.
[Nexus 6 Android Development] Poojan Patel:
has anyone ever had a problem with google camera?? Because on stock kernel google camera used to work perfectly and now i have flashed elite kernel and video recording in google camera isnt working. :(

here what it is:

on Stock kernel: google camera works fine(new (v3.1) and old (v2.7 or v2.5) both )

on elite kernel: everything works fine on old version and video recording doesnt work on new version.
[Nexus 6 Android Development] ricco333:
Read back a few pages, there was a release of Elite that fixed the camera problem some users were having.

Erik
[Nexus 6 Android Development] buckmarble:
Last 3 builds I believe have the cam fixed.
[Nexus 6 Android Development] brymaster5000:
Yes - I will take a look at this this weekend. I was planning on looking at something else governor related anyway.
[Nexus 6 Android Development] pantmunu:
+1 for elemental x governor. Good balance on battery and performance.
[Nexus 6 Android Development] adm1jtg:
I would love to see interactivex and ondemandx, are those not valid anymore as i rarely see them, that said interactivex is the main gov used on lean kernel so would love to see and test it out

Sorry if I am a little old school
[Nexus 6 Android Development] brymaster5000:
Sorry guys - with the holidays coming and going, my limited time is getting even more limited. I will get to those governor requests soon...but no eta because apparently when i give one - my weekend goes by without sitting down once.
[Nexus 6 Android Development] jkc120:
Does anyone know off hand if this works with the MMB29K (6.0.1) factory image?
[Nexus 6 Android Development] teinwhite:
It does.
[Nexus 6 Android Development] g2uzer:
I seen where there's been a fix for the camera but last night my phone froze for a few and also didn't save a couple pictures I took using the Google camera, I had to flash back to stock kernel since I take a few pictures thru out the day perhaps others are having similar issues? Nexus 6 on pure Nexus. It's this issue even kernel related? Only thing I did was flash the latest kernel after clean flashing latest ROM. Thank for the hard Work!
[Nexus 6 Android Development] buckmarble:
What ROM
[Nexus 6 Android Development] g2uzer:
PureNexus
[Nexus 6 Android Development] buckmarble:
I've been taking photos without fail every day on PN. Only thing I can suggest is do a fresh wipe and install
[Nexus 6 Android Development] gamewarden234:
I'm on stock. Everything works.
[Nexus 6 Android Development] g2uzer:
Will try it again. Thanks a lot. With 6.0.1 being out I might just wait to clean flash the update when its available, thanks again.
[Nexus 6 Android Development] biglilsteve:
I've seen other devs release kernels that are specifically for 6.0.1. Why isn't that the case here?
[Nexus 6 Android Development] buckmarble:
Ye have little faith lol.
[Nexus 6 Android Development] biglilsteve:
Haha, I wasn't doubting anyone! I am just curious why some kernels felt the need to post 6.0.1-only builds.

I was in love with this kernel while I was on MRA58R Cataclysm but didn't flash it when updating to the new MMB29K build for fear it wouldn't be compatible.
[Nexus 6 Android Development] demlv:
Love the kernel. Jealous of the newer build of PureNexus. [MENTION=2967322]buckmarble[/MENTION] are you a tester for [MENTION=4395895]BeansTown106[/MENTION], or do you just make personal builds of PN?
[Nexus 6 Android Development] buckmarble:
I build my own but I'm always communicating with beans.

---------- Post added at 03:08 PM ---------- Previous post was at 03:04 PM ----------

Well, the reason they are specifically for 6.0.1 is because they enabled something called CPUSETS. This allows the OS to assign certain types of tasks to a single cpu or a set of cpus. If the OS side doesn't have the hooks to compliment the kernel, then the phone is very laggy and stuttery.
[Nexus 6 Android Development] Vortex1969:
Out of respect to the Dev never ask for an ETA. The most likely have day jobs and familys just like the rest of us.

They do this for free and I'm sure as a hobby like most.

It will be here until then enjoy...
[Nexus 6 Android Development] demlv:
I think you misunderstood. He was asking why this kernel works already with 6.0.1, when others needed to be updated. :good:
[Nexus 6 Android Development] Vortex1969:
Sorry my bad misread. [emoji33]

---------- Post added at 03:24 PM ---------- Previous post was at 03:17 PM ----------

I see the post above now I can say all I'm missing is Elite..[emoji1]
[Nexus 6 Android Development] biglilsteve:
Alright, so this kernel does not enable CPUSETS? And you did that to ensure compatibility with a wide variety of ROMs?
[Nexus 6 Android Development] buckmarble:
Did you do your own build? If you did, take a look at my github and you can see the mods i made to build my kernel inline :eek::cool::highfive:

The reason we haven't release yet is because we are evaluating the CPUSETS. It has hooks into MP-Decision. The reason we went with zen is because of the crappy 3 sec touch boost of all cores, but that appears to be gone with the updated mpd binary. It seems to either be completely removed and following the input boost driver or modified to only boost for 1 sec. I'm inclined to lean toward it was removed from the mpd binary.

---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------

Incorrect, the build in the OP does not include CPUSETS because it is the older M source base.

I already have a new kernel with CPUSETS for 6.0.1 that we are testing and evaluating. Unfortunately, it will have to stay 6.0.1+ specific.
[Nexus 6 Android Development] biglilsteve:
Thanks for the clarification!
[Nexus 6 Android Development] Vortex1969:
Just look thanks Google hehe. Don't want to loose zen.

After looking at the changes I would say as well its probably the mpd binary.
[Nexus 6 Android Development] buckmarble:
Just keep your options open. All the behavior we didn't like about MPD is gone. There might not be a reason to have zen anymore. :eek::eek:
[Nexus 6 Android Development] Vortex1969:
Of you will send me your boot.IMG I would like to test for and with you.

Thanks
[Nexus 6 Android Development] buckmarble:
hit me up on hangouts. forrestmarble@gmail.com
[Nexus 6 Android Development] Vortex1969:
Will do it will be later leaving the office soon pick the kids up ect. dinner. hehe life...
[Nexus 6 Android Development] cujo6801:
Hey we know some of you have life's out there but to Rub it in our faces like this...

Come on bro....

:D

Sent from the "DOG" pound...
[Nexus 6 Android Development] buckmarble:
OP updated with new build for 6.0.1

A couple of changes to be aware of

1. It is for 6.0.1+ only. They have implemented a new CPUSETS feature in the OS and kernel and if used on 6.0.0, you will get some major lag and wonkiness

2. Because of the aforementioned CPUSETS, the build now defaults to MpDecision instead of Zen. The radical behavior of MPD we really didn't like is now non-existent with the updated binary. Also, there are hooks for CPUSETS in mpd that aren't in zen. I have gotten some quite startling increases in battery life with MPD. So far today, I am at just over 3hrs of screen on time, mostly using chrome, hangouts and slack, and still at 70% of battery. My testers are seeing the same results, so hopefully all of you do as well.
[Nexus 6 Android Development] biglilsteve:
^my man!!!

Thanks for the information as well.
[Nexus 6 Android Development] colinmcg71:
Fantastic! Can't wait for the new PN build to drop and get this excellent kernel flashed :D
[Nexus 6 Android Development] Droidphilev:
Hi, thank you!

Since all the fuss about systemless root (which i don't use yet):

- Does the kernel work with SuperSU 2.61 but also with 2.52?

- If it does work with SuperSU 2.61: if i understand it correctly the kernel needs to be enforcing to work with this version of SSU. OP still mentions "permissive". Is the kernel enforcing now or is my info that 2.62 only works with enforcing kernels wrong?

Sorry to ask all this :(
[Nexus 6 Android Development] buckmarble:
1. It should work with both, although i haven't tested.

2.You do not need an enforcing kernel to work with systemless root. I have tested this piece with an earlier version of systemless root.
[Nexus 6 Android Development] Tex99:
Thank you for update!! Great, works well on cataclysm 6.0.1 :) just a notice, you know why fauxsound app says this ? It happened also on 6.0.0
[Nexus 6 Android Development] buckmarble:
Rom issue probably. This is what I'm seeing.
[Nexus 6 Android Development] Droidphilev:
Many many thanks for the clear explanation!
[Nexus 6 Android Development] gamewarden234:
Tested both,works with both. FYI I flashed this on stock and both zen and mpd were checked initially. Turned of zen works great so far although it hovers around 1497 mhz for a bit before dropping
[Nexus 6 Android Development] Tex99:
Thank you. I see that you also can not change speaker gain, and it's normal on shamu ? I ask this because I have n6 since 2 weeks, before I had n5 and there wasn t problem with speaker gain, I could change the gain
[Nexus 6 Android Development] buckmarble:
It is broken for the fauxsound app, but not all together. You can increase it in kernel aduitor
[Nexus 6 Android Development] MrMiami81:
Can I install the kernel for 6.0.1 even though I'm still running 6.0.0?
[Nexus 6 Android Development] Droidphilev:
FYI: working fine with SSU 2.52. Thanks again for this build!
[Nexus 6 Android Development] buckmarble:
On what rom? There should only be a 1 sec boost to the 1497. But unlike the past, it shouldn't be boosting all cores at the same time.

---------- Post added at 03:07 PM ---------- Previous post was at 03:07 PM ----------

No. It will cause some seriously wonky behavior on 6.0.0.
[Nexus 6 Android Development] pantmunu:
Since u guys re-enabled mpd , is this script supposed to look like this , just asking if it should still be there.
[Nexus 6 Android Development] buckmarble:
Yep. That # in front of mpd disables that line so that mpd stays running and echo 0 disables zen.
[Nexus 6 Android Development] Phrodini:
Buckmarble, how long does it usually take for your phone to reboot
[Nexus 6 Android Development] buckmarble:
I don't know. Typical amount of time its always been. If you flashed the new kernel on 6.0.0 base, it'll take forever to boot.
[Nexus 6 Android Development] Phrodini:
Will be a record setting boot time for sure. I'm still waiting for more roms to be updated to see which 6.0.1 to flash. I do miss the double tap power camera feature from pure tho.
[Nexus 6 Android Development] buckmarble:
If you are on stock 6.0.1, this feature is now in the stock rom under display in settings.
[Nexus 6 Android Development] wrongway213:
New MPD implementation is getting crazy battery results here as well. Last night on a fresh flash of 6.0.1 kernel I hit 3 hours SOT and only burned 40% of battery - still 60% to go! Scaling is smooth as can be as well, and I was even running Zzmoove Inzane governor (totally performance oriented, not battery oriented) and still got those results. Awesome work guys!
[Nexus 6 Android Development] adm1jtg:
Just tested on stock 601 and got huge lags in xda app and in touchpal keyboard. Will test more but so far was EXTREMELY laggy for me like the okld days when you typed faster then the computer could keep up.
[Nexus 6 Android Development] wrongway213:
You flash over another kernel? Dirty flash anything? Does your init.d script match the one posted a page or two back? This does not add up if on stock and 12-07 kernel - something must be up.
[Nexus 6 Android Development] adm1jtg:
Flashed on top of your previous 16th i think it was version. Like I said I will keep testing also was on low battery could it have been throttling due to being below 15%? I changed no settings loaded with straight defaults
[Nexus 6 Android Development] buckmarble:
Are you sure you're on 6.0.1?
[Nexus 6 Android Development] adm1jtg:
yes fastbooted the system image from the factory image i also fastbooted the boot.img first then had flashed your 16th build booted up and loaded stuff then you released the new 601 version and i flashed on top of that.

Since no one else seems to be having issues i will reload clean and try again. BTW i am encrypted of that matters
[Nexus 6 Android Development] Vortex1969:
Do you use any kernel editor. If so and you didn't clear the app cache. Check because last night when I installed for testing both mpd and zen was toggled on. If so uncheck zen and reboot.

If you had been using Elite kernel before.

Just a thought...
[Nexus 6 Android Development] buckmarble:
If you are on stock images, you need to clear space in /system in order to install busybox and supersu. Init d relies on busy box so if it isn't installed, the script will fail to run
[Nexus 6 Android Development] brymaster5000:
Chainfire released a comment on the lack of system partition space in his super su thread. A must read for all. These are the times we are headed in...
[Nexus 6 Android Development] pantmunu:
Dlete
[Nexus 6 Android Development] mashuto:
Don't know if I misunderstood but I am still seeing the old mpdecision behavior. I tap the screen and all four cores shoot up to 1497 mhz for 3 seconds, at least according to the cpu tab in kernel adiutor.

Since I just installed though I have no way yet of knowing how the battery will hold up, but I will certainly monitor it tomorrow.
[Nexus 6 Android Development] mashuto:
Latest pure nexus (today's build) clean flashed.
[Nexus 6 Android Development] Nucleotide:
Just flashed on a clean install of Chroma. Will report back any issues/misbehaviour, if any.

Thanks a lot for your solid work. Greatly appreciated. ;)
[Nexus 6 Android Development] buckmarble:
The 12-9 build?
[Nexus 6 Android Development] mashuto:
Yes
[Nexus 6 Android Development] buckmarble:
You should be getting a boost to 1497 for only 1 sec. Not 3.
[Nexus 6 Android Development] mashuto:
Hmm, it's definitely boosted for longer than a second. I'll check my checksums and make sure I don't have bad downloads and I'll probably reflash the kernel again. And if needed, do another clean flash tomorrow.

Do you have a recommended flashing order? Should I flash the rom and let it boot up then come back and reflash the kernel later?
[Nexus 6 Android Development] buckmarble:
Wipe, rom, gapps, kernel, boot
[Nexus 6 Android Development] mashuto:
Yea that's my usual order, with a couple other small things thrown in, like a boot animation and then viper at the end.

I'll keep an eye throughout the day tomorrow and see if it looks better and also watch on battery life.

Edit: so I did another clean flash and am definitely still getting it for 3 seconds. One thing I did notice in kernel adiutor is that it actually changes the minimum frequency to 1497 for about 3 seconds before reverting. But if I manually set the minimum to 300 the boost only lasts for about a second and doesn't touch the min frequency.
[Nexus 6 Android Development] wrongway213:
Oh my... No OC or anything, no performance mods... Just this kernel set up proper on a nice DU build:) Think this is the highest bench I've seen on the N6 so far.. Looks like the new chipset function has this phone way beefed up
[Nexus 6 Android Development] arifqur:
Wow! Thats some score.

Does the device score higher on Antutu 6.0 than on Antutu 5.7 ?
[Nexus 6 Android Development] arifqur:
What!!??
[Nexus 6 Android Development] head_banger:
That's with last elite kernel with blu_active gov ;)
[Nexus 6 Android Development] arifqur:
What theme are you using for statusbar icons?
[Nexus 6 Android Development] head_banger:
Timberwolf :thumbup:
[Nexus 6 Android Development] arifqur:
Thanks
[Nexus 6 Android Development] wmfreak:
Anybody flash this on latest PN rom? Pkease share your experience.
[Nexus 6 Android Development] withoutme5:
Thanks for this kernel, running smooth with latest chroma without issues.
[Nexus 6 Android Development] :
Pure Nexus? I've used Elite on all roms and it always runs amazing!!! These guys don't play when it comes to kernel development. Give it a flash. I'm on CM13 and latest is outstanding!! Thanks guys!!
[Nexus 6 Android Development] Formhault:
Lol "detial" :D
[Nexus 6 Android Development] wrongway213:
What tweaks? Never seen a score near that high..can't get past like 81k here even using blu_active.
[Nexus 6 Android Development] head_banger:
You disabled Zen hotplug?
[Nexus 6 Android Development] pantmunu:
I am seeing the same on purenexus and not in chroma. I should have made a video last night when I flashes pure nexus. It was a clean flash too. So. Don't know what is actually wrong. Prolly something in the user end or some scripts running from the ROM side. All in all , the kernel itself is pretty amazing. Thanks devs.
[Nexus 6 Android Development] wrongway213:
Yup, running MPD. Thought maybe you tweaked I/O read-ahead, GPU or something else to get that high of a score, lol.
[Nexus 6 Android Development] whaevr:
Filesystem type?? Here's what I got
[Nexus 6 Android Development] KonoeKyon:
Yeah, a lot higher, they redid how it calculates and weights each section of the test.
[Nexus 6 Android Development] davwman:
Kernel is no joke running minimal rom and pico gapps with latest elite kernel at stock settings.
[Nexus 6 Android Development] miguelito18:
This kernel just keeps getting better and better
[Nexus 6 Android Development] adm1jtg:
I seem to be benching only about 71k clean install of np 601 version. What am I doing wrong?

Update: Like an earlier poster I am seeing still about a 3 second touch boost when I touch screen in kernel auditor, not 1 second.

Update 2: Like other poster I went and manually set min to 300, as mine was also jumping to 1496 as min. So far the 1 sec touch boost seems OK now.
[Nexus 6 Android Development] buckmarble:
It sounds like the initd isn't getting your min set correctly if its doing this. Did you dirty flash rom? Do you have any other scripts in init.d?
[Nexus 6 Android Development] manojpy:
I just noticed the same issue in K ADIUTOR. Manually changed to 300 and seems to work. The max was also jumping, manually changed to 2649. No other initd scripts.
[Nexus 6 Android Development] adm1jtg:
Clean install of pure nexus, formatted manually system, caches and data. In init.d I only see 90userinit, 91elite and 99SuperSuDaemon. That's all
[Nexus 6 Android Development] buckmarble:
OK, do me a favor, reboot, let the phone sit until the screen shuts off before you do anything, then go into ka and see how it behaves.
[Nexus 6 Android Development] manojpy:
Clean install lite rom by Danvdh. Supersu 2.62
[Nexus 6 Android Development] buckmarble:
Does this rom have busy box installed?
[Nexus 6 Android Development] adm1jtg:
Just did that no change. Still 3 or 4 second burst min goes to 1496

Update: running the script from inside kernel auditor the script executes but same issue.
[Nexus 6 Android Development] manojpy:
Yes busybox pro installed in bin. Could that have anything to do with it?
[Nexus 6 Android Development] wipian:
And here I was, thinking I was going mad?!?!

I'm seeing the same behaviour:

Busybox pro, installed bb in system or su/bin

Kernel Aduitor is working so bb install is okay.

Upon reboot, init script doesn't run (KA can run it through settings though so they can be applied)

I'm using Cataclysm with SuperSU 2.62.
[Nexus 6 Android Development] buckmarble:
Might be something with SuperSU 2.62. That's the system less root isn't it?
[Nexus 6 Android Development] wrongway213:
Sure is.
[Nexus 6 Android Development] mashuto:
That might be his problem, but same behavior over here on purenexus which uses supersu 2.52

Either way though, the min frequency needs to be set on boot it seems, correct? And the reason we are still seeing the old mpdecision behavior is because it isn't, correct? Or is this still something else going on.
[Nexus 6 Android Development] adm1jtg:
Same issue running script from within kernel auditor. Script executes but no change in behavior. Still 3 or 4 second burst where min freq hits 1494
[Nexus 6 Android Development] davwman:
I'm running systemless and have no issues. I've noticed that the flashing method makes a difference with systemless
[Nexus 6 Android Development] buckmarble:
I have tried to replicate the 3-4 second boost you guys are seeing with absolutely zero success. I need some more help from you all on this. I can't fix something i can't replicate.
[Nexus 6 Android Development] adm1jtg:
Could it be a system r/w Vs r/o issue. The script is actually unable to change those files?

Also would it be possible to list the changes the script makes so I could have kernel auditor set them manually.
[Nexus 6 Android Development] buckmarble:
I doubt it, but i may have to set different permissions on the sysfs nodes in the init.d script.
[Nexus 6 Android Development] mashuto:
Happy to help you, but I'm not sure what more I can do right now. Let me know what you need and I'll try and get you any info you need.

Best I can say right now is that I clean flashed the pure nexus dec 9th build, wiped everything except internal storage. Flashed the following in order: pure nexus, gapps, dialer, boot animation, elite, viper. In kernel adiutor I show that on screen touches the min freq jumps to 1497 for about 3 seconds. However, if I set the min freq (even to the exact same value) the behavior changes to what looks like it should be. If I change to set on boot it seems to persist through a reboot. Even though they are stock values, it still sets them, which seems to be what is needed to get the correct behavior.

So, if you need logs or anything else, let me know and I'll be happy to try and get them for you.
[Nexus 6 Android Development] buckmarble:
something is up. I just flashed the kernel zip, instead of using the kernel built into my version of pure nexus, and still can't replicate. There is another thing that i forgot i did in the kernel zips. The input boost should be boosting to 1728(which i'm getting after flashing the kernel zip), not 1497, so that piece of it is an indicator that something might not have taken. If you go into root explorer, open up init.shamu.power.rc and see if it says #Elite at the top, the very first line?
[Nexus 6 Android Development] mashuto:
It actually does seem to boost to 1728, for a second, like it seems it should, it's just that the other behavior still seems to happen as well, so like a second (or less) at 1728, but the min freq goes up to 1497 for 3 seconds.

Checked the file and yes #Elite is the first line.