The most important feature: Full access to the SD card has been reenabled for apps after the public outcry[0].
Updates:
Status: Released
Labels: Restrict-AddIssueComment-Commit
Comment #4444 on issue 67570 by jshar...@android.com: Android 4.4 Samsung Galaxy s4 external sd card is now read only, Remove or option to edit non app files.
https://code.google.com/p/android/issues/detail?id=67570
Hey all, in KitKat we introduced APIs that let apps read/write file in app-specific directories on secondarystorage devices, such as SD cards.
We heard loud and clear that developers wanted richer access beyond these directories, so in Lollipop we added the new ACTION_OPEN_DOCUMENT_TREE intent. Apps can launch this intent to pick and return a directory from any supported DocumentProvider, including any of the shared storage supported by the device. Apps can then create, update, and delete files and directories anywhere under the picked tree without any additional user interaction. Just like the other document intents, apps can persist this access across reboots.
This gives apps broad, powerful access to manage files while still involving the user in the initial selection process. Users may choose to give your app access to a narrow directory like “My Vacation Photos,” or they could pick the top-level of an entire SD card; the choice is theirs.
To make it easy for developers to transition to these new APIs, there’s a new DocumentFile support library class. It looks and feels just like a traditional java.lang.File object, which makes it easy to adapt existing code:
These new APIs aren’t just limited to shared storage; they can be used with any DocumentsProvider that adds support for Root.FLAG_SUPPORTS_IS_CHILD, such as the advanced Vault example:
If you're an end user, please reach out to app developers to ask them to start using these new APIs. With these new rich APIs in place, this issue is considered fixed.
I still feel that offering desktop style access to the file system is a mistake.
The file system is way too complex for a normal user and since developers can put files almost anywhere it is usually a total mess.
I would much largely prefer a personal sandbox for each app : their own folder in Android/packageName like they can optionally use right now. On top of that, add an API to grant access to shared folders for music/photos/documents/misc files.
This gives apps broad, powerful access to manage files while still involving the user in the initial selection process. Users may choose to give your app access to a narrow directory like “My Vacation Photos,” or they could pick the top-level of an entire SD card; the choice is theirs.
To make it easy for developers to transition to these new APIs, there’s a new DocumentFile support library class. It looks and feels just like a traditional java.lang.File object, which makes it easy to adapt existing code:
http://developer.android.com/reference/android/support/v4/pr...
These new APIs aren’t just limited to shared storage; they can be used with any DocumentsProvider that adds support for Root.FLAG_SUPPORTS_IS_CHILD, such as the advanced Vault example:
https://android.googlesource.com/platform/development/+/andr...
If you're an end user, please reach out to app developers to ask them to start using these new APIs. With these new rich APIs in place, this issue is considered fixed.
[0] https://code.google.com/p/android/issues/detail?id=67570