I'm working on an Android port of an iOS game at the moment. I am using the Android NDK only (android_native_app_glue) in Eclipse (CDT + ADT). I am using the Android emulator, API 15 (but we are targeting API9+) as we do not yet have an Android device. The game has about 200-300mb of assets and I'm unsure of how to include them properly or how to get into a fast testing/debugging cycle with assets attached.
As it stands I am linking the assets folder in my Android project to the resources folder that contains the game assets. This works but the problem lies in the fact that when I build it takes about 9-10 minutes for the 200mb .apk file to be installed onto the emulator. This is simply unacceptable when things need to be tested quickly.
If I strip the assets out of the project, it installs very quickly. Because of this I am stripping out the bulk of the assets at the moment to do my testing but when it comes to the long run I need a better solution.
My question, is there a way to setup an Android game project with a large asset collection during development to allow for fast testing/iteration? E,g. fast deployment or updating of .apk to allow for quick testing.