See bug for more details. The apk already supports asking for this permission at runtime. Upgrading to this android build does not revoke the permission out from under the app.
Bug: 130440726
Test: Manually tested by upgrading walleye to this build and seeing now playing continue to work.
Change-Id: I599586b93ad786762e151fb798d4e5011f2b0315
/metadata should be synchronous enoughly to avoid boot failure.
Bug: 134172577
Change-Id: I342b1eab9b3b79024deebe039e07d0aa93209148
Signed-off-by: Jaegeuk Kim <jaegeuk@google.com>
- Pre-granting runtime permissions. The stub will be installed on Pixel
1's and this matches Pixel 4 setup.
Bug: 133353187
Test: Build/installed images on Pixels and confirm AA setup
Change-Id: I9e964a1ef40284c6777c733f0f7e771109c7c5a6
Most apps already have the permission to act as full producers
(isolated_app, ephemeral_app, priv_app, untrusted_app_all), but
the camera doesn't inherit that as it runs in its own domain.
Granting only the socket (i.e. ipc) permission, as:
* only that is needed at the moment.
* granting the shmem/fd permissions would require a broader change, as traced_tmpfs is declared in private/.
Specific denial:
05-20 13:56:20.303 7751 7751 W trigger_perfett: type=1400 audit(0.0:19): avc: denied { write } for name="traced_producer" dev="tmpfs" ino=7061 scontext=u:r:google_camera_app:s0:c181,c256,c512,c768 tcontext=u:object_r:traced_producer_socket:s0 tclass=sock_file permissive=0 app=com.google.android.GoogleCamera
Bug: 130543265
Tested: extrapolating from the same fix on crosshatch, tested manually on blueline-userdebug.
Merged-In: I53dc08a28d167f566b759d8f91d00a4828f4847f
Change-Id: I53dc08a28d167f566b759d8f91d00a4828f4847f
(cherry picked from commit 12b6414919)
The Camera HIDL wrapper needs access to
properties "ro.camera.req.fmq.size" and
"ro.camera.res.fmq.size" which control
the fast message queue size. Cases exist
where the default size is not sufficient.
The precise amount can be controlled by
the respective device configuration which
can set the previously mentioned properties.
Bug: 77865891
Test: Manual using application
Change-Id: I468bde2ee356e0d1d20f781fe6a3af48143cc4b2
Merged-In: I468bde2ee356e0d1d20f781fe6a3af48143cc4b2
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
ag/6722341 will set WLAN driver/FW when start legacy HAL.
The patch removes init.qcom.wlan.sh because it is not necessary
Bug: 127715974
Test: Property with wlan driver/FW version at enforcing mode:
It can be verified by the below command:
# adb shell getprop vendor.wlan.driver.version
# adb shell getprop vendor.wlan.firmware.version
Change-Id: Id94874cb96bc489a0f3eccfb97d780001b712330
ag/6722341 will set WLAN driver/FW when start legacy HAL.
The patch have some change to for the same purpose:
1. Add sepolicy for wifi hal to set WLAN driver/FW into property
2. Remove sepolicy for init.qcom.wlan.sh, because it no necessary
Bug: 127715974
Test: Property with wlan driver/FW version at enforcing mode:
It can be verified by the below command:
# adb shell getprop vendor.wlan.driver.version
# adb shell getprop vendor.wlan.firmware.version
Change-Id: I48f1752749db376a19235676af116cbbdeb63811
ModemDiagnosticSystem app has moved away from platform certificate
(ag/7094557). Updating seapp_contexts so it can associate app with
modem_diagnostics.te.
Test: Open MDS
Bug: 131719647
Change-Id: Idb140c49c8ba4fcba79eb994b8aa53b25f8f0972
The HAL is served from a system app and used by
a vendor daemon.
Test: ls /system/app/atfwd/atfwd.apk
Test: ls /vendor/bin/ATFWD-daemon
Test: lshal
Bug: 130714844
Change-Id: I87e10fa56ac84ddd7e4210ac2bc4f1338265e1e9
- Settings Intelligence needs the location and location permissions
pregranted and fixed in order to function correctly. This change
makes the calendar and location settings consistent acrosss the
range of devices that support Q.
Bug: 130349398
Test: built & flashed to device, confirmed permission granted
Change-Id: Ibf1003e5ffbb5bcc51b57161b72cdd128557b04a
Set stune.boost to 100 to boost process to big cores and prefer_idle to
1 to spread tasks. This saves ~370ms from kernel boot to boot_complete.
Before CL:
BootComplete : 10.046 0.067631
Post CL:
BootComplete : 9.6713 0.083226
Test: boottime
Bug: 80345258
Change-Id: I29159ba3102a23f302ddc2a2747879fd1ca39c27
