> Can I ask you to file a bug at b.android.com with the text you just wrote > here?
I was about to, but it seems that the behavior is a bit erratic. For "final" checking before filing a bug I just made yet another AVD with the snapshot feature checked, and this time it did give sound. So I'm not sure anymore what the pattern is, while it is too time-consuming to do any statistics on creating AVDs under Android 3.0, so I'd rather wait now if other group members experience similar issues before filing a bug report. Thanks On Feb 23, 4:28 pm, David Turner <[email protected]> wrote: > Thanks a lot for this information. Can I ask you to file a bug at > b.android.com with the text you just wrote here? > It will help us track the issue for a future fix. > > Thanks > > On Wed, Feb 23, 2011 at 11:00 AM, blindfold <[email protected]>wrote: > > > Problem solved! The trick for me was to delete the huge (in my case > > close to 1 GB) cache file "snapshots.img" that the new emulator had > > created in my AVD folder for the Android 3.0 emulator - because I had > > selected the corresponding "snapshot" checkbox while defining a new > > AVD. Unlike a system reboot, this forced a clean restart of the > > emulator (taking much longer, obviously), and next I had sound. I now > > made a new Android 3.0 AVD with the "snapshot" checkbox not selected, > > and things are fine now. > > > I suspected that the new emulator with the snapshot option turned on > > also cached whatever PC audio device it had found and selected upon a > > first run, such that if it goes wrong there one is stuck without > > audio. However, creating yet another AVD with the snapshot option > > turned on for some reason again gave me the same no-sound problem that > > I had before, so it looks like using the snapshot option consistently > > causes problems with the audio device. I did not further investigate > > though. > > > On Feb 23, 10:07 am, blindfold <[email protected]> wrote: > > > I should add that I do get sound also with the Android 3.0 *preview* > > > emulator, but just not with the new final Android 3.0 emulator. I > > > rebooted my system because the new emulator appears to be doing some > > > heavy caching judging from the quick startup after a first run, but to > > > no avail. What can one do? Is it a new bug? > > > > On Feb 23, 9:26 am, blindfold <[email protected]> wrote: > > > > > I'm not getting any sound with the Android 3.0 (Honeycomb, final) SDK > > > > emulator. I have no such problem with the Android 2.2 and 2.3.1 > > > > emulators. This is on Windows 7 64-bit. I have all volume sliders up. > > > > Anyone else having this problem? > > > > > Thanks > > > -- > > You received this message because you are subscribed to the Google > > Groups "Android Developers" group. > > To post to this group, send email to [email protected] > > To unsubscribe from this group, send email to > > [email protected] > > For more options, visit this group at > >http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
