[Verizon Samsung Galaxy S III] HMkX2:
I strongly suspect it will not work, as a lot of the internal workings (functions, variables) are completely different. Running the binaries themselves should work 100%, however. You'd need to script that yourself.

You need to run it every time it unmounts. The 'fix' is adding in exFat support in CM10.1 itself -- and is easily done by someone with the talent to do it. (Everything is open source.) I am not ashamed to say I lack that experience.

I'd rather sacrifice a bit of convenience for safety, so I do not intend making my script persistent.

I am not familiar with how dual-kernels work. Presumably it shares system directories. If so, it would lead to a conflict since you don't want the script around when the Siyah kernel is booted. I suggest deleting the "/etc/init.d/S50fuse-mountsd" script and running the "/system/xbin/fuse-mountsd.sh" script

yourself

whenever you boot into CM10.1.

I am running mastamoon's CM10.1 on a GS3 with 64gb Sandisk Class-10 with

NTFS

. I do not have the deep sleep issue. I lost my BBS stats from today (dumb-ly forgot plugging USB debugging resets stats), but this shows I still have sleep with NTFS. It must be a flaw with the

exfat binary

-- I'm sorry I cannot provide any help there, aside from suggesting using NTFS.

To all those with Deep-Sleep issues: my script only handles analysis/mounting/unmounting. It does not "run" in the background -- it runs, does its job, then terminates. If there is a problem, it is with the

mount.exfat-fuse

binary. I did not compile it, so I cannot track down the bug. Sorry. :(

That will happen to

any

files you delete on-the-phone using phone-explorer apps. You need to use a SD-rescan app to update the phone's index any time you add or delete files from the phone itself. It would happen if you were using my script or not.

Also, I have done some checking. Your "mount" command is giving nonstandard outputs... and is checking for a directory "on". This cascades to cause other errors. Can you type "mount" as root and tell me what the output looks like? If it says anything different from "/directory/mounted /device/here <type> option1,option2,option3" (e.g. "______ on device _______"), there is a big problem.

And I cannot copy files from my PC to the ExtSdCard (device busy or unplugged).​

That is a permissions issue -- it's unique to using EXT4. Not a big deal if you fix it.

It goes (Computer -> MTP access -> Phone Kernel -> Media_RW User ---(Permissions check)---> SD Card). When you plug your phone into the computer, the phone itself sees user "media_rw" accessing files on the device. Apparently you have permissions set on your EXT4 card such that "media_rw" has READ permissions, but not WRITE permissions. (This is also why Solid Explorer cannot delete files, but

ROOT

Explorer can. "Root" supercedes everything, whereas Solid Explorer probably uses the non-root regular mobile user "u#_a##" where # is a random number.)

The following commands should fix your permissions, assuming your EXT4 card is mounted to /storage/sdcard1/ like normal -- if not, simply adjust it. The first line changes the group owner (CM10.1 does not have "recursive" chown, hence the roundabout method using xargs) and chmod to make files "read-write-execute" for media_rw and "read-execute" for everyone else.

find /storage/sdcard1/ -print0 | xargs -0 chown media_rw:media_rw
chmod -R 775 /storage/sdcard1/

captain_throwback, I see your questions and I'm thinking about them -- but I can't troubleshoot a device I don't own. I'll try my best.