yashsingh1/xdaforums huggingface dataset:
[Android Software Development] gelhack:
:good: You are obviously better at it than I am. All I found was a bunch of Java stuff, no shell command. I'm going to play with it a bit to see if I can get it to just scan the linked folders and not the entire SD card.
[Android Software Development] madmack:
Is the infringing app taken off again? Maybe the stealer is "unpublishing" or something. :confused:
[Android Software Development] madmack:
I have not attempted that. Thanks for the info. You know most apps out there use java sendBroadcast methods? lol. That includes Rescan ROOT from the play store. I'm wondering whether there are any caveats to this command: if it work on all android versions, etc.

In any case, I don't think FM needs any of that now. This command won't remove content from gallery unless I'm missing some use-case.
[Android Software Development] ksbansal:
Great app!!!!!

The most bug free internal to sd app ever but it would be great if you make so you can select applications to move? Rather than finding folders and creating folders manuay. But still the greatest folder mounting app :). I would upgrade if you could add a feature like that.
[Android Software Development] egingell:
Yeah, and Java is purposely written to be overly complicated.

Sent from my SPH-D710

---------- Post added at 12:16 PM ---------- Previous post was at 12:14 PM ----------

That would require some voodoo magic. If they all stored their crap in predictable places, it wouldn't be a problem.

Sent from my SPH-D710
[Android Software Development] madmack:
+1 :good:
[Android Software Development] lord_muad_dib:
you're indeed right, i wiped /system, reflashed the rom and so far it's all working

i don't know what was messed up though.

i haven't tested many apps so far but r/w is working good

damn it was hard without foldermount :D

thank you man
[Android Software Development] chegeluuv:
Just to confirm, FolderMount v2.9b doesn't work on my HTC One M8 CM13. :crying: :( The app installed fine and asked for permissions correctly. Just couldn't get SuperSU to install, even though it works on stock.

Thanks for the effort though. :good:
[Android Software Development] SpasilliumNexus:
No go on a Moto X Pure Edition with stock 6.0 Marshmallow. Setting up mounts seems to go well in the app, but checking the source folders comes up empty. I've tried permissive on boot, but got the same results.

Here's my Pastebin of FM's logging: http://pastebin.com/0XBmrPeN

And here's my Pastebin of my build.prop: http://pastebin.com/SkXu6mwd

EDIT: I remembered this app wanting to fix an entry in build.prop. I'll see if I can find it.

EDIT2: 'persist.esdfs_sdcard=true' was the entry. Changing it to 'false' fixes the mounts, and works in Enforcing.

Also, 'persist.fuse_sdcard=false' was another entry that FM wanted to change in Lollipop, but now it's set to 'true' by default in Marshmallow.
[Android Software Development] madmack:
Thanks for this. I'll make sure the patch is applied to versions above Lollipop as well. I usually only fix build.prop for versions of Android that I've confirmed working so the patch was only getting applied to Lollipop. Easy fix.
[Android Software Development] Rintenfinten:
I just installed cm13 (CM Remix on Note 4) to test FM.

FM tries to write to sd card but fails. Trying to repair also fails.
[Android Software Development] egingell:
FM 2.9b works perfectly (aside from the afore mentioned file moving operation - it crashes FM) on both TW LP 5.0.1 and 5.1.1.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[Android Software Development] smallKING81:
The program v. 2.9b can't detect and create folder of destination automatically. The field "folder of destination" is empty.

I use HTC One M8, ROM Viper 5.0.1 MM
[Android Software Development] mazlixek:
LG g flex 2 here, installed and bought app, installed games, sucessfully moved with this app, but when I try to launch some game, it wants to download the data again. I can see the data on external SD card, but games want to download it again into internal memory. Android 5.1.1, any suggestions? Tried it with Asphalth, UFC, Dead Trigger 2, UNSKILLED, Modern Combat 5 etc. All games first launched and downloaded everything to the point of playing, then I used FM to move the data files, but then the game want to download data again. whyyyy, was really looking forward to have multiple games installed.

EDIT: pins normally working, but it has no effect on the games, what should happen when I enable some pin? Should any file be created in the internal memory? Should internal data and obb folders look same as external?
[Android Software Development] GiRaFa-SAMA:
Not working on Galaxy S4 GT-i9505 using JDCT 6.0.1

My error : internal folders are inaccessible

Enviado de meu GT-I9505 usando Tapatalk
[Android Software Development] HJarausch:
2.9b works on my Galaxy S5 with Android 6.01 but there is a catch.

There are still these silly MM restrictions for write access to the external SD card.

E.g., when I use FM to mount /storage/emulated/0/Pictures to my external SD card Pictures I cannot do screen dumps anymore - it reports access restriction errors.

For other applications there seems to be an exception: if one binds "the application's home directory" on /data/data/<App Provider> to "ExtSDcard"/Android/data/<App Provider>, it seems to work.

I wonder how the access restrictions to the external SD card are implemented. Does the "open system call" compare the path to the name of the provider of the application?

Thanks for some info on these items,

Helmut.
[Android Software Development] lupick:
Same Issue here With MM on Nvidia Shield tablet.

even if I grant the permission to SDCAR at firs run FM cannot create any folder on SD. ES filemanager for example is able to do that.

Here the lig

https://docs.google.com/document/d/...yWlMMrVrE-MuZ90NblVBk7E/edit?usp=docslist_api

Maybe this could be the culprit:

757:com.android.externalstorage/u0a6 for content provider com.android.externalstorage/.ExternalStorageProvider

03-07 20:11:26.653 19757 19757 W System : ClassLoader referenced unknown path: /system/priv-app/ExternalStorageProvider/lib/arm
[Android Software Development] elcomm:
CM13 fresh install on a Tab Pro 8.4 (mondrian), reinstalled all apps with Titanium, then installed Beta.

Picked up all my existing links no problem, but program closes when I try to copy new stuff over (like you said might happen).

PS Permissive or enforcing same thing
[Android Software Development] mv:-):
I'm getting an "Out of Space" error. I'm able to install other apps though -- I even installed random apk/apps just to see if I get the error.

If I install the current non-beta version from Play Store, I get error 506 ("Can't install app").

What do these errors mean? Any workaround/fix?

[Tried clearing cache, data, restarting but still a no-go; Custom ROM: MM/CM13, GBs of free space, both internal and external storage]
[Android Software Development] marvi0:
Same here not working on nvidia shield tablet.
[Android Software Development] Joker87:
Any chance to make it working with micro sd encryption?

I tried and it doesn't work on galaxy S5
[Android Software Development] HJarausch:
There is a general problem (for me, at least). I have done "mount -o bind" which works just fine (as does foldermount), but the target folder doesn't have read permissions - therefore no files are visible for the non-root user (which is the case with Foldermount 2.9b, as well). And I can't change these permissions (even with a root file manager) probably because Android 6 mounted these folders with a user mask.

Does anybody know how to change the mount options which are used by Android 6?

Many thanks for a hint,

Helmut
[Android Software Development] PpukisS:
"Create folder failed. Permission problem?", " unknown error" in the notification

Hello,

I have rooted Acer Iconia One B-750 with Android Kitkat 4.4.4 and the latest version of FolderMount and I have problem with mooving files and problem with creating folders. There is the same problem that I have :

"Hey guys. So I put this on my Huawei u8650 running Cyanogen 7.2 which is a modded Android 2.3.7 and it doesn't want to move the files. I go to the Apps analizer, select an app, create pair, it asks if it wants to create a destination folder automatically and I say Yes. But it doesn't create one. And no matter where I try to put it, it says "Your source directory is not empty. Would you like me to move the files to the destination (and possibly overwrite destination files?)". Doesnt matter if I say yes or no, it tries to move it and it fails. So I try to add a folder with the app and it says "Create folder failed. Permission problem?" no matter where I try to make a folder"

With ES file manager or ASTRO file manager I can create folder or moving files anywhere.

Can you help me with this problem please ?
[Android Software Development] MrHomebrew:
Hello Hello. Been a wile sense we worked on a new phone compatability for FolderMount. Back when FolderMount was first created. My how it has grown.

Currently on the Galaxy S7 Edge SM-g935w8

FolderMount is not working.

Attached is info you would need.

If you need anything else just let me know.

Thanks in advance for your time.
[Android Software Development] PpukisS:
First I want to thank you for your response.

But, I dont know what is essential for me on this picture. So could you more explain your answer please ? Thanks in advance for your answer.
[Android Software Development] Checha_5:
Works perfect on my Moto G 2014 with Resurrection Remix v5.6.5 (MM).

Thanks man, you are awesome!
[Android Software Development] MrHomebrew:
I never responded to your comment.

I am requesting help and support from the creator of FolderMount
[Android Software Development] PpukisS:
Ok, sorry for that ...
[Android Software Development] Danilo-Sanchez:
Thank you for the information! This is exactly what I was waiting to flash CM13 on my Titan!
[Android Software Development] MrHomebrew:
Would love to see compatibility with the Galaxy s7 edge exynos
[Android Software Development] endolith:
I have the same error every time I try to access a media file. The files are mounted and show up in the correct location in file manager, and WhatsApp can load older media files successfully, but any new files are lost from the phone. Interestingly they do still show up on WhatsApp Web.

Is there any solution?

I tried "SDFix" but it didn't help.

Samsung Galaxy S Relay

CM11 Android 4.4.4

Another app I tried was having problems but I told it to delete and re-download all its files and now it works. They are on the external SD, mounted on internal like they're supposed to be. WhatsApp does not work, though. Any new media files from conversations disappear into the void.
[Android Software Development] fipsy:
Can someone update this broken link? I have exactly this problem and don't want to complain without reading the recommended notices. :p When using FM with boeffla kernel and CM11 on my Galaxy S3 (GT-I9300) the device freezes after a few minutes and can only be revived by restoring a system backup. :(
[Android Software Development] endolith:
https://web.archive.org/web/20150904015230/http://www.devasque.com/foldermount/kk-support.html

I also have cm11 but mine doesn't freeze :/
[Android Software Development] madmack:
No chance. sorry

working on compatability with samsung's latest next. it'll happen in time.

entire HDD failure on the website about 2 weeks ago. I haven't backed up everything unfortunately so some of the sites I was hosting are gone :banghead: I'll piece back whatever I salvaged when I get some time. This particular page you're looking for is still cached and I do have an offline copy of it as well.
[Android Software Development] fipsy:
I've checked the hints and everything seems to be okay. The ramfs entries as well as the environment variables. So at the moment I have no clue what the reason for this issue is.

The first 2 or 3 minutes everything runs well. Until FM mounts the folders. About one minute after this operation it's suddenly not possible to launch apps anymore: Nothing happens. After one or two more minutes the display goes black. Only the status line is still visible and can be swiped down and the lockscreen works. But nothing else is possible. The device doesn't respond to anything more. Even trying to shutdown or reboot fails. It's reproducible and without FolderMount the device is running stable over weeks without any need to reboot. If I uninstall FolderMount this issue still persists. So FolderMount obviously changes vital system configurations. I have to restore the system partition using TWRP to make the device work again.

By the way: I tried to bind the WhatsApp Media Folder (/sdcard/WhatsApp) from the External SDCard to the internal card.
[Android Software Development] madmack:
v2.9.1b

I was able to work around Samsung's new sdcardfs file system emulation and revert back to the AOSP's fuse variant so FolderMount should now be working fine with the Samsung S7/Edge (running Android M). I needed to change a couple of files this time around, some of them aren't small. So the APK grew in size accordingly. It also seems that the patched variant doesn't like ExFAT or NTFS fs on the sdcard. As soon as my phone was patched, the UI asked me to format the sdcard to FAT32 which I did (I don't have anything important on it). So for those that want to use FM with one of these new sammy devices, beware of this and make sure you backup.

I am attaching the latest version here. Please test it. I found plenty of bugs in the older version :|

This version will probably be the play store release (or close) given that I took care of some issues with the file copy operation as well.

Enjoy.
[Android Software Development] Meneldur:
I'm on CM13 and SuperSU is somewhat messy to install and keep. Will FM be always tied to SuperSU?

Mnldr/D855/16G/CM13
[Android Software Development] fipsy:
Sigh! My SDCard is formatted in exFAT, beause it's a 64 GB Card. But the playstore version 2.8.2 of FM also had issues on my device, as I reported in my last message. I already had the assumption that the filesystem could be the evildoer. :eek:
[Android Software Development] madmack:
With the newer versions of Android, yes. Either that or a permanent permissive SELinux which I'm generally against.

you should be able to format the 64GB to FAT32. I did it on my 128GB. Only limitation I'm aware of is the max file size which is ~4GB.
[Android Software Development] fipsy:
That's exactly the point! I need to store HD videos on the card. That's the only reason for me using such a big card. And 4 GB suffice for only about 10-15 minutes. :rolleyes:

I just tried to install the FolderMount version 2.9.1b from above. Installation works but if I try to launch it, it immediately crashes (FC).

Maybe good news or bad news - depending on your point of view: I think I found the reason for my problems with FM 2.8.2: If you try to bind a hidden folder on the external SDCard (beginning with a dot) to the internal SDCard the freeze-problem occurs. Now I used a normal folder and it works without freezing the device. Quite strange!
[Android Software Development] PieceKeepr:
Newest release is working on my M8 with Android 6.0 based Venom rom. I have a couple of pairs that absolutely refuse to turn green but they are still working.
[Android Software Development] madmack:
You think you can give me a logcat of the crash ? I'm wondering why it's doing it. Hopefully it's only your device. Last thing I want is for my release to break compatibility with earlier versions of Android.
[Android Software Development] fipsy:
Logcat is coming soon.

The other problem (device freezing) had to do with the fact that a WhatsApp folder was going to be mounted as I know now. Binding other folders doesn't make problems. I don't know how other users succeeded in creating bindings for WhatsApp Media Folders. WhatsApp locks it's SDCard Folder very early on boot and if it then receives Pictures or Videos it immediately stores them on the internal SDCard. This happens a long time before FM is binding the folder to the External SDCard. And if FM finally does, all Pictures and Videos received at boot time are lost because they had been placed into the internal SDCard folder that's now invisible to WhatsApp. The only way to solve this problem could be a synchronization of the two folders before every bind operation.

So it's a really VERY, VERY bad idea to bind WhatsApp Media Folders with FolderMount!
[Android Software Development] casouzaj:
I have always used FM to bind the whole WhatsApp folder, residing in the internal memory, to my SD card. Never had any problems with it.
[Android Software Development] MrHomebrew:
Working on the Galaxy S7 edge g935w8 Canadian exynos version.

It corrupted my SD card as I thought it would first run of FolderMount where it patches.

Files move to sd card and Mount correctly.

Moving files to sd card can be extremely slow at times. 100mb file can take half hour to transfer. Other apps at 100mb will transfer in minutes other times. Something to consider.
[Android Software Development] casouzaj:
Oh, I see your point now! Have not tested it, but, in theory you're right!
[Android Software Development] fipsy:
Not just in theory. :) But there maybe a workaround: If you configure WhatsApp not to download media automatically and you always wait when booting, until FolderMount has bound your WhatsApp folder from external SDCard, you probably will have no losses. Only voice messages are still affected because you cannot prevent them from being downloaded automatically.
[Android Software Development] MrHomebrew:
Great amount of space saved
[Android Software Development] Rintenfinten:
No he is not right. They remain in internal memory. If you cancel bind in FM you can copy them to external sd so they are not lost.
[Android Software Development] fipsy:
They are lost because no one will ever do this! I'm also not able to unbind the WhatsApp Folder while WhatsApp is running. It's keeping folder and files open and there would be unpredictable problems when changing contents of folders that are in use.

I also have to revise what I said earlier. The freezes have nothing to do with the name of the folder that's bound from the external SDCard. They are completely independent from what's bound. They do not occur on every boot but every now and then. And when they occur (always at boot time) they will not go away until the system is restored using a recovery. So there must be deep-seated reasons for this issue. Perhaps there is someone else who uses a Galaxy S3 (GT-I9300) with CM11 and FolderMount? Would be nice to hear from...

[MENTION=1436971]madmack[/MENTION]: Have you been able to identify the problem on the basis of my logcat?
[Android Software Development] Rintenfinten:
[MENTION=5110154]fipsy[/MENTION]: I have done this dozens of times without any problem. Besides, you can stop WhatsApp process before doing so ?
[Android Software Development] fipsy:
Maybe it works on your system with your WhatsApp Version. But you cannot generalize it. On my smartphone with CM11 it definitely doesn't work. And when freezing and defrosting WhatsApp (I think this is what you mean if you say "stopping") you may afterwards have problems with your WhatsApp contacts in the phonebook. It's quite fragile against those interventions.
[Android Software Development] Rintenfinten:
No, I simply used the App Manager and it worked on CM12.1 and on Touchwiz 5 to 5.1.1. I am quite sure it also worked on Kitkat. Anyways, you seem to be the super master expert so I am out here.
[Android Software Development] fipsy:
You mean "Force stop" in Settings -> Apps? This doesn't work for a long time. At least not on Kitkat. A short time later WhatsApp is started again. Even if you stop the message service. You can see this using a Task Manager and by the fact that messages will still arrive. There are too many intents that will start the App as broadcast receiver again. But maybe it works if you hurry. Though it's not a safe method!
[Android Software Development] Rintenfinten:
Useless to help someone who knows everything better. You just have to turn wifi and data off if you are scared to get messages during the unbind time. Then move everything inside the internal sd WhatsApp folder to the external sd WhatsApp folder and finally bind the folder again inside folder mount. I am doing exactly this for years without the slightest hint of a problem and no matter what you say I will continue to do so my friend... ?
[Android Software Development] fipsy:
Would be nice to conduct this debate on a factual and not on a personal level!

Be happy if this works for you, though I'd not recommend it. Nevertheless I ceased to use FolderMount as it occasionally freezes my device for any reason whatsoever. Maybe an interference with some other apps running on my device or the exFAT filesystem of the SDCard or maybe a gerneral problem with SGS3 and CM11.
[Android Software Development] madmack:
Yes. I am afraid this is related to the lost DB on my website. I used to have a DB online where some mapping was happening between devices and different custom vold binaries that I've compiled. If FM determines that your sdcard permissions cannot be fixed dynamically at runtime, it will look up that DB to see if I have developed a custom vold binary, download and patch your /system and reboot. This is probably one of the biggest losses I had when the HDD on the server crashed earlier this month :crying: I don't think I'll recompile the binaries or the DB list now given the time I have.

What I will do instead is make FM not crash at least :p Thanks for the logcat. It just simply won't even suggest anything for you and it'll continue to fail silently.

I agree. I tried moving my Whatsapp folder yesterday (4GB). It took more than a day. lol. I can't release this to the play store. Gotta optimize the new DocumentFile APIs that I am using in Android M. Thanks for the feedback.
[Android Software Development] PieceKeepr:
I had this issue a while back as well. Don't know what really caused it but setting the startup delay for 30 seconds eliminated the freezing.
[Android Software Development] fipsy:
So the "old" version 2.8.2 didn't do this lookup from your website? Because it runs without any problems.

I can well understand you! It's really a disaster and brings you to the verge of a nervous breakdown. This type of crash happened to me once. Since that day I'm making backups every time I change any vital things on any system.

---------- Post added at 07:43 PM ---------- Previous post was at 07:13 PM ----------

I have also tried this and it had no effect. But I now I'm on another path. Some time ago, when I was performing extensive copy operations on the external SDCard as source and destination, I noticed occasionally errors and the copy process was aborted. I always couldn't explain this. But yesterday I had the assumption that it could perhaps be associated with the CPU voltage. Particularly because freezes are a typical symptom of undervolting. As I don't undervolt my CPU I never before had sensed that the CPU voltage could be a reason for this problem. Now I experimentally overvolted my CPU by 25 mV. And almost unbelievable but true, the copy errors reliably do not occur anymore! So maybe the CPU of my device caused the problems. I will now investigate into seeking any relations between the CPU voltage and freezes with FolderMount. Perhaps this is the root of the problems...
[Android Software Development] PieceKeepr:
That's extremely interesting. Keep us posted please.