| 228629e920edf056eb12a3d0f4adf6ef84642632 |
|
08-Apr-2010 |
Brad Fitzpatrick <bradfitz@android.com> |
Rename logtag for clarity.
BUG=2581935
Change-Id: I85f0b704435861acd5a406ce5ec084b60696580c
/frameworks/base/core/java/android/content/EventLogTags.logtags
|
| 2c5da313dd72c284fbc2c11839f8a452ab5ce574 |
|
25-Mar-2010 |
Brad Fitzpatrick <bradfitz@android.com> |
Log blocking Binder calls to the EventLog.
This mimics what we do already for SQLiteDatabase's db_operation and
ContentProvider's content_query_operation and
content_update_operation: over a threshold things are always logged,
and under which they're sub-sampled.
Change-Id: Ia0280b9b07b336ee88b17be2a31a7af0fd7c5770
/frameworks/base/core/java/android/content/EventLogTags.logtags
|
| a63730d1f103f78589faef461d2af7351fc49f42 |
|
08-Feb-2010 |
Brad Fitzpatrick <bradfitz@android.com> |
Log ContentProvider operations to the EventLog.
Just like with db_operation, operations over 100ms are always logged,
while operations under that are subsampled.
This will help with performance analysis, getting real-world
performance numbers from dogfooders.
/frameworks/base/core/java/android/content/EventLogTags.logtags
|
| 44641d3db3b5fd5c7616c8a646ec8b6af20baa18 |
|
09-Jan-2010 |
Paul Westbrook <pwestbro@google.com> |
Bug 2321983
Move SYNC_DETAILS from framework/base to the gsf clientlib
/frameworks/base/core/java/android/content/EventLogTags.logtags
|
| 45e6dbf90b24543c90f8c6b0426e9b70c934838d |
|
08-Dec-2009 |
Doug Zongker <dougz@android.com> |
move event log tags used by SyncAdapter into a local .logtags file
/frameworks/base/core/java/android/content/EventLogTags.logtags
|