Jul 15, 2011 Free Studio consists of 48 programs. Using them you can download music and video from YouTube, convert audio and video files between formats and for different devices, edit audio, video, images, create 3D videos and 3D images, make screenshots, etc.
The Developer Preview for Android 11 is now available; test it out and share your feedback.
Android Studio 3.6 has been released to the stable channel.Download it here.
Android Studio 4.1 is currently in the Canary and Dev channels, and AndroidStudio 4.0 is currently in the Beta channel.
For the latest news on releases, including a list of notable fixes ineach release, also see the Release updates.
If you encounter any problems using a preview version of Android Studio, pleaselet us know. Your bug reports help to make AndroidStudio better.
Android Studio 4.1
This section provides a summary of the new features and changes in AndroidStudio 4.1.
Support for Jetpack Compose
Jetpack Compose toolkit provides a modern approach to building your app's UI.The toolkit also brings all of Kotlin's benefits, such as helping you to writeconcise and idiomatic code that's fully interoperable with Java.
For the best experience developing with Jetpack Compose, you should use thelatest version of Android Studio 4.1. That's because when you use AndroidStudio to develop your app with Jetpack Compose, you can benefit from smarteditor features, such as New Project templates and the ability to immediatelypreview your Compose UI.
To learn more and get started, go to the Jetpack Compose overview.
Assertions in debug builds
Assertions in your Java code are now enabled when deploying the debug versionof your app. Because the Android runtime doesn't support enabling assertions atruntime (that is, passing the equivalent of the
-ea
/-enableassertions
flagto a Java VM), assertions in your app previously had no effect.
Now, when you build and deploy the debug version of your app using AndroidGradle plugin
Note: This feature currently supports only apps written in the Java programminglanguage. Support for Kotlin is coming soon.
4.1.0-alpha01
and higher, the built-in compiler (D8) rewritesthe code to enable assertions at compile time, so you always have the assertionchecks active.
Known Issues for 4.1 Preview
This section describes current known issues in Android Studio 4.1 Preview.
Patches not working in 4.1 Canary 2
Patches for Android Studio 4.1 Canary 2 are currently broken. To update to anewer version of Android Studio 4.1, shut down Android Studio, then downloadand install the latest package.
This issue has been fixed in Android Studio 4.1 Canary 3.
Timeout errors in CPU Profiler
You may experience 'Recording failed to stop' errors in the Android Studio CPUProfiler when you select the Sample Java Methods or Trace Java Methodsconfigurations. These are often timeout errors, especially if you see thefollowing error message in the
idea.log
file:
Wait for ART trace file timed out
The timeout errors tend to affect traced methods more than sampled methods andlonger recordings more than shorter recordings. As a temporary workaround, itmay be helpful to try shorter recordings to see if the error disappears.
If you experience timeout issues with the Profiler, please file a bugthat includes the make/model of your device(s) and any relevant entries from
idea.log
and logcat.
Git version control errors in the IDE
Operations requiring authentication in Git version control are broken in theIDE for Android Studio 4.1 Canary 1.
To fix this issue, upgrade to Android Studio 4.1 Canary 2.
Android Studio 4.0
This section provides a summary of the new features and changes in AndroidStudio 4.0.
CPU Profiler UI Upgrades
Based on your feedback, the CPU Profiler UI has been overhauled to provide amore intuitive workflow. Notable changes include:
- CPU recordings are now separated from the main profiler timeline to allow foreasier analysis. Recorded data are organized in groups on the left side of theProfiler window. Youcan move groups up and down to reorganize the list by clicking the options icon in the top-right corner of the window, orby dragging-and-dropping individual items within a group.
- For easier side-by-side analysis, you can now view all thread activityin the thread activity timeline (including methods, functions, and events).
- The tabs for Flame Chart, Top Down, and Bottom Up analyses arenow in the righthand column. In the Threads group, threads are automaticallyexpanded for System Trace recordings and collapsed by default for otherrecording types. Double-click on thread names to expand or collapse them.
- The System Trace UI, as shown in the screenshot above, is also improved.For example, events are now uniquely colored for easier differentiation.
This feature is still a work in progress, so please continue to providefeedback.
Separate annotation processing feature removed
The ability to separate annotation processing into a dedicated task has beenremoved. This option was used to maintainincremental Java compilation when non-incremental annotation processors areused in Java-only projects; it was enabled by setting
android.enableSeparateAnnotationProcessing
to true
in thegradle.properties
file, which no longer works.
Instead, you should migrate to using incremental annotationprocessors to improvebuild performance.
Build Speed window
When using Android Studio 4.0 Canary 3 with Android Gradle plugin
4.0.0-alpha03
and higher, the Build Speed window helps you understand anddiagnose issues with your build process, such as disabled optimizations andimproperly configured tasks. When using Android Studio 4.0 Canary 3 and higher,and Android Gradle plugin 4.0.0-alpha03
and higher, you can open the BuildSpeed window as follows:
- If you haven't already done so, build your app by selectingBuild > Make Project from the menu bar.
- Select View > Tool Windows > Build from the menu bar.
- In the Build window, open the Build Speed window in one of thefollowing ways:
- After Android Studio finishes building your project, click theBuild Speed tab.
- After Android Studio finishes building your project, click the link in theright side of the Build Output window.
The Build Speed window organizes possible build issues in a tree on theleft. You can inspect and click on each issue to investigate its details in thepanel on the right. When Android Studio analyzes your build, it computes the setof tasks that determined the build's duration and provides a visualization tohelp you understand the impact of each of these tasks. You can also get detailson warnings by expanding the Warnings node.
Which tasks determine build duration?
Gradle determines task execution by task interdependencies, project structure,and CPU load, and executes tasks either sequentially or in parallel. For a givenbuild, the Build Speed window highlights the set of sequentially executedtasks that determined the duration of the current build. Addressinginefficiencies in these highlighted tasks is the best starting point forreducing your overall build time.
Keep in mind, you might see a different set of tasks determining build durationwith each build you execute. For example, if you make changes to the buildconfiguration, run a build with a different set of tasks (such as an incrementalbuild), or run a build under different constraints (for example, heavier CPUload), the Build Speed window may highlight a different set of tasks that mostimpacted that build's duration. Because of this variability, you might want touse the Build Speed window across multiple builds to consistently reduce buildduration.
Live Layout Inspector
Debug your layout with an updated Live Layout Inspector that provides complete,real-time insights into your app's UI while it's deployed to a device.
To open a Layout Inspector window, go toView > Tools Windows > Layout Inspector. Along with many of the samefeatures of the existing Layout Inspector, the Live Layout Inspector alsoincludes:
- Dynamic layout hierarchy: Updates as the views on the device change.
- Property values resolution stack: Investigate where a resource propertyvalue originates in the source code and navigate to its location by followingthe hyperlinks in the properties pane.
- 3D view: See your app's view hierarchy at runtime with advanced 3Dvisualization. To use this feature, in the Live Layout Inspector window simplyclick on the Layout and rotate it.
You can use the Live Layout Inspector only when deploying your app to devicesrunning API level 29 or higher. You must also enable the feature by navigatingto File > Settings > Experimental, and checking the box next toEnable Live Layout Inspector.
Multi Preview
Multi Preview is a visual tool for simultaneously previewing layouts indifferent devices and configurations, which can help catch potential issuesin your layouts.
You can access this feature by clicking on the Multi Preview tab in thetop-right corner of the IDE window:
You can select from two different configuration sets: Pixel devices and projectlocales. To switch between these configuration sets, select from the dropdownmenu at the top of the Multi Preview window:
Java 8 library desugaring in D8 and R8
Android Studio now includes support for using a number of Java 8 language APIswithout requiring a minimum API level for your app.
Through a process called desugaring, the DEX compiler, D8, in Android Studio3.0 and higher already provided substantial support for Java 8 language features(such as lambda expressions, default interface methods, try with resources, andmore). In Android Studio 4.0, the desugaring engine has been extended to be ableto desugar Java language APIs. This means that you can now include standardlanguage APIs that were available only in recent Android releases (such as
java.util.streams
) in apps that support older versions of Android.
The following set of APIs is supported in this release:
- Sequential streams (
java.util.stream
) - A subset of
java.time
java.util.function
- Recent additions to
java.util.{Map,Collection,Comparator}
- Optionals (
java.util.Optional, java.util.OptionalInt
andjava.util.OptionalDouble
) and some other new classes useful with the aboveAPIs - Some additions to
java.util.concurrent.atomic
(new methods onAtomicInteger
,AtomicLong
andAtomicReference
) ConcurrentHashMap
(with bug fixes for Android 5.0)
To support these language APIs, D8 compiles a separate library DEX file thatcontains an implementation of the missing APIs and includes it in your app. Thedesugaring process rewrites your app's code to instead use this library atruntime.
To enable support for these language APIs, include the following in yourmodule's
build.gradle
file:
Let us know if you run into issues or if there are other APIs you want supportedby filing bugs bugs on ourbug tracker.
Support for Kotlin DSL script files
The Android Gradle plugin now supports Kotlin DSL build script files (
*.kts
).When used with Android Studio, certain IDE features, such as the ProjectStructure dialog and build script quick fixes, now also support reading andwriting to Kotlin build script files.
Smart editor features for ProGuard rules
Android Studio now provides smart editor features when you open ProGuard rulesfiles, such as syntax highlighting, code completion, and error checking. Theeditor also integrates with your Android Studio project to provide full symbolcompletion for all classes, methods, and fields, and includes quick navigationand refactoring.
New Motion Editor
Android Studio now includes a visual design editor for theMotionLayout layout type, making iteasier to create and preview animations.
The Motion Editor provides a simple interface for manipulating elements from theMotionLayout library that serves as the foundation for animation in Androidapps. In previous releases, creating and altering these elements requiredmanually editing constraints in XML resource files. Now, the Motion Editor cangenerate this XML for you, with support for start and end states, keyframes,transitions, and timelines.
Note: Before using the Motion Editor, be sure to set the ConstraintLayout
dependency in your build.gradle
file to version 2.0.0-beta3
, as described inthe MotionLayoutreference documentation.
To get started with the Motion Editor:
- Create a ConstraintLayout.
- Right-click on the preview in the Layout Editor.
- Click Convert to MotionLayout, as shown below.
After Android Studio converts your ConstraintLayout to MotionLayout, a MotionScene file is also added to the directory containing your XML.
The
MotionLayout
then becomes your root layout, and it appears in the MotionEditor UI. The layout already includes a start ConstraintSet
, endConstraintSet
, and a transition going from start to end.
You can use the overview graphic to select a
ConstraintSet
orTransition
and to select components on the selection panel.
Then you can edit the constraints and attributes of either the start or end
ConstraintSet
the same way you would edit a ConstraintLayout
.
If you want to build more elements to your graph, you can use the creationicons to quickly add a
ConstraintSet
, Transition
, or OnClick
/OnSwipe
gestures.
To add a keyframe, first click on the Transition arrow:
Then, in the Transition timeline pane, click on the top-right corner andselect KeyPosition:
This action opens a dialog where you can set attributes for the keyframe.
You can also add
OnClick
and OnSwipe
handlers to the Transition in theattribute panel.
This action opens a dialog where you can set attributes of the click such astarget components and drag direction.
The Motion Editor supports previewing animations on the design surface. When ananimation is selected, click Playabove the timeline to preview the animation.
New in Android Gradle plugin 4.0.0
This section describes new features and behavior changes included in AndroidGradle plugin 4.0.0.
New options to enable or disable build features
Android Gradle plugin 4.0.0-alpha05 introduces a new way to control which buildfeatures you want to enable and disable, such as View Binding, Data Binding, andJetpack Compose. When new features are added, they will be disabled, by default.You can then use the
buildFeatures
block to enable only the features you want,and it helps you optimize the build performance for your project. You can setthe options for each module in the module-level build.gradle
file, as follows:
You can also specify the default setting for these features across all modulesin a project by including one or more of the following in your project's
gradle.properties
file, as shown below. Keep in mind, you can still use thebuildFeatures
block in the module-level build.gradle
file to override theseproject-wide default settings.
Feature-on-feature dependencies
In previous versions of the Android Gradle plugin, all Dynamic Feature modulescould depend only on the app's base module. When using Android Gradle plugin4.0.0, you can now include a feature module that depends on another featuremodule. That is, a
:video
feature can depend on the :camera
feature, whichdepends on the base module, as shown in the figure below.
Dynamic feature
:video
depends on feature :camera
, which depends on the base :app
module.
This means that when your app requests to download a dynamic feature module, theapp also downloads other feature modules it depends on. After you createdynamic feature modulesfor your app, you can declare a feature-on-feature dependency in the module's
build.gradle
file. For example, the :video
module declares a dependency on:camera
as follows:
Additionally, you should enable the feature-on-feature dependency feature inAndroid Studio (to support the feature when editing the Run configuration, forexample) by clicking Help > Edit Custom VM Options from the menu bar andincluding the following:
'feature' and 'instantapp' Android Gradle plugins removed
Android Gradle plugin 3.6.0 deprecated the Feature plugin(
com.android.feature
) and the Instant App plugin (com.android.instantapp
) infavor of using the Dynamic Feature plugin (com.android.dynamic-feature
) tobuild and package your instant apps using Android AppBundles.
In Android Gradle plugin 4.0.0-alpha01 and higher, these deprecated plugins arefully removed. So, to use the latest Android Gradle plugin, you need to migrateyour instant app to support Android AppBundles.By migrating your instant apps, you can leverage the benefits of appbundles and simplify your app's modulardesign.
Note: To open projects that use the removed plugins in Android Studio 4.0, theproject must use Android Gradle plugin 3.6.0 or lower.
Dependencies metadata
When building your app using Android Gradle plugin
4.0.0-beta02
and higher, theplugin includes metadata that describes the dependencies that are compiled intoyour app. When uploading your app, the Play Console inspects this metadata toprovide you with the following benefits:
- Get alerts for known issues with SDKs and dependencies your app uses
- Receive actionable feedback to resolve those issues
The data is compressed, encrypted by a Google Play signing key, and stored inthe signing block of your release app. However, you can inspect the metadatayourself in the local intermediate build files in the following directory:
<project>/<module>/build/outputs/sdk-dependencies/release/sdkDependency.txt
.
If you'd rather not share this information, you can opt-out by including thefollowing in your module's
build.gradle
file:
Kotlin Android live templates
Android Studio now includes Android livetemplates for yourKotlin classes. For example, you can now type
toast
and press theTab key to quickly insert a Toast. For a full list of available livetemplates, click File > Settings from the menu bar (or Android Studio >Preferences on macOS) and navigate to Editor > Live Templates.
Fragment wizard and new fragment templates
A New Android Fragment wizard and new fragment templates are now available whenyou navigate to File > New > Fragment > Gallery or click Create newdestination in the Navigation editor.
The Fragment gallery wizard.
Import native libraries from AAR dependencies
Starting with Android Gradle Plugin 4.0 Canary 9, you can import C/C++ librariesfrom your app's AAR dependencies. When you follow the configuration stepsdescribed below, Gradle automatically makes these native libraries available touse with your external native build system, such as CMake. Note that Gradle onlymakes these libraries available to your build; you must still configure yourbuild scripts to use them.
Libraries are exported using the Prefab package format.
Each dependency can expose at most one Prefab package, which comprises one ormore modules. A Prefab module is a single library, which could be either ashared, static, or header only library.
Typically, the package name matches the Maven artifact name and the module namematches the library name, but this is not always true. Because you need to knowthe package and module name of the libraries, you might need to consult thedependency's documentation to determine what those names are.
Configure your external native build system
To see the steps you need to follow, click on the external native build systemyou plan to use.
Native dependencies included in an AAR are exposed to your CMake project viaCMAKE_FIND_ROOT_PATH. This value will be set automatically by Gradle whenCMake is invoked, so if your build modifies this variable be sure to appendrather than assign to it.
Each dependency exposes a config-file package to your CMake build, which youimport with the find_package command. This command searches for config-filepackages matching the given package name and version and exposes the targets itdefines to be used in your build. For example, if your application defines
libapp.so
and it uses curl, you should include the following in yourCMakeLists.txt file:
You can now specify
#include 'curl/curl.h'
in app.cpp
. When you build yourproject, your external native build system automatically links libapp.so
against libcurl.so
and packages libcurl.so
in the APK or app bundle.
Known Issues for 4.0 Preview
This section describes current known issues in Android Studio 4.0 Preview.
Timeout Errors in CPU Profiler
You may experience 'Recording failed to stop' errors in the Android Studio CPUProfiler when you select the Sample Java Methods or Trace Java Methodsconfigurations. These are often timeout errors, especially if you see thefollowing error message in the
idea.log
file:
Wait for ART trace file timed out
The timeout errors tend to affect traced methods more than sampled methods andlonger recordings more than shorter recordings. As a temporary workaround, itmay be helpful to try shorter recordings to see if the error disappears.
If you experience timeout issues with the Profiler, please file a bugthat includes the make/model of your device(s) and any relevant entries from
idea.log
and logcat.
Patches not working in 4.0 Beta 2
Patches for Android Studio 4.0 Beta 2 are currently broken. To update to anewer version of Android Studio 4.0, shut down Android Studio, then downloadand install the latest package.
This issue will be fixed in an upcoming release.
Git version control errors in the IDE
Operations requiring authentication in Git version control are broken in theIDE for Android Studio 4.0 Beta 1.
To fix this issue, upgrade to Android Studio 4.0 Beta 2.
Missing Run, Debug, and Profile toolbar buttons
If you have customized the Run/Debug group of action buttons—for example,by modifying options under Appearance & Behavior > Menus and Toolbars in theSettings or Preferences window—thoseaction buttons might disappear from the toolbar after you restart the IDE. Thisis a known issue in the version of IntelliJ that Android Studio 4.0 is built on(see issue IDEA-228450).
To resolve this issue, revert any customizations you have made to those buttonsas follows:
- Select File > Settings (or Android Studio > Preferences on macOS).
- On the left of the window, navigate to Appearance & Behavior > Menus andToolbars.
- On the right side of the window, navigate to Main Toolbar > Toolbar RunActions and select Run/Debug.
- Near the top of the window, click Revert.and select Restore Run/Debug.
- Click OK. You should now see the missing buttons in the toolbar.
Patches Not Available for Canary 5
No patches for Android Studio 4.0 Canary 5 are available for previouslyreleased Android Studio 4.0 Canary versions. To install Android Studio 4.0Canary 5, please download it from the Android Studio downloads page.
Profilers and Live Layout Inspector in Canary 5
Starting with Android Studio 4.0 Canary 5, the Live Layout Inspector and theProfilers do not function correctly on Windows, causing the following errormessage:
To fix this issue, upgrade to Android Studio 4.0 Canary 7 or higher.
Missing Kotlin Maven repo
If you are using Android Studio 4.0 Canary 4 or lower, you might see thefollowing error message:
To resolve this issue, update to Android Studio 4.0 Canary 5 or higher.
IllegalStateException when deploying app with native dependencies
If your app includes native dependencies and has
androidParallelJsonGen=true
(the default), you will encounter an IllegalStateException
exception whenyou deploy your app from Android Studio. To work around this issue, setandroid.enableParallelJsonGen=false
in your project's gradle.properties
file. See Issue 149575364 for more details.
Issues including native dependencies
The Android Gradle plugin currently defaults to an older version of Prefab witha couple known issues:
- Paths to libraries are incorrectly escaped on Windows.
- The CMake plugin exports static libraries incorrectly.
- Valid STL combinations may be incorrectly rejected.
The latest version of Prefab has fixes for these issues. To use the latestversion of Prefab, set
android.prefabVersion
to 1.0.0-alpha6
or higher inyour project's gradle.properties
file.
Google Inc. – 828.1MB – Shareware –
A comprehensive development environment that allows programmers to write, debug, test and emulate
Overview
Android Studio is a Shareware software in the category Miscellaneous developed by Google Inc..
It was checked for updates 2,011 times by the users of our client application UpdateStar during the last month.
The latest version of Android Studio is 3.5.2.0, released on 11/21/2019. It was initially added to our database on 05/22/2013. The most prevalent version is 1, which is used by 38 % of all installations.
Android Studio runs on the following operating systems: Windows. The download file has a size of 828.1MB.
Users of Android Studio gave it a rating of 1 out of 5 stars.
Write a review for Android Studio!
2,011 users of UpdateStar had Android Studio installed last month.
03/03/2020 | Kodi 18.6 update available with bug fixes |
01/16/2020 | Google offers important browser update to fight NSA vulnerabilities |
01/11/2020 | Important update for the Tor Browser fixes critical security gaps |
12/16/2019 | New Skype 8.55 offers added features |
12/14/2019 | New Chrome 79 for Android version deletes data |
03/21/2020 | balenaEtcher 1.5.79 |
03/21/2020 | Webcam and Screen Recorder 8.0.682 |
03/21/2020 | TimePunch 3.8.321 |
03/21/2020 | All My Books 5.1 |
03/21/2020 | Webcam Simulator XP Edition 7.603 |
Secure and free downloads checked by UpdateStar
Stay up-to-date
with UpdateStar freeware.
with UpdateStar freeware.
03/13/2020 | The best free SSD tools for you |
03/11/2020 | New version of Microsoft Windows Malicious Software Removal Tool available |
03/11/2020 | Firefox 74 is available for download with more security |
03/04/2020 | Google Chrome update fixes dangerous security vulnerability |
03/03/2020 | Kodi 18.6 update available with bug fixes |
- » android sudio 2.3
- » android studio 3.5.2.0 download
- » android studio3.14
- » android studio スピードアップ
- » androidstudio2.2 下载
- » android studio1.4
- » telecharger android studio 4.3
- » android studio3.4.2
- » android studio 3.4 下載
- » android studio 2.3.0