Age | Commit message (Collapse) | Author |
|
Change-Id: I4d04f8495fe86c994f48ebeed6149b85314e5514
|
|
Without a check, when performing a vendor blob regen it'll add another
dependency on top of any existing one
Change-Id: I9c7f17082fd850235c794d44cec3cda0c4b883ef
|
|
Change-Id: I7ebde1c32e2a64c867b7ae26c3aa254432386df2
|
|
Change-Id: Iffd8855f0971997792cb9b0d6db818772c339e24
|
|
* Before loading the HAL, make sure the device exists
Change-Id: Ice2a1322ef8d7a3a7d7371a3bdd86547dec20bf1
|
|
Change-Id: I20146c0bc065a460f5a86455ed9a21abce5f9417
|
|
Change-Id: I56bd82e77cbde3efc9b038ed2bc3857d119bf090
|
|
Change-Id: Ib704750a56eec2e26440bdfee92976776db58812
|
|
Change-Id: I7a278b5b9618d3235162a07516dff11ee94e378a
|
|
Change-Id: I40e31540144053513e6ed82f51aa5f2655eb710a
|
|
Change-Id: I686c4356d0bc3d732a8266f6d3c610356e51512b
|
|
* From https://github.com/LineageOS/android_hardware_interfaces/commit/1ee53cfa566471153661b2715ade8a9a5d525776
Change-Id: I7116f4becb57e684396ef1e6608f9c760ab82459
|
|
Change-Id: Ic46de254772fb2c3d57566ac0c60a7f5a7f55ab9
|
|
* It was only useful to jason, which needs a copy of libpowermanager in vendor
Change-Id: I754c666730d841fd71837358fe87a5ce1a3d7921
|
|
Change-Id: Ibe89b7a99929cd8e52424be502094997194a476f
|
|
Change-Id: I35b40e6debe407390300750aab41741fa038e1f9
|
|
* As recommended by Google for multiple different versions of the same HAL in VINTF manifests
* https://android.googlesource.com/platform/hardware/interfaces/+/master/drm/1.1/README.md#devices-launching-with-android-pie
Change-Id: I4922d72ab60ca1aae78c010aeb610f9bca9012cb
|
|
* make vendor_manifest.xml
Change-Id: Ida66af588dc2d66c6cc6f62b573f05e7dd8ba600
|
|
Change-Id: Ic38ffa02b2e1dca5c842c738f4f1bcc978f8b5bd
|
|
Co-authored-by: Marc Bourgoin <themard85@gmail.com>
Change-Id: I49d46c4eb27ccef6e2ae678e8eccc10c2e5257aa
|
|
* Current profile URL points to a 404 page
Change-Id: I92f3ded52dda04f6cec5709d51c84b32f39d8095
|
|
* Make the lib vendor_available and remove it from vndk-ext
Change-Id: I3945a460d563aaf07aaa7b757bb9c0dddc4f91cd
|
|
* Nothing uses it and it isn't even in manifest
Change-Id: I7e991b1c851b80a1590df20943cf8a964e03ab28
|
|
* They're built automatically since newer revision needs them
Change-Id: I695bb8d7c4120add9c8583658de5ae73f508a25c
|
|
* Defaults to true if full VNDK is enabled
Change-Id: I2d59cbae13eb3712fd13ab09eea582c8d5768e8f
|
|
Change-Id: I66b834b2df9f652ef3173815270d7aa0a85a9e14
|
|
* Deprecated
Change-Id: I1b3638b07ed45f6f72b551d1d241d48f661310c6
|
|
* Dead since Q, where XML audio policies weren't enforced yet
Change-Id: I302a0ed97964b052176dc3bb0141db1ba85e78c8
|
|
Change-Id: I69a14e00cfc3291175351259f2d8cbd6b0dc827a
|
|
From LA.UM.9.2.r1-03000-SDMxx0.0
* Otherwise zram remained disabled
- Increase ZRAM swap size.
- post_boot: Ensure SLAB_STORE_USER is disabled for zram kmem_caches
- post_boot: Set zRam disk size to 50% of RAM size.
- Set zRam disk size to 50% of RAM size for non-Go devices.
- post_boot: update zram setting avoid 32 bit overflow
- post_boot: use 'MB' as deault unit for zram disksize setting
- post_boot: updating post_boot for <=2 GB devices
Change-Id: I73ec74c4a10f2d0c65506d73f43fe64a20ed2cc5
|
|
Change-Id: I226a80e945c73d8dfa7b61e538162d612329a6df
|
|
Change-Id: Ie613a3dac3629dc11aaf89f44e5277bcf483e814
|
|
All devices use pre-R audio.bluetooth_qti.default.so and platina uses
pre-R audio hal, in which the new set_event_callback API is not
implemented and the audio service will crash due to mismatched struct.
This reverts commit 939fd6b3019828b56469d7b75f237bf176bfe57f.
Change-Id: Ia330ac05d84d3dfb3a639458d66a3dc29689e67c
|
|
Change-Id: Ic8caabd4a5cf458dfc2c91971247168de28a27ce
|
|
The hal class is essentially triggered from the boot class, so it's
possible that the HAL starts before the permissions are set, and manual
intervention was added to deal with the issue. However, we can simply
move chown to an earlier stage to avoid playing with the workflow.
Change-Id: I189b247576151f76efaf26b2d266564dc7768fba
|
|
This reverts commit d08d3a25d6a8a81dc59fb2d6d9503fe525b1d0af.
Change-Id: I8e2ce16722b0e9727f6962530d4fcaba91606d7f
|
|
* It's already present in device/qcom/sepolicy-legacy-um
* Fixes build after latest tag merge due to
freq_prop -> vendor_freq_prop rename
Change-Id: I54c7d76260041b7c383428449e149aa35d51c08f
|
|
* qcom_ims_prop -> vendor_qcom_ims_prop
* Fixes build after device/qcom/sepolicy-legacy-um update
Change-Id: I8d1b736deaaf54ce012cf3e42a4c927d43326631
|
|
* platina doesn't have IR
Change-Id: If5d83ef3dc0169700fcd738f6a50cb38b104c30a
|
|
Change-Id: I172349433946883aa1035e91ab3ab703a96e7912
|
|
Change-Id: Id99f001f11c5f26e1d8c5827acc13a218fe16793
|
|
Change-Id: I63b18d20003ed9543801f5946c6a26140d1f3eef
|
|
For some reason, any prebuilt ones from pre-R ROMs no longer work on R
and cause the following error:
E ANDR-PERF: Unable to link to gPerfHal death notifications!
Change-Id: I1dc96e4a51c4c81dd847c59a58ec670d89054f64
|
|
Change-Id: I86b85da4a0f859274081d35fb349ea3e0f734740
|
|
Change-Id: Ic2299cb1ebb2a19d91ad48a1075df72d726756ab
|
|
Change-Id: Icd7f381c574ea36eb4d797cefd60ba9f1a0941bd
|
|
* They are used by xtwifi-inet-agent which disabled.
Change-Id: I4fbf6e02276b508a27f320e630ddad3c9aada5a8
|
|
Change-Id: If1dfd39ab820cdf5e7ac5caf05dc8fea1cd95235
|
|
Change-Id: I0acef3da2c3567a28edd0a71dac89a5828f7725d
|
|
* Don't show the broken setting until we have a working
QCOM wfd stack
Change-Id: Ie0637914b853609e27e8c5cb5699364b1717f712
|
|
Change-Id: Ia38914588a0b0e3bc30c51df9a7b8681f5bf9d76
|
|
There is no evidence that Qualcomm devices running a rather recent IMS
stack need to include AOSP RCS packages. RCS already worked before this
change and continues to do so, but the main goal was to get rid of some
of the RCS related log spam, which was accomplished here.
Change-Id: I219546e29d288373877e9bcd194a60ef5e09f224
|
|
* It's built by default if vndk is set to current
Change-Id: I2a00446046bafe265e5ac894656abc72514319d8
|
|
This has been turned into a VINTF fragment.
Change-Id: Iaf53a2e1fbac75d53ec11d4c56c51230f4758daf
|
|
Align with templates while we are at it
Change-Id: I3cd279191c7bd3582f1c1f80c588eb26cf9da933
|
|
In analogy to I017491fd383551c5aadf8648edb900e0c12a27b8
Change-Id: I18f770da2986653a70fdfa92f3be5e1199d06d08
|
|
Preinstalled overlays needn't be signed with the same cert
as the package it overlays, simply being preinstalled is
enough. Sign with the default cert instead for now, which
provides fewer special privileges.
Bug: 162195999
Test: verify values still overlaid correctly
Change-Id: I017491fd383551c5aadf8648edb900e0c12a27b8
|
|
Change-Id: I3f3b699311182449467a90f05a448411d17aadcc
|
|
Change-Id: Ib1e2965a5e9f16929f1dc11c719d917cd85604d1
|
|
Configstore's build rule is already included by
build/make/target/product/base_vendor.mk
Change-Id: Ib73d27f0e19f1eda9a50cd305b323250e122ef87
|
|
Change-Id: Id57661f4f1c4143cbd7b69472e6ab4b428ffab4f
|
|
Change-Id: Ifaf8240542786ba9964d27850e22ce5c43348770
|
|
Qcom extends default range to add wigig support,
which we don't support.
Change-Id: I17324e41b8345de508e8d2627ea282c65ab1262b
|
|
* Kill logcat spam
Change-Id: I20d1f698d3c2d1b56e79f6eb6c5c17069e43c60f
|
|
* Hardware supports 40
Change-Id: I075fff615814fa105ec1493c5bdde60b8abccf0e
|
|
* Disable XTWIFI
Change-Id: I70f39d8d611167f65bb3912590b05f8a8d121c80
|
|
Change-Id: Id4bc301454f9ac675a296a1c74581211789711fc
|
|
sdm660 uses cnss-daemon
Change-Id: I621d026c377502270c0832add025ba6188e0ebde
|
|
Change-Id: I47767a436557f0995abbb3c876bb268484fedaec
|
|
Change-Id: Ib543425786c498eec8ef421f85047bcb1cb0cae3
|
|
They are compiled as dependencies of ipacm
Change-Id: I72076113083308e26573289923f5d3c00a8a6b44
|
|
* Only matters when it differs from the device OEM.
Change-Id: Id9af8263cb42dc7a0e3a9ce8677385e224910302
|
|
* It's now deprecated
Change-Id: I00c8bdc09da4ba39508314ec8feba67d60e4fb04
|
|
Change-Id: Id2fb715d0dbe3b148603d0fe5b9ab301fbeea683
|
|
Change-Id: If730bffdf749f30ddf0dfeec8ce769848b19b17e
|
|
* This device does not have sscrpcd, so the extra logic in the script is
useless.
* The /persist/sensors directory and files already have their
permissions set by init.qcom.rc during the early-boot phase.
Change-Id: I3ea825c7cd297fadd19cd56217ac0010a2f47089
|
|
* These are implicitly included by AOSP.
Change-Id: I9e557444161e7ca60793bddde82330a6bd04908b
|
|
Change-Id: Ib0caebf1d3414f46833ff0091d28aba6788b2c1c
|
|
* The Lineage framework does not have a dependency on any of these
packages, since we do not make use of Qualcomm WLAN value-adds.
Change-Id: I8802d3159354a235c25e4d1d3b96cf280dbd5c20
|
|
* These are already packaged by AOSP.
Change-Id: I77f91fbbb33a6d891d14fe852b094ab914ca3111
|
|
* The mediametrics packages are part of the AOSP media stack already.
* libavserviceextensions is not available in Lineage.
Change-Id: Ia05789b6d59ad04e236b20155ac8b9575b0bdab1
|
|
* These don't exist.
Change-Id: I08f319e26867eb0b8fcdfaa632b4f6061f33b982
|
|
* These files are listed as prebuilts already.
Change-Id: I130ee9f82e6fe9a6015a3820f2ca4a0dca6c8e61
|
|
* It's proprietary and already included in vendor makefiles.
Change-Id: Ic19703a39e3e691a04b226b2cb2a27b02703724d
|
|
* This tool can be built manually for debugging cases,
there is no need to ship it in production
Change-Id: I9ab8b076b4bede70c368c198960ceabc68dad65b
|
|
Fixed : CTS issue due to ipsec_tunnel feature.
CTS issues are showing failure on devices with first_api_level set to
29 . With this api level certain test cases which weren't executing
till now begin executing. Ex: android.net.cts.IpSecManagerTunnelTest.
These tests mandatorily requrire ipsec_tunnel feature to be enabled.
Change-Id: If52b652ac3cc6488fefcf851527f224efa03e7eb
|
|
Wifi Passpoint is common permission for all the targets. So, adding
it in wlan makefile.
Change-Id: I30df2278e693fa168de735d20d253da4e7b97200
CRs-Fixed: 2487922
|
|
Change-Id: I37ed14286a1c2ede3e35214723464b5774361adb
|
|
android.hardware.opengles.aep and android.hardware.vulkan*
are duplicated
android.software.webview is already in system partition
Change-Id: I8ca77c1f4cf17a4fd64e37293313befa561c95fe
|
|
* Deprecated
Change-Id: Id50d6721cb1fb96bdb6d3ddb40b36a0147094b86
|
|
* This is defined nowhere in tree.
Change-Id: Ib82c10b46489af30c06dbe26b4aa73fd1fb15fc6
|
|
* No longer exists.
Change-Id: I7f5088b8daedd87107c94f4bddd45286d7453834
|
|
TARGET_PROVIDES_KEYMASTER is a no-op because there's no OSS
keystore for sdm660 devices.
Change-Id: I740bdc65d04cdde7b4965a9ee4705b6d317daa4f
|
|
This block is completely redundant because..
- WITH_DEXPREOPT := true is the default
- WITH_DEXPREOPT_PIC is never read
- DEX_PREOPT_DEFAULT := nostripping has no effect when the
BOARD_USES_SYSTEM_OTHER_ODEX flag is set to true
Test: make
Change-Id: I618a1e395ca1a14555cd50eef1a4f1aa079b553d
|
|
* MAX_EGL_CACHE_KEY_SIZE - Not used anywhere.
* MAX_EGL_CACHE_SIZE - Not used anywhere.
* PRODUCT_VENDOR_MOVE - No longer needed.
* USE_OPENGL_RENDERER - Not used in any repos we build
(msm8960 display HAL leftover).
* BOARD_USES_QCNE - Only referenced in very old BSPs.
Change-Id: I8d140fecdbbaac979bc8398745ffa95b911e4c89
|
|
The TARGET_USES_64_BIT_BINDER option is deprecated and can be removed
Change-Id: I6b828da1fbcc8c054c5b35ff78c870a689f7ed9f
|
|
Change-Id: I40a14bce12ee4725af17a3e8fbc05143e5577f8e
|
|
TARGET_KERNEL_ARCH is a no-op unless it is different from TARGET_ARCH.
TARGET_KERNEL_HEADER_ARCH is also a no-op unless
it is different from TARGET_KERNEL_ARCH.
Change-Id: If64fb040c8ec61394e2657f13e51ff7a08519220
|
|
Remove various variables related to where kernel and ramdisk are loaded
by the bootloader. There are two reasons for this:
1. The B1C1 bootloader ignores all the offset values for kernel, ramdisk
and tags. The default B1C1 memory layout has been designed to accomodate
a larger KASAN kernel.
2. The variables BOARD_KERNEL_TAGS_OFFSET and BOARD_RAMDISK_OFFSET are
ignored by the Android build system (unless they are copied into the
BOARD_MKBOOTIMG_ARGS variable). This is in contrast to the variables
BOARD_KERNEL_BASE, BOARD_KERNEL_PAGESIZE and BOARD_MKBOOTIMG_ARGS which
are referenced by build/make/core/Makefile
Bug: 117832711
Change-Id: I3404a4e084ed063d51077a3a80229854362c768b
|
|
So that init knows how to start it and to provide
an example of how to specify interfaces since there
are no lazy starting services on Pixel yet.
In order to make lights a lazy service, it would also
have to be marked as 'oneshot'.
Test: manually using Light as a lazy service
Bug: 64678982
Merged-In: I846a7e2d9545b42af9b985adb74883bda1b8c355
Change-Id: I846a7e2d9545b42af9b985adb74883bda1b8c355
|