Starting an AVD from a custom location

by Patrick » Mon, 28 Jun 2010 16:55:28 GMT

Sponsored Links

I want the android emulator to start a AVD from a non default location
using the following command:
./android-sdk-linux_86/tools/emulator -sysdir /opt/
development/.android/avd/ -avd AVD1.6_HTC_SD

The .android directory is a copy from the default .android directory
from my homefolder...

The emulator states the following:
emulator: ERROR: unknown virtual device name: 'AVD1.6_HTC_SD'
emulator: could not find virtual device named 'AVD1.6_HTC_SD'

Any ideas?


Starting an AVD from a custom location

by Xavier Ducrohet » Tue, 29 Jun 2010 03:58:50 GMT

 -sysdir cannot be used with AVDs.

you can overide the location of the .android folder by setting an env

In your case, you should try:
$ ANDROID_SDK_HOME=/opt/development emulator -avd AVD1.6_HTC_SD



Sponsored Links

Other Threads

1. Music for background

How can I set mp3 for background music in my app?


2. ActionBar problems

Hi All,

We're trying to use ActionBars on Honeycomb and stay backward
compatible with earlier code. Everything seemed to be fine when we
just used the default behaviors, like the upgrade of options menus to
show in the action bar as Actions.

But then the requirements got broader and they wanted us to start
styling the action bar, setting its background, adding the "go to
home" indicator to the icon and other things and we lost our backwards

I've been trying to figure it out and saw this paragaph in the "using
action bars" document:


In this example, the application requires a minimum version of API
Level 4 (Android 1.6), but it also targets API Level 11 (Android 3.0).
This way, when the application is installed on a device running
Android 3.0 or greater, the system applies the holographic theme to
each activity, and thus, each activity includes the Action Bar.

However, if you want to use Action Bar APIs, such as to add tabs or
modify Action Bar styles, you need to set the android:minSdkVersion to
"11", so you can access the ActionBar class.


This seems to say that if we want to talk to the ActionBar directly,
i.e. use the Action Bar API, that we have to set our minSdkVerion="11"
in the manifest.

I'm having an argument with my boss, who thinks that since it "works"
on Honeycomb, that the above excerpt does not apply to us. But I point
out that when I comment out the code that tries to talk to the action
bar directly, then I don't get Verify Errors on pre-Honeycomb devices.
Everything used to work fine before we started trying to talk to the
Action Bar directly.

So, does that section, specifically the second paragraph that starts
with "However", which seems to modify the paragraph before it, really
apply? If so, why can we talk to the ActionBar on Honeycomb devices,
despite our minSdkVersion="8".

Our access to the action bar is wrapped in a wrapper class, as
described in the "backwards compatilibility" article.



3. Developers Phone Program

4. Starting an Android App from a Website

5. search contact selain first name dan last name

6. Frustrating but quite common taking SNAPSHOT problem

7. ada yg punya games