[android-developers] Re: Epilog: Largish HTTP Post vs. ANR

2008-12-07 Thread David Turner
but these days, we recommend the much shorter alias: http://b.android.com :-) On Sun, Dec 7, 2008 at 3:00 PM, Mark Murphy <[EMAIL PROTECTED]> wrote: > > [EMAIL PROTECTED] wrote: > > Dumb question... where's the appropriate place to send the bug reports? > > http://code.google.com/p/android/issue

[android-developers] Re: Epilog: Largish HTTP Post vs. ANR

2008-12-07 Thread Mark Murphy
[EMAIL PROTECTED] wrote: > Dumb question... where's the appropriate place to send the bug reports? http://code.google.com/p/android/issues/list -- Mark Murphy (a Commons Guy) http://commonsware.com _The Busy Coder's Guide to Android Development_ Version 1.9 Available! --~--~-~--~~-

[android-developers] Re: Epilog: Largish HTTP Post vs. ANR

2008-12-07 Thread enervatron
Dumb question... where's the appropriate place to send the bug reports? Mike On Fri, Dec 5, 2008 at 5:27 PM, Andrew Stadler <[EMAIL PROTECTED]> wrote: > > On Fri, Dec 5, 2008 at 8:40 AM, <[EMAIL PROTECTED]> wrote: > >> So I finally figured out what was going on. It had nothing to do with >> HTT

[android-developers] Re: Epilog: Largish HTTP Post vs. ANR

2008-12-05 Thread Andrew Stadler
On Fri, Dec 5, 2008 at 8:40 AM, <[EMAIL PROTECTED]> wrote: > So I finally figured out what was going on. It had nothing to do with > HTTP posts, > thankfully. What it did have to do with was Formatter (or String.format). An > innocuous foreground loop using Formatter was taking 10 seconds for ab

[android-developers] Re: Epilog: Largish HTTP Post vs. ANR

2008-12-05 Thread Michael
You will not be able to access /data on the G1 with the shell. It's a "security feature". --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-develo

[android-developers] Re: Epilog: Largish HTTP Post vs. ANR

2008-12-05 Thread enervatron
On Thu, Dec 4, 2008 at 6:26 PM, Dianne Hackborn <[EMAIL PROTECTED]> wrote: > You can look in I believe /data/anr/traces.txt to find a dump of the stacks > of all processes and threads when the ANR happened, which should tell you > what your thread was stuck doing at the time. Ah, nice. You should