AMS FAQs on Android Core Issues

AMS there are several common problems in the following:

1. Low Memory issues

2. Performance Issues

3. Activity Jump Problem

4. Slow reception of broadcasts

Low Memory issues:

1. View kernel.log keyword sendsigkill / Lowmemorykiller

2. search through the application process name in the above search results, note that the process name in Kernel.log is printed to intercept the following

Performance issues:

Detailed analysis of the time-consuming points in event.log,system.log , and main.log and the current system state need to be carefully compared

Activity Jump question:

Print current system activity using adb shelldumpsys activity Stack information to understand the specific jump

broadcast reception Slow problem :

broadcast sent when the static registration of the broadcast is sent in an orderly manner, you need to wait until the previous processing is completed before sending after a broadcast, so there will be a slow reception problem

broadcast receive need to open Activitymanagerservice.java in debug_broadcast macro specific analysis broadcast send process

A few common debug commands:

?cat/proc/Meminfo?adbShellPS?cat/proc/<PID>/Oom_score_adj?Kill-3 <PID>?DumpsysActivity?Procrank?Top

Common am Log :

Common Activity record reason for destruction:

AMS FAQs on Android Core Issues