yashsingh1/xdaforums huggingface dataset:
[Android Software Development] madmack:
That ramfs is the problem right there. The only way for binds to work is to mount them to the source mountpoint (/mnt/media_rw/sdcard0) and not some fuse daemon layer (/storage/sdcard0) so FM is doing what it should. It works on all devices that have the correct ramfs implementation. I have no idea why your rom dev decided to do -u 2800 -g 2800 -w 2800. Makes no sense to me and could very well explain your write issues. If you're able to rebuild the ramfs into the kernel, change this line to make it look like the sdcard1 and you should be good. (i.e. 1023). Look at this for a good example.

Noted ! thanks. at the moment, FM does ask if you want to move the data back to the source when deleting a pair but the destination folder itself remains (albeit empty).
[Android Software Development] Antiga Prime:
Excellent, thanks, I'll try that.

On the other hand, this app seems to work, and according to this post in another CM11 thread, it might be something that should be changed in the app. I don't know which is the correct implementation, just handing off information I've found. If it works I'll report back.
[Android Software Development] Antiga Prime:
Ok, so I was able to change that line and repack the kernel, but now it turns out that the entire /storage/sdcard0/ folder/mountpoint is empty even though I can see it's mounted:

/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

Could it be maybe a permission issue? In your example, the service command for the sdcards uses a -d switch, but on my ramfs they don't have that -d switch, and the /storage/sdcard0 even has an additional -w switch. Any ideas on what these do?

On the other hand, it would seem to be that the app I mentioned earlier, which is working the way Foldermount works on 4.3, is using this method, as so are others; I, on the other hand, can't seem to grasp on how it's working. Just thought you might want to know.

Thanks again.

Edit: Also, I had edited my "platform.xml" file as described here, just in case it matters.
[Android Software Development] madmack:
Interesting. If you want to know what these parameters refer to, look up this.

The debuggerd stuff you talk about is no longer necessary if you're using ChainFire's SuperSU > 1.93. Read up on his Google+ account for more info. As a matter of fact, StickMount itself abandoned that approach recently. FM switches between the debuggerd and the 1.93 method automatically depending on your root app so this isn't the culprit. I'm pretty sure it's a permission issue you're having. Either reformat the internal vold device or somehow find a way to fix the permissions on it. I don't even know what UID, GID 2800 is which is what your device is currently using. If I had more time like in the good old days, I would try to get my sdcard working with the default U/GIDs "1023" before trying again.
[Android Software Development] Antiga Prime:
Well, regarding the permission issues, I was talking about that when mounting a pair with Foldermount, the CM filemanager wasn't able to access the mounted folder (as seen in the screenshot I posted previously). Most other apps showed the folder as empty. In fact, when I did mount a folder, the only app that could see the contents of the folders was the app performing the mount, whether it was FM, terminal, Smanager, SSH terminal, etc.

This ROM comes with Superuser already installed, so I didn't think much of it. Are you suggesting that if I switch to SuperSU, FM might work? (EDIT: Switched to SuperSU 1.93, no mounts worked after that).

Edit:

-w: specify GID required to write (default sdcard_rw)\n
-d: derive file permissions based on path\n

Edit 2: [MENTION=1436971]madmack[/MENTION] Sorry for being such a pain; having said that... I realized that the /mnt/media_rw/sdcard0 mount point is made with user:root and group:2800, so even after correcting the User and Group for the FUSE mount service, I'd imagine most things wouldn't have access to the real mount point and, of course, the files on said internal memory, and I can't seem to find where on earth is the command (which I assume is also in the RAMFS) that mounts the filesystems, with that user and group in particular.

The fstab.qcom file has:

/devices/platform/msm_sdcc.1/mmc_host/mmc0 auto ext4 defaults voldmanaged=sdcard0:15,nonremovable,noemulatedsd

But that doesn't specify anything regarding user and/or group. :confused:
[Android Software Development] madmack:
No clue. Could be kernel related although I really doubt it. If I had the device and ample of time, it would be an interesting little project to fix... Unfortunately I have neither.
[Android Software Development] Antiga Prime:
Well, I decided that if I can't find out where it's getting those permissions from, I might be able to change the permissions, so I did:

chown media_rw:media_rw /mnt/media_rw/sdcard0

And it finally worked, mounting in FM works as it did, files do appear in both folder pairs and in /storage/sdcard0 in general.

I'm using the kernel I modified as per your instructions, and even though I don't know if running that previous command on the unmodified version would work, I'm happy with it working the way it is now, so thanks again for all your help in pointing me in the right direction.
[Android Software Development] madmack:
Awesome work. Thanks for letting me know. I actually learned something now and you should probably pass this info out to your dev so they can incorporate this chmod trick into their cwm installation script file.
[Android Software Development] Antiga Prime:
Spoke too soon; even though FM does mount the folder, nothing else can write to /storage/sdcard0, even though /mnt/media_rw/sdcard0 is writable, apps use /storage/sdcard0/... I'll post back if I find a solution, lol.
[Android Software Development] iknight8:
Worked like a charm. Tried Link2SD but gave the worst headache trying to set up and getting it to work.
[Android Software Development] timonoj:
Help! I'm a bit weirded out by FM's behavior. To be honest, it never worked for me, but I was giving it another shot, as I'm very frustrated due to storage.

Anyway. I found FM lists some very old folders its been long since they no longer exist. I deleted the app, even deleted the dalvik cache, and yet the folders keep showing. Not sure why.

FM listing of /storage/emulated/0/Android/obb

However, ES File Explorer can't find an Emulated/0. I guess it works in a different mode?

For the same folder (it goes through /storage/emulated/legacy/Android/obb):

...and I also get this last listing through adb shell:

So as you can see, FM seems to be showing an older version of all these folders. Even crazytaxi now has moved to crazytaxiplayheaven, but FM will still show the old version.

I tried to navigate FM to /storage/emulated/legacy, but that folder shows empty. Also it shows no linked folders.

EDIT: I found /mnt/shell/emulated/obb on the adb shell. It displays the same folders as FM, but I can can't find these folders anywhere else on the system. What is this sorcery? Too damn much virtual storage!
[Android Software Development] madmack:
Don't mess with all these paths. all you should care about are two paths:

1. /storage/emulated/0/ (which is what every app receives when they call the android default storage APIs). In FM, you should ONLY link to subfolders of this path. Everything else is at your own risk and I don't support it.

2. /data/media. If you're using an emulated storage, your data exists on this partition. when you navigate in /storage/emulated/0/Android/obb in FM, you're really looking at the content of /data/media/obb/. Everything else, you're looking in /data/media/0/

You can ignore the rest. Not sure why you're messing with them. Too much virtual storage indeed.

Given the discrepency I'm seeing in what FM and what ES File Explorer is reporting. You might be running in the KK custom kernel bug. If so, have your dev look at the OP of this thread. Namely THIS
[Android Software Development] timonoj:
Thanks for the help. Sadly in my kernel it won't be easy, as you guys already checked. It's ktoonz running on danvdh's ROM. Just the other day a guy commented (in an androidpolice comments in an article about SD cards) he was able to mount folders just fine using the same kernel/rom, so I got encouraged to fiddle a bit to see if I could figure what was wrong in my case. Thanks for the guide with all the details, I'll try to learn if I can recompile my own custom kernel :)
[Android Software Development] Mike B.:
FYI, my i747 currently runs a slightly modified version of Danvdh's 5.4 ROM with the 02-01-2014 build of the KT747-TW-JB-4.3-ATT kernel. FolderMount Premium v2.6.4 works perfectly for me, dependably linking several SD (/storage/emulated/0/) directories to the external card without any problems whatsoever.

I never tried ES File Explorer, but Root Explorer, Terminal, and all other tools correctly find both the internal symlinks and the external targets. Perhaps it's time for you to try some minor additional "fiddling"? ;)
[Android Software Development] 911-Future_Maker:
Hi m8, can you make some option for power users who knows what they're doing to disable the reminder message when browsing up to root?
[Android Software Development] madmack:
I'm against cluttering the setting menu with options. Is it really that bad? How often do you click on this anyway? Advanced users can always "dismiss" that message instead. ;)
[Android Software Development] egingell:
A checkbox on the dialog?

To answer the question: someone who's setting up for the first time might have to see that dialog a lot.

Besides, when someone sees the same warning dialog multiple times, one tends to assume that it will be that one every time and miss something important. Like "your phone is about to explode. Click OK to skip the countdown".

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Android Software Development] auldthief:
Obb folder on my PC!!!

OK, so this was fun. I mounted a hard disk partition as a cifs share using mount manager. Then I used directory bind to bind the obb folder on the internal memory to this cifs share. Directory bind transferred all the data on the obb folder in the internal memory of my MK908 android TV to the network share. I was able to transfer obb folders for Asphalt 8, MC4 and nova 3 from the internal memory to the mounted obb folder. This way I have an obb folder equal in size to the hard disk partition (50 GB!!!).

THe problem comes when I try to install games that download game data directly to the external SD, like real racing 3. Since directory bind was designed to mount internal SD folders to external SD, I am not able to bind external SD folder to internal SD (where I mounted the CIFS share) and the app hence tells me that I do not have sufficient storage on my SD card, which is true ( since I only have a 2 GB SD card on my MK908). I was wondering if anyone here can tell me how I can make the app install gamedata on the internal (mounted) folder rather than on external SD. Hope I was able to explain the problem to you guys clearly, cuz when I read this back, I find it hard to understand myself! :D
[Android Software Development] 911-Future_Maker:
Well not that often, I just mounted my thumbnails folder to system which all we know was always recreating itself and eating space,

but no more as system is read only memory. D: The real thing that bothers me is that I have to ignore that message on

every new mount entry I'm adding because I have to browse up to /root/storage to select a specific folders on my extsdcard and usb drive.

Thx anyway, I'm really greatful you made such as great app.
[Android Software Development] madmack:
Check box will do! Not sure how users will revert that option in the future other than resetting the app's data but they're advanced anyway so I'm sure they'll figure it out. I just added it to the to do list. It might be a little while before it gets implemented though given that I'm and will be out of town for quite some time.
[Android Software Development] androidfreak70:
bad app:( when i click on pin icon my device reboot:( then when its turn on reboot again its reboot after i see MOUNTING FOLDERS in nofication appear i uninstalled the app now my device fine but any can help?:(

my device c6602 4.3
[Android Software Development] egingell:
Try the solution in the FAQ. It's for 4.2 , but it's also specifically for Xperia, so it might still apply.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Android Software Development] androidfreak70:
ok i will try
[Android Software Development] Everblue:
hello, thank to dév for this app. I use it for my samsung smartphone and is very usefull. :good:

I buy a Archos gamepad 2 and whit this device, the mounted folder is on protection write. can not copy or create files and directory in mount point.

Any suggestion ?
[Android Software Development] madmack:
send me a bug report (from app setting menu) and I'll take a look. Mention the issue on the top or bottom of email before sending it out.
[Android Software Development] stormy_ugur:
this app is not working on kit kat on note 3 n9005
[Android Software Development] madmack:
It does on my note 3 with kitkat.
[Android Software Development] stormy_ugur:
Do you using Custom or stock rom ?
[Android Software Development] AASonyKK:
Thanks!

An entry in the options like "Try the write permission" for the "advanced" user is a bad idea?

One thing, if I try to edit an old link and their destination path do not longer exist I'm unable to edit it. I think this happen because the old path do not longer exist. If this is the case you can easily add a control and in this case let the user choose the new path from the root and not from the old path.
[Android Software Development] madmack:
stock. Always. If FolderMount works on stock, then the issue is with the custom rom. I support stock roms only.

Try the write permission? Didn't understand that one.

I'll look into that bug! Thanks for letting me know. Usually pinning a folder pair will create the destination if it doesn't exist unless FM doesn't have write permissions to the path.
[Android Software Development] stormy_ugur:
Sorry but why stock roms only? We are not human who are using Custom rom?;) what is the differents between stock and custom?
[Android Software Development] AASonyKK:
I read fast and didn't noticed that you talked about dismiss the dialog for navigate the root and not dismiss the warning write error with FM unable to write into the external sdcard.

About the destination, I used Android stock with stickmount and the sd was mounted in /storage/emulated/0/usbstick/sda1.

Now I use Paranoid and it automatically mount the sd in /storage/emulated/usbstick so I needed to change all my links but the old folders do not exists anymore.

I did't try to pin them first.
[Android Software Development] madmack:
You do realize that there are thousands of custom roms out there right? It's impossible to support that when the rom dev messed up the stock ROM so bad that apps like FolderMount stop working. I don't know what's different, ask the rom owner. His problem really, not mine.
[Android Software Development] madmack:
I don't think pinning them will work for you given that the mount point is now different. Unfortunately recreating the pairs is probably your only way to fix it atm.
[Android Software Development] Mike B.:
A stock ROM is released by the device manufacturer and is usually very stable but often less than exciting. Custom ROMs are created/modified/mangled/enhanced by someone else and can be either much better or much worse than stock. If something as clean and straightforward as FolderMount doesn't work on your (supposedly compatible?) ROM, you probably don't have one of the "much better" ones... ;)
[Android Software Development] stormy_ugur:
yea there are thousands custom roms but i asked you what is the different between custom and stock roms? it's mean it is hard to make available folder mount app for custom roms? what is the different for you? if folder mount app support just stock roms why not support custom roms? i think you can do this .thanks

yea i see :) i think custom roms much better than stock roms. i hope the developer of Folder Mount can see us here who are waiting this app for custom roms :)
[Android Software Development] egingell:
Your definition of "better" is presumably based on aesthetics and other end-user criteria. Programmers see way more than that.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Android Software Development] InevitableDJ:
Guys a quick question hopefully, I have a Samsung galaxy S5 SM-G900F when moving the obb of a game it copies it over but the obb file still remains in /android/obb

It's also the same file size as the one that's moved to my sd card.

Why is that happening?

EDIT: mange to move the files deleting and re adding but now everytime I go in to the game it asks to download it again.

Final fantasy 6 is the game
[Android Software Development] mvladimir199:
HTC Desire 601(4.4.2) Zara_ul_Europe

Greetings!

Will there be a patch for HTC Desire 601 (Android 4.4.2)
[Android Software Development] sicnarf007:
me too. im using foldermount premium but not works. im running kitkat leaked rom in my note 2. but if i use the normal foldermount it works but i can make only 3 mounted files.
[Android Software Development] MihaiA7X:
will this app work on galaxy trend plus?? it has android 4.2.2!! I want to know before rooting my phone...if it does i'll buy premium right away because I tried everything to move data from internal to external...

EDIT: the app works!! tested it and bought premium!! Awesome work thank you!!!
[Android Software Development] madmack:
Interesting. The same segment of code is executed when you click on "detach all" or when the tasker APIs are called. When you've done a "detach only" tasker profile, does anything at least appear in the status bar? It should say something along the lines of "unmounting all folder pairs".
[Android Software Development] danarama:
Yeah it does.

I've made a little video to demonstrate.

https://www.dropbox.com/s/procvce6omtf92i/fm.mp4
[Android Software Development] madmack:
I've just ran a quick test on my phone and the tasker profile to unmount all seems to work just fine. :confused: I can't think of anything obvious on why it might not work for you.
[Android Software Development] danarama:
No, It makes no sense to me either. Are there any troubleshooting steps I can take?
[Android Software Development] madmack:
Hold on. We might be looking at a bug that is related to the "otg" device lookup.
[Android Software Development] danarama:
Interesting. How can that be identified? Why would the tasker task operate differently to in-app?
[Android Software Development] madmack:
try this apk. see if it works?
[Android Software Development] madmack:
I literally haven't changed a thing in the mount all function between this version and the play store version. Maybe something else is at play here.
[Android Software Development] danarama:
Odd.

2.6.4 restored. Mount all working again. Unmount as previously reported

Edit... Really don't know if logcat is useful and whether it records anything at all but I made one anyway
[Android Software Development] ivanchin99:
Updated a new version of Asphalt. Removed the old one. Now foldermount cant detect the obb folder of Asphalt 8. But it still shows the 1.6gb file size of Obb root folder. I cant link/mount the files :confused:

Folder is visible with other file explorer:rolleyes:

Edit: Submitted bug report
[Android Software Development] samt3:
I have a S4 sch-r970. I triple boot it. I use SOKP most of the time its my third rom on the phone. Also have cm11 and my secondary and stock touchwiz as my primary. Anyway i can't get this to work with SOKP or Cyanogen but it works fine on touchwiz. Thing is on my AOSP roms it mounts my external sd or sdcard1 but shows up empty on my internal sd. Ive tried switching back from custom kernel to stock kernel then back to ktoonez kernel but no difference. I run Ktoonez on all three of my roms through. So doubt thats the problem. Even updated Cyanogen so see if that made a defferecne being I got the CM11 and the SOKP build the same day didnt know if it was a problem with CM and got built into SOKP being its based of CM. Any ideas what the problem maybe?
[Android Software Development] jayinc11:
I want use, and FolderMount the entire data/data folder instead of individual folders within the data folder. My only concern is folders such as provider.settings, provider.telephony, cellbroadcastreceiver, etc. that look like they are part of system functionality, if they get mounted on the sdcard whether this will cause issues. Phone is sammy i717 BeanStalk 4.4.2 ROM
[Android Software Development] danarama:
Even if it were possible via this app it would be a really BAD idea. But Its not possible.
[Android Software Development] egingell:
Yes. It will cause huge problems. Unless you can ensure that the data will be available immediately - not after the phone finally mounts the SD card - and that the owner, group, and permissions are correct which can't be done with FAT32, don't do it.

Well, it is technically, but you'd have to do all the legwork.

And another thing: The phone reads from the data partition and loads it into memory, so even after Folder Mount mounts the folder, everything that was already read (buried data or nothing?) will continue being used - not the settings you expect - and the erroneous data will overwrite your old data.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Android Software Development] danarama:
Not to mention the data of the folder pairs needed to mount the folder aren't existing in /data/data because you moved it to /sdcard. Needs to be mounted in order to mount. Catch 22
[Android Software Development] egingell:
Indeed. Plus what I added to my previous post in edit just now.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Android Software Development] jayinc11:
Thanx guys. This data folder is whopping 430mb with almost 4800 files. I would have loved to show it the way to the SD card. I guess I will do per installed/downloaded app.

BTW This is a fantastic app, I also dig that it fixes write permissions for 4.4.2. It's a must have in my arsenal of phone setup since I root & flash a lot.

So backing app and restoring is important. I noticed tho' that there is no option to select destination of the backup settings say to SD Card. I know FMount it too but I think an option to re-direct destination folder would be great. Otherwise one has to remember to copy the backup to sdcard before flashing a new rom.

Also instead of overwriting the last backup is it possible to create a new backup settings with each new backup?

Like I said nevertheless an awesome app! Great job!
[Android Software Development] egingell:
Personally, I always forego the in-app backup and use Titanium Backup. There are others if you don't want to use Titanium Backup.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Android Software Development] ahac85:
Hi I got this working on my HTC one m8, I wish to unpatch the system, can I ask what files were patched? Also when I uninstall this app and reinstall it an symlink is still there which I deleted

Sent from my HTC One_M8
[Android Software Development] madmack:
This logcat won't help me unfortunately. There is a bug currently that I want to take care of the proper way before we can test anything new. I want to take care of auto detection of mounted OTG devices on KK devices and offer users a list of external sdcard options if more than one is available which isn't currently the case. This is very likely why FM isn't working for you at the moment. Unfortunately, I won't have much time to sit down and put that into FM's code until sometime in June perhaps. It'll happen eventually though. :)
[Android Software Development] danarama:
No problem... No rush. It works through the app, so no big deal.

Thanks :)