This content has been marked as final. Show 2 replies
Yes Android emulator is very problematic, and there are certain out of box emulator configurations that would not even start up on a reasonably powerful PC.
What works typically for me is to use an emulator built using SDK version 15 or 16 - for some reason, the Android SDK API level's emulators are much more problematic than before. There are some configurations (for example Nexus 7 tab) that simply hangs when trying to start it using default RAM allocation. After reducing it to 512, I can start it but then I can't start app. With older version of the emulator, if I set the RAM to say 512, generally the emulator will start and the app will also start (although very slowly).
Unfortunately this is an Android issue, and there is very little ADF Mobile can do.
In short, if possible please deploy to a device, and also please remember to deploy in release mode when you don't need to debug the app, as performance difference is very great. There are some articles on how to compile Android app in release mode. This may also help with your Android deployment. https://blogs.oracle.com/shay/entry/speed_up_adf_mobile_deployment