• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Introducing the new Android Runtime - ART

funkylogik said:
I thought ART was supposed to be the thing that makes lower spec devices perform better (more iOs like)? Stupid google :confused:
Click to expand...

Nope, the optimization for 512MB-RAM devices is built into the OS itself - Project Svelte. Nothing to do with ART - which is, after all, to be considered a preview and work-in-progress. It's not supposed to be ready for the mainstream just yet, and it really isn't. It's not surprising (to me, at least) that some of the lower-spec devices got left off the ART guest list.
 
So does anyone know what happens if you backup apps using Titanium Backup while in ART and then try to restore those apps on a new rom which is using dalvik runtime (by default)?

I'm on ART at the moment and I'm wondering what form the TB backups are stored in if I back up any new updates or installations.

Should I swap back to dalvik (with the consequent time-consuming app updates on reboot) and do my TB backups in dalvik, then swap back to ART?

I am concerned about having a mix of two types of compiled app in my TB backup folder, where some apps will be incompatible with one runtime, and the rest of the apps incompatible with the other...

And what of my current TB backups (all made while in dalvik runtime)? Will they be incompatible if I stay in ART?
 
davoid said:
So does anyone know what happens if you backup apps using Titanium Backup while in ART and then try to restore those apps on a new rom which is using dalvik runtime (by default)?

I'm on ART at the moment and I'm wondering what form the TB backups are stored in if I back up any new updates or installations.

Should I swap back to dalvik (with the consequent time-consuming app updates on reboot) and do my TB backups in dalvik, then swap back to ART?

I am concerned about having a mix of two types of compiled app in my TB backup folder, where some apps will be incompatible with one runtime, and the rest of the apps incompatible with the other...

And what of my current TB backups (all made while in dalvik runtime)? Will they be incompatible if I stay in ART?
Click to expand...

Purely a guess (as I haven't tried) but I imagine you'd be fine to restore either way - just probably do a cache wipe afterwards for good measure.
 
I use ART as my daily, along with a custom CM rom and ElementalX kernel.

Feels snappier than Dalvik, and battery life seems to be improved so far.

Make sure all of your apps are up to date. Titanium backup, for example, wasn't compatible but now it is.
 
The S3 is even lower spec than the 10 but ART greatly improved it. It makes it pointless to even update to 4.4 if they leave all the good stuff out! It's just 4.3 with the goodies taken out. Having their best stuff held back with Dalvik is unacceptable. Rooting and flashing a ROM would ruin OTA updates turning a Nexus into another everyday tablet and that's why I want to avoid rooting a nexus. But if Google refuses to give them ART then I might have to do just that.
 
There are still plenty of improvements (both user-facing and under-the-hood) to be found in 4.4; removing the highly experimental optional runtime doesn't really cripple 4.4 at all. Sure, it's a nice bonus and a fun toy to play with, but Svelte should still improve the overall user experience without having to switch runtimes.
 
codesplice said:
Nope, the optimization for 512MB-RAM devices is built into the OS itself - Project Svelte. Nothing to do with ART - which is, after all, to be considered a preview and work-in-progress. It's not supposed to be ready for the mainstream just yet, and it really isn't. It's not surprising (to me, at least) that some of the lower-spec devices got left off the ART guest list.
Click to expand...

Yup, ART was completely unknown until users got the device in hands and started to tinker in developer options.

It was never marketed or hyped, because its not ready yet
 
That won't change the fact that I must live with OOM panics and stuttering until they give us the feature. I like iOS fluidity and Dalvik feels lacking. Has been for a long time.
 
That's right, but had they released an unfinished product we'd be complaining about crashes, random reboots, and app incompatibilities.

Nexus 5 users got a sneak peek of a beta feature that WILL be a huge improvement to android when its finished. Until then you can flash a stock ROM with ART added. You don't need to wipe data or reset up apps
 
Doesn't flashing ANY ROM require rooting and custom recovery? That is what I'm trying to avoid. Doing that would require a wipe because it will boot loop if you dirty flash. And rooting/flashing would break OTA updates making the next upgrade a pain in the butt which I bought a nexus to avoid entirely. As for it being experimental, I thought that was the point of including it as a 'developer option' right? Seems foolish to not include it with the rest of the 'experimental' options!
 
nickdalzell said:
Doesn't flashing ANY ROM require rooting and custom recovery? That is what I'm trying to avoid. Doing that would require a wipe because it will boot loop if you dirty flash. And rooting/flashing would break OTA updates making the next upgrade a pain in the butt which I bought a nexus to avoid entirely. As for it being experimental, I thought that was the point of including it as a 'developer option' right? Seems foolish to not include it with the rest of the 'experimental' options!
Click to expand...

Flashing going from one stock ROM to another stock based ROM with ART wouldn't require a full wipe

you'd always be able to dirty flash the updated ROM on top faster than you'd get the OTA
 
I wonder if it's a chipset issue(or at least they just want to test it on Qualcomm first). Notice all the devices running it have Qualcomm chipsets.
 
For an experimental feature it feels pretty good. Ive been running it daily since writing this topic.
The main problem is that some apps wont work with it but the good ones are catching up. Tibu now works with it and the Xposed Framework dev' is probably hard at work rebuilding his app :beer::)
 
Flashing a ROM still requires root, and a custom recovery. that would still break OTA updates. having a Nexus then at that point would be worthless. i might as well just turn a Nexus 10 into a Galaxy Tab 3 but with a better screen.

He ain't officially on KK but like the rest of us with Samsungs we had to do the 'root and flash' thing to even upgrade the phone to Android 4.4. that is a big pain as there are tons of iterations of the GS3 and not all the ROMs work on all the iterations of the S3. a GT-i9300 ROM won't work on a VZW SGH-i535 for example. either way i like the iOS-easy OTA upgrade method which is why i bought a Nexus tablet, as it's the only thing Android has comparable with the iPhone/iPad as far as being stock and getting upgrades as they are released, and without the fragmentation issue and carrier bloat. i suppose when i'm due for an upgrade i'll get a Nexus 5 to save myself the pain of rooting. i'm just worried that at the last second, Google pulls the plug on ART and we never get it on the Nexus tablets, which really could benefit from it.
 
nickdalzell said:
Flashing a ROM still requires root, and a custom recovery. that would still break OTA updates. having a Nexus then at that point would be worthless. i might as well just turn a Nexus 10 into a Galaxy Tab 3 but with a better screen.
Click to expand...
Root and custom recovery does not break OTA's...

Certain things you do after root can break it.
 
i thought the biggest disadvantages of root would be broken OTA updates? i thought that only worked on unrooted devices? if there is a way to do this and still benefit from OTA i'd go ahead and wipe/root/flash my 7 at least, i have nothing to lose on it as everything i run on it is cloud-based anyway. but i don't want to find out at the last second that i can no longer upgrade it easily and i need to flash ROMs to get upgrades.
 
You must log in or register to reply here.
Back
Top Bottom