| Commit message (Collapse) | Author |
|---|
|
Change-Id: I990a4d2c68cd51f0043390408c3b128c4bb20900
|
|
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
Change-Id: I0d7ef57b31e8cc75fadd4d5d04fd70690af01939
|
|
* CAF's init.qcom.early_boot.sh checks /persist/alarm/powerOffAlarmSet
before setting ro.alarm_boot, but on Oreo nothing writes to that
file, thus code is never executed and the prop is never set.
* Without ro.alarm_boot=true, the system will boot normally instead of
boot to min framework even on rtc, and alarm will ring after boot
completed.
Change-Id: Ie4d30358314337c229a66a16195f675198ef7d52
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
|
|
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
|
|
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
|
|
Change-Id: I635dc8d27f92f9a2fa83da62c2f32e48bd2c7680
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
|
|
Check if power off alarm is set, then set alarm's properties
Adapted from Mao Jinlong <c_jmao@codeaurora.org> patch in init.qcom.early_boot.sh
Change-Id: Ib86584d1c09aba07c47435ac8bed39aac79a80f7
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
|
|
This was missed out from init.qcom.early_boot.sh.
Change-Id: Iab5b0d7782a53b97315d2aa9d0c301ed7725e01d
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
|
|
Change-Id: I3fd23490bcdfa4097dad73161ad226337e93cd18
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
|
|
The maximum heap size for each virtual machine is 1GB. This is too big
and puts too much pressure on both the garbage collector when it tries
to perform collections in older generations. The symptoms are simple,
some applications will allocate objects that live long enough to be
promoted to older generations, escaping the efficient CMS collections.
Eventually, a stop-the-world collection will go through this large block
of memory and cause applications to pause for too long.
Additionally, the out of memory killer follows a LRU approach where it
tries to kill older applciations to make room for new ones. The problem
arises when the least recently used applications don't have large heaps
but the most recent ones do. When this happens the system halts to a
crawl while older apps and services are killed and respawned in a never
ending cycle of jankiness.
These values were obtained experimentally but actually match the
defaults for devices with >2gb of ram and xhdpi.
Change-Id: I73a92269ceac61dd4d4c1b1600f55a21534a27a0
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
|
|
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
|
|
Change-Id: I656cbed7abf351fea4129e7ff3c930eb9d8914ae
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
|
|
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
|
|
Signed-off-by: dd3boh <dade.garberi@gmail.com>
|
|
Signed-off-by: dd3boh <dade.garberi@gmail.com>
|
|
I prefer it like this :P
Signed-off-by: dd3boh <dade.garberi@gmail.com>
|
|
Change-Id: I656cbed7abf351fea4129e7ff3c930eb9d8914ae
Signed-off-by: dd3boh <dade.garberi@gmail.com>
|
|
|
|
|
|
Change-Id: I4108d946fe4005af64a34b46e68dd94cdef98a6b
|
|
|
|
*Lets start
|
|
Change-Id: Ifd9184c31569d88a21d989e6df59d20e47aed135
|
|
|
|
|
|
|
|
|
