I'm unable to start the emulator. I can create new devices in the AVD, they appear with a little green tick next to the name, but they do not start. No emulator loads up. No error message shows up either. I've tried waiting for over 15 minutes.
The same happens when I try to load it up on eclipse. I have a test project. It compiles & tries to launch, I get the message below on the console after which nothing happens.
[2012-05-13 15:26:30 - TestApp] ------------------------------
[2012-05-13 15:26:30 - TestApp] Android Launch!
[2012-05-13 15:26:30 - TestApp] adb is running normally.
[2012-05-13 15:26:30 - TestApp] Performing com.test.testapp.TestAppActivity activity launch
[2012-05-13 15:26:30 - TestApp] Automatic Target Mode: launching new emulator with compatible AVD 'MyAVD'
[2012-05-13 15:26:30 - TestApp] Launching a new emulator with Virtual Device 'MyAVD'
Weird thing is, it used to work before I had formatted & re-installed Windows.
I don't know where I'm going wrong; I've tried searching on Google & StackOverflow to find a solution & I've tried all the solutions I found with no success.
Class Path is set. SDK installed to a location with no spaces in the path. Restarted. Re-Installed. Changed "Launch Default Activity", "Automatic Target" to "Manual". No luck. There is no running Android Device. Can anyone shed some light on this issue?
Details:
64 Bit Windows
32 Bit JDK
32 Bit Java EE Eclipse Extracted to "C:\eclipse"
Android SDK Installed to "C:\android-sdk"
PATH variable includes:
";C:\Program Files (x86)\Java\jdk1.7.0_04\bin"
";C:\android-sdk\platform-tools"
";C:\android-sdk\tools"
Related
The standard new app HelloWorld doesn't run as it in the Android emulator.
On Apple Mac, I created an AVD : Nexus7-4.3-JellyBean ( Android 4.3 API 18 , CPU/ABI ARM(armabi-v7a) RAM 343 VM Heap 32 / Storage 200 MiB / SD Card 128 MiB)
then running HelloWorld from Eclipse ADT , I get the following in the console log ( no error stated ...)
[2013-12-07 16:11:22 - HelloWorld] ------------------------------
[2013-12-07 16:11:22 - HelloWorld] Android Launch!
[2013-12-07 16:11:22 - HelloWorld] adb is running normally.
[2013-12-07 16:11:22 - HelloWorld] Performing com.example.helloworld.MainActivity activity launch
[2013-12-07 16:11:22 - HelloWorld] Automatic Target Mode: launching new emulator with compatible AVD 'Nexus7-4.3-JellyBean'
[2013-12-07 16:11:22 - HelloWorld] Launching a new emulator with Virtual Device 'Nexus7-4.3-JellyBean'
The emulator is launched, it displays the Android log, then unlocking it with Fn F2 I get the home page and I can see the list of apps BUT HelloWorld is not there.
Why can't I see any information or at least any error?
Try resetting your adb as explained in
The Console log is not complete yet, after starting the emulator, apk installing will start then launching,
Try to manually start the emulator then run your app and choose the already running emulator and see what happen.
- I wanted to post this as a comment but it takes 50 reputation to do so :)
I am following the Phonegap Android getting started guide: http://docs.phonegap.com/en/2.4.0/guide_getting-started_android_index.md.html#Getting%20Started%20with%20Android
After a lot of fiddling, I have got everything running with the following versions:
Phonegap 2.4
Android SDK tools 21.1
Android SDK platform tools 16.0.1
Android SDK Platform 4.2
When I run the app in the emulator (via Eclipse), it launches but shows the flashing Android logo. If I right-click the project and run again, the console shows the app is installing and launched. However, the android logo remains.
Console log:
[2013-02-21 02:27:16 - testapp] Waiting for HOME ('android.process.acore') to be launched...
[2013-02-21 02:28:04 - testapp] ------------------------------
[2013-02-21 02:28:04 - testapp] Android Launch!
[2013-02-21 02:28:04 - testapp] adb is running normally.
[2013-02-21 02:28:04 - testapp] Performing com.rb.testapp.testapp activity launch
[2013-02-21 02:28:05 - testapp] Automatic Target Mode: using existing emulator 'emulator-5554' running compatible AVD 'test'
[2013-02-21 02:28:05 - testapp] Uploading testapp.apk onto device 'emulator-5554'
[2013-02-21 02:28:45 - testapp] Installing testapp.apk...
[2013-02-21 02:29:04 - testapp] Success!
[2013-02-21 02:29:05 - testapp] Starting activity com.rb.testapp.testapp on device emulator-5554
If I run the app from the command line /cordova/run.bat. The Emulator launches with a blank screen. The console reports the app is installed and launching.
I'm guessing there's a problem with the version of the emulator i'm running. My CPU does not support virtualisation. Is there any way to get this running?
Many thanks.
Well, I fixed this myself by installing the Android SDK 4.0 platform and using this for my emulator. Aparrently there is a fix for this (although I haven't tried this): PhoneGap not firing deviceready on Android 4.2
I have documented my setup process here: http://cookieflow.wordpress.com/2013/02/24/installing-android-4-2-sdk-and-phonegap-2-4-0-on-windows-7/
I created a 'hello' project. I didn't change anything about the default template generated by eclipse. Then I ran the application. I didn't get any error. However, the application isn't being installed on the emulator.
environment :
windows7 x64
jdk-7u7-windows-x64
installer_r20.0.3-windows
eclipse-jee-juno-SR1-win32-x86_64
I googled many articles, but I didn't find any solutions.
[2012-10-15 16:39:42 - hello] Android Launch!
[2012-10-15 16:39:42 - hello] adb is running normally.
[2012-10-15 16:39:42 - hello] Performing com.example.hello.MainActivity activity launch
[2012-10-15 16:39:42 - hello] Automatic Target Mode: launching new emulator with compatible AVD 'AndroidAVD4.1.2'
[2012-10-15 16:39:42 - hello] Launching a new emulator with Virtual Device 'AndroidAVD4.1.2'
[2012-10-15 16:39:42 - Emulator] emulator: warning: opening audio input failed
I have read many similar article for 1 week, and I've tried
many things to fix this problem :
various android sdk version re-install
project re-creation
avd re-creation
change eclipse workspace
Changing android sdk folder to root with no space.
the re-start adb and eclipse.
As a trial, I uninstalled all anti-virus and defense software, then performed a reboot.
This solved my problem.
I just began to learn android. I'm using Windows XP, eclipse indigo JavaEE and its ADT. Then I was trying out the official Hello World. I've created an AVD and paste the code. But when I run the program, problem occured during AVD initialization. Here's the log:
[2011-11-15 15:53:33 - helloworld] --------------
[2011-11-15 15:53:33 - helloworld] Android Launch!
[2011-11-15 15:53:33 - helloworld] adb is running normally.
[2011-11-15 15:53:33 - helloworld] Performing com.helloworld.HelloworldActivity activity launch
[2011-11-15 15:53:33 - helloworld] Automatic Target Mode: launching new emulator with compatible AVD 'myAVD'
[2011-11-15 15:53:33 - helloworld] Launching a new emulator with Virtual Device 'myAVD'
[2011-11-15 15:53:35 - Emulator] NAND: could not write file C:\DOCUME~1\qi\LOCALS~1\Temp\\AndroidEmulator\TMP185.tmp, No space left on device
There's plenty spaces in my C:\ and I was very confused about the No space left. And the folder is empty. The number "185" changes if I press "Run" again.
I was using Android 4.0. I've tried restarting, and changing to Android 2.2. None works. I've done this "hello world" on another machine. It worked.
Open AVD manager and Edit your Emulator at which your are working on.
Wipe data and then increase the SD Card size of your Emulator which will solve the problem.
Looks like you've run out of free disk space on volume C: (either that, or the guys who commented the question are right and it's complaining about SD card size).
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?