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.
Related
HAXM Enabled version 7.1.0 and i verified that it's working when the emulator is running
The emulator is using the Nvidia GPU however it's barely using maximum 7% of the GPU at any given time
I have 27.3.1 of Emulator version ( Latest )
Tried x86 image and x86_x64 image
I tried hardware acceleration
I tried software acceleration
I bumped the emulator ram to 4GB (I have 20 GB)
I set the emulator CPU priority to real time
I have NOTHING but Android Studio, and emulator running
The emulator is running horribly slow and laggy and even gives a black screen when going from activity to another
This has been the case since forever
I tried deleting the entire Android SDK and installing from scratch
I have intel virtual technology enabled in BIOS
I tried Google Apis vs none Google Apis emulators
I tried Nexus 5, X, Pixel 1, 2, XL with android P, O, 16 and all laggy
This is what helped me with my Android 9 emulator:
Use Google Play x86 image instead of Google API x86 image, because the former had a notification "Preparing for setup.." which never finished.
After launching the emulator first time, going through the initial google device setting (skipping what can be skipped..) and setting up the SD card (as an external storage).
If there are some app updates running, wait for it and then force quit 'Google play services' app. If the emulator will be slow again after reboot, you might want to do this after every launch.
Disable mobile data in settings, because it was trying to connect again and again, using up all CPU. And CPU helps with rendering, so if there is no available CPU, it gets slow.
Edit:
5. Go to emulator Settings/Advanced and set OpenGL ES rendered to Desktop native OpenGL and OpenGl ES API level to Renderer maximum and reboot the emulator. In my case, using autoselect/autodetect had far worse performance.
-- this is a follow up for my comment above (it's too long to be written as a comment) --
then we established that the problem is coming from your compute (or your OS) - If you're using a Laptop make sure to check the settings of the laptop performance when plugged and when you're using a batterie. In case you have a desktop check also the settings if there is some sort of limitation set by the OS. That can happen to avoid overhitting and loud fan noises. If any of the above doesn't work and you still really wanna figure this problem out and I'll assume you're using Windows 10, then install Ubuntu or any other Linux distribution as a second OS just to try things out. If The problem is solved then you definitely need to change some settings in your windows.
For anyone looking for an answer. I simply updated windows 10 to a newer version and update my graphics card drivers and the emulator is insanely fast again.
I had the same issue on my laptop and also on my high-end PC. I tried everything I could find on the internet:
updating HAXM to the latest version (in SDK Manager)
disabling Hyper-V on Windows
disabling audio in emulator
disabling multi-core feature
changing the renderer
disabling snapshots [1]
Now, I cannot be 100 % sure that anything from above could not somehow contribute to fixing the issue (even that I changed most of it back), but the issue disappeared immediately after I did this:
Go to SDK Manager -> Install the latest SDK Platform
There is said in Android Developers User Guide [1] that these are the requirements for Graphics Acceleration:
SDK Tools: Latest release recommended (version 17 minimum)
SDK Platform: Latest release recommended (Android 4.0.3, Revision 3, minimum)
Even that I did have SDK Platform version 27, for some reason I believe that HW acceleration was not working, cause even moving the emulator windows was laggy (or even its settings). As I said before, latest SDK Platform version seems to be the thing that fixed it.
Also, do not forget to kill all emulator processes and also Android Studio. But maybe restart the whole computer just to be sure (I was doing it a lot, cause I was also checking a bios virtualization settings few times).
If it won't work for you, try turn off the snapshots as that was the last before I tried this. You will have to wipe the data from that image, or even better - create a new AVD and download the latest image from "Recommended" tab.
Hope this will be helpful to someone as I did spend several frustrating hours fixing it (after few months of living with it).
Disabling mobile data is one way that works if you're not connected already to data (regardless of wifi connection), another debugging tool that could help you is the FPS Meter in the Debugging Options in Android, relevant github guide
If your emulator is SUDDENLY slow, this might be the reason:
I ran through the same issue.
I then realized that it was a picture quality issue.
So if you're using a lot of pictures in your app, it will run slow unless you 'lower the picture quality'.
You can use http://compressimage.toolur.com/ to reduce your image quality.
Whenever I open the AVD Manager and launch any one of the virtual devices I created, the emulator starts and closes immediately. When I run the virtual device in AVD Manager for the first time I get an error message that QEMU has stopped working.
I have given the right path to the JDK. More over, I have tried to install Android Studio again and again, but still its not working. I am using Windows 7(32 bit, 2GB RAM, without graphic card).
Is there need of graphic card to run emulator? If not, what should I do the run the emulator?
In AVD manager open settings for your virtual device.
In the Emulated Performance section open the dropdown for Graphics.
Change it from Automatic to Software.
Hit the Finish button to save new setting and try starting the emulator again.
I finally found the solution here: https://www.bram.us/2017/05/12/fix-for-the-android-emulator-crashing-during-launch/
It seems to be an incompatibility with other software, such as Docker, Oracle Virtual Box and other products that use VCPU. In my case, it seems that VBox and/or DraftSight caused the issue. I don't get the error when I terminate those applications first.
After trying Vahid's answer, it stopped crashing. Unfortunately it was lagging badly. After installing the NVIDIA drivers for my card (I have a 1060), I was able to change the setting to Hardware again, and now it is much smoother.
In most cases the solution provided above by #Vahid would work but if for some reason you still want to use hardware for graphics. You can try upgrading graphics drivers and make sure to set your graphic profile aka GPU workload to Graphics instead of compute. This settings can be found in Nvidia control panel or AMD Radeon software settings, not sure if this would work for integrated graphics.
I am creating a camera application that detects claps, however the sound detection does not work in genymotion but only works in the regular emulator. I am not sure why.
There is a bug in the windows version of Genymotion that prevent the input sound from working.
It works well on Linux and Mac but not on Windows.
There is no way to work around it at this time.
I've setup an Android-x86 image (4.0-RC1-eeepc) in VirtualBox on a Dell Latitude D820. This particular ISO is not for the laptop, but of all available ISOs it works the best.
I have worked through some of the troubles I have come across (by not having an ISO for my device), but I haven't been able to get the sound working. The Android-x86 VirtualBox tutorial and other online resources directed me to use the ALSA driver with SoundBlaster 16, but this has not worked.
This question got me to look at some of the ALSA commands to see what I could find, but I'm not getting anywhere with it.
With the ALSA driver and SoundBlaster controller I get the following from alsa_ctl init
Unknown hardware: "Dummy" "Dummy Mixer"
Hardware is initialized using a guess method
This looked very wrong to me so switched to the Intel HD Audio as the other question did.
With the ALSA driver and Intel HD Audio controller I get the following from alsa_ctl init
Unknown hardware: "HDA-Intel" "SigmaTel ID 7680" ...
Hardware is initialized using a guess method
While this looks a little more promising, I still have no audio.
Since Android is basically Linux, I thought I would be able to translate a Linux solution. Several webpages have content similar to this one saying to modify /etc/modprobe.d/alsa-base.conf and add options snd-hda-intel model=CORRECT_MODEL and this appears to help a lot of Linux users. However, this doesn't seem applicable to Android. At least not to me, since I don't have alsa-base.conf
I know so very little about audio and ALSA. Is there anyting jumping out from what I have above? Even a nudge in a general direction would be great.
Some questions that I have:
What does it mean when I get the Unknown hardware: "Dummy" info? No audio device?
Lastly, I have verified that my sound works outside of virtual box. My first throught is that since my laptop can run Linux with sound, I should be able to include the Linux drivers in Android. Does that make any sense? Unfortunately, I also don't really know how to go about doing that either.
Thank you
I had the same issues.
I was using VMWare for WhatsApp. And had various Android versions without audio...
Setup VMWare with HDAudio config file mod.
alsa_ctl init
Always showed no devices.
I installed this App from Google Play "AlsaMixer (ROOT)"
And this versions got audio instantly:
android-x86-4.3-20130725.iso
android-x86-4.4-RC1.iso
Had a similar no audio problem in vbox. In your init.sh add this line to the end of the alsa_amixer stuff:
alsa_amixer set PCM 100 unmute
After I aded that my audio worked fine.
I had the same issue.
I kept looking for init.sh and then realized I had to install the darn thing to disk before that was worth fiddling with (it's re-parsed on reboot and the live disc doesn't save).
So I snagged the latest x86 ports and flipped through them till I found a 4.2x without issues. Sadly I lost track of which is which, and the good one is simply vm.iso?!
Long story short, audio is working fine with this build, I didn't even need to tweak anything.
System:
Motherboard Tab:
4GB RAM (Half the Host RAM)
[x] Hard Disk (Only boot device)
everything else is default
Processor Tab:
2 cores
everything else is default
Audio:
Windows DirectSound
ICH AC97
everything else is default
Working on phoenix os and androidx86 for sound fix
1) Install AlsaMixer apk
2) Open AlsaMixer
3) Search Master Playback Volume and edit value to 90
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.