Testing report: OnePlus 11

[NovigradWitcher]

• OS: OOS 16 (based on Android 16)
• Model: 8/128

What works fine:

• Setting up a work profile using Harbor in the main profile
• Freezing/unfreezing apps
• Transferring files from personal to work

Issues

• No ADB Shell access to work profile
• No work to personal file transfer (but you mentioned that as a current limitation)
• Cannot install apps in the work profile through an apk from the personal profile - I must either transfer the files into the work profile, or use an app store installed inside the work profile (Obtainium, F-Droid, Aurora Store etc.)
• Add to launcher shortcuts not working on my launcher (Niagara Launcher). Doesn't seem like a launcher issue since adding shortcuts work for every other app.

Overall status (imo)

• I have been daily driving this for a week, since I like to keep my work apps separate.
• The issues I mentioned are QoL features I would like fixed, but no impedance in daily usage.
• I would recommend you look at Insular or Island since those are the only work profile apps I know which allow shell/ADB access to the work profile.

[Stem0794]

@NovigradWitcher Thanks for the detailed report.

Could you add a few details?

• Exact Harbor version.
• Exact OxygenOS build and Android security patch.
• Niagara Launcher version.
• For ADB access: the exact command you tried and the complete error message. Also, do you mean external USB/wireless ADB or Harbor’s Shizuku tools?
• For shortcuts: does Niagara show a pin-confirmation prompt? Does Harbor display “This launcher cannot pin Harbor shortcuts”?
• If possible, could you temporarily switch to the OxygenOS launcher and try the same shortcut once? That would help isolate whether this is Harbor’s shortcut request or Niagara’s handling of Work-profile shortcuts.

The current APK workflow copies the file into the Work profile, after which it must be opened from Work Files or another Work app. Harbor’s “Install APKs” control only removes the Work-profile restriction; Android still requires consent for the app requesting installation. A direct “transfer and open installer” flow would be a separate enhancement.

Work-to-Personal file transfer is also still a known limitation.

Please don’t include an IMEI, serial number, account address, or other personal information.

[NovigradWitcher]

• Harbor version: 0.2.0-alpha-6
• Exact OOS build: CPH2447_16.0.5.1002(EX01B90P01)
• Android Security patch - 1 July 2026
• Niagara Launcher version - 1.16.27
• ADB Access - Tried external wireless ABD tools. Harbor can access Shizuku i.e. Harbor Shizuku tools page opens fine - but there's only one option - of multiple full-user workspaces (to create a new user). Don't know if I can do anything else with this? Can I use on device Shizuku apps inside the work profile, or Shizuku based tools inside the user profile can access work profile apps?
• No, niagara does not show any prompt, Harbor also does not show anything. Just the app minimises. Same with OnePlus's system launcher.
• A direct transfer and open installer flow would be a much needed enhancement imo. Some people might use the work profile for app isolation (like me) - in this case we're not signing into the play store. So sideloading additional stores (Obtainium/Aurora Store/F-Droid) becomes necessary.

[Stem0794]

@NovigradWitcher Thanks, this narrows it down considerably.

The Shizuku screen behavior is expected: when Advanced tools are opened from Personal Harbor, Harbor shows the experimental full-user workspace controls.

Open the work-badged Harbor app and select Advanced there; you should see Clone an installed package. This can ask Android to install an app already present in Personal into Work with fresh app data. Please try it with F-Droid or Obtainium and share the exact message Harbor displays. Android 16 may deny the cross-user package command even when Shizuku is connected, but OxygenOS needs to be tested directly.

Shizuku-compatible apps can also be installed inside the work profile and request their own Shizuku permission. Shizuku includes handling for managed-profile permission requests, with confirmation managed through its primary-user app. A Shizuku app running in Personal does not automatically gain access to Work apps; it must explicitly support cross-user operations, and OxygenOS must permit the requested shell operation. Each app and profile has its own authorization.

Harbor deliberately does not provide an unrestricted ADB shell. For the external wireless ADB problem, I would still need the name of the tool and its exact command or error to determine whether OxygenOS is blocking access to the work-profile user.

Since shortcut creation fails with both Niagara and the OnePlus launcher, this is not specific to Niagara. Harbor submits Android’s standard pinned-shortcut request, but OxygenOS appears to discard it without displaying the confirmation UI. I’ll treat this as a OnePlus/OxygenOS compatibility problem and investigate better failure detection or a fallback.

I agree about the APK workflow. A useful enhancement would combine select/transfer APK → open Android’s installer inside Work, while retaining Android’s normal confirmation and per-source permission. That would make installing F-Droid, Obtainium, or Aurora Store possible without signing into Play Store or manually finding the copied APK.

[Stem0794]

@NovigradWitcher I’ve implemented these improvements in Harbor 0.2.0-alpha07.

• Sending exactly one APK from Personal to the work-badged Harbor target now copies it into Work Downloads/Harbor and immediately opens Android’s package installer. Android still controls unknown-source authorization and the final install confirmation.
• Shortcut requests now use a stable app-bound ID and a valid Android launch intent. Harbor also keeps an on-screen result with Try again when you return to the Work app, including when a launcher accepts the request but shows no confirmation.
• Personal Advanced now points to the work-badged Harbor app for Clone an installed package.

I validated the APK transfer end to end on a Galaxy S24 running Android 16: Harbor remained the Work profile owner, the APK reached Work storage, and the Work package installer opened with a read-only content grant. I also reproduced the shortcut failure, fixed an Android 16 intent error, and then confirmed that One UI showed its Add to Home screen? prompt and that Harbor’s status survived reopening the Work app.

OxygenOS still needs verification on your OnePlus 11. Could you update to alpha07 and try:

1. Share one APK from Personal and choose the work-badged Harbor target.
2. In work-badged Harbor, open an app’s menu and choose Add to launcher.
3. Open work-badged Harbor → Advanced and check Clone an installed package.

Please let me know which installer or launcher prompt appears, plus the exact Harbor status shown after the shortcut request.

[NovigradWitcher]

1. Share APK works perfectly, the Android installer prompt appears. Additionally, copying it to Downloads/Harbor requires manually cleaning up the file afterwards, it would be nice if that could be changed (maybe hold the file in a temp directory and run cleanup post installation).
2. Add to launcher is working for Niagara and OnePlus's System launcher.
3. Not able to access advanced tools section in work-badged Harbor as it says Shizuku is not installed. That's probably because I use a Shizuku fork by thedjchi - specifically it has a stealth tool option that installs Shizuku using a changed package name to bypass detection by banking apps and the like. I think Harbor checks for Shizuku using the hardcoded package name - a better approach (and one that will work with all Shizuku forks regardless of the package name) is to check if the Shizuku permission is present. I made a PR for another app here, see if you can use this. Otherwise, thedjchi was kind enough to provide a code snippet inside their fork - which developers can use to detect Shizuku based on the permission, I'll share that.
4. Another bug that I noticed was that clicking on uninstall for an app, inside the work Harbor, does nothing.