Highly recommend enabling ART.

[anon5664829]

ART work fine with rooted phone or custom kernel. Don't know what you're talking about. I can prove it.

You need to use odexed gapps.

I didn't flash a custom Gapp at all. I assume the Gapps it came with are already odexed...

EDIT: It seems the problem was caused by Xposed framework. Got ART again now.

Posted via Android Central App

 

[anon5664829]

Re: Google Nexus 4 - Highly recommend enabling ART.

Why does it add significantly to the size of apps? Some of my apps doubled in size.

Possibly since its compiling things before you run them and may create more files for that. Sorry this is deep stuff I don't understand at the moment all I know is it is a new run time which runs things for the app as soon as it is downloaded, it's in certain cases faster then dalvik and also better for battery.

Posted via Android Central App

 

[Greg C]

Re: Google Nexus 4 - Highly recommend enabling ART.

Possibly since its compiling things before you run them and may create more files for that. Sorry this is deep stuff I don't understand at the moment all I know is it is a new run time which runs things for the app as soon as it is downloaded, it's in certain cases faster then dalvik and also better for battery.

Posted via Android Central App

Thank you Chetan for taking the time to answer.... makes sense.

 

[Fearless Freep]

Re: Google Nexus 4 - Highly recommend enabling ART.

Why does it add significantly to the size of apps? Some of my apps doubled in size.

Here is the layman explanation courtesy of Android Police:

ART, which stands for Android Runtime, handles app execution in a fundamentally different way from Dalvik. The current runtime relies on a Just-In-Time (JIT) compiler to interpret bytecode, a generic version of the original application code. In a manner of speaking, apps are only partially compiled by developers, then the resulting code must go through an interpreter on a user's device each and every time it is run. The process involves a lot of overhead and isn't particularly efficient, but the mechanism makes it easy for apps to run on a variety of hardware and architectures. ART is set to change this process by pre-compiling that bytecode into machine language when apps are first installed, turning them into truly native apps. This process is called Ahead-Of-Time (AOT) compilation. By removing the need to spin up a new virtual machine or run interpreted code, startup times can be cut down immensely and ongoing execution will become faster, as well.
[...]
fully compiled machine code will usually consume more storage space than that of bytecode. This is because each symbol in bytecode is representative of several instructions in machine code. Of course, the increase in size isn't going to be particularly significant, not usually more than 10%-20% larger. That might sound like a lot when APKs can get pretty large, but the executable code only makes up a fraction of the size in most apps.

 

[Greg C]

Re: Google Nexus 4 - Highly recommend enabling ART.

Here is the layman explanation courtesy of Android Police:

Very easy to understand. Thanks!

 

[anon5664829]

Re: Google Nexus 4 - Highly recommend enabling ART.

Here is the layman explanation courtesy of Android Police:

Very easy to understand. Thanks!

I was kinda right?

Sent from my Nexus 4 using Mobile Nations mobile app

 

[Greg C]

Re: Google Nexus 4 - Highly recommend enabling ART.

I was kinda right?

Sent from my Nexus 4 using Mobile Nations mobile app

Lol... yes... YOU were right as well!