Amazefilemanager: Access file from SAF

Created on 16 Jun 2019  路  7Comments  路  Source: TeamAmaze/AmazeFileManager

I use Shelter to manage work profile. Shlter provide access to work profile with SAF. I can access file in work profile with stock file manager but not with Amaze. Could you please provide a function to access file from SAF? Thanks anyway!

Issue-Feature

All 7 comments

Hmm... interesting. I too agree we should use SAF as much as possible. But before that I couldn't even get Amaze to clone into the work profile in Shelter.

Nexus 5x running AOSPExtended (9.0), as well as Pixel 3 emulator running stock 9.0. But I may try with other Android versions in emulator too.

Shelter provide access from personal profile to work profile with SAF so you don't need to clone Amaze into work file. Jusr enable file transfer in Shelter then you can access file in work profile from Documents UI.

Continue test on LG Nexus 5x running AOSPExtended (9.0).

I remember I was able to make Amaze to appear in Shelter/Work profile on one occasion, but I needed to uninstall Shelter afterwards to verify some other PR, so... :(

Anyway, with File Shuttle enabled, in DocumentsUI while in Shelter, when I tried to open an archive which is supported by Amaze but not DocumentsUI, I got

2019-07-01 11:12:41.930 813-3215/? I/ActivityManager: START u0 {act=android.intent.action.VIEW dat=content://com.android.externalstorage.documents/document/primary:Download/node-v10.16.0.tar.gz typ=application/octet-stream flg=0x3} from uid 1010042

Maybe it's something we may start looking into?

Sidenote: interesting message when attempted to install/clone Amaze into Shelter

2019-07-01 11:27:31.066 813-895/? I/PackageManager: Verification timed out for file:///data/app/vmdl516529562.tmp
2019-07-01 11:27:31.067 813-895/? I/PackageManager: Continuing with installation of file:///data/app/vmdl516529562.tmp
2019-07-01 11:27:31.101 813-895/? W/PackageParser: Ignoring duplicate uses-permissions/uses-permissions-sdk-m: android.permission.READ_EXTERNAL_STORAGE in package: com.amaze.filemanager.debug at: Binary XML file line #48
2019-07-01 11:27:31.105 813-895/? W/PackageManager: installPackageLI
2019-07-01 11:27:31.110 505-2175/? E/installd: Failed to delete /data/app/vmdl516529562.tmp: No such file or directory
2019-07-01 11:27:31.121 813-3205/? I/ActivityManager: START u10 {dat=file:///data/user_de/10/com.google.android.packageinstaller/no_backup/package8962550192651936629.apk flg=0x2000000 cmp=com.google.android.packageinstaller/com.android.packageinstaller.InstallFailed (has extras)} from uid 1010019

As I'm not a developer, I can't provide any help... Hope it's not too difficult and thanks again! :+1:

I remember I was able to make Amaze to appear in Shelter/Work profile on one occasion, but I needed to uninstall Shelter afterwards to verify some other PR, so... :(

OK, got the trick. From https://developer.android.com/work/managed-profiles#testing_apps

If you manually install an app over a USB cable to a device which has a work profile, the app is installed on both the personal and the work profile.

We do need to pivot to using SAF sometime in the future. Google is enforcing the use of Storage Access Framework in 2020.

Also, related to #1700.

Surely do. And a long way to go... :/

Was this page helpful?
0 / 5 - 0 ratings

Related issues

DoctorD90 picture DoctorD90  路  3Comments

disdagithubacc picture disdagithubacc  路  4Comments

TjrGithub picture TjrGithub  路  5Comments

organik1 picture organik1  路  5Comments

staltz picture staltz  路  3Comments