wasdennnoch / AndroidN-ify

[Discontinued] An Xposed module to use features introduced in Android N on your LP+ Device
265 stars 93 forks source link

Question: What to do when Xposed doesn't read N-Ify settings? #1167

Closed jahirfiquitiva closed 7 years ago

jahirfiquitiva commented 7 years ago

Description

I would like to know what else can one do to make Xposed read this module settings. I already tried rebooting, reinstalling the app, deleting cache/data, and I made sure SELinux was set to Permissive. The problem still persists.

What I can't understand is how other modules can work without this "restriction".

Also, I would like to know what else can one do to make this work properly, besides those things. I mean, there must be something one could do, or not?

Please help me. Thanks in advance.

Module version (build version) Build 757

Freewander10 commented 7 years ago

I made a post here about the order of installation. Seems to have helped a few persons. You can check it out and see if it works for you too.

licaon-kter commented 7 years ago

I'm seeing a lot off boot loops when upgrading N-ify...

But on point, what I do:

Freewander10 commented 7 years ago

No. Those aren't the correct permission. Change them to 664 or 777.

licaon-kter commented 7 years ago

Why would you give eXecutable rights!?

jahirfiquitiva commented 7 years ago

@Freewander10 Thanks it worked. Followed the installation steps and changed permissions to 777. After some reboots and trial-error, I had it working.

Btw, I still think developers should do something about this, because other modules work fine.

Freewander10 commented 7 years ago

@licaon-kter because it probably won't work if you don't. I can't specifically say why it requires it though. But if you want to get it working without changing permissions. Check out the link I posted earlier to the post on xda. And follow those instructions.

@jahirfiquitiva no problem bro. And MrWasdennnoch is already working on that.

wasdennnoch commented 7 years ago

The snapshots should already set the permissions to 0664, but apparently that doesn't work right yet.