diff options
Diffstat (limited to 'en')
-rw-r--r-- | en/devices/graphics/arch-sh.html | 4 | ||||
-rw-r--r-- | en/devices/storage/config.html | 2 | ||||
-rw-r--r-- | en/security/selinux/implement.html | 10 |
3 files changed, 8 insertions, 8 deletions
diff --git a/en/devices/graphics/arch-sh.html b/en/devices/graphics/arch-sh.html index 3b597abb..c3c74dfe 100644 --- a/en/devices/graphics/arch-sh.html +++ b/en/devices/graphics/arch-sh.html @@ -60,7 +60,9 @@ hardware-accelerate the Canvas API. As you can see from the charts on the Acceleration</a> page, this was a bit of a bumpy ride. Note in particular that while the Canvas provided to a View's <code>onDraw()</code> method may be hardware-accelerated, the Canvas -obtained when an app locks a Surface directly with <code>lockCanvas()</code> never is.</p> +obtained when an app locks a Surface directly with <code>lockCanvas()</code> never is. +As of API 23, a hardware-accelerated Canvas can be obtained from a Surface using +<code>lockHardwareCanvas()</code> instead.</p> <p>When you lock a Surface for Canvas access, the "CPU renderer" connects to the producer side of the BufferQueue and does not disconnect until the Surface is diff --git a/en/devices/storage/config.html b/en/devices/storage/config.html index 272566f7..f9f31c79 100644 --- a/en/devices/storage/config.html +++ b/en/devices/storage/config.html @@ -24,7 +24,7 @@ <p>External storage is managed by a combination of the <code>vold</code> init -service and <code>MountService</code> system service. Mounting of physical +service and <code>StorageManagerService</code> system service. Mounting of physical external storage volumes is handled by <code>vold</code>, which performs staging operations to prepare the media before exposing it to apps.</p> diff --git a/en/security/selinux/implement.html b/en/security/selinux/implement.html index a17e4f89..11473906 100644 --- a/en/security/selinux/implement.html +++ b/en/security/selinux/implement.html @@ -106,17 +106,15 @@ labels may also be assigned to specific mounts such as vfat using the context= mount option. <li><em>property_contexts</em> - Located in the sepolicy subdirectory. This file assigns labels to Android system properties to control what processes can -set them. This configuration is read by the init process during startup and -whenever the selinux.reload_policy property is set to 1. +set them. This configuration is read by the init process during startup. <li><em>service_contexts</em> - Located in the sepolicy subdirectory. This file assigns labels to Android binder services to control what processes can add (register) and find (lookup) a binder reference for the service. This -configuration is read by the servicemanager process during startup and whenever -the selinux.reload_policy property is set to 1. +configuration is read by the servicemanager process during startup. <li><em>seapp_contexts</em> - Located in the sepolicy subdirectory. This file assigns labels to app processes and /data/data directories. This configuration -is read by the zygote process on each app launch and by installd during startup -and whenever the selinux.reload_policy property is set to 1. +is read by the zygote process on each app launch and by installd during +startup. <li><em>mac_permissions.xml</em> - Located in the sepolicy subdirectory. This file assigns a seinfo tag to apps based on their signature and optionally their package name. The seinfo tag can then be used as a key in the seapp_contexts |