Xiaomi Pocophone F1 128Gb+6Gb Dual LTE [91/118] Minimum network capability

implementation SHOULD still accept SNEP GET requests for exchanging the handover

request/select records over NFC. However an implementation itself SHOULD NOT send

SNEP GET requests for performing connection handover.

[C-1-13] MUST poll for all supported technologies while in NFC discovery mode.

SHOULD be in NFC discovery mode while the device is awake with the screen active and

the lock-screen unlocked.

SHOULD be capable of reading the barcode and URL (if encoded) of Thinfilm NFC Barcode

products.

(Note that publicly available links are not available for the JIS, ISO, and NFC Forum specifications

cited above.)

Android includes support for NFC Host Card Emulation (HCE) mode.

If device implementations include an NFC controller chipset capable of HCE (for NfcA and/or NfcB)

and support Application ID (AID) routing, they:

[C-2-1] MUST report the android.hardware.nfc.hce feature constant.

[C-2-2] MUST support NFC HCE APIs as defined in the Android SDK.

If device implementations include an NFC controller chipset capable of HCE for NfcF, and implement

the feature for third-party applications, they:

[C-3-1] MUST report the android.hardware.nfc.hcef feature constant.

[C-3-2] MUST implement the NfcF Card Emulation APIs as defined in the Android SDK.

If device implementations include general NFC support as described in this section and support

MIFARE technologies (MIFARE Classic, MIFARE Ultralight, NDEF on MIFARE Classic) in the

reader/writer role, they:

[C-4-1] MUST implement the corresponding Android APIs as documented by the Android

SDK.

[C-4-2] MUST report the feature com.nxp.mifare from the

android.content.pm.PackageManager.hasSystemFeature () method. Note that this is not a standard

Android feature and as such does not appear as a constant in the

android.content.pm.PackageManager class.

7.4.5. Minimum Network Capability

Device implementations:

[C-0-1] MUST include support for one or more forms of data networking. Specifically,

device implementations MUST include support for at least one data standard capable of

200Kbit/sec or greater. Examples of technologies that satisfy this requirement include

EDGE, HSPA, EV-DO, 802.11g, Ethernet, Bluetooth PAN, etc.

[C-0-2] MUST include an IPv6 networking stack and support IPv6 communication using

the managed APIs, such as java.net.Socket and java.net.URLConnection , as well as the native

APIs, such as AF_INET6 sockets.

[C-0-3] MUST enable IPv6 by default.

MUST ensure that IPv6 communication is as reliable as IPv4, for example.

[C-0-4] MUST maintain IPv6 connectivity in doze mode.

[C-0-5] Rate-limiting MUST NOT cause the device to lose IPv6 connectivity on any IPv6-

compliant network that uses RA lifetimes of at least 180 seconds.

SHOULD also include support for at least one common wireless data standard, such as

Page 91 of 118