Also, install the android sdk on your pc and use ADB to install the app on your phone. All that uploading gets old fast 
Adb is a much faster and cleaner way od doing it. Plus you need the android sdk tools in order to get debugging information from your device anyhow.
Trust me, itâs well worth the time it takes to set up 
ADVANCED MOVE: Once you get everything moving correctly, follow these steps from Roaming Gamer to get multiple CoronaViewer builds running on one device.Â
Still a problemâŚI have now successfully uninstalled what was the old CoronaViewer(1/2 my game) and installed a clean build of CoronaViewer to the phone. When I run the application, it asks for access to itâs DropBox folder and then shows the CoronaViewer title and logo for one second before switching back to the main menu on Android. When I look at Apps in memory, it still shows CoronaViewer as loaded. But again, when I attempt to go back to it, it shows the title and logo again for one second before switching back to the main menu on Android - while leaving itself in memory. Is this the normal behavior of CoronaViewer on an Android device?
I simply made an HTML file the Android browser can see with nothing on the page but a link to my Corona.apk. All I do is click the link every time I want to update - the download of about 30MB only takes about 5 seconds on my connection, so it doesnât really get old.
But what interests me in your post is your comment about the need to get debugging information from the device. Doesnât the Simulator do that in the Console? When would I need to debug it right on the phone itself?
To each his own
I prefer just being able to do: adb install -r apkName.apk and have it install via usb.
Anyway⌠To answer your question, the Corona simulator doesnât give you runtime console output from the device itself.
So to see your print statements, error messages etc when running the app on your device, you will need to use either ddms or the monitor application which come as part of the android sdk. You can also just use the command line (also requires adb) and enter the command: adb logcat
Then with your device connected via usb, You have access to the aforementioned data via an on screen console.
This goes without saying, but device testing is crucial and you need to be sure that things are outputting and running as expected on the device. The simulator has itâs caveats, that could trip you up on device (i.e no enforcement of case sensitivity for filenames), so itâs imperitive that you have access to the devices output.
Thats is why itâs better to just use adb, rather than side loading the apks, just use the tools provided, it makes for a easier workflow, trust me.
Hope this helps.
The time it takes to build the app, upload it to a server (or run a webserver on your computer and point your web directory to the build folder), then take the time to copy over the binary (uninstalling the previous one if necessary) vs. save the source file in your editor and watch the device refresh.
Now as to why itâs not working, you need to look at your console log and see if there are errors (just like any other app on a device). CoronaViewer has the complexity of having to deal with two build.settings files. If your app needs plugins, then your CoronaViewer needs to be built with the plugins too.
Rob
Did you ever get this figured out, Troy?