yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Q&A, Help & Troubleshooting] WarRaven:
I find chrome scrolls smoother with ART. Idk placebo maybe.

WR

Sent from my Nexus 5
[Nexus 5 Q&A, Help & Troubleshooting] maxpower7:
I find that just about every app scrolls smoother with ART. It's definitely not a placebo effect. I've gone back to Dalvik a couple times, and it always amazes me how scrolling in general is more stuttery (relatively, of course - it's still better than just about any other phone). It's especially noticeable in Chrome and Facebook. On ART, everything is just about perfect.
[Nexus 5 Q&A, Help & Troubleshooting] Enddo:
i think ART definitely handles 'lists' of items better. so like blog posts, facebook timeline stuff, etc will always come out ahead on ART. from loading, aligning, and scrolling
[Nexus 5 Q&A, Help & Troubleshooting] emperorfra:
I m using ART on stock ROM and everything seems to run fine :)
[Nexus 5 Q&A, Help & Troubleshooting] Laggalot:
can anyone explain why art doesnt work with gravitybox? will it in the future?

Gesendet von meinem GT-I9505 mit Tapatalk
[Nexus 5 Q&A, Help & Troubleshooting] MrBelter:
Well since going back Dalvik i have noticed no difference whatsoever my Nexus 5 feels exactly the same as it did when i was running ART.
[Nexus 5 Q&A, Help & Troubleshooting] Re-FleX_NL:
I think ill stick to Dalvik @ the moment, ART is still in Beta and some apps just dont work... Think the time we all are gonna use ART is near becease they implemented it in 4.4.

Maybe in 5.0 ART is a standard :)

1 negative point is that youre apps grow in used space... i have a 16gb nexus model and my storage is valuable ;)
[Nexus 5 Q&A, Help & Troubleshooting] meangreenie:
you guys know that dalvik/art VM only run Java code right? or at least goggles ripped off mobile version of it.

placebo is a powerful effect
[Nexus 5 Q&A, Help & Troubleshooting] wideasleep1:
Oh puhleeze.
[Nexus 5 Q&A, Help & Troubleshooting] meangreenie:
please what? change reality?

ever wondered why dalvik runtime counts for so little of the total score in the antutu test
[Nexus 5 Q&A, Help & Troubleshooting] Blackbox421:
I'm also in ART since day one. Is there really a difference in the battery life?

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Q&A, Help & Troubleshooting] andQlimax:
there is still a java VM

but with dalvik the "executable" code is generated and executed at runtime, with ART the "executable" code is generated when the app is installed so the execution of the app should be faster since there are less operations to do...please search something about it

ART is proved to be slighty faster, and should be of course more faster when it will be finished.
[Nexus 5 Q&A, Help & Troubleshooting] paradoxiumwind:
My apps loaded instantly anyway with stock dalvik, but I switched to ART and all my apps still work fine, I don't know if I can notice any difference in speed though, because it was already very fast. Cataclysm ROM with element kernel.
[Nexus 5 Q&A, Help & Troubleshooting] x8hsu:
ARTing! In my exp. it's faster and drains less power. Although it's only under test for now, ART is absolutely the future.
[Nexus 5 Q&A, Help & Troubleshooting] PhilipTD:
Is the Compatibility List accurate? It has listed as "Not Working": Google Play, Nova Launcher, Flash Player, barcode scanners, Google Wallet, Google Text to Speech, Gallery, MX Player, Pandora, screenshot, Titanium Backup, Whatsapp, Widgetlocker, and YouTube. I find this hard to believe.
[Nexus 5 Q&A, Help & Troubleshooting] Laggalot:
google play works and nova is what iam using since months! so from my experience they work

Gesendet von meinem GT-I9505 mit Tapatalk

edit:whatsapp+ and screenshot do work aswell ^^
[Nexus 5 Q&A, Help & Troubleshooting] bunga bunga matze:
I switched to ART for a over a week, the following apps are working on stock rom 4.4.2. without any problems!

Google Play, Whatsapp, Barcoo (Barcode scanner ), Youtube, Gallery and making screenshots!

(I've tested by myself)...:D
[Nexus 5 Q&A, Help & Troubleshooting] PhilipTD:
That's great news.

Do you know if there's a reliable list of incompatible apps somewhere?
[Nexus 5 Q&A, Help & Troubleshooting] b.spec:
I was running Dalvik + moto x patch and was really enjoying the performance (not sure how much the patch helped, but oh well). Recently switched to ART a few weeks ago and I definitely notice an improvement in speed. Not a huge difference, but the overall performance, especially when switching between apps, is just quicker.

In terms of battery life, it's more or less the same for me. Obviously it depends from person to person, but I'm still getting around 5 hours SOT so I'm not complaining about that.

A little sad I can't try Xposed Framework + Gravity Box, but for now I'm sticking with ART.
[Nexus 5 Q&A, Help & Troubleshooting] bunga bunga matze:
unfortunately, no.....:rolleyes:
[Nexus 5 Q&A, Help & Troubleshooting] pgptheoriginal:
MX Player is working, too! That list is outdated ;)

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Q&A, Help & Troubleshooting] imablackhat:
I've been using art for about a week. Notice its more snappy. Haven't ran into any compatibility issues yet.
[Nexus 5 Q&A, Help & Troubleshooting] TarunN5:
GO Launcher dosent seem to work on ART
[Nexus 5 Q&A, Help & Troubleshooting] Blackbox421:
I'm also on ART. Everything is Wirkung so far, even whatsapp etc.

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Q&A, Help & Troubleshooting] s00000000000ka:
Just in time

ART FTW

no problem
[Nexus 5 Q&A, Help & Troubleshooting] Dodgexander:
I too had problems installing apps like Titanium Backup and Swype keyboard.

But when I did a fresh install, changed to ART straight away and rebooted. They then installed fine.

Seems for me at least the "app not installed" problem with ART was linked with something else.
[Nexus 5 Q&A, Help & Troubleshooting] jdawg2485:
So what about root? Does it break root? Does xposed installer work yet?
[Nexus 5 Q&A, Help & Troubleshooting] :
Hi,

It does not break root, whatever ART or Dalvik runtime...

Xposed is still not compatible with ART runtime, if you use Xposed and switch to ART, Dalvik runtime will be automatically set again after reboot to avoid bootloop.
[Nexus 5 Q&A, Help & Troubleshooting] jdawg2485:
Ok thank you for the info :)
[Nexus 5 Q&A, Help & Troubleshooting] jdawg2485:
Ok so I uninstalled Xposed uninstaller (but not the modules), switched to ART but after reboot it switched back like you said. Do I have to uninstall all the modules from my phone first?
[Nexus 5 Q&A, Help & Troubleshooting] :
You need to go into Xposed Framework, Framework-> Uninstall (it will restore the original file "app_process") then reboot. Once rebooted switch to ART again...
[Nexus 5 Q&A, Help & Troubleshooting] jdawg2485:
Awesome, thanks again dude!
[T-Mobile Samsung Galaxy S 4] HampTheToker:
I'm sure you've seen the commercials. That "knock knock" lockscreen seems purdy nifty, so I started wondering how difficult it would be to port. Is anyone interested, or am I the only one?
[T-Mobile Samsung Galaxy S 4] cryptic3:
Never seen the commercial going to check it out on YouTube.. But it is cool there will be one more person who wants it
[T-Mobile Samsung Galaxy S 4] HampTheToker:
I like the double tap approach. Not sure if I'd prefer it, but I'd love to try it out.
[Verizon Samsung Galaxy S III] mikestrong19:
I am relatively new to the world of rooting and ROMs, but I have successfully installed CM10 on a previous Samsung phone, so I am decently literate.

I am currently attempting to install CM10.1 on my Verizon Galaxy S III (following the instructions on the Install CM for d2vzw page on the CM wiki), but I have reached an impasse at step 7. I was not aware that I had to put the VRALE6.bootloader.zip file on the SD card before starting this process, so I am now attempting to get that file onto my SD card either by sideloading through CWM or by pushing it to the SD card through adb. The issue is that CWM gives me an error (can't mount SD card) and adb doesn't recognize my device (I have tried installing and reinstalling various drivers for the past few hours). I enabled USB Debugging mode before starting the process, but I am only able to get into Download and CWM modes right now (if I don't do the Download Mode or Recovery Mode key combination, I am stuck on the Galaxy S III screen). Am I bricked at this point, or is there a way to get VRALE6.bootloader.zip onto my phone and continue with the ROM process?
[Verizon Samsung Galaxy S III] mikestrong19:
It is important to note that I formatted the SD card before starting this process because I wanted enough space to put the Cyanogenmod file on it. However, I think I may have formatted it generically rather than into FAT-32. Could this be the issue?

I am going to pick up a microSD card reader today in order to flash the SD card to FAT-32 and put the CyanogenMod file on it.

I am getting 5 errors upon startup of CWM (E: Can't mount /cache/recovery/command, can't mount /cache/recovery/log, etc.). When I try to mount the SD card or external SD card, I get E: Can't mount /sdcard/
[Verizon Samsung Galaxy S III] vortex3811:
Same issue with sd card not mounting.

I'm having somewhat of the same issue. I've tried both Clockwork recovery and TWRP and have the same issue.

Should have mentioned that i still have access to the stock rom and can use my phone just fine.

I some how got Clockwork mod recovery to work using the Rom Manager pro App.

I wish i had been paying better attention to what i was doing but i know i updated CWMrecovery from in rom manager and chose to install my chosen rom with that.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
My suggestion is to start over completely. There is a much easier way to do this.

My suggestion is to flash one of the rooted stock ROMs through Odin. There's a thread in android development that has rooted stock. Then when that's done boot up your phone. If it bootloops wipe data. Then use Ez-Unlock 1.2 app to unlock your bootloader. Make sure it's 1.2. Now use GooManager to flash TWRP. You are done! This is probably the easiest way to do this.

Thread: http://xdaforums.com/showthread.php?p=33948598
[Verizon Samsung Galaxy S III] mikestrong19:
I am not familiar with TWRP, so is the process the same for flashing CM (putting CM zip file on sd card and going to install from SD card in TWRP)? Are there any additional steps beyond this?
[Verizon Samsung Galaxy S III] mikestrong19:
I am following the directions in the thread linked above to root and install TWRP. So far, I have the rooted stock ROM running fine, but I can't get TWRP to work. I downloaded Goomanager and attempted to get TWRP using the Install Openrecovery Script option. However, it said that it couldn't find a recovery for my device. I also tried to use the adb method, but nothing happened after I put in the commands. I even tried to flash the latest TWRP .tar file from their website using Odin, but it keeps failing. Is there any way to get TWRP on my phone?

EDIT:Whoops, I skipped over the EZ-Unlock step. Now everything works. Thanks for the help, Sandman!
[Verizon Samsung Galaxy S III] Wh1t3Rose:
No problem bro. Glad you are all fixed up :)
[Verizon Samsung Galaxy S III] mikestrong19:
Alright, maybe I'm not quite fixed up yet. I have TWRP installed and I can go between TWRP, download mode, and the normal stock rooted ROM fine. However, I cannot get to the SD Card in TWRP in order to install CM. TWRP gives me the following errors upon booting into recovery:

E: Unable to find parition size for '/boot'

E: Unable to find parition size for '/data'

E: Unable to find parition size for '/recovery'

Updating partition details:

E: Unable to mount '/system'

E: Unable to mount '/cache'

E: Unable to mount '/cache'

E: TWFunc: :Copy_Log - - Can't open destination log

E: Unable to mount '/cache'

Upon trying to go to Install, I am unable to select the external SD card, and an additional error appears when I attempt to touch Micro SD Card (E: Unable to mount '/external_sd').

I guess I could try to sideload the CM zip file through adb, but I would rather fix the SD card for future use. I have been researching and working on the SD card for the better part of today, to no avail. I am pretty sure the issue is in the formatting of the SD card (it appears to be RAW rather than the required FAT32 for CM), but I cannot format the SD card into FAT-32 no matter what I try (both Windows and 3rd party formatting tools). They all say that the SD card is either write-protected (I have already checked the read/write switch on the side of the SD card adapter) and/or the format cannot be completed. I have tried both my old SD card that I have kept for a few phones (an 8GB Samsung microSD card) and a brand new Sandisk 8GB microSD card, both of which will not work.

I am able to transfer files to the SD card with no issue (with both ADB and through dragging/dropping in Windows), but I cannot install from SD in recovery.

Does anyone have a solution to allow me to install CM on my phone?
[Verizon Samsung Galaxy S III] Wh1t3Rose:
Download root checker from the play store. Make sure you are rooted
[Verizon Samsung Galaxy S III] mikestrong19:
Yes, I do have root access. I think the problem lies somewhere in my SD card.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Do you have another computer to try formatting the sdcard with? And you said that you receive the same errors when trying to reformat the new 8 GB sdcard as with your other sdcard which is formatted to RAW?
[Verizon Samsung Galaxy S III] mikestrong19:
I do have access to another computer, but I ran out of time and patience yesterday. I will try it when I get home later today. And yes, both cards are RAW (even the new one) and I can't get either one to format or work in TWRP.
[Verizon Samsung Galaxy S III] mikestrong19:
So it appears the the issue with formatting was due to my computer's drivers (even though I installed the latest Samsung USB drivers) and not the SD card. I was able to format the SD card to FAT32 on another computer and put CM and GAPPS onto it. When booted normally into TouchWiz, the phone sees the SD card fine. However, I still get the same "Can't mount external SD card" error as well as the others previously listed when I attempt to install a zip from recovery. I even tried to sideload the ROM from ADB, but it still didn't work.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Which version of CWM and also TWRP are you using?
[Verizon Samsung Galaxy S III] mikestrong19:
And the problems keep rolling in. I was able to mount my SD card and get rid of the TWRP errors by installing a modded TWRP 2.6.0.0 from this thread (http://xdaforums.com/showthread.php?p=44277901). However, when I go to install CM (cm-10.1.3-d2vzw.zip), I get the following error:

assert failed: getprop("ro.product.device") ==

E: Error executing updater binary in zip '/external_sd/cm-10.1.3-d2vzw.zip'

Error flashing zip '/external_sd/cm-10.1.3-d2vzw.zip'

Updating partition details

I did a factory reset before attempting to install this, but I did not format data or do anything else.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Well, that is for the Sprint S3 my friend. We can't interchange recoveries between the different S3 models to flash roms. You may want to ask Kennyglass123 or any of those other guys if they can make a change for the VZW S3 for you to test it out.
[Verizon Samsung Galaxy S III] mikestrong19:
Sounds good. I think the problem has been isolated to being something with needing a modded TWRP. I tried using an older, non-modded TWRP (2.5.0.0), which didn't work.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Would you mind trying this soft brick fix? If I'm not mistaken, I believe you're experiencing this same issue--excluding the Sprint TWRP issue you just mentioned. You will need to flash your VZW custom recovery either through GooManager, Rom Manager, or Odin btw.
[Verizon Samsung Galaxy S III] mikestrong19:
I can still get between the stock rooted ROM, download mode, and recovery mode fine, so does that mean I am still soft-bricked and should try this?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Yea, because you are still receiving these errors right?

This soft brick fix is an attempt to correct the /system and /data errors.

Edit: Oh great, none of the links work. I'll see about finding alternate links.
[Verizon Samsung Galaxy S III] mikestrong19:
I am still getting the errors, so I will try this. And I already have the VRALEC and VRALF bootchains, as well as the rooted stock file from when I first tried to install CM from the CM wiki instructions, so don't worry about getting new files.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Let me know how it goes. Your bootloader will be locked so you can unlock it using EZ Unlock v1.2
[Verizon Samsung Galaxy S III] mikestrong19:
The two bootchains flashed fine, but Odin gets stuck on Setup Connection (and eventually fails) when attempting to flash the stock rooted ROM. Kennyglass told me that the issue is with the phone, and that a fix (like the one for Sprint I tried) for Verizon has yet to be released. At this point, I will probably use the stock rooted ROM with Nova Launcher to at least avoid using the atrocity that is TouchWiz, but if a solution is found for flashing AOSP ROMs on Verizon, I will definitely try it. Thanks for your help!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Hmm, that really is unfortunate. It fails even with all three settings checked in Odin? It fails even after a second try? Hope you can find a fix if you do keep trying at another time.
[Verizon Samsung Galaxy S III] mikestrong19:
Well, it worked now. All I did was restart my phone and run Odin as an administrator. Again, thanks for taking the time to help. Hopefully, the resident developers here (who are all much smarter than I) will be able to figure out how to get AOSP ROMs working on Verizon's GS3s. In the meantime, Nova Launcher will have to suffice.
[Verizon Samsung Galaxy S III] CNexus:
I will post a modded recovery for you to flash shortly

Note that you will not be able to flash this like normal because it will be in .img format...however, I can suggest using my FlashTool to flash it fairly easily

I will post a link to it when it's ready, shouldn't be long
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Glad it worked! AOSP, once its running for you, isn't too bad. Everyone has their preference. I encourage you to give it another go with official CM cuz from what I see, it was more a run of bad luck. You have this thread for a reference point to get back to normal you know? If not, try moving onto another TW rom such as Bonestock if you want to stick to a more streamlined stock rom.
[Verizon Samsung Galaxy S III] mikestrong19:
Two things:

1. I am now stuck on the 4G LTE screen (great......) after having put the stock rooted ROM via ODIN on. EDIT: Nevermind, I just did a factory reset from stock recovery and it worked. All of my (seemingly endless) problems are solved.

2. I am confused as to whether all Verizon GS3s are unable to install CM and other similar ROMs, or if it was just my phone.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Its just something that happens. Your issues would have prevented you from flashing a TW rom as well and that was not an AOSP issue. You were unable to even flash any rom, let alone CM to begin with.
[Verizon Samsung Galaxy S III] mikestrong19:
So from what I gather, the only solution to this is to wait for a fix from the XDA community similar to the Sprint GS3 fix (i.e. there is nothing more that I can do)?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Idk what's going on with Sprint S3 but I'm saying you should try again to flash CM once you have unlocked your bootloader and installed a custom recovery again. If it happens again, then you should see if the recovery that Cnexus may post will help you. When Hero wrote that soft brick thread in August 2012, he went on to develop a very popular rom. That soft brick thread I linked to is a year old. Your issue is not common but it does happen. Idk if you'll have the same issue again but you should try now while all this info is still fresh.
[Verizon Samsung Galaxy S III] CNexus:
It looks like you're good to go now, just a problem with the phone that you fixed.

The Sprint S3 only needed a modded recovery for the newest phones which were using an updated kernel

So do as advised above and try to flash CM again and we'll work from there.
[Verizon Samsung Galaxy S III] mikestrong19:
Should I flash the latest stock TWRP or wait for your modded version?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Latest TWRP.
[Verizon Samsung Galaxy S III] mikestrong19:
I unlocked my bootloader using EZ-Unlock 1.2 and flashed TWRP 2.6.3.0 with Odin, but I still get the errors in TWRP. I would assume the only thing to do at this point is wait for CNexus to post his Verizon GS3 fix.
[Verizon Samsung Galaxy S III] mikestrong19:
CNexus: If you do end up making a TWRP mod (I know you are busy and probably have more important things to worry about, so I am in no rush), should I look in this thread or in the Verizon GS3 forum for it?
[Verizon Samsung Galaxy S III] mikestrong19:
Any guidance at this point? The problem definitely lies in recovery mode (the modded TWRP for Sprint found my SD card fine), and I have run out of options now that stock TWRP again failed. The one thing that I could try is to use the new CyanogenMod Installer (http://wiki.cyanogenmod.org/w/CyanogenMod_Installer), but I don't know if that would work or possibly even make things worse.

EDIT: Nevermind, CM Installer isn't supported for the d2vzw.
[Verizon Samsung Galaxy S III] jackpot08:
i still have this problem. i cant flash cm11. it says failed. what should i do?
[Verizon Samsung Galaxy S III] mikestrong19:
Bump
[Verizon Samsung Galaxy S III] mikestrong19:
I would just like to update this thread for anyone who may find this via forum search, Google, or otherwise: the solution to the "Can't Mount" errors in TWRP or CyanogenMod is to download the latest non-touch version of CWM from ROM Manager. This removed the errors and I was able to install CM and GAPPS without any problems.

Thanks to everyone for their help.