Develop Bugs

[Q] sd problem

I rooted my evo and its been working fine, but I now have a problemo..
The SD card is mounted because I can see everything through astro, I can connect it to the computer and browse the sd card and see pix and music
The music player says "No music found" and the gallery wont display my photos.
Any suggestions? I dont want to format the sd card if possible. More info by request.
Thanks

Also when I take pictures theyll stay for a while, I dont know exactly when they disapear, but maybe when the phone is rebooted. They do although get saved to the sd card in the proper 100MEDIA folder

Would you happen to be on the sense 2.1 ports? That happens to me when I'm on them.

what do you mean by the port? I am using 2.1 tho. its been working fine for about 4 months

Take SD card out..copy contents, format SD card, copy contents back, insert SD card back..your problem should be fixed..if not, get a better SD card.
Sent from my PC36100 using XDA App

If you don't want to format it, try unmounting & remounting the SD card. You can also try manually running the media scanner. There are multiple toggle widgets that do this - Widgetsoid is my personal preference, but there are others. The dev tools app on CM7 also has an option to run the media scanner.
I think this is a rom issue & not an sd card issue. Backup your current rom, then restore from a backup of a different rom or try a clean install of a new one. If you choose to do a fresh flash, I suggest going with the stock rooted rom. If you still have the problem, then copy all of the files to your computer, format the card, then copy what you need back to the SD.
If it works fine on a different rom, you know the problem is rom related. You can try a completely clean install of whatever rom you're running right now, but it may just be a bug pertaining to the rom.
What rom are you on at the moment? Just curious...

honestly I cant remember. how to I find out?

iknowthefuture said:
honestly I cant remember. how to I find out?
Click to expand...
Click to collapse
You don't remember what rom you're on? Really?
Umm, okay. Go to settings, then about phone down at the bottom. If you don't know which piece of info is the rom - you should recognize the name - just post everything in that menu.

iknowthefuture said:
I rooted my evo and its been working fine, but I now have a problemo..
The SD card is mounted because I can see everything through astro, I can connect it to the computer and browse the sd card and see pix and music
The music player says "No music found" and the gallery wont display my photos.
Any suggestions? I dont want to format the sd card if possible. More info by request.
Thanks
Click to expand...
Click to collapse
You want to make sure that you don't have a ".nomedia" file in with your pictures or music. Certain apps can automatically create a .nomedia file and place it in with your music files or pictures, etc. When a .nomedia file is present, that folder won't get scanned for media of any kind, therefore your stuff wont show up. I'm not saying that's definitely your problem, by any means. However, simply suggesting that you check your folders, to make sure that the .nomedia file isn't there. I forget which apps can create that file, but I know it can happen.

i used unrevoked.. which one is the rom in software info?

iknowthefuture said:
i used unrevoked.. which one is the rom in software info?
Click to expand...
Click to collapse
It may be named Rom Version, Mod Version, build number... I've seen multiple different wordings for it. Mine says "Build Number", but I'm on MIUI. It isn't baseband, kernel, model version, or Android version. It won't be only numbers, and it isn't PC36100.
Let me ask you this... have you flashed any roms through recovery or Rom Manager? If not, you're on stock.

3.70.651.1 cl294884 release-keys is build number

I just tried to install fresh evo 3.5 rom and when it rebooted it stuck at the white "htc evo 4g" screen

k2buckley said:
You want to make sure that you don't have a ".nomedia" file in with your pictures or music. Certain apps can automatically create a .nomedia file and place it in with your music files or pictures, etc. When a .nomedia file is present, that folder won't get scanned for media of any kind, therefore your stuff wont show up. I'm not saying that's definitely your problem, by any means. However, simply suggesting that you check your folders, to make sure that the .nomedia file isn't there. I forget which apps can create that file, but I know it can happen.
Click to expand...
Click to collapse
found the .nomedia file. deleted it and pix and music are back. It was at the root of the sd card. Thanks

iknowthefuture said:
found the .nomedia file. deleted it and pix and music are back. It was at the root of the sd card. Thanks
Click to expand...
Click to collapse
Glad to have helped. And I just gave you your first thanks (it was an accident, I meant to hit the quote button, lol). But either way, you got your first thanks! Take it easy.

App2SD now working on S3!

I just received an e-mail from Zeedomax over at GalaxyS3Root.com with a fix for the App2SD problem on the Galaxy S3!
This will allow you to install apps to your SD card on your GS3.
I just picked up a 64gb SD card and will be enjoying all the extra space for my apps!
Here is the link: http://galaxys3root.com/galaxy-s3-t...-external-microsd-for-u-s-canadian-galaxy-s3/
Much credit goes out to Max for his awesome help on Android!
*Note, this does not use the "App2SD" app, it is just a mod that will swap where your phone stores data

Should we wipe and reinstall apps in order to take advantage?

I think that you can uninstall and then restore with Titanium Backup.

How's the performance with using the SD as the main memory?
I'm planning on using my 32gb class 10 sandisk.
feedbacks?

I didn't use it for very long because I still have room with the 16 gb that came on my phone. But when I did, it worked fine for me. I have a class 10 sdxd. If you don't like it though, it's super simple to switch back.

There thread in s3 development already??
Sent from my SPH-L710 using xda premium

Thanks op this works well
from a galaxy, far, far away.

iomega311 said:
I just received an e-mail from Zeedomax over at GalaxyS3Root.com with a fix for the App2SD problem on the Galaxy S3!
This will allow you to install apps to your SD card on your GS3.
I just picked up a 64gb SD card and will be enjoying all the extra space for my apps!
Here is the link: http://galaxys3root.com/galaxy-s3-t...-external-microsd-for-u-s-canadian-galaxy-s3/
Much credit goes out to Max for his awesome help on Android!
*Note, this does not use the "App2SD" app, it is just a mod that will swap where your phone stores data
Click to expand...
Click to collapse
if i recall this is old news now i believe bout 2 or 3 weeks now......that theyve had this already, under android developement section i believe in the second page, but this is still good for people that dont kow and still wanna find it.....only problem bout this is that their is a issue with some phones that when u install this it will swap the storage but ure internal desappears thus leaving u with just the external as a new internal, so u cant access ure real internal anymore due to the lack of support.
there is a way to fix this just follow the instructions here: give thanks to android94301 for figuring out how to do it.
http://forum.xda-developers.com/showthread.php?t=1849861&page=5
As Promised, Solved: another way to do it using Script Manager
--------------------------------------------------------------------------------
I didn't invent this, Zedomax adapted in from mattiadj. But most people haven't been able to get it fully working, probably due to variations in the init.d function of various ROMS. They'd be able to see the External SD card as the internal SD, but the internal SD would disappear. This method avoids using init.d, and instead uses the app Script Manager to load the script on boot.
After much fooling around, I figured out how to do it so the External SD card and the internal cards are swapped, but you can see both with any file Explorer. I got it working on CleanROM 2.0, but it should work on Beans 10 as well.
Here's how to do it: Warning, if you do not understand the following instructions, or don’t have experience doing these things, you probably don’t want to do this hack. I am not responsible if you a) brick your phone, b) delete your data, or c) get very frustrated. That being said, the most likely failure will be that you only see the one card (the External card).
Back everything up that you care about first!!!!
1. First, I'd recommend making a Nandroid backup of your phone.
2. Next, just to be extra safe, I would backup your internal SD card to your PC. While you are doing that, if you have data on the external SD card, back that up too.
3. Next, I would format your external SD card to fat 32. (You could probably use Ext format too, but I didn’t test that.)If you already have it in that format, and have content on it, this won't affect the content, but back it up just to be safe. It’s probably better to have the Ext SD blank to begin with, you can always copy back its content from your pc.
4. Next copy the contents of the internal SD to the External SD card. This is to avoid confusion about apps and such.
5. Next install script manager free from the play store:
https://play.google.com/store/apps/d...51bGwsMSwyLDNd
It will show up on your phone as S manager ads.
6. Download the mod from here: http://downloadandroidrom.com/file/G...EDOMAXv0.2.zip
7. You’ll see a folder called: 11extsd2internalsd_gs3_fat32orextfat_US_ZEDOMAXv0. 2.zip
You need to unzip the folder, then go to System/etc/init.d and copy the 11extsd2internalsd file from there to your phone. Put it into the /data directory. Use Root Explorer, and your phone will need to be rooted.
(https://dl.dropbox.com/u/6305/SD C...0directory.png)
Or you can get just the 11extsd2internalsd file here: https://dl.dropbox.com/u/6305/SD C...tsd2internalsd
8. Using Root Explorer, navigate to that file in the /data directory. Press and hold the file name until the menu pops up, and click on permissions.
https://dl.dropbox.com/u/6305/SD C...ermissions.png
(Unix geeks set them to 777, and everyone else copy the picture below. Click OK.
https://dl.dropbox.com/u/6305/SD C...ings 777.png
9. Open the script manager app, and select Browse as Root in the config screen. Tell it to remember this setting.
https://dl.dropbox.com/u/6305/SD C...and save.png
10. Navigate to the /data directory and choose the 11extsd2internalsd file that is located in /data and click on it. Click on the “Is script” button.
11. Now tap on the buttons that say Su, Boot, and Save. The file name will come up in yellow after the save.
https://dl.dropbox.com/u/6305/SD C...ter save.png
12. Reboot your phone and you should see the swap working and be able to access both internal and external SD cards. The external card will show up as sdcard, and the internal card will show up as extSDCard. Your apps should now install to the external card, since your phone will think it's the internal card. Is that confusing? It was to me too!
Good luck and please share your experiences specifying which ROM you used, so that others can avoid frustration.
Thank you’s always appreciated.

This is not working for me but thanks anyways

the dropbox links are not working... can someone specify what the setting is?
---------- Post added at 10:01 PM ---------- Previous post was at 09:57 PM ----------
gotnoypi said:
the dropbox links are not working... can someone specify what the setting is?
Click to expand...
Click to collapse
never mind, clicking the other link above contains the working Dropbox link

So, would this also work for note2? I can't see any reason why it shouldn't.

manuarh said:
So, would this also work for note2? I can't see any reason why it shouldn't.
Click to expand...
Click to collapse
Note 2 dont have init.d folder and etc is read only can create foldr or paste script

I can't set default storage!
I deleted the mode but when I want to dowload something from play store it said there isn't enough space!!
How can I bakc it???
An can I use this mod with Omega custom rom?

Anyone experiencing their s3 taking long time to charge after using this mod? Before this mod, my phone charge normally. Now it will take forever to go up 1 percent. It has been at 59% for 15min

I a made a Nandroid backup before teying anything. Then I flashed the file using recovery but now I get yhe error that I have insufficient space on my phone and O cant install anything. I restote the Nandroid backup but it is still giving me the ertot. please help!

Looks good to me!

Not working on virgin mobile galaxy s3.

Can't access SD Card on PC since RamExpander installation

Hi!
I recently installed the RamExtender application for my One V so it could run games more fluently.
However, right after installing it and creating a "ram-swapping" partition, my SD Card would not show up anymore in "My Computer" tab. I can only see my phone storage and the H: letter (usually the SD Card) is there but when I click on it, it says "Please Insert a disk into removable disk".
Please see the picture attached to the thread so you can see what's actually happening. The SD Card is not corrupted since my games still work and I can browse its files in ASTRO file manager... HTC Sync Manager won't sync either.
Any ideas how to fix it? I still want to put music and custom APKs in my SD Card!!
Thank you very much everyone

First of all, NEVER use these kinds of apps
if you're ROOTED, flash the Turbo Boost MOD
just delete the swap file u created from the SD card and you should be okay !

Seraz007 said:
First of all, NEVER use these kinds of apps
if you're ROOTED, flash the Turbo Boost MOD
just delete the swap file u created from the SD card and you should be okay !
Click to expand...
Click to collapse
Thank you very much! Well I did uninstall the app and deleted the .swap file left behind by the app, but still the SD Card won't mount on Windows because it seems Ram Expander is not fully uninstalled
What other file/directory should I be looking for? How to be sure it's fully deleted?
Thanks again!

alpha8768 said:
Thank you very much! Well I did uninstall the app and deleted the .swap file left behind by the app, but still the SD Card won't mount on Windows because it seems Ram Expander is not fully uninstalled
What other file/directory should I be looking for? How to be sure it's fully deleted?
Thanks again!
Click to expand...
Click to collapse
well after deleting the swap file should have worked(it worked for me before)
umm try installing the app and then Removing SWAP FILE from the APP itself

alpha8768 said:
Thank you very much! Well I did uninstall the app and deleted the .swap file left behind by the app, but still the SD Card won't mount on Windows because it seems Ram Expander is not fully uninstalled
What other file/directory should I be looking for? How to be sure it's fully deleted?
Thanks again!
Click to expand...
Click to collapse
The best and final way is to make factory reset, wiping everything, including SD card....
Then just install everything from scratch and you'll have working hov...

Seraz007 said:
well after deleting the swap file should have worked(it worked for me before)
umm try installing the app and then Removing SWAP FILE from the APP itself
Click to expand...
Click to collapse
Well I reinstalled the App in order to try it but there is no option to remove the swap file in it I'll try to contact the dev by Email and see what I can do...
*UPDATE* The dev says he's not avaible to provide me support. Contacting another user who used this app before.
bratusm said:
The best and final way is to make factory reset, wiping everything, including SD card....
Then just install everything from scratch and you'll have working hov...
Click to expand...
Click to collapse
*Cut my life into pieces. This is my last resort* -Lyrics from Papa Roach. And here comes the awesome guitar rift!
Hope this will not be necessary. As a newbie in the Android ecosystem (I come from Windows Phone 7.8 lol), I had a real hard time rooting/unlocking my bootloader and installing the new kernel+rom...

U can do 1 thing.....
Use es file explorer and in the menu click on manager then choose SD card analyst.....
Once it stops scanning check 4 swap file if present delete it and reboot....
Hope it solves the issue
Sent from my HTC Wildfire S A510e using Tapatalk 2

[Q] Dumb Question Of The Day: write to external mSD

Dumb Question Of The Day: I put a 64G mSD card into my Kit Kat 600. I don't know how to get data to it. I tried my file manager (ES File Explorer) but it tells me I can't copy to the card because of operating system limits. (I am trying to download videos etc from both Dropbox and Google drive). I thought it was only data created by apps that could not have a "save" directory on the external. What good is the card ?! I am clearly missing something here.
- I will not root yet. Any other help from you folks?
p.s. I can "see" the card with some system files on it.

Are you rooted?

rockjock2020 said:
Are you rooted?
Click to expand...
Click to collapse
No. Not rooted. I would like to avoid rooting for a while.

It's a work around not a true fix. http://youtu.be/tJHhrJfrYJw

Is there any way to get write permissions to SD card - xposed Fix EXTSD dont work

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.