yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] beauh82:
My safetynet is failing too. It says CTS profile mismatch. It always used to work before I updated to the new pure nexus and the new 4.04 ex
[Nexus 6P Original Android Development] snsone:
It mismatched for me too until i enabled magiak hide from the manager and rebooted
[Nexus 6P Original Android Development] zerosource:
is there a way to disable home screen rotation? i can't find option.
[Nexus 6P Original Android Development] Pollie81:
Why do you ask this in a kernel topic?

You can set the screen rotation globally in the rom itself, home screen rotation is normally set inside the launcher options.
[Nexus 6P Original Android Development] zerosource:
because it doesn't rotate before I installed ex.
[Nexus 6P Original Android Development] Pollie81:
Hmm, ok.. strange. Then i can't help you..
[Nexus 6P Original Android Development] maximusmullivan:
Well your screenshots indicate you're looking for auto rotate settings under your google app settings, that's the wrong place. It's under display settings.
[Nexus 6P Original Android Development] zerosource:
I'm looking for *home screen rotation setting, not system-wide screen rotation.
[Nexus 6P Original Android Development] maximusmullivan:
Ok. Good luck
[Nexus 6P Original Android Development] luigidk:
Can use EX as follows:

Will bypsss unlocked bootloader check?

Will let me install ViPER4Android (permissive)

Lets me enable dt2w wo root?

Thx
[Nexus 6P Original Android Development] kyzn:
Yes.

Ex kernel is enforcing. And running permissive on boot is counter productive because to pass safety net you need to be enforcing.

Yes, I think so.
[Nexus 6P Original Android Development] luigidk:
Oh, bummer on enforcing because as unrooted i can't install v4a.

Are you sure AP requires enforcing?

I used a permissive kernel that had a bypass for the unlocked bootloader check and AP worked fine.
[Nexus 6P Original Android Development] Augustin79:
I'm getting stuck on the Google logo after installing elementalX kernel. Anyone know how to fix this?
[Nexus 6P Original Android Development] burningcreation:
Did could happen if you installed it over another kernel. Did you do that?
[Nexus 6P Original Android Development] Augustin79:
No, I dirty flashed before flashing Elemental
[Nexus 6P Original Android Development] xflowy:
any more ideas on this?
[Nexus 6P Original Android Development] joooooooooosh:
Is anybody having an issue with the CPU where the little cluster is stuck at the max frequency?

I updated EX to 4.04 yesterday, and I noticed battery was being depleted faster than normal. Checked kernel manager and battery usage is just over 25% per hour with the little cluster stuck on max frequency.
[Nexus 6P Original Android Development] Badger50:
During the aroma install, did you overclock the CPU?? Flar2 doesn't recommend that. Pays minimal dividends anyway. Go back and install it again and select the stock values [emoji106]

Sent from me :)
[Nexus 6P Original Android Development] joooooooooosh:
I did overclock. However, it used to be alright. Yesterday was the first time I used express settings though so maaaybe that might be it? Idk

I reinstalled using stock frequencies and the little cluster is still running at max frequency. I'll see how everything goes throughout the day and report back tonight.
[Nexus 6P Original Android Development] Badger50:
If it persists....clear the app data or uninstall the EXKM app, then install it again and clear cache and dalvik in recovery [emoji106]

Sent from me :)

---------- Post added at 12:19 PM ---------- Previous post was at 12:18 PM ----------

Outa curiosity, what rom are you using? Is it MM or Nougat?

Sent from me :)
[Nexus 6P Original Android Development] JYJY:
I experienced the exact issue. However, I did resolve it by uninstalling FB and FB Messenger - little cluster back to normal frequency.

I'm running the latest Nitrogen 7.1.1 rom.

Hope this helps.
[Nexus 6P Original Android Development] joooooooooosh:
I tried your suggestions to no avail :'(

I'm on 7.1.1 Cortex.

EDIT:

The culprit was FB messenger. Killing it fixed the issue in my case.
[Nexus 6P Original Android Development] jujak82:
Same problem here
[Nexus 6P Original Android Development] joooooooooosh:
Yep it was definitely FB messenger running in the background. Force closed it and all is right with the world.

Thanks for tip.
[Nexus 6P Original Android Development] Badger50:
Then you'll have to wait to hear from Master Flar2 himself. I've used his app on so many different roms and systems and never encountered that issue at all. Hope you guys find an answer though [emoji106]

Sent from me :)
[Nexus 6P Original Android Development] flar2:
Frequencies running at max are caused by app problems. Likely Facebook.

It's not a kernel issue.
[Nexus 6P Original Android Development] DorianX:
Yup I noticed that issue yesterday, looking at battery stats found the culprit (FB Messenger), just cleared data for that app and problem solved

Enviado desde mi Nexus 6P mediante Tapatalk
[Nexus 6P Original Android Development] joooooooooosh:
RE FB messenger causing battery issues:

https://www.reddit.com/r/Nexus6P/comments/5n3zcz/facebook_messenger_battery_usage/
[Nexus 6P Original Android Development] d08speed3:
Mannnnn this is prob the reason why my little cluster was locked at 1555mhz. Usage was almost at 100%!!! Cleaned flashed 3x to get rid of this with same issues. I will delete FB Messenger and see how it goes! Thanks for posting this!
[Nexus 6P Original Android Development] JYJY:
It is fixed now. Apparently, the issue is on the server-side.
[Nexus 6P Original Android Development] CappyT:
I understand that is generally not really liked to ask for feature (it's a solid and stable kernel) BUT

Is there or have been a plan to add hotplugging to EX? Because that would be really cool to have, tried a kernel that had it (Flash Kernel) and it was really helpful squeezing a bit more battery and keeping the temps low. Unfortunatly, that kernel isn't supported anymore, so I'm back to EX.
[Nexus 6P Original Android Development] thloe:
Hello!

Sorry for this noob question but i don't know much about Kernels. Is the monthly security patch only the specific part for the kernel or for the whole rom? I Hope you guys know what i mean. Thanks for answer!
[Nexus 6P Original Android Development] nathanchance:
It applies to both, there will be security patches in the kernel and various repos for the ROM.
[Nexus 6P Original Android Development] zerosource:
hi, i find that i cannot toggle between speaker phone or ear phone during a call with Facebook messenger using this kernel. is there anyone else having the same issue?
[Nexus 6P Original Android Development] indian84:
I don't use FB messenger, but to be honest, I don't think the kernel has anything to with the toggle.

Doesn't make a whole lot of sense.
[Nexus 6P Original Android Development] bossofindy:
I'm using this kernel with ex manager and certain options are missing like changing gov, i/o, vibration strength did I miss some changes or do something wrong?
[Nexus 6P Original Android Development] Badger50:
That's really odd. Maybe clear app data, uninstall, reboot, download again from play store. It should look like this of course.

View attachment 4002002

Sent from me :)
[Nexus 6P Original Android Development] bossofindy:
I tried all that, I think I will reflash rom and kernel and see what happens
[Nexus 6P Original Android Development] flar2:
That's how it looks if root access is denied or your phone is not rooted.
[Nexus 6P Original Android Development] bossofindy:
Thanks I reflashed pn and forgot it doesn't come rooted, on a side note once I cleared app data in ex manager, and it goes through startup, verifying license etc, it said acquiring root and took me straight to app, it didn't tell root access denied.
[Nexus 6P Original Android Development] nicochoco03:
for the battery drain i have update latest beta of facebook and messenger apps and after battery drain little again so i have make a recalibration battery and now all is good !!
[Nexus 6P Original Android Development] note3userr:
I have that enabled and it still fails. Says mismatch
[Nexus 6P Original Android Development] USFguy:
Battery is constantly showing that "Kernel (Andriod OS)" is my top battery drainer in Gsam, running stock ROM but no Kernel tuner such as EX is that my issue?
[Nexus 6P Original Android Development] grazhve:
+1
[Nexus 6P Original Android Development] flar2:
Nothing to do with the kernel
[Nexus 6P Original Android Development] grazhve:
Best governor, for battery life ?
[Nexus 6P Original Android Development] danmaman:
Hi [MENTION=4684315]flar2[/MENTION]

Do you looked into this stuff I posted in g+

With sys/module/workqueue/parameters/pwer_efficient?

What is it,? And make it sense

Thanks
[Nexus 6P Original Android Development] d1n0x:
If you have no root management app installed, of course it's not going to ask you.
[Nexus 6P Original Android Development] relevant_placeholder:
[MENTION=4684315]flar2[/MENTION], if memory serves me well support for the livedisplay was added and then removed. Not sure what was reason for removal but now on lineageos I'm having problem maintaining the color profile from the app. Could you please consider returning it and make it toggle able? Thanks.
[Nexus 6P Original Android Development] flar2:
I don't know why, but LiveDisplay removes the settings at screen off and reapplies them at screen on. This causes all sorts of problems.
[Nexus 6P Original Android Development] relevant_placeholder:
Yes, noticed same thing. Would contacting someone from lineageos developers help to resolve this? It's mutual interest, me thinks.

Btw, closing PM's was eloquently bad thing to do.
[Nexus 6P Original Android Development] flar2:
Ever since Nougat was released, there's a problem of selinux restricting access to sysfs settings.

You need to use a root command to read most things in sysfs, but that's really slow. So my app tries to read it the "normal" fast way first (which takes like a couple milliseconds) and if it's denied, it uses root to read. That's why there are so many denied errors.

As for the big cluster offline, I think this is also related to selinux. I notice it on my apps because they sometimes show the big cluster stats without root and sometimes don't. There is context for cpu stuff (sysfs_devices_system_cpu) and a more restricitve context for regular sysfs. Sometimes the context gets changed to sysfs and then the cores get stuck offline.
[Nexus 6P Original Android Development] flar2:
They aren't going to change it, most likely and there are other problems specific to angler.

I had to close my PMs, there is a 5,000 pm limit and I was constantly having to delete them and then it would fill up again, and it was impossible to keep up with them and wasting to much time. 90% of the PMs were things that should have been posted on the forums.
[Nexus 6P Original Android Development] matt4321:
Cheers for the response, been racking my brains for the past week with this one. It's odd that even with a fresh install the big cluster is not going offline. From reading about it seems some are experiencing it but not all. With it potentially being related to SELinux is there something user side we could do to fix this? Would say changing to permissive help, although this isn't ideal as a permanent solution. It has some impact on battery obviously which is why I've been investigating and trying to track the problem down. Pretty much having the big cluster on idle the whole time takes a bit of toll. So does it seem like the big cluster isn't getting the root permissions to go offline? Some of these are probably dumb questions, sorry haha, I'm nowhere near as technical as you :p
[Nexus 6P Original Android Development] jhs39:
For a lot of people the issue you describe is being caused by Facebook apps, usually Facebook Messenger.
[Nexus 6P Original Android Development] USFguy:
What is it then? It seems to be destroying my battery life sucking up greater than 30% every charge.
[Nexus 6P Original Android Development] Az Biker:
Have you trued Better Battery Stats or Wakelock Detector to see what is keeping your device awake?

It's not a Rom or the kernel, per se, because I'm using both and getting 4+ hr sot daily with moderate-heavy use.
[Nexus 6P Original Android Development] matt4321:
So this is the strange thing, I uninstalled this at first. And it didn't fix it. I then did a clean install so no apps were installed other than GApps and elementalx manager and still had the issue of the big cluster not going offline
[Nexus 6P Original Android Development] relevant_placeholder:
I've never seen big cluster going offline unless throttling kicks in. When or on what have you seen them going out and it's not cause of heat?

To put this to rest, use ex app with stock kernel that comes with your ROM.
[Nexus 6P Original Android Development] matt4321:
From the past year of using my 6P with ElementalX, it's always been my understanding and seeing it within the app that the little core is always online, 2 of the big cores come on when needed and then when high performance stuff happens all 8 are online.

Whereas now when I go to the app I always see all 8 cores just always online. Maybe I need to find some time to throw stock on and see what normal kernel behavior is.

Maybe I'm just derping, do most people always have 8 cores online then? and it only throttles when needed?
[Nexus 6P Original Android Development] relevant_placeholder:
Reboot and then go to the app, two big cores will be off. Or try something CPU intensive, maybe AnTuTu? As temps go up so do cores go off.

That's my experience at least.
[Nexus 6P Original Android Development] SlimSnoopOS:
I just briefly glossed over your exchange with [MENTION=4684315]flar2[/MENTION] and I think there is some confusion. He specifically mentions CPUs behaving outside of his apps control due to selinux and you are referring to the CPUs staying online. I think the confusion is about the big cluster (CPUs 4-7). Here's my generic understanding of Snapdragon 810 and 808: CPU0 (little) and CPU4 (big) control their respective clusters. Default BIG.little behavior (and in this kernel), the clusters follow the master CPUs 0 and 4. Big cluster should be offline when under high heat (throttling) or low battery. The big cluster should idle at low speeds and ramp up when it takes a load off the little CPU then drop back down once that load is complete. All CPUs should be online at all times. The behavior, as a user, that you want to be on the lookout for is whether your CPUs are sticking to the highest frequencies or the big cluster is offline for an extended period of time that is not detailed above.
[Nexus 6P Original Android Development] flar2:
All cores should be online unless there is thermal throttling.

There has been a lot of confusion about cores on/off line since nougat because, as I mentioned, an selinux bug prevents a lot of apps from showing their status properly.

DevCheck will show them as "offline" if they are offline or as "NA" if it can't read the status.
[Nexus 6P Original Android Development] donroja:
@ flar2 - First off, thank you for this amazing kernel, best experience I've had on pure nexus yet! Secondly, I'm wondering if the permissive zip that you made would work with ElementalX-N6P-4.04? Permissive is needed for me to run an app to mirror my phone to my pioneer deck... Thanks in advance and for all your hard work... I forgot to mention, I'm currently on 6.0.1 and using N6P-1.21 and the permissive zip works great.
[Nexus 6P Original Android Development] mlese92:
For some reason the substratum (layers) app hits me with the app isn't responding after installing this kernel. I tried rebooting, clearing caches, reinstalling and nothing. It works on stock kernel so I assumed it was the kernel causing the issue. Its not a major deal because this kernel is great i just didn't know if anyone had any issues with this as well. I ran a search and couldn't find anything in the thread. Any help appreciated. Thanks again for the fantastic kernel
[Nexus 6P Original Android Development] jhs39:
Did you clear the app data and cache? I use this kernel with Substratum with no issues. If that doesn't work try flashing the vendor image that is compatible with your ROM. That has been known to fix Substratum issues.
[Nexus 6P Original Android Development] mlese92:
Yeah just tried it and no avail. Not really sure what's left other than a clean flash butt nooooo
[Nexus 6P Original Android Development] s13epy:
[MENTION=4684315]flar2[/MENTION] everything is running amazing so far thank you for your work. I'm using stock CPU frequencies, FIOPS/512, and disabled all sleep/wake settings. Running the factory Google image MDB08M with systemless root.

I am curious though if you'll ever implement into your Aroma installer the option to choose a governor?
[Nexus 6P Original Android Development] logonaniket:
Why Advanced color settings doesn't stick after restart? #Nexus6P
[Nexus 6P Original Android Development] NovaSlim:
When flar2 start tweaking CPU governors, that option might surface. Right now ElementalX governor is not tuned for N6P.
[Nexus 6P Original Android Development] micmars:
Working just fine here...did you flip the apply on boot toggle?

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Original Android Development] emiwonder:
seems to be kernel issue. no such problem using Kylo or stock.
[Nexus 6P Original Android Development] elreydenj:
I too experience the quick drop from 99 - 98 percent.
[Nexus 6P Original Android Development] ShermanTenor:
[MENTION=4684315]flar2[/MENTION] - thanks so much for developing your ElementalX family of kernels. I've really enjoyed the added functionality offered by them with a few devices. I'm wondering, do all of your kernels have init.d support? I saw it as a listed feature for the HTC One (M7) and Nexus 7 (2013) versions, but thought I would ask as it wasn't specifically mentioned in the Nexus 6P kernel's features in the OP of this thread.

Perhaps its a given - but I thought I'd ask all the same!

Thanks again for all of your hard work!

ST
[Nexus 6P Original Android Development] anglerstock:
Not sure how you guys measure quickdrops of just 1%, but battery on android has never been symmetric. For example you get 4 hours SOT during the first 50% but you only get 2.5 hours SOT during the other 50% left. That said, the % drop by default is never linear.
[Nexus 6P Original Android Development] emiwonder:
don't know, on my old moto g and nexus 6p with stock kernel or kylo battery consumpts gradually. about 15 percent per hour.
[Nexus 6P Original Android Development] flar2:
This is identical to stock in every way related to battery
[Nexus 6P Original Android Development] anglerstock:
Yupp. Others using stock kernel are reporting same thing on battery thread.

---------- Post added at 12:03 PM ---------- Previous post was at 11:03 AM ----------

Flar2 is it possible to have a post in the OP where you can explain in a few words what exactly every option in the kernel app does? Maybe not every option, but at least the ones related to sound for example or others related to cpu/gpu scaling. Whenever you have time, no hurry. I was just thinking that it will be beneficial to all those that purchased the app to pretty much know what each feature does, although some of them are self explanatory. Thanks.
[Nexus 6P Original Android Development] __NBH__:
Are the touch boost options working yet? I've played with the settings but struggle to see a difference with it disabled or at a frequency. I did a test today with the first 4 cores as touch boost and I'm still getting amazing battery.

Also it shows 8 cores but all of them have the same frequencies to choose from, shouldn't 4 show the little frequencies? This is in kernel adiutor by the way.
[Nexus 6P Original Android Development] zgroten:
I'm having random reboots on the most current version of this kernel and xposed framework installed.

No apps even activated on Xposed. Anyone else having issues with xposed? Or the latest version of the kernel?
[Nexus 6P Original Android Development] anglerstock:
All reboot questions from users that have exposed installed should be banned :p
[Nexus 6P Original Android Development] NovaSlim:
logs, Xposed logs go to Xposed forum and sys/fs/pstore contents needs to be uploads here so developer can look into it to see what might have gone wrong.

N6P with this Kernel, Xposed V78 and Gravity Box 6.0 running just fine. :p:p
[Nexus 6P Original Android Development] zgroten:
Explain real quick. I know there's a warning for xposed that custom kernels may cause issues, but I'm wondering if THIS kernel has caused anyone issues. It's a valid question.

---------- Post added at 10:51 PM ---------- Previous post was at 10:48 PM ----------

THANKS! I can rule out the kernel and focus on potential mods that I've activated in gravitybox.

Do you have dt2w, seLinux enforcing, or anything else disabled, enabled?
[Nexus 6P Original Android Development] NovaSlim:
S2W( all directions), and selinux permissive. Haven't tried enforcing yet but will try sometime later.
[Nexus 6P Original Android Development] zgroten:
I think that enforcement of selinux is the issue. I'll test it out with permissive.
[Nexus 6P Original Android Development] Purpeltendire:
I've attached my pfstore contents from a reboot earlier, I grabbed them right after the boot sequence finished.

I'm running MDB08M, ver. 0.07 of this kernel, Xposed framework 78, SELinux set to Enforce. S2W enabled only to the right, S2S only to the left.

It happened while I was playing with the Greenify Xposed settings twice in a row, so I uninstalled Greenify and its module completely. I'm thinking that was the issue and have had zero complaints with the kernel, but I figured I might as well be helpful while I can.

Now that Greenify is gone, the only thing I'm running in Xposed is GravityBox for 6.0.

Let me know if I can provide anything else.
[Nexus 6P Original Android Development] chubby65:
Set SELinux to permissive

That should stop your reboots
[Nexus 6P Original Android Development] jhs39:
You tried both clearing app data and flashing vendor image and neither helped? What happens when you try to use Substratum?
[Nexus 6P Original Android Development] mlese92:
Yeah I tried both and I get this
[Nexus 6P Original Android Development] jhs39:
Did you flash the ElementalX kernel over another custom kernal? What Rom are you running?
[Nexus 6P Original Android Development] mlese92:
I flashed it over the stock kernel in the pure nexus ROM. Tried reflashing ROM dirty and not elemental and still get the same errorn
[Nexus 6P Original Android Development] clambert11:
Try manually deleting the overlays. Looks like a theme issue to me.
[Nexus 6P Original Android Development] mlese92:
Just clean flashed and everything works. Thanks for the reply though I'll try that next time if it happens again. :svetius:
[Nexus 6P Original Android Development] Closed Source Project:
So sorry if this has been discussed before, I have tried searching all over the thread but yielded no results:

Has anyone been able to get ARISE audio mod working with this kernel? I'm on PN ROM and I cannot get Viper's driver to install while using this kernel (I've re-named the audio config file and everything). As soon as I flashed the ROM again and went back to the stock kernel it worked just fine. Any suggestions to get it to work with this kernel?

Thanks!
[Nexus 6P Original Android Development] HerrT:
I'm using PureNexus and ElementalX together with ARISE Deut 2.3.3 patched (without the Dolby Add-On). I didn't have to rename the audio config file either.

The only "strange" behavior I've seen is that I need to wait some time after installation of ARISE/Viper before opening the Viper App to make sure that it has SuperSU rights granted...
[Nexus 6P Original Android Development] Badger50:
If renaming the audio effect file thing didn't work. Make sure that file is also located in the system/etc. I read on the A.R.I.S. site that this has been happening with some of the newer roms and kernels as of late.

View attachment 4013786

Sent from me :)