I\'m starting to develop and android app using Cordova 5.0.0 (cordova -v prints 5.0.0), and testing it on a Moto Razr D1 with Android 4.1.2. Under Windows 7, btw.
Here are a couple of things to check and be aware of, in case you didn't know:
cordova -v
won’t necessarily match the platform version cordova platform
If you've updated to the latest version of cordova-android sdk, please ensure you read through the releasenotes.md: https://github.com/apache/cordova-android/blob/master/RELEASENOTES.md
I'm not sure what SD is but I've installed my apps via
adb install
After comparing and checking your uploaded apk to your device, which I believe is easier to debug than the emulator, start up Android Debug Bridge with logcat:
adb -d logcat
If you prefer debugging with logcat through emulator, then:
adb -e logcat
There are extra debug flags to reduce the verbosity here: http://developer.android.com/tools/debugging/debugging-log.html. You'll need to adjust the filter spec to however you like, such as this: adb logcat ActivityManager:I MyApp:D *:S
. I prefer to use adb logcat *:D
to capture almost all debugging messages but reduce the verbosity slightly.
Hopefully, upon connection and startup of logcat you'll be able to catch what errors may be happening to cause your issue.
EDIT: Here's another method to do device debugging via chrome browser developer tools: https://developer.chrome.com/devtools/docs/remote-debugging
In general, here are the steps from the above link:
Requirements: Chrome 32 or later, USB cable to connect to Android device, browser debugging requires Android 4.0+, app debugging requires Android 4.4+
There is more information in the remote-debugging link above regarding live screencasting, proxy setup, port forwarding, and virtual host mapping.