NOTICE: This content was originally posted to Google+, then imported here. Some formatting may be lost, links may be dead, and images may be missing.
Just uploaded a new version of StickMount to Play, which will be available for you within a few hours.
There's really only two changes. The first is forcing the use of toolbox for certain commands, which may prevent some issues for people who have busybox symlinked (bad idea).
The second change is using SuperSU's new 'mount master' feature. If you are running SuperSU v1.93 or newer (the app will warn you if you are not), this prevents the need for hijacking a system service on Android 4.3 and newer to perform the (un)mounting. This simplifies the process and makes it much less error prone, less invasive, and thus more reliable.
Forced a number of commands to toolbox, prevent busybox confusion
Add mount master usage if available, and warning if not
What is the best way to install busybox on stock rom? Busybox app by Stericson is good enough? edit: unlocked and rooted of course
+Cristian Zomparelli Provided you have your device unlocked and rooted, that app is one of the most popular, although not the only one. You can go for the "smart install." I chose xbin as installation directory, but you can also leave the settings as they are.
What's proper way to install busybox then?
Will it make all the whites whiter and the dark colors darker? :) [Note: Not responsible if it does not]
There is no proper way to install busybox. If you symlink it (like most installers do, and it replaces basic commands), you're always at risk of breaking root apps, as the syntax and supported options of those various basic commands will change.
Of course, root apps should prefix commands with 'toolbox' if they depend on specific toolbox commands and syntax, and provide their own busybox binary if they need busybox (there are so many different versions of busybox out there, you really cannot depend on whatever version the user installed).
In an ideal situation, there would be no interference, but unfortunately in practise, shit is just known to break.
+Chainfire here's an alternate solution, which may be better considering toolbox versions could change output from device to device. These two versions of busybox are directly from the busybox website so source is also from their site. https://code.google.com/p/android-casual/source/browse/#svn%2Ftrunk%2FCASUALcore%2Fsrc%2FCASUAL%2Fcommunicationstools%2Fadb%2Fbusybox%2Fresources. Use of these requires a link to the source.
If you use this, you would check the arch and deploy x86 or ARM binary, then use it for the mount command and whatever else you need.
These two binaries cover android devices which are not 64 bit. I find this to be a more reliable option as it doesn't rely upon native tools.
Received the update an hour ago, thanks a ton
+Adam Outler right, exactly as I said, if you want to depend on busybox, include your own. Using toolbox is pretty clear-cut, you can just look up (for example on http://androidxref.com ) which commands are or aren't supported. I'm generally against including busybox for small things because of (a) the licensing requirements and (b) the size. Adding 2 MiB to a package of 50 KiB just for some console commands seems like an aweful waste, most of the time.
Sehr gute Neuerungen, mach weiter so Chainfire! Lass dich nicht beirren!
I'm your Fan ;)
HEY WOW! So you're that one fan?