Dear experts - including Nikolay,
Last week Chander Pechetty mentioned bug 6478 in a different thread and
as it seemed to cause the same issues I experience now and then, I've
tried to capture the logs and today I succeeded.
The symptoms are that while playing Bebbled the phone somtimes slows
down drastically, in the end goes unresponsive and may even reboot. The
logs are at the time littered with "obtainBuffer timed out (is the CPU
pegged?)" messages from AudioTrack.
Maybe Bebbled is misbehaving in some way, but it would be much
preferable that the system could just kill it rather than reboot.
I've attached my log file to the existing bug in the hope that someone
with more insight can figure out the root cause and better way of
handling it.
Details here:
http://code.google.com/p/android/issues/detail?id=6478
Best / Jonas
Chander Pechetty wrote:
Interesting, I had filed an issue earlier with my G1 crashing
occasionally when playing bebbled; wonder if they are related ( to
cosmic rays :-)
http://code.google.com/p/android/issues/detail?id=6478
--
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
