Hi Somebody else was kind enough to send me an email about dexopts. Basically in some situation it is possible to already replace the byte code into optimized dex inside the apk. Documentation can be found in the dalvik documentation folter dalvik/docs/dexopt.html) but also (the same) here http://blogold.chinaunix.net/u3/116108/showart_2260593.html
Preparation There are at least three different ways to create a "prepared" DEX file, sometimes known as "ODEX" (for Optimized DEX): 1. 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. 2. The system installer does it when an application is first added. It has the privileges required to write to dalvik-cache. 3. 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.## precise GC ## 4. -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
