This device is fully capable of streaming audio to Bluetooth hearing
aids using the ASHA GATT protocol built on top of L2CAP, similar to
A2DP.
Enable the config option for the system to handle pairs of hearing aids
properly and expose the option in Settings.
More info at https://source.android.com/devices/bluetooth/asha
Test: user reported successful audio streaming
Change-Id: Ice82c48ce80626eb8beb5c51681072e213b73c39
The framework was changed in Android R to require explicit authenticator registration.
This change allows apps to continue to use the fingerprint sensor.
Bug: 147445115
Test: Builds
Change-Id: Id3385edc784b2053c8b54ec3153728f4e6e22a45
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 ~3.5 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 precious RAM on this
device.
Change-Id: I745e39b6ff212dfaf9213517d2a2be8ff7384e24
wahoo does not use separate interface for a group, it will share main
p2p0 interface.
Bug: 141382930
Test: run P2P with whaoo as GO
Change-Id: I061ed0ac66f8ae75c84d7683f66d4baffd3a3112
Remove the old config_ims_package device config and configure the
new MMTEL and RCS configurations in Telephony instead. Also,
configure the RcsService to be the default RCS service.
Bug: 111305845
Test: make checkbuild
Change-Id: I0d709b8248f1c40f0a5b50ec799396706eeadd65
These are replaced by formal mainline module overlays.
Bug: 143464763
Test: Send for Wifi regression tests
Change-Id: I45881ed210132252b9c5c7d6be03ed845e33f971
Accessibility transforms require a specific color mode that is not
always available for the user to select.
Bug: 130376719
Test: atest com.google.android.config.pts
Change-Id: I0724a55a2d10a9447fa667545f3101e441779dc2
Enable link probing feature on wahoo devices.
Bug: 112029045
Test: Manually tested that link probing works on taimen
Change-Id: I66a5fcb3b9e4645521f1fa258eb74f563cc816a8
Another overlay overwrites this config value so this was never used.
Bug: 122261360
Test: atest vendor/google_testing/pts/tests/config/src/com/google/android/config/pts/ConfigTestCase.java
Change-Id: I5c2773885a0f214c483e3bf5b88d15a63804ff6c
Some Pixel devices had a wrong brand value provisioned into keymaster.
Due to this misprovisioning those devices fail device ID attestation because it includes a check for the correct brand value.
This is now solved by re-trying Device ID attestation if we are running on a potentially misprovisioned device, allowing for the known incorrect brand value.
Bug: 69471841
Test: atest com.android.cts.devicepolicy.MixedDeviceOwnerTest#testKeyManagement
Change-Id: I41b51a355e1b582fd7c7f12f8b7e0992294b16e3
Merged-In: I73dd4501416bcc2587d137d8b1e27127e3bfc0c0
(cherry picked from commit 0e5b3f1396)
Some Pixel devices had a wrong brand value provisioned into keymaster.
Due to this misprovisioning those devices fail device ID attestation because it includes a check for the correct brand value.
This is now solved by re-trying Device ID attestation if we are running on a potentially misprovisioned device, allowing for the known incorrect brand value.
Bug: 69471841
Test: atest com.android.cts.devicepolicy.MixedDeviceOwnerTest#testKeyManagement
Change-Id: I73dd4501416bcc2587d137d8b1e27127e3bfc0c0
This is set in the nexus_overlay and no differences existed until
GMSCore was added to the nexus_overlay. GMSCore only exists in the Wahoo
overlay and the overlay currently crushes our config which applies to
all Google devices. By re-adding it to this overlaid overlay, we gain
our powers back.
Bug: 72663665
Test: Manual
Change-Id: I9794a212b782028f12cd87793ab5723030b8ed95
This is necessary because the driving DnD rules will be migrated from
Pixel Ambient Services to GmsCore. Pre-granting this permission is
necessary to avoid a feature regression when compared to Pixel 2.
Bug: 74115747
Test: Manually confirmed config change in Pixel 2 build
Change-Id: Icb595b6a31787c18eef38da50f5a256ada5c05f2
(cherry picked from commit e30688631f)
The files in arm/arm64 are symlinks and pinning symlinks is not
supported. Pin the target vdex file intead.
Bug: 73990433
Test: manual
Change-Id: I1edadcc3be6d88cc07c599cba024babc5abe0633
Moving config_displayBlanksAfterDoze into device folder instead
of device family because walleye supports seamless transitions
but taimen doesn't.
Change-Id: I4710388122852dc68bff9c2cb96633ffade9be4e
Fixes: 71897888
Test: flash walleye, taimen and salfish
2017 devices use single SKU so there is no default country code.
In case of cellular loss, we shouldn't revert country code so user
can keep using the last known country code to access APs.
Bug: 65602314
Test: compile, manually test that framework get this change
Change-Id: I2a8bf967c980cdecafc9cdf03be51fe0d1f6fa8f
This reverts commit "Enable haptic text handle on muskie/walleye/taimen" [1]
We decided to not enable this on O MR1.
[1]: I5ec238870329b1a234df955d9dd1541a9ae26d82
d30e0d7350
Test: Manually made sure that haptic feedback is no longer triggered
when moving text handle on Walleye.
Bug: 62454887
Fixes: 65291208
Change-Id: I82121f3907215e31750a10344e795ad1e60dbaad
If ramp rates aren't even multiple of 60 then we're more likely to get
brightness changes that differ each frame, which can show up as a
stuttering in the animation.
Bug: 64514692
Test: made change, took systrace, saw smooth ramping
Change-Id: I48ec832f752a8aefb6185c1583141f2fb1a29e85
Introduce a separate RSSI threshold for entry so there is some
hysteresis between entry and exit.
Bug: 64422319
Test: Unit tests
Change-Id: I0cf0b6e34baa3827dcaeefbb009fa04b071dd28b
