I used to be on ART runtime running CM11 nightlies. Since couple of days,
nightlies refuse to work correctly using ART runtime (basically Phone UI will
crash on reboot, and much of others,too).
Having already reinstalled my phone from scratch to have confirmation that
the issue is due to the choice of runtime, I'm searching a way to switch back
to Dalvik runtime from ART, using ClockworkMod and avoid full reinstallation
of the phone.
Any ideas, hints ?
Related
Every time I try to change runtime to ART and reboot, the option still says "Use Dalvik". There also isn't a long boot time and the 'Android is upgrading' wait.
I am able to change to ART runtime if I do a clean flash of Omnirom but unable to do so after installing all of my apps.
Is there a log to see which apps are causing this? or if it's app related at all?
I am using Samsung Galaxy S3 i9300. I have also flashed SuperSU and Temasek Kernel.
Sythun said:
Every time I try to change runtime to ART and reboot, the option still says "Use Dalvik". There also isn't a long boot time and the 'Android is upgrading' wait.
I am able to change to ART runtime if I do a clean flash of Omnirom but unable to do so after installing all of my apps.
Is there a log to see which apps are causing this? or if it's app related at all?
I am using Samsung Galaxy S3 i9300. I have also flashed SuperSU and Temasek Kernel.
Click to expand...
Click to collapse
I guess you are using exposed, that causes the issue with ART.
BeDesireS said:
I guess you are using exposed, that causes the issue with ART.
Click to expand...
Click to collapse
Ahh I see. Thanks.
Edit: Yep that was the issue. Uninstalled Xposed framework modifications and it worked. And also ART runtime doesn't seem to like low available space and will start causing crashes of apps.
I guess I'm a little late to the topic, but I installed CM11 on my nook color and my razr HD. After reading this thread, I uninstalled xposed from both devices.
Every time I change from Dalvik to Art, the boot process takes long, apps getting modified, and once it's all done and I check developer options, it's telling me that it runs Dalvik.
Is there a way to pinpoint which apps could cause this?
Would it be sufficient to remove all apps and then install one app after the other to see if Art is still running, or would I have to reinstall Android or at least wipe all user data?
Hello, I recently successfully unlocked the boot loader and rooted my device running stock Android 4.4.2 but I'm having a problem with the Dalvik and ART runtimes. I've read that when you change over from Dalvik to ART it takes about 20 minutes to change everything as ART requires about 10% more space for each app. But my problem is that whenever I click on "Use ART" and my tablet reboots, nothing happens. It turns off and boots up like normal without any changes, so I looked in the options and nothing changed. I'm still using Dalvik. I've tried this process a few times but still it boots up with Dalvik.
I have 3.5GB of space left on my device with about 8GB used so I don't know if that causing it not work or whether because I've rooted my device.
Any help would be appreciated
Smithy5995 said:
Hello, I recently successfully unlocked the boot loader and rooted my device running stock Android 4.4.2 but I'm having a problem with the Dalvik and ART runtimes. I've read that when you change over from Dalvik to ART it takes about 20 minutes to change everything as ART requires about 10% more space for each app. But my problem is that whenever I click on "Use ART" and my tablet reboots, nothing happens. It turns off and boots up like normal without any changes, so I looked in the options and nothing changed. I'm still using Dalvik. I've tried this process a few times but still it boots up with Dalvik.
I have 3.5GB of space left on my device with about 8GB used so I don't know if that causing it not work or whether because I've rooted my device.
Any help would be appreciated
Click to expand...
Click to collapse
Are you using Xposed? Can't use ART if you are.
It could be Xposed.. the developer said Xposed relies on Dalvik, and it requires basically an entire rewrite to even test if its work porting to ART.
By the way I've switched from Dalvik to Art and so forth a few times now (I don't have Xposed) and I've had no issues. I prefer ART though.
TheCraig said:
It could be Xposed.. the developer said Xposed relies on Dalvik, and it requires basically an entire rewrite to even test if its work porting to ART.
By the way I've switched from Dalvik to Art and so forth a few times now (I don't have Xposed) and I've had no issues. I prefer ART though.
Click to expand...
Click to collapse
Using Xposed with Art will most likely end in a bootloop. Art is faster but still a bit in Googles experimental phase.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
Using Xposed with Art will most likely end in a bootloop. Art is faster but still a bit in Googles experimental phase.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The latest version of Xposed forces you back to Dalvik if you attempt to enable ART.
Thanks
Thanks for the replies everyone. I am using Exposed. I think I'll just keep using Dalvik for the moment instead of going through the hassle of deleing Xposed
I was hoping I could play around with ART this weekend on my Note 3 with CM11 M7 but it won't even enable, I've enabled Dev Options, changed runtime from Dalvik to ART, reboots, and then starts up only a few seconds later back using Dalvik (where as ART should take a few minutes to convert apps over to its runtime)
Any ideas why it won't switch over?
Does Android Lollipop only support ART or does it support dalvik too, like Kitkat supported ART?
only ART I think
galaxyYtester said:
Does Android Lollipop only support ART or does it support dalvik too, like Kitkat supported ART?
Click to expand...
Click to collapse
most likely only ART as that is the way they are going - The build and the kernel will be built on ART so I very much doubt there will be a dalvik version
Android Lollipop should be released on Friday 17th October however don't expect it to be any phones officially until Christmas although you can always check out dev builds from the released source code but don't expect it to be on the galaxy y 5360 as ART does not support armv6
You can read the full change log
http://www.androidpolice.com/2014/10/15/its-officialandroid-l-is-android-5-0-lollipop/
That worries me
This week I had the Amazon app crash on me (nexus 5, 4.4.4, ART) while changing Amazon accounts (worked before, something happened while doing it which apparently corrupted the app permanently).
Cleared the app data/cache, uninstalled, reinstalled, rebooted, nothing fixed it. Every time I'd try to login, it crashed.
The only thing that fixed it was to revert back to Dalvik, then back to ART.
Looks like the conversion/recompiling process cleaned whatever got broken. Weird, as I'd expect uninstalling/reinstalling the app would suffice, if the corruption was limited to its own precompiled binary.
Without this, my only option would be a factory reset, I guess.
Even if Dalvik is dead, maybe we could get a "refresh" option for ART as a second-to-last resource.
I installed Slimkat 4.4.4 on a aging Nexus 7 2012, but Mobdro will not work. I have uninstalled Mobdro, went into recovery and cleared cache, and Dalvik cache, did a SD Maid cleaning and then downloaded Mobdro (latest version), re-installed, but I still get the same useless error message, "Unfortunately, Mobdro has stopped". The app did work before in a stock non-root Lollipop install.
I checked to see if any of the other apps were preventing Mobdro from working, I thought it was MinMinGuard so I disabled it and rebooted, but it was not the problem. I could not see any other app conflicts or problems.
I am thinking it is a conflict with Slimkat and Mobdro, or perhaps a setting in Slimkat that has created a conflict, I pretty much left all the settings in SLimkat at default. So I am wondering what ROMS have you used that Mobdro works on? Unless I can find a fix for Slimkat and Mobdro, I would like to move to another ROM that others have used that will work with Mobdro, any help would be appreciated.