Xposed 2.7 Exp. Issues (KK 4.4) - Xposed General

-Running Xposed 2.7 Experimental1 on stock 4.4 rooted Droid Mini
Lately, I've been encountering some issues with Xposed in general.
-When downloading a new module
Anytime I find a new module I want, I download it normally and it downloads/installs no problem. But once it finishes, I don't get a notification to activate it and the module screen still says install. If I go to my modules, it's not there. I have to kill Xposed from recent apps and reopen it to my modules for the one I downloaded to be there, and only then can I activate it, which gives me the toast message to reboot.
-When updating an installed module
Similar to above, whenever I download a module update, it goes through normally, but after install, Xposed still says there's an update for said module, and said module disappears from my modules. Killing Xposed and reopening to my modules afterwards makes it show up, but in order for the module update changes to take effect, I have to disable the module, re-enable it, then reboot my phone.
Anyone have any idea? I've uninstalled and reinstalled the framework but that did nothing.

Related

Xposed installer crashes on opening any module in the download section

Hello!
I have a problem described in the topic.
My device is Samsung GS4 Active running stock 4.4.2 KK, rooted.
Until yesterday I had a working Xposed installer (2.7experimental) with half a dozen modules, namely: Amplify, AppOpsXposed, Lucky patcher, One++, Vk hack and of course Wanam Xposed.
And yesterday I got rid of all the Google stuff. Deleted all Google *** apps, including GP market and GP services. Migrated to 1Mobile Market.
And after that Xposed installer (itself, not the modules) started to crash on doing the following:
1) start Xposed installer, 2) click Download section, 3) click ANY module there including the framework itself.
So I get "Unfortunately, Xposed Installer has stopped".
The error log does NOT have anything about the crashes.
What has been done to avoid this behavior:
- cleared dalvik-cache
- wiped cache partition
- uninstalled an installed back different versions of Xposed installer (2.6.1 & 2.7experimental)
- activated and deactivated all 6 modules installed
Luckily, ALL the modules work perfectly, they have been successfully activated in Xposed installer every time I reinstalled the app.
So my question is: does anyone know what to fix so to make the Installer open the modules in Download section without crashes.
Thank you in advance. Sorry for my English
a.warlamov said:
Hello!
I have a problem described in the topic.
My device is Samsung GS4 Active running stock 4.4.2 KK, rooted.
Until yesterday I had a working Xposed installer (2.7experimental) with half a dozen modules, namely: Amplify, AppOpsXposed, Lucky patcher, One++, Vk hack and of course Wanam Xposed.
And yesterday I got rid of all the Google stuff. Deleted all Google *** apps, including GP market and GP services. Migrated to 1Mobile Market.
And after that Xposed installer (itself, not the modules) started to crash on doing the following:
1) start Xposed installer, 2) click Download section, 3) click ANY module there including the framework itself.
So I get "Unfortunately, Xposed Installer has stopped".
The error log does NOT have anything about the crashes.
What has been done to avoid this behavior:
- cleared dalvik-cache
- wiped cache partition
- uninstalled an installed back different versions of Xposed installer (2.6.1 & 2.7experimental)
- activated and deactivated all 6 modules installed
Luckily, ALL the modules work perfectly, they have been successfully activated in Xposed installer every time I reinstalled the app.
So my question is: does anyone know what to fix so to make the Installer open the modules in Download section without crashes.
Thank you in advance. Sorry for my English
Click to expand...
Click to collapse
Found your old question after having the same problem, with no answer. Later, I realized (from reading xposed installer logs) that the problem was me previously "integrating into ROM" (with Titanium) what is called "Android System Webview" app.. I had problems "undoing" the integration, ended up re-installing it from the Market... but now it works.
So I'm leaving this here: if the installer closes on opening stuff in Modules tab, check your WebView.
Hello friends, I'm running Marshmallow 6.0 on my Oneplus One phone and I need xposed framework... but after flashing it (xposed-v89-sdk23-arm), my phone app stopped working, no access to contacts, favorites... nothing! I tryied even with xposed-v88-sdk23-arm version, but the same.... No phone app access. So, I cannot use my phone with xposed framework flashed on it! Will anybody help me solve this horrible problem, please? Thank you.
almost same question here. My sdk is 22
Running xposed installer after installation makes my phone to soft-reboot
Try force stopping Xposed Installer app, then clear cache and data for app, then restart app and see what happens. Also ask in section for your phone model/ROM if still happening.
Yakimus said:
almost same question here. My sdk is 22
Running xposed installer after installation makes my phone to soft-reboot
Click to expand...
Click to collapse
The posts #3-5 should be in different threads, but i have the same problem as OP, an old device with Android 4.4.2, XI 2.6.1. XI will stop/crash when i try to open any module in the download section.
Also have Titanium backup installed... but i have no app called "Android System Webview". Is it something i should install for Xposed Installer? I never had this problem before but haven't updated for a while, so i'm trying to get some things updated. Thanks
I finally found that the problem was that I had Download Manager disabled. Enabling/(defrosting it with Titanium) has allowed XI to work again!

Xposed 88.1 on Xperia Z3c with Android 7.0

I tried to install Xposed 88.1 on my Xperia Z3 Compact with rooted stock Android 7.0, but ran into a few problems:
1. Modules will not download. If I start a download, it immediately stops itself. I've worked around this by opening the repository source and downloading the APKs directly from the browser page.
2. Modules do not work, even though the framework seems to be installed and active.
When I run the modules, I get messages that say something like "system framework not responding" or "module not active in framework".
The modules in question include BootManager, GravityBox [N], Amplify, etc.
Is this a common problem? Is there a fix currently?

getting not-active xposed lately, was fine a few weeks ago (xposed log attached)

Hi all
I have used xposed for a long time now, but I noticed something strange lately.
My setup:
Oneplus One without Gapps, with Magisk and Xposed, Android 6.0.1 Sultan ROM.
Xposed reports the framework v.87.0 systemless by topjohnwu is installed but not active.
However, my xposed modules (deny location consent, fakegapps, greenify, magnet sensor control, statusbar headset icon) seem to work perfectely.
I already checked, if there is a disabled file, but could not find one.
I already did reboots, disabled xposed&rebooted, enabled xposed&rebooted, reinstalled v87.0 sdk 23 from topjohnwu, but no change.
The yellow sign wont go.
I noticed something strange:
I wanted to update my busybox inside system/xbin, but was not able to remove it, even with root explorer I could not delete the 22 (?) Mb busybox file in system/xbin.
Magisk seems to work fine though.
I then uninstalled all busybox installation apps and installed the busybox module from Magisk.
Could you help me getting proper xposed?
Or is this an error?
xposed log:
https://pastebin.com/XVP0UGim

Problems with modules not activating after module apk reinstall (Nougat 7.0)

I seem to have a problem whereby, when I do
adb install -r <module.apk>
then sometimes Xposed doesn't seem to find that the module has changed. To be sure I have to manually go into the GUI and click and unclick the module checkbox. Sometimes, rarely though, I get a popup detecting the module has been replaced and asks me directly if I want to reboot. Then it works.
Is this a known bug with Xposed for Nougat Android 7 etc.
Solved!
I found out that I most likely rebooted before the
Intent.ACTION_PACKAGE_ADDED intent was intercepted by Xposed Framework (probably)
This Intent most likely contained the path to the apk, which resides in a folder that every other time of a reinstallation changes suffix between "-1" and "-2". This seemed to be causing File not found by Xposed Framework every other (reinstallation) time.
Conclusion:
Don't reboot Xposed before the Intent.ACTION_PACKAGE_ADDED Intent is broadcast by Android!
It is a bit strange however, that I don't always seem to get that Xposed Framework "Do you want to reboot because a module has been updated" Toast however... though it seems to work anyway as long as you wait long enough though. Then, again, if the toast never show, then you won't know how long to wait, and sometimes it can take quite a while actually!

Updated Magisk after being prompted to, now have two installs of it?

Hi, first time posting to XDA and I'll try to be concise, but I am tremendously confused and quite frightful of having to reflash/factory reset my entire device.
I got Magisk 6.1.0(165) after my Xposed Framework became more of a problem than a solution a long time ago, with a basic desire of rooting my device to control what apps boot at launch and examine Wakelocks and run an ad blocker.
For a long time, I did not update after the headache of clearing Safetynet and getting things functional.
Magisk prompted me to update, and I decided to after I had installed a few new apps that I now wanted to block from running on boot, but I never got around to finding a method to prevent apps from loading at startup like I desired with Xposed, i previously just disabled or uninstalled the problematic apps.
Before updating, I used TWRP to run a backup and rebooted.
After the update, Magisk informed me that the latest version i had updated to, was not supported and that it would behave asif it wasn't installed at all... Great...
I downloaded the zip to my device's SD card, and after a reboot noticed that I had Two installs of Magisk. When I held the icon to view app info, one of them would behave as I expected, and the other would show me additional options like modules, downloads, superuser and hide.
When I opened the second copy of Magisk, the first one vanished from my applications tray and cannot be found anymore, and Magisk now shows it's green checkmark next to Latest Version v20.4 and Installed Version 17.1 but Safetynet gives me an API error.
Clicking Update Magisk Manager from the menu offers to install v7.5.1(267) but I am wary enough that I am unsure if I should proceed and am not even sure if Magisk has a module that I am looking for-- Something to control what apps launch on startup.
Will updating Magisk Manager show a new list of additional modules to be downloaded and perhaps something that I am looking for? Should I be worried about bootlooping my device and needing to reset it?
I once used the Boot Manager found on the Xposed Framework, but it's long since become non-functional and became the reason why I simply uninstalled what was bothering me, but now I want to keep the new applications that I have and disable their bootup on start.
Is Magisk the place that I should be looking for such a feature?
Running a Samsung GalaxyS5.

Categories

Resources