Android emulator not launching the app - android

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

Related

Failed to install *.apk on device 'emulator-5554' error

[2015-01-21 14:27:38 - FirstAndroidProject] Launching a new emulator with Virtual Device 'Android_5.0.1'
[2015-01-21 14:27:51 - FirstAndroidProject] New emulator found: emulator-5554
[2015-01-21 14:27:51 - FirstAndroidProject] Waiting for HOME ('android.process.acore') to be launched...
[2015-01-21 14:30:52 - FirstAndroidProject] HOME is up on device 'emulator-5554'
[2015-01-21 14:30:52 - FirstAndroidProject] Uploading FirstAndroidProject.apk onto device 'emulator-5554'
[2015-01-21 14:30:53 - FirstAndroidProject] Installing FirstAndroidProject.apk...
[2015-01-21 14:33:00 - FirstAndroidProject] Failed to install FirstAndroidProject.apk on device 'emulator-5554!
[2015-01-21 14:33:00 - FirstAndroidProject] (null)
[2015-01-21 14:33:01 - FirstAndroidProject] Launch canceled!
This is my very first Android app. I tried every possible way explained in solutions provided in stackoverflow.com but every time I launched the app I get the above error in the console.
But on every time I opened the icon in the menu list in the emulator after the above message is displayed, the app opens successfully. What is actually meant by the above error?
Kill your adb manually in the your processes after close the emulator, restart your eclipse..
Clean your project and restart the emulator. Then, try launching the app again.

Android Emulator problems, to do with the .apk

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.

Emulator Takes Much Time and at the end it Fail

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.

hello world fails to show up in emulator

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.

emulator: ERROR: the user data image is used by another emulator. aborting

[2011-02-09 23:59:11 - Timerproject] ------------------------------
[2011-02-09 23:59:11 - Timerproject] Android Launch!
[2011-02-09 23:59:11 - Timerproject] adb is running normally.
[2011-02-09 23:59:11 - Timerproject] Performing acarin.timetracker.project.ezhil.Timerproject activity launch
[2011-02-09 23:59:11 - Timerproject] Automatic Target Mode: Preferred AVD 'MA_AVD_2.3.1' is not available. Launching new emulator.
[2011-02-09 23:59:11 - Timerproject] Launching a new emulator with Virtual Device 'MA_AVD_2.3.1'
[2011-02-09 23:59:31 - Timetracker] New emulator found: emulator-5554
[2011-02-09 23:59:31 - Timetracker] Waiting for HOME ('android.process.acore') to be launched...
[2011-02-10 00:01:40 - Timetracker] HOME is up on device 'emulator-5554'
[2011-02-10 00:01:40 - Timetracker] Uploading Timetracker.apk onto device 'emulator-5554'
[2011-02-10 00:01:40 - Timetracker] Installing Timetracker.apk...
[2011-02-10 00:04:11 - Timetracker] Failed to install Timetracker.apk on device 'emulator-5554!
[2011-02-10 00:04:11 - Timetracker] (null)
[2011-02-10 00:04:11 - Timetracker] Launch canceled!
i run the Timerproject but another timetrack project is only running the same timetracker project also doest responding
just close the already running emulator and start a new emulator more over if that doesn't works too close the eclipse too
If you're running Eclipse, and you've started the app from within (using Run As->Android App), then it should reuse the existing AVD. If it can't find it, then it will try to start another emulator and fail with the error you're seeing. Check the system Path environment variable and make sure it's including the SDK directory. If it doesn't then you'll see this error (I had the same problem; turned out I misspelled Program Files as Program Fiiles).
Hope this helps.
Open command prompt browse your adb path like
cd C:\Program Files\Android\android-sdk\platform-tools
type the command
adb kill-server && adb start-server
this will resolve your problem

Categories

Resources