* This introduces fixup scripts and kang mode and fixes
passing of arguments longer than one word,
such as --section "Hello world".
Change-Id: I42dde659e9bea4f7e1c9a7a3fa8da3243774ca4e
Signed-off-by: SamarV-121 <samarvispute121@gmail.com>
* This is required for Ambient Display to work properly.
Change-Id: Ibad86be4e1c43a221fc2224d0a8f8ca2c938a6c7
Signed-off-by: SamarV-121 <samarvispute121@gmail.com>
New name is config_dozeAfterScreenOffByDefault
Bug: 73178121
Change-Id: Ie3d1ea5a2cc480655592bf6e49b37f5ea07f3f5
Signed-off-by: SamarV-121 <samarvispute121@gmail.com>
* also use ims.apk and qti-telephony-common.jar only from davinci
* Add power-off alarm framework
Signed-off-by: SamarV-121 <samarvispute121@gmail.com>
The current use of the SCROLL_PREFILING hint hurts scroll performance
and results in a lot of dropped frames.
The hint ID corresponding to SCROLL_PREFILING only takes into effect for
a default timeout value of 80 ms (as found in perfboostsconfig.xml),
while the duration value in the process_interaction_hint function runs
for a much longer time, from 1500 ms up to 5000 ms (bounds of
kMinFlingDuration and kMaxInteractiveDuration). During the period
of time, when the timeout value has elapsed and current time is less
than duration, another interaction hint cannot be processed. Therefore,
if the user decides to scroll during this period, high frame drops can be
experienced as the CPU freq isn't raised by processing another hint to
account for this additional scrolling.
By only using SCROLL_VERTICAL, fluidity can be maintained, improving user
experience.
Change-Id: I2fbde8b2db6710d262e9a058e0bc9c02e524648c
Signed-off-by: SamarV-121 <samarvispute121@gmail.com>
Currently, the launch boost perflock is held for a fixed duration, either
specified in perfboostsconfig.xml for perf HAL platforms or hardcoded in the
powerHAL for non-perf HAL platforms.
Using a fixed duration for this perflock has two shortcomings:
* perflock can be held for too long, causing the CPU freq and other resources
to be boosted for too long even if the application has finished launching,
resulting in excessive battery drainage
* perflock can be held not long enough if it takes more than the timeout
time to finish launch
The framework sends out a powerhint for both when launch starts and when
launch ends. The launch finish hint can be used to signal when to release the
perflock.
Reference: Wahoo power-libperfmgr
Change-Id: I405cc453c5f58d9fb2583b9c6017f3964a0ce024
Signed-off-by: SamarV-121 <samarvispute121@gmail.com>
The service must be made part of the input group,
so that the power HAL can access the input nodes present
in the different targets.
Change-Id: I30a7bde8aebac4b76cbf59f5f795ea245aba1014
Signed-off-by: Giuseppe Barillari <joe2k01dev@gmail.com>
Signed-off-by: SamarV-121 <samarvispute121@gmail.com>
Removed unused code and added generic hint handling to power.c file,
does not need to be device specific anymore.
Change-Id: I0d4e2a73de0ce4d3735314d2e49ba58c23eb313c
Signed-off-by: SamarV-121 <samarvispute121@gmail.com>
VNDK restrictions doesn't includes standard headers by
default, add them explicitly.
Change-Id: I4c72a28ffa141ecadcfe47cc7c1f62f2a0c8576e
Signed-off-by: SamarV-121 <samarvispute121@gmail.com>
Using the wall clock will cause boosts to be disabled
when/if the clock is adjusted backward.
Bug: 29191415
Bug: 29208304
Change-Id: I8af5f40b46d996ce7bccb8324fc186e2f3a5b267
Signed-off-by: SamarV-121 <samarvispute121@gmail.com>
* MP-CTL does not handle POWER_HINT_INTERACTION and POWER_HINT_LAUNCH
directly. Requests for processing are sent by Qualcomm BoostFramework
(QPerformance) at the framework service level. Since we do not have
BoostFramework, process POWER_HINT_INTERACTION and POWER_HINT_LAUNCH
in PowerHAL to ensure a sufficient level of performance.
* For proper operation, perfboostsconfig.xml file is required.
Change-Id: I9fedcbaa189147c91d932711c831c2ce038a7ec7
Signed-off-by: SamarV-121 <samarvispute121@gmail.com>
* Without this, fingerprint stops working after using it
for the first time.
Change-Id: Ibdcdf8f1b5beaf481f2a7a9fd8ad199494161502
Signed-off-by: SamarV-121 <samarvispute121@gmail.com>
This makes bionic and various art tools that compile/runs cpu-specific
code choose the cortex-a53 variant at runtime. It does not affect
build-time compilation.
Bug: 120773446
Test: bionic benchmarks with and without this change
Change-Id: I670c8acd094090135515688c5f057c2cc08a083f
Signed-off-by: SamarV-121 <samarvispute121@gmail.com>
* Our ims.apk doesn't load ims-ext-common.jar, and it's moved to /product
on 10 where PRODUCT_BOOT_JARS doesn't work.
* Create a system copy of the jar and add it to boot classpath to make
it loadable from the apk without extra work,
Change-Id: Ia530a530bd4469e12500410fc5e8ba393de60b18
Signed-off-by: SamarV-121 <samarvispute121@gmail.com>
The product abstracts configs that need to be set to support updating of APEXes.
Change-Id: Id5aa944ceba6a6846308f1c18a08af8b3bb38589
Signed-off-by: SamarV-121 <samarvispute121@gmail.com>
