there.
I'm using Genymotion for test.
I'm developing an android application.
This application can make a sound.
then
I tried to test my android application.
But,it would not make a sound.
My environment is Macbook.
and
Virtual box is 5.1.
and
VMDevice is Google Nexus 4 with API level 22.
this would not make any sound even if i could change the volume of sound on genymotion.
And my virtual device setting is here.
In genymotion FAQ page,
https://www.genymotion.com/help/desktop/faq/
What are the VirtualBox versions compatible with Genymotion?
5.1+ versions are not recommended as they lead to sound issues
To run virtual devices, you must install Oracle VM VirtualBox 5.0.28.
Genymotion might run with older versions but we cannot guarantee it.
so you should use version 5.0 or older to get sound working
It takes me a long time, finally got the answer.
Several versions of VirtualBox are known to cause issues in Genymotion.
For Genymotion to run properly, make sure you have the right version of VirtualBox installed:
Mac OS X: 5.0.26 (a sound issue prevents version 5.0.28 to run properly)
Windows: 5.0.28
Linux: 5.0.28
In any case, do not use versions 5.1.x, as they are known to cause sound issues and in some cases prevent Genymotion to start.
For me, setting the sound effects destination in the Sound setting did the trick. You have to open the emulator after setting the destination.
Huge thanks to https://stackoverflow.com/a/40007818
I also had no sound when using Windows 10 1709, VirtualBox 5.1.26 and Genymotion 2.11.0.
I noticed this line in VBox.log:
Audio: Skipping to create input stream "[LUN#0] ac97.mc", as the host
audio backend reached its maximum of concurrent audio input streams
What solved my no audio issue was to activate the "Stereomix" in the recording devices in Windows Sound settings. For an unknown reason this was deactivated.
I cannot get sound working in the emulator in Android Studio. It's not my code as it's a very simple example program to demonstrate the MediaPlayer that works fine on an actual device.
On the emulator in Android Studio there is absolutely no sound, not even system sounds. Is this an Android/Android Studio bug? Or could it be the configuration of my particular system? Windows 10 issue?
Anyone else having this problem? Any solution other than using a real device or Genymotion (which I've never used) ?? Thanks.
EDIT: The only way I can get the emulator in Android Studio to start with audio is to launch it from the terminal with both the "-no-snapshot" and "-no-snapshot-load" options. And this only works about 80% of the time. It has something to do with snapshots. There are a couple of old questions on this but no solutions.
it seems that the problem has something to do with the emulator api so changing the emulator api solved it for me and I guess it will do for you.
Try to open your Oracle VM Virtualbox. Go to Settings -> Audio -> Host Audio Driver and change it to PulseAudio.
Let me know if it helps.
In Android Studio, click the Volume Up button (doc).
I have a problem with my genymotion emulator on Mac OX Yosemite. I have tried several devices, but every time, the voice and sounds are very deep. I was wondering whether anyone who has used virtual box or genymotion knows how to fix this problem.
I'm trying install latest Vuforia SDK in my Stuff (Mac Os 1.6.8 + ADT-mac-bundle) and follow step by step Instruction. So far is well. In this condition, I use emulator with AVD and setting my emulator with built-in webcam for camera. When I try app in emulator always showing "unfortunately stopped". Any suggestion for this problem?
Note: I still wonder for this issue, if issue about hardware. It's mean I must buy gadget with Android OS. I use emulator because I don't have gadget with Android OS. Thx
Vuforia is using the device's GPU to render the texture. So you will need to get your hands on some hardware.
I have a celeron processor :/ and android emulator on eclipse uses 100% of cpu and hangs everything unless I kill it . I was just trying a hello android program from a book and don`t know much about android or even eclipse .I have the android-eclipseplugin installled .
Can someone help me with is ?thanks!
As others have said, the solution is disabling sound. Unfortunately, in recent Android Studio releases (I'm using 1.4) the option to disable sound has been removed from the GUI. To disable sound you can do it either by launching the emulator from the command line with the -noaudio flag, or by editing the AVD's config file and setting the following parameters:
hw.audioInput=no
hw.audioOutput=no
On Linux, I found that file at ~/.android/avd/myAVD.avd/config.ini
I've had the exact same problem and found a solution that works for me.
In the config of the AVD I've set an extra flag "Audio playback support" to "no".
I've also made sure the AVD has 1GB of RAM.
This worked for me.
For me, it was unchecking the Multi-Core CPU check box
Niels' answer worked well for me https://stackoverflow.com/a/7706018
in that the emulator stopped using 100% CPU (dropped down to 10-15%)
Furthermore it had another useful "side effect". I noticed that playing video in Totem or music in RhythmBox would block while the emulator was running. VLC would play video but refuse to play the accompanying soundtrack for the video.
As soon as the emulator was killed, music would start playing.
Niels' answer to set "Audio playback support" to "no" prevents this issue.
I am running Ubuntu 11.04 and Android emulator version 13.0 (build_id OPENMASTER-172639).
I had same issue on my macOS High Sierra and for me helps to create new AVD device and choose CPU/ABI = x86_64, not x86 in Android version dialog. Hope that helps.
The Android emulator is emulating an ARM CPU without hardware acceleration which can be pretty slow even on a core2duo for example.
You can try to reduce the screen resolution of the virtual device which should result in a small performance increase.
The emulator is notoriously slow to start; it can take 15 minutes or longer on an underpowered machine. You can speed start-up a bit by passing the -no-boot-anim to the emulator start-up command. Other emulator options are described here. Also, some AVDs start faster than others. Try creating an AVD with the lowest level SDK that is useful for you.
Once the emulator has started, you don't need to shut it down. When an app exits (or crashes, or whatever), you can just run it again.
One alternative that worths mentioning is Genymotion. It's an android emulator based on VirtualBox, with pre-created images. It supports some features the stock Android emulator isn't very good at, like Wifi 3G, Bluetooth, GPS (with a fancy Google Maps integration, so you don't have to find coordinates manually), multiple screens, etc.
It worth giving it a try at http://www.genymotion.com/
I had this issue running the emulator on Ubuntu 14.04. Disabling the audio does bring down the CPU usage, but in case you need audio to work, it can be fixed by adding a symlink:
sudo ln -s /usr/lib/x86_64-linux-gnu/libpulse.so.0 /usr/lib/x86_64-linux-gnu/libpulse.so
The reason for this is that the emulator tries to use pulseaudio as the backend, but will be unable to link to libpulse.so, which does not exist on Ubuntu (unless you installed the libpulse-dev package). Then it will fall back to ALSA, which constantly calls poll, causing 100% CPU usage.
A fix for the emulator is coming, but for now, adding the symlink solves the issue.
I strongly recommend not to use android emulator. Use VirtualBox + android x86 OS (you can download it here ), and you will get real perfomance increase.
Unfortunately, as far as i remember, it is not from google and it supports only Android 2.2. I really do not understand, why google is not going to make simulator as fast as iPhone simulator , or to make official x86 release for debugging. I do not need emulating ARM processor instructions and I think 99% developers do no need it too.