ist it possible to run AVD on VirtualBox?
I have Ubuntu 14 installed on it.
I have downloaded new Android Studio but with a bit obsolete tools 25.2.5 what allows to use "android" command.
I have created such AVD:
Available Android Virtual Devices:
Name: AVD1
Device: Nexus 6 (Google)
Target: Android 4.0.3 (API level 15)
Tag/ABI: default/armeabi-v7a
Skin: 1440x2560
When I launch it i can see only black screen and nothing happens.
I heard that it's not possible to run AVD on emulated operation system, but don't know if it's true. Is there any solution to overcome this problem?
And if not, what you would reccoment then? Should I find some online emulator, test on phycial device or maybe install AVD on my host system (Windows), and test on Windows. But i don't know if I can take file generated on Ubuntu and test on Windows??
Thank you in advance!
Related
I am trying to debug an app (with min. API 10) that runs fine on a real device running Nougat (API 24) but the app crashes during specific tasks on a real device running KitKat (API 19).
I use Android Studio.
I want to emulate a device running API 19 to understand what is making the app crash, using the bugger in Android Studio.
I created several new virtual devices in the Android Virtual Device Manager and selected the KitKat system image (API19) (Android 4.4.4) (google APIs), but when I launch the emulator for these devices, the emulator crashes after showing the Android logo. And I cannot reach the home screen.
I have no problem running API25 on emulated Nexus 5 or 6.
Where should I start looking to fix my issue ?
Thanks
Ensure you are using the latest x86 Google APIs system images from the SDK Manager as well as the latest Android Emulator. As of writing this, it should be revision 29 for the API 19 system image (see screen shot):
Revision 29, should work:
To further troubleshoot, you can run the emulator from the command line to see any error output. To to this, run the following commands from your Android SDK location, as indicated in the Android Studio SDK Manager window.
$ ./tools/bin/avdmanager list avd (this will list all AVDs on your machine, identify the API 19 AVD that you want to run and note the "Name:" field.
$ ./emulator/emulator -avd Nexus_5_API_19 (with Nexus_5_API_19 being the name of your AVD on your machine.)
Note any error messages. If you find an error with the emulator, you can file a bug here: https://developer.android.com/studio/report-bugs.html
I can successfully launch AVDs for the targets Android 5.1 (Google APIs) and Android 6.0 (Google APIs), both using CPU=x86. However the AVD I create for Android 4.1 (Google APIs) using CPU=arm cannot be launched. When I try to launch it I see a dialog:
Cannot launch AVD in emulator.
Output:
emulator: ERROR: This AVD's configuration is missing a kernel file!!
emulator: ERROR: ANDROID_SDK_ROOT is undefined
Since two AVDs do work I'm sure ANDROID_SDK_ROOT is defined. I've also verified that File -> Project Structure -> SDK Location is correct.
I have also run the Android SDK Manager, uninstalled all API 16 items and reinstalled these API 16 items:
SDK Platform
Intel x86 Atom System Images
ARM EABI v7a System Image
Google APIs
Sources for Android SDK
Within the Android SDK Manager all other libraries and packages are up to date. And I have restarted my Windows 7 computer.
Also note that I am forced to create this API 16 AVD for CPU=arm rather than using CPU=x86 as the Android Virtual Device Manager, when showing available system images, does not show an x86 image for target=Android 4.1 with Google APIs).
Does anyone know what the problem is? Or suggest things I can try to debug this issue?
Edit from a day after opening this question: Since I've seen no answer I'm assuming this is another Android Studio bug. I've input this bug report - https://code.google.com/p/android/issues/detail?id=207494
I got same error while trying to run ARM based emulator which is of API 16. I got this error when ARM images are downloaded from the android-studio itself( Not using Standalone SDK Manager option under System Settings->Android SDK in android-studio).
I solved this by launching Standalone SDK Manager from android studio. Then open Tools->Manage AVDs from Standalone SDK Manager menu. Here you can find your emulators. I observed that my ARM CPU emulator shows question marks in the columns named Platform,API label,CPU/ABI. Which seems to be some sort bug. Select the Emulator and click on edit. Choose the Target API,CPU/ABI properly and then click ok.
Now my emulator works perfectly. This solved my problem.
I figured out that updating android-studio caused this problem for me.
I seem to have messed up AVD Emulator and need some expert help in solving the problem.
Here are the symptoms:
When I try to open my_avd (my default avd) from AVD Manager, it takes a very long time to load (approx 10 - 20 mins). When loading completes, it just hangs and does not respond to any clicks (unlock mode!).
I try loading my app on this emulator, it is abandoned with:
"emulator-5554 disconnected! Cancelling 'com.app.xyz.xyzactivity activity launch'!"
When trying to launch 'my_avd' from terminal ('...android-sdk-linux/tools $ ./emulator -avd my_avd'), the load time is less, but it abandons with a "Segmentation fault" error in terminal.
I have tried deleting & re-creating my_avd multiple times, but no go.
Have tried increasing the 'Device ram size' to 1024 also, but even that did not help.
Tried the 'Snapshot: Enabled' mode while creating my_avd, but that only worsens the problem.
Have reinstalled eclipse, android sdk, etc.
I am using Eclipse, Android 4.0 (API 14) on Ubuntu 11.x (x64 processor with ia32-libs installed).
Any help/ suggestions will be highly appreciated.
Thanks in advance
Ram
Try another API version. I have this problem with API 14 and 15, but works fine with all the others. If you can't get it to work with, for example, the API 8 or 10 then you got a problem with your AVD emulator. I would suggest you to let the Eclipse choose the device for you (based on the your target version and the devices registered on your AVD Manager). Check the configurations of the device and make sure that they are the same of the real device you're emulating. Here goes the Motorola_spice_key (android 2.3.3) config:
Name : Motorola_spice_key
Device : 2.7'' QVGA(240x320:ldpi)
CPU/ABI : ARM(armeabi)
Target : Android 2.3.3 (Api level 10)
skin : 240x320
snapshot: true
Memory - RAM/VMHeap : 512 / 16
Internal Storage: 200MiB
SD Card : 512Mib
Try this one. If fails, then you might have to reinstall the emulator.
When I start my AVD emulator, the emulator just shows blank screen with 'android' written at the center. I waited for half an hour but nothing changed.
I am using Android SDK 2.1 and Eclipse 3.5
I see that quite a lot. In my case, I can clear it by shutting the emulator window, doing 'adb kill-server' followed by 'adb start-server', then restarting the emulator. I have also had more success launching the emulator first before letting the debugger launch it when I start debugging.
I was faced with a blank black screen after the emulator was started by Titanium and none of the emulator buttons such as Menu or Home did anything.
To fix it I entered the following commands from the sdk / tools directory:
android list avd
This listed the emulator images. In my case it listed two:
Available Android Virtual Devices:
Name: titanium_3_WVGA854
Path: C:\Users\xxx\.android\avd\titanium_3_WVGA854.avd
Target: Android 1.6 (API level 4)
Skin: WVGA854
Sdcard: C:\Users\xxx\.titanium\android.sdcard
---------
Name: titanium_8_WVGA854
Path: C:\Users\xxx\.android\avd\titanium_8_WVGA854.avd
Target: Google APIs (Google Inc.)
Based on Android 2.2 (API level 8)
Skin: WVGA854
Sdcard: C:\Users\xxx\.titanium\android.sdcard
In my case I wanted the Android 2.2 API so I entered
emulator #titanium_8_wvga854
WARN/WindowManager(61): No focus window, dropping: KeyEvent{action=0 code=82 repeat=0 meta=0 scancode=229 mFlags=8}
That seams a problem of 1.6
Upgrade to 2.1 and shall disappear.
I was faced with a blank black screen after the emulator was started by Titanium and none of the emulator buttons such as Menu or Home did anything.
To fix it I entered the following commands from the sdk / tools directory:
android list avd
This listed the emulator images. In my case it listed two:
Available Android Virtual Devices:
Name: titanium_3_WVGA854
Path: C:\Users\xxx\.android\avd\titanium_3_WVGA854.avd
Target: Android 1.6 (API level 4)
Skin: WVGA854
Sdcard: C:\Users\xxx\.titanium\android.sdcard
---------
Name: titanium_8_WVGA854
Path: C:\Users\xxx\.android\avd\titanium_8_WVGA854.avd
Target: Google APIs (Google Inc.)
Based on Android 2.2 (API level 8)
Skin: WVGA854
Sdcard: C:\Users\xxx\.titanium\android.sdcard
In my case I wanted the Android 2.2 API so I entered
emulator #titanium_8_wvga854
its only a problem of computer memory, sometimes when we build again and again by eclipse or other IDE, it consumes memory (don't know why maybe because of leaks) and it memory is user 90% , so that sometimes it creates problem for emulator launching and takes a lot of time to get launched.
windows xp
Running Android emulator version 10.0 (build_id OPENMASTER-104271)
Kill the emulator which cause a dumprep.exe which I killed too.
You just need to resave the AVD configuration. Perhaps something got corrupted
In eclipse > Android SDK and AVD Manager, select your AVD Name and click Edit ...
Click Edit AVD ( resaves your settings )
select your AVD Name and Click Start...
Disabling Host GPU in the settings for the AVD worked for me. This was a problem for me with 2.3, but not 5.0.