Hi everyone,
I got an issue with my Moto G. I was using ART runtime ever since I bought my Flacon and today by mistake I put off Developer Options. I turned on Dev Ops and the runtime was shown as Dalvik. After that I just cant change the runtime to ART. I get the reboot to change runtime from libvm.so to libart.so? popup but nothing happens after rebooting. Tried it about 10 times now.
Thank you!
EDIT: I should have googled first. As it turns out, I've got Xposed Framwork installed, hence, ART won't get enabled.
Sorry for the post.
Cheers!!
If you're using Xposed, it won't change.
rogeriorp said:
If you're using Xposed, it won't change.
Click to expand...
Click to collapse
I have same Problem. I had Xposed installed but uninstalled it. I still cant change runtime to ART even though xposed installer is not on my device anymore.
Related
I have been rebooting my Nexus 5 when using Xposed Framework modules and for every perfect reboot I get a bootloop. Is anyone else experiencing this? It's frustrating that my Stock Rooted with Xposed Framework setup would cause bootloops and every time a bootloop occurs it eats up a lot of battery and makes the phone uncomfortably warm.
do you have art selected?
I have the same setup as you.....xposed never sent my device into boot loop. As the poster above me stated, are you using art or dalvik? I believe xposed does not work with art. Also, could using a module within xposed that is not developed for 4.4+ cause such misbehavior?
Sent from my Nexus 5 using xda premium
I have had this problem.. I don't know how to fix it.. I just restore a backup and try it again.. Sometimes it works and sometimes it don't
Sent from my Nexus 5 using XDA Premium 4 mobile app
I use Xposed on all my devices, I've never had so much as a stutter from it, let alone a bootloop. You've got something else going on. As others pointed out, if you are using ART runtime, Xposed isn't compatible.
_MetalHead_ said:
I use Xposed on all my devices, I've never had so much as a stutter from it, let alone a bootloop. You've got something else going on. As others pointed out, if you are using ART runtime, Xposed isn't compatible.
Click to expand...
Click to collapse
Yeah it's not that, I don't have ART enabled and on top of that enabling ART while Xposed is installed automatically sends you back into the OS and cancels the request for ART as a part of Xposed Framework, so I couldn't have enabled it anyway.
grizzlywan said:
Yeah it's not that, I don't have ART enabled and on top of that enabling ART while Xposed is installed automatically sends you back into the OS and cancels the request for ART as a part of Xposed Framework, so I couldn't have enabled it anyway.
Click to expand...
Click to collapse
I wasn't inferring that ART was the only possible cause, just the most common. What modules are you trying to use?
_MetalHead_ said:
I wasn't inferring that ART was the only possible cause, just the most common. What modules are you trying to use?
Click to expand...
Click to collapse
GravityBox and Greenify. Nothing that should be causing this.
grizzlywan said:
GravityBox and Greenify. Nothing that should be causing this.
Click to expand...
Click to collapse
If you disable both mods do you still get boot loops? And are you using the version of GB that's meant for kitkat?
_MetalHead_ said:
If you disable both mods do you still get boot loops? And are you using the version of GB that's meant for kitkat?
Click to expand...
Click to collapse
Still getting boot loops with both mods disabled, even went as far as to uninstall Xposed Framework to see if it would happen. I rebooted 10 times and it boot looped 3 times out of those 10.
Yes, using GravityBox for KitKat.
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?
Hi, I have recently rooted my nexus 5 using cf auto root and have installled a custom recovery and I am trying to change my runtime from dalvik to ART but everytime I change my phone reboots but it still says my runtime is Dalvik, none of my apps are optimsed etc, any ideas on what to do ?
Hi,
I guess you are using Xposed stuff... if yes it's normal, for now Xposed framework is not compatible with ART runtime so to avoid bootloop it goes back to Dalvik runtime automatically.
Hammer_Of_The_Gods said:
Hi,
If you are using Xposed stuff it's normal... for now Xposed framework is not compatible with ART runtime so to avoid bootloop it goes back to Dalvik runtime automatically.
Click to expand...
Click to collapse
oh ahaha cheers for that I didnt realise that xposed framework would effect it
vinsta11 said:
oh ahaha cheers for that I didnt realise that xposed framework would effect it
Click to expand...
Click to collapse
Yep, some reading: http://forum.xda-developers.com/showpost.php?p=50163642&postcount=478 from the Xposed thread: http://forum.xda-developers.com/showthread.php?t=1574401...
So ART runtime or Xposed, you will need to make a choice...
Hammerhead (KTU84P), rooted. I tried to turn on ART by going to "developer options" and under select runtime, select ART, then it will ask me to reboot. But after reboot, I come back to the developer options, it still shows "Dalvik".
Anyone can tell me how to turn on ART? Thanks.
iantung329 said:
Hammerhead (KTU84P), rooted. I tried to turn on ART by going to "developer options" and under select runtime, select ART, then it will ask me to reboot. But after reboot, I come back to the developer options, it still shows "Dalvik".
Anyone can tell me how to turn on ART? Thanks.
Click to expand...
Click to collapse
You're running xposed yes?
iantung329 said:
Hammerhead (KTU84P), rooted. I tried to turn on ART by going to "developer options" and under select runtime, select ART, then it will ask me to reboot. But after reboot, I come back to the developer options, it still shows "Dalvik".
Anyone can tell me how to turn on ART? Thanks.
Click to expand...
Click to collapse
By uninstalling Xposed.
Lethargy said:
By uninstalling Xposed.
Click to expand...
Click to collapse
(face palm)
Xposed is not ART compatible? I can't believe that I am this stupid not to realize this pitfall. Guess I have see if I want ART or Xposed....
Thanks for pointing this out.
iantung329 said:
Hammerhead (KTU84P), rooted. I tried to turn on ART by going to "developer options" and under select runtime, select ART, then it will ask me to reboot. But after reboot, I come back to the developer options, it still shows "Dalvik".
Anyone can tell me how to turn on ART? Thanks.
Click to expand...
Click to collapse
XPosed does not currently support ART runtime. You're going to need to uninstall it as said above in order to utilize ART.
Sent from Tapatalk on Nexus 5
iantung329 said:
(face palm)
Xposed is not ART compatible?
Click to expand...
Click to collapse
Nope. Dalvik is a "Just-in-Time" run time. This means translation of code happens at the time it happens - when it is needed to be executed. Xposed allows modules to intercept these commands and change them.
ART is not Just-in-time. It does all translation prior to the application running, which means that there is nothing for Xposed to intercept
When I first switched to ART i had no problem. When I looked at runtime today its in dalvik. When I restarted in ART its still in dalvik. any ideas why ART is not sticking? Thanks in advance
unlocked bootloader with some minor xposed apps installed
Carrzy said:
When I first switched to ART i had no problem. When I looked at runtime today its in dalvik. When I restarted in ART its still in dalvik. any ideas why ART is not sticking? Thanks in advance
unlocked bootloader with some minor xposed apps installed
Click to expand...
Click to collapse
Your answer is in that last line - xposed cannot run with ART and will change the setting back to Dalvik if you try to change to ART.
doogald said:
Your answer is in that last line - xposed cannot run with ART and will change the setting back to Dalvik if you try to change to ART.
Click to expand...
Click to collapse
I figured it was xposed.. Thanks for the clarification!