Basically your app isn’t handling being interrupted by phone calls well. You can actually test this on the Simulator. If you have a Mac it’s like CMD-Down Arrow. That will send a suspend event to your app. Then CMD-Down Arrow will send a resume event. You should make sure your app handles that condition well.
My only Android device is a Kindle Fire and I can’t do a phone call test on it to see what happens.
Corona lets you choose to build for iOS, Android, Nook or Amazon/Kindle in the File->Build menu options.
Android, Nook and Amazon/Kindle are all Android devices that can use the same .apk file that the build process saves. Kinda bear with me, this is going to be a bit convoluted…
An app that you build with “Android” **WITH Corona SDK** can run on any Android device except for the Fire and the Nook. You can put that app up in Google Play and any other Android Marketplace… including Amazon. However, since that app is compiled with full features, it cannot install on the Kindle fire (has Google Mobile Services turned on). So if you want your app on the fire, you have to build a specific Kindle/Amazon build. That build should be able to run on generic Android devices, but it won’t have the full features (camera, gps, etc). If you’re app isn’t using them, then its not a big deal.
Now sitting off to the side is the Nook. Corona lets us build a version specifically for the Nook which I suspect is doing the same thing the Kindle/Amazon build is doing in stripping out Googles GMS, and other things the Nook can’t do. The feature set between the Nook and the Kindle Fire must be enough that Ansca had to do separate builds. I suspect that a Nook built .APK file can run on generic Android devices, but I don’t have a device to test with to confirm it. [import]uid: 19626 topic_id: 24942 reply_id: 101284[/import]