xref: /frameworks/base/docs/html/about/versions/jelly-bean.jd

page.title=Jelly Bean
tab1=Android 4.3
tab1.link=#android-43
tab2=Android 4.2
tab2.link=#android-42
tab3=Android 4.1
tab3.link=#android-41

@jd:body
<div id="butterbar-wrapper" >
  <div id="butterbar" >
    <div id="butterbar-message">
<a target="_blank" href="https://docs.google.com/a/google.com/forms/d/1EHLPGqhbxj2HungHRRN4_0K9TGpc-Izy-u46vBDgS8Q/viewform">
      Take the Android Developer Survey</a>
    </div>
  </div>
</div>

<style>
#android-41 {display:none;}
#android-42 {display:none;}
</style>

<script>
function revealSection(hashy) {
  if (hashy != "" && !$(hashy).is(":visible")) {
    sectionId = $(hashy).closest(".version-section").attr("id");
    link = $("#title-tabs a[href$="+sectionId+"]");
    link.parent().addClass("selected");
    link.parent().siblings().removeClass("selected");
    
    sectionDiv = $(".version-section"+link.attr("href"));
    if (sectionDiv.length) {
      $(".version-section").hide();
      sectionDiv.show();
    }
    
    $('html, body').animate({
         scrollTop: $(hashy).offset().top
     }, 100);
  }
}

$(document).ready(function() {
  $("#title-tabs li a").each(function() {
    $(this).click(function(){
      $(this).parent().addClass("selected");
      $(this).parent().siblings().removeClass("selected");
      $(".version-section").hide();
      $($(this).attr("href")).show();
      return false;
    });
  });

  hashy = escapeHTML(location.hash);
  revealSection(hashy);
});

window.onhashchange = function () {
  revealSection(escapeHTML(location.hash));
}

</script>


<!-- BEGIN ANDROID 4.3 -->
<div id="android-43" class="version-section">

<div style="float:right;padding:0px 0px 10px 28px;width:480px;">
<div>
<a href="{@docRoot}images/jb-android-43@2x.png"><img src="{@docRoot}images/jb-android-43.jpg" alt="Android 4.3 on phone and tablet" width="472"></a>

</div>
</div>
<p>Welcome to Android 4.3, a sweeter version of <span
style="white-space:nowrap;">Jelly Bean!</span></p>

<p>Android 4.3 includes performance optimizations and great
new features for users and developers. This document provides a glimpse of what's new for
developers.

<p>See the <a href="{@docRoot}about/versions/android-4.3.html">Android 4.3 APIs</a>
document for a detailed look at the new developer APIs.</p>

<p>Find out more about the new Jelly Bean features for users at <a
href="http://www.android.com/whatsnew">www.android.com</a>.</p>


<h2 id="43-performance" style="line-height:1.25em;">Faster, Smoother, More
Responsive</h2>

<p>Android 4.3 builds on the performance improvements already included in Jelly
Bean &mdash; <strong>vsync timing</strong>, <strong>triple buffering</strong>,
<strong>reduced touch latency</strong>, <strong>CPU input boost</strong>, and
<strong>hardware-accelerated 2D rendering</strong> &mdash; and adds new
optimizations that make Android even faster.</p>

<p>For a graphics performance boost, the hardware-accelerated 2D renderer now
<strong>optimizes the stream of drawing commands</strong>, transforming it into
a more efficient GPU format by rearranging and merging draw operations. For
multithreaded processing, the renderer can also now use <strong>multithreading
across multiple CPU cores</strong> to perform certain tasks.</p>

<p>Android 4.3 also improves <strong>rendering for shapes and text</strong>.
Shapes such as circles and rounded rectangles are now rendered at higher quality
in a more efficient manner. Optimizations for text include increased performance
when using multiple fonts or complex glyph sets (CJK), higher rendering quality
when scaling text, and faster rendering of drop shadows.</p>

<p><strong>Improved window buffer allocation</strong> results in a faster image
buffer allocation for your apps, reducing the time taken to start rendering when
you create a window.</p>

<p>For highest-performance graphics, Android 4.3 introduces support for
<strong>OpenGL ES 3.0</strong> and makes it accessible to apps through both
framework and native APIs. On supported devices, the hardware accelerated 2D
rendering engine takes advantage of OpenGL ES 3.0 to optimize <strong>texture
management</strong> and increase <strong>gradient rendering
fidelity</strong>.</p>


<h2 id="43-graphics">OpenGL ES 3.0 for High-Performance Graphics</h2>

<p>Android 4.3 introduces platform support for <a class="external-link"
href="http://www.khronos.org/opengles/3_X/" target="_android">Khronos OpenGL ES 3.0</a>,
providing games and other apps with highest-performance 2D and 3D graphics
capabilities on supported devices. You can take advantage of OpenGL ES 3.0
and related EGL extensions using either <strong>framework APIs</strong>
or <strong>native API bindings</strong> through the Android Native Development
Kit (NDK).</p>

<p>Key new functionality provided in OpenGL ES 3.0 includes acceleration of
advanced visual effects, high quality ETC2/EAC texture compression as a standard
feature, a new version of the GLSL ES shading language with integer and 32-bit
floating point support, advanced texture rendering, and standardized texture
size and render-buffer formats.

<p>You can use the OpenGL ES 3.0 APIs to create highly complex, highly efficient
graphics that run across a range of compatible Android devices, and you can
support a single, standard texture-compression format across those devices.</p>

<p>OpenGL ES 3.0 is an optional feature that depends on underlying graphics
hardware. Support is already available on Nexus 7 (2013), Nexus 4, and
Nexus 10 devices.</p>


<h2 id="43-bluetooth" style="clear:both;">Enhanced Bluetooth Connectivity</h2>

<h4 id="43-bt-le">Connectivity with Bluetooth Smart devices and sensors</h4>

<p>Now you can design and build apps that interact with the latest generation
of small, low-power devices and sensors that use <a
href="http://www.bluetooth.com/Pages/Bluetooth-Smart-Devices.aspx"
class="external-link" target="_android">Bluetooth Smart technology</a>. </p>

<div style="float:right;margin:0px 0px 32px 0px;width:460px;">
<img src="{@docRoot}images/jb-btle.png" alt="" width="450" style="padding-left:1.5em;margin-bottom:0">
<p class="img-caption" style="padding-top:1.5em;line-height:1.25em;margin-bottom:0;padding-left:1.5em;">Android 4.3 gives you a single, standard API for interacting with Bluetooth Smart devices. </p>
</div>

<p>Android 4.3 introduces built-in platform support for <strong>Bluetooth Smart
Ready</strong> in the central role and provides a standard set of APIs that
apps can use to discover nearby devices, query for GATT services, and read/write
characteristics.</p>

<p>With the new APIs, your apps can efficiently scan for devices and services of
interest. For each device, you can check for supported GATT services by UUID and
manage connections by device ID and signal strength. You can connect to a GATT
server hosted on the device and read or write characteristics, or register a
listener to receive notifications whenever those characteristics change.</p>

<p>You can implement support for any GATT profile. You can read or write
standard characteristics or add support for custom characteristics as needed.
Your app can function as either client or server and can transmit and receive
data in either mode. The APIs are generic, so you’ll be able to support
interactions with a variety of devices such as proximity tags, watches, fitness
meters, game controllers, remote controls, health devices, and more.
</p>

<p>Support for Bluetooth Smart Ready is already available on Nexus 7 (2013)
and Nexus 4 devices and will be supported in a growing number of
Android-compatible devices in the months ahead.</p>

<h4 id="43-bt-avrcp">AVRCP 1.3 Profile</h4>

<p>Android 4.3 adds built-in support for <strong>Bluetooth AVRCP 1.3</strong>,
so your apps can support richer interactions with remote streaming media
devices. Apps such as media players can take advantage of AVRCP 1.3 through the
<strong>remote control client APIs</strong> introduced in Android 4.0. In
addition to exposing playback controls on the remote devices connected over
Bluetooth, apps can now transmit metadata such as track name, composer, and
other types of media metadata. </p>

<p>Platform support for AVRCP 1.3 is built on the Bluedroid Bluetooth stack
introduced by Google and Broadcom in Android 4.2. Support is available right
away on Nexus devices and other Android-compatible devices that offer A2DP/AVRCP
capability. </p>


<h2 id="43-profiles">Support for Restricted Profiles</h2>

<div style="float:right;margin:22px 0px 0px 24px;width:340px;">
<img src="{@docRoot}images/jb-profiles-create-n713.png" alt="Setting up a Restricted Profile" width="340" style="margin-bottom:0">
<p class="img-caption" style="padding-top:1.5em;line-height:1.25em;margin-bottom:0;">A tablet owner can set up one or more restricted profiles in Settings and manage them independently. </p>
<img src="{@docRoot}images/jb-profiles-restrictions-n713.png" alt="Setting Restrictions in a Profile" width="340" style="margin-bottom:0;padding-top:1em;">
<p class="img-caption" style="padding-top:1.5em;line-height:1.25em;">Your app can offer restrictions to let owners manage your app content when it's running in a profile. </p>
</div>

<p>Android 4.3 extends the multiuser feature for tablets with <strong>restricted
profiles</strong>, a new way to manage users and their capabilities on a single
device. With restricted profiles, tablet owners can quickly set up
<strong>separate environments</strong> for each user, with the ability to
manage <strong>finer-grained restrictions</strong> in the apps that are
available in those environments. Restricted profiles are ideal for friends and
family, guest users, kiosks, point-of-sale devices, and more. </p>

<p>Each restricted profile offers an isolated and secure space with its own
local storage, home screens, widgets, and settings. Unlike with
users, profiles are created from the tablet owner’s environment, based on the
owner’s installed apps and system accounts. The owner controls which installed
apps are enabled in the new profile, and access to the owner’s accounts is
disabled by default. </p>

<p>Apps that need to access the owner’s accounts &mdash; for sign-in,
preferences, or other uses &mdash; can opt-in by declaring a manifest attribute,
and the owner can review and manage those apps from the profile configuration
settings.</p>

<p>For developers, restricted profiles offer a new way to deliver more value and
control to your users. You can implement <strong>app restrictions</strong>
&mdash; content or capabilities controls that are supported by your app &mdash;
and advertise them to tablet owners in the profile configuration settings.
</p>

<p>You can add app restrictions directly to the profile configuration settings
using predefined boolean, select, and multi-select types. If you want more
flexibility, you can even launch your own UI from profile configuration settings
to offer any type of restriction you want. </p>

<p>When your app runs in a profile, it can check for any restrictions configured
by the owner and enforce them appropriately. For example, a media app
might offer a restriction to let the owner set a maturity level for the profile.
At run time, the app could check for the maturity setting and then manage
content according to the preferred maturity level. </p>

<p>If your app is not designed for use in restricted profiles, you can opt
out altogether, so that your app can't be enabled in any restricted profile.</p>


<h2 id="43-optimized-location">Optimized Location and Sensor Capabilities</h2>

<p><a href="{@docRoot}google/play-services/index.html">Google Play services</a>
offers advanced location APIs that you can use in your apps. Android 4.3
<strong>optimizes these APIs</strong> on supported devices with new hardware and
software capabilities that minimize use of the battery. </p>


<div style="float:left;margin:22px 24px 36px 22px;width:250px;">
<a href=""><img src="{@docRoot}images/google/gps-location.png" alt="" height="160" style="padding-right:1.5em;margin-bottom:0"></a>
</div>

<p><strong>Hardware geofencing</strong> optimizes for power efficiency by
performing location computation in the device hardware, rather than in
software. On devices that support hardware geofencing, Google Play services
geofence APIs will be able to take advantage of this optimization to save
battery while the device is moving. </p>

<p><strong>Wi-Fi scan-only mode</strong> is a new platform optimization that
lets users keep Wi-Fi scan on without connecting to a Wi-Fi network, to improve
location accuracy while conserving battery. Apps that depend on Wi-Fi for
location services can now ask users to enable scan-only mode from Wi-Fi
advanced settings. Wi-Fi scan-only mode is not dependent on device hardware and
is available as part of the Android 4.3 platform.</p>

<p>New sensor types allow apps to better manage sensor readings. A <strong>game
rotation vector</strong> lets game developers sense the device’s rotation
without having to worry about magnetic interference.  <strong>Uncalibrated
gyroscope</strong> and <strong>uncalibrated magnetometer</strong> sensors report
raw measurements as well as estimated biases to apps. </p>

<p>The new hardware capabilities are already available on Nexus 7 (2013) and
Nexus 4 devices, and any device manufacturer or chipset vendor can build them
into their devices.</p>


<h2 id="43-media">New Media Capabilities</h2>

<h4 id="43-modular-drm">Modular DRM framework</h4>

<p>To meet the needs of the next generation of media services, Android 4.3
introduces a <strong>modular DRM framework</strong> that enables media application
developers to more easily integrate DRM into their own streaming protocols, such
as MPEG DASH (Dynamic Adaptive Streaming over HTTP, ISO/IEC 23009-1).</p>

<p>Through a combination of new APIs and enhancements to existing APIs, the
media DRM framework provides an <strong>integrated set of services</strong> for
managing licensing and provisioning, accessing low-level codecs, and decoding
encrypted media data. A new MediaExtractor API lets you get the PSSH metadata
for DASH media. Apps using the media DRM framework manage the network
communication with a license server and handle the streaming of encrypted data
from a content library. </p>

<h4 id="43-vp8-encoder">VP8 encoder</h4>

<p>Android 4.3 introduces built-in support for <strong>VP8 encoding</strong>,
accessible from framework and native APIs. For apps using native APIs, the
platform includes <strong>OpenMAX 1.1.2 extension headers</strong> to support
VP8 profiles and levels. VP8 encoding support includes settings for target
bitrate, rate control, frame rate, token partitioning, error resilience,
reconstruction and loop filters. The platform API introduces VP8 encoder support
in a range of formats, so you can take advantage of the best format for your
content. </p>

<p>VP8 encoding is available in software on all compatible devices running
Android 4.3. For highest performance, the platform also supports
hardware-accelerated VP8 encoding on capable devices.</p>

<h4 id="43-surface">Video encoding from a surface</h4>

<p>Starting in Android 4.3 you can use a surface as the input to a video
encoder. For example, you can now direct a stream from an OpenGL ES surface
to the encoder, rather than having to copy between buffers.</p>

<h4 id="43-media-muxer">Media muxer</h4>

<p>Apps can use new media muxer APIs to combine elementary audio and video
streams into a single output file. Currently apps can multiplex a single MPEG-4
audio stream and a single MPEG-4 video stream into a <strong>single MPEG-4 ouput
file</strong>. The new APIs are a counterpart to the media demuxing APIs
introduced in Android 4.2. </p>

<h4 id="43-progress-scrubbing">Playback progress and scrubbing in remote control
clients</h4>

<p>Since Android 4.0, media players and similar applications have been able to
offer playback controls from remote control clients such as the device lock
screen, notifications, and remote devices connected over Bluetooth. Starting in
Android 4.3, those applications can now also expose playback <strong>progress
and speed</strong> through their remote control clients, and receive commands to
jump to a specific <strong>playback position</strong>. </p>


<h2 id="43-beautiful-apps">New Ways to Build Beautiful Apps</h2>


<h3 id="43-notification-access">Access to notifications</h3>

<p>Notifications have long been a popular Android feature because they let users
see information and updates from across the system, all in one place. Now in
Android 4.3, apps can <strong>observe the stream of notifications</strong> with the
user's permission and display the notifications in any way they want, including
sending them to nearby devices connected over Bluetooth. </p>

<p>You can access notifications through new APIs that let you <strong>register a
notification listener</strong> service and with permission of the user, receive
notifications as they are displayed in the status bar. Notifications are
delivered to you in full, with all details on the originating app, the post
time, the content view and style, and priority. You can evaluate fields of
interest in the notifications, process or add context from your app, and route
them for display in any way you choose.</p>

<p>The new API gives you callbacks when a notification is added, updated, and
removed (either because the user dismissed it or the originating app withdrew it).
You'll be able to launch any intents attached to the notification or its actions,
as well as dismiss it from the system, allowing your app to provide a complete
user interface to notifications.</p>

<p><strong>Users remain in control</strong> of which apps can receive
notifications. At any time, they can look in Settings to see which apps have
notification access and <strong>enable or disable access</strong> as needed.
Notification access is disabled by default &mdash; apps can use a new Intent to
take the user directly to the Settings to enable the listener service after
installation.</p>

<h4 id="43-view-overlays">View overlays</h4>

<p>You can now create <strong>transparent overlays</strong> on top of Views and
ViewGroups to render a temporary View hierarchy or transient animation effects
without disturbing the underlying layout hierarchy. Overlays are particularly
useful when you want to create animations such as sliding a view outside of its
container or dragging items on the screen without affecting the view
hierarchy. </p>

<h4 id="43-optical-bounds">Optical bounds layout mode</h4>

<p>A new layout mode lets you manage the positioning of Views inside ViewGroups
according to their <strong>optical bounds</strong>, rather than their clip
bounds. Clip bounds represent a widget’s actual outer boundary, while the new
optical bounds describe the where the widget appears to be, within the clip
bounds. You can use the optical bounds layout mode to properly align widgets
that use outer visual effects such as shadows and glows.</p>

<h4 id="43-rotation-animation">Custom rotation animation types</h4>

<p>Apps can now define the exit and entry animation types used on a window when the
device is rotated. You can set window properties to enable
<strong>jump-cut</strong>, <strong>cross-fade</strong>, or
<strong>standard</strong> window rotation. The system uses the custom animation
types when the window is fullscreen and is not covered by other windows.</p>

<h4 id="43-screen-orientations">Screen orientation modes</h4>

<p>Apps can set new orientation modes for Activities to ensure that they are
displayed in the proper orientation when the device is flipped. Additionally,
apps can use a new mode to <strong>lock the screen</strong> to its current
orientation. This is useful for apps using the camera that want to
<strong>disable rotation</strong>  while shooting video. </p>

<h4 id="43-quick-responses-intent">Intent for handling Quick Responses</h4>

<p>Android 4.3 introduces a new public Intent that lets any app <strong>handle
Quick Responses</strong> &mdash; text messages sent by the user in response to
an incoming call, without needing to pick up the call or unlock the device. Your
app can listen for the intent and send the message to the caller over your
messaging system. The intent includes the recipient (caller) as well as the
message itself. </p>


<h2 id="43-intl">Support for International Users</h2>

<div style="float:right;margin:22px 0px 0px 24px;width:380px;">
<img src="{@docRoot}images/jb-rtl-arabic-n4.png" alt="" width="180" style="margin-bottom:0;">
<img src="{@docRoot}images/jb-rtl-hebrew-n4.png" alt="" width="180" style="margin-bottom:0;padding-left:10px;">
<p class="img-caption" style="padding-top:1.5em;line-height:1.25em;">More parts of Android 4.3 are optimized for RTL languages.</p>
</div>

<h4 id="43-rtl">RTL improvements</h4>

<p>Android 4.3 includes RTL performance enhancements and broader RTL support
across framework UI widgets, including ProgressBar/Spinner and
ExpandableListView. More debugging information visible through the
<code>uiautomatorviewer</code> tool. In addition, more system UI components are
now RTL aware, such as notifications, navigation bar and the Action Bar.</p>

<p>To provide a better systemwide experience in RTL scripts, more default system
apps now support RTL layouts, including Launcher, Quick Settings, Phone, People,
SetupWizard, Clock, Downloads, and more.</p>

<h4 id="43-localization">Utilities for localization</h4>

<div style="float:right;margin:16px 12px 0px 32px;width:260px;clear:both;">
<img src="{@docRoot}images/jb-pseudo-locale-zz.png" alt="" width="260" style="margin-bottom:0;">
<p class="img-caption" style="padding-top:1.5em;line-height:1.25em;">Pseudo-locales make it easier to test your app's localization.</p>
</div>

<p>Android 4.3 also includes new utilities and APIs for creating better RTL
strings and testing your localized UIs. A new <strong>BidiFormatter</strong>
provides a set of simple APIs for wrapping Unicode strings so that you can
fine-tune your text rendering in RTL scripts. To let you use this utility more
broadly in your apps, the BidiFormatter APIs are also now available for earlier
platform versions through the Support Package in the Android SDK. </p>

<p>To assist you with managing date formatting across locales, Android 4.3
includes a new <strong>getBestAvaialbleDate()</strong> method that automatically
generates the best possible localized form of a Unicode UTS date for a locale
that you specify. It’s a convenient way to provide a more localized experience
for your users. </p>

<p>To help you test your app more easily in other locales, Android 4.3
introduces <strong>pseudo-locales</strong> as a new developer option.
Pseudo-locales simulate the language, script, and display characteristics
associated with a locale or language group. Currently, you can test with a
pseudo-locale for <strong>Accented English</strong>, which lets you see how your
UI works with script accents and characters used in a variety of European
languages. <!--To use the pseudo-locale, enable “Developer options” in Settings
and then select Accented English from Language and Input settings. --></p>


<h2 id="43-accessibility">Accessibility and UI Automation</h2>

<p>Starting in Android 4.3, accessibility services can <strong>observe and
filter key events</strong>, such as to handle keyboard shortcuts or provide
navigation parity with gesture-based input. The service receives the events and
can process them as needed before they are passed to the system or other
installed apps.</p>

<p>Accessibility services can declare <strong>new capability attributes</strong>
to describe what their services can do and what platform features they use. For
example, they can declare the capability to filter key events, retrieve window
content, enable explore-by-touch, or enable web accessibility features. In some
cases, services must declare a capability attribute before they can access
related platform features. The system uses the service’s capability attributes
to generate an opt-in dialog for users, so they can see and agree to the
capabilities before launch.</p>

<p>Building on the accessibility framework in Android 4.3, a new <strong>UI
automation framework</strong> lets tests interact with the device’s UI by
simulating user actions and introspecting the screen content. Through the UI
automation framework you can perform basic operations, set rotation of the
screen, generate input events, take screenshots, and much more. It’s a powerful
way to automate testing in realistic user scenarios, including actions or
sequences that span multiple apps.</p>


<h2 id="43-enterprise-security">Enterprise and Security</h2>

<h4 id="43-wpa2">Wi-Fi configuration for WPA2-Enterprise networks</h4>

<p>Apps can now configure the <strong>Wi-Fi credentials</strong> they need for
connections to <strong>WPA2 enterprise access points</strong>. Developers can
use new APIs to configure Extensible Authentication Protocol (EAP) and
Encapsulated EAP (Phase 2) credentials for authentication methods used in the
enterprise. Apps with permission to access and change Wi-Fi can configure
authentication credentials for a variety of EAP and Phase 2 authentication
methods. </p>

<h4 id="43-selinux">Android sandbox reinforced with SELinux</h4>

<p>Android now uses <strong>SELinux</strong>, a mandatory access control (MAC)
system in the Linux kernel to augment the UID based application sandbox.
This protects the operating system against potential security vulnerabilities.</p>

<h4 id="43-keychain">KeyChain enhancements</h4>

<p>The KeyChain API now provides a method that allows applications to confirm
that system-wide keys are bound to a <strong>hardware root of trust</strong> for
the device.  This provides a place to create or store private keys that
<strong>cannot be exported</strong> off the device, even in the event of a root or
kernel compromise.</p>

<h4 id="43-keystore">Android Keystore Provider</h4>

<p>Android 4.3 introduces a keystore provider and APIs that allow applications
to create exclusive-use keys. Using the APIs, apps can create or store private
keys that <strong>cannot be seen or used by other apps</strong>, and can be
added to the keystore without any user interaction. </p>

<p>The keystore provider provides the same security benefits that the KeyChain
API provides for system-wide credentials, such as binding credentials to a
device. Private keys in the keystore cannot be exported off the device.</p>

<h4 id="43-seuid">Restrict Setuid from Android Apps</h4>

<p>The <code>/system</code> partition is now mounted <code>nosuid</code> for
zygote-spawned processes, preventing Android applications from executing
<code>setuid</code> programs. This reduces root attack surface and likelihood of
potential security vulnerabilities.</p>


<h2 id="43-tools">New Ways to Analyze Performance</h2>

<div style="float:right;margin:16px 6px 0px 32px;width:390px;">
<img src="{@docRoot}images/jb-systrace.png" alt="" width="390" style="margin-bottom:0;">
<p class="img-caption" style="padding-top:1.5em;line-height:1.25em;">Systrace uses a new command syntax and lets you collect more types of profiling data.</p>
</div>

<h4 id="43-systrace">Enhanced Systrace logging</h4>

<p>Android 4.3 supports an enhanced version of the <strong>Systrace</strong>
tool that’s easier to use and that gives you access to more types of information
to profile the performance of your app. You can now collect trace data from
<strong>hardware modules</strong>, <strong>kernel functions</strong>,
<strong>Dalvik VM</strong> including garbage collection, <strong>resources
loading</strong>, and more. </p>

<p>Android 4.3 also includes new Trace APIs that you can use in your apps to mark
specific sections of code to trace using Systrace <strong>begin/end
events</strong>. When the marked sections of code execute, the system writes the
begin/end events to the trace log. There's minimal impact on the performance of
your app, so timings reported give you an accurate view of what your app is
doing.</p>

<p>You can visualize app-specific events in a timeline in the Systrace output
file and analyze the events in the context of other kernel and user space trace
data. Together with existing Systrace tags, custom app sections can give you new
ways to understand the performance and behavior of your apps.</p>

<div style="float:right;margin:6px 0px 0px 32px;width:380px;">
<img src="{@docRoot}images/jb-gpu-profile-clk-n4.png" alt="" width="180" style="margin-bottom:0;">
<img src="{@docRoot}images/jb-gpu-profile-cal-n4.png" alt="" width="180" style="margin-bottom:0;padding-left:10px;">
<p class="img-caption" style="padding-top:1.5em;line-height:1.25em;">On-screen GPU profiling in Android 4.3.</p>
</div>

<h4 id="43-gpu-profiling" >On-screen GPU profiling</h4>

<p>Android 4.3 adds new developer options to help you analyze your app’s
performance and pinpoint rendering issues on any device or emulator.</p>

<p>In the <strong>Profile GPU rendering</strong> option you can now visualize
your app’s effective framerate on-screen, while the app is running. You can
choose to display profiling data as on-screen <strong>bar or line
graphs</strong>, with colors indicating time spent creating drawing commands
(blue), issuing the commands (orange), and waiting for the commands to complete
(yellow). The system updates the on-screen graphs continuously, displaying a
graph for each visible Activity, including the navigation bar and notification
bar. </p>

<p>A green line highlights the <strong>60ms threshold</strong> for rendering
operations, so you can assess the your app’s effective framerate relative
to a 60 fps goal. If you see operations that cross the green line, you
can analyze them further using Systrace and other tools.</p>

<p class="caution" style="clear:both">On devices running Android 4.2 and higher,
developer options are hidden by default. You can reveal them at any time by
tapping 7 times on <strong>Settings &gt; About phone &gt; Build number</strong>
on any compatible Android device.</p>

<h4 id="43-strictmode">StrictMode warning for file URIs</h4>

<p>The latest addition to the StrictMode tool is a policy constraint that warns
when your app exposes a <code>file://</code> URI to the system or another app.
In some cases the receiving app may not have access to the <code>file://</code>
URI path, so when sharing files between apps, a <code>content://</code> URI should
be used (with the appropriate permission). This new policy helps you catch and fix
such cases. If you’re looking for a convenient way to store and expose files to other
apps, try using the <code>FileProvider</code> content provider that’s available
in the <a href="{@docRoot}tools/support-library/index.html">Support Library</a>.</p>

</div><!-- END ANDROID 4.3 -->
























<!-- BEGIN ANDROID 4.2 -->
<div id="android-42" class="version-section">
<div style="float:right;padding:0px 0px 12px 34px;">
<div>
<img src="{@docRoot}images/jb-device-2.png" alt="Android 4.2 on phone and tablet" height="348" width="400">
</div>
</div>
<p>Welcome to Android 4.2, the latest version of <span
style="white-space:nowrap;">Jelly Bean!</span></p>

<p>Android 4.2 has performance optimizations, a refreshed system UI, and great
new features for users and developers. This document provides a glimpse of what's new for
developers.

<p>See the <a href="{@docRoot}about/versions/android-4.2.html">Android 4.2 APIs</a>
document for a detailed look at the new developer APIs.</p>

<p>Find out more about the new Jelly Bean features for users at <a
href="http://www.android.com/whatsnew">www.android.com</a>.</p>


<h2 id="42-performance" style="line-height:1.25em;">Faster, Smoother, More Responsive</h2>

<p>Android 4.2 builds on the performance improvements already included in Jelly Bean
&mdash; <strong>vsync timing</strong>, <strong>triple buffering</strong>,
<strong>reduced touch latency</strong>, and <strong>CPU input boost</strong>
&mdash; and adds new optimizations that make Android even faster.</p>

<p>Improvements in the <strong>hardware-accelerated 2D renderer</strong> make
common animations such as scrolling and swiping smoother and faster. In
particular, <strong>drawing is optimized</strong> for layers, clipping and
certain shapes (rounded rects, circles and ovals).</p>

<p>A variety of <strong>WebView rendering optimizations</strong> make scrolling
of web pages smoother and free from jitter and lags.</p>

<p>Android’s <strong>Renderscript Compute</strong> is the first computation
platform ported to run directly on a <strong>mobile device GPU</strong>. It automatically
takes advantage of <strong>GPU computation</strong> resources whenever possible,
dramatically improving performance for graphics and image processing. Any app using
Renderscript on a supported device can benefit immediately from
this GPU integration <strong>without recompiling</strong>.</p>


<div style="float:left;margin:16px 24px 12px 0px;">
<a href="" target="_android">
<img src="{@docRoot}images/jb-nexus10-1.png" alt="10-inch tablet running Android 4.2" width="380" height="281" /></a>
</div> 

<h2 id="42-ui" style="margin-top:2em;">Refined, refreshed UI</h2>

<p>Android 4.2 refines the Jelly Bean user experience and brings familiar
Android UI patterns such as status bar, system bar, and notifications window to
all tablets.</p>

<p>All screen sizes now feature the <strong>status bar</strong> on top, with
pull-down access to <strong>notifications</strong> and a new <strong>Quick
Settings</strong> menu. The familiar </strong>system bar</strong> appears on the
bottom, with buttons easily accessible from either hand. The <strong>Application
Tray</strong> is also available on all screen sizes.</p>


<h2 id="42-multiuser" style="margin-top:2em;clear:left;">One tablet, many users</h2>

<p>Now several users can <strong>share a single Android tablet</strong>, with
each user having convenient access to a <strong>dedicated user
space</strong>. Users can switch to their spaces with a single touch from the
lock screen.</p>

<p>On a multiuser device, Android gives each user a separate environment,
including user-specific emulated SD card storage. Users also have their own
homescreens, widgets, accounts, settings, files, and apps, and the system keeps
these separate. All users share core system services, but the system ensures that
each user's applications and data remain isolated. In effect, each of the multiple
users has his or her own Android device.</p>

<p>Users can install and uninstall apps at any time in their own environments.
To save storage space, Google Play downloads an APK only if it's not already
installed by another user on the device. If the app is already installed, Google
Play records the new user's installation in the usual way but doesn't download
another copy of the app. Multiple users can run the same copy of an APK because
the system creates a new instance for each user, including a user-specific data
directory.</p>

<p>For developers, <strong>multi-user support is transparent</strong> &mdash;
your apps do not need to do anything special to run normally in a multi-user
environment and there are no changes you need to make in your existing or
published APKs. The system manages your app in each user space just as it does
in a single-user environment. </p>


<h2 id="42-engagement" style="clear:left; margin-top:1em;">New ways to engage users</h2>

<div style="float:right;margin:22px 0px 0px 24px;width:280px;">
<div>
<img src="{@docRoot}images/jb-lock-calendar.png" alt="Calendar lock screen widget" width="280" height="543" style="padding-left:1em;margin-bottom:0">
</div>
<p class="img-caption" style="padding-top:1.5em;line-height:1.25em;">You can extend <strong>app widgets</strong> to run on the lock screen, for instant access to your content.</p>
</div>

<h3 id="42-lockscreen-widgets">Lock screen widgets</h3>

<p>In Android 4.2, users can place <strong>app widgets</strong> directly on
their <strong>lock screens</strong>, for instant access to favorite app content
without having to unlock. Users can add as many as five lock screen widgets,
choosing from widgets provided by installed apps. The lock screen displays each
widget in its own panel, letting users swipe left and right to view different
panels and their widgets.</p>

<p>Like all app widgets, lock screen widgets can display <strong>any kind of content</strong> and
they can accept direct user interaction. They can be entirely self-contained,
such as a widget that offers controls to play music, or they can let users jump
straight to an Activity in your app, after unlocking along the way as
needed.</p>

<p>For developers, lock screen widgets offer a great new way to engage users.
They let you put your content in front of users in a location they’ll see often,
and they give you more opportunities to bring users directly into your app.</p>

<p>You can take advantage of this new capability by building a new app widget or
by extending an existing home screen widget. If your app already includes home
screen widgets, you can extend them to the lock screen with minimal change. To
give users an optimal experience, you can update the widget to use the full lock
screen area when available and resize when needed on smaller screens. You can
also add features to your widgets that might be especially useful or convenient
on the lock screen.</p>

<h3 id="42-daydreams">Daydream</h3>

<p>Daydream is an <strong>interactive screensaver mode</strong> that starts when
a user’s device is docked or charging. In this mode, the system launches a
daydream &mdash; a remote content service provided by an installed app &mdash;
as the device screensaver. A user can enable Daydream from the Settings app and
then choose the daydream to display.</p>

<p>Daydreams combine the best capabilities of live wallpapers and home screen
widgets, but they are more powerful. They let you offer the any kind of content
in a completely new context, with user interactions such as flipping through
photos, playing audio or video, or jumping straight into your app with a single
touch.</p>

<p>Because daydreams can start automatically when a device is charging or
docked, they also give your app a great way to support new types of user
experiences, such as leanback or exhibition mode, demo or kiosk mode, and
"attract mode" &mdash; all without requiring special hardware.</p>

<div style="float:left;margin:20px 30px 0px 0px;width:460px;">
<div>
<img src="{@docRoot}images/jb-dream-1.png" alt="Daydream screensaver mode" height="300" style="padding-left:1em;">
</div>
<p class="image-caption" style="padding:.5em .5em .5em 1.5em;"><span
style="font-weight:500;">Daydream</span> lets you create powerful interactive screensavers that display any kind of content.</p>
</div>

<p>Daydreams are similar to Activities and can do anything that Activity
can do &mdash; from rendering a UI hierarchy (without using RemoteViews) to
drawing directly using Canvas, OpenGL, SurfaceTexture, and more. They can play
video and audio and they can even accept direct user interaction. However,
daydreams are not Activities, so they don’t affect the backstack or appear in
Recents and they cannot be launched directly from your app.</p>

<p>Implementing a daydream is straightforward and you can take advantage of UI
components and resources that you’ve already created for other parts of your
app. You can provide multiple daydreams in your app and you can offer distinct
content and display settings for each.</p>

<h2  id="42-external-display" style="clear:left;">External display support</h2>

<p>Android 4.2 introduces platform support for <strong>external
displays</strong> that goes far beyond mirroring &mdash; apps can now target
unique content to any one or multiple displays that are attached to an Android
device. Apps can build on this to deliver new kinds of interaction and
entertainment experiences to users.</p>

<h3 id="42-display-manager">Display manager</h3>

<p>Apps interact with displays through a new display manager system service.
Your app can enumerate the displays and check the capabilities of each,
including size, density, display name, ID, support for secure video, and more.
Your app can also receive callbacks when displays are added or removed or when
their capabilities change, to better manage your content on external
displays.</p>

<h3 id="42-presentation">Presentation window</h3>

<p>To make it easy to show content on an external display, the framework
provides a new UI object called a <strong>Presentation</strong> &mdash; a type of dialog that
represents a window for your app’s content on a specific external display. Your
app just gives the display to use, a theme for the window, and any unique
content to show. The Presentation handles inflating resources and rendering your
content according to the characteristics of the targeted display.</p>

<div style="margin:0 auto;width:569px;padding-top:1em;">

<img src="{@docRoot}images/external-display.png" alt="" width="555" height="351" style="padding-left:1em;margin-bottom:0">

<p class="image-caption" style="padding:1.25em">You can take full control of two or more independent displays using <strong>Presentation</strong>.</p>
</div>

<p>A Presentation gives your app full control over the remote display window and
its content and lets you manage it based on user input events such as key
presses, gestures, motion events, and more. You can use all of the normal tools
to create a UI and render content in the Presentation, from building an
arbitrary view hierarchy to using SurfaceView or SurfaceTexture to draw directly
into the window for streamed content or camera previews.</p>

<h3 id="42-preferred display">Preferred display selection</h3>

<p>When multiple external displays are available, you can create as many
Presentations as you need, with each one showing unique content on a specific
display. In many cases, you might only want to show your content on a single
external display &mdash; but always on the that’s best for Presentation content.
For this, the system can help your app choose the best display to use.</p>

<p>To find the best display to use, your app can query the display manager for
the system’s <strong>preferred Presentation display</strong> and receive callbacks when that
display changes. Alternatively, you can use the media router service, extended
in Android 4.2, to receive notifications when a system video route changes. Your
app can display content by default in the main Activity until a preferred
Presentation display is attached, at which time it can automatically switch to
Presentation content on the preferred display. Your apps can also use media
router’s MediaRouteActionProvider and MediaRouteButton to offer standard
display-selection UI.</p>

<h3 id="42-protected-content">Protected content</h3>

<p>For apps that handle protected or encrypted content, the display API now
reports the <strong>secure video capabilities</strong> of attached displays. Your app query a
display to find out if it offers a secure video output or provides protected
graphics buffers and then choose the appropriate content stream or decoding to
make the content viewable. For additional security on SurfaceView objects, your
app can set a secure flag to indicate that the contents should never appear in
screenshots or on a non-secure display output, even when mirrored.</p>

<h3 id="42-wireless-display">Wireless display</h3>

<p>Starting in Android 4.2, users on supported devices can connect to an
external display over Wi-Fi, using <a
href="http://www.wi-fi.org/wi-fi-certified-miracast%E2%84%A2">Miracast</a>, a
peer-to-peer wireless display standard created by the <a
href="http://www.wi-fi.org/">Wi-Fi Alliance</a>. When a wireless display is
connected, users can stream any type of content to the big screen, including
photos, games, maps, and more.</p>

<p>Apps can take advantage of <strong>wireless displays</strong> in the same way as they do other
external displays and no extra work is needed. The system manages the network
connection and streams your Presentation or other app content to the wireless
display as needed.</p>


<h2 id="42-native-rtl">Native RTL support</h2>

<div style="float:right;margin:22px 0px 0px 24px;width:340px;">
<div>
<img src="{@docRoot}images/jb-rtl.png" alt="RTL layout mirroring" width="340" height="457" style="margin-bottom:0;">
</div>
<p class="image-caption" style="padding-top:1em">Developers can now <strong>mirror their layouts</strong> for RTL languages.</p>
</div>

<p>Android 4.2 introduces <strong>full native support for RTL</strong>
(right-to-left) layouts, including layout mirroring. With native RTL support,
you can deliver the same great app experience to all of your users, whether
their language uses a script that reads right-to-left or one that reads
left-to-right.</p>

<p>When the user switches the system language to a right-to-left script, the
system now provides automatic mirroring of app UI layouts and all view widgets,
in addition to bidi mirroring of text elements for both reading and character
input.</p>

<p>Your app can take advantage of <strong>RTL layout mirroring</strong> in your app with minimal effort.
If you want the app to be mirrored, you simply declare a new attribute in your
app manifest and change all "left/right" layout properties to new "start/end"
equivalents. The system then handles the mirroring and display of your UI as
appropriate.</p>

<p>For precise control over your app UI, Android 4.2 includes new APIs that let
you manage layout direction, text direction, text alignment, gravity, and 
locale direction in View components. You can even create custom versions of
layout, drawables, and other resources for display when a right-to-left script
is in use.</p>

<p>To help you debug and optimize your custom right-to-left layouts, the
HierarchyViewer tool now lets you see start/end properties, layout direction,
text direction, and text alignment for all the Views in the hierarchy.</p>


<h2 id="42-intl">Enhancements for international languages</h2>

<p>Android 4.2 includes a variety of <strong>font and character
optimizations</strong> for international users:</p>
<ul>
<li>For Korean users, a new font choice is available &mdash; Nanum (나눔글꼴)
Gothic, a unicode font designed especially for the Korean-language script.</li>
<li>Improved support for Japanese vertical text displayed in WebViews.</li>
<li>Improved font kerning and positioning for Indic, Thai, Arabic, and Hebrew
default fonts.</li>
</ul>

<p>The default Android keyboard also includes an updated set of
dictionaries:</p>
<ul>
<li>Improved dictionaries for French (with bigram support), English, and
Russian</li>
<li>New dictionaries for Danish, Greek, Finnish, Lithuanian, Latvian, Polish,
Slovenian, Serbian, Swedish, Turkish</li>
</ul>


<h2 id="42-ui-tools">New ways to create beautiful UI</h2>

<h3 id="42-nested-fragments">Nested Fragments</h3>

<p>For more control over your UI components and to make them more modular,
Android 4.2 lets you <strong>nest Fragments inside of Fragments</strong>. For
any Fragment, a new Fragment manager lets you insert other Fragments as child
nodes in the View hierarchy.</p>

<p>You can use nested Fragments in a variety of ways, but they are especially
useful for implementing dynamic and reusable UI components inside of a UI
component that is itself dynamic and reusable. For example, if you use ViewPager
to create fragments that swipe left and right, you can now insert fragments into
each Fragment of the view pager.</p>

<p>To let you take advantage of nested Fragments more broadly in your app, this
capability is added to the latest version of the <strong>Android Support
Library</strong>.</p>


<h2 id="42-accessibility">Accessibility</h2>

<p>The system now helps accessibility services <strong>distinguish between touch
exploration and accessibility gestures</strong> while in touch-exploration mode.
When a user touches the screen, the system notifies the service that a generic
touch interaction has started. It then tracks the speed of the touch interaction
and determines whether it is a touch exploration (slow) or accessibility gesture
(fast) and notifies the service. When the touch interaction ends, the system
notifies the service.</p>

<p>The system provides a new global accessibility option that lets an
accessibility service open the Quick Settings menu based on an action by the
user. Also added in Android 4.2 is a new accessibility feedback type for
<strong>Braille devices</strong>.</p>

<p>To give accessibility services insight into the meaning of Views for
accessibility purposes, the framework provides new APIs for associating a View
as the label for another View. The label for each View is available to
accessibility services through AccessibilityNodeInfo.</p>


<h2 id="42-camera">Improved Camera with HDR</h2>

<p>Android 4.2 introduces a <strong>new camera hardware interface and
pipeline</strong> for improved performance. On supported devices, apps can use a
new <strong>HDR camera scene mode</strong> to capture an image using high
dynamic range imaging techniques. </p>

<p>Additionally, the framework now provides an API to let apps check whether the
camera shutter sound can be disabled. Apps can then let the user disable the
sound or choose an alternative sound  in place of the standard shutter sound,
which is recommended.</p>


<h2 id="42-renderscript">Renderscript Computation</h2>

<p>In Android 4.2, Renderscript Compute introduces new scripting features, new
optimizations, and direct GPU integration for the highest performance in
computation operations.</p>

<h3 id="42-filterscript">Filterscript</h3>

<p>Filterscript is a subset of Renderscript that is focused on <strong>optimized
image processing across a broad range of device chipsets</strong>. Developers
can write their image processing operations in Filterscript using the standard
Renderscript runtime API, but within stricter constraints that ensure wider
compatibility and improved optimization across CPUs, GPUs, and DSPs.</p>

<p>Filterscript is ideal for hardware-accelerating simple image-processing and
computation operations such as those that might be written for OpenGL ES
fragment shaders. Because it places a relaxed set of constraints on hardware,
your operations are optimized and accelerated on more types of device chipsets. 
Any app targeting API level 17 or higher can make use of Filterscript.</p>

<h3 id="42-rs-intrinsics">Script intrinsics</h3>

<p>In Android 4.2, Renderscript adds support for a set of script intrinsics
&mdash; pre-implemented <strong>filtering primitives that are
accelerated</strong> to reduce the amount of code that you need to write and to
ensure that your app gets the maximum performance gain possible.</p>

<p>Intrinsics are available for blends, blur, color matrix, 3x3  and 5x5 convolve,
per-channel lookup table, and converting an Android YUV buffer to RGB.</p>

<h3 id="42-rs-groups">Script groups</h3>

<p>You can now create <strong>groups of Renderscript scripts</strong> and
execute them all with a single call as though they were part of a single script.
This allows Renderscript to optimize execution of the scripts in ways that it
could not do if the scripts were executed individually.</p>

<div style="float:right;padding-top:1em;width:400px;margin-left:2em;">
<img src="{@docRoot}images/jb-rs-chart-versions.png" alt="Renderscipt optimizations chart" width="360" height="252"
style="border:1px solid #ddd;border-radius: 6px;" />
<p style="image-caption">Renderscript image-processing 
benchmarks run on different Android platform versions (Android 4.0, 4.1, and 4.2)
in CPU only on a Galaxy Nexus device.</p>
<img src="{@docRoot}images/jb-rs-chart-gpu.png" style="border:1px solid #ddd;border-radius: 6px; alt="" width="360" height="252" />
<p style="image-caption">Renderscript image-processing benchmarks comparing operations run with GPU + CPU to those run in CPU only on the same Nexus 10 device.</p>
</div>

<p>If you have a directed acyclic graph of Renderscript operations to run, you can
use a builder class to create a script group defining the operations. At
execution time, Renderscript optimizes the run order and the connections between
these operations for best performance.</p>


<h3 id="42-rs-optimization">Ongoing optimization improvements</h3>

<p>When you use Renderscript for computation operations, you apps benefit from
<strong>ongoing performance and optimization improvements</strong> in the
Renderscript engine itself, without any impact on your app code or any need for
recompilation.</p>

<p>As optimization improves, your operations execute faster and on more
chipsets, without any work on your part. The chart at right highlights
the performance gain delivered by ongoing Renderscript optimization improvements
across successive versions of the Android platform.</p>

<h3 id="42-gpu-compute">GPU Compute</h3>

<p>Renderscript Compute is the first computation platform ported to run directly on a mobile device GPU. It now
automatically takes advantage of <strong>GPU computation</strong> resources
whenver possible to improve performance. With GPU integration, even the most
complex computations for graphics or image processing can execute with
dramatically improved performance.</p>

<p>Any app using Renderscript on a supported device can benefit immediately from
this GPU integration, without recompiling. The Nexus 10 tablet is the first
device to support this integration.</p>

<h2  id="42-dev-options" style="clear:right;margin-top:1em;">New built-in developer options</h2>

<p>The Android 4.2 system includes a variety of new developer options that make
it easier to create great looking apps that perform well. The new options expose
features for <strong>debugging and profiling</strong> your app from any device
or emulator.</p>

<p class="caution" style="clear:right;">On devices running Android 4.2,
developer options are hidden by default, helping to create a better experience
for users. You can reveal the developer options at any time by tapping 7 times
on <strong>Settings</strong> > <strong>About phone</strong> > <strong>Build
number</strong> on any compatible Android device.</p>

<div style="float:left;margin:20px 42px 0px 0px;width:290px;">
<div>
<img src="{@docRoot}images/jb-dev-options-device.png" width="280" height="548">
</div>
<p class="image-caption" style="padding:.5em">New <span
style="font-weight:500;">developer options</span> give you more ways to profile and debug on a device.</p>
</div>

<p style="margin-top:2em;">New developer options in Android 4.2 include:</p>

<ul>
<li><strong>Take bug report</strong> &mdash; immediately takes a screen shot and
dumps device state information to local file storage, then attaches them to a
new outgoing email message.</li>
<li><strong>Power menu bug reports</strong> &mdash; Adds a new option to the
device power menu and quick settings to take a bug report (see above).</li>
<li><strong>Verify apps over usb</strong> &mdash; Allows you to disable app
checks for sideloading apps over USB, while still checking apps from other
sources like the browser. This can speed up the development process while
keeping the security feature enabled.</li>
<li><strong>Show hardware layers updates</strong> &mdash; Flashes hardware
layers green when they update.</li>
<li><strong>Show GPU overdraw</strong> &mdash; Highlights GPU overdraw
areas.</li>
<li><strong>Force 4x MSAA</strong> &mdash; Enables 4x MSAA in Open GL ES 2.0
apps.</li>
<li><strong>Simulate secondary displays</strong> &mdash; Creates one or more
non-secure overlay windows on the current screen for use as a simulated remote
display. You can control the simulated display’s size and density.</li>
<li><strong>Enable OpenGL traces</strong> &mdash; Lets you trace OpenGL
execution using Logcat, Systrace, or callstack on glGetError.</li>
</ul>

<h2 id="42-platform-tech" style="padding-top:1em;clear:left;">New Platform Technologies</h2>

<p>Android 4.2 includes a variety of new and <strong>enhanced platform technologies</strong> to
support innovative communications use-cases across a broad range of hardware
devices. In most cases, the new platform technologies and enhancements do not directly
affect your apps, so you can benefit from them without any modification.</p>

<h3 id="42-security">Security enhancements</h3>

<p>Every Android release includes dozens of security enhancements to protect
users.  Here are some of the enhancements in Android 4.2:</p>

<ul>
<li><strong>Application verification</strong> &mdash; Users can choose to enable
“Verify Apps" and have applications screened by an application verifier, prior
to installation.  App verification can alert the user if they try to install an
app that might be harmful; if an application is especially bad, it can block
installation.</li>
<li><strong>More control of premium SMS</strong> &mdash; Android will provide a
notification if an application attempts to send SMS to a short code that uses
premium services which might cause additional charges.  The user can choose
whether to allow the application to send the message or block it.</li>
<li><strong>Always-on VPN</strong> &mdash;  VPN can be configured so that
applications will not have access to the network until a VPN connection is
established.  This prevents applications from sending data across other
networks.</li>
<li><strong>Certificate Pinning</strong> &mdash; The libcore SSL implementation
now supports certificate pinning.  Pinned domains will receive a certificate
validation failure if the certificate does not chain to a set of expected
certificates.  This protects against possible compromise of Certificate
Authorities.</li>
<li><strong>Improved display of Android permissions</strong> &mdash; Permissions
have been organized into groups that are more easily understood by users. 
During review of the permissions, the user can click on the permission to see
more detailed information about the permission.</li>
<li><strong>installd hardening</strong> &mdash; The installd daemon does not run
as the root user, reducing potential attack surface for root privilege
escalation.</li>
<li><strong>init script hardening</strong> &mdash;  init scripts now apply
O_NOFOLLOW semantics to prevent symlink related attacks.</li>
<li><strong>FORTIFY_SOURCE</strong> &mdash;  Android now implements
FORTIFY_SOURCE. This is used by system libraries and applications to prevent
memory corruption.</li>
<li><strong>ContentProvider default configuration</strong> &mdash; Applications
which target API level 17 will have “export” set to “false” by default for each
ContentProvider, reducing default attack surface for applications.</li>
<li><strong>Cryptography</strong> &mdash; Modified the default implementations
of SecureRandom and Cipher.RSA to use OpenSSL.  Added  SSLSocket support for
TLSv1.1 and TLSv1.2 using OpenSSL 1.0.1</li>
<li><strong>Security Fixes</strong> &mdash; Upgraded open source libraries with
security fixes include WebKit, libpng, OpenSSL, and LibXML. Android 4.2 also
includes fixes for Android-specific vulnerabilities. Information about these
vulnerabilities has been provided to Open Handset Alliance members and fixes are
available in Android Open Source Project.  To improve security, some devices
with earlier versions of Android may also include these fixes.</li>
</ul>

<h3 id="42-bt-stack">New Bluetooth stack</h3>

Android 4.2 introduces a new Bluetooth stack optimized for use with Android
devices. The new Bluetooth stack developed in collaboration between Google and
Broadcom replaces the stack based on BlueZ and provides improved compatibility
and reliability.

<h3 id="42-audio">Low-latency audio</h3>

<p>Android 4.2 improves support for low-latency audio playback, starting from the
improvements made in Android 4.1 release for audio output latency using OpenSL
ES, Soundpool and tone generator APIs. These improvements depend on hardware
support &mdash; devices that offer these low-latency audio features can
advertise their support to apps through a hardware feature constant. New
AudioManager APIs are provided to query the native audio sample rate and buffer
size, for use on devices which claim this feature.</p>

<h3 id="42-camera-interface">New camera hardware interface</h3>

Android 4.2 introduces a new implementation of the camera stack. The camera
subsystem includes the implementations for components in the camera pipeline
such as burst mode capture with processing controls.

<h3 id="42-nfc-interface">New NFC hardware interface and controller interface</h3>

Android 4.2 introduces support for controllers based on the NCI standard from
the NFC-Forum. NCI provides a standard communication protocol between an NFC
Controller (NFCC) and a device Host, and the new NFC stack developed in
collaboration between Google and Broadcom supports it.  

<h3 id="42-dalvik">Dalvik runtime optimizations</h3>

<p>The Dalvik runtime includes enhancements for performance and security across
a wider range of architectures:</p>
<ul>
<li>x86 JIT support from Intel and MIPS JIT support from MIPS</li>
<li>Optimized garbage-collection parameters for devices with > 512MB</li>
<li>Default implementations of SecureRandom and Cipher.RSA now use OpenSSL</li>
<li>SSLSocket support for TLSv1.1 and TLSv1.2 via OpenSSL 1.0.1</li>
<li>New intrinsic support for StrictMath methods abs, min, max, and sqrt</li>
<li>BouncyCastle updated to 1.47</li>
<li>zlib updated to 1.27</li>
<li>dlmalloc updated to 2.8.6</li>
</ul>

</div> <!-- END ANDROID 4.2 -->
























<!-- BEGIN ANDROID 4.1 -->
<div id="android-41" class="version-section">

<div style="float:right;width:320px;padding:0px 0px 0px 34px;clear:both">
<div>
<img src="{@docRoot}images/jb-android-4.1.png" height="426" width="320">
</div>
</div>
<p>Welcome to Android 4.1 the first version of Jelly Bean!</p>

<p>Android 4.1 is the fastest and smoothest version of Android yet. We’ve made 
improvements throughout the platform and added great new features
for users and developers. This document provides a glimpse of what's new for developers.

<p>See the <a href="{@docRoot}about/versions/android-4.1.html">Android 4.1 APIs</a> document for a detailed look at the new developer APIs.</p>

<p>Find out more about the Jelly Bean features for users at <a href="http://www.android.com/whatsnew">www.android.com</a>.</p>


<h2 id="performance">Faster, Smoother, More Responsive</h2>

<p>Android 4.1 is optimized to deliver Android's best performance and lowest touch latency, in an effortless, intuitive UI.</p>

<p>To ensure a consistent framerate, Android 4.1 extends <strong>vsync timing</strong> across all drawing and animation done by the Android framework. Everything runs in lockstep against a 16 millisecond vsync heartbeat &mdash; application rendering, touch events, screen composition, and display refresh &mdash; so frames don’t get ahead or behind.</p>

<p>Android 4.1 also adds <strong>triple buffering</strong> in the graphics pipeline, for more consistent rendering that makes everything feel smoother, from scrolling to paging and animations.</p>

<p>Android 4.1 reduces touch latency not only by <strong>synchronizing touch</strong> to vsync timing, but also by actually <strong>anticipating</strong> where your finger will be at the time of the screen refresh. This results in a more reactive and uniform touch response. In addition, after periods of inactivity, Android applies a <strong>CPU input boost</strong> at the next touch event, to make sure there’s no latency.</p>

<p><strong>Tooling</strong> can help you get the absolute best performance out of your apps. Android 4.1 is designed to work with a new tool called <strong>systrace</strong>, which collects data directly from the Linux kernel to produce an overall picture of system activities. The data is represented as a group of vertically stacked time series graphs, to help isolate rendering interruptions and other issues. The tool is available now in the <a href="{@docRoot}tools/index.html">Android SDK</a> (Tools R20 or higher)</p>


<div style="float:left;margin:12px 24px 0px 0px;">
<img src="{@docRoot}images/jb-accessibility-focus-250.png" width="240px" height="469">
</div>

<div style="width:85%;padding-top:16px;">
<h2 id="accessibility">Enhanced Accessibility</h2>

<p>New APIs for accessibility services let you handle gestures and manage <strong>accessibility focus</strong> as the user moves through the on-screen elements and navigation buttons using accessibility gestures, accessories, and other input. The Talkback system and explore-by-touch are redesigned to use accessibility focus for easier use and offer a complete set of APIs for developers.</p>

<p>Accessibility services can link their own <strong>tutorials</strong> into the Accessibility settings, to help users configure and use their services.</p>

<p>Apps that use standard View components <strong>inherit support</strong> for the new accessibility features automatically, without any changes in their code. Apps that use custom Views can use new accessibility node APIs to indicate the parts of the View that are of interest to accessibility services. </p>

</div>

<div style="clear:both;padding-top:1px;">

<h2 id="intl">Support for International Users</h2>

<div style="clear:both;padding-top:16px;float:right;">

<div style="float:right;margin-left:18px;fpadding-top:90px;padding-bottom:60px">
<img src="{@docRoot}images/jb-r2l.png" width="280" height="356">
</div>
</div>

<h3>Bi-Directional Text and Other Language Support</h3>

<p>Android 4.1 helps you to reach more users through support for <strong>bi-directional text</strong> in TextView and EditText elements. Apps can display text or handle text editing in left-to-right or right-to-left scripts. Apps can make use of new Arabic and Hebrew locales and associated fonts.</p>

<p>Other types of new language support include:</p>
<ul>
<li>Additional Indic languages: Kannada, Telugu, and Malayalam</li>
<li>The new Emoji characters from Unicode version 6.0</li>
<li>Better glyph support for Japanese users (renders Japanese-specific versions of glyphs when system language is set to Japanese)</li>
<li>Arabic glyphs optimized for WebViews in addition to the Arabic glyphs for TextViews</li>
<li>Vertical Text support in WebViews, including Ruby Text and additional Vertical Text glyphs</li>
<li>Synthetic Bold is now available for all fonts that don't have dedicated bold glyphs</li>
</ul>

<h3>User-installable keymaps</h3>

<p>The platform now supports <strong>user-installable keyboard maps</strong>, such as for additional international keyboards and special layout types. By default, Android 4.1 includes 27 international keymaps for keyboards, including Dvorak. When users connect a keyboard, they can go to the Settings app and select one or more keymaps that they want to use for that keyboard. When typing, users can switch between keymaps using a shortcut (ctrl-space).</p>

<p>You can create an app to <strong>publish additional keymaps</strong> to the system. The APK would include the keyboard layout resources in it, based on standard Android keymap format. The application can offer additional keyboard layouts to the user by declaring a suitable broadcast receiver for ACTION_QUERY_KEYBOARD_LAYOUTS in its manifest. </p>
</div>


<h2 id="ui">New Ways to Create Beautiful UI</h2>


<div style="float:right;margin:22px 0px 0px 24px;width:280px;">
<div>
<!-- <img src="{@docRoot}images/jd-notif-cd.png" style="width:200px"> -->
<img src="{@docRoot}images/jb-notif-ex1.png" width="280" height="548">
</div>
<p class="image-caption" style="padding:.5em">Developers can create custom notification styles
like those shown in the examples above to display rich content and actions.</p>
</div>

<h3>Expandable notifications</h3>

<p>Notifications have long been a unique and popular feature on Android. Developers can use them to place important or time-based information in front of users in the notification bar, outside of the app’s normal UI.</p>

<p>Android 4.1 brings a major update to the Android notifications framework. Apps can now display <strong>larger, richer notifications</strong> to users that can be expanded and collapsed with a pinch or swipe. Notifications support <strong>new types of content</strong>, including photos, have configurable priority, and can even include multiple actions.</p>

<p>Through an improved <strong>notification builder</strong>, apps can create notifications that use a larger area, up to 256 dp in height. Three <strong>templated notification styles</strong> are available:</p>

<ul>
<li>BigTextStyle &mdash; a notification that includes a multiline TextView object.</li>
<li>BigInboxStyle &mdash; a notification that shows any kind of list such as messages, headlines, and so on.</li>
<li>BigPictureStyle &mdash; a notification that showcases visual content such as a bitmap.</li>
</ul>

<p>In addition to the templated styles, you can create your own notification styles <strong>using any remote View</strong>.</p>

<p>Apps can add up to three <strong>actions</strong> to a notification, which are displayed below the notification content. The actions let the users respond directly to the information in the notification in alternative ways. such as by email or by phone call, without visiting the app.</p>

<p>With expandable notifications, apps can give more information to the user, effortlessly and on demand. Users remain in control and can long-press any notification to get information about the sender and optionally  disable further notifications from the app.</p>

<div style="float:left;margin:66px 30px 0px 0px;width:280px;">
<div>
<img src="{@docRoot}images/jb-appwidgets.png" width="280" height="548">
</div>
<p class="image-caption" style="padding:.5em"><span
style="font-weight:500;">App Widgets</span> can resize automatically to fit the home screen and load different content as their sizes change.</p>
</div>

<div style="padding-top:1px;clear:right;">


<h3>Resizable app widgets</h3>

<p>Android 4.1 introduces improved App Widgets that can <strong>automatically resize</strong>, based on where the user drops them on the home screen, the size to which the user expands them, and the amount of room available on the home screen. New App Widget APIs let you take advantage of this to <strong>optimize your app widget content</strong> as the size of widgets changes.</p>

<p>When a widget changes size, the system notifies the host app’s widget provider, which can reload the content in the widget as needed. For example, a widget could display larger, richer graphics or additional functionality or options. Developers can still maintain control over maximum and minimum sizes and can update other widget options whenever needed. </p>

<p>You can also supply separate landscape and portrait layouts for your widgets, which the system inflates as appropriate when the screen orientation changes.</p>

<p>App widgets can now be displayed in third party launchers and other host apps through a new bind Intent (AppWidgetManager.ACTION_APPWIDGET_BIND).</p>

</div>

<h3>Simplified task navigation</h3>

<p>Android 4.1 makes it easy for you to manage the “Up” navigation that’s available to users from inside of your apps and helps ensure a consistent experience for users.</p>

<p>You can <strong>define the intended Up navigation</strong> for individual Activity components of your UI by adding a new <strong>XML attribute</strong> in the app’s manifest file. At run time, as Activities are launched, the system extracts the Up navigation tree from the manifest file and automatically creates the Up affordance navigation in the action bar. Developers who declare Up navigation in the manifest no longer need to manage navigation by callback at run time, although they can also do so if needed.</p>

<p>Also available is a new <strong>TaskStackBuilder</strong> class that lets you quickly put together a synthetic task stack to start immediately or to use when an Activity is launched from a PendingIntent. Creating a synthetic task stack is especially useful when users launch Activities from remote views, such as from Home screen widgets and notifications, because it lets the developer provide a managed, consistent experience on Back navigation.</p>

<h3>Easy animations for Activity launch</h3>

<p>You can use a new helper class, <strong>ActivityOptions</strong>, to create and control the animation displayed when you launch your Activities. Through the helper class, you can specify custom animation resources to be used when the activity is launched, or request new zoom animations that start from any rectangle you specify on screen and that optionally include a thumbnail bitmap.</p>

<h3>Transitions to Lights Out and Full Screen Modes</h3>

<p>New system UI flags in View let you to cleanly transition from a normal application UI (with action bar, navigation bar, and system bar visible), to "lights out mode" (with status bar and action bar hidden and navigation bar dimmed) or "full screen mode" (with status bar, action bar, and navigation bar all hidden). </p>

<h3>New types of remoteable Views</h3>

<p>Developers can now use <strong>GridLayout</strong> and <strong>ViewStub</strong> views in Home screen widgets and notifications. GridLayout lets you structure the content of your remote views and manage child views alignments with a shallower UI hierarchy. ViewStub is an invisible, zero-sized View that can be used to lazily inflate layout resources at runtime.</p>

<h3>Live wallpaper preview</h3>

<p>Android 4.1 makes it easier for users to <strong>find and install Live Wallpapers</strong> from apps that include them. If your app includes Live Wallpapers, you can now start an Activity (ACTION_CHANGE_LIVE_WALLPAPER) that shows the user a preview of the Live Wallpaper from your own app. From the preview, users can directly load the Live Wallpaper.</p>

<h3>Higher-resolution contact photos</h3>

<p>With Android 4.1, you can store <strong>contact photos</strong> that are as large as <strong>720 x 720</strong>, making contacts even richer and more personal. Apps can store and retrieve contact photos at that size or use any other size needed. The maximum photo size supported on specific devices may vary, so apps should <strong>query the built-in contacts provider</strong> at run time to obtain the max size for the current device. </p>


<h2 id="input">New Input Types and Capabilities</h2>

<h3>Find out about devices being added and removed</h3>

<p>Apps can <strong>register to be notified</strong> when any new input devices are attached, by USB, Bluetooth, or any other connection type. They can use this information to change state or capabilities as needed. For example, a game could receive notification that a new keyboard or joystick is attached, indicating the presence of a new player.</p>

<h3>Query the capabilities of input devices</h3>

<p>Android 4.1 includes APIs that let apps and games take full advantage of all input devices that are connected and available.</p>

<p>Apps can query the device manager to enumerate all of the input devices currently attached and learn about the capabilities of each.</p>

<h3>Control vibrator on input devices</h3>

<p>Among other capabilities, apps can now make use of any <strong>vibrator service</strong> associated with an attached input device, such as for <strong>Rumble Pak</strong> controllers.</p>


<h2 id="graphics">Animation and Graphics</h2>

<h3>Vsync for apps</h3>

<p>Extending vsync across the Android framework leads to a more consistent framerate and a smooth, steady UI. So that apps also benefit, Android 4.1 <strong>extends vsync timing</strong> to all drawing and animations initiated by apps. This lets them optimize operations on the UI thread and provides a stable timebase for synchronization.</p>

<p>Apps can take advantage of vsync timing for free, through Android’s <strong>animation framework</strong>. The animation framework now uses vsync timing to automatically handle synchronization across animators.</p>

<p>For specialized uses, apps can access vsync timing through APIs exposed by a new Choreographer class. Apps can request invalidation on the next vsync frame &mdash; a good way to schedule animation when the app is not using the animation framework. For more advanced uses, apps can post a callback that the Choreographer class will run on the next frame. </p>

<h3>New animation actions and transition types</h3>

<p>The animation framework now lets you define start and end actions to take when running ViewPropertyAnimator animations, to help synchronize them with other animations or actions in the application. The action can run any runnable object. For example, the runnable might specify another animation to start when the previous one finishes.</p>

<p>You can also now specify that a ViewPropertyAnimator use a layer during the course of its animation. Previously, it was a best practice to animate complicated views by setting up a layer prior to starting an animation and then handling an onAnimationEnd() event to remove the layer when the animation finishes. Now, the withLayer() method on ViewPropertyAnimator simplifies this process with a single method call.</p>

<p>A new transition type in LayoutTransition enables you to automate animations in response to all layout changes in a ViewGroup.</p>


<h2 id="connectivity">New Types of Connectivity</h2>

<h3>Android Beam</h3>

<p>Android Beam is a popular NFC-based technology that lets users instantly share, just by touching two NFC-enabled phones together.</p>

<p>In Android 4.1, Android Beam makes it easier to share images, videos, or other payloads by <strong>leveraging Bluetooth for the data transfer</strong>. When the user triggers a transfer, Android Beam hands over from NFC to Bluetooth, making it really easy to manage the transfer of a file from one device to another.</p>

<h3>Wi-Fi Network Service Discovery</h3>

<p>Android 4.1 introduces support for multicast <strong>DNS-based service discovery</strong>, which lets applications find and connect to services offered by peer devices over Wi-Fi networks &mdash; including mobile devices, printers, cameras, media players, and others. Developers can take advantage of Wi-Fi network service discovery to build cross-platform or multiplayer games and application experiences.</p>

<p>Using the service discovery API, apps can create and register any kind of service, for any other NSD-enabled device to discover. The service is advertised by multicast across the network using a human-readable string identifier, which lets user more easily identify the type of service.  </p>

<p>Consumer devices can use the API to scan and discover services available from devices connected to the local Wi-Fi network. After discovery, apps can use the API to resolve the service to an IP address and port through which it can establish a socket connection.</p>

<p>You can take advantage of this API to build new features into your apps. For example, you could let users connect to a webcam, a printer, or an app on another mobile device that supports Wi-Fi peer-to-peer connections.  </p>

<h3>Wi-Fi Direct Service Discovery</h3>

<p>Ice Cream Sandwich introduced support for Wi-Fi Direct, a technology that lets apps <strong>discover and pair directly</strong>, over a high-bandwidth peer-to-peer connection. Wi-Fi Direct is an ideal way to share media, photos, files and other types of data and sessions, even where there is no cell network or Wi-Fi available.</p>

<p>Android 4.1 takes Wi-Fi Direct further, adding API support for <strong>pre-associated service discovery</strong>. Pre-associated service discovery lets your apps get more useful information from nearby devices about the services they support, before they attempt to connect.  Apps can initiate discovery for a specific service and filter the list of discovered devices to those that actually support the target service or application.</p>

<p>For example, this means that your app could discover only devices that are “printers” or that have a specific game available, instead of discovering all nearby Wi-Fi Direct devices. On the other hand, your app can advertise the service it provides to other devices, which can discover it and then negotiate a connection. This greatly simplifies discovery and pairing for users and lets apps take advantage of Wi-Fi Direct more effectively.</p>

<p>With Wi-Fi Direct service discovery, you can create apps and <strong>multiplayer games</strong> that can share photos, videos, gameplay, scores, or almost anything else &mdash; all without requiring any Internet or mobile network. Your users can connect using only a direct p2p connection, which avoids using mobile bandwidth.</p>

<h3>Network Bandwidth Management</h3>

<p>Android 4.1 helps apps <strong>manage data usage</strong> appropriately when the device is <strong>connected to a metered network</strong>, including tethering to a mobile hotspot. Apps can query whether the current network is metered before beginning a large download that might otherwise be relatively expensive to the user. Through the API, you can now get a clear picture of which networks are sensitive to data usage and manage your network activity accordingly.</p>


<h2 id="media">New Media Capabilities</h2>

<h3>Media codec access</h3>

<p>Android 4.1 provides low-level access to platform hardware and software codecs. Apps can query the system to discover what <strong>low-level media codecs</strong> are available on the device and then and use them in the ways they need. For example, you can now create multiple instances of a media codec, queue input buffers, and receive output buffers in return. In addition, the media codec framework supports protected content. Apps can query for an available codec that is able to play protected content with a DRM solution available on the device.</p>

<h3>USB Audio</h3>

<p>USB audio output support allows hardware vendors to build hardware such as <strong>audio docks</strong> that interface with Android devices. This functionality is also exposed with the Android <strong>Open Accessory Development Kit</strong> (ADK) to give all developers the chance to create their own hardware.</p>

<h3>Audio record triggering</h3>

<p>Android now lets you <strong>trigger audio recording</strong> based on the completion of an audio playback track. This is useful for  situations such as playing back a tone to cue your users to begin speaking to record their voices. This feature helps you sync up recording so you don’t record audio that is currently being played back and prevents recordings from beginning too late.</p>

<h3>Multichannel audio</h3>

<p>Android 4.1 supports <strong>multichannel audio</strong> on devices that have hardware multichannel audio out through the <strong>HDMI port</strong>. Multichannel audio lets you deliver rich media experiences to users for applications such as games, music apps, and video players. For devices that do not have the supported hardware, Android automatically downmixes the audio to the number of channels that are supported by the device (usually stereo).</p>

<p>Android 4.1 also adds built-in support for encoding/decoding AAC 5.1 audio.</p>

<h3>Audio preprocessing</h3>

<p>Developers can apply <strong>preprocessing effects</strong> to audio being recorded, such as to apply noise suppression for improving speech recording quality, echo cancellation for acoustic echo, and auto gain control for audio with inconsistent volume levels. Apps that require high quality and clean audio recording will benefit from these preprocessors.</p>

<h3>Audio chaining</h3>

<p>MediaPlayer supports <strong>chaining audio streams together</strong> to play audio files without pauses. This is useful for apps that require seamless transitions between audio files such as music players to play albums with continuous tracks or games.</p>

<h3 id="media-router">Media Router</h3>

<p>The new APIs MediaRouter, MediaRouteActionProvider, and MediaRouteButton provide standard mechanisms and UI for <strong>choosing where to play media</strong>. Support is built-in for wired headsets and a2dp bluetooth headsets and speakers, and you can add your own routing options within your own app.</p>

<h2 id="renderscript">Renderscript Computation</h2>

<p>Android 4.1 extends Renderscript computation to give you more flexibility. You can now <strong>sample textures</strong> in your Renderscript compute scripts, and <strong>new pragmas</strong> are available to define the floating point precision required by your scripts. This lets you enable <strong>NEON instructions</strong> such as fast vector math operations on the CPU path, that wouldn’t otherwise be possible with the full IEEE 754-2008 standard.</p>

<p>You can now <strong>debug</strong> your Renderscript compute scripts on <strong>x86-based emulator and hardware devices</strong>. You can also define multiple root-style kernels in a single Renderscript source file.</p>


<h2 id="browser">Android Browser and WebView</h2>

<p>In Android 4.1, the Android Browser and WebViews include these enhancements:</p>
<ul>
<li>Better HTML5 video user experience, including touch-to-play/pause and smooth transition from inline to full screen mode. </li>
<li>Improved rendering speed and reduced memory usage for better scrolling and zooming performance.</li>
<li>Improved HTML5/CSS3/Canvas animation performance.</li>
<li>Improved text input.</li>
<li>Updated JavaScript Engine (V8) for better JavaScript performance.</li>
<li>Support for the updated HTML5 Media Capture specification (the "capture" attribute on input type=file elements).</li>
</ul>


<h2 id="google">Google APIs and services</h2>

<p>To extend the capabilities of Android even further, several new services for Android are available.</p>

<h3 id="gcm">Google Cloud Messaging for Android</h3>

<p>Google Cloud Messaging (GCM) is a service that lets developers send <strong>short message data</strong> to their users on Android devices, without needing a proprietary sync solution. </p>

<p>GCM handles all the details of <strong>queuing messages and delivering them</strong> efficiently to the targeted Android devices. It supports message <strong>multicasting</strong> and can reach up to 1000 connected devices simultaneously with a single request. It also supports message <strong>payloads</strong>, which means that in addition to sending tickle messages to an app on the device, developers can send up to 4K of data. </p>

<p>Google Cloud Messaging is completely <strong>free for all developers</strong> and sign-up is easy. See the <a href="{@docRoot}google/gcm/index.html">Google Cloud Messaging</a> page for registration, downloads, and documentation.</p>

<h3>App Encryption</h3>

<p>Starting with Android 4.1, Google Play will help protect application assets by encrypting all paid apps with a device-specific key before they are delivered and stored on a device.</p>

<h3>Smart App Updates</h3>

<p>Smart app updates is a new feature of Google Play that introduces a better way of delivering <strong>app updates</strong> to devices. When developers publish an update, Google Play now delivers only the <strong>bits that have changed</strong> to devices, rather than the entire APK. This makes the updates much lighter-weight in most cases, so they are faster to download, save the device’s battery, and conserve bandwidth usage on users’ mobile data plan. On average, a smart app update is about <strong>1/3 the size</strong> of a full APK update.</p>

<h3 id="gps">Google Play services</h3>

<p>Google Play services helps developers to <strong>integrate Google services</strong> such as authentication and Google+ into their apps delivered through Google Play.</p> 

<p>Google Play services is automatically provisioned to end user devices by Google Play, so all you need is a <strong>thin client library</strong> in your apps.</p>

<p>Because your app only contains the small client library, you can take advantage of these services without a big increase in download size and storage footprint. Also, Google Play will <strong>deliver regular updates</strong> to the services, without developers needing to publish app updates to take advantage of them.</p>

<p>For more information about the APIs included in Google Play Services, see the <a href="http://developers.google.com/android/google-play-services/index.html">Google Play services</a> developer page.</p>

</div> <!-- END ANDROID 4.1 -->