Hi!
I just wanted to play around with the Android SDK and write some "Hello, world!" applications, because I think the world needs more of those ;-)
But I have a problem with the emulator: it doesn't find my AVDs. I get a correct list of the avds by using
Code:
android list avd
but when running the avd with the emulator
Code:
emulator @myavd
I get the error message:
Code:
emulator: ERROR: unknown virtual device name: 'myavd'
emulator: could not find virtual device named 'myavd'
.
I'm using Windows 7 RC1 32bit.
Anyone any idea how to fix this?
Bye
Christian
I've seen similar problems from time to time. I found it best to create AVDs from within Eclipse when possible (don't forget to set up an emulated SD card of *more* than 8MB at the same time associated with each AVD).
Christian S. said:
Hi!
I just wanted to play around with the Android SDK and write some "Hello, world!" applications, because I think the world needs more of those ;-)
But I have a problem with the emulator: it doesn't find my AVDs. I get a correct list of the avds by using
Code:
android list avd
but when running the avd with the emulator
Code:
emulator @myavd
I get the error message:
Code:
emulator: ERROR: unknown virtual device name: 'myavd'
emulator: could not find virtual device named 'myavd'
.
I'm using Windows 7 RC1 32bit.
Anyone any idea how to fix this?
Bye
Christian
Click to expand...
Click to collapse
Use this instead
Code:
emulator -avd myavd
Hi!
Thank you for the answers!
I found the problem:
The "android" tool created the AVDs in the directory "d:\.android\", the emulator expects them in "c:\users\<username>\.android\".
I created an NTFS junction as workaround and it works now
Bye
Christian
I am having this same problem but with vista please help...
I am getting the following error
[2009-08-11 22:18:33 - Emulator] emulator: ERROR: unknown virtual device name: 'my_avd'
[2009-08-11 22:18:33 - Emulator] emulator: could not find virtual device named 'my_avd'
and I am not sure why. I am very new to eclipse, but want to get started with android development. How would I tell ecipse to look in the correct directory to find the AVD?
I look forward to hearing back.
Cheers
DG
The "android" tool created the AVDs in the directory "d:\.android\", the emulator expects them in "c:\users\<username>\.android\".
I created an NTFS junction as workaround and it works now
Click to expand...
Click to collapse
That was exactly my problem, I've moved my "HOME" directory on another disk, and I can't launch emulator.
But now, with your NTFS junction method, it's OK !!
Hey there guys you've probably already sorted this but after you create your avd just cd to the tools folder of the sdk and type
emulator -avd (your name)
the avd will be created in the same directory as your sdk for example i type
cd C:/sdk/android/tools
emulator -avd Sheilds1.5 -sdcard C:/sdcard.img
Hope this helps
Shields
also link here to explain all
http://developer.android.com/guide/developing/tools/avd.html
On Vista, android creates the avd folder under C:\Users\<username>\.android . It does this even if you are logged into a domain account (i.e. it doesn't create a C:\Users\<domain>.<username>\.android folder. This will cause the "unknown virtual device" error also. Copy the .android folder to C:\Users\<domain>.<username> and you will be good to go.
Nice one, Christian. The ntfs juction/mklink did the trick for me
Christian S. said:
Hi!
Thank you for the answers!
I found the problem:
The "android" tool created the AVDs in the directory "d:\.android\", the emulator expects them in "c:\users\<username>\.android\".
I created an NTFS junction as workaround and it works now
Bye
Christian
Click to expand...
Click to collapse
ok thanks very much! , it solves my problem
bye
Guillaume
What NTFS function???
alexadvance said:
That was exactly my problem, I've moved my "HOME" directory on another disk, and I can't launch emulator.
But now, with your NTFS junction method, it's OK !!
Click to expand...
Click to collapse
What NTFS function are you speaking of???!!!!?!?!?
If you have moved your home folder from c:\users\myUser to D:\myUser for example, you need to open a command line (cmd.exe) and do the following :
1. cd c:\users\myUser
2. mklink /j .android d:\myUser\.android
so that android will think files are in c:\users\myUser\.Android
Hope it will help you.
sybux said:
If you have moved your home folder from c:\users\myUser to D:\myUser for example, you need to open a command line (cmd.exe) and do the following :
1. cd c:\users\myUser
2. mklink /j .android d:\myUser\.android
so that android will think files are in c:\users\myUser\.Android
Hope it will help you.
Click to expand...
Click to collapse
Thanks a lot, I also met this problem, and this method really worked.
that's not even "c:\users\<username>\.android\" ... it's one directory up relative to My documents folder, that's where they're created. christian has probably moved his "my documents" folder to D:, that's why he has the d:\.android folder ... but that's the java problem, ... it has property UserDir which points to c:\users\<username> but differs from what some other elements evaluate user home path.
Environment Var > Link
Maybe I'm being stubborn, but I'm not a big fan of the symlinks or junction points or whatever.
via Yahoo! Answers and another random blog
You can override the behavior of both by declaring an environment
variable called ANDROID_SDK_HOME
Make it point to your HOME folder ( EX : C:\Documents and Settings\Phoenix\
) and both the emulator and the java based tools will read
and write into the same folder.
Pugz3D said:
Maybe I'm being stubborn, but I'm not a big fan of the symlinks or junction points or whatever.
via Yahoo! Answers and another random blog
You can override the behavior of both by declaring an environment
variable called ANDROID_SDK_HOME
Make it point to your HOME folder ( EX : C:\Documents and Settings\Phoenix\
) and both the emulator and the java based tools will read
and write into the same folder.
Click to expand...
Click to collapse
TY for the Advice!
For me, making a junction from my homedir to c:\users\{username} didn't work, but setting the ANDROID_SDK_HOME to my actual home dir did.
I've raised this so SDK guys were aware:
code.google.com/p/android/issues/detail?id=13008
Christian S. said:
Hi!
Thank you for the answers!
I found the problem:
The "android" tool created the AVDs in the directory "d:\.android\", the emulator expects them in "c:\users\<username>\.android\".
I created an NTFS junction as workaround and it works now
Bye
Christian
Click to expand...
Click to collapse
Tienes razón, esta sí es la solución al problema:
1. copias la carpeta .android dentro del directorio del usuario c:\users\<usermane>\
2. Vuelves a correr el emulador, y listo. Funciona perfecto.
Chao,
pedrozopayares
Another solution
I've run into a similar problem with the same error output and here is a short description of the malady and the cure:
If you run tools/android and install with sudo (don't know why I did that anyway ), it gives the same error while trying to run the emulator. So, don't. Just use your regular user privileges.
I'm trying to get some custom code compiled for android, but when I try to make the file, it requires a function called errx in libc -> err.h.
When I use the one I have on my system and try to recompile libc.so, I get the following compilation error:
Code:
In file included from bionic/libc/unistd/getopt_long.c:59:
bionic/libc/include/err.h:35: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'extern'
In file included from bionic/libc/unistd/getopt_long.c:60:
bionic/libc/include/errno.h:45: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'extern'
If I try to delete the contents or err.h, I get no errors.
Note that I'm not modifying errno.h in any way.
Is there a workaround for this?
I'd really like a workaround to this.
I have recently returned to Linux after using Windows, and cannot set up the SDK.
I have altered the PATH, but when running command: adb, I get this error
HTML:
[[email protected] tools]$ adb
adb: error while loading shared libraries: libncurses.so.5: cannot open shared
object file: No such file or directory
I have now fixed.
For anyone who has this problem in the gfuture, the solution is simple:
Go to install/remove software and search for libncurses. Download and install all files. (there should only be 4) Now try again.
Mods, lock this thread please.
It seems it is not an easy thing to start android development. I followed the official instruction and tried to run the MyFirstApp example from developer.android.com on my Windows 7 64bit machine with AVD. But after 2 days effort, I am still cannot make it work for me in Eclipse and in adb command line.
The best I reached in command line approach is the following -- the second block with italic words shows the error I got:
Code:
E:\Workspace\MyFirstApp>ls bin
AndroidManifest.xml build.prop
AndroidManifest.xml.d classes
MyFirstApp-debug-unaligned.apk classes.dex
MyFirstApp-debug-unaligned.apk.d classes.dex.d
MyFirstApp-debug.apk dexedLibs
MyFirstApp.ap_ proguard.txt
MyFirstApp.ap_.d res
[I][B]E:\Workspace\MyFirstApp>adb install bin\MyFirstApp-debug.apk
failed to copy 'bin\MyFirstApp-debug.apk' to '/data/local/tmp/MyFirstApp-debug.a
pk': No such file or directory
rm failed for /data/local/tmp/MyFirstApp-debug.apk, No such file or directory[/B][/I]
I hope somebody can help me about these:
1. I am in Windows with AVD, why adb want to find /data/local/tmp, which is linux style location?
2. where does the adb try to copy the apk file to? My SDK is installed under "C:\Users\myname\AppData\Local\Android\android-sdk". There is no space in the address path. The source apk file is ready and should not be the cause of that error, I think.
3. Any configuration of the installed SDK needs to be modified in Windows machine? I think the SDK manager should be able to figure out what the machine is and download/install appropriate components for the user. Is that right?
I have similar or the same issue by using Eclipse.
thanks,
I am cross compiling C, C++ code that uses small static libraries to build a single larger shared library.
When it tries to build the shared library I get errors:
bin/ld: error: no archive symbol table (run ranlib)
I dig down to the build directory and the 'link.txt' file has
"gcc-ar ....."
I am using the android.toolchain.cmake file for the CMAKE_TOOLCHAIN_FILE.
When I change the 'link.txt file to have:
arm-...-ar library
arm...-ranlib library.a
the shared library link works.
Any suggestions on how to get cmake to generate the right link.txt file?