I am a beginner android developer and I had followed the instructions in the Quick Start and SDK Setup. After following all the steps I attempted to run the Hello World sample application and when I run the project, I get the standard "emulator.exe has encountered a problem and needs to close." box. I tried running the avd that I created in the AVD manager with the same results. I also tried running the AVD from the command line, using "emulator.exe #my_avd". I've tried 2.1 and 2.2 platforms. I using Eclipse 3.5 SR2 with the android plug-in. I am running Windows XP SP3, 512MB RAM, Intel Core 2 Quad on a virtual machine using VM-Ware. My machine running the virtual machine has the 3GB max ram for a 32-bit machine.
Thanks in Advance,
Mark
In response to comments:
Android console says:
[2010-07-29 10:39:20 - HelloAndroid] ------------------------------
[2010-07-29 10:39:20 - HelloAndroid] Android Launch!
[2010-07-29 10:39:20 - HelloAndroid] adb is running normally.
[2010-07-29 10:39:20 - HelloAndroid] Performing odog.andriod.example.helloandroid.HelloAndriod activity launch
[2010-07-29 10:39:20 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'my_avd'
[2010-07-29 10:39:20 - HelloAndroid] Launching a new emulator with Virtual Device 'my_avd'
DDMS console says nothing.
I have not tried to run the emulator on the physical machine. I'm trying to keep the Android development machine "clean". My physical machine has Visual Studio 2010, 2008, 6, Windows Platform SDKs, DirectX SDKs of various versions as well as various versions of Eclipse for micro-controller and BlackBerry programming. Little mucky .... needs to be formatted.
It seems deleting and reinstalling all the packages in the Android SDK and AVD Manager worked. Thanks for interest.
Related
Recently I tried to learn Android programming. I installed Eclipse, Android SDK, almost 10 GB of data with SDK Manager. I create new project and AVD. When I run the code, all I see on the console is this :
[2015-02-18 20:16:27 - Hey] ------------------------------
[2015-02-18 20:16:27 - Hey] Android Launch!
[2015-02-18 20:16:27 - Hey] adb is running normally.
[2015-02-18 20:16:27 - Hey] Performing com.example.hey.MainActivity activity launch
[2015-02-18 20:16:27 - Hey] Automatic Target Mode: Preferred AVD 'AndroidEmu' is not available. Launching new emulator.
[2015-02-18 20:16:27 - Hey] Launching a new emulator with Virtual Device 'AndroidEmu'
[2015-02-18 20:16:45 - Hey] New emulator found: emulator-5554
[2015-02-18 20:16:45 - Hey] Waiting for HOME ('android.process.acore') to be launched...
And all I see is emulator with android logo. I waited almost half an hour, I tried almost every method on internet, I am working on this problem since yesterday and now I am completely stuck.
I have 32-Bit Windows 7, 4 GB RAM, Intel Core 2Duo CPU. I have an old computer, is this the problem?
I really need help, I want to learn Android so much but thanks to these problems, I couldn't try anything.
Android Emulator is known for being really slow. I would recommend you to take a look at Genymotion. https://www.genymotion.com/
It's a lot better experience.
Its better to try your own real device as per my opinion
Please consider trying Android Studio instead of Eclipse. It is the newer and officially supported IDE for android development. Doing so will allow you to use HAXM, which is Intel's tool to allow your emulator to make use of hardware acceleration. You should see considerable speed improvements with it.
https://software.intel.com/en-us/android/articles/installation-instructions-for-intel-hardware-accelerated-execution-manager-windows
Whenever I tried to run any projects from my eclipse following message thrown up in the console window
[2014-07-30 06:32:53 - Project_Name] ------------------------------
[2014-07-30 06:32:53 - Project_Name] Android Launch!
[2014-07-30 06:32:53 - Project_Name] adb is running normally.
[2014-07-30 06:32:53 - Project_Name] Performing com.example.workingver1.HomeScreen activity launch
[2014-07-30 06:32:54 - Project_Name] Automatic Target Mode: launching new emulator with compatible AVD 'AVD_for_5_4_FWVGA'
[2014-07-30 06:32:54 - Project_Name] Launching a new emulator with Virtual Device 'AVD_for_5_4_FWVGA'
[2014-07-30 06:32:54 - Emulator] unknown option: -dns
[2014-07-30 06:32:54 - Emulator] please use -help for a list of valid options
What could be the problem?
I tried following things but couldn't rectify it.
Clean Project and Run
Tried Windows->preference->launch (Launch Settings)
Delete my existing AVD and Create a new one, that too didn't work
Any suggestions?
in Eclipse
Select Windows -> Preference
Android -> Launch -> Default Emulator Option ->
Paste this: -Dns-server 8.8.8.8,8.8.4.4
than Apply -> OK
clean up your project
check for ANDROID ARM system image is available installed properly
open Android virtual device
check your API levels properly
select Arm
it might be an ARM Ram problem too .. if you use core i3 system processor choose 512 ram in Avd or choose any other emulator with 512 Ram I suggest you to go with android API level 19 or 20 with Android Nexus one Emulator its the better emulator which starts easily.
and
start the emulator launch it
once your Emulator starts running then run your app
Try this,
clean up the project
set the default emulator option in windows
1. preference
2. android
3. launch
I just configured eclipse on Ubuntu 11.10 for Android Development.
When i try to launch Emulator it shows me following error.
Console says:
[2012-08-24 22:15:12 - Test two] Android Launch!
[2012-08-24 22:15:12 - Test two] adb is running normally.
[2012-08-24 22:15:12 - Test two] Performing com.project.test.two.MainActivity activity launch
[2012-08-24 22:15:12 - Test two] Automatic Target Mode: launching new emulator with compatible AVD 'avd14'
[2012-08-24 22:15:12 - Test two] Launching a new emulator with Virtual Device 'avd14'
[2012-08-24 22:15:12 - Test two] Launch canceled!
I also have installed ARM EABI v7a System image API level 14 (4.0)
SDK platform, Google APIs and sample SDKs are also installed as per shown in SDK manager.
Android SDK tools: 20.0.3
Android SDK platform-tools 14
How do i tackle it?
run this command in your terminal
chmod +x /sdk/tools/android
It works fine for me for the same problem. Try this.
I am trying to learn about Android development. I have installed Eclipse (3.6.2) the ADT plugin (10.0.1) and the Android SDK (r11 off the official site) all are installed as 32 bit but my OS is Windows 7 64-bit.
What happens is I run my app (HelloAndroid) and the emulator and I see the main wallpaper screen but then then nothing happens! I have looked on the emulator for the app and cannot find it anywhere.
My console output is shown below...
[2011-05-20 19:14:20 - HelloAndroid] ------------------------------
[2011-05-20 19:14:20 - HelloAndroid] Android Launch!
[2011-05-20 19:14:20 - HelloAndroid] adb is running normally.
[2011-05-20 19:14:20 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch
[2011-05-20 19:14:20 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'Android2.1'
[2011-05-20 19:14:20 - HelloAndroid] Launching a new emulator with Virtual Device 'Android2.1'
My AVD (Android Virtual Device) is set up as the tutorial suggests and the target is Android2.1-update1-API Level 7.
I have installed this app on my phone (HTC Hero, Android 2.1) and it works fine, but before I try and write other applications I need to get the emulator working, has anyone encountered this issue before?
I have looked online and cannot find a solution that solves my problem.
Thanks for your help in advance.
You can use adb to install your app. Find the bin directory in your eclipse workspace. There should be a YOUR_PROJECT_NAME.apk file there. To install it, from the command line, run:
adb install -r YOUR_PROJECT_NAME.apk
You will need adb in your path.
Start the emulator, switch to the logcat view in Eclipse (Window -> show view -> other ... -> logcat).
Clear the console output for logcat.
Try to deploy your application.
What does the output in logcat say? Does it display an error message?
On Windows 7 64-bit, running Eclipse 3.6 64-bit, JDK (jdk1.6.0_23) 64-bit and Android 2.3 (bitness?), running a program via Eclipse's Run|Run (Ctrl+F11) invokes the android emulator, but won't install .apk on the emulator (and certainly won't run it).
(update, answering #Computerish's question) All I am getting at Eclipse's Console is:
[2010-12-16 10:23:33 - HelloAndroid] ------------------------------
[2010-12-16 10:23:33 - HelloAndroid] Android Launch!
[2010-12-16 10:23:33 - HelloAndroid] adb is running normally.
[2010-12-16 10:23:33 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch
[2010-12-16 10:23:33 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'AVD23'
[2010-12-16 10:23:33 - HelloAndroid] Launching a new emulator with Virtual Device 'AVD23'
This problem doesn't happen on Windows XP, running Eclipse 3.5.2 and Android 2.2 (all 32-bit).
I tried the solution suggested by the accepted answer in this thread but it didn't help. Task manager shows adb's Image Name as 'adb.exe *32'. Perhaps there is a mismatch between the bitness of Eclipse+JDK (64-bit) and the Android emulator/SDK?
Is Android development using 64-bit JDK not possible (yet)?
OK, here is the final answer (as of today): Android development, using 64-bit JDK only, is not possible (yet).
If you install the 64-bit Eclipse and install only the 32-bit JDK, Eclipse will refuse to start.
So, if you decided to install the 64-bit Eclipse, you need to install both the 64-bit JDK and the 32-bit JDK.
Thereafter, even the infamous installer_r08-windows.exe will run (and even invoke "SDK Manager.exe" automatically for you).
But 64-bit Eclipse still won't install .apk on Android emulator.
Conclusion: Google is absolutely correct in stating that Android is not supported (yet) under 64-bit Windows. The fact that some geniuses manages to do some magic to make their environment work is beyond me.
I suppose that 32-bit ADB waits for 32-bit JDK. Just install 32-bit JDK - and everything should work after that. i'm running Android SDK on 64 bit machine with both installed JDK's 32 and 64 bits - and everything is OK
I know this might be late, but I found a fix for it.
I'm running:
-64-bit Windows 7
-64-bit Java 1.7 SDK
-64-bit Eclipse for Java Developers + ADT Plugin
-64-bit Android SDK
So what I do is save my java source files, and run the application through Eclipse. I close the emulator after it fully loads to the home screen. Next, I go to my command prompt in Win7 and type emulator -verbose -avd youravdname. After you press enter, Eclipse will decide to upload and install the .apk file onto the emulator. Now you can see your new activities!
It's very cumbersome, and I wonder why this even works. I seriously spent hours wondering if I even installed everything correctly.
I had the same problem as the original poster and I'm also using Android SDK 2.3, Eclipse Helios, JDK 1.6.0_23 64-bit on Windows 7 Professional 64-bit.
However, once I've killed the adb.exe *32 process and then restarted eclipse and then tried running HelloAndroid app again, the emulator started successfully, the app *.apk was loaded and ran perfectly.
I didn't do anything else and I haven't installed JDK 32-bit on my machine.