There I go again with my assumptions. I was basically assuming the next SDK was 1.1r1 based on the following thread http://groups.google.com/group/android-developers/browse_thread/thread/3d83bee2892b6f78/ca6fc62d3bc57537?show_docid=ca6fc62d3bc57537# where Dave mentioned it would be addressed. Anyhow thanks for the response and perhaps Dave can provide some insight or an update.
~clark On Feb 24, 9:20 pm, Romain Guy <[email protected]> wrote: > I don't know if it's safe to make such an assumption. I'm just saying > that you cannot make an assumption about which SDK was the "next SDK" > :)) And I know next to nothing about SoundPool so i can't tell you > more unfortunately. > > > > On Tue, Feb 24, 2009 at 9:18 PM, clark <[email protected]> wrote: > > > Thanks for the quick reply Romain Guy. So is it safe to assume that > > SoundPool was not updated in the 1.1r1/RC33 update? I don't mean to > > be pedantic about it but I just want to make sure I'm reading into > > your reply correctly. > > > Thanks again, > > ~clark > > > On Feb 24, 9:14 pm, Romain Guy <[email protected]> wrote: > >> The "next SDK" might actually be cupcake. Not all fixes went into SDK > >> 1.1r1/rc33 since the release of 1.0. SDK 1.1 is actually a rather > >> limited update with very specific fixes. > > >> On Tue, Feb 24, 2009 at 9:11 PM, clark <[email protected]> wrote: > > >> > I've recently started working with the SoundPool class in SDK 1.1R1, > >> > and noticed that my app deadlocks from time to time, or sounds are not > >> > loaded. I remember reading, back in November, that this was to be > >> > addressed in the next SDK. > > >> > I've used pretty much the same code that others have used and most of > >> > the time it works for a bit. Just a minute ago, the app completely > >> > crashed with no "Force Close" and returned to the home screen. > >> > Logcat reveals that "HeapWorker is wedged: 26577ms spent inside > >> > Landroid/media/SoundPool;.finalize()V" > > >> > I'm not sure if this is the same issue others had with SoundPool or if > >> > I have encountered an entirely new beast. > > >> > Regards, > >> > ~clark > > >> -- > >> Romain Guy > >> Android framework engineer > >> [email protected] > > >> Note: please don't send private questions to me, as I don't have time > >> to provide private support. All such questions should be posted on > >> public forums, where I and others can see and answer them > > -- > Romain Guy > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time > to provide private support. All such questions should be posted on > public forums, where I and others can see and answer them --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
