Develop Bugs

Snote won't save. Folder seems "locked"

So I went from Ditto note ROM back to official stock w/ root and everything has been perfect, but I noticed that I can't save s-note files anymore, nor can I copy files to the SNOTE folder unless I have root access. I've cleared snote data, but it's not helping.
Any ideas? This is on the latest 4.4.2 firmware and I've already allowed read/write access to my external card, but the Snote folder is in the internal memory, so that shouldn't be related.

I that similar problem.I did several wipes,flashed different roms-the old roms before official kitkat worked fine,official kitkat based roms wouldn't allow me to save s-notes. I wiped internal memory and it fixed the problem for me.

spookhc said:
I that similar problem.I did several wipes,flashed different roms-the old roms before official kitkat worked fine,official kitkat based roms wouldn't allow me to save s-notes. I wiped internal memory and it fixed the problem for me.
Click to expand...
Click to collapse
I think I solved it... this one's strange!
I created a separate folder and manually copied backups of previous s-notes in there. Then from a file manager I was able to open those files in snote and when I edited them, I was able to save them. The problem, however, is that this custom folder isn't where snote would normally save a new folder, so I went into my file manager with root access and deleted the snote folder. Then I cranked snote back up and it automatically creates a new "snote" folder and it allows me to save now.
Hope that lasts.

[Serious Bugs] Android 4.4.2 Galaxy Note 2

Hello, folks
Recently I upgraded to Android Kitkat 4.4.2 (Indian Version) on my Samsung Galaxy Note II, I have come across a serious BUG after upgrading to Android 4.4.2.
BUG Details: Memory card cannot be read internally
For Instance while connected to Winscp via SSHDroid new folder cannot be created in Memory Card but at the same time new folder can be created in Phone Memory
I guess writing has been restricted
It's not over..... While downloading videos via YouTube Downloader 4.2 (Dentex) when custom folder chosen to memory card downloading gets failed
Again I guess writing has been restricted
I tried 3-4 different memory cards guessing problem might be in memory card (formatted as well)
Flashed my Note II via Hard Reset
Tried all ways and I have come to conclusion the BUG is in Android 4.4.2 Kitkat (Indian Version)
Kindly share if you have encountered same BUG as well (Specially Indian Consumers)
Regards,
Note II

Galaxy Note II said:
Hello, folks
Recently I upgraded to Android Kitkat 4.4.2 (Indian Version) on my Samsung Galaxy Note II, I have come across a serious BUG after upgrading to Android 4.4.2.
BUG Details: Memory card cannot be read internally
For Instance while connected to Winscp via SSHDroid new folder cannot be created in Memory Card but at the same time new folder can be created in Phone Memory
I guess writing has been restricted
It's not over..... While downloading videos via YouTube Downloader 4.2 (Dentex) when custom folder chosen to memory card downloading gets failed
Again I guess writing has been restricted
I tried 3-4 different memory cards guessing problem might be in memory card (formatted as well)
Flashed my Note II via Hard Reset
Tried all ways and I have come to conclusion the BUG is in Android 4.4.2 Kitkat (Indian Version)
Kindly share if you have encountered same BUG as well (Specially Indian Consumers)
Regards,
Note II
Click to expand...
Click to collapse
It's not a bug, it is included in the Kitkat update for security purposes.
There is a fix for that but you have to be rooted.

anesterian said:
It's not a bug, it is included in the Kitkat update for security purposes.
There is a fix for that but you have to be rooted.
Click to expand...
Click to collapse
Bro What kind of security is it? I cannot copy my own files into my memory card
iQuran cannot read my memory card in which has supporting files
I cannot save/download videos from YouTube Downloader to my memory card

What rom are you using?
You can simply transfer your files using a comupter...
Then paste it to your memory card..
That's what I did when I'm on Stock Kitkat ROM...
If you want to apply the SD Card fixed root your phone first.
Sent from my GT-N7100

anesterian said:
What rom are you using?
You can simply transfer your files using a comupter...
Then paste it to your memory card..
That's what I did when I'm on Stock Kitkat ROM...
If you want to apply the SD Card fixed root your phone first.
Sent from my GT-N7100
Click to expand...
Click to collapse
Take a look at my signature

They did what. You can't copy from internal to external memory. Omg i see no 4.4 on my device.
Edit : ok i understand now.
Sent from my GT-N7100

you can copy or move anything with stock file manager My Files..only third party application has no permission to write.

xplore file manager can handle files in sd card too...

Google chose to block write access, for third party apps (those not pre-installed), to external storage; except in their own directories.
There is currently a loophole which some developers have updated their apps to use, but with future iterations of android this will likely be blocked.
This change has been primarily to keep the sdcard clean; un-installing third party apps had left orphaned files the sdcard and resulted in a poor user experience. Personally I'm not sure how viable an explanation this is when you weigh it up against the affect to the user experience of preventing 3rd.P apps from accessing anything outside of their own granted space, or the space granted to a partner app. I think this is either google being evil, trying to lower the value of an sdcard slot to drive OEMs to make devices without one (for various profitable purposes) OR because google goofed on their first time really deciding what access they should have (previously there was no formal access rights definition, it was a free-for-all.)
Hold this space

You can install my apks from play store to back up apk in external card and quick office for editing and saving dox in external card without rooting from play store..enjoy
Sent from my GT-N7100 using XDA Premium 4 mobile app

you are right,writing of sdcard has been restricted in android 4.4.2

Is it possible to revert back to 4.3?

wrena said:
Is it possible to revert back to 4.3?
Click to expand...
Click to collapse
The easiest solution is getting root access and using the sdfix app; reverting is overkill if you just want 3p rw access back.

Happened to me yesterday. I was goin to format my fone, so i took a backup of some apps on helium(Since im not rooted)on my sd card. I formatted my fone. After that wen i went in carbon folder, it was empty. No data.

[Q] SD Card Fix Issue With P600

Hi,
I hope someone has suggestions on the following issue. I've searched threads, but haven't found this specifically.
I need the ability to R/W with multiple programs to my SD card. Due to work and also teaching concerns, I need to access directories of ebooks, articles and databases that are large and in the past were synced from the cloud to my device. Obviously KitKat makes an issue of this.
I recently obtained a Samsung Galaxy Note 10.1 2014 P600. Refurbished by the manufacturer. This has only a one-month warranty so rooting wasn't a concern.
1. I rooted the device using CF Autoroot. Rooting was confirmed by Root Checker.
2. I ran SDFix. No joy. Access to the SD card was sporadic - for example - music on the card would only play 2 seconds of each song.
3. Using Titanium Backup, I froze all Knox-related programs (this was more than the list of 6 I think. I can provide a list later.) Later, I also backed-up and deleted the programs.
Access to the SD card was still sporadic. After a reboot, I might have access for a few minutes, and then restricted access again.
4. I then tried Xposed Framework and the "Handle External Storage" module (see the 3rd method in this article http://technofaq.org/posts/2014/04/fixing-external-sd-card-write-issue-on-android-kitkat/). This worked but still had issues - I had drive access but from time to time it would disappear - it would seem to randomly unmount.
5. But, I decide to keep trying and in the process went to create a folder with File Explorer. FX gave me a message about KitKat - and asked if I wanted to configure it to try to write to the SD card under KitKat. I said yes - and suddenly I cannot access the drive at all.
Android Version 4.4.2
Kernel Version 3.4.39-1462259
Build Number: KOT49H.P600UECNK1
SE for Android Status Enforcing SEPF_SM-P600_4.4.2_0032
The SD card is a Sandisk 128GB.
I haven't tried flashing another ROM because I also need S-Pen and Chromecast functionality - so I just didn't want to fool with it.
1. Does anyone have any suggestions to get SD card RW access?
2. If "No" to the above, what is a good stock ROM with S-Pen and Chromecast functionality that has already addressed the SD issue that I can flash (and where is it located)?
Thank you all for your help.

Have you tried manually editing /system/etc/permissions/platform.xml?
Find this section:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
</permission>
And change it to this:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
[B][COLOR=Blue]<group gid="media_rw" />[/COLOR][/B]
</permission>
Check permissions on platform.xml after editing and fix if needed. Reboot.

blindmanpb said:
Have you tried manually editing /system/etc/permissions/platform.xml?
Click to expand...
Click to collapse
[SNIP]
Yes - I checked SDFix after running it, and platform.xml had already been correctly edited. Thanks for the suggestion though.

Have you tested this SD card in other devices, and other SD cards in this device?

Caveman6 said:
Hi,
I hope someone has suggestions on the following issue. I've searched threads, but haven't found this specifically.
I need the ability to R/W with multiple programs to my SD card. Due to work and also teaching concerns, I need to access directories of ebooks, articles and databases that are large and in the past were synced from the cloud to my device. Obviously KitKat makes an issue of this.
I recently obtained a Samsung Galaxy Note 10.1 2014 P600. Refurbished by the manufacturer. This has only a one-month warranty so rooting wasn't a concern.
1. I rooted the device using CF Autoroot. Rooting was confirmed by Root Checker.
2. I ran SDFix. No joy. Access to the SD card was sporadic - for example - music on the card would only play 2 seconds of each song.
Edit: This ROM would be a good fit for you it has all of the stock features plus some also the ability to read and write to the SD card. http://forum.xda-developers.com/showthread.php?t=2793898
3. Using Titanium Backup, I froze all Knox-related programs (this was more than the list of 6 I think. I can provide a list later.) Later, I also backed-up and deleted the programs.
Access to the SD card was still sporadic. After a reboot, I might have access for a few minutes, and then restricted access again.
4. I then tried Xposed Framework and the "Handle External Storage" module (see the 3rd method in this article http://technofaq.org/posts/2014/04/fixing-external-sd-card-write-issue-on-android-kitkat/). This worked but still had issues - I had drive access but from time to time it would disappear - it would seem to randomly unmount.
5. But, I decide to keep trying and in the process went to create a folder with File Explorer. FX gave me a message about KitKat - and asked if I wanted to configure it to try to write to the SD card under KitKat. I said yes - and suddenly I cannot access the drive at all.
Android Version 4.4.2
Kernel Version 3.4.39-1462259
Build Number: KOT49H.P600UECNK1
SE for Android Status Enforcing SEPF_SM-P600_4.4.2_0032
The SD card is a Sandisk 128GB.
I haven't tried flashing another ROM because I also need S-Pen and Chromecast functionality - so I just didn't want to fool with it.
1. Does anyone have any suggestions to get SD card RW access?
2. If "No" to the above, what is a good stock ROM with S-Pen and Chromecast functionality that has already addressed the SD issue that I can flash (and where is it located)?
Thank you all for your help.
Click to expand...
Click to collapse
Take a look at this thread http://forum.xda-developers.com/showthread.php?t=2741914. It looks like 128Gb SD card only works with 4.3
Edit: Try this ROM it should have RW to SD card. Along with S-Pen and Chromecast ability because it is stock based.
http://forum.xda-developers.com/showthread.php?t=2793898
Sent from my SM-P600 using XDA Free mobile app

Thank you for the prior comments. Due to work and the holidays I wasn't able to reply prior to now.
It turns out the issue was my attempt at using a 128GB card- the Samsung Note 10.1 2014 can apparently only handle up to a 64GB card.
Out of curiosity, has anyone found a way to root and reset KNOX to 0?

Orion116 said:
Take a look at this thread http://forum.xda-developers.com/showthread.php?t=2741914. It looks like 128Gb SD card only works with 4.3
Edit: Try this ROM it should have RW to SD card. Along with S-Pen and Chromecast ability because it is stock based.
http://forum.xda-developers.com/showthread.php?t=2793898
Sent from my SM-P600 using XDA Free mobile app
Click to expand...
Click to collapse
128GB cards do not work with 4.3. I have 4.3 and have tested four different Sandisk 128gb cards in fat32 and Exfat and no luck. Only 64gb works with 4.3 and this was confirmed with Best Buy demo units as well (pre 4.4 update of the demos course).

Caveman6 said:
Thank you for the prior comments. Due to work and the holidays I wasn't able to reply prior to now.
It turns out the issue was my attempt at using a 128GB card- the Samsung Note 10.1 2014 can apparently only handle up to a 64GB card.
Out of curiosity, has anyone found a way to root and reset KNOX to 0?
Click to expand...
Click to collapse
from what I know and read once knox is tripped you cant reset it. I think you can root without tripping it but just cant reset it.

It's a one-way trip!
mikep2323 said:
from what I know and read once knox is tripped you cant reset it. I think you can root without tripping it but just cant reset it.
Click to expand...
Click to collapse
Right! The problem is that "tripping" knox actually changes the hardware. It burns out a fusible link which, of course, can't be un-burnt.

Caveman6 said:
Thank you for the prior comments. Due to work and the holidays I wasn't able to reply prior to now.
It turns out the issue was my attempt at using a 128GB card- the Samsung Note 10.1 2014 can apparently only handle up to a 64GB card.
Out of curiosity, has anyone found a way to root and reset KNOX to 0?
Click to expand...
Click to collapse
Good news! The issue I was having was with the SPECIFIC 128 GB card. I tried a PNY 128GB card instead, and it is working perfectly.

[Q] TItanium Backup SD card not writable after Lollipop Upgrade

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

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.