My emulator stopped working whilst making an app and kept saying it couldn't install the .apk in the console whilst running. When running the emulator in the manager it loads fine but obviously doesn't have an app to load.
When I try and run the app in the emulator it gives me the error and then loads up the phone without my app on it. This suggests its the apps fault in my mind, so i created a new project which i left untouched where it just said "hello world", even when trying to run this I get the same issue.
I've tried other peoples responses on here such as moving the apk file but that was to no avail, I've ended up redownloading and installing the sdk files but the same error persists. I'm new to this & appreciate any help.
My console after attempting to run app:
[2014-03-28 19:57:52 - LiverpoolPolls] ------------------------------
[2014-03-28 19:57:52 - LiverpoolPolls] Android Launch!
[2014-03-28 19:57:52 - LiverpoolPolls] adb is running normally.
[2014-03-28 19:57:52 - LiverpoolPolls] Performing com.example.liverpoolpolls.Loadhomemenu activity launch
[2014-03-28 19:57:52 - LiverpoolPolls] Automatic Target Mode: launching new emulator with compatible AVD 'emulator'
[2014-03-28 19:57:52 - LiverpoolPolls] Launching a new emulator with Virtual Device 'emulator'
[2014-03-28 19:57:54 - LiverpoolPolls] New emulator found: emulator-5554
[2014-03-28 19:57:54 - LiverpoolPolls] Waiting for HOME ('android.process.acore') to be launched...
[2014-03-28 20:02:12 - LiverpoolPolls] HOME is up on device 'emulator-5554'
[2014-03-28 20:02:12 - LiverpoolPolls] Uploading LiverpoolPolls.apk onto device 'emulator-5554'
[2014-03-28 20:02:18 - LiverpoolPolls] Installing LiverpoolPolls.apk...
[2014-03-28 20:04:34 - LiverpoolPolls] Failed to install LiverpoolPolls.apk on device 'emulator-5554!
[2014-03-28 20:04:34 - LiverpoolPolls] (null)
[2014-03-28 20:04:35 - LiverpoolPolls] Launch canceled!
I shall download that other emulator and see where that gets me.
Related
i have created an android app at android 4.4. When I launch the emulator, the application icon is visible on the screen but as soon as i click it, it displays an error message-Unfortunately, The New Boston(name of my app) has stopped.
I have checked the code again n again and it is perfectly fine.
while launching the emulator, console shows the following
[2014-03-28 23:33:22 - TheNewBoston] Android Launch!
[2014-03-28 23:33:22 - TheNewBoston] adb is running normally.
[2014-03-28 23:33:22 - TheNewBoston] Performing com.thenewboston.travis.MainActivity activity launch
[2014-03-28 23:33:22 - TheNewBoston] Automatic Target Mode: using existing emulator 'emulator-5554' running compatible AVD 'avd1'
[2014-03-28 23:33:22 - TheNewBoston] Uploading TheNewBoston.apk onto device 'emulator-5554'
[2014-03-28 23:33:23 - TheNewBoston] Failed to install TheNewBoston.apk on device 'emulator-5554': EOF
[2014-03-28 23:33:23 - TheNewBoston] java.io.IOException:
In eclipse there is no virtual device for android ver 4.4 thats why its crashing,you can try genemotion.com emulators
I am new to developing Android applications. My first application takes too much time to load, and fails at the end.
I'm using a Windows 8 laptop with 4GB of RAM and an Intel processor. I'm writing all of this because I saw an answer regarding Windows.
[2014-03-08 07:26:52 - Mytest] Android Launch! [2014-03-08 07:26:52 -
Mytest] adb is running normally.
[2014-03-08 07:26:52 - Mytest] Performing
com.example.mytest.MainActivity activity launch
[2014-03-08 07:26:53 - Mytest] Automatic Target Mode: launching new
emulator with compatible AVD 'nnt'
[2014-03-08 07:26:53 - Mytest] Launching a new emulator with Virtual
Device 'nnt'
[2014-03-08 07:27:15 - Mytest] New emulator found: emulator-5554
[2014-03-08 07:27:15 - Mytest] Waiting for HOME
('android.process.acore') to be launched
[2014-03-08 07:39:36 - Mytest] HOME is up on device 'emulator-5554'
[2014-03-08 07:39:36 - Mytest] Uploading Mytest.apk onto device
'emulator-5554'
[2014-03-08 07:39:36 - Mytest] Installing Mytest.apk...
[2014-03-08 07:41:51 - Mytest] Failed to install Mytest.apk on device
'emulator-5554!
[2014-03-08 07:41:51 - Mytest] (null) [2014-03-08 07:41:51 - Mytest]
Launch canceled!
Please let me know.
I have had this problem before. I have tried following steps.
Plug-in your charger, if it's not connected.
Start emulator from AVD - manager, this works for most of the time.
Try Genymotion emulator, it is free for personal use and it works smooth. You also can use Eclipse plug-in.
Get it here: Genymotion
If you having troubles with installation, here is User Guide.
I am using it and I am very happy.
Here i am placing the console details ,i need to change any emulator settings or need to add any statements in manifest file .help me ,thank you
[2013-03-28 11:08:29 - Lisnx] Android Launch!
[2013-03-28 11:08:29 - Lisnx] adb is running normally.
[2013-03-28 11:08:29 - Lisnx] Performing com.lisnx.activity.SplashActivity activity launch
[2013-03-28 11:08:34 - Lisnx] Launching a new emulator with Virtual Device 'AVD_4.0'
[2013-03-28 11:08:45 - Lisnx] New emulator found: emulator-5554
[2013-03-28 11:08:45 - Lisnx] Waiting for HOME ('android.process.acore') to be launched...
[2013-03-28 11:10:49 - Lisnx] HOME is up on device 'emulator-5554'
[2013-03-28 11:10:49 - Lisnx] Uploading Lisnx.apk onto device 'emulator-5554'
[2013-03-28 11:11:00 - Lisnx] Installing Lisnx.apk...
[2013-03-28 11:12:43 - Lisnx] Success!
[2013-03-28 11:12:43 - facebook_y] Could not find facebook_y.apk!
[2013-03-28 11:12:43 - Lisnx] Starting activity com.lisnx.activity.SplashActivity on device emulator-5554
Looks like you need to install the facebook sdk into the emulator before your app will run.
Try this:
adb install %HOMEPATH%\facebook-android-sdk-3.0.1\bin\FBAndroid-2.1.apk
Extracted from here section #2
Android Emulator boots up with flashy 'Android' but the application never starts up and I wont see any Home Screen even after waiting for 30 min. I use PC of RAM 2 GB still I am unable to see the hOme screen on Emullator.. The Console is as
[2012-02-26 17:36:52 - SDK Manager] Created AVD 'GingerBread2.3.3' based on Android 2.3.3, ARM (armeabi) processor,
[2012-02-26 17:36:52 - SDK Manager] with the following hardware config:
[2012-02-26 17:36:52 - SDK Manager] hw.lcd.density=160
[2012-02-26 17:36:52 - SDK Manager] vm.heapSize=24
[2012-02-26 17:36:52 - SDK Manager] hw.ramSize=256
[2012-02-26 17:37:11 - test_ball_handler] New emulator found: emulator-5554
[2012-02-26 17:37:11 - test_ball_handler] Waiting for HOME ('android.process.acore') to be launched...
[2012-02-26 17:42:00 - test_ball_handler] ------------------------------
[2012-02-26 17:42:00 - test_ball_handler] Android Launch!
[2012-02-26 17:42:00 - test_ball_handler] adb is running normally.
[2012-02-26 17:42:00 - test_ball_handler] Performing com.eg.a.Test_ball_handlerActivity activity launch
[2012-02-26 17:42:00 - test_ball_handler] Automatic Target Mode: using existing emulator 'emulator-5554' running compatible AVD 'GingerBread2.3.3'
[2012-02-26 17:42:00 - test_ball_handler] Uploading test_ball_handler.apk onto device 'emulator-5554'
[2012-02-26 17:42:01 - test_ball_handler] Installing test_ball_handler.apk...
[2012-02-26 17:44:15 - test_ball_handler] Failed to install test_ball_handler.apk on device 'emulator-5554!
[2012-02-26 17:44:15 - test_ball_handler] (null)
[2012-02-26 17:44:15 - test_ball_handler] Launch canceled!
[2012-02-26 17:47:56 - test_ball_handler] ------------------------------
Try changing the ADB connection timeout.
I think it defaults that to 5000ms and I changed mine to 10000ms to get rid of that problem. If you are in Eclipse, you can do this by going through Window -> Preferences and then it is in DDMS under Android.
It's not uncommon for an AVD to be born (or become) corrupt/misbehaving. The solution for that is to make a new AVD (with same settings) and delete the corrupt/misbehaving one.
Another possible problem is AVDs can eat up a lot of your CPU, so if your system is already in struggle-town, chances of AVD booting and running nicely is slim.
I followed Hello World tutorial exactly. Emulator comes up but fails to show Hello World text. Here's the log info:
[2011-11-26 20:06:57 - HelloAndroid] Android Launch!
[2011-11-26 20:06:57 - HelloAndroid] adb is running normally.
[2011-11-26 20:06:57 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch
[2011-11-26 20:06:57 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'AndroidPhone'
[2011-11-26 20:06:57 - HelloAndroid] Launching a new emulator with Virtual Device 'AndroidPhone'
[2011-11-26 20:07:09 - HelloAndroid] New emulator found: emulator-5554
[2011-11-26 20:07:09 - HelloAndroid] Waiting for HOME ('android.process.acore') to be launched...
[2011-11-26 20:45:37 - HelloAndroid] HOME is up on device 'emulator-5554'
[2011-11-26 20:45:37 - HelloAndroid] Uploading HelloAndroid.apk onto device 'emulator-5554'
[2011-11-26 20:45:38 - HelloAndroid] Installing HelloAndroid.apk...
After about 1/2 hour, this shows up in the log...
[2011-11-26 20:48:59 - HelloAndroid] Failed to install HelloAndroid.apk on device 'emulator-5554!
[2011-11-26 20:48:59 - HelloAndroid] (null)
[2011-11-26 20:49:02 - HelloAndroid] Launch canceled!
I’ve read posts on similar problem. I’ve tried many suggested solutions including restarting Eclipse, rebooting and restarting eclipse, creating a new project in eclipse, starting emulator first with “wipe user data” box checked, increasing the emulator time-out period from 5000 to 20000, unlocking emulator by clicking and dragging mouse, clicking Menu and Home buttons on emulator, and running the Layout version. Nothing worked. I’m using Android 4.0 AVD and Eclipse Build id: 20110916-0149 and the latest JDC on a Dell Inspiron 1501 laptop.
It’s hard to believe Google would make this discouraging example as the first impression new users experience. Hopefully someone can help.
When you have the "Failed to install HelloAndroid.apk on device 'emulator-5554!", try to wait some seconds,
dont close the VM and
reclick on "Launch Buton"
When you create a new Activity project, it effectively creates a Hello World app. Create a new project. Don't modify it. Just run it. If you don't see a Hello world message, check your install.