Lines Matching refs:to
24 launch apps on the virtual device, which are streamed to the client.
29 same time, it's best to use a large screen device as a client, like a Pixel
32 * **Demos**: installed on the host, meant to showcase specific VDM features.
33 The demos can be also run natively on the host to illustrate better the
34 difference in the behavior when they are streamed to a virtual device.
38 * An Android device running Android 13 or newer to act as a client device.
41 `eng` build) to act as a host device. Even though VDM is available starting
45 * Both devices need to support
50 and the communication protocol are entirely up to the virtual device owner.
56 Simply connect your devices, navigate to the root of your Android checkout and
63 The interactive script will prompt you which apps to install to which of the
70 the APKs need to be built against a locally built SDK.
89 **Tip:** Subsequent installs without changes to permissions, etc. do not
111 the Host app will ask to create a CDM association: allow it.
120 1. Check out the [Demo apps](#demos) that are specifically meant to showcase
139 and start streaming the display contents to the client. The client will show
142 - Long pressing on an app icon will open a dialog to select an existing
143 display to launch the app on instead of creating a new one.
147 streaming the display contents to the client. The display on the Client app
149 back to the home activity. Run the commands below to enable this
159 streaming the display contents to the client. Run the commands below to
182 - **Remote** allows the host device to act as a pointer that controls the
189 events to the activity on the focused display.
192 display. Use together with the stylus demo. Run the commands below to enable
202 - **Device profile**: Enables device streaming CDM role as opposed to app
207 the host device's recent apps. Run the commands below to make this
216 - **Enable cross-device clipboard**: Whether to share the clipboard between
218 own isolated clipboards. Run the commands below to enable this
238 to enable this functionality.
259 request orientation change. Run the commands below to enable this
261 *This can be changed dynamically but only applies to newly created
278 - **Custom home**: Whether to use a custom activity as home on home displays,
279 or use the device-default secondary home activity. Run the commands below to
290 Note: The virtual keyboard acts like a physically connected keyboard to the
291 host device. If you want the software keyboard to be shown on the virtual
292 displays, you likely need to enable this in the host Settings. On a Pixel
296 commands below to enable this functionality. \
306 Policy* to be set to *Show IME on the remote display*. Run the commands
307 below to enable this functionality. \
318 the host device to a local file on the device. This can be helpful with
336 - Each display on the Client app has a "Rotate" button to switch between
338 the display of the streamed activity. The "Resize" button can be used to
342 contents of that display to an immersive fullscreen activity. The client's
343 back button/gestures are sent back to the streamed app. Use Volume Down on
344 the client device to exit fullscreen. Volume Up acts as a home key, if the
355 keyboard** are forwarded to the activity streamed on the focused display.
357 **Externally connected mouse** events are also forwarded to the relevant
366 accelerometer events, which allows for selecting which device's sensor to
379 - **Permissions**: A simple activity with buttons to request and revoke
388 APIs and allows for selecting which device's vibrator to use. By default,
414 - Added support for dynamic policy changes, so the device does not need to be
430 - Added device awareness to contexts.
440 - Improved support for audio, allowing routing to be based on the origin