Amazefilemanager: No Write Access to external SD Card

[kspang]

3.1.2 Beta 9

READ is possible but not the WRITE access (new file/folder, delete file, rename file).
Happened on external SD card only.

[VishalNehra]

Please specify more details like android version.

[kspang]

Issue remains the same on 3.1.2RC3.
Device: Samsung Galaxy Note 3 (N9005, HLTE)
OS: Stock Android v5.0

[EmmanuelMess]

SD cards sometimes have a "lock" that's a physical switch.

[kspang]

SD card is writable by es file explorer or camera app.
So, it's not likely caused by SD card switch which is available in normal size SD card instead of micro SD card.

[VishalNehra]

Did you give the required storage access permission from system recents screem when asked?

[kspang]

Such permission dialog is only available for Android 6 or above.
This is Android 5, sd card read/modify/delete permissions were granted upon installation.

[VishalNehra]

@kspang indeed. Can you provide a logcat for every operation you perform. Also, please filter the logcat for Amaze only.

[ildar]

I have the issue. Did the
adb.logcat.txt during:

1. switch to external SD
2. "+" create folder
3. select the storage
4. "+" create folder
5. back to selecting storage

Version 3.1.2 RC3 (F-Droid) on my RR M 6.0.1

[ildar]

boink ?

[Myppomeu]

Lineage OS 14.1 (Android 7)
Amaze file manager v3.2.1 from F-Droid
Have the same problem. Amaze show only read permission. Logcat:

1. Open file with Amaze Text Editor
2. Edit it
3. Save it
4. Return to main window

09-24 23:29:16.511  1100  5622 I ActivityManager: START u0 {act=android.intent.action.VIEW dat=file:///storage/FF7F-1F0C/1.txt typ=text/plain cmp=android/com.android.internal.app.ResolverActivity} from uid 10088 on display 0
09-24 23:29:16.675  1100  1196 I ActivityManager: Displayed android/com.android.internal.app.ResolverActivity: +146ms
09-24 23:29:17.874  1100  1144 I PackageManager: Setting last chosen activity com.amaze.filemanager/.activities.TextReader for user 0:
09-24 23:29:17.874  1100  1144 I PackageManager:   Action: "android.intent.action.VIEW"
09-24 23:29:17.874  1100  1144 I PackageManager:   Category: "android.intent.category.DEFAULT"
09-24 23:29:17.874  1100  1144 I PackageManager:   Type: "text/plain"
09-24 23:29:17.874  1100  1144 I PackageManager:   AutoVerify=false
09-24 23:29:17.879  1100  5622 I ActivityManager: START u0 {act=android.intent.action.VIEW dat=file:///storage/FF7F-1F0C/1.txt typ=text/plain flg=0x13000000 cmp=com.amaze.filemanager/.activities.TextReader} from uid 10088 on display 0
09-24 23:29:18.107  1100  1196 I ActivityManager: Displayed com.amaze.filemanager/.activities.TextReader: +202ms
09-24 23:29:18.736  1100  5658 W ActivityManager: Finishing task with all activities already finished
09-24 23:29:18.737  1100  5658 W ActivityManager: Duplicate finish request for ActivityRecord{b231f24 u0 android/com.android.internal.app.ResolverActivity t458 f}
09-24 23:29:19.774  4304  4304 W InputMethodService: Window size has been changed. This may cause jankiness of resizing window: -1 -> -2
09-24 23:29:19.783  4304  4304 I LatinIME: Starting input. Cursor position = 10,10
09-24 23:29:22.525  5702  5702 D MediaScannerReceiver: action: android.intent.action.MEDIA_SCANNER_SCAN_FILE path: /storage/FF7F-1F0C/1.txt
09-24 23:29:22.541  6207  6229 D conversations: deleted file /storage/emulated/0/Android/data/com.amaze.filemanager/cache/1.txt
09-24 23:29:24.113  1100  1100 W WindowManager: Attempted to remove non-existing token: android.os.Binder@c81234c
09-24 23:29:24.789  4304  4304 W InputMethodService: Window size has been changed. This may cause jankiness of resizing window: -1 -> -2
09-24 23:29:25.999  7114  7114 W IInputConnectionWrapper: finishComposingText on inactive InputConnection
09-24 23:29:26.120  1100  1100 W WindowManager: Attempted to remove non-existing token: android.os.Binder@8094576
09-24 23:29:26.967  1100  5178 I ActivityManager: START u0 {act=android.intent.action.VIEW dat=file:///storage/FF7F-1F0C/1.txt typ=text/plain cmp=android/com.android.internal.app.ResolverActivity} from uid 10088 on display 0
09-24 23:29:27.121  1100  5615 E BitmapFactory: Unable to decode stream: java.io.FileNotFoundException: /data/system_ce/0/recent_images/453_activity_icon_1506277585633.png (No such file or directory)
09-24 23:29:27.143  1100  1196 I ActivityManager: Displayed android/com.android.internal.app.ResolverActivity: +146ms
09-24 23:29:28.157  1100  5631 I PackageManager: Setting last chosen activity com.amaze.filemanager/.activities.TextReader for user 0:
09-24 23:29:28.157  1100  5631 I PackageManager:   Action: "android.intent.action.VIEW"
09-24 23:29:28.157  1100  5631 I PackageManager:   Category: "android.intent.category.DEFAULT"
09-24 23:29:28.157  1100  5631 I PackageManager:   Type: "text/plain"
09-24 23:29:28.157  1100  5631 I PackageManager:   AutoVerify=false
09-24 23:29:28.160  1100  1144 I ActivityManager: START u0 {act=android.intent.action.VIEW dat=file:///storage/FF7F-1F0C/1.txt typ=text/plain flg=0x13000000 cmp=com.amaze.filemanager/.activities.TextReader} from uid 10088 on display 0
09-24 23:29:28.389  1100  1196 I ActivityManager: Displayed com.amaze.filemanager/.activities.TextReader: +198ms
09-24 23:29:29.008  1100  5658 W ActivityManager: Finishing task with all activities already finished
09-24 23:29:29.008  1100  5658 W ActivityManager: Duplicate finish request for ActivityRecord{5216a62 u0 android/com.android.internal.app.ResolverActivity t460 f}
09-24 23:29:30.670  6207  6229 D conversations: deleted file /storage/emulated/0/Android/data/com.amaze.filemanager/cache/1.txt

Editing this file with Amaze Text Editor opened from native Lineage OS file namager succeed.
Amaze have "storage" permission.

[VishalNehra]

@Myppomeu thanks for your detailed review. I'll be looking into this.

[dp-alvarez]

Has there been progress on this? I'm affected by the same bug.
Apparently Amaze can write to /mnt/media_rw/ but behaves strangely. It thinks there is 0 bytes of free space on that path, so it refuses to create or copy files there. Also it will not accept that path being added as a shortcut, it thinks the path does not exist, very weird.

[ildar]

I have it working on LOS14.1
Please check if the app can create folders and check
https://github.com/TeamAmaze/AmazeFileManager/issues/539

[dp-alvarez]

I think I figured it out, it was my fault after all.
The problem is that I had removed the "Files" (aka "DocumentsUI") app from the default LOS14.1 installation, and amaze relies on it in order to get permissions to write to the external storage. After restoring it everything works fine.
I find this kind of strange, why does Amaze need another app to provide it with access to the external storage, specially when it has root access? Some weird android design philosophy I suppose?
Anyhow it is solved now, sorry for the noise.

[VishalNehra]

@dp-alvarez glad that you figured it out! That's a restriction put on by Android.

[ildar]

I think this part needs a video howto.

[Myppomeu]

@dp-alvarez, in my case Amaze have permissions granted by Files app, but bug is actual

[kentchristopher]

For the aid of others, I was having this same issue on LineageOS 14.1. I had disabled the native "Browser" app. Once re-enabled, I was able to write to the SD card fine. Strange, but it works.

[Myppomeu]

@kentchristopher
Can't confirm. Doesn't work in my case. Any else you do? Reboot, run browser, etc.

[Couchy]

I would also appreciate a rooted or systemized app way of doing this. Having to open the native file browser is kind of silly.

[Flashwalker]

Issue remains the same on 3.4.3. After selecting SD card for writing in permissions dialog nothing is happens. Amaze throws this dialog again and again each time i try to modify files on SD.
Android 7.0.

[rhaokiel]

For me, Amaze complained about modifying the SD card, until I switched it into root mode. Then when I tried to delete a file it asked me to navigate to the root of the SD card in DocumentsUI app. After doing so, Amaze had no problems deleting anything in the future without needing to select through DocumentsUI again. However, the FTP server through Amaze still cannot modify the SD card.

Termux reports all of these files with the following permissions: -RWXRWX--X | root | sdcard_rw

But Amaze reports them as read only 'r'

Termux reports the files on internal storage with the same permissions, but Amaze says they are 'rw'