Walkthrough - Android 16 (API 36) Work Profile Setup & Run

This developer guide provides step-by-step instructions on how to set up an Android 16 Work Profile (Managed Profile) on an emulator using command-line tools (adb), install the NTP DIG PING MORE application inside the work profile, and run/debug it.

Prerequisites

Before starting, ensure that:

1. You have the Android SDK installed and adb is available in your shell's PATH.
2. An Android Emulator running Android 16 (API 36) is booted and connected to ADB.
3. You have the Test DPC APK (testdpc.apk) and the project's debug APK (app-debug.apk) available locally.

Step 1: Launch and Reset the Android 16 Emulator

Start the Android 16 emulator using wiped user data to guarantee a clean environment:

emulator -avd Medium_Phone_API_36 -wipe-data

Ensure the emulator is fully booted by verifying:

adb devices
# Output should show: emulator-5554	device
 
adb shell getprop sys.boot_completed
# Output should be: 1

Step 2: Create a Work Profile via CLI on Android 16

To create a managed work profile associated with the primary user (User 0), execute the following command:

adb shell pm create-user --profileOf 0 --user-type android.os.usertype.profile.MANAGED "Work Profile"

Expected Output

Success: created user id 10

[!NOTE] The created user ID (typically 10 or higher) will be referred to as USER_ID in all subsequent commands.

Start the newly created profile user:

adb shell am start-user USER_ID

Step 3: Setup Test DPC as the Profile Owner

Test DPC is an enterprise utility used to simulate device policy constraints.

1. Install Test DPC to the managed profile user:

   adb install --user USER_ID testdpc.apk

2. Register Test DPC as the official Profile Owner of the work profile:

   adb shell dpm set-profile-owner --user USER_ID com.afwsamples.testdpc/.DeviceAdminReceiver

Expected Output

Success: Active admin and profile owner set to com.afwsamples.testdpc/.DeviceAdminReceiver for user 10

Step 4: Install the Application in the Work Profile

Install the project's debug APK inside the work profile using the --user flag:

adb install --user USER_ID ./app/build/outputs/apk/debug/app-debug.apk

Expected Output

Performing Streamed Install
Success

Step 5: Launch the Application in the Work Profile

Launch the NTP DIG PING MORE application launcher activity targeting the work profile user:

adb shell am start --user USER_ID -n io.github.mobilutils.ntp_dig_ping_more/.MainActivity

Expected Output

Starting: Intent ( cmp=io.github.mobilutils.ntp_dig_ping_more/.MainActivity )

In the emulator screen, you should now see the application open with a small briefcase badge on the bottom right of its launcher icon and task switcher bar, confirming that it is successfully running inside the secure Work Profile partition on Android 16!

Summary of command used to setup and run the app inside the Work Profile on Android 16

Tracking Android execution and ADB commands for Work Profile setup on Android 16.

Validation Results

We verified that:

1. The profile user was created successfully with ID 10.
2. Test DPC was set as the profile owner.
3. The NTP DIG PING MORE app (io.github.mobilutils.ntp_dig_ping_more) was successfully installed inside user 10 profile.
4. The app successfully launched under the profile user 10.

Here is the captured emulator screenshot verifying that the NTP DIG PING MORE app successfully launched inside the secure Work Profile partition on Android 16:

User Profile	Work Profile