個人積分：40分
文章編號：17453769
他藉由設定Android內建的參數，讓Android提早啟動"內建"的記憶體回收機制，所以比手動安全多了
我講解Aggressive這個profile其中一項，各位其他就可以自行理解
=> 當記憶體不足97M時，要執行Empty Application的回收
個別process引用xda如下:
FOREGROUND_APP:
// This is the process running the current foreground app. We'd really
// rather not kill it! Value set in system/rootdir/init.rc on startup.
VISIBLE_APP:
// This is a process only hosting activities that are visible to the
// user, so we'd prefer they don't disappear. Value set in
// system/rootdir/init.rc on startup.
SECONDARY_SERVER:
// This is a process holding a secondary server -- killing it will not
// have much of an impact as far as the user is concerned. Value set in
// system/rootdir/init.rc on startup.
HIDDEN_APP:
// This is a process only hosting activities that are not visible,
// so it can be killed without any disruption. Value set in
// system/rootdir/init.rc on startup.
CONTENT_PROVIDER:
// This is a process with a content provider that does not have any clients
// attached to it. If it did have any clients, its adjustment would be the
// one for the highest-priority of those processes.
EMPTY_APP:
// This is a process without anything currently running in it. Definitely
// the first to go! Value set in system/rootdir/init.rc on startup.
// This value is initalized in the constructor, careful when refering to
// this static variable externally.
test
個人積分：40分
文章編號：17453808
個人積分：3771分
文章編號：17455643
個人積分：5分
文章編號：17456282
個人積分：12分
文章編號：17462196
個人積分：734分
文章編號：17462628
個人積分：10分
文章編號：17463135
個人積分：5分
文章編號：17463351
個人積分：40分
文章編號：17463434
個人積分：734分
文章編號：17463538
