I'm unable to start my AVD. I've uninstalled and installed it 2nd time. Still the same. I have kept the AVD for approx half an hour, Still no luck.
Below is the Console log i get when try to run the Application in AVD.
[2014-02-12 20:43:02 - HelloAndroid] ------------------------------
[2014-02-12 20:43:02 - HelloAndroid] Android Launch!
[2014-02-12 20:43:02 - HelloAndroid] adb is running normally.
[2014-02-12 20:43:02 - HelloAndroid] Performing com.example.helloandroid.MainActivity activity launch
[2014-02-12 20:43:02 - HelloAndroid] Automatic Target Mode: Unable to detect device compatibility. Please select a target device.
[2014-02-12 20:43:05 - HelloAndroid] Launch canceled!
[2014-02-12 20:44:38 - HelloAndroid] ------------------------------
[2014-02-12 20:44:38 - HelloAndroid] Android Launch!
[2014-02-12 20:44:38 - HelloAndroid] adb is running normally.
[2014-02-12 20:44:38 - HelloAndroid] Performing com.example.helloandroid.MainActivity activity launch
[2014-02-12 20:44:38 - HelloAndroid] Automatic Target Mode: Unable to detect device compatibility. Please select a target device.
[2014-02-12 20:44:49 - HelloAndroid] Launching a new emulator with Virtual Device 'AVD_for_Nexus_4_by_Google'
[2014-02-12 20:45:23 - Emulator] bind: Permission denied
[2014-02-12 20:45:23 - HelloAndroid] New emulator found: emulator-5558
[2014-02-12 20:45:23 - HelloAndroid] Waiting for HOME ('android.process.acore') to be launched...
And attached is the logcat when starting the AVD from AVD Manager.
http://sdrv.ms/1bWRKru
I think there is a problem in mounting the data partition or its not available.
In a real device, if you have not flashed the data partition properly, with fastboot, the same issue will occur.
I have checked my api level of the device and the program i'm creating. I have also restarted my eclipse and the problem still does not seem to resolve. is there any other solutions to this ?
[2014-02-15 19:31:39 - JudoApp] New emulator found: emulator-5554
[2014-02-15 19:31:39 - JudoApp] Waiting for HOME ('android.process.acore') to be launched...
[2014-02-15 19:42:15 - JudoApp] HOME is up on device 'emulator-5554'
[2014-02-15 19:42:15 - JudoApp] Uploading JudoApp.apk onto device 'emulator-5554'
[2014-02-15 19:42:16 - JudoApp] Installing JudoApp.apk...
[2014-02-15 19:44:37 - JudoApp] Failed to install JudoApp.apk on device 'emulator-5554!
[2014-02-15 19:44:37 - JudoApp] (null)
[2014-02-15 19:44:38 - JudoApp] Launch canceled!
change ADB connection timeout from ddms (default is 5.000,change it to 10.000)
Ive seen the questions posted about this issue. I understand it takes several minutes for the emulator to configure itself and launch. But if Im getting the specific error:
[2011-05-13 08:41:36 - HelloAndroid] ------------------------------
[2011-05-13 08:41:36 - HelloAndroid] Android Launch!
[2011-05-13 08:41:36 - HelloAndroid] adb is running normally.
[2011-05-13 08:41:36 - HelloAndroid] Performing com.santiapps.helloandroid.HelloAndroid activity launch
[2011-05-13 08:41:36 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'my_avd'
[2011-05-13 08:41:36 - HelloAndroid] Launching a new emulator with Virtual Device 'my_avd'
[2011-05-13 08:41:49 - Emulator] 2011-05-13 08:41:49.650 emulator[411:903] Warning once: This application, or a library it uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw and move to Quartz.
[2011-05-13 08:41:50 - Emulator] emulator: emulator window was out of view and was recentred
[2011-05-13 08:41:50 - Emulator]
[2011-05-13 08:41:50 - HelloAndroid] New emulator found: emulator-5554
[2011-05-13 08:41:50 - HelloAndroid] Waiting for HOME ('android.process.acore') to be launched...
[2011-05-13 08:44:33 - HelloAndroid] WARNING: Application does not specify an API level requirement!
[2011-05-13 08:44:33 - HelloAndroid] Device API version is 12 (Android 3.1)
[2011-05-13 08:44:33 - HelloAndroid] HOME is up on device 'emulator-5554'
[2011-05-13 08:44:33 - HelloAndroid] Uploading HelloAndroid.apk onto device 'emulator-5554'
[2011-05-13 08:44:34 - HelloAndroid] Installing HelloAndroid.apk...
[2011-05-13 08:47:20 - HelloAndroid] Failed to install HelloAndroid.apk on device 'emulator-5554!
[2011-05-13 08:47:20 - HelloAndroid] (null)
[2011-05-13 08:47:22 - HelloAndroid] Launch canceled!
[2011-05-13 08:53:55 - HelloAndroid] ------------------------------
[2011-05-13 08:53:55 - HelloAndroid] Android Launch!
[2011-05-13 08:53:55 - HelloAndroid] adb is running normally.
[2011-05-13 08:53:55 - HelloAndroid] Performing com.santiapps.helloandroid.HelloAndroid activity launch
[2011-05-13 08:53:55 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'my_avd'
[2011-05-13 08:53:55 - HelloAndroid] Launching a new emulator with Virtual Device 'my_avd'
[2011-05-13 08:54:06 - Emulator] 2011-05-13 08:54:06.327 emulator[460:903] Warning once: This application, or a library it uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw and move to Quartz.
[2011-05-13 08:54:06 - Emulator] emulator: emulator window was out of view and was recentred
[2011-05-13 08:54:06 - Emulator]
[2011-05-13 08:54:06 - HelloAndroid] New emulator found: emulator-5554
[2011-05-13 08:54:06 - HelloAndroid] Waiting for HOME ('android.process.acore') to be launched...
[2011-05-13 09:08:07 - Emulator] emulator: ERROR: unexpected qemud char. channel close
couldnt it be I have a bad configuration...?
wait for the emulator to setup completely and then test your app. Also, I would leave you AVD open so you dont have to wait so long everytime you run your application.
When it shows the red writing, don't close anything - leave it there and then press the run button again. Worked like a charm.
I was facing the same problem but i tried 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.
Try this: create another emulator in AVD Manager and try to run your application in the new emulator.
Hope this might help you
You may need to increase the device ram size. For some Honeycomb AVDs at least, the default of 256 is insufficient, and caused me the same problem. Try at least 512.
Go to window and preference and increase the ADB connection time out(ms) which is 500 by default. Also change the base local debugger port to more than 9000 in my case it worked.
See Related post
This worked on Linux for me:
Run Emulator (Wait for the home screen of the Emulator to load)
Click Window > Open Perspective > DDMS
In Devices Panel, click on drop down menu > Reset adb
Run project
Valen answer is correct although its nice to know when to start running the app and when is not ok to start the app.Open the devices perspective. The next time you want to run an app first open the 'Android virtual device Manager' and run your avd then click on the device perspective and watch your emulator processes one by one firing up.. as soon this is done (its not fast you have to wait .. but at least you have some idea of whats going on .... a progress bar would be ideal for this place), click on your project and run as android app. On the devices perspective one more process will appear with the name of the package of your app. As soon as this happen your app is running on the device and it can be tested.
I have noticed this error when the emulator has not loaded fully, "android" is flashing on your screen. In other words, it is not yet ready for the application to be installed.
Just wait till you see that the emulator is fully ready, meaning the "android" has vanished and the device screen is visible on the emulator. Now run it and the application loads smoothly.
Restart ADB server from DMOZ
or refer to this tutorial How to solve Failed to install .apk
[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
I'm trying to build "Hello, Android" with the Android SDK, but Android won't say "hello" to me.
I build with the 2.6 version of the SDK and run in Eclipse on Win XP. (I've installed the plug-in.)
Here's what I get:
[2009-09-23 16:35:19 -
HelloAndroid]Android Launch!
[2009-09-23 16:35:19 -
HelloAndroid]adb is running normally.
[2009-09-23 16:35:19 -
HelloAndroid]Performing
com.example.helloandroid.HelloAndroid
activity launch
[2009-09-23 16:35:19 -
HelloAndroid]Automatic Target Mode:
launching new emulator with compatible
AVD 'my_avd'
[2009-09-23 16:35:19 -
HelloAndroid]Launching a new emulator
with Virtual Device 'my_avd'
[2009-09-23 16:35:21 -
HelloAndroid]New emulator found:
emulator-5554
[2009-09-23 16:35:21 -
HelloAndroid]Waiting for HOME
('android.process.acore') to be
launched...
[2009-09-23 16:36:20 -
HelloAndroid]HOME is up on device
'emulator-5554'
[2009-09-23 16:36:20 -
HelloAndroid]Uploading
HelloAndroid.apk onto device
'emulator-5554'
[2009-09-23 16:36:30 -
HelloAndroid]Installing
HelloAndroid.apk...
[2009-09-23 16:36:43 -
HelloAndroid]Success!
[2009-09-23 16:36:44 -
HelloAndroid]Starting activity
com.example.helloandroid.HelloAndroid
on device
[2009-09-23 16:36:44 -
HelloAndroid]Launch error:
device (emulator-5554) request
rejected: device not found
I got this to work. It may be a timing issue. Have to press Menu button on emulator keypad to unlock the screen. Then the output is displayed.