Release Updates

Revision 8 of Android 10 x86_64 Google Play / Google APIs System Images

pondelok 30. septembra 2019

x86 32-bit images were released last Friday

Revision 8 of Android 10 x86 Google Play / Google APIs System Images

piatok 27. septembra 2019

Emulator 29.2.2 Canary: Google Maps UI on Windows, new Windows build, fixes for Maps / Multi Display UI

piatok 27. septembra 2019

Emulator 29.2.2 is now available in the Canary and Dev channels. This release is primarily about making the Google Maps UI available on Windows, and shipping fixes to both the Google Maps UI and Multi Display UI. Changes:

Google Maps UI is now available on Windows. The Windows emulator is now built with the MSVC toolchain. This is a big change; please let us know any issues running the emulator on Windows.

Google Maps UI: Fixed bugs and improved UX:
Fixed hang when switching back and forth between Points and Routes tab.
There should be fewer warning messages from Qt.
Tweaked colors, font, and letter spacing.
After playing back a saved route, the same saved route should still be selected and the map now re-shows the route creator with the same route. When playing an unsaved route, once stopped, the unsaved route shows up again with the option to save the route.
Fixed issue where usage metrics were not being sent.
The user can now delete multiple saved points/routes at once with multiple selection.
Improved styling of route playback panel.
Directions and markers should now persist when playing back a route.
If the Maps UI is disabled, the location agent now also properly disables itself so that the location is not always continuously being updated from the (disabled) Maps UI.
Clicking "Set Location" now clears the search box and selected point in the list.
Deleting a saved point now also clears the search box and map marker.
Zoom control is now no longer hidden by the lower Maps panel.
Improved styling of the popup menu.
Fixed issue where the selected status of routes in the routes list did not properly update on playing/stopping route playback.
Fixed issue with intermediate route waypoints not being displayed.
GPX/KML import and playback should now work again.

Multi Display UI: Fixed bugs and improved UX:

Ctrl-Shift-M can now be used to bring up the Multi Display UI.
Fixed issues with emulator window size not updating.
Tweaked button sizes, colors, font size of titles, and positions of icons.
Fixed issue where usage metrics were not sent.

Android P x86 System Images (Google Play, Google APIs) with ARM to x86 Translation - Canary

štvrtok 26. septembra 2019

x86 system images with translation versus ARM system images

Previously, Android app developers who needed to develop/test Android apps that used native ARM libraries could not use the x86-based emulator system images, and were forced to use system images with full ARM emulation, which are over 10x slower than the x86-based system images. Or, developers were forced to build or hunt down the x86 version in parallel. This is one of the top reasons app developers still resort to physical devices.

To address this, we've released P x86 system images that can also run apps with ARM native code. This leverages Google's ARM to x86 translation technology, which enables running native ARM apps at a much higher speed than with the actual ARM system images. App developers can then much more easily use the emulator to develop/test apps that are natively ARM or have native ARM dependencies. Note that the ARM to x86 translation technology enables the execution of intellectual property owned by Arm Limited. It will only be available on Google APIs and Play Store system images, and can only be used for application development and debug on x86 desktop, laptop, customer on-premise servers, and customer-procured cloud-based environments.
Why is x86 system with ARM to x86 translation faster?
The x86-based system images are fast due to leveraging CPU virtualization technologies such as HAXM and KVM, while the ARM system images are much slower due to having to emulate the entire stack, especially any system code and anything related to the memory management unit (MMU), which made basic memory read/write instructions very, very slow.
On the other hand, with an x86 system along with Google's ARM to x86 translation technology, we avoid the much more expensive system and MMU emulation, while only translating user-level code. This is a big win, as it allows memory accesses to proceed at near the original speed as if it were on x86, with the overhead confined to the bits related to instruction translation itself (and thus only being significant for CPU-bound apps (most apps being memory bandwidth or I/O bound)).

Known issues

Setting breakpoints in an ARM native library running in the translation environment is not supported. This is because the code that actually ends up running will be x86 code that is hard to map to the original ARM code in LLDB.
Since this is a technology that is getting new exposure and use cases, some app functionality may not work as expected. Please let us know of any issues through Issuetracker.
ARM64 is not yet supported.
This replaces any existing Android P x86 Google APIs / Google Play system image installation.

Emulator 29.2.1 Stable

pondelok 23. septembra 2019

Fixed crash on startup on Linux Wayland systems. This was because XkbGetKeyboard was used to query the host system's keyboard state. It seems usage of XkbGetKeyboard is not advisable on Linux and perhaps in general: https://github.com/glfw/glfw/issues/389

Big thanks to the /r/androiddev community for getting back to us quickly on this with getting stack traces and verifying the fix!

Fixed issue where keyboards with different letter mappings than QWERTY (AZERTY, QWERTZ, etc.) would end up typing the original QWERTY-mapped key. The previous unexpected behavior is actually due to a new input system where the emulator only sends raw keycodes to the guest OS; by also changing the Android guest's keyboard type to a different keyboard type, more keyboard types can be tested.

Keycode forwarding can still be used, but we need to ensure the Android guest is aware of the host keyboard type. We now require turning that on manually via -feature KeycodeForwarding.
A future system image update will automatically apply KeycodeForwarding-related guest side updates so the keyboard types on host and guest always match.
On Linux with non-US keyboards, we also found an issue where keycodes were not sent unless keycode forwarding was used. In this case, for now, please change the Android guest's keyboard type to the same keyboard type that you're using.

Updated metrics for Multi-Display UI.

Linux emulator now statically links libunwind.

Emulator 29.2.1 Canary

piatok 20. septembra 2019

Google Maps UI
Previously, it can be hard to work with virtual location settings because of the high barrier of entering lat/lon points manually and finding or generating GPX/KML files. Now, Extended Controls > Location includes an integrated Google Maps view, along with a point selector and route generator.
Individual points can be saved and re-sent to the device as the virtual location, while routes can be generated through typing in addresses or clicking two points. Each route can be replayed; locations along the route are sent in real time (or faster, according to a speed multiplier) to the guest OS. At the same time, GPX/KML can still be imported. Other notes:

Known issue: Not yet available on Windows. Further work needs to happen to stabilize the Windows build needed for Google Maps UI on Windows.
Known issue: Only available in Canary channel even if 29.2.1 is released to stable. This is so we have more time to get feedback and stabilize the feature.
We automatically attempt to fallback to the old UI if an incompatibility or failure to load Google Maps happens.

Fixed crash on startup on Linux Wayland systems. This was because XkbGetKeyboard was used to query the host system's keyboard state. Usage of XkbGetKeyboard turns out to be not advisable on Linux Wayland and perhaps in general (for example: https://github.com/glfw/glfw/issues/389)

Big thanks to the /r/androiddev community for getting back to us quickly on this with getting stack traces and verifying the fix!

Fixed issue where keyboards with different letter mappings than QWERTY (AZERTY, QWERTZ, etc.) would end up typing the original QWERTY-mapped key. The previous unexpected behavior is actually due to a new input system where the emulator only sends raw keycodes to the guest OS; by also changing the Android guest's keyboard type to a different keyboard type, more keyboard types can be tested.
Keycode forwarding can still be used, but we need to ensure the Android guest is aware of the host keyboard type.
We now require turning that on manually via -feature KeycodeForwarding.
A future system image update will automatically apply KeycodeForwarding-related guest side updates so the keyboard types on host and guest always match.
On Linux with non-US keyboards, we also found an issue where keycodes were not sent unless keycode forwarding was used. In this case, for now, please change the Android guest's keyboard type to the same keyboard type that you're using.
Updated metrics for Multi-Display UI.
Linux emulator now statically links libunwind.

Android Studio 3.6 Canary 12 available

streda 18. septembra 2019

Canary or Dev channelHelp > Check for UpdatesAndroid Studio > Check for Updatesdownload it here Fragment wizard and new fragment templatesFileNewFragmentGalleryCreate new destination General fixesAPK Viewer

Issue #137130596: Analyze apk could not be completed.

Data Binding

Issue #140645228: Variables declared in other same name layout files are not recognized

Issue #139933333: Unresolved binding fields in nested controls

Dexer (D8)

Issue #140290149: Class module-info is missing a super type. Class file version 53.

Editing

Issue #140362782: Files created by templates are not picked up by resource repositories

Layout Editor

Issue #140678037: Visualization tab disappears in 3.6 Canary 10

Lint

Issue #133465551: Lint 26.5.0-beta02 DefaultLocale triggers on Kotlin's decapitalize method

New Project Wizard

Issue #138951281: Create New Module wizard is blocked by Project needs to be converted to androidx.* dependencies

Run Debug

Issue #138127703: Misleading DDMS message

View Binding

Issue #136103081: <include> inside <merge> is not allowed

Android Studio Preview release notesreporting a bugvote for an existing issue

Updates archive

Subscribe to updates