Database Info

Android is upgrading. Every boot. ART only

Having just rooted and unlocked boot loader, my N5 is giving the "android is upgrading" message for 80+ apps (half the usual) on EVERY reboot. This behaviour is only seen with ART runtime. Not with Dalvik. It was also not seen when on ART in stock form. Running Franco r14 kernel with stock rom. Any ideas?

stanc74 said:
Having just rooted and unlocked boot loader, my N5 is giving the "android is upgrading" message for 80+ apps (half the usual) on EVERY reboot. This behaviour is only seen with ART runtime. Not with Dalvik. It was also not seen when on ART in stock form. Running Franco r14 kernel with stock rom. Any ideas?
Click to expand...
Click to collapse
Thats how it is every boot it has to pre compile the code for apps

Hmm...but in pre root form, this only happened the first time after selecting runtime. Now its happening every reboot! Is this supposed to be normal for a rooted phone?

stanc74 said:
Hmm...but in pre root form, this only happened the first time after selecting runtime. Now its happening every reboot! Is this supposed to be normal for a rooted phone?
Click to expand...
Click to collapse
I don't see that issue on my s2 skyrocket running 4.4 art. I'm not running art on my n5. I'm guessing it's an issue with the franko kernel, but that's just a guess

This happens to my N5 as well. Omni 12/01 nightly + Franco r14
Sent from my Nexus 5 using XDA Premium 4 mobile app

chill out guys, this is normal behavior when using ART.

This is not normal behavior at all on stock ROM. When you switch to ART, it only does the upgrade/compile thing on the first boot. Having it redo it after every reboot is probably a compatibility issue with the ROM you are running.

mdandashly said:
When you switch to ART, it only does the upgrade/compile thing on the first boot.
Click to expand...
Click to collapse
That's my recollection as well. It still is on stock ROM. But it looks like other people who have rooted are facing issues that might have arose from kernel or app issues.
I have already wiped cache and rebuilt dalvik fwiw. Also uninstalled titanium backup while no weird odex files are noted. Only Franco kernel left as last data point but I wanted to see if others faced this problem before taking the plunge to reinstall stock kernel

dorkythegreat said:
This happens to my N5 as well. Omni 12/01 nightly + Franco r14
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It does not happen on stock rooted for me either. I would suggest returning to stock rooted to use ART. According to Omni threads they are in nightlies so stuff is expected to be wrong.

Fwiw. I've flashed stock kernel, reflashed the patched libart.so (ie. Whatsapp compatibility fix) , reinstalled whatsapp. Still no joy.

Ah... from According to:
[url]https://code.google.com/p/android/issues/detail?id=61916
The problem is identified as an extra unbalance check between MonitorEnter / MonitorExit JVM instructions, which ART does and Dalvik doesn't. Some apps (such as Whatsapp) fail to have those balanced.
The fix will be probably fixed in AOSP sooner than later...
Sooo ... everybody relax and have a cup of tea (me included) :good:[/QUOTE]

stanc74 said:
Ah... from [URL="http://forum.xda-developers.com/showthread.php?p=47473296”]this thread about ART[/URL], this upgrading on every boot seems a known ART bug related to partially incompatible apps like whatsapp
Click to expand...
Click to collapse
Hmmm... sorry for the bad news but the problem discussed in that thread is unrelated with yours. We were discussing the (initial) whatsapp incompatibility.
BTW: Using ART here (Nexus 4), absolutely no problems now

it will depend on your apps. this is normal behavior. my n7 doesnt go through it, but my n4 does. they have different apps installed. my n5 goes yhrough it as well(but only 3 apps upgrading on a reboot). its fine if you want to freak out over it, but in reality it is normal.

I have 80 apps upgrading on reboot..and these are pretty standard apps.... This is quite a mysterious situation.
Good to know its happening. Perhaps next ota will address this...

stanc74 said:
I have 80 apps upgrading on reboot..and these are pretty standard apps.... This is quite a mysterious situation.
Good to know its happening. Perhaps next ota will address this...
Click to expand...
Click to collapse
my nexus 4 has 92 apps that upgrade after every reboot while on ART. 92 apps, out of 183 apps.

I’m using ART. Running Purity ROM with ElementalX. No long boot issue. I did have a long boot with apps optimization when I switched to ART the first time, but since then it boots normally and quickly.

Updated to 4.4.1. Had to flash stock boot and system IMG along the way. Updated, rooted and now it seems fine. Fast reboot with no data loss!

simms22 said:
chill out guys, this is normal behavior when using ART.
Click to expand...
Click to collapse
markdapimp said:
Thats how it is every boot it has to pre compile the code for apps
Click to expand...
Click to collapse
stanc74 said:
Having just rooted and unlocked boot loader, my N5 is giving the "android is upgrading" message for 80+ apps (half the usual) on EVERY reboot. This behaviour is only seen with ART runtime. Not with Dalvik. It was also not seen when on ART in stock form. Running Franco r14 kernel with stock rom. Any ideas?
Click to expand...
Click to collapse
i am running stock 4.4.2 on N5 with bootloader unlocked and after each reboot i face the same cache rebuilt thing (android is upgrading) for all the user applications i have. Is it normal for stock rom too? have you seen any one on stock who is having otherwise?

I have this problem on my sony xperia sp running cm11, but it is happening since 5 days. Maybe it is the new version of a custom kernel, or link2sd.

Nope it's not normal. What else have you installed or flashed?
Sent from my Nexus 5 using Tapatalk

Can't switch to ART

For some reason I can't switch to ART. When I select that in developers options, it prompts to reboot but afterwards when I check it is still on dalivk. Any idea? Running purity rom with Franco kernel.

Check the purity rom and franko kernel to see if it supports art

Do you haze xposed installed
Sent from my Nexus 5 using Tapatalk

Franco works fine. You'll have xposed installed so it'll just reboot back to Dvalik
Sent from my Nexus 5 using Tapatalk

Oh so do I have to uninstall xposed to switch to ART?

onecrzyasian said:
Oh so do I have to uninstall xposed to switch to ART?
Click to expand...
Click to collapse
Yes.
I had this issue this afternoon. Couldn't figure out why ART wouldn't activate until I searched.
Uninstall xposed, select ART, then reboot, and then when all of the apps have been refreshed upon boot up, reinstall Xposed.

onecrzyasian said:
Oh so do I have to uninstall xposed to switch to ART?
Click to expand...
Click to collapse
Yes

blackdragoon said:
Yes.
I had this issue this afternoon. Couldn't figure out why ART wouldn't activate until I searched.
Uninstall xposed, select ART, then reboot, and then when all of the apps have been refreshed upon boot up, reinstall Xposed.
Click to expand...
Click to collapse
wait you reinstalled Xposed and was able to keep ART??

onecrzyasian said:
wait you reinstalled Xposed and was able to keep ART??
Click to expand...
Click to collapse
Oh wait, now that you mentioned it...
I just checked again. Didn't notice that it switched back to Dalvik.

Xposed will probably never work with ART
Sent from my Nexus 5 using Tapatalk

A handy hint I have just discovered... Uninstall Xposed from within the framework first, THEN remove it from your phone... Apparently Xposed leaves "things" behind :/

takuhii said:
A handy hint I have just discovered... Uninstall Xposed from within the framework first, THEN remove it from your phone... Apparently Xposed leaves "things" behind :/
Click to expand...
Click to collapse
Hi,
Yes you need to uninstall from Xposed framework to restore the original "app_process" file and reboot..., then nothing is left on your phone.

ART runtime in VZW 4.4 update

Has anyone had any luck moving from Dalvik to ART with the latest VZW 4.4 update?
When I switch over to ART, the device asks to be rebooted. It will reboot, but when it comes back up, it's set back to Dalvik again.
WP=0 and rooted if that's worth anything.

digitaloutsider said:
Has anyone had any luck moving from Dalvik to ART with the latest VZW 4.4 update?
When I switch over to ART, the device asks to be rebooted. It will reboot, but when it comes back up, it's set back to Dalvik again.
WP=0 and rooted if that's worth anything.
Click to expand...
Click to collapse
This was actually the first thing I switched once I got the 4.4 update. I have rebooted since and mine is sticking to ART. I have noticed no problems or compatibility issues as of yet.
EDIT: I forgot to mention that I am not or have ever rooted my Maxx.

Mine has successfully switched to ART and have no problems. I am wp off but am not rooted.

Interesting. Wonder if it's related to root. It works fine on my Nexus but my Nexus isn't rooted either.

digitaloutsider said:
Has anyone had any luck moving from Dalvik to ART with the latest VZW 4.4 update?
When I switch over to ART, the device asks to be rebooted. It will reboot, but when it comes back up, it's set back to Dalvik again.
WP=0 and rooted if that's worth anything.
Click to expand...
Click to collapse
I am WP=0 and rooted as well and encounter the same exact problem you do. Probably an incompatibility with root.

I switched to art first thing after update and root. No problems to report and no noticeable difference either. My only issues is that a video I took was choppy. Doubt it was an art issue.
Sent from my XT1080 using Tapatalk

Just switched to test...the initial boot took FOREVER on the "Android is upgrading" screen...but it seems to be working fine...
WP off and rooted 4.4
Sent from my XT1080 using Tapatalk

In another thread a few people mentioned that if you are using Xposed that the setting won't stick. This is intentional as it could possibly brick your phone if Xposed is compiled with ART at the moment.
http://forum.xda-developers.com/showthread.php?t=2582646
If it's not Xposed, then there may be other apps out there that have similar safety mechanisms.

[Q] Anyone else experience this?

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.

[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?