Foxviewer466

-->

Start AVD Manager Without Android Studio. First, open the file explorer and go to the Android SDK folder. Inside the SDK folder, find and open the Emulator folder. As you can see, I've 2. In the file explorer, hold the Shift key on your keyboard and right-click on the empty space. Restart computer. Delete and recreate AVD. Change AVDs Graphic to Software (both in the AVD manager and directly in file) Reinstall Emulator in SDK manager (all possible ways - update, delete and reinstall, reinstall on demand when starting AVD) Reinstall HAXM. Reinstall Android studio. Check all Android versions in SDK manager. First, start AVD manager. If you haven’t created any AVD or android virtual device before, you will find it in Tools-AVD Manager. Click on Create new virtual device button. It will show you a list of different devices. You can select any of these phones. It will show you a list of system images.

Please visit the Surface Duo Tech Community to ask questions or discuss any issues you are having with the Surface Duo emulator or SDK.

Following are some common issues and their resolution.

Surface Duo emulator does not appear in the device list in Android Studio or Visual Studio

The current version of the Surface Duo emulator cannot be started by your IDE. First manually start the emulator and once it's running it should appear in the list for deployment and debugging:

• Windows - choose from Start > Surface Duo Emulator.
• Mac - start from the command line using ./run.sh (or ./run_vs.sh for Visual Studio for Mac).

Once you have started the Surface Duo emulator, it should appear in the device list as Virtual device.

Surface Duo emulator does not appear in the Android Virtual Device (AVD) Manager

The current version of the Surface Duo emulator cannot be managed in AVD Manager. Instead it must be installed from our download page and started manually:

• Windows - choose from Start > Surface Duo Emulator.
• Mac - start from the command line using ./run.sh (or ./run_vs.sh for Visual Studio for Mac).

Apps do not open across both screens

By default applications will only open on a single screen. The user can then choose to span the application across both screens by dragging

There is no way for app developers to programmatically force an app to use both screens either. It is always a user-controlled action.

Contents do not rotate with the emulator

Verify that Auto-rotate is enabled in the notification drawer or in Settings > Display > Auto-rotate screen. The default value is to NOT rotate, and often is overlooked.

Note

If you are still experiencing rotation issues after enabling auto-rotate, you may be using an old version of the emulator from September 2020. This issue has been fixed since emulator version 2020.1014.2. Follow the emulator installation instructions to get the latest version.

How to 'Factory reset' the Surface Duo emulator

In the installation folder, there are four batch files run_wipe.bat, run_wipe.sh, run_vs_wipe.bat, run_vs_wipe.bat.

Virtual Device Manager

• Windows - In the artifacts folder inside of the installation folder, you can execute run_wipe.bat (or run_vs_wipe.bat for Visual Studio) directly to return the Surface Duo emulator image to its original state.
• Mac - In a terminal window, navigate to the folder where you copied the emulator files. And then type ./run_wipe.sh (or ./run_vs_wipe.sh for Visual Studio for Mac) to return the Surface Duo emulator image to its original state.

These files are installed with the emulator version 2020.1014.2 released in mid-October 2020.

If you are using an older version and cannot update immediately

If you have an earlier version, you should download the latest version, or you can create a script file manually. Start by copying the existing run_clean (or run_vs_clean) file to run_wipe (or run_vs_wipe) and modify it as shown below:

or for shell files on macOS and Linux:

The updated batch/script file should be located in the same directory as the existing batch/script files that you use to start the emulator. If you are modifying the Visual Studio version (with _vs in the filename) be sure the final line refers to run_vs.bat or run_vs.sh.

Surface Duo emulator fails to launch after an interuption

When the emulator is interrupted while in the middle of saving a Snapshot, on subsequent launches, it will attempt to boot from a corrupted snapshot state. Or, sometimes an unexpected issue happens while the emulator is running, and attempts to launch it result in the error, 'emulator: ERROR: bad workspace: cannot find prebuilt kernel in: ../bin/prebuilts/qemu-kernel/x86_64/kernel-qemu'

In this case, perform a Factory reset as described above to fix the issue and re-launch the emulator.

-->

Important

Media optimization for Teams is supported for Microsoft 365 Government (GCC) and GCC-High environments. Media optimization for Teams is not supported for Microsoft 365 DoD.

Note

Media optimization for Microsoft Teams is only available for the Windows Desktop client on Windows 10 machines. Media optimizations require Windows Desktop client version 1.2.1026.0 or later.

Microsoft Teams on Azure Virtual Desktop supports chat and collaboration. With media optimizations, it also supports calling and meeting functionality. To learn more about how to use Microsoft Teams in Virtual Desktop Infrastructure (VDI) environments, see Teams for Virtualized Desktop Infrastructure.

With media optimization for Microsoft Teams, the Windows Desktop client handles audio and video locally for Teams calls and meetings. You can still use Microsoft Teams on Azure Virtual Desktop with other clients without optimized calling and meetings. Teams chat and collaboration features are supported on all platforms. To redirect local devices in your remote session, check out Customize Remote Desktop Protocol properties for a host pool.

Prerequisites

Before you can use Microsoft Teams on Azure Virtual Desktop, you'll need to do these things:

• Prepare your network for Microsoft Teams.
• Install the Windows Desktop client on a Windows 10 or Windows 10 IoT Enterprise device that meets the Microsoft Teams hardware requirements for Teams on a Windows PC.
• Connect to a Windows 10 Multi-session or Windows 10 Enterprise virtual machine (VM).

Install the Teams desktop app

This section will show you how to install the Teams desktop app on your Windows 10 Multi-session or Windows 10 Enterprise VM image. To learn more, check out Install or update the Teams desktop app on VDI.

Prepare your image for Teams

To enable media optimization for Teams, set the following registry key on the host:

1. From the start menu, run RegEdit as an administrator. Navigate to HKEY_LOCAL_MACHINESOFTWAREMicrosoftTeams. Create the Teams key if it doesn't already exist.

2. Create the following value for the Teams key:

Name	Type	Data/Value
IsWVDEnvironment	DWORD	1

Install the Teams WebSocket Service

Install the latest Remote Desktop WebRTC Redirector Service on your VM image. If you encounter an installation error, install the latest Microsoft Visual C++ Redistributable and try again.

Latest WebSocket Service versions

The following table lists the latest versions of the WebSocket Service:

Version	Release date
1.0.2106.14001	07/29/2021
1.0.2006.11001	07/28/2020
0.11.0	05/29/2020

Updates for version 1.0.2106.14001

Increased the connection reliability between the WebRTC redirector service and the WebRTC client plugin.

Updates for version 1.0.2006.11001

• Fixed an issue where minimizing the Teams app during a call or meeting caused incoming video to drop.
• Added support for selecting one monitor to share in multi-monitor desktop sessions.

Install Microsoft Teams

You can deploy the Teams desktop app using a per-machine or per-user installation. To install Microsoft Teams in your Azure Virtual Desktop environment:

1. Download the Teams MSI package that matches your environment. We recommend using the 64-bit installer on a 64-bit operating system.

   Important

   The latest update of the Teams Desktop client version 1.3.00.21759 fixed an issue where Teams showed UTC time zone in chat, channels, and calendar. The new version of the client will show the remote session time zone.

2. Run one of the following commands to install the MSI to the host VM:

   • Per-user installation

     This process is the default installation, which installs Teams to the %AppData% user folder. Teams won't work properly with per-user installation on a non-persistent setup.

   • Per-machine installation

     This installs Teams to the Program Files (x86) folder on a 32-bit operating system and to the Program Files folder on a 64-bit operating system. At this point, the golden image setup is complete. Installing Teams per-machine is required for non-persistent setups.

     There are two flags that may be set when installing teams, ALLUSER=1 and ALLUSERS=1. It is important to understand the difference between these parameters. The ALLUSER=1 parameter is used only in VDI environments to specify a per-machine installation. The ALLUSERS=1 parameter can be used in non-VDI and VDI environments. When you set this parameter, Teams Machine-Wide Installer appears in Program and Features in Control Panel as well as Apps & features in Windows Settings. All users with admin credentials on the machine can uninstall Teams.

     Note

     Users and admins can't disable automatic launch for Teams during sign-in at this time.

3. To uninstall the MSI from the host VM, run this command:

   This uninstalls Teams from the Program Files (x86) folder or Program Files folder, depending on the operating system environment.

   Note

   When you install Teams with the MSI setting ALLUSER=1, automatic updates will be disabled. We recommend you make sure to update Teams at least once a month. To learn more about deploying the Teams desktop app, check out Deploy the Teams desktop app to the VM.

Verify media optimizations loaded

After installing the WebSocket Service and the Teams desktop app, follow these steps to verify that Teams media optimizations loaded:

1. Quit and restart the Teams application.

2. Select your user profile image, then select About.

3. Select Version.

   If media optimizations loaded, the banner will show you Azure Virtual Desktop Media optimized. If the banner shows you Azure Virtual Desktop Media not connected, quit the Teams app and try again.

4. Select your user profile image, then select Settings.

   If media optimizations loaded, the audio devices and cameras available locally will be enumerated in the device menu. If the menu shows Remote audio, quit the Teams app and try again. If the devices still don't appear in the menu, check the Privacy settings on your local PC. Ensure the under Settings > Privacy > App permissions - Microphone the setting 'Allow apps to access your microphone' is toggled On. Disconnect from the remote session, then reconnect and check the audio and video devices again. To join calls and meetings with video, you must also grant permission for apps to access your camera.

   If optimizations do not load, uninstall then reinstall Teams and check again.

Known issues and limitations

Using Teams in a virtualized environment is different from using Teams in a non-virtualized environment. For more information about the limitations of Teams in virtualized environments, check out Teams for Virtualized Desktop Infrastructure.

Client deployment, installation, and setup

• With per-machine installation, Teams on VDI isn't automatically updated the same way non-VDI Teams clients are. To update the client, you'll need to update the VM image by installing a new MSI.
• Media optimization for Teams is only supported for the Windows Desktop client on machines running Windows 10.
• Use of explicit HTTP proxies defined on the client endpoint device is not supported.

Avd Manager Mac Download

Calls and meetings

• The Teams desktop client in Azure Virtual Desktop environments doesn't support creating live events, but you can join live events. For now, we recommend you create live events from the Teams web client in your remote session instead.
• Calls or meetings don't currently support application sharing. Desktop sessions support desktop sharing.
• Give control and take control aren't currently supported.
• Teams on Azure Virtual Desktop only supports one incoming video input at a time. This means that whenever someone tries to share their screen, their screen will appear instead of the meeting leader's screen.
• Due to WebRTC limitations, incoming and outgoing video stream resolution is limited to 720p.
• The Teams app doesn't support HID buttons or LED controls with other devices.
• New Meeting Experience (NME) is not currently supported in VDI environments.

For Teams known issues that aren't related to virtualized environments, see Support Teams in your organization.

Collect Teams logs

If you encounter issues with the Teams desktop app in your Azure Virtual Desktop environment, collect client logs under %appdata%MicrosoftTeamslogs.txt on the host VM.

If you encounter issues with calls and meetings, collect Teams Web client logs with the key combination Ctrl + Alt + Shift + 1. Logs will be written to %userprofile%DownloadsMSTeams Diagnostics Log DATE_TIME.txt on the host VM.

Contact Microsoft Teams support

To contact Microsoft Teams support, go to the Microsoft 365 admin center.

Android Avd Manager Mac

Customize Remote Desktop Protocol properties for a host pool

Install Avd Manager Mac

Customizing a host pool's Remote Desktop Protocol (RDP) properties, such as multi-monitor experience or enabling microphone and audio redirection, lets you deliver an optimal experience for your users based on their needs.

Enabling device redirections is not required when using Teams with media optimization. If you are using Teams without media optimization, set the following RDP properties to enable microphone and camera redirection:

• audiocapturemode:i:1 enables audio capture from the local device and redirects audio applications in the remote session.
• audiomode:i:0 plays audio on the local computer.
• camerastoredirect:s:* redirects all cameras.

Android Virtual Devices Download

To learn more, check out Customize Remote Desktop Protocol properties for a host pool.