app is not responding while testing on genymotion

Question

I'm using genymotion android emulator to test my application(which needs google play services). As genymotion can't support this, I followed the instruction here. How to install Google Play Services in a Genymotion VM (with no drag and drop support)?

Whenever I tried to start this app on genymotion, dialog box appears saying "app isn't responding. Do u want to close it?".I've been using genymotion with Galaxy Nexus-4.2.2 since my first development of this app.It was perfectly fine.I don't know why it stops working all of the sudden. This problem only happen when I test my app on genymotion, not with real device and eclipse emulator. No error in logcat.Emulator can connect to internet. All checked . My code has no problem .I deleted genymotion AVD ,created and test with new one also can't solve the problem.
Please tell me how to solve this problem?

Answer 1

This message appears when you are doing a long task on the main thread. It is called ANR (Application Not Responding). You should look at what's happening by using debug and profiling tools.

Add a break point into your code and Bedug (instead of Run) your app on the device. You can also profile the execution of your app through DDMS, to identify the part of the code that runs on the UI thread and take more than 5 second to process. You can find here more about Tracedump, the method profiling tool on Android.

Also, it could not come from your app but being caused by a third party element you call. I know for example the new "Photos" app from the Google apps can cause ANRs when you select a picture from the cloud that have not been downloaded yet.

If it is coming from a third part app, I don't know how you can solve this problem.

Answer 2

Genymotion emulator does not come with integrated googleplay services so i suggest you check if the service exist in the device before trying to access it, that it wont freeze when you try to access the service.. Also you could debug directly in your phone, using the adb or using the adb own emulator (I know the emulator on the adb is slow xD but still..)