With this CL, wahoo devices have the same status with marlin/sailfish
in terms of vndk-sp libs.
Bug: 37550338
Bug: 37483222
Test: RenderScript apps work (e.g. CameraScript)
Test: boot successful without following message:
failed to load /vendor/lib64/egl/libEGL_adreno.so from sphal namespace:
dlopen failed: library "libcutils.so" not found
Change-Id: I4a2159395904c2597ed74785b00dca4487aea715
Move hal configuration file to /vendor to satisfy treble requirement.
Test: wahoo sensor works
Bug: 35947802
Change-Id: I0ef5aff67653090791c1f11b79bc5f3420122aec
android.hidl.base@1.0 and android.hidl.manager@1.0 are built into libhidltransport.
Test: links
Bug: 33276472
Change-Id: Ie75f2af2a53c53cde3ebf5e76c7282261e3c7c74
Note: this shouldn't be permanent solution. Anything that is installed
to /vendor partition must be compiled against the vndk build of the
system libraries, which might be different than the core build of the
libraries. However, since the number of such libraries are so many and
thus it takes considerable time to build them as vndk. So, in the mean
time, we just build vendor libraries against the core build as before
and copy the core builds to the vendor partition.
Bug: 37483222
Test: the listed files are in /vendor/lib(64?)/vndk-sp and their
contents are the same as those in /system/lib(64?).
Test: muskie/walleye boots
Change-Id: I143fb2cf8b6f3215a05582b23997150d75028adb
Adds vulkan support level and version to system/etc/permissions;
fixes sepolicy so the vulkan driver can load.
Fixes tests in android.graphics.cts.VulkanFeaturesTest:
- testVulkanHardwareFeatures
- testVulkanVersionForVrHighPerformance
sepolicy change mostly borrowed from equivalent marlin config
Test: CtsGraphicsTestCases/android.graphics.cts.VulkanFeaturesTest
Bug: b/37719307
Change-Id: Ia99d6dacc8d8353cb7ef0e1cfaca0636708c5067
out/target/product/muskie/system/etc/fs_config_dirs is not built. The
build tool fixed in https://android-review.googlesource.com/#/c/382272
so this one can now be reverted.
This reverts commit fe01b01dbe.
Signed-off-by: Mark Salyzyn <salyzyn@google.com>
Bug: 37721445
Bug: 36071012
Change-Id: If53ad9eeb676c9566553befbd51e2b336f46087b
This CL adds support to notify frameworks when an audio
or debug accessory is attached.
Bug: 36604276
Test: Manually test inserting an Audio accessory.
Change-Id: I9ec0f88ed85ed593b31132ba58bfedb51a435cd8
Bug: 36097673
Test: mm && tested on Walleye to make sure QCOM driver load.
Test: RS CTS tests pass
Test: Imageprocessing tests pass, and confirming running on GPU.
Change-Id: Iaca74a8e90d9fd10e4327bd55d982e95b700ca0f
* changes:
init.hardware.rc: start qseecomd on fs
manifest.xml: add gatekeeper and keymaster definitions
Add sepolicies for binderized QCOM KM 3.0 and GK 1.0 HAL
device: don't use generic GK and KM HALs
device: add frp prop
persist.radio.data_con_rprt=true
This will enable RIL to report DATA_REGISTRATION_STATE RAT IWLAN
if device is IMS registered for voice over Wifi. Reporting IWLAN
in this use case is needed for telephony to use IWLAN RAT for APN
selection for data call (ex. MMS) over IWLAN use cases.
Bug: 37326164
Change-Id: I5d102a70b67aa098de015fb72038edccb5c3fd67
Allow SLPI to crash and restart without bringing down the system.
Bug: 37503415
Test: load, confirm SSR entry gets set
Change-Id: I87fa72f557bf37add17f3a908e589dbc6f0c722e
This has the side effect of disabling preloading of the EGL/GLES drivers
in Zygote.
Bug: 37323602
Test: confirm driver not loaded in zygote, run gles3jni + vulkanGears
Change-Id: I4231ada91ba7dda7f7d6f8cff1de7957c24f2d99
Muskie and Wallye overlays should override the overlays defined
in wahoo. Also, resources outside of the "values" directory are
overlayed by the file so there is no need of power_profile.xml
for wahoo since muskie and walleye will always override it completely.
BUG: 36796913
Test: Verified "App usage since last charge" under Settings->Battery
Change-Id: Idc0bbe8920bf209d7cd721ea2b7fb32647d30ec2
Test Done: dumpsys to check effects are loaded
Bug: 36865903
Change-Id: I10efc6921a95e96bfc29337b95275788b9780524
Signed-off-by: David Lin <dtwlin@google.com>
It managed the eSE by accessing the driver through the /dev/pn81a node.
Test: Boot brings up esed which connects to the eSE.
Bug: 35628284
Change-Id: I6fa3384169adb60095585856accd53bc61d06cf4
