# RedPot user handbook

2026-10-30

Check About RedPot first. Public v0.1.0 and the updated preview have different requirements and controls.

https://redpot.top/handbook

## 01. Installation and first launch

Check your version and Mac, then install RedPot and prepare your first Android system.

> Applies to RedPot 0.3.3.11 · Apple Silicon · macOS 26 or later.

### Check the applicable version

This handbook covers the compact control center in RedPot 0.3.3.11. Check RedPot → About RedPot first.

| Item | Current public download |
| --- | --- |
| Version | 0.3.3.11 · build 2026110118 |
| Processor | Apple Silicon (ARM64) |
| Minimum system | macOS 26 |
| System image | Not bundled; import separately |

Free has no time limit. Purchase Pro on the website and activate it with a serial. Allow disk space for images, device data and growth.

- [Installer details and SHA-256](https://redpot.top/news/public-download)

### Install RedPot

1. Download the DMG using Download for Mac on the website. Check its filename and selected version. Avoid repackaged installers from unknown sources.
2. Open the DMG and copy RedPot.app to Applications. When replacing an existing installation, shut down its devices normally and quit RedPot first.
3. Open RedPot from Applications and read the license agreement. Accept it to continue to the control center.
4. Check the version in About RedPot. Once the application has been copied, eject the DMG.

> Tip: If macOS blocks the application, record the exact message and check the official source, version and checksum. Do not disable system security checks or delete device data as a troubleshooting shortcut.

### Prepare the first system

A package with a bundled system prepares its local image on first use. This unpacks, checks and copies files; it does not download Android. A package without an image requires a compatible local system to be imported.

1. Wait for completion and read the result or specific error. Keep source files available and leave enough disk space.
2. If preparation fails, retry from the prompt, or enter the control center and use Prepare built-in system again or Import another image in the creation dialog. Built-in preparation is available only when the package includes a system.
3. Check that the system is available. Only a system that passes validation can be used to create a device.

- [Import a local image step by step](https://redpot.top/handbook/images#import)

### Complete the first session

1. Click New device or press ⌘N, select a usable system and an appropriate configuration. Start with Light or Standard.
2. Click Create & start and wait until Android is interactive. A running process, a visible frame and a fully booted Android system are different milestones.
3. Complete Android’s own first-run setup, then try Settings, text input and a known compatible APK.
4. When finished, choose Power off from the device row’s More actions menu and wait for Off. Closing the display window only dismisses that window.

- [Full device creation guide](https://redpot.top/handbook/first-device)
- [States and everyday controls](https://redpot.top/handbook/devices)

### Before and after an update

- Shut down devices and back up important data before updating. Application files and device data are stored separately.
- After updating, check the version, device list, images and license before starting your usual device.
- If the device list becomes empty, check the active data location and product version before deleting old folders or recreating data under the same name.
- RedPot Park is the upstream validation product and uses different data/preferences from the distributed RedPot app. They are separate installations.

## 02. Create your first Android device

Choose a system, resources and display, then verify the resulting device.

> Applies to RedPot 0.3.3.11 · Apple Silicon · macOS 26 or later.

### Before you begin

- Have a validated local image and a Mac that meets the image and client requirements.
- Leave host storage and memory headroom. Free allows one running device; shut down a background device first if needed.
- Choose a recognizable name, such as Android for study or App testing. Names are 1–64 characters, cannot start with a dot, and cannot contain path separators or control characters.

### Create step by step

1. Click New device in the control center, or choose File → New Android (⌘N).
2. Enter a name and select an available System image. Read the reason for a disabled option; use Import another image if none is available.
3. Choose Light, Standard or Custom. Custom accepts CPU count, RAM in MB and internal storage; 1024 MB = 1 GB.
4. Choose the display preset separately. Custom screen requires width, height and DPI. Resource and display presets are independent.
5. For a first device, leave extra kernel arguments under More settings empty. Read the validation message and click Create & start.
6. A successful creation opens the device window and attempts startup. Check its state in the device list; successful creation does not mean Android has finished booting.

### Preset reference

| Preset | CPU | RAM | Internal storage |
| --- | --- | --- | --- |
| Light configuration | 2 CPUs | 2048 MB | 32 GB |
| Standard configuration | 4 CPUs | 4096 MB | 64 GB |
| Custom configuration | Limited by license and host | Enter MB | 16 / 32 / 64 / 128 / 256 GB |

| Display preset | Resolution (pixels) |
| --- | --- |
| Light phone | 720 × 1600 |
| Phone | 1080 × 2400 |
| Tablet | 1600 × 2560 |

These are the current preview presets. Use the values displayed by your installed build. Higher resolution increases rendering work, and more allocated resources do not always improve performance. Test your real workload.

### Disabled creation or a creation failure

| Symptom | What to do |
| --- | --- |
| System unavailable | Read missing-file, graphics or OS requirements and resolve them first. |
| Invalid name or number | Correct the name; use positive integer CPU/RAM values, with RAM in MB. |
| Free limit exceeded | Shut down another device or reduce CPU/RAM within the allowance. |
| Creation failed | Keep the entered configuration, record the error and check disk space and paths. Avoid repeated submissions. |
| Device exists but startup failed | Read the device-row error and retry startup instead of creating duplicate devices. |

### After the first boot

Check touch, keyboard input, network access and a simple app separately. Back up accounts and files you need to keep. Renaming does not change the data path. To use a different system, create another device instead of overwriting the existing disk.

- [Keyboard, mouse and clipboard](https://redpot.top/handbook/input)
- [Change device configuration](https://redpot.top/handbook/configuration)

## 03. Control center and device management

Understand device states, start and pause safely, shut down and recover from stale state.

> Applies to RedPot 0.3.3.11 · Apple Silicon · macOS 26 or later.

### The compact control center

The control center uses a single compact layout with Devices, Images, APK, Help and Settings tabs. Search devices by name or ID and filter All, Running, Starting, Paused, Off or Attention.

- Double-click a device row to open its display. The gear opens settings; More actions contains pause, screenshot, power off, force stop and delete.
- For an unavailable action, inspect its hint and current state. An in-progress operation cannot be submitted again.
- Recent activity and installation details describe the current session. They are not a permanent audit history; record needed information before quitting.

### Add and find devices

Create a device with New device or ⌘N. Stored device count differs from the number permitted to run concurrently. Free can keep devices for different purposes and run them in turn. If a device seems missing, clear the name/state filters, then check the storage location in Settings.

- [Complete creation workflow](https://redpot.top/handbook/first-device#create)

### States and primary actions

| State | Meaning | Next action |
| --- | --- | --- |
| Off / startup failed | No normal running session | Start & open; read any failure first |
| Starting / restoring | System is preparing or booting | Wait for a state change; avoid repeated starts |
| Running | Running session; display can be opened | Open window or use available actions |
| Paused | Execution paused; resources remain allocated | Resume & open |
| Attention / inconsistent state | Saved state and process differ, or a failure occurred | Follow the specific message; do not assume healthy operation |

A live process does not prove Android is responsive. Display, ADB and installation may become ready later. Boot time depends on the image, first-run initialization and host resources.

### Window closing, pause and shutdown

| Action | Effect |
| --- | --- |
| Close Android window | Dismisses the display; the device keeps running and retains its concurrent slot. |
| Close control center or last window | RedPot can remain running. Reopen via Window → Control Center (⌘0). |
| Pause / resume | Pauses execution and can resume; memory and a concurrent slot remain allocated. |
| Lock screen / tap power | Locks or wakes Android; it does not shut down the VM. |
| Power off | Asks Android to save data and shut down; wait for Off. |
| Force stop | Terminates an unresponsive device; unsaved data may be lost. |

1. Save work inside Android, then locate its device in the control center.
2. Choose More actions → Power off, check the name and confirm. Default settings show a shutdown confirmation.
3. Wait for Off before starting another device, changing hardware or backing up. Consider Force stop only if normal shutdown does not respond.

### Reset state and delete

Reset State is offered when the process has exited but its saved running state is stale. It removes stale runtime records while preserving the disk. It is neither an Android factory reset nor a repair of corrupted guest files.

> Note: Delete removes the device and its disk data irreversibly. Shut down normally and export or back up important data first. Power off is sufficient to free a concurrent slot.

- [Checks before backup](https://redpot.top/handbook/storage#backup)
- [Troubleshoot startup and black screens](https://redpot.top/handbook/troubleshooting#black-screen)

## 04. CPU, display and device settings

Tune a device for its task and understand when each change takes effect.

> Applies to RedPot 0.3.3.11 · Apple Silicon · macOS 26 or later.

### Open settings and check editability

1. Click the device-row gear or Device settings on the Android window’s right rail. Search for a setting by name.
2. Shut down normally before editing hardware. Running, paused, hibernated or inconsistent devices have locked hardware settings.
3. If hibernated, resume and then shut down normally. Do not remove restore files to bypass the restriction.
4. Save changes; the next start uses the new configuration. Merely opening a window does not apply unsaved changes.

### Name and general information

General information shows the name and data location. A name must be 1–64 characters, cannot start with a dot, and cannot contain path separators or control characters. Renaming changes the display name without moving the data folder. Reveal in Finder shows its actual location.

### Allocate CPU and RAM

| Updated allowance | Free | Pro |
| --- | --- | --- |
| Running devices | 1 | 5 |
| CPU ceiling per device | 4 CPUs | 32 CPUs |
| RAM ceiling per device | 8 GB | 128 GB |

Ceilings are neither recommended allocations nor a guarantee of host resources. RAM is entered as a positive integer in MB and is limited by physical memory and the license. Leave headroom for macOS and other apps.

1. Run your actual workload at the default settings and check whether only initial boot or installation is slow.
2. Check Memory Pressure and Swap Used in macOS Activity Monitor. If pressure stays high, run fewer devices or reduce each allocation.
3. Change one parameter at a time and repeat the same task. Additional RAM does not automatically fix app compatibility or graphics errors.

### Resolution, DPI and window size

- Width and height define Android’s pixel resolution. DPI affects interface scaling; diagonal inches describe the configured screen size. Begin with a preset for easier troubleshooting.
- Resizing the Mac window scales the display area; it does not change Android resolution. To change guest resolution, shut down and edit Display.
- Use the right-rail rotation button to rotate the device. Rotation is separate from resolution editing, and an app may still lock its orientation.

### Internal storage and SD card

Internal storage can grow but cannot shrink. Growth happens on the next start and preserves apps/files. An SD card can be connected or disconnected without discarding its contents, but changing its capacity reformats it on the next start.

> Note: Do not treat an SD capacity change as lossless expansion. Read the erase-data confirmation before saving and back up the card first.

- [Expand internal storage](https://redpot.top/handbook/storage#expand)
- [Connect and resize an SD card](https://redpot.top/handbook/storage#sd-card)

### Application settings and reset

Control-center Settings or RedPot → Settings (⌘,) includes the license, shutdown confirmation, active storage location, bundled runtime, version and agreement. The engine path is read-only; the distributed app uses its bundled runtime first. There is no data-folder migration wizard in this interface.

Reset interface and agreement restores interface/confirmation preferences and reopens the agreement. It preserves devices, images, data, storage location and running devices. It does not erase Android. The client follows macOS language; the website language switch affects only the website.

## 05. Display, keyboard and interaction

Use touch interaction, text input, copy/paste, screenshots and Android buttons.

> Applies to RedPot 0.3.3.11 · Apple Silicon · macOS 26 or later.

### Mouse and trackpad

| Gesture | Android action |
| --- | --- |
| Click display | Tap the position and focus the display for input. |
| Press and drag | Drag or swipe; a long press depends on the app’s handling of the held touch. |
| Wheel / trackpad scrolling | Simulate a swipe at the pointer; place it over scrollable content first. |
| Hold ⌘ and drag | Simulate a pinch gesture if the target app supports it. |

If interaction does not respond, check for pause/lock state and click inside the display. Read hints for disabled physical buttons; an unavailable input channel is not proof of an app hang.

### Keyboard and composed text

1. Open an editable field in Android and click until its cursor appears.
2. Type with the Mac keyboard. With an input method, finish choosing the candidate so the committed text is sent to Android.
3. Use arrow keys, Return, Delete and Tab for editing/navigation. If an app’s custom field fails, test a normal text field in Android Settings first.

Text input depends on the device input channel and Android-side support. Keyboard entry is not a full game key-mapping system; app-specific shortcuts and protected fields may behave differently.

### Copy and paste text

| Shortcut / control | Action |
| --- | --- |
| ⌘V / Paste into Android | Paste Mac clipboard text into the focused Android field. |
| ⌘C | Copy selected Android text to the Mac clipboard. |
| ⌘X | Cut selected text in an editable field. |
| ⌘A | Select all in the current supported field. |
| ⌘⇧C | Read Android clipboard text into the Mac, useful after copying inside Android. |

These operations transfer text, not images or arbitrary files. Focus the display and ensure the device is started and not paused. If paste is empty, copy a short plain-text sample on the Mac and retry. Preserve any failure message.

### Navigation and physical buttons

- The bottom Back, Home and Recents buttons return to the previous screen, open Android’s home screen and switch apps.
- The right rail provides lock, volume, screenshot, rotation, APK installation, paste, USB cast and settings. Availability depends on device state.
- Android → Keys includes actions such as holding Power. These control Android; use Power off to shut down the VM.

### Take and save a screenshot

1. Select the intended Android window and click Screenshot, or choose Screenshot from that device’s More actions menu.
2. On success, the PNG opens in the Mac’s default image viewer. It initially resides in a temporary directory.
3. For a lasting copy or a support report, save/export it to your own folder. Redact account details, QR codes and other private information before sharing.

> Tip: If screenshot capture fails, do not treat an old frame as a fresh result. Record the message and check that the current device supports capture.

### USB casting to a physical Android phone

Development builds with this feature can stream a RedPot device to a physical Android receiver and return touch input. This does not import the phone’s operating system into RedPot or provide generic USB passthrough. Compatible hardware, receiver and build are required.

1. Start the RedPot device and open USB Cast. If Export Android Receiver APK is available, export it and install it on your physical phone.
2. Connect the phone with a data-capable USB cable and respond to the receiver permissions shown on the phone. Refresh and select it in the dialog.
3. Enable streaming, select bitrate/FPS and click Apply. Inspect link status and errors. The selected FPS is a target, not a guarantee.
4. When finished, disable streaming and apply. If export is unavailable or no phone is detected, record your build and phone model for support.

## 06. Prepare and import system images

Distinguish systems from apps, validate image completeness and import into the local library.

> Applies to RedPot 0.3.3.11 · Apple Silicon · macOS 26 or later.

### Choose the right source

A system image creates an Android device; an APK installs an app inside a running device. Do not send APKs to the system importer or treat a firmware ZIP as an Android application.

| Source form | Current preview behavior |
| --- | --- |
| RedPot / Redroid directory | Checks required files such as kernel and img.raw and runtime requirements. |
| Prepared Google image | Checks Image, initrd.cpio, system.img, vendor.img, userdata.img, metadata.img, cache.img and compatibility requirements. |
| Android Studio system-image directory | Recognizes supported images and prepares the kernel, ramdisk, writable disks and compatibility fixes in a private copy. |
| Standalone .img / img.raw | Requires recognition and a compatible ARM64 kernel pairing. A filename extension does not guarantee compatibility. |

> Tip: Obtain images from a source you are entitled to use and follow its license. Recognizing a file does not mean every OEM ROM, Google service or application has been verified.

### Find, select, check and import

1. Click Import image in the control center or Import another image in the creation dialog.
2. Use Search this Mac to inspect candidates from the image library, Android SDK, Downloads and other searched locations. Choose Folder if the search is incomplete.
3. Select an image folder for subdirectory scanning. The current preview’s picker also accepts a standalone .img. A folder or .img can be dropped into the importer’s drop area.
4. Select a candidate, read its recognition result, missing files and compatibility messages, then click Check and import.
5. Wait for completion. Files are validated and written into an independent local image library. Supported Google images receive compatibility fixes on the copy, leaving originals unchanged.
6. Return to Images or the creation dialog and verify availability before creating a device.

This is a local import workflow, not an image downloader. The interface reports stages such as checking and importing. The absence of a percentage does not imply a hang, and filenames alone do not prove success.

### Library, original files and device data

After a successful import, the library no longer depends on the original source folder. Created devices have their own writable data. Moving the original download is not the same as deleting a device, but do not manually remove files from the active library or files referenced by devices.

A system can create separate devices for different purposes. Create a separate device to try another system; importing an image does not automatically upgrade an existing device.

### When validation fails

1. Read the full error: missing files, unreadable source, missing kernel, or unmet host/graphics requirements.
2. Check the original source for complete extraction, the correct folder and an architecture suitable for the Mac. A completed archive download does not ensure a complete prepared system.
3. Check destination free space and folder access, then revalidate. Do not rename unrelated files or fabricate files to bypass checks.
4. If it still fails, report the source, OS version, file list and exact error. Do not upload an entire large image or a disk containing private data.

### Download an image from the website

Open Baidu Netdisk from the resource page with access code hmkz, then download Google - Android 17.zip from 系统镜像. Extract it and select the complete folder in RedPot → System Images → Import Image. Refer to the included instructions and checksum file.

- [Browse system images](https://redpot.top/resources#system-images)
- [Continue troubleshooting](https://redpot.top/handbook/troubleshooting)

## 07. APK installation and app management

Install from local files, direct links or public sources and verify each result.

> Applies to RedPot 0.3.3.11 · Apple Silicon · macOS 26 or later.

### Prepare the device and package

Start the target and wait for Android and its installation channel to become ready. Paused, stopping or inconsistent devices are not valid normal targets. If an installation is busy, wait for the current batch.

- Local input supports .apk and .zip containing the required split APKs for an app. The local limit is 1000 MiB; the combined extracted APK size is also limited.
- Do not treat arbitrary ZIPs, system firmware or unrelated apps as a split-install package. Direct support for .xapk and .apks is not promised by this input.
- App execution still depends on Android version, CPU architecture, graphics, Google services and app-specific requirements. A successful installation verifies installation only.

### Install local files

1. Identify the target device. Drop one or more APKs onto its Android display to queue installation there.
2. Alternatively, click Install APK on the Android rail and choose files. Dropping onto the control center opens target selection.
3. Importing in APK → Local registers files in the local list. Then select an entry and target to install. Registration is not installation.
4. Read the device-row result and open Install details to check every file. Finally locate and launch the app inside Android.

### Direct links and public sources

1. Open APK → Remote. For a single package, use APK link and provide a name and a public http(s) .apk URL.
2. For a catalog, use Add source, enter its name and public index.json URL, then click Verify & Add.
3. After validation, search names/package IDs and filter by source. Check updates refreshes source indexes; it does not automatically update apps inside Android.
4. Download the remote entry locally, then select a device to install. Downloading, downloaded and installed are different stages.

The current source input is for anonymously accessible public repositories; it does not store login cookies or tokens. Links returning login pages, HTML errors or invalid APK content fail. Removing a source removes its registration while retaining downloaded packages.

### Installation details and cancellation

| State / action | Meaning |
| --- | --- |
| Queued | This package has not started. |
| Downloading | Fetching a remote file; no fabricated percentage. |
| Installing | The current app is being installed. |
| Done / failed / skipped | Read each receipt or reason instead of assuming one summary covers every file. |
| Cancel remaining | Skips not-yet-started apps; the current installation finishes. |
| Clear finished records | Clears finished records without canceling unfinished tasks. |

Closing installation details does not cancel the queue. Records last until the app exits; save needed error text before quitting.

### Handle a failure

| Message or symptom | Suggested action |
| --- | --- |
| Target not ready / ADB unavailable | Resume/start the device, wait for Android boot, then inspect the current port in ADB connection. |
| Incompatible ABI or SDK | Check supported APK architectures and minimum Android version; choose a matching package/system. |
| Signature mismatch / downgrade rejected | Prefer a newer release signed by the same developer. Export data before uninstalling the old app if necessary; uninstalling may erase data. |
| Insufficient storage | Check both Android internal storage and the Mac’s physical disk. Back up before expanding internal storage if needed. |
| Installed but will not launch | Record the app version, image, steps and screen state; repeated installation is not a compatibility diagnosis. |

### Updates, uninstalling and data

For updates, prefer packages from the same source and signing identity, and inspect installation details. Uninstall apps through Android’s app settings. Removing a package from the Mac’s APK list or disk does not uninstall it from a device. Uninstalling, clearing app storage and deleting the whole device are separate data operations.

- [Inspect the current ADB connection](https://redpot.top/handbook/network#adb)
- [Protect and manage data](https://redpot.top/handbook/storage)

## 08. Network and ADB connections

Diagnose connectivity and locate the correct local ADB endpoint.

> Applies to RedPot 0.3.3.11 · Apple Silicon · macOS 26 or later.

### Identify the failing network layer

Mac connectivity does not guarantee every Android app can reach the same service. Test the Mac browser, an Android browser and the affected app separately, and note where access fails.

1. Verify Mac connectivity, then test a known reachable address inside Android.
2. If one app fails, inspect its account, service availability, permissions and version before rebuilding the device.
3. If all Android access fails, record device state, image, network messages and the Mac’s VPN/proxy environment, then retry after a normal shutdown.

> Tip: The Network settings page displays saved configuration. Read-only configuration is not a live connectivity check.

### Connect ADB to this device

Normal startup and GUI APK installation do not require manually entered ADB commands. The following is for debugging or guided diagnostics and assumes adb is available in your terminal.

1. Start the target and wait for Android. Open Device settings → Connections → ADB connection.
2. Read the displayed 127.0.0.1 endpoint and port, then copy the command. If a port is occupied, a later start may use another one.
3. Paste and run the full adb connect command supplied by that page in the Mac terminal. Do not reuse another device’s port or one from an old screenshot.
4. Run adb devices and inspect the target’s state. Explicitly select that endpoint for later commands to avoid acting on the wrong device.

```text
adb devices
```

This handbook does not prescribe a fixed port. Use the one currently shown for the device. The loopback address belongs to this Mac; it is not a public endpoint for another computer or phone.

### Common ADB states

| State | Check |
| --- | --- |
| connection refused / cannot connect | Ensure the device is not off or paused, reread its current port and wait for Android boot. |
| offline | Wait for readiness and check for a stale port; disconnect that target and reconnect with the current command if needed. |
| unauthorized | Inspect Android for a debugging authorization prompt and verify the target before responding. |
| more than one device | Specify the current device endpoint explicitly rather than issuing untargeted commands. |
| adb not found | The terminal tool is missing or not on the search path; it does not prove the RedPot device is damaged. |

### File transfer boundaries

The documented drag-and-drop input on the Android display installs APKs. Arbitrary documents, photos or directories should not be assumed to become a shared folder. Use an Android app’s own import/export workflow for normal files. Advanced users can use connected ADB after verifying the device and destination path.

- [App installation workflow](https://redpot.top/handbook/apps)
- [Prepare a reproducible report](https://redpot.top/handbook/support)

## 09. Storage, SD cards and data protection

Understand capacity versus usage and protect data before resizing, backing up or deleting.

> Applies to RedPot 0.3.3.11 · Apple Silicon · macOS 26 or later.

### Locate the active data folder

The default data directory is ~/Library/Application Support/RedPot. Existing configuration can affect the actual location, so use the path shown in control-center Settings and Reveal in Finder. Individual device settings also show their data location.

The application, image library, device disks and temporary installation files are distinct. Replacing RedPot.app does not itself remove Android data; copying only the app does not back up devices. The current interface has no one-click whole-library migration.

### Virtual capacity and physical usage

A 64 GB internal-storage setting describes logical Android capacity, not a guarantee of a fixed physical footprint on the Mac. Images, writable data, SD cards and backups consume space separately. App installations and file writes can increase host usage.

- Check both Android internal storage and free space on the Mac’s physical disk. Either can cause installation or write failures.
- Expanding a virtual disk does not create free physical space on the Mac. It is not a remedy for a full host disk.
- Before cleaning up, distinguish downloaded copies/installers from active device data. Avoid manually deleting disks from an active data folder.

### Expand internal storage

1. Back up important content and shut down normally. Ensure the device is not paused, hibernated or in an inconsistent state.
2. Open Device settings → Hardware → Internal storage and choose a larger available capacity.
3. Save and restart. Growth runs on the next start and is designed to preserve existing apps/files.
4. Verify capacity and files in Android storage settings. If an error appears, record it rather than repeatedly modifying disk files.

> Tip: Internal storage can grow, but cannot shrink. Keep a backup of critical data in case of disk failure or interruption.

### Connect, disconnect and resize an SD card

1. Shut down, then open Device settings → Hardware → SD card. Enable Connect SD card and select a capacity.
2. Save and start, then check the card inside Android. The guest may show its own initialization prompt.
3. To stop using it temporarily, shut down, disable connection and save. Contents are retained and can be reused by reconnecting at the same capacity.
4. To change capacity, export important files first. Saving a new capacity asks for reformat confirmation; the next start erases the card.

> Note: Changing SD capacity erases data; expanding internal storage preserves it. Check the settings page and device name before confirming.

### Make a consistent backup

1. Export the most important files from Android and finish active app operations.
2. Shut down every device normally and ensure none is running or paused. Resume hibernated devices and shut them down normally.
3. Record the RedPot version, active data path and system images, then quit the client.
4. Use your backup tool to copy the complete data directory and any referenced external files, preserving structure, permissions and timestamps. Ensure the destination has enough space.
5. Verify that the backup is readable and retain the original. Restoring to another path or Mac may involve path/runtime differences; retain a copy and obtain specific guidance first.

This is advice for a powered-off data backup, not a built-in export/import wizard or a memory snapshot. Current hardware-accelerated devices do not support memory snapshots/hibernation; Pro does not automatically enable unavailable template-fork features. Certificates are machine-bound, so copying data does not transfer a license.

### Before deletion or uninstalling

Deleting a device irreversibly removes its disk. Removing the RedPot application and cleaning its separate data directory are different steps. Keep a folder if its purpose is unclear. Reinstallation does not replace a backup, and erasing all data should not be the first general troubleshooting step.

- [Reset state versus delete](https://redpot.top/handbook/devices#recovery)
- [Get guidance on recovery](https://redpot.top/handbook/support)

## 10. Account, purchase and client activation

From email sign-in and order verification to machine binding: distinguish serial numbers and certificate files.

> Applies to current website services. Certificate import requires the updated client. Check the license page for public sales availability.

### Email sign-in and orders

1. Open Account & licenses, enter your purchase email and complete the security check before requesting a code. No email is sent without verification.
2. Enter the received 6-digit code and select Sign in / register. Codes last 10 minutes and resending requires a 60-second wait. Use the most recent valid code.
3. After signing in, view your own orders/licenses. Signing in with another email does not automatically merge that account’s purchase history.

Free client use does not require buying Pro. Website sign-in provides orders, licenses and support. Offline certificate activation is separate from entering email credentials in the client.

### Free, Pro, monthly and annual subscriptions

| Item | Free | Pro |
| --- | --- | --- |
| Duration | No trial time limit | Monthly or annual subscription term |
| Concurrency / per-device limits | 1 device / 4 CPUs / 8 GB | 5 devices / 32 CPUs / 128 GB |
| Binding | No paid certificate required | Both include 3 Macs, each with its own certificate |

Monthly subscriptions cost ¥9.9 at the discount price or ¥19.9 at the regular price; annual subscriptions cost ¥99 discounted or ¥199 regular. Both include 3 Macs. Availability, the current price and payment methods are determined by the license page and order confirmation.

Monthly and annual terms are 1 and 12 calendar months from confirmed payment, with month-end dates clamped to the last day of the target month. Both include the same Pro resources; all Macs share the order expiry. Existing orders retain their purchased price, term and seat count.

### Purchase and payment verification

1. Sign in, select an available plan and verify the price, term and recipient before creating an order.
2. Complete payment using the Alipay or WeChat flow offered by the order. An expired code requires a valid new order; do not pay an unfamiliar recipient.
3. Return to the site and check for server-confirmed Paid status. Closing the cashier, scanning or seeing a QR code does not confirm receipt.
4. If the payment app shows success but the site is pending, retain the order number/time and refresh status. Avoid immediately paying again; contact support if needed.

- [Open account and licenses](https://redpot.top/license)

### Serial, receipt and certificate

| Item | Purpose |
| --- | --- |
| RP-… serial number | Enter it in the updated client to activate, or open the client from the website for automatic binding. |
| .redpot-order receipt | Purchase receipt, not a device license certificate. |
| Machine code | Read automatically by the client for binding. No copying or website input is required. |
| .redpot-license certificate | A signed license obtained and verified automatically by the client. Existing files can also be imported offline. |

> Tip: Keep serials/certificates private and out of public screenshots, posts and feedback text. Renaming or editing a file does not transfer its authorization.

### Open the client from the website and bind automatically

1. Install the current official RedPot 0.3.3.11 release on the Mac that will use Pro.
2. Choose Activate in RedPot in your website order. You can also enter a serial in the I have a serial number tab and choose the same action.
3. Allow the browser to open RedPot. The client identifies this Mac, requests the license and verifies its certificate, then shows Binding successful. Pro is active.
4. New subscriptions support 3 Macs. Reactivating the same Mac does not use another seat. Links expire after 5 minutes; create a new link if expired, or copy the serial into the client if opening fails.

### Enter a serial in the client

1. Open RedPot → License and paste the complete RP-… serial.
2. Choose Activate license with an internet connection. No machine ID entry is needed.
3. After binding, signature and validity checks and saving, the client confirms success. Follow the error message if activation fails; the existing license is preserved.
4. Existing .redpot-license files can be verified and activated through Import offline certificate without an internet connection.

| Validation failure | Action |
| --- | --- |
| Wrong file or invalid content | Check the complete serial. For offline import, use the original .redpot-license rather than an order receipt. |
| Machine mismatch | Enter the serial on this Mac to activate; do not import another Mac’s certificate. |
| Invalid signature | Download the original file from the site; report persistent errors. |
| Expired / time issue | Check certificate validity and the Mac’s correct date; do not backdate the clock. |

### Renewal, expiry, removal and moving Macs

- Renew by purchasing a new monthly or annual subscription at the then-current website price, without automatic billing. Its term starts at payment and does not stack onto the old certificate; issue from the new order and verify its dates.
- Expiry/removal does not delete devices/data or automatically end running processes. Future starts are checked against Free limits.
- Remove local license removes local activation; it does not unbind the website machine or transfer a seat.
- The current offline-certificate flow has no self-service machine unbinding, online seat release or instant remote revocation. Contact support for a move or a changed machine code.
- Certificate verification can be offline; purchase, website issuance and redownload require connectivity. Keep the Mac clock accurate.

## 11. Troubleshooting

Identify the failing stage, then resolve it with the least disruption.

> Applies to RedPot 0.3.3.11 · Apple Silicon · macOS 26 or later.

### Record the symptom first

Record RedPot/macOS versions, Mac chip/RAM, image, device resources, the full error and time. Classify the failure as app launch, image import, device boot, input, network, installation or licensing. Change one condition at a time and retain before/after results.

### The application will not open

1. The current public release requires Apple Silicon and macOS 26 or later.
2. Check that the app was copied to Applications and that you are not opening a different copy from an old DMG.
3. Record the full macOS message, verify the official package/checksum and redownload the same version if necessary.
4. If it still fails, report the version and message. Do not begin by deleting Android data.

### Startup failure, endless boot or black display

1. Read the device state: running, paused, attention or failed. Resume if paused; tap Power to wake a locked screen.
2. Check image validation, CPU/RAM allowance and host memory/storage headroom.
3. Android may still initialize after the process starts. Record duration and state changes rather than relying on a fixed startup time.
4. If the display is stale but the device responds, close and reopen that display window. If the whole device is unresponsive, try normal shutdown.
5. Use Force stop only if normal shutdown fails, accepting possible unsaved-data loss. If the process has exited but records are stale, use Reset State when offered.
6. Retain errors, image source and steps. Do not overwrite disk.raw or write another system into the existing device.

### Limit reached after closing a window

Closing a window, hiding the app or pausing a device does not free its concurrent slot. Return to the control center, find background devices with Running/Paused filters, shut down normally and confirm Off. If the limit persists, check activation/expiry/removal and whether the requested CPU/RAM exceeds the current allowance.

### Input, paste or rotation fails

1. Focus the intended window/field, ensure the device is not paused and check that Android is unlocked.
2. Test short text in a normal Android field before the affected app to separate system input from app restrictions.
3. Paste handles text. An empty clipboard or one containing only images/files will not yield the expected text.
4. For rotation/button errors, retain hints and errors. An app can lock orientation; a changed window shape alone does not prove guest rotation.

- [Input operations and prerequisites](https://redpot.top/handbook/input)

### App download, installation or execution fails

For download failure, check that the URL supplies a public installer. For installation failure, inspect each result in Install details. For launch failure after installation, check architecture, Android version, graphics and service dependencies. These are distinct failure stages.

- [Installation error reference](https://redpot.top/handbook/apps#result)
- [Network and ADB diagnosis](https://redpot.top/handbook/network)

### Payment or license has not taken effect

1. Verify the purchasing email and a Paid order status on the website. Scanning or opening a cashier is not a completed payment.
2. Enter the serial in RedPot → License on the target Mac, or choose Activate in RedPot on the website. The client identifies this Mac automatically.
3. In the client, select the file, wait for verification, click Activate license and check the resulting tier.
4. Handle machine mismatch, expiry or signature errors as indicated, without editing the certificate.

- [Complete purchase and activation guide](https://redpot.top/handbook/activation)

### A device or its files appear missing

- Clear search/state filters and check the active data path in control-center Settings.
- Verify you opened RedPot, not RedPot Park or another installation. Renaming does not move its data.
- A disconnected SD retains contents and can be reconnected at the same capacity. Reconnection cannot undo formatting caused by a capacity change.
- Retain existing folders/backups and request recovery guidance. Do not create replacement files where original data may remain.

### Submit an actionable report

If these checks do not resolve the issue, report minimal reproduction steps, expected/actual results and the full error through website support. Include actions already tried, especially force stops, SD capacity changes or version updates.

- [Ready-to-fill feedback template](https://redpot.top/handbook/support#template)
- [Open support](https://redpot.top/support)

## 12. Get support and send feedback

Describe an issue, add updates and follow replies in your account.

> Applies to current website services. Certificate import requires the updated client. Check the license page for public sales availability.

### Before submitting

- Read the relevant chapter and retain the full error and minimal reproduction steps.
- Record the Mac chip/RAM, macOS/RedPot versions, image, device settings and APK version. Include only relevant information.
- Save screenshots locally as evidence. The web feedback form does not currently accept attachments; paste relevant redacted error text.

### Create a support request

1. Open Support and sign in with your website email-code account. If already signed in, check the displayed account.
2. Choose Installation & startup, Devices & performance, Apps & images, Purchases & licenses, Feature suggestion or Other.
3. Write a specific title, record versions/device in Environment, and describe steps and expected/actual results in the message.
4. Check the success message and the new entry in My feedback. After a timeout or network error, refresh the list first to avoid duplicates.

Titles are 3–100 characters, environment up to 300, and message 10–1800. An account can create up to five requests per day. Keep one issue in one request and add details as replies.

### A report template

```text
Issue title:
Mac chip / RAM:
macOS / RedPot versions:
System image / Android version:
Device CPU / RAM / storage:
App name and version (if relevant):

Steps to reproduce:
1.
2.
3.
Expected result:
Actual result and full error:
Time and frequency:
Actions already tried:
```

For long errors, include the most relevant excerpt and specify whether it occurred during creation, boot, installation or activation. Avoid repetitive log dumps.

### What to keep private

- Do not submit passwords, email codes, payment QR codes, full serials, certificates or private keys.
- For payment issues, supply the order number, time, amount and message, not banking credentials or payment passwords.
- Redact accounts, phone numbers, conversations and private paths from logs/screenshots. Requests are associated with your account to handle the issue.

### Read replies and add information

1. Sign in with the same email, open My feedback and expand the request to read its status and messages.
2. Use Refresh for new results and load more history when needed. Another email does not show this account’s requests.
3. Reply in the existing request with new results or changes. A customer reply returns the issue to an open state.

Replies are currently read on the website, without reply-email notifications or a guaranteed response time. The absence of an email does not mean no reply exists.

- [View my feedback](https://redpot.top/support#my-feedback)

## 13. Shortcuts and terminology

Find common actions quickly and distinguish similar concepts.

> Applies to RedPot 0.3.3.11 · Apple Silicon · macOS 26 or later.

### Application shortcuts

| Shortcut | Action |
| --- | --- |
| ⌘N | New Android |
| ⌘0 | Show control center |
| ⌘, | Open application settings |
| ⌘R | Start the device in the active Android window |
| ⌘⇧P | Pause/resume the active device |
| ⌘⇧H | Request shutdown of the active device |
| ⌘H | Hide RedPot |
| ⌘⌥H | Hide other applications |
| ⌘Q | Quit RedPot; save work and shut down devices normally first |

Android menu actions target the active Android window. If the target is unclear or unavailable, click the intended window first. Actions still depend on device state. ⌘ means Command, ⇧ Shift and ⌥ Option.

- [Text editing shortcuts](https://redpot.top/handbook/input#clipboard)

### Glossary

| Term | Meaning |
| --- | --- |
| Host / guest | The host is the Mac; the guest is Android running in RedPot. |
| System image | Base system files for an Android environment, not an app installer. |
| Device / instance | A separate Android environment created from a system, with its own writable data. |
| APK / split APKs | An Android package; an app may need a base package plus configuration splits. |
| Concurrency | Devices running at the same time, not all stored devices. |
| Pause / shutdown | Pause retains running resources; shutdown ends the session and frees its slot. |
| DPI | Android display density, affecting interface scaling. |
| ADB | Android debugging connection used for installation/diagnostics; use the current device endpoint. |
| Serial / certificate | A serial activates the license through the client. The client stores a signed certificate for offline verification on this Mac. |
| Snapshot / powered-off backup | A memory-state snapshot differs from copying data after shutdown. |

### Current feature boundaries

- This handbook covers the compact macOS control center in RedPot 0.3.3.11.
- System import uses local files; opening the client from the website does not mean a system is automatically downloaded.
- Hardware-accelerated devices do not offer memory snapshots/hibernation. Pro does not promise template forks, unlimited concurrency or universal app compatibility.
- Backup/recovery is not one-click migration. Copying the data directory does not transfer a machine-bound license.
- Website support currently provides account-based text requests/replies without attachments or reply-email notifications.

### Jump to a task

- [First installation](https://redpot.top/handbook/getting-started)
- [Create Android](https://redpot.top/handbook/first-device)
- [Actually shut down a device](https://redpot.top/handbook/devices#windows)
- [Change CPU and display](https://redpot.top/handbook/configuration)
- [Import a system](https://redpot.top/handbook/images#import)
- [Install an app](https://redpot.top/handbook/apps#local)
- [Back up device data](https://redpot.top/handbook/storage#backup)
- [Import a license certificate](https://redpot.top/handbook/activation#activate)
- [Troubleshoot](https://redpot.top/handbook/troubleshooting)
- [Send feedback](https://redpot.top/support)