4.1.2 which version

Samsung initially confirmed plans to upgrade the Tab 2 The upgrade appeared to be available initially to Tab 2 7. In a statement issued in late September , Samsung confirmed that its Galaxy Tab 2 7.

The upgrade is available only as a manual download via Sony's PC Companion program. Sony originally confirmed that the Xperia Acro S would receive Android 4.

The upgrade is being delivered in phases, Sony says, and should reach all users within the next couple of months. Sony initially confirmed that the Xperia Go would get Jelly Bean back in October of ; at the time, the company said the phone's upgrade would be delivered "from the end of March" Sony originally confirmed that the Xperia Ion would get Android 4.

The company said the phone's upgrade would be delivered "in the subsequent weeks" following a wave of higher priority upgrades in March of The software will reach handsets "over the coming weeks," Sony says, with availability and timing varying "by market and customer variants.

Sony initially confirmed that the Xperia P would get Jelly Bean back in October of ; at the time, the company said the phone's upgrade would be delivered "from the end of March" Sony had originally promised a Jelly Bean upgrade for the device at a launch event the previous summer, saying it would provide the software as soon as possible -- once it had had to the chance to "optimize" its various custom applications.

Sony originally confirmed that the Xperia S would receive Android 4. Sony originally confirmed that the Xperia SL would receive Android 4. On February 7, meanwhile, Sony officially announced it was beginning the rollout for the device, with availability and timing varying based on "market and customer variants.

The upgrade is available via Sony's PC-based Companion application. The Xperia TL is the U. The upgrade is apparently available only as a manual download through Sony's PC Companion desktop software.

Sony had initially promised to deliver Jelly Bean to the Xperia TX "from mid-Q1 " and later went on to specify February or March as the months to watch. In early February, Sony specified March as the month in which the upgrade would definitely begin.

Specific timing and availability will vary based on "market and customer variants," according to the company. Sony previously confirmed that its Xperia V phone would get Jelly Bean; the company originally said the upgrade would start "from mid-Q1 " and later went on to specify February or March as the months to watch.

The upgrade is being delivered over-the-air to all Excite 10 devices. Toshiba had previously stayed mum about its plans for Jelly Bean upgrades; until the rollout began, we had no idea if or when the company would deliver the software.

The upgrade is being delivered over-the-air to all Excite 7. The press release was posted to LG's Korean website; it isn't clear at this point when the upgrade could reach devices in other regions of the world.

It's also worth noting that LG has an embarrassingly bad track record at keeping its Android upgrade promises, with an ever-growing backlog of devices still waiting for overdue upgrades; while I certainly hope the company's efforts will improve, it's hard to take its word at face value at this point.

At this point, however, no specific time frame has been provided for when the software could arrive. Moto says the device will receive its upgrade in the first quarter of The Asian and European versions of the phone, meanwhile, are set to be upgraded within the month of December, and the Latin America- and Mexico-based editions are confirmed for upgrades but have no set time frames as of yet.

The Japan-based version of the phone, meanwhile, is also confirmed for a Jelly Bean upgrade -- but no specific timing information is available for its rollout as of yet. Thus far, however, the company has provided no estimate as to when the upgrade could occur.

While there's no final word about upgrade plans for these devices, known facts and circumstances make their odds of an Android 4. Acer hasn't said a word about the device in years; the phone didn't even receive the 2. So Jelly Bean? Yeah -- probably not. Add that to the fact that the device has been discontinued, and an Android 4. With no discussion since the days of Gingerbread, a sudden jump to Jelly Bean doesn't seem likely.

There's been no sign of Gingerbread or Ice Cream Sandwich since then -- so you probably shouldn't get your hopes up for Jelly Bean now. There's been no official statement saying the device won't get Ice Cream Sandwich, but a jump from 2. Not the greatest odds in the world, particularly with HTC having confirmed the newer Wildfire S phone wouldn't even get ICS due to its limited hardware resources. Jelly Bean? Don't count on it.

Big Red would deliver a big surprise if it suddenly offered Jelly Bean to this very dated device. Cellular phone is still stuck on Froyo. With Ice Cream Sandwich quickly fading in the rear-view mirror, the appearance of the Easter bunny seems more likely than the appearance of Jelly Bean. Cellular, and the Optimus V on Virgin Mobile.

While Moto hasn't officially gone on the record about this phone's future, a 4. The Droid -- which has quite limited hardware compared to today's baseline smartphone specs -- never received Gingerbread or Ice Cream Sandwich.

As such, its odds of an Android 4. That pretty much tells you everything you need to know about the phone's Jelly Bean chances. Take-home message?

If you hold your breath for Jelly Bean, you'll probably pass out long before it arrives. That clearly does not bode well for the phone's Jelly Bean upgrade chances. The information was posted to an Android 4. The phone is no longer sold by the carrier. Google has made it quite clear that this four-year-old phone is at the end of its life. Motorola had originally confirmed that the Atrix 4G would be upgraded to Ice Cream Sandwich; its announcement was a backtrack on that promise. As such, the phone is now set to remain at Android 1.

Motorola had originally confirmed that the Photon 4G would be upgraded to Ice Cream Sandwich; its announcement was a backtrack on that promise. To improve app performance while profiling, the Memory Profiler now samples memory allocations periodically by default. If desired, you can change this behavior by using the Allocation Tracking dropdown when testing on devices running Android 8. Using the Allocation Tracking dropdown, you can choose from the following modes:.

Off: turns memory allocation off. If not already selected, this mode is enabled automatically while taking a CPU recording and then returned to the previous setting when the recording is finished. You can change this behavior in the CPU recording configuration dialog. This data might be useful when investigating bottlenecks that cause UI jank and low framerates. For example, each frame that takes longer than the 16ms required to maintain a smooth framerate is displayed in red. To see frame rendering data, record a trace using a configuration that allows you to Trace System Calls.

After recording the trace, look for info about each frame along the timeline for the recording under the section called FRAMES , as shown below. To learn more about investigating and fixing framerate issues, read Slow rendering. The event timeline now shows when fragments are attached and detached. Additionally, when you hover over a fragment, a tooltip shows you the fragment status.

Previously, the Network profiler displayed only raw text from connection payloads. In the Response and Request tabs, click the View Parsed link to display formatted text, and click the View Source link to display raw text. For more information, see Inspect network traffic with Network Profiler. For more information, see Auto-download missing packages with Gradle. Android Studio now includes support for static code analysis using Clang-Tidy for projects that include native code.

When selecting this inspection in the Settings or Preferences dialog, you can also see the list of Clang-Tidy checks that are enabled and disabled under the Option section of the right-most panel.

To enable additional checks , add them to the list and click Apply. CMake version 3. Note that Gradle still uses version 3. For more information on configuring CMake in build. In other words, you can now build and deploy both installed app and instant experiences from a single Android Studio project and include them in a single Android App Bundle.

Syncing your project with your build configuration is an important step in letting Android Studio understand how your project is structured. However, this process can be time-consuming for large projects. If your project uses multiple build variants, you can now optimize project syncs by limiting them to only the variant you have currently selected.

You need to use Android Studio 3. When you meet these requirements, the IDE prompts you to enable this optimization when you sync your project.

The optimization is also enabled by default on new projects. For more information, see Enable single-variant project sync. If you've opted into sharing usage statistics to help improve Android Studio, you'll see these two new icons in the status bar at the bottom of the IDE window:.

Simply click the icon that best represents your current experience with the IDE. When you do so, the IDE sends usage statistics that allow the Android Studio team to better understand your sentiment. In some cases, such as when you indicate a negative experience with the IDE, you'll have an opportunity to provide additional feedback.

Kotlin version 1. Although you typically don't need to specify the build tools version, when using Android Gradle plugin 3. The assistant opens when you start Android Studio after a fresh installation or update if it detects that there is new information to show. Android Jetpack helps to accelerate Android development with components, tools, and guidance that eliminate repetitive tasks and enable you to more quickly and easily build high-quality, testable apps.

Android Studio includes the following updates to support Jetpack. For more information, see the Jetpack documentation. The new Navigation Editor integrates with the navigation components of Android Jetpack to provide a graphical view for creating the navigation structure of your app.

The Navigation Editor simplifies the design and implementation of navigation between in-app destinations. In Android Studio 3. To learn more, read the Navigation Editor documentation.

As part of Jetpack, we are migrating the Android Support Libraries to a new Android extension library using the androidx namespace. For more information, see the AndroidX overview. If you have any Maven dependencies that have not migrated to the AndroidX namespace, the Android Studio build system also automatically converts those project dependencies.

The Android Gradle plugin provides the following global flags that you can set in your gradle. Both flags are set to true when you use the Migrate to AndroidX command. If you want to start using AndroidX libraries immediately and don't need to convert existing third-party libraries, you can set the android.

You no longer need to build, sign, and manage multiple APKs, and users get smaller, more optimized downloads. Additionally, you can add feature modules to your app project and include them in your app bundle. For more information, including instructions for building and analyzing an Android App Bundle, see Android App Bundle.

Many Android layouts have runtime data that can make it difficult to visualize the look and feel of a layout during the design stage of app development.

You can now easily see a preview of your view in the Layout Editor filled with sample data. When you add a view, a button appears below the view in the Design window. Click this button to set the design-time view attributes. You can choose from a variety of sample data templates and specify the number of sample items with which to populate the view. To try using sample data, add a RecyclerView to a new layout, click the design-time attributes button below the view, and choose a selection from the carousel of sample data templates.

Slices provide a new way to embed portions of your app's functionality in other user interface surfaces on Android. For example, Slices make it possible to show app functionality and content in Google Search suggestions. To learn more, including how to test your Slice interactions, read the Slices getting started guide.

For more information, see the Android Developers blog. Try the following new Android Profiler features in Android Studio 3. You can now save Profiler data as sessions to revisit and inspect later. The profiler keeps your session data until you restart the IDE. When you record a method trace or capture a heap dump , the IDE adds that data along with your app's network activity as a separate entry to the current session, and you can easily switch back and forth between recordings to compare data.

This trace configuration is built on systrace and is useful for investigating system-level issues, such as UI jank. If you deploy your app to a device running Android 8. While your app is running, select a portion of the timeline that you want to inspect and select JNI heap from the drop-down menu above the class list, as shown below. You can then inspect objects in the heap as you normally would and double-click objects in the Allocation Call Stack tab to see where the JNI references are allocated and released in your code.

You can now import, export, and inspect. Import your. You can then inspect its data in the Memory Profiler as you would any other heap dump. To save heap dump data to review later, use the Export Heap Dump button at the right of the Heap Dump entry in the Sessions pane. In the Export As dialog that appears, save the file with the. You can now import and inspect. Currently, you can't import System Trace recordings. You can then inspect its data in the CPU Profiler similar to how you normally would, with the following exceptions:.

After you deploy your app to a device, the profiler automatically starts recording CPU activity when your app calls startMethodTracing String tracePath , and the profiler stops recording when your app calls stopMethodTracing. The Energy Profiler displays a visualization of the estimated energy usage of your app, as well as system events that affect energy usage, such as wakelocks, alarms, and jobs.

The Energy Profiler appears as a new row at the bottom of the Profiler window when you run your app on a connected device or Android Emulator running Android 8. Click the Energy row to maximize the Energy Profiler view. Place your mouse pointer over a bar in the timeline to see a breakdown of energy use by CPU, network, and location GPS resources, as well as relevant system events.

System events that affect energy usage are indicated in the System timeline below the Energy timeline. Details of system events within the specified time range are shown in the event pane when you select a time range in the Energy timeline. To see the call stack and other details for a system event, such as a wakelock, select it in the event pane.

To go to the code responsible for a system event, double-click the entry in the call stack. The new lint checks help you to find and identify common code problems, ranging from warnings about potential usability issues to high-priority errors regarding potential security vulnerabilities.

To make sure that your Java code interoperates well with your Kotlin code, new lint checks enforce the best practices described in the Kotlin Interop Guide.

Examples of these checks include looking for the presence of Nullability annotations, use of Kotlin hard keywords, and placing lambda parameters last. To enable these checks for command-line builds, add the following to your build. New lint checks for Slices help to ensure that you are constructing Slices correctly.

For example, lint checks warn you if you have not assigned a primary action to a Slice. Use the new lintFix Gradle task to apply all of the safe fixes suggested by the lint check directly to the source code. An example of a lint check that suggests a safe fix to apply is SyntheticAccessor.

Various metadata, such as the service cast check, have been updated for lint checks to work with Android 9 API level Lint now records which variant and version a baseline is recorded with, and lint warns you if you run it on a different variant than the one with which the baseline was created.

For example, the resource cycle checks now apply to additional resource types, and the translation detector can find missing translations on the fly, in the editor. Issue IDs are now shown in more places now, including in the Inspection Results window. This makes it easier for you to find the information that you need to enable or disable specific checks through lintOptions in build.

For more information, see Configure lint options with Gradle. Data Binding V2 is now enabled by default and is compatible with V1. This means that, if you have library dependencies that you compiled with V1, you can use them with projects using Data Binding V2.

However, note that projects using V1 cannot consume dependencies that were compiled with V2. R8 is a new tool for code shrinking and obfuscation that replaces ProGuard. When using the Project window in previous versions of Android Studio, you could navigate and inspect only the header files that belong to libraries you build from a local project.

Previous versions of Android Studio enabled native multidex when deploying the debug version of an app to a device running Android API level 21 or higher. Beginning with Android Studio 3. To use AAPT2, make sure that you have a google dependency in your build. Android Studio no longer passes the --configure-on-demand argument to Gradle. The ADB Connection Assistant provides instructions, in-context controls, and a list of connected devices in a series of pages in the Assistant panel.

You can now save and load snapshots of an AVD Android virtual device at any time in the Android Emulator, making it fast and easy to return an emulated device to a known state for testing. Controls for saving, loading, and managing AVD snapshots are now in the Snapshots tab in the emulator's Extended controls window.

Builds configured with source sets failed with the following message when Instant Run was enabled:. Build failures occurred during dexing in some projects with large numbers of modules or external dependencies, with the following error message:.

This update also includes changes that make running lint checks from Gradle much faster in some scenarios. In some cases, when a project created in Android Studio 3. The result was that projects did not build when the Run or Debug button was clicked, which in turn caused failures such as deployment of incorrect APKs and crashes when using Instant Run.

To solve this problem, Android Studio 3. This modification occurs after the first Gradle sync when the project is loaded. Improvements include better control flow analysis for collections and strings, improved nullability inference, new quick fixes, and much more.

When you use the Room database library , you can take advantage of several improvements to SQL editing:. This update includes several improvements for data binding :. You can now use a LiveData object as an observable field in data binding expressions. The ObservableField class can now accept other Observable objects in its constructor. You can preview a new incremental compiler for your data binding classes. For details of this new compiler and instructions for enabling it, see Data Binding Compiler V2.

Libraries keep their generated binding classes when the app is compiled, rather than being regenerated each time. This can greatly improve performance for multi-module projects. You don't need to make any changes to your code or your development workflow to get these benefits, unless you had previously manually disabled the D8 compiler. If you set android. For projects that use Java 8 language features , incremental desugaring is enabled by default, which can improve build times.

Desugaring converts syntactic sugar into a form that the compiler can process more efficiently. You can disable incremental desugaring by specifying the following in your project's gradle.

For details about how to use the new, simplified Build window, see Monitor the build process. The Gradle sync and IDE indexing processes are now much more efficient, reducing time wasted on many redundant indexing operations.

Improvements include the following:. Sync time is also greatly reduced for large projects. Performance when building and syncing with CMake has been improved through more aggressive reuse of cached results. Running lint from the command line now analyzes your Kotlin classes. For each project that you would like to run lint on, Google's Maven repository must be included in the top-level build. The Maven repository is already included for projects created in Android Studio 3.

The CPU Profiler now includes a default configuration to record sampled traces of your app's native threads. You can use this configuration by deploying your app to a device running Android 8. After that, record and inspect a trace as you normally would. You can change default settings, such as the sampling interval, by creating a recording configuration.

To switch back to tracing your Java threads, select either a Sampled Java or Instrumented Java configuration. The CPU Profiler and Memory Profiler include a search feature that allows you to filter results from recording a method trace, memory allocations, or heap dump. To search, click Filter in the top-right corner of the pane, type your query, and press Enter. In the CPU Profiler's Flame Chart tab, call stacks that include methods related to your search query are highlighted and moved to the left side of the chart.

For more information on filtering by method, class, or package name, see Record and inspect method traces. The Network Profiler now includes a Request tab that provides details about network requests during the selected timeline. In previous versions, the Network Profiler only provided information about network responses. After selecting a portion of the timeline in the Network Profiler , you can select one of the following tabs to see more detail about the network activity during that timeframe:.

The Layout Inspector gained new features, including some functionality previously provided by the deprecated Hierarchy Viewer and Pixel Perfect tools:.

The Palette in the Layout Editor has received many improvements:. You can use the new Convert view command in the Component tree or design editor to convert a view or layout to another type of view or layout.

You can now easily create constraints to items near the selected view using the new Create a connection buttons in the view inspector at the top of the Attributes window. The behavior of the Use same selection for future launches option in the Select deployment target dialog has been made more consistent. If the Use same selection option is enabled, then the Select deployment target dialog opens only the first time that you use the Run command until the selected device is no longer connected.

When targeting a device running Android 8. This is possible because the resources are contained in a split APK. For details of what's new and changed in the emulator since Android Studio 3. To see keyboard shortcuts for many commands, just hold the mouse pointer over a button until the tooltip appears.

Commands that were previously under this menu have been moved. In many cases, the functionality available through the Device Monitor is now provided by new and improved tools. See the Device Monitor documentation for instructions for invoking the Device Monitor from the command line and for details of the tools available through the Device Monitor. Simply ignore this error and click Cancel to resume the installation.

This is a minor update to Android Studio 3. Android Plugin for Gradle 3. When using the new plugin with these large projects, you should experience the following:. For more information about what's changed, see the Android Plugin for Gradle release notes. If you're ready to upgrade to the new plugin, see Migrate to Android Plugin for Gradle 3. So with this release, Android Studio includes Kotlin language support for Android development.

To get started, read how to add Kotlin to your project. You can now use certain Java 8 language features and consume libraries built with Java 8. Jack is no longer required , and you should first disable Jack to use the improved Java 8 support built into the default toolchain. To update your project to support the new Java 8 language toolchain, update the Source Compatibility and Target Compatibility to 1. To learn more, read how to use Java 8 language features.

The new Android Profiler replaces the Android Monitor tool and provides a new suite of tools to measure your app's CPU, memory, and network usage in realtime. You can perform sample-based method tracing to time your code execution, capture heap dumps, view memory allocations, and inspect the details of network-transmitted files.

The event timeline at the top of the window shows touch events, key presses, and activity changes so you have more context to understand other performance events in the timeline.

Then, you can troubleshoot CPU performance issues using a variety of data views and filters. The Memory Profiler helps you identify memory leaks and memory churn that can lead to stutter, freezes, and even app crashes.

It shows a realtime graph of your app's memory use, lets you capture a heap dump, force garbage collections, and track memory allocations. For more information, see the Memory Profiler guide. The Network Profiler allows you to monitor the network activity of your app, inspect the payload of each of your network requests, and link back to the code that generated the network request.

For more information, see the Network Profiler guide. Android Studio now allows you to profile and debug any APK without having to build it from an Android Studio project—as long as the APK is built to enable debugging and you have access to the debug symbols and source files. This displays the unpacked APK files, but it does not decompile the code. So, to properly add breakpoints and view stack traces, you need to attach Java source files and native debug symbols. The new Device File Explorer allows you to inspect your connected device's filesystem, and transfer files between the device and your computer.

This replaces the filesystem tool available in DDMS. For more information, see the Device File Explorer guide. Android Studio also includes a new modularize refactoring action to help you add support for Instant Apps in an existing project.

In the dialog that appears, select the module where the classes should go and click OK. For more information, see how to create an Android Things project. Image Asset Studio now supports vector drawables and allows you to create adaptive launcher icons for Android 8. For more information, read about Adaptive Icons. To support the new font resources in Android 8. The layout editor can also preview the fonts in your layout. To try downloadable fonts, ensure that your device or emulator is running Google Play Services v For more information, read about Downloadable Fonts.

The Firebase Assistant has been updated with a new tutorial to test App Indexing. The App Links Assistant has been updated with the following new capabilities:. Android Studio now supports a special tag in the manifest file that allows you to test your intent filter URLs. These are the same tags that the App Links Assistant can create for you.

If any one of the test URLs does not pass the intent filter definition, a lint error appears. Such an error still allows you to build debug variants, but it will break your release builds.

The Layout Editor has been updated with a number of enhancements, including the following:. The Layout Inspector includes enhancements to make it easier to debug issues with your app layouts, including grouping properties into common categories and new search functionality in both the View Tree and the Properties panes. You can now use the APK Analyzer from the command line with the apkanalyzer tool. It will eventually replace the DX compiler, but you can opt-in to use the new D8 compiler now.

DEX compilation directly impacts your app's build time,. And when comparing the new D8 compiler with the current DX compiler, D8 compiles faster and outputs smaller.

To try it, set the following in your project's gradle. For more information, see the blog post about the D8 compiler. This makes it easier to keep your libraries up to date, especially when using a continuous integration CI system. All new projects now include the Google Maven repository by default. To update your existing project, add google in the repositories block of the top-level build. Learn more about Google's Maven repository here.

Android Studio 2. Also see corresponding updates for Android Emulator This is a minor update to Android Studio 2. To use the lean Navigation Bar, click View to open the View menu, then ensure that Navigation Bar is selected and Toolbar is not selected.

This release also includes a number of bug fixes. See all bug fixes in 2. Known issue: Some device manufacturers block apps from automatically launching after being installed on the device. When deploying your app to a physical device using Android Studio 2. To avoid this issue, either use the emulator or enable automatic launching for your app in your device's settings.

The procedure for doing this is different for each device, so check the instructions provided by the manufacturer. To learn more about this issue, see Issue Samsung Galaxy Tab 3 7. Kyocera Hydro Elite C HTC Desire e. LG Enact VS Huawei MediaPad 7 Vogue.

Sony Xperia M C Samsung Galaxy Note 8. Sony Xperia ZR 3G. ZTE Vital N Samsung Galaxy Core GT-i Samsung Galaxy Win GT-i Blu Studio 5. NGM Forward Infinity. Huawei Ascend P2 U HTC First. LG Lucid 2 VS HTC Desire L. LG Optimus F5 P Sony Xperia L C Sony Xperia SP 3G. Sony Xperia ZQ. Samsung Galaxy Note Alcatel One Touch Star A.