Develop Reference

Emulator doesn't start in eclipse

I've tried to find answers and similar problems, but nothing has fixed the problem.
I created a project and wanted to run the emulator to check if everything is working fine. But the emulator doesn't start up. It gives the following ouput, in console:
[2015-01-08 10:20:06 - MTNInfoHub] ------------------------------
[2015-01-08 10:20:06 - MTNInfoHub] Android Launch!
[2015-01-08 10:20:06 - MTNInfoHub] adb is running normally.
[2015-01-08 10:20:06 - MTNInfoHub] Performing com.mtninfohub.MainHub activity launch
[2015-01-08 10:20:33 - MTNInfoHub] Launching a new emulator with Virtual Device 'test'
[2015-01-08 10:20:33 - Emulator] ko:Could not create temp file for system partition image: %s,size=0x%llx
[2015-01-08 10:20:33 - Emulator]
Please help me.
Running on centos, 32 bit architecture

Had this problem with Android Studio. To fix it, I just ran Android Studio as administrator.

NAND error in Hello World project in the official Android developer tutorial

I'm working on the Hello World project at http://developer.android.com/resources/tutorials/hello-world.html
The trouble comes when I run the application. The sequence of messages I get is something like:
[2012-04-30 15:13:19 - HelloAndroid] ------------------------------
[2012-04-30 15:13:19 - HelloAndroid] Android Launch!
[2012-04-30 15:13:19 - HelloAndroid] adb is running normally.
[2012-04-30 15:13:19 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch
[2012-04-30 15:13:19 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'my_avd'
[2012-04-30 15:13:19 - HelloAndroid] Launching a new emulator with Virtual Device 'my_avd'
[2012-04-30 15:13:25 - Emulator] NAND: could not write file /tmp/android-jhsu/emulator-7iTL7m, File exists
What exactly is stopping the process from executing properly? What do I need to do to fix this?
UPDATE 1:
OK, I tried your suggestions about clearing the avd.
I went into my android_sdk_linux directory and entered "tools/android list avd". The output was:
Available Android Virtual Devices:
Name: my_avd
Path: /home/jhsu/.android/avd/my_avd.avd
Target: Android 4.0.3 (API level 15)
ABI: armeabi-v7a
Skin: WVGA800
So I entered "tools/emulator -avd my_avd -wipe-data". The output was:
NAND: could not write file /tmp/android-jhsu/emulator-5FHEn7, File exists
But I looked in the /tmp/android-jhsu directory and saw no file at all, not even a hidden file.
Where do I go from here?

I was able to fix it exporting ANDROID_TMP
export ANDROID_TMP=/home/myuser

For me at least, I'd let my disk run out of space without realizing it.
It was just coincidence that this was the first item that failed.

It's a real disturbing situation when error can't completely describe problem in detail!
finally I figured out all this kind of error messages ("File Exists" and "There is no space") are due to small amount of mounted space on /tmp folder.
in Linux try mount and you'll see specified parameters of tmpfs and /tmp
changing $ANDROID_TMP value is not a proper solution and even doesn't work at all.
try editing fstab
sudo gedit /etc/fstab
and increase /tmp size to a larger value that makes sense to you (like:1500M)
then reboot system
PS: It's not IDE-dependent (Eclipse or Android-Studio) but something that deal with AVD Emulator

android app won't install

I recently bought a couple of books on android programming and have been having a terrible time getting anything to work. I finally got one of the books sample code to show up. I noticed that when it worked that in the eclipse console it showed installation logging. In everything else I've tried it never gets to that point. All I ever get is what is shown below. Does anyone know why it doesn't continue to the installation point?
I also noticed that in the code that does work, there's a folder structure in the bin directory that matches the src directory.
src>com.deitel.doodlz
bin>com>deitel>doodlz - contains all the class files
In my project, there is no folder structure like this in my bin directory. Is there something else I need to do besides just hitting the run button? Do I have to do some type of build first? Thanks.
[2012-03-12 21:21:52 - Now2] ------------------------------
[2012-03-12 21:21:52 - Now2] Android Launch!
[2012-03-12 21:21:52 - Now2] adb is running normally.
[2012-03-12 21:21:52 - Now2] Performing my.android.stuff.Now2Activity activity launch
[2012-03-12 21:21:52 - Now2] Automatic Target Mode: Preferred AVD 'android_2_3_3' is not available. Launching new emulator.
[2012-03-12 21:21:52 - Now2] Launching a new emulator with Virtual Device 'android_2_3_3'
[2012-03-12 21:21:57 - Emulator] emulator: WARNING: Unable to create sensors port: Unknown error
[2012-03-12 21:21:57 - Emulator] emulator: emulator window was out of view and was recentered
[2012-03-12 21:21:57 - Emulator]

Android Emulator issues on Windows 7 64-bit

I'm having a bit of an issue with the emulator launching from Eclipse. I have everything set up to the letter as far as I can tell and I'm just following the Hello, World example and when I try and run it after setting up the emulator I get this:
[2011-08-18 17:43:16 - Emulator] invalid command-line parameter: Files\Android\android-sdk\tools/emulator-arm.exe.
[2011-08-18 17:43:16 - Emulator] Hint: use '#foo' to launch a virtual device named 'foo'.
[2011-08-18 17:43:16 - Emulator] please use -help for more information

Don't use spaces in sdk path.If your sdk contains path like program files/sdk-windsows then it will prompt error.Place in a directory where no spaces exists

Android project run error

Whenever I run the project an error is displayed. It says:
[2011-07-18 13:36:34 - Emulator] invalid command-line parameter: Files\android-sdk\tools/emulator-arm.exe.
[2011-07-18 13:36:34 - Emulator] Hint: use '#foo' to launch a virtual device named 'foo'.
[2011-07-18 13:36:34 - Emulator] please use -help for more information
I am not getting what's wrong.

I also faced same issue. There is a bug with Android v12. See this discussion for your solution. And I followed Carl S answer. Now its working fine.