For now this is implicitly built by lineage specific
libprotobuf-cpp-lite-3.9.1-vendorcompat lib, but in the future this
might not be the case.
Change-Id: I724e933e046cbf631c078321d55550b96ca998da
With libwifi-hal-qcom migrated to Android.bp with soong namespace
the namespace should be added to PRODUCT_SOONG_NAMESPACES as well.
Bug: 273376293
Test: m droid
Change-Id: I041a57bc6873903895a0b8783eb13106ea224886
update thermal HAL makefile path to the new common folder.
Bug: 289146743
Test: presubmit
Change-Id: I4c2b93d37d12de8e0ac01deb9ad21b34e0a2da5c
Signed-off-by: Ram Chandrasekar <rchandrasekar@google.com>
Qcom has issues that prevent it from working with a hermetic
partition build.
Bug: 205632228
Test: Presubmits
Change-Id: I490a29da38a6f68e7dd3650d8140cb11adaa8c7a
Some legacy devices such as mata and cheryl lack an IWlan stack. These
devices can set this overlay to true in order not to incorrectly display
a permanent exclamation mark over the mobile network signal icon.
Change-Id: Ife02d90706990bf28c156c9850ef0773802bc5b0
This is enabled by default on U, and it causes apps like
Chrome and YouTube to render the frame rate at 30FPS when
playing some videos.
Change-Id: I649bf03d550c2b9726c7957d15ed09e455d874ec
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
* The following HALs in device manifest are not declared in FCM <= level 4:
vendor.dolby.hardware.dms.IDms/default(@2)
INCOMPATIBLE
Signed-off-by: Asriadi Rahim <asriadirahim03@gmail.com>
The Pixel CarrierSettings app also provides APNs in addition to carrierconfigs, so let's use them for better carrier support.
Change-Id: If07e08b32857e14db2c8fd1b1bf4966721c66e6b
For whatever reason, after the U QPR1 merge, surfaceflinger is no longer
able to find an OpenGL implementation without this hint.
Change-Id: I59610ce628acb41807bb75b01a8c6cac7d08f740
This package provides comprehensive support for the Active Edge squeeze
gesture supported on this device.
Change-Id: I2158c22e727e293e3f02b9ddf614a943848ad587
* Stop handling vendor mounting from kernel, first stage init is gonna
do that, together with system (which is now /system)
* Use correct mount flags coming from kernel dts
* Move system and vendor mount points to /dev/block/by-name/, we don't
have bootdevice symlink to that point in init
* Copy fstab to recovery for first stage init
Change-Id: Iaa0ecc3f13c3cfd3fe357ca509549d0f68a29cf0
* With the new WiFi AIDL HAL, the framework thinks the device
supports interface combination for some unknown reason,
even though the service doesn't advertise it. As a result,
the WiFi service fails on configureChip method.
Change-Id: I0c3fa7b4c947c3525c30f7cef0b2674bee224da7
This reverts commit 83759b7709.
* Our Adreno driver is support EGL_KHR_partial_update,
beginning of the https://android-review.googlesource.com/c/platform/frameworks/base/+/320411,
the EGL_EXT_buffer_age extension was forcibly enabled
* If disable EGL_EXT_buffer_age extension support, the following OpenGL memory leak will occur:
* W OpenGLRenderer: dequeueBuffer failed, error = -110; switching to fallback
Change-Id: Ie511aa32922cb53a1d70160fe6f0a2dd80cf413c | AOSP
This commit adds the IPSEC_TUNNELS feature flag, with XFRM Interfaces
used as the implementation of choice.
Bug: 117183273
Bug: 137629222
Test: Compiles, passes tunnel-mode CTS tests
Test: adb shell pm list features
Change-Id: I19c598947525783850b29d149db85db89f8b347e
Fails to be set from vendor otherwise:
init: Do not have permissions to set 'ro.telephony.block_binder_thread_on_incoming_calls' to 'false' in property file '/vendor/build.prop': SELinux permission check failed
Change-Id: I3c3ea61af240557f3b1053497c3ed1403f7ae318
As of I3c7aed1bdb45db728d319f7d757400e44d232283 the Bluetooth stack
defaults to reasonable defaults that should work for all devices.
Change-Id: I056d63c4c8a2727e384172e964dc0000b6773504
ag/16564596 will change default value to false.
Configure correct overlay configuration.
Bug: 212488775
Test: manual test & build
Change-Id: Iaf1a0a23dae69fde5995e591a757a8ef5374d5b5
System properties set with the "=" operator cannot be overriden. This
device is used elsewhere in the system and some of the properties need
to be overridden. The "?=" operator will use the assigned value if no
other values are assigned elsewhere, allowing for overrides.
Bug: 230638462
Test: adb shell getprop | grep bluetooth
Change-Id: Id6cd7901555edafef141bbc1bbd5e06dc3a54d0c
The class of device is a string with a list of uint8t values:
90,2,12
The meaning is as follows:
{Service Field, Major class, Minor class}
Service Field: 0x5A -> 90
Bit 17: Networking
Bit 19: Capturing
Bit 20: Object Transfer
Bit 22: Telephony
MAJOR_CLASS: 0x02 -> 2 (Phone)
MINOR_CLASS: 0x0C -> 12 (Smart Phone)
Bug: 217452259
Test: make -j; -- check that bluetooth.device.class_of_device is
correct
Change-Id: I24fd57bacbf6786a26f7079e7a6e9857dbe170d1
bluetooth.audio@2.1 adds new functionalities required for Bluetooth LE
Audio development
Bug: 150670922
Change-Id: Iac2ece0c029a38fef82e81f5ba3ba491163818ef
Prevents the following warnings:
build/make/core/Makefile:61: warning: overriding commands for
target `out/target/product/walleye/vendor/etc/IPACM_cfg.xml'
build/make/core/base_rules.mk:525: warning: ignoring old commands for
target `out/target/product/walleye/vendor/etc/IPACM_cfg.xml'
Change-Id: I07ba0b5d9f8776a4a539cdd5fa928562aeffcfc1
Google's prebuilt cgroups.json and task_profiles.json for products
launched with previous API levels only covers
ro.product.first_api_level >= 28. [1]
Pixel 2 / Pixel 2 XL were launched with Oreo (API level 26),
so schedtune and task groups are completely broken. Since the
system also checks /vendor/etc for vendor profiles, make a copy
of cgroups_28.json and task_profiles_28.json and ship them to
/vendor/etc. Profiles for previous API levels are all the same
anyway.
Test: boot and check /dev/stune/
[1] system/core/libprocessgroup/profiles/
Signed-off-by: Chenyang Zhong <zhongcy95@gmail.com>
Change-Id: I33c0540ef50054fad839886f9f014cc275659e77
Populates a new feature flag to record the level of OpenGL ES dEQP
test support. Updates the analogous Vulkan dEQP feature flag to the
value for the next dessert release.
Bug: 159841535
Change-Id: I9ed8ec8af0c76962cfd77a91d806cad95de70c28
-. RECEIVE_SMS and READ_PHONE_NUMBERS permissions are no longer used.
-. Add the ACCESS_FINE_LOCATION permission for iOS WiFi D2D which was approved in b/188150877.
Bug: 188150877
Fix: 162937804
Test: Manual tested on Barbet.
Change-Id: I8a61258fb907bb7e1423a43536615951fb49cc5a
Merged-In: I8a61258fb907bb7e1423a43536615951fb49cc5a
android.software.verified_boot.xml should be copied to TARGET_COPY_OUT_VENDOR instead of system
Bug: 190401885
Test: run cts-on-gsi -m CtsSecurityTestCases -t android.security.cts.VerifiedBootTest#testVerifiedBootSupport
Change-Id: Ifc7818b1cef1284653d377b7bbc11bf4aaa44da0
As resources were moved from the android package to the connectivity
resources package, migrate resources to a new overlay for the new
package.
(clean cherry-pick from downstream branch)
Bug: 185850634
Test: m
Merged-In: I2789e88adbfb912f18017bae3d37696057a4afa5
Change-Id: I86f3ea2b486aa4a47c5a5c123571d9276a4d3095
* `ro.control_privapp_permissions=enforce` - Default in LineageOS
environments.
* `keyguard.no_require_sim=true` - Set in build/ in LineageOS
environments.
Change-Id: I5a17e8bca9c896984f3ceca90c8ca9479540072c
* In Android 12, android.hardware.radio.deprecated was removed due to [1]
So we don’t need to build this blobs and remove it from the manifest.
* Note: QTI do not pick this commit
* ref:
[1] 899ef068c6
Change-Id: Ie00e6090469b5393ac52fd4112b4bd7025815544
* We build this, so lets just use to sepolicy designed for it.
* hardware/google/pixel-sepolicy/citadel declares types that
are used in this, so lets include it too.
Change-Id: If8e8632e724693f19fa721c1c19358c6f9e282d8
* Looking at thermal-engine's needs, without this it is spammy
during sleep, and the denial isn't seen on R, so lets allow it
to maintain the old behavior.
Change-Id: Ie0a66addeb32d34fcfb7b90e146504477ea94c1f
* Looking in `git log`, we can see that this isn't needed
functionallity, and that all attempts to "read" it in any
way can be safely ignored.
Change-Id: I1dd6c57f9cec024371cec8f9074b000531514ba9
The pinner now asks the runtime for these files.
Test: adb shell dumpsys pinner
Bug: 144773394
Change-Id: Ifead4354d29b3ce658b2f5771b778a050b0579b5
Merged-In: I6627afc390f8dcacc197680dcc4917e2ac5bc090
This change replaces the '/system/lib64/libsurfaceflinger.so' pin, as
the file was removed in ag/12524602. The updated pin relies on
go/aog/1552085, as system_service needs read access to SurfaceFlinger.
Bug: 176197656
Test: adb shell dumpsys pinner (coral)
- shows that /system/bin/surfaceflinger is successfully pinned
adb logcat | grep PinnerService (coral)
- no longer shows a file-not-found error in PinnerService
Change-Id: Iae2a96c5fe4b1f5698d21de9970140321d11c460
Compressed APEX has been introduced in Android 12, and they are enabled
by default inheriting updatable_apex.mk.
Unfortunately, when the device is encrypted, they are causing bootloops
on msm8998.
As the only advantage is some space gain on disk, we can
simply disable them: keep the variable immediately after including the
updatable_apex.mk to avoid being overwritten.
Signed-off-by: Roberto Sartori <roberto.sartori.android@gmail.com>
Change-Id: If46fa28e4bc59af80de441d1fca6c3f13f395168
These overlay values are just the default AOSP ones at the moment. We'll
change them on the system side instead.
Change-Id: I2898dec7c3c39eac604cb7f90224760869f65bbc
qcril will block any further MT SMS if previous one is not ACKed.
For this bug, IMS service is not ready and resulted in qcril stuck in blocking state.
This solution will add 30s timer to reset blocking state if there is no ACK from Telephony.
Bug: 169549852
Test: MT SMS during power off
Change-Id: I6f52170654925143aeb55f8bc0cf4c379717e718
The CarrierSettings app enables/disables carrier apps based on sim
inserted, so use it instead of CarrierConfig.
Change-Id: I163dd615e9d8268c5f94a28ae234a30f74c7e83b
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 wfcactivation sepolicy pem file has the wrong public key, causing
the mac_permissions.xml to have the wrong signature for the
wfcactivation app. That further causes a signature verification fail
during boot, which prevents the wfcactivation app from being labeled
with the proper domain of wfc_activation_app.
Used the following command to extract the proper public key from the
wfcactivation apk:
openssl pkcs7 -inform DER -in CERT.RSA -out CERT.pem -print_certs
This fixes selinux denial errors, like the following, that caused wifi
calling to fail on some carriers:
avc: denied { find } for service=qchook pid=3473
uid=10112 scontext=u:r:priv_app:s0:c512,c768
tcontext=u:object_r:qchook_service:s0 tclass=service_manager
Change-Id: I9ba03a5d27a2d6947355a9e1c076e2728ec1d50b
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
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
