ok so i suppose I’ll get started with a rough guide (This is all for windows by the way) I’m really only a newbie at corona myself so this isn’t definitive, and obviously i’m not responsible if your app causes a human strain of cordyceps and thus the zombie apocalypse:
1-download apktool (it’s googleable)
2-build your app with corona
3-take the apk and put it in the “place-apk-here-for-modding” folder of apktool (NOTE your apk filename must not contain spaces or it’ll crash the tool, if it does, remove them, you can still put them back later)
4-launch apktool using the “script.bat” file in the apktool folder
5-select options 22, 1 then 9 to decompile your apk. in your apktool root folder, find the “projects” folder, there will be a directory named after your apk
6-see which files you want to delete (for me on xp, going too deep into the “build” folder crashes explorer, so i ignore it). the ones i delete are (note, these may be different for you depending on what you use):
assets->webui
smali->org
smali->com->anything you don’t need (I normally delete everything but **my project’s dir** and **the ansca dir**, but it depends on what you use. ie if you use facebook stuff don’t delete the facebook folder)
7-open the “AndroidManifest.xml” and delete the vibrate permission if you don’t use it; then people won’t be wondering why they need it/phones that don’t support it can still get your app. also delete the internet permissions one if you don’t need the internet (some people get suspicious at this, as it is though i use advertising so i’ve always kept it)
You can also set your version name and version code in here, which i did because whatever version of corona i was using wouldn’t let me use decimal points in the version
8-back in apk tool selet 2 to compress your images
9-select 11 to recompile your apk, you can then re-add any spaces and move it back to wherever you want out of the
“place-apk-here-for-modding” folder (it will have an “unsigned” prefix)
10-i dunno if the sign option in apktool is for debugging only, but just in case i then sign my apk again by hand before uploading to market/testing on device:
[html]
to create the new keystore if you haven’t got one
keytool.exe -genkey -v -keystore yourkeystorename.keystore -alias -keyalg RSA -keysize 2048 -validity 10000
then each time you want to sign it run
jarsigner.exe -verbose -keystore >pathtokeystore>yourkeystorename.keystore yourapkname.apk
[/html]
(just put that in code tags so it doesn’t lose the angle brackets!)
it’ll ask you for password prompts etc in the dos window, fill these out as required.
then zipalign and you’re done
===========
Think that’s about the gyst of it, it looks long but it really takes a minute to do each time once you’ve done it once or twice, and the signing commands i have saved in a text file i just copy and paste
if you copy the apk to your phone first, then uninstall, follow this process and reinstall, you’ll notice a pretty hefty filesize difference
Also, with the same version of corona i noticed it went down even more when i licensed it (i knew that happened for Apple builds but didn’t think it worked for Android builds…) to give you an idea, it was about
~6meg raw
~3meg when i followed the above process with an unlicensed corona
~1meg when i did the process with a licensed corona (same version)
probably a lot of holes and I’m sure people a lot more in the know than me can improve vastly on it, but it’s a good jumping off point if you haven’t done it before i suppose 
just remember to test it first, so you haven’t accidentally removed a library your app actually uses
[import]uid: 71799 topic_id: 13323 reply_id: 49569[/import]
