Set "persist.vendor.radio.procedure_bytes" property value
to SKIP for testIccTransmitApduLogicalChannel to pass
Change-Id: I117dd9ec6976d35e23ce10158e1ef4706e17104f
CRs-Fixed: 2491738
Drop framework_manifest.xml part as the hal is already parsed.
Don't bring in the c2 xml files as CAF squashed the c2
support in the already existing media codecs.
Change-Id: Ibe051f4b19c2dbb0a208e751a3b7a332a329b447
Signed-off-by: celtare21 <celtare21@gmail.com>
Choreographer VSync has some performance impact for CPU rendered apps
as the app has to wait for VSync to start a new frame draw. When the
frame draw time exceeds one VSync, this has a direct impact on the FPS.
"debug.cpurend.vsync" property controls the VSync for CPU rendered apps.
Disable VSync for CPU rendered app, by setting this property to false.
Signed-off-by: adi8900 <adrianszymanski242@gmail.com>
For some reason volte wasnt working on carriers even with
updated carrierconfig overlays so add it for now
Signed-off-by: PainKiller3 <ninadpatil100@gmail.com>
Sometimes SW_VSNC of DispSync comes 1ms earlier than signal_retire_fence(or HW_VSYNC)
It means VSYNC-sf only 5ms behind signal_retire_fence.
And VSYNC-sf will be 5.5ms earlier when applying early_sf_phase.
(the phase-sf changes from 6ms to 0.5ms)
Therefore, VSYNC-sf comes 0.5ms earlier than signal_retire_fence when
applying early_sf_phase for transaction and cause frame missed.
Add more 1ms to early_sf_phase then it will come 0.5 later than signal_retire_fence
in this case.
Bug: 118606025
Test: Open/close apps, observe no jank
Test: -Launch app, stay the same picture on screen at least 30s
-Tap home key, observe no jank when doing app animation
Change-Id: I2da26e844cfc3dc86d7617e44906230ded760d7c
Signed-off-by: PainKiller3 <ninadpatil100@gmail.com>
* Fixes the bug in dual SIM device where preferred data selection didn't stick after reboot
Co-authored-by: federicobenedetti <fede.benedetti9@gmail.com>
* Given the fact that the bootloader allows bootable images with
arbitrary signatures to boot, one can relock the bootloader after
installing a signed custom recovery. After that, custom ROMs can be
installed from recovery as usual, as long as the boot.img's are
signed.
* This is NOT a security vulnerability because unlocked bootloader is
still prerequisite to access fastboot boot/flash, in contrast it's a
feature suggested by Google.
* To make it feasible with Lineage, sign the img with AOSP verity key
which is publicly available.
* OnePlus happens to use the same key to sign their own images and
bootloader, so as a bonus there's even no 5s warning indicating a
custom boot.img is in use on boot.
* This doesn't mean using custom ROMs with locked bootloader is
suggested.
Change-Id: I178e9588e1dde96400dcb2178a027597d05949bd
* Sadly, out-of-the-box Miracast support was killed in P, so
we need this to keep Wi-Fi display feature working.
Change-Id: Id680d918b64c0e3733251db45992ec477b6fbdfb
