From 6b1a18c61b5a3127d72d26b0ff39f0fdc1a66215 Mon Sep 17 00:00:00 2001 From: Heidi von Markham Date: Thu, 28 Jul 2016 13:59:25 -0700 Subject: Docs: Updating bug report content Adding Joe's comments Correcting BLE content Adding Gina's comments Bug: 30434587, 29216826 Change-Id: Ief2db9f14cc75dd4e53f839308dd54c4c352ea1d --- src/source/read-bug-reports.jd | 55 ++++++++++++++++++++++++++++++++++++++---- 1 file changed, 50 insertions(+), 5 deletions(-) diff --git a/src/source/read-bug-reports.jd b/src/source/read-bug-reports.jd index 0f82f3df..595d3bb7 100644 --- a/src/source/read-bug-reports.jd +++ b/src/source/read-bug-reports.jd @@ -96,6 +96,9 @@ When viewing event logs, you can search this section for specific process ID ...

+

 

+

For other useful event log tags, refer to +/services/core/java/com/android/server/EventLogTags.logtags.

ANRs and deadlocks

Bugreports can help you identify what's causing @@ -121,7 +124,7 @@ blocked or busy main thread, the system kills the process and dumps the stack to

-

You can also grep for ANR in in the logcatlog, +

You can also grep for ANR in in the logcat log, which contains more information about what was using CPU at the time of the ANR.

@@ -800,7 +803,7 @@ ACTIVITY MANAGER BROADCAST STATE (dumpsys activity broadcasts) -

Monitor Contention

+

Monitor contention

Monitor contention logging can sometimes indicate actual monitor contention, but most often indicates the system is so loaded that everything has slowed down. You might see long monitor events logged by ART in system or event log.

@@ -811,7 +814,7 @@ You might see long monitor events logged by ART in system or event log.

In the event log:

10-01 18:12:44.364 29761 29914 I dvm_lock_sample: [com.google.android.youtube,0,pool-3-thread-9,3914,ScheduledTaskMaster.java,138,SQLiteClosable.java,52,100]

-

Background Compilation

+

Background compilation

Compilation can be expensive and load the device.

@@ -937,6 +940,24 @@ screen on, and 2 is for keyguard done.

10-18 15:36:37.660 3283 3283 I screen_toggled: 2

+

+

Bug reports also contain statistics about wake locks, a mechanism used by +application developers to indicate their application needs to have the device +stay on. (For details on wake locks, refer to +PowerManager.WakeLock +and Keep +the CPU on.) + +

The aggregated wake lock duration statistics track only the +time a wake lock is actually responsible for keeping the device awake and +do not include time with the screen on. In addition, if +multiple wake locks are held simultaneously, the wake lock duration time is +distributed across those wake locks.

+ +

For more help visualizing power status, use +Battery Historian, a +Google open source tool to analyze battery consumers using Android bugreport +files.

Packages

The DUMP OF SERVICE package contains application versions (and other useful @@ -1132,5 +1153,29 @@ Process LRU list (sorted by oom_adj, 34 total, non-act at 14, non-svc at 14): Proc #21: cch+6 B/ /CE trm: 0 995:com.google.android.partnersetup/u0a18 (cch-empty)>

- - \ No newline at end of file + +

Scans

+

Use the following steps to identify applications performing excessive +Bluetooth Low Energy (BLE) scans:

+ +

Note: For devices running Android 7.0, the +system collects data for BLE scans and associates these activities +with the initiating application. For details, see +Low Energy (LE) +and Bluetooth scans.

-- cgit v1.2.3