| Good question. Obviously, some stuff must
be dealt with at runtime. I have not
studied
the code, but am guessing mmap is used.
But everything that can be dealt
with ahead of time
would hopefully be realized.
But, yes, something still is
resolved to make it work.
Does that mean it infringing the patent?
Link
Note that the link is three years old now, so it
may not be totally
correct or current.
Preparation
There are at least three
different ways to create a "prepared" DEX file, sometimes known as "ODEX" (for
Optimized DEX):
The VM does it "just in time". The output goes into a
special dalvik-cache directory. This works on the desktop and engineering-only
device builds where the permissions on the dalvik-cache directory are not
restricted. On production devices, this is not allowed.
The system
installer does it when an application is first added. It has the privileges
required to write to dalvik-cache.
The build system does it ahead of
time. The relevant jar / apk files are present, but the classes.dex is stripped
out. The optimized DEX is stored next to the original zip archive, not in
dalvik-cache, and is part of the system image.
The rules may
not be applicable if you have a rooted device.
---
You are being MICROattacked, from various angles, in a SOFT manner. [ Reply to This | Parent | # ]
| 
