This is a squash of:
Author: Minchan Kim <minchan@google.com>
Date: Mon Oct 14 14:22:45 2019 -0700
Enable zram writeback job scheduler
Bug: 140882488
Change-Id: I5489a7ce7a8d73306a6ecf69f57d338b2b0eaad2
Signed-off-by: Minchan Kim <minchan@google.com>
Author: Minchan Kim <minchan@google.com>
Date: Tue Nov 26 06:48:48 2019 -0800
fstab: correct zram parameter names
There was a report about warning during boot.
[libfs_mgr]Warning: unknown flag: zram_loopback_path=/data/per_boot/zram_swap
[libfs_mgr]Warning: unknown flag: zram_loopback_size=512M
We don't use zram_loopback_path any longer so remove it.
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
Change-Id: Iafb355999cd4995f34bf67259a8a39993ae8326a
Signed-off-by: Minchan Kim <minchan@google.com>
Signed-off-by: aswin7469 <aswinas@pixysos.com>
Signed-off-by: Sandeep-FED <sandymankara11@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: chandu078 <chandudyavanapelli03@gmail.com>
Signed-off-by: Manikantaraavi <raavimanikanta6595@gmail.com>
* When it is enabled, if we have multiple SIM cards, the networks
settings UX will only show the first SIM card.
* Thanks to Telegram@CyberPhantom52 for the fix patch.
Signed-off-by: TH779 <i@779.moe>
Change-Id: I2690e6dcd69f8e0fe814ea3c92c85d7c6f894166
libgf_ud_hal.so looks for vendor.boot.verifiedbootstate to be set to the phones true state
in our case, for an unlocked phone, it must be orange
(green = locked with factory rom, orange = unlocked no checking, yellow = locked with user key)
Change it to look for vendor.boot.fingerprintbstate which we set to orange without having to mess with anything safetynet related.
Co-authored-by: Matt Filetto <matt.filetto@gmail.com>
Added below two changes to enable the AAC frame control
when property persist.vendor.bt.a2dp.hal.implementation
has nbeen enabled.
- Send bitrate value to MM on basis of MTU and sample rate.
CRs-Fixed: 2402346
Change-Id: I6c964311dfa5db335d3b9dd21c60d1f9dcc61ebe
- A2dpSrc: Calculate bitrate with exact peer MTU value.
CRs-Fixed: 2466969
Change-Id: I95e93cb29d1add0b2bca8f99827849519311a0b1
CRs-Fixed: 2474400
Change-Id: I8eea975fac290c117d9781c1455e81e9404f6bd6
Signed-off-by: Omkar Chandorkar <gotenksIN@aosip.dev>
- Enable/Disable TWS plus feature support using persist
property - "persist.vendor.btstack.enable.twsplus"
- TWS plus feature is supported only if property is set to
"True" else feature is not supported.By default property
is set to False.
CRs-Fixed: 2344895
Change-Id: I855f448146424b7b647ca599f3d830073ec7c409
Signed-off-by: Omkar Chandorkar <gotenksIN@aosip.dev>
High power consumption issues were reported for some HS/CK/Speaker
in close range(1 meter) on hastings platform as they may not have
perfect RSSI golden range logic for power control and always request
SOC to increase TX power to max power level. Newer hastings SOC support
LPA power control to avoid unnecessary higher power consumption.
The change enable this soc feature according to value of property.
And disable it for special remote devices which have been added in BL
when new ACL link is created.
If feature is enabled, controllable power level for remote is L0-L9,
BT controller increase it to L10 or L11 according to RSSI and NAK rate.
Otherwise controllable power level for remote is from 0 to max power
level signified in NVM, most likely L11 for hastings.
CRs-Fixed: 2597191
Change-Id: I354bb34a84aa7a55537e3a595daac54c46d90603
Signed-off-by: Omkar Chandorkar <gotenksIN@aosip.dev>
