This step prepares the tablet or phone before installing and activating the kiosk app.

1. Factory Reset the Tablet or Phone

Warning: This will erase all data on the device.

Method 1: Factory Reset from Settings (Recommended)

• Open Settings
• Go to System or General Management
• Tap Reset Options
• Select Erase all data (Factory reset)
• Tap Reset Phone or Reset Tablet
• Confirm with Erase Everything

The device will restart and erase all existing data.

Method 2: Factory Reset Using Recovery Mode

Use this method if the device is locked or you cannot access Settings.

• Turn OFF the device
• Press and hold Power + Volume Up on most devices
• Wait until the Android Recovery Menu appears
• Use the Volume buttons to move through the menu
• Select Wipe data / factory reset
• Press the Power button to confirm
• Select Yes
• After reset is finished, choose Reboot system now

2. First Setup After Reset

After the device reboots:

• Select your language
• Connect to Wi-Fi
• Skip Google account if it is not needed yet
• Complete only the minimum setup required

Important:

• Do not fully configure the device more than necessary
• Do not set a screen lock yet if you plan to continue Device Owner setup

3. Enable Developer Options

USB debugging is inside Developer Options.

• Open Settings
• Go to About Phone or About Tablet
• Find Build Number
• Tap Build Number 7 times

Expected message:

You are now a developer

4. Enable USB Debugging

• Go back to Settings
• Open Developer Options
• Find USB Debugging
• Turn it ON
• Tap Allow if prompted

5. Connect the Tablet or Phone to the Computer

• Connect the device using a USB cable
• Wait for the prompt:

Allow USB debugging?

Then:

• Check Always allow from this computer
• Tap Allow

6. Verify ADB Connection on the Computer

Open Command Prompt or Terminal on your computer and run:

adb devices

Expected output example:

List of devices attached
R9WN12345 device

Expected Result

After this step is completed:

• The device is fully reset
• Developer Options are enabled
• USB Debugging is enabled
• ADB connection is working
• The device is ready for kiosk app installation

This step prepares the Android device so the kiosk app can be installed and assigned as Device Owner.

Download this file first Iplay-Kiosk-Program-Tool 'cmd-here' but I recommended to use our Official Tool 'KSoft Tool

1. Factory Reset the Phone (Required) Skip if already reset

Device Owner can only be set on a fresh or unprovisioned device.

• Open Settings
• Go to System or General Management
• Tap Reset
• Select Factory data reset
• Tap Erase all data

After reboot, complete only the minimum setup needed to reach the home screen.

Important:

• Do not add a Google account yet
• Do not set screen lock, PIN, fingerprint, or pattern yet

2. Enable Developer Options

• Open Settings
• Go to About Phone
• Find Build Number/OS Version
• Tap Build Number 7 times

Expected message:

You are now a developer

3. Enable USB Debugging

• Go back to Settings
• Open Developer Options
• Enable USB Debugging

4. Connect Phone to PC and Verify ADB

Connect the device to the PC using a USB cable, then run:

adb kill-server
adb start-server
adb devices

Expected output example:

List of devices attached
R9WN12345 device

On the phone:

• Accept the RSA fingerprint prompt
• Check Always allow from this computer
• Tap Allow

5. Install the Kiosk APK

Install your kiosk app using:

adb install -r iplaykiosk.apk

-r means replace the existing version if it is already installed.

6. Set Device Owner

Run the exact command below:

adb shell dpm set-device-owner com.kwarton.iplaykiosk/.KioskDeviceAdminReceiver

If successful, Android will register the kiosk app as the Device Owner.

7. Verify Device Owner

To confirm it worked, run:

adb shell dpm list-owners

Expected result:

Device Owner:
com.kwarton.iplaykiosk

Common Errors and Fixes

1. already provisioned

This means the device was already set up before running Device Owner.

Fix:

• Factory reset the phone again
• Run the Device Owner command before completing full Android setup

2. Unknown admin

This usually means the APK is not installed correctly or the admin receiver name is wrong.

Fix:

• Make sure the APK is installed first
• Confirm the receiver name is exactly:

com.kwarton.iplaykiosk/.KioskDeviceAdminReceiver

3. unauthorized

This means the phone has not approved USB debugging yet.

Fix:

• Reconnect the USB cable
• Unlock the phone
• Accept the RSA prompt on the device

Expected Result

After this step is completed:

• The kiosk app is installed
• ADB communication is working
• The app is registered as Device Owner
• The device is ready for admin setup and license activation

Before binding hardware, activating a license, or changing production settings, you must open the kiosk Admin panel and configure the correct API server.

1. Open the Admin Panel

Open the Admin panel from the kiosk app.

Default admin password:

admin1234

• Launch the iPlay Kiosk app
• Open the Admin panel
• Enter the password:

admin1234

After login, you can access production settings, binding, API, media, whitelist, and theme controls.

2. Go to the API Menu

Inside the Admin panel, open the API section.

This section controls how the app connects to the live server for:

• account login
• license verification
• license activation
• license release
• license transfer

3. Set the Correct API Server

Set the API Server exactly to:

https://iplay.kwarton.com/

Important:

• Use the full HTTPS URL
• Do not remove https://
• Do not use an old local IP or test domain in production

4. Why This API Server Is Required

The kiosk app depends on this server for all live account and license functions.

If the API is wrong:

• login may fail
• license activation may fail
• unbind or release may fail
• mode switching may fail
• license transfer may fail

5. Save the API Settings

After entering the correct API:

• Tap Save
• Return to the Admin panel
• Reopen the API page if needed to confirm the value is saved

Expected saved value:

https://iplay.kwarton.com/

6. Verify Internet Connection

Before continuing to license activation:

• Make sure the device is connected to Wi-Fi or mobile data
• Make sure the device is not connected only to the ESP32 setup AP
• Confirm the kiosk device can reach the internet

Important:

• The ESP32 setup AP is only for ESP32 configuration
• It is not a replacement for internet access to the API server

7. Recommended Check Before Activation

Before moving to the next step, confirm all of the following:

• Admin panel opens correctly
• Password admin1234 works
• API Server is set to https://iplay.kwarton.com/
• The device has internet access

8. Security Recommendation

After successful setup, it is recommended to change the default admin password to prevent unauthorized access.

Default password:

admin1234

Recommended action:

• Open the Password menu in Admin
• Set a new secure admin password
• Store it safely for maintenance use

9. Common Problems

1. Login does not work

Fix:

• Check internet connection
• Check API Server
• Confirm the account credentials are correct

2. Activation shows network error

Fix:

• Verify the API is exactly:

https://iplay.kwarton.com/

• Do not stay connected only to the ESP32 setup AP
• Reconnect to router internet if needed

3. Release or transfer fails

Fix:

• Check API server value
• Check internet access
• Retry after confirming the server is reachable

Expected Result

After this step is completed:

• The Admin panel is accessible
• The API Server is correctly configured
• The kiosk is ready for account login and license activation

Final required value:
API Server = https://iplay.kwarton.com/
Admin Password = admin1234 (change later for security)

Before activation, you must log in to your account first because your license keys are inside your dashboard account.

1. Connect the Device to the Internet

• Make sure the kiosk device is connected to Wi-Fi or mobile data
• Confirm the device can open the login page
• Do not continue if there is no internet connection

2. Open the Kiosk Admin Panel

To continue setup, open the Admin panel in the kiosk app.

Default admin password:

admin1234

• Launch the iPlay Kiosk app
• Open the Admin panel
• Enter the default password:

admin1234

After login, you can access the API, production, binding, and activation settings.

3. Set the Correct API Server

Before logging in or activating, make sure the kiosk app API Server is set to:

https://iplay.kwarton.com/

This is required so the app can:

• log in to your account
• verify license keys
• activate the correct hardware target
• release or transfer licenses correctly

4. Log In to Your Account

• Enter your registered account email or username
• Enter your password
• Tap Login

After login, the app can check your account and retrieve the license information linked to your account.

5. Get Your License Key

Your activation key is not random. You must use the license assigned to your account.

To get your license:

• Log in to the web dashboard
• Open the License page
• Check your available Vendo or Cloud Member license
• Copy the correct license key

6. Enter the License Key in the Kiosk App

Paste the valid license key into the activation field inside the kiosk app.

Examples of where activation is used:

• ESP32 BLE binding
• ESP32 Wi-Fi binding
• External timer mode activation

7. Start Activation

After entering the license key:

• Tap Activate or Bind
• Wait for server verification
• Do not close the app during checking

If the license is valid, the server will activate it for the correct hardware target.

8. Important Activation Rule

A Vendo license must match the actual hardware target.

Examples:

• BLE mode uses the ESP32 BLE hardware target
• Wi-Fi mode uses the ESP32 Wi-Fi device ID
• External mode uses the kiosk external hardware target

If you want to move to another mode later, release or transfer the current activation first.

9. If Activation Fails

Check these first:

• Internet connection is working
• Admin panel was opened correctly using the right password
• API server is exactly set to https://iplay.kwarton.com/
• License key is correct
• You are logged in to the correct account
• The license is not revoked
• The license is not still active on another hardware target

10. Expected Result

After successful activation:

• The kiosk stores the server activation data
• The selected mode becomes available for production use
• The license status becomes active on the server

Example flow:
1. Connect to internet
2. Open Admin panel using admin1234
3. Set API Server to https://iplay.kwarton.com/
4. Login to dashboard account
5. Copy valid license key
6. Enter license key
7. Tap Activate / Bind
8. Wait for success confirmation

After the app is installed and the license is ready, the next step is to choose the correct production mode and bind or activate the correct hardware target.

1. Open the Admin Panel

Open the kiosk Admin panel using the default password:

admin1234

From the Admin panel, go to:

• Production
• Binding
• API if you still need to verify the server

2. Verify the API Server

Before binding or activation, make sure the API server is set to:

https://iplay.kwarton.com/

If the API is wrong, activation and release may fail.

3. Choose the Correct Production Type

In the Production menu, choose the correct production type.

Available options may include:

• Vendo
• Cloud Member

For ESP32 binding or external timer activation, use the correct Vendo flow when required.

4. Choose the Timer Mode

If you are using Vendo, choose the actual hardware setup:

• Internal Timer for ESP32 BLE or ESP32 Wi-Fi
• External Timer for charge-state or external board flow

Important:

• Internal mode is for ESP32 integration
• External mode is a different hardware target
• Only one active hardware target should be used at a time

5. If Using ESP32 Internal Timer

Go to the Binding menu and choose the transport:

• BLE
• Wi-Fi

BLE Binding Flow

• Enable BLE mode
• Scan for the ESP32 device
• Select the correct ESP32
• Enter the valid license key when prompted
• Wait for successful binding

Wi-Fi Binding Flow

• Enable Wi-Fi mode
• Enter the ESP32 base URL
• Enter the ESP32 device ID / hardware ID
• Save the settings
• Enter the valid license key when prompted
• Wait for successful binding

Important:

• Wi-Fi binding does not need BLE first
• Use the real ESP32 Wi-Fi device ID
• The ESP32 and kiosk must be configured correctly for the network

6. If Using External Timer Mode

If you choose External Timer:

• Open the External activation section
• Enter the valid Vendo license when prompted
• Wait for successful activation

Important:

• External mode is not the same as ESP32 internal mode
• External activation uses its own hardware target
• If ESP32 is currently bound, unbind or transfer first before continuing

7. If You Need to Switch Modes

Do not leave multiple hardware targets active at the same time.

Example:

• If BLE is already active and you want External mode, release or transfer first
• If External mode is active and you want Wi-Fi ESP32, release or transfer first

The server must keep one correct active target at a time.

8. Save and Verify

After selecting the correct mode and completing activation or binding:

• Save the settings
• Return to the portal
• Test the runtime behavior
• Confirm the selected mode is working correctly

Check:

• Insert coin behavior
• Timer response
• Lock and unlock behavior
• BLE or Wi-Fi communication if using ESP32
• Charging detect behavior if using external mode

9. Common Mistakes to Avoid

• Using the wrong API server
• Trying to use Wi-Fi and BLE at the same time
• Switching to External mode without releasing current ESP32 activation
• Using the wrong hardware ID or device ID
• Trying to activate without internet connection

Expected Result

After this step is completed:

• The correct production mode is selected
• The correct hardware target is activated or bound
• The kiosk is ready for real production testing

Example internal Wi-Fi flow:
1. Open Admin panel
2. Set API Server to https://iplay.kwarton.com/
3. Select Vendo
4. Select Internal Timer
5. Select Wi-Fi mode
6. Enter Base URL and Device ID
7. Save
8. Enter valid license key
9. Wait for binding success

This step explains how to connect the kiosk device and the ESP32 through the same router network and how to configure the ESP32 from its built-in web server.

1. Power On the ESP32

After the ESP32 starts, it will open its own setup Access Point (AP).

Typical setup AP example:

iPlay-Setup-XXXX

Default setup AP password:

12345678

You can connect to this AP from a phone, tablet, or laptop to open the ESP32 setup page.

2. Connect to the ESP32 Setup AP

• Open Wi-Fi on your phone, tablet, or laptop
• Connect to the ESP32 setup AP
• When asked for the password, enter:

12345678

Then open a browser and visit:

http://192.168.4.1/

This opens the ESP32 local configuration page.

3. Configure the ESP32 Router Connection

Inside the ESP32 web server, enter the router information:

• Router SSID
• Router Password

If you want a fixed address for the ESP32, enable static IP mode.

Recommended example:

Static IP: 192.168.1.11
Gateway: 192.168.1.1
Subnet: 255.255.255.0
DNS1: 8.8.8.8
DNS2: 8.8.4.4

Important:

• The Static IP is for the ESP32 itself
• The Gateway must be your router IP
• Do not use 192.168.4.1 as the gateway for station mode
• Choose an IP that is not already used by another device

4. Save the ESP32 Wi-Fi Settings

After saving:

• The ESP32 will connect to your router as a Wi-Fi client
• The setup AP can still remain available if enabled
• The ESP32 will get its router-side IP

If static IP is enabled, the ESP32 should keep the same IP after reboot.

Example:

http://192.168.1.11/

5. Connect the Kiosk Device to the Same Router

The kiosk device must also connect to the same router network.

Example:

• ESP32 router IP: 192.168.1.11
• Kiosk device IP: 192.168.1.20
• Router gateway: 192.168.1.1

Important:

• The kiosk device and ESP32 must be on the same network
• They do not communicate through the ESP32 setup AP in production mode
• The ESP32 setup AP is mainly for configuration

6. Verify the ESP32 Web Server from the Kiosk Network

Before binding in the kiosk app, verify that the ESP32 web server can be reached from the same router network.

Open a browser on the kiosk device or another device on the same router and visit:

http://192.168.1.11/

Replace the IP with your actual ESP32 IP.

If the page opens, the ESP32 is reachable over the router network.

7. Configure Wi-Fi Binding in the Kiosk App

Open the kiosk Admin panel and go to the Binding menu.

Set:

• Mode = Wi-Fi
• Base URL = ESP32 router IP or full base URL
• Device ID = actual ESP32 Wi-Fi hardware ID / device ID

Example:

Base URL: http://192.168.1.11
Device ID: D485F9641D44

Then:

• Tap Save
• Enter the valid license key when prompted
• Wait for successful binding

8. How Communication Works

The communication flow is:

• The kiosk app sends HTTP requests to the ESP32 Base URL
• The ESP32 receives the command through its Wi-Fi web server
• The ESP32 responds with pulse, credit, timer, or config data

This only works correctly when:

• the ESP32 is connected to the router
• the kiosk device is on the same network
• the Base URL is correct
• the Device ID is correct

9. Common Problems

1. ESP32 web page opens only on 192.168.4.1

This means you are still using the setup AP, not the router network.

Fix:

• Connect the ESP32 to the router first
• Connect the kiosk device to the same router
• Use the router-side ESP32 IP, not 192.168.4.1

2. Kiosk cannot communicate with ESP32

Fix:

• Check that both devices are on the same router network
• Check the Base URL
• Check the ESP32 Device ID
• Check that the ESP32 web server opens from a browser

3. ESP32 IP changes after reboot

Fix:

• Use static IP mode in the ESP32 web server
• Or reserve the IP in the router DHCP settings

10. Expected Result

After this step is completed:

• The ESP32 is connected to the router
• The kiosk device is on the same network
• The ESP32 web server is reachable from the router IP
• The kiosk app can bind and communicate with the ESP32 over Wi-Fi

Example final setup:
ESP32 AP Password: 12345678
Router IP: 192.168.1.1
ESP32 IP: 192.168.1.11
Kiosk Device IP: 192.168.1.20
Kiosk Base URL: http://192.168.1.11
ESP32 Device ID: D485F9641D44

This step explains how to bind the kiosk device to the ESP32 using BLE.

1. Prepare the ESP32

Before binding:

• Power on the ESP32
• Make sure the correct BLE firmware is installed
• Keep the ESP32 close to the kiosk device

2. Enable Bluetooth on the Kiosk Device

• Open Android Bluetooth settings
• Turn Bluetooth ON
• Keep the device near the ESP32

Important:

• Do not rely on normal Android Bluetooth pairing for production binding
• BLE binding must be done inside the kiosk app

3. Open the Admin Panel

Use the default admin password:

admin1234

Then go to:

• Production
• Binding

4. Verify the API Server

Before binding, make sure the API server is:

https://iplay.kwarton.com/

This is required for license verification and BLE activation.

5. Select the Correct Production Mode

Verify:

• Production Type is correct
• Vendo is selected if required
• Internal Timer is selected

BLE binding belongs to Internal Timer, not External Timer mode.

6. Start BLE Scan

In the Binding menu:

• Choose BLE
• Tap scan
• Wait for available ESP32 devices to appear

7. Select the Correct ESP32

From the scan results:

• Tap the correct ESP32 device
• Wait for the binding dialog
• Do not choose the wrong nearby ESP32 board

8. Enter the License Key

When prompted:

• Enter the valid license key
• Tap Activate or Bind
• Wait for server verification

The license must match the correct BLE hardware target.

9. Test BLE Communication

After binding:

• Return to the portal
• Test insert coin or runtime control
• Check that the kiosk app can communicate with the ESP32

10. Important BLE Rules

• If BLE mode is active, Wi-Fi logic should not be used at the same time
• Only one transport should be active at a time
• BLE mode should use BLE-only communication

11. Common Problems

No ESP32 found

• Check ESP32 power
• Move the device closer
• Restart Bluetooth and scan again

Binding fails

• Check internet connection
• Check API server
• Check the license key
• Check the selected production mode

Communication fails after binding

• Make sure BLE mode is still selected
• Make sure Wi-Fi mode is not active
• Restart the ESP32 and retry

Expected Result

After this step:

• The kiosk app is bound to the correct ESP32 BLE board
• The valid license is activated for the BLE hardware target
• BLE communication works for production use

Example BLE flow:
1. Power on ESP32
2. Enable Bluetooth
3. Open Admin panel
4. Set API Server to https://iplay.kwarton.com/
5. Select Vendo + Internal Timer
6. Choose BLE
7. Scan and select ESP32
8. Enter valid license key
9. Tap Bind
10. Test communication

After activation and hardware setup are complete, configure the kiosk portal before handing the device to the operator or customer.

1. Open the Admin Panel

Open the Admin panel using the admin password:

admin1234

Then review these sections:

• Portal
• Production
• Binding
• Media
• Theme
• Whitelist
• Time Rate

2. Configure the Portal Menu

In the Portal section, review:

• Portal title
• Landscape mode
• Portal log visibility

Recommended:

• Set the correct kiosk title
• Enable landscape mode only if the installed device layout requires it
• Disable logs in production unless needed for debugging

3. Configure Media

In the Media section, review:

• Insert coin sound
• 2-minute warning sound
• Voice prompt
• Floating timer overlay
• Locked banner image

Recommended:

• Use clear insert coin sound
• Use warning sound only if needed
• Upload a proper locked banner image for production
• Use PNG or JPG for best compatibility

4. Configure Theme

In the Theme section, review:

• Portal theme
• Icon shape

Available examples:

• Iplay Default
• Aurora Glass
• Square or Round icon style

Make sure the portal remains readable and clean on the actual device screen.

5. Configure the Whitelist Apps

In the Whitelist section, select only the apps that should be visible in the portal.

Recommended:

• Add only approved apps
• Remove unnecessary system or third-party apps
• Verify the icon and label look correct in the portal

6. Configure Time Rate

If using internal timer mode, open Time Rate and configure:

• Rate per time
• Free minutes if needed
• Minimum coin behavior

Important:

• Time Rate is hidden in External Timer mode
• External mode does not use the same internal timer rate logic

7. Verify Production Type and Binding

Before leaving the Admin panel, verify again:

• Correct production type is selected
• Correct timer mode is selected
• BLE or Wi-Fi binding is successful if using ESP32
• External activation is successful if using external mode

8. Test the Portal Runtime

Return to the main portal screen and check:

• Portal title displays correctly
• Insert Coin button is visible
• Timer is visible
• Whitelisted apps appear correctly
• Task button works
• Admin button still opens the password dialog

9. Test the Actual Rental Flow

Run a real production test.

Check:

• Coin insert or pulse input works
• Timer starts correctly
• Device locks and unlocks correctly
• ESP32 communication works if using internal mode
• Charge-state behavior works if using external mode

10. Final Recommendation Before Handoff

Before giving the kiosk to the operator:

• Change the default admin password
• Confirm the correct API server is saved
• Confirm the correct license is active
• Confirm only approved apps are visible
• Confirm the portal looks correct in portrait or landscape mode

Expected Result

After this step is completed:

• The portal is visually ready
• The correct apps are shown
• The selected production mode works properly
• The kiosk is ready for production use

Final checklist:
- Admin password changed
- API server correct
- License activated
- Correct mode selected
- Binding successful
- Portal title correct
- Whitelist checked
- Runtime tested