yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Android Development] indian84:
AFH is undergoing maintenance. Try after sometime.
[Nexus 6P Android Development] jr67:
Looks like androidhostfile.com is down for maintenance. Nothing Nathan can do about that.
[Nexus 6P Android Development] snoprosledneck88:
Looks like I downloaded just in time. About an hr ago or so:good:
[Nexus 6P Android Development] Craxx:
some mirror?

best regards

Craxx

Sent from my Nexus 6p
[Nexus 6P Android Development] winxuser:
Msm hotplug and ondemand Gov works a treat for me. Unplug from the charger at 9am and by 6pm it was still in the high 80% battery mark, excellent work.
[Nexus 6P Android Development] nathanchance:
Can't do a mirror because I don't have a copy of those files anywhere but AFH. I did apply for a Basketbuild account so if I get approved for that, I will have builds in both places.
[Nexus 6P Android Development] snoprosledneck88:
It appears AFH is back up.
[Nexus 6P Android Development] shafubhai:
How is that even possible? What's your usage like? Please share!!!!
[Nexus 6P Android Development] winxuser:
minimum to mild usage, i dont play games, its mainly just browsing through facebook, xda, maybe a youtube video

---------- Post added at 09:19 AM ---------- Previous post was at 09:18 AM ----------

99% of the time 4 cpu cores are turned off
[Nexus 6P Android Development] nathanchance:
I am actually going to give a write up on battery life/performance here tonight, got a lot to discuss lol.
[Nexus 6P Android Development] shafubhai:
Are you using any profile or hotplugging?
[Nexus 6P Android Development] winxuser:
No profile. Just msm hotplug turned on and core control turned off, ondemand Gov on both big and little
[Nexus 6P Android Development] winxuser:
That's all I have done :/ but yeah battery life is great, but Nathan may have a better idea for people
[Nexus 6P Android Development] feis:
Thank you! Nice educational read. I also want to add one thing. Correct me if im wrong, but little cores doesnt actually use less power, i saw somewhere a table of voltages for both big and small, and small is efficient only until like 960mhz frequency, after that voltages increases a lot and it uses even more than big in the same frequencies, for example 1300mhz
[Nexus 6P Android Development] evilryry:
I already knew a little bit on how this all worked but there was a lot of things touched on that I didn't know/fully understand. Thanks for the nice educational post Nathan.
[Nexus 6P Android Development] nathanchance:
Yeah, that post was from [MENTION=4752299]Alcolawl[/MENTION], it was a great read as well. It may or may not use more power since electric power is technically voltage multiplied by current and I don't believe that we have a chart of currents at the different voltages. But yes, the voltage increase at higher frequencies will certainly contribute more to power consumption :)

Glad to hear :)
[Nexus 6P Android Development] xperator:
No not really. I think what you referring to is for 5X ?

Efficiency is a different topic. I've just started learning and experimenting about that myself but as Nathan said the main rule is that we should use both clusters equally. Little has 6 more clock steps after 960 (including 2 oc frequencies) so there is no way 960 is the most efficient clock on Little. Not to mention if you try to lock Little to 960 most of your casual tasks would run into stuttering issues. So 960 is definitely not even powerful enough. It is a good clock frequency to work with, but not super duper good.

Also who said higher frequencies on Little are battery killers, evil and all that ? With DragonX V1 I used the highest OC clock which is 1708 to handle most of our heavy loads on Little. And we had some good results. 4 users including myself reported acceptable stats with 5 SOT for each cycle. So that wipes the idea about higher frequencies using high voltages and bla bla

Interestingly with DragonX V2 we went the other way, we locked the max of Little to 1344 ignored anything over that. Again good results. Both profiles weren't perfect obviously we had some mixed feedbacks but there was no absolute negative results.
[Nexus 6P Android Development] feis:
Im not talking about efficiency, im talking about voltages and power use. And im not talking about lags or anything, we are talking bout different things lol. And 5x uses same cores and same architecture, just 2 less big cores, so very simmilar:)
[Nexus 6P Android Development] xperator:
Same thing. High clocks and voltage doesn't mean they would eat your battery in 1 bite

Also they are not really similar. Someone asked Alcolawl if that would apply to 6P and he said no those are based on sd808.
[Nexus 6P Android Development] nathanchance:
The voltages may not identical but the technologies are identical so the logic should still be applicable.
[Nexus 6P Android Development] xperator:
Yeah the part about migrating tasks to Big earlier may apply Sometimes I wish I could program interactive governor as well but it's not possible. Who knows maybe they can find a way to make Big handle more tasks using those parameters but honestly I don't think they are doing it the easy way. I had that idea from the beginning and l've kinda done that with DragonFly

Not sure if you ever monitored DragonFly clock usage that profile uses Big more than any profiles out there. Even with smallest task both clusters will ramp up asap so we definitely have Big working all the time.

[MENTION=1453730]feis[/MENTION] if you still looking for highest efficient clock on Little I think that would be 1344, not 960.
[Nexus 6P Android Development] Alcolawl:
I've been running a custom profile for the last week or so that caps the LITTLE cluster at 1248, while passing along more tasks than normal to the big cluster. The big cluster is also tweaked in a way that it will jump to 960 under even moderate loads. Very smooth, great battery, and no stuttering to report. This is backed by testers as well.

I said that this may not be applicable to the SD810 because you have two extra A57 cores sucking down power. If you look at power consumption charts for a quad core A57 vs a quad core A53 under, the difference is pretty clear. With the SD808 the power consumption for the SD808 Is almost halved. So this methodology just plain works better for the chooser in the N5X.
[Nexus 6P Android Development] rignfool:
So... I have some questions on the 'race to idle'

If race to idle is so important... Why are we using interactive? And even more so... Why are the interactive profiles so popular? Wouldn't ondemand... Or ondemand based still be the way to go?

All they do, is slow down the twitch in interactive... Which is counterproductive to the race to idle philosophy... No?
[Nexus 6P Android Development] Lord. Tech:
hey, which wake gestures are included? dt2w? up,down,right,left sweep? double tap power bottom shortcut? i use these on ex currently but i really wana try the latest ninja with hotplugging :D
[Nexus 6P Android Development] nathanchance:
I mean you are not wrong but I think the logic is that interactive is a more flexible governor, you can have it ramp up like ondemand or you can keep it conservative, all by messing with some tunables. Ondemand's aggressive attitude is not always necessary to be efficient. You have to take into account power consumption when considering what is efficient. That's the goal of the interactive governor, to scale appropriately with the various loads and provide the optimal range of frequencies.
[Nexus 6P Android Development] kyzn:
Judging from the icon at the top left, Resurrection Remix.
[Nexus 6P Android Development] Toutatis_:
Probably Resurrection Remix judging by the logo at the top left of the status bar

Edit: ninja'd
[Nexus 6P Android Development] kyzn:
[MENTION=6842057]nathanchance[/MENTION] spreading the influence. :D
[Nexus 6P Android Development] TheUndertaker21:
Love all the blue thing dude. Gonna do the same:)
[Nexus 6P Android Development] atrix2man:
Resurrection Remix

---------- Post added at 12:08 AM ---------- Previous post was at 12:07 AM ----------

Blue has always looked best to me. Reminds me the ICS days
[Nexus 6P Android Development] nathanchance:
That's the spirit :svetius:
[Nexus 6P Android Development] chachin:
off topic. who ready for nexus2016 :D
[Nexus 6P Android Development] kyzn:
I'm ready for Nexus 2017.
[Nexus 6P Android Development] nathanchance:
Lol not me, I am not a fan of the design and HTC's last Nexus (9) was a disaster. I'm hoping that the device tree and kernel source aren't completely botched as I may upgrade to it in 2017 depending on any deals and how improved the 2017 Nexus is. We'll see though. I'll for sure be on Angler for another year or so.
[Nexus 6P Android Development] resynx:
I have to say this is the first time I'm not itching for a new Nexus release. The 6P hits all of the major points and to this day I am still in love with this phone. Never thought the day would come where I seriously consider not upgrading to the new Nexus :D
[Nexus 6P Android Development] chachin:
ok im on 066-9 eas df linaro6.1 and i want to move to ninja 1.2 so.. should i um dirty flash my rom then kernel and reboot or just go ahead and do it like an update since its made by you all mighty kernel god [MENTION=6842057]nathanchance[/MENTION] :o

edit:

oh goodie goodie new rom update i guess ill just clean flash and all that bs thanks for your answer dude
[Nexus 6P Android Development] nathanchance:
I would dirty flash your ROM then the kernel.
[Nexus 6P Android Development] minhgi:
I just have the kernel installed and seem to be very responsive. It seem UKSM is missing and found it to be very usable for efficient memory management. Is there in the future that the kernel can be added. Thanks
[Nexus 6P Android Development] nathanchance:
Where did you have this support before?
[Nexus 6P Android Development] minhgi:
I have only been using ElementalX and Franco. I regularly switch between them two depending when they get updated. Both have UKSM so I thought this feature was a norm for Nexus kernel.
[Nexus 6P Android Development] nathanchance:
They have KSM support (UKSM is a different thing but something I am curious about now). I also have KSM support in addition to ZRAM support: https://github.com/nathanchance/Ninja-Kernel/blob/m/mm/ksm.c
[Nexus 6P Android Development] minhgi:
Interesting, I though UKSM was an enhanced version of KSM. I didn't saw KSM the feature available in kernel auditor.
[Nexus 6P Android Development] nathanchance:
It is but it isn't in any of our kernels. I am actually adding the patch now and seeing what is up. It may not be optimal for our device but it is worth giving it a shot.

EDIT: Well it would help if KSM was enabled in my defconfig :silly: I'll enable that for sure next build regardless of how this UKSM thing turns out.
[Nexus 6P Android Development] minhgi:
Thanks allot for even considering. Just noticed your kernel stay idle at 302mhz and 3-5 percent cpu usage quite often when not doing much. That sure good sign when my phone will be in deep sleep and using very little power.
[Nexus 6P Android Development] theesotericone:
I'll be sticking with Angler as well. Not a big HTC fan and the leaks make the phone look like fatter than any thing released in the last 3 years. Who knows, maybe HTC will put it on a diet before release. Either way the 6P does all I could ask for currently. Development will stay strong for it since it's a lot of peoples favorite phone. Google will officially support it for another year. And we have another great kernel to use with it. I'll save my cash for something else. Like rock sliders for my new to me 4runner.:cool:
[Nexus 6P Android Development] nathanchance:
Yes, it's in the OP.
[Nexus 6P Android Development] Lord. Tech:
oh yes i read ''wake gestures'' in OP, a few other kernels just mean dt2w and camera by that, so just wanted to confirm it includes all the sweeps. now i have, thanks:good: gonna flash it soon.
[Nexus 6P Android Development] tcat007:
It's this normal? I was paying Candy Crush and all of a sudden it seemed like it was moving in slow motion.
[Nexus 6P Android Development] nathanchance:
Do you have hotplugging enabled? Phone hot?
[Nexus 6P Android Development] tcat007:
Hotplug enabled, phone not hot. Funny, just tried a timed level (90 seconds) and it took about 10 minutes, very slow motion. Odd since all other apps feel normal.
[Nexus 6P Android Development] AzraelsKiss:
Have you tried flipping the big cores on?

Have a good one!
[Nexus 6P Android Development] nathanchance:
Well hotplugging will offline the cores but they should be onlining under load. Are you using the default values?
[Nexus 6P Android Development] Samuel Holland:
A big thank you for sharing your work and the info for Angler. I'm really enjoying this phone thanks to y'all on Xda taking the time to help others. May the good Lord bless y'all back times ten and keep up the good work.
[Nexus 6P Android Development] tcat007:
Was using default, tried hotplug on and off. Decided to clear cache and data in candy crush, and seems to be running smooth. Could have been some sort of FB connection problem. ???
[Nexus 6P Android Development] nathanchance:
Thank you for the kind words :)
[Nexus 6P Android Development] nathanchance:
Update!

Just your standard update, nothing really special to note. I'd definitely give my tech lesson post here a read though. Additionally, before I get questions on what it is, Adreno Boost will supercharge your GPU governor (make it ramp up faster). You can tune this in EXKM under the Graphics section or using this sys fs path (it takes a value between 0 and 3):

/sys/devices/soc.0/fdb00000.qcom,kgsl-3d0/devfreq/fdb00000.qcom,kgsl-3d0/adrenoboost

Download: v3.7 for N and v1.10 for M

Changelog: (also on Github)

Adreno Boost (thanks to [MENTION=4684315]flar2[/MENTION])

fsync toggle

Upstream CAF patches

KSM patch additions (thanks to [MENTION=5051294]frap129[/MENTION] for pointing these out)

Removal of some scheduler patches, which hampered performance/battery life

Fix for frequencies at boot (should for sure boot up with stock values now)

Interactive governor patches (thanks to [MENTION=3292224]franciscofranco[/MENTION] for these)
[Nexus 6P Android Development] eduardozeassesme:
Wtf links trolls?
[Nexus 6P Android Development] eduardozeassesme:
Sorry problem is on xda labs, on chrome is ok
[Nexus 6P Android Development] kyzn:
XDA labs still has issues with HTML.
[Nexus 6P Android Development] eduardozeassesme:
Really? But is the first time hehe lol
[Nexus 6P Android Development] AzraelsKiss:
It's a malformed /URL tag... The web client has translated it better than the app was capable of.

Have a good one!
[Nexus 6P Android Development] tcat007:
Just flashed 3.7. Looking at Kernel Adiutor, it has 2 lines under set on boot section, but in hotplug section it shows to be off. Does this look right?
[Nexus 6P Android Development] snoprosledneck88:
Thanks for the update good sir. Love your work. Keep it up!
[Nexus 6P Android Development] nathanchance:
Those need to say echo 1 not echo 0. I don't use Kernel Adiutor so I am not familiar with that interface at all.
[Nexus 6P Android Development] HikingMoose:
I just flashed Ninja got the first time (only had the phone for 5 days). I can't seem to get all 8 cores to hotplug using kernel adiutor, I haven't made any changes really, just tried turning on hotplugging. Is it just the kernel adiutor acting up?
[Nexus 6P Android Development] nathanchance:
Most likely because EX Kernel Manager works fine for me.
[Nexus 6P Android Development] tcat007:
I disabled everything set on boot and rebooted. Those 2 items in sys/ are both "0". I manually changed to 1.
[Nexus 6P Android Development] HikingMoose:
Grrrrr. I guess I'm have to buy yet another kernel control app, because this month everyone had moved on to another app. Lmao.

I wonder if there will ever be a time where everyone uses the same app for at least 6 months or a year. Haha

I just tried like 5 apps. Nothing has enough controls to even use hotplugging, so I guess I'm stuck buying ex.
[Nexus 6P Android Development] frost_nz:
EX should have been your first purchase... :p

You won't be disappointed with EX, it's well worth the small price.
[Nexus 6P Android Development] snoprosledneck88:
I'm surprised the EXKM handles so much stuff because his kernel doesn't support all of this. Just find that interesting.
[Nexus 6P Android Development] nathanchance:
EX Kernel Manager is the only kernel control app you'll ever need. I've flashed at least ten kernels before making this one and I have had zero issues with it. Single best $4 you'll ever spend. Support is fantastic, it works 99.9% of the time, and it is universal. The battery monitor I cannot live without and the user settings section is great. Sorry to sound like a promo but paid apps have such a stigma around them and this one doesn't deserve it.
[Nexus 6P Android Development] nathanchance:
Even though it is named for his kernel, it aims to be a universal control app. I added UKSM, which wasn't supported. I emailed him, he had it added in less than a week.
[Nexus 6P Android Development] HikingMoose:
It does have a lot of great features. Now I'm just trying to decide on what settings I want. I have 0 min big cores on, and only a minimum of 2 small, and it's not much worse than stock, but might have a little lady here and there, when it plugs all the way down to just two cores. You guys run with one big core and two small always on?
[Nexus 6P Android Development] feis:
If you hotplug all 8cores whats gonna drive your phone? Fairydust? Lol. 2little and 1big core should be online, thats normal
[Nexus 6P Android Development] kyzn:
[MENTION=4684315]flar2[/MENTION] just likes it clean.
[Nexus 6P Android Development] snoprosledneck88:
This is yank555 2.2 hot plug settings, having 2 little one big online. In 2.1 we had three little no big online. I liked that better, maybe just configure 2.2 to be the same. Just to try.
[Nexus 6P Android Development] HikingMoose:
I ended up turning one big core back to always on, and two little cores always on, but I enabled touchboost. So far it's performing well and battery is decent.

---------- Post added at 09:23 AM ---------- Previous post was at 09:18 AM ----------

I think you misunderstood something. I was trying to get MORE cores going. I could only use 4 according to the app.
[Nexus 6P Android Development] snoprosledneck88:
Touchboost will use more battery. Not saying you cant use it but I figured I would warn ya. You can disable touchboost and use inputboost. They kinda work the same but inputboost is more load based, if i recall correctly. Touchboost will jump to a set higher frequency every time you touch the screen. So for example when you texting, every letter will boost to the higher frequency. Inputboost wouldn't boost to the higher frequency till it needs to. Try inputbost 40ms-100ms and adjust the frequencies to your liking.
[Nexus 6P Android Development] tcat007:
Just bought EX manager. I can't find any mention of big/little was there was on Adiutor. I assume "big" is 1-4?
[Nexus 6P Android Development] shadowstep:
0, 1, 2 & 3 are the 4 little cores and 4, 5, 6 & 7 are the 4 big cores.
[Nexus 6P Android Development] HikingMoose:
I just noticed that ex manager uses for RAM then my launcher! WTH

---------- Post added at 12:40 PM ---------- Previous post was at 12:36 PM ----------

I know it uses more battery. But it would appear that touchboost isn't an option, I'm actually using input boost....yet it's functioning the same as touchboost. When it detects input, it boosts.

I'm guessing input boost = touchboost.
[Nexus 6P Android Development] Toutatis_:
You can't see any touchboost option in EXKM because it's disabled by default with Ninja Kernel.

Input boost and touch boost are two different things.
[Nexus 6P Android Development] shadowstep:
A few days back, my device suddenly started lagging crazy (irrespective of the EXKM profiles or your stock settings) after I flashed an update of your kernel. Don't really remember the exact versions on which I faced the issue, but if I'm not wrong, it happened on 1.9 and 1.10rc2. I have no idea what or why it happened, but it did. I moved back to ElementalX and the issue disappeared. However, I just flashed the recent update and it's all fixed! It is working like a charm again. And I can't be happier! Keep up the good work! Appreciate it. :D

Sent from my exceedingly happy Nexus 6P flying away to glory, powered by Ninja Kernel! ;)
[Nexus 6P Android Development] tcat007:
I'm new to exkm. How do you get the user governor profiles to show up on this list?
[Nexus 6P Android Development] nathanchance:
You need to select interactive for both cores and click Governor options ... > Load
[Nexus 6P Android Development] tcat007:
Thanks! That was easy. I searched all over EX pages and couldn't find that simple explanation.
[Nexus 6P Android Development] Brad331:
Wake Gestures in Nougat

It seems like all the wake gestures in the Nougat version are gone except DoubleTap2Wake. /sys/android_touch no longer exists. Would you please add back the various sweep2wake gestures? Thank you!

Source: https://github.com/flar2/angler/blo...e2d/drivers/input/touchscreen/wake_gestures.c
[Nexus 6P Android Development] nathanchance:
They are definitely there: https://github.com/nathanchance/Nin...ase/drivers/input/touchscreen/wake_gestures.c

I use them every day. Sounds like you aren't actually on Ninja.
[Nexus 6P Android Development] Brad331:
Wow, you're right! That's strange because according to my Powershell command history, I did sideload Ninja. Anyway, I flashed it again and now everything is good. Thank you for the quickest reply and sorry to bother you with a silly question!
[Nexus 6P Android Development] nathanchance:
I will give you credit for linking me the necessary commits at least ;)

Enjoy! :)
[Nexus 6P Android Development] Juzman:
Just compiled latest PN 7 and now you have v3.7 kernel, downloading now. ^_^
[Nexus 6P Android Development] stevesin:
Little off topic, but was thinking of plunging into nougat. Are all rooms currently substratum only?
[Nexus 6P Android Development] biglo:
[MENTION=6842057]nathanchance[/MENTION] just want to confirm with you, the yank hotplugging that your speaking of that is used in your kernel is the same as what google is currently using the their nougat rom for the 6p?
[Nexus 6P Android Development] Badger50:
Yep.
[Nexus 6P Android Development] nathanchance:
Google doesn't hotplug in their kernels for this device. I don't actually think they hotplug on any of their devices. This was a feature I added from [MENTION=2033478]Yank555[/MENTION].
[Nexus 6P Android Development] biglo:
Really? Wow I didnt even know that, gonna give this kernel a go and see how it feels. I think tmy 6p gets a little too warm for small task like whatsapping.
[Nexus 6P Android Development] RASanchez007:
I just flashed ninja kernel along with the the newest v3.7 and was wondering if anybody enables the hotplugging option.
[Nexus 6P Android Development] RASanchez007:
What cpu boost options are used while on glass fish 1.2 too?
[Nexus 6P Android Development] nathanchance:
I don't use hotplugging. You need to apply the frequency and milliseconds options on boot.
[Nexus 6P Android Development] bobbarker2:
Hey Nathan, I'm curious as to why you prefer such a small read ahead size for your I/o scheduler. Tons of testing has been done showing their being a sweet spot and large performance impact for read ahead size, somewhere in the 1024-2048 range depending on the scheduler and disk activity taking place. But you always go for 256kb and under. Any particular reason? Something specific to maple?
[Nexus 6P Android Development] nathanchance:
Nah I just don't think I need a high readahead, I've never felt like my I/O performance was lacking. I have been floating between 128-1024, I change it up every so often. Plus people are already free to change the values, I wanted to keep the default values closer to stock.
[Nexus 6P Android Development] Prattham:
So what would be the ideal io and read ahead to use?