# Install on the child's phone 1. **Install the APK and open the app.** No need to remove accounts, no setup yet. These already work: the kid launcher (opt-in on the phone), **Dọn máy** (debloat) (only needs wireless-debugging pairing; the app runs `pm disable-user` against the phone itself), and **Bố mẹ quản lý trên máy này** (the parent page on the child's phone, in preview mode: features that need more permissions are greyed out with a note saying which one). 2. **Set the parent PIN:** the pairing form (step 5) makes you set one. It protects the page on this phone and allows pairing more parent phones. 3. **Grant permissions as needed** , following the [feature and permission table](https://kidguard.asia/#permissions) : accessibility, usage access, device admin, location… 4. **Optional, strongest: Device Owner** (ways A-D below). **Only this step** needs every account removed from the child's phone first. 5. **Pair the parent's phone or browser** (home Wi-Fi or relay, see [Away from home] ). There are five ways to install; pick one. Ways A to D make KidGuard the phone's **Device Owner** (the Android role a company uses for work phones): it can lock apps and can't be removed, no root needed. Way E skips this but is weaker. **Only for Device Owner (ways A-D):** Android only lets an app become Device Owner while the phone has **no accounts**. KidGuard keeps app accounts; phone accounts must be removed first. **Phone accounts** (Google, Samsung, Xiaomi, Oppo/HeyTap…): on the child's phone open **Settings → Accounts** and remove them. Sign back in after setup: everything comes back. **Keep apps signed in** (Zalo, Facebook, Telegram…): automatic. KidGuard turns those apps off for a moment, **the phone restarts once** (about 1 minute), setup finishes, and the apps are turned back on. Way A (QR) does not need it: a new phone has no accounts yet. Ways B, C, D all do it; the on-phone setup carries on after you unlock the screen and tells you with a notification. If a phone account is there, KidGuard stops and names the account to remove. By hand (if needed): `adb shell pm disable-user --user 0 <package>`, wait 15 seconds, `adb shell sync`, `adb reboot`, wait about 30 seconds after the phone is up, set up Device Owner, then `adb shell pm enable <package>`. Which app owns which account: `adb shell dumpsys account`. A. On the phone itself Needs: Android 11+, Wi-Fi. No computer. Phone accounts (Google, Samsung…) must be removed first: KidGuard stops and says which ones. [Download the APK](https://github.com/HoangTran0410/kidguard/releases/latest/download/kidguard.apk) on the child's phone, install it and open KidGuard. Tap **Full setup without a computer (Android 11+)**. Turn on Developer options: open **About phone** and tap **Build number** 7 times. In Developer options, turn on **Wireless debugging** and allow this Wi-Fi. Back in KidGuard, tap **Show the code box in a notification**. Then in Wireless debugging tap **Pair device with pairing code**. Pull down the notification shade, tap **Enter pairing code** and type the 6 digits shown. KidGuard does the rest, then turns Wireless debugging off again. The code goes into a notification because the pairing dialog closes when you leave Settings. If the notification doesn't show, type the code in KidGuard itself. B. Scan a QR code Needs: a new or factory-reset phone with stock-like Android (Pixel, Samsung, Nokia…). Turn the child's phone on and stop at the welcome screen. Tap 6 times on an empty spot. The phone opens a QR scanner. Scan the [setup QR code](https://kidguard.asia/qr) (open it on a computer or another phone). The phone downloads KidGuard over Wi-Fi and sets it up. Open KidGuard and finish the short checklist on screen. Some skins drop the 6-tap screen (e.g. Oppo / Realme ColorOS on Android 8–9). Use [way C](https://kidguard.asia/en/guide#install-usb) there. C. Computer and USB cable Needs: a computer with Chrome or Edge, a USB cable. No adb to install. About 3 minutes. On the child's phone: remove the phone accounts (Google, Samsung, Xiaomi, Oppo…) in **Settings → Accounts**. Leave app accounts alone. Turn on Developer options: **Settings → About phone**, tap **Build number** 7 times. In Developer options, turn on **USB debugging**. Xiaomi / Redmi / POCO: also turn on **USB debugging (Security settings)** and **Install via USB**. Plug the phone into the computer and open the [installer page](https://kidguard.asia/install) in Chrome or Edge. Press the connect button and pick the phone in the dialog. On the phone tap **Allow** (tick “Always allow from this computer”). Press the install button. When it's done the page shows the address for the parent. D. Command line Needs: macOS, Linux or Windows, a USB cable. Prepare the child's phone as in [way C](https://kidguard.asia/en/guide#install-usb), steps 1–3, and plug it in. Get the source on the computer (or just the [setup.sh](https://github.com/HoangTran0410/kidguard/blob/main/scripts/setup.sh) / [setup.ps1](https://github.com/HoangTran0410/kidguard/blob/main/scripts/setup.ps1) file). Run: `git clone https://github.com/HoangTran0410/kidguard && cd kidguard scripts/setup.sh # Windows powershell -ExecutionPolicy Bypass -File scripts\setup.ps1` The script downloads adb if it is missing, and the latest KidGuard release (SHA-256 checked) if it finds no APK. Add `-y` to skip the questions. It runs 8 steps: install the app, set Device Owner, grant usage access and secure-settings access, turn on accessibility, allow background running, open the app, print the parent's address. E. Basic mode Needs: any Android 8+. No computer, accounts can stay. For old phones with no QR screen and no computer or cable. Install the APK, open KidGuard, follow the **To do** list on the screen. Turn on each item in order: device admin, accessibility, usage access, location (choose **Allow all the time**), notifications, battery. Each button opens the right system screen: turn the setting on, then press Back. **Why it is weaker:** blocked apps are closed back to the home screen instead of greyed out. Not available: family DNS, blocking app installs / USB debugging, locking airplane mode / location / clock, reboot, Tailscale. A child who boots into **Safe Mode** or turns accessibility off stops the blocking. The parent page shows a red warning and the parent app notifies. You can switch to Device Owner later with way A, C or D (accounts removed, like a fresh install). Rules and pairing are kept.