On Mon, Nov 14, 2011 at 9:28 PM, CultOf Droid <usu.ana...@gmail.com> wrote: > a> Apps based on system app are built as .apks and .odex files. This > kind of app packaging is NOT distributable, unless you create custom > firmware for the app. I want a regular .apk with classes.dex inside > the Apk. For instance, if I want to make myMail, based on the system > email application, HOW can I make a standalone myMail.apk which is > easily distributable?
Step #1: Create an SDK project. Step #2: Copy the source, resources, and manifest from the AOSP into your SDK project. Step #3: Spend many developer-months repairing all the compile errors due to references from code to other stuff elsewhere in the firmware that is not part of the SDK. This may require copying more code/resources from the AOSP into your project, or removing some features that are too heavily dependent upon things you have no access to, or rewriting some code to stick to SDK-visible classes and methods. > b> Clearly building in the OS source path makes the app less portable, > as compared to those built with the standard SDK. Any comments on how > to increase portability, if you base your app on a system app? Follow that same procedure. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android 3.2 Programming Books: http://commonsware.com/books -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
