Closed jahirfiquitiva closed 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.
I'm seeing a lot off boot loops when upgrading N-ify...
But on point, what I do:
/data/data/tk.wasdennnoch.androidn_ify/shared_files
and for that XML I change permissions from 660 (RW-RW----) to 666 (RW-RW-RW-)No. Those aren't the correct permission. Change them to 664 or 777.
Why would you give eXecutable rights!?
@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.
@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.
The snapshots should already set the permissions to 0664, but apparently that doesn't work right yet.
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