# Error loading a new app in genymotion android emulator

**URL:** <https://forum.ionicframework.com/t/error-loading-a-new-app-in-genymotion-android-emulator/21102>\
**Category:** ionic-v1\
**Created:** [April 16, 2015, 1:05pm UTC](https://forum.ionicframework.com/t/error-loading-a-new-app-in-genymotion-android-emulator/21102 "2015-04-16T13:05:27Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![suryamishra2111](https://avatars.discourse-cdn.com/v4/letter/s/7c8e57/32.png) [@suryamishra2111](https://forum.ionicframework.com/u/suryamishra2111)\
**Post date:** [April 16, 2015, 1:05pm UTC](https://forum.ionicframework.com/t/error-loading-a-new-app-in-genymotion-android-emulator/21102/1 "2015-04-16T13:05:27Z")

</div>

I started with Ionic today. Wanted to test it out quickly but am not able to test the sample app in a genymotion emulator.  
I followed all the steps untill “ionic run android” (‘run’ instead of ‘emulate’ for genymotion). But am getting the following error:

> C:\ionic2\mytodo\platforms\android\cordova\node\_modules\q\q.js:126  
> throw e;  
> ^  
> Error: Device communication timed out. Try unplugging & replugging the device.  
> at null.\_onTimeout (C:\ionic2\mytodo\platforms\android\cordova\node\_modules\q\q.js:1717:25)  
> at Timer.listOnTimeout (timers.js:110:15)

I tried it both in the CMD and console2 prompts. The app is blank. Just did build and run. I have used the same genymotion emulator successfully with a plain cordova app (without ionic).

**EDIT**  
Interestingly if I drag the apk file directly into the open emulator, it starts running the app. Am I missing something here?

---

<div class="post-metadata">

**Author:** ![bobrov1989](https://sea1.discourse-cdn.com/ionicframework/user_avatar/forum.ionicframework.com/bobrov1989/32/98131_2.png) [@bobrov1989](https://forum.ionicframework.com/u/bobrov1989)\
**Post date:** [April 16, 2015, 3:58pm UTC](https://forum.ionicframework.com/t/error-loading-a-new-app-in-genymotion-android-emulator/21102/2 "2015-04-16T15:58:51Z")

</div>

Did you first run genymotion virtual device and then execute ionic run android ?

---

<div class="post-metadata">

**Author:** ![suryamishra2111](https://avatars.discourse-cdn.com/v4/letter/s/7c8e57/32.png) [@suryamishra2111](https://forum.ionicframework.com/u/suryamishra2111)\
**Post date:** [April 17, 2015, 10:31am UTC](https://forum.ionicframework.com/t/error-loading-a-new-app-in-genymotion-android-emulator/21102/3 "2015-04-17T10:31:54Z")

</div>

Yes I did run the emulator before running the command.

---

<div class="post-metadata">

**Author:** ![mhartington](https://sea1.discourse-cdn.com/ionicframework/user_avatar/forum.ionicframework.com/mhartington/32/137757_2.png) [@mhartington](https://forum.ionicframework.com/u/mhartington)\
**Post date:** [April 17, 2015, 12:39pm UTC](https://forum.ionicframework.com/t/error-loading-a-new-app-in-genymotion-android-emulator/21102/4 "2015-04-17T12:39:30Z")

</div>

So lets make sure everything is setup.

You have the android sdk install correct?

In genymotion, in the vm selection window, you can change the path to the android sdk. By default, genymotion will point to its own version. Change this to be the path that you have set

---

<div class="post-metadata">

**Author:** ![suryamishra2111](https://avatars.discourse-cdn.com/v4/letter/s/7c8e57/32.png) [@suryamishra2111](https://forum.ionicframework.com/u/suryamishra2111)\
**Post date:** [April 17, 2015, 12:59pm UTC](https://forum.ionicframework.com/t/error-loading-a-new-app-in-genymotion-android-emulator/21102/5 "2015-04-17T12:59:50Z")

</div>

Mike - Thanks. Your tip seems to have solved it for me.

I say “seems” because it started working when I changed it to android SDK. But then out of curiosity I just changed it back to the default genymotion SDK to see what happens. And it worked with the genymotion SDK too. 😕

One thing that I am doing different than yesterday is that I am using Console 2 to start, add android, build and run my app. Yesterday I was using CMD till build. Not sure if that’s even remotely the root cause.

In any case, I am up and running now. Thanks.
