[android-beginners] Re: About ERROR: unknown virtual device name: 'myavd'
Mr Ducrohet, Thank, this solution worked for me!! On 25 ago, 20:41, Xavier Ducrohet x...@android.com wrote: I see that you have changed the location of the user folders (in S: instead of C:) When the user location is not the default one, we have seen some cases where windows reports the location of the user folder differently depending on which API you use (the command line tool and Eclipse use a Java API, while the emulator use a windows C++ API). You can override the behavior of both by declaring an environment variable called ANDROID_SDK_HOME Make it point to your HOME folder (S:\Documents and Settings\Phoenix\ in this case) and both the emulator and the java based tools will read and write into the same folder. Xav On Tue, Aug 25, 2009 at 6:21 AM, Phoenixphoenixsen...@gmail.com wrote: I also have the same error. I've tried creating the AVD on the command line and via the gui in the Eclipse plugin. Both created the AVD with no problems, but the emulator still cannot find it. I've tried running with the configuration set to Automatic, and to Manual and manually selecting Launch a new Android Virtual Device and checking the box next to 'my_avd', and the emulator still cannot find it. I know it exists, I can see it in S:Documents and Settings \Phoenix\.android\avd\my_avd.avd I've tried stopping and re-starting the ADB server, stopping and re- starting Eclipse... nothing has fixed it. This is on a new setup, just set up today. Eclipse Galileo, Android SDK 1.5_r3 for Windows, on XP. The complete console: [2009-08-25 06:11:11 - HelloAndroid] -- [2009-08-25 06:11:11 - HelloAndroid] Android Launch! [2009-08-25 06:11:11 - HelloAndroid] adb is running normally. [2009-08-25 06:11:11 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch [2009-08-25 06:11:11 - HelloAndroid] Automatic Target Mode: Preferred AVD 'my_avd' is not available. Launching new emulator. [2009-08-25 06:11:11 - HelloAndroid] Launching a new emulator with Virtual Device 'my_avd' [2009-08-25 06:11:12 - Emulator] emulator: ERROR: unknown virtual device name: 'my_avd' [2009-08-25 06:11:12 - Emulator] emulator: could not find virtual device named 'my_avd' -- Xavier Ducrohet Android Developer Tools Engineer Google Inc. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Beginners group. To post to this group, send email to android-beginners@googlegroups.com To unsubscribe from this group, send email to android-beginners-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~--~~~~--~~--~--~---
[android-beginners] Re: About ERROR: unknown virtual device name: 'myavd'
2009/9/16 Nicolas Gramlich stoeps...@gmx.de Hi, just tried this again with the ADT 0.9.3 (downloaded today) and Android 1.6 r1 (also from today) and in the Virtual Devices-Window I can see my newly created AVD with a green checker to the left: A valid Android Virtual Device. ANDROID_SDK_HOME is properly set to C:\Users\nico; for user and system-environment variables. I can also see the emulator-image being properly created in C:\Users \nico\.android\avd\Emu_1_6.avd\userdata.img. I'm using Windows7 RC 64Bit with a 64 Bit JDK and Eclipse is running (or has to run) with its own 32 Bit JRE. Any ideas? On 27 Aug., 03:21, Xavier Ducrohet x...@android.com wrote: On Wed, Aug 26, 2009 at 4:21 AM, Phoenixphoenixsen...@gmail.com wrote: On Aug 25, 4:41 pm, Xavier Ducrohet x...@android.com wrote: I see that you have changed the location of the user folders (in S: instead of C:) There are user folders on both S: and C:. Only the Desktop and My Documents special folders are on S:. Everything else (including App Data) is on C:. [The documents are shared between operating systems on different partitions] Android (or Eclipse?) has been the only thing to use S:. When the user location is not the default one, we have seen some cases where windows reports the location of the user folder differently depending on which API you use (the command line tool and Eclipse use a Java API, while the emulator use a windows C++ API). That would explain why the command line tools and Eclipse could see my_avd just fine, but the emulator could not find it. But, shouldn't Android be set up to use HOMEDRIVE/HOMEPATH? Standard environment variables. I think there are difference on XP/Vista which makes using those hard to use (back in the previous SDK we were using LOCALAPPDATA but we ended up having the same problem). What we use on java is the user.home property setup by the VM. Looks like the Java VM thinks your home is in S:\... I look again into these 2 env variables and see if they could be used. Also, a single line in the installation instructions could have prevented this confusion. When Android can see the AVD from the command line and the Eclipse gui, but not from the emulator, and no explanation is given (especially on the first test project), it's ... disheartening. I agree. We should at least have the emulator output a message saying where it's looking for the AVD and how to fix the problem if it's not where the AVDs are created. In any event, with the ANDROID_SDK_HOME variable set to the S: home (which is not the real home directory, that is on C:), the emulator now works. Well we don't want to go and set a permanent env on your machine. I guess we could but relying on existing standard env variables should be better. I mean, what happens if the user removes it or change the location of his/her home folder but doesn't update this? In any case we do need to find a solution. Xav -- Xavier Ducrohet Android Developer Tools Engineer Google Inc. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Beginners group. To post to this group, send email to android-beginners@googlegroups.com To unsubscribe from this group, send email to android-beginners-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~--~~~~--~~--~--~---
[android-beginners] Re: About ERROR: unknown virtual device name: 'myavd'
Hi I had the same problem and for me the problem the emulator and an environment variable (HOMEPATH or USERPROFILE) instead of the registry (like android-tool.) I found the solution here: http://forums.pragprog.com/forums/67/topics/2709 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Beginners group. To post to this group, send email to android-beginners@googlegroups.com To unsubscribe from this group, send email to android-beginners-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~--~~~~--~~--~--~---
[android-beginners] Re: About ERROR: unknown virtual device name: 'myavd'
hmm. I answered you, but I cant see my post, so I'll try again .. in short. I had the sam problem, found the solution here: http://forums.pragprog.com/forums/67/topics/2709 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Beginners group. To post to this group, send email to android-beginners@googlegroups.com To unsubscribe from this group, send email to android-beginners-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~--~~~~--~~--~--~---
[android-beginners] Re: About ERROR: unknown virtual device name: 'myavd'
Hi, just tried this again with the ADT 0.9.3 (downloaded today) and Android 1.6 r1 (also from today) and in the Virtual Devices-Window I can see my newly created AVD with a green checker to the left: A valid Android Virtual Device. ANDROID_SDK_HOME is properly set to C:\Users\nico; for user and system-environment variables. I can also see the emulator-image being properly created in C:\Users \nico\.android\avd\Emu_1_6.avd\userdata.img. I'm using Windows7 RC 64Bit with a 64 Bit JDK and Eclipse is running (or has to run) with its own 32 Bit JRE. Any ideas? On 27 Aug., 03:21, Xavier Ducrohet x...@android.com wrote: On Wed, Aug 26, 2009 at 4:21 AM, Phoenixphoenixsen...@gmail.com wrote: On Aug 25, 4:41 pm, Xavier Ducrohet x...@android.com wrote: I see that you have changed the location of the user folders (in S: instead of C:) There are user folders on both S: and C:. Only the Desktop and My Documents special folders are on S:. Everything else (including App Data) is on C:. [The documents are shared between operating systems on different partitions] Android (or Eclipse?) has been the only thing to use S:. When the user location is not the default one, we have seen some cases where windows reports the location of the user folder differently depending on which API you use (the command line tool and Eclipse use a Java API, while the emulator use a windows C++ API). That would explain why the command line tools and Eclipse could see my_avd just fine, but the emulator could not find it. But, shouldn't Android be set up to use HOMEDRIVE/HOMEPATH? Standard environment variables. I think there are difference on XP/Vista which makes using those hard to use (back in the previous SDK we were using LOCALAPPDATA but we ended up having the same problem). What we use on java is the user.home property setup by the VM. Looks like the Java VM thinks your home is in S:\... I look again into these 2 env variables and see if they could be used. Also, a single line in the installation instructions could have prevented this confusion. When Android can see the AVD from the command line and the Eclipse gui, but not from the emulator, and no explanation is given (especially on the first test project), it's ... disheartening. I agree. We should at least have the emulator output a message saying where it's looking for the AVD and how to fix the problem if it's not where the AVDs are created. In any event, with the ANDROID_SDK_HOME variable set to the S: home (which is not the real home directory, that is on C:), the emulator now works. Well we don't want to go and set a permanent env on your machine. I guess we could but relying on existing standard env variables should be better. I mean, what happens if the user removes it or change the location of his/her home folder but doesn't update this? In any case we do need to find a solution. Xav -- Xavier Ducrohet Android Developer Tools Engineer Google Inc. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Beginners group. To post to this group, send email to android-beginners@googlegroups.com To unsubscribe from this group, send email to android-beginners-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~--~~~~--~~--~--~---
[android-beginners] Re: About ERROR: unknown virtual device name: 'myavd'
Nicolas, what's the problem exactly? To be honest, nothing has been done on the AVD handling since this thread was originally created. Xav On Wed, Sep 16, 2009 at 4:32 AM, Nicolas Gramlich stoeps...@gmx.de wrote: Hi, just tried this again with the ADT 0.9.3 (downloaded today) and Android 1.6 r1 (also from today) and in the Virtual Devices-Window I can see my newly created AVD with a green checker to the left: A valid Android Virtual Device. ANDROID_SDK_HOME is properly set to C:\Users\nico; for user and system-environment variables. I can also see the emulator-image being properly created in C:\Users \nico\.android\avd\Emu_1_6.avd\userdata.img. I'm using Windows7 RC 64Bit with a 64 Bit JDK and Eclipse is running (or has to run) with its own 32 Bit JRE. Any ideas? On 27 Aug., 03:21, Xavier Ducrohet x...@android.com wrote: On Wed, Aug 26, 2009 at 4:21 AM, Phoenixphoenixsen...@gmail.com wrote: On Aug 25, 4:41 pm, Xavier Ducrohet x...@android.com wrote: I see that you have changed the location of the user folders (in S: instead of C:) There are user folders on both S: and C:. Only the Desktop and My Documents special folders are on S:. Everything else (including App Data) is on C:. [The documents are shared between operating systems on different partitions] Android (or Eclipse?) has been the only thing to use S:. When the user location is not the default one, we have seen some cases where windows reports the location of the user folder differently depending on which API you use (the command line tool and Eclipse use a Java API, while the emulator use a windows C++ API). That would explain why the command line tools and Eclipse could see my_avd just fine, but the emulator could not find it. But, shouldn't Android be set up to use HOMEDRIVE/HOMEPATH? Standard environment variables. I think there are difference on XP/Vista which makes using those hard to use (back in the previous SDK we were using LOCALAPPDATA but we ended up having the same problem). What we use on java is the user.home property setup by the VM. Looks like the Java VM thinks your home is in S:\... I look again into these 2 env variables and see if they could be used. Also, a single line in the installation instructions could have prevented this confusion. When Android can see the AVD from the command line and the Eclipse gui, but not from the emulator, and no explanation is given (especially on the first test project), it's ... disheartening. I agree. We should at least have the emulator output a message saying where it's looking for the AVD and how to fix the problem if it's not where the AVDs are created. In any event, with the ANDROID_SDK_HOME variable set to the S: home (which is not the real home directory, that is on C:), the emulator now works. Well we don't want to go and set a permanent env on your machine. I guess we could but relying on existing standard env variables should be better. I mean, what happens if the user removes it or change the location of his/her home folder but doesn't update this? In any case we do need to find a solution. Xav -- Xavier Ducrohet Android Developer Tools Engineer Google Inc. -- Xavier Ducrohet Android Developer Tools Engineer Google Inc. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Beginners group. To post to this group, send email to android-beginners@googlegroups.com To unsubscribe from this group, send email to android-beginners-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~--~~~~--~~--~--~---
[android-beginners] Re: About ERROR: unknown virtual device name: 'myavd'
On Aug 25, 4:41 pm, Xavier Ducrohet x...@android.com wrote: I see that you have changed the location of the user folders (in S: instead of C:) There are user folders on both S: and C:. Only the Desktop and My Documents special folders are on S:. Everything else (including App Data) is on C:. [The documents are shared between operating systems on different partitions] Android (or Eclipse?) has been the only thing to use S:. When the user location is not the default one, we have seen some cases where windows reports the location of the user folder differently depending on which API you use (the command line tool and Eclipse use a Java API, while the emulator use a windows C++ API). That would explain why the command line tools and Eclipse could see my_avd just fine, but the emulator could not find it. But, shouldn't Android be set up to use HOMEDRIVE/HOMEPATH? Standard environment variables. You can override the behavior of both by declaring an environment variable called ANDROID_SDK_HOME Make it point to your HOME folder (S:\Documents and Settings\Phoenix\ in this case) and both the emulator and the java based tools will read and write into the same folder. Xav How did Android end up using S: in the first place? At that time, couldn't it set up it's own ANDROID_SDK_HOME variable to explicitly say which directory it would be using? (Of course, if it used HOMEDRIVE/HOMEPATH this would be unnecessary.) Also, a single line in the installation instructions could have prevented this confusion. When Android can see the AVD from the command line and the Eclipse gui, but not from the emulator, and no explanation is given (especially on the first test project), it's ... disheartening. In any event, with the ANDROID_SDK_HOME variable set to the S: home (which is not the real home directory, that is on C:), the emulator now works. Thank you, Xav. Hopefully if other people experience this odd problem, they will find this solution. (I'm still not sure why it isn't working for Tony) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Beginners group. To post to this group, send email to android-beginners@googlegroups.com To unsubscribe from this group, send email to android-beginners-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~--~~~~--~~--~--~---
[android-beginners] Re: About ERROR: unknown virtual device name: 'myavd'
still doesn't work why On Aug 26, 7:41 am, Xavier Ducrohet x...@android.com wrote: I see that you have changed the location of the user folders (in S: instead of C:) When the user location is not the default one, we have seen some cases where windows reports the location of the user folder differently depending on which API you use (the command line tool and Eclipse use a Java API, while the emulator use a windows C++ API). You can override the behavior of both by declaring an environment variable called ANDROID_SDK_HOME Make it point to your HOME folder (S:\Documents and Settings\Phoenix\ in this case) and both the emulator and the java based tools will read and write into the same folder. Xav On Tue, Aug 25, 2009 at 6:21 AM, Phoenixphoenixsen...@gmail.com wrote: I also have the same error. I've tried creating the AVD on the command line and via the gui in the Eclipse plugin. Both created the AVD with no problems, but the emulator still cannot find it. I've tried running with the configuration set to Automatic, and to Manual and manually selecting Launch a new Android Virtual Device and checking the box next to 'my_avd', and the emulator still cannot find it. I know it exists, I can see it in S:Documents and Settings \Phoenix\.android\avd\my_avd.avd I've tried stopping and re-starting the ADB server, stopping and re- starting Eclipse... nothing has fixed it. This is on a new setup, just set up today. Eclipse Galileo, Android SDK 1.5_r3 for Windows, on XP. The complete console: [2009-08-25 06:11:11 - HelloAndroid] -- [2009-08-25 06:11:11 - HelloAndroid] Android Launch! [2009-08-25 06:11:11 - HelloAndroid] adb is running normally. [2009-08-25 06:11:11 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch [2009-08-25 06:11:11 - HelloAndroid] Automatic Target Mode: Preferred AVD 'my_avd' is not available. Launching new emulator. [2009-08-25 06:11:11 - HelloAndroid] Launching a new emulator with Virtual Device 'my_avd' [2009-08-25 06:11:12 - Emulator] emulator: ERROR: unknown virtual device name: 'my_avd' [2009-08-25 06:11:12 - Emulator] emulator: could not find virtual device named 'my_avd' -- Xavier Ducrohet Android Developer Tools Engineer Google Inc.- Hide quoted text - - Show quoted text - --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Beginners group. To post to this group, send email to android-beginners@googlegroups.com To unsubscribe from this group, send email to android-beginners-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~--~~~~--~~--~--~---
[android-beginners] Re: About ERROR: unknown virtual device name: 'myavd'
On Wed, Aug 26, 2009 at 4:21 AM, Phoenixphoenixsen...@gmail.com wrote: On Aug 25, 4:41 pm, Xavier Ducrohet x...@android.com wrote: I see that you have changed the location of the user folders (in S: instead of C:) There are user folders on both S: and C:. Only the Desktop and My Documents special folders are on S:. Everything else (including App Data) is on C:. [The documents are shared between operating systems on different partitions] Android (or Eclipse?) has been the only thing to use S:. When the user location is not the default one, we have seen some cases where windows reports the location of the user folder differently depending on which API you use (the command line tool and Eclipse use a Java API, while the emulator use a windows C++ API). That would explain why the command line tools and Eclipse could see my_avd just fine, but the emulator could not find it. But, shouldn't Android be set up to use HOMEDRIVE/HOMEPATH? Standard environment variables. I think there are difference on XP/Vista which makes using those hard to use (back in the previous SDK we were using LOCALAPPDATA but we ended up having the same problem). What we use on java is the user.home property setup by the VM. Looks like the Java VM thinks your home is in S:\... I look again into these 2 env variables and see if they could be used. Also, a single line in the installation instructions could have prevented this confusion. When Android can see the AVD from the command line and the Eclipse gui, but not from the emulator, and no explanation is given (especially on the first test project), it's ... disheartening. I agree. We should at least have the emulator output a message saying where it's looking for the AVD and how to fix the problem if it's not where the AVDs are created. In any event, with the ANDROID_SDK_HOME variable set to the S: home (which is not the real home directory, that is on C:), the emulator now works. Well we don't want to go and set a permanent env on your machine. I guess we could but relying on existing standard env variables should be better. I mean, what happens if the user removes it or change the location of his/her home folder but doesn't update this? In any case we do need to find a solution. Xav -- Xavier Ducrohet Android Developer Tools Engineer Google Inc. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Beginners group. To post to this group, send email to android-beginners@googlegroups.com To unsubscribe from this group, send email to android-beginners-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~--~~~~--~~--~--~---
[android-beginners] Re: About ERROR: unknown virtual device name: 'myavd'
I also have the same error. I've tried creating the AVD on the command line and via the gui in the Eclipse plugin. Both created the AVD with no problems, but the emulator still cannot find it. I've tried running with the configuration set to Automatic, and to Manual and manually selecting Launch a new Android Virtual Device and checking the box next to 'my_avd', and the emulator still cannot find it. I know it exists, I can see it in S:Documents and Settings \Phoenix\.android\avd\my_avd.avd I've tried stopping and re-starting the ADB server, stopping and re- starting Eclipse... nothing has fixed it. This is on a new setup, just set up today. Eclipse Galileo, Android SDK 1.5_r3 for Windows, on XP. The complete console: [2009-08-25 06:11:11 - HelloAndroid] -- [2009-08-25 06:11:11 - HelloAndroid] Android Launch! [2009-08-25 06:11:11 - HelloAndroid] adb is running normally. [2009-08-25 06:11:11 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch [2009-08-25 06:11:11 - HelloAndroid] Automatic Target Mode: Preferred AVD 'my_avd' is not available. Launching new emulator. [2009-08-25 06:11:11 - HelloAndroid] Launching a new emulator with Virtual Device 'my_avd' [2009-08-25 06:11:12 - Emulator] emulator: ERROR: unknown virtual device name: 'my_avd' [2009-08-25 06:11:12 - Emulator] emulator: could not find virtual device named 'my_avd' --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Beginners group. To post to this group, send email to android-beginners@googlegroups.com To unsubscribe from this group, send email to android-beginners-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~--~~~~--~~--~--~---
[android-beginners] Re: About ERROR: unknown virtual device name: 'myavd'
I see that you have changed the location of the user folders (in S: instead of C:) When the user location is not the default one, we have seen some cases where windows reports the location of the user folder differently depending on which API you use (the command line tool and Eclipse use a Java API, while the emulator use a windows C++ API). You can override the behavior of both by declaring an environment variable called ANDROID_SDK_HOME Make it point to your HOME folder (S:\Documents and Settings\Phoenix\ in this case) and both the emulator and the java based tools will read and write into the same folder. Xav On Tue, Aug 25, 2009 at 6:21 AM, Phoenixphoenixsen...@gmail.com wrote: I also have the same error. I've tried creating the AVD on the command line and via the gui in the Eclipse plugin. Both created the AVD with no problems, but the emulator still cannot find it. I've tried running with the configuration set to Automatic, and to Manual and manually selecting Launch a new Android Virtual Device and checking the box next to 'my_avd', and the emulator still cannot find it. I know it exists, I can see it in S:Documents and Settings \Phoenix\.android\avd\my_avd.avd I've tried stopping and re-starting the ADB server, stopping and re- starting Eclipse... nothing has fixed it. This is on a new setup, just set up today. Eclipse Galileo, Android SDK 1.5_r3 for Windows, on XP. The complete console: [2009-08-25 06:11:11 - HelloAndroid] -- [2009-08-25 06:11:11 - HelloAndroid] Android Launch! [2009-08-25 06:11:11 - HelloAndroid] adb is running normally. [2009-08-25 06:11:11 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch [2009-08-25 06:11:11 - HelloAndroid] Automatic Target Mode: Preferred AVD 'my_avd' is not available. Launching new emulator. [2009-08-25 06:11:11 - HelloAndroid] Launching a new emulator with Virtual Device 'my_avd' [2009-08-25 06:11:12 - Emulator] emulator: ERROR: unknown virtual device name: 'my_avd' [2009-08-25 06:11:12 - Emulator] emulator: could not find virtual device named 'my_avd' -- Xavier Ducrohet Android Developer Tools Engineer Google Inc. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Beginners group. To post to this group, send email to android-beginners@googlegroups.com To unsubscribe from this group, send email to android-beginners-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~--~~~~--~~--~--~---
