* We also changed zram_loopback_size with zram_backingdev_size so correct it.
Bug: 145116439
Test: confirmed there is no warning and zram backing device was configured
Signed-off-by: Minchan Kim <minchan@google.com>
Change-Id: I51be34c59203813a2f493eee6ab442c9940b75d7
The first default zram write back time is 3 hours which
is for go device to quickly save more ram. For Pixel
devices, we have more working set and could bring launch
time impact if we write back too fast. Thus, adjust the
first time write back time to 24 hours which is aligned
with periodic write back time.
Bug: 166739872
Test: boot
Signed-off-by: Martin Liu <liumartin@google.com>
Change-Id: I2388dd6d75ab0a938fe0edae0563fd26e48c9908
This removes the default mounting of debugfs, as
it is no longer allowed from android-S new-launch.
Change-Id: I78878e1c4177c07d66b13e5659d4360252c5f87b
This patch enables zram-writeback job. It will run idle marking
at 60m since the device is boot. After that, it will do first
writeback after 3hour to sweep initiallized cold pages out.
After that, it periodically write out every 24hour.
Bug: 117682284
Bug: 127185055
Test: confirm with manual testing
Signed-off-by: Randall Huang <huangrandall@google.com>
Change-Id: I6857c79ca3ce6a3619f4b7e200d7f17a8decd659
-Set max_comp_streams to num of cores since upstream also moves this to
percpu.
Bug: 38249616
Test: boot and run zram-perf showing better performance
Change-Id: I0b92b246d773db85aa03d033b2cecee54347cbd1
Our device has broken roles: they appear to be permanently set to
NONE and don't respond to configfs writes. This causes Android to
not see the USB port as connected, breaking the USB settings.
To repair USB preferences, we spoof roles in the following fashion:
- data role: DEVICE (if NONE)
- port mode: UFP (if NONE)
Implement a USB gadget HAL based on the default implementation from
AOSP and move key features from init.mt6768.usb.rc to it. Also remove
triggers for some proprietary USB features that aren't too useful on
custom ROMs and seem to exist mostly for engineering purposes.
Change-Id: Ie920fea8b3834d3bada2609df66ca68ddbb980b1
* E System : java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {com.mediatek.ims (/system/priv-app/ImsService): android.permission.UPDATE_DEVICE_STATS}
* ffb94e69c3
* This grants location permissions, however we're excluding these apps from
location indicators - they already have location permissions!
* https://cs.android.com/search?q=config_locationExtraPackageNames&sq=
* It isn't used for much else, so it's fine to re-use it for this
Test: No more ImsService in location indicators
Change-Id: If6c71769b87eb59deadaaa933e1c8449b949af26
We support IMS features on carriers not listed in the CarrierConfig, so let's use the props to enable it everywhere.
Change-Id: Id3ad71d522a22048f7ad86d89695ad262361632d
Configure the new MMTEL and RCS configurations in Telephony.
Also, configure the RcsService to be the default RCS service.
Bug: 111305845
Change-Id: I0d709b8248f1c40f0a5b50ec799396706eeadd65
* Also compile shim only for 32bit since the constructors symbol changes
between 32bit and 64bit and our IMS stack is 32bit only anyway.
Signed-off-by: bengris32 <bengris32@protonmail.ch>
added opPackageName as a parameter to the constructor
of AudioTrack which breaks our libsink which was compiled
for an older libaudioclient.
* fixes the following error:
CANNOT LINK EXECUTABLE "/system/bin/vtservice": cannot locate symbol "_ZN7android10AudioTrackC1E19audio_stream_type_tj14audio_format_tjj20audio_output_flags_tPFviPvS4_ES4_i15audio_session_tNS0_13transfer_typeEPK20audio_offload_info_tjiPK18audio_attributes_tbfi" referenced by "/system/lib/libsink.so"
https: //github.com/LineageOS/android_frameworks_av/commit/fd90fdfe2a611ae824a32e236da288b1fdfd445d
Change-Id: I290e1beca02d46c4393d17356fa22741d771f847
