yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] erraggy:
[MENTION=4684315]flar2[/MENTION] could you please look into this sepolicy issue that recent CM based ROMs are having with custom kernels? [MENTION=5169465]RIPng[/MENTION] found that the following change fixes the problem and it has been tested by many on the official BlissPop 1.7 successfully using his sensei r46.1.

http://xdaforums.com/showthread.php?p=58228533

Thanks in advance! I love using your kernel on BlissPop and cannot upgrade to the official build until I can also flash your kernel as well :D
[Nexus 6  Original Android Development] antiochasylum:
It was actually [MENTION=4913579]CPA Poke[/MENTION] who told [MENTION=5169465]RIPng[/MENTION] what to do, and I already said this 1 page back.
[Nexus 6  Original Android Development] erraggy:
I didn't see mention of the sepolicy in your post and therefore couldn't make the connection. Sorry about that. There have been many theories posted around about why custom kernels force closed system UI, and I wanted to be sure that I had proof before asking [MENTION=4684315]flar2[/MENTION] to look into it.

Also, no where in your post do you say anything about what the linked gerrit fixes. SystemUI force closing is what I'm referring to. Is that also what you were referring to, [MENTION=2579817]antiochasylum[/MENTION]?
[Nexus 6  Original Android Development] DespairFactor:
CPA Poke gave me the sepolicy for the theme fix, I fixed it myself with the contexts anyhow before that, the way imoseyon did, I didn't test until after I replaced the binary though. The PIE fix was something I found myself.
[Nexus 6  Original Android Development] Circaflex:
Is this how every thread is going to be for The next week? Constant questions about a buggy theme engine and begging devs to implement the fix...
[Nexus 6  Original Android Development] antiochasylum:
Its pretty obvious what my post was for. Also i was talking about where you were asking CPA poke as to where to apply the se policy fixes.

Thats all. I don't care about anything else. Nor am I involved.

Yes. Its already annoying. Buts its only going to get worse.

Anyway, no point in beating a dead horse. Back to FLARS kernel.
[Nexus 6  Original Android Development] erraggy:
This is a development thread, right? I was sharing a fix that can only be applied in kernel source and has not been applied in this kernel yet. Not only relevant to BlissPop, but all CM based ROMs.

I will continue to behave in this way unless the OP or a moderator tells me otherwise.
[Nexus 6  Original Android Development] Krunk83:
Anytime I flash this kernel or Franco I get stutter. Stock kernel does not have this issue.

nexus 6
[Nexus 6  Original Android Development] danarama:
Stutter where?. Never had stutter and I even change my settings to be less smooth.
[Nexus 6  Original Android Development] Krunk83:
Primarily unlocking the phone. The animation. Also closing apps or switching between apps.

nexus 6
[Nexus 6  Original Android Development] simms22:
ahh.. the animation. maybe thats why i dont see a stutter, i always keep my animations disabled(i dont like animations).
[Nexus 6  Original Android Development] Krunk83:
I like em. Maybe I'll try without.

nexus 6
[Nexus 6  Original Android Development] paychex:
If it only lasts a week I'll take it
[Nexus 6  Original Android Development] flar2:
I've seen it, all that extra screen resolution is hard to drive. I'm trying something very different. Hang on for the next release.
[Nexus 6  Original Android Development] flar2:
The theme engine stuff will probably be release + 1. At that point the kernel will work with anything.
[Nexus 6  Original Android Development] Pilz:
I can't wait for the next update! I've been flipped between this and lean kernel lately but I prefer elemental. The s2s works better and without any modification unlike other kernels. :)
[Nexus 6  Original Android Development] Jeff_in_LA:
Question about the extra nav/menu button on the bottom

Question about the extra nav/menu button on the bottom.

How do I assign a command to it?

I bought your control app today, great work!

J
[Nexus 6  Original Android Development] danarama:
Wrong thread?
[Nexus 6  Original Android Development] Jeff_in_LA:
I installed Elemental kernel to my Nexus 6 today. After the install, I also purchased the 3.99 control and update app.

Now I have 4 soft capacitive buttons on the bottom of the screen instead of 3. Can I assign that button? If so where..

Thanks
[Nexus 6  Original Android Development] flar2:
I usually never mess with color, but I find this one to have a bit of yellow tint, so I'm dialing back the red and green to about 230.

I still have to get a handle on the frequencies. Not yet sure all the things that mpdecision and power.shamu.so do on this device. I see they mess with the frequencies a lot, I might have to cap the freqs like I do on my other kernels.
[Nexus 6  Original Android Development] LeoRex:
Thanks..... sorry about that... don't tell me... this already came up and was answered somewhere in the thread. crap... I thought I looked through everything. :)
[Nexus 6  Original Android Development] bradputt:
Well, I'm grateful that there's color control for us now because the warm screen is driving me crazy!

Really grateful Mr. Flar2. Big thanks!!
[Nexus 6  Original Android Development] NICEGYPT:
How the color control works? I tried a lot of apps none is working.
[Nexus 6  Original Android Development] Dabarr:
I do not own this device yet. However I know "Trickster MOD" does have build in Color Control. Don't know if it's compatible with this kernel though. You gotta try it out. Hope this helps you.

Cheers
[Nexus 6  Original Android Development] NICEGYPT:
Thanks, yes it does work I just tried it.
[Nexus 6  Original Android Development] Dabarr:
Glad it worked for you. I will be playing with the colors as well as soon as I get my nexus 6.
[Nexus 6  Original Android Development] GYGZACH:
Thanks for the recommendations on color. Any others? I've dialed back red and green to about 230 and blue at 255
[Nexus 6  Original Android Development] adbFreedom:
I am currently running R230 G235 B250 and it definitely turns the yellow back to white. I tried (what I thought) used to be the "Trinity Colors" I ran on my Galaxy Nexus (135, 135, 214) that didn't work lol
[Nexus 6  Original Android Development] Zenoran:
I just dialed back the red a bit and it looks good. Interests to hear about other people's settings on colors for this device.
[Nexus 6  Original Android Development] flar2:
Will do in the next update.
[Nexus 6  Original Android Development] NICEGYPT:
R207 G208 B255. the best for me. I like the white to have a very light blue tint
[Nexus 6  Original Android Development] Neejay:
R210, G208, B230 - slight blueish tint
[Nexus 6  Original Android Development] whiplash353:
My screen is less warm now but depending on the angle there is still a yellow blotch if you at it straight forward but at a angle it goes away so I'm hoping it's the glue thing
[Nexus 6  Original Android Development] ChaosMinionX:
Anyone else having minimum frequency continually being set frequency as 1728000 - I have this behavior in both Trickster and ElementalX App
[Nexus 6  Original Android Development] paychex:
Think that's just mdpresision being mdpersision. It's not actually set there
[Nexus 6  Original Android Development] drawde40599:
That app and most apps read min wrong , min is 300 , that's touchboost freq is what your looking at . use prefmon app to read in real time .
[Nexus 6  Original Android Development] wrinklefree:
RGB Calibration

I'm having the best luck with 245/240/255 on my N6. When I get back home I'll measure the color temp with my colorimeter and calibrate as needed.
[Nexus 6  Original Android Development] slickie88:
My i1 Display Pro is locked up in storage and I can't get access to it for a few months. :(
[Nexus 6  Original Android Development] danarama:
Pretty sure that's to do with something other than this kernel
[Nexus 6  Original Android Development] drawde40599:
What ROM are u using ? Do u have APPs installed that mess with capacitive buttons? . I don't see how this could be kernel related
[Nexus 6  Original Android Development] Jeff_in_LA:
Pure shamu 3.95. I didn't load any app that adjusts the capacitive buttons. The 4th button showed up after flashing this kernel
[Nexus 6  Original Android Development] danarama:
Coincidence. Remove kernal app and reflash ROM. See if it goes. I bet not.
[Nexus 6  Original Android Development] paychex:
You did something else too
[Nexus 6  Original Android Development] simms22:
what does the fourth button look like? screenshot?
[Nexus 6  Original Android Development] Jeff_in_LA:
Ok.. By the way, I've been doing this since my HTC EVO, so this is not new to me.

First, I loaded the app Lightflow on a stock Pure Shamu 3.95 rom.

I could not get the LED to work in any way. Yes, I added it to notifications.

Then it occurred to me I've never seen the LED work at all.

I looked up and found out the Elemental x Kernel has a way to light the LED while charging, thus testing my LED. Which worked BTW.

I made a Nandroid, then I flashed the kernel with 2.8.4 TWRP, went thru the aroma installer.

Rebooted. I saw the 4th button (see pic on the bottom)

Even more bizarre, I wiped data,system,cache, dalvic cache and restored my nanroid with the stock kernel.. It's still there!

I did no other configuration changes today.

My only thought, is this some type of setting for a left handed person to control the device with one hand?
[Nexus 6  Original Android Development] rignfool:
Pure shamu has a customizable nav bar...

Check in settings

Sent from my Nexus 6
[Nexus 6  Original Android Development] Jeff_in_LA:
Good call ringfool.. I have no idea how I set that! A cool feature thoughts... Thanks!
[Nexus 6  Original Android Development] antiochasylum:
That home screen... Ocd nightmare.
[Nexus 6  Original Android Development] flar2:
I'm very excited about the next release, the phone feels like I want it to. Maybe tonight.
[Nexus 6  Original Android Development] treIII:
Sounds good

Sent from my Nexus 6 using Xparent Blue Tapatalk 2
[Nexus 6  Original Android Development] colinmcg71:
Looking forward to it!
[Nexus 6  Original Android Development] DroidIt!:
Hey [MENTION=4684315]flar2[/MENTION] hope all is going good :) When you do the next release which governor will you be reccomending: ElementalX, interactive, on demand, or some other?
[Nexus 6  Original Android Development] flar2:
There will be an all new ElementalX gov.
[Nexus 6  Original Android Development] PDP///M:
Will it be based on conservative?
[Nexus 6  Original Android Development] adio201:
Also will it have sepermison?
[Nexus 6  Original Android Development] cfrank38:
Sounds very nice we are waiting ..
[Nexus 6  Original Android Development] paychex:
So you want a clone of FK?
[Nexus 6  Original Android Development] PDP///M:
Did i say that? I asked because flar had said he might do something with conservative as well.
[Nexus 6  Original Android Development] flar2:
No, it's similar to the previous ex gov but extensively reworked for this device and updated to work better with Linux 3.10.

Multiphase demand based switching.

Anyway, won't be ready tonight. I have to get my source code all cleaned up before releasing. I also have to update the app to work properly with all the new tunables.
[Nexus 6  Original Android Development] flar2:
I've been browsing the web and writing emails for the past half hour and I'm only down 5%. Performance is better than interactive. This is ultra smooth.
[Nexus 6  Original Android Development] joeyrushlow:
Slimbus?

Hey Flar2, glad to see you on this device =D

Any chance we could get those slimbus tweaks that poondog and zeroinfinity came up w/ the for the one?

I'd do it myself but I'm still a n00b on compiling a damn kernel =(
[Nexus 6  Original Android Development] instinctkiller:
Can't wait to get the new ElementalX governor !!
[Nexus 6  Original Android Development] flar2:
That tweak isn't used anymore.
[Nexus 6  Original Android Development] PDP///M:
Flar, could you expain migration load threshold in Boost settings in layman's terms?
[Nexus 6  Original Android Development] old_fart:
Oooh, google patented it seven years ago.

http://www.google.com.ar/patents/CN101111078A?cl=en

Apple can't use/steal it, nanner nanner nanner !
[Nexus 6  Original Android Development] cfrank38:
In the leankernel thread a very interesting comment. Maybe yo can look at this flar.......
[Nexus 6  Original Android Development] flar2:
It means if a thread moves from one CPU core to another, the new CPU core will match the speed of the old one.

Ive used the scheduler tweaks from Vincent Guittot on every one of my kernels dating back to the HTC one xl.
[Nexus 6  Original Android Development] flar2:
Update!!!

**Experimental**

I made a lot of changes, this needs testing.

I'm not adding it to the updater in the ElementalX app yet. Manual installation only.

Also, I pushed an update to the app (version 1.47) so it will work with this new stuff. If you have version 1.46 or before, it will not work properly and the CPU governor screen will crash.

Normally I keep Qualcomm's mpdecision, but this time it's getting in the way more than helping, so I've added a simple hoplugging driver to the kernel. The touchboost is too much and it's not providing any benefit.

The way hotplugging now works:

Two cores are always on, the third and fourth are independent and come online if needed. By default, if the load is over 80 for 400ms another core comes online. The third and/or fourth cores stay online as long as the load demands it or for a minimum of one second. While the screen is off, it goes down to a single core. That's basically it.

path for tunables is /sys/devices/platform/msm_sleeper

up_threshold: load at which a core comes online, can be 0 to 100 (default is 80)

enabled: 1 = enabled, 0 = disabled (default is 1)

up_count_max: time over threshold to bring a core online, in tenths of a second (default is 4)

down_count_max: time under threshold to take a core offline, in tenths of a second (default is 10)

max_online: number of cores to use, can be 2, 3, or 4 (default is 4)

suspend_max_online: number of cores to use while suspended, can be 1, 2, 3 or 4 (default is 1)

I've also completely revamped the ElementalX CPU governor. It's still multiphase and changes according to context like before, but switches frequencies very quickly. It samples fast and ramps up to max frequency a lot but quickly drops to minimum frequency. It should be at minimum frequency most of the time. Input boosting is built-in. DO NOT USE CPU BOOST! Make sure cpu-boost is disabled (should be by default unless you've enabled it in an app or something).

Input boost is for 300ms by default. It doesn't actually increase the frequency, it just doesn't let it drop below input_min_freq for the length of the timeout after the first touch. It's not continuous, only active on the first touch. Increase this for extra smoothness (it's smooth for me).

Gboost is included again, so the governor behaves differently while gaming. During graphics intensive gaming, the frequency doesn't drop below gboost_min_freq (set to 1574MHz by default).

Finally, I've added a max screen off frequency to the governor. It's set to 1728MHz by default.

Other changes: I made noop the default i/o scheduler. We'll try it for a while and then maybe try deadline and fiops. I added the restorecon cpufreq thing to ramdisk that other were talking about. I did NOT fix this up to work with the theme chooser, I will do something about that next release.

Download:

ElementalX-N6-0.21

Changes:

-disable mpdecision

-add msm-sleeper hotplug driver

-revamp elementalx governor

-various tweaks and optimizations

-noop is default i/o scheduler
[Nexus 6  Original Android Development] tysonwald:
Can't wait to try
[Nexus 6  Original Android Development] DARTHVAPOR:
Will this work with cm12 theme chooser?

Sent from my Nexus 6 using Xparent Cyan Tapatalk 2
[Nexus 6  Original Android Development] monkboy24:
Hey bro did u read flars entire post? He provided a answer for this exact question.

BTW I wasn't trying to be rude or anything
[Nexus 6  Original Android Development] erraggy:
Hey, [MENTION=4684315]flar2[/MENTION] thanks for such an in depth changelog! I've got the updated app and I'll give 21 a go. Really appreciate your work.

UPDATE: installing 21 went fine and I'm up and running on it now. One note is that all my settings in your elementalX app were reset and I went through the initial tutorial again. No complaints as I understand some of my previous overridden settings may have conflicted with the rewritten kennel.

Thanks again.
[Nexus 6  Original Android Development] DroidRC1:
Running 21 and one thing I've notice is that my screen turns on faster when waking, which is nice!
[Nexus 6  Original Android Development] Remoteconcern:
It feels very quick to me. Initially it lagged everywhere but i checked the ex app and it had held onto a few settings it didn't need. I cleared data and restarted it and all was good. Might be worth a try for anyone with a similar problem.
[Nexus 6  Original Android Development] n80k:
Just got a SOD on .21. Log attached. I have s2w,s2s,dt2w,fast charge,1024 read ahead and everything else stock/default except I'm running pure shamu 3.97. Hadn't had any issues until I flashed this kernel over the .20 version however

Btw I'm not sure if this was intentional or not but it was not very easy to find documentation for which log to pull. Maybe I'm blind and it is on the main page but I had to do some digging through old posts before I found where the log was located that you need (/sys/fs/pstore/console-ramoops). No biggie but I'm just sayin
[Nexus 6  Original Android Development] Ladduro:
Flashed it and left everything stock. Feels a little snappier, especially dialer animation, that was a little laggy in .20.

Will keep you posted :)
[Nexus 6  Original Android Development] antiochasylum:
[MENTION=4684315]flar2[/MENTION] - I don't think I have ever felt a phone more fluid than it is now. That ramp up is just awesome. The phone feels so smooth and fluid.

Thanks again for all your hard work. We ALL appreciate it. :)
[Nexus 6  Original Android Development] inzaghi75:
Flar2 says probably he includes theme chooser support. With the test build it doesn't work.

Gesendet von iPad mit Tapatalk
[Nexus 6  Original Android Development] danarama:
In future he will
[Nexus 6  Original Android Development] danarama:
[MENTION=4684315]flar2[/MENTION], this is an incredible update. Thank you so much for looking into your own hotplugging method!

Off topic (to this post anyway) - doubletap to wake, I assume this doesn't have the same battery issues as the Nexus 5? My ROM has the recompiled Power thingy to allow dt2wake but its pretty unreliable I find. Theres no halm in activating it in Elex too?
[Nexus 6  Original Android Development] Bontropi:
Unbelievable Kernel, Flar.

Keep Rockin'!
[Nexus 6  Original Android Development] D-m-x:
You need to enable both, Sweep2Wake and Douple Tap to Wake for flar2 own DT2W implementation. If you choose to enable only DT2W in the App it will be Googles Implementation (pretty unreliable). Also he said something like 0,1 - 0,2% impact on the Battery per Hour if you enable it, so basically nothing.
[Nexus 6  Original Android Development] stumpy352:
Hmmm. On .21 now. Just got the notification to update to .20 interesting. ? I think .20 must be jealous of .21 new hot plugging. Lol.
[Nexus 6  Original Android Development] fallingd0wn:
Very impressed with .21 so far. Noticeable performance improvement.
[Nexus 6  Original Android Development] danarama:
Thanks.. Intersting

Just re that 0.1 / 0.2, is that on top of the google implementation? I would imagine not since the digitiser needs to be on anyway?
[Nexus 6  Original Android Development] PDP///M:
. 21 is ticking all the right boxes for me, for the few hours I've been playing with it. Need a few days to see how battery life goes, obviously. But i can sacrifice a bit of battery for smooth and snappy. Good work Flar! One question though. When the phone boots up, does the cpu run 4 cores at max frequency?
[Nexus 6  Original Android Development] flar2:
Nothing showing in the log, but with the way my luck has been going on this device, the new elementalx gov might have the same rare stability issue on certain hardware as the old ex gov. I guess we'll wait and see.

The 0.1-0.2% per hour is on top of normal idle drain. Stock dt2w and my implementation are about the same. Nexus 5 is the only device that has significant drain from the wake functions, now everyone thinks they cause drain. The problem on the Nexus 5 was that the digitizer could not receive power without the entire LCD panel being powered on (the LCD using much more power than the simple digitizer).

For me, the battery is better.

The phone boots up with the performance governor and the hotplugging doesn't start for 60 seconds after boot.
[Nexus 6  Original Android Development] Ladduro:
Not sure why, but for me scrolling in Chrome and tapatalk is laggy and chopped. I am on 4g at the moment with all stock kernel settings.

Will continue to test and let you know, but 20 was smoother, at least while scrolling

Sent from my Nexus 6
[Nexus 6  Original Android Development] danarama:
Thanks for clarifying. I knew the N5 issue was somehow related to the digitiser, but Im new to n6 so wasn't sure how it worked. I'm happy with the use of 0.1/0.2 as im using the google implementation anyway
[Nexus 6  Original Android Development] bikeryder007:
The one from Flar works WAY better than the stock one. Once you enable s2w, double tap works every single time.
[Nexus 6  Original Android Development] danarama:
Yep much more reliable.
[Nexus 6  Original Android Development] michmeister:
Wow. Didn't he just state that it wasn't . read man.
[Nexus 6  Original Android Development] Remoteconcern:
Flar, I would love to be able to have just double tap to wake without swipe enabled. Unfortunately the google method is terrible - yours is far better. Is there any way we could enable just your version of double tap to wake?
[Nexus 6  Original Android Development] jtwlbz:
[MENTION=4684315]flar2[/MENTION] I just got rebooted with 0.21 while playing Crossy road. Everything stock except double tap wake and swipe to sleep.

https://drive.google.com/open?id=0BxVfdaBxfZXBV0Voa0R2eUo1enM&authuser=0
[Nexus 6  Original Android Development] n80k:
Doubtful. I hadn't had any issues until now and I've been running elementalx since I got the phone. Could be the custom ROM who knows. Sorry the log didn't help
[Nexus 6  Original Android Development] Johnny424:
running great flar. thanks for your work on this. first time I have run without mpdecision. very smooth. as soon as you merge the cm fix my life will be complete

thanks buddy
[Nexus 6  Original Android Development] n80k:
Just had another episode like I had earlier except instead of holding down the power button to do a reset I just let it be and about 10-15 seconds later the screen popped on again

Other than that this phone is so smooth it feels slippery. Thank you so much [MENTION=4684315]flar2[/MENTION]
[Nexus 6  Original Android Development] Johnny424:
any oc or UV?

nvm see earlier post
[Nexus 6  Original Android Development] sn0warmy:
Just switched over to this kernel (v .21) after trying Franco and Leankernel. It is very smooth and snappy.

However, I am encountering one issue. During setup I enabled 'sweep up to wake'. It works if I am sitting and messing with the phone. However, if I put the phone down and let it sit for 1+ minutes, if I go and sweep up on the screen it will not respond until I sweep up 3-4 times. I haven't touched any kernel tweaks. Any ideas?
[Nexus 6  Original Android Development] adio201:
Same thing with me ever since I got my nexus 6. I was trying sensi kernel after some tweaks it run smooth and fast with small sipps of battery . I'm trying this kernel again after seeing the update but like snowarmy said I have to tap the phone a few times to turn it on and I'm using ex governor and I notice some lags play some games so I'm using performance governor right now

Send from Nexus 6 rocking Pacman ROM :D