avd

Android emulator fails to start when used with tcpdump-option on Windows10

*爱你&永不变心* 提交于 2020-01-04 04:01:49
问题 I can run an avd using cmd on Windows 10 with the command: emulator -avd avdmy but when I want to use tcpdump to capture the network-traffic, the emulator fails to start: emulator -avd avdmy -tcpdump ~/test.cap qemu-system-i386.exe: -tcpdump: invalid option I have no problems running the emulator itself. Might this be a Bug or am I missing something? The problem occurrs for every AVD I've tried. I've checked emulator -help and I am sure -tcpdump is an option. My question is do I need tcpdump

AVD Manager on Android Studio 1.5.1 and install to a custom location emulator won't run

倖福魔咒の 提交于 2020-01-03 10:46:11
问题 I installed Android Studio (1.5.1 -- see image for build details). While installing I chose the custom option so I could install a specific path. I knew that my %SystemDrive% was pointed at a network location and I wanted to install to my local disk. So, this means that by default, the application would've installed to : \networkpath\users\myUserName\Android\SDK However, since I chose the custom installation I chose a local path: c:\users\myUsername\Android\SDK Project Creation and Build Work

AVD Manager on Android Studio 1.5.1 and install to a custom location emulator won't run

混江龙づ霸主 提交于 2020-01-03 10:46:09
问题 I installed Android Studio (1.5.1 -- see image for build details). While installing I chose the custom option so I could install a specific path. I knew that my %SystemDrive% was pointed at a network location and I wanted to install to my local disk. So, this means that by default, the application would've installed to : \networkpath\users\myUserName\Android\SDK However, since I chose the custom installation I chose a local path: c:\users\myUsername\Android\SDK Project Creation and Build Work

Android 2.3.3 emulator with x86 image won't run with “Use host GPU”

扶醉桌前 提交于 2020-01-03 08:56:40
问题 I noticed that if I check the "Use host GPU" checkbox when creating a new virtual device with Android 2.3.3 and Intel x86 system image, the emulator just won't run, it shows black screen with no signs of life, aside from errors in logcat. According to some information that I found online, running on host GPU was never intended to work for 2.3.3 images, only 4.0.3+. But then I found this answer where the author claims to successfully run it after installing ironhide . But ironhide, which I've

Orange triangle in the target column of Android Device Chooser window

﹥>﹥吖頭↗ 提交于 2020-01-02 19:15:22
问题 When I launch my Android app with Eclipse, the usual window "Android Device Chooser" appears. I can here choose on which device I want to run my app. In the target column appears next to my target an orange triangle with an exclamation mark (kind of 'warning') When I search on the internet about this problem I've found this. What does the orange triangle in the target column of Android Device Chooser window mean? But the problem is the solution given in this thread doesn't work for me.I'm

Orange triangle in the target column of Android Device Chooser window

我与影子孤独终老i 提交于 2020-01-02 19:15:10
问题 When I launch my Android app with Eclipse, the usual window "Android Device Chooser" appears. I can here choose on which device I want to run my app. In the target column appears next to my target an orange triangle with an exclamation mark (kind of 'warning') When I search on the internet about this problem I've found this. What does the orange triangle in the target column of Android Device Chooser window mean? But the problem is the solution given in this thread doesn't work for me.I'm

android x86 emulator not respecting vm.heapSize

不羁岁月 提交于 2020-01-02 08:54:07
问题 The Android x86 ( API-10 ) emulator does not seem to respect the VM size specified through the AVD manager. See below for config.ini created from AVD manager hw.lcd.density=240 sdcard.size=64M skin.name=WVGA800 skin.path=add-ons/addon-intel_atom_x86_system_image-intel_corporation-10/skins/WVGA800 hw.cpu.arch=x86 abi.type=x86 hw.keyboard=yes vm.heapSize=96 hw.ramSize=256 image.sysdir.1=add-ons/addon-intel_atom_x86_system_image-intel_corporation-10/images/x86/ When I start up the app I print

Can't run older Android targets in AVD

ε祈祈猫儿з 提交于 2020-01-01 18:52:30
问题 I'm trying to test an app in an AVD with Android 3.1 as the target but it is running terribly slow and doesn't seem to respond. I created a new AVD with Android 2.1 as the target but this AVD does not show up in the run configurations in Eclipse even when refreshed and restarted. Does anyone know why I cannot run older versions of Android? 回答1: I've found that the targetSdkVersion in the manifest file affects what shows up in the run configuration. Setting the target selection mode to Manual

Can't run older Android targets in AVD

五迷三道 提交于 2020-01-01 18:52:14
问题 I'm trying to test an app in an AVD with Android 3.1 as the target but it is running terribly slow and doesn't seem to respond. I created a new AVD with Android 2.1 as the target but this AVD does not show up in the run configurations in Eclipse even when refreshed and restarted. Does anyone know why I cannot run older versions of Android? 回答1: I've found that the targetSdkVersion in the manifest file affects what shows up in the run configuration. Setting the target selection mode to Manual

Android Studio - Panic: Could not open AVD

我怕爱的太早我们不能终老 提交于 2020-01-01 04:33:06
问题 After many hours of fixing Gradle issues, I was able to build my test app in Android Studio. But when I tried to run it in an AVD, it just won't open. This is the log: Waiting for device. C:\Users\Rahaman\AppData\Local\Android\android-studio\sdk\tools\emulator.exe -avd testAVD -netspeed full -netdelay none PANIC: Could not open: testAVD P.S.: I've defined the environment variable ANDROID_SDK_HOME to point to the .android directory. 回答1: Okay, my libraries are in D: drive. So I had to copy the