Makefile contain the following sysprops
bluetooth.profile.bap.unicast.server.enabled
bluetooth.profile.tbs.server.enabled
bluetooth.profile.vc.server.enabled
However, CS indicates the above sysprops aren't defined anywhere
nor read anywhere? Given how the following LE Audio sysprops are
missing from the makefile, and the similarities in naming, we
suspect there was a typo?
bluetooth.profile.bap.unicast.client.enabled
bluetooth.profile.ccp.server.enabled
bluetooth.profile.vcp.controller.enabled
Bug: 372711861
Test: builds
Flag: EXEMPT bugfix
Change-Id: I3b1be96531ffa6639647e0240dfc0f07ad1843a3
Set InputDispatche and InputReader prefer idle explicitly, which is a
workaround and should be removed after they become ADPF.
Bug: 366146314
Flag: NONE init rc file change does not support flags
Test: tasks set as expected
Change-Id: I38afa16f8f85e6aea31ddd5367c2e2d4a3249ced
This patch prevents a Null Pointer Exception in
queryMoistureDetectionStatus() when getPortStatusHelper() fails to open
the /sys/class/typec file. The failure results in an empty
currentPortStatus vector, causing the NPE when accessing its first
element.
Bug: 361097811
Flag: EXEMPT bugfix
Test: NPE does not occur when getPortStatusHelper() fails
Change-Id: I2cbe70d3b00cb2cf8c28a28d91a18fbf7c326ea7
Signed-off-by: Kuen-Han Tsai <khtsai@google.com>
This feature is provided by the ConnectivityThermalPowerManager app that
we extract as a proprietary blob, so we can expose it.
Change-Id: I407e9e2235531fbca0b2c0e48b68105b1e77ad1f
The CarrierSettings app enables/disables carrier apps based on sim
inserted, so use it instead of CarrierConfig.
Change-Id: I163dd615e9d8268c5f94a28ae234a30f74c7e83b
Commit 49895bb361e74ffe92a3c0b76f988c8e4697b5c1 in device/google/gs101
failed to remove these overlays. Since this tree was created from
device/google/gs101, this results in the following issue on pantah:
* Pull down status bar
* Try to adjust brightness, network settings open instead
This is caused by the 171px offset that causes the status bar
to overlap the brightness slider.
Test: Reliably adjust brightness, confirm with "Show layout bounds"
from developer settings.
Change-Id: I1b97a28c257cb5b0faba830f29e9058d2dbe50fa
All production zuma devices have CS40L2x haptic driver ICs that support
multiple intensities, so expose the Off/Low/Medium/High vibration
strength options like stock.
Co-authored-by: Michael Bestas <mkbestas@gmail.com>
Change-Id: I72645b5bd5772e182592a630df86f9b6166b4923
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 6 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
* Use vendor.google.wifi_ext@1.0-service
that is in the vendor partition instead
of the AOSP WiFi service.
Change-Id: Ia0fff6ffc532cc6b5e41f8ac242d00e64627cee8
