Android core issue-ams faq analysis, androidams
AMS has the following common problems:
1. low memory problems
2. Performance problems
3. Activity jump
4. Slow Broadcast Reception
Low memory problems:
1. view the keyword sendsigkill/lowmemorykiller in the kernel. log.
2. Search and view the application process name in the preceding search results. Note that the process name in kernel. log is printed as the last 15 digits.
Performance problems:
You need to carefully compare and analyze the specific time consumption and current system status in event. log, system. log, and main. log.
Activity jump problem:
Use the adb shelldumpsys activity to print the current system activity stack information to understand the specific jump
Slow Broadcast Reception:
When a broadcast is sent, the static registered broadcast is sent in an ordered manner. The latter broadcast is sent only after the previous processing is completed. Therefore, the latter receives slowly.
To receive a broadcast, open the DEBUG_BROADCAST macro in ActivityManagerService. java to analyze the broadcast sending process.
Several common Debugging commands:
• Cat/proc/meminfo • adb shell ps • cat/proc/<pid>/oom_score_adj • kill-3 <pid> • dumpsys activity • procrank • top
Common am log:
Common Causes of activity record destruction: