I'm sorry for my poor English..:crying:
This problem has been questioned a lot but I still can't find an answer suitable for me.
I upgraded my LineageOS 14.1 to 15.1 yestdoday with wiping system, cache and dalvik cache, and data not wiped. And install magisk xposed 90.2, but it said 'framework installed but not active'.
I tried reboot (not soft reboot) my phone, then every thing keeps FC.
After a soft reboot, every thing seems to work fine, and Xposed Installer said framework is active. But some modules said 'module not active' while others work perfectly.
Modules not work: QXposed (for QQ), WeXposed (for WeChat), FingerprintPay (for payment apps)
Modules work: Xposed Edge, Android Phone Vibrator, Greenify, InstantFaceUnlock, etc.
Why I got this problem?
In a word, xposed doesn't work after a reboot (via app or power button), but works after a soft reboot. And modules that target for apps (not for system) don't work.
Thx very much!
Related
I'm using Xposed 2.6.1 (libraries used StickyListHeaders & libsuperuser)
All modules are activated, reboot, etc... The modules never get activated with a normal reboot.
If I do a soft reboot, then they all work...
None of them work with a hard reboot.
All modules are last versions... they are installed on internal memory.
I' tried to uninstall and reinstall * reboot for both modules & even Xposed. Same results.
It seems that I'm not the only one having that issue, but have search for real solution without success.
I do have a phone with Android 4.2.2, Kernel 3.4.5 ([email protected] #1 Tue Jan 13 16.55:43 CSST 2015 / Build number ALPS.JB3.MP.V1
Here is attached the Xposed error log file.
Please help, as I'm sure it will help a lot of other users.
Thanks,
Jean-Frederic
Solved !
Ok, got it solved in between... but I'm back here to explain what happened as it can help others.
I thought the modules were moved to internal memory by pressing the appropriate button in the application options, but when I did move it, the modules was still active in Xposed.
So I guess that the move was not done completely or correctly.
So I uninstalled the module (GravityBox[JB]), then re-installed it and moved it to internal memory BEFORE activating it.
Then reboot, then activation in Xposed, then reboot... then Tadada !!!! it works perfectly even with hard reboot.
Hope this help,
Jean-Frederic
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!
Hi
I have a banking app that works great once Magisk is running, however as soon as I reboot the banking app runs at boot (I assume before Magisk does its hiding) and detects root/magisk and some functions stop working.
I can wipe data and start again and everything is fine until the next reboot, so the hide works, just not fast enough during boot
Is there any way to stop apps booting at start like bootmanger does - https://play.google.com/store/apps/details?id=de.defim.apk.bootmanager&hl=en
I'm running Lineage OS 14.1 so have 7.1.1 so no xposed aptions currently....
You can go to Memory in settings. There is "Apps at boot" or something like that (my phones language isn't set to English, so I don't know the exact name). But there you could prevent apps to start at boot.
Worked perfectly, and managed to clean up a few others as well!
Thanks so much
a module ?
Xposed rootless for example, at each Snapchat logon i have to deactivate/activate it, and each deactivation it's a full dalvik remake (1h).
And the switch toggle of Xposed doesn't work for SafetyNET or SnapChat, so the module have to be deactivated
It's impossible and too long !
So i don't use XPosed and don't make Update of module !
pingopower said:
a module ?
Xposed rootless for example, at each Snapchat logon i have to deactivate/activate it, and each deactivation it's a full dalvik remake (1h).
And the switch toggle of Xposed doesn't work for SafetyNET or SnapChat, so the module have to be deactivated
It's impossible and too long !
So i don't use XPosed and don't make Update of module !
Click to expand...
Click to collapse
Easy, everything has to be optimized for Xposed. But... I don't have long boot time on my device. Activate and deactivate Xposed in magisk is very quick for me. Normal boot time for both. Moto e4 on nougat 7.1.1. so it may be something specific to your device or Android version. Your device may just be very slow optimizing. Do you have a ton of apps installed? Because that makes optimization even longer. It is a very resource intensive operation.
No other modules should have that besides Xposed. Like I said, Xposed MUST optimize EVERYTHING.
pingopower said:
a module ?
Xposed rootless for example, at each Snapchat logon i have to deactivate/activate it, and each deactivation it's a full dalvik remake (1h).
And the switch toggle of Xposed doesn't work for SafetyNET or SnapChat, so the module have to be deactivated
It's impossible and too long !
So i don't use XPosed and don't make Update of module !
Click to expand...
Click to collapse
I don't know why the switch inside Xposed dont work for you. It worked for me when I used Marshmallow.
But what happens about the dalvik is that Xposed is a very complex and extended modification that can hook (and therefore alter) pretty much every app on your device. So when you "remove" or "install" it by enabling or disabling the module on magisk a dalvik wipe is triggered by the system the next time you boot.
The process is similar to when you systemize an app or updates your device, but instead of one or few apps to recompile, the system has to recompile (aka "optimize") most, if not all the apps on your system.
On Marshmallow specially, the Android uses an Ahead Of Time (AOT) compiler, meaning that all this compilation will occur on next boot, before the rest of the system can be used. To fix this problem, Google started using Just In Time (JIT) compiler from Nougat on, meaning that the optimization will occur when and if necessary, and if possible when the device is idle or not being intensely used. That's why in Nougat or Oreo this problem does not happen.
After updating to Magisk 17.1, when I install a new module or update an existing module, it installs successfully but after rebooting all the apps changes to default system apps, and default setting. Again i reboot, then everything comes back except that xposed framework gets deactivated along with all its modules(like gravity box etc.) then i again reboot to activate it, then again reboot to activate its modules. Thus the complete process involves 4-5 reboots to function everything back to normal. This didn't happened before. I'm using Lenovo K8 note, Android O(8.0). Any solution??