Closed PoneyClairDeLune closed 3 weeks ago
I think somehow you setup the action to launch your device Package Installer by default.
Now when you click on .apk
files from your file manager it should show you both the option. If it still doesn't show, try 3rd party File manager such as Material Files.
offer a dedicated "installer" screen where only a file picker and an installer button are offered.
We do have dedicated FileManager for AM (pre-releases) though.
I've tried to find a way to launch the installer in AppManager directly, but that failed.
What do you mean by "launch the installer in AppManager directly"? Alternatively you can share the apk file to AM "Install" to install via AppManager.
I think somehow you setup the action to launch your device Package Installer by default.
No. I just confirmed that the settings page shows « Aucun paramètre par défaut défini » (No default parameters defined). As long as the package installer is enabled, it will always try to intercept .apk
files.
We do have dedicated FileManager for AM (pre-releases) though.
Hope it will be ready soon!
What do you mean by "launch the installer in AppManager directly"?
Launching the Interceptor and trying to formulate a customized intent to the package installer activity in App Manager. Might have done it incorrectly on my end however.
You can use the “Share” button (if available) or a good file manager such as Material Files (you may need to use the “Open With” option) or MiXplorer. I don't plan on implementing a dedicated page for it since it should be the job of a properly developed file manager.
you may need to use the “Open With” option
The thing is that the ROM itself intercepts and redirects .apk
files to be opened by its own package installer. If that had worked I wouldn't have made this issue at all.
However, the share button served as a pretty nice circumvention mechanism!
The thing is that the ROM itself intercepts and redirects
.apk
files to be opened by its own package installer.
You didn't include your device info, so it's hard to tell. But I don't believe this to be true. A file manager can provide as many options it can by utilising the intent filters (as done by MiXplorer or App Manager beta). It's the file manager or the system “opener” that's causing issues. If you're, say, opening an APK from the browsers “Download” section or Android-default “Files” app, it may directly lead to the system installer in some ROMs because the system opener is configured to do that.
Please check before submitting an issue
Describe a description of the new feature
Some devices only have vendor ROMs available, and they will attempt at hijacking opening
.apk
files. By offering a dedicated installer screen in AppManager, this can be bypassed entirely for users with root.Describe the solution you'd like
Like "running apps" and "log viewer", offer a dedicated "installer" screen where only a file picker and an installer button are offered.
Describe alternatives you've considered
Additional context
No response