Android Provisioning Studio User Manual

1. Overview

What is Android Provisioning Studio?

Android Provisioning Studio (APS) is a desktop application for preparing, configuring, and managing Android devices from one place. It brings device information, applications, files, direct controls, reusable configurations, and deployment tools together in a single workflow.

APS is especially useful when the same device setup needs to be repeated. Instead of going through the same steps manually on every Android device, you can create a reusable Profile containing the actions required for that setup and deploy it whenever it is needed again.

You can also use APS without creating a Profile. For one-time tasks, you can connect a device and work with it directly — inspect its hardware and system information, manage applications and files, change settings, capture diagnostic information, or perform common device actions.

This makes APS suitable for anything from inspecting a single Android device to preparing many devices with the same configuration.

How APS works

APS is built around a simple workflow:

Connect → Inspect → Profile → Deploy → Review

Start by connecting one or more Android devices to your computer. Connected devices appear in APS and can be selected whenever you want to inspect or work with them.

For immediate tasks, you can work directly with the selected device. If the work represents a setup that you will need again, you can create a Profile instead. A Profile stores an ordered set of actions, such as installing applications, transferring files, changing display settings, configuring device behavior, or applying supported management policies.

When the Profile is ready, Deploy applies it to the devices you select. APS follows the actions in the Profile, shows the progress of the deployment, and records the result so you can review what happened on each device.

Not every task needs the complete workflow. A quick inspection or individual change may begin and end in the Device tab. Profiles and Deployments become useful when you want a setup to be repeatable and consistent.

The main areas of APS

Dashboard

The Dashboard gives you an overview of your current APS environment. From here, you can see connected-device information, access frequently used Quick Actions, and review recent deployments.

Device

Device is where you inspect and work directly with the Android device currently selected in the sidebar. It provides device information, direct controls, application management, file access, and Logcat diagnostics.

Profiles

Profiles is where you create reusable device setups. A Profile combines actions in the order they should be performed, allowing the same configuration to be reviewed, saved, and used again whenever it is needed.

Deploy

Deploy is where Profiles are applied to devices. Select a Profile, choose one or more target devices, start the deployment, and follow its progress and results.

Workspace

Workspace is the local file area used by APS to keep operational files and generated outputs organized. It provides dedicated locations for APKs, deployment files, backups, reports, screenshots, exported Profiles, and deployment logs.

Settings

Settings contains the main APS preferences and maintenance options. This includes APSBridge setup, operator information, appearance options, and controls for locally stored APS data.

APSBridge

APSBridge is the Android companion for APS. It can provide additional device and application information and enables managed-device capabilities that are not available through standard device access.

APSBridge is not required for basic APS operation. You can connect and inspect devices, manage applications and files, create Profiles, and run Deployments without it. APSBridge setup and its additional capabilities are covered later in this manual.

2. Getting Started

This chapter takes you through the initial setup required to connect an Android device to APS and start working with it.

For most devices, the process only needs to be completed once for each computer you use with APS.

What you need

Before connecting your first device, make sure you have:

• Android Provisioning Studio installed on your computer.
• An Android device you are authorized to configure.
• A USB cable that supports data transfer. Some USB cables are designed for charging only and cannot establish an APS connection.
• Access to the Android device so you can enable Developer options and approve the computer for USB debugging.

APS includes the components required to communicate with Android devices, so you do not need to install Android Studio or configure additional connection tools separately.

Enable Developer options

Android keeps its developer features hidden by default. Before APS can communicate with a device, Developer options must be enabled.

The exact names and locations of Android settings can vary slightly between manufacturers and Android versions, but the usual procedure is:

1. Open Settings on the Android device.
2. Open About phone, About tablet, or the equivalent device information page.
3. Find Build number.
4. Tap Build number seven times.
5. If requested, enter the device PIN, password, or unlock pattern.
6. Android will confirm that Developer options have been enabled.

On some devices, Build number may be located inside another section such as Software information.

Once Developer options have been enabled, they remain available unless the device is reset or the setting is manually disabled.

Enable USB debugging

After enabling Developer options:

1. Return to the main Settings screen.
2. Open Developer options. Depending on the device, this may be under System, Additional settings, or another advanced settings section.
3. Find USB debugging.
4. Turn it on.
5. Confirm the Android warning if one appears.

USB debugging allows APS to communicate with the device through Android Debug Bridge (ADB).

You do not need to change other Developer options for normal APS operation. Unless you specifically know that another setting is required for your device or workflow, leave the remaining options unchanged.

Connect the device

Connect the Android device to your computer using a USB data cable.

Keep the device unlocked during the first connection.

When the device connects to a computer with USB debugging enabled, Android may display a message similar to Allow USB debugging? The dialog also shows the computer's RSA key fingerprint.

Choose Allow to authorize the computer.

If Android offers Always allow from this computer, you can enable it on computers you trust. This prevents the authorization dialog from appearing every time the same device is reconnected to that computer.

APS cannot approve this authorization for you. It must be accepted directly on the Android device.

Check the device in APS

Open APS after connecting the device.

Detected Android devices appear in the device sidebar. APS automatically monitors connected devices, so a newly connected device should normally appear without restarting the application.

Select the device to begin working with it.

A device can appear with different connection states:

Online

The device is connected, authorized, and ready for APS operations.

Unauthorized

The computer has not yet been approved for USB debugging. Unlock the Android device and look for the USB debugging authorization dialog.

Offline

The device has been detected but APS cannot currently communicate with it. Reconnecting the USB cable or waiting for Android to finish starting can often restore the connection.

If a device does not appear, use Refresh devices in APS after checking the USB connection and USB debugging status.

When several devices are connected, use the device name and serial number to make sure you are working with the correct one.

Your first look at a device

Once the device shows as Online, select it and open Device → Overview.

APS begins collecting available information about the device, including its identity, Android version, hardware, display, storage, battery, network, security, and system information.

Some information can take slightly longer to appear, and the amount of information available can vary between Android versions and device manufacturers.

At this point, APS is ready to use.

You can continue directly to the Device tab if you want to inspect or work with this device, or create a Profile when you want to prepare a configuration that can be used again.

Connecting multiple devices

APS can detect multiple Android devices connected to the computer at the same time.

Each device appears separately in the sidebar and is identified by its device information and serial number. Selecting a device in the sidebar determines which device is used by the Device area and other single-device operations.

For larger setups, devices can also be connected through suitable powered USB hubs. The number of devices that can operate reliably at the same time depends on the computer, USB controller, hubs, cables, power requirements, and the connected Android devices.

Before running a deployment across several devices, make sure every intended target appears in APS and reports a usable connection state.

APSBridge

APS can be used without APSBridge, so installing the companion is not required just to get started.

When you need the additional information or managed-device capabilities provided by APSBridge, it can be set up from APS. Device management configuration has additional Android requirements and should only be enabled when the device is intended to be managed that way.

The relevant APSBridge options are explained later in the Settings and Device chapters.

If your device does not connect

If APS cannot see the device, check the basics first:

• Make sure the USB cable supports data, not only charging.
• Unlock the Android device.
• Confirm that Developer options and USB debugging are enabled.
• Look for an unanswered Allow USB debugging? dialog on the device.
• Disconnect and reconnect the USB cable.
• Try another USB port or cable if necessary.
• Use Refresh devices in APS.

If the device is still unavailable, see Troubleshooting at the end of this manual.

3. Dashboard

The Dashboard is the starting point for day-to-day work in APS. It provides an overview of your current environment, including your Profiles, recent deployment activity, frequently used actions, and the Android device currently selected in the sidebar.

You can use the Dashboard without a connected device to review Profiles and previous Deployments. Device information and Quick Actions become available when an online device is selected.

Dashboard overview

At the top of the Dashboard, four summary cards provide a quick view of your current APS activity.

Profiles Ready shows how many of your saved Profiles contain enabled actions and are ready to be used for a Deployment.

Last Deployment shows the most recent Deployment together with its Profile, status, device count, and completion information.

Deployment Health summarizes the results of recorded Deployments and recent activity, making it easier to notice repeated failures or changes in deployment reliability.

Action Coverage shows the actions currently available through the APS action catalog. Individual actions can still depend on the Android version, device capabilities, or APSBridge.

These cards are intended as a quick overview. Profiles can be reviewed and edited in Profiles, while complete deployment results are available through Recent Deployments.

Quick Actions

Quick Actions provide fast access to operations you use regularly. APS can keep up to 10 configured Quick Actions on the Dashboard, allowing them to remain ready whenever you need them.

A Quick Action contains a single configured action and runs directly on the device currently selected in the sidebar. This makes it useful for routine tasks that do not require a complete Profile or Deployment.

To create one, select Add Action, give the preset a recognizable name, choose an action, and configure its options. Once saved, the Quick Action remains available on the Dashboard for future use.

Before running a Quick Action, select the intended online device and check the action before choosing Run. APS runs one Quick Action at a time and displays its result when the operation finishes.

Quick Actions can also be edited or removed when they are no longer needed. Lock Quick Actions can be used to prevent accidental execution until they are unlocked again.

Quick Actions are intended for immediate work and do not create Deployment history. When a task contains several actions, needs to run on multiple devices, or should have a recorded Deployment result, use a Profile and Deploy instead.

Selected device

The Dashboard includes a compact summary of the device currently selected in the sidebar. It provides its identity and connection status together with available information such as Android version, battery, memory, and storage.

Selecting another connected device updates this information and also changes the target used by Quick Actions.

For complete device information and controls, open Device.

Recent Deployments

Recent Deployments provides quick access to previous Deployment runs. Each record shows the Profile used, when the Deployment took place, its overall result, and the devices involved.

Open a Deployment to see more information about the run, including its Deployment ID, duration, device results, and the actions performed on each device. This makes Recent Deployments useful both for confirming completed work and investigating a failed operation.

Deployment logs can be exported directly from the Dashboard. Exported logs are stored in:

Workspace → Exports → Deployment Logs

A Deployment record can also be deleted when it is no longer required. Deleting the record removes it from APS history but does not undo any changes that were already made to the Android devices. Export the log first if you may need to keep a record of the Deployment.

4. Device

The Device area is where you inspect and work directly with the Android device currently selected in the sidebar. It brings together detailed device information, direct controls, application management, file access, and diagnostic tools.

Use Device when you want to inspect a device or perform an immediate operation without creating a Profile. Actions performed here apply directly to the selected device and do not create a Deployment record.

When several devices are connected, always check the device name and serial number before performing an action. Selecting another device in the sidebar changes the device you are working with throughout this area.

The Device tabs

The Device area is organized into five tabs:

Overview provides a complete summary of the selected device, including its identity, hardware, display, storage, battery, network, security, and system information.

Actions provides direct device controls and supported APSBridge management actions.

Apps lets you inspect installed applications, install APKs, manage applications, and create application reports.

Files provides access to available Android storage and allows files to be transferred between the device and your computer.

Logcat displays Android diagnostic messages and provides tools for filtering and exporting them when troubleshooting a device or application.

For a newly connected device, Overview is usually the best place to start.

Overview

The Overview tab brings the available information about the selected Android device into one place. APS collects this information automatically and organizes it into separate cards.

The Device card identifies the device and provides its main Android and system information, including its model, device name, serial number, Android version, build information, and the latest captured device screenshot.

Display shows the current screen configuration, including resolution, refresh rate, density, orientation, brightness, timeout, and other display settings.

Hardware provides information about the device platform, processor, architecture, graphics, memory, and other available hardware details.

Storage shows the device’s storage capacity, current usage, and available space.

Battery shows the current charge and charging state together with the additional battery information reported by Android.

Network provides a summary of the available Wi-Fi, Bluetooth, and mobile-network state.

Security brings together available information about the device’s security and management state, including encryption, screen lock, USB debugging, and device ownership where available.

System contains additional operating information and shows the current status of APSBridge, including whether the companion is installed and whether its managed-device role is active.

The exact information available can vary between Android versions and manufacturers. APSBridge can also provide additional information that is not normally available through standard device access.

Refresh device information

APS loads device information automatically when a device is selected. Use Refresh Device Information whenever you want APS to request an updated set of values from the device.

Individual information cards may finish loading at different times. If a value remains unavailable, the device may simply not expose that information.

Device screenshots

APS can capture the current Android screen directly from Overview.

Select Take Screenshot to capture the screen currently displayed on the device. The resulting image appears in the Device card and remains a static capture — it is not a live view or remote-control screen.

Select Export Screenshot when you want to keep the image. Exported screenshots are stored in:

Workspace → Exports → Device Screenshots

Take a new screenshot whenever the current device screen matters, as the image already displayed in APS may be from an earlier capture.

Device Technical Sheet

Select Export Tech Sheet to generate a PDF containing the available technical information for the selected device.

The generated report is stored in:

Workspace → Exports → Device Reports

A Device Technical Sheet provides a convenient record of the device and can be useful for documentation, inventories, handovers, or support. Refresh the device information before exporting when you need the report to reflect its latest state.

Actions

The Actions tab provides direct controls for the Android device currently selected in the sidebar. Use it when you need to make an immediate change, test a device response, or perform a routine operation without creating a Profile.

Actions performed here apply directly to the selected device and do not create a Deployment record. When the same configuration needs to be applied again or across multiple devices, add the required actions to a Profile and run it through Deploy instead.

Before performing an action, make sure the intended device is selected and Online. Some actions take effect immediately.

Device Controls

Device Controls contains common operations for controlling the selected Android device. From here, you can change the device name, wake or sleep the screen, restart or power off the device, and control supported screen-lock behavior.

You can also send standard Android navigation commands such as Home, Back, and Recent Apps. These can be useful while preparing or testing a device without having to interact with its screen directly.

Restarting the device temporarily disconnects it from APS. Once Android has started again, the device will become available when its connection to APS is restored.

Display Controls

Display Controls provides direct access to common screen settings, including brightness, automatic brightness, orientation, and supported screen-awake behavior.

Changes are applied directly to the selected device, making these controls useful for testing settings or making quick adjustments. For display settings that should be part of a repeatable device configuration, use the corresponding actions in a Profile.

Input & Sound

Input & Sound provides controls for common device interaction and audio settings, including supported input commands and volume controls.

These controls are useful for quickly adjusting or testing the selected device without creating a Profile.

APSBridge Controls

APSBridge Controls provides additional management actions when APSBridge and the required managed-device capabilities are available on the selected device.

These actions can be used for tasks such as applying device restrictions, configuring kiosk behavior, managing applications, and controlling other supported Android policies.

The available capabilities depend on the Android version, device manufacturer, APSBridge status, and the management state of the device. Some actions therefore require APSBridge to be configured with the appropriate permissions before they can be used.

Because managed-device actions can significantly change how an Android device behaves, review their configuration before applying them. APSBridge setup and its management capabilities are covered later in this manual.

ADB Terminal

The ADB Terminal provides direct command access to the selected Android device for advanced users. Commands are entered without the adb prefix, as APS automatically sends them to the currently selected device.

For example:

• shell getprop — displays Android system properties.
• shell pm list packages — lists installed application packages.
• shell dumpsys battery — displays detailed battery information.
• shell settings get system screen_brightness — reads the current screen brightness value.
• reboot — restarts the selected device.

The command output is displayed directly in APS and can be copied or cleared when no longer needed.

Terminal commands are executed directly and are not recorded as Deployments. Use the terminal for specific commands, diagnostics, or operations that are not covered by the standard APS controls. For repeatable operations, use the appropriate action in a Profile whenever possible.

For additional commands and usage information, see Google's official Android Debug Bridge documentation. When using commands from the documentation in the APS Terminal, omit the adb prefix.

Apps

The Apps tab is where you view and manage the applications installed on the Android device currently selected in the sidebar. It provides a central place to inspect installed applications, install APK files, perform direct application actions, and create application reports.

Operations performed from Apps apply directly to the selected device and do not create a Deployment record. When the same application setup needs to be repeated or applied to multiple devices, use the corresponding actions in a Profile instead.

Installed applications

APS displays the applications installed on the selected device in a searchable and filterable list. Applications can be identified by their displayed name or by their Android package name.

A package name is the unique identifier Android uses for an application, such as com.example.app. Unlike the displayed application name, the package name provides a precise way to identify an application when configuring actions, comparing devices, or troubleshooting.

Select an application to view the information available from the device. This can include its version, package information, installation details, storage usage, permissions, current state, signing information, and other technical properties reported by Android.

APSBridge can provide additional application information, including application names, icons, and storage details. When APSBridge information is not available, APS continues to display the application data accessible through the standard device connection.

Use Refresh Applications whenever you want APS to reload the application list, particularly after installing, removing, or modifying an application.

Install an APK

Select Install APK to install an Android application package stored on your computer. Choose the APK file and APS will install it on the device currently selected in the sidebar and display the result when the operation finishes.

An installation can be rejected by Android when the APK is not compatible with the device, requires a different Android version, conflicts with the signature of an existing installation, or when sufficient storage is not available.

After a successful installation, refresh the application list if you want to inspect the newly installed application and its details.

When an APK is part of a configuration that should be used again, add the installation to a Profile instead. This allows the application to be installed together with the other actions required for that device setup.

Application actions

Selecting an application provides direct controls for working with that package. Depending on the application and the Android device, you can launch the application, open its Android App Info page, force stop it, clear its cache or data, enable or disable it, or uninstall it.

Some application actions make immediate changes to the device. Clear Cache removes temporary application files, while Clear Data removes the application's locally stored data, settings, and other application state. Disabling or uninstalling system applications can also affect other Android functions.

Android may restrict certain operations for protected, system, or manufacturer applications. The actions available and their results can therefore vary between applications, Android versions, and device manufacturers.

Application reports

APS provides two ways to export application information: a complete Application List and an individual App Technical Sheet.

The Application List is exported as an Excel spreadsheet (XLSX). It contains the applications currently shown in the Apps list together with the technical information available for them. Search and filtering can be applied before exporting when you want the spreadsheet to contain a more focused selection of applications.

The Excel export is useful when you need to review the software environment of a device as a whole, compare application information, create an inventory, or keep a structured record that can be opened and processed in spreadsheet software.

For an individual application, Export Tech Sheet creates an App Technical Sheet in PDF format. The report contains the available technical information for the selected application and provides a convenient standalone document for documentation, handover, or troubleshooting.

Application List exports and App Technical Sheets are stored in:

Workspace → Exports → App Reports

Together, these exports provide both levels of documentation: the Excel Application List for an overview of the applications on a device, and the PDF App Technical Sheet when detailed information about a specific application is required.

Files

The Files tab provides access to the available storage on the Android device currently selected in the sidebar. Use it to browse files and folders, transfer content between your computer and the device, and perform common file-management operations.

Files works directly with storage on the Android device. It is separate from Workspace, which organizes the files used and generated by APS on your computer.

Browse device storage

APS displays the storage locations available on the selected device, including internal storage and additional storage volumes when they are accessible.

Quick-access locations such as Downloads, Pictures, Movies, Music, DCIM, and Android provide shortcuts to commonly used folders. You can also navigate through the device storage normally using folders and breadcrumbs.

Files and folders can be searched and sorted to make larger directories easier to work with. Selecting an item displays additional information about it, including its location, size, modification date, and other details available from the device.

Android may restrict access to certain parts of its file system, particularly system and application data. The locations available in APS can therefore vary depending on the Android version, device manufacturer, and the access permitted by the device.

Transfer files

Use Upload to copy files from your computer to the folder currently open on the Android device. Multiple files can be selected when you need to transfer several items to the same location.

Files and folders can also be downloaded from the Android device to your computer. Transfer activity is shown in the Transfer Queue, allowing you to follow the progress and result of file operations.

Keep the device connected while a transfer is in progress. When necessary, refresh the current folder after an upload to display the newly transferred files.

Uploading an APK through Files only copies the APK to the device storage — it does not install the application. To install an APK directly, use Device → Apps → Install APK, or include the installation in a Profile for a repeatable setup.

Manage files and folders

The Files tab also provides common file-management operations for the accessible device storage. You can create folders and perform supported operations such as renaming, moving, or deleting files and folders.

You can also copy the full path of an item when you need to reference its location elsewhere in APS, for example when working with commands or configuration actions.

File-management operations are performed directly on the Android device. Android may prevent changes to protected or restricted locations.

Take particular care when deleting files or folders. Deleted content cannot be restored through APS, and removing files used by Android or an installed application may affect how the device or application operates.

When files need to be transferred or managed as part of a repeatable device setup, use the corresponding actions in a Profile. This keeps the required files and file operations together with the rest of the configuration.

Logcat

The Logcat tab displays diagnostic messages from the Android device currently selected in the sidebar. Use it to investigate application behavior, monitor device activity, or collect information while troubleshooting.

Logcat captures messages from the selected device only. Select the intended device and make sure it is Online before starting a capture.

Capture Logcat messages

Select Start to begin capturing Logcat messages from the device. New entries appear as they are received and include the timestamp, process, severity level, tag, and message.

Select Pause to stop the list from updating while capture continues in the background. Select Resume to display the messages collected while the view was paused.

Select Stop when you no longer need to capture messages.

Use Clear to remove the currently captured entries from APS. This clears the Logcat view only and does not remove logs from the Android device.

Filter and search messages

Use the Logcat toolbar to narrow the displayed messages and focus on relevant activity.

The log-level filter can be used to show messages at a selected severity, such as Debug, Info, Warn, or Error.

Use the process filter to narrow the results by application package, process ID, or tag. Use the search field to find matching text within the captured messages. Enable Regex when you need to search using a regular expression.

When Follow is enabled, the list automatically stays at the newest messages. Disable it when you want to inspect earlier entries without the view moving as new messages arrive.

Filters and searches affect only what is displayed in APS. They do not change the messages being captured from the device.

Logcat buffer

APS keeps up to 50,000 Logcat entries in memory while capture is running. There is no capture time limit.

The status bar shows the current buffer usage, for example 23,482 / 50,000 entries.

When the buffer reaches 50,000 entries, APS automatically removes the oldest entries as new messages arrive. The status bar indicates when older entries are being removed.

Filtering, searching, and exporting operate on the entries currently available in this rolling buffer. If you need to preserve earlier messages, export them before they are replaced by newer entries.

Export Logcat

Select Export to save the currently displayed Logcat results as a text file.

Apply filters or search terms before exporting when you want the file to contain only messages related to a specific application, severity level, tag, or other search criteria.

Logcat exports are intended for diagnostics and troubleshooting. They are separate from Deployment logs and do not create a Deployment record.

5. Profiles

The Profiles area is where you create and manage reusable Android device configurations. A Profile contains an ordered set of actions that can be applied to one or more devices through Deploy.

Use Profiles for device setups that need to be repeated consistently. A Profile can combine application installation, file operations, display settings, device controls, network configuration, workflow steps, and other supported actions into a single reusable configuration.

Creating or editing a Profile does not make changes to a connected device. Profile actions are executed only when the Profile is used in Deploy and a Deployment is started.

Profiles overview

The Profiles area is divided into three main working areas.

The Profiles list contains the Profiles available in APS. Select a Profile to view and edit its configuration, or create a new one for a different device setup.

The Actions area contains the actions configured for the selected Profile. Actions are executed in the order shown when the Profile is deployed.

The details area displays the settings for the selected Profile or action. Use it to configure action parameters and review any available compatibility or validation information.

Create and manage Profiles

Select New Profile to create a Profile. Give it a clear name and, when useful, add a description or notes describing its purpose, intended devices, or setup requirements.

Use descriptive names that make Profiles easy to identify later. For example, Retail Demo Setup or Warehouse Scanner Configuration provides more context than a generic name such as New Profile.

You can return to an existing Profile at any time to review its configuration, add or remove actions, or change the action order.

Lock a Profile

Use Lock to protect a completed Profile from accidental changes.

A locked Profile can still be used for Deployments, but its configuration cannot be modified until the Profile is unlocked. This includes editing, adding, removing, or reordering actions.

Locking is useful for configurations that have been tested or approved and are used repeatedly. Unlock the Profile when changes are required, review the updated configuration, and lock it again when it is ready for use.

Delete a Profile

Delete a Profile when its configuration is no longer required.

Deleting a Profile removes it from APS. It does not reverse or otherwise affect changes made to devices by previous Deployments using that Profile.

If you may need the configuration again, export the Profile before deleting it. Profile import and export are covered later in this chapter.

Work with Profile actions

Select Add Action to add a new step to the selected Profile. Available actions are grouped by function, including applications, files, display, device controls, workflow, network, advanced operations, and supported managed-device operations.

Configure the required settings for each action before using the Profile in a Deployment. Actions can also be disabled when you want to keep them in the Profile without executing them.

Actions run from top to bottom in the order shown. Arrange them according to the sequence required by the device setup. For example, an application must be installed before an action attempts to launch it, and actions that depend on a device restart should run only after the device is available again.

Actions can be reordered as the Profile is built or updated.

The following sections describe the available Profile actions and how they can be used to build a device configuration for deployment.

6. Deploy

The Deploy area is where you apply a saved Profile to one or more Android devices. APS executes the enabled actions in the Profile, tracks progress for each target device, and records the results of the Deployment.

Use Deploy when a device configuration contains multiple actions, needs to be applied consistently across devices, or requires results that can be reviewed later. Changes made through direct Device controls or Dashboard Quick Actions are separate and do not create a Deployment record.

Prepare a Deployment

Select the Profile you want to deploy, then choose the target devices. Only connected devices that are Online can be included.

Review the Profile before continuing. APS executes enabled actions in the order defined by the Profile. Make sure any APKs, documents, certificates, images, or other local files referenced by its actions are still available on the computer.

Verify the name and serial number of each target device before starting. Devices selected for a Deployment are independent of the single device currently selected in the Device area.

The Deployment review shows the selected Profile, target devices, enabled actions, and other relevant information before execution. Start Deployment becomes available when the Deployment has a valid Profile, at least one online target device, and at least one enabled action.

Start a Deployment

Select Start Deployment when the Profile and target devices are ready. APS may require additional confirmation when the Profile contains actions that can erase data or significantly change device behavior.

When the Deployment starts, APS captures the Profile configuration, enabled actions, and selected target devices for that run. Changes made to the saved Profile afterward do not affect the active Deployment and apply only to future Deployments.

Keep APS open and the target devices connected while the Deployment is running.

If an action restarts a device, use the appropriate workflow actions in the Profile to wait for the device and Android to become available before subsequent actions are executed.

Monitor Deployment progress

While a Deployment is running, APS displays its status, overall progress, start time, duration, and Deployment ID.

Each target device has its own progress and action results. Expand a device to see which action is currently running and review the status of completed actions.

The Live Log displays additional messages for the selected device and can help identify the cause of warnings or failures.

Actions are executed in the order defined by the Profile. If an action fails on a device, the remaining actions for that device are skipped. Other target devices continue independently.

You can navigate to other areas of APS while a Deployment is running and return to Deploy to continue monitoring its progress. Avoid disconnecting target devices or closing APS until the Deployment has finished.

Cancel a Deployment

Select Cancel Deployment when you want to stop the remaining work.

Cancellation takes effect between actions. An action already in progress may finish before processing stops.

Cancelling a Deployment does not undo actions that have already completed. Applications, files, settings, policies, or other changes already applied remain on the affected devices.

Review the device and action results after cancellation to determine which parts of the Profile were completed.

Review results and logs

When the Deployment finishes, review the overall result and the status of each target device. Expand individual devices to inspect failed, skipped, or warning actions and use the Live Log for additional details.

For important configurations, verify the expected result on the target devices rather than relying only on the overall Deployment status.

Deployment logs can be saved automatically when a run finishes or exported manually when the option is available. They are stored in:

Workspace → Exports → Deployment Logs

Completed Deployments are also added to APS history and can be opened later from Dashboard → Recent Deployments.

Select New Deployment to return to the setup view and prepare another Deployment.

7. Workspace

The Workspace area provides access to the local files used by APS. It keeps files used for device configuration and files generated by APS organized in a dedicated APS Workspace folder on your computer.

Use Workspace to manage APKs, deployment files, backups, exported Profiles, reports, screenshots, and Deployment logs. Workspace contains files on your computer and is separate from Device → Files, which provides access to storage on the selected Android device.

Workspace overview

APS creates the APS Workspace folder in your computer’s Documents location and organizes it into folders for different types of content.

APKs contains Android application packages that can be used when preparing devices or configuring Profile actions.

Deploy Files contains files used by Profile actions, such as documents, media, configuration files, certificates, images, and other content that needs to be transferred to a device.

Backups provides a location for backup files you choose to store in Workspace. The presence of this folder does not mean that APS automatically creates device backups.

Exports contains files generated or exported by APS.

Within Exports, APS uses separate folders for:

• Profiles
• App Reports
• Deployment Logs
• Device Reports
• Device Screenshots

These folders provide a consistent location for files created by the corresponding APS features.

Select Open Location to open the APS Workspace folder in your computer’s file manager.

Browse Workspace files

Select a Workspace folder from the navigation area or open folders directly from the file list. Use the breadcrumbs and navigation controls to move through the folder structure.

You can search and sort the current folder to find files more easily. Select a file or folder to view available information such as its name, location, size, and modification date.

Select Open to open a file with its associated application or to open the selected folder.

Use Copy Path to copy the full local path of a file or folder, for example when you need to reference it while configuring a Profile action.

Files stored in Workspace remain on your computer until they are moved or deleted.

Import files and folders

Use Import to copy content from another location on your computer into the currently selected Workspace folder.

Select Import Files to add one or more files, or Import Folder to copy an entire folder and its contents.

Importing content into Workspace does not transfer it to an Android device or automatically add it to a Profile. To use an imported file during device configuration, reference it from the appropriate Profile action.

Keep files referenced by Profiles in their expected locations. Moving, renaming, or deleting a referenced file can prevent the corresponding action from completing during a Deployment.

Manage Workspace files

Workspace provides controls for managing its local files and folders. You can create folders, rename items, open files with their associated applications, and delete content that is no longer required.

You can organize Workspace content by project, customer, device group, deployment purpose, or any other structure that fits your workflow. Keeping related APKs, certificates, configuration files, images, and other deployment resources organized can make Profiles easier to maintain.

Take care when deleting Workspace content. Files deleted through APS cannot be restored through APS, and removing a file referenced by a Profile can cause a future Deployment action to fail.

Use Refresh when files have been added, removed, or changed outside APS and you want the current Workspace view to reflect the latest contents.

8. Actions

This guide explains the actions available in Android Provisioning Studio (APS), what each one changes, what to enter, and what to expect. Action and field names match the APS interface.

How actions run

• Device Actions run immediately against the selected, connected device. Profile Actions are saved in an ordered provisioning profile and run in that order during deployment. Actions offered in both places use the same profile action configuration.
• Set Multiple Device Name, Reboot to Recovery, Reboot to Bootloader, Delay, Wait for Device, and Wait for Boot Completion are profile actions. Take Screenshot, Home, Back, Recent Apps, and Power Off Device are immediate controls.
• An action marked disabled in its editor is skipped. A profile runs on the device selected for deployment; check the deployment target before applying changes.
• New action forms start with APS defaults; they do not automatically read the device's current setting. Saving/running a defaulted action can therefore change the device.
• New actions start enabled. Initial field values are noted below when they materially affect the result.
• ADB actions need the device connected and authorized for ADB. Managed Device actions require the current APSBridge build installed, responding, and registered as Android Device Owner. The Android version shown for a managed action is its minimum API level.
• Values are applied when the action runs. Unless stated otherwise, APS does not automatically restore the previous value. Add a later action with the desired final value when a profile must change something temporarily.
• Package names use Android application IDs such as com.example.app. Device paths are paths on Android; local paths refer to files on the computer running APS.

Managed Device

These policies require APSBridge installed and connected, with APSBridge registered as Android Device Owner. The minimum Android version is listed where it applies; target devices may also impose OEM-specific limits.

Kiosk

1. Enter Kiosk Mode

Purpose: Starts Android Lock Task (kiosk) mode and launches the selected app. Fields: Kiosk application — the installed app's package ID. Requirements: Android 9 / API 28+, Device Owner, and a launchable app. APS first replaces the kiosk allowlist with this single package, then launches it into Lock Task mode. To permit additional apps in a multi-app kiosk, apply Set Kiosk Apps after entering kiosk mode.

2. Exit Kiosk Mode

Purpose: Exits Lock Task mode by setting the allowed kiosk app list to empty. Fields: none. Requirements: APSBridge as Device Owner. This also clears the configured kiosk allowlist. The next Enter Kiosk Mode sets the allowlist to its selected app; after entering, run Set Kiosk Apps again if you need a multi-app list. APS does not restore the prior list.

3. Set Kiosk Apps

Purpose: Replaces the complete list of apps permitted to run in Lock Task mode. Fields: Allowed kiosk applications — one Android package per line; an empty list clears the allowlist (new action default is empty). This action does not enter kiosk mode. Apply it after Enter Kiosk Mode when you need a multi-app allowlist, because Enter Kiosk Mode sets the list to the selected app only. Removing the running app from the list can cause Android to exit Lock Task mode.

4. Set Kiosk Features

Purpose: Chooses system features Android exposes while Lock Task mode is active. Fields: independent switches for Home, Overview / Recents, Notifications, System Info, Keyguard, and Global Actions (typically the power menu). New action default: only Global Actions is on. Requirements: Android 9 / API 28+ and Device Owner. APS requires Home when Notifications or Overview is on. Home/Overview can let a user leave the kiosk app for system screens. This action neither enters nor exits kiosk mode.

5. Set Status Bar Disabled

Purpose: Blocks or restores access to the status bar during normal use. Fields: Status bar access — Disable or Allow (new action default: Disable). Requirements: Android 6.0 / API 23+ and Device Owner. When disabled, users normally cannot pull down notifications or Quick Settings. This policy is separate from Lock Task feature availability; configure kiosk notifications/system info with Set Kiosk Features. It does not disable the lock screen.

6. Set Keyguard Disabled

Purpose: Disables or restores Android's keyguard (lock screen) policy. Fields: Android keyguard — Disable or Allow (new action default: Disable). Requirements: Android 6.0 / API 23+ and Device Owner. Disabling it can remove the normal unlock screen; restoring it makes the device's configured PIN, password, or pattern relevant again.

Security & Restrictions

7. Set Camera Disabled

Purpose: Blocks or restores camera use device-wide. Fields: Camera use — Disable or Allow (new action default: Disable). Requirements: Android 6.0 / API 23+ and Device Owner. This policy affects all apps.

8. Set Screen Capture Disabled

Purpose: Prevents or permits screenshots and screen recording under Android's screen-capture policy. Fields: Screen capture — Disable or Allow (new action default: Disable). Requirements: Android 6.0 / API 23+ and Device Owner.

9. Set Lock Screen Message

Purpose: Sets administrator/contact text displayed on Android's lock screen. Fields: Lock screen message — up to 500 characters; leave empty to clear the current message. Requirements: Android 7.0 / API 24+ and Device Owner. Placement and styling vary by device.

10. Set Maximum Time To Lock

Purpose: Sets the maximum inactivity interval before Android locks the device. Fields: Maximum inactivity — choose No maximum, 30 seconds, 1, 5, 10, or 30 minutes; or enter Custom duration (seconds) from 0 to 86,400. Zero removes the maximum. Requirements: Device Owner. This does not configure a PIN/password or lock the device immediately.

11. Set User Restriction

Purpose: Adds or removes one Android user restriction. Fields: Restriction — select an available policy; Selected restriction — Add restriction or Clear restriction. New action default: Block Factory Reset is selected for adding. Options depend on the connected device's Android version. Restrictions can block important settings and device management capabilities; only the selected restriction is changed.

12. Set Bluetooth State

Enables or disables Bluetooth through APSBridge. Fields: Bluetooth — Enabled or Disabled (new action default: Enabled). Requirements: APSBridge installed, current, and registered as Device Owner; Android 6.0 / API 23+. APSBridge requests the adapter state change and waits up to seven seconds for the requested state. This differs from Set Wi-Fi State, which uses ADB shell and does not require Device Owner.

Apps

13. Hide / Show Application

Purpose: Hides or shows an installed package without uninstalling it. Fields: Android package; Application visibility — Hide or Unhide (new action default: Hide). Requirements: Device Owner. Hiding can remove the app from launchers and make it unavailable to the user while its package/data remains installed. Showing reverses this policy.

14. Suspend / Resume Applications

Purpose: Suspends or resumes one or more installed packages. Fields: Applications — one Android package per line; Application availability — Suspend or Resume (new action default: Suspend). Requirements: Android 7.0 / API 24+ and Device Owner. A suspended app is unavailable to the user and may not run normally; resuming restores its availability. This is distinct from disabling or uninstalling an app.

15. Block / Allow App Uninstall

Purpose: Controls whether the user may uninstall a package. Fields: Android package; App uninstall — Block or Allow (new action default: Block). Requirements: Device Owner. Blocking uninstall does not install, hide, or suspend the app. Turning the block off permits normal uninstall behavior again.

16. Set Application Restrictions

Purpose: Sends managed configuration values to an app that supports Android managed configurations. Fields: Android package; Managed configuration JSON — a JSON object (new action default {}). Supported values include strings, booleans, numbers, string arrays, nested objects, and arrays of objects. Requirements: Device Owner and an app that declares matching managed configuration keys. The target app defines valid keys and values. {} clears the configured values.

17. Set Runtime Permission

Purpose: Sets one runtime permission for an installed app through the managed Device Owner policy. Fields: Android package; Android runtime permission (for example android.permission.CAMERA); Permission state — Default / user controlled, Grant, or Deny. New action default: CAMERA is set to Grant. Default returns handling to Android/user control. Requirements: Device Owner and an applicable Android runtime permission. For the ADB-based alternative, see Grant / Revoke Permission.

18. Set Runtime Permission Policy

Purpose: Sets the default handling of runtime permission requests. Fields: Default runtime permission policy — Default / Prompt, Automatically Grant, or Automatically Deny (new action default: Default / Prompt). Requirements: Device Owner. This governs requests globally, while Set Runtime Permission sets one permission for one app.

19. Keep Uninstalled Packages

Purpose: Tells Android to retain data/package state for listed packages after they are uninstalled, where Android supports it. Fields: Packages to retain — package IDs, one per line; an empty list clears the policy (new action default is empty). Requirements: Android 9 / API 28+ and Device Owner. It does not prevent uninstall and does not itself reinstall an app.

Network & Certificates

20. Set Always-On VPN

Purpose: Selects an installed VPN app as Android's always-on VPN provider. Fields: VPN application; VPN lockdown on/off (new action default off); on Android 10+, optional Lockdown bypass allowlist — package IDs allowed network access outside the VPN. Requirements: Android 7.0 / API 24+, Device Owner, and an installed app implementing Android's VPN service. Lockdown blocks network traffic outside the VPN except packages in the supported bypass list. Disabling lockdown allows traffic when the VPN is disconnected.

21. Clear Always-On VPN

Purpose: Removes the Device Owner always-on VPN provider configuration. Fields: none. Requirements: Android 7.0 / API 24+ and Device Owner. It does not uninstall the VPN app or remove unrelated VPN profiles.

22. Install CA Certificate

Purpose: Installs a local X.509 CA certificate as a managed trust anchor. Fields: X.509 CA certificate — choose a .cer, .crt, .pem, or .der certificate file. Requirements: Device Owner and a valid CA certificate. Only install certificates from a source you trust; apps that use Android's system trust store may trust certificates signed by this CA.

23. Remove CA Certificate

Purpose: Removes a managed CA certificate from the device trust store. Fields: X.509 CA certificate — select the same certificate file that was installed. Requirements: Device Owner. It removes that managed certificate, not unrelated certificates.

24. Install Client Certificate / Key Pair

Purpose: Installs a client identity for apps/services that use Android KeyChain. Fields: Client certificate / chain — X.509 certificate/chain; PKCS#8 private key — matching private key; Key alias — 1–100 letters, numbers, dots, underscores, or hyphens; User selectable — whether the user may choose this credential. Requirements: Android 9 / API 28+, Device Owner, matching certificate and PKCS#8 key, and Android KeyChain ready to accept credentials.

25. Remove Client Key Pair

Purpose: Removes a managed client key pair by alias. Fields: Key alias used when the pair was installed. Requirements: Android 7.0 / API 24+ and Device Owner. It removes only the matching managed credential.

26. Set / Clear Global HTTP Proxy

Purpose: Applies or clears the Device Owner global HTTP proxy. Fields: Global HTTP proxy — Clear proxy or Configure proxy; when configuring: Proxy host, Proxy port (1–65535), and Exclusion list (one host/domain pattern per line, without spaces or commas). Requirements: Device Owner. A proxy is not a VPN; apps that do not use Android's system proxy may not route traffic through it. Clear removes this managed proxy configuration.

System

27. Set System Update Policy

Purpose: Controls Android system update installation behavior. Fields: Update policy — Default / clear policy, Automatic, Windowed, or Postpone (new action default is Default / clear policy). For Windowed, set Window start and Window end as local clock times. Requirements: Device Owner. Android's update service controls whether an update is available; Windowed times define its maintenance window.

28. Set System Update Freeze Periods

Purpose: Defines recurring calendar periods during which Android system updates are frozen. Fields: one or more start/end month-and-day dates; remove all periods to clear the policy. February 29 is not accepted. Each period may be at most 90 days and periods must not overlap and must be at least 60 days apart. Requirements: Android 9 / API 28+ and Device Owner. Dates recur annually, not on one specific year.

29. Set Automatic Time

Purpose: Requires or releases automatic network-provided time. Fields: Automatic time — Require automatic time or Release policy (new action default: Require automatic time). Requirements: Device Owner. Releasing the policy lets Android/device settings determine time behavior; it does not enter a specific time.

30. Set Automatic Time Zone

Purpose: Enables or disables automatic time-zone detection. Fields: Automatic time zone — Enable automatic zone or Disable automatic zone (new action default: Enable automatic zone). Requirements: Android 11 / API 30+ and Device Owner. Use Set Time Zone to choose a fixed zone instead.

31. Set Time Zone

Purpose: Sets a specific time zone. Fields: IANA time zone — for example Europe/Berlin, Europe/Bucharest, or America/New_York (new action default: Europe/Berlin). Requirements: Android 9 / API 28+ and Device Owner. If automatic time-zone control is active, turn it off first.

32. Set Wallpaper

Purpose: Applies an image as the Home screen wallpaper, Lock screen wallpaper, or both. Fields: Wallpaper image — non-empty PNG, JPEG, or WebP image up to 25 MB; Apply to — Home screen, Lock screen, or Home and Lock screens. Requirements: Android 7.0 / API 24+ and Device Owner. The device may crop/scale the image to fit its display.

Dangerous

33. Wipe Device / Factory Reset

Purpose: Erases the managed device. Fields: Reason shown to the user (optional, up to 200 characters); Wipe external storage; Wipe reset-protection data. Requirements: Device Owner. This is destructive and removes user data; the device disconnects when reset begins. External storage and reset-protection data are included only when their options are selected. APS asks for separate confirmation immediately before profile deployment. Confirm the target device before running.

Apps

34. Install APK

Purpose: Installs one or more APK files on the target using ADB package installation. Fields: APK files (choose one or more); Replace existing application (default on); Allow version downgrade (default off); Grant runtime permissions (default off). Requirements: connected and authorized ADB device; compatible APK. APS does not enforce an Android 9 / API 28 minimum for this action. Downgrade and permission flags are passed to Android's package installer, which may reject them for the package or OS. Replacing an installed app generally requires a matching signing identity.

35. Launch App

Purpose: Launches an installed app. Fields: Android package name. The package must be installed, enabled, and have a launchable activity. Launching does not install or unlock the app.

36. Force Stop App

Purpose: Stops the app's running processes. Fields: Android package name. The app can start again through user interaction, system events, or a later Launch App action. This does not clear its data.

37. Clear App Data

Purpose: Clears the app's private data and resets it to a first-run state. Fields: Android package name. This is destructive to the app's local settings, accounts, databases, and files in its private data area. It does not uninstall the app; confirm the package before running.

38. Enable App

Purpose: Enables an installed package that Android currently marks disabled. Fields: Android package name. This restores the package's availability but does not launch it.

39. Disable App

Purpose: Disables an installed package. Fields: Android package name. Android may prevent disabling essential system packages; a disabled app cannot be launched normally until enabled again.

40. Uninstall App

Purpose: Removes an app package. Fields: Android package name; Keep app data on/off (default off). When enabled, APS passes Android's keep-data uninstall option; when off, Android removes the package's data as part of uninstall. Uninstall cannot be undone by this action; reinstall the app to use it again.

41. Open App Info

Opens Android's App Info screen for the app selected in the Apps view. Fields: none; select an app first. This opens settings for interactive use and does not itself change app settings.

Files

All device-side paths must be valid paths accessible through ADB. Transfer access depends on Android version, storage permissions, and OEM restrictions. Folder actions copy recursively.

42. Push File

Copies one local file to the device. Fields: Local file (existing computer file); Device destination path (destination filename/path). Ensure the destination parent exists and is writable.

43. Push Folder

Copies a local folder and its contents recursively to the device. Fields: Local folder; Device destination path (destination folder). The folder contents are copied beneath the specified destination; check paths to avoid copying into an unintended location.

44. Pull File

Copies one device file to the computer. Fields: Device file path; Local destination path (local output file or destination selected in the editor). The source must exist and be readable through ADB.

45. Pull Folder

Copies a device folder and its contents recursively to the computer. Fields: Device folder path; Local destination path (computer destination folder). Ensure sufficient local disk space.

46. Create Folder

Creates a device folder, including missing parent folders. Fields: Device folder path. Existing directories may remain as-is; the path must not point to a protected/unwritable location.

47. Move / Rename Path

Moves or renames a device file or folder. Fields: Source device path; Destination device path. Source must exist; destination parent must be writable. Moving across filesystems may not be supported. This changes the original path rather than making a copy.

48. Delete Path

Permanently deletes a device file or folder. Fields: Device path. APS requires explicit confirmation for immediate deletion; profile execution uses the configured path. This cannot be undone. Avoid broad or system paths; APS validation blocks unsafe root paths.

Display

49. Set Brightness

Sets the screen brightness level. Fields: Brightness (0–100%); Disable adaptive brightness before applying. The level is stored as a manual brightness value. When that checkbox is selected, APS also turns automatic brightness off before applying the level; when it is not selected, APS leaves the automatic brightness mode unchanged. The default profile level is 80% and the checkbox is selected.

50. Set Auto Brightness

Enables or disables Android automatic brightness. Fields: Automatic brightness — on/off. This changes the same automatic-brightness mode that Set Brightness can turn off with its profile checkbox. To use auto brightness, enable it here; a later Set Brightness with its checkbox selected turns it off again. The default profile setting is on.

51. Set Screen Timeout

Sets inactivity time before the screen turns off. Fields: Timeout value and Unit — seconds or minutes; minimum 1 second and maximum 24 hours. Presets range from 15 seconds to 30 minutes. The new action default is 2 minutes. This is separate from device sleep or power-off, but Keep Screen Awake may supersede the timeout.

52. Keep Screen Awake

Enables or disables Android's screen stay-awake behavior. Fields: Keep Screen Awake — Enable or Disable; Power sources — when enabled, choose one or more of USB, AC charger, and Wireless charger. Existing profiles without the new Enable/Disable value continue to behave as Enable.

When enabled, APS sets Android's stay-awake-while-plugged-in policy for the selected sources, runs the stay-awake override for devices that do not report a power source, and raises the screen timeout to Android's maximum value. When disabled, APS turns off the stay-awake override, clears the selected-source policy, and removes the screen-timeout override so Android uses its default. APS does not save or restore the timeout that was set before enabling. After disabling, you may also want to apply Set Screen Timeout again to choose your desired normal screen-off timeout.

53. Set Orientation

Locks display orientation. Fields: Orientation — Portrait, Landscape, Reverse portrait, or Reverse landscape. Applying it disables automatic rotation, sets the chosen rotation, and restarts the Home launcher. Use Set Auto Rotate afterward to enable sensor-based rotation again. The default profile orientation is Landscape.

54. Set Auto Rotate

Enables or disables sensor-based rotation. Fields: Automatic rotation — on/off. This changes the same rotation mode Set Orientation disables. Applying this action restarts the Home launcher. It does not select a fixed orientation. The default profile setting is off.

55. Set Animation Scale

Sets Android window, transition, and animator duration scales. Fields: Animation mode — Animations off, Reduced, Normal, or Custom; Custom exposes Window animation scale, Transition animation scale, and Animator duration scale, each selectable from 0, 0.25, 0.5, 0.75, 1, 1.5, 2, 5, and 10×. 1× is normal, 0× disables that animation, below/above 1× is faster/slower. New action default is Animations off. This affects visual animation timing, not app processing speed.

56. Display Density / DPI

Applies a display density override or resets to Android's default. Fields: Density (DPI) — integer 72–1000, or reset/default to remove the override. Higher/lower density changes the logical size of interface elements. Extreme values can make controls unusable.

57. Display Resolution

Applies a display resolution override or resets to the Android default. Fields: Width and Height — both integer pixel dimensions from 320 to 10,000, or reset both to default. Enter both dimensions together. The physical panel resolution is not changed.

58. Font Scale

Sets Android system font scaling. Fields: Font scale — 0.5 to 3; 1 is the normal size, smaller/larger values reduce/enlarge system text. Apps that use custom typography may not follow it exactly.

59. Light / Dark UI Mode

Sets Android UI appearance. Fields: Automatic, Light, or Dark. Automatic follows Android's configured schedule/system setting; apps must support Android's night mode to fully adapt.

60. Autohide System Bars

Enables/disables automatic hiding of Android status and navigation bars. Fields: Autohide on/off. When enabled, normal system gestures can temporarily reveal the bars; this is not a security boundary or a replacement for kiosk policy.

Device

61. Set Device Name

Changes the Android device name stored in global system settings. Fields: Device Name (required, up to 64 characters; surrounding whitespace is trimmed). It does not change manufacturer, brand, or model. Some Android screens may show other device labels.

62. Set Multiple Device Name

Assigns sequential names across targets using the device order captured when deployment starts. Fields: Prefix (required); Start at (positive first sequence number); Digits (1–64, minimum zero-padding width). Generated names may not exceed 64 characters. Example: prefix Store-, start 7, digits 3 produces Store-007, Store-008, etc. The sequence is recalculated per deployment. Profile-only.

63. Reboot

Restarts Android normally. Fields: none. The device disconnects temporarily. Put Wait for Device, then usually Wait for Boot Completion, after it if later actions must run after restart.

64. Reboot to Recovery

Restarts into recovery mode. Fields: none. Android ADB profile actions generally cannot continue while the device remains in recovery; the user may need to return the device to Android and reconnect it.

65. Reboot to Bootloader

Restarts into bootloader/fastboot mode. Fields: none. Standard Android ADB actions generally cannot continue in this mode. Use only when the device's bootloader workflow is intended.

66. Wake Device

Wakes the screen if asleep. Fields: none. It does not unlock the device or bypass a secure lock screen.

67. Sleep Device

Turns off the display and places the device in its normal sleep state. Fields: none. The device remains powered on; this is not shutdown.

68. Lock Device

Triggers Android's current screen-lock behavior. Fields: none. It does not create/change credentials. Whether a secure prompt appears depends on the existing lock configuration and policy.

Input & Sound

69. Set Volume

Sets media-stream volume. Fields: Volume (0–100) — integer percentage. Android maps the percentage to the device's available volume steps; it does not set ringtone/alarm volume. The default profile value is 50.

70. Mute Volume

Mutes the media volume. Fields: none. It affects media playback; it does not necessarily mute calls, alarms, or other audio streams.

Network

71. Set Wi-Fi State

Enables or disables Wi-Fi using the Android ADB shell Wi-Fi service command. Fields: Wi-Fi — Enabled or Disabled (new action default: Enabled). Requirements: connected and authorized ADB device; APS does not require APSBridge or Device Owner for this action. This changes the radio state; it does not select or connect to a network. Android may reject the shell request if shell permissions do not allow the operation.

72. Open Wi-Fi Settings

Opens Android Wi-Fi settings for interactive use from Device Actions. Fields: none. The user can inspect/select a network; opening this screen does not itself enable Wi-Fi or connect to a network.

73. Open Bluetooth Settings

Opens Android Bluetooth settings for interactive use from Device Actions. Fields: none. The user can interact with settings; this does not itself change Bluetooth state.

Advanced

Advanced actions can change system state or execute arbitrary commands. Use only values/commands you understand. They require the selected device to be ADB-accessible.

74. Run ADB Command

Runs custom ADB arguments against the selected device. Fields: ADB arguments — enter arguments after the device target is selected (for example shell getprop ro.product.model). Do not include adb or the device serial. This advanced command can change or erase device data.

75. Run Shell Command

Runs a custom Android shell command on the device. Fields: Shell command — command text without adb shell (for example getprop ro.product.model). Available privileges are those of the ADB shell; this is not automatically root. Commands may be destructive or device-specific.

76. Input Text

Types text into the currently focused Android input field. Fields: Text. First focus the intended field; this does not choose a field or submit a form. Android input injection may not represent every character identically on all keyboards/devices.

77. Generic Keyevent

Sends an Android keyevent. Fields: Android key code — integer from 0 to 999 (examples: Home 3, Back 4, Enter 66, Power 26). Key events can trigger navigation or destructive UI controls.

78. Start Activity / Intent

Starts an Android activity through an intent. Fields: Intent action; optional Component; optional Data URI. At least an action or component is required. Example action: android.intent.action.VIEW; example component: com.company.app/.MainActivity. Android may reject a component or intent that is unavailable to the caller.

79. Grant / Revoke Permission

Grants or revokes one app runtime permission through ADB. Fields: Package; Permission; Grant permission on/off. The package must be installed and the permission must be runtime-grantable on that Android version. This runs ADB package-manager permission commands, while Set Runtime Permission uses the Device Owner policy.

Manual Controls

These immediate controls appear in the Manual Controls subsection of Device Actions; they are not Profile Actions.

80. Take Screenshot

Captures the selected device screen and saves the image in the APS workspace. Fields: none. The connected device must support Android screen capture through ADB.

81. Home

Sends one Home navigation command to the selected device. Fields: none. Android navigation and kiosk policy can limit the result.

82. Back

Sends one Back navigation command. Fields: none. The current app/screen determines the result.

83. Recent Apps

Opens Android's Recent Apps screen. Fields: none. Android navigation and kiosk policy can restrict access.

84. Power Off Device

Powers off the selected device. Fields: none. The device disconnects from APS and must be powered on manually.

Workflow (Profile-only)

These actions control timing/connection between profile steps; they are not immediate Device Actions.

85. Delay

Pauses the workflow before continuing. Fields: Duration (time). Choose enough time for the preceding operation to take effect; this is a fixed pause and does not check device state.

86. Wait for Device

Waits for the target to become available through ADB. Fields: Timeout; Poll interval (how often APS checks). If it does not reconnect before timeout, the action fails and the deployment cannot proceed normally. It checks ADB connectivity only, not whether Android has finished booting.

87. Wait for Boot Completion

Waits until Android reports that boot has completed. Fields: Timeout; Poll interval. Usually place after Wait for Device because ADB can reconnect before Android is ready. Timeout expiration means boot completion was not observed within the configured period.

9. Troubleshooting

This chapter covers common problems with device connections, APSBridge, Profiles, Deployments, files, and Logcat.

When a problem affects a specific device, first confirm that the correct device is selected and shown as Online in the APS sidebar.

Device connection problems

Device does not appear in APS

Make sure the Android device is connected using a USB data cable and is unlocked. Confirm that USB debugging is enabled in Android Developer Options, then reconnect the device and select Refresh Devices in the APS sidebar.

Some USB cables provide power only and cannot transfer data. If the device still does not appear, try a known data cable or another USB port.

Device is shown as Unauthorized

An Unauthorized device has not authorized the computer for USB debugging.

Unlock the Android device and accept the USB debugging authorization prompt. APS cannot accept this prompt on the device for you.

After authorization, refresh the device list and wait for the device to appear as Online.

Device is shown as Offline

An Offline device has been detected but is not currently available for communication.

Disconnect and reconnect the device, check the USB cable and connection, and refresh the device list. Wait until the device is Online before running actions or including it in a Deployment.

Devices may also appear temporarily offline while Android is restarting.

Device information and APSBridge

Some device information is unavailable

Device information is loaded when a device is selected, and individual sections may finish loading at different times.

Wait briefly, then select Refresh Device Information from Device → Overview.

The information available can vary between Android versions and device manufacturers. APSBridge can provide additional information where supported, so a missing value does not necessarily indicate a connection problem.

APSBridge controls are unavailable

Some device-management actions require APSBridge and specific Android management capabilities.

Check the APSBridge status under Device → Overview → System and review the requirements shown for the action you want to use.

Having APSBridge installed does not make every managed action available. Supported capabilities can depend on the Android version, device manufacturer, and current device-management state.

APSBridge setup does not complete

Review the message displayed by APS and confirm that the intended device is Online and meets the requirements for the selected setup.

Existing accounts, additional users, work profiles, or another device-management configuration may prevent Android from allowing the requested management setup.

Do not factory-reset a device solely in response to a setup error. A factory reset removes device data and should only be performed when it is an intentional part of the provisioning or recovery process.

Profiles and Deployment problems

A Profile cannot be edited

The Profile may be locked.

Select the Profile and use Unlock before changing its configuration, actions, or action order.

An action cannot be added or configured

Review the action settings and complete all required fields. Check package names, file paths, entered values, and any compatibility or validation information displayed by APS.

Some actions may also depend on capabilities that are not available on every Android device.

Start Deployment is unavailable

Confirm that:

• a valid Profile is selected,
• at least one target device is selected and Online, and
• the Profile contains at least one enabled action.

The target devices selected in Deploy are independent of the device currently selected for direct work elsewhere in APS.

A Deployment fails or stops partway through

Expand the affected device in Deploy and review its action results and Live Log.

If an action fails, APS skips the remaining actions for that device. Other target devices continue independently.

Before starting another Deployment, review which actions were already completed. Correct the device issue or update the Profile as required before repeating the Deployment.

Cancel Deployment does not stop immediately

Cancellation takes effect between actions. An action already in progress may finish before APS stops processing the remaining actions.

Cancellation does not undo actions that have already completed or reverse changes already applied to the device.

Files, applications, and Logcat

A file or APK cannot be found during a Deployment

Check the path configured in the Profile and confirm that the referenced file still exists on the computer running APS.

Moving, renaming, or deleting a referenced file can prevent the corresponding action from completing.

Exporting a Profile stores its configuration but does not include copies of referenced APKs, certificates, images, documents, or other external files. When using the Profile on another computer, make sure the required files are also available.

Access to a device folder is denied

Android restricts access to some system and application directories.

Use an accessible storage location, such as Downloads, when appropriate. USB debugging does not provide unrestricted access to private Android directories.

No Logcat messages are visible

Make sure the device is Online and select Start to begin capturing messages.

Set the log-level filter to All and clear any process, search, or Regex filters that may be hiding entries.

If the Logcat buffer contains entries but the list appears empty, broaden or clear the active filters.

An exported Logcat file cannot be found

Export the Logcat results again and verify the selected save location.

Logcat exports are separate from Deployment Logs and are not automatically stored in the Workspace Deployment Logs folder.

Information for support

When requesting support, provide enough information to identify the problem and reproduce it. Include the exact message shown by APS, the action or workflow that produced it, the device model, Android version, and device serial number when relevant.

For Deployment problems, also include the Deployment ID and the Deployment log when available.

Do not include passwords, credentials, private certificates, or other sensitive information unless it is specifically required to investigate the problem.