yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] .hEiMDaLL.:
You are right.. I get four messages in logcat for each touch with QCOMPowerHAL: Failed to acquire lock.

Still wondering why it doesn't get stopped by using the "disable touchboost" option in EXKM and where the "switch" (the file) flar2 uses to deal with it is located. (and why there's a need for touchboost in the first place when we have input boost)

Regarding performance it's possible to mimic perfd with some governor settings. SOT is affected very much by perfd/touchboost, especially if you type a lot (or touch the screen often).

Btw. are you getting a lot of

flar2.exkernelmanager: type=1400 audit(0.0:28502): avc: denied { search } for comm=4173796E635461736B202334 name="msm_thermal" dev="sysfs" ino=7502 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u : object_r:sysfs_thermal:s0 tclass=dir permissive=0

and

flar2.exkernelmanager: type=1400 audit(0.0:28507): avc: denied { search } for comm=4173796E635461736B202335 name="msm_performance" dev="sysfs" ino=7156 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u : object_r:sysfs_performance:s0 tclass=dir permissive=0

when changing settings in EXKM? ( @flar2 too )

Yes, my "little" project is growing faster than I thought. At first I just wanted to make the sh scripts for the profiles a bit more error safe by adding some funtions to deal with different file permissions, eg. get the permission, save it, set to writable, write, restore it, etc. Now it has grown to a full tweaking tool and I'm still learning about the (m)ksh characteristics. I'm not used to extensive shell scripting, though ;)

Hope to release it soon. I'm currently trying to finish the backup and restore functions (more complicated than I thought, when you want to keep it fully modularized and don't want to add unnecessary code to the tweak-modules) and get the update routine running and deal with different ro.product_model and/or ro.product_platform to get the right profiles.
[Nexus 6P Original Android Development] hinxnz:
Changing the touch boost value won't do anything if you have stop perfd. I think touch boost is more responsive than cpu boost if you can notice it but can't adjust it by the sys interface.

I don't get that in logcat though, try wiping data for app and reboot.
[Nexus 6P Original Android Development] .hEiMDaLL.:
Decided to use just /sys/module/msm_performance/parameters/touchboost in the public profiles till I know more.

I searched for perfd source code but couldn't find it or any info wether it controls more than just touchboost or not.

(Anyone) any info on that or where to look for the source code?

The other error was my fault. Messed up super su lol
[Nexus 6P Original Android Development] BrianDickens:
Regarding the new exploit that just came up (as I cannot yet post links, google for Android Security Advisory—2016-03-18), I'm assuming the AOSP patches given at the AOSP site will be integrated into the ElementalX kernel?
[Nexus 6P Original Android Development] bgboii:
Yeah that is what I was trying to avoid. Idk what happened. Do you think I should of flashed the boot IMG and then flash SuperSU then the kernel?
[Nexus 6P Original Android Development] nathanchance:
Yes that should work.
[Nexus 6P Original Android Development] hanschke:
anyone test the n kernel for older android?
[Nexus 6P Original Android Development] KonoeKyon:
It mostly works if you don't care about using the camera.
[Nexus 6P Original Android Development] nadiros:
Yes, flar2 says he's been using his N kernel on MM.
[Nexus 6P Original Android Development] BakedTator:
Just flash r14 for Android N and everything seems to be working fine...sound, camera, and the like a function as intended (video recording works perfectly as well as video playback with the camera app and Google photos)
[Nexus 6P Original Android Development] hanschke:
if the camera or something else dont work it is not a good idea. thats why I asked.
[Nexus 6P Original Android Development] patsimeon:
Is there any way to have a version that doesn't have the 'sweep up to wake' on by default? Even when I don't have that feature checked on Aroma installer it still stays on, and I can't figure out how to turn it off at all. Tried reflashing it over and over. Tried reflashing stock rom and stock kernel then elementalx again. Still no luck.

Just in case, here's my setup:

Nexus 6P 6.0.1 MHC19I

Stock ROM

No Root

ElementalX 1.15

unlocked bootloader

TWRP 3.0.0-1
[Nexus 6P Original Android Development] nathanchance:
Because you don't have root, you won't be able to have the changes you make in Aroma take effect. I suppose flar2 could change that but most people want wake gestures.
[Nexus 6P Original Android Development] patsimeon:
Aww man. Everything's perfect minus the fact that that gesture is on by default. Is there any way to make a flashable zip of elementalx that skips the aroma installer? perhaps I can edit the screen wake gestures before flashing the zip through twrp
[Nexus 6P Original Android Development] flar2:
Why don't don't you just root the phone? I personally can't stand not being rooted. The only reason not to root is Android Pay, and I really don't see the point of paying with your phone. I just tap my credit card at the checkout and it's much easier than paying with a phone.
[Nexus 6P Original Android Development] patsimeon:
I wish I could just root, but I have specific apps that don't work when the phone is rooted. I tried using xposed & rootcloak to remedy that, but then Snapchat stopped working. So I figured the best way to mod my phone without rooting is exactly what I've done, which is unlock the bootloader, custom recovery, custom kernel. And also custom DPI by pushing build.prop edits through adb. All my apps still work this way and I get great battery life. But that swipe up gesture just doesn't do it for me personally.
[Nexus 6P Original Android Development] nadiros:
R14? Wrong thread mate ;)
[Nexus 6P Original Android Development] .hEiMDaLL.:
Gonna try it for some time with perfd started.

But some of my tweak settings get reset in rare occasions and I think perfd is the source of it.

I managed to find the sepolicy file for perfd on googlesource.com and got at least some insight on what directories and kernel variables it accesses.
[Nexus 6P Original Android Development] hinxnz:
Yeah it controls governor settings as you can see in the logcat I posted above, also KSM and frequencies.
[Nexus 6P Original Android Development] drawde40599:
Snap chat works fine with Root so does Android Pay

Flash 2.68

Delete Xbind folder

adb shell

adb shell run "su"

adb shell run "chmod 751 /su/bin"﻿

(Or use a file manager﻿ to get 751)﻿
[Nexus 6P Original Android Development] patsimeon:
I didn't say Snapchat doesn't work with root. I said I have apps that don't work with root. One example is Shomi. I tried to remedy that with rootcloak but since rootcloak requires xposed, that's when Snapchat stopped working. So I can't have root cuz some apps stop working, and fixing those apps while keeping root breaks Snapchat.
[Nexus 6P Original Android Development] drawde40599:
Gotcha my bad , I read it wrong .

Have you tried those modifications though ?
[Nexus 6P Original Android Development] steveo17:
You can use Snapchat with xposed. You have to be logged in first to Snapchat before flashing xposed
[Nexus 6P Original Android Development] 1112ee:
I though pay stopped working with any kind of root
[Nexus 6P Original Android Development] TechMillz93:
Your right it shouldn't work systemless or system so idk what he's talking about
[Nexus 6P Original Android Development] drawde40599:
Nope I use it everyday . Just follow directions I wrote . I would also delete your cards and start fresh before hand
[Nexus 6P Original Android Development] TechMillz93:
Anyone who has the N build how's everything functioning? Any flaws?
[Nexus 6P Original Android Development] drawde40599:
It works just fine , Screen is from last month but ....

https://drive.google.com/file/d/0B285zEYT-PIIR0xaMHk0MHN2SXc/view?usp=docslist_api

---------- Post added at 10:15 AM ---------- Previous post was at 10:14 AM ----------

It works just fine , Screen is from last month but ....

https://drive.google.com/file/d/0B285zEYT-PIIR0xaMHk0MHN2SXc/view?usp=docslist_api
[Nexus 6P Original Android Development] TechMillz93:
But how?
[Nexus 6P Original Android Development] drawde40599:
I'm still using 2.68 on Marshmallow .

Flash 2.68

Delete Xbind folder from SU folder then run

adb shell

adb shell run "su"

adb shell run "chmod 751 /su/bin"﻿

(Or use a file manager﻿ to get 751)﻿

Reboot

Add your cards .

Waaaaaalaaaaaa

I use it every single day I promise you .
[Nexus 6P Original Android Development] TechMillz93:
Did u run these commands on a PC or twrp terminal?
[Nexus 6P Original Android Development] drawde40599:
PC. I couldn't get terminal to work . But people have been having luck just changing bin chmod manually with there file manager.
[Nexus 6P Original Android Development] jesssiii:
On 2.68, permission is auto set, you just need to do the terminal commands before flashing SuperSU.

echo SYSTEMLESS=true>>/data/.supersu

echo BINDSYSTEMXBIN=false>>/data/.supersu
[Nexus 6P Original Android Development] coolcat67:
Hi [MENTION=4684315]flar2[/MENTION] for future builds of Android, would it be possible to upload a modified boot image to flash over stock boot image in order to root the stock system image via traditional root method? After flashing the latest stock images and EX kernel I was having a hell of a time rooting via traditional method. I finally figured out that EX doesn't disable dm-verity in the stock boot image to allow traditional root to work. Many posts were made about this when the 6P was first released, and I remember you had mentioned this in the OP way back then, but it is no longer mentioned in Heisenberg's 6P rooting guide or in your OP. A user in another thread was nice enough to alert me to this issue and sent me a link to a modified boot image to flash over the stock boot image before flashing supersu and EX.

I know many people use either systemless root or a custom ROM which would circumvent this issue but a post about this in the OP alerting users to this issue in the stock ROM would be very helpful IMO. Just a suggestion. Thanks for all your hard work!
[Nexus 6P Original Android Development] nathanchance:
What "issue" with the stock ROM? Why not just use systemless root? System root is slowly becoming obsolete because of how locked down Google is making everything. All you have to do is flash the SuperSU zip (it will decide which one it can do) then flash EX, there is no change in the process from system root. I don't mean to sound rude but you are asking one of the hardest working developers to do even more work.
[Nexus 6P Original Android Development] coolcat67:
First of all, supersu does not install systemless by default-- it installs via system method by default. Second of all, what work am I asking? To put a sentence in the OP alerting users that his kernel doesn't disable dm-verity so flashing supersu will cause a bootloop unless you force it to install systemless? I was coming from CataclysmMOD (which disables dm-verity for you) and kept bootlooping on flashing supersu. This was the first time I ever had to ask for help rooting or tweaking my device. This issue was raised all over when the 6P was first launched but now it is hardly mentioned anywhere. I typically am able to find answers pretty quickly on my own. I figured if I had this problem, other users would as well and a mention of it would be helpful to others.

For me, the next best thing to cataclysm is xposed+gravity box (and a few other mods) and if I'm going to use xposed, I see no benefit to forcing systemless root as Android Pay won't work anyway. There is probably a reason chainfire doesn't make that the default rooting method. I know you are one of the most helpful guys around making FAQs for everything and always trying to help people troubleshoot their issues so I am a little taken back by the response quite honestly. I don't think I was asking for much-- only trying to help others through my experience.

If I'm not mistaken, flar immediately uploaded a modfied boot.img to disable dm-verity when the 6P first came out (or his kernel initially did this by default, it's hard to remember back in November...), so if he was able to do that within hours of the source code being published, I didn't think it would take much effort to do it for future builds. But again, the main thing I was suggesting was a mention of this potential issue in the OP. Not everyone uses a custom rom.
[Nexus 6P Original Android Development] nathanchance:
Perhaps, I just wasn't understanding/seeing the issue you were having. To me, you were asking for flar2 to include a boot.img for system rooting (which would mean unpacking the stock image, reloading sepolicy, and repacking it). While that doesn't take too much extra effort, rooting via systemless requires nothing extra on his end and it works just fine. flar2 himself uses stock and has not reported any issues with rooting. I highly recommend you actually read Chainfire's release notes. With SuperSU 2.64+ (current version is 2.68), if a firmware can't be rooted via /system, it will root via a systemless installation, all without the systemless flags. I just rooted my friend's stock Nexus 6P a week ago or so (MHC19I) and had no problems just flashing SuperSU then EX. Didn't bootloop or anything. You can still use Xposed and all of your other tweaks with systemless root, the rooting method doesn't matter. Again, I am not meaning to be rude and I apologize if it came across that way.
[Nexus 6P Original Android Development] coolcat67:
Ah well I think I know what the cause of my problem was if supersu is supposed to auto detect dm-verity and install systemless if the boot image has it enabled. I didn't realize it now did that. Because I had forced systemless root in the past via terminal commands, I changed the terminal command to unforce systemless root (changing echo systemless="true" to "false"), which probably forced system root when the boot image didn't support it. After bootlooping a few times, I did try to change the command back to "true" but supersu kept installing to system anyway.

The reason I didn't want systemless with xposed is because AP wouldn't work anyway and I figured system root would be more compatible with xposed and any modules I might install... It's all making sense now. Sorry for the previous post [MENTION=4684315]flar2[/MENTION] -- seems the issue I had probably won't affect many users.
[Nexus 6P Original Android Development] Az Biker:
Older Versions

Just flashed 1.15 w./ PN... I know thermal throttling can cause this, but the CPU temp is <90°... Any idea why these are offline? Even running a avi file...

UPDATE: So I flashed EX 1.10 and all four cores show 633 again with nothing in the configuration changed except the kernel.
[Nexus 6P Original Android Development] beren:
working good on my 6p :good:
[Nexus 6P Original Android Development] flaheat88:
Hey guys just wondering I'm running stock+rooted+elementalx and I keep getting updates from Google. Is it cool to update or will I lose root or my recovery? It's probably been answered already so sorry in advance.
[Nexus 6P Original Android Development] nathanchance:
You won't be able to update if you have TWRP installed. flar2 has a post here on how to do updates while rooted and having a custom recovery.
[Nexus 6P Original Android Development] sherlock5545:
Flar always suggests dirty flashing the ROM if coming from another kernel. What about stock factory image though? On his website he says simply flashing boot.img isn't enough most of the time.
[Nexus 6P Original Android Development] cattel:
Could someone help me! I'm trying to install an new governor, i've put the file in the gov folder, but didnt show up in the kernel ex!

Need to do something else???
[Nexus 6P Original Android Development] Balino:
It needs to be hardcoded in the kernel

And flar2 already stated he is not going to add governors in elementalx

Inviato dal mio Nexus 6P utilizzando Tapatalk
[Nexus 6P Original Android Development] SlimSnoopOS:
If you're using stock rom with another custom kernel, use fastboot or TWRP to flash the stock boot.img that matches your rom then flash Ex. If you're on stock rooted with stock Google kernel, just flash Ex.
[Nexus 6P Original Android Development] sherlock5545:
Thanks. So I suppose simply flashing the boot image is enough if I'm on stock with another custom kernel.
[Nexus 6P Original Android Development] Prattham:
Yes.

Cheers ?

Sent from my Purified NexusixP

If someone helped you don't just say thanks hit the thanks button
[Nexus 6P Original Android Development] Az Biker:
[MENTION=4684315]flar2[/MENTION] Bumping this in case it was missed
[Nexus 6P Original Android Development] Prattham:
Quick question

In the ex app under wakelock

It says disabled

What does it mean? I mean is the wakelock disabled or blocking wakelock is disabled

And wakelock should be disabled right?

Really confused here

I want to ask i want to stop the wakelock i dont want them

So i have to disable or enable?

Cheers ?
[Nexus 6P Original Android Development] Badger50:
Yes, disabled is your setting if you want to block the wakelock.
[Nexus 6P Original Android Development] Az Biker:
I'm running PN, EX 1.10, Vomertweaks 'dynamic mode' and greenify. Of course there are MANY variables in batt life, and this is about what I average with my normal use. People who game and stream a lot won't get as much life as people who listen to music and text a lot. Object is to find the best batt life for the way you run your device. After all, who wants to get 8 hrs SOT by using only 20% of your devices potential?
[Nexus 6P Original Android Development] revolt1:
on 3.0 I was having a issue with video play back after I recorded? any one else with this issue
[Nexus 6P Original Android Development] drawde40599:
You should flash the stock system.img also to make sure your 100% . Some kernels Modify more than just there boot.img
[Nexus 6P Original Android Development] KonoeKyon:
Use 1.15 if you are on marshmallow. It's an issue with the N kernel updates to the camera not working on M.
[Nexus 6P Original Android Development] jerrylzy:
Hi flar2! Long time no see. Just wanna point out that ARMv8 has builtin AES instructions to accelerate Google's full disk encryption. There's really not much of a difference in terms of speed with encryption, so I would suggest to force encryption to protect data security.
[Nexus 6P Original Android Development] funcrusher:
Please don't do what that guy^ suggests. Those that want that security have it.

:) :)
[Nexus 6P Original Android Development] artpena2323:
I know it's not probably best thing to do. But anyway to keep high brightness mode all the time. It turns off of course when u lock device. Thanks

---------- Post added at 01:38 AM ---------- Previous post was at 01:37 AM ----------

Doh. Wrong forum. Sorry

---------- Post added at 01:39 AM ---------- Previous post was at 01:38 AM ----------

Ugh. This is the right one. Any help would be appreciated
[Nexus 6P Original Android Development] nathanchance:
Use the High Brightness Mode widget, it persists across screen locks.
[Nexus 6P Original Android Development] artpena2323:
Thank You. I'll try it. Do I disable it in EX manager and only use widget. Or leave enabled and use widget. Thanks
[Nexus 6P Original Android Development] nathanchance:
Disabled in EXKM and leave it up to the widget.
[Nexus 6P Original Android Development] artpena2323:
Perfect. I'll try it. Thanks alot
[Nexus 6P Original Android Development] relevant_placeholder:
Why not double tap to full brightness option? [MENTION=4684315]flar2[/MENTION]
[Nexus 6P Original Android Development] MoistPicklez:
Just bought EXKM to show my support, and wow, just amazed by how awesome my battery life is after a bit of tweaking! Amazing [MENTION=4684315]flar2[/MENTION]! Thanks very much mang!
[Nexus 6P Original Android Development] Az Biker:
Once you adjust to the batt savings of EX, try including Vomertweaks "Dynamic Mode" :D
[Nexus 6P Original Android Development] MoistPicklez:
Thanks bro! I have heard of Vomertweaks, but never actually tried it. Does it have it's own thread for the 6P?

Edit: NVM found it, gonna buy it!
[Nexus 6P Original Android Development] Az Biker:
It's as easy as install, select DYNAMIC MODE, and enjoy the extra 30+ min batt life :)

All your EX Manager settings will remain in effect, except CPU/governor settings, when using VT.
[Nexus 6P Original Android Development] Prattham:
Okay what if i use w governor profile snd use vomertweaks? Will it mess with each other or vt will over write it?

Can i even use that?

What are your settings? I mean everything like cpu clocks peed for both clusters io scheduler read ahead tcp algorithm? Which governor?

It will be nice if you can share

Cheers ?
[Nexus 6P Original Android Development] akhi24nick:
Just flashed N developer preview.

Whats the order of flashing kernel and su zip?

elementalx first and su 2.70zip later?

or is it reverse? and we can flash the cf auto root zip in chainfire thread right? for root?
[Nexus 6P Original Android Development] nathanchance:
I would do SuperSU then ElementalX.
[Nexus 6P Original Android Development] Az Biker:
With EX 1.15, I only changed the colors, read ahead to 1024, and Sweep up to wake, everything else remains default...

I don't mess with i/o, govs, tcp, abc 123... I leave that to the pros [MENTION=4684315]flar2[/MENTION] and [MENTION=1363323]vomer[/MENTION] :p

On Vomertweaks, I only select DYNAMIC MODE.

Yesterday I was at 44% with 4hr sot, and 20 hrs 56 min unplugged...

That's way more than enough batt life for my normal day, but with EX kernel getting better, and effective tweaks like VT, I can't help but be curious how much life I can get with my use on my device, just for curiosity sake :D
[Nexus 6P Original Android Development] iron maiden:
Hello as I said buy vomer vomer tweaks but will not update the application or have new profiles? thank you very much

Thanks [MENTION=298610]Flar[/MENTION] for kernel Elemental
[Nexus 6P Original Android Development] clambert11:
[MENTION=4670411]az_biker[/MENTION] What does the read ahead to 1024 do for you? I haven't seen a lot of talk about that in here.
[Nexus 6P Original Android Development] keej:
I too am curious if/when security patches like this are applied to ElementalX. Will they just automatically be included on your next release? This is for CVE-2015-1805.
[Nexus 6P Original Android Development] d08speed3:
Can I still use the Gov. Scripts along with Vomertweaks? Just brought the app and set dynamic mode.
[Nexus 6P Original Android Development] ChrisJ951:
Is F2FS supported? (I searched and found two posts in the thread asking but no response)
[Nexus 6P Original Android Development] Az Biker:
Well, this isn't a scientific answer, but imagine a snow plow only 20 feet in front of your car, you couldn't go very fast if you suddenly needed to. Now imagine a snow plow 200 feet in front of you; you'd have plenty of room to suddenly speed up for a short burst :D

THAT, is as technical as I get, sorry :p
[Nexus 6P Original Android Development] TechMillz93:
I think so, im rocking vomer with ghost pepper
[Nexus 6P Original Android Development] chris9000:
Any idea why my alarm clock apps don't seem to work? Phone alarm hasn't gone off for the past 2 days. Google's own clock app and Sleep Cycle are failing to activate until I turn on the screen. Added both to doze exceptions under Greenify and Android's Doze battery optimization settings.
[Nexus 6P Original Android Development] c_86:
No issues here at all. Wipe and clean install.