All screen sizes now feature the status bar on top, with pull-down access to notifications and a new Quick Settings menu. The familiar system bar appears on the bottom, with buttons easily accessible from either hand. The Application Tray is also available on all screen sizes. Now several users can share a single Android tablet , with each user having convenient access to a dedicated user space.

Users can switch to their spaces with a single touch from the lock screen. 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 their own Android device. 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. For developers, multi-user support is transparent — 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.

You can extend app widgets to run on the lock screen, for instant access to your content. In Android 4. 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. Like all app widgets, lock screen widgets can display any kind of content 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.

For developers, lock screen widgets offer a great new way to engage users. 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. In this mode, the system launches a daydream — a remote content service provided by an installed app — as the device screensaver. A user can enable Daydream from the Settings app and then choose the daydream to display. 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.

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" — all without requiring special hardware. Daydream lets you create powerful interactive screensavers that display any kind of content.

They can play video and audio and they can even accept direct user interaction.

Root Android 4.2.2 Jelly Bean with KingoRoot APK without Computer

You can provide multiple daydreams in your app and you can offer distinct content and display settings for each. Apps can build on this to deliver new kinds of interaction and entertainment experiences to users. 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.

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. You can take full control of two or more independent displays using Presentation. 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.

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. For this, the system can help your app choose the best display to use. Alternatively, you can use the media router service, extended in Android 4.

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. For apps that handle protected or encrypted content, the display API now reports the secure video capabilities 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.

When a wireless display is connected, users can stream any type of content to the big screen, including photos, games, maps, and more. Apps can take advantage of wireless displays 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. Developers can now mirror their layouts for RTL languages. 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.

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. Your app can take advantage of RTL layout mirroring in your app with minimal effort. The system then handles the mirroring and display of your UI as appropriate.

For precise control over your app UI, Android 4.

You can even create custom versions of layout, drawables, and other resources for display when a right-to-left script is in use. For more control over your UI components and to make them more modular, Android 4. For any Fragment, a new Fragment manager lets you insert other Fragments as child nodes in the View hierarchy. 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. To let you take advantage of nested Fragments more broadly in your app, this capability is added to the latest version of the Android Support Library. The system now helps accessibility services distinguish between touch exploration and accessibility gestures 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. 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. 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. On supported devices, apps can use a new HDR camera scene mode to capture an image using high dynamic range imaging techniques.

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. Filterscript is a subset of Renderscript that is focused on optimized image processing across a broad range of device chipsets.

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. Intrinsics are available for blends, blur, color matrix, 3x3 and 5x5 convolve, per-channel lookup table, and converting an Android YUV buffer to RGB. You can now create groups of Renderscript scripts 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. Renderscript image-processing benchmarks run on different Android platform versions Android 4. 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. When you use Renderscript for computation operations, you apps benefit from ongoing performance and optimization improvements in the Renderscript engine itself, without any impact on your app code or any need for recompilation.

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. Renderscript Compute is the first computation platform ported to run directly on a mobile device GPU.

It now automatically takes advantage of GPU computation 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. 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.

The Android 4. The new options expose features for debugging and profiling your app from any device or emulator. New developer options give you more ways to profile and debug on a device. In most cases, the new platform technologies and enhancements do not directly affect your apps, so you can benefit from them without any modification. Every Android release includes dozens of security enhancements to protect users. Here are some of the enhancements in Android 4. These improvements depend on hardware support — 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. The Dalvik runtime includes enhancements for performance and security across a wider range of architectures:.

Root Android 4.2.2(Jelly Bean) with KingoRoot (PC Version)

Find out more about the Jelly Bean features for users at www. To ensure a consistent framerate, Android 4. This results in a more reactive and uniform touch response. Tooling can help you get the absolute best performance out of your apps. The data is represented as a group of vertically stacked time series graphs, to help isolate rendering interruptions and other issues.

New APIs for accessibility services let you handle gestures and manage accessibility focus 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. Accessibility services can link their own tutorials into the Accessibility settings, to help users configure and use their services. Apps that use standard View components inherit support 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. 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. The platform now supports user-installable keyboard maps , such as for additional international keyboards and special layout types. By default, Android 4. 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. You can create an app to publish additional keymaps to the system. The APK would include the keyboard layout resources in it, based on standard Android keymap format. Developers can create custom notification styles like those shown in the examples above to display rich content and actions. Notifications have long been a unique and popular feature on Android. Apps can now display larger, richer notifications to users that can be expanded and collapsed with a pinch or swipe.

• Give your smartphone the look it deserves with this launcher!
• free calculator application for ipad.
• yahoo fantasy hockey app download!
• Download and install Jellybean 4.2 Default Apps for Android Devices?
• chaton application for nokia c6.
• Jelly Bean | Android Developers.
• Related Searches?

Notifications support new types of content , including photos, have configurable priority, and can even include multiple actions. Through an improved notification builder , apps can create notifications that use a larger area, up to dp in height. Three templated notification styles are available:. In addition to the templated styles, you can create your own notification styles using any remote View.

Apps can add up to three actions 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. 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.

App Widgets can resize automatically to fit the home screen and load different content as their sizes change. New App Widget APIs let you take advantage of this to optimize your app widget content as the size of widgets changes. 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. You can also supply separate landscape and portrait layouts for your widgets, which the system inflates as appropriate when the screen orientation changes. App widgets can now be displayed in third party launchers and other host apps through a new bind Intent AppWidgetManager. 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.

Also available is a new TaskStackBuilder 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. You can use a new helper class, ActivityOptions , 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. 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.

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.

Jelly Bean

From the preview, users can directly load the Live Wallpaper. With Android 4. 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 query the built-in contacts provider at run time to obtain the max size for the current device.

Apps can register to be notified 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.

Android – Jelly Bean

Apps can query the device manager to enumerate all of the input devices currently attached and learn about the capabilities of each. Among other capabilities, apps can now make use of any vibrator service associated with an attached input device, such as for Rumble Pak controllers. Extending vsync across the Android framework leads to a more consistent framerate and a smooth, steady UI. So that apps also benefit, Android 4. This lets them optimize operations on the UI thread and provides a stable timebase for synchronization. The animation framework now uses vsync timing to automatically handle synchronization across animators.

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 — 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. 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.

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. Bluetooth Smart support a. Restricted profiles - put your tablet into a mode with limited access to apps and content. Setup wizard simplification - getting started on Android is easier thanks to the ability to correct previous input, and because of streamlined user agreements.

Faster user switching - switching users from the lock screen is now faster. Explore these carousel items. Use the previous and next buttons, as well as the keyboard arrows, to change the displayed item. An even sweeter Jelly Bean Jelly Bean 4. Restricted profiles for tablets You can now limit access to apps and content at home and work. Bluetooth Smart support Bluetooth Smart minimizes power use while measuring and transmitting data for fitness sensors like Fitbit, Runtastic and other devices, making your phone or tablet more power efficient.

Dial pad autocomplete Just start touching numbers or letters and the dial pad will automatically suggest numbers or names. Even more features Check them out.