We've just released Android Studio 1.1 Preview 2 to the canary and dev channels. As mentioned last week for preview 1, the focus for version 1.1 is bug fixes; we are working in parallel on version 1.2 where we are migrating to the IntelliJ 14 codebase, among other feature work.
In this build, there are several new lint checks:
In addition, the default launcher icons have been updated to a Material Design look, and it now also includes an xxxhdpi density icon.
56986: Incorrect flag for portuguese
59042: strings.xml reformated every time I create new Activity
77158: Sync removes modules that do not have a Gradle counterpart.
81457: Fixes low resolution icon in Linux.
82387: Add intention to correct XML namespace for support lib
82564: Making AVD Manager separate (non-modal) window.
92005: Allow cancelling task that retrieves device screenshots
93284: Including comments when merging xml
94499: Fixing the device preview in the search and create cases
97006: Gradle lint does not recognize Context.getDrawable() as API 21+
98297: Fix run dialog modality to allow avd manager interaction
98317: Fixing resource merge to work within new project wizard
98997: Pick test runner from Gradle while creating test configuration
101279: Fix id reference check to properly handle undefined id's
103257: Append .exe extension on Windows (mksdcard)
103257: Welcome Wizard, on Windows, shows "Tools directory not found" error incorrectly
+ Bug fixes not tagged with a bug number in the commit message.
You can manually check for updates via Help > Check for Update... (on OSX, look in the Android Studio menu). This will download and install a small patch rather than download a full IDE image. If you are using an older version, you'll need to download a full install from the downloads page.
NOTE: 1.1preview2 is currently only available in the canary and dev channels, and Android Studio will by default look in the Beta or Stable channels, so if you want to update, open the preference dialog, go to the Updates category and change the channel setting.
If you run into problems, be sure to check the Known Issues page which we'll update as necessary
Recent Changes >