[G2 Android Development] raimondomartire:
Guys I reply to everyone so I hope to be usefull for all problem

Te rom it's odex last roma are deodex so some apk don't work because before rom update you don't have make wipe of dalvik-cache. Now you can go in settings/application or programm (search in your language) /search app with FC problem and wipe data. You can try also with titanium backup to delete dalvik-cache

Second error "update me apk" FC in new settings menu it's error of mine. I don't copy update me apk in system/app. (I dont have phone and can't test it :)) How solve it . Reflash zip file in download tab of this thread (where you have download rom) that I'll upload in 1 hour. You can download also from market

In weekend I'll publish new 3.0.1 to solve this problem

***

A lots of users tell me to explain difference between odex vs deodex.

What do the .odex files do?

All of your apps on your device are packaged as .apk files; these files are compiled from google source code and can interchangeably be viewed/thought of as a compressed folder (like a .zip or a .rar); and all of your framework components (well most…) are packaged as .jar files which literally stands for Java Archive (so again this can be compared to a .zip or a .rar).

When the android OS want’s to run your apps or utilize its framework components, it has to parse (read/interpret) the compressed data held within your .apk and/or.jar files. What the odex file structure aims to do, is to expedited this process by utilizing another file (.odex file) to compliment every.apk file (and .jar file); the odex file, includes the most critical data in an uncompressed format so the android os can quickly interpret that important information before parsing through the rest of the data held within the compressed .apk files (and .jar files). So subsequently, in an .odex file structure the .apk & .jar files don’t include all of the applications/framework-components data; Essentially, two files are acting as one; for your apps there are .apk files + their corresponding .odex file and for your framework components there are .jar files + their corresponding .odex file. This works nicely as an optimized file structure, except in the circumstance when the user want’s to theme; theming requires a modification to your .apks; the image files (.pngs) held within the pngs are replaced with different ones. However it is impossible to theme an application if it exists as two files. So that is why it is said you need to be DeOdexed in order to theme; DeOdexing is the process of re-bundling that uncompressed critical data (.odex files) back into your compressed .apk (& .jar) files, so that now all of the data is included in the .apk files necessary to run your applications without the presence of .odex files; in addition all the data is now included within the .jar files necessary to utilize your framework components without .odex files. In a DeOdexed file structure, there are no odex files present.

What are the benefit’s of DeOdexing?

Simple. To be able to theme a stock ROM.

Deodexing doesn’t speed your phone up or do anything of the sort.

It is simply something that is necessary to be able to theme a stock ROM.