[TouchPad Development] EricBlade:
Did that log actually help?

Are you a wizard?

* edit: Oh, I figured out that probably when the sound crashes out.. that's when it freezes and reboots from the lock screen. Swipe up, it goes to make the "click" sound, and that locks up the app, and a few minutes later, it either reboots on it's own, or i'm forced to force the issue. I'll see if I can also grab a log the next time the sound goes out.. I'll probably have to grab it with adb though, unless the sound goes out while i'm doing something ..

** further edit: here's what I've got from the log

W/Binder (19517): Binder call failed.
W/Binder (19517): android.os.DeadObjectException
W/Binder (19517): at android.os.BinderProxy.transactNative(Native Method)
W/Binder (19517): at android.os.BinderProxy.transact(Binder.java:496)
W/Binder (19517): at android.content.IIntentReceiver$Stub$Proxy.performReceive(IIntentReceiver.java:124)
W/Binder (19517): at android.app.ActivityThread$ApplicationThread.scheduleRegisteredReceiver(ActivityThread.java:866)
W/Binder (19517): at android.app.ApplicationThreadNative.onTransact(ApplicationThreadNative.java:388)
W/Binder (19517): at android.os.Binder.execTransact(Binder.java:446)
I/art ( 416): Explicit concurrent mark sweep GC freed 2761(94KB) AllocSpace objects, 0(0B) LOS objects, 16% free, 20MB/24MB, paused 2.258ms total 114.807ms
I/art ( 416): Explicit concurrent mark sweep GC freed 2637(87KB) AllocSpace objects, 0(0B) LOS objects, 16% free, 20MB/24MB, paused 2.410ms total 142.456ms
I/art ( 416): Explicit concurrent mark sweep GC freed 2504(81KB) AllocSpace objects, 0(0B) LOS objects, 16% free, 20MB/24MB, paused 2.380ms total 113.067ms
I/art ( 416): Explicit concurrent mark sweep GC freed 2774(92KB) AllocSpace objects, 0(0B) LOS objects, 16% free, 20MB/24MB, paused 2.441ms total 116.607ms
I/art (19616): Explicit concurrent mark sweep GC freed 11665(471KB) AllocSpace objects, 0(0B) LOS objects, 25% free, 2MB/3MB, paused 366us total 27.587ms
I/art ( 416): Explicit concurrent mark sweep GC freed 2771(93KB) AllocSpace objects, 0(0B) LOS objects, 16% free, 20MB/24MB, paused 2.288ms total 116.088ms
I/art ( 416): Explicit concurrent mark sweep GC freed 2895(97KB) AllocSpace objects, 0(0B) LOS objects, 16% free, 20MB/24MB, paused 2.075ms total 135.437ms
I/art (19616): Explicit concurrent mark sweep GC freed 14491(608KB) AllocSpace objects, 0(0B) LOS objects, 24% free, 2MB/3MB, paused 366us total 26.336ms
I/art ( 416): Explicit concurrent mark sweep GC freed 2879(97KB) AllocSpace objects, 0(0B) LOS objects, 16% free, 20MB/24MB, paused 2.319ms total 115.234ms

It's just repeating this over and over and over until it eventually gives me the "app not responding" dialog, and then it reboots from the Evervolv screen. This happens whenever the sound goes down, and something tries to play sound (such as the lock screen)

Sadly, I don't know how to pull older things from the log, so I can't pull whatever happened before. And it's rebooted now, which I'm pretty sure resets it, doesn't it?

** last edit for now: Just installed the camera test build. Big thumbs up there. Camera working. Pictures seem to be somewhat better than I remember from this camera, so I'll take it! The preview in Google Camera is seriously not in the correct aspect ratio, but the pictures come out just fine for the hardware limitation. I tried Bluetooth on it, and this time it is able to detect my Windows PC. It can't make a connection to it, and it's not detecting my Mac, Linux, or other Android devices, though. I know you didn't say it was fixed until after you'd already posted on that topic, but figured I'd mention it.

*** ok, really last edit until i go to sleep or discover something else that looks like it might be important. The "Explicit concurrent mark sweep GC" lines just constantly spew when the sound goes dead. Perhaps something in sound is memory leaking, or even something completely unrelated is, and Android starts killing things off?

Here's a pastebin of the logcat from when i just woke it up, sound went dead (it played the *click* noise, then i tried volume up, and the device locked up from the UI side), as well as some free memory and memory usage numbers, just as a thought: http://pastebin.com/CW4VjBFB