Dhizuku¶

ackpine-dhizuku artifact provides a plugin for Ackpine which, when applied, uses Dhizuku to obtain package installer service instead of plain context.getPackageManager().getPackageInstaller(), so that Ackpine can manage sessions on behalf of the active device owner even if your app doesn't have such privileges. This can bypass the requirement for user confirmation for uninstalls and fresh installs, request version downgrades, and use selected uninstall flags.

Dhizuku calls run as the device owner application's UID. They do not run as root, ADB shell, or the Android system. Ackpine therefore exposes only the package installer options applicable to that identity.

Kotlin examples below use APIs from ackpine-dhizuku-ktx artifact. For general plugin usage in session parameters, see Configuration.

Setting up Dhizuku¶

Latest Dhizuku API version:

First of all, if you don't already have Dhizuku support in your app, you need to explicitly add a Dhizuku-API dependency to your build:

[versions]
dhizuku = "see above"

[libraries]
dhizuku-api = { module = "io.github.iamr0s:Dhizuku-API", version.ref = "dhizuku" }

dependencies {
    val dhizukuVersion = "see above"
    implementation("io.github.iamr0s:Dhizuku-API:$dhizukuVersion")
}

Then add an ackpine-dhizuku dependency:

[libraries]
ackpine-dhizuku = { module = "ru.solrudev.ackpine:ackpine-dhizuku", version.ref = "ackpine" }

# Kotlin extensions
ackpine-dhizuku-ktx = { module = "ru.solrudev.ackpine:ackpine-dhizuku-ktx", version.ref = "ackpine" }

dependencies {
    implementation("ru.solrudev.ackpine:ackpine-dhizuku:$ackpineVersion")

    // Kotlin extensions
    implementation("ru.solrudev.ackpine:ackpine-dhizuku-ktx:$ackpineVersion")
}

Initialize Dhizuku and obtain permission before launching an Ackpine session that uses the plugin:

if (!Dhizuku.init(context)) {
    return
}
if (!Dhizuku.isPermissionGranted()) {
    Dhizuku.requestPermission(permissionListener)
    return
}

The plugin supports Android 8.0 (API 26) and newer.

Using the plugin¶

android {
    dependenciesInfo {
        includeInApk = false
        includeInBundle = false
    }
}

To apply the plugin to an install session, just add this to your install parameters configuration:

val session = packageInstaller.createSession(uri) {
    // ...some session configuration...
    dhizuku()

    // Or, if you want to configure some parameters for the plugin
    dhizuku {
        requestDowngrade = true
    }
}

var parameters = new InstallParameters.Builder(uri)
        // ...some session configuration...
        .registerPlugin(DhizukuPlugin.class, DhizukuPlugin.InstallParameters.DEFAULT)
        .build();

// Or, if you want to configure some parameters for the plugin
var dhizukuParameters = new DhizukuPlugin.InstallParameters.Builder()
        .setRequestDowngrade(true)
        .build();
var parameters = new InstallParameters.Builder(uri)
        .registerPlugin(DhizukuPlugin.class, dhizukuParameters)
        .build();

Also, you can use Dhizuku for uninstall sessions:

val session = packageUninstaller.createSession(packageName) {
    // ...some session configuration...
    dhizuku()

    // Or, if you want to configure some parameters for the plugin
    dhizuku {
        keepData = true
        allUsers = true
        systemApp = true
    }
}

var parameters = new UninstallParameters.Builder(packageName)
        // ...some session configuration...
        .registerPlugin(DhizukuPlugin.class, DhizukuPlugin.UninstallParameters.DEFAULT)
        .build();

// Or, if you want to configure some parameters for the plugin
var dhizukuParameters = new DhizukuPlugin.UninstallParameters.Builder()
        .setKeepData(true)
        .setAllUsers(true)
        .setSystemApp(true)
        .build();
var parameters = new UninstallParameters.Builder(packageName)
        .registerPlugin(DhizukuPlugin.class, dhizukuParameters)
        .build();

If Dhizuku is not active, or if Dhizuku permission is not granted for your app, session will fail.

Hidden APIs¶

This plugin initializes hidden Android API exemptions through AndroidX Startup using LSPosed's HiddenApiBypass. In case you have your own additional exemptions:

1. Disable the initializer in AndroidManifest.xml:

   <provider
       android:name="androidx.startup.InitializationProvider"
       android:authorities="${applicationId}.androidx-startup"
       android:exported="false"
       tools:node="merge">
       <meta-data
           android:name="ru.solrudev.ackpine.privileged.HiddenApiExemptionsInitializer"
           tools:node="remove" />
   </provider>
   

2. Add this list to your HiddenApiBypass.setHiddenApiExemptions call:

   HiddenApiBypass.setHiddenApiExemptions(
       "Landroid/content/pm/IPackageManager",
       "Landroid/content/pm/IPackageInstaller",
       "Landroid/content/pm/IPackageInstallerSession",
       "Landroid/content/pm/PackageInstaller",
       "Landroid/os/UserHandle",
       "Landroid/os/ServiceManager"
   )
   

Plugin parameters¶

By default, all flags are disabled.

Dhizuku operations only target the current Android user (unlike Shizuku and libsu plugins), because device owner identity doesn't give access to cross-user operations on its own without android.permission.INTERACT_ACROSS_USERS_FULL permission, which has signature|installer|role protection levels.

Install flags¶

requestDowngrade¶

Indicates that an upgrade to a lower version of a package than currently installed has been requested.

Ackpine sets downgrade-request flag which is honored for debuggable installed apps or debuggable OS builds, but does not add the unrestricted downgrade permission flag used by root, shell, or system identities. The device owner must still be authorized by Android to perform the downgrade, so setting this option does not guarantee that a downgrade will succeed.

This is a delicate API.

Uninstall flags¶

keepData¶

Flag parameter to indicate that you don't want to delete the package's data directory.

allUsers¶

Flag parameter to indicate that you want the package deleted for all users.

systemApp¶

Flag parameter to indicate that a system app should be marked as uninstalled for the current user.

This does not remove the app from the system partition. For an updated system app, it prevents the update from being rolled back globally when uninstalling it for the current user.

Capabilities¶

DhizukuPlugin implements InstallCapabilityProvider and UninstallCapabilityProvider, so you can query whether individual Dhizuku install/uninstall parameters are supported for a given configuration via getCapabilities(). See Querying capabilities for an overview of the capabilities API.

Each field in DhizukuInstallCapabilities mirrors the corresponding DhizukuPlugin.InstallParameters flag and reports whether it is supported for the resolved configuration. Similarly, DhizukuUninstallCapabilities mirrors DhizukuPlugin.UninstallParameters.

val capabilities = PackageInstaller.getCapabilities(InstallerType.SESSION_BASED, DhizukuPlugin::class)
val dhizukuCaps = capabilities.plugin(DhizukuPlugin::class) ?: return
if (dhizukuCaps.requestDowngrade.isAvailable) {
    // The plugin can request a downgrade for this configuration
}

var capabilities = PackageInstaller.getCapabilities(InstallerType.SESSION_BASED, DhizukuPlugin.class);
var dhizukuCaps = capabilities.plugin(DhizukuPlugin.class);
if (dhizukuCaps != null && dhizukuCaps.getRequestDowngrade().isAvailable()) {
    // The plugin can request a downgrade for this configuration
}

For uninstall:

val capabilities = PackageUninstaller.getCapabilities(UninstallerType.PACKAGE_INSTALLER_BASED, DhizukuPlugin::class)
val dhizukuCaps = capabilities.plugin(DhizukuPlugin::class) ?: return
if (dhizukuCaps.keepData.isSupported) {
    // keepData is effective on this device
}

var capabilities = PackageUninstaller.getCapabilities(UninstallerType.PACKAGE_INSTALLER_BASED, DhizukuPlugin.class);
var dhizukuCaps = capabilities.plugin(DhizukuPlugin.class);
if (dhizukuCaps != null && dhizukuCaps.getKeepData().isSupported()) {
    // keepData is effective on this device
}