yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] magnamentis:
wakelock detector works fine here, on nexus 5 & Nexus 6, cataclysm, elementalX + Xposed hence it's obviously something in your setup, the issues as well as the non-working WLD. i do not install WLD as system app, it's not necessary, getting all the stats as expected. only thing that comes to my mind

considering the information you provided is whether you're on permissive or enforcing SELinux. i'm always permissive which is why 80% of the issues reported here never cross my path, which is why i choose always permissive, not time to permanently troubleshoot :)

not a stupid question at all :) a very good way to find out whether it's in system or in user space :good:
[Nexus 5 Original Android Development] edrickmph:
Yes i am on enforcing mode. Do i need to be in permissive to have this lag and freezes gone? And how can i do this with EX?
[Nexus 5 Original Android Development] pagratios:
The last 3-4 days my N5 does reboots without a reason that I can understand. After reboot goes to lockscreen without asking for PIN. I have attach the zip from SysLog after last reboot.

I am usig Cataclysm 6.0.0_r2 and ElementalX 6.06
[Nexus 5 Original Android Development] magnamentis:
sorry i forgot to mention ( corrected ) not only nexus 6 but nexus 5 as well, same setup ( identical except wallpaper LOL )

i dunno, you have to try it out. in EX you either need the aroma variant and uncheck SELinux enforcing or you can download SELinuxMode Changer which i do both to make sure i'm always permissive. as said you have to try it out, can't tell blindly if that will solve your issue, this things can be very tricky. follow the following procedure if you cannot make it work otherwise, but follow the procedure to the letter, else it's a waste of time, no shortcuts and no step left out, even though they appear unimportant on first glance:

http://xdaforums.com/showpost.php?p=62192068&postcount=4059

---------- Post added at 11:27 AM ---------- Previous post was at 11:23 AM ----------

not sure if that was you but someone had the same problem yesterday, did you check your powerbutton ? reason reboot first of all would mean that someone/something triggered the reboot command which can happen on N5s with defective power buttons. if it was you, be so kind and reply this time so that we can exclude the possibility and i do not give the same answer several times.
[Nexus 5 Original Android Development] pagratios:
Yes I was me at cataclysm thread. Although I answered and there (http://xdaforums.com/showpost.php?p=64246528&postcount=27025) with a log from SysLog and my question for the defective power button is that if it is button problem why do not ask for PIN? Also the reboot start from google animation not Google logo with unlocked locker
[Nexus 5 Original Android Development] grep_i:
Can you tell since when you are using cataclysm 6.0.0_r2 and also check just to be sure if the problem is not with your power button. I had this problem once and fiddling with the power button fixed it for me. Also can you tell more about the used software on your phone like Supersu or other root and things like xposed and extra modules

---------- Post added at 11:02 AM ---------- Previous post was at 10:57 AM ----------

I am in enforcing mode also and have no problems whatsoever.

You can always try that suggestion but because it works for me in the same mode I'm not sure if that is the problem. The only known difference between your and my setup is the used rom.
[Nexus 5 Original Android Development] #sharath:
I had the same problem as you on the November build, i was also using Xposed. When the December build came i dirty flashed it (which removed Xposed),wiped the cache and dalvik. Now the issue is fixed, i think Xposed is the culprit i'm not sure. You can try what i did.
[Nexus 5 Original Android Development] magnamentis:
ok thanks, that would be a fast reboot which means it's not kernel but rom/userspace caused or as i said triggered by something. so you think it's not the powerbuttten which makes sense if it's a fast reboot because that feature is not in the power off menu of cataclysm. unfortunately that leaves me clueless, try the procedure i linked you to because that's the way to either find out what is the culprit, solve it or both.

that works one hundred percent if the reason is not in system, kernel or hardware. it's the proper way to troubleshoot unaccounted for weird issues.
[Nexus 5 Original Android Development] pagratios:
I have uninstalled xposed wiped cache and install it again. Same :(

I cannot find the procedure that you linked.
[Nexus 5 Original Android Development] edrickmph:
Upon uninstalling pushbullet and installing greenify, my phone is back to normal! No more lags and freezes. I dont know why it is like this, Weird?
[Nexus 5 Original Android Development] grep_i:
You can flash xposed uninstaller or start by disabling all modules and enable them one by one to see which one is giving the problems
[Nexus 5 Original Android Development] pagratios:
I uninstalled xposed, wiped cache. Now wait...
[Nexus 5 Original Android Development] magnamentis:
one page page is the link, here it is again: http://xdaforums.com/showpost.php?p=62192068&postcount=4059

hope it was a one time lapsus because i thinks if we communicate we should at least read the replies carefully :) ;)
[Nexus 5 Original Android Development] pagratios:
After uninstalling the xposed the phone haven't been rebooted. Next step to find which module has the problem
[Nexus 5 Original Android Development] sharon1122:
I'm using elementalx on 6.0 stock rom and viper4android wont work for me

Before i insalled the rom i just had to go on "selinux mode changer" app and change it to permissive but when i do it now it just go back to enforcing

What should I do?
[Nexus 5 Original Android Development] grep_i:
This thread is about kernel ElementalX and your question is not about this kernel.

Can you search for another thread where they might help you.

---------- Post added at 10:06 AM ---------- Previous post was at 09:56 AM ----------

You are doing it wrong pal if you want to disable Xposed modules you need to have Xposed installed.

Disable a module is something you do from within Xposed installed app.

So right step is disable all Xposed modules which will be difficult to do because your phone does not boot up if I understand you correctly.

Maybe you should not mess with custom rom and just stick to stock rom and see if that solves your problem or wait till a newer version of your rom.

Also I need to ask you to direct your question to another thread because your question is not about the kernel.
[Nexus 5 Original Android Development] dechronic:
I am gllad you solved your problem. You may not need this but you may find it useful in the future. CPU Usage & Process Viewer
[Nexus 5 Original Android Development] sharon1122:
My questions is about the kernel because the kernel is the reason the app won't work

And also i asked how i can change the kernel mode to premissive
[Nexus 5 Original Android Development] magnamentis:
if you uninstall xposed framework entirely and the uninstall the modules which after all are apps which only work with the framework, those apps are as good as or even better deactivated because they are simply not present. not present (installed apps ) are for sure de-activated, thus far your post was mentioning a problem that does not exist hence was wrong and makes things sound much more complicated and dangerous than they really are. in the wake of such posts there will be confusion amongst unexperienced users which we shall have to deal with. not useful though.
[Nexus 5 Original Android Development] grep_i:
So if you install stock kernel everything is OK

---------- Post added at 01:45 PM ---------- Previous post was at 01:42 PM ----------

I do understand what you are trying to say, but I think the confusion is not coming from me.

If my answer is confusing than I guess the question is confusing as well.

I have a mantra and that is be specific.
[Nexus 5 Original Android Development] uttam.ace:
Hi, I am using MM6.0.1+CataclysmMod+CatElementalX6.07, I have enabled D2TW, now I want to disable D2TW permanently, is their any way I mean without changing to stock kernal.

Thanks
[Nexus 5 Original Android Development] blanco2701:
Just flash over the elemental x kernel zip (not the express zip) and uncheck that option. Or, if you have ex kernel manager app (worth it 1000%), use it to turn it off.
[Nexus 5 Original Android Development] magnamentis:
the problem with saying (not trying to, but saying) and explaining things nicely seems to be that people feel the urge to defend themselves instead of admitting the obvious brake loose further, mostly off topic discussions. whatever you say. the question was legit and your reply was unnecessary and false. he uninstalled xposed hence his modules are inactive, full stop, nothing to add. the purpose here is not to proof that we have something to say or know things better but to share useful information. using words like mantra as well don't change any facts, even though they are often used to make things sound educated. this should be the end to it i hope else there would be one more name on my ignore list, easy as that.
[Nexus 5 Original Android Development] flar2:
Uncheck enforcing when you install elementalx
[Nexus 5 Original Android Development] magnamentis:
look at things like this: if you boot your device, SELinux changer app will change to permissive quite early right after the SystemUI started while kernel settings usually are applied a tick later. SELiunux Mode Changer is one of the first apps that kicks in, i have it on all my devices and can see when the notification comes on and the all rest gets activated one by one. so if you let the SELinux box checked in Aroma Installer of the kernel, the kernel settings once the get applied will change your SELinux back to enforcing, while if you're using a kernel without that feature it would stick.

the rest was already stated, uncheck SELinux Enforcing checkbox in Aroma Intaller of the Kernel which means to simply re-flash the kernel again to get access to aroma installer.
[Nexus 5 Original Android Development] uttam.ace:
Thanks it worked.

---------- Post added at 08:15 PM ---------- Previous post was at 08:14 PM ----------

Thanks it worked.
[Nexus 5 Original Android Development] grep_i:
Everything you are trying to say reflects on you, so put me on your ignore list see if I care.

I was just literally answering the question.

There was nothing false about my answer, it might be in your eyes but still you are only one person.
[Nexus 5 Original Android Development] :
No. This has been answered.
[Nexus 5 Original Android Development] magnamentis:
you can't use SSU 2.52 with 6.07 which is for systemless root 2.6x only. if you need to run conventional root for good reason like incompatible apps then you have to use EX 6.06 which is the config i'm running to make sure that all my root apps including those with hard coded paths to root are running properly. this should be solved with 6.62 but then i prefer to wait until this is out of WIP status. i have no time to fiddle and since i'm only using apps and features i need i cannot have some of them not working properly.

in case that you don't have such apps or prefer to be on latest, there is no problem with EX6.07 and SSU 6.62. i had it up and running and except select apps as mentioned all was running well, including xposed.
[Nexus 5 Original Android Development] RusherDude:
Sorry, it's hard to find an answer for 2.52 when all the talking about supersu lately is for systemless :(, but thank you!

Thanks for the reply, but isn't 6.06 for Android 6.0 only? Didn't it gave out problems for Android 6.0.1?
[Nexus 5 Original Android Development] magnamentis:
read my post again i added a few things ( edited it ) while you were replying to it, sorry. the answer is no, 6.06 & 2.52 is running flawlessly on with 6.0.1, for me even better than the newer combo did. only thing is that you either need a kernel that has a modified boot.img or modifies it on the fly or a modified boot.img to flash over, but that was already like that before as far as i remember. hence if you flash 6.0.1 and the appropriate kernel with SSU 2.52 it works as well as 6.0.0 did.
[Nexus 5 Original Android Development] RusherDude:
It didn't work either, I reflashed stock system, kernel and cache partitions from 6.0.1, then flashed supersu 2.52 and afer that ElementalX 6.06, and I'm getting the same problem (same daemon su problems I shown before on the pasted log) on logcat.. What did you do to be able to run those two? maybe flash them on the inverse order or something?

EDIT: Do you mean that you flashed chainfires modified boot images over stock before flashing ElementalX 6.06? Chanfire posted boot images for using root on 6.0 yea but for me on 6.0 it wasn't needed to use those images since ElementalX 6.05 would work directly over stock rooted. Isn't is the case anymore?

At the end, I ended up using ElementalX 6.07 with SuperSU 2.62 even if I don't want systemless root (at the first problem im rollbacking totally to 6.0 with system root and ElementalX 6.06). What a mess with this supersu change story.

[MENTION=4684315]flar2[/MENTION], couldn't you make ElementaX compatible with both Android 6.0.1 and SuperSU 2.52? I mean doing the same you did on version 6.05 so it worked on 6.0. :(

-

Btw, since 6.0.1 permits double power button to open camera, and N5 button is ****, it would be awesome if the "direct camera" feature was assignable to DT2W or Swipe to wake, like double touch opened the camera directly, or swipe, or touch + swipe or something. This could be a powerful feature and would save a ton of N5 buttons for us ElementalX users :D
[Nexus 5 Original Android Development] TJKV:
Just FYI, the SuperSU 2.62-3 on MM 6.0.1 on my hammerhead with ElementalX 6.07 works just fine with Secure Settings and such apps with hardcoded paths to the su binary in /system. So one can also be on the latest SuperSU and ElementalX ;)
[Nexus 5 Original Android Development] flar2:
I already added the camera gesture to 5X and 6P.

As for root, if the rom is already rooted, just flash EX. It is compatible with SuperSU 2.52 on ROMs that are already rooted.

If you are not already rooted, then you'll need SuperSU 2.62 because I don't have the patched sepolicy needed for the older root.
[Nexus 5 Original Android Development] RusherDude:
But there is any change in 6.0.1 about that sepolicy? because I used 2.52 with elementalx 6.05 on 6.0 and had 0 problems.. what changed for 2.52 to not be supported now?

About the camera gesture, why only 5X and 6P :P? N5 and others nexuses now have the double power button gesture for camera too on 6.0.1, could you implement it for us too?

Thank you!

---------- Post added at 05:20 AM ---------- Previous post was at 05:18 AM ----------

For now im using the normal 2.62 and I havent found any of my root apps not working so im fine, thanks!
[Nexus 5 Original Android Development] bluenote73:
I'm about to root/xposed/ex my N5 just updated to 6.01, so it seems like I should be using N5-6.07 and systemless 2.62. Unfortunately the systemless is a little confusing to me, so I'm a little apprehensive.

My main question is - what is the proper order to apply xposed, EX and supersu systemless?

thanks
[Nexus 5 Original Android Development] flar2:
There s nothing complicated

If you're not already rooted, flash SuperSU, then EX.

If already rooted, simply flash EX.
[Nexus 5 Original Android Development] bluenote73:
Thanks, and then xposed?
[Nexus 5 Original Android Development] grep_i:
If you need it yes
[Nexus 5 Original Android Development] magnamentis:
once having played around and getting into a state where things don't make sense anymore i usually flash google's factory image, boot to wizard, boot back into recovery, go back to latest perfectly working nandroid and apply all that i've learned lately and bingo.

lately i was not even able to flash a working nandroid backup even though i formatted everything but sdcard manually + factory reset and all. then i flashed factory image and the very same nandroid that did not boot before did work again. what i'm saying ist that obviously every recovery based wipe and format task still leaves residues and the only way to start from zero is to flash google's factory image to get rid of those, get IMEIs back and the likes.

if you revert to your latest 6.0.0. nandroid and install 6.0.1 normally like before, rom+kernel+supersu 2.52 all will work like it always did, nothing special to consider. as to the modified boot.img, if you flash EX that's not necessary because EX modifies the exsiting boot.img while if you plan to go with stock kernel you'd need the modified boot.img that has been posted.

---------- Post added at 01:20 PM ---------- Previous post was at 01:15 PM ----------

thanks, was aware of that but still good to post this more often so that it sticks :) i'll probably change to systemless upon next google update because the solution chainfire chose for not ( he says hopefully temporary ) is to write a symlink to system hence it's not systemless anymore whent it comes to certain requirements. further i have 6.0.1 up and running in a perfect manner now and don't see any reason to spend hours to update all my nexii. there still is that saying: if it aint broken don't fix it LOL. thanks again for the useful input, very much appreciated.;)

---------- Post added at 01:23 PM ---------- Previous post was at 01:20 PM ----------

as mentioned earlier by myself and later by someone else the lates supersu 2.62 fixes that but it's not a real fix, it's a workaround by chainfire, he writes now a symlink into system hence it's not really systemless. however main thing is that it's working now and since this is WIP we can expect improvements in the near future still :)
[Nexus 5 Original Android Development] RusherDude:
Well, usually a backup fixes completely the situation unless you have some data corrupting both the old and new system :laugh:, or at least I've seen such situations. But I wasn't talking about that. I was saying that I didn't make it to work SuperSU 2.52 with ElementalX 6.06 on 6.0.1, even after flashing all the stock partitions :(

Yeah, but if it works, its good :)
[Nexus 5 Original Android Development] magnamentis:
do you remember if you had unchecked SELinux enforcing to make it permissive, else nothing comes to my mind other that i always flash 2.52 last, after the kernel. weird an on one hand it would be interesting to find out what went wrong, on the other hand since you've got things running now that will most probably not be worth the effort anymore :) glad things are working for you now, everything else is secondary :) :good:
[Nexus 5 Original Android Development] ajeesh vijayan:
trusted face and ex kernel

until lollipop everything was fine..

trusted face works on cataclysm stock ..

but when flashing ex kernel trusted face stops after deep sleep.. face is not recognizing and when I tried improve face match camera not starting.. on stock kernel it works fine..

sorry for my English..
[Nexus 5 Original Android Development] Eduardo C.:
I'm with latest Cataclysm and Elemental X 6.07. I didn't uncheck "selinux enforcing" on Elemental X installation and everything is running fine... is it mandatory?

Thx
[Nexus 5 Original Android Development] Joy Bangla:
No not mandatory if everything running fine. Some stuff needs selinux permissive to work.
[Nexus 5 Original Android Development] magnamentis:
no it's not, else there would be no choice ;) there are few apps ( less and less ) that don't like SELinux enforced but within a few months this will either be settled or replacement apps will be available. i'm on permissive at all times because i don't need special security and then just am not in the mood to check upon each problem whether SELinux makes a difference or not. Permissive always works and enforcing mostly works nowadays.
[Nexus 5 Original Android Development] grep_i:
Eduardo it is not mandatory but it is advised to leave SElinux enforcing on at all times it is extra security on your mobile OS that can also prevent viruses from working. It is not antivirus or replacement rather an addition.

Disabling SElinux or set it to permissive must be a last resort to see if that is the reason why a specific app is not working other than that leave it on.

---------- Post added at 10:56 AM ---------- Previous post was at 10:52 AM ----------

Maybe you can give us more information like phone brand, type, model. All software versions like

Rom version

Ex Kernel version

Android version

Supersu or other root version, etc.
[Nexus 5 Original Android Development] ajeesh vijayan:
cataclysm 6.0.1

ex 6.07

super su 2.61

is it working on your rom with ex consistently? can you check?

thanks
[Nexus 5 Original Android Development] haseoxth:
Stock 6.0.1 with latest EX and SuperSU installed, trusted face works well here. It seems your issue has nothing to do with EX kernel.

By the way on my device with google app beta version installed for the past days I always had a force stop when trying to use trusted face but after install 5.7.14.19 stable version today everything works well again.
[Nexus 5 Original Android Development] grep_i:
I would check that but can you point me in the right direction which app you are talking about exactly. I can not find an app called trusted face
[Nexus 5 Original Android Development] Balino:
I think he is talking about the Trusted Face feature in smart lock option.
[Nexus 5 Original Android Development] ajeesh vijayan:
I think it's ex..

because on stock cataclysm kernel with same setup everything works fine..

after flashing ex and about 30 mins of sleep trusted face won't work.. when selecting front camera , camera error pop up

on stock kernel no issue

sorry for my English

thank you
[Nexus 5 Original Android Development] grep_i:
In my first test I could configure it but it never unlocks my phone.

Tomorrow I will try it more thoroughly and I will give you my definitive answer
[Nexus 5 Original Android Development] ajeesh vijayan:
thank you
[Nexus 5 Original Android Development] jordi_e:
Hello peeps,

Does it work great alongside chroma latest version

Thanks
[Nexus 5 Original Android Development] lovendsuicide:
Yes, just go ahead and flash.
[Nexus 5 Original Android Development] grep_i:
After some more thorough testing in daylight and such. The conclusion stays the same it is configuring well but does never unlock my phone.

Tested voice recognition also, it works well with Google search but it does not really unlock the phone.

It starts the Google search app but the phone status is still locked
[Nexus 5 Original Android Development] sandrosdj:
After setting sound settings to the values you can see on the screenshots, it resets after changing track/music player app.

Any ideas?
[Nexus 5 Original Android Development] creeve4:
Use FauxSound.
[MENTION=3332811]faux123[/MENTION] seems to have coded his sound control in such a way that only his app can prevent the settings from changing. I've tried multiple methods, but nothing worked.
[Nexus 5 Original Android Development] flar2:
EXKM also works, lock the settings after you change them
[Nexus 5 Original Android Development] chazall1:
I have been running your kernel for a while as my go too. Franco kernel updater has the ability to show my current temp in the notification panel. Can you incorporate the same temp feature in your kernel or Kernel Manager? One less app to have.

Thanks for your great work.
[Nexus 5 Original Android Development] flar2:
Already in EX Kernel Manager. Got o settings and you will find the option
[Nexus 5 Original Android Development] Hatshipuh:
Got several random reboots over the past few days ever since on ROMs with updated binaries.

Not sure if it really started since then, but the random reboots come quite often, coupled with very slow charging, even losing battery when using the phone on charger.

Last_kmsg from last reboot attached, but every reboot log has the same error.
[Nexus 5 Original Android Development] flar2:
No kernel errors
[Nexus 5 Original Android Development] chazall1:
Thanks I will DL EX Manager.