Gadget Controls is a function in Android 11 that allows for clever home automation controls to be shown in the power menu. Google included APIs that designers of clever home apps can utilize to emerge controls in the power menu. If an OEM believes the feature is lame or they desire to go a different path (such as just allowing smart house controls from gadgets in their own environment), then they can simply disable support for Device Controls.
When Google first included Device Controls to the CDD on February 25th, 2020, they mandated its inclusion by including a “MUST” requirement in Section 2.2.3– Handheld Software Requirements. However, on May 20th, 2020, Google updated the text to eliminate the proposed “MUST”. The brand-new Section 3.8.16– Device Controls details how the function has to be executed however does not actually need that it be implemented in the first place! We hope OEMs wont disable this clever function, but theres no chance for us to understand if they have disabled it up until theyre all set to unveil their own flavors of Android developed on top of Android 11, which wont happen up until a number of months from now.
Earlier this month, Google unveiled the first Android 11 Beta and talked extensive about the best functions for users to take pleasure in and for developers to implement. Weve now found out that 3 of the top features in Android 11 will not be available on every Android gadget.
Many of the brand-new OS functions that Google unveiled for Android 11 will be part of the Android Open Source Project (AOSP) that smartphone gadget makers base their own software application on, but the Apache 2.0 license, as I discussed previously, lets anybody customize the software application as they see fit. In order to preserve consistency in APIs and platform behavior between Android devices, Google bundles the circulation of Google Mobile Services (which includes applications and structures like the Google Play Store and Google Play Services) with license contracts mandating that gadgets adhere to the guidelines under Googles “Android Compatibility Program” (amongst other requirements).
In the CDD, Google lists software and hardware functions that gadget makers “MUST” implement, are just “STRONGLY RECOMMENDED” to implement, or “SHOULD NOT” carry out. If a function is noted as “MUST” carry out, then the gadget maker needs to add that feature or they cant ship Google apps on their gadgets. If a function is listed as “SHOULD NOT” execute, then the gadget maker cant add that feature or they cant bundle Google apps. If a function is listed as “STRONGLY RECOMMENDED,” then its up to the device maker whether or not they want to execute the function. The CDD is a constantly changing file, even before its publication every year following the public release of a brand-new Android version. Google frequently updates the file to eliminate features, change the language to be clearer, and relax requirements based on feedback from its partners. Nevertheless, once Google makes a CDD public for a specific Android variation, those requirements will be set in stone for Google-certified devices running that Android OS variation.
Designer @deletescape shared a pre-release copy of a file that information changes coming to the CDD, offering us an early look at how Google is shaping Android 11 throughout the ecosystem. 3 of the changes to the CDD caught our attention due to the fact that they relate to some of the most fascinating features in Android 11.
Gadget Controls
Proposed Section 3.8.16 (New) – Device Controls (Updated 5/20/2020).
3.8.16 Device Controls.
Android includes ControlsProviderService and Control APIs to enable designers to publish device controls for fast status and action for users.
3.8.16.1 Device Controls User Affordance.
If gadgets carry out Device Controls, then they:.
IdentityCredential– Mobile Drivers Licenses.
One of the features that Im most thrilled about is the IdentityCredential API. As we detailed last year, the IdentityCredential API is created to allow applications to keep identity documents, such as mobile motorists licenses, on the gadget. Several nations (and some U.S. States) worldwide currently permit their people to save their chauffeurs licenses in a mobile app. Nevertheless, Google is working to make this more protected by having the data kept offline in a safe environment.
The Identity Credential System permits app designers to recover and keep user identity documents.Device applications:.
[C-SR] are STRONGLY RECOMMENDED to implement the Identity Credential System.
If gadget implementations implement the Identity Credential System they:.
These changes were most likely unwinded due to feedback from OEMs who are the ones that will have to go back and carry out these functions if they werent already prepared on doing so. That takes effort, time, and money, which would simply postpone the release of Android 11 for non-Google gadgets even further. Still, if Google does make these features required as soon as more, well post an upgrade on the XDA Portal.
One of Androids most significant advantages compared to iOS is how the former manages notices. That space in usability will get back at larger in Android 11 with the intro of “Conversations.” In Android 11, alerts from messaging apps are organized together and are revealed in a separate section in the notification panel above a lot of other notices. This lets you rapidly react and see to messages without needing to scroll through all your other pending alerts. Regrettably, this cool modification to notifications might not be offered on all devices. Google is offering OEMs the choice to select whether they wish to “group and screen discussion alerts ahead of non-conversation notifications.” OEMs often customize the notice panel, and so its no surprise that Google is providing OEMs an option here. Still, its regrettable that Google isnt selecting to impose more consistency in notices in Android 11.
A sample picture of a digital drivers license accessed through the LA Wallet app. Source: Envoc.
[C-0-1] MUST return non-null for the IdentityCredentialStore #getInstance() method.
MUST execute the android.security.identity. The relied on application must be carried out such that the Trusted Computing Base for the Identity Credential System does not consist of the Android Operating System.
[C-1-1] MUST report the android.software.controls.feature flag to be TRUE.
[C-1-2] MUST offer a user affordance with the capability to include, modify, choose and operate the users favorites from the controls signed up by the 3rd-party apps through the android.service.controls.ControlsProviderService and the android.service.controls.Control APIs.
[C-1-3] MUST provide access to this user affordance within three interactions from the Launcher.
[C-1-4] MUST properly render in this user affordance the name and icon of each 3rd-party app that supplies controls by means of the android.service.controls.ControlsProviderService API along with any specified icon, status text, device type, name, structure, zone, custom-made color, and subtitle offered by the android.service.controls.Control API.
Proposed Section 9.11.3 (New) – Identity Credential (Updated 3/18/2020).
Conversely, If device executions do not carry out such controls, then they.
[C-2-1] MUST report Null for the ControlsProviderService and the Control APIs.
If device implementations allow 3rd party apps to inform users of noteworthy events, they: … Android R presents support for discussion notice, which is a notice that uses NotificationManager.MessageStyle and supplies a released People Shortcut ID.
Gadget applications are:.
[H-SR] HIGHLY RECOMMENDED to group and screen discussion notices ahead of non discussion alerts with the exception of continuous foreground service alerts and value: high notices.
If conversation alerts are organized into a separate area, gadget executions.
[H-1-8] MUST display discussion notifications ahead of non discussion notices with the exception of ongoing foreground service notifications and importance: high notifications.
Device implementations are:.
[H-SR] STRONGLY RECOMMENDED to supply access to the following actions from conversation notices: screen this discussion as a bubble if the app supplies the needed data for bubbles.
The AOSP application meets these requirements with the default System UI, Settings, and Launcher.
Discussions in Notifications.
Conversations in Android 11. Source: Google.
Proposed changes to Section 3.8.3.1 – Presentation of Notifications (Updated 4/08/2020).
Weve now discovered that three of the top functions in Android 11 will not be offered on every Android gadget.
Many of the brand-new OS functions that Google unveiled for Android 11 will be part of the Android Open Source Project (AOSP) that smartphone device makers base their own software on, however the Apache 2.0 license, as I mentioned previously, lets anyone modify the software application as they see fit. In order to keep consistency in APIs and platform behavior in between Android devices, Google bundles the circulation of Google Mobile Services (which consists of applications and frameworks like the Google Play Store and Google Play Services) with license contracts mandating that devices adhere to the rules under Googles “Android Compatibility Program” (among other requirements). As soon as Google makes a CDD public for a particular Android variation, those requirements will be set in stone for Google-certified devices running that Android OS variation.
Given That Android 7.0 Nougat, Google has needed all modern-day Android gadgets to support an “isolated execution environment” (per Section 2.2.5– Security Model in the CDD).
The source code for Android 11 consists of the IdentityCredential API (which developers will call to save identity documents in the phones protected environment) and the IdentityCredential HAL (which user interfaces with the phones safe environment), but OEMs are not needed to execute them. When Google first proposed the addition of IdentityCredential in the CDD on January 10, 2020, they listed it as a requirement. Nevertheless, they unwinded this requirement on March 18, 2020, and now only strongly advise that OEMs support this function. Were not amazed that Google relaxed this requirement– adding a modification that affects the trusted execution environment will require effort from OEMs to implement. Its possible that OEMs merely require more time to prepare for this change. For users, however, that implies theres no assurance your particular Android 11 smart device will support safely keeping a mobile chauffeurs license in the phones secure environment.
We must note that theres no technical limitation preventing the extensive adoption of the IdentityCredential system amongst Android 11 gadgets. Among the requirements for carrying out the IdentityCredential system is that the device has a Trusted Execution Environment (TEE) or a dedicated secure processor in which a “trusted application” interacts with the saved identity documents. Because Android 7.0 Nougat, Google has actually needed all modern Android gadgets to support an “separated execution environment” (per Section 2.2.5– Security Model in the CDD). Gadgets with ARM processors usually include ARMs TrustZone TEE, and Google offers the Trusty OS that runs on TrustZone. The existence of a TEE suffices to support the IdentityCredential system, though it would be more secure if the qualifications are stored in an ingrained safe and secure CPU (such as in the Secure Processing Unit of some Qualcomm Snapdragon processors) or a discrete protected CPU (such as in Googles Titan M or Samsungs new security chips). Notably, devices with discrete secure CPUs might likewise be able to support the “Direct Access mode” feature of the IdentityCredential system, which will permit the user to bring up their identity document even when there isnt enough power left in the gadget to boot up the main OS.
Google is also dealing with an IdentityCredential Jetpack library to make it much easier for designers to include support for safely keeping identity documents on Android, however the genuine difficulty will be getting governments to authorize apps using this API to firmly save federal government IDs. According to Engadget, South Korea simply presented assistance for keeping motorist licenses in a mobile app, so were starting to see an uptick in acceptance for this innovation. I, for one, am excited to see where this goes since itll imply one less thing to bring with me when I go outside.
XDA” Exclusive” Exclusive: 3 of Android 11s best features will not be available on every device.
