History log of /frameworks/base/core/java/android/webkit/TracingConfig.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
90980b42080c88b0b31ccbbbe1760037b26de8f7 04-Apr-2018 Tim Volodine <timvolodine@google.com> [WebView Tracing API] documentation fixes.

Some fixes to the WebView Tracing API related documentation.
In particular this patch makes sure that:
- the defaults are correct,
- the examples are correct,
- the formatting is ok,
- the text for parameters etc.. is formatted consistently,
- the documentation is spellchecked and typos corrected.

BUG: 63750258
Test: manual inspection of the generated html documentation
Change-Id: I53ac1a1d003e519739464b8d8554f3d8262c46e4
/frameworks/base/core/java/android/webkit/TracingConfig.java
1a07ccc07e9cc5b0ba8e8922979a486bd83f333d 19-Mar-2018 Tim Volodine <timvolodine@google.com> WebView Tracing API: remove LARGE_BUFFER, make RECORD_CONTINUOUSLY the default mode

This patch:
- remove the RECORD_UNTIL_FULL_LARGE_BUFFER tracing option, because
this does not appear really useful in the production setting as
the buffer size limit exceeds the device memory and can grow
uncontrollably large.
- make RECORD_CONTINUOUSLY the default mode for tracing, to make
sure the least memory is used by default (typically 4x less than the
previous default RECORD_UNTIL_FULL).
- add some missing IntDef values (to make them match with the constants)

BUG: 63750258
Test: CTS

Change-Id: Ib3698273dee776ebc7a8388fc1bd8c80255e3b63
/frameworks/base/core/java/android/webkit/TracingConfig.java
88604f2f8ac07283fa70ec2feb3aaeadcedaf0ce 18-Jan-2018 Tim Volodine <timvolodine@google.com> WebView Tracing API: address comments from the API council.

Address comments from the API council regarding the WebView Tracing API.

android.webkit.TracingController:
* start() throws IllegalStateException if the system is already tracing
(this is instead of returning false)
* stop uses Executor instead of Handler
* removed stop() (the method w/o arguments)
* renamed stopAndFlush to stop
* use OutputStream instead of a custom callback interface TracingOutputStream
* dropped requirement for UI threading
* updated documentation

android.webkit.TracingFileOutputStream:
* removed the TracingFileOutputStream file completely (functionality
replaced by the existing FileOutputStream)

android.webkit.TracingConfig:
* removed example with CATEGORIES_NONE and “-input,-gpu”.
* customCategories are List<String> instead of String
* updated documentation
* added two more predefined categories: CATEGORIES_ALL,
CATEGORIES_ANDROID_WEBVIEW
* some refactoring, added a Builder class
* ensure that only include category patterns can be specified
* uniform addCategories interface for construction
* predefined category sets are a bitmask now

BUG: 71584598,71584599,63750258
Test: CTS
Change-Id: I615ef5f43d26968329182b09e7c26178f1f85ecc
/frameworks/base/core/java/android/webkit/TracingConfig.java
c809542c3081ee2fd31313f29626cc0b765147cf 10-Nov-2017 Tim Volodine <timvolodine@google.com> Add WebView Tracing API.

Add classes/interfaces necessary for the support of tracing API
in WebView.

In particular:
- TracingController: singleton class for starting and stopping
tracing and inspecting tracing status.
- TracingConfig: holds tracing configuration, such as categories
to filter and the tracing mode.
- TracingOutputStream: interface for capturing tracing data.
- TracingFileOutputStream: supporting class for capturing tracing
data to a file.

BUG: 63750258
Test: in progress

Change-Id: I7decd486788766fc8dfa766ae027c02f9d4c6f80
/frameworks/base/core/java/android/webkit/TracingConfig.java