Stay organized with collections
Save and categorize content based on your preferences.
Android Studio v1.5.0 (November 2015)
Fixes and enhancements:
- Added new Memory Monitor analysis abilities to Android Monitor. When you view an HPROF file
captured from this monitor, the display is now more helpful so you can more quickly locate
problems, such as memory leaks. To use this monitor, click Android Monitor at
the bottom of the main window. In Android Monitor, click the Memory tab. While
the monitor is running, click the Dump Java Heap icon, and then click
Captures in the main window and double-click the file to view it. Click
Capture Analysis on the right. (The
Android Device Monitor can't be running at the same time as Android Monitor.)
- Added new deep link and app link support. The Code Editor can automatically create an
intent filter for deep linking in the
AndroidManifest.xml file. It can also
generate code to help you integrate with the
App Indexing API
in an activity in a Java file. A deep link testing feature
helps you verify that a specified deep link can launch an app. In the General
tab of the Run/Debug Configurations dialog, you can specify deep link launch
options. You can also test App Indexing API calls in an activity by using the Android Monitor
logcat display. The Android lint tool now has warnings for
certain issues involving deep links and the App Indexing API.
- Added the ability to use short names when code-completing custom views in the Code Editor.
- Added support for more
VectorDrawable elements to
Vector Asset Studio
for backward-compatibility. Vector Asset Studio can use these elements to convert vector
drawables into PNG raster images to use with Android 4.4 (API level 20) and lower.
- Added new
lint checks for Android TV and Android Auto to give you
immediate, actionable feedback in Android Studio, along with several quick fixes. For example,
for Android TV, it can report and provide a quick fix for permissions, unsupported hardware,
uses-feature element, and missing banner issues. For Android Auto, it can
validate the correct usage in the descriptor file referred from your
AndroidManifest.xml file, report if there isn't an intent filter for the
MediaBrowserService class, and identify certain voice actions issues.
- Added new
lint checks for insecure broadcast receivers,
SSLCertificateSocketFactory and HostnameVerifier class uses, and
File.setReadable() and File.setWritable() calls. It also detects
invalid manifest resource lookups, especially for resources that vary by configuration.
- Fixed a number of stability issues.
Content and code samples on this page are subject to the licenses described in the Content License. Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.
Last updated 2025-08-26 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[],[],null,["\u003cbr /\u003e\n\nAndroid Studio v1.5.0 (November 2015)\n\nFixes and enhancements:\n\n- Added new Memory Monitor analysis abilities to Android Monitor. When you view an HPROF file captured from this monitor, the display is now more helpful so you can more quickly locate problems, such as memory leaks. To use this monitor, click **Android Monitor** at the bottom of the main window. In Android Monitor, click the **Memory** tab. While the monitor is running, click the **Dump Java Heap** icon, and then click **Captures** in the main window and double-click the file to view it. Click *Capture Analysis* on the right. (The Android Device Monitor can't be running at the same time as Android Monitor.)\n- Added new deep link and app link support. The Code Editor can automatically create an intent filter for deep linking in the `AndroidManifest.xml` file. It can also generate code to help you integrate with the [App Indexing API](http://developers.google.com/app-indexing/android/publish) in an activity in a Java file. A deep link testing feature helps you verify that a specified deep link can launch an app. In the **General** tab of the *Run/Debug Configurations* dialog, you can specify deep link launch options. You can also test App Indexing API calls in an activity by using the Android Monitor **logcat** display. The Android `lint` tool now has warnings for certain issues involving deep links and the App Indexing API.\n- Added the ability to use short names when code-completing custom views in the Code Editor.\n- Added support for more [VectorDrawable](/reference/android/graphics/drawable/VectorDrawable) elements to [Vector Asset Studio](/tools/help/vector-asset-studio) for backward-compatibility. Vector Asset Studio can use these elements to convert vector drawables into PNG raster images to use with Android 4.4 (API level 20) and lower.\n- Added new `lint` checks for Android TV and Android Auto to give you immediate, actionable feedback in Android Studio, along with several quick fixes. For example, for Android TV, it can report and provide a quick fix for permissions, unsupported hardware, `uses-feature` element, and missing banner issues. For Android Auto, it can validate the correct usage in the descriptor file referred from your `AndroidManifest.xml` file, report if there isn't an intent filter for the `MediaBrowserService` class, and identify certain voice actions issues.\n- Added new `lint` checks for insecure broadcast receivers, `SSLCertificateSocketFactory` and `HostnameVerifier` class uses, and `File.setReadable()` and `File.setWritable()` calls. It also detects invalid manifest resource lookups, especially for resources that vary by configuration.\n- Fixed a number of stability issues.\n\n\u003cbr /\u003e"]]
