No AVD Sound When Testing an Android App?
On creating an Android Virtual Device (AVD) audio playback is normally OK. However, if using an old saved AVD there may be no AVD sound. When this happens messages may be seen in LogCat, including one or more of the following. (It varies by the API level of the AVD.):
AudioTrack Error obtaining an audio buffer, giving up.
AudioTrack obtainBuffer timed out (is the CPU pegged?).
AudioFlinger could not create track, status: -12.
Be aware that the last error is also seen with other sound playback issues. These other issues are usually memory related: such as the audio file is to big; too much data in the file (e.g. sample rate to high or varies to much); or the limit (32) on the number of audio tracks attempting to be played has been reached.
Note: If you don’t see messages in LogCat the following solutions may still apply. But also check that the PC’s sound is not off! (Or turned down low). Even forgetting to unplug headphone may be why you have no AVD sound.
Solutions to Try When You Can’t Play AVD Sound
In earlier editions of the Android Software Development Kit (SDK) the AVDs may not have been created with audio playback enabled. Subsequent SDKs enabled audio when an AVD was created. If an AVD is started and there is no AVD sound try the following:
- Uncheck Launch from snapshot when starting the AVD.
- Edit the AVD config.ini file to set Audio playback support to yes.
- Delete the AVD and recreate it.
- Use a physical Android device.