| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: Iba15f82cb00d19217382c78d8ff37dda1e97ea59
|
|
|
|
|
|
|
|
|
|
|
| |
There were a couple of pieces of UI data (unread count & flag
indicating whether a filter is transient) associated with a filter.
This CL moves both of them out into a separate class. The panel
maintains a mapping from a filter to its associated UI data.
The core filter class has been moved out into ddmlib.
Change-Id: I325176c33094d583c0ef9abe890e5462aeeb4945
|
|
|
|
|
|
|
| |
Requires Change-Id Ie120f978e5c5646e086ec999c9ef5027b724cc7a
in tools/base
Change-Id: Ib436fa6b70ba49e48b2e7c974094c27b77c9fbb9
|
|
|
|
|
|
|
| |
Replace LogCatPidToNameMapper with a call to
IDevice.getClientName(pid)
Change-Id: I8c29b5d29cccf29ea22536a3f270f0f8963aba64
|
|
|
|
|
|
| |
Also remove the need to double-click to see a stack.
Change-Id: I076179b09350d1c85614c7325e2faa4848b4e8d8
|
|
|
|
|
|
|
| |
Rather than rely on the user enabling the setting in
developer options, we enable it automatically.
Change-Id: I25360d88e8b0262dc6c5b9f503cd0e7e2958ba28
|
|
|
|
| |
Change-Id: I8fdb798a0c5374a4be2825cb4be5f4f58437253e
|
|
|
|
|
|
|
|
|
|
|
| |
General cleanup of the SysInfo Panel:
- Remove support for displaying wakelocks/alarm/sync etc info since
the existing parsers were woefully out of date and didn't work
anyway.
- Move parsing datasets out of the SWT thread
Change-Id: Iac77c322ad1db715772f585212da2330a6f9d693
|
|
|
|
| |
Change-Id: I86d00756242c4a3f5ac70a926065789fde428825
|
|
|
|
|
|
|
|
|
|
|
|
| |
The sysinfo panel provides a pie chart visualizer for a few
"adb shell dumpsys" options. Unfortunately, most of them don't
work with newer devices since the output format of the dumpsys
command has changed. This CL updates the CPU load parser to work
for both old and new output formats.
http://code.google.com/p/android/issues/detail?id=39243
Change-Id: Ie76eedcaa7cfe13edf930104308ac824319dafa8
|
|
|
|
| |
Change-Id: If5f0c6073cfe847c8d04360cfe7b2f5e4cd58766
|
|
|
|
|
|
|
|
| |
- Makes it easier to scan
- Doesn't show user id at all for phones since there are no
multiple users on a phone.
Change-Id: I108f220ccf0af7e1293dd6cab58705ea19014ae4
|
|
|
|
|
|
|
| |
Scrolling behavior should not be altered when the scroll bar
location changes due to the addition of new messages.
Change-Id: Id38deb9f17d6d58bea6f25b33fed23c887c5cc5d
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Another go at adding support for automatically enabling/disabling
scroll lock. Past attempts have been brittle because of differences
in how Windows, Linux and Mac handle the scrollbar.
The key to getting this work consistently across platforms seems
to be in explicitly setting the range of values for the scrollbar.
Setting the maximum to be a high enough value relative to the
thumb allows accurate detection of even minor movements away from
the bottom of the scrollbar.
Change-Id: Ic3259cc4e2e8a20f3a87ce4bf234217cea792f88
|
|
|
|
|
|
|
|
| |
The HELO and APNM packets may append the user id at the end of the
packet. If that data is available, display it as part of the
application name.
Change-Id: Ie353c2cc2895db649fc6ab6054f1c88f5d2f247f
|
|
|
|
| |
Change-Id: I6238185edd10227a01ae2f5282de18b17edb26bc
|
|
|
|
|
|
|
| |
Fix NPE that could happen if the device goes offline even before
logcat command is issued on it,
Change-Id: I334caae5e42d25eff396ce0b7b7a5e44c3ed4f61
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are a number of places where we need to display a device
name. Currently, DDMS shows the serial number + manufacturer/model
if available, but in other instances, we just show the serial
number.
This CL provides a getName() method in the IDevice interface so
that all the locations which require a human readable name can
use this.
The name is typically of the form manufacturer-model-serial.
If the manufacturer/model strings are not available, then those
fields are omitted, so it will show just the serial number.
Change-Id: I80ef7b48a4c7c8587042c1227c932251e18dba2e
|
|
|
|
|
|
|
|
|
|
| |
This CL allows the default action to be either of the "Find Next"
or the "Find Previous" buttons in the find dialog.
Typically, in logcat you want to find previous, while in gltrace
view you want to find next.
Change-Id: Ie11cbd8a7987b8011ec2ee3664034e9ecfc4e24b
|
|
|
|
| |
Change-Id: If2e89c894f5f11104e30d892bcae2b2daec17b08
|
|
|
|
| |
Change-Id: Ie3b2e424a7dc9df73aca1c7914497f1c9a126901
|
|
|
|
| |
Change-Id: I137994ea4723299461c695559d664230a98b082f
|
|
|
|
|
|
|
|
|
|
|
|
| |
This CL adds support for invoking a find dialog when
the logcat view is in focus. The dialog can be invoked
via Edit -> Find (Ctrl + F), or via the context menu.
The dialog provides a way to specify a search term and
allows the user to search forward or backward in the
list of messages.
Change-Id: I7e7c6b20a051c161f035b3b45aba5f119f2c11a9
|
|
|
|
| |
Change-Id: I3825ba3149c644e834744f347a3973e9c8cd07ce
|
|
|
|
|
|
|
| |
This changeset fixes various code fragments opening
resources without closing them.
Change-Id: I6ed48a32dc5de4c11cab394dd3883ebbb54d2938
|
|
|
|
|
|
|
|
|
|
| |
This patch enables users to customize the colors used for
log messages of different priority levels. These settings
are available in the Android -> Logcat -> Colors preference page.
This fixes: http://code.google.com/p/android/issues/detail?id=31494
Change-Id: I9430f573f84f09d00bfe25d6e53eeccf4e338e9d
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To help users who don't know about logcat, we automatically monitor
logcat output to see if there are any errors from a user application,
and if so, display the logcat view.
This patch makes this feature a bit easier to use:
- The first time the logcat view is about to be displayed, a dialog
is shown that allows the users to enable/disable auto monitoring.
Note that this can also be done via logcat preferences.
- Users can now control the message priority that will trigger
auto monitoring.
- Once the logcat view has been displayed, we turn off auto monitoring
until the next launch. This reduces overhead and avoids unnecessary
change of focus in cases where the user is already interacting with
the logcat view.
Change-Id: I44a9ccea9148dea7bf6dc7d7864a1bb56a7376fe
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, when users create regex based filters, any error in the
regex pattern is logged. When the error is logged, context switches
to the Eclipse console view. As a result, users have to switch back
to the logcat view and fix the error.
This patch validates the text on entry and sets the text color to
be red if the pattern is incorrect. There are no context switches
as a result.
This fixes issue: http://code.google.com/p/android/issues/detail?id=22019
Change-Id: I5b571e34c1517b0a78046b56ad83c2aa8632abdb
|
|
|
|
|
|
|
|
|
|
| |
When a device is disconnected, an explicit message informing
the user of this event is attached to the log.
See http://code.google.com/p/android/issues/detail?id=25830 for
the reason why this might be useful.
Change-Id: I969004cb72b877b8319a639607f82c1c9f9a8635
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch allows users to create logcat filters based on an
existing message. When a message is right clicked, it brings up
a menu with an entry that says "Filter similar messages..".
Selecting that will bring up the "Add new filter" dialog with
its input fields prefilled based on the message contents.
This fixes: http://code.google.com/p/android/issues/detail?id=25835
Change-Id: If324330cbf78b503be61c31ebcff053d0f869c1e
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch fixes a bunch of outstanding issues related to
scrolling in the presence of a full buffer.
Currently, the logbuffer is provided as the input model to the
TableViewer, and ViewerFilter's are used to filter the data.
This patch removes the JFace toolkit and directly works on the
SWT Table. When log messages arrive, rather than refreshing the
entire table, we can now just delete the TableItems corresponding
to the logs that were pushed out, and add new TableItems for the
incoming logs.
At steady state, this implementation performs far less work than
the previous implementation. However, during startup, this
implementation will perform more work since it does not use the
SWT.VIRTUAL bit (as all TableItems are created anyway).
Also, zebra striping has been removed to avoid appearance of flicker
when scroll lock is on.
Auto scroll lock behavior has been removed, and scroll lock button
behaves exactly like the scroll lock button in an Eclipse console.
Change-Id: Ic14487f7ad41338a581aed0ba2d85d292a584950
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Issue: http://code.google.com/p/android/issues/detail?id=28253
Change-Id: If7b3c2a898b30834a8e76c5aad615a41ba5ecc04
|
|/
|
|
|
|
|
| |
This patch simply makes sure that the filename will have a .png extension when saving a screenshot through DDMS.
Change-Id: Idb00259ac456fcaf11ee99736663fc7ddbbc505b
Signed-off-by: Sebastian Roth <sebastian.roth@gmail.com>
|
|
|
|
|
|
|
|
| |
The thread id's output in "logcat -v long" used to be encoded in hex,
but not anymore. This fixes the logcat parser to accomodate both the
old and the new formats.
Change-Id: I0871a68f2f82c5e4660c404ec8970063d7b68a88
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
LogCatReceiverFactory has a deadlock scenario that occurs like this:
1. When a device is disconnected, removeReceiverFor() is called from
a DDMS device monitor thread. This thread holds certain DDMS internal
locks. removeReceiverFor() is synchronized on LogCatReceiverFactory.
So we have:
DDMS thread - holds device lock
removeReceiverFor - waiting to obtain lock for "this" object.
2. At the same time, a separate thread could call newReceiver.
As part of creating a new receiver, we add a device change listener.
So we have:
newReceiver - holds "this" object.
create device change listener - waiting for device lock.
As a result, the system deadlocks. This patch fixes this condition by
calling the removeReceiverFor from a non DDMS thread since we don't
really care about DDMS locks here.
Change-Id: Ic4ef4589acdcd7980864da23cde760debc4cfbb8
|
|
|
|
|
|
|
|
|
| |
Always start with network panel paused, letting user control start
and stop explicitly. Also pause when client is changed.
Handle devices without xt_qtaguid module by showing error dialog.
Change-Id: I4f6c81d8c52729c155b7f4a477bcec1857681da8
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
New panel that shows live network statistics by reading xt_qtaguid
proc file across adb. Shows all tags for selected UID on a chart
with 30 seconds of history. Each tag is presented as unique series,
with the overall usage in grey. Table below the chart shows running
totals of known tags.
Includes options to pause, reset, and change polling frequency.
Bug: 5194997
Change-Id: I72d43ab51aaf93ecfd6d45fcd452c7230cdee5b7
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This changeset fixes issue
23747: i and İ character problem in turkish operating Systems...
and probably many other bugs in the Turkish locale.
Basically, we had a lot of String.toLowerCase() and
String.toUpperCase() calls. This performs locale sensitive
conversions, which in many cases is NOT what we want; for "machine
readable" conversions we should be using Locale.US which performs no
special cases.
For more, see
http://developer.android.com/reference/java/util/Locale.html#default_locale
Change-Id: I996b0e70fb377e8dae484c5811deb8bc9afb684c
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This changeset makes the SDK codebase compile with source=1.6 (which
means it also requires JDK 6). This means that methods implementing an
interface requires @Override's. It also means we can start using APIs
like the ArrayDeque class and methods like String#isEmpty().
This changeset looks big but the change is trivial: it's basically
adding @Override in all the places that need it, along with some other
automatic Eclipse cleanup in certain files (such as reordering imports
where they were incorrectly ordered (because older versions of Eclipse
didn't always handle inner classes right)), as well as cleaning up
trailing whitespace and removing some $NON-NLS-1$ markers on lines
where there aren't any string literals anymore.
This changeset also sets the source and target JDK level to 6 in the
Eclipse compiler .settings file, and synchronizes this file to all the
other Eclipse SDK projects.
Change-Id: I6a9585aa44c3dee9a5c00739ab22fbdbcb9f8275
|
|
|
|
|
|
|
|
| |
DDMS displays only the serial number for connected devices.
This patch appends the manufacturer & model name to the serial
number.
Change-Id: I90400365fe984b0b0a198e3c21aaf25eb05aa930
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Setting up scroll lock automatically is broken due to the highly
platform dependent nature of the scroll bar events. This patch
improves the current situation significantly, but may not be the
last word on this subject.
This patch does the following:
1. Sets up auto scroll lock on Windows and Linux.
2. Removes auto scroll locking on Mac. Users have to manually
press the Pause Logcat button.
3. Renames the "Scroll to latest" button to "Pause Logcat" to
more accurately reflect what is happening.
Change-Id: I1ce03371d7ac7aeaea218aa3c5c426c69c56a527
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The previous commit introduced a bug: The SWT table model is a list of
logcat messages before any filters are applied. But the user sees the
filtered messages. So when user selects items in the table, the
selection index will not match the index in the input model.
This patch applies all current filters to the input model and then
indexes this filtered list to get the same items that the user has
selected in the view.
Change-Id: If955bd5c22e1c587bcf5fe32092f513d53c0d8ef
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Fix NPE when selecting all items: Issue is that in case of a
table with SWT.VIRTUAL, tableItem.getData() could return NULL if
the item hasn't been shown. So we have to rely on the original
model to retrieve the items.
2. When viewing items after applying a filter, clear log will
clear the full log but not the filtered view. To clear the filtered
view, the SWT ViewerFilters have to be reapplied.
Change-Id: I6c66be4e0e8abb6db114588f382bcd3b9fe8ee0f
|
|
|
|
|
|
|
| |
When a saved filter is double clicked, bring up the 'Edit Filter'
dialog for the selected filter.
Change-Id: Idd6766ba95e0d2f228c664ffccf8dbfb5b93b0b8
|
|
|
|
|
|
|
| |
Fix for http://code.google.com/p/android/issues/detail?id=22111 which is
OS X Lion specific. This fix hasn't actually been tested on OS X Lion!
Change-Id: Ifb4397e1482ebacc84cd90e83bb6837b883fbd08
|
|
|
|
|
|
|
|
|
| |
Fix for Issue #21554. When a client process dies, the native
heap view is immediately cleared. This makes it impossible to
view the native heap snapshots for processes that are being
killed due to OOM errors.
Change-Id: I3b6c868832c6b48e591d31d1643db20887ff8c13
|
|
|
|
|
|
|
|
| |
One some platforms, the table doesn't show any rows at all, and there is
no way to resize the table. This patch makes sure that there is one row
that is always displayed.
Change-Id: Ib93839c610926a7f8629436d26bb7ad9485431af
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the logcat buffer is full, any received message will push out
an old message. As a result, the messages keep moving up the table,
which is annoying if you want to view a particular message.
Ideally, we'd keep the view constant, but only the scrollbar moves
up to indicate that we have received new messages. But this doesn't
work in an SWT table.
One solution would be to refresh the table and then scroll it to
remain in the same place. This causes a flicker and is annoying.
This patch stops refreshing the table when the user is viewing an
older item in the table, and starts auto refresh if the scroll bar
is again brought to the bottom. In addition it provides a toolbar
button that reflects the state of scrolling, similar to a scroll
lock checkbox.
The one downside to this is that since the scrollbar does not move,
the user does not have clue if new messages are being received.
The new messages will be noticed only if the user unselects the
scroll lock button, or manually moves the scrollbar down.
This is a fix for Issue #20805.
Change-Id: I12108789265fec38287a466d21505db85892594d
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Various places of the code construct a new FileInputStream
on the fly and give it to another method. One many
occasions the stream is never properly closed, which can
lock files on Windows.
2 specific cases:
- Properties.load() doesn't seem to close its input
(when looking at the source bundled with the JRE).
- The doc of InputSource (used by various XML parsers like
the pull parser) indicates the caller should in general
not close the stream and the parser itself should do it.
Change-Id: I622b54a22f97ed2c9c8fdc56ccde331207d9d212
|