I have problem that i can't find answer to anywhere.
I recently installed new 128GB sd card. I wanted to delete some mp3 file (i will be doing that quite often now) and Aimp asked for permission to do so, and popup from android came out, with internal storage. I switched to sd and clicked ”use this folder” on root directory of sd, but i still can't delete files as i don't have write permission. Aimp still asks for write permission but now root directory of sd has no 'use this folder button' it shows up after i go to any folder and then back up, but it changes nothing, i still can't write to sd.
I have identical situation with ttorrent.
What i can do to change that? It's extremely annoying.
I granted permissions in apk setting for writing in memory too.
Same issue for me. It was on Android 9, and it is on Android 10 also(
Related
Has any one else lost the ability to write to their socketed sdcard since the 4.4.2?
thesavo said:
Has any one else lost the ability to write to their socketed sdcard since the 4.4.2?
Click to expand...
Click to collapse
Thats a "feature" of kitkat. Can't be changed unless you have root.
Seriously?
Yes, see here for fix(if your rooted):
https://play.google.com/store/apps/details?id=nextapp.sdfix
thesavo said:
Seriously?
Click to expand...
Click to collapse
It's a security issue. Before KK, the SD card was wide open to any other process to be able to request read/write to any directory and file, regardless of whether or not they created that file or directory.
Now, under KK, a program can create a file or folder in a "protected" area and only that program has the ability to modify the contents in that folder. It cannot modify other folders or files that it didn't create.
Time to move the podcasts. So my older shows that I worked hard to keep to keep the ext sdcard1 as a target, will have to be copied to sdcard0.too bad.thanks @iBolski
No wonder BeyondPod kept 'accidently' putting shows on SDcard0 for the last year. Even though I "pinned" it to SDcard1 in the advanced settings.
Even with the application that patches the /etc/permissions/platform.xml, I have found certain apps still do not work correctly. Dolphin Browser, for example, cannot switch to /storage/sdcard1. It keeps saying it can't find it and I need to ensure I don't have "USB Mode" enabled, which I don't even have as an option when connected to a PC.
I also have init.d installed on my machine and I had startup scripts that mounted various directories from my external to the internal SD card to "fool" the device so that apps that wouldn't save to the external but the internal would save across a mount. Well, that no longer works. For example, Amazon MP3 will not save downloaded music anywhere except to the internal sd card. I had my startup scripts mount an amazonmp3 directory on my external SD card to the internal amazonmp3 directory on the internal memory card. When I proceeded to download music, it didn't show up in the external directory. However, I noticed that the internal sd card's memory did decrease. I then unmounted the directory and saw that the Amazon MP3 app was ignoring the mount under KitKat and directory saved the files into the /storage/sdcard0/amazonmp3 directory, even though it was mounted to the directory on the external SD card. It did work under JB and ICS, but apparently, with KitKat, some apps will still write directly to the native directory on the internal SD card, ignoring the fact that I've mounted a different directory to it.
The stock Moto camera will write to the external SD card if you go and change the setting for it. However, the Google Camera does not give you any option to store your pictures anywhere except on the internal SD card memory. :crying:
Remember, apps can write to the external card, if you don't apply the "patch", but only to what is considered a protected are (the /storage/sdcard1/Android directory structure) and then, they can only write to a directory that the app created. They can read other directories, but they cannot modify them.
iBolski said:
It's a security issue. Before KK, the SD card was wide open to any other process to be able to request read/write to any directory and file, regardless of whether or not they created that file or directory.
Now, under KK, a program can create a file or folder in a "protected" area and only that program has the ability to modify the contents in that folder. It cannot modify other folders or files that it didn't create.
Click to expand...
Click to collapse
That's official explanation (bull****) as you described above with non stock camera. Basically KK made external storage almost useless. I found this nice description quite long time ago.
https://plus.google.com/+TodLiebeck/posts/gjnmuaDM8sn
Zeljko1234 said:
That's official explanation (bull****) as you described above with non stock camera. Basically KK made external storage almost useless. I found this nice description quite long time ago.
https://plus.google.com/+TodLiebeck/posts/gjnmuaDM8sn
Click to expand...
Click to collapse
I know at this point, Root Explorer still works with it, after setting the correct permissions into the /etc/permissions/platform.xml file. That works for a lot of apps. The only one that I know that is currently broken is Dolphin browser. I cannot navigate to the /storage/sdcard1/ area anymore. It keeps telling me it can't find the file or directrory and that I should make sure the SD card is ready and USB Mass Storage (haven't seen this option since my Droid X2) is not on.
So definitely, Dolphin Browser is doing something differently that even the patch isn't working for it.
Problem is that without root user cannot edit platform.xml and even after that some applications refuse to write to sd card. Another example is OfficeSuite 7 Pro which I bought and now cannot edit file if it's needed. Workaround is to save to internal then overwrite to sd card.
Basically stock Android becoming more and more limited, harder and harder to get root... That's so bad that I wouldn't update to official kk in the case that my phone has locked bootloader.
Read this article http://www.xda-developers.com/andro...use-even-more-issues-for-root-app-developers/
Did the platform.xml fix to enable external sd write, but then got "not enough space.
Hello all. I couldn't post this as a reply to anything (not enough posts) so I put a new thread here to share my experience for the possible benefit of others with the same problem.
I have a rooted T-Mobile Galaxy Note 10.1 2014 edition (SM-P607T) running stock kitkat 4.4.2 (uvuane2 fw). I did the platform.xml manual fix to enable external sd card writing, but in every file manager in which I tried to move a file (root explorer, ES, even TW My Files) only a few MB would move and then I would get an insufficient space error. I knew this couldn't be right as I was using a 32gig sandisk with almost nothing on it. I had previously used this card in my Note 2 SGH-T889 also running 4.4.2, which had created the "Android" and "lost.dir" folders on the card. I wondered if something in those folders was interfering with write, or perhaps a filesystem issue. So I formatted the external sd from settings and bingo, the write suddenly worked! Anyone have any thoughts as to how and why?
Cheers...Kittie
(Correction: In ES and My Files, I got insufficient space error, but in Root Explorer, I got the "restricted write access 4.4.2 nothing we can do etc." popup.)
Hi. I try to explain this briefly and informative so you can help me out. I transferred a huge amount of files (video, music, pictures and apks) via zapya from my old xperia m dual to xperia m2 aqua. After moving files I just found out the files do not get automatically in Album, Movies and .... apps and just remains in Zapya and you can view them only there (So noone else faced such problem?!) But the main problem is, I just finded files and moved them with ES File Explorer File Manager, this is what happend >>>
I accidentally moved files to wrong section (storage/emulated/0) which I guess is systemic path. So the phone began to alerting me with love storage space and when I tried to move files to SD card (with same method i moved them to wrong path), It says the phone needs to be rooted for moving files. Now the files can not be deleted, copied, cut or modified as I guess the phone consider them as systemic files and phone internal storage became full.
I just don't want to root this new phone (at least now, or even root and unroot again), so please help me what to do without rooting (I consider root/unroot as my last hope).
What is the version of android you use ?
If I remember correctly in Android 4.4 KitKat without root you can copy, move files as follows:
Internal memory -> external sd card.
External sd card <-> cloud storage.
You can only copy, move in this direction, but not back:
Internal memory -> external sd card.
Cloud storage -> external sd card.
Also you can't rename or delete folders on external sd card.
You can fix this inconvenience only if you're rooted.
You need to add add <group gid="media_rw" /> in file /system/etc/permissions/platform.xml .
Root
I am concluding that only rooting can make it possible, but waiting for more responses maybe something happen! Now looking for a safe half root method.
Try with File Commander that came with phone as preinstalled system app. You can't use ES File Explorer to edit files on external SD card as KK restriction because it's user application, only system apps can do that.
@AleksJ
Sorry man, but you are so wrong, you can edit external SD card content only with system (non-user) apps and that's KK restriction. So I got this File Commander app preinstalled and I had used it until I rooted my phone. Now Solid Explorer is the best...
Go to Settings/Memory (I think). There is an option to move images/video/music files and maybe other content from/to the internal memory and the SD Card. It also has an option to wipe the cache files (not the directory /cache which is another thing).
All of a sudden now since I put in a new SD card into my tablet I can't seem to grant write permission to apps, or more I can't see the card in the window to give permission to grant it. When it takes me to the window to grant permission all it has on the left is recent and internal storage, going into the menu on the right it's already set to show SD card, selecting hide SD card hide internal storage, so basically it's acting like the internal storage is the SD card and there is no SD card. my tablet is not rooted and is running the latest software update available.
rooting the tablet will allow you to fix it easily. the exSD problem has been around for awhile.
one of the easiest ways to do it is to install a free app that does it for you. (then uninstall if you have no plans to use it)
TWRP manager and Foldermount come to mind, they will both fix the SD issue autoamagically when you first run them.
you can not fix this issue, to my knowledge, without root permissions.
At this point don't want to go thru everything for rooting till after they push out Marshmallow to the tablet. What I don't get though is why it's a not working correctly now, giving apps write permission worked totally fine before when I had my old 32gb SD card in there, it just won't let me grant permission to the new 64gb card.
Hi there,
I am using ES File Explorer on my Samsung Galaxy S7. I have noted there is an issue with the write permission with an encrypted SD card. All the new folders I created on encrypted SD card will have an icon with a question mark and I cannot access those folders. The default file explorer that comes with the phone works fine with the encrypted SD card.
I have no problem creating and using new folders on a non-encrypted SD card. Does anyone have any idea how do i fix this?
Thanks
Did you find solution to it?
Email the devs of es file explorer.
I've already contacted the ES File Explorer devs. It seems to me that this write permission issue with encrypted SD card happens to all the 3rd party apps (ES file explorer, MyPhoneExplorer, etc.). The phone just won't let those apps to properly write to the encrypted SD.
I wonder if anyone here having the same issue like me?
I just post a question to MyPhoneExplorer's forum. Hopefully someone there will have a clue of the problem.
"Hi there,
I used MyPhoneExplorer to sync files between my PC and my phones (Samsung Galaxy S3, S5, Note3) without any problem before.
Now, I have a Galaxy S7 (Android 6.0 Marshmallow) and I have noted an issue with the write permission to the ENCRYPTED external SD card. Every time i try to copy/write a file from my PC to my encrypted external SD card via MyPhoneExplorer, it returns an error message saying "Please note: It's impossible to wirte to the external SD card (External storage) for all third party applications due to a security restriction in Android! The internal phone storage (Memory card) is not affected by this restriction. "
Please note that I have no problem copy/write files from my PC to the non-encrypted external SD card on my Galaxy S7.
And i observe that this issue with the write permission to encrypted SD card in Android 6 also happens with other 3rd party app such as ES File Explorer.
So, I reckon the way apps write to encrypted external SD might be changed in Android 6?!?!
Could you please have a look."
Have exactly the same behavior in ES Explorer. When rebooted can see the folder and content. Internal file explorer from Samsung(?) works fine.
I encountered the same problem as well. Happens on all 3rd party apps. Just wondering Is this Galaxy S7 issue only or does this happen on other devices? Are there any workarounds for this issue other than removing encryption completely from SD card?
Have the same problem with every file explorer I tried. the only one that works is the built-in myfiles
I am having the same issue. It seems all my 3rd party apps can't write on SD card. Only Samsung built-in can. I am on G930U snapdragon rooted but no custom recovery. Flashed xposed framework (xposed-v85.1-sdk23-arm64-custom-build-by-wanam-20160530) via Flashfire and installed the Marshmellow SD card module and restarted phone. I still can't delete files from 3rd party app such like a music file within Jet Audio music player. Phone seems to lag now esp when i am on sms. Anyone have any idea on the sd card write permission?