* Google has provisioned this on the Pixel 5 (RQ1A.201205.010) to
utilize the 8 GB of RAM better, and I have also observed that a
lightweight selection of apps was hitting the cached app limit before
exhausting RAM on another device with 8 GB of RAM
* This shouldn't cause adverse effects on devices with less RAM (e.g. 4
GB) as the low memory killer should kick in long before this limit on
such devices
Signed-off-by: pix106 <sbordenave@gmail.com>
* Background ART heap compaction for cached apps has been recommended
for Android Go devices for a while, and Google has enabled it for the
Pixel 5 on RQ1A.201205.010. This feature should help fit more cached
apps in memory
Signed-off-by: pix106 <sbordenave@gmail.com>
Runtime Resource Overlays (RROs) can no longer change the value of
resources in manifest when read during PackagerParser.
This change uses component-override to enable the service by default.
Remove usages of profile_supported_* from overlays as they no
longer configure the enable state of Bluetooth components.
Bug: 135048762
Test: adb shell pm query-services \
com.android.bluetooth/.avrcpcontroller.AvrcpControllerService
adb shell pm query-services \
com.android.bluetooth/.hid.HidDeviceService
adb shell pm query-services \
com.android.bluetooth/.sap.SapService
Change-Id: I284d254a921b14d1533745611a083f4b5a27d9dc
- add a new config and set as true for mcc/mnc
which support call composer calls
- allow implicit broadcast of new intent, which
contains call composer information
Change-Id: I5d042f88d57d54f3b7a944d9a2f49061cd0313d3
CRs-Fixed: 2672216
* Removed non-existing overlays
* Removed overlays with the same value as the system
Note: profile_supported_ba has to be added again once the quartz
bluetooth branch works
Change-Id: I13a42fed84d2146171e0927c225997e3961a9f0b
* Our HAL doesn't really support bokeh mode, but enabling this
makes our auxiliary camera available in Snap again.
* Also update copyrights, as this was never an AOSP overlay,
and that copyright was a typo.
Change-Id: I296d42e5e371711b7acb81cb3235ea572a2ded56
* Airtel India uses some mncs of 404 mcc
Signed-off-by: Zainudin Shamilov <izainudinshamilov@beatwo.men>
Change-Id: Iecefcefa628acc7aee7c8e6022a7c26a7765b245
* All of them support VoLTE/VoWiFi/ViLTE
Signed-off-by: Zainudin Shamilov <izainudinshamilov@beatwo.men>
Change-Id: I8f52933358a8c32c53f938f3e5866362c8123be0
* Remove Double Definition
* Reordeder Alphabetic
* Move Audio and Media Files to Configs
* Move Wifi Configuration to Configs
* Cleanup Overlay and Reorder
* Move Privapp Permission to new Folder
* Reorder Properties and rename mk
* Move Xiaomi Doze to new Folder
Add carrier config allow_holding_video_call and
allow_add_call_during_video_call as false to hide
hold/add button for video call
Change-Id: I7fd961520dfdc3b819ed3410de83b3d5cddafd16
CRs-Fixed: 2564151
- Add a config flag to determine whether to
show one way VT options when accepting an
incoming VT call
Change-Id: Ie545bc3b0ea4579404ba3c86623ab8de00c856fd
CRs-Fixed: 2534325
New Q blobs triggering a annoying notification while using volte . Hide ims notification for JIO India (mainly) by their MCC/MNC as its ain't showing for airtel volte so this bool should work .
test
