1. Are you ready for the Galaxy S20? Here is everything we know so far!

ART vs DALVIK Runtime

Discussion in 'Android Devices' started by Maine Coon, Jul 17, 2014.


ART vs dalvik runtime

  1. ART is faster

    16 vote(s)
  2. dalvik is faster

    4 vote(s)
  3. same

    6 vote(s)
  4. what are you talking about

    3 vote(s)
  1. rushmore

    rushmore Extreme Android User

    How is something that has nominal improvements with both battery life and performance, but displaces 25% storage positive? Not seeing a net positive here. Seeing all negative and curious what diabolical ulterior motive ART really has in the grand scheme of things..... ;) :)

    1. Download the Forums for Android™ app!


  2. hilmar2k

    hilmar2k Android Expert

    Its more like 10-20%, depending on the app.
  3. stormtrooper

    stormtrooper Lurker

    After switching to Art I did notice apps opening faster but my phone froze like 3 times just simply swiping from screen to screen. But it has been a day and so far no freeezin and apps open super quick. However I had this hacked Pandora (unlimited skips) and stopped working after switching to art and wouldn't let me download since. But so far I'm kinda happy with art lol
    -LG g3 at&t
  4. meganoobie

    meganoobie Well-Known Member

    So, I have some experience now. I replaced my original LG G3 on vacation. I had it in my pocket with my S4 on a really aggressive roller coaster and the screen got scratched. As a side note, it had one scratch that you had to really look to fine, but once I knew it was there, it was impossible to not notice. The S4 took a massive beating, 50 scratches. Not sure if it was positioning or just better glass, but it's a work phone anyway, couldn't care less.

    Anywho, I swapped out at Best Buy and didn't have the battery for the ART switch, so I left Davlik for the remained of the week. My observations are that ART is clearly faster, AND I'm getting better battery life. My storage went from 21gb free to 19.8gb with 221 apps, not a big penalty IMO.

    I'm leaving it on ART for now
  5. has anyone switched to ART? if so, how do you like it? I'm on the fence of switching. i heard its great but then hear about certain bugs. i can live with some but the one that i hear a lot is battery drainage. i love my g3's battery life and if it were to deplete a lot quicker, that would be a downfall for me. any suggestions?
  6. Crashumbc

    Crashumbc Android Expert

    its still beta, so there are some bugs and some apps have issues.

    I haven't switched because I'm on VZW which seems to have massive issues with it. Crashes battery drain etc... Most of the really bad stuff I've heard is all from VZW people.
  7. meganoobie

    meganoobie Well-Known Member

    I switched and no bugs whatsoever, Sprint. If anything, I feel like the battery is a bit better. It's reversible as well, so no risk.
  8. hilmar2k

    hilmar2k Android Expert

    It's a non-starter on Verizon.
  9. HuskyKMA

    HuskyKMA Well-Known Member

    I'm on Verizon and I tried turning ART on. Don't do it! Almost bricked my phone. A few seconds after starting up it would become unresponsive. Finally after about a dozen times trying, the phone remained working long enough for me to get back into the developer options and switch it back to DALVIK. Works fine now but I thought I killed my shiny new phone there for a little while.
  10. pastafarian

    pastafarian Pâtes avec votre foie

    I ran ART on my Sprint G3 for a week or so with no issue. It is maybe a teeeeeny bit faster with no noticeable battery impact better or worse. Frankly, I didn't notice much of a difference at all. Unfortunately, ART doesn't play with xposed (yet) so once rooted, it was back to dalvik for me.
  11. HarvesterX™

    HarvesterX™ Newbie

    In the past I've been a part of many message boards where developers have complained about receiving 1* ratings due to lack of ART compatibility and understood where they were coming from. Developers shouldn't need to modify their code at all (most of them, more on the later) in order to be compatible with ART once ART becomes the standard.

    Things hage changed now however as recent commits show that Google has now deleted all libdvm (DALVIK) files from AOSP source. This is as much of a red flag as any for developers because if their apps are still not working with the latest updated ART runtime then they need to seriously begin looking through their code.

    As a developer myself I can tell you that ART is far less forgiving when you comes to bad coding habits and poorly written code and if issues are still persisting there's a good chance there's something in the code causing the issues. With out said ART as far as we know isn't in release mode yet so there's still a shot that there's something going on with the runtime itself..

    An example is the Facebook app. I know it has caused many people yo enter into a bootloop after installing it. Now it's installable and seems to begin to load juwt fine but then hangs at the splash screen. Considering that Messenger app is working fine, and that the Facebook developers have had plenty of time optimizing the their code (early to mid Facebook releases were horrible on battery life) and I'd expect the Facrbook app to launch just fine, and it almost does. Maybe if I tried it a few times it might open..who knows. This seems like an ART issuez but then again which knows. All apps that also allow you to log into Facebook (such as many games) will also become nonrespsondent if you attempt to log in...at least the ones I've briefly tried (Crazy Taxi for one).

    That could be an ART runtime issue still, or it could be caused by what I mentioned I would get into later. Besides poorly coded apps, the other only reason app devs will have to edit their source is if they rely on old DALVIK runtime hacks in order to accomplish something. Like I said, ART is less forgiving. Perhaps the Facebook API (particularly seems to be the login procedure) relies on a DALVIK hack or similar?

    Other than Facebook (which will work soon enough and might very well be working for others, I'm running a G2 with a G3 ROM), I haven't ran into other issues. Chaos Rings 2, a Square Enix game (and pretty awesome too if you like their games) didn't work at first and just wouldn't load. After a reboot it works fine. Unsure about my FF games by SQ because I haven't downloaded them to test yet. I know previously they haven't been working so I'll probably test them today.

    I did have to remove Xposed framework of course but that was more of a blessing. That's the lazy way developers and modders to get what they want. To others it's the only way they know how which is cool, but luckily I only used it for modding my navigation bar and my status bar which is easily done with apktool mobile.

    I also used the FakeWifi module for Modern Combat 5 because Gameloft doesn't believe that anyone uses unlimited data anymore and that everyone had access to WiFi. Well apktool was used again to edit the smali and return true in the connectivity calls (0x1). Finally In had root cloak for apps that won't run while rooted, but I don't often use any if these apps and if/when I do I'm sure it won't take too long to find the appropriate method in the source in set it to return 0x0 (false, if example the method is named check root() ).

    I wish the Xposed dev would release the updated framework that he claims he has that is ART compatible. I understand he wants to wait until ART is stable and the standard, but the latest ART runtime has been nothing short of stable and there no longer is any DALVIK support in AOSP...Not everyone knows how to decompile and mod what they need and it's an awesome tool. Oh yeah...removing the ads from YouTube..I used a module for that as well, but now I just added the as URLs to the host file (using adaway since the host is too large to even edit using the phone, at least on all the editors I've tried).

    I have encountered one anomoly though. I often use benchmark tools such as LinPack and the CPU test in Quadrant before and after making cpu/kernel changes to get an impression on how much of an impact my changes have made. I don't use benchmark apps to bench certain ROMs or devices as that's a pointless endeavor.

    Benchmark apps ARE useful though in determining the differences before and after making certain modifications. Here I was benching the differences in CPU performance between DALVIK and ART, and the two benchmarks I listed are good choices because they don't rely on the NDK (native development kit...ART runtime compiles everything ahead of time into native code so you won't see any changes most of the time and sometimes ART might bench lower here).

    My test was set up so that for both DALVIK and ART mode, I used the same kernel settings and kept all other settings constant. I would test after a fresh reboot after letting Android settle in for about 5 minutes. Tests made by others have already shown that in this category ART should see a fairly significant (at least noticeable) increase over DALVIK, with stating gains of up to 100%. The benchmark app for the 100% claim wasn't given, but this information was gathered from reliable sources and should be the case.

    I ran Linpack 10 times in each mode and my results were as follows (I'm just reporting the ranges for each instead of a single average just so the fluctuation range can be seen). In DALVIK I was seeing scores of 875-1050 megaflops. With ART I was getting 250-500 megaflops. The actual scores themselves don't matter if you attempt this test yourself. If you have a G2 and score only 700 megaflops that doesn't mean jack..I was running in a fairly high performance mode...we aren't benching actual devices or ROMs but what's important to us is the differences between our two means and not the values themselves.

    ART should have given us higher figures (higher is better when comparing megaflops) given past tests done by others. This has me scratching my head a bit because in no way does the OS feel slower at all, in fact it feels like an OS should..smooth and fluid and any lag I previously saw is basically gone (G2 lags very little anyways). I can also report that I'm running at cooler temperatures than before suggesting that less work is being done by the CPU which is what I'd expect. And as expected I'm not seeing ant gains in performance in NDK reliant apps such as 3DMark (Icestorm). In fact the score may have dropped a little or it could have just been due to natural deviation. I didn't run the teat enough to determine which...just wanted to be sure everything was on par.

    If anyone else with a G2 or a G3 wishes to repeat this experiment and add their data to it, it would be most appreciated. Of course the ROM you're running will have a factor because the ROM will determine which version of the libart.so runtime you're running. The CPU test in Quadrant is also a good non NDK test to run. I have ART scores for it but forgot to run it before switching and don't feel like waiting 20 minutes to convert everything back to ART after switching back to DALVIK. Not today at a least :)

    I'm not quite sure what's happening with Linpack because that's inconsistent with others' finding. My Quadrant CPU score did seem quite high from memory though. *shrugs*

    That's been my experience with ART. Long post indeed but ART is new, it is replacing DALVIK, and the more information the better. You'd also be amazed at some of the tech illiterate "devs" on XDA. Not naming anyone particularly but at least the goods ones stand out from the bad . and don't always go by just one single source or information over there unless you already have confidence in the developer. Xposed framework has also brought out a lot of jank from people whipping up quick mods, offering them for free, only to find that most of the features you needed you have to make an IAP for. If you run across these, report them to XDA mods so they can investigate and then shut the thread down. XDA is meant to be an open developers forum,... Not a marketing center for devs (no matter how good or bad) to sell their apps. Donations are always accepted and is the practice. Not "devs" accepting donations as well as cash from IAPs. Help keep the site the way it's designed.

    Lol sorry bout the rant. Just a lot of that going on...

    (VS980 BTW, Verizon G2..not a G3...)
    GTCC and lunatic59 like this.
  12. rushmore

    rushmore Extreme Android User

    Simply put, Dalvik to ART is a systemic change to the framework with its own specific protocols and operational requirements. It is perhaps too much of a change too soon until stock roms also adhere and all the apps as well.

    I still do not see the value add to it. Only less storage and in some cases depending on the app and the way data libraries are accessed, worse performance. Neither Dalvik or ART are truly "one size fits all". That premise is one of the "grand illusions".
  13. StrifeJester

    StrifeJester Android Enthusiast

    For everyone that is posting about ART being faster you realize a lot of this is in your heads. The current applications are minimal that can take advantage of ART. The core Android apps may be slightly faster but there should be almost no difference and in some cases should make dalvik optimized apps run slightly slower. Until 5.0 starts hitting devices and Google gives the complete ax to dalvik a lot of devs will not do anything to update their apps.
  14. meyerweb

    meyerweb Android Enthusiast

    Why not? Dev's have had to update apps to be compatible with numerous Android version changes. Lots of apps written for Gingerbread wouldn't run on ICS without updates. That's life. If Google had to maintain backwards compatibility with all prior apps we'd have next to no progress at all.

    And it's not just Android. Try running a Windows 3.1 or Windows 95 app on Windows 8. Or an app written for iOS 3 on iOS 8. Other than very simple apps that don't make much use of the OS's services, it's not going to happen.

    The idea that you can have progress without pain is absurd.

    Running a benchmark that hasn't been written with ART in mind may, or may not, tell you anything useful. Given your results, I'd say the issue is the benchmark, not ART.

    And the Xposed dev hasn't released his ART compatible version because it's compatible with the Android L version of ART, which is very, very different than the KitKat version. It wouldn't run on KitKat ART any more than the current version does. Google has been very up front that the current version of ART is experimental, and nothing more.
    jammychap likes this.
  15. lunatic59

    lunatic59 Moderati ergo sum

    ftfy ;)
  16. meyerweb

    meyerweb Android Enthusiast

    Except even Microsoft doesn't really do that. They do it more than Google does, but there are plenty of old apps that don't run under Win 8, or even Win 7. Some run in "compatibility mode," but that really isn't very compatible either.
  17. lunatic59

    lunatic59 Moderati ergo sum

    So true, but a good deal of criticism MS takes is for keeping a good deal of legacy code included in an OS release to try and accommodate those stuck 3 or 4 versions back.

    They're dedicated to keeping some of the people happy some of the time. :)
  18. Hrethgir

    Hrethgir Android Expert

    I switched to ART, but I was having stability issues, so switched back to DALVIK. Only time I've had issues was on ART, had random reboots and freezes, only times I've had to pull the battery.
  19. nickdalzell

    nickdalzell Android Expert

    Coming from Samsung it sure is a nice surprise to see the runtime select on stock software on the G3. Loving the phone even more now!
  20. jammychap

    jammychap Well-Known Member

    Trying Art now, gonna take a while to start, optimising app 5 of 333 lol
  21. jammychap

    jammychap Well-Known Member

    After restarting with art I experienced lag of the lag from lagville, temp had gone up to 38.6C, and battery saver kicked in, at that point I chose to try a quadrant test and scored only 7192, will try again once cooled off
  22. jammychap

    jammychap Well-Known Member

    Down to 30c tested again and scored 13848, I think it was faster on Dalvik as far as the benchmark results go, but phone seems to run ok so far.
  23. jammychap

    jammychap Well-Known Member

    switched back to Dalvik, waited for a load of updates to install cleared ram n tested again, now hitting 21720 on quadrant at 34c so clearly faster on dalvik, this is on stock unrooted 4.4.2.

    I also tested it on Antutu benchmark alongside my old GT-i9300 running Neatrom v8.0 n this is where things get weird.....................

    The G3 scored 30675 and was behind the S3 for most of the test

    The S3 scored 27731 but on quadrant the S3 scores 7732, how can they be so close on Antutu and so far apart on quadrant?

    Had a bit of a play n disabled a few things go I don't want, just managed a score of 35223, quite happy with that one.
  24. jammychap

    jammychap Well-Known Member

    Frozen out a few apps with TV and stopped loads from auto starting with clean master and now well happy with the speed on this rom.

LG G3 Forum

The LG G3 release date was June 2014. Features and Specs include a 5.5" inch screen, 13MP camera, 2/3GB RAM, Snapdragon 801 processor, and 3000mAh battery.

June 2014
Release Date
Similar Threads - ART DALVIK Runtime
  1. Pantsoffski
  2. Metatrans Apps
  3. App Update
  4. electricpunch
  5. App Update
  6. App Update
  7. SquiddyKat
  8. App Update
  9. zhornak
  10. mkmossop

Share This Page