yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] TheShamsMan:
Hey guys, I was wondering if anyone can refer me to a resource where I can find RGB screen settings and values for Kernel Auditor?

I freelance as a photographer and would like to calibrate my Nexus screen to reflect accurate colors. Is that possible? Is there a way to fine tune your screen? Thanks!
[Nexus 6P Original Android Development] xSilas43:
Worked before on the 11/18 build but not on the new one, I imagine they will be updated soon.

To get truly accurate colours you need hardware to do it however I have fine tuned the profile to what I have found to be accurate colours, by no means perfect but much more accurate than default. Attached below.
[Nexus 6P Original Android Development] micmars:
So I take it that's a no.

I flashed both versions, and had no dark reboot menu on either build, using all permutations of the dark/light/automatic toggle, both alone and I concert with at least 5 different dark layers for settings, framework and system UI.

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Original Android Development] DespairFactor:
That toggle is only for stuff we have natively themed into the toggle on the ROM, it doesn't touch layers unless the layers themers have tied into it.
[Nexus 6P Original Android Development] micmars:
Gotcha...I thought that it may be a theme issue.

Thanks for the input.

Do you know of any layers that apply a dark theme to the reboot menu and Android is starting screens?

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Original Android Development] jiv101:
Magpie
[Nexus 6P Original Android Development] micmars:
Perfect. I own the theme, so I'll give it a shot.

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Original Android Development] jiv101:
You're definitely going to have to tinker with it cause the options are endless
[Nexus 6P Original Android Development] micmars:
Yer, I know...I was just telling the dev for that theme in hangouts the other day that he's kind of nuts for doing that...it didn't help.

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Original Android Development] DespairFactor:
New build is here for now.

https://androidfilehost.com/?w=files&flid=16795
[Nexus 6P Original Android Development] p70shooter:
It says access denied mate.
[Nexus 6P Original Android Development] freddienuxx:
[MENTION=649160]despair[/MENTION] is this same rom as [MENTION=5105835]Cl3Kener[/MENTION] ? I got his rom running on my Nexus 5.

just curious thx in advance

Sent from my Nexus 6P
[Nexus 6P Original Android Development] DespairFactor:
Fixed

Yep
[Nexus 6P Original Android Development] p70shooter:
Still says the same for me.
[Nexus 6P Original Android Development] jaythenut:
All fine here downloaded
[Nexus 6P Original Android Development] p70shooter:
Sorted now, I was clicking the quoted post rather than the actual post
[Nexus 6P Original Android Development] jaythenut:
Can't talk now just going to flash:D
[Nexus 6P Original Android Development] coolsid8:
Any chance for a release for 8.1 ?
[Nexus 6P Original Android Development] demanzke:
Your answer is literally the message you replied to, the kernel is going to be rebased for 8.1.
[Nexus 6P Original Android Development] coolsid8:
Was checking if the device is still supported as the reply was 3 weeks ago.
[Nexus 6P Original Android Development] Mrcactuseater:
Maybe it is maybe it isn't, you'll find out if a new kernel is released.
[Nexus 6P Original Android Development] TRgamer:
Wow what a philosophical answer... You must be proud...

#coolsid8 was only asking as 3 weeks past.. No need of harsh reply...

Hope 2018 will be a more friendly year especially in the forums.. Cheers
[Nexus 6P Original Android Development] DespairFactor:
Kylo has been revived, new build is up!

https://drive.google.com/open?id=1NbKC6BGzlBSvi0jpSjFUhPlwpAyJ2-5X
[Nexus 6P Original Android Development] demanzke:
I've noticed they're selling the sweets lately but I did not realize that it's already Christmas!

Edit: I noticed the branch is called pie, is this for pie only?
[Nexus 6P Original Android Development] DespairFactor:
Will work on Oreo and pie
[Nexus 6P Original Android Development] sage of six paths:
I might try this with the crdriod pie rom, but i'm a bit hesitant going to pie cause of battery life.
[Nexus 6P Original Android Development] Lawlrus:
You should be more worried about random reboots on pie with a custom kernel than battery life, if you do any reading at all in pie threads you would see its still currently unstable custom kernel wise.

If you want the best battery life for this device stay on 8.1. Future versions of android on this device will NEVER be as good, or have better battery life than the OS versions that were actually optimized for the device by google

That's how outdated devices go.
[Nexus 6P Original Android Development] sage of six paths:
Yeah I guess you're right. I'm still not sure how people have 7 or 8 hours of sot, i cant get even close to that no mater the rom or the settings. I guess they won the lottery on the battery side. And this last rom I tried had the best battery life on the first day, then went a bit down hill. And there I thought I hit the jackpot lol.

Also to the point, stock 8.1 should give some decent battery life since it should be optimized, but it's draining battery almost as much as pie dies on my device, so their optimization isn't god know what ( at least on my device ).
[Nexus 6P Original Android Development] Lawlrus:
Because you're probably not looking at the right place.

What exactly on 8.1 is draining your battery? You can't just say its the ROM or settings, that's not how **** works. And chalking it up to its not optimized right " for my device" is a cop out and a lazy way of passing the buck. Android source is android source, aside from hardware issues, EVERY device would be having the same issue if source optimizations were the cause.

There's no magic kernel, or ROM, or settings that work for everyone that give godly battery consumption. Battery consumption is situational to everyone's habits for the most part, sure kernels can offer some help with letting it sleep more, or utilizing the cores and frequency's more intelligently/optimizing its functionality, but you're not going to go from 3 hours sot to 6 just because you install a kernel or flash some magical zip file that runs optimizations.

I have no problems getting over 5 hours sot before getting lower than 50% battery, and 9.0 battery life is not that much more terrible for me than what 8.1 is system wise. I will say that a lot of apps I use on 9.0 are fked compared to 8.1 with not letting my device sleep etc.

But, I don't game, because computers were made for that, I don't use garbage battery destroying apps like Facebook or WhatsApp among others.

I've stated this to people on this forums for years until I'm blue in the face that people need to use applications to see what exactly is draining their battery, and try to make adjustments based off of that. More times than not, people need to make changes to themselves, not changes to their device.

Edit: and I will agree that this device does not use the best internals, which shouldn't be surprising because this is what happens when you let a Chinese mfg source hardware.

But my device was bought new something like three years ago, and I've never had any issues with my battery, I'm not saying they didn't use **** battery's at some point, but id love to see some solid statistics on how people that did have to replace them treat their phone versus people that treat them better and had to replace them.
[Nexus 6P Original Android Development] sage of six paths:
I don't know how to determine what is draining my battery even on stock android. I am, at least i think, a lightweight user. Facebook, messenger, instagram, book reader, a little bit of youtube and that's it.

80% of my battery use is mostly messenger for chatting with my gf, and the rest is above mentioned. No games or anything else, some aliexpress browsing when i need stuff and thats it.

Elemtal x kernel with some of the popular profiles, six core mod, and all possible settings that can be turned off to preserve battery, i turn em off. Adaptive brightness, nfc, printing, assistant, location etc.

It's either my device, or the battery i recently changed does not hold the charge that well. I don't know give ma tip what to do, what apps to use to check for the drain. I'm out of the options.

It appears tho that i've found the combo to have the battery last the way i would expect form this device. Stock 8.1, xposed with amplify, doze for gps, excalibur cpu profile with interactive guvernor, not using six core mod, and ofc turning all of the things above. Had 99% at 12pm, 12 hours later at 31% and pretty much using the phone almost all day. The differernce is tho that i've moved to facebook and messenger light apps.
[Nexus 6P Original Android Development] Lawlrus:
[MENTION=6088965]sage of six paths[/MENTION]

Try gsam or maybe even accubatery off the play store, give it permissions to monitor apps if you have to.

Gsam always worked out pretty well for me, I just started looking at accubattery so I'm not sure how well it does.

Biggest thing is checking to see what apps if any are keeping your device from entering deep sleep, and creating wake locks

Edit: forgot the name of it because I haven't had to monitor this **** for a long time, but better battery stats was always my go to. Think you can just search via google and get the apk off of XDA.
[Nexus 6P Original Android Development] sage of six paths:
There isn't any need for that. My biggest culprits i guess were gps and i've dozed that, and the facebook and messenger and i'm using light versions of those. So if the battery usage stays like this i did it. I have the accubattery pro but i dont use it anymore. It didnt really tell me anything new. Facebook and Instagram were draining the battery the most. I've used it mainly for checking the health of the battery. I still recommend using amplify and doze for gps, i think u will get the best results from that. As soon as there is any official xposed for pie, i'm moving since i really like pie a lot more than oreo. We can move to dm if necessary so we dont spam the topic.
[Nexus 6P Original Android Development] Sheetzie03:
Definitely Can't hurt in my opinion, that's for sure.

I hear you with Facebook. Rather than using the lite version, I stopped using it all together a few years back. Lol It's an awfully optimized application, not to mention so much of its substance is useless garbage lol But yeah if you use it to speak with family and friends, I understand you have to use it.

And then w/ Accubattery, a little while back everyone was talking about this And they basically put their trust in it. But more and more I'd see that what Accubattery was reporting, mainly regarding the health of some ones battery, simply wasn't Accurate. Many times it would say a battery is fine when it absolutely wasn't and needed replaced. And Vice versa. So I stopped trusting/using the app. Maybe others have also caught on because I haven't heard nearly as much as I did about it like a year ago.

Later Mate
[Nexus 6P Original Android Development] mojorisin7178:
My wife's Galaxy s5 got los 15 and battery life was excellent. Better than stock marshmallow. And my note 2 was the same thing much better battery life. But other devices I have had did lose battery life due to custom updates. So I guess it depends.
[Nexus 6P Original Android Development] Lawlrus:
You're talking about going from some company's bloated ass version of android to a custom pure aosp? I mean that makes perfect sense, and shows why in stopped supporting such devices after my lg g2.

But if you're talking about pure aosp, to pure asop, then more tikes than not, you will start getting reduced performance in an outdated device.

I've been in the custom android scene since the OG droid RAZR battle tank that was a six lb piece of steel lol. Sometimes there's non difference, sometimes its better, but the vast majority of the time its bad. People want their devices tonplay full feature vidya games now, that wasn't the case three years ago.
[Nexus 6P Original Android Development] Nitrooo84:
I flashed kylo.R1.zip over the latest Pie StatiXOS (statix_angler-20190428-1354-9-v2.0-OFFICIAL.zip), but the phone didn't boot.
[Nexus 6P Original Android Development] AmyClaraRose:
Statix is FBE kylo is FDE
[Nexus 6P Original Android Development] p70shooter:
Hope you bootloop ?
[Nexus 6P Original Android Development] jaythenut:
Flashed and ruining very very smooth:silly:
[Nexus 6P Original Android Development] Jsilver73:
New build running lovely - had to switch back to kill in rom off as it seems to kill LMT as well as app that I want to kill. Added long press kill through gb as a work around and it's working fine :)
[Nexus 6P Original Android Development] TheShamsMan:
Hey! I'm an LMT user. Can you elaborate a bit on your experience? Is LMT crashing on you when you try to kill task using LMT? I don't quite follow. Thanks!
[Nexus 6P Original Android Development] Jsilver73:
No crash, just kills the service and you have to go back in and restart - like I say, if you run xposed (which I know it's against the grain for purists but it has been 100% stable for me) and set back long press to kill app this works fine when killing foreground app ;)
[Nexus 6P Original Android Development] terenchan:
SRGB is getting an error when click over it in settings for 29/11 build
[Nexus 6P Original Android Development] Jsilver73:
Yes, I see, thank you for reporting. Changing theme settings also throws error message but interestingly does change the setting.
[Nexus 6P Original Android Development] xSilas43:
Curious but why do you event want sRGB mode?

Also an unrelated note but the renderserver.net links are redirecting wrong now.
[Nexus 6P Original Android Development] micmars:
Uhm, because it's a very good, less saturated look...no need for a custom kernel.

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Original Android Development] DespairFactor:
It's fixed now

But you have a custom kernel with the ROM :P and sRGB is actually terrible looking.
[Nexus 6P Original Android Development] micmars:
Well there is that, but I was answering the question out of context...

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Original Android Development] hibby50:
The md5s for the 5.2 and 11/29 builds do not match those on the renderserver site. can anyone confirm or provide the correct md5s?
[Nexus 6P Original Android Development] DespairFactor:
5.2 is good for sure, and the uber download hsould be too. I have flashed the 5.2 from render myself.
[Nexus 6P Original Android Development] freddienuxx:
[MENTION=5169465]DespairFactor[/MENTION] long press for Google now doesn't work. is there some where to enable it? thx in advance
[Nexus 6P Original Android Development] DespairFactor:
you need to enable in the google app
[Nexus 6P Original Android Development] DespairFactor:
Let's get my download counts so high that RenderServer's counter breaks;)
[Nexus 6P Original Android Development] kingmikel:
I've also downloaded it, and it's running great!
[Nexus 6P Original Android Development] jiv101:
Hey [MENTION=5169465]DespairFactor[/MENTION] what governor do you recommend for battery
[Nexus 6P Original Android Development] jaythenut:
One little thing I've found the percentage don't stick in the battery for me
[Nexus 6P Original Android Development] DespairFactor:
What?

I use impulse
[Nexus 6P Original Android Development] Jsilver73:
Last time I asked despair said impact /FIOPS with 'cake' as packet sched (read post 2 ;))

I've been running that for the past few days and performance is silky smooth - not sure about battery because I think with the angler the question seems to be "what do I need to do to kill the battery" rather than preserve it lol :laugh:
[Nexus 6P Original Android Development] jaythenut:
This is with percentage on in battery as you can see not there;)
[Nexus 6P Original Android Development] Jsilver73:
:silly:

Yes and you smell lovely every morning ahahahahaha

I think I meant impact lol

Edit - forget it, it is obviously to really in the morning for me to be on XDA lol

Impulse works very good too.:silly:
[Nexus 6P Original Android Development] TheShamsMan:
Hey guys, I'm using SwiftKey with 520dpi and the keyboard and buttons are off. Anyone else?
[Nexus 6P Original Android Development] DespairFactor:
App issue
[Nexus 6P Original Android Development] p70shooter:
Have you enabled the cut out option?
[Nexus 6P Original Android Development] xda4ck:
Hi all... I have flashed kylo kernel 5.2 on my Nexus 6p but I forgot to take a screenshot of the CPU frequency table from stock kernel. Can please someone post a screenshot of the stock frequencies for 6p ?

You're help will be really appreciated.
[Nexus 6P Original Android Development] Badger50:
Does that help? :)
[Nexus 6P Original Android Development] xda4ck:
Hi badger

Thanks for response.... Can you go to kernel adiutor's Frequency table option and take screenshot of both big and LITTLE CPU chips...? It will really help me to arrive at proper under clicking/overflight frequencies relative to stock frequencies....

Thanks again...
[Nexus 6P Original Android Development] Badger50:
Cluster 1, and 2 :)
[Nexus 6P Original Android Development] Badger50:
Respectively of course.
[Nexus 6P Original Android Development] xda4ck:
Great... This will really help..... Thanks a lot...[emoji4]
[Nexus 6P Original Android Development] ChronoReverse:
I spy 5.3!
[Nexus 6P Original Android Development] TheShamsMan:
Gotcha! What keyboard do you use? Or do you just stick with default DPI? Thanks!
[Nexus 6P Original Android Development] DespairFactor:
I am now on Despair on little, barry allen on big

You do, and it is lovely

I use Google Keyboard and a 440 DPI
[Nexus 6P Original Android Development] xSilas43:
Try super Swift key, I'm using that on 384 dpi with no issues.
[Nexus 6P Original Android Development] DespairFactor:
Thanks for the solution for the nubs;) Just kidding, I am a nub too
[Nexus 6P Original Android Development] dabug123:
Hmmmm Barry Allen on big wonder who else uses that
[Nexus 6P Original Android Development] DespairFactor:
You use boost though;) I don't
[Nexus 6P Original Android Development] Zetsubou Sensei:
Hey guys, anyone else having problem using kernel adiutor with the 5.3 kernel? It's not loading any of the settings for me. I've wiped cache and reflashed it twice.

---------- Post added at 09:40 PM ---------- Previous post was at 09:33 PM ----------

Nvm guys, I redownloaded off the EU server and it works now. Something might have been wrong with my initial download. Sorry for the trouble.
[Nexus 6P Original Android Development] DespairFactor:
Now we need to spread it like a virus, the force awakens, beware of rebel scum, join the dark side
[Nexus 6P Original Android Development] DespairFactor:
I have uploaded a new build, I can't guarantee stability yet, it is built using UBERTC 5.2.x
[Nexus 6P Original Android Development] Jsilver73:
Seems pretty stable so far and certainly snappy :good:
[Nexus 6P Original Android Development] jaythenut:
Yeah all good here as well just half the governors have gone I guess you know that lol
[Nexus 6P Original Android Development] DespairFactor:
They were dropped on 5.3, they weren't tunable and I didn't find a lot of them were offering anything different for this device.
[Nexus 6P Original Android Development] jiv101:
That's pretty
[Nexus 6P Original Android Development] belloni:
Is there any other way of changing vibration strength without buying elemental app?! It needs increasing alot!
[Nexus 6P Original Android Development] xSilas43:
,xposed?
[Nexus 6P Original Android Development] belloni:
What module?!
[Nexus 6P Original Android Development] xSilas43:
Vibration tuner (free) or buy ultimate notification control from gravity box.
[Nexus 6P Original Android Development] ChronoReverse:
Ooh 5.5 is out, time to flash, I'm such a kernel junkie ;)

Incidentally, I've been annoyed by the way the thermal throttling worked on the N6P for a while. For regular use like web browsing it's amazing but the overly aggressive throttling is extremely apparently during gaming.

I suppose it's an overreaction to the heat of the SD810 and the bad press other phones were getting but looking at the thermal.conf file indicates that this phone is under extreme throttling by the time it reaches 42 degrees Celsius. Since at room temperature, the screen-on idle CPU temperature would be around 36 degrees Celsius (and can jump to 42 in 2 seconds on load), you can see how forcing the Big cores to 960MHz at 42 degrees and completely turned off at 44 degrees is ridiculous.

Compare to the SD800 series where the general throttling temperature would be in the 70s.

So after looking at /system/etc/thermal-engine.config and editing it judiciously, I now have a phone that doesn't turn into a snail at the slightest hint of load. It still cuts down cores and reduces frequencies but averages at the 60s when under load instead. Something for everyone to look at if they're interested.
[Nexus 6P Original Android Development] abraxo:
not quite versed in kernel options but I have heard only great things about Kylo. Can anyone specify the differences between Kylo and stock for those who are 'uneducated'?
[Nexus 6P Original Android Development] ChronoReverse:
I'll attach it. Take a look.
[Nexus 6P Original Android Development] dabug123:
Ya I just posted about this few days ago in lean thread I didn't edit mine quite that Much but I'll try your and see as well
[Nexus 6P Original Android Development] exo8:
Hey Despair, How do I donate and buy you some beers.
[Nexus 6P Original Android Development] ChronoReverse:
Yeah, I've been tracking the CPU utilization closely for a while under a few of my common conditions (web browsing, heavy and light gaming, idling, benchmarking) while using a lightly edited thermal-config and used that to heavily edit it to my tastes. I'm still testing it for smoothness, performance and battery life (the latter particularly takes a while) but I thought I'd mention it.

The primary goal was to _not_ have to apply CPU or thermal control adjustments at all from an app (e.g., Kernel Aduitor).

The maximum frequency is allowed but only at idle temperatures (<42) which makes it a "turbo" sort of feature. The maximum frequency is quickly limited to a lower but still fast (Big 1.7GHz Little 1.25GHz) speed for the majority of the time while active cores are reduced. I've found that 1 little + 2 big is still extremely fast so that's the normal configuration.

As temperatures soar in the 70s, more aggressive frequency throttling is finally applied until things are forced to shut down at 82.
[Nexus 6P Original Android Development] ChronoReverse:
Under normal conditions (assuming stock Kylo, e.g., interactive governor) the snappiness shouldn't be any different but sustained performance should be smoother. In one particular game I was playing, I could actually see wild swings of framerates as the phone throttled the CPU to almost nothing and then unleashing back to full tilt when the phone cools a bit. Drove me nuts.
[Nexus 6P Original Android Development] ChronoReverse:
Okay, more testing revealed that you need at least two Little cores online for Google Camera to behave well 100% of the time. Occasionally it can act weird if only a single core is available (doesn't seem to shift loads to the Big core) so if you're also testing the thermal-engine file, make this change:

action_info 0+0+1+1+0+0+1+1 0+0+1+1+0+1+1+1 0+1+1+1+1+1+1+1

Original post updated.
[Nexus 6P Original Android Development] DespairFactor:
I have a donate link under my avatar, or on renderserver there is a paypal link on my profile.

Good share

Everything is different here, different toolchain, more patches to optimize task scheduling. Network patches to increase throughout on the NIC. Almost everything you can imagine.