Now that we are building our own vendor image, some necessary
packages aren't being built and some props aren't being set.
Change-Id: I3e91822b336761cdecf3f6ebe416276dc0585785
The GoogleParts app disables the EUICC app when there's no GMS, but it
doesn't happen quick enough. The crash dialog pops up a few times right
after initial boot up. There's no need to alarm the user, so hide it.
Change-Id: Ia06b336b30a8886bae522c6e8a76a1ca15da5edd
This is a squash of the following:
Author: Ethan Chen <intervigil@gmail.com>
Date: Sat Dec 1 13:53:00 2018 -0800
wahoo: Declare eUICC permission
Change-Id: I1b151021ca9fc6cf35141b2ccb337bc83197089e
Author: razorloves <razorloves@gmail.com>
Date: Fri Oct 18 00:06:22 2019 -0500
wahoo: Move eUICC permissions xml to /product
All eUICC items were moved to /product in Q.
Change-Id: I614f86b16f61959c47465863ab1d5d55030209ab
Change-Id: I323dce8b848b44e45ed21002950059e58719113c
Author: Rashed Abdel-Tawab <rashed@linux.com>
Date: Sat Sep 7 11:13:09 2019 -0700
wahoo: Build a disabled vbmeta image
Change-Id: Ie8f1e0929b037b35b5e45c2e31be9253fa0bb097
From: Nolen Johnson <johnsonnolen@gmail.com>
Date: Sun May 9 16:04:34 2021 -0400
wahoo: Simplify AVB flag logic
* AVB's `--flags 3` argument builds a disabled VBMeta with
disabled hashtree, so no need to set both flags individually.
Change-Id: Ibe9ee322a5af58f13e76d53e18dee49451fe8838
Change-Id: Ie7f19e42835f8f1d2fa5be22e1beeb7228ad55a3
Introduce the productpartition to wahoo series devices, however only define the common product partition in this tree.
Later details, such as the inclusion of system_ext partitions for taimen, is included in per-device trees.
Product partition is defined at 3.0GiB with later requirements of Android 13, causing an increase from the previous values.
Lineage build servers export OVERRIDE_TARGET_FLATTEN_APEX=true,
causing the system image inode count to be insufficient.
Change-Id: I171afeb3fcf85199215c54fe068cf04547999285
This addresses an underlying problem since /dev/hw_random is used. The
issue is that EntropyMixer, which runs in system_server, needs to read
from /dev/hw_random, but thanks to our qualcomm ueventd, EntropyMixer
can never accress this node, resulting in warnings like this:
W EntropyMixer: Failed to add HW RNG output to entropy pool
W EntropyMixer: java.io.FileNotFoundException: /dev/hw_random (Permission denied)
AOSP ueventd handles this well, so just remove this line to get things
back to stage. This issue was never exposed because Google derps the
logging here, which is already fixed on Pie.
c78a463e87
Change-Id: I42c9aaa8f57306536e51c0a17febad57a5a77581
Downloaded the apk from play store and used the following command
to extract the proper public key from the apk:
openssl pkcs7 -inform DER -in CERT.RSA -out CERT.pem -print_certs
Change-Id: I32da280607e931b50822fd1ae08b45af455a9885
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
Sometimes, being able to disable the camera laser sensor quickly is
useful for taking pictures of reflective objects without a purple dot
showing up in the picture, especially when precise upfront focus isn't
required. Enable the existing toggle in developer options to expose this
functionality.
Older versions of the stock ROM included this option, but it's been
removed since then.
Change-Id: I24fcde77536fffcdafda749bd02157c510ac9aa1
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
This is preventing eng builds from being adb insecure.
It's also conditionally handled in vendor repo.
Change-Id: Idc77c39a5e2311ea1fcb273c6140afe655c574c9
This is so all the required libraries in hardware/google/pixel get
matching libs in vendor in build
Change-Id: Ib7e1f5c2204b5ad75fa0c88d35b6a77e10998142
