yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] Kusanagi Fire:
There's a new beta version of Layers Manager that works as intended. Not sure if it's been pushed to the store as a final build yet.
[Nexus 6P Original Android Development] Tanged:
Ah okay, so just install the new beta and layers work as usual? No need to flash/install anything extra?
[Nexus 6P Original Android Development] tcat007:
Yes. You do need to join beta to get it pushed from playstore.
[Nexus 6P Original Android Development] elreydenj:
239 243 255

278 254 264 10

I used to like banged up profile under franco. Those are the numbers , but i dont know exactly how they equate to ex manager's inputs.... Can anyone give me a hand?
[Nexus 6P Original Android Development] Born<ICs:
For your Kernel what options are selectable in the Aroma installer?

What are some recommended setting adjusted values that yeild improvement?

thanks, cheers
[Nexus 6P Original Android Development] flar2:
I'll try to figure out how to tame the min cpu freq in EXKM tonight. It is problematic, as I've just been playing with it.

For now, avoid going to the CPU settings screen.
[Nexus 6P Original Android Development] flar2:
Depends what kind of improvement you want.

For now, just go with the defaults.
[Nexus 6P Original Android Development] Franzie3:
flar2, running very well so far, no issues dt2s working well. Is a prevention for pocket wakes going in like it was in the N6? No rush just curious. I haven't had it happen yet but i know it's bound to
[Nexus 6P Original Android Development] zamula:
So I've encountered a weird problem with EX, and also another custom kernel. About a minute after booting my screen appears "washed out" like the contrast etc. is set wrong (it's okay right after boot). I attempted to modify some color settings within the EX app but can't correct it. I also tested without any layers applied or screen modifying apps installed, but no change. When I go back to the stock kernel there are no issues.

Has anyone encountered something similar or have any suggestions? Of course if all else fails I'll do a complete wipe and hopefully determine the culprit. Thanks!
[Nexus 6P Original Android Development] flar2:
Very strange, let's see if anyone else reports.
[Nexus 6P Original Android Development] adrman:
I had that happen when I tried to use the KCAL interface for CF.Lumen 3.16. I ended up having to completely uninstall CF.Lumen and reninstall it using the CF.Lumen driver.
[Nexus 6P Original Android Development] Jsilver73:
Yes I've got the same issue, it's like there is a translucent layer across the screen, I've tried messing around with the values in rgb and got it looking a bit Bayer but not right at all. When I restore original values of looks very washed out.
[Nexus 6P Original Android Development] Stud22:
I had the same thing happen to be after a reboot last night. I went into the color control app and shut off set at boot then restarted then it was back to normal. I thought I screwed my phone up somehow.
[Nexus 6P Original Android Development] FuMMoD:
I had the same happen to me this morning. It went away after a few reboots.
[Nexus 6P Original Android Development] Jsilver73:
Thank you, yes I had cf lumen installed and completely forgot about it, just uninstalled it and it looks on now.

I'm new to all this tweaking of the screen, I like bright colours and white whites - if anyone could share their songs that would be ace.

I tried a couple that are posted in this thread but they don't seem to completely relate to all the settings on the elemental x app.
[Nexus 6P Original Android Development] michaelearth:
After flashing ElementalX 1.01 over version 1.0, I can no longer get the camera to work. I've tried wiping cache and had no luck. Any idea whats wrong here?

Thank You
[Nexus 6P Original Android Development] flar2:
https://play.google.com/store/apps/details?id=flar2.hbmwidget

A few things: you need to be using Android 6.0.1, you may have incorrect boot.img (solved by flashing stock boot.img if you're on stock, reflashing the ROM if you're on a custom ROM, and then reinstalling EX), or you may not have the latest vendor and bootloader updates.

Without more info, all I can tell you is that everything on this kernel works.
[Nexus 6P Original Android Development] Fauert:
Works every time i swipe ... ;)
[Nexus 6P Original Android Development] michaelearth:
The rom I'm using is PureNexus and its Android 6.0.1. I did go ahead and dirty flash the latest PureNexus rom and installed ElementalX 1.0.1 and that didn't fix the issue either.

I'm not sure if I have the latest vendor and bootloader updates. How I would check that?
[Nexus 6P Original Android Development] drawde40599:
If you didn't manually flash them then you probably don't have them I believe they were both updated from 6.0 .

Just extract them from the latest Factory img and FastBoot them .

https://developers.google.com/android/nexus/images
[Nexus 6P Original Android Development] just4747:
Ok then maybe it is my ROM. I updated from rooted stock 6.0 by flashing all the pieces manually through fastboot (not wiping data though) and then re-rooting and flashing the kernel. Maybe I need to start fresh, because both my swipe and double tap barely work ever since.
[Nexus 6P Original Android Development] mpgrimes:
[MENTION=4684315]flar2[/MENTION] one thing I noticed, high brightness resets to off every time screen goes off...
[Nexus 6P Original Android Development] GCbard:
this high brightness mode is great! Good job! I really like this feature. In the future would it be possible to have this feature activated when normal max brightness is reached when adaptive brightness is activated? Like on the samsung galaxy s6?
[Nexus 6P Original Android Development] flar2:
Yes, this is how it is normally implemented, as you are not supposed to use it all the time. It could be changed, I will think about it.

That is not handled by the kernel. On the Nexus 6, people were using Tasker for stuff like that.
[Nexus 6P Original Android Development] ratson:
Hbm is working fine on my device, core7 seems to stay offline though.
[Nexus 6P Original Android Development] jamespat93:
Thanks I bought the app. Hbm is working great here too, no issues so far with anything.
[Nexus 6P Original Android Development] grayskul:
Would Wi-Fi have anything to do with the kernel? Cause that was the only thing eating up my battery. Not anything crazy but if I had Wi-Fi turned on even when not @ the house it was my only wakelock. I just hate having to turn the toggle of and on. If it's a ROM issue maybe I'll just clean flash the whole thing. I had to turn the toggle off in location settings as well to have it settle down.
[Nexus 6P Original Android Development] NovaSlim:
Location-> Scanning-> I hope you don't have either of the Scanning option on as they are huge wakelock generators.

Never had any Wifi wakelock issue on this kernel.
[Nexus 6P Original Android Development] GCbard:
Some benchmark scores. Great kernel.
[Nexus 6P Original Android Development] flar2:
Update!!!

This update adds an optional high brightness mode. This is a special mode that makes the screen much, much brighter than is possible with stock. This is meant to be used temporarily when outdoors in bright sunshine. You can quickly toggle HBM with the HBM Widget (https://play.google.com/store/apps/details?id=flar2.hbmwidget). It can also be controlled with EX Kernel Manager.

Obviously, you use HBM at your own risk. Most AMOLED screens have it so it should be fine. If you don't want to use HBM, there is no effect on anything else.

Also, I will update the hbm widget soon (when I have time)

Download

ElementalX-N6P-1.02

Changes:

-High brightness mode

-a few optimizations
[Nexus 6P Original Android Development] ggeralds:
Question all, I know we can adjust gain for speaker, mic and headphones with this kernel, however the headphone gain seems to do nothing with bluetooth head phones (at least jaybirds or photonics). Are bluetooth gains different than standard headphone gains? If so is that something that may make it into this kernel in the future? Thanks in advance.
[Nexus 6P Original Android Development] ncsuwolfs:
is it not a good idea to leave high brightness mode on other then battery drain? higher chance of burn in?

edit: nvm it wont stay on after a screen lock
[Nexus 6P Original Android Development] AceDuff93:
I was following the thread silently since I have yet to unlock my 6P, but I think I can be of some use on this. sRGB mode won't stick after reboot if Secure Startup is enabled. You need to disable it, or you'll have to keep enabling sRGB at each reboot. Moreover, it might still keep resetting itself, but the trick is not to go in the Developer Options. If you enable sRGB mode, than reboot and don't enter Developer Options, it will stick, you can notice if you use Google Calendar widget. Once you tap to go into Developer Options, it lags because it disables sRGB mode. I don't know why there are these weird behaviours, anyway that's how it is.
[Nexus 6P Original Android Development] grayskul:
I did state that. But I did turn that off. Here's a screenshot. But if I turn off WiFi then it goes away.
[Nexus 6P Original Android Development] steveo17:
That's not a wakelock

That's just saying that you have Wi-Fi on
[Nexus 6P Original Android Development] joshuadjohnson22:
Awesome! Any chance this fixes the sRGB mode when customizing the color? Would love to add some blue to the whites and a tad bit more saturation without going full cartoon ;). Thanks for all you do!
[Nexus 6P Original Android Development] NovaSlim:
What is shown there is not a wakelock(it just shows you had wifi on all the time, which you should btw), you are looking at the wrong category. Wakelocks you can control are listed under the "Partial Wakelock" tab.
[Nexus 6P Original Android Development] revolt1:
How does the high brightness mode work once you enable it
[Nexus 6P Original Android Development] nathanchance:
It makes your screen super bright. It turns off once you lock the screen when you do it from within the kernel. If you use the High Brightness Mode widget, it will persist until you turn it off.
[Nexus 6P Original Android Development] revolt1:
Was hoping maybe it was a the trick to make it go by faster when it hits light
[Nexus 6P Original Android Development] nathanchance:
No, if you get the widget, you could set up a Tasker profile to read the amount of light in the room and have it kick it on when it reaches a certain threshold, but it isn't automatic in its current implementation.
[Nexus 6P Original Android Development] resynx:
Appreciate the update flar!
[Nexus 6P Original Android Development] ncsuwolfs:
awesome update, bought the high brightness widget and am gonna leave it on unless i see any noticable side effects. the brigthness is perfect
[Nexus 6P Original Android Development] nathanchance:
I'd be very cautious with leaving it on all the time, you will probably experience some pretty bad burn in eventually if you don't regulate it.
[Nexus 6P Original Android Development] bsg411:
The hbm is the same brightness as when the display brightness is turned all the way up while adaptive brightness is off.

Edit: correction....hbm is noticeably brighter than with adaptive brightness off.
[Nexus 6P Original Android Development] flar2:
I just pushed a small update to the HBM Widget to fix maintaining high brightness mode after screen goes off.

Again, I don't recommend leaving it on all the time. It's way too bright unless you're outside.
[Nexus 6P Original Android Development] SSVanderbilt:
Hey flar, if I ever wanted to go back to the stock rom how would I go about doing so? I haven't round the stock kernel anywhere on XDA yet :( I just want to make sure I can revert if I run into the camera force closing problem!
[Nexus 6P Original Android Development] flar2:
You can always get it from the factory image available from Google.

There shouldn't be any camera force closing problem though. That is from incorrect installation.
[Nexus 6P Original Android Development] SSVanderbilt:
Which file would I be flashing via adb, from the factory image; boot.img?
[Nexus 6P Original Android Development] nathanchance:
It would be via fastboot and yes, the boot.img is the stock kernel.
[Nexus 6P Original Android Development] SSVanderbilt:
Thank you! and ahh yeah fastboot*. It won't cause problems with anything else right? It's just the kernel?
[Nexus 6P Original Android Development] nathanchance:
Just make sure you are flashing the boot.img of the build you are on. 6.0.1 kernels are not compatible with 6.0 and vice versa.
[Nexus 6P Original Android Development] SSVanderbilt:
Perfect, thanks man!
[Nexus 6P Original Android Development] grayskul:
My bad but still its not dozing like it used to unless I turn it off. Of well maybe clearing cache and dalvik might fix it.
[Nexus 6P Original Android Development] lobrau:
So now that HBM is working for the 6p, is there anyone versed enough with tasker to create a profile/task to enable HBM when a certain % of light hits sensor, and of course to disable once it drops below? Guess it would have to use the intents that flar wrote for the widget and some sort of threshold. I'm not nearly good enough with tasker to figure this out.
[Nexus 6P Original Android Development] shawnaye:
Hey [MENTION=4684315]flar2[/MENTION], I just wanted to ask. Under your app, in the voltage table there's two 384mhz voltages.

I assume the top one is for cluster 1 and the bottom is cluster 2.

I've noticed for all the voltages. Cluster 2 seems to run at a lower voltage at the relevant frequencies compared to cluster 1.

Doesn't this mean that using cluster 2 would be better than cluster 1 in all possibilities?
[Nexus 6P Original Android Development] italia0101:
On the Nexus 6 the command was " echo 1 > /sys/devices/virtual/graphics/fb0/hbm"

Is that still the case flar2?
[Nexus 6P Original Android Development] zer0se7en:
Hello, [MENTION=4684315]flar2[/MENTION]. Will this have a USB Fast Charge on future updates? That was one of the main feature I love having this kernel on my old Nexus 5. I would've liked to experience the same thing on our Nexus 6p. Cheers!
[Nexus 6P Original Android Development] gandharva:
Thanks for the detailed explanation. But my intention in asking here was to get this fixed, so sRGB will stick without strange behaviour.
[Nexus 6P Original Android Development] Mikulec:
Whats the default CPU and GPU governor?
[Nexus 6P Original Android Development] gandharva:
Interactive/FIOPS(512)
[Nexus 6P Original Android Development] Raijin:
Yes, it's exactly the same.

---------- Post added at 12:26 PM ---------- Previous post was at 12:24 PM ----------

Thank you flar2! My friends started to think I'm crazy, turning on and off and then on the screen each time. Now it works perfectly.
[Nexus 6P Original Android Development] Badger50:
Good lord!....you can signal aircraft with his new brightness thingy. Well done my friend! :)
[Nexus 6P Original Android Development] tcat007:
Why? My 6p charges in 1hr 20 min, faster than my n5 ever did.
[Nexus 6P Original Android Development] b00st4ddicted:
Would anyone like to share their badass optimized configuration? :D
[Nexus 6P Original Android Development] dadsterflip:
Sorry if it has been asked. I only looked thru a few pages . on chroma ROM and systemless root. Flashed this kernel and lost my superuser. Did the unzip su. Kernel. Super user. I really wanna run this kernel lol. Any fix or am I just doing something wrong here?
[Nexus 6P Original Android Development] flar2:
I will look into this, but it might not be a kernel thing

I will look into this eventually. First I need to get up to speed on USB C.
[Nexus 6P Original Android Development] flar2:
It shouldn't be complicated. Normally if you already have root, you should just be able to flash ElementalX. There is no need to mess around with un-su and things like that.

Reflash Chroma without wiping, flash SuperSU 2.62 and then flash ElementalX
[Nexus 6P Original Android Development] dadsterflip:
Thank you for the fast reply. Just been digging your kernel!
[Nexus 6P Original Android Development] monkeyhandler:
With the HBM, does the screen color become super saturated like the Note 4/5 in their brightness boost mode?
[Nexus 6P Original Android Development] redsmith:
Nope, it just boosts brightness to an awesome level.
[Nexus 6P Original Android Development] monkeyhandler:
Thanks!
[Nexus 6P Original Android Development] rp1226:
Not sure, but might need to flash root after the kernel to patch the boot.img?

Liking the kernel so far. works well and the high brightness is a nice add.
[Nexus 6P Original Android Development] steveo17:
maybe for USB A connections?
[Nexus 6P Original Android Development] flar2:
No, my installer uses the existing ramdisk, so if you are rooted before installing, you will be rooted after installing
[Nexus 6P Original Android Development] rp1226:
Thanks for the heads up. So the note to flash root after every other kernel just in case ;)
[Nexus 6P Original Android Development] flar2:
With ElementalX, rooting is a one-time thing. Once you have root, just flash EX. Any updates to EX, just flash it. No need to flash root again.
[Nexus 6P Original Android Development] jesssiii:
I'd love a flashable zip for the stock kernel, can't find one anywhere. Just for peace of mind.
[Nexus 6P Original Android Development] steveo17:
you can download and flash the stock kernel and recovery via flashify
[Nexus 6P Original Android Development] AceDuff93:
I can't be sure because I have no technical knowledge on this, but it's probably a bug and I'm not sure it can be fixed via kernel modification either.
[Nexus 6P Original Android Development] zer0se7en:
Dude, I was talkin' about fast charging when attached to a computer not on the fast charger that came with it. ElementalX for Nexus 5 has that feature.
[Nexus 6P Original Android Development] drothenberger:
TWRP can flash the boot.img file from the stock files directly.
[Nexus 6P Original Android Development] Chilidog:
Hey idk what's going on but I still can't get LTE... I've tried clean flashing the kernel and changing setting but it doesn't stick. Everytime after I reboot I have to toggle airplane mode to get LTE

Edit: Nevermind it looks like it is a stock issue as well
[Nexus 6P Original Android Development] kauemelhado:
Have you tried flashing modem.img??

Idk, but I don't think the Kernel has anything to do with LTE reception.
[Nexus 6P Original Android Development] Chilidog:
Ya I've flashed the ;latest radio a few times
[Nexus 6P Original Android Development] kauemelhado:
With stock rom it works properly?
[Nexus 6P Original Android Development] Chilidog:
I did some more research and it looks like I am not the only one, sorry [MENTION=4684315]flar2[/MENTION] for clogging up the thread.
[Nexus 6P Original Android Development] nrage23:
Flash the previous radio. The newest one is the one having issues with LTE connectivity.
[Nexus 6P Original Android Development] tech_head:
Having the same issue, stock with ElementalX.

I had the same issue with a stock kernel.

I don't know if it's the radio or something in the 6.0.1 build itself.

I just figure I'll toggle airplane mode after boot. it's not the first time I've had to do this for a phone.
[Nexus 6P Original Android Development] flar2:
I would just keep the latest radio and go with it.

I also noticed a bit less LTE connectivity at first, but now it seems to be connected to LTE all the time.

You might try Settings->Backup & reset->Network settings reset
[Nexus 6P Original Android Development] oscillik:
really?! I did not know this. Is it the same process as flashing a zip?
[Nexus 6P Original Android Development] nathanchance:
Yes, you click Install then you click the Images button in the bottom right hand corner, navigate to your image, select it and then boot partition, flash it and you are good to go!
[Nexus 6P Original Android Development] rp1226:
I wonder if there is a way to enable Qualcomm Quick Charge (so you can use charger blocks with USB Type A plugs.) Always can be hopeful. :)
[Nexus 6P Original Android Development] mpgrimes:
Try flashing 2.15 radio.....
[Nexus 6P Original Android Development] ShermanTenor:
(sorry - I know this is kinda OT as the LTE issue has nothing to do with EX)

FWIW, I was having the same LTE issues yesterday after fastboot flashing to 6.0.1. I ended up flashing the 2.15 radio and it improved things a lot, then ended up changing it back last night to the 2.50 (6.0.1) version of the radio and its been fine since. I thought maybe it was signal related as I updated at the office, but I'm back in the office today, and every time i have checked, I get LTE without issue.

Could the flash order have anything to do with this? I originally followed this order:

1) fastboot flash bootloader bootloader-angler-angler-02.45.img

2) fastboot flash radio radio-angler-angler-02.50.img

3) fastboot reboot-bootloader

4) fastboot flash boot boot.img

5) fastboot flash cache cache.img

6) fastboot flash system system.img

7) fastboot flash vendor vendor.img

So the radio was flashed before most of the other flashes. Maybe flashing the radio last would be more helpful? I'm really unsure though how it could impact the other flash areas... otherwise why separate out the areas into different IMG files?!?

After step 7, I rebooted into recovery and flashed SU 2.52 and EX 1.01. After, my phone wouldn't get past the boot logo animation, so I ended up flashing TWRP again and then flashed SU 2.62 and EX again. I was able to boot with this config, so I then downgraded SU to 2.52 as I don't care about systemless root, and wanted max compatibility with root applications and that is where I am now. Seems to be working OK now.
[Nexus 6P Original Android Development] italia0101:
You managed to get this to work with tasker? My profile is wonky on the 6p, the light sensor seems weird
[Nexus 6P Original Android Development] Raijin:
Yes, the command to enable the HBM works.

Try to change the path of the light sensor. It's different. In Nexus 6P it is:

/sys/devices/virtual/graphics/fb0/mdp/qcom,mdss_fb_primary.182/leds/lcd-backlight/brightness
[Nexus 6P Original Android Development] italia0101:
Sorry I'm being dense lol, change it where?
[Nexus 6P Original Android Development] Raijin:
You're not being dense :)

Sorry for not being able to send you the profile. I'm using now the widget by flar2, because I keep it all day active until the night.

I'm a very basic user of Tasker, so I can only recommend you to set that correct path (it's a little different than in Nexus 6) in your profile.

I found a Tasker profile made by danarama in the forum to activate HBM when the brightness slider is set to the maximum, but it don't work, apparently due to a bug of Tasker with Marshmallow. If someone knows about Tasker and is interested in it, click here to see the post.

Maybe your problem is related to that bug.
[Nexus 6P Original Android Development] ShermanTenor:
[MENTION=4350436]Raijin[/MENTION] - Where do you define the path to the light sensor in tasker? I'm a newbie to Tasker, so please be gentle! :)
[Nexus 6P Original Android Development] Raijin:
Lol, I'm sorry [MENTION=1334806]italia0101[/MENTION] . I gave you a path that have absolutely nothing to do. It was the one of the brightness slider.

Please don't use it. You can create a profile with "State > Sensor > Light Level", or just type " Light Level" in the search bar below. Sorry for confusing you.
[Nexus 6P Original Android Development] italia0101:
No problem [emoji4], thanks for replying