Fixed
Status Update
No update yet.
Comments
aa...@google.com
Hey thanks for reporting! We're just starting to dig into this.
Can you run
$ adb version
and also
$ which adb
Can you run
$ adb version
and also
$ which adb
jv...@google.com
$ adb version
Android Debug Bridge version 1.0.31
$ which adb
/usr/bin/adb
BTW - "adb kill-server" also does the job, so it's really the server restart, not "adb logcat" that kicks off logging in AS again.
Android Debug Bridge version 1.0.31
$ which adb
/usr/bin/adb
BTW - "adb kill-server" also does the job, so it's really the server restart, not "adb logcat" that kicks off logging in AS again.
aa...@google.com
How about something like this?
I think having defined members be directly under the class node while references are nested in a group makes more sense.
Also note that the method refs have a
jv...@google.com
Hey Torsten, can you refresh my memory? You're using a Nexus 6 device, right?
aa...@google.com
an...@google.com
No, Nexus7 (2013), Android build MMB29K dev-keys.
Description
1) the methods are a lighter shade of gray if they're just a reference
2) there's no counter for the "defined methods" column.
This is not very discoverable and we had various people at Google I/O be confused about this, especially when they had multi-dex in their APK, looking at classes.dex they saw their methods and were annoyed that the tool didn't allow them to see their bytecode.
We should consider changing this UI to make this more discoverable.
One option: have two separate trees in the view, one for definitions and another for references. where each root node is named as such.