[Xperia Z1 Android Development] santeria27:
root: flash the last supersu.zip via recovery thats all and works fine! and mobile data by me dont work!!!! sms,tele,etc works

Telephony

One of the most common features related to making phone calls, call blocking, is finally now being made a requirement for any device running Android 7.0 Nougat.

7.4.1.1. Number Blocking Compatibility

Android Telephony device implementations MUST include number blocking support and:

MUST fully implement BlockedNumberContract and the corresponding API as described in the SDK documentation.

MUST block all calls and messages from a phone number in ‘BlockedNumberProvider’ without any interaction with apps. The only exception is when number blocking is temporarily lifted as described in the SDK documentation.

MUST NOT write to the platform call log provider for a blocked call.

MUST NOT write to the telephony provider for a blocked message.

MUST implement a blocked numbers management UI, which is opened with the intent returned by TelecomManager.createManageBlockedNumbersIntent() method.

MUST NOT allow secondary users to view or edit the blocked numbers on the device as the Android platform assumes the primary user to have full control of the telephony Page 59 of 85 services, a single instance, on the device. All blocking related UI MUST be hidden for secondary users and the blocked list MUST still be respected.

SHOULD migrate the blocked numbers into the provider when a device updates to Android 7.0.

9.13. Safe Boot Mode

Android provides a mode enabling users to boot up into a mode where only preinstalled system apps are allowed to run and all third-party apps are disabled. This mode, known as “Safe Boot Mode”, provides the user the capability to uninstall potentially harmful third-party apps. Android device implementations are STRONGLY RECOMENDED to implement Safe Boot Mode and meet following requirements:

Device implementations SHOULD provide the user an option to enter Safe Boot Mode from the boot menu which is reachable through a workflow that is different from that of normal boot.

Device implementations MUST provide the user an option to enter Safe Boot Mode in such a way that is uninterruptible from third-party apps installed on the device, except for when the third party app is a Device Policy Controller and has set the UserManager.DISALLOW_SAFE_BOOT flag as true.

Device implementations MUST provide the user the capability to uninstall any third-party apps within Safe Mode.

Users who own a separate Android device for their work may now be met with a separate lock screen to grant access to certain apps, an attempt by Google to allow for enterprises to sandbox critical apps separately in case clumsy workers allow a third-party access to their device.

3.9.2 Managed Profile Support

Support the ability to specify a separate lock screen meeting the following requirements to grant access to apps running in a managed profile.

Device implementations MUST honor the DevicePolicyManager.ACTION_SET_NEW_PASSWORD intent and show an interface to configure a separate lock screen credential for the managed profile.

The lock screen credentials of the managed profile MUST use the same credential storage and management mechanisms as the parent profile, as documented on the Android Open Source Project Site

The DPC password policies MUST apply to only the managed profile’s lock screen credentials unless called upon the DevicePolicyManager instance returned by getParentProfileInstance

USB Connections

If you’re familiar with the work done by Nathan K. and Benson Leung with regards to USB Type-C cables, then you might be somewhat aware of the issues regarding USB Type-C interoperability and safety. Many third-party fast-charging methods modify the voltage levels and other parts to provide faster charging at the expense of the device losing compatibility with USB Power Delivery (USB PD) methods. Google is now strongly recommended that OEMs stop modifying their charging methods in this manner, with the possibility of revoking CTS in the future for devices that fail to meet these guidelines.

7.7.1 USB Peripheral Mode

Type-C devices are STRONGLY RECOMMENDED to not support proprietary charging methods that modify Vbus voltage beyond default levels, or alter sink/source roles as such may result in interoperability issues with the chargers or devices that support the standard USB Power Delivery methods. While this is called out as “STRONGLY RECOMMENDED”, in future Android versions we might REQUIRE all type-C devices to support full interoperability with standard type-C chargers

Mobile Data Management

Data Saver is one of the low-key features introduced in Nougat. The feature allows users to restrict background data access only to those apps that are white-listed. This is especially useful to users who are on plans with low data limits. Unfortunately, this feature is not required to be implemented by OEMs.

7.4.7. Data Saver

Device implementations with a metered connection are STRONGLY RECOMMENDED to provide the data saver mode. If a device implementation provides the data saver mode, it:

MUST support all the APIs in the ConnectivityManager class as described in the SDK documentation.

MUST provide a user interface in the settings, allowing users to add applications to or remove applications from the whitelist.

Conversely if a device implementation does not provide the data saver mode, it:

MUST return the value RESTRICT_BACKGROUND_STATUS_DISABLED for ConnectivityManager.getRestrictBackgroundStatus

MUST not broadcast ConnectivityManager.ACTION_RESTRICT_BACKGROUND_CHANGED

MUST have an activity that handles the Settings.ACTION_IGNORE_BACKGROUND_DATA_RESTRICTIONS_SETTINGS intent but MAY implement it as a no-op.