While I know you guys aren't interested in resolving problems with rooted devices, how about a bunch of users who are running official builds on non-rooted devices? (Specifically the LG Ally on the Verizon network)
How should they escalate the problem given their carrier is probably not at all interested? On Jun 23, 10:42 am, Doug <dougforp...@gmail.com> wrote: > If anyone is still interested, I've been able to reproduce the > problem, but not a lot of logging I'm afraid. > > * If the device is connected via USB the problem doesn't seem to > occur. > * If both "Mobile Data" and "WiFi" are turned OFF, the problem doesn't > seem to occur. > * If either "Mobile Data" OR "WiFi" is enabled, the problem occurs (In > my case mobile-data is 'dead' as the phone isn't registered with a > mobile network) > > I've been able to capture logcat output on phone (using "logcat > / > sdcard/logcat.out" from the Android Terminal app) on three occasions, > but after a quick glance there doesn't seem to be much in common > (don't know if this is due to output-buffering/file-flushing) > > Doug > > On Jun 14, 4:15 pm, Doug <dougforp...@gmail.com> wrote: > > > > > Hence my original request for information on how to determine the > > cause of (what appears to be) a panic-caused reboot. > > If I can determine the problem then you'll definitely see a ticket. > > > In terms of unknown software - how would I go about getting access to > > official pre-release (i.e. Beta or RC) versions of Android for the > > purposes of dev/test? Is that even an option? > > > On Jun 14, 4:06 pm, Dianne Hackborn <hack...@android.com> wrote: > > > > On Mon, Jun 14, 2010 at 3:37 PM, Doug <dougforp...@gmail.com> wrote: > > > > Dianne - I completely agree that this is theoretically not an issue > > > > that I should be concerned with, however, as the developer of an app > > > > that seems to be triggering this bad behavior it is up to me to try to > > > > determine whether or not anything can be done about it. I can point > > > > my finger in any direction (Motorola, Verizon, even Google/AOSP) but > > > > as you know users don't know (or even care) where the problem lies, > > > > all they see is my app misbehaving and thats the end of it. I'd > > > > rather do a little research to help identify/resolve the problem now > > > > than have to deal with the user rants later. > > > > I care much more about the platform software being fixed than applications > > > working around such a bug. (Of course for some unknown piece of software > > > running on a device, I care less about it.) > > > > In other words, if your app is crashing the platform, I would like to > > > have a > > > bug filed with steps to reproduce so this issue in the platform can be > > > fixed. > > > > -- > > > Dianne Hackborn > > > Android framework engineer > > > hack...@android.com > > > > Note: please don't send private questions to me, as I don't have time to > > > provide private support, and so won't reply to such e-mails. All such > > > questions should be posted on public forums, where I and others can see > > > and > > > answer them. -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
