as the log hints, it is likely that your app pegs cpu for too long or your app causes GCs which may also peg cpu.
On Sep 1, 1:11 pm, sasq <jonas.minnb...@gmail.com> wrote: > Don't know why I bother asking here but, you never know, right? > > Anyway - after stopping and restarting playback of an audiotrack > stream, on some devices I consistently get; > > W/AudioTrack( 2453): obtainBuffer timed out (is the CPU pegged?) > 0x64acc0 user=00010000, server=00000000 > > after freezing for a couple of seconds. This happens whether I just > pause() and flush() my audiotrack or release() and recreate it. > > Anyway to avoid this? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
