Merge "Deprecate TimingLogger"

am: aec0ab99d4

Change-Id: Ie6709d7e83ee68d491eac481635bcba3d44efe1e
This commit is contained in:
Charles Munger
2019-11-22 12:51:48 -08:00
committed by android-build-merger
2 changed files with 13 additions and 6 deletions

View File

@@ -48530,12 +48530,12 @@ package android.util {
method @Nullable public static java.util.List<java.lang.String> getTimeZoneIdsForCountryCode(@NonNull String);
}
public class TimingLogger {
ctor public TimingLogger(String, String);
method public void addSplit(String);
method public void dumpToLog();
method public void reset(String, String);
method public void reset();
@Deprecated public class TimingLogger {
ctor @Deprecated public TimingLogger(String, String);
method @Deprecated public void addSplit(String);
method @Deprecated public void dumpToLog();
method @Deprecated public void reset(String, String);
method @Deprecated public void reset();
}
public class TypedValue {

View File

@@ -44,7 +44,14 @@ import android.os.SystemClock;
* D/TAG ( 3459): methodA: 6 ms, work C
* D/TAG ( 3459): methodA: end, 16 ms
* </pre>
*
* @deprecated Use {@link android.os.Trace}, or
* <a href="https://developer.android.com/studio/profile/benchmark">Android Studio</a>. In
* general, milliseconds is the wrong granularity for method-level tracing. Rounding errors
* can overemphasize cheap operations, or underemphasize repeated operations. This timing
* system also does not take CPU scheduling or frequency into account.
*/
@Deprecated
public class TimingLogger {
/**