yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Droidphilev:
Thank you for the tip. Coming from Samsung devices it's all new to use stock roms. Since BB is integrated in most custom roms and every Samsung stock rom i ever had only lasted for a few hours i was never in need for the installer ;)
[Nexus 6  Original Android Development] magnamentis:
B is the recommended procedure by atl4ntis and it has proven to be a good idea, it did never cause issues but flashing 2.61 before last did 3 times out of 10 for me and for others as well as i've been reading. however, both ways are possible while i wanted to mention that for those who have error messages in twrp after flashing 2.61 and not getting further, there have been many BTW and none who had trouble flashing 2.61 last, even flar2 said that the order does not matter kernel wise. now all the info is on the table and however has issues with one method is aware of possible workarounds which is the whole point of it. all good thus far, thanks.
[Nexus 6  Original Android Development] flar2:
If the rom is pre-rooted, save yourself the trouble and just flash elementalx
[Nexus 6  Original Android Development] flar2:
Once you have root (by whatever method) you can just flash elementalx. No need to flash SuperSU again or do any tricks.
[Nexus 6  Original Android Development] bond32:
What color profiles (if any) do you guys prefer? Perhaps we should start a poll...

I tend to lean to the "cooler" setting from here: http://xdaforums.com/showpost.php?p=59092146&postcount=3017

Red: 232

Green: 228

Blue: 255

Saturation: 26 (again season to taste)

Value (Gamma): 126

Contrast: 128 (default)

Hue: 1515

Props to Wrinklefree, all of his profiles are awesome.

I also like the one labeled "Janzen". Thoughts?
[Nexus 6  Original Android Development] pkgnex:
I actually split the difference between the two Wrinklefree profiles (6500 and 7500, I think). I found the cooler one a bit too cool, and the warmer one too warm for my tastes, but averaging the values seems just right!
[Nexus 6  Original Android Development] magnamentis:
to what avail should we start a poll, if 99% would use yellowish colors i still would choose cooler colors for me. for one guy it's totally irrelevant what others prefer, use or have and this is not a smalltalk place to post personal preferences and compare wallpaper, sizes and length LOL. take this to facebook or twitter IMO.
[Nexus 6  Original Android Development] bond32:
Uh, ok then.

Perhaps I got tired of seeing all the "OMG WUT HAPPENED, WHY MY FONE BROKEN" posts?

Perhaps it would be nice to talk about something that isn't how to install the kernel?

At any rate, I would try something that someone else felt was their preferred color profile. If someone felt a "yellowish" profile was best for them, heck I would try it.
[Nexus 6  Original Android Development] magnamentis:
ok, get your point while i think you certainly agree that this is not the right place, especially we don't want more non-sense added to the previous non-sense because we get tired of the previous non-sense LOL i'm kidding but mean it as well, no offense, i understand you just trying to explain my previous reply. all good.
[Nexus 6  Original Android Development] bond32:
Agree to disagree to agree? LOL

But you're right, we can discuss color profiles elsewhere, seeing how they are with most all kernel apps not just the EX manager.

Back to the kernel then! I have no other questions other than saying awesome work to the dev.
[Nexus 6  Original Android Development] backdown00:
I am very new to this kernel have always run hells but have heard great things about ex. I wanted to ask, hells core had a mako hot plug that allowed a dual core build (and would ramp up if necessary), is this possible in ex kernel? Thanks all!
[Nexus 6  Original Android Development] nathanchance:
If you have the ElementalX Kernel Manager, it is possible but to be honest, I don't think it is worth it. I tried it and the battery results were not that much better. The custom hotplug that is included will offline two cores while the screen is off and online all four when the screen is on. The ElementalX governor is pretty good about keep the frequencies where they should be under light loads.
[Nexus 6  Original Android Development] jbeezley:
I was just looking for some color profiles... Thanks. Where can I find some info about what all these settings control in kernel adiutor? I have 3.07 installed, but honestly I have never even known how a kernel functions except it's like the main thread of the device tree?? Something like that? I really want to understand it and not just blindly adjust things and see what happens.
[Nexus 6  Original Android Development] afilopou:
Amazing battery. Thanks Dev.

6.0.1 stock

Always data on and always paired with moto 360 2nd gen.
[Nexus 6  Original Android Development] biglilsteve:
This isn't possible in EX is it? The only available hotplugging solutions are MPDecision and "Custom Hotplugging".

Custom Hotplugging runs a set number of cores when the screen is off and a set number of cores when the screen is on (2 and 4 by default, respectively). You can change these values to whatever you want, but there is no provision for the hotplug to run two cores under light loads and then dynamically online more cores when loads are heavy.
[Nexus 6  Original Android Development] montbazon:
hello, flar2

I did try both file systems ext4 and f2fs with CM13.

CM13 with ext4 boots well without any problem. But with f2fs sadly doesn't boot at all. What i can see is just endless booting animation.

I tested many of kernel from xda. But the only one lean kernel is that can boot with CM13.

I wonder know whether you could fix this issue.

Thank you in advance
[Nexus 6  Original Android Development] magnamentis:
interesting how many folks go through so much hassle to change to f2fs, not worth it IMO and it not only limits compatibility of some kind but at the end of each API life cycle one has to wait longer to get new stuff up and running. especially on nexus devices where flashing factory images which is sometimes best practice and sometimes even needed, makes one go through the entire process again. be glad if it doesn't work and stick to default file system ext4.

yes this is personal preference, just thought it worth to post my opinion on the matter once in a while, everyone shall proceed as he likes of course :laugh:

while the main reason to post this is because XDA is full of post of folks with trouble that is related to f2fs.
[Nexus 6  Original Android Development] montbazon:
Actually i hadn't any interest in f2fs before Nexus 9 get the file system with factory. Yes Google did. Not by any other developers.

As you know, ext4 is very mature and effective file system. But it wasn't constructed for NAND memory.

And f2fs have been already merged into Linux mainline kernel.

IMHO it could be a one of better option for a future flash device.
[Nexus 6  Original Android Development] magnamentis:
yes, that way i agree, first of all it could be the future once it comes out of the box, then on devices with real lags and stuttering due to read/write or other issues that can make the difference. my point was that we're not there yet and beside the fact that we're all free to which extend we can or want to set priorities it was just an opinion, based on the many issues users are posting across the board. BTW i've been discussing this with some of the most renown kernel devs and they took similar stances while it remains a personal decision

last but not least, if not many users went through a lot of issues to make things happen we would advance much less rapidly, hence all good as it is :good:
[Nexus 6  Original Android Development] backdown00:
That might actually work as my phone never really scales above 2 cores online so if I can force it to only be 2 - pretty much same scenario :). Thank you for this info!
[Nexus 6  Original Android Development] flar2:
Sorry for the late response, but yes this is possible with EXKM.

Goto the CPU screen then Hotplug options, and click "Run with all cores online" to disable it. It will then run with two online and hotplug 3 and 4 as needed.
[Nexus 6  Original Android Development] Ghisy:
Hi [MENTION=4684315]flar2[/MENTION],

I've finally updated my Nexus 6 to Marshmallow (Chroma) and I flashed ElementalX as usual. I did leave SELinux on enforcing though. Would it cause any problem with viper4android? Because it needed a permissive kernel on Lollipop to function properly. I've only flashed everything last night so I don't have much "real world" usage so far.

Thanks for the heads up!
[Nexus 6  Original Android Development] nathanchance:
Chroma in particular has whitelisted Viper so that it can work with an enforcing kernel.
[Nexus 6  Original Android Development] Ghisy:
So it's whitelisted on the ROM side then? Good! I wasn't sure how the newest SELinux policy worked. Thanks! (again, I haven't run into any problem last night when setting things up but yeah, just wanted to make sure...)
[Nexus 6  Original Android Development] RandomPooka:
I'd considered messing around with that before. Does anyone have any experience or comparisons between running with all cores all the time vs hotplugging them? Is battery life and/or heat impacted much? I'm sure many apps only use a singe core, but if you're multitasking your face off, would it be constantly "powering up" offline cores and shutting them back down and causing more drain than just leaving them on and idle?

Apologies if I'm reading between the lines here and assuming that enabling a core on the fly may cause more drain than just leaving it sit idle in the background at a low frequency, but that's kind of what I'm trying to learn. I'm currently envisioning it as starting and stopping your vehicle's engine every time you use it. If you're going to be using it for a long time, you obviously would leave it running, but if you're only using it occasionally, you wouldn't leave it running in your driveway for three hours just in case you maybe have to drive somewhere. The comparison I'm trying to figure out is something along the lines of a postal delivery truck turning the vehicle off at every mailbox to save gas, but actually causing more problems because of firing the vehicle back up so frequently and for short bursts.

TL;DR Are the benefits of shutting cores down offset by any increased power consumption when enabling them again on the fly? Or is it more efficient to leave them run at a low, low idle?
[Nexus 6  Original Android Development] nathanchance:
I tried it at first since I was coming from Mako Hellscore and I did not notice any difference when I switched to the normal custom hotplug. The custom one offlines two cores while the screen is off and turns them all on when the screen wakes. There may be a little battery saving capacity in two all the time and four when needed that I just didn't notice but I did notice a couple of performance issues. I just leave it stock now and don't even mess with it.
[Nexus 6  Original Android Development] nhizzat:
None. I've got V4A running with SELinux enforcing on the latest build. Any one of latest zips provided by guitarherod is all you need. Flash in TWRP, enable V4A, done.
[Nexus 6  Original Android Development] nixie2121:
I just did this and can confirm it is working with enforcing!
[Nexus 6  Original Android Development] biglilsteve:
Yeah the general consensus seems to be that dynamic hotplugging is counterproductive with our particular SOC. I always end up with performance and stability issues when trying to use a dynamic hotplug.
[Nexus 6  Original Android Development] JacobManning17:
Are you using any custom settings? I can't even seem to get close to this good of battery life!
[Nexus 6  Original Android Development] biglilsteve:
No custom settings needed. Getting 5hrs SOT is easy with M! This is me right now.
[Nexus 6  Original Android Development] jigsawmv:
What layer are you using?
[Nexus 6  Original Android Development] biglilsteve:
That's Commute/Evolve. Best couple bucks I ever spent.
[Nexus 6  Original Android Development] Droidphilev:
You mind sharing your settings please?
[Nexus 6  Original Android Development] biglilsteve:
I only reduced max frequency to 2265 and touch boost to 1190. And those probably didn't really do anything. Honestly most people should be able to get 4-5 sot on stock settings.
[Nexus 6  Original Android Development] Droidphilev:
Thank you!
[Nexus 6  Original Android Development] magnamentis:
i mean this serious, can some folks with less than 6-8h SOT tell me what they're doing, i can do whatever i want ( within my use case ) and never need more than 11-12%/hour on full brightness non-stop playing cards on wifi with bad signal strength and 3G. that makes >8h SOT

i mean the fact that people are asking for a 5h SOT setup indicates that many of you have even less than that bad SOT and find 5h even good while i'd immediately start finding the reason if i had such bad SOT combined wit more than 0.3%/h drain in idle over night.

my kernel is set more or less default where it counts, default frequencies, slight OVER volt to avoid RRs, touchboost slightly higher, 2048 readahead, fiops and highspeed. all together this not even a battery friendly setup.

what i do for battery life is i have tasker set to manage a few things like brightness, radios etc. when conditions are met (based on remaining battery percent and internet connection) & greenify which with screen on has less impact. further i'm using exposed whithout amplify or such which certainly does not boost the battery?

i'm genuinely a bit at loss how SOTs can be so low for some and then finding it even good, i'm really interested to learn about which use cases and setups could be responsible for that, thanks
[Nexus 6  Original Android Development] dtroup64:
I've NEVER gotten anything close to 8 hrs SOT. I'm a marketing director for a museum, am on my phone a lot. Take pictures all day, Instagram them for the museum, tweet, facebook post etc. At my job, we text each other quite frequently, and as I'm in the galleries, and not at my desk, I check and respond to work email all day. I've NEVER ended up with more than 2.5 hrs of SOT at the end of the day, and I usually have about 40 or 50% left. I truly cannot imagine what I would need to do to have 8hrs SOT— except perhaps just leave my phone's screen on purposefully and have it running Amazon Kindle or something so the screen didn't shut off... :)
[Nexus 6  Original Android Development] magnamentis:
thanks, very much appreciate your response while it just adds to my confusion, i know that i'm not the only one with 7+ hours SOT which made me curious to find out what might be the reasons. what comes to my mind are LTE users, mostly on LTE and doing all the day long tasks and syncing on LTE with a sup-optimal signal strength. this is the only thing that comes to my mind which would account for 2-3h difference while i'm explicitly not addressing gamers. playing power demanding games can kill the battery in much less than 5h, of this i'm fully aware.

thing is that i'm syncing everything that exists in google sync + photos (offline photos) + dropbox + dropsync (offline dropbox) and so on for 8 accounts, 5x gmail and 3x IMAP.

in short, i really suspect that it could be the difference between wifi usage and LTE + medium to poor signal that makes for the difference.

thanks again for your contribution :good:
[Nexus 6  Original Android Development] biglilsteve:
That hits the nail on the head. I personally spend more than half of each day on an LTE connection. So on these average days, I consistently track for right around 5 hrs SOT. If i am off work and home all day on WiFi (5 GHz), I can generally track for right around 6-7.

But you said a lot earlier about using tasker and greenify which I'm sure helps with battery. You also alluded to the fact that you spend the bulk of your time on WiFi which is huge. Maybe a lot of us arent.

I don't think its crazy at all for an average user with minimal tweaks to track for 4-5 hrs SOT especially if they don't get to be on WiFi all day.. The crazy thing is for a user to consistently track for 7 to 8 like yourself. That's the exception where people need to ask about use case, not the other way around.
[Nexus 6  Original Android Development] magnamentis:
all clear, thanks for confirming that there is something to it.

[HUMOR] of course i cannot ask s to my own use case LOL only about that of others haha.....[/HUMOR]
[Nexus 6  Original Android Development] Polv89:
What's your favourite preset for perfect whites?

Inviato dal mio Nexus 6 utilizzando Tapatalk
[Nexus 6  Original Android Development] Scott:
[MENTION=4684315]flar2[/MENTION]

Man, I just cant talk enough about how good your kernel is! If you ever need a spokesman you can count on me... (although I already push your kernel when I can ;))

I migrated back to a Nexus 6 and am running the paid Elemental X app and latest kernel and I am getting crazy insane benchmarks!

Thanks Dude!

-Scott
[Nexus 6  Original Android Development] jbeezley:
I'm thinking there's a bit of misconception with this SOT issue. SOT isn't necessarily a continuous use of the screen non stop, but an aggregate of the time it's been on. I'm a user that has the screen on for 5-30min at a time, continually running mobile data on a horrid data connection, never WiFi, yet I also consistently get over 6hrs SOT. Keeping the phone awake is probably eating into these users battery that constantly CHECK the phone, rather than use it.
[Nexus 6  Original Android Development] derdjango:
Hey, I'm running Elite kernel and wanna try elementalX (running pure nexus). Since we're not supposed to flash over a custom kernel, how do I proceed in flashing the kernel?
[Nexus 6  Original Android Development] KonoeKyon:
Reflash pure nexus then flash elemental, and make sure there's no scripts in init.d or su.d that set kernel settings.
[Nexus 6  Original Android Development] derdjango:
Thanks mate. So I'll just wait for the next pure nexus update then. Can I just delete Kernel Adiutor to reset the settings?
[Nexus 6  Original Android Development] KonoeKyon:
Yeah if you use any kernel apps clear their data also. But that won't affect any init.d scripts that may or may not be present in the system, I don't use pure nexus myself so I'm unsure if they have any that would affect the kernel.
[Nexus 6  Original Android Development] magnamentis:
yes that's it and nobody ever said otherwise. i think it's clear that it's rare thing, almost only for thesting if at all, that someone is having his/her display on for 6-8 hours in a row. just can't see why this could have been understood otherwise.

basically to make this clear i even posted the 11-12%/h and that the over all SOT is extrapolated, except if someone would have it on till the battery dies which as well is neither recommended nor a common use case. so we're in full agreement about those facts but it was always meant and communicated like that, at least from my side.
[Nexus 6  Original Android Development] JacobManning17:
I have WiFi, LTE, and battery saving location services on all day, adaptive brightness, and using stock EX settings I get just about 3-3.5 hours SOT given use over an 18 hour day.

I'm a college student in the city so I'm constantly moving (phone connecting to different WiFi networks on campus) and occasionally have poor cell signal in large cement buildings. I use my phone mostly for texting, web browsing, snapchat, and listening to music.

According to the "active drain" section in EX Kernel Manager, it is ~20% per hour on stock settings (ergo a maximum of 5 hours SOT if I did nothing besides use the phone straight for 5 hours with the screen on).
[Nexus 6  Original Android Development] benleonheart:
OK; did te following.

1.) flashed latest cata stable

2. flashed latest cata MOD

3. Flashed elementalX

4. Flahes superSU 2.61

5. boot into system, install Elemental X Kernel Manager

Look at all cores, stuck at 300.

Elemental X on the Nexus 5 would put core0 online with 300 all the time and the rest in 0, and as needed they would power up.

Any clue why this is not working for me on Shamu?
[Nexus 6  Original Android Development] flar2:
No clue. I've never had this, nor have I heard of it happening.
[Nexus 6  Original Android Development] benleonheart:
Compared it to my NExus5 Settings and what I'm seeing on the Nexus5 is that I have elementalx governor, but when I go into the hotplug options I'm not being able to activate "mpdecision", whenever I click on mpdecision it sets itself to "disabled"

Thanks.
[Nexus 6  Original Android Development] Lancez:
You either flash the whole stable ROM or flash the MOD on top of stock ROM, why did you flash both of them at same time? I think that could be the cause of your problem.
[Nexus 6  Original Android Development] benleonheart:
No, instructions say to flash the latest stable, and then the newest mod...

latest stable is Dec8, latest mod is Dec14... I've got that part straight.

The thing is I cannot enable mpdecision for elementalx governor. whenever I click on it, it turns into "disabled" instead of mpdecision.
[Nexus 6  Original Android Development] flar2:
Please run with the default settings. Mpdecision is disabled on the device. The setting in the app is old and doesn't work anymore.
[Nexus 6  Original Android Development] DonQuixote77:
Correct me if I'm wrong (since I've flashed Cataclysm on my wife's Hammerhead), but the December14 file isn't so much a "mod" as it is a delta update.
[Nexus 6  Original Android Development] benleonheart:
On the Nexus6 I am moving from Stock to Cataclysm 6.0.1 and I preferred to go the Stable 8th route. Which is followed by the December14 file (there are somethings that changed from Dec8->Dec14, hence me flashing it)

I could've gone the Stock-FlashonTopDec14 route but I said, nah.
[Nexus 6  Original Android Development] Lancez:
You should have stated Dec.8 instead of stable + MOD in the first place. Anyway, I'm running the cats mid on stock with EX kernel with default setting, no problems at all.
[Nexus 6  Original Android Development] benleonheart:
Yep, I'm gonna follow your and flar2's advice on running it on the default settings... that's how I did it on hammerhead also...

Thanks!
[Nexus 6  Original Android Development] Lancez:
You got that right, it's beta but stable as Dec.8

---------- Post added at 01:45 PM ---------- Previous post was at 01:43 PM ----------

Once you got everything right, you'll love this kernel. Performance and battery life are phenomenal.
[Nexus 6  Original Android Development] benleonheart:
I agree, loved it on Hammerhead, got around 4.5 SOT on stock cooling.
[Nexus 6  Original Android Development] DonQuixote77:
I just wanted to say that it's great to see a fellow Ottawan (is that even a word?) doing such great work for the Shamu and kernels in general.

I've only just started trying out custom kernels on my device (just got it over a month ago), and this has been the best for me hands down since I flashed it a couple days ago.. The ElementalX governor works great, it really gives a smooth UX while keeping frequencies in check.

Thanks so much for your work. Cheers!
[Nexus 6  Original Android Development] magnamentis:
your contribution is very much appreciated, wish we were closer in distance, would be some kind of challenge to give you five ( or more hours LOL )
[Nexus 6  Original Android Development] jbeezley:
The above quote is what prompted the reply from me to which you later replied below. I apologize if I quoted the wrong person, technically.

Yes, we had been in agreement the entire time, but then again I was actually positing a scenario in which these users are commonly getting sub par SOT. You and I seem to be doing fine, after all.
[Nexus 6  Original Android Development] Alxoom33:
Yes, but they are really the same thing.
[Nexus 6  Original Android Development] Tex99:
What is the default read ahead value ? Thank you
[Nexus 6  Original Android Development] nathanchance:
512
[Nexus 6  Original Android Development] flar2:
Cheers!

Ottawan is the word. I had to look that up a few years ago when I moved here.