Develop Reference

Create Android qcow2 from QEMU

I was wondering if it was possible to use QEMU to start the emulator created from the Android Virtual Device Manager in Android Studio? I know it can be started from the command line, but I'm trying to understand how it works underneath. I know the AVD creates a qcow2, but it also creates a lot of other .img files that I'm not sure how to combine into a command that can actually start it.
If I can't start it via QEMU, is it possible to create an Android qcow2 emulator image to run for device testing in the same way? I found a similar guide online (https://yzygitzh.github.io/android/2017/11/03/android-x86-qemu.html), but I haven't gotten it to work so far. I also don't know how it would perform in comparison, specifically for app testing. Would anyone have any insight on that?
Similar Research:
Android emulator is based on QEMU. Can I use KVM with it? (Kind of beats around the question, but doesn't exactly answer it)
Mount qcow2 image created by Android emulator (Discusses a bit about the Android Device Emulator files)
How to show which options are passed to QEMU when launching the android emulator? (Seems closer to partially answering the question)
https://stackoverflow.com/revisions/48310014/9 (Shows building the emulator wrapping around QEMU, but not using the emulator without the wrapper)

IntelliJ Idea - Android Virtual Device doesn't start

I'm using IntelliJ Idea 13 to develop Android applications on Ubuntu 12.04 64-bit. But my virtual device never starts despite there is no error.. its screen always stays like this:
My Android target level is 4.4 (API 19). How can I solve this issue?
Edit: Here is my AVD details:

I Recommend you look at this post to a similar question.
https://stackoverflow.com/a/5535532/2978914
they are using eclipse but you should be able to view the logcat, other posts say first load can be ridiculously long.
the spec of your PC may come into play as this post https://superuser.com/a/347298 explains the way the emulator converts to arm opcode: direct quote:
To use emulator more effectively, this is my experience:
Don't close emulator everytime you run your application.
Scale the emulator screen smaller.
Disable snapshot (Yes, it's useful but it takes time to close the emulator).
Specify a file path for SD card image file. I use only one SD card for many AVDs.
If you got any problems in adb, just reset adb, don't close emulator.
Open few programs in your operating sytem.
If you are using Windows, don't ever close emulator. Do it combined with Hibernate of Windows.

My AVD has started after I check "Use Host GPU" option from "Emulation Options".

Is there any way to run glassware in an emulator?

Today Google just released the GDK Sneak Peak for Google Glass. I have tried to run the samples they have hosted in GitHub with no success:
gdk-stopwatch-sample
gdk-compass-sample
gdk-timer-sample
I am targetting against Android 4.0.3 Glass Development Kit Sneaky Preview and trying to run it in an AVD that also targets it with the following other specs:
640x360 hdpi
For the CPU I tried both ARM & Intel Atom
When I run the app and the dialog to choose the device is shown I do see the virtual device as non compatible.
If I skip it and try to run it I see the following error output:
Installing com.google.android.glass.sample.compass
DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/com.google.android.glass.sample.compass"
pkg: /data/local/tmp/com.google.android.glass.sample.compass
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
I have tried to force not to require the glass library (setting the requirement to false) in the AndroidManifest.xml:
<uses-library
android:name="com.google.android.glass"
android:required="false" />
... but obviously doesn't run properly, it's being shown in kind of an overlay:
I have also tried using Genymotion, but it doesn't run either.
Is there any way to run successfully glassware in an emulator?
EDIT:
Adding the gdk.jar as a library doesn't work.

Only a small percentage of the sample code seems to be using the GDK libraries. For example, the Compass example has a CompassService that is in charge of attaching the CompassRenderer into the Glass Live Card. It also has a CompassMenuActivity, that basically has calls to standard Android menu rendering. Those could be called a "glue" that wrap the compass-functionality into the Glass experience. Major parts of the compass code are just standard Android libraries.
Assuming that the emulator currently does not have a way to run glass libraries (and no-one has hacked them into it yet), and if you want to run the Compass example without actual Glass hardware, you need to implement the Service & MenuActivity in your own "standard Android" way. Basically, create an activity that implements the CompassRenderer in a surfaceview.
Have a look at these commits for an example (tested on Galaxy S4, views are being rendered and menu items are functional):
https://github.com/blaind/gdk-stopwatch-sample/commit/26e9801af983b9fc931d6dfe5ce1fcb80766fd10
https://github.com/blaind/gdk-compass-sample/commit/0d89e922a167c0fac6890684c514b9028e7bfea8

Youwave for Android in remote desktop environment using thin client

I am using YouWave for Android in a remote desktop environment with Atrust Thin Client T60 series. When I run the YouWave emulator, a black screen appears and it stops there.
Also the home, menu and other buttons (except rotate button) does not work. When I tried to run an app it says
Android OS not ready.
When I open YouWave for a second time, it says
Another YouWave for Android is already running or previous run is cleaning up.
This repeats even if I tried to open waiting for few minutes. Is there any remedy for this?

A better alternative to YouWave or Bluestacks is GenyMotion
it is the fastest emulator ive ever used, everything works
to use it first visit the website, signup for an account then download the genymotion application. It works with Windows, Mac, Linux/Debian Linux.
After installing it, login using the signed up data & you will get a list of devices.
These are images of various physically available Android devices like nexus 7, nexus s etc. Download the desired device image.
These images are rooted & some with gapps, you can link the emulator to the android sdk for directly testing your app in the emulator. This emulator is so awesome that you can change the resolution of the device. you can add a shared folder using virtualbox, the shared folder is located # mnt/shared/

Try this and start again the YouWave
Go to Start > Run (or press Windows + R)
Copy and paste the bold text to the dialog box: %USERPROFILE%\.Virtualbox\HardDisks
Delete or rename youwave_vm01.vdi
Copy and rename youwave_vm01_golden.vdi to youwave_vm01.vdi
NOTE: youwave_vm01_golden.vdi is a clean Android instalation, keep a copy at all times.

I recommend you to use BlueStacks.
I am using it, and it's working all right, i was also having issues with YouWave.

MonoDroid - Target Device does not display in IDE

I'm trying to run the very simplest app on MonoDroid though the MonoDevelop IDE - i.e. the one that is created as part of the new project (the one that increments the lable on button clicks - i won't post code as I don't think it is relevant unless someone really wants it).
When I press the run menu item then run (or debug) i get the emulator selection
I dutifully start the emulator - (I've tried API_7, API_10, API_12) and that works OK. But the IDE above never refreshes to show the currently running emulator so I can't launch the application. I have manually refreshed but the same list comes up. What I am expecting is the new emulator to appear in the list and the OK button becoming active.
I have tried running adb devices in the command line and I can see that the debug bridge has picked up the device i.e. it says emulator-5554 which matches the TCP/IP port that the emulator is running on.
I've also tried restarting the debug server i.e.
adb kill-server
adb restart-server
But I can't see the emulator appear on the above dialog. The debug server is running on port 5037. Could the IDE be listening to a different port?
Fundamentally I'm trying to get the simplest app running through MonoDevelop. And I'm failing. Please help good people.

I had the same problem initially when I tried running the emulators. My recommendations from my own experience would be to:
Run the Android SDK manager and retrieve all the latest SDK packages.
Create your own Android Virtual Device via the AVD Manager rather than running those that are listed when the IDE is intially run. You should then start the AVD manually via the AVD manager and ensure it is fully loaded before starting the de-bug.