* This hint along with almost every MTKPOWER_HINT depends on fwk side changes
* Use INTERACTION hint to boost stuffs on interaction instead
Change-Id: I79603458fb525cdc1b6ac58cee31b84d63083f79
Signed-off-by: SamarV-121 <samarvispute121@pm.me>
Signed-off-by: dodyirawan85 <40514988+dodyirawan85@users.noreply.github.com>
The pinner now asks the runtime for these files.
Test: adb shell dumpsys pinner
Bug: 144773394
Change-Id: I8de2a2935901cbd3eaa50ce2d8aa09f61080ba02
Merged-In: Ie633ea788dab3389a3407ec9a461b5837befca46
Signed-off-by: dodyirawan85 <40514988+dodyirawan85@users.noreply.github.com>
This change replaces the '/system/lib64/libsurfaceflinger.so' pin, as
the file was removed in ag/12524602. The updated pin relies on
go/aog/1552085, as system_service needs read access to SurfaceFlinger.
Bug: 176197656
Test: adb shell dumpsys pinner (coral)
- shows that /system/bin/surfaceflinger is successfully pinned
adb logcat | grep PinnerService (coral)
- no longer shows a file-not-found error in PinnerService
Change-Id: Iae2a96c5fe4b1f5698d21de9970140321d11c460
Signed-off-by: dodyirawan85 <40514988+dodyirawan85@users.noreply.github.com>
The default camera app can be *huge* in some cases, e.g. when the app in
question is Google Camera. The system will only pin up to the first 80
MiB of the APK file, as well as the first 80 MiB of its odex. There are
several problems with this:
- We could easily end up with 160 MiB of camera app files pinned,
which is a tall order with the 8 GiB of usable RAM that we have
- The data that gets pinned may not even be the most critical data for
launching the camera
Let's disable pinning of the camera app to save RAM.
Change-Id: I745e39b6ff212dfaf9213517d2a2be8ff7384e24
Signed-off-by: dodyirawan85 <40514988+dodyirawan85@users.noreply.github.com>
The app is moving to /product
Test: m
Test: check if it can boot
Bug: 137908189
Change-Id: Ifd73ba03884543e33d61c74d933ad8171dd3b259
Signed-off-by: dodyirawan85 <40514988+dodyirawan85@users.noreply.github.com>
Support has landed in WebView, so time to turn it on in framework!
Change-Id: I064cf3512928637895932b3405adaec74b1ceed2
Signed-off-by: dodyirawan85 <40514988+dodyirawan85@users.noreply.github.com>
* so LTE+ icon will show whenever it's available
Change-Id: I45a569fa52d19f4b9af370d7a18c4198e29febc6
Signed-off-by: dodyirawan85 <40514988+dodyirawan85@users.noreply.github.com>
* Matches the hardcoded default value in stock
Change-Id: Iadb2a78fdb1fad971ee37e434dba616cfab172b9
Signed-off-by: dodyirawan85 <40514988+dodyirawan85@users.noreply.github.com>
* Main carrier config from MtkCarrierConfig asset default_v2.9.3.xml,
with vendor specific settings appended to the end.
[dodyirawan85 edits]: Originaly from xiaomi ruby adapted for our device, since i can't found anything on stock
Change-Id: I7bcb5f9714720e3b42b5b1e5dc13cfe4233ac874
Signed-off-by: bengris32 <bengris32@protonmail.ch>
Signed-off-by: dodyirawan85 <40514988+dodyirawan85@users.noreply.github.com>
* Import required system IMS blobs from XOS X6833B-H894DEFGHI-T-GL-231102V2897.
* Set the default IMS implementation to com.mediatek.ims via overlay.
* Force enable IMS features via overlay and sysprops.
* Add MediaTek framework jars to bootjars.
* Copy priv-app permissions for MediaTek IMS.
Change-Id: Ie258bff336586919a1127c3f7241e3ef9d689dd5
Signed-off-by: bengris32 <bengris32@protonmail.ch>
Signed-off-by: dodyirawan85 <40514988+dodyirawan85@users.noreply.github.com>
Fix phone asking for restart for adding new sim card on every boot.
Change-Id: I0163981c4713d81860f07c2b6feecfa71ae28598
Signed-off-by: Wink Saville <wink@google.com>
Signed-off-by: k2wl <kar2wlan@gmail.com>
Signed-off-by: dodyirawan85 <40514988+dodyirawan85@users.noreply.github.com>
X6883B supports switching between 60, 90 and 120 Hz refresh rates,
so let's expose it in Settings -> Display -> Peak refresh rate for users to save
battery if necessary.
Test: visual confirmation after toggling several times
Change-Id: Ia206c495e3f40f583f8cd35e7753c30a5e917656
Signed-off-by: dodyirawan85 <40514988+dodyirawan85@users.noreply.github.com>
The ndk_platform backend will soon be deprecated because the ndk backend
can serve the same purpose. This is to eliminate the confusion about
having two variants (ndk and ndk_platform) for the same ndk backend.
Bug: 161456198
Test: m
Merged-In: Id16039722fd70d4e2e934a0988f13a768ce833ec
Change-Id: Id16039722fd70d4e2e934a0988f13a768ce833ec
Signed-off-by: dodyirawan85 <40514988+dodyirawan85@users.noreply.github.com>
