I've just updated to Marshmallow using LG Bridge. I am setting up some of my apps again, in paticular "Call Recorder".
I have noticed that my microsd card is not mounted as "external_SD" anymore, as it was on Lollipop, but instead as "6901-0911". Is anyone else seeing this on Marshmallow?
How can I fix this and return it to "external_SD"?
Thanks to Marshmallow: This is now standard. No way to change it, except major system changes or at least a Xposed-module.
MickyFoley said:
Thanks to Marshmallow: This is now standard. No way to change it, except major system changes or at least a Xposed-module.
Click to expand...
Click to collapse
In previous version of android there was a system file which you could edit to change the mount point, it seems this is gone with MM.
This really sucks because a LOT of apps have not updated and so when it comes to trying to application data to the SD card these apps fail because they can't find the external SD directory.
It appears that its using the UUID number as the folder name when mounting it..
Related
Hi all,
I am trying to get android to work on my old Tilt2 for my fiance so we can play games together. I've gone through all the steps by adding the correct files to the root of the storage card and running Haret. Every thing seems to work "fine" other than the fact that I can't see a storage card while in Android. I tried to partition my SD card to see if that would help but I am unable to determine the proper way to do that. Any help would be appreciated
Do you have some type of file manager installed on Android? I know that I could always see it, with the exception of the Android folder on my card.
Demonic240 said:
Hi all,
I am trying to get android to work on my old Tilt2 for my fiance so we can play games together. I've gone through all the steps by adding the correct files to the root of the storage card and running Haret. Every thing seems to work "fine" other than the fact that I can't see a storage card while in Android. I tried to partition my SD card to see if that would help but I am unable to determine the proper way to do that. Any help would be appreciated
Click to expand...
Click to collapse
I've said this 100x, not sure why it never shows up on people's searches...
But backup all the data on the card. Format the card (full format, FAT32) using the HP Tool. Restore all the data on the card after the format, or start over fresh doesn't really matter. Apps should now be able to see the card, etc.
I'm not concerned about apps seeing the storage card. I don't have a "My Files" app that will let me navigate the card. Do I need to download a file manager in order for it to work?
I fixed it.. I had to download a file management app I feel dumb now.
Which App?
lotusfrontera said:
Which App?
Click to expand...
Click to collapse
Astro is pretty good, and is included in AndroidApps folder IIRC.
arrrghhh said:
Astro is pretty good, and is included in AndroidApps folder IIRC.
Click to expand...
Click to collapse
Amusingly, I use multiple file storage apps. Super Manager for making system files r/w, and file expert for the look and feel. I have astro too, on my other phone, but only really use it for enabling all file type downloads from the web.
Sent from my SGH-I897 using XDA App
The first thing that bothered me after updating to stock 4.4.2 is the lack of SD card write for media.
Well here i fixed that, (ROOTED users only)
using your root explorer, navigate to /system/etc/permissions/
now look for "platform.xml" back up this file somewhere in case anything goes wrong.
now replace this file with the modified file attached, set correct permissions and reboot!
In case anyone is wondering what change is in the modified file, it is a permission added to write media to sdcard, ( "<group gid="media_rw" />" under external storage)
unzip the attached file (it should read platform.xml), and do leave the feedback.
is it same wtih this program?
https://play.google.com/store/apps/details?id=nextapp.sdfix
is it possible to change the directory of SD card just like previous OS
in kit kat directory is "storage/sdcard1"
in previous OS is ""storage/removeable/sdcard1"
because of this some of my app couldn't detected the data
raitokun said:
is it same wtih this program?
https://play.google.com/store/apps/details?id=nextapp.sdfix
is it possible to change the directory of SD card just like previous OS
in kit kat directory is "storage/sdcard1"
in previous OS is ""storage/removeable/sdcard1"
because of this some of my app couldn't detected the data
Click to expand...
Click to collapse
havent tried the app, but then again why would you want to keep an extra app for something that can be fixed
This doesnt change the directory, only allows the apps to write to sd card.
raitokun said:
is it same wtih this program?
https://play.google.com/store/apps/details?id=nextapp.sdfix
is it possible to change the directory of SD card just like previous OS
in kit kat directory is "storage/sdcard1"
in previous OS is ""storage/removeable/sdcard1"
because of this some of my app couldn't detected the data
Click to expand...
Click to collapse
xyge said:
havent tried the app, but then again why would you want to keep an extra app for something that can be fixed
This doesnt change the directory, only allows the apps to write to sd card.
Click to expand...
Click to collapse
install app, run app, uninstall app. solved with no user interference between and safe from bootloops. also, on JellyBean the sdcard direcotry was the same as KK (storage/sdcard1)
xkeita said:
install app, run app, uninstall app. solved with no user interference between and safe from bootloops. also, on JellyBean the sdcard direcotry was the same as KK (storage/sdcard1)
Click to expand...
Click to collapse
Well part of the reason why I prefer Android is the learning and understanding that comes with messing around with it, so I prefer modifying the system as per my needs
With that said, if the app doesn't require to be kept after fixing the issue it's definitely a good option for the ones who don't want to go with all the trouble.
Sent from my C6502 using Tapatalk
xyge said:
Well part of the reason why I prefer Android is the learning and understanding that comes with messing around with it, so I prefer modifying the system as per my needs
With that said, if the app doesn't require to be kept after fixing the issue it's definitely a good option for the ones who don't want to go with all the trouble.
Sent from my C6502 using Tapatalk
Click to expand...
Click to collapse
I know bro, I'm usually doing things with android modifying stuff here and there but sadly most users won't even do a single search after getting into a problem and that's kinda irritating after some time...
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
Hi,
I updated my G Pad 7.0 Wifi (V400) to Stock 5.0 Lollipop yesterday via OTA and everything looked fine.
I have 2 users on my tablet (one - main - for me, the other one for my girlfriend) and I noticed that the secondary user is unable to mount SDcard at all, so my gf cannot use a big part of her applications.
I already tried rebooting, mount/unmonut and remove/re-insert sdcard, next step should be a WIPE, but I'd like to know first if it's a bug or a Lollipop "security feature" or something.
If you have an updated v400, can you have a try?
Thank you very much!
Davide.
I have a V410. On stock LG kitkat no normal users are able to write to the microSD, not even the primary user. I have to enable root access to even write files to it with a file manager. No lollipop yet on the V410 (not stock anyway).
I know its not exactly what you were asking, but just thought I'd share it. LG definitely has sdcard access messed up in their roms for this tablet line, at least that has been my experience. TWRP, AROMA File Manager, and timmytim's CM12 can all use the sdcard just fine.
jason2678 said:
I have a V410. On stock LG kitkat no normal users are able to write to the microSD, not even the primary user. I have to enable root access to even write files to it with a file manager. No lollipop yet on the V410 (not stock anyway).
I know its not exactly what you were asking, but just thought I'd share it. LG definitely has sdcard access messed up in their roms for this tablet line, at least that has been my experience. TWRP, AROMA File Manager, and timmytim's CM12 can all use the sdcard just fine.
Click to expand...
Click to collapse
Jason, thank you for sharing your experience but I'm facing a different issue. I try to explain it better.
With 4.4.2 I was able to move some of my applications to the sdcard (Settings --> Applications --> [app name] --> Move to SD card). Doing this with my primary user allowed me to save some internal storage space and all of my users could play games that were previously moved to the sdcard.
Now with 5.0.2 everything is fine with my primary user, but with my second user I can't see sdcard at all... I see all my moved application in the drawer as a "generic Android icon", and if I try to launch them I get the "SD card removed" popup error.
I know that in a major upgrade like Kitkat->Lollipop a clean installation with full wipe is required, but I asked if someone with Lollipop could try my same scenario in order to check if this is a common Lollipop "feature" (making a wipe useless) or just a bug due to messy upgrade.
Thanks in advice to everybody for your help.
Just to share my personal solution with all of you: I tried a full wipe with no results. At the end I decided to switch to CM12.1 and this solved my problem.
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.