透過集合功能整理內容
你可以依據偏好儲存及分類內容。
Android Studio 1.5.0 版 (2015 年 11 月)
修正與改善項目：
- 為 Android 監控器新增記憶體監控器分析功能。查看透過這個監控器擷取的 HPROF 檔案時，系統現在會顯示更實用的資訊，讓您可更快找出記憶體流失等問題。如要使用這個監控器，請按一下主視窗底部的「Android Monitor」。在 Android 監控器中，按一下「MEMORY」分頁標籤。在監控器執行期間，按一下「Dump Java Heap」圖示，在主視窗中點選「Captures」，然後按兩下要查看的檔案。接著按一下右側的「Capture Analysis」。請注意，Android 裝置監控器無法與 Android 監控器同時執行。
- 開始支援深層連結和應用程式連結。程式碼編輯器可針對
AndroidManifest.xml 檔案所含的深層連結自動建立意圖篩選器，還可以產生程式碼，協助您在 Java 檔案的活動中整合 App Indexing API。深層連結測試功能可驗證指定深層連結能否啟動應用程式。在「Run/Debug Configurations」對話方塊的「General」分頁中，您可以指定深層連結啟動選項。您也可以使用 Android 監控器的 logcat 顯示畫面，測試活動中的 App Indexing API 呼叫。Android lint 工具現在會針對有關深層連結和 App Indexing API 的某些問題發出警告。
- 在程式碼編輯器中完成自訂檢視的程式碼時，您現在可以使用簡稱。
- 為 Vector Asset Studio 新增更多
VectorDrawable 元素的相關支援，以提供回溯相容性。Vector Asset Studio 可利用這些元素將向量可繪項目轉換為 PNG 光柵圖片，以便與 Android 4.4 (API 級別 20) 以下版本搭配使用。
- 為 Android TV 和 Android Auto 新增
lint 檢查功能，讓您可在 Android Studio 中立即取得具體可行的回饋。此外，系統還可提供多項快速修正建議。舉例來說，如果是 Android TV，系統可回報權限、不支援的硬體、uses-feature 元素和缺少橫幅問題，並提供快速修正建議。如果是 Android Auto，系統可驗證 AndroidManifest.xml 檔案所參照的描述元檔案是否使用正確、在沒有 MediaBrowserService 類別的意圖篩選器時回報，並找出某些語音指令問題。
- 針對不安全的廣播接收器、
SSLCertificateSocketFactory 和 HostnameVerifier 類別使用情形，以及 File.setReadable() 和 File.setWritable() 呼叫新增 lint 檢查功能。此外，系統也會偵測無效的資訊清單資源查詢作業 (尤其是會因設定而改變的資源)。
- 修正多項穩定性問題。
這個頁面中的內容和程式碼範例均受《內容授權》中的授權所規範。Java 與 OpenJDK 是 Oracle 和/或其關係企業的商標或註冊商標。
上次更新時間：2025-08-27 (世界標準時間)。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-08-27 (世界標準時間)。"],[],[],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"]]
