mirror of
https://github.com/MaaAssistantArknights/MaaAssistantArknights.git
synced 2026-07-19 18:47:55 +08:00
i18n: EN device updates/fixes
This commit is contained in:
Constrat
@@ -3,107 +3,106 @@ order: 4
|
||||
icon: mingcute:android-fill
|
||||
---
|
||||
|
||||
# Android Physical Device
|
||||
# Android Physical Devices
|
||||
|
||||
::: warning
|
||||
This method involves ADB debugging and requires connection to a computer, it is **not recommended** for beginners.
|
||||
This method involves ADB command-line usage, has lower stability, and still requires computer connection. **Not recommended** for beginners.
|
||||
:::
|
||||
|
||||
::: info Note
|
||||
|
||||
0. Please also check [Connection](../connection.md).
|
||||
1. Starting from Android 10, Minitouch is no longer available when SELinux is in `Enforcing` mode, please switch to other touch modes or switch SELinux **temporary** to `Permissive` mode.
|
||||
2. Due to the extreme complexity of the Android ecosystem, try to change the `Connection Configuration` in MAA `Settings` - `Connection` to `General Mode` or `Compatibility Mode` or `2nd Resolution` or `General Mode (Blocked exception output)` until one of the modes is working properly.
|
||||
3. Since MAA only supports `16:9` ratio resolutions, devices with non-`16:9` or `9:16` screen ratios will need to be forced to change their resolution, which includes most modern devices. If the connected device has a native `16:9` or `9:16` screen resolution ratio, you can skip the `Change resolution' section. 4.
|
||||
4. Switch your device's navigation method to something other than `Full Screen Gestures`, such as the `Classic Navigation Keys` to avoid misuse.
|
||||
5. Please adjust the `Shaped Screen UI Adaptation` section in the in-game settings to 0 to avoid task errors.
|
||||
0. Please also refer to [Connection Settings](../connection.md).
|
||||
1. Starting from Android 10, Minitouch is no longer available when SELinux is in `Enforcing` mode. Please switch to other touch modes, or **temporarily** switch SELinux to `Permissive` mode.
|
||||
2. Due to the extreme complexity of the Android ecosystem, try changing the `Connection Configuration` in MAA `Settings` - `Connection Settings` to `General Mode`, `Compatibility Mode`, `2nd Resolution`, or `General Mode (Block Exception Output)` until one mode works properly.
|
||||
3. Since MAA only supports `16:9` aspect ratios, devices with non-`16:9` or `9:16` screen ratios (including most modern devices) need to have their resolution forcibly changed. If your device's native screen ratio is `16:9` or `9:16`, you can skip the `Change Resolution` section.
|
||||
4. Switch your device's navigation method to something other than `Full Screen Gestures`, such as `Classic Navigation Keys`, to avoid accidental operations.
|
||||
5. Please set the `Notched Screen UI Adaptation` option in the game settings to 0 to avoid task errors.
|
||||
:::
|
||||
|
||||
::: tip
|
||||
Typical `16:9` ratio resolutions are `3840x2160` (4K), `2560x1440` (2K), `1920x1080` (1080P), `1280x720` (720P).
|
||||
Typical `16:9` resolutions include `3840x2160` (4K), `2560x1440` (2K), `1920x1080` (1080P), and `1280x720` (720P).
|
||||
:::
|
||||
|
||||
## Download, run adb debugging tool and connect the device
|
||||
## Download and Run ADB Debug Tool to Connect Device
|
||||
|
||||
1. Download [adb](https://dl.google.com/android/repository/platform-tools-latest-windows.zip) and unzip it.
|
||||
2. Open the extracted folder, clear the address bar and type `cmd` and enter. 3.
|
||||
3. Type `adb` in the command prompt window that pops up, if it gives you a lot of help text in English, it will run successfully.
|
||||
4. Turn on `USB debugging` on your mobile phone, this may be different for each brand of mobile phone, so please use a search engine. Manufacturers may provide additional options for USB debugging, such as `USB Installation` and `USB Debugging (Security Settings)` in MIUI, please enable them at the same time.
|
||||
5. Connect your phone to your computer via data cable and enter the following command in the command prompt window you just got.
|
||||
1. Download [ADB](https://dl.google.com/android/repository/platform-tools-latest-windows.zip) and extract it.
|
||||
2. Open the extracted folder, clear the address bar, type `cmd`, and press Enter.
|
||||
3. In the command prompt window that appears, type `adb`. If you see extensive help text, the command ran successfully.
|
||||
4. Enable `USB Debugging` on your phone. The process varies by manufacturer, so use a search engine to find instructions. Manufacturers may provide additional USB debugging options, such as MIUI's `USB Installation` and `USB Debugging (Security Settings)` - enable these too.
|
||||
5. Connect your phone to the computer with a data cable and enter the following command in the command prompt:
|
||||
|
||||
```bash
|
||||
adb devices
|
||||
```
|
||||
|
||||
- If executed successfully, it will give you a message that the ``USB debugging`` device is connected.
|
||||
- When executed successfully, it will show connected USB debugging devices.
|
||||
|
||||
- Example of a successful connection:
|
||||
|
||||
```bash
|
||||
List of devices attached
|
||||
VFNDU1682100xxxx device
|
||||
VFNDU1682100xxxx device
|
||||
```
|
||||
|
||||
- **The alphanumeric combination in front of `device` is the serial number of the device, which also serves as the `connection address` of the MAA.**
|
||||
- **The alphanumeric combination before `device` is the device serial number, which is also your MAA `Connection Address`.**
|
||||
|
||||
- For modern Android devices to perform `USB debugging`, you need to click the pop-up window on the debugged device to authorise it, if not authorised, the example is as follows:
|
||||
- Modern Android devices require authorization on the device itself. Without authorization, you'll see:
|
||||
|
||||
```bash
|
||||
List of devices attached
|
||||
VFNDU1682100xxxx unauthorized
|
||||
Unauthorised
|
||||
VFNDU1682100xxxx unauthorized
|
||||
```
|
||||
|
||||
- If you are prompted for unauthorised or the serial number of the device shows `offline`, you need to reboot the device and computer and try again. If the problem is still not solved, you can delete the `.android` folder under the current user's personal folder and reboot again to retry, please search for the exact location.
|
||||
- If you consistently get "unauthorized" or "offline" status, restart both your device and computer. If that doesn't help, delete the `.android` folder in your user's personal directory and try again after restarting. Use search to find the exact location.
|
||||
|
||||
## Change resolution
|
||||
## Change Resolution
|
||||
|
||||
::: tip
|
||||
Mobile phone screen resolution is `short side*long side`, not `long side*short side` of computer monitor. Please determine the exact value according to your target device.
|
||||
Mobile screen resolution is specified as `short edge × long edge`, not `long edge × short edge` as with computer monitors. Determine the appropriate values for your specific device.
|
||||
:::
|
||||
|
||||
- If there is only one device within the device list above, you can change/restore the resolution directly by running the following command.
|
||||
- If you only have one device in your device list, run these commands to change/restore resolution:
|
||||
|
||||
```bash
|
||||
# View current resolution
|
||||
adb shell wm size
|
||||
# Restore the default resolution
|
||||
# Restore default resolution
|
||||
adb shell wm size reset
|
||||
|
||||
# Change resolution to 720p
|
||||
# Change to 720p
|
||||
adb shell wm size 720x1280
|
||||
# Change resolution to 1080p
|
||||
# Change to 1080p
|
||||
adb shell wm size 1080x1920
|
||||
```
|
||||
|
||||
- If there are multiple devices, you need to add the parameter `-s <target device serial number>` between `adb` and `shell`, as shown in the following example.
|
||||
- If you have multiple devices, add the parameter `-s <target device serial number>` between `adb` and `shell`:
|
||||
|
||||
```bash
|
||||
# View current resolution
|
||||
adb -s VFNDU1682100xxxx shell wm size
|
||||
# Restore the default resolution
|
||||
# Restore default resolution
|
||||
adb -s VFNDU1682100xxxx shell wm size reset
|
||||
|
||||
# Change resolution to 720p
|
||||
# Change to 720p
|
||||
adb -s VFNDU1682100xxxx shell wm size 720x1280
|
||||
# Change resolution to 1080p
|
||||
# Change to 1080p
|
||||
adb -s VFNDU1682100xxxx shell wm size 1080x1920
|
||||
```
|
||||
|
||||
- Some applications with irregular design may still have wrong layout after restoring the resolution, usually restarting the corresponding application or device can solve the problem.
|
||||
- Some apps with irregular designs may still have layout issues after resolution restoration. Usually, restarting the app or device resolves this.
|
||||
|
||||
::: danger Warning
|
||||
It is strongly recommended to restore the resolution **before** restarting the device next time, otherwise it may lead to unpredictable consequences depending on the device, ~~including but not limited to chaotic layout, touch misalignment, application flashback, unlocking, etc~~.
|
||||
Strongly recommended to restore the default resolution **before** restarting your device. Otherwise, depending on your device, unpredictable consequences may occur, ~~including layout chaos, touch misalignment, app crashes, inability to unlock, etc~~.
|
||||
:::
|
||||
|
||||
## Automating resolution changes
|
||||
## Automate Resolution Changes
|
||||
|
||||
1. Create two new text files in the MAA directory and fill them with the following contents.
|
||||
1. Create two text files in the MAA directory with the following content:
|
||||
|
||||
```bash
|
||||
# Adjust resolution to 1080p
|
||||
adb -s <target device serial number> shell wm size 1080x1920
|
||||
# Reduce screen brightness (optional)
|
||||
# Lower screen brightness (optional)
|
||||
adb -s <target device serial number> shell settings put system screen_brightness 1
|
||||
```
|
||||
|
||||
@@ -112,69 +111,69 @@ It is strongly recommended to restore the resolution **before** restarting the d
|
||||
adb -s <target device serial number> shell wm size reset
|
||||
# Increase screen brightness (optional)
|
||||
adb -s <target device serial number> shell settings put system screen_brightness 20
|
||||
# Return to desktop (optional)
|
||||
# Return to home screen (optional)
|
||||
adb -s <target device serial number> shell input keyevent 3
|
||||
# Lock screen (optional)
|
||||
adb -s <target device serial number> shell input keyevent 26
|
||||
```
|
||||
|
||||
2. Rename the first file to `startup.bat` and the second file to `finish.bat`.
|
||||
2. Rename the first file to `startup.bat` and the second to `finish.bat`.
|
||||
|
||||
- If you don't see the double confirmation dialogue box for changing extension after renaming, and the file icon doesn't change, please search for "How to display file extensions in Windows".
|
||||
- If no confirmation dialog appears when changing the extension and the file icon doesn't change, search for "How to show file extensions in Windows."
|
||||
|
||||
3. In `Settings` - `Connection` - `Starts with Script` and `Ends with Script` of MAA, fill in `startup.bat` and `finish.bat` respectively.
|
||||
3. In MAA's `Settings` - `Connection Settings`, set `Start Script` to `startup.bat` and `End Script` to `finish.bat`.
|
||||
|
||||
## Connecting to MAA
|
||||
## Connect to MAA
|
||||
|
||||
### Wired connection
|
||||
### Wired Connection
|
||||
|
||||
::: tip
|
||||
A wired connection does not require any IP address or port, only the device serial number given by `adb devices`.
|
||||
Wired connections don't need IP addresses or ports - just the device serial number from `adb devices`.
|
||||
:::
|
||||
|
||||
1. Fill in the MAA `Settings` - `Connection` - `Connection address` with the serial number of the target device obtained above.
|
||||
1. Enter the target device serial number from above into MAA's `Settings` - `Connection Settings` - `Connection Address`.
|
||||
2. Link Start!
|
||||
|
||||
### Wireless Connection
|
||||
|
||||
- Make sure that the device and the computer are on the same LAN and can communicate with each other. Settings such as `AP Isolation`, `Guest Network`, etc. can prevent communication between devices, please refer to the documentation of the corresponding router.
|
||||
- Wireless debugging is disabled after a device reboot and needs to be reset.
|
||||
- Ensure your device and computer are on the same network and can communicate with each other. Router settings like `AP Isolation` or `Guest Network` can block device communication - check your router documentation.
|
||||
- Wireless debugging is disabled after device restart and must be re-enabled.
|
||||
|
||||
#### To open a wireless port using `adb tcpip`
|
||||
#### Using `adb tcpip` for Wireless Debugging
|
||||
|
||||
1. Enable wireless debugging by entering the following command in the command prompt window you just opened.
|
||||
1. In the command prompt, enable wireless debugging:
|
||||
|
||||
```bash
|
||||
adb tcpip 5555
|
||||
# Add the -s parameter to specify the serial number if multiple devices are present.
|
||||
# Add -s parameter to specify the serial number if multiple devices are connected
|
||||
```
|
||||
|
||||
2. View the device IP address.
|
||||
2. Find your device's IP address:
|
||||
|
||||
- Go to `Settings` - `WLAN` on your mobile phone and click on the currently connected wireless network to view the IP address.
|
||||
- The IP address is different for different brands of devices, so please find it yourself.
|
||||
- Go to your phone's `Settings` - `Wi-Fi`, tap the connected network to view the IP address.
|
||||
- The location varies by manufacturer - search for instructions if needed.
|
||||
|
||||
3. Put `<IP>:5555` into MAA `Settings` - `Connection` - `Connection Address`, such as `192.168.1.2:5555`.
|
||||
3. Enter `<IP>:5555` in MAA's `Settings` - `Connection Settings` - `Connection Address`, e.g., `192.168.1.2:5555`.
|
||||
4. Link Start!
|
||||
|
||||
#### Use `adb pair` to open the wireless port
|
||||
#### Using `adb pair` for Wireless Debugging
|
||||
|
||||
::: tip
|
||||
`adb pair` wireless pairing, i.e. connecting after pairing using `wireless debugging` in Developer Options on Android 11 and newer, avoids the need for a wired connection compared to `adb tcpip`.
|
||||
`adb pair` wireless pairing (available in Android 11 and later via Developer Options) allows connection without a physical USB connection, unlike `adb tcpip`.
|
||||
:::
|
||||
|
||||
1. Go to your phone's developer options, tap `Wireless debugging` and turn it on, tap OK, tap `Pair device using pairing code` and don't close the pop-up window that appears until pairing is complete. 2.
|
||||
1. On your phone, go to Developer Options, tap `Wireless Debugging` and enable it. Tap `Pair device with pairing code` and keep the popup open until pairing completes.
|
||||
|
||||
2. To perform pairing.
|
||||
2. Complete the pairing:
|
||||
|
||||
1. At the command prompt, type `adb pair <IP address and port given in the device pop-up>` and enter.
|
||||
2. Type `<six-digit pairing code given in the device pop-up window>` and enter.
|
||||
3. The window appears with something like `Successfully paired to <IP:port>` and the pop-up window on the device disappears automatically, and the computer name appears at the bottom in the paired devices.
|
||||
1. In the command prompt, type `adb pair <IP address and port shown in the device popup>` and press Enter.
|
||||
2. Enter the six-digit pairing code from the device popup and press Enter.
|
||||
3. When you see `Successfully paired to <IP:port>`, the device popup will close automatically, and your computer's name will appear in the paired devices list.
|
||||
|
||||
3. Put the `<IP address and port>` given on the current device's screen into MAA `Settings` - `Connection` - `Connection Address`, e.g. `192.168.1.2:11451`, **must be different from the one you have just put in**.
|
||||
3. Enter the IP address and port shown on your device screen into MAA's `Settings` - `Connection Settings` - `Connection Address`, e.g., `192.168.1.2:11451`. **This is different from the address used for pairing**.
|
||||
4. Link Start!
|
||||
|
||||
#### Enable the wireless port with root privileges
|
||||
#### Using Root to Enable Wireless ADB
|
||||
|
||||
~~If you have access to root, why do you need to read this document~~
|
||||
|
||||
|
||||
@@ -3,142 +3,146 @@ order: 3
|
||||
icon: teenyicons:linux-alt-solid
|
||||
---
|
||||
|
||||
# Linux Emulator and Container
|
||||
# Linux Emulators and Containers
|
||||
|
||||
## Preparation
|
||||
|
||||
You can choose one of the following installation methods:
|
||||
Choose one of the following installation methods:
|
||||
|
||||
### Use maa-cli
|
||||
### Using maa-cli
|
||||
|
||||
[maa-cli](https://github.com/MaaAssistantArknights/maa-cli) is a simple CLI for MAA made with Rust. Please read installation and usage tutorials in [User Guide for CLI](../cli/).
|
||||
[maa-cli](https://github.com/MaaAssistantArknights/maa-cli) is a simple command-line tool for MAA written in Rust. Please read the [CLI User Guide](../cli/) for installation and usage instructions.
|
||||
|
||||
### Use Wine
|
||||
### Using Wine
|
||||
|
||||
The MAA WPF GUI can currently be run using Wine.
|
||||
The MAA WPF GUI can currently be run through Wine.
|
||||
|
||||
#### Installation Steps
|
||||
|
||||
1. Go to the [.NET Release Page](https://dotnet.microsoft.com/en-us/download/dotnet/8.0) to download and install the .NET **Desktop** Runtime for Windows.
|
||||
1. Go to the [.NET download page](https://dotnet.microsoft.com/en-us/download/dotnet/8.0) and download/install the Windows version of .NET **Desktop** Runtime.
|
||||
|
||||
2. Download MAA for Windows, unzip it and run `wine MAA.exe`.
|
||||
2. Download the Windows version of MAA, extract it, and run `wine MAA.exe`.
|
||||
|
||||
::: info Note
|
||||
You need to set the ADB path to [`adb.exe` for Windows](https://dl.google.com/android/repository/platform-tools-latest-windows.zip) in the connection settings.
|
||||
You need to set the ADB path to the [Windows version of `adb.exe`](https://dl.google.com/android/repository/platform-tools-latest-windows.zip) in the connection settings.
|
||||
|
||||
If you need to connect to USB devices via ADB, please run `adb start-server` outside of Wine first, i.e. connect to the native ADB server via Wine.
|
||||
If you need to connect to USB devices via ADB, first run `adb start-server` outside of Wine to connect to the native ADB server through Wine.
|
||||
:::
|
||||
|
||||
#### Use Linux native MaaCore (experimental feature)
|
||||
#### Using Linux Native MaaCore (Experimental)
|
||||
|
||||
Download the [MAA Wine Bridge](https://github.com/MaaAssistantArknights/MaaAssistantArknights/tree/dev/src/MaaWineBridge) source and build it, replace the Windows version with the generated `MaaCore.dll` (ELF file) in the same directory as the Linux native dynamic libraries (`libMaaCore.so` and dependencies).
|
||||
Download and build the [MAA Wine Bridge](https://github.com/MaaAssistantArknights/MaaAssistantArknights/tree/dev/src/MaaWineBridge) source code, replace the Windows version with the generated `MaaCore.dll` (ELF file), and place the Linux native dynamic libraries (`libMaaCore.so` and dependencies) in the same directory.
|
||||
|
||||
Running `MAA.exe` through Wine will load the Linux native libraries.
|
||||
When running `MAA.exe` through Wine, it will load the Linux native libraries.
|
||||
|
||||
::: info Note
|
||||
To use Linux native MaaCore, you need to set the ADB path to Linux native ADB in the connection settings.
|
||||
When using the Linux native MaaCore, you need to set the ADB path to the Linux native ADB in the connection settings.
|
||||
:::
|
||||
|
||||
#### Linux Desktop Integration (experimental feature)
|
||||
#### Linux Desktop Integration (Experimental)
|
||||
|
||||
Desktop integration provides native desktop notification support and the ability to map fontconfig font configurations to WPF.
|
||||
Desktop integration provides native desktop notification support and maps fontconfig font configurations to WPF.
|
||||
|
||||
Enable it by placing `MaaDesktopIntegration.so` generated by MAA Wine Bridge in the same directory as `MAA.exe`.
|
||||
Place the `MaaDesktopIntegration.so` generated by MAA Wine Bridge in the same directory as `MAA.exe` to enable this feature.
|
||||
|
||||
#### Known Issues
|
||||
|
||||
- Wine DirectWrite forces hinting to be enabled and does not pass DPI to FreeType, resulting in poor font display.
|
||||
- When not using native desktop notifications, the popup notification will grab the system-wide mouse focus, making it impossible to operate other windows. This can be mitigated by enabling virtual desktop mode via `winecfg`, or disabling desktop notifications.
|
||||
- Wine-staging users need to disable the `Hide Wine Version` option in `winecfg` in order for MAA to properly detect the Wine environment.
|
||||
- Wine's Light theme causes some text colours in WPF to be abnormal, it is recommended to switch to no theme (Windows Classic theme) in `winecfg`.
|
||||
- Wine uses the old XEmbed tray icon, which may not work properly under GNOME.
|
||||
- Auto-update is not supported when using Linux native MaaCore (~~Updater: I think I should download a Windows version~~).
|
||||
- Wine DirectWrite forces hinting and doesn't pass DPI to FreeType, resulting in poor font display.
|
||||
- When not using native desktop notifications, popup notifications grab the system-wide mouse focus, making it impossible to interact with other windows. You can mitigate this by enabling virtual desktop mode in `winecfg` or disabling desktop notifications.
|
||||
- Wine-staging users need to disable the `Hide Wine version` option in `winecfg` for MAA to correctly detect the Wine environment.
|
||||
- Wine's Light theme causes text color issues in WPF. We recommend using no theme (Windows Classic theme) in `winecfg`.
|
||||
- Wine uses the old XEmbed tray icon system, which may not work properly under GNOME.
|
||||
- When using Linux native MaaCore, automatic updates are not supported (~~the updater thinks: I should download a Windows version~~)
|
||||
|
||||
### Use Python
|
||||
### Using Python
|
||||
|
||||
#### 1. Installing dynamic library
|
||||
#### 1. Installing MAA Dynamic Library
|
||||
|
||||
1. Download and extract `Linux library` in [MAA Website](https://maa.plus/), or install from linux software repository:
|
||||
1. Download and extract the Linux dynamic library from the [MAA website](https://maa.plus/), or install from a software repository:
|
||||
|
||||
- AUR：[maa-assistant-arknights](https://aur.archlinux.org/packages/maa-assistant-arknights), edit the script according to the post-install instruction.
|
||||
- AUR: [maa-assistant-arknights](https://aur.archlinux.org/packages/maa-assistant-arknights), follow the post-installation instructions
|
||||
- Nixpkgs: [maa-assistant-arknights](https://github.com/NixOS/nixpkgs/blob/nixos-unstable/pkgs/by-name/ma/maa-assistant-arknights/package.nix)
|
||||
|
||||
2. Open `sample.py` in `./MAA-v{VERSION}-linux-{ARCH}/Python/`
|
||||
2. Navigate to `./MAA-v{version}-linux-{architecture}/Python/` and open the `sample.py` file
|
||||
|
||||
> **Note**
|
||||
> The precompiled version is built in a relatively new distro (Ubuntu 22.04), you may run into binary compatability problem, if libstdc++ in your environment is too old.
|
||||
> Where you should reference to [Linux tutorial](../../develop/linux-tutorial.md), or run inside a container instead.
|
||||
::: tip
|
||||
The precompiled version includes dynamic libraries compiled on relatively new Linux distributions (Ubuntu 22.04). If your system has an older libstdc++ version, you might encounter ABI incompatibility issues.
|
||||
You can refer to the [Linux Compilation Tutorial](../../develop/linux-tutorial.md) to recompile or use a container solution.
|
||||
:::
|
||||
|
||||
#### 2. `adb` Settings
|
||||
#### 2. ADB Configuration
|
||||
|
||||
1. Target to [`if asst.connect('adb.exe', '127.0.0.1:5554'):`](https://github.com/MaaAssistantArknights/MaaAssistantArknights/blob/722f0ddd4765715199a5dc90ea1bec2940322344/src/Python/sample.py#L48)
|
||||
1. Find the line [`if asst.connect('adb.exe', '127.0.0.1:5554'):`](https://github.com/MaaAssistantArknights/MaaAssistantArknights/blob/b4fc3528decd6777441a8aca684c22d35d2b2574/src/Python/sample.py#L62)
|
||||
|
||||
2. `adb` Tools Settings
|
||||
2. ADB Tool Configuration
|
||||
|
||||
- If you use `avd` in `Android Studio` as your emulator, it contains `adb` that you can use it directly. Just fill in your `adb` path in `adb.exe`, you can usually find it in `$HOME/Android/Sdk/platform-tools/` , eg.:
|
||||
- If using `Android Studio`'s `AVD` emulator, it comes with ADB. You can directly specify the ADB path to replace `adb.exe`, typically found in `$HOME/Android/Sdk/platform-tools/`, for example:
|
||||
|
||||
```python
|
||||
if asst.connect("/home/foo/Android/Sdk/platform-tools/adb", "avd_ID"):
|
||||
```
|
||||
```python
|
||||
if asst.connect("/home/foo/Android/Sdk/platform-tools/adb", "emulator's ADB address"):
|
||||
```
|
||||
|
||||
- If you use other emulators, you have to install `adb` first: `$ sudo apt install adb` and then fill in the path of adb or just fill in `adb` if you had put it into the `PATH` environment variable.
|
||||
- For other emulators, first install ADB: `$ sudo apt install adb`, then either specify the path or simply use `adb` if it's in your `PATH` environment variable.
|
||||
|
||||
3. Emulator `adb` ID Settings
|
||||
3. Getting the Emulator's ADB Address
|
||||
|
||||
- You can use the adb tool directly: `$ ${adb_path} devices` , eg.:
|
||||
- Use the ADB tool directly: `$ adb_path devices`, for example:
|
||||
|
||||
```shell
|
||||
$ /home/foo/Android/Sdk/platform-tools/adb devices
|
||||
List of devices attached
|
||||
emulator-5554 device
|
||||
```
|
||||
```shell
|
||||
$ /home/foo/Android/Sdk/platform-tools/adb devices
|
||||
List of devices attached
|
||||
emulator-5554 device
|
||||
```
|
||||
|
||||
- `emulator-5554` that the terminal returns is the ID of emulator adb, replacing `127.0.0.1:5555` with it, eg.：
|
||||
- The returned `emulator-5554` is the emulator's ADB address. Replace `127.0.0.1:5555` with it, for example:
|
||||
|
||||
```python
|
||||
if asst.connect("/home/foo/Android/Sdk/platform-tools/adb", "emulator-5554"):
|
||||
```
|
||||
```python
|
||||
if asst.connect("/home/foo/Android/Sdk/platform-tools/adb", "emulator-5554"):
|
||||
```
|
||||
|
||||
4. Now you can test: `$ python3 sample.py` , if return `连接成功` , you almost finish setting.
|
||||
4. Now you can test with `$ python3 sample.py`. If it returns "Connection successful," you're ready to proceed.
|
||||
|
||||
#### 3. Tasks Settings
|
||||
#### 3. Task Configuration
|
||||
|
||||
Customizing tasks: Reference to [AsstAppendTask](../../protocol/integration.md#asstappendtask) and modify [`# 任务及参数请参考 docs/集成文档.md`](https://github.com/MaaAssistantArknights/MaaAssistantArknights/blob/722f0ddd4765715199a5dc90ea1bec2940322344/src/Python/sample.py#L54) section in `sample.py`.
|
||||
Custom tasks: Refer to the [Integration Documentation](../../protocol/integration.md) and modify the [`# Task parameters can be found in docs/integration.md`](https://github.com/MaaAssistantArknights/MaaAssistantArknights/blob/722f0ddd4765715199a5dc90ea1bec2940322344/src/Python/sample.py#L54) section in `sample.py`
|
||||
|
||||
## Emulator Supports
|
||||
## Emulator Support
|
||||
|
||||
### ✅ [AVD](https://developer.android.com/studio/run/managing-avds)
|
||||
|
||||
Requests: Resolution should be 16:9 and above 720p
|
||||
Requirements: 16:9 screen resolution larger than 720p
|
||||
|
||||
Recommendation: x86\_64 architecture (R - 30 - x86\_64 - Android 11.0) with `Linux x64 动态库` in MAA
|
||||
Recommended configuration: x86_64 architecture (R - 30 - x86_64 - Android 11.0) with MAA's Linux x64 dynamic library
|
||||
|
||||
Note: Starting from Android 10, Minitouch is no longer available when SELinux is in `Enforcing` mode. Please switch to other touch modes, or **temporarily** switch SELinux to `Permissive` mode.
|
||||
|
||||
### ⚠️ [Genymotion](https://www.genymotion.com/)
|
||||
|
||||
Native x86\_64 architecture in high version of Android, light weight but easy to crash when running Arknights.
|
||||
High Android versions include x86_64 framework. Lightweight but tends to crash when running Arknights.
|
||||
|
||||
We have not testing strictly, but adb functions and path have no error.
|
||||
Not thoroughly tested yet, but ADB functionality and path retrieval work without issues.
|
||||
|
||||
## Containerized Android
|
||||
## Containerized Android Support
|
||||
|
||||
> **Note**
|
||||
> The following solutions are likely to depend on special kernel modules, make sure to have them installed accordingly.
|
||||
::: tip
|
||||
The following solutions typically require specific kernel modules. Please install the appropriate modules according to your distribution and the particular solution.
|
||||
:::
|
||||
|
||||
### ✅ [Waydroid](https://waydro.id/)
|
||||
|
||||
Need to reset the resolution to 16:9 (You can set it above 720P):
|
||||
After installation, you need to reset the resolution (to 16:9 ratio and greater than 720p, then restart):
|
||||
|
||||
```shell
|
||||
waydroid prop set persist.waydroid.width 1280
|
||||
waydroid prop set persist.waydroid.height 720
|
||||
```
|
||||
|
||||
After restarting, record `IP address` in `Setting` - `About phone` , fill `${IP address}:5555` to the adb IP address in `sample.py` .
|
||||
To set up ADB IP address: Go to `Settings` - `About` - `IP address`, note the first `IP`, and use `${recorded IP}:5555` in `sample.py` for the ADB IP.
|
||||
|
||||
If you are using amdgpu, `screencap` command may write messages to stderr, causing image decoding error.
|
||||
Run `adb exec-out screencap | xxd | head` to check if there is something like `/vendor/etc/hwdata/amdgpu.ids: No such file...` in the output.
|
||||
Modify screencap commands in `resource/config.json` from `adb exec-out screencap` to `adb exec-out 'screencap 2>/dev/null'` as a workaround.
|
||||
If using amdgpu, the `screencap` command might output messages to stderr, causing image decoding failures.
|
||||
You can run `adb exec-out screencap | xxd | head` and check if there's text like `/vendor/etc/hwdata/amdgpu.ids: No such file...` in the output.
|
||||
If present, try changing the screenshot command in `resource/config.json` from `adb exec-out screencap` to `adb exec-out 'screencap 2>/dev/null'`.
|
||||
|
||||
### ✅ [redroid](https://github.com/remote-android/redroid-doc)
|
||||
|
||||
Arknights runs properly in Android 11 image. Do remember to expose port 5555 for adb.
|
||||
Android 11 version images can run the game normally. Make sure to expose port 5555 for ADB.
|
||||
|
||||
@@ -3,62 +3,62 @@ order: 2
|
||||
icon: basil:apple-solid
|
||||
---
|
||||
|
||||
# Mac Emulator
|
||||
# macOS Emulators
|
||||
|
||||
## Apple Silicon Chips
|
||||
|
||||
### ✅ [PlayCover](https://playcover.io) (The software runs most fluently for its nativity 🚀)
|
||||
### ✅ [PlayCover](https://playcover.io) (Runs most fluently as it's native 🚀)
|
||||
|
||||
Compatible in beta, plz submit issue marked with `MacOS` when encounter errors.
|
||||
Experimental support. Please submit issues if you encounter problems, and include `MacOS` in the title.
|
||||
|
||||
P.S.: For the reason of `MacOS` mechanism itself, errors might occur when `PlayCover` is minimized and you switch to others windows. The errors of screenshot might crash `MAA`. Reference 👉🏻️[issue](https://github.com/MaaAssistantArknights/MaaAssistantArknights/issues/4371#issuecomment-1527977512)
|
||||
Note: Due to macOS system limitations, screenshot issues may occur when minimizing the game window, switching to other windows while in Stage Manager, or moving the window to other desktops/screens. Related issue: [#4371](https://github.com/MaaAssistantArknights/MaaAssistantArknights/issues/4371#issuecomment-1527977512)
|
||||
|
||||
1. Requests: MAA version above v4.13.0-rc.1
|
||||
0. Requirements: MAA version v4.13.0-rc.1 or newer
|
||||
|
||||
2. Download and install [fork version of PlayCover](https://github.com/hguandl/PlayCover/releases)
|
||||
1. Download and install the [forked version of PlayCover](https://github.com/hguandl/PlayCover/releases).
|
||||
|
||||
3. Download [decrypted version of Arknights](https://decrypt.day/app/id1454663939), and then install in PlayCover.
|
||||
2. Download the [decrypted Arknights client package](https://decrypt.day/app/id1454663939) and install it in PlayCover.
|
||||
|
||||
4. Right-click Arknights in PlayCover, choose `Setting` - `Jailbreak Bypass`, enable `Enable PlayChain`, `Enable Jailbreak Bypass (Alpha)`, `Insert Introspection Library`, `MaaTools`, then click `OK`.
|
||||
3. Right-click on Arknights in PlayCover, select `Settings` - `Bypasses`, check `Enable PlayChain`, `Enable Jailbreak Detection Bypass`, `Insert Introspection Libraries`, `MaaTools`, then click `OK`.
|
||||
|
||||
5. Relaunch Arknights, `[localhost:${port number}]` will appear above, meaning launching is successful.
|
||||
4. Now launch Arknights, which should run normally. The title bar will end with `[localhost:port]`, indicating successful activation.
|
||||
|
||||
6. In MAA, click `Settings` - `Connection Settings`, `Minitouch` choose `MacPlayTools`. `Connection Address` filling the content in `[]` .
|
||||
5. In MAA, go to `Settings` - `Connection Settings`, set `Touch Mode` to `MacPlayTools`. For `Connection Address`, enter the content inside the `[]` from the title bar.
|
||||
|
||||
7. Finish, MAA is able to build connection. If errors occur in image recognition, you could try to set resolution to 1080P in PlayCover.
|
||||
6. Setup complete! MAA should now connect successfully. If you encounter image recognition errors, try setting the resolution to 1080P in PlayCover.
|
||||
|
||||
8. 3-5 do not need to be repeated, you could just launch Arknights after that. While you have to repeat step 2 if Arknights is updated.
|
||||
7. Steps 3-5 only need to be done once. After that, just launch Arknights. After each Arknights client update, you'll need to repeat step 2.
|
||||
|
||||
### ✅ [MuMu Emulator Pro](https://mumu.163.com/mac/)
|
||||
|
||||
Supported, but less thoroughly tested. Requires using a touch mode other than `MacPlayTools`. Related issue: [#8098](https://github.com/MaaAssistantArknights/MaaAssistantArknights/issues/8098)
|
||||
|
||||
### ✅ [AVD](https://developer.android.com/studio/run/managing-avds)
|
||||
|
||||
Compatible
|
||||
Supported, but starting from Android 10, Minitouch is no longer available when SELinux is in `Enforcing` mode. Please switch to other touch modes, or **temporarily** switch SELinux to `Permissive` mode.
|
||||
|
||||
### ✅ [BlueStacks Air](https://www.bluestacks.com/mac) (Free, optimized for Apple M-series chips)
|
||||
|
||||
Supported, tested, and can be connected via maatouch at `127.0.0.1:5555`.
|
||||
Supported and tested. Can be connected using MaaTouch via `127.0.0.1:5555`.
|
||||
|
||||
You need to enable **"Android Debugging (ADB)"** in the emulator's **`Settings`** - **`Advanced`** section.
|
||||
You need to enable `Android Debugging (ADB)` in the emulator's `Settings` - `Advanced` section.
|
||||
|
||||
## Intel Chips
|
||||
|
||||
::: tip
|
||||
Due to a lack of manpower for Mac version development, updates are relatively slower. It is recommended to use Mac's built-in multi-system feature to install Windows and use the Windows version of MAA.
|
||||
Due to limited development resources for the Mac version, updates are relatively slower. We recommend using Boot Camp to install Windows and using the Windows version of MAA instead.
|
||||
:::
|
||||
|
||||
### ✅ [Bluestacks-CN 5](https://www.bluestacks.cn/)
|
||||
### ✅ [BlueStacks](https://www.bluestacks.com/)
|
||||
|
||||
Fully compatible. Need to turn on `Settings` - `Engine Settings` - `Allow ADB connection`.
|
||||
Fully compatible. You need to enable `Android Debug Bridge` in the emulator's `Settings` - `Advanced`.
|
||||
|
||||
### ✅ [Bluestacks 5](https://www.bluestacks.com/tw/index.html)
|
||||
|
||||
Fully compatible. Need to turn on `Settings` - `Advanced` - `Android Debug Bridge`.
|
||||
|
||||
### ✅ [Nox](https://www.yeshen.com/)
|
||||
### ✅ [Nox Player](https://www.bignox.com/)
|
||||
|
||||
Fully compatible.
|
||||
|
||||
P.S.: Nox adb bin file path in Mac is `/Applications/NoxAppPlayer.app/Contents/MacOS/adb` , in parent path `MacOS` you are able to use `adb devices` command to get adb path.
|
||||
Note: On macOS, the Nox ADB binary is located at `/Applications/NoxAppPlayer.app/Contents/MacOS/adb`. In the `MacOS` parent directory, you can use the `adb devices` command to check the ADB port.
|
||||
|
||||
### ✅ [AVD](https://developer.android.com/studio/run/managing-avds)
|
||||
|
||||
Compatible.
|
||||
Supported, but starting from Android 10, Minitouch is no longer available when SELinux is in `Enforcing` mode. Please switch to other touch modes, or **temporarily** switch SELinux to `Permissive` mode.
|
||||
|
||||
@@ -3,13 +3,9 @@ order: 1
|
||||
icon: ri:windows-fill
|
||||
---
|
||||
|
||||
# Windows Emulator
|
||||
# Windows Emulators
|
||||
|
||||
:::warning
|
||||
TODO: replace these Chinese emulators links with English ones
|
||||
:::
|
||||
|
||||
The following emulators are displayed randomly in no particular order.
|
||||
The following emulators are displayed in random order with no particular ranking.
|
||||
|
||||
<script setup>
|
||||
import MarkdownIt from 'markdown-it'
|
||||
@@ -25,29 +21,29 @@ const shuffleArray = (array) => {
|
||||
|
||||
const fullySupport = shuffleArray([
|
||||
{
|
||||
name: 'Bluestacks 5',
|
||||
name: 'BlueStacks 5',
|
||||
link: 'https://www.bluestacks.com/',
|
||||
note: 'Fully compatible. Need to turn on ADB Connectivity in the emulator `Settings` → `Advanced` → `Android Debug Bridge` → `Enable`. Known to be compatible with Hyper-V.\n\n- Recommended to download [Offline Installer](https://support.bluestacks.com/hc/en-us/articles/4402611273485-BlueStacks-5-offline-installer) to avoid slow and bundled installation; recommend installing [Android 11](https://support.bluestacks.com/hc/en-us/articles/4402611273485-BlueStacks-5-offline-installer#:~:text=To%20install%20BlueStacks%205%20Android%2011) version; to uninstall it, please use the official [Uninstall Tool](https://support.bluestacks.com/hc/en-us/articles/360057724751-How-to-uninstall-BlueStacks-5-BlueStacks-X-and-BlueStacks-Services-completely-from-your-PC) to get rid of the residue.\n- If the adb port number keeps changing irregularly and is different every time you start it, it may be because your computer has [Hyper-V](https://support.bluestacks.com/hc/en-us/articles/4415238471053-System-requirements-for-BlueStacks-5-on-Hyper-V-enabled-Windows-10-and-11) enabled. MAA will now try to automatically read the port number within the Blue Stacker emulator configuration file, if this does not work/you have a need to multi-open/have more than one emulator kernel installed, please refer to the [Connection (TODO)](../connection.html#the-port-number-of-bluestack-emulator-hyper-v-is-different-every-time-it-is-started) to make changes. Since Hyper-V runs as administrator, operations that don\'t involve adb such as auto-shutdown of the emulator, auto-detect connection, etc. also need to run MAA as administrator.',
|
||||
note: 'Fully compatible. Need to turn on ADB Connectivity in the emulator `Settings` → `Advanced` → `Android Debug Bridge` → `Enable`. Known to be compatible with Hyper-V.\n\n- Recommended to download [Offline Installer](https://support.bluestacks.com/hc/en-us/articles/4402611273485-BlueStacks-5-offline-installer) to avoid slow and bundled installation; recommend installing [Android 11](https://support.bluestacks.com/hc/en-us/articles/4402611273485-BlueStacks-5-offline-installer#:~:text=To%20install%20BlueStacks%205%20Android%2011) version; to uninstall it, please use the official [Uninstall Tool](https://support.bluestacks.com/hc/en-us/articles/360057724751-How-to-uninstall-BlueStacks-5-BlueStacks-X-and-BlueStacks-Services-completely-from-your-PC) to get rid of residues.\n- If the ADB port number keeps changing irregularly and is different every time you start it, it may be because your computer has [Hyper-V](https://support.bluestacks.com/hc/en-us/articles/4415238471053-System-requirements-for-BlueStacks-5-on-Hyper-V-enabled-Windows-10-and-11) enabled. MAA will now try to automatically read the port number from the BlueStacks emulator configuration file. If this doesn\'t work, or you need to use multiple instances, or have installed multiple emulator cores, please refer to [Connection Settings](../connection.html#bluestacks-emulator-hyper-v-port-number-changes-every-startup) to make adjustments. Since Hyper-V runs as administrator, operations that don\'t involve ADB such as automatic emulator shutdown or connection detection also need MAA to run as administrator.',
|
||||
},
|
||||
{
|
||||
name: 'MuMu Emulator 12',
|
||||
link: 'https://mumu.163.com/',
|
||||
note: 'Fully compatible, with additional support for the [Screenshot Enhanced Mode](../connection.html#mumu-screenshot-enhanced-mode). Known to be compatible with Hyper-V.\n\n- The "Exit emulator when done" function may occasionally be abnormal, if you encounter it, please contact MuMu official for feedback.\n- You need to check the port information of the corresponding instance through the ADB button of MuMu 12 Multiple Opener when you open more than one instance, and change the port number of the connection address in MAA `Settings` - `Connection Settings` to the corresponding port.',
|
||||
link: 'https://www.mumuglobal.com/',
|
||||
note: 'Fully compatible, with additional support for [Screenshot Enhanced Mode](../connection.html#mumu-screenshot-enhanced-mode). Known to be compatible with Hyper-V.\n\n- The "Exit emulator when done" function may occasionally have issues. If you encounter problems, please report them to MuMu\'s official support.\n- When running multiple instances, you need to check the port information of each instance through the ADB button in MuMu 12 Multi-Instance Manager, then change the port number in MAA `Settings` - `Connection Settings` to match the corresponding port.',
|
||||
},
|
||||
{
|
||||
name: 'LDPlayer',
|
||||
link: 'https://www.ldmnq.com/',
|
||||
note: 'Fully compatible, with additional support for the [Screenshot Enhanced Mode](../connection.html#ld-screenshot-enhanced-mode). Need to turn on ADB Connectivity in the emulator : `Settings` → `Others` → `ADB debugging` → `Enable local connection`. Known to be compatible with Hyper-V.\n\n- LDPlayer 9 installer will automatically and silently disable Hyper-V during the installation process. Please pay attention if you have related needs.',
|
||||
link: 'https://www.ldplayer.net/',
|
||||
note: 'Fully compatible, with additional support for [Screenshot Enhanced Mode](../connection.html#ld-screenshot-enhanced-mode). Known to be compatible with Hyper-V.\n\n- LDPlayer 9 installer will automatically and silently disable Hyper-V during the installation process. Please be aware of this if you need Hyper-V for other purposes.',
|
||||
},
|
||||
{
|
||||
name: 'Nox',
|
||||
link: 'https://www.yeshen.com/',
|
||||
note: 'Fully compatible, but less tested. Known to be compatible with Hyper-V.',
|
||||
name: 'Nox Player',
|
||||
link: 'https://www.bignox.com/',
|
||||
note: 'Fully compatible, but less thoroughly tested. Known to be compatible with Hyper-V.',
|
||||
},
|
||||
{
|
||||
name: 'Memu',
|
||||
link: 'https://www.xyaz.cn/',
|
||||
note: 'Fully compatible, but less tested.',
|
||||
name: 'MEmu Play',
|
||||
link: 'https://www.memuplay.com/',
|
||||
note: 'Fully compatible, but less thoroughly tested.',
|
||||
},
|
||||
]);
|
||||
|
||||
@@ -55,22 +51,22 @@ const partiallySupport = shuffleArray([
|
||||
{
|
||||
name: 'MuMu Emulator 6',
|
||||
link: 'https://mumu.163.com/update/win/',
|
||||
note: 'Support has been dropped since MAA v5.1.0 and NetEase has stopped maintaining it on 15-08-2023.\n\n- No longer support auto-detect connection, need to use generic connection configuration and manually configure adb path and connection address.\n- Need to run `Forced Replacement of ADB` in `Settings` - `Connection` to use efficient touch modes such as Minitouch, MaaTouch.\n- You need to run MAA with administrator privileges to use the "Exit Emulator When Done" function.\n- MuMu 6 default resolution is not supported, you need to change it to `1280x720`, `1920x1080` and other 16:9 ratio.\n- MuMu 6 multi-open uses the same adb port, so it can\'t support multi-open MuMu 6.',
|
||||
note: 'Support has been dropped since MAA v5.1.0, and NetEase stopped maintaining it on August 15, 2023.\n\n- No longer supports automatic connection detection. You need to use general connection configuration and manually configure ADB path and connection address.\n- You need to run `Force Replace ADB` in `Settings` - `Connection Settings` to use efficient touch modes like Minitouch and MaaTouch.\n- You need to run MAA with administrator privileges to use the "Exit Emulator When Done" function.\n- MuMu 6\'s unusual default resolutions are not supported. You need to change it to standard 16:9 ratios like `1280x720` or `1920x1080`.\n- MuMu 6 multi-instance uses the same ADB port for all instances, so MAA cannot support multiple MuMu 6 instances.',
|
||||
},
|
||||
{
|
||||
name: 'Windows Subsystem for Android™️',
|
||||
name: 'Windows Subsystem for Android™',
|
||||
link: 'https://learn.microsoft.com/en-us/windows/android/wsa/',
|
||||
note: 'Support has been dropped since MAA v5.2.0 and will be discontinued by Microsoft on 05-03-2025.\n\n- Requires the use of [custom connection](../details.html#Custom connection) is required.\n- WSA 2204 or later (the version number is in the `About` page of the subsystem settings), select `Common Configuration` for the connection configuration.\n- WSA 2203 or older (the version number is at the top of the subsystem setup page), for the connection configuration select `WSA Older Versions`.\n- Since this software only supports 720p or higher `16:9` resolution better, please manually drag the window size as close to the 16:9 ratio as possible. (If your monitor is 16:9, you can press `F11` to go full screen).\n- Please try to make sure that Arknights is in the foreground and no other Android apps are running in the foreground at the same time, otherwise it may cause the game to pause or the task recognition error.\n- WSA\'s screenshots often somehow capture a white screen, resulting in recognition of abnormalities, or not recommended to use.',
|
||||
note: 'Support has been dropped since MAA v5.2.0, and Microsoft will discontinue it on March 5, 2025.\n\n- Requires using [custom connection](../connection.html) method.\n- For WSA 2204 or later versions (version number can be found in subsystem settings under `About`), select `General Configuration` for connection configuration.\n- For WSA 2203 or older versions (version number appears at the top of subsystem settings page), select `WSA Older Versions` for connection configuration.\n- Since MAA only properly supports `16:9` resolutions of 720p or higher, please manually adjust the window size to be as close to 16:9 ratio as possible. (If your monitor is 16:9, you can press `F11` for fullscreen).\n- During task execution, try to ensure Arknights remains in the foreground with no other Android apps running simultaneously, otherwise the game may pause or task recognition may fail.\n- WSA sometimes inexplicably captures white screens during screenshots, causing recognition issues. Not recommended for use.',
|
||||
},
|
||||
{
|
||||
name: 'AVD',
|
||||
link: 'https://developer.android.com/studio/run/managing-avds',
|
||||
note: 'Theoretical support.\n\n- Starting from Android 10, Minitouch is no longer available when SELinux is in `Enforcing` mode, please switch to other touch modes, or switch SELinux **temporary** to `Permissive` mode.\n- AVD is made for debugging, it is more recommended to use other emulators designed for gaming.',
|
||||
note: 'Theoretically supported.\n\n- Starting from Android 10, Minitouch is no longer available when SELinux is in `Enforcing` mode. Please switch to other touch modes, or **temporarily** switch SELinux to `Permissive` mode.\n- AVD is designed for development debugging, not gaming. Other emulators specifically designed for gaming are recommended instead.',
|
||||
},
|
||||
{
|
||||
name: 'Google Play Games (Developer)',
|
||||
link: 'https://developer.android.com/games/playgames/emulator?hl=zh-cn',
|
||||
note: 'Theoretical support. Hyper-V must be enabled, and a Google account must be logged in.\n\n- You need to use [custom connection](../connection.html) to connect, the ADB port is `6520`.\n- Due to the SELinux policy of Android 10 and later versions, Minitouch cannot work properly, please switch to other touch modes.\n- The first connection after each emulator startup will fail, you need to check `Attempt to kill and restart ADB process after connection failure`.',
|
||||
link: 'https://developer.android.com/games/playgames/emulator',
|
||||
note: 'Theoretically supported. Requires Hyper-V to be enabled and a Google account to be logged in.\n\n- You need to use [custom connection](../connection.html) to connect, with ADB port `6520`.\n- Due to SELinux policies in Android 10 and later, Minitouch cannot work properly. Please switch to other touch modes.\n- The first connection attempt after each emulator startup will fail. Enable `Attempt to kill and restart ADB process after connection failure`.',
|
||||
},
|
||||
]);
|
||||
|
||||
@@ -78,7 +74,7 @@ const notSupport = shuffleArray([
|
||||
{
|
||||
name: 'Google Play Games',
|
||||
link: 'https://play.google.com/googleplaygames',
|
||||
note: 'Not supported, [Consumer Client](https://developer.android.com/games/playgames/pg-emulator#installing-game-consumer) cannot use ADB.',
|
||||
note: 'Not supported. The [Consumer Client](https://developer.android.com/games/playgames/emulator#installing-game-consumer) cannot connect via ADB.',
|
||||
},
|
||||
]);
|
||||
|
||||
|
||||
Reference in New Issue
Block a user