text:
Android Emulator is included with Android Studio.
Versions of the emulator prior to 25.3.0 were distributed as part of the Android SDK Tools.
To ensure you have the latest version, check the SDK Manager for updates.
For Android Emulator versions prior to 25.3.0, see the Android SDK Tools release notes.
For details of bugs fixed in each release, see the Android Studio release updates blog.
30.0.10 (April 30, 2020)
This update includes support for running the emulator directly in Android Studio and virtual devices with Freeform Window Mode activated by default.
Run the Emulator in Android Studio
The Android Emulator can now be run directly in Android Studio. Use this feature to conserve screen real estate, to navigate quickly between the emulator and the editor window using hotkeys, and to organize your IDE and emulator workflow in a single application window.
Freeform Window Mode
You can now create an AVD that has Freeform Window Mode enabled by selecting the 13.5" Freeform tablet hardware profile when creating a virtual device in Android Studio. This hardware profile requires a system image with Android 11 Developer Preview 3 or higher.
Known issues
Resizing freeform windows is currently broken due to issues transferring focus to the Window Manager. This will be addressed in a future Android 11 system image release.
30.0.0 (February 19, 2020)
This update includes Android 11 (API level 30) system images and improved performance when running ARM binaries.
Android 11 system images
You can now create an AVD that runs Android 11 by selecting either of the available API level 30 system images:
- x86: Includes both x86 and ARMv7 ABIs.
- x86_64: Includes x86, x86_64, ARMv7 and ARM64 ABIs.
Support for ARM binaries on Android 9 and 11 system images
If you were previously unable to use the Android Emulator because your app depended on ARM binaries, you can now use the Android 9 x86 system image or any Android 11 system image to run your app – it is no longer necessary to download a specific system image to run ARM binaries. These Android 9 and Android 11 system images support ARM by default and provide dramatically improved performance when compared to those with full ARM emulation.
Known issues
- Some ARMv7 binaries fail to run on Android 11 x86 and x86_64 system images. Consider building for ARM64 when targeting Android 11.
29.0.11 (May 29, 2019)
This update includes the following improvements and fixes:
- Windows: The emulator now relies on the
libgccDLL that we ship instead of being compiled with
- Linux: Added logcat support to the gRPC API. For more information about gRPC, see gRPC streaming emulator (Linux).
- The emulator now includes a headless build for 32-bit x86 guests
qemu-system-i386). This feature enables x86 32-bit images for API levels 26 and lower to run with the headless build. Note that for 32-bit x86 guests with API 27 and later, the emulator uses the 64-bit engine (
qemu-system-x86_64) because in these system images, while the userspace is 32-bit, the kernel is 64-bit. Android Studio uses the kernel to select emulation engines.
- You can now specify custom Qt library paths using the
ANDROID_QT_LIB_PATHenvironment variable.
- You can now run the emulator with previous binaries that use QEMU1 if the
QEMU1 executables (
emulator[64]-[x86|arm|etc]) are placed in the emulator directory.
- Windows: Fixed an issue that could sometimes cause the emulator to fail to start with a "vCPU shutdown request" message.
- Fixed an issue with an unnecessary pipeline barrier in emulated compressed textures in Vulkan.
- Fixed an error that occurred with http proxy requests when chunked transfer encoding was used. For more information, see the commit details.
29.0.9 (May 7, 2019)
This update includes the following fix:
- Windows: Fixed an issue where the virtual scene camera and webcam would not work on the emulator.
29.0.8 (May 6, 2019)
This update includes the following improvements and fixes:
- Added support for multiple virtual hardware displays when there's a guest service to enumerate and set each display. Multiple virtual hardware displays will be included in a future emulator system image update.
- Added a new command line option:
-delay-adb. This option suppresses processing of ADB packets until the guest has completed booting (off a cold boot). This option helps resolve issues that could occur if you use the emulator in a CI environment that reboots the emulator and uses DDMS at the same time.
- Fixed an error that occurred when snapshots are loaded where
glIsRenderbufferwould return the incorrect value.
- Fixed some issues with stale state when the Android guest reboots.
- Windows: Fixed issues that prevented the emulator from starting when the Windows username had non-ASCII characters or spaces.
Known issues
- The Snapshots UI is disabled for Automotive system images because snapshots aren't currently supported for these system images.
29.0.6 (May 1, 2019)
This update includes several new features, improvements to existing features, and bug fixes.
Removal of QEMU1 and 32-bit Windows support
To better maintain the emulator, we no longer ship QEMU1 and 32-bit Windows binaries. If you are using Windows 32-bit, you cannot upgrade to version 29.0.6.
Requirements for Android Q system images
If you want to run an AVD that uses an Android Q system image, you must now use version 29.0.6 (this release version) or higher.
Project Marble Improvements
This update continues our work on the Project Marble initiative that was announced at the Android Developer Summit in November 2018. For more information about other Project Marble improvements in previous releases, see Android Emulator: Project Marble Improvements.
For this update, most of our Project Marble efforts were dedicated to reducing emulator resource usage, such as reducing the emulator's CPU usage while idle. We've also included changes that make it easier to work with the emulator in a wider variety of environments, and we've addressed general quality issues.
The following sections describe the Project Marble improvements that are included with this update:
Improvements for host audio behavior
Starting with version 28.0.3, the emulator blocks audio input from the host by default.
If you want to use the host audio data, you can enable that option by going to Extended Controls > Microphone and enabling Virtual microphone uses host audio input. This option is automatically disabled whenever the emulator is restarted.
If you are using the command line, you can also enable host audio using the
-allow-host-audio option, and you can use the following ADB commands to turn
host audio data on or off, respectively:
adb emu avd hostmicon
adb emu avd hostmicoff
Improvements for headless emulator builds
Starting with version 28.0.25, the emulator includes a headless build option that can run without the UI. You can use headless builds to help you set up the emulator for Docker and continuous integration (CI) workflows.
With this update, we've made further improvements to allow the emulator to run
with a minimum number of dependencies. On Linux, headless builds no longer
include the
pulseaudio or
libX11 libraries. The system-dependent shared
libraries that are not packaged with the emulator has been reduced to the
following list:
Upgraded Qt UI libraries to 5.12 LTS
This update includes the following improvements from the Qt 5.12 LTS release:
- To avoid crashes in Qt's
libpngdecoding when starting certain system images, the emulator now uses its own copy of
libpngto decode PNG images.
- To address issues with some Linux installs containing incompatible versions
of some Qt dependent libraries, we now package
libsqlite3, and
libxkbcommonwith the emulator.
- The emulator now uses the platform's native windowing libraries to get monitor dimensions, instead of using the Qt libraries that returned unreliable results.
Automatic CPU optimizations after cold boot
To address CPU usage, the emulator now runs the following ADB commands on a cold
boot after it receives a
boot complete signal:
adb shell settings put screen_off_timeout 214783647
- This command increases the screen off timeout so the emulator can be used in battery mode without charging. In battery mode, background CPU usage is greatly reduced.
- In AC charging mode, GMSCore background operations such as app updates can take over all the device's CPU cores—and by extension, the user's machine—with no warning.
adb shell pm revoke com.google.android.googlequicksearchbox android.permission.RECORD_AUDIO
- This command revokes microphone permissions for the Google search app, which greatly reduces background CPU usage on the home screen and in the launcher when the Google search app is active.
- This command is run in addition to the emulator's default behavior of disabling host audio for the host. Furthermore, this automatically provides the CPU usage mitigation described for hotword detection from the 28.0.23 release.
New environment variables for performance monitoring
You can now use two new environment variables to enable detailed monitoring of the emulator's performance and resource usage.
- This environment variable enables tracking of both CPU and RAM usage. Tracking for RAM usage distinguishes between graphics usage and total resident memory.
- This environment variable enables printing every time an input or graphics operation takes a long time (longer than 1 ms).
- We're also using this environment variable to help diagnose issues that Windows users have experienced with more jank (dropped frames) than users experience on macOS or Linux.
General Project Marble improvements
This update also includes the following general improvements that are part of the Project Marble initiative:
- You can now immediately pause all vCPUs on the emulator via the following console commands:
adb emu avd pause
adb emu avd resume
- Greatly reduced overhead of OpenGL drawing. This improvement reduces CPU usage while the emulator is playing animations.
- Restored support for mainline QEMU's e1000 virtual network device. You can use this device to set up the emulator in a bridged network environment. In a bridged network environment, the emulator is shown on the host network and the host network is shown on the emulator.
- QEMU 2.12-appropriate BIOS binaries are now used to start up the emulator.
- Upgraded
ffmpegversion to 3.4.5 for video encoding and decoding.
- Greatly reduced overhead of QEMU main loop I/O on macOS by replacing the main
loop that was based on
select()with a main loop that is based on
- Logcat buffer size increased to 2 MB to address issues with flaky unexpected EOF when running logcat with the emulator.
- The emulator now exports the
LC_ALL=Cenvironment variable by default. This change addresses crashes and incompatibility issues associated with running the emulator in different locales.
- You can now track the CPU and RAM usage of the emulator using performance stats that you can access at Extended Controls > Settings > Advanced > Performance Stats. Use these stats to quickly diagnose issues if the emulator seems to be using too much CPU or RAM.
glReadPixels GL_IMPLEMENTATION_COLOR_READ_TYPEnow uses the host GPU's result instead of an emulated one. This change helps fix issues where images and assets do not display because of improper format for readback.
- Added support for the OpenGL ES extensions
GL_APPLE_texture_format_BGRA8888if these extensions are supported by the host.
- Added more diagnostic info to the Bugreport UI. In addition, you can access
bug reports from the console using the following commands:
telnet localhost 5554
avd bugreport
- On Android Q system images, the emulator increases its minimum RAM size to 2 GB.
- Added more logging and printing whenever OpenGL or the hypervisor fails to initialize.
- If the emulator cannot start a concurrent
-read-onlyinstance of an AVD, the emulator now attempts to relaunch the
-read-onlyAVD 3 more times over 3 seconds. This change increases the likelihood that the emulator will be able to launch concurrent
-read-onlyinstances an AVD if other writable instances of that AVD are not done cleaning up stale files.
- For upcoming system images, the emulator now supports Hardware Composer 2.0. This change should lower the driver overhead when running most animations.
- The emulator build is now based on CMake/Ninja.
- In the emulator extended controls UI, divider lines in the keyboard shortcuts table have been restored.
- Users can now opt-in to provide our team with CPU and RAM usage metrics in a 10 second interval. We use these metrics to enrich our data about emulator resource usage with different use cases from our users, which allows us to make the emulator more efficient and responsive.
General Project Marble fixes
This update also includes the following general fixes that are part of the Project Marble initiative:
- Fixed issues with twitching and incorrect frames that were displayed on systems with Intel GPUs when using Android Q system images.
- Fixed issues where a black screen was displayed when using Android Q system images with Pixel 2 XL skins (or any skin that has a notch or rounded corners).
- Fixed an issue where the
-partition-sizecommand line option would not set the data partition size.
- Fixed an issue where pulseaudio on the Linx emulator would spin and take up an entire CPU core in some situations.
- Fixed issues with out of bounds memory access when processing compressed textures.
- Fixed GL errors that occurred on the host in
glTexSubImage2Dwhen updating certain gralloc buffers (with format RGB 565, RGB10A2, RGB(A)16F).
- Fixed a display issue in Android Q system images with snapshots where the notification shade's geometry was rendered with an improper instance divisor setting.
- Fixed a few hard-to-reproduce crash and freeze issues on launch that happened due to Qt losing signals or having flaky, inconsistent states on startup.
- Fixed numerous concurrency issues. We are now able to build the Linux emulator with ThreadSanitizer (TSAN), which can easily uncover bugs that are otherwise difficult to reproduce.
- For Linux users: we have found that on certain host kernels, the guest Android
kernel can error out and exit in KVM with a generic hardware error. The emulator
will now
abort()when this happens in order to increase debuggability (previously, the emulator just hung).
- For Linux users: for convenience with CI setups, you can use the new
-stdouterr-file <file-name>command line option to redirect both
stderrto a file.
- Fixed an issue where
SO_REUSEADDRwas used incorrectly. For more information, see the commit details.
- Fixed a long-standing issue with the Windows emulator where sub-processes, such as ADB commands, failed to start if the username had spaces in it.
- Fixed an issue with missing initialization of RCU in HAXM vCPU threads. This fix can possibly address some crashes and race conditions.
- Fixed a crash that happened with certain patterns of saving and loading snapshots from the snapshots UI using recent Android Q system images.
- Fixed an issue where the virtual scene camera would be blank when the emulator was initialized from a snapshot if an AR macro was playing when that snapshot was saved.
- Fixed an issue where some users with remote desktop setups got a black screen
when launching the emulator on Linux. To avoid this, the emulator now explicitly
MESA_RGB_VISUAL. For more information, see the commit details.
- Fixed an issue where the rotate buttons would appear on TV AVDs.
- Fixed an issue where if emulator was set always on top, the extended controls window appeared every time the emulator was rotated.
Hardware profiles for foldable devices
The emulator now includes hardware profiles for foldable devices. To use these new hardware profiles, you must be using Android Studio 3.5 Canary 10 or higher.
There are two foldable hardware profiles that you can use to create an AVD:
- 7.3" Foldable: 1536x2152 unfolded, 4.6" 840x1960 folded
- 8" Foldable: 2200x2480 unfolded, 6.6" 1480x2480 folded
When you run the emulator using one of these hardware profiles, you can fold and unfold the device using the fold and unfold actions in the emulator toolbar, console commands, or the following keyboard shortcuts:
- Fold:
Ctrl + F(
Command + Fon macOS)
- Unfold:
Ctrl + U(
Command + Uon macOS)
AR macros
The emulator now includes AR macros that can help you test common AR actions. For example, you can use a macro to reset all the device's sensors to their default state.
For more information, see Test common AR actions with macros.
Vulkan support (Windows, Linux)
Windows and Linux users can now test Vulkan apps with the Android Emulator up to Vulkan 1.1 when using a compatible system image (Android Q Beta 3 or higher for Vulkan 1.1, Android Q Beta 2 for Vulkan 1.0) and a compatible host GPU (this includes most Intel, NVIDIA, and AMD GPUs from 2014 and later).
To enable Vulkan support, you must add the following feature flags to your
~/.android/advancedFeatures.ini file (create the file if it doesn't exist):
Vulkan = on
GLDirectMem = on
Initial support for ROM developers
ROM developers who are building the
sdk_phone_x86 or
eng variants) targets on AOSP
master branch can now run a
Vulkan-enabled emulator.
This support is still experimental and is mainly for developers who work on
system images, drivers, and game engines. Many extensions are still missing.
HOST_COHERENT memory is supported, and you should now be able to
run the Vulkan API Tutorial Samples.
If you are using linux, you can try this by using the following commands:
mkdir aosp-master
cd aosp-master
repo init -u https://android.googlesource.com/platform/manifest -b master --depth=1
repo sync -c -j12
. build/envsetup.sh
lunch sdk_phone_x86_64-userdebug
make -j12
emulator -no-snapshot -feature Vulkan,GLDirectMem
Skia rendering with Vulkan
NVIDIA and AMD GPUs that support Vulkan also support zero-copy interop with
OpenGL via the
GL_EXT_memory_objects extension. The emulator leverages this
capability to provide a complete way to render the Android UI using the Skia
Vulkan APIs.
If you have an NVIDIA or AMD GPU that supports Vulkan, use the following commands to test the Skia rendering with a compatible system image (Android Q Beta 3 and higher):
adb shell
setprop debug.hwui.renderer skiavk
macOS support for Vulkan
macOS support is still experimental, but the emulator already includes the Swiftshader, MoltenVK, and libportability (gfx-rs) APIs. You can experiment with these APIs by setting the following environment variables:
- Swiftshader:
- MoltenVK:
- libportability:
Known issues
HAXM can sometimes fail to map Vulkan coherent memory to the guest and shuts down the emulator. This is addressed in an upcoming HAXM update.
gRPC streaming emulator (Linux)
We're always trying to make the emulator as versatile as possible by allowing host GPU rendering and interactivity in the widest range of running contexts. Our CI and remote desktop users have the following long-standing issues:
- Programmatically sending input commands to the emulator involves either running adb shell commands that can experience high overhead, or using the telnet console, which is faster, but might not work with certain network configurations.
- CI users often run emulators headless, which can make it difficult to notice issues that require the screen to be visible or interactive.
- Remote desktop users often can't interact with the emulator when using host GPU rendering because GPU rendering is often tied to the host's non-virtual displays.
To address this, when running on a Linux machine, the emulator now serves a gRPC service. gRPC is a general framework for RPC that works over HTTP.
By default, the emulator gRPC service is disabled, but you can activate the
service using the following command line option, where
is the port which the emulator should serve gRPC requests (usually
-grpc <port>
Once the service is started, gRPC commands can then be issued from clients. The current set of commands allows both sending input events and receiving screenshots. These commands help address the following issues:
- Input commands can be sent to the emulator with low overhead over HTTP. HTTP also enables commands to be sent in additional network configurations.
- Screenshot commands can be sent to query the current screen, even if the emulator is running headless. For interactivity, input events can also be sent back to the emulator.
- Remote desktop users can run the emulator headless on the main display with GPU accelerated rendering while using gRPC to get screenshots and send input events in order to interact with the emulator.
For a complete list of the commands that are available, see this protobuf.
To help you get started with gRPC, we've provided some sample clients that you can refer to.
Currently, this includes the following samples:
- A Go-based service that can be used to query emulator states.
- A React app that demonstrates remote interactivity via screenshot and input RPCs. This sample requires protobuf version 3.7.0 or higher.
- A Python sample that queries the emulator's VM configuration and then sends a series of commands.
28.0.25 (March 29, 2019)
This update includes the following improvements and fixes:
Headless emulator build
The emulator has been difficult to set up with Docker and other continuous integration (CI) workflows due to the implicit expectations of the system being able to support Qt along with its shared library dependencies (among other issues).
As a first step to address this, we've introduced a variant of the emulator
launcher with QEMU executables that does not depend on Qt. On Linux, there is
still a link to
libX11, but we hope to remove that soon as well.
To use the headless emulator, run the emulator from the command line as usual,
but replace the emulator binary invocation with
emulator-headless. For more
information, see the 28.1.8 Canary
release update.
- Fixed twitching and incorrect frame display on Intel GPUs when running Android Q system images.
- Fixed issues where black screen would display when using Android Q system images with Pixel 2 XL skins.
- The latest BIOS binaries are now used to start up the emulator. This change can help reduce "vCPU shutdown request" errors that happen sometimes when launching the emulator on Windows.
- Backported a fix for the "wrong display when resuming Android Q system images from a snapshot" issue.
- Users were experiencing "unauthorized" emulators issues
due to an incompatible change in ADB in platform-tools 28.0.2. You can
now safely use ADB from platform-tools 28.0.2 with the emulator. If you are
experiencing problems with "unauthorized" emulators, do the following
troubleshooting steps:
- Exit all emulators.
- Delete both the
- Run the following command:
adb kill-server
- Run the following command:
adb devices
- Wipe the AVD data.
- Relaunch the emulator.
28.0.23 (January 29, 2019)
This update includes the following improvements and fixes:
Host audio input disabled by default
A recent post on Reddit detailed how the guest Android OS would always be using the host microphone's audio, and thereby allowing "Ok Google" to work unexpectedly. We're sorry about this and will work with the Android team to make sure hotword detection is disabled in the system image as well.
To address this, we've made the following changes:
- Actual host audio data is now squelched by default. When the guest uses the microphone, silence is passed over instead of the host's audio.
- If you want to use the host audio data, you can now enable that option by going to Extended Controls > Microphone and enabling Virtual microphone uses host audio input. This option is automatically disabled whenever the emulator is restarted.
Updates on CPU usage investigations
During our Project Marble investigations, we've noticed that high CPU usage on the emulator generally falls into the following three categories:
At idle: Automatic app updates in Play Store images
We found that at random intervals, all apps installed get updated, even when the user is not logged in. During the process, CPU usage is driven to the number of cores x 100% (typically ~400%) in GMSCore and dex2oat. You can mitigate this issue by disabling auto app updates in the Play Store app.
At idle: Hotword detection
When on the home screen and without any app foregrounded, there can be a great deal of CPU usage (~25% with spikes to 50%). This is caused by hotword detection that constantly pings the host. You cannot mitigate this issue by disabling host audio input because the CPU cost is primarily caused by the time that it takes to travel to the guest from the host. However, you can mitigate this issue by revoking microphone permissions from the Google app.
While active, sometimes at idle: Animations
The third source of high CPU usage is animations. We have found that by optimizing the graphics driver stack we can also reduce CPU usage even when the emulator is not idle. We will be rolling out graphics driver optimizations incrementally as part of Project Marble.
28.0.22 (December 21, 2018)
This update includes the following improvements and fixes:
- Fixed a long-standing issue where in some settings, the Mac emulator would reboot or kernel panic on Quickboot save. (Issue 120951634)
- When using a mapped file as the RAM snapshot, the emulator now unmaps the file mapping explicitly on exit.
28.0.20 (December 11, 2018)
This update includes the following improvements and fixes:
- Fixed an issue on Windows that caused the emulator to freeze on snapshot load with certain models of Intel GPUs.
- Fixed an issue that caused an
unauthorizedADB device state when using a non-standard
- Fixed an issue on Windows that caused the emulator to crash when booting system images with CPU acceleration disabled.
- Fixed the pixelated emulator display issue. Downsampling should now be working.
- Fixed an issue on 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 cause the emulator clock to sporadically change.
- 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 Wi-Fi peer-to-peer, start two AVDs with the same
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.
28.0.16 (November 2018)
This update includes several new features, improvements to existing features, and bug fixes.
Resource usage
The emulator now uses less RAM overall, especially when using system images with API level 28 or higher. These system images include improved memory usage for guest-side graphics drivers.
In addition, we have also improved resource usage in the following areas:
- Reduced emulator memory usage during long-running tests. If you still experience issues with memory usage during long-running tests, please create an issue that describes your use case in Issue Tracker.
- Reduced CPU usage when running apps with animations.
- Fixed an issue where the QEMU AIO context could leak on Windows.
Run multiple instances of a single AVD concurrently
You can now launch multiple instances of the same AVD and run them concurrently. Instances that you launch after the first instance are read-only, and their changes to the guest virtual disk are discarded on exit.
To run multiple instances of the same AVD at the same time, launch any instances
after the first instance from the command line using the
-read-only flag.
This feature is made possible by copying the QCOW2 files associated with the
writable parts of the Android image. To help you manage disk space, we have also
bundled the
qemu-img command line tool to allow you to pre-commit QCOW2
files before launching multiple instances.
In addition, when used in tandem with the File-backed guest RAM snapshots feature, multiple AVD instances share the primary AVD Quickboot snapshot as a common source of copy-on-write guest RAM. This property means that the instances share much of their RAM in common. Use this feature to run tests that require multiple devices to run in parallel.
We appreciate your feedback on possible use cases that are part of your normal interactive or CI workflow. Please create or upvote issues in Issue Tracker.
File-backed guest RAM snapshots
By pre-allocating and mapping guest RAM as a file, the emulator can now save Quickboot snapshots during runtime, instead of doing all of the work on exit. If you currently experience long save times when closing your emulators, enable this feature to improve your Quickboot performance. By default, a Quickboot snapshot is saved on exit and loaded again every time, like suspending and waking a real device.
Because Android guest RAM is now auto-saved by default, if you want to define a device state and repeatedly load from that state, you need to tell the emulator to discard changes after each session. You can do this in the following ways:
- Use the
-read-onlyflags when launching the emulator from the command line.
- Go to Extended Controls > Snapshots > Settings and switch Auto-save current state to Quickboot? to No.
- You will need to restart the emulator after selecting this option. If the
emulator is set to auto-save, you can run the following command to set a
adb emu avd snapshot remap 0After you run this command, the emulator Quickboot snapshot will stay at that checkpoint. Run the same command again to load the emulator from your checkpoint.
Snapshots that are taken and loaded through the Snapshots UI function as they did before, with no file mapping.
Because this is a large change to how Quickboot works, we would greatly
appreciate your feedback on whether it improves Quickboot performance and what
kind of issues you encounter when using it. If you experience problems, you can
disable this feature by adding the following line to your
~/.android/advancedFeatures.ini file:
QuickbootFileBacked = off
When you start the emulator from a snapshot (either using the
command line option, or launching from a snapshot in the AVD manager) the
emulator disables both auto-saving for Quickboot snapshots and saving Quickboot
snapshots on exit. This reduces the chances that the Quickboot snapshot will be
unintentionally overwritten, and avoids slow fallback paths that do not use
file-backed Quickboot snapshots.
We have rebased our variant of QEMU from QEMU 2.9 to QEMU 2.12. This update includes the following QEMU changes:
- https://wiki.qemu.org/ChangeLog/2.10
- https://wiki.qemu.org/ChangeLog/2.11
- https://wiki.qemu.org/ChangeLog/2.12
Here are some of the notable changes that impact the Android Emulator:
- x86:
gdbstubnow provides access to SSE registers.
- Disk images: Image locking is added and enabled by default. Multiple QEMU processes cannot write to the same image as long as the host supports OFD or posix locking, unless options are specified otherwise.
qemu-img: qemu-img resizesupports preallocation of the new parts of the image.
- QCOW2 shrinking now supported in
- Fixed issues with screen readers and added better support for these tools in the Screen Record and Snapshot UI.
- Made the Quick Boot notification icons more accessible to users who are color blind.
- Fixed an out-of-bounds memory access issue that could occur for OpenGL ES vertex array pointers.
- Some older GPUs did not support OpenGL 2.1 or greater (which is required), or had other reliability issues. These issues could cause the emulator to crash on start, freeze, or be unusable on the default GPU setting. The emulator now automatically switches to the Swiftshader renderer if it detects that these GPUs are in use.
- Fixed an issue that caused the emulator to not post the correct framebuffer if
FBO != 0was bound at the time of
- Fixed issue where the virtual Android display would only show up in the top left corner. We believe this was due to misconfigured Qt environment variables. The emulator now overrides all Qt scaling-related environment variables.
- Fixed an issue where the emulator crashed in some situations when loading GLES1 apps from a snapshot.
- Fixed concurrency issues in OpenGL and launching render threads that could result in double frees or corrupted data.
- Android Emulator now supports ASTC LDR compressed texture support
GL_KHR_texture_compression_astc_ldr) for system images that use API level 28 or higher.
- Most modern GPUs should now be able to launch the emulator with OpenGL ES 3.x
enabled by default without using the
GLESDynamicVersionfeature flag.
-gpu guest(software rendering in the guest) has been deprecated. System images for API level 28 or higher now automatically switch to using Swiftshader instead (
-gpu swiftshader_indirect).
- If the emulator is launched from the command line using the
-no-windowflag, the default renderer is now Swiftshader.
- The emulator can now update bearing along with latitude and longitude position. The magnetometer virtual sensor adjusts itself dynamically to magnetic north by inferring motion when playing back a GPX or KML file.
- Device speed can now be set on the Location page.
- When playing back a GPX or KML file, the speed is set automatically, and is set to zero when the playback ends.
- The altitude is no longer restricted to being between -1,000 and +10,000 meters.
- Fixed an issue where the virtual GPS location would not be updated periodically unless the Extended Controls window was opened at least once.
On Windows, more webcams are now supported because the emulator dynamically resizes the camera frames that are delivered from the webcam. This feature also prevents errors in frame delivery from causing the emulator to hang.
Play Store
To address issues with running out of disk space on Play Store images, the emulator now automatically resizes the userdata partition to 6 GB when running with a fresh Play Store AVD.
General quality improvements and fixes
- Some users reported that the emulator has been running slow. We identified one
possible cause where the temp directory for the emulator ends up with too many
stale files inside. As a workaround, the emulator no longer stores ADB liveness
check files in that directory. However, it may also help to delete the contents
of that folder. The folder is located in one of the following locations,
depending on your operating system:
- Windows:
- macOS or Linux:
- Windows:
- If the emulator is unable to start due to insufficient free RAM, an error message is now displayed. If you are on Windows and notice that there is RAM free, but you are still unable to start the emulator, the commit charge may have been exceeded. For help with this issue, see the emulator Troubleshooting page.
- The
-sysdircommand line option now properly overrides the inferred system image directory.
- Virtual modem now supports the model activity info
- Fixed various issues with memory leaks, memory corruption, and CPU usage. If you are experiencing crashes, memory leaks, or other high resource usage, please create an issue in Issue Tracker.
- Fixed an issue that reappeared on macOS 10.14 where using Bluetooth headsets with the emulator would degrade audio globally. To prevent this, the emulator now avoids using Bluetooth audio when running on macOS. (Issue 37070892)
- Fixed an issue on Windows where the emulator clock would not be in the correct timezone.
- Fixed emulator slowness and hangs on Linux systems with spinning harddrives (HDDs).
- Fixed some compile warnings that could lead to stack corruption on macOS.
- Fixed issues that could result in misleading reports of hanging.
- Fixed an issue with destroying thread pools that could cause a crash if one of the threads was not successfully created.
- Fixed an issue on macOS where timers would become unreliable, leading to hangs and other strange behavior. If you experience emulator hangs on macOS, please create an issue in Issue Tracker.
- Fixed an issue where closing the emulator would disable the UI, but not actually close the emulator.
- Fixed issues involving sporadic crashes, including an abort due to opening too
many instances of
- Fixed an issue that caused the emulator to fail to start after the first time if ADB was terminated forcefully.
- The MIPS build has been removed. If you still require MIPS, please create an issue in Issue Tracker.
- Fixed an issue where ADB connections could become corrupt on snapshot load.
- Fixed an issue where the emulator window would have an afterimage or teleport offscreen when resuming a snapshot where the device orientation was different from the AVD's default orientation.
- Fixed issues involving crashes when saving snapshots.
- On Linux, btrfs filesystems can cause extreme slowdowns because the emulator
automatically saves snapshots and uses copy-on-write for its virtual disk
devices. We recommend cleaning out the
~/.android/avddirectory and running the following command on the empty
chattr +CThis creates new snapshots in a folder where copy-on-write is disabled.
We would like to mention HAXM 7.3.2 again because it must be installed in order for recent system images to run properly on the emulator. HAXM 7.3.2 should already be available in the Stable channel, and can also be installed manually from https://github.com/intel/haxm/releases.
Here are a couple of the issues that this version of HAXM resolved:
- Fixed random crashes of guest OSes that use a recent Linux kernel (>= 4.6). For example, Ubuntu 18.04 (#39, #74).
- Fixed an x86 instruction emulator bug that could lead to a host crash (#93).
32-bit Windows deprecation
Due to low usage and high maintenance costs, we are planning to deprecate the 32-bit version of the Android Emulator that runs on Windows. We will roll out a transition plan before removal and end-of-life for the 32-bit version of the Android Emulator. However, we are actively seeking any feedback or concerns with this future change.
Please let us know in Issue Tracker if you currently rely on the 32-bit version of the Android Emulator that runs on Windows and tell us how we can best work with you going forward.
27.3.10 (August 2018)
This update includes the following bug fix:
RAM size configuration fix
Some users reported that the emulator has been running slow. We identified one
possible cause where the AVD RAM size in the AVD's
config.ini file was being
set incorrectly.
To mitigate this, the emulator increases the minimum RAM level for images that
use API level 26 or higher to the Android Studio default level of 1536 MB. If
your AVD's
config.ini file is not listing
hw.ramSize in megabytes,
please create an issue in Issue Tracker.
You can find the
config.ini file in the following location:
27.3.9 (July 2018)
This update includes the following improvements and bug fixes:
Improved error messages for Windows Hypervisor Platform
Some users were having difficulty diagnosing why the Windows Hypervisor Platform
(WHPX) failed to initialize when they activated a WHPX emulator. To help you
diagnose these issues, we have added more informative error messages. You can
enable these error messages by running the emulator from the command line using
-verbose flag.
General fixes
- Fixed OpenGL errors that occur when loading a snapshot in the camera app.
27.3.8 (July 2018)
This update includes several new features, improvements to existing features, and bug fixes.
You can now save multiple AVD snapshots for a given device configuration and choose which of the saved snapshots to load when you start the emulator.
Starting with Android Studio 3.2 Canary 13, each device configuration includes a control in the advanced settings in the Virtual Device Configuration dialog with which you can you can specify which AVD snapshot to load when starting the AVD.
To accommodate this expansion of the snapshot features, we have added a Snapshots category to the Extended controls dialog. This new pane contains controls for saving and loading AVD snapshots, including the controls for saving and loading the quick-boot snapshot that had previously been in the Settings pane.
You can edit the name and description of each saved snapshot.
For details, see Snapshots.
HAXM 7.2.0 is now available in all channels.
This update includes bug fixes and improved support for large amounts of RAM. Also, with this HAXM update and Emulator 27.3 and later, snapshots load their contents into RAM on demand rather than loading the entire snapshot when the virtual device starts. This change should greatly decrease the time needed to load a snapshot.
For details, see Configuring VM acceleration.
27.2.9 (May 2018)
This update includes several new features, improvements to existing features, and bug fixes.
Screen recording
You can now record video and audio from the Android Emulator and save the recording to a WebM or animated GIF file.
The screen recording controls are in the Screen record tab of the Extended Controls window.
Tip: You can also open the screen recording controls by pressing Control + Shift + R (Command + Shift + R on Mac).
To begin screen recording, click the Start recording button in the Screen record tab. To stop recording, click Stop recording.
Controls for playing and saving the recorded video are at the bottom of the Screen record tab. To save the video, choose WebM or GIF from the menu at the bottom of the tab and click Save.
You can also record and save a screen recording from the emulator using the following command on the command line:
adb emu screenrecord start --time-limit 10 [path to save video]/sample_video.webm
You can take screenshots from the command line with either of the following commands:
screenrecord screenshot [destination-directory]
adb emu screenrecord screenshot [destination-directory]
Screenshots are saved in PNG format.
Virtual scene camera and ARCore
Developing and testing augmented reality apps (AR) with ARCore is now even easier with the new virtual scene camera, which allows you to experiment with your AR experience within a virtual environment.
For information on using the virtual scene camera in the emulator, see Run AR apps in Android Emulator.
Google Play Store on Pixel device images
The Google Play Store is now enabled for Pixel and Pixel 2 device images. This is indicated in the AVD Manager in Android Studio 3.2 and later with the Google Play logo in the Play Store column. AVDs with Google Play Store enabled have a Google Play tab in the Extended controls dialog that provides a convenient button for updating Google Play services on the device.
You can now load a Quick Boot snapshot without restarting the emulator. To load a snapshot, open the Extended Controls window to the Settings page and click the Load Now button.
We have made many improvements to the loading and saving of snapshots to improve efficiency of resource usage and to minimize the time that each operation takes. If you still experience unusually long saves, please file an issue, providing details of your CPU, RAM, and settings of any antivirus / firewall / security software that is running.
Rendering with Skia
When using images for API 27 or later, the emulator can render the Android UI with Skia, which can render more smoothly and efficiently.
For now, use of Skia requires that you explicitly enable it.
To enable Skia rendering, use the following commands in adb shell:
su setprop debug.hwui.renderer skiagl stop start
On Windows, Android Emulator now uses Media Foundation as the webcam back end, which greatly improves performance and frame rate for webcam capture, up to 720p 30 FPS.
On Mac, you can now use webcam0 and webcam1 together.
-phone-number-prefix command-line option has been changed to
-phone-number [number], which allows setting of the full
phone number.
You can now use alphanumeric SMS addresses.
- The Linux version of the Android Emulator is now built using a modern Clang C++ toolchain. This change fixes the issue of the emulator failing to start due to libGL and libstdc++ errors.
- Fixed several causes of crashes and hangs.
- To avoid crashes and hangs caused by not having enough free disk space, the emulator now checks for sufficient free disk space on startup, and will not start unless at least 2 GB is free.
- Fixed an issue that prevented some Unity games from rendering.
- Fixed DNS issue that caused the emulator to be unable to connect to the network.
- Fixed an issue that caused changes to the internal storage allocated to an AVD through the Virtual Device Configuration dialog to not work.
- Fixed an issue of many adb processes being created and not properly shut down.
- Fixed an issue that caused the rotate buttons and other parts of the UI to become unresponsive unless the Extended controls window was open.
- Fixed an issue that caused copy and paste from the host to not work unless the Extended controls dialog was opened at least once.
- The frameless emulator's resize rectangle has been updated to better follow the emulator's visual theme.
- Telephone and SMS are now properly deactivated when airplane mode is on.
- Fixed an issue that caused SMS and cellular functionality to be disabled after loading a snapshot.
- You will no longer receive false warning messages saying
"Unable to open... \pstore.bin. Permission denied."
- Fixed an issue that prevented re-positioning the AVD on some Mac screens.
- Fixed issues with flickering and blank screens on newer MacBook Pro computers when running AVDs with Pixel 2 XL skins.
- Fixed issues with blank screens when switching into zoomed mode while a frameless emulator was active.
- Fixed an issue that caused the device skin and emulator contents to scroll out of sync when zoomed in.
If you are still experiencing hangs or other instabilities, please file an issue.
27.1.12 (March 2018)
This update includes fixes for the following issues:
- Bluetooth audio quality degraded after starting the emulator. (Issue 37095756)
- Locations sent to one emulator were sent to all of them. (Issue 73450633)
- GPS location set using the console was overridden by values set using Extended Controls > Location in the graphical user interface. (Issue 73471760)
If you are still experiencing hangs or other instabilities, please file an issue.
With this update, a current system image, and a preview version of Android Studio, you can use Android Emulator to run augmented reality applications built with ARCore. For detailed requirements and instructions, see Run AR apps in Android Emulator.
27.1.10 (February 2018)
Camera capture resolution
720p frames can now be captured from an attached webcam.
To work with Android 8.1 (API level 27) and higher system images, any attached webcam must have the capability to capture 720p frames.
- Fixed an issue that caused webcam capture to sometimes output a distorted or all-green image.
- Fixed an issue that made it possible to see the following message even when there was no actual hang: "emulator: ERROR: detected a hanging thread 'Qt event loop'. No response for 15000 ms".
If you are still experiencing hangs or other instabilities, please file an issue.
27.1.7 (February 2018)
Frameless emulator window:
By default, emulators with device skin files are now shown without a surrounding window frame. To show the surrounding window frame, enable Show window frame around device in the Settings pane of the Extended Controls window.
Quick Boot improvements to make working with AVD snapshots more efficient:
- You can save an AVD snapshot at any time using the Save Now button in the Settings pane of the Extended Controls dialog box.
- The emulator reduces the time that it takes to save a snapshot in many cases by saving only the difference between the current state and the previously saved snapshot.
For details, see the Quick Boot documentation.
The emulator has been updated to use QEMU 2.9.
Some notable improvements include the following:
- Optimized I/O and finer-grained I/O thread locking for greater performance.
- Fixed bugs since QEMU 2.8 (26.1.4).
- New implementation of the HAXM back end.
See the full list of changes in the QEMU 2.9 change log.
Swiftshader implementation conforming to OpenGL ES 3.0:
The emulator's Swiftshader renderer now conforms fully with OpenGL ES 3.0. For details of the Swiftshader renderer, see the Settings > Advanced section of Extended Controls.
- Fixed an issue where clipboard sharing was not working unless the Enable clipboard sharing option was toggled off and on.
- Fixed a hang when using the Swiftshader rendering back end with low-resolution AVDs.
27.0.5 (January 2018)
ANGLE for rendering on Windows is now disabled by default.
If ANGLE works better for you, you can re-enable it with command line flag
-gpu angle_indirect. Or, open the Extended controls window, navigate to Settings > Advanced, and select ANGLE D3D11 for the OpenGL ES renderer setting.
Fixed an issue where Shift+B does not type a capital B character.
27.0.2 (December 2017)
New Quick Boot feature provides faster emulator start times, based on a snapshot of your AVD instance.
Quick Boot is enabled by default for all AVDs. Although the first time you start an AVD it must perform a cold boot (just like powering on a device), all subsequent starts are fast and the system is restored to the state at which you closed the emulator (similar to waking a device).
If you want to control when the emulator saves a snapshot, open the emulator's Extended controls window and click Settings. Here, you can select one of the following settings for Save quick boot state on exit:
- Yes: Always save quick boot snapshot when you close the emulator. This is the default.
- No: Never save quick boot snapshot; always perform a cold boot.
- Ask: Prompt whether or not to save quick boot snapshot when you close the emulator.
Your selection applies only to the currently open AVD.
For more information, see the Quick Boot documentation.
Added support for Mac OpenGL ES 3 (for system images using API level 24 and higher, Google APIs, and the x86 ABI).
For added stability in OpenGL ES 2+ apps, emulator now uses OpenGL core profile if available.
New options for rendering with Swiftshader / ANGLE:
-gpu swiftshader_indirect: Faster, more stable variant of Swiftshader that works with Quick Boot.
-gpu angle_indirect(Windows only): More stable variant of ANGLE D3D that also works with Quick Boot.
The older
-gpu swiftshaderand
-gpu angleoptions are now deprecated. In the Extended controls window, the "SwiftShader" and "ANGLE" options for the OpenGL ES renderer setting in Settings > Advanced now use the
Various other bug fixes.
26.1.4 (August 2017)
This is a minor release with bug fixes and the following improvements to GPU configuration:
- Enable boot animation when running on ANGLE renderer
- Disable GLES3 when running on ANGLE renderer
26.1.3 (August 2017)
This is a minor release with bug fixes, performance improvements, and small feature changes.
- This version is now required to use the latest Android 8.0 system images.
They are Treble-compliant,
featuring separate
- New HAXM 6.2.0 now available (check the SDK Manager) and includes the
following updates:
- Improved memory usage. The peak working set of memory pinned by HAXM is no longer equal to the size of the AVD's RAM; instead, memory is paged in on demand. This should help the emulator run more reliably on machines with lower amounts of RAM.
- The emulator with HAXM 6.2.0 can now boot faster on macOS, skipping a lengthy initialization phase.
- Improvements to GPU configuration
- Fixed issues with black screen on boot when performing guest-side software rendering by falling back to host-side software rendering with Swiftshader. Latest revisions of system images for API levels 19 - 25 with Google APIs should have working guest-side rendering.
- Fixed an issue where the emulator was switched to a software renderer
due to detecting the presence of older Intel GPUs, but the emulator was
actually running on a discrete GPU. Which GPUs will be switched to use ANGLE
or Swiftshader rendering is determined as follows:
- Older Intel iGPUs have driver issues on both OpenGL and ANGLE D3D drivers. Users with Intel HD Graphics 3xxx and older will use Swiftshader.
- Some users reported the inability to use API level 25 images because of a bug in which "Pixel Launcher keeps stopping." This seems to be a driver issue in some Intel HD 4xxx models. So they will be switched to use ANGLE automatically.
- For best results with GPU emulation, we recommend either to use a discrete NVIDIA or AMD GPU, or a newer Intel GPU (Iris, HD 5xxx, HD 5xx/6xx).
- Fixed an issue where the emulator would fail to start (OpenGL emulation
failed to initialize) if the AVD was configured with
hw.gpu.mode=hostand the emulator was launched in a remote desktop client.
- Clarified "OpenGL ES API level (requires restart)" settings; added an option to downgrade from OpenGL ES 3 to OpenGL ES 2 if experiencing issues or needing to test on lower OpenGL ES API levels.
- Mesa renderer is deprecated;
hw.gpu.mode=mesawill now be automatically switched to use Swiftshader on the host.
- Improvements for macOS:
- The emulator is now fully compatible with macOS 10.13 High Sierra through either Hypervisor.Framework or HAXM 6.2.0.
- Hypervisor.framework is now enabled by default on macOS for 32-bit x86
images to improve performance and macOS compatibility. If you experience
issues with it specifically, please file a bug report and append
HVF = offto
~/.android/advancedFeatures.ini(create this file if it doesn't exist).
- Fixed issues with no internet / failure to attach debugger while using Hypervisor.framework.
- To enhance compatibility and performance of webcam capture, the QTKit-based camera capture has been replaced with a buffered one based on AVFoundation.
- Added support for Wi-Fi in some system images (currently only API level 25).
An access point called "AndroidWifi" is available and Android automatically
connects to it. Wi-Fi support can be disabled by running the emulator with the
command line parameter
-feature -Wifi.
- Some users raised the concern that the fixed-size Play Store system images did not have sufficient storage. As such, we've increased the size to 2 GB by default (up from 800 MB).
- Added a keyboard shortcut (Ctrl+Shift+U) to open the bug reporting UI page directly from the settings page.
- Fixed an issue where if an older CPU with Intel x86 EPT but without UG was used, the emulator would fail to boot if more than one core was configured.
- Fixed an issue where HyperV would be improperly detected if the emulator was itself running in a Xen hypervisor.
- Fixed an issue where the emulator would crash on start in some Linux configurations.
26.1.2 (July 2017)
This release includes new features and performance improvements.
Added the ability to define a custom HTTP proxy configuration in the extended controls (click More , and then click Settings and Proxy). By default, the emulator uses the Android Studio HTTP proxy settings, but this screen allows you to define a manual proxy configuration.
Added VNC support for guest mode GPU so emulator can be remotely viewed and controlled. For example, you can launch the emulator and let VNC listen to port 5901 as follows:
- Execute:
emulator -gpu guest -avd avd_name -no-window -qemu -vnc :1
Open a VNC viewer, such as tightvnc viewer, to connect to port 5901.
To use Mac's built-in screen sharing client, a VNC password is required when launching the emulator. To set a password, use this command:
emulator -gpu guest -avd avd_name -no-window -qemu -vnc :1,password -monitor stdio
And then enter
change vnc passwordinto the console, and enter a password.
Android O is not currently supported for VNC mode.
- Execute:
Added a File a bug button in the extended controls Help screen (Click More , and then click Help and Emulator help). Clicking File a bug opens a dialog where you can see the bug report details such as the screenshot, the AVD configuration info, and a bug report log. You can then save the report for yourself or report emulator issues.
Added gyroscope sensor to emulator and virtual sensors panel. This requires a system image with gyroscope support to work (currently API level 24 and 25).
Added host-preferred DNS to Qemu DNS list on Windows, when multiple virtual network interfaces on the host introduce multiple DNS addresses which are not functional for the emulator.
Added experimental macOS Hypervisor.Framework support for 32-bit x86 images on macOS 10.10+ through server flags, which should improve boot time and performance.
- If you experience problems with it, add the line
HVF = offin
- If you experience problems with it, add the line
OpenGL ES 3.x is now enabled by default for system images and host GPUs that support OpenGL ES 3. Currently, only Android O (API level 26) and Windows/Linux hosts support OpenGL ES 3.
- If you experience problems with OpenGL ES 3, add the line
GLESDynamicVersion = offin
- If you experience problems with OpenGL ES 3, add the line
Emulator now uses offscreen OpenGL FBOs for all rendering except final display image posting, which should help with color consistency issues across platforms.
After collecting data on sudden emulator slowdown issues, we have determined that the problem may have to do with some interaction between older Intel OpenGL drivers and Windows updates. As such, users with Intel HD 4000, 3000, 2000 (and related GPUs) now have rendering set by default to either a D3D renderer (ANGLE) or Swiftshader (software renderer).
26.0.0 (March 2017)
This release is compatible with API level 26. It also includes a number of performance improvements and bug fixes.
Minor revision 26.0.3 (May 2017)
- Adds online-updateable feature flags for quickly addressing issues stemming from problematic hardware configurations. This allows Google to roll out fixes and features that are dependent on user configurations by updating server-side flags. If you notice issues with specific hardware, please report a bug so we can investigate the problem.
- New support for rotary input for Android Wear API level 25 system images. To emulate the rotary input dial on a Wear device, click the Rotary Input tab on the extended window.
- The Crash Reporting dialog is now resizable and no longer resets When to send crash reports to Ask without input.
- The 32-bit emulator now requires that the maximum AVD RAM size be less than or equal to 512 MB, in order prevent the emulator from running out of room in the 2 GB virtual address space.
- Adds support for absolute paths in emulator images.
- Adds a new tab in the extended window for Google Play Store images that displays the Play Services version and a button to check for updates to Play Services.
- Adds a dropdown to select the OpenGL renderer on the Emulator Settings page. If you are experiencing issues with the OpenGL driver on a Windows machine, try using the ANGLE (D3D11) or ANGLE (D3D9) options (requires a restart). If you are experiencing issues with the OpenGL driver on a non-Windows machine, try using the Swiftshader software renderer (requires a restart).
- Fixes a rare crash on exit when the emulator receives both
- Fixes a scaling issue when changing displays on a Mac machine. (Issue 268296)
- Fixes an issue where the emulator takes 300% of the CPU and holds it after resuming the host computer from sleep or when the emulator has been running for a long time.
- Fixes a crash when the emulator is shutting down.
Updates with HAXM v6.1.1 (March 2017)
Note: HAXM v6.1.1 is available for Mac users through the SDK Manager as of March 30th, and will be available for Windows users soon.
Version 26.0.0 of the Android Emulator supports HAXM v6.1.1, which includes the following updates:
- Enables Performance Monitoring Units (PMU) emulation. (Issue 223377)
- Fixes coexistence with VirtualBox and Docker on Macs. (Issue 197915)
- Revises the installation error message displayed when the installer fails to detect Intel VT-x on Windows, usually because Hyper-V is enabled.
- Adds support for accelerating the Android Emulator in a Hyper-V-based Windows VM. This update requires that the host Hyper-V instance (the one that manages the Windows VM/guest) use the latest version of Hyper-V with nested virtualization enabled. Hyper-V must be disabled in the guest Hyper-V instance (the Windows VM).
- Android SDK Platform-Tools revision 25.0.4 or later.
- Android SDK Tools revision 26.0.0 or later.
New features and bug fixes
- Compatible with API level 26.
- Fully GLES 2.0 compliant. Given a host GPU that has conformant desktop
OpenGL drivers, the emulator now passes 100% of the Android CTS dEQP-GLES2
mustpasslist. This has been released for API level 24 x86 images (revision 11 and higher) and will soon be included for all system images.
- Improved video playback performance. The emulator now stores all video color buffers in host/guest shared memory and performs necessary final YUV to RGB conversion in the GPU. 1080p30 should be well within reach of most systems now. This has been released for API level 24 x86 images (revision 11 and higher) and will soon be included for all system images.
- The emulator now correctly unregisters itself from the
adb deviceslist on exit and closes open TCP ports on Linux machines.
- adb connections are now more reliable. A running emulator is detected faster and doesn't go into "offline" or "unauthorized" status anymore.
25.3.0 (March 2017)
As of this release, the Android Emulator will be released separately from the SDK Tools. This release contains a variety of performance improvements, new features, and bug fixes.
Minor revision 25.3.1 (March 2017)
- Fixed a crash occurring on some GPU configurations by disabling GLAsyncSwap by default.
This feature was added in 25.3.0 to improve frame timing and frames per second for games
and video, but causes the emulator to fail on some unknown machine configurations. You can
manually enable it by opening the
android_sdk/emulator/lib/advancedFeatures.inifile and setting
GLAsyncSwap = on.
- Android SDK Platform-Tools revision 24 or later.
- Android SDK Tools revision 25.3.0.
New features and bug fixes
- Updated emulation engine to QEMU 2.7, including all recent bug fixes, improved performance, and new features.
- New IPv6 support.
- The emulator now uses SwiftShader as a pure software renderer on the host.
- Android Pipe performance improvements: Android Pipe, the main
communication channel between the emulator and Android OS, is now an
order of magnitude faster, has lower latency and offers better
multi-threaded performance. This causes a number of performance
improvements for the emulator, including:
- Improved ADB push/pull speed.
- Better 3D acceleration support.
- Increased overall responsiveness of the emulator.
- Improved graphics performance.
- The emulator now uses GPU-side buffers (glBindBuffers / glBufferData) when the guest requests them, decreasing CPU overhead in some apps.
- Improved audio support.
- Faster disk I/O: The emulator now uses separate threads to dispatch disk I/O, resulting in lower latency and better throughput (~1.5x sequential I/O speed, ~5x random access I/O speed). This also reduces the number of flushes to disk, resulting in much lower physical device load.
- The emulator now uses sparse files for disk boots on Windows machines, speeding up both first boot and "wipe-data" boots. When creating or resetting an AVD, the emulator now writes 100-200 MB of data to disk, instead of 2 GB or more.
- Various GUI enhancements:
- The emulator now uses Qt 5.7.0, which includes bug fixes and performance improvements.
- UI initialization no longer attempts to load all emulator executables as Qt plugins, so it's dramatically shorter, especially on HDDs.
- UI interactions are now faster and smoother, including rotation, window resizing, and extended controls window loading and closing.


text:
Government sites such as bea.gov and census.gov provide lot of
interesting data relevant current events. These data are usually
provided in dense spreadsheet tables with limited, if any,
charting facilities making them relatively inaccessible to the
casual visitor. As a former Economics and Statistics educator, I
have an interest in presenting data in a straightforward, visual
Perl's libraries such as Text::CSV, HTML::TableExtract,
Spreadsheet::ParseExcel provide means to extract relevant
information from data distributed in commonly used file
With the advent of HTML5's canvas element, the task of
generating graphics can be offloaded to the visitor's web
browser (ignoring, for the moment issues with browser support
for this feature). Web applications can avoid external graphics
files, instead embedding the data necessary to produce a chart
in a table element in the HTML. Such a table can then be
displayed as a chart using unobtrusive JavaScript, if the client
browser supports it.
Recently, Perl has gained a number of simple Web application
frameworks. One of these is Dancer .
Web applications written using Dancer can be deployed easily in
a number of ways, including as standalone scripts. Dancer works
well with Perl's Template::Toolkit for HTML generation.
I propose a presentation putting these elements together to
create a simple interface to the National Income Accounts data
provided by the Bureau of Economic
Analysis :
None of this is particularly complicated, but I am not aware of
any tutorials or documentation that would help someone with
reasonable familiarity with all the technologies involved to put
together such an application. Therefore, an example of such a
self-contained web application might be of interest.
Of course, these building blocks can be used to provide
interfaces to data from other domains than Economics as well.
Sinan Unur is an economist by training and currently works as an
independent programmer and consultant helping his clients make
sense of large and complicated data sets.
He earned his Ph.D. in Consumer Economics at Cornell University
where he worked as a Senior Lecturer until 2009, teaching
Economics and Statistics to graduate and undergraduate students.
Unur's passion for Perl dates back about ten years to when he
decided to switch from Java to Perl as his tool of choice for
writing Economics experiments. He is an active contributor to
the Perl tag on
Stackoverflow and
maintains Perl's Crypt::SSLeay and Net::Sharktools modules on
Comments on this page are now closed.
I'm most interested in solving problems. Too much time was spent showing that there was data on the web in several different formats and complaining that it's hard to work with.
I was there to see the solutions to the finding and fetching problem, offering indexes to users, munging the various formats, leveraging datasets against one another, and how it was all realized visually.
I felt that there was way too much time spent on the graphs and why embedded graphs are bad. In the end I felt as if we were told that his experiment was a bad idea, that canvas is not good for drawing conceptual stuff and that svg is better. I guess I expected more of a walkthrough on how to use perl with HTML5 Canvas.
Supporting materials are great, however you should download them prior to presentation. Sorry I can't help you with your problems, I was expecting you to help me with mine. Finally got to the point… canvas is not ready for prime time.

subset: commoncrawl


text:
Tomorrow at 1:20 in the morning, I'll be off on my way to Little Rock… Land of… The Clintons? Really I have not much clue what is there, but I know what lies ahead of me will be 26.2 miles of pain, laughs, tears, torture and in the end, triumph. I know this all sounds like some Rocky fighter theme song post, and I know that I truly deserve the pain, since I didn't train as I should have, but I have to pump myself up somehow and giving myself a pep talk is the only way to do it.
I know we'll cross the finish line, get our huge medal and after a freezing cold ice bath, a post race party where we'll eat 'Whole Hog BBQ', quite a few days of soreness, waking up with tears, and only being able to move my eyeballs while laying in bed, we'll all laugh about it.
It's getting there and starting which is the most scary to me at this point. Once you start there is no turning back. I know once we get half way, we'll struggle through the end, but I know we will get there, and we will finish. Taking those first steps off the starting line will be scary, but thinking of the finish, thinking of the journey we'll be taking through the streets of Little Rock, and the memories we'll make together will be worth it. When my feet hurt so much, when my legs are tired, and when my back hurts from holding my body and running for that long, I'll think of those who can't run, who can't do what we are doing, and I'll keep going. Because in the end, I can. I can keep going.
There are always the should have done this, could have done that, and this time, there are a lot of things that we should have prepared better on, but I know we'll be fine. I know we'll make it to the end and having that feeling is reassuring.
I haven't run much this week to give my IT band a rest. You know, fresh legs? I guess my legs are a little to fresh as in haven't been running fresh, but oh well. What can you do. The race is in three days.
So, onto a plane we go, to see what Arkansas has in store for us. I'm nervous. I'm excited. I'm terrified. But most of all, I'm thankful. Thankful that we can get together and do something that we love to do, well love is a strong word at this point. I guess something we like to do all in the name of that medal at the finish line. Thankful that we can share the laughs and the feelings and the pain together.
I'm so glad that Leslie is going along, and I know her smiling face and her banter along the course will keep me laughing. I am so glad that Maritza is running the half, and will be cheering for us along the course and will also keep us laughing. And My Maniac Sister who will be running besides me, who will tell me to man up and not to cry, I couldn't do it without you either. :) It will be one for the books, er, blog, that's for sure.
In the words of Kelly Clarkson, which has become my own person anthem for this weekend…"What doesn't kill you makes you stronger."
We'll be a lot stronger after this weekend, or maybe we'll just prepare better next time. :)


text:
The Breaking Dawn DVD is around in time for Valentine's Day. In case you want to drop hints to your significant other as to what edition you want, the Twilight Examiner has a full rundown of who has what perk. The perks amount to special packaging, the content on the discs themselves is the same.
The Breaking Dawn – Part 1 DVD/Blu-ray release date is February 11th in the U.S.
Special features included on each of these include the following:
Audio Commentary with Director Bill Condon
"Edward Fast Forward" and "Jacob Fast Forward"
6-Part Making-of Documentary
Edward & Bella's personal Wedding Video
Get a glimpse into "Jacob's Destiny"
See more on the Twilight Examiner.


text:
Event box
Learning Lab
Welcome to the new Homework Help, Reading Buddies, and Computer Literacy Learning Lab.
Teen Volunteers working with an Adult Coordinator are available Monday, Tuesday, and Thursday to assist students in 1st through 8th grade with:
Homework Help
Registration is required, and the application can be found in the Learning Lab during open hours. The Learning Lab will be closed on all school holidays and breaks.
- Date:
- Thursday, May 2, 2019 Show more dates
- Time:
- 4:00pm - 5:30pm
- Location:
- Community Meeting Room
- Library:
- Union City Library
- Audience:
- Kids Tweens
- Categories:
- Education and Learning
The Library is wheelchair accessible. An ASL (American Sign Language) interpreter will be provided for this program if requested at least 7 days in advance. For assistance, please contact your library or email@example.com. Events subject to change or cancellation without prior notice.
All Alameda County Library events are free.


text:
The Clerk of the Senate is appointed by the President of the Senate under subsection 58(1) of the Parliamentary Service Act 1999. Staff of the department are engaged under section 22 of that Act.
The department's employees are located at Parliament House in Canberra.
The department's staffing structure did not change significantly in 2009–10. As in previous years, the number of non-ongoing staff fluctuated to meet the workload generated by the sittings of the Senate.
Staffing levels were supplemented by:
The Working in the Senate Development Program offers Senate work experience to officers from the public service. This program is run on a calendar year basis. In both 2009 and 2010, two participants in the program were primarily attached to various committee secretariats, providing administrative and research support. They also had short structured placements with the Table and Procedure offices.
The Parliament of Australia Graduate Program also is run on a calendar year basis. In both 2009 and 2010, two graduates in Australian Public Service graduate programs participated in the program. Participation involves the graduates being placed with the department for one of their three-month rotations. During this time, the graduates mainly work with a committee secretariat. Graduates also familiarise themselves with the work carried out by the Table and Procedure offices.
Figure 23 shows that the full-time equivalent (FTE) staffing level for 2009–10 was 159, four less than for 2008–09. The decrease was largely the result of reduced staffing levels in the Committee Office, in part due to more effective utilisation of staff across that office. More staffing statistics, including a breakdown of the FTE staffing level by office, are provided in appendix 2.
Figure 23 Full-time equivalent staff numbers, 2005–06 to 2009–10
Text description of figure 23
Workforce planning for the whole department is undertaken annually. The department's 2009–10 workforce report reinforced trends reported in recent years, including a number of staff nearing retirement age and a workforce with an average age that matched that of the public service, as reported in the State of the Service Report 2008–09.
Several initiatives were proposed as a result of this year's workforce planning in relation to:
These were considered by the program managers and are being implemented or are being further considered as part of the department's structural review.
The department continued to attract a significant number of suitable applicants for its advertised employment vacancies, including for specialist roles. An average of 32 applications were received for each advertised employment vacancy. The Gazette and the department's internet page continue to be the main media by which applicants become aware of vacancies.
The number of staff separations in 2009–10 was less than in 2008–09. Table 7 shows the reasons for separations.
The names of the department's senior executives appear in figure 1 in the 'Departmental overview' chapter and in reports on performance for each office.
The remuneration of the Clerk of the Senate, who is the holder of a statutory office, is set by the President of the Senate after consultation with the Remuneration Tribunal.
In 2009–10, four of the department's Senior Executive Service (SES) staff were covered by individual agreement-based transitional instruments (formerly known as Australian workplace agreements). One SES staff member was covered by a determination made under subsection 24(1) of the Parliamentary Service Act 1999. In accordance with their terms and conditions, and consistent with the provisions of the department's employee collective agreement, SES staff received a 4 per cent pay increase in May 2010 in recognition of individual and departmental performance outcomes. The salary ranges for SES staff are set out in appendix 2.
Table 8 shows the number of senior executives (including the Clerk) who received or were due to receive total remuneration of $130,000 or more, for 2007–08 to 2009–10.
a Excludes remuneration bands that did not apply to any senior executives during the periods reported.
The aggregate amount of total remuneration for the senior executives shown in table 8 is $1,424,737 ($1,475,245 in 2008–09).
During 2009–10, most non-SES staff were covered by an employee collective agreement. A small number of staff were covered by Australian workplace agreements.
The department's employee collective agreement commenced in July 2006 with a nominal expiry date of 30 June 2010. In May 2010, the agreement delivered a 4 per cent salary increase to staff: 2 per cent based on 'effective or better' individual performance during the May 2009 to April 2010 assessment period, and 2 per cent based on productivity improvements.
In January 2010, the department commenced negotiations with bargaining representatives for a new enterprise agreement for non-SES staff. Eight negotiation meetings were held between January and May. In negotiating this agreement, the department worked within the requirements of the Australian Government Employment Bargaining Framework applicable to the parliamentary service.
The enterprise agreement was agreed to by staff in June 2010 and was lodged with Fair Work Australia on 30 June 2010 for approval. Once approved, it will come into effect in July 2010, with a nominal expiry date of 30 June 2012.
The enterprise agreement is similar in form to the current collective agreement. It highlights the principles and objectives by which the department, and staff, will work towards achieving greater efficiencies and savings, and articulates the roles of parliamentary executive level staff. Key enhancements in the enterprise agreement include:
The enterprise agreement provides for 3 per cent pay increases in May 2011 and May 2012.
The salary ranges applicable to non-SES staff classification levels are set out in appendix 2.
In addition to salary, staff are entitled to a range of benefits including leave entitlements, study assistance, staff assistance program access, guaranteed minimum superannuation payments at the same level as the department's nominated default fund and a range of allowances that support staff members in effectively carrying out their duties and being appropriately remunerated.
A small number of non-SES staff have been covered by individual agreement-based transitional instruments. At 30 June 2010, the department was in the process of terminating these instruments so that the new enterprise agreement will cover all non-SES employees.
By agreement between the department and affected SES staff, it is intended that the existing subsection 24(1) determination and SES individual agreement-based transitional instruments will be terminated during 2010–11 and a new collective determination will be made under subsection 24(1) of the Parliamentary Service Act to cover all SES staff (except the Clerk).
The department's employment arrangements do not provide for individual or team-based performance pay.
The department's staff are expected to take personal responsibility for developing and enhancing their skills and knowledge and improving their individual performance. In consultation with supervisors, staff set professional development goals for a 12-month performance cycle. The department recommends that staff undertake at least three days of work-related off-the-job learning activities each year.
During 2009–10, 12 employees received financial assistance, paid leave, or both, under the department's Studybank scheme, to help them undertake tertiary studies relevant to the department's objectives.
To supplement external training, the department may conduct in-house learning and development activities during the year. In 2009–10, the department delivered:
The department's professional development program, the Parliamentary Executive Professional Upgrade Program (PEP UP), is a calendar year program and ran in both 2009 and 2010. The program was open to all departmental staff in both years. It provides staff with technical information and develops their knowledge about the Senate, its operation and the work carried out by the department in support of senators. Feedback on PEP UP sessions indicates that the program is effective and supports the development needs of staff.
The department's program of induction seminars for new staff was revised during 2009–10. A new program will be launched in early 2010–11. The Director Human Resource Management met with new staff on their first day with the department and again one month later, to brief them on their obligations as parliamentary service employees and ensure their adherence to the Parliamentary Service Code of Conduct and the Parliamentary Service Values.
The department undertook a range of preventative measures in 2009–10 aimed at minimising the risk of workplace injuries, which contributed to the satisfactory outcome of no serious incidents or compensable injuries during the year.
Initiatives and measures undertaken in 2009–10 to create a safe and healthy working environment for the department's staff included:
In 2010, the Health and Safety Management Arrangements were reviewed. Staff were consulted about the updated arrangements, which take into account the Occupational Health and Safety Code of Practice 2008 and reflect other minor changes in the department's operations.
Under the terms of the department's employee collective agreement, influenza vaccinations were made available to staff in May 2010.
The department's Health and Safety Committee met five times during 2009–10. The committee is made up of elected health and safety representatives for each designated workgroup. Each representative is elected for a two-year term in accordance with the Occupational Health and Safety Act 1991. The committee was consulted in relation to all incident and hazard reports received by the department. The committee also considered information about proposed new workstations and monitored changed procedures for the restocking of first aid kits.
Comcare did not accept any claims for compensation in respect of the department during 2009–10.
In 2009–10, within the department there were:
Parliamentary sitting calendar
Go to the full calendar of events
House of Representatives
Get informed
Get involved
Visit Parliament
Website features
Parliamentary Departments


text:
2010 wasn't a bad year for music DVDs but I think it was very similar to 2009. In 2009, there weren't that many notable DVDs released from the big name bands and a lot of bands used DVDs as special bonuses in first pressing of new releases. I also missed a few DVD releases in 2009 and that carried over to 2010 as well. The difference between the last few years, aside from Iron Maiden not releasing an awesome DVD this year, is that I made sure I picked up a few more DVDs. Actually, this turned out to be one of my better years for DVDs, I think I acquired about ten and all of them were very well done. Bands and labels are continuing to raise the bar by putting a lot of content into these DVDs so that the fans get a lot of value for their hard earned dollar. So here is my list of The Top 5 Music DVDs of 2010:
The Big 4 (Metallica, Slayer, Megadeth & Anthrax) – Live From Sofia, Bulgaria (2010): Technically this is a box set but the reason you're buying the box set is to see the concert. It was obvious from the second I opened the package that this was going to be the DVD of the Year because the expectation of seeing all four Thrash heavyweights on one bill, and then on one stage together, was the whole point. As far as content goes, this was definitely the best DVD. You got full sets from each band, along with the 'Am I Evil?' jam during the Metallica set, and they were all great performances. There was also enough bonus footage of the backstage are and the 'Am I Evil?' rehearsals to make that a special add-on. Maybe the fact that I got the DVD in the box set has something to do with it because the box set did include the audio CDs, booklet and photo cards but the DVD can be purchased separately and, if I got that version, it would still be at the top spot.
Michael Schenker Group – The 30th Anniversary Concert: Live In Tokyo (2010): I'm putting Michael Schenker in the second spot because this was a tour souvenir for me after I caught the show in Foxboro, MA a few months later in July. Michael Schenker has been one of my favorite guitarists for a long time and the early MSG albums are still classics. When I caught the show in July, it was one of the best concerts I'd seen this year, if not all-time, Michael and the band put on a great show. This concert in Tokyo is basically the same show I saw in Foxboro with a little different running order, a couple extra songs and a different touring lineup. The concert is superb and it's obvious that the magic between Schenker and original MSG singer Gary Barden is still there. Not a lot of extras here (some backstage footage and interviews) but the performance more than makes up for it with classic songs and great musicianship.
Jeff Scott Soto – One Night In Madrid 2009 (2010): ONE NIGHT IN MADRID 2009 was released in Europe in late 2009 but got a proper U.S. release in early 2010 along with the two disc live album. Not only is Jeff Scott Soto one of the best Rock singers in the business, he is also extremely fan friendly when releasing CDs and DVDs. This DVD set includes the 21 song setlist from Sala Heineken in Madrid and and extensive bonus section that is longer than the main show! The Madrid show includes songs from all over Soto's career and is a superb performance. The bonus section features eight music videos from Soto's solo albums and second bonus section that includes behind the scenes tour footage and a tribute to Marcel Jacob, Soto's bandmate in Talisman who passed away unexpectedly in 2009. The total running time for the single DVD is 4 hours & 5 mins but the concert itself is only 1 hour & 42 mins long…..that means there's over 2 hours of bonus material. Now that's really giving the fans something extra! This DVD would have easily made the #2 spot but the MSG performance was just a bit more special because I had seen it live. ONE NIGHT IN MADRID is a very close 3rd…..maybe if the live album was included in the package instead of a separate release it would have put it in 2nd.
Halford – Live In Anaheim (2010): LIVE IN ANAHEIM is another one of those releases that got a separate DVD and a separate live CD release, it would have been nice to have the whole package together but that's another issue. This DVD is two parts: Part 1 is a band documentary including four songs performed in Tokyo, Japan in February 2003 and Part 2 is the full 19 song concert in Anaheim from June 2003. This Halford footage is prior to Rob Halford reuniting with his Judas Priest bandmates so the Halford band was his only focus and, at the time, they were promoting and touring the band's then latest record CRUCIBLE (2002). The band's performances are tight, Rob is in fine form vocally and the Anaheim setlist is varied enough where there are twelve Judas Priest songs but seven songs coming from CRUCIBLE, RESURRECTION (2001) and some songs from Rob's days in Fight. Personally, I would prefer more solo/Fight/Halford tunes than the Priest stuff because, well, it's Halford but at least Rob and the band pull out some lost Priest nuggets like 'Rapid Fire', 'Never Satisfied' and 'Riding On The Wind'.
Heaven & Hell – Neon Nights: Live In Europe (2010): This Heaven & Hell live DVD captures the band live headlining the Thursday night opening day of the 2009 Wacken Open Air Festival in Germany. Obviously, with the death of Ronnie James Dio, NEON NIGHTS: LIVE IN EUROPE is the final recorded document of the Dio-era Black Sabbath/Heaven & Hell…..ten months later, Ronnie would pass away. This DVD is the basic Heaven & Hell concert in support of the band's latest studio album THE DEVIL YOU KNOW (2009) and it's basically the same set that I saw a month later in Boston. As far as extras go, just a couple of interview segments with each band member including Ronnie. I'm adding this DVD in ahead of a few others I have because the performance is superb and the impact of the music is great. If this is the way we remember Ronnie James Dio and his time in Sabbath, then this is the way to do it.


text:
Game Experience May Change During Online Play.
1. ACCEPTANCE OF AGREEMENT. This Agreement can be accepted only by an adult 18 years or older. By clicking the "ACCEPT" button, you affirm that you are an adult 18 years or older and you are accepting this Agreement on your own behalf or on behalf of your minor child (under 18).
2. GRANT OF LICENSE. SCEA grants you a non-exclusive right to use this software for play on a PlayStation®2 computer entertainment system only. You may not (i) rent, lease or sublicense the software, (ii) modify, adapt, translate, reverse engineer, decompile or disassemble the software, (iii) attempt to create the source code from the object code for the software, or (iv) download game content for any purpose other than game play. You may, however, transfer all your rights to use the software to another person provided that you transfer the original product and this Agreement with the software.
3. AUTHENTICATION. This software uses "DNAS" (Dynamic Network Authentication System), a proprietary authentication system created by Sony Computer Entertainment Inc. (SCEI). "DNAS" retrieves information about a user's hardware and software for authentication, copy protection, account blocking, system, rules, or game management and other purposes. The information collected does not identify the user personally and will not be shared with any non-SCE company. SCEI, SCEA and their affiliates cannot guarantee the continuous operation of the "DNAS" servers and shall not be liable for any delay or failure of the "DNAS" servers to perform. If you receive a message during login identifying a "DNAS" authentication error, please contact SCEA Consumer Services at 1-866-466-5333. For additional information concerning "DNAS", visit www.us.playstation.com/DNAS. In the event of a systems incompatibility or inoperability with "DNAS", the sole liability of SCEI, SCEA and their affiliates shall be limited to the repair or replacement of the user's affected game software, console, or peripherals at the option of SCEA. SCEI, SCEA and their affiliates shall not be liable for any delays, system failures, authentication failures, or system outages, which may, from time to time, affect online game play or access thereto.
4. COLLECTION OF INFORMATION. Before you can play, you will be asked to create an account with a user, player or other game name ("game name") and password. You may also be asked to select or provide additional information for a game profile. This information will not identify you personally. You agree that this non-personally identifying information may be provided to any tournament website which is established by SCEA or its partners in connection with this game. Such information will not be displayed on any tournament site without your permission and agreement to participate in the tournament.
5. PROTECTION OF IDENTITY. When you choose a game name, choose an alias to protect your identity. Avoid using any part of your game name in your password. When you choose a password, choose a unique combination of letters and numbers that is unrelated to your game name or to any information you may share with other players in the game. SCEA will not ask you for your password and you should not provide this information to any third party. This game will save your game name, profile and password automatically. If your game name is inactive for an extended period your account may be deactivated. To inquire about a deactivated account, please contact SCEA Consumer Services at 1-800-345-7669. You agree that you have no expectation of privacy or confidentiality in the personal information you may intentionally or unintentionally disclose through login, game play and chat. You should avoid saying anything personally identifying in chat. SCEA has no liability for any violation of this Agreement by you or by any other player.
6. ONLINE CONDUCT. When you play, you agree to be respectful of your fellow players and never to engage in any behavior that would be abusive or offensive to other players, disruptive of the game experience, fraudulent or otherwise illegal. This includes but is not limited to:
(a) Harassing or intimidating other players while chatting or playing this game online or using information obtained while chatting or playing this game to harass or intimidate fellow players outside of the game;
(b) Using language, selecting user, character, clan or team names or creating any other content that is racially, ethnically or religiously offensive, sexually abusive, obscene or defamatory;
(c) Selecting as a user, character, clan or team name any word, symbol or combination of words and symbols which is identical to or substantially similar to any character, weapon, vehicle or other intellectual property element owned by SCEA which appears in this game or any other SCEA game;
(d) Using content that is commercial in nature such as advertisements, solicitations and promotions for goods or services;
(e) Falsely representing that you are an employee of Sony Corporation, Sony Computer Entertainment America, or any other affiliated or related company;
(f) Disrupting the normal flow of chat in game chat rooms;
(g) Making a false report of user abuse to SCEA Consumer Services (see below);
(h) Violating any local, state or national law including but not limited to laws related to copyright, trademark, defamation, invasion of privacy, identity theft, hacking and the distribution of counterfeit software;
(i) Using a cheat code or cheat device. For a detailed explanation of the SCEA policy on cheating visit www.us.playstation.com/onlinecheating.
If you violate this Agreement in any manner, SCEA may at its discretion and without notice to you temporarily or permanently block your account in this game and any related games. In appropriate cases, SCEA may bring legal action against you or cooperate in any government or private legal action or investigation relating to your conduct within the game. To report violations of this Agreement or to inquire about a blocked account, call SCEA Consumer Services at 1-800-345-7669. SCEA has no liability for any violation of this Agreement by you or by any other player.
7. INTELLECTUAL PROPERTY RIGHTS. All title and intellectual property rights in and to the content of this software is the property of the content owner(s) and may be protected by applicable copyright and other intellectual property laws and treaties. This Agreement grants you no ownership rights in such content. All rights not expressly granted are reserved by SCEA.
8. WARRANTY/DISCLAIMER. SCEA WARRANTS TO THE ORIGINAL PURCHASER OF THE GAME DISC THAT THE DISC IS FREE FROM DEFECTS IN MATERIALS AND WORKMANSHIP FOR A PERIOD OF NINETY (90) DAYS FROM THE DATE OF PURCHASE. SEE GAME MANUAL FOR LIMITED WARRANTY DETAILS. EXCEPT AS PROVIDED HEREIN, THE GAME DISC, SOFTWARE AND ALL RELATED SERVICES ARE PROVIDED "AS IS" AND, TO THE MAXIMUM EXTENT PROVIDED UNDER LAW, SCEA DISCLAIMS ALL WARRANTIES OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Without limiting the foregoing, SCEA does not promise that this software will work properly with any network adaptor, modem, memory card or other peripheral device that has not been licensed by SCEI or SCEA. To insure compatibility use only PlayStation® or PlayStation® licensed products. Additionally, SCEA does not guarantee thatyou will be able to play this game at any time you want. From time to time, there may be problems related to access, delay and failure to perform that are beyond the immediate and reasonable control of SCEA. In the event of a dispute regarding the online functionality of this software (except with regard to the operation of "DNAS" explained in paragraph 3 above), you agree that the sole liability of SCEA and its affiliated companies will be limited to repair or replacement of the game software at SCEA's option. SCEA may, at its sole discretion, discontinue hosting of the game server at any time. SCEA has no liability for such discontinuance.
9. MODIFICATION. SCEA at its sole discretion may modify the terms of this Agreement at any time. You are responsible for reviewing the terms of this Agreement each time you login to play. By accepting this Agreement and by playing the game online, you agree to be bound by all current terms of the Agreement. To print out a current copy of this Agreement using your computer, go to www.us.playstation.com/support/useragreements.
10. MISCELLANEOUS. This Agreement shall be construed and interpreted in accordance with the laws of the State of California applying to contracts fully executed and performed within the State of California. Both parties submit to personal jurisdiction in California and further agree that any dispute arising from or relating to this Agreement shall be brought in a court within San Mateo County, California. If any provision of this Agreement shall be held invalid or unenforceable, in whole or in part, such provision shall be modified to the minimum extent necessary to make it valid and enforceable, and the validity and enforceability of all other provisions of this Agreement shall not be affected thereby. This Agreement constitutes the entire agreement between the parties hereto related to the subject matter hereof and supercedes all prior oral and written and all contemporaneous oral negotiations, commitments and understandings of the parties, all of which are merged herein.


text:
What did I do last night?Posted by Matt Grover at 10:03 am
Oh yes, that's right I went to see Queens Of The Stone Age at Brighton Dome.
Were they awesome? Yes they were.
Did I suffer some permanent ear damage? Yes I think I did.
Was I disappointed that they didn't play Feel Good Hit Of The Summer? Yes I was.
Was I over the moon when they opened with Hanging Tree? Hell yeah!
Enjoy some shit photos from the shit camera on my Nokia.
0 comments:
Subscribe to: Post Comments (Atom)