yashsingh1/xdaforums huggingface dataset:
[Xposed General] FaySmash:
The issue you facing is because the new (unofficial) xposed installer has a different file were the activated modules are written in. So if a module checks if it's on the list, it doesn't find it on the old location (like unicon) and quits.
[Xposed General] StolidSentinel:
Look back at the comments from 6 months ago when people thought XPosed for Nougat would never happen.. THAT'S drama! :D Wanna trade phones?? No?? So you DO see my point!
[Xposed General] lahceneamine:
It seems to be with the new version :

/data/data/de.robv.android.xposed.installer/shared_prefs/enabled_modules.xml

Instead of :

/data/data/de.robv.android.xposed.installer/conf/enabled_modules.list

I'm gonna try to do a bind / simlink and see what happens.
[Xposed General] demonoidmaster:
You do realize you can't do that if you CAN'T boot at all. Did you even read anything i said? (If an xposed module bootloops your device, the only way to make it boot with all modules disabled is to delete the file of enabled xposed modules, then boot, tick back those that work and reboot)

I don't understand why you want some overly complicated magical way of flipping a switch to disable a xposed module or magisk or xposed itself when your device just won't boot, when xposed is disabled (be it through the app or via magisk) you can't disable it's xposed modules, someone already pointed that out, disabling magisk won't help you either

Only other way that you can disable xposed is by doing vol + vol - as your device turns on but like some guy said you can't disable xposed modules when xposed is turned off.

Just do what everyone has always done ok? Delete the enabled modules file from the xposed data folder and reboot to android and go on from there...

---------- Post added at 02:45 PM ---------- Previous post was at 02:27 PM ----------

I'm really getting tired or your f'ing use of those belittling emoji's that indicate you're calling me stupid
[Xposed General] Gggggas:
[MENTION=7086291]demonoidmaster[/MENTION]

Can't the modules be disabled even with this zip?

https://is.gd/N15j5h
[Xposed General] demonoidmaster:
The reason why you can't even disable xposed modules is because you're disabling xposed when xposed isn't even the problem, faulty xposed modules have nothing to do with xposed. Instead of disabling xposed through magisk use the xposed manager to do that, there's a disable switch in there for a reason, turning off the magisk module turns off the module and that's it, nothing more. Turning off xposed through the xposed manager app, that's different, but then again none of this matters because if you have a faulty xposed module and can't boot then there's NO other way but simply deleting the one file that tells xposed "hey, these are activated, boot them up ok" vs disabling xposed
[Xposed General] demonoidmaster:
This literally does the exact same thing as i was talking about but in zip form so

[MENTION=5673532]manos78[/MENTION]

There you go, a zip file to flash through twrp (since doing it manually is too much work for you) to disable all xposed modules incl. the faulty one if you ever can't boot. All you'd have to do then is reenable the modules that work + reboot, ?
[Xposed General] manos78:
Sorry!

I appreciate your comments!

My objective is explain a different way to use the Xposed Framework when using it with Magisk.

Please, you use Xposed SYSTEM or SYSTEMLESS?

This is not possible with a bootloop!

And when you can't boot, then you boot to the TWRP and

disable the MAGISK not the XPOSED!

This is the different between you and me!

Then explain why the Xposed Installer let the user enable/disable modules with the Framework disabled and not when it doesn't detects the Framework.

The Installer is now checking the file "disabled". But it only does for SYSTEM installation, and not for Magisk Installation. This the different and the point that I want to point.

I repeat. This assumption is false... In my way I boot to TWRP and I disable MAGISK. After that you can boot. And then my objective is use the Xposed Installer to disable the faulty module. At time, I can only do it with a very tricky hack: create the "disabled" file and open the Installer... only with this the UI leaves the option for enable/disable modules.[/QUOTE]

I explain it: The reason is because I like to use STOCK Roms and upgrade using OTAs. So for this the only way (at time) is a SYSTEMLESS rooting & Xposed. This can be done using Magisk. So in my opinion the Magisk way is the future. And for this I recommend to fully support it in the Xposed Installer. It needs to support the two variants: SYSTEM and SYSTEMLESS. At time, it only support the SYSTEM version.
[Xposed General] demonoidmaster:
There's no reason to disable magisk or xposed when an xposed module is faulty. Plain and simple, someone even attached a zip that you can flash that basically does what i said before, why do you want to overcomplicate things, nobody cares if you can't disable xposed modules whenever magisk is disabled or xposed is disabled, the only thing that makes them xposed modules enabled is a file, you don't need to disable magisk, you don't need to disable xposed, how hard is that to comprehend?

---------- Post added at 03:57 PM ---------- Previous post was at 03:51 PM ----------

1. I use xposed as a magisk module.

2. No you don't? Deleting the enabled modules list doesn't magically make your installed modules vanish from your xposed manager list, it simply disables them all, they'll all be there once you open the manager after you boot up
[Xposed General] FaySmash:
symlinking isn't enough. as you see, the new list is a xml file, the old one a text file. you have to write the package name of the apps which doesn't work in the enabled_modules.list I suppose.
[Xposed General] waleeds1:
Non of the closed modules were working after flashing the official exposed for nougat. Everything was fine with the unofficial version. Got it fixed by using the officail installer by rovo89. Anyone else having this issue? If anyone can tell me a fix or confirm that its working, I'd unisntall it and install this installer as I always preferred this.
[Xposed General] Ja_som:
Did you tried this version?

https://xdaforums.com/showpost.php?p=74093833&postcount=2312
[Xposed General] MrWasdennnoch:
Actually Xposed still reads the modules from a modules.list file but with the introduction of a new file encryption system in N the path got changed to

/data/user_de/0/de.robv.android.xposed.installer/conf/modules.list

The shared_prefs are only used by the installer to quickly determine which modules in the list are activated or not, it doesn't get read by Xposed.

The magisk version still tries to read the config file from the old path (which may still be there from the old installer version) instead of the new path, leading to the described behavior of only some modules working (the previously activated ones).
[Xposed General] waleeds1:
I updated the installer from the update prompt in the app, before going for the official nougat installation
[Xposed General] lahceneamine:
And there's nothing we can do about it know that the dev is not willing to update his module (unicon) ?
[Xposed General] MrWasdennnoch:
It's not related to the modules themselves but where Xposed searches for the module list to load the modules (unless I'm missing something and that module tries to read it as well).
[Xposed General] manos78:
Thank you!

Now this is the new path: "/data/user_de/0/de.robv.android.xposed.installer/conf/" :good:

---------- Post added at 09:31 AM ---------- Previous post was at 09:19 AM ----------

Hi [MENTION=7086291]demonoidmaster[/MENTION],

This is your opinion. And I respect.

However, my opinion is quite different: If your phone doesn't boot (because a bootloop) you don't really know the cause. So booting in pure Stock disabling Magisk (that disables all extensions) is the most simple and direct solution. Futhermore, to disable it you don't delete anything, only create a "disable" file... so all can be undone.

I have a similar file for touching the disable Magisk file. So it's not overcomplicate.

And [MENTION=3283196]rovo[/MENTION] and [MENTION=5345056]DVDandroid[/MENTION] cares about enable/disable Xposed modules when the framework is disabled. Why then do they include the support in their Installer?

It's really hard to comprehend that my only request is to check not only if the Xposed framework is disabled by the "native" "disabled" file but for the Magisk module "disable" as well?

1. Great! Then try almost one time to disable Magisk with TWRP! :highfive:

2. When you delete this file you lost the list of modules

active

... or you don't have some of your modules deactivated but installed?

In any case: I know your position. And I respect it. However, please let other people to work in a different way. I prefer to disable Magisk and I like to see at some time full support for Xposed as Magisk Module. Nothing more.

Regards.

---------- Post added at 09:52 AM ---------- Previous post was at 09:31 AM ----------

Hi,

If you need a ZIP file for touch the Magisk disabler file (aka "Magisk Disabler") in TWRP, then you can download it from here:

https://www.sendspace.com/file/2dw5a7

Regards!
[Xposed General] demonoidmaster:
It doesn't delete modules, the file is used by xposed, when it finds those it boots any module added to the list in the file, no file = xposed assumes they are not active thus = they will not be loaded on boot
[Xposed General] RSDamasceno:
Error

10-14 23:57:21.356 I/XposedInstaller( 9754): RepoLoader -> Downloaded http://dl.xposed.info/repo/partial/12999.xml.gz with status 2 (error: Downloading http://dl.xposed.info/repo/partial/12999.xml.gz failed: connect timed out), size 0 bytes
[Xposed General] manos78:
Sure! It deletes the

list

of active modules.

So, when you delete this file, and you have, for example 10 installed Xposed modules and 5 active... You need to manually re-activate the list of

active

modules. And which are previously activated? You lost this info when you delete this file. So delete this file isn't the best way for "disable" the Xposed Framework. This is the reason for the "disabled" file... introduced by Rovo; and also included in Magisk (for disable Magisk and individual modules).

Please, stop to comment

your

way for working with Xposed. Other users are using a different way. Your way can be right for you... and our way is right for us.

My request is quite simple: Add support in the Xposed Installer for Xposed as a Magisk module, when the module is disabled. Nothing more.
[Xposed General] bflmpsvz:
The updated installer from 09/10/17 doesn't list updated systemless framework v88.1:

https://xdaforums.com/xposed/unofficial-systemless-xposed-t3388268
[Xposed General] teddy0209:
I'm using the 09/10/17 build test version and it works perfectly fine, at least on systemless version...
[Xposed General] demonoidmaster:
So you delete the file, all modules are set as disabled, why is it then hard to simply enable all modules except the faulty one and reboot? Like seriously, why disable magisk or xposed or whatever other random stuff if what makes your device bootloop is an xposed module

If it would be magisk that would be having issues then yes obviously you'd want to disable it, but everything i said so far had only to do with xposed modules and how this was a good way to fix your device back when Android Lollipop was the most recent OS and Magisk didn't exist yet

However one thing that really would be revolutionary is having say magisk autodisable modules + reboot if it detects that a module is either behaving badly or is suspiciously doing stuff it shouldn't

Same goes with xposed, right now there's two managers, the Material Design one made by the OP and the one made by Rovo, but like with Magisk Manager with the thing i said about that it would be great if Xposed Manager could detect when a module is misbehaving or doing weird stuff and could disable it + reboot device

Substratum already does that with SystemUI themed aspects, anything that makes it crash more than once back-to-back it will disable and let you know that one of them is faulty
[Xposed General] manos78:
Because two reasons:

1) If the device is in bootloop you can't be 100% sure that the problem is one specific Xposed module. Then the best option is disable Magisk and boot in pure stock (100% safe).

2) If you have N installed Xposed modules, and M (where M<N) active modules, then you don't need to remember or backup the list of active modules. If you remove the list of active modules then you definitively lost the list of active modules.

I do in this way because

it's the most simple and efective solution

. Please, check this algorithm:

- If your device doesn't boot...
- Then boot (using keys) in recovery mode (aka TWRP). Then install the ZIP "Magisk disable" and reboot.
- When booted, open Magisk Manager and disable "Code Mode" (this removes the "disable" file of Magisk).
- Check your logs (Magisk & Xposed), and then disable the module/s that creates troubles.
- Reboot.

This is simple, easy and efective!

However, what is the problem? That the Xposed Installer doesn't enables the option to enable/disable modules because the "disable" file for Xposed is not found. However, if the file "disabled" is found it permits to do it even if the framework is not running.

Why not then enable this option also forwhen the Xposed is a Magisk module and the Magisk is disabled?

This is just me request.

---------- Post added at 11:21 AM ---------- Previous post was at 11:16 AM ----------

I agree! It will be a very interesting function.

This thread is for [MENTION=5345056]DVDandroid[/MENTION]'s Material Xposed Installer. This manager blocks the UI for enable/disable modules when the framework is not detected. However, it enables when the "disabled" file is found. My request is to enable it when the Xposed is installed as a Magisk module and Magisk or the module is "disabled".
[Xposed General] demonoidmaster:
1. Well i mean if you update something and your device bootloops, doesn't take a rocket scientist to know it's what you just updated or installed that caused the bootloop

2. Simply removing the file doesn't harm anything, it'll get recreated (but blank until you select modules) and will get modules relisted in it once you select your modules once more and reboot. Also i don't know who has X amounts of modules and keeps only some enabled, makes no sense..If you don't use a module uninstall it, if you do keep it enabled

Normal people don't have 15+ xposed modules installed, that's just overkill
[Xposed General] manos78:
Sure? You know that current Xposed Installers re-order the list of loaded Xposed modules? You know that the order is relevant when two modules (or more) overwrite the same function? You know that some Xposed modules can interference with some Magisk modules? You know that some Apps checks for the presence of some rooting tools and other stuff?

Are you completly sure that you know who is preventing your device to boot without lock in the logs?

1) Some people (like me) disable several xposed modules until they are required. If you uninstall them you lost the configuration. So disable it's preferable over uninstall.

2) Disable Magisk with TWRP and reenable it with Magisk Manager it's simple and fast. I prefer it over your way of "disable Xposed". Why can you accept that other people likes to go in this way?

Thank you for your comments!
[Xposed General] teddy0209:
Lol, I have more than that on my M9... Modules from the LP days... Though I keep outdated modules disabled... I activate those updated for N first, then activate outdated modules one at a time (except those known to be Android version dependent).
[Xposed General] DB126:
What a ridiculous comment. I have well over a dozen modules installed on several devices with various modules disabled until needed. Done for reasons that do not need to be justified here. Please don't project personal preferences on the Android community with a suggestion that a variation from your 'standard' is somehow abnormal.
[Xposed General] SacredDeviL666:
Hello All.....

I thought that i would pop in and drop a message ....

Well we all know that we have different preferences with how we use phones and i hope we don't generalize or label them based on that.

Its a nice thought though but something we should avoid discussing in the forums to prevent back and forth irrelevant responses and you know what :p

Sorry no beer icon... but still BEEERRRRRRR
[Xposed General] Barbiox Dogg:
[MENTION=5345056]DVDandroid[/MENTION] this mod apk is not letting GravityBox for Nougat work. Pls fix it. Thanks for your hard work. Really appreciate.
[Xposed General] Ja_som:
Use the test version, it works fine.
[Xposed General] Poppeye0:
What test version? First post only has stable version??!
[Xposed General] culiacanazo:
I don't know how to link from XDA Labs so just press to find the original post.

:P
[Xposed General] Ibuprophen:
The following is the post from DVDandroid with the test version.

https://xdaforums.com/showpost.php?p=74093833&postcount=2312

Good Luck!

~~~~~~~~~~~~~~~

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Xposed General] culiacanazo:
Lol

Hey, mine works too, doesn't it! :silly:

Can't say i didn't try ?
[Xposed General] Ibuprophen:
I had tried the test version the day after DVDandroid had posted it and, though it worked for the most part, one of the modules crashed the test installer (technically restarted it) after selecting it to open the modules settings/options.

I just began to use the stable version again and all was well.

~~~~~~~~~~~~~~~

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Xposed General] DVDandroid:
Pushed new version

This new version fixes some bug on Android 7.0+.

You probably need to clear app's data if module are not loaded from Xposed

I'm very busy and I cannot work on the app or read this discussion . I'm sorry and if you want to help me sending fixes, the app is open-source here
[Xposed General] shuli81:
Try to update through the app. I'm getting error "there was a problem parsing the package"
[Xposed General] exodius48:
I think there is an error in xposed systemless version, topjohnwu does not release 87.3 SDK25. Xposed 87.3 just for SDK23 or lower.
[Xposed General] hjmodi:
Sorry everyone.

I'm not currently able to respond here because of Exams. And not going to be able to keep up with this thread because of academic reasons. So I'm transferring this thread to [MENTION=5345056]DVDandroid[/MENTION].

So from now on he will be maintaining this thread.
[Xposed General] siren_shadows:
can you just add a download please?
[Xposed General] stevtec86:
hi, i installed the xposed material (last update), i downloade the framework V79 for arm , but at the reboot, my telephone stack on boot.

I'm a Samsung Galaxy S4 GT-I9505 with custom Rom, based on 5.0.1
[Xposed General] FPSUsername:
2 bugs:

Accent color doesn't change

The settings, about and support get colored on tap, but never go back to normal until you restart the app.View attachment 3591040View attachment 3591041
[Xposed General] DVDandroid:
Bug fixed in last update. However you need to grant su access to app

(Please read post 2) you can uninstall xposed from recovery
[Xposed General] Halcyon:
confirmed not working download section
[Xposed General] DVDandroid:
Try to uninstall app from your device and download and install it from first post.
[Xposed General] Ja_som:
Hi [MENTION=5345056]DVDandroid[/MENTION]

when I want to export enabled modules list I get an error, see screenshot... Export installed modules list works...
[Xposed General] drewski_1:
The "New version of Xposed Installer is available!" message doesn't go away, even after updating
[Xposed General] Midomad:
+1

Same here.
[Xposed General] DVDandroid:
try to clean app data and restart, then try again

1) can't change accent color

2) fix in next release

try to clean app data and restart, then try again

i'm looking for a fix

I'm trying to understand what is the problem, however, you can use the device's normal reboot function.
[Xposed General] milojoseph:
The app says it cannot read log.

Sent from my SM-G900T powered by AllianceROM

and boosted by speedy kernel

Lollipop ?
[Xposed General] Midomad:
Confirmed.

Edit:working after a reboot.
[Xposed General] yochananmarqos:
Logging works fine here.
[Xposed General] SuperSandro2000:
If I want to enter settings the app just crashes. I'm am running marshmallow 6.0.1.

Gesendet von meinem SM-G900F mit Tapatalk
[Xposed General] milojoseph:
After reboot still have problems

Sent from my SM-G900T powered by AllianceROM

and boosted by speedy kernel

Lollipop ?
[Xposed General] romracer:
Same here

--------- beginning of crash
12-28 16:18:15.034 15854 15854 E AndroidRuntime: FATAL EXCEPTION: main
12-28 16:18:15.034 15854 15854 E AndroidRuntime: Process: de.robv.android.xposed.installer, PID: 15854
12-28 16:18:15.034 15854 15854 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{de.robv.android.xposed.installer/de.robv.android.xposed.installer.SettingsActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.preference.Preference.setOnPreferenceChangeListener(android.preference.Preference$OnPreferenceChangeListener)' on a null object reference
12-28 16:18:15.034 15854 15854 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2416)
12-28 16:18:15.034 15854 15854 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2476)
12-28 16:18:15.034 15854 15854 E AndroidRuntime: at android.app.ActivityThread.-wrap11(ActivityThread.java)
12-28 16:18:15.034 15854 15854 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1344)
12-28 16:18:15.034 15854 15854 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
12-28 16:18:15.034 15854 15854 E AndroidRuntime: at android.os.Looper.loop(Looper.java:148)
12-28 16:18:15.034 15854 15854 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5417)
12-28 16:18:15.034 15854 15854 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
12-28 16:18:15.034 15854 15854 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
12-28 16:18:15.034 15854 15854 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
12-28 16:18:15.034 15854 15854 E AndroidRuntime: at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:114)
12-28 16:18:15.034 15854 15854 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.preference.Preference.setOnPreferenceChangeListener(android.preference.Preference$OnPreferenceChangeListener)' on a null object reference
12-28 16:18:15.034 15854 15854 E AndroidRuntime: at de.robv.android.xposed.installer.SettingsActivity$SettingsFragment.onCreate(SettingsActivity.java:93)
[Xposed General] Ja_som:
Thanks, also disabling and enabling storage access works :)

Also no issue with log or settings here...
[Xposed General] espaciox99:
If I want to enter settings the app just crashes. I'm am running cm 13 :(
[Xposed General] teddy0209:
John Wu released those version prior to the release of official xposed for N...