On my instance of JB emulator it runs with new behavior. Make sure you've started correct emulator, as I noticed several times that ADT/SDK 20.0 could start something else (non-selected item) from the list.
On Sunday, July 15, 2012 9:54:18 AM UTC+3, Ran wrote: > > It seems that on the JB emulator everything works as before. > Is that by design? > > Thanks. > > > On Thursday, July 12, 2012 9:29:20 PM UTC+3, nnk wrote: >> >> >> There's no documented, approved way to read the log entries. >> >> Having said that, if you just exec() logcat, as you did before, you'll >> automatically get your own log entries. You don't need to do anything >> special. The log system knows which log entries belong to you, and >> which log entries belong to others, and will only give you your log >> entries. >> >> -- Nick >> >> On Jul 12, 10:24 am, Mark Murphy <[email protected]> wrote: >> > On Thu, Jul 12, 2012 at 12:59 PM, Dianne Hackborn <[email protected]> >> wrote: >> > > however every app can read the logs containing only the lines >> > > *they* have written, without needing any permission. >> > >> > OK, I'll bite: how do you do this? Most of the read-the-logs code that >> > I have seen uses logcat via Runtime#exec(), and I don't see a >> > command-line switch on logcat to limit output to just your own >> > process' lines. >> > >> > (BTW, count me as one of the fans of this decision, despite the very >> > loud grumblings I expect you will receive from various quarters) >> > >> > Thanks! >> > >> > -- >> > Mark Murphy (a Commons Guy)http://commonsware.com| >> http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy >> >> > >> > Android Training in NYC:http://marakana.com/training/android/ >> > -- 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
