Hi, "debug messages" was to imply anything emitted by locat, System.out.. , System.err.. , printStackTrace from Exception etc
And yes it's the same whether through Eclipse or otherwise, I suggested it can be painful when debugging in Eclipse with some real (non Google sponsored) devices that emit an excessive amount of these messages to find your own messages within that mess, filtering and redirecting to file and grep and changing buffer sizes and other time wasting steps aside. Some of the carrier sourced devices fill the default Eclipse buffer in a minute or so, particularly when GPS is on, the Google devices Galaxy S, Galaxy Nexus, Nexus 7 don't. Regards On Wednesday, October 3, 2012 11:17:42 AM UTC+10, Lew wrote: > > > > On Tuesday, October 2, 2012 5:40:32 PM UTC-7, gjs wrote: >> >> Hi, >> >> >The world doesn't comprise Eclipse alone. >> >> Wow really [sic]! Thanks for letting us all know... >> >> A real device is useful for testing various hardware features - bluetooth >> [sic], nfc [sic], hd [sic] >> video recording, sensors - accelerometer, barometer, compass, gryo >> [sic], magnetic, wifi direct etc etc >> > > Indeed, yes, a real device is useful, and like an emulator, can be tested > via command-line or > Eclipse means. > > You didn't answer my assumption about what you meant by "debug messages", > but if you > meant logcat output, that's the same whether it's through Eclipse or not. > > Wow, really. > > So what is the deal about not "relying on debug messages through Eclipse"? > > If you didn't mean logcat output, would you please tell us what you were > referring to? > > -- > Lew > > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
