I installed jdk 1.7.0, eclipse and the android plugin. I create a new android project but when I try to launch I get this message:
[2011-08-09 18:24:15 - myTEst] ------------------------------
[2011-08-09 18:24:15 - myTEst] Android Launch!
[2011-08-09 18:24:15 - myTEst] adb is running normally.
[2011-08-09 18:24:15 - myTEst] Performing crr.myTest.MyTEstActivity activity launch
[2011-08-09 18:24:15 - myTEst] Automatic Target Mode: launching new emulator with compatible AVD 'myDev22'
[2011-08-09 18:24:15 - myTEst] Launching a new emulator with Virtual Device 'myDev22'
[2011-08-09 18:24:15 - Emulator] invalid command-line parameter: Files.
[2011-08-09 18:24:15 - Emulator] Hint: use '#foo' to launch a virtual device named 'foo'.
[2011-08-09 18:24:15 - Emulator] please use -help for more information
I get the same message if I try to launch the emulator from the sdk manager. What does that mean? Thanks, Andrea.
Related
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.
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.
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.
This should be a really simple one. I am doing the Hello Android tutorial and I was able to get my app to install into the emulator. However, when I go to run again (with no changes) the eclipse environment insists on launching a new emulator instead of connecting to the existing one. How do I fix that? My development environment is a Mac Mini running Mac OS 10.6.8.
Thanks.
New Update:
I have found the answer:
First I read this [question linked above by Mangusto][1]
Use same android emulator everytime
Then I realized that what one really needs to do, if the emulator is opening and initializing slowly, is to start the emulator, wait for it to initialize, and then attach to it the manual way described in the link above. Automatic does not work if your emulator is starting slowly as it disconnects as I described in the update below.
Thanks for the responses.
Update:
Below is the print out from eclipse (I tried to link image but could not due to my user level. I need reputation level of 10 or more). I had already tried the suggestion below about automatic vs manual. I think the issue is that while the apk file was installed it did not automatically launch in the emulator. Therefore, eclipse disconnected from the emulator. I was able to see my application by navigating to the apps within the android emulator.
[2011-11-24 08:25:34 - SDK Manager] Created AVD 'myAvd' based on Android 4.0, ARM (armeabi-v7a) processor,
[2011-11-24 08:25:34 - SDK Manager] with the following hardware config:
[2011-11-24 08:25:34 - SDK Manager] hw.lcd.density=240v
[2011-11-24 08:25:34 - SDK Manager] vm.heapSize=24
[2011-11-24 08:25:34 - SDK Manager] hw.ramSize=512
[2011-11-24 08:29:17 - HelloAndroid] ------------------------------
[2011-11-24 08:29:17 - HelloAndroid] Android Launch!
[2011-11-24 08:29:17 - HelloAndroid] adb is running normally.
[2011-11-24 08:29:17 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch
[2011-11-24 08:29:17 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'myAvd'
[2011-11-24 08:29:17 - HelloAndroid] Launching a new emulator with Virtual Device 'myAvd'
[2011-11-24 08:29:25 - Emulator] 2011-11-24 08:29:25.377 emulator-arm[984:80b] 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-11-24 08:29:25 - HelloAndroid] New emulator found: emulator-5554
[2011-11-24 08:29:25 - HelloAndroid] Waiting for HOME ('android.process.acore') to be launched...
[2011-11-24 08:31:29 - HelloAndroid] HOME is up on device 'emulator-5554'
[2011-11-24 08:31:29 - HelloAndroid] Uploading HelloAndroid.apk onto device 'emulator-5554'
[2011-11-24 08:31:29 - HelloAndroid] Installing HelloAndroid.apk...
[2011-11-24 08:33:36 - HelloAndroid] Failed to install HelloAndroid.apk on device 'emulator-5554!
[2011-11-24 08:33:36 - HelloAndroid] (null)
[2011-11-24 08:33:36 - HelloAndroid] Failed to install HelloAndroid.apk on device 'emulator-5554': Connection reset by peer
[2011-11-24 08:33:36 - HelloAndroid] com.android.ddmlib.InstallException: Connection reset by peer
[2011-11-24 08:33:36 - HelloAndroid] Launch canceled!
[2011-11-24 08:34:55 - HelloAndroid] ------------------------------
[2011-11-24 08:34:55 - HelloAndroid] Android Launch!
[2011-11-24 08:34:55 - HelloAndroid] adb is running normally.
[2011-11-24 08:34:55 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch
[2011-11-24 08:34:55 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'myAvd'
[2011-11-24 08:34:55 - HelloAndroid] Launching a new emulator with Virtual Device 'myAvd'
[2011-11-24 08:35:03 - Emulator] WARNING: Data partition already in use. Changes will not persist!
[2011-11-24 08:35:05 - Emulator] WARNING: Cache partition already in use. Changes will not persist!
[2011-11-24 08:35:06 - Emulator] 2011-11-24 08:35:06.756 emulator-arm[1004:80b] 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-11-24 08:35:06 - HelloAndroid] New emulator found: emulator-5556
[2011-11-24 08:35:06 - HelloAndroid] Waiting for HOME ('android.process.acore') to be launched...
[2011-11-24 08:35:11 - HelloAndroid] emulator-5556 disconnected! Cancelling 'com.example.helloandroid.HelloAndroid activity launch'!
[2011-11-24 08:42:36 - HelloAndroid] ------------------------------
[2011-11-24 08:42:36 - HelloAndroid] Android Launch!
[2011-11-24 08:42:36 - HelloAndroid] adb is running normally.
[2011-11-24 08:42:36 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch
[2011-11-24 08:42:36 - HelloAndroid] Automatic Target Mode: Preferred AVD 'myAvd' is not available. Launching new emulator.
[2011-11-24 08:42:36 - HelloAndroid] Launching a new emulator with Virtual Device 'myAvd'
Its because your application Target mode has set to manual. To solve :
Right Click on your project-> Run as -> Select Run Configurations ->
In that select Target Tab ->Select Automatic instead of manual
Click on Apply and run.
Now your app doesn't prompt for a device.
For a reverse case Select Manual.
Hope it helps.
Go to DDMS Perspective and if you can't see any emulator device on the list, Find the "View menu" dropdown on the "Devices" window on the left, and click Reset ADB.
After adb restarted it should be able to show all of your devices again.
Me also had the same problem.First of all clean your project.Take the DDMS mode in the eclipse .Here you are able to handle the devices in the emulator.There you can see the emulator control.From there select your device and run it.Hope it will solve your problem.
I had BlueStacks android app player installed. Its an application that runs on mac and pc allowing you to emulate android. Looks like it uses the android emulator under the covers. To uninstall on mac, go to Library>bluestacksplayer and uninstall app ... .solved the emulator 5554 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.