So, apparently, it is still not supported and Google has no solution yet.
http://www.pcworld.com/article/2275..._details_emerge_the_little_things_add_up.html
http://www.pcworld.com/article/2275..._details_emerge_the_little_things_add_up.html
This detail, which came out in conversations I had with Google engineers today, explains why the Android file system organization is, well, a mess, and why I’ve had such inconsistent experiences with Android and removable storage across the various Honeycomb tablets I’ve tried (and I’ve tried all of them that are available so far).
“We don’t want to expose the user to file locations,” explained Hiroshi Lockheimer, director of engineering at Google. “How do you manage that as a user? The not-good answer is with the file browser.” Lockheimer says that many of the experiences I’ve seen so far are what individual hardware manufacturers have enabled, as opposed to what Google has provided natively. The good thing is that Lockheimer says Google is looking at ways to do this; but the problem hasn’t been solved yet.