[go: up one dir, main page]

Release updates archive

Emulator 28.1.0 is now available in the Canary and Dev channels.

Changes and additions:
  • Project Marble: We are prioritizing CPU/RAM usage of the emulator as part of Project Marble.
    • In addition to the top most annoying issues, we would like your feedback on all aspects of emulator resource usage and performance, especially if you are running a machine with 8 GB of RAM or lower. In general, we would like to make running the emulator much more viable on machines with less RAM and less powerful CPUs.
  • Pause/resume. To address concerns about resource usage, the emulator can now be completely paused. When paused, the emulator will largely not consume CPU, while allowing its RAM to be paged out more readily, which should allow more processes to run on the system. The pause/resume mechanism works as follows:
    • Minimizing the emulator; minimize pauses the emulator, and restoring the emulator window will resume running. Or use the console commands:
    • adb emu avd pause
    • adb emu avd resume
  • Fixed issues where the emulator did not minimize properly or could not be restored from a minimized state.
  • The emulator's CPU usage stats for main loop and vCPU threads can now be displayed in the console when the environment variable SHOW_FPS_STATS is set to 1. This can be useful for sending feedback on excessive CPU/RAM usage situations.
  • For our CI users: The emulator no longer causes Qt and its dependencies to be linked when started with the -no-window flag. This allows the emulator to run on machines with more minimal configurations due to assuming the existence of fewer system libraries in addition to improving resource usage.
  • The emulator UI is now based on Qt 5.11.
  • For upcoming system images, the emulator now supports Hardware Composer 2.0. This should result in lower driver overhead when running most animations.
  • The emulator build is now based on CMake/Ninja.
Removal of deprecated components: Windows 32-bit build, QEMU1
  • The Windows 32-bit build has been removed. This will break compatibility on 32-bit Windows systems. We did this to ship a smaller download and to better focus our resources on what the vast majority of users seem to be using. Please let us know if this removal does not work for you.
  • QEMU1 (the emulator-$ARCH.exe binaries in the emulator folder) has been removed. This will break compatibility for the following system images:
    • AOSP armeabi-v7a API 14
    • AOSP armeabi-v7a API 16
    • AOSP mips API 16
    • AOSP mips API 17
    • AOSP armeabi-v7a API 19
    • Android TV x86 API 21
    • Android TV armeabi-v7a API 21
    • AOSP armeabi-v7a API 21
    • AOSP armeabi-v7a API 22
    • Android Wear armeabi-v7a API 23
    • Android Wear x86 API 23
    • AOSP armeabi-v7a API 23
    • API 9 and lower
  • We plan to release updated system images for the broken combinations that are widely used, and/or make a previous emulator build always available to run the older images. Please let us know if this removal does not work for you, and what combinations of 32-bit build / QEMU1 are critical to your use case.

We just released ConstraintLayout 2.0.0 alpha 3. It’s available from the google maven repository:
dependencies {
implementation 'com.android.support.constraint:constraint-layout:2.0.0-alpha3'
}

or if using the AndroidX packages:

dependencies {
    implementation 'androidx.constraintlayout:constraintlayout:2.0.0-alpha3'
}

Changes

This release contains various bug fixes and performance improvements:
  • Barrier fixes
  • Chains optimizations
  • Fixed glitches in MotionLayout touch handling (end state could be triggered incorrectly)


We also added several new features to MotionLayout:
  • New XML format for specifying ConstraintSets, allowing finer-grained overrides
  • KeyTimeCycle : a keyframe that allows you to define a cycle driven by time instead of by the transition (e.g. a pulsating color defined this way will keep pulsating even if the overall transition is stopped)
  • KeyPosition now supports percentWidth/percentHeight
  • KeyTrigger : a keyframe that can fire callbacks depending on the current animation progress
  • Supports custom interpolators (referencing a Framework XML interpolator)
  • Touch interactions can now drive multiple state transitions seamlessly one after another
  • OnClick: now supports multiple OnClick per MotionScene. Important: motion:mode has been renamed to motion:clickAction.
  • Added ImageFilterButton, an equivalent of ImageFilterView but extending ImageButton
  • Added new callbacks in TransitionListener

New XML Format for ConstraintSet

An important addition in alpha 3 is a new way of defining ConstraintSet in the MotionScene file. Previously, <Constraint> elements had to contain all attributes defined on a view (as we replace everything when you apply them). Now, you can instead only add the specific areas you are modifying, as sub-elements of <Constraint>:
  • <Layout> : layout-related (constraints) attributes
  • <PropertySet> : visibility, alpha and progress
  • <Transform> : scale, translation, rotation, pivot, elevation
  • <Motion> : easing, arc motion, etc.

For example, let's say that you wanted to only modify the rotation of a widget in a ConstraintSet. Previously you would have needed to repeat all the attributes to preserve the position of the widget:

         <Constraint
            android:id="@+id/button"
            android:layout_width="64dp"
            android:layout_height="64dp"
            android:layout_marginTop="100dp"
            motion:layout_constraintStart_toStartOf="parent"
            motion:layout_constraintEnd_toEndOf="parent"
            motion:layout_constraintTop_toTopOf="parent"
            android:rotation="45" />

With alpha 3 you can instead only specify the Transform area, the rest will be unaffected:

         <Constraint  android:id="@+id/button">
            <Transform motion:rotation="45" />
         </Constraint>

Emulator 28.0.22 is now available in all channels.

Changes versus previous stable 28.0.20:
  • Fixed long-standing issue where in some settings, the Mac emulator would reboot or kernel panic on Quickboot save. https://issuetracker.google.com/issues/120951634
  • When using a mapped file as the RAM snapshot, the emulator now unmaps the file mapping explicitly on exit.

Emulator 28.0.22 is now available in the Canary and Dev channels.

Change:


Android Studio 3.3 Release Candidate 3 (RC3) is now available in the Beta channel.

If you have Android Studio set up to receive updates on the Beta channel, you can get the update by choosing Help > Check for Updates (Android Studio > Check for Updates on Mac). Otherwise, you can download it here.

Linter performance improvement

This release includes a fix for a Lint performance regression introduced in Android Studio 3.1. With this fix, the Lint performance has improved as much as 4X compared to Android 3.3 RC2.

Go to definition

Fix for "go to definition" for layouts, drawables and other file resources coming from AARs.


This update includes fixes for several bugs, including the following:
  • Issue#120196378: Java 8 language support, as requested by android.enableR8.desugaring=true in your gradle.properties file, is not supported when android.enableR8=false.
  • Issue#120168590: When enabling R8 full mode, it removes a field that is being used.
  • Lint task takes longer with AGP 3.1.0-alpha07


For information on new features and changes in all preview builds of Android Studio 3.3, see the Android Studio Preview release notes. For details of bugs fixed in each preview release, see previous entries on this blog.

We greatly appreciate your bug reports, which help us to make Android Studio better. If you encounter a problem, let us know by reporting a bug. Note that you can also vote for an existing issue to indicate that you are also affected by it.


Android Studio 3.4 Canary 9 is now available in the Canary and Dev channels.

If you have Android Studio set to receive updates on the Canary or Dev channel, you can get the update by choosing Help > Check for Updates (Android Studio > Check for Updates on Mac). Otherwise, you can download it here.

This update includes the following improvements:
  • An editor intention action was added, so that you can use well-known classes like RecyclerView or WorkManager in the editor and, if unknown, it automatically suggests the right Gradle artifact to import from http://maven.google.com.


This update includes fixes for several bugs, including the following:

For information on new features and changes in previous releases of Android Studio, see the Android Studio Preview release notes. For details of bugs fixed in each preview release, see previous entries on this blog.

We greatly appreciate your bug reports, which help us to make Android Studio better. If you encounter a problem, let us know by reporting a bug. Note that you can also vote for an existing issue to indicate that you are also affected by it.


Android Studio 3.4 Canary 8 is now available in the Canary and Dev channels.

If you have Android Studio set to receive updates on the Canary or Dev channel, you can get the update by choosing Help > Check for Updates (Android Studio > Check for Updates on Mac). Otherwise, you can download it here.

New Resource Manager

Resource management is a new tool window for creating, managing, and using resources in your app. This tool window allows you to do the following:
  • Bulk import: You can now import multiple drawable assets at once by either dragging and dropping them into your Resources tool window or the Resource management import wizard. The wizard can also convert your SVG files into VectorDrawables.
  • Drag and drop assets: From the Resource management tool window you can drag and drop drawables onto the Layout Editor design and text view surfaces.
  • View alternative versions: You can now view alternative versions of your resources by double-clicking a resource within the Tool window. This view shows the different versions you have created and the qualifiers that were included.
  • Tile and list views: You can change the view within the tool window to help visualize your resources.
If this tool window does not appear in your Canary build, you can access it by selecting View > Tool Windows > Resources. For more information on this feature and others, see New features in Android Studio Preview.


This update includes fixes for several bugs, including the following:
  • Issue#120555992: Stop disabling tips of the day
  • Issue#120460980: Update AGP to Gradle 5.1-milestone-1
  • Issue#117646654: Stop injecting SDK m2repositories
  • Issue#116673790: Getting Execution failed for task processDebugResources'. > java.nio.charset.MalformedInputException: Input length = 1
  • Issue#119210741: Lint offers auto fix to incompatible Android Gradle Plugin versions.
  • Issue#119994299: Android Studio / Image Assets Wizard / Launcher Icons / Legacy / Tool tip
  • Issue#119563792: Incorrect warnings in Android Studio Room SQL with FTS
  • Issue#118538324: Custom layout with Dialog Preference from android x layout issue in Android studio
  • Issue#120087311: Enforce RestrictTo(LIBRARY) when the API is defined in another project
  • Issue#120162341: Lint detection of Configuration.densityDpi field is strange when minSdk < 17
  • Issue#67816403: Option to disable System Image patcher
  • Issue#119661177: The ViewDataBinding.OnStartListener lifecycle observer leaks the view hierarchy after Fragment.onDestroyView
  • Issue#120255763: Deterministic Builds Break when using databinding


For information on new features and changes in previous releases of Android Studio, see the Android Studio Preview release notes. For details of bugs fixed in each preview release, see previous entries on this blog.

We greatly appreciate your bug reports, which help us to make Android Studio better. If you encounter a problem, let us know by reporting a bug. Note that you can also vote for an existing issue to indicate that you are also affected by it.

Emulator 28.0.21 is now available in the Canary and Dev channels.

Change:

Emulator 28.0.20 is now available in all channels. This is a maintenance release to fix issues both longstanding and arising from 28.0.16.

Changes versus the previous stable version (28.0.16):
  • Fixed freeze on snapshot load on Windows with certain models of Intel GPUs.
  • Fixed unauthorized ADB device state when using a non-standard ANDROID_SDK_HOME location.
  • Fixed crash when booting system images with CPU acceleration disabled on Windows.
  • Fixed pixelated emulator display. Downsampling should now be working.
  • Fixed an issue in macOS 10.14+ where the virtual scene camera mouselook control could become too sensitive due to an interaction with new accessibility security settings.
  • Fixed an error in timezone calculation that could result sporadically incorrect setting of the emulator clock.
  • Fixed rendering errors in various cocos2d and Unreal engine apps.
  • Added support in the emulator for Wi-Fi peer-to-peer. Two emulators can now talk to each other directly via Wi-Fi if using the latest Pie Play Store image. To use, start two AVDs with the same -wifi-server-port and -wifi-client-port arguments:
    • emulator @<server-avd-name> -wifi-server-port 9999
    • emulator @<client-avd-name> -wifi-client-port 9999
  • Added support for more webcams on Windows by taking any incompatible frame sizes and dynamically resizing them to fit the camera setting in the Android guest.

Emulator 28.0.20 is now available in the Canary and Dev channels.

There is a single change to fix a late breaking issue:

  • Fixed an issue when running the emulator in OpenGL ES 3.1 mode where shaders would fail to link.

Emulator 28.0.19 is now available in the Canary and Dev channels.

Changes:
  • Fixed an issue in macOS 10.14+ where the virtual scene camera mouselook control could become too sensitive due to an interaction with new accessibility security settings.
  • Fixed an error in timezone calculation that could result sporadically incorrect setting of the emulator clock.
  • Fixed rendering errors in various cocos2d and Unreal engine apps. If you are interested in or are currently using the emulator for game development, we are interested in making that experience as high fidelity as possible and would appreciate feedback in Issuetracker.


Android Studio 3.3 Release Candidate 2 (RC2) is now available in the Beta channel.

If you have Android Studio set up to receive updates on the Beta channel, you can get the update by choosing Help > Check for Updates (Android Studio > Check for Updates on Mac). Otherwise, you can download it here.

This update includes fixes for several bugs, including the following:

For information on new features and changes in all preview builds of Android Studio 3.3, see the Android Studio Preview release notes. For details of bugs fixed in each preview release, see previous entries on this blog.

We greatly appreciate your bug reports, which help us to make Android Studio better. If you encounter a problem, let us know by reporting a bug. Note that you can also vote for an existing issue to indicate that you are also affected by it.


Android Studio 3.4 Canary 7 is now available in the Canary and Dev channels.

If you have Android Studio set to receive updates on the Canary or Dev channel, you can get the update by choosing Help > Check for Updates (Android Studio > Check for Updates on Mac). Otherwise, you can download it here.

This update includes the following change:
  • R8 now supports Android library projects.

This update includes fixes for several bugs, including the following::
  • Issue#116747159: Task generateDebugR2 fails on 3.3a12 when generating separate R classes.
  • Issue#119536413: Convert FixStackFramesTransform to a task.
  • Issue#112158840: Templates use deprecated classes if theme isn't appcompat.
  • Issue#116541301: Databinding v2 produces errors when another annotation processor fails.


For information on new features and changes in previous releases of Android Studio, see the Android Studio Preview release notes. For details of bugs fixed in each preview release, see previous entries on this blog.

We greatly appreciate your bug reports, which help us to make Android Studio better. If you encounter a problem, let us know by reporting a bug. Note that you can also vote for an existing issue to indicate that you are also affected by it.