New Features of Android 4.3

Faster, smoother, and more responsive

Android 4.3 is already included in jelly bean-Vertical synchronization timing, triple buffering, reduced touch latency, CPU input boost, and hardware-accelerated 2D rendering performance improvements-added new optimizations, make Android even faster.

For graphic performance improvement, the current hardware-accelerated 2D rendering-optimized stream graphics command turns it into a more efficient GPU format for rearranging and merging painting operations. For multi-threaded processing, rendering can also use multiple threads across multiple CPU cores to execute certain tasks.

It also improves the shape and text rendering of Android 4.3. The shape of the circle and the rounded rectangle, such as a higher quality and more effective way. Text optimization, including increasing performance when using multiple fonts or complex font sets CJK), higher rendering quality zooming text, and faster rendering shadows.

Improve the window Buffer Allocation Result for your application in a faster Image Buffer Allocation, reduce the time spent when you create a window to start rendering.

For the highest graphics performance, Android 4.3 released OpenGL ES 3.0 support and accessed applications through frameworks and native APIs. On the supported devices, the hardware accelerates the advantages of the 2D rendering engine OpenGL ES 3.0, optimizes texture management and improves gradient rendering fidelity.

OpenGL ES 3.0 high-performance graphics

Android 4.3 introduces support for the platform's Khronos OpenGL ES 3.0 and provides the highest-performance 2D and 3D graphics functions to support games and other applications on devices. You can use OpenGL ES 3.0 and related EGL extensions to bind them to native APIs of the Framework API or Android Native Development Kit NDK.

The main new features provided in OpenGL ES 3.0 include advanced visual effects, accelerated high quality ETC2/EAC texture compression as a standard feature, the new version of the full-digit and 32-bit floating point support, advanced texture rendering in the glsl es coloring language, and standardized texture sizes and Rendering Buffer formats.

You can use the OpenGL ES 3.0 API to create highly complex and efficient graphics. When encountering a series of compatible Android devices, these devices can support a single, standard texture compression format.

An optional function of OpenGL ES 3.0 depends on the underlying graphics hardware. Supported Nexus 4 and Nexus 10 devices for 72013 years.

Enhanced Bluetooth connections to Bluetooth Smart devices and sensors

Now you can design and build applications, small, low-power devices and sensors, and use Bluetooth Smart technology for the latest generation of interaction.

Android 4.3 introduces the core function supported by the built-in Bluetooth Smart readiness platform, and provides a set of standard APIs that can be used by applications to discover nearby devices and query the services of the General Agreement on Customs and trade, and read/write features.

With the new API, your application can effectively scan the interests of devices and services. For each device, you can check the device ID and signal strength of the UUID that supports the general agreement on customs and trade service and management connections. You can connect to the gateway server on the device and read or write the features, or register a listener for changes to these features when a notification is received.

You can support any configuration file of the general agreement on customs and trade. You can read or write standard features or add custom features. Your application can be used as a client or server to send and receive data in any mode. APIs are universal, so you can use various devices that support interaction, such as proximity tags, watches, fitness rice, game controllers, remote controls, medical devices, and.

Supporting Bluetooth Smart readiness is now available in Nexus 72013) and Nexus 4 devices will be compatible with Android devices more and more support in the next few months.

AVRCP 1.3 Overview

Android 4.3 added built-in support for AVRCP Bluetooth 1.3, allowing your applications and remote streaming media devices to support richer interactions. You can remotely control the APIS introduced by the client in Android 4.0. For example, the Media Player application can use AVRCP 1.3. In addition to playing control exposed on a remote device, applications can now transmit metadata such as track names, writers, and other types of media metadata over Bluetooth connections.

The support of AVRCP 1.3 is based on the Bluetooth Stack Bluedroid of Google and Broadcom launched by Android 4.2. Supports the A2DP/AVRCP feature immediately on Nexus devices and other android compatible devices.

Restrictions

Android 4.3's extended multi-user feature, slice restricted area profile, is a new way to manage users and their capabilities on a single device. Profile restriction, tablet users can quickly set up to different environments for each user, and have the ability to manage fine-grained restrictions in applications in these environments. Restricted configuration files are ideal for friends and family, Guest users, kiosks, point-of-sale devices, and more.

Each restricted configuration file provides its own local memory, home screen widgets, and sets up isolated and secure spaces. Different users create configuration files from the environment of the tablet owner based on the applications and system accounts installed by the owner. The employer controls the launch of new configuration files in the installed application, which by default is disabled to access the owner's account.

The application needs to access the owner's account-sign-in, preference, or other purposes-you can choose to view and manage the configuration file settings of these applications by declaring an obvious attribute, and the owner can view and manage the configuration file settings of these applications.

For developers, restrictions on configuration files provide a new way to provide more value and user control. You can implement application restrictions-Control of content or functions supported by your application-and publish configuration settings in the tablet user configuration file.

You can add application restrictions, directly configure file configuration settings, use pre-defined Boolean, select, and select multiple types. If you want to learn more about the flexibility, you can even launch your own UI to provide any type restrictions from configuration file configuration settings.

When your application runs in a configuration file, it can check that the configuration is restricted by the owner and execute them as appropriate. For example, a media application may provide a limit for setting the owner maturity level. At runtime, the application can check the maturity settings and then manage the content based on the preferred maturity level.

If your application is not designed to be used in a restricted profile, you can exit completely so that your application cannot enable any restrictive profile.

Optimized location and sensor functions

The Google Play Service provides an advanced location where you can use APIs in your applications. Android 4.3 is optimized to support devices with new hardware and software features, minimizing battery usage of these Apis.

Hardware geo-fencing optimizes the power efficiency of mobile devices for location computing, rather than in software. When the device supports hardware geo-fencing, Google Play's geo-fencing API will be able to use this optimized device to move while saving battery.

The scan Wi-Fi-only mode is a new platform optimization that allows users to retain wi-fi scans without connecting to the Wi-Fi network to improve positioning accuracy, saving battery at the same time. Applications that rely on the Wi-Fi wireless location service can now require users to enable scan-only mode in advanced Wi-Fi settings. Wireless Network connections are only available in scan mode and are not part of the Android 4.3 platform that relies on hardware devices.

The new sensor type allows applications to better manage sensor readings. A game rotation vector allows game developers to detect the rotation of devices without worrying about magnetic interference. Original measurement reports for uncalibrated gyroscope and uncalibrated magnetic sensors, and estimated deviations in applications.

New hardware features have been available on Nexus 72013) and Nexus 4 devices, any device manufacturer or chip manufacturer can build their own devices.

New media features modular DRM framework

To meet the needs of next-generation media services, Android 4.3 adopts a modular DRM framework, making it easier for media application developers to integrate their own streaming media protocols, for example, mpeg dash uses HTTP's dynamic adaptive stream, ISO/IEC 23009's DRM-1 ).

With the combination of new APIs and enhanced existing APIs, the Media DRM framework provides an integrated service license management and configuration to access low-level codecs and decode encrypted media data. A new MediaExtractor API allows you to obtain PSSH metadata for DASH media. Use the Media DRM framework application to manage the license server, network communication, and process encrypted data streams from the content library.

VP8 Encoder

Android 4.3 introduces the built-in support for VP8 encoding and accesses from the framework and local APIs. For applications that use local APIs, the platform includes the OpenMAX 1.1.2 extension header and supports VP8 profiles and levels. Supports setting of target bit rate, control rate, frame rate, Token partition, error recovery, reconstruction, and loop filter for VP8 encoding. This platform API introduces the VP8 encoder supports various formats, so you can use the best format content.

VP8 encoding is a software that can run Android 4.3 On all compatible devices. To achieve the highest performance, the platform also supports hardware-accelerated VP8 encoding devices.

Video Encoding from the surface

In Android 4.3, you can use a surface as the input of the video encoder. For example, you can now directly copy from the surface stream of OpenGL ES, rather than between buffers.

Media MUXER

Applications can combine the basic audio and video streams of the new media muxer api into a single output file. Currently, applications can reuse MPEG-4 audio streams and a single MPEG-4 video stream into a single MPEG-4 output file. The new API corresponds to the media resolution API introduced in Android 4.2.

Remote Control of client playback progress and washing

Since Android 4.0, media players and similar applications have been able to provide playback control, such as remote control of the client device lock screen, notifications and remote devices connected via Bluetooth. These applications can start on Android 4.3 and now publish the playback progress and speed. You can remotely control the client and receive commands to jump to a specific playing position.

Notice on a new way to build a better application

Notifications have always been a popular Android feature because they allow users to view information and update the entire system. Now in Android 4.3, the app can observe the stream with the user's license notification and display the notification in any way they want, including sending them to nearby devices for Bluetooth connection.

You can access the new API so that you can register a notification listener service and user permission. They are displayed in the status bar to receive notifications. Notifications are delivered to you fully, with all the details on the original application, posting time, content views and styles, and priority. You can evaluate the interest in the notification, process field, or from your application, and display them as routed in any way you choose to add context.

New APIs are added, updated, and deleted when you receive callback notifications, either because of user rejection or original application exit ). You will be able to launch any notification or intention of its action, and close it from the system, giving your application a complete user interface notification.

The user still controls which applications can receive notifications. At any time, they can see the settings, view which applications have notifications, and enable or disable access as needed. By default, notification access is disabled-the application can use a new intent to enable the listening service after the user directly sets the installation.

Overwrite

Now, you can create a temporary view on the top of the ViewGroup with transparent overlay views to present a "level or short-lived animation effect, without interfering with the underlying layout level. Overwriting is especially useful when you want to create an animation, such as slide in view of its container or drag the project on the screen without affecting the view hierarchy.

Optical Layout

A new layout mode allows your ViewGroup to internally manage positioning and view based on its optical boundaries, rather than their editing boundaries. The editing world represents the actual outer boundary of a part, while the new optical world describes the appearance of a part within the editing range ,. You can use the optical layout mode to correctly align external visual effects such as shadow and halo components.

Custom rotation animation type

The application can now define a window when the entry-exit animation type is used on the rotating device. You can set window properties to make the switch, fade in and out, or rotate the standard window. The system uses a Custom Animation type when the window is full screen or not covered by other windows.

Screen direction mode

Applications can set new direction activities to ensure they are in the correct direction when the device is flipped in display mode. In addition, applications can use a new mode to lock the screen and its current direction. This is very useful when apps use cameras to disable rotation while shooting videos.

Quick Response to Letter of Intent handling

Android 4.3 introduces a new public intent that allows any application to process rapid responses-the user sends text messages and calls to respond without needing to pick up the phone or unlock the device. Your application can listen to the intent and send a message to the caller from your email system. This includes the recipient's incoming call) and the message itself.

Support international users

More RTL languages optimized for Android 4.3.

RTL Improvement

Android 4.3 RTL performance enhancement and wider RTL support for cross-framework UI components, including progress/fine-tuning and ExpandableListView. More debugging information can be seen through the uiautomatorviewer tool. In addition, more and more system UI components are now RTL attention, such as notifications, navigation bar and operation bar.

The RTL script provides better system-level experience. More default applications now support RTL layout, including transmitters, quick settings, phones, people, Installation Wizard, clock, download, and more.

Localized Utility

The pseudo-language environment makes it easier to test the localization of your applications.

Android 4.3 also includes new applications and APIs for creating better RTL strings and localized user interface tests. A new BidiFormatter wraps Unicode strings so that you can fine-tune your text rendering by providing a simple set of APIs in RTL scripts. To allow you to use this utility more extensively in your applications, the BidiFormatter API can now be used for earlier versions of platforms to support packages through the Android SDK.

To help you manage the date formats set across regions, including a new Android 4.3 getBestDateTimePattern) method, you can automatically generate a Unicode UTS date that is the best localized form for the specified region. This is a convenient way to provide more localization experience for your users.

To help you test your applications, it is easier to introduce a pseudo-language environment to Android 4.3 in other language environments as a new development option. Displays the characteristics of a simulated language, script, and a region setting or language group. Currently, you can test English with a pseudo accent, which allows you to see how your user interface is used with scripts in a variety of European language accents and character Language Environments.

Auxiliary Functions and UI Automation

Starting from Android 4.3, the secondary service can observe and filter key events, such as handling keyboard shortcuts, or provide gesture-based input navigation parity. Before the events received by the service and processed, they are passed to the system or other installed applications as needed.

Accessibility services can declare new feature properties to describe what their services can do and what platform features they use. For example, they can declare capabilities, filter key events, retrieve window content, enable exploration touch, or enable Network accessibility. In some cases, the Service must declare a capability attribute to access the functions of the platform. The system generates a Select User dialog box using the service's capability attribute to show them and agree to the capabilities before launching.

Based on the auxiliary function framework on Android 4.3, a new UI automation framework allows UI interaction between test devices by simulating user operations and saving the screen content. Through the UI automation framework, you can perform basic operations, set screen rotation, generate input events, take, and so on. This is a powerful user in reality, including automated testing across multiple application behavior or sequences.

WPA2 for enterprise and secure Wi-Fi

Applications can now configure wireless network creden。 and they need to connect to the WPA2 Enterprise Access Point. Developers can use the new API to configure the Scalable authentication protocol EAP) the authentication method used in the enterprise and the encapsulated EAP Phase II) credential. Applications with the right to access and change Wi-Fi can configure authentication creden。 for various EAP and 2nd-phase authentication methods.

Sandbox and SELinux enhancement for Android

Currently, Android uses SELinux to forcibly control MAC access. The UID is added to the Linux Kernel Based on the Application sandbox. This protects the operating system against potential security vulnerabilities.

Key chain enhancement

The current key chain API provides a way for applications to confirm the hardware trust Root of the device to which the system full key is bound. This provides a local device that creates or stores private keys that cannot be exported, even in a root or kernel compromise event.

Key library for Android provides

Android 4.3 introduces an API of the keystore provider, allowing applications to create exclusive keys. Using APIs, applications can create or store private keys that cannot be viewed or used by other applications, and can be added to a keystore without any user interaction.

The key chain APIs provided by the keystore supplier share the same security advantages, providing full-system creden。, such as binding creden。 to devices. You cannot export the private key library to close the device.

Restrict the setuid of an Android Application

/Install nosuid in the system partition to prevent the setuid Program executed by the Android Application. This attack surface and potential security vulnerabilities are less likely.

New methods for analyzing performance

Using a new command syntax, you can collect more types of analysis data.

Enhanced systrace records

The systrace tool that supports enhanced Android 4.3 is easier to use, allowing you to access more types of information to analyze the performance of your applications. Now, you can collect trace data from the hardware module and kernel functions of the Dalvik virtual machine, including garbage collection, resource loading, and collection.

Android 4.3 also includes new tracing APIs. You can tag specific code segments in your application to track start/end events using systrace. When the marked code segment is executed, the system start/end event is written to the tracking log. The performance impact of your application is minimal, so timing reports give you an accurate view of what your application is doing.

You can imagine the events of a specific application in the systrace output file of the timeline, and analyze the tracking data of other kernels and user spaces in the context of the event. Together with the existing systrace tags, the Custom Application Section provides you with new methods to understand the performance and behavior of your application.

GPU analysis on the Android 4.3 screen.

GPU analysis on the screen

Android 4.3 adds a new development solution to help you analyze the performance of your application and precisely render problems to any device or simulator.

In the personal data GPU rendering "option, you can now visualize the Effective Frame Rate screen of your application when the application is running. You can select a bar chart or line chart on the screen to display the analysis data, and use different colors to indicate the time spent in creating the drawing command blue), issue the command orange), and wait for the command to complete the yellow ). The system updates the graphics on the screen to continuously display the graphics for each visible activity, including the navigation bar and notification bar.

A green line highlights the 60 ms threshold for rendering operations, so you can evaluate the relatively effective Frame Rate of your application to a target of 60 fps. If you see operations that go beyond the Green Line, you can analyze the systrace and other tools they are further using.

On devices running Android 4.2 and later, development options are hidden by default. You can reveal 7 times the number of compatible Android devices they have created at any time by clicking Settings> about mobile phone>.

Strict mode StrictMode) URI of the warning File

The latest strict mode StrictMode) tool is a policy constraint that warns the system or other applications of exposing a file: // URI. In some cases, when receiving files that applications may not be able to access: // URI path, you should use: // URI to share files between applications ). This new policy can help you seize and solve such cases. If you are looking for a convenient way to store and publish files to other applications, try using the FileProvider's support library.

From: http://blog.csdn.net/sunny2come/article/details/9471411