Handle INSTALL_FAILED_HYPEROS_ISOLATION_VIOLATION

[MuntashirAkon]

Please check before submitting an issue

• I am using the latest version of App Manager
• I have searched the issues and haven't found anything relevant
• I have read the docs

Describe a description of the new feature

HyperOS 2.0 has introduced a new restriction on which apps can update a system app. So, if you want to update a system application using App Manager, it will fail with the the following message:

INSTALL_FAILED_HYPEROS_ISOLATION_VIOLATION: <installer-app> not allow to install <system-app>

Describe the solution you'd like

Handle these specific cases for HyperOS. There can be many ways to handle this. But the most quick and feasible way would be to simply retry by setting the installer package to something else (e.g. com.android.shell or com.android.fileexplorer) if the error contains this constant value. However, this can only be done with root/ADB.

Describe alternatives you've considered

Setting the installer name temporarily through the installer options. But this is not an efficient way.

Additional context

N/A

[androidacy-user]

Note that in modern Android this doesn't actually fully spoof the source (Android always stores the real source as initiatingPackage even if installerPackage is overridden) so this may not be particularly effective.

[MuntashirAkon]

Note that in modern Android this doesn't actually fully spoof the source (Android always stores the real source as initiatingPackage even if installerPackage is overridden) so this may not be particularly effective.

That's not an issue since Shell is (still) allowed to update the system apps (in privileged mode, initiating package is always set to Shell). Actually, I'm surprised that they're not checking the initiating package instead.

[bhcavusoglu]

I encountered the same problem after the hyperos 2.0 update and this is what I found as a solution and it works without any problems. There are two package managers in hyperos and one of them is completely focused on restriction. Disable or remove the application named "com.miui.packageinstaller" package (with the help of adb shell). Finally, make sure that you allow the restricted settings in the appmanager application settings. In this way, you can continue to use it without any problems. Sorry for my bad English

[MuntashirAkon]

Disable or remove the application named "com.miui.packageinstaller" package (with the help of adb shell).

No side effects at all?

Sorry for my bad English

Most users of App Manager (including me) are not native English speakers. So, you don't need to apologize. Besides, your English is quite good compared to some of the native speakers I find here.

[OlliesGudh]

I encountered the same problem after the hyperos 2.0 update and this is what I found as a solution and it works without any problems. There are two package managers in hyperos and one of them is completely focused on restriction. Disable or remove the application named "com.miui.packageinstaller" package (with the help of adb shell). Finally, make sure that you allow the restricted settings in the appmanager application settings. In this way, you can continue to use it without any problems. Sorry for my bad English

I have encountered the same issue while trying to update System WebView. I had already removed the "com.miui.package installer" through adb and then proceeded to allow the restricted settings as suggested here. Your solution didn't work, I keep getting the same error: "INSTALL_FAILED_HYPEROS_ISOLATION_VIOLATION: io.github.muntashirakon.AppManager not allow to install com.google.android.webview"

I have also updated the stable trichrome library from apkmirror, but still...

[MuntashirAkon]

addfba2