I just got my v500 and rooted/flashed kitkat (Mahdi Rom) and I was wondering if anyone figured out a way to get apps to SD on the device. I tried the kitkat SD fixer first. When that didn't work, I tried link2sd, which despite trying multiple different file systems, I could not get to work completely (wanted to move app as well as app data, the only filesystem it would recognize was fat32 and would not allow me to move the data). Then I tried foldermount, which works for individual files/folders, but when I try to move android data/off it just tells me to use a sub-directory.
So I was just looking here to see if anyone has managed to do it and how. Preferably in the style Jelly Bean allowed where you could just select "Move to SD" in the app settings.
Thanks
zetorung said:
... Then I tried foldermount, which works for individual files/folders, but when I try to move android data/off it just tells me to use a sub-directory.
Thanks
Click to expand...
Click to collapse
What do you mean by move android data/off ? you mean move the folder android entirely ? I use kitkat and foldermount unlocked version and i move my apps one by one with folder corresponding in android folder.
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
I have just installed cyanogenmod 10.2, android 4.3 on my samsung s4 lte version.
It is a great rom, but I am not able to move apps to my SD. Even if I download Link2SD or FolderMount, which I paid for, they both seem to act
weird and complain. How can I transfer my games and apps to my SD card?
Thanks
alrosh7 said:
I have just installed cyanogenmod 10.2, android 4.3 on my samsung s4 lte version.
It is a great rom, but I am not able to move apps to my SD. Even if I download Link2SD or FolderMount, which I paid for, they both seem to act
weird and complain. How can I transfer my games and apps to my SD card?
Thanks
Click to expand...
Click to collapse
FolderMount, the free version works great for me on CM10.2.
ladislav.heller said:
FolderMount, the free version works great for me on CM10.2.
Click to expand...
Click to collapse
How do you use it? Do you manually create the link ? I didnt have to do that with the stock ROM. Also in the app list, it lists many applications as
0 bytes.. and can't do anything with them
alrosh7 said:
How do you use it? Do you manually create the link ? I didnt have to do that with the stock ROM. Also in the app list, it lists many applications as
0 bytes.. and can't do anything with them
Click to expand...
Click to collapse
Yes. There is a "+" sign in the menu. Tap on it and FolderMount (FM) will ask for source folder (you can browse it via UI) and also asks whether it should create the destination folder automatically.
For example I have Sygic maps on internal SD (/sdcard/Sygic) which is a quite big folder, around 5 GB. So I inked it to external SD - FM autocreated it on external SD and moved the files.
Try to find Youtube videos about FM usage.
ladislav.heller said:
Yes. There is a "+" sign in the menu. Tap on it and FolderMount (FM) will ask for source folder (you can browse it via UI) and also asks whether it should create the destination folder automatically.
For example I have Sygic maps on internal SD (/sdcard/Sygic) which is a quite big folder, around 5 GB. So I inked it to external SD - FM autocreated it on external SD and moved the files.
Try to find Youtube videos about FM usage.
Click to expand...
Click to collapse
Thanks!
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...
Hey warriors!
Pls help - after installing apk and storing obb files into sd card/android/obb folder I cannot run any HD game with my G3. The application will not find the files.
My procedure:
- download apk + cache
- install apk
- place obb files into obb folder (usually the files are already in a correctly named folder, e.g. "com.pixelbite.rr3" (for recklessracing3), so I just extract and copy them from my PC over to SD card)
- run apk - it will then give me an error message, or just look for the files for eternity, or simply just crashes
I have tried couple of games - NOVA3, MC5, RecklessRacing with no luck
- is it because I am not rooted?
- is it necessary to change something in phone settings prior to installing?
- or simply what I am doing wrong?
Many thanks for your help!
leeris said:
Hey warriors!
Pls help - after installing apk and storing obb files into sd card/android/obb folder I cannot run any HD game with my G3. The application will not find the files.
My procedure:
- download apk + cache
- install apk
- place obb files into obb folder (usually the files are already in a correctly named folder, e.g. "com.pixelbite.rr3" (for recklessracing3), so I just extract and copy them from my PC over to SD card)
- run apk - it will then give me an error message, or just look for the files for eternity, or simply just crashes
I have tried couple of games - NOVA3, MC5, RecklessRacing with no luck
- is it because I am not rooted?
- is it necessary to change something in phone settings prior to installing?
- or simply what I am doing wrong?
Many thanks for your help!
Click to expand...
Click to collapse
Most of the time, that stuff is stored in the /data partition which you cannot access to write to without root. The only "people" that can access and write to that area are the app itself that wrote to it initially, and an account with root access.
Some games might store some "cache" to the internal sd card, but that all depends on the app.
This is why using the cloud is so much better for game advancement, but not all games are using that.
iBolski said:
Most of the time, that stuff is stored in the /data partition which you cannot access to write to without root.
Some games might store some "cache" to the internal sd card, but that all depends on the app.
This is why using the cloud is so much better for game advancement, but not all games are using that.
Click to expand...
Click to collapse
I think I got your point but what would be the safest way to install games without issues? Will rooting the device solve the problem, or is there still some work to do most of the time with every game?
And if root is OK, is there any one-click root available for G3 which is safe? I am very good at bricking the phones
leeris said:
I think I got your point but what would be the safest way to install games without issues? Will rooting the device solve the problem, or is there still some work to do most of the time with every game?
And if root is OK, is there any one-click root available for G3 which is safe? I am very good at bricking the phones
Click to expand...
Click to collapse
The only other way to make this work, and you would have had to backed everything up before, is to use Helium which (without root) requires you to have a Windows or Mac client app installed on your PC and you hook up you device that way. It can then backup the data and restore it, without root. However, it only works with certain apps. Not all apps can be backed up with Helium.
As for rooting, it depends on which model of G3 you have. Overall, rooting is easy, but it depends on which version of the Android OS it's running and again, which model of G3 you are using. I don't want to go into it with this thread as it can all be discovered by going to the following FAQ thread in the OP and finding the section for rooting. There it explains which root method works on which model of phone and what version of the OS you must be on. Again, this all depends on the model of the phone you have. Here is the link to the FAQ post:
http://forum.xda-developers.com/lg-g3/help/help-thread-lg-g3-question-t2947298
After that, you can use a lot of different apps to backup and restore your app and data. TiBu is the most popular one.
iBolski said:
The only other way to make this work, and you would have had to backed everything up before, is to use Helium which (without root) requires you to have a Windows or Mac client app installed on your PC and you hook up you device that way. It can then backup the data and restore it, without root. However, it only works with certain apps. Not all apps can be backed up with Helium.
As for rooting, it depends on which model of G3 you have. Overall, rooting is easy, but it depends on which version of the Android OS it's running and again, which model of G3 you are using. I don't want to go into it with this thread as it can all be discovered by going to the following FAQ thread in the OP and finding the section for rooting. There it explains which root method works on which model of phone and what version of the OS you must be on. Again, this all depends on the model of the phone you have. Here is the link to the FAQ post:
http://forum.xda-developers.com/lg-g3/help/help-thread-lg-g3-question-t2947298
After that, you can use a lot of different apps to backup and restore your app and data. TiBu is the most popular one.
Click to expand...
Click to collapse
But when a game with cache is officially downloaded from Google Play - this should work more or less correctly right?
leeris said:
But when a game with cache is officially downloaded from Google Play - this should work more or less correctly right?
Click to expand...
Click to collapse
What? You have me confused.
What are you expecting to happen when you download an app from Google Play? Not sure what you are asking...
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.