Database Info

[Q] Dalvik to ART ?

Tried to switch from dalvik to ART but on reboot it doesn't seem to stick. I go back into dev options and it still says dalvik. I'm on the original soak test, which shouldn't matter, but I'm curious if anyway else switch to ART and got it to stick. Thanks.

I've heard that happens if you're using xposed
Sent from my XT1080 using Tapatalk

livinitwarrior said:
I've heard that happens if you're using xposed
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
I'll have to see if that works. Any idea if I can uninstall xposed switch to ART then reinstall xposed or do I have to choose to keep one or the other?

Should be able to. Don't mess with your modules, just install the framework in the app itself, reboot, and try it then.
Sent from my XT1080 using Tapatalk

Xposed doesn't work with ART (yet). The Xposed developer purposely has your runtime switch back to Dalvik upon reboot to keep you from going into a bootloop with ART.

tehcodeman said:
Xposed doesn't work with ART (yet). The Xposed developer purposely has your runtime switch back to Dalvik upon reboot to keep you from going into a bootloop with ART.
Click to expand...
Click to collapse
Okay, thanks.

I have this same problem. I uninstalled Xposed, but it still switches back to Dalvik. Is there another app that can automatically switch to Dalvik, or did Xposed leave something behind?
EDIT: Nevermind, figured it out. It does leave stuff behind, it came to me that I had to hit an INSTALL button to install the framework, so i had to reinstall Xposed and hit an Uninstall button to uninstall the framework.

After i've changed runtime to ART every start up of phone is accompanied by error message: Google Play services has stopped.
I've wiped Play data but it didn't help.
Any ideas how to solve this issue?
Droid Mini, 4.4.2, rooted

.: SID :. said:
After i've changed runtime to ART every start up of phone is accompanied by error message: Google Play services has stopped.
I've wiped Play data but it didn't help.
Any ideas how to solve this issue?
Droid Mini, 4.4.2, rooted
Click to expand...
Click to collapse
This is a known issue with google play services. There is an update in the works, and an APK is floating around that will resolve this, although the error only occurs on boot, and does not cause any negative effects beyond the single error message.

Teksu said:
This is a known issue with google play services. There is an update in the works, and an APK is floating around that will resolve this, although the error only occurs on boot, and does not cause any negative effects beyond the single error message.
Click to expand...
Click to collapse
I've seen already 2 or 3 updates for Google Services, but my is still the same. May be this error occurs when it can't be updated?

SystemUI Process crashing.

So I've been running the same setup since I updated to 4.4.4 about a month ago. Stock 4.4.4 rom with Xposed framework, rooted, custom kernel, custom DPI.
This morning I wake up and my phone will boot past the boot screen and just keep giving me the "Unfortunately, the process com.android.systemui has stopped.
Does anyone have stock 4.4.4 systemui file in case mine got corrupted somehow? Or should I flash the system.img? What does the system.img change if I flash it. Will if affect my apps/data/etc?

System.img replaces everything in /system. Your data and apps are in /data
Might be worth reading the sticky threads. This is pretty basic info that you should already know if you're messing with root.
Most likely the problem will be with /data anyway
Sent from my Nexus 5 using Tapatalk

I read somewhere that Xposed might be causing it. Is there a way to disable it as I can't get to it fast enough before the systemui crashes.

Isn't there an xposed removal flashable zip in the xposed thread? I think there is.
It won't be xposed itself but it could be a module or the settings of moduke causing it, which are stored in /data.
That said, removal of xposed would be the best course to take for elimination purposes.
Sent from my Nexus 5 using Tapatalk

impruv said:
I read somewhere that Xposed might be causing it. Is there a way to disable it as I can't get to it fast enough before the systemui crashes.
Click to expand...
Click to collapse
I had this problem after flashing a new nightly version of my ROM.
http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401/post51306764
I went into safe mode, documented in the thread above. Uninstalled the xposed installer. Reinstalled the xposed installer apk. Updated Xblast tools to the latest version. Problem seems to have gone away. Will have to see what happens after I flash the next nightly, however. This might have something to do with the ROM overwriting /system

I came across this thread after Googling the issue I was having. I am also rooted, running 4.4.4 (CarbonROM on the Nexus 7 and stock on Moto X), and am running Xposed on both my Nexus 7, and on my Moto X. Suddenly last night I rebooted (first the N7, and then this morning the X), and lo and behold, System UI crashed on both.
I then restored my most recent nandroids on both (within a week), and all good again. Then updated all my apps that needed updating. Rebooted again because the Moto X froze, and again, System UI crash. That got me thinking that an app that was updated may be the culprit. So I updated each of my apps that had updates available one-by-one, and rebooted after each one. All good, until I came to Google+. When Google + updated, and then I rebooted, BOOM. System UI crash. Not sure if this is a conflict with Xposed or a coincidence, but Google + is definitely causing the issue for me. Hope this helps.
EDIT: I will try uninstalling Xposed then updating Google+, and report back.
UPDATE: After once again restoring my latest Nandroid, I uninstalled Xposed, rebooted, and updated all of my apps, including Google+. Rebooted, and all was good. I then went to re-install Xposed, and noticed that there were a few modules, XBlast, Gravity Box, and App Opps, that had updates available. I downloaded and installed the updates, then re-installed Xposed and rebooted. All is fine again.

sn2hotty said:
I came across this thread after Googling the issue I was having. I am also rooted, running 4.4.4 (CarbonROM on the Nexus 7 and stock on Moto X), and am running Xposed on both my Nexus 7, and on my Moto X. Suddenly last night I rebooted (first the N7, and then this morning the X), and lo and behold, System UI crashed on both.
I then restored my most recent nandroids on both (within a week), and all good again. Then updated all my apps that needed updating. Rebooted again because the Moto X froze, and again, System UI crash. That got me thinking that an app that was updated may be the culprit. So I updated each of my apps that had updates available one-by-one, and rebooted after each one. All good, until I came to Google+. When Google + updated, and then I rebooted, BOOM. System UI crash. Not sure if this is a conflict with Xposed or a coincidence, but Google + is definitely causing the issue for me. Hope this helps.
EDIT: I will try uninstalling Xposed then updating Google+, and report back.
UPDATE: After once again restoring my latest Nandroid, I uninstalled Xposed, rebooted, and updated all of my apps, including Google+. Rebooted, and all was good. I then went to re-install Xposed, and noticed that there were a few modules, XBlast, Gravity Box, and App Opps, that had updates available. I downloaded and installed the updates, then re-installed Xposed and rebooted. All is fine again.
Click to expand...
Click to collapse
Yea it was XBlast that caused the issue. I fixed it by disabling Xposed with the key taps, updating all the modules and then rebooting.

[Q] Uninstalled Xposed. Boot looping?

Hey guys, I just rooted my device after getting the OTA update to android L.
I went into my xposed framework app, because it wasn't active, i decided to uninstall xposed framework from within the app. This uninstalled and then rebooted. But its booting and is just playing the google boot animation.
Not sure what to do! its so dumb that this has bricked my phone. I can boot into fastboot mode though.
I would rather not lose all of my stuff haha. I did back up my pics and music though. So not a huge deal if i do.
Please help?
Keaton

Just went into recovery mode. Says "No Command"
What do i do?
Keaton

Hey,
I had the same issue:
Updated to lollipop recently through sideload. All worked fine. Today I unistalled the Xposed Framework... could no longer boot... to be honest I was **** scared...
All I had to do was the following:
- downloaded the stock rom from here: https://developers.google.com/android/nexus/images
- extracted from the factory image the system.img file
- managed to get the soft bricked phone to boot into bootloader / fastboot
- used Nexus Root Toolkit to flash the system.img.
Nexus 5 back to normal, no data lost.
Hope this helps ,
rgs

Are you seriously posting about xposed not working on L?
Seriously?
Xposed is for Dalvik only. It does not work on Art.

GldRush98 said:
Are you seriously posting about xposed not working on L?
Seriously?
Xposed is for Dalvik only. It does not work on Art.
Click to expand...
Click to collapse
You just saw the word Xposed and leapt into action, didn't you?

GldRush98 said:
Are you seriously posting about xposed not working on L?
Seriously?
Xposed is for Dalvik only. It does not work on Art.
Click to expand...
Click to collapse
What's wrong with you ? Chill & read!
We had issues as we removed an existing xposed setup we thought was remaining after upgrading to Lollipop, not trying to make it work with lillipop!
Anyhow serious on not, we ended up with a dead phone and we are sharing issues / solutions.

Help - Cannot get Xposed installed on the Z5 (perpetual bootloop)

Alright, I know the Z5 is supposed to bootloop a few times (AndroPlus says 2-3 times in his rooting thread) before it'll boot with Xposed installed, but after installing the framework, mine just bootloops indefinitely.
I've tried several times on different firmwares (32.0.A.6.152 and 32.0.A.6.209 Customized_US) and with different Xposed versions (xposed-v79-sdk22-arm64.zip and xposed-v80-sdk22-arm64.zip). Each time, I let it bootloop 5+ times for good measure. Each bootup, it'll load the wallpaper, then load SystemUI, and then freeze shortly after, followed by a reboot. It does this perpetually and will not boot all the way. I have no Xposed modules nor the Installer installed on the phone, so there should be nothing interfering with the bootup in that regard. I have tried with the Xposed Installer installed beforehand as well.
The only other advice I've found online is a couple articles that suggest this old modified Xposed package "xposed-v74-sdk21-arm64-dl12345-UNOFFICIAL-20150929.zip" for Z3, Z4, and Z5 that bootloop when installing Xposed, but I'm hesitant to use a dated version and one that's for an older SDK as well. Plus, the threads on XDA recommend the latest Xposed version as working.
The phone is rooted, obviously, with SuperSU 2.46 and running AndroPlus kernel, which shouldn't be a problem. I do have a bunch of system apps (bloatware) that are uninstalled and some disabled, but I don't see why that would cause an issue. I honestly cannot think of anything else that would be causing this to not work. Really hoping someone here has experienced the same and knows the solution. I'm also curious: how many times have others had to let their device bootloop before successfully booting with Xposed?

neonixxx said:
Alright, I know the Z5 is supposed to bootloop a few times (AndroPlus says 2-3 times in his rooting thread) before it'll boot with Xposed installed, but after installing the framework, mine just bootloops indefinitely.
I've tried several times on different firmwares (32.0.A.6.152 and 32.0.A.6.209 Customized_US) and with different Xposed versions (xposed-v79-sdk22-arm64.zip and xposed-v80-sdk22-arm64.zip). Each time, I let it bootloop 5+ times for good measure. Each bootup, it'll load the wallpaper, then load SystemUI, and then freeze shortly after, followed by a reboot. It does this perpetually and will not boot all the way. I have no Xposed modules nor the Installer installed on the phone, so there should be nothing interfering with the bootup in that regard. I have tried with the Xposed Installer installed beforehand as well.
The only other advice I've found online is a couple articles that suggest this old modified Xposed package "xposed-v74-sdk21-arm64-dl12345-UNOFFICIAL-20150929.zip" for Z3, Z4, and Z5 that bootloop when installing Xposed, but I'm hesitant to use a dated version and one that's for an older SDK as well. Plus, the threads on XDA recommend the latest Xposed version as working.
The phone is rooted, obviously, with SuperSU 2.46 and running AndroPlus kernel, which shouldn't be a problem. I do have a bunch of system apps (bloatware) that are uninstalled and some disabled, but I don't see why that would cause an issue. I honestly cannot think of anything else that would be causing this to not work. Really hoping someone here has experienced the same and knows the solution. I'm also curious: how many times have others had to let their device bootloop before successfully booting with Xposed?
Click to expand...
Click to collapse
i have installed it 3-4 times on my phone , and every time , it only bootlooped once. but then i manually rebooted just to be sure. i dont really know what causes yours to bootloop, did you try wiping cache and dalvik after installation? does your device optimize apps on startup?

arismelachrinos said:
i have installed it 3-4 times on my phone , and every time , it only bootlooped once. but then i manually rebooted just to be sure. i dont really know what causes yours to bootloop, did you try wiping cache and dalvik after installation? does your device optimize apps on startup?
Click to expand...
Click to collapse
Thanks for the response. Yeah, I've tried wiping cache and dalvik after installing, before rebooting. It does go through optimizing every single app on the first boot after clearing cache, and doesn't on the subsequent reboots, which is just as is expected.
And I have also tried manually powering off the phone from the power dialog while it was booting, before it could freeze and bootloop itself. It made the device shut down gracefully, then I let it sit for about 15 minutes and turned it on, but the results were the same as well.

Xposed Issue/Question

Hello all. I'll try to explain my issue with as much detail and hopefully somebody can help me.
Anyways I picked this phone up on sale on amazon and I have already unlocked the bootloader and am successfully rooted. Now I want to use Xposed. I have been trying to get it to work for 2 days now and I am fed up.
I downloaded the correct Xposed installer(SDK 24 v88.2) and it will somewhat work but then after a reboot It says it's installed but not active and it tells me to check the logs of which are blank. I am rooted the supersu way and have twrp installed.
I've read about some script I can put in the init.d folder or something like that but I cannot seem to get it to work.
I am on emui 5.0 with android 7.0.
Can someone please for the life of me help me get this to work?
I'm simply trying to use a module for my Snapchat called snaptools.
I know it's a lot to ask but can someone please help with a tutorial or a fix/instructions?

Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.

RedSkull23 said:
Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.
Click to expand...
Click to collapse
I do not have greenify installed unfortunately. I literally got this phone 2 days ago and I've never had this issue before.
I just uninstalled the SuperSU version and Installed the magisk version for root and then installed Xposed through the magisk manager and installed the modified Xposed installer apk that can see the systemless install. Xposed has survived a couple reboots and my modules are working but I fear that it will stop working as you stated before randomly. Have you tried it my way?
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.

patrick8996 said:
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.
Click to expand...
Click to collapse
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...

RedSkull23 said:
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...
Click to expand...
Click to collapse
Hmm I'm still active but I haven't restarted since I posted. I'm wondering why there isn't a more detailed thread regarding this as it seems a lot of people use this phone.
Maybe you can try fresh with magisk and the modified Xposed installer for straight systemless. I've had a hell of a lot more luck this way than I have through the regular install. It's survived 5 reboots so far. Have you tried just a soft reboot inside the Xposed installer? I mean I know it's not a full restart but it may maintain Xposed and keep it active.

Maybe because only a limited set of people are facing this. And maybe only some devices suffer this. I tried both, fresh installations of normal Xposed / systemless Xposed, both didn't survived after 2 or 3 normal reboots. Yes I always rebooted by Xposed Installer when it was installed, even because i can preserve on/off button the longest i can this way, but sometimes a soft reboot isn't sufficient to apply some modifications, so i rarely used them. I daily rebooted with normal reboots. I'll try when new versions will be available at this point, i tried actual builds for 2 weeks encountering always this error so I'm not motivated on trying them again

Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future

RedSkull23 said:
Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future
Click to expand...
Click to collapse
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.

patrick8996 said:
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.
Click to expand...
Click to collapse
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:

RedSkull23 said:
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:
Click to expand...
Click to collapse
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.

patrick8996 said:
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.
Click to expand...
Click to collapse
Never faced this. The framework keeps staying active actually

RedSkull23 said:
Never faced this. The framework keeps staying active actually
Click to expand...
Click to collapse
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.

patrick8996 said:
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.
Click to expand...
Click to collapse
V15.1 should fix everything. V15.0 was messing up thousands of phones

RedSkull23 said:
V15.1 should fix everything. V15.0 was messing up thousands of phones
Click to expand...
Click to collapse
Ya I installed 15.1 and no longer have any issues. I'm happy all has been working for this long
Sent from my BLN-L24 using Tapatalk