Hello! On KitKat, I have uninstalled Xposed but it appears I can not switch from Dalvik to Art after uninstallation. What can I do? Thanks, Jan, [email protected]
janbenes said:
Hello! On KitKat, I have uninstalled Xposed but it appears I can not switch from Dalvik to Art after uninstallation. What can I do? Thanks, Jan, [email protected]
Click to expand...
Click to collapse
Either reflash your ROM or stay with dalvik (which is the default runtime for KitKat, ART on KitKat was more or less some kind of alpha program).
Actually, there was a solution. In /system/bin, there was a file (most probably from XPOSED called app_process. I think this file caused reverting to Dalvik from ART. There was also file app_process.orig, supposedly from era before XPOSED. So I renamed app_process to something and then renamed app_process.orig to app_process. Then I was able to switch to ART. On my tablet, ART runs absolutely flawlessly.
Related
Hi,
Just got back to my desk after lunch to find my Nexus 5 looking very "normal"
Google search bar is back
Homescreen dots are back
I have huge icons again (despite build.prop changed to 360)
Hidden apps have reappeared
Wallpaper scrolls again
etc, etc
I have tried uninstalling and reinstalling the framework, wiped cache and dalvik from recovery and also tried downloadind the modules I use again (mainly GravityBox, XGEL settings and Hide Apps), but no luck.
It's been weeks since I've changed anything on my phone (since 23/04 Purity build), so I can only conclude it has something to do with Xposed or one of the modules.
Any idea what the problem might be before I resort to Nandoird or reflashing the ROM?
Xposed log file attached.
Cheers
Lee
EDIT: Reflashing ROM hasn't helped
SUCCESS! :laugh:
Turned out that the latest Google Search update had killed XGEL Settings.
So you can either get XGEL 1.6 Beta Build 2, or roll back Google Search to factory version.
I just rolled back Search for now as I still need to check if any other modules are affected (Hide Apps Xposed for example).
Hope this saves someone a headache!
Lee
i'm running slimkat 7.0 on my verizon s3. i did a titanium restore of my apps, including xposed modules. i made sure the xposed installer had successfully installed the framework and rebooted. none of the modules are serving their function. i uninstalled the framework and rebooted. then i re-installed and rebooted. nothing. anyone have any fresh ideas?
here is my log https://s3.amazonaws.com/pushbullet-uploads/udqtQ-Jj4T1bNCg4yzc6lMYj8TLDJfHdusPsnQ/error.log
bogedy said:
i'm running slimkat 7.0 on my verizon s3. i did a titanium restore of my apps, including xposed modules. i made sure the xposed installer had successfully installed the framework and rebooted. none of the modules are serving their function. i uninstalled the framework and rebooted. then i re-installed and rebooted. nothing. anyone have any fresh ideas?
here is my log https://s3.amazonaws.com/pushbullet-uploads/udqtQ-Jj4T1bNCg4yzc6lMYj8TLDJfHdusPsnQ/error.log
Click to expand...
Click to collapse
Did you make sure that the modules are check in the installer...
When in doubt... Re-download and install modules... Some people have problems restoring backed up modules... Like they just don't work... A reinstall usually fixes it...
Hi guys!
Is too much complicated to generate a flasheable zip or method to disable all xposed modules from recovery?
With this huge change to lollipop is super easy to install a module that bootloop your phone (like mine......) and is not so good to factory reset just for a simple module. I know the risks, and I have nandroid and backups, but again, is too complicated to format all the phone an pasting backup just for a simple module.
Thanks!
PD: I tried the old "xposer disabler" but says that there is not app backup folder and nothing to be done.
kk
disable from kitkat not from android 5
Well if you just want to get out of a bootloop because of a new module, just delete Xposedbridgeapi.jar temporarily from /system/frameworks
berryman13 said:
Well if you just want to get out of a bootloop because of a new module, just delete Xposedbridgeapi.jar temporarily from /system/frameworks
Click to expand...
Click to collapse
Nice, next time I will consider to try it (I get on bootloop again.... and I restored a backup)
you can just create an empty file named 'disabled' in '/data/data/de.robv.android.xposed.installer/conf/'
berryman13 said:
Well if you just want to get out of a bootloop because of a new module, just delete Xposedbridgeapi.jar temporarily from /system/frameworks
Click to expand...
Click to collapse
I realize this is a few years later but THANKS!
It's amazing how many people can access their /data/data directory from recovery to disable XPosed and how uneducated people are and don't use encryption!
Yesterday I disabled all Xposed modules and RESET my phone. I didn't uninstalled any module or xposed apk. I directly resest my phone.
But my phone went to the RESET LOOP (keep reseting). After 5 hours it started to work perfectly.
Now the problem is every module of xposed is uninstalled. But some modules are still active, like new boot animation (which I got from Android L Theme module), new font (which I got from ifont module).
Please tell me a way to fix these issues. In SD Card, there are folders of modules and in each folder there is a backup folder (with a zip file). So how to restore my boot animation and default font?
Should I reinstall and remove them?
I factory reset my LG Volt 2 and had 3.13 GB of available space on my internal storage. After flashing xposed-v85-sdk22.zip using FlashFire, Xposed is successfully installed, but I'm left with only 2.35 GB of available space. Theres no way Xposed is supposed to take up .78 GB of storage. I don't have a single Xposed module installed and it's not the Xposed installer which is taking up only 1.34MB. Here are the apps on my device after flashing Xposed sorted by size to prove that no other apps are taking up all that space.
It's probably because many system apps have to be recompiled with less optimization. Usually, they are pre-compiled by the vendor and stored as odex files on the /system partition, but now they're also stored in the Dalvik cache. Unfortunately, it's necessary, otherwise hooks wouldn't work reliably. The only workaround I can imagine is using compiler filter properties to influence how much is compiled, but that would mean that the uncompiled methods are slower. It's basically space vs. performance.
rovo89 said:
It's probably because many system apps have to be recompiled with less optimization. Usually, they are pre-compiled by the vendor and stored as odex files on the /system partition, but now they're also stored in the Dalvik cache. Unfortunately, it's necessary, otherwise hooks wouldn't work reliably. The only workaround I can imagine is using compiler filter properties to influence how much is compiled, but that would mean that the uncompiled methods are slower. It's basically space vs. performance.
Click to expand...
Click to collapse
Im having the same problem also, once I flashed the Xposed Framework, without any module installed, not also Xposed Installer, but it takes up to 800mb of internal storage. Is it normal? What workaround can I do because I dont know anything about compiler filter.
Honor 4C, rooted, Marshmallow.