I have the T-Mobile Galaxy Note 3. I was on stock and just took the OTA upgrade to Lollipop (N900TUVUFOB6). After doing this, I rooted the phone with CF Auto Root and installed TWRP 2.8.5.0. I have root access fine. I keep my apps backed up from Titanium Backup on my SD card. When I open up Titanium Backup it tells me the directory isn't writable. I am on the latest su binary / supersu and I have tried changing the mount namespace setting with no luck. Is there anything else I could try to fix it?
Did you install the SD card fix app?
I think there is an option on lollipop to authorize other apps to access directories that are not there own. That might be the problem.
I searched and found you need to change a setting in Preferences - Backup folder location. Near the top is Storage Provider. Click and change to Directory provider. Fixed it for me. Never knew that was a setting before!
sjancura said:
I searched and found you need to change a setting in Preferences - Backup folder location. Near the top is Storage Provider. Click and change to Directory provider. Fixed it for me. Never knew that was a setting before!
Click to expand...
Click to collapse
Thanks so much! I had to pick the option DocumentProvider storage and then select the directory through there. Working fine now.
Sorry. Meant Document provider not Directory provider. ?
Has anyone found a reason why TiBu now thinks the entire directory of dalvik cache is unnecessary when you run the clean up option?
Changing that to DocumentProvider storage solved my problem too sjancura, thanks!
Hi,
I spoke too soon... I am still having problem with using external SD card with titanium backup.
I changed the storage provider to DocumentProvider but I cannot 'save' that selection as it's grayed out - please see the screenshot.
I have tried changing name of ex SD card. At first I used SDFix apps which were able to help with similar problem in KitKat but haven't fixed the issue now in lollipop.
I had the same problem (Running Lollipop and TB) and I got it fixed by using one of the KitKat fixes. The one I used was "SDFix" by "NextApp, Inc." in the google play store.
dajomas said:
I had the same problem (Running Lollipop and TB) and I got it fixed by using one of the KitKat fixes. The one I used was "SDFix" by "NextApp, Inc." in the google play store.
Click to expand...
Click to collapse
Thanks...that worked for me too.
sjancura said:
I searched and found you need to change a setting in Preferences - Backup folder location. Near the top is Storage Provider. Click and change to Directory provider. Fixed it for me. Never knew that was a setting before!
Click to expand...
Click to collapse
Hours of frustration brought to an end by that advice ... thanks mate ... you're a legend!
Hi,
I tried running SDFix, having run it in tbe past, prior to finding out this morsel of info on changing DP. However I still can't get it to save that location. Same greyed out directory like previous user posted.
Yeah I found that as well, changed it but could not "save" to that folder location (greyed out). Tried SDFix app, no change. Tried creating a new folder in TB, AND then using ESFile Explorer & neither would allow me to write to the extSD card. Rooted, stock Sprint Lollipop ROM.
I had that issue, worked it out. When you're browsing for a folder with the DocumentProvider select the root of the SD card, then it should close and return to the browser in Titanium Backup. Browse to the sub folder you want, you should be able to click the save button now.
Hi Ghosthree3,
Thanks so much for this. I'm going to give it a shot. My extSD card was used in the past on an earlier version of Android OS, whereby I could write to the extSD card just fine. Consequently there are prior backups on there. As such, I'm wondering if i should mount the phone, copy that folder off, delete that folder on the extSD card and then via TB create a "new" Titanium Backup folder and see if it then allows me to write. Note: I tried mounting the phone to my PC in an effort to create a folder on the extSD card and that method too, prevented me from creating a folder, hence my thought on getting what I have off of the device, and attempting writing a new folder per your directions. I wonder if my PC will allow me to erase that folder.....
Dopamin3 said:
I have the T-Mobile Galaxy Note 3. I was on stock and just took the OTA upgrade to Lollipop (N900TUVUFOB6). After doing this, I rooted the phone with CF Auto Root and installed TWRP 2.8.5.0. I have root access fine. I keep my apps backed up from Titanium Backup on my SD card. When I open up Titanium Backup it tells me the directory isn't writable. I am on the latest su binary / supersu and I have tried changing the mount namespace setting with no luck. Is there anything else I could try to fix it?
Click to expand...
Click to collapse
Install xposed and then use xinternalsd then configure it as u wish. This will fix the problem
Sent from my iris_X8 using XDA Free mobile app
sjancura said:
I searched and found you need to change a setting in Preferences - Backup folder location. Near the top is Storage Provider. Click and change to Directory provider. Fixed it for me. Never knew that was a setting before!
Click to expand...
Click to collapse
Thank you!
Hi s j a n cu r a,
Thank you very much. Someone else posted that, but maybe i'm not selecting it properly. When I select Document Provider, I browse to "Open from SD card", scroll down to the "Titanium Backup" folder, hit "Select" the "Titanium Backups" that are there [at one time I had no issues writing to my EXT SD card], it then says, "Detect!" [External storage] and I select "Everywhere in External Storage". It finds 41 backups there, I select that "External Storage' radio button. That's where I seem to hit a wall. The "Use the current folder" appears to be greyed out. I'm left only with "Cancel". I think there is some deeper issue writing to ExtSD because with File Explorer I can't copy picture files from one folder to the other. That's what is giving me this feeling that something else is going on with write permission. Frustrating to say the least. My only recourse at this point is to use the internal SD, which does work.
Google lollipop external sdcard fix. There's an app in the play store.
Sent from my SM-N900T using Tapatalk
Related
recently my WF stops installing apps, either from market or restoring from titanium backup. Im using Leaf r3 rom w/ 2.2.1. Error when updating from market says "Couldn't install on USB storage or SD card".
Any idea how to fix it? thanks!
check option in leaf rom to install apps in sd card from settings-->applications....
Ankurcul said:
check option in leaf rom to install apps in sd card from settings-->applications....
Click to expand...
Click to collapse
I dont see that option in settings/application. Can you be more specific?
i found this solution by googling, this may help someone drop by this thread
connect your device to your PC and manually delete the “smdl2temp1” file. The file is likely to reside in 2 locations:
1. /sdcard/.android_secure: this is an invisible folder on your SD card, which you can access with any file manager, like ASTRO
2. /mnt/secure/asec/: access to this folder requires root and a program like Root Explorer
it works for me.
is it solved now??
Hope I'm not repeating a question here. I couldn't find anything in this forum. I just finished updating my international m8 to lollipop ota. After installing titanium backup from the market, I noticed my previous backup on ext_sd are reported as not writable by titanium. I was under the impression that the new android L would rectify this Kitkat issue. Is there any work around for this issue yet? Thanks.
So I found a test version of titanium backup for Lollipop http://bit.ly/1v0njNa. Unfortunately I'm getting Documents crashes when I selected the extsd after switching to documentprovider storage. So I'm still unable to assign the backup directory to my external sd. Any input would be appreciated. Thanks!
mateenf said:
Hello All,
Since kitkat 4.4.2 was released on the Galaxy Note 3, many users were unable to write files to the External SD Card. Below is a simple fix for rooted users on the Galaxy Note 3 N9005 ( International Snapdragon Variant).
**Please be advised that I have only tested this on my personal N9005. However, you are free to test it on your own devices at your own risk!! **
1. Using a root-enabled file manager, navigate to /system/etc/permissions
2. Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.
3. Add an additional group definition for this permission...<group gid="media_rw" />
4. Save the changes to the file.
5. Restart.
Attached is a copy of my platform.xml.
Click to expand...
Click to collapse
Thread link forum.xda-developers.com/showthread.php?t=2617921
Working ok.
Thanks for the reply. I did use that solution when I was on 4.4 but lollipop has a different documentprovider solution now. I finally figured out what was happening. The issue isn't with titanium backup up but with how documentprovider was accessing my ext_sd. For some reason the documents will crash if I left ext_sd unnamed. I ended resolving the issue by naming my sdcard and it's been working as expected. Weird little bug in lollipop... In addition to the DNS issue.
Thanks for that solution. I had the same issue.
After naming the SD card using my laptop, the HTC Documents application no longer crashed and I can allow write access to the application (ES fileexplorer in my case.).
I guess it is an HTC bug, the documentsprovider shows the label/name of the ext SD card on the button to be pressed to allow access, and apparently it can't handle an empty SD card name.
Hi!
Just updated my HTC One M8 to 5.0.1. I thought I would be able to R/W SdCard finally, but NO!
When I'm asked to grant access, I hit Grant, and then when I select SdCard (external) error pops up with : "Documents has stopped working". I used Solid Explorer (to delete or create folder), ES File Explorer (same), Quickpic (to delete picture). Of course "stock" File Explorer is working fine.
I tried: disabling Docs, G Drive, etc., uninst. updates and nothing helps.
Has someone got this too? Or is it only on my side?
Thanks!
gutec
gutec said:
Hi!
Just updated my HTC One M8 to 5.0.1. I thought I would be able to R/W SdCard finally, but NO!
When I'm asked to grant access, I hit Grant, and then when I select SdCard (external) error pops up with : "Documents has stopped working". I used Solid Explorer (to delete or create folder), ES File Explorer (same), Quickpic (to delete picture). Of course "stock" File Explorer is working fine.
I tried: disabling Docs, G Drive, etc., uninst. updates and nothing helps.
Has someone got this too? Or is it only on my side?
Thanks!
gutec
Click to expand...
Click to collapse
I have this problem too and i hate it. I dunno what to do. Only the system filemanager can write on sd card.
androidpolice.com said:
Now that Lollipop no longer requires root permission to gain access to the SD card, most file managers will be working to add compatibility fairly quickly.
Click to expand...
Click to collapse
gutec said:
Hi!
Just updated my HTC One M8 to 5.0.1. I thought I would be able to R/W SdCard finally, but NO!
When I'm asked to grant access, I hit Grant, and then when I select SdCard (external) error pops up with : "Documents has stopped working". I used Solid Explorer (to delete or create folder), ES File Explorer (same), Quickpic (to delete picture). Of course "stock" File Explorer is working fine.
I tried: disabling Docs, G Drive, etc., uninst. updates and nothing helps.
Has someone got this too? Or is it only on my side?
Thanks!
gutec
Click to expand...
Click to collapse
xTee said:
I have this problem too and i hate it. I dunno what to do. Only the system filemanager can write on sd card.
Click to expand...
Click to collapse
did you try the Kitkat sdcard fix in the play store .. i have no problems saving to the external sd
clsA said:
did you try the Kitkat sdcard fix in the play store .. i have no problems saving to the external sd
Click to expand...
Click to collapse
No root.
Problem SOLVED!
I have formatted sd card in WINDOWS without disk label - NOT WORKING
Formatted WITH disk label (in my case "SanDisk") - WORKING!
Odd...
Thx guys!
gutec said:
Problem SOLVED!
I have formatted sd card in WINDOWS without disk label - NOT WORKING
Formatted WITH disk label (in my case "SanDisk") - WORKING!
Odd...
Thx guys!
Click to expand...
Click to collapse
Gutec solution worked really nice.
I have a HTC M8 (Lollipop) and i was fighting to make SD work with no luck ... neither from HTC.
And now a guy comes with one simple step and everything working as it should.
Why HTC or any other company didn't figure out this solution and didn't give directions that solve the problem ..... and Gutec i really wan't to know how you come with this solution?
Anyway thanks a lot
format it as fat32
it's incredible that you format an SD with Android, and still cannot use the card.
Format it as Fat32 and Label as discribed by gutec WORKS!
THANKS!
I've got to say that my SD card is in fact formatted FAT32, without any set label and I don't have any problem writing to it. I can't imagine the drive label being important for anything, unless there is some really weird bug in Android.
thank you so much
So simple. Just label the sd card and problem solved. Didn't figure that out yet, glad you did.
RE:
HTC M8 European version.
Android 5.0.1 official update.
No root.
Cannot write to sd card with 3rdparty apps. Except copilot, none are working.
My card has a label, tried formatting with phone and windows pc with no positive result, same problem persists.
what else can I do?
thanks to the post above my problem was fixed. Also its not necessary to format too(i didnt cs mine was already fat32 so i didnt bother). Just adding a label to sd card will do. seems Documents app cannot open the card while its unlabeled
gutec said:
Formatted WITH disk label (in my case "SanDisk") - WORKING!
Click to expand...
Click to collapse
This works, but seriously.. Un-effing-believable.. A volume label?? Really???! God, what a joke. I'd love to know who fat-fingered this one..
Thanks so much.
Google turning into Microsoft with this?
gutec said:
Problem SOLVED!
I have formatted sd card in WINDOWS without disk label - NOT WORKING
Formatted WITH disk label (in my case "SanDisk") - WORKING!
Odd...
Thx guys!
Click to expand...
Click to collapse
Hi guys. If you did everything and still not able to see the card, you should try some extra steps.
In the "Grant permissions" screen use three dots menu and check "Show SD card" and after that you will be able to see it and selected. This worked for me.
gutec said:
Problem SOLVED!
I have formatted sd card in WINDOWS without disk label - NOT WORKING
Formatted WITH disk label (in my case "SanDisk") - WORKING!
Odd...
Thx guys!
Click to expand...
Click to collapse
Hi gutec,
Thanks for the tip, worked for me. :good:
External SD had no label, e.g. app "Nokia here" couldn't find maps on external card.
[offtopic] Sony Z1 compact on 5.1.1 [/]
Thanks to gutec & Arslan, it's working.
Arslan-Ahmed said:
thanks to the post above my problem was fixed. Also its not necessary to format too(i didnt cs mine was already fat32 so i didnt bother). Just adding a label to sd card will do. seems Documents app cannot open the card while its unlabeled
Click to expand...
Click to collapse
It seems important that it is FAT 32 - if NOT Fat32 then you have to reformat to FAT32 ( I had a 64gb sdxc)
gutec said:
Hi!
Just updated my HTC One M8 to 5.0.1. I thought I would be able to R/W SdCard finally, but NO!
When I'm asked to grant access, I hit Grant, and then when I select SdCard (external) error pops up with : "Documents has stopped working". I used Solid Explorer (to delete or create folder), ES File Explorer (same), Quickpic (to delete picture). Of course "stock" File Explorer is working fine.
I tried: disabling Docs, G Drive, etc., uninst. updates and nothing helps.
Has someone got this too? Or is it only on my side?
Thanks!
gutec
Click to expand...
Click to collapse
I too have had this happen as well only it isn't documents closing, the app (which ever one I'm using, they all seem to do it xplore, es file manager etc) itself just continues to ask for permission over and over right after I select SD card
Same problem-cannot grAnt access to SD card with many file manager apps
gutec said:
Hi!
Just updated my HTC One M8 to 5.0.1. I thought I would be able to R/W SdCard finally, but NO!
When I'm asked to grant access, I hit Grant, and then when I select SdCard (external) error pops up with : "Documents has stopped working". I used Solid Explorer (to delete or create folder), ES File Explorer (same), Quickpic (to delete picture). Of course "stock" File Explorer is working fine.
I tried: disabling Docs, G Drive, etc., uninst. updates and nothing helps.
Has someone got this too? Or is it only on my side?
Thanks!
gutec
Click to expand...
Click to collapse
I too have this issue with many file manager apps which is weird, they worked fine a month ago, now it's like someone hit the "off " switch. If you get it worked out please contact me at [email protected] so that I may correct mine as well...Thank you
Hi,
my H815 is freshly and happily rooted, and i wonder if i have to install SdFix or not.
Do we have to do this on Lillipop?
on Google Play, SdFix says "for kitkat" and don't mention Lollipop.
What do you think?
Thanx for answers
I had to use it for some apps, so I say YES. Lollipop has the same regulations for the external SD like KitKat, so the apps have the same problems.
misteurz said:
Hi,
my H815 is freshly and happily rooted, and i wonder if i have to install SdFix or not.
Do we have to do this on Lillipop?
on Google Play, SdFix says "for kitkat" and don't mention Lollipop.
What do you think?
Thanx for answers
Click to expand...
Click to collapse
I use it as well and it works - I can now save TB backup directly on my external SD :good:
clandes said:
I use it as well and it works - I can now save TB backup directly on my external SD :good:
Click to expand...
Click to collapse
+1
there was this thread some time ago by @TecknoFreak that explained how to fix that by editing the /system/etc/permissions/platform.xml file by hand, no need for an app http://forum.xda-developers.com/showthread.php?t=2524277. he posted this in another thread but i cant remember now where i saw it
having said that, i cant remember if i used TB saving my backups to external before or after i made the change to my xml using the steps from the thread but i am pretty sure it was before. also the LG camera can write to ext_sd so dont know for sure this is needed. plus i just did a reflash of @MicroMod777 xTreme rom so it reset that file and i can still write to my ext_sd with TB and camera
oops...i take back part of this, i just now noticed the notification i got from TB that said my backup failed cause i did not have enough space to write the backup to, but the camera still saves to external
so i must have done the xml edit before i did TB, either way, i dont think you need an app for this. sure it might make it easier, but editing the file is not too bad to tackle either
I downloaded SDFix from Google Play (pretty sure it's the same one I used when KitKat first came out) and it reported that the app wasn't necessary.
EU H815 rooted with the recently released Low Effort Exploit (and not by unlocking the bootloader via LG's Dev site).
TiBu was one of the first apps I installed after rooting earlier this week, and it never had a problem backing up to my ext. SD card.
Midnight_Rider said:
there was this thread some time ago by @TecknoFreak that explained how to fix that by editing the /system/etc/permissions/platform.xml file by hand, no need for an app http://forum.xda-developers.com/showthread.php?t=2524277. he posted this in another thread but i cant remember now where i saw it
having said that, i cant remember if i used TB saving my backups to external before or after i made the change to my xml using the steps from the thread but i am pretty sure it was before. also the LG camera can write to ext_sd so dont know for sure this is needed. plus i just did a reflash of @MicroMod777 xTreme rom so it reset that file and i can still write to my ext_sd with TB and camera
oops...i take back part of this, i just now noticed the notification i got from TB that said my backup failed cause i did not have enough space to write the backup to, but the camera still saves to external
so i must have done the xml edit before i did TB, either way, i dont think you need an app for this. sure it might make it easier, but editing the file is not too bad to tackle either
Click to expand...
Click to collapse
My edits should work just fine for TB backing up on external. I did the same edits to my H811 and works great. I was getting the same error as well and it got fixed after those edits that is just one line missing.
I rather change a line or 2 before installing an app to my phone but that is just me.
Specifically for TitaniumBackup, you just need to go to preferences and when selecting your backup folder, change the storage provider to DocumentProvider storage (Click above the DETECT button) and then navigate to your folder.
Works fine without any fixes.
Charsher47 said:
Specifically for TitaniumBackup, you just need to go to preferences and when selecting your backup folder, change the storage provider to DocumentProvider storage (Click above the DETECT button) and then navigate to your folder.
Works fine without any fixes.
Click to expand...
Click to collapse
Don't get the option to 'protect' backups though if you go this route. Only if you use the default setting with edited platform.xml file.
TecknoFreak said:
My edits should work just fine for TB backing up on external. I did the same edits to my H811 and works great. I was getting the same error as well and it got fixed after those edits that is just one line missing.
I rather change a line or 2 before installing an app to my phone but that is just me.
Click to expand...
Click to collapse
Same here, and this worked perfectly fine on my H815 (SEA version). Now I can actually let GoneMadMusicPlayer edit tags in my music collection.
Thanks :good:
I seem to have been at this for hours now. I finally got Xposed framework on my Tab S and Note 4 and decided to try Marshmallow SD fix
https://forum.xda-developers.com/xposed/modules/xposed-marshmallow-sd-fix-write-t3403263/page29
and then EXT SD fix
https://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
In each case going to Titanium backup it just doesn't work - I get the same old "Folder is not writable" message for anything on the SD card.
Since many people are having success - I'm assuming this is because of the Samsung version of Xposed framework ?
I don't know but nothing I do seems to work.
Any suggestions / advice - has anyone got this to work on their tab s or note 4?
louiscar said:
I seem to have been at this for hours now. I finally got Xposed framework on my Tab S and Note 4 and decided to try Marshmallow SD fix
https://forum.xda-developers.com/xposed/modules/xposed-marshmallow-sd-fix-write-t3403263/page29
and then EXT SD fix
https://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
In each case going to Titanium backup it just doesn't work - I get the same old "Folder is not writable" message for anything on the SD card.
Since many people are having success - I'm assuming this is because of the Samsung version of Xposed framework ?
I don't know but nothing I do seems to work.
Any suggestions / advice - has anyone got this to work on their tab s or note 4?
Click to expand...
Click to collapse
If it's lollipop you need the sdcard fix. If it's mm you just need to allow write permissions to the app.
ashyx said:
If it's lollipop you need the sdcard fix. If it's mm you just need to allow write permissions to the app.
Click to expand...
Click to collapse
I'm not sure I understand that. Are you talking about extsd or marshmallow fix ? Also there are no permissions to set other than the ones shown. For Titanium those are all set to on. Ie. Storage.
Is there a specific 'write' permission elsewhere that I've missed?
louiscar said:
I'm not sure I understand that. Are you talking about extsd or marshmallow fix ? Also there are no permissions to set other than the ones shown. For Titanium those are all set to on. Ie. Storage.
Is there a specific 'write' permission elsewhere that I've missed?
Click to expand...
Click to collapse
Any app that wishes to write to the external storage should show a dialog requesting permission to the ext sd after that it will have full write access.
Any app that doesn't isn't mm compatible.
Which folder path are you trying to use?
ashyx said:
Any app that wishes to write to the external storage should show a dialog requesting permission to the ext sd after that it will have full write access.
Any app that doesn't isn't mm compatible.
Which folder path are you trying to use?
Click to expand...
Click to collapse
The Titanium problem is fairly common. if all apps need to be was mm compatible then we wouldn't need a fix for the SD cards I would have thought.
But coming to Titanium itself I can select the old folder with is exsdcard/titaniumbackup but Titanium will tell me this has no write access but I can use it to read from and restore.
There is no location that Titanium will use or see on the extsdcard. What one has to do to is to copy the contents of your backup folder to the internal card then select that as the backup folder in Tba. Then you have elect to change the backup folder but choosing DocumentProvider storage. At this point you then have to create a folder - an existing folder is no good. Once created it will copy the contents of the internal folder to the extsdcard. Apart from the fact that this 'workaround' is much slower it is also inconvenient and any kind of change for whatever reason in the backup folder means that you can't just switch to the old one you have to go through the whole creation process.
As far as I am concerned this is why I wanted an SD card fix but I also understand to some point your view and it does make some sense. However it is confusing. When this nightmare started with Kitkat I understood that apps were allowed their own folder but couldn't affect or write to other folders. Also they were media folders only. This as I remember also affected file managers which then couldn't do their intended job.
With MM and without any fix Solid explorer can and does have full access to the sd card and can write in any folder from what I can see. Other apps seem to possibly access with documentprovider permissions - I'm not sure but many appear to have no problems but the pop up is very much like the documentprovider - choose a folder. So I am confused why Titanium has these problems and can understand a point of view that they haven't adapted as they should have perhaps but then I find it hard to believe that they wouldn't have done what they can with the features /tools they have for one of the most popular backup programs..
Either way, at the end of the day I was really hoping I could have got a fix which worked much like sdcard fix on Kitkat which stopped the nonsense and Google's insistence that they know best how we can and should use our SD cards.
And indeed for many people Marshmallow fix and or EXTSD appear to work for a lot of people in the way I was hoping - hence the creation of this thread because
1) it certainly doesn't for both my Samsung devices and
2) Many people with Samsungs (and some other devices) appear to be having the same difficulty.
I don't understand what has been done on MM to make it so difficult to overcome the problem but obviously it appears Google is just plain bloody minded and trying to make it more foolproof.
louiscar said:
The Titanium problem is fairly common. if all apps need to be was mm compatible then we wouldn't need a fix for the SD cards I would have thought.
But coming to Titanium itself I can select the old folder with is exsdcard/titaniumbackup but Titanium will tell me this has no write access but I can use it to read from and restore.
There is no location that Titanium will use or see on the extsdcard. What one has to do to is to copy the contents of your backup folder to the internal card then select that as the backup folder in Tba. Then you have elect to change the backup folder but choosing DocumentProvider storage. At this point you then have to create a folder - an existing folder is no good. Once created it will copy the contents of the internal folder to the extsdcard. Apart from the fact that this 'workaround' is much slower it is also inconvenient and any kind of change for whatever reason in the backup folder means that you can't just switch to the old one you have to go through the whole creation process.
As far as I am concerned this is why I wanted an SD card fix but I also understand to some point your view and it does make some sense. However it is confusing. When this nightmare started with Kitkat I understood that apps were allowed their own folder but couldn't affect or write to other folders. Also they were media folders only. This as I remember also affected file managers which then couldn't do their intended job.
With MM and without any fix Solid explorer can and does have full access to the sd card and can write in any folder from what I can see. Other apps seem to possibly access with documentprovider permissions - I'm not sure but many appear to have no problems but the pop up is very much like the documentprovider - choose a folder. So I am confused why Titanium has these problems and can understand a point of view that they haven't adapted as they should have perhaps but then I find it hard to believe that they wouldn't have done what they can with the features /tools they have for one of the most popular backup programs..
Either way, at the end of the day I was really hoping I could have got a fix which worked much like sdcard fix on Kitkat which stopped the nonsense and Google's insistence that they know best how we can and should use our SD cards.
And indeed for many people Marshmallow fix and or EXTSD appear to work for a lot of people in the way I was hoping - hence the creation of this thread because
1) it certainly doesn't for both my Samsung devices and
2) Many people with Samsungs (and some other devices) appear to be having the same difficulty.
I don't understand what has been done on MM to make it so difficult to overcome the problem but obviously it appears Google is just plain bloody minded and trying to make it more foolproof.
Click to expand...
Click to collapse
The fix for KitKat and lollipop isn't needed for MM because Google did in fact listen to people griping about the ext card restrictions.
MM will give full access to properly coded apps.
I have many different devices running MM and all gave write access to the ext sdcard including TB, which I use regularly.
However that doesn't mean to say I haven't had the issue you speak of. I may have even had it with TB.
The folder path I use in this case is mnt/media_rw/
This path is almost always accessible by apps and is the path I'm using right now for TB.
If that doesn't work try disabling 'mount namespace separation' in SuperSU settings then reboot also make sure your TB is up to date.
ashyx said:
The fix for KitKat and lollipop isn't needed for MM because Google did in fact listen to people griping about the ext card restrictions.
MM will give full access to properly coded apps.
Click to expand...
Click to collapse
Ok understood.
I'm guessing then that the so called Marshmallow fix via xposed is to get older apps which may not be updated to work
ashyx said:
I have many different devices running MM and all gave write access to the ext sdcard including TB, which I use regularly.
However that doesn't mean to say I haven't had the issue you speak of. I may have even had it with TB.
The folder path I use in this case is mnt/media_rw/
This path is almost always accessible by apps and is the path I'm using right now for TB.
Click to expand...
Click to collapse
Ok so now the plot thickens and I've no idea what is going on here. Tba says when I navigate to this folder [and I'm assuming that the choice when asked is "filesystem storage" and not "Filesystem storage - Media" (which only offers internal memory anyway)]
"This folder cannot be accessed"
and that is before getting to the external sd card which would be the number (F91E-D472) in my case. ie. mnt/media-rw
Needless to say - Solid explorer can see this and navigate to the sd card no problem.
This happens on both Note 4 and TAB s and I'm really curious now because something on my systems are different.
ashyx said:
If that doesn't work try disabling 'mount namespace separation' in SuperSU settings then reboot also make sure your TB is up to date.
Click to expand...
Click to collapse
Sure, namespace is unchecked - did that on both devices some time ago, and Tba is up to date.
Pretty damn confused now
louiscar said:
Ok understood.
I'm guessing then that the so called Marshmallow fix via xposed is to get older apps which may not be updated to work
Ok so now the plot thickens and I've no idea what is going on here. Tba says when I navigate to this folder [and I'm assuming that the choice when asked is "filesystem storage" and not "Filesystem storage - Media" (which only offers internal memory anyway)]
"This folder cannot be accessed"
and that is before getting to the external sd card which would be the number (F91E-D472) in my case. ie. mnt/media-rw
Needless to say - Solid explorer can see this and navigate to the sd card no problem.
This happens on both Note 4 and TAB s and I'm really curious now because something on my systems are different.
Sure, namespace is unchecked - did that on both devices some time ago, and Tba is up to date.
Pretty damn confused now
Click to expand...
Click to collapse
Have you tried placing the TB folder on your ext sdcard then used the detect button (whole device) in preferences to detect the folder and then select it under mnt/media_rw?
ashyx said:
Have you tried placing the TB folder on your ext sdcard then used the detect button (whole device) in preferences to detect the folder and then select it under mnt/media_rw?
Click to expand...
Click to collapse
This was the method I used as soon as I updated to MM and didn't notice the "this folder is not writable" message.
However, the option to choose mnt/media_rw isn't available. If I use Detect > whole device I'll be offered :
/storage/F91E-D472/Titaniumbackup
perhaps I'd see the other option under normal circumstances but Tba is not able to access that path so wouldn't find it in a search ... I guess
Aha! could this be the problem?
see post #15
https://forums.geforce.com/default/topic/917126/write-to-external-sd-restriction-in-marshmallow/
What is your sd card formatted as - mine is FAT32 so perhaps I need to go exfat?
..but then such links show that I'm certainly not alone - this one actually confirms that tb has this write problems and leads to the Documentprovider solution:
https://www.youtube.com/watch?v=GATqU1_xzqA
louiscar said:
Aha! could this be the problem?
see post #15
https://forums.geforce.com/default/topic/917126/write-to-external-sd-restriction-in-marshmallow/
What is your sd card formatted as - mine is FAT32 so perhaps I need to go exfat?
..but then such links show that I'm certainly not alone - this one actually confirms that tb has this write problems and leads to the Documentprovider solution:
Click to expand...
Click to collapse
ExFAT. Anything above 4gb should be ExFAT.
ashyx said:
ExFAT. Anything above 4gb should be ExFAT.
Click to expand...
Click to collapse
curiously I set permissions to 777 for the mnt/media_rw and titanium can go there but any further (even though I've done the same for the sdcard folder - nada!
and sadly after converting to exfat - mnt/media_rw .... "this folder cannot be accessed"
Not sure what else I can do.