[Sprint Samsung Galaxy S 4 Android Development] FNetV1:
Solution to my "Forcing WhatsApp to save to SD card" dilema:

I have inadvertently found a solution to the problem I had stated on my previous post. I installed FolderMount and then FolderMount complained that something about ./xxxxx/sdcard needed to be patched before FolderMount could work properly, I agreed and restarted the phone. Upon doing this I went back to Apps2SD, created my MountScript (su.d) re-created my MountFolder, I enabled it, restarted the phone so that mount script could take effect. Upon restarting the phone I opened up ES file explorer, went to /emulated/0/WhatsApp to confirm if bind was working correctly this time, I was able to see the (22GB) directory tree and its files, I went to open up a video to see if it would open up just fine this time or if it would error out like what I was experiencing last time, and sure this time the video did opened up just fine and started playing, this was the first sign that the problem did got fixed. Now, I open up WhatsApp, I do a series of downloading, I first take note of the disk size used as shown from ES File explorer for both the Internal Storage and the External Storage to verify if in deed any downloading being done from What's app is not "dinging" my internal storage but the external storage. The starting figures were Internal Storage: 2.82GB Used and External storage: 44.26GB Used I downloaded like a few 10's of MB of video data from WhatsApp then went right back to ES File Explorer to compare which storage took the load for these files, and sure enough, the Internal Storage stood exactly the same while the External Storage went up to 44.28GB an increase of 0.02x GB or 2x MB's of space. For me, this concludes that now WhatApp is working exactly how I want it to work, to automatically save multimedia files directly to the Micro SD card instead of the very limited internal storage. I guess that concludes this problem for now.

Just one observation. While the problem is (or it seems to be) fixed for now, ES file explorer reports the following storage units: #1: Internal Storage 2.82GB, #2: SD Card 44.28 GB and #3 SD Card 44.28 GB so it seems that the SD Card is repeated twice, hmm interesting aside from that observation everything is fine, just wondering why the SD Card is listed twice?

To close, you might be wondering why didn't I just do the binding with the FolderMount app? The answer would be because of my personal experience with that particular app at the Stock KitKat rom back liek a year or 2 ago. It would mount it fine, it would save the content from WhatsApp to the SD card just fine, then one day the user would bring the phone back to me because the internal storage is full, however I see nothing under /emulated/0/ to warrant all the disk space waste but witih a huge exception, there is a huge amount of GB being wasted on Cache, when Cache got cleared Whats App all of a sudden complained that it couldn't find any of the media files, however all the media files were still intact on the Micro SD card and when you opened up a media file manually through ES File Explorer under the Internal Storage it would open up just fine from these media files that are only physically located on the SD card that are binded to a folder on the internal storage. So back in those days FolderMount had a side effect, it was actually filling up the Cache while saving a copy of the file to the SD card simultaneously. Now, I admit I haven't tried FolderMount under Lollipop ever since I upgraded to Lollipop (OK3) I just installed an AOSP ROM (Ressurection Remix Marshmallow) and then installed Apps2SD instead of FolderMount, and never had an issue. So in light of what I remember seeing when I was using Android 4.4.2 on this phone I decided not to go fully in with FolderMount however FolderMount did fix the issue that I was having by patching the /sdcard "so that the apps can be able to write to the SD card", and talking about that, I remember Apps2SD telling me something similar to that nature which I did went ahead and I did patched it first from the Apps2SD's "FixSD" menu, but App2SD's "patch" wasn't effective, only :FolderMount"'s patch was effective. This is something for other people to take observation if you use this and some other TouchWiz roms and are having difficulty with FolderMount through Apps2SD you might want to also install the FolderMount [ROOT] app, let FolderMount patch ../sdcard/ and then go back to Apps2SD and to everything else there.

Well thats' it, I am glad that I finally have a fully functional phone that behaves exactly like I want it to. The primary user of this APH-L720T is my father and I am sure he will be happy too expecially when he sees that the camera app wont be crashing anymore (like it was the case with LITERALLY EVERY SINGLE AOSP roms for the L720T that I have tried)