yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] nathanchance:
Yeah, which settings are not applying? What ROM are you on?
[Nexus 6P Original Android Development] masri1987:
Pure nexus.

Impulse reverts to to interactive,

2nd cluster minimum speeds are changed to 600mhz (or something like that from 384)

All my color settings under graphics revert to stock

cpu input boost values revert to stock as well.

profile was bluejay

i'm seeing if it'll happen with redhawk
[Nexus 6P Original Android Development] nathanchance:
You have the profile apply on boot toggled right?
[Nexus 6P Original Android Development] masri1987:
yep
[Nexus 6P Original Android Development] nagato86:
[MENTION=4684315]flar2[/MENTION] reboot while I was using the phone ... you can check what it depends?! https://www.dropbox.com/s/16fnxbrihw6wu3l/last_kmsg.txt.zip?dl=0

Inviato dal mio Nexus 6P utilizzando Tapatalk
[Nexus 6P Original Android Development] mobileman88:
I have never seen any spontaneous reboots while using the phone. Do share what you are also using :

xposed? - Which version?

Supersu - which version?

xposed modules ? - what modules and version?

One thing I found effective in clearing my instability was to reboot to TWRP and clear Dalvik and Cache. Usually that fixes it for most times.
[Nexus 6P Original Android Development] nagato86:
Latest pure nexus rom

Supersu 2.76

No xposed/modules

Inviato dal mio Nexus 6P utilizzando Tapatalk
[Nexus 6P Original Android Development] justibasa:
Having the same issue on exkm after a reboot. Running ex 1.19 and poor Nexus on a clean flash. Actually thought I was going crazy, and it's affecting my Pokemon gameplay. ???? I am seeing the set on boot toast. I've completely wiped the app and reset up, with the same issue next time i reboot. Just thought I'd let you know it's not just you. The main issue is the 2nd set of cores says NA and I it won't let me set to interactive at all. So I get a really bad lag. And ghostpepper profile won't set on boot either.

Edit: after uninstalling and reinstalling the app, issue seems to be gone. :laugh:
[Nexus 6P Original Android Development] ajm786:
[MENTION=4684315]flar2[/MENTION],

For some reason, only within the past day, the EXKM app has randomly started to keep the phone awake. In BBM, it shows up under Partial Wakelocks. No, this is not Power Manager service or any of those, it's the EXKM app itself. I suspect it had to do with checking for updates, so I disabled that for now, and the wakelocks seem to have gone away completely.
[Nexus 6P Original Android Development] ccblox:
I'm pretty sure that the governor controls are only for the 'interactive' governor, which would explain why that setting is changing for you. Not sure about the rest.
[Nexus 6P Original Android Development] masri1987:
how did you get that ?

I was following instructions from the creator of Heimdall V4 profile whom advised changing those governor values after going into impulse.

Anyway i degreenified EXKM, will report back if problems persist (so far it's ok) thank you
[Nexus 6P Original Android Development] SlimSnoopOS:
Nah, that's not the case. One or more of the profiles are intended for other governors.
[Nexus 6P Original Android Development] ccblox:
Oh, interesting, I didn't know that.

I only noticed that after applying them in EXKM on the ElementalX kernel, my governor was being changed from elementalx to interactive. Didn't know there were profiles designed for other governors.

Could still be the problem, if he's selecting profiles designed for a different governor.
[Nexus 6P Original Android Development] mobileman88:
that should be good. do clear your cache and dalvik in TWRP then reboot your phone. let me know if you still have the problem.
[Nexus 6P Original Android Development] bsg411:
My battery, CPU, and phone overall have been running hot lately... Anyone have any suggestions? I'm running:

Pure Nexus

Elemental X 1.18
[Nexus 6P Original Android Development] SlimSnoopOS:
Most of the profiles are for Interactive and they set this as default in the script. You could always change that governor if you desire. I think Blue Jay profile is/was for Impulse governor. I haven't kept up with them so maybe more exist.
[Nexus 6P Original Android Development] Krunk83:
[MENTION=4684315]flar2[/MENTION] you're right, it's not the wake gestures. I was wondering if you could test one more thing for me though. Turn on "Show touches" in developer options. When the screen is off, with a custom kernel(any, obviously EX in this case) installed, tap the screen a few times and then turn on the screen via the power button. You will then see the false touches shown with a grey dot. I am on my third phone and this has happened on every phone with a custom kernel installed. I'm posting this here because EX is my favorite kernel and have not been able to use it or any custom kernel on this device because it this issue. Thanks
[Nexus 6P Original Android Development] JRJ442:
I just tried that and couldn't reproduce it. Are you using any Xposed modules that alter screen touches? I know older versions of flat style color bars used to leave ghost touches behind in certain apps.
[Nexus 6P Original Android Development] lahma69:
Update to xpad.c

flar2,

Would you possibly consider updating xpad.c ( https://github.com/flar2/angler/blob/ElementalX-1.00/drivers/input/joystick/xpad.c ) to its newest version which includes compatibility for Xbox One controllers? The updated xpad.c can be found here:

https://github.com/torvalds/linux/blob/master/drivers/input/joystick/xpad.c

I've been updating xpad.c in the stock kernel and compiling it myself, but I'm beginning to tire of going through the whole process of recompiling the kernel each time it is updated. I figured it might be more practical to ask a custom kernel developer such as yourself to implement the updated xpad.c (you could then tout Xbox One controller support as a feature of the kernel).

Besides updating xpad.c in the kernel, the only other action required to get Xbox One controllers working on the Nexus 6P is to copy the key layout files to "/system/usr/keylayout/". There are currently 3 Xbox One controller key layouts described in the most up-to-date xpad.c:

Xbox One USB Controller Key Layout File:

Vendor_045e_Product_02d1.kl

Xbox One (Firmware 2015) USB Controller Key Layout File:

Vendor_045e_Product_02dd.kl

Xbox One Elite USB Controller Key Layout File:

Vendor_045e_Product_02e3.kl

All 3 of these files are identical to the Xbox 360 key layout file that already exists as "/system/usr/keylayout/Vendor_045e_Product_028e.kl". So, this file can simply be copied 3 times and renamed to the 3 file names listed above, or you can download a zip file I compiled with the 3 key layout files (which also have commenting inside each one stating what controller it supports) and a readme.txt describing in detail what I quickly described above.

Android Key Layout Files for Xbox One controllers:

https://mega.nz/#!bYES2QrR!g2zBQPfn_UGeozl_IbYIWsilNtHFutxXY_fDE2u1gt4

And if for some reason you are interested in testing Xbox One controller functionality with a kernel that already has an updated xpad.c, here is a copy of the stock Nexus 6P kernel (3.10.73-ga12dd8b) with updated xpad.c (flash .img to boot in TWRP):

https://mega.nz/#!eA1GRZDL!pH8vx_63Vs5WRyHClacN2N_ry76HVyndK_S8HUJ8sHk

I apologize if this is the wrong place to request such a detailed feature. I didn't know where else to ask. If you don't wish to update xpad.c at this time, please feel free to delete my long post to clean up the thread. Thanks!
[Nexus 6P Original Android Development] Krunk83:
No. Chroma ROM. Happened on stock ROM too.

Nexus 6P
[Nexus 6P Original Android Development] vn00914361:
Is there any way to make the CPU settings stay after being changed or reboot? For example, the CPU cores and Hexacore mode. They're always changed automatically after awhile.

Sorry if this question is already asked, I'm new to Nexus 6P and originally come from Nexus 5.

Thank you.
[Nexus 6P Original Android Development] therock3181:
You need to click on the symbol next to what is written on the same line. It will turn blue. It will stick after a reboot.
[Nexus 6P Original Android Development] flar2:
These will not stick because there are other processes that occasionally put them online, like the thermal-engine.
[Nexus 6P Original Android Development] vn00914361:
Thank you for your response. I'm very familiar with EX Kernel Manager itself because I used it on my Nexus 5 :)

Thank you for the info, [MENTION=4684315]flar2[/MENTION]. And also thank you for your work :)

---------- Post added at 07:39 PM ---------- Previous post was at 07:38 PM ----------

Thank you for your response. I'm very familiar with EX Kernel Manager itself because I used it on my Nexus 5 :)

Thank you for the info, [MENTION=4684315]flar2[/MENTION]. And also thank you for your work :)
[Nexus 6P Original Android Development] Trenth2247:
Favorite profile for 6p?

I'm just curious on what profiles y'all use and what type of Battey stats u get? Thanks. I'm currently liking silverfish
[Nexus 6P Original Android Development] likonvampire:
Anyone tried the kernel on DP5 yet ?
[Nexus 6P Original Android Development] coronanlime:
Modifying headphones gain and then using volume control on connected headphones causes Google now to pop open instead of adjust volume. Do it enough times and it causes a reboot.
[Nexus 6P Original Android Development] Nitemare3219:
Don't think a kernel for DP5 has been released yet.
[Nexus 6P Original Android Development] likonvampire:
We will have to wait fort the AOSP source to be available , was just checking if anyone tried the DP4 EX release on DP5
[Nexus 6P Original Android Development] chubby65:
Oh yeah my favorite kernel from my Nexus 6 now on the 6p

AWESOME
[Nexus 6P Original Android Development] bsg411:
I just grabbed the app. Will try the color profile when I get home today.
[Nexus 6P Original Android Development] flar2:
A little tweak to get rid of touchboost (in terminal, as root):

stop perfd

Use with caution, I'm not sure what else it does. It may be more beneficial to leave it running.
[Nexus 6P Original Android Development] NovaSlim:
You can freeload if you want to :p, but you are missing out on the colored dashboard, kernel updates notifications(and you can choose between express/aroma version once those are available) and other features EX kernel Manager have.

Above all [MENTION=4684315]flar2[/MENTION] is a great developer who cares a lot about his users and deserves our support, plus that $50 google playstore credits you got have to go somewhere ;) .
[Nexus 6P Original Android Development] flar2:
So, it turns out this device does have a secret doubletap2wake setting:

echo 1 > /sys/devices/soc.0/f9924000.i2c/i2c-2/2-0070/input/input0/wake_gesture

Surprised nobody found it yet!
[Nexus 6P Original Android Development] FuMMoD:
It's because you're the man!
[Nexus 6P Original Android Development] shawnten:
out of curiosity does this phone have the hidden high brightness settings. I love your high brightness widget on the nexus 6
[Nexus 6P Original Android Development] Mikey:
Long time no see [MENTION=4684315]flar2[/MENTION]

Time to jump back onto your train :)
[Nexus 6P Original Android Development] hutzdani:
Problem is I got frankos manager over 2 years ago and it works with pretty much all kernels that are built upon Google's source code for that device.

Unfortunately I can't justify buying every developers kernel manager, you only need one ;) however you can always donate right !
[Nexus 6P Original Android Development] boxcar8028:
It’s like christmas morning! Good to see that flar2 is in the house! :good::good::good:
[Nexus 6P Original Android Development] markwebb:
Thank you so much. Props on the screen calibration alone!
[Nexus 6P Original Android Development] d1ez3:
Can the phone still doze with this enabled?
[Nexus 6P Original Android Development] flar2:
Probably. All the kernel needs to do is what it normally does: enter suspend (ie, deep sleep). Doze is a userspace thing, where Android restricts background operations by apps and services to specific time windows.
[Nexus 6P Original Android Development] dsmitty166:
Works great! Thanks!
[Nexus 6P Original Android Development] tropazr:
Buying the dev's app from the Play Store and leaving it uninstalled would be a great way to donate!!! Just saying! ;)

---------- Post added at 12:16 PM ---------- Previous post was at 12:11 PM ----------

I am not familiar with this. Is this code that I can add that will enable this feature right away?
[Nexus 6P Original Android Development] flar2:
I will add it to EXKM tonight

Entering that command will enable it right away, but would not survive a reboot.
[Nexus 6P Original Android Development] dsmitty166:
Yeah, you can for now until flar adds it in to kernel manager. However, as he has stated, you will need to redo this upon reboot. If you want to try it out, you will need to download a terminal emulator from play.

The commmands then are as follows

su
echo 1 > /sys/devices/soc.0/f9924000.i2c/i2c-2/2-0070/input/input0/wake_gesture
[Nexus 6P Original Android Development] tropazr:
Yep got it to work with terminal emulator. Works perfect (except for the reboot part). Aweeeeesssssome! I was going to freak out if I couldn't get DT2W. Loving this phone now. THANK YOU SIR!
[Nexus 6P Original Android Development] imstill@g:
Sorry for the request, but as many have stated in a few threads, previously google had " twist to launch camera" implemented during the early stages, any chance of reinitiating that? Thanks for your work either way.
[Nexus 6P Original Android Development] flar2:
I suspect that will be something for ROM devs to figure out, but I'll take a look.
[Nexus 6P Original Android Development] italia0101:
Btw if you're someone that moves around a lot, having inactive time set so low will cause a lot of wakelocks. I've had a pretty massive discussion here about it all, ;

http://xdaforums.com/android/apps-games/root-doze-settings-editor-android-t3235130

i've connected my device to ADB and watched how Doze works, even if you're in idle ( doze ) and you start moving, the device will leave doze and go back to " inactive " now if you're inactive time is set to 60 seconds ( like yourself ) then the process will go like this , inactive ( 60s) , sensing , locating ( if you're moving it won't go into doze ) , inactive ( 60s) sensing, locating .. and it'll keep doing that till the device is still.

now of course if you're someone who's at a desk all day , then its going to get into doze quicker, but if you're moving around all day, then it's going to cause " sensing " and " locating " a lot more often than you'd want.

so bare that in mind when messing with the settings,

Oh and this also applies to Greenifys " agreesive doze" which is just the " force-idle " command when screen is off,
[Nexus 6P Original Android Development] NovaSlim:
I am at a desk all day, except for the 1.5-2 hour in which I exercise/shop/drive. So yeah, I think that setting is fine with me.

Thanks for informing me though, that kind of explains why Doze is my #2 wakelock.
[Nexus 6P Original Android Development] italia0101:
Yep that will work great for you :good: , just trying to warn people if they have a job where they are out and about all the time , it will probably do more worse than good.
[Nexus 6P Original Android Development] 4redstars:
Bear with me, I've been stuck an a Galaxy S6 for a while and didn't flash anything for a while.

Bootloader unlocked, Sweep up to wake selected and no sweep to sleep selected. I can't get sweep up to wake my phone.

Is there some other thing I need to get it working? Do I need to select sweep to sleep to get sweep to wake working? Do I need to root and add the Elemental app or wake gestures?

Thanks all.
[Nexus 6P Original Android Development] flar2:
You need root so the boot script has permission to enable the setting.
[Nexus 6P Original Android Development] sherlock5545:
I'm finally back on the Nexus line again. Glad to see you here too, [MENTION=4684315]flar2[/MENTION]. One small question, are wake controls on this device the same as on the Nexus 5 that drained a lot of battery? Or is the hardware appropriate for a negligible drain, like on devices that support dt2w natively?
[Nexus 6P Original Android Development] Scottland:
Hi,

Just installed - so wanted so say thanks to [MENTION=4684315]flar2[/MENTION] (ElementalX app purchased ;))

2 Questions:

1) I assume that colour tweaking will completely negate the need to use the sRGB mode in developer settings?

2) Has anyone played with underclocking the CPU or enabling Hexacore mode? i.e are there any 'known' settings that work quite well

Thanks :)
[Nexus 6P Original Android Development] italia0101:
Yes that's correct there is negligible drain with wake gestures :)
[Nexus 6P Original Android Development] flar2:
1. sRGB mode is something different than color control. Color control allows you to change RGB, Hue, Saturation, Contrast and Value, which are like the settings you will find on decent monitors. These will allow you to adjust brightness, contrast and color temperature. Basically calibration. sRGB is a colorspace, like the setting you would find on a camera or in Photoshop if you are processing RAW images. This is a way of profiling the range of colors that can be reproduced.

2. Try it and see. We're still in the experimental phase. I haven't had time to do much testing myself.
[Nexus 6P Original Android Development] Scottland:
Cool, thanks I'll play around then :)
[Nexus 6P Original Android Development] Franzie3:
[MENTION=4684315]flar2[/MENTION] have you found a nice RGB color combo yet or are you still stock as far as screen color control goes?
[Nexus 6P Original Android Development] 4redstars:
It's working. Thanks Flar!
[Nexus 6P Original Android Development] flar2:
Mine's pretty good out of the box, a bit on the cool side though.

Sometimes I dial back the green and blue a bit, to warm up the screen.
[Nexus 6P Original Android Development] xamius:
How long should boot take the first time? Custom rom boot animation has been going for about 5 minutes so I assume something went wrong. I tried without the enforce option checked and it never loaded the boot animation....
[Nexus 6P Original Android Development] flar2:
You most likely need the enforcing option unchecked with a custom ROM.

The neverending bootanimation is a symptom of enforcing kernel with Rom requiring permissive mode.
[Nexus 6P Original Android Development] Simer03:
Man I lost like 6% battery over about 5 hours overnight. I can't seem to get the same idle time as u guys! I average 5-6 hours screen time tho even on LTE so I can't really complain but my idle drain is infuriating lol
[Nexus 6P Original Android Development] likonvampire:
[MENTION=4684315]flar2[/MENTION] stumbled into something on Reddit under the Nexus6p subreddit.

Not criticizing your work here as I am using it currently using your kernel and it has been awesome. Take a look : http://i.imgur.com/RFPHPaS.png
[Nexus 6P Original Android Development] Mushroom.:
I have not found this to be true. I am seeing long wake locks and much less time in deep sleep when using any of the wake gestures. 5-6% per hour, without touching the phone for extended times. As soon as I disable them, the device sleeps normally, less than 1% drain per hour.
[Nexus 6P Original Android Development] flar2:
That's not my experience at all. I ran the phone for nearly a week 100% stock, and since I add gestures I've had them enabled the entire time. There is no difference in idle drain. Idle drain is exceptional, I lose just 1% or less overnight.

5-6% per hour is worse than just leaving the phone's screen on. There's no way that's due to the gestures.
[Nexus 6P Original Android Development] bajasur:
[MENTION=4684315]flar2[/MENTION]

I just attempted to install kernel from within ex manager. It auto downloaded and rebooted into twrp and flashed kernel. Went into bootloop directly after, just wanted to give you a heads up. Manual flash went great! Thanks for great kernel and the app is beautifully materialized, great work
[Nexus 6P Original Android Development] mitchdickson:
You could just try it, right?
[Nexus 6P Original Android Development] 1Cubesolver:
Since no one else said if they tried it yet or not I decided to install it and everything is working fine as of right now.
[Nexus 6P Original Android Development] jiajialing:
anyone tried 3.03 works for dp5? tks
[Nexus 6P Original Android Development] steviemch:
Possibly check the post right above yours?

Nexus 6P
[Nexus 6P Original Android Development] kyzn:
I was using DarkspiceR7.5 but it caused popping sound when I use Viper4Android. The battery life was amazing but the interference was killing my eardrums.

Switched to MadDog recently and it fixed it. It drains my battery faster but nothing too alarming. I still get a solid 5 hours SOT with streaming music and podcasts, Reddit, emulation, internet and social media. Location mode set to high accuracy.
[Nexus 6P Original Android Development] relevant_placeholder:
No Xposed here, using ex for a long time, several devices. All gestures off, show touch area on in dev options. Same thing when waking the device up.

Don't have any problems with battery drain when screen off but just thought it's work mentioning.
[Nexus 6P Original Android Development] therock3181:
DarkSpiceR7.5 and Heimdall (v4 and V5) caused popping sound with v4A. I tried to higher the low and big clusters and it didn't work out. I was wondering if I was the only one !

I started using GhostPepper and it stopped.
[Nexus 6P Original Android Development] kyzn:
There's an explanation over at the V4A thread as to why this happens. Apparently interactive governors ramp up too quickly and the audio output gets affected when using a custom kernel. The solution was switch to On-demand or change the minimum frequencies to above 400mhz.
[Nexus 6P Original Android Development] therock3181:
I'm aware. Putting the frequency above 400mhz didn't work on heimdall or darkspice. With Ghostpepper it's all good.
[Nexus 6P Original Android Development] flar2:
I can add this to the kernel, but it will be up to users to add the keylayouts, since I don't want to modify system in any way.
[Nexus 6P Original Android Development] tlrsax54:
[MENTION=4684315]flar2[/MENTION] Got a new Nexus 6p and been running Chroma + Elementalx (no xposed/mods), Darkspice profile. Today I randomly had a reboot happen while it was in my pocket, not sure if I accidentally did it or if something weird happened, thought I'd send a log :) Never done this before so hopefully this works;

http://pastebin.com/ZqRXp7q7
[Nexus 6P Original Android Development] flar2:
No problems in the log
[Nexus 6P Original Android Development] lahma69:
Wow, that is so awesome! I really did not know if my request would even merit a response, so I really appreciate you taking time not only to respond, but also to implement a feature due to the request of peon such as myself ;)

Concerning the keylayouts, I definitely did not expect you to implement those in the kernel. I mostly included the additional information for the purpose of completeness and for outlining the entire picture in regards to my request. Being that it took a significant amount of time on my part to understand all the different pieces needed to add functionality of a previously unsupported gamepad, I figured it might be useful information to someone else who became aware of the fact that your kernel had the required elements to make Xbox One gampads function on the Nexus 6P.

Perhaps I should post that info in a dedicated topic. I'm not sure if the "Nexus 6P Android Development" forum would be most appropriate or if it should just go into the "Nexus 6P General" forum, but I will read the rules to find out.

Thanks again! I will patiently await a commit for the updated xpad.c (hopefully on v1 and v3). Just out of curiosity's sake, could someone such as myself submit a pull request on your Github for something simple such as this? Would that be a more appropriate means of requesting such a change when the code is very simple and/or already exists?