When building with the Android SDK, you set the APK file name via the <project> tag’s “name” attribute in your “build.xml” file. For example…
\<?xml version="1.0" encoding="UTF-8"?\> \<project name="YourApkFileName" default="help"\> \<!-- The rest of your project settings go here. --\> \</project\>
Regarding application icons, you have to set that up the native Android way. Icon files such as “Icon-mdpi.png” and “Icon-hdpi.png” are only supported by the Corona Simulator and are ignored by the Android SDK. Native Android developers have to add application icons (aka: launcher icons) to their Android project’s “res” directory and reference that application icon file via the AndroidManifest.xml file’s <application android:icon=""> attribute as documented by Google here…
http://developer.android.com/guide/topics/manifest/application-element.html#icon
http://developer.android.com/design/style/iconography.html
Also, the “build.settings” file is ignored for native Android SDK builds. The “build.settings” file is only used by the Corona Simulator. This means you have to edit the AndroidManifest.xml file yourself. But that said, that gives you ultimate control over how your app is configured. Google documents how to set the AndroidManifest.xml file via the link below. Also, our sample projects’ AndroidManifest.xml files contains comments that indicate why those tags were added, which should prove helpful.
http://developer.android.com/guide/topics/manifest/manifest-intro.html
There is definitely a lot to learn when doing native Android development, but once you get the hang of it and all of its nuances, it’s not so bad. That said, it also shows how easy we made Android development via the Corona Simulator.