[android-developers] Re: Oops, I crashed the phone

2010-08-17 Thread String
On Aug 16, 11:07 pm, Mark Gjøl bitflips...@gmail.com wrote: My drawing loop is strictly single threaded (fed data by several other threads, obviously) I didn't mean that you had multiple drawing threads; I don't either, really. But like you, I do have several threads, that feed the drawing

[android-developers] Re: Oops, I crashed the phone

2010-08-16 Thread String
On Aug 15, 12:46 pm, Mark Gjøl bitflips...@gmail.com wrote: It's always a problem if you can crash the phone. As I'm working with OpenGL I'm guessing this is the problem, as I'm working directly with the hardware. When the phone crashes it hangs for a couple of minutes, Mark, It's not just

[android-developers] Re: Oops, I crashed the phone

2010-08-16 Thread Mark Gjøl
String, I could try and make sure I'm not drawing to the screen from several places at the same time, but I don't think this is the problem. My drawing loop is strictly single threaded (fed data by several other threads, obviously), so Android would have to be maintaining multiple GL message loops

[android-developers] Re: Oops, I crashed the phone

2010-08-15 Thread Mark Gjøl
This is what I get from adb logcat until the phone reboots: I/ActivityManager( 88): Start proc dk.nindroid.rss for activity dk.nindroid.rss/.ShowStreams: pid=6295 uid=10046 gids={3003, 1015} I/global ( 6295): Default buffer size used in BufferedOutputStream constructor. It would be better to