Age | Commit message (Collapse) | Author |
|
Remove MODULE_LICENSE_APACHE2
Repositories containing third-party code need a METADATA and a
license_type. Repositories containing only first-party code no longer
need a MODULE_LICENSE_* file.
Remove EPL-licensed eclipse plugin and attribute_stats.
Remove CC-BY-SA licensed typos files.
Bug: 68860345
Bug: 69058154
Bug: 151953481
Test: treehugger
Test: https://android-build.googleplex.com/builds/forrest/run/L63500000550775268
Exempt-From-Owner-Approval: janitorial work
Change-Id: I5fafa76de21fb0b46c82a2c07ac048afbee3df25
|
|
This reverts commit eaada771a6e62ca494a625ce1b060f1a94fa9877.
Reason for revert: Breaks build_test and other builds
Bug: 155862492
Change-Id: I1a14b84d54b05596ec250b31ae56e437cf49fd81
|
|
Remove the source and switch the OWNERS to the janitors to prevent
necromancy.
Test: treehugger
Change-Id: I85d58aafad17c65d7d2963c99409dddf8888fb16
|
|
Change-Id: I1abdf1d9fddfe2e5ac1771bc919801efd5dd128e
|
|
The current tracing calls in RenderScript don't properly close
tags if there is an exception after opening a tag. So we don't
enable it by default.
Change-Id: I518da93896e7684efae6644cd6f8de6e6ebc56bb
|
|
This CL includes the following minor tweaks the systrace options
dialog:
- shows the default values to be used in a couple of text boxes
- splits the list of tags into two sections: a commonly used set
and a list of advanced tags
Change-Id: I19b3033c099c181c2d801da262a899f6586da9fd
|
|
We can just use the IntegerFieldEditor with a specified validity
range instead.
Change-Id: I23a60089b022a5fde8f94dcdc46d78a0dcb10182
|
|
For the V1 options dialog, Integer.toHexString is used to
write the value of the debug.atrace.tags.enableflags system
property, but it lacks the "0x" prefix. When this value is later
read by the framework with strtoll, it incorrectly interprets
the number as base 10 instead of hex.
This change updates the writing code to include a "0x" prefix
before the hex value, thereby ensuring that it is correctly
interpreted as a hex value in subsequent read operations.
Change-Id: I3fdb2f99d7e89dd197ee5433c2f54b14f147b62c
|
|
Change-Id: I0c72d2656dc4d16a32b62277e2814d511d67378f
|
|
Parts of the systrace html file were duplicated in the source
code (HTML_PREFIX and SUFFIX) as well as in the systrace scripts.
This CL picks up that content from data files present in the
systrace folder and removes the duplicated content from the source
files.
Change-Id: I517d23faa14022a666a7f314ffbb34187b1fed1f
|
|
Change-Id: I1b936bdd17a8348bd4bf88c4cccfbe90f43f93c0
|
|
Change-Id: I7d51fca33179b5dba3f5c12bf705a9a9c149383d
|
|
Change-Id: I2d15ec924fd43709f1b4afbfb575afc5d20b3afd
|
|
Change-Id: If1068713f3faa60db2a22e7dc6464a2af4928743
|
|
Currently, applications have to be launched with gltrace
enabled for OpenGL tracing to work. This patch provides the host side
support for dynamically enabling/disabling tracing on running apps.
At a high level, the functionality is similar to traceview:
- ClientData#FEATURE_OPENGL_TRACING indicates whether the VM on
the device supports this feature.
- If the feature is supported, then JDWP is used to send the
enable or disable messages.
- Users can trigger OpenGL tracing via a toolbar item in the DDMS
device view.
Change-Id: Icf5e5eade74f94cf6a74ff793533f75f1853731f
|
|
The atrace executable on the device now provides a list of
supported categories with the command atrace --list_categories.
This CL first tries to determine which version of atrace is
present on the device by running the list categories command
and attempting to parse its output.
For the older version, existing static "Capture Options" dialog
is displayed. For the newer version, only the supported categories
are displayed.
Change-Id: I300e7e652a9ae99f47d61a1669604802b74054a4
|
|
Change-Id: If75df27e17f5ad866b4a73a8422444f82c4c7ac0
|
|
Change-Id: I0757c58061aeb932b7f1c21d0cadea5d5d25024c
|
|
Also increased timeout since it seems to take a while longer
on the first attempt.
Change-Id: Ib005408f428dd083cc058a8594d4f6d55a0eead6
|
|
Fixes http://code.google.com/p/android/issues/detail?id=38000
Change-Id: I3465d1df1c85853ea1cb9fb01c92998842b884c5
|
|
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
|
|
Provides the ability to obtain user options for systrace,
launch systrace with those options and save the results in
an HTML file.
Change-Id: I4564421b86ebb384e5bd2b3e2329249abd3771aa
|
|
This CL integrates uiautomatorviewer into Eclipse. There are two
components to this:
1. Take UI Hierarchy Dump from a device: This is added as an action
to the device view in the DDMS perspective.
2. Viewing the resulting UI hierarchy: This is added as an editor,
associated with the .uix extension. The editor simply wraps a
UiAutomatorView.
The UiAutomatorView is modified slightly to allow for opening just
the hierarchy file without the associated screenshot. This is to
enable opening the .uix file via standard Eclipse Open File Dialog.
When opened this way, the canvas displaying the screenshot is replaced
with a button that allows the user to specify the actual screenshot
to be displayed.
Change-Id: I0f31fe95b2728123ff6f0f748478c18c0c2f1b48
|
|
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
|
|
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
|
|
Change-Id: Iab558863997bb8c5f72c8ef9349719ca003c1724
|
|
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
|
|
When hprof files are obtained from the device, they are saved by
default. This patch changes the default to open the hprof file if
it is a registered content type implying that there is an editor
for it.
This fixes http://code.google.com/p/android/issues/detail?id=21297
Change-Id: Ic89eb59855888daa4775852181d2af245c8893d9
|
|
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
|
|
Change-Id: If2b847d6937ea64b2727ff78f1c94850f91da81b
|
|
logcat provides two different ways to resolve the source corresponding
to a stacktrace: the primary method is to search for file name and
line number, and the secondary method is to search for the fully
qualified method name. Which method is used depends on a preference
setting.
This patch makes the following changes:
- Resolution now uses both the methods - it first tries to resolve
using the fqmn, and then improves the result using the filename/
linenumber if that is available.
- Since both methods are used, the preference setting can be removed.
- If there are multiple search results, rather than always jumping
to the first result, user will be prompted to select a result
This fixes http://code.google.com/p/android/issues/detail?id=18514
Change-Id: I1abdfe5f7e70423fb04d62f1092e1a8037537837
|
|
Both monitor and ADT use the same ddms-plugin preference pages.
However, certain preference fields are only applicable in the context
of ADT + Eclipse. This CL wraps the creation of such preferences
around a check for the availability of the ADT plugin.
Change-Id: Ic1c425d00feae3eeceece53e226baa99c3c8dc93
|
|
Currently, source revealers just reveal a file in the current perspective.
This changeset adds an option to first switch perspectives before revealing
the source file.
Change-Id: I5e89a89276f48ba41504434a1d2bb417f9ba541c
|
|
device."
|
|
Change-Id: I89bf6b84a2ef2ed9a876eec41fae9a974ba93137
|
|
Before selecting a target device.
Change-Id: I704d8af3d5f89dcbc5eb8e5e6b6090ddd8561e22
|
|
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
|
|
Currently, there are three locations that require the ability
to open a Java file containing a particular method: DDMS stack trace,
logcat and traceview.
The logcat and traceview panels use JDT to open up a Java editor on
a method. As a result, these plugins have a dependency on JDT.
The stack trace panel uses the DDMS plugin's sourceRevealer extension
point to achieve the same purpose. ADT plugin provides an
implementation of the sourceRevealer plugin. As a result, this
introduces a JDT dependency only on the ADT plugin.
This patch makes both the logcat & trace view code to use the same
sourceRevealer extension point. As a result, all source code
involved in revealing the source of a Java method is present in
a single place, and DDMS & Traceview plugins don't depend on JDT
anymore.
Change-Id: I5b840dc4d6ad45e5611a80cff740101c484a99dd
|
|
When ADT plugin starts up, it attempts to set the console to be used
for certain parts of DDMS to be the Android console.
Doing this however causes the DDMS plugin to be activated, which
launches adb server if it is not already there.
Removing this enables us to not touch adb unnecessarily.
This patch moves the initialization of the DDMS console into the
DDMS plugin, and uses the DDMS console as opposed to the Android
console for messages from DDMS.
Change-Id: I010a7028a2f22ac4da1c55903e001dcdd329d91f
|
|
DDMS plugin checks for 3 files when the tools location is set.
If any is missing, it won't connect to ADB. However there is
no way to know that exactly. This adds a log with the path
of the missing file.
Change-Id: If7b679342e6eef314470f63998cdb701e1e1920b
|
|
Change-Id: I42508186ea339de1d97f0de2e801e6152311881a
|
|
Change-Id: Ia2f02cbb02a89df6f665739427d842d6826a61cd
|
|
Change-Id: I3ade32621326456f030d9aaa581b011420fe4413
|
|
When a error message is detected on logcat, display logcat view but
with a filter for the application selected so that only the relevant
messages are displayed.
Change-Id: Ic84c59b63519302eac286ae243b228a305288b3d
|
|
- When applications are launched (run/debug) on a device, start
monitoring the logcat output on that device.
- If some important message comes across, and the logcat view is not
currently displayed, then activate it.
Change-Id: Ib88973badde4cb2860379129dfe0eb03a3f955dc
|
|
Until now there was only one instance of LogCatReceiver. This
instance would listen to the logcat output from the currently
selected device.
This patch modifies this behavior to make one LogCatReceiver
responsible for listening to only one device. If there are multiple
devices, then multiple instances of LogCatReceivers are instantiated.
The instantiation is also moved to a separate factory.
This modification allows for the scenario where the LogCatReceiver's
can be instantiated independent of the UI, and are reused by the UI
whenever needed.
Change-Id: I46008cbd5ee41880372a62e7e09634ce2d2fc122
|
|
Add a preference where users can set the size of the message list.
Defaults to 1000.
Change-Id: Ia888c3802f07607274bfbdca0ade8fbda009ba55
|
|
Change-Id: Idbf3bc093f2a049b5e0e0cd9605a6f8bdc8f7723
|
|
Change-Id: Ia2693424f0106fb3aa1724c211a8e1273f3a0c28
|
|
The existing logcat view has been renamed to OldLogCatView. It is
still accessible from the Views menu with the title:
"LogCat (deprecated)".
The new view is the default. The only missing feature compared to
the old view is the lack of double click handler. Subsequent CL's
add this feature.
Change-Id: If8ce594539f3f82c0c47ebb2d46159d6feed5a21
|