Xiaomi Redmi Note 8 Pro 128Gb+6Gb Dual LTE [40/132] Widgets

MAY override the app icon badges with their proprietary badging scheme when third-party

applications indicate support of the proprietary badging scheme through the use of

proprietary APIs, but SHOULD use the resources and values provided through the

notification badges APIs described in the SDK , such as the Notification.Builder.setNumber()

and the Notification.Builder.setBadgeIconType() API.

3.8.2. Widgets

Android supports third-party app widgets by defining a component type and corresponding API and

lifecycle that allows applications to expose an “AppWidget” to the end user.

If device implementations support third-party app widgets, they:

[C-1-1] MUST declare support for platform feature android.software.app_widgets .

[C-1-2] MUST include built-in support for AppWidgets and expose user interface

affordances to add, configure, view, and remove AppWidgets directly within the Launcher.

[C-1-3] MUST be capable of rendering widgets that are 4 x 4 in the standard grid size. See

the App Widget DesignGuidelines in the Android SDK documentation for details.

MAY support application widgets on the lock screen.

If device implementations support third-party app widgets and in-app pinning of shortcuts, they:

[C-2-1] MUST report true for AppWidgetManager.html.isRequestPinAppWidgetSupported() .

[C-2-2] MUST have user affordance asking the user before adding a shortcut requested by

apps via the AppWidgetManager.requestPinAppWidget() API method.

3.8.3. Notifications

Android includes Notification and NotificationManager APIs that allow third-party app developers to notify

users of notable events and attract users' attention using the hardware components (e.g. sound,

vibration and light) and software features (e.g. notification shade, system bar) of the device.

3.8.3.1. Presentation of Notifications

If device implementations allow third party apps to notify users of notable events , they:

[C-1-1] MUST support notifications that use hardware features, as described in the SDK

documentation, and to the extent possible with the device implementation hardware. For

instance, if a device implementation includes a vibrator, it MUST correctly implement the

vibration APIs. If a device implementation lacks hardware, the corresponding APIs MUST

be implemented as no-ops. This behavior is further detailed in section 7 .

[C-1-2] MUST correctly render all resources (icons, animation files, etc.) provided for in

the APIs, or in the Status/System Bar icon style guide , although they MAY provide an

alternative user experience for notifications than that provided by the reference Android

Open Source implementation.

[C-1-3] MUST honor and implement properly the behaviors described for the APIs to

update, remove and group notifications.

[C-1-4] MUST provide the full behavior of the NotificationChannel API documented in the

SDK.

[C-1-5] MUST provide a user affordance to block and modify a certain third-party app's

notification per each channel and app package level.

[C-1-6] MUST also provide a user affordance to display deleted notification channels.

[C-1-7] MUST correctly render all resources (images, stickers, icons, etc.) provided

Page 40 of 132