External Storage Technical Information | Android Developers
External Storage Technical Information for Android 4.4
Android supports devices with external storage, which is defined to be a case-insensitive filesystem with immutable POSIX permission classes and modes. External storage can be provided by physical media (such as an SD card), or by exposing a portion of internal storage through an emulation layer. Devices may contain multiple instances of external storage.
Access to external storage is protected by various Android permissions. Starting in Android 1.0, write access is protected with the WRITE_EXTERNAL_STORAGE permission. Starting in Android 4.1, read access is protected with the READ_EXTERNAL_STORAGE permission.
Starting in Android 4.4, the owner, group and modes of files on external storage devices are now synthesized based on directory structure. This enables apps to manage their package-specific directories on external storage without requiring they hold the broad WRITE_EXTERNAL_STORAGE permission.
For example, the app with package name com.example.foo can now freely access Android/data/com.example.foo/ on external storage devices with no permissions. These synthesized permissions are accomplished by wrapping raw storage devices in a FUSE daemon.
Since external storage offers minimal protection for stored data, system code should not store sensitive data on external storage. Specifically, configuration and log files should only be stored on internal storage where they can be effectively protected.
------------------------------------------------------------------------------
https://developer.android.com/about/versions/android-4.4.html
External storage access on Android 4.4
You can now read and write app-specific files on secondary external storage media, such as when a device provides both emulated storage and an SD card. <--- (The F6 for example)
The new method
getExternalFilesDirs() works the same as the existing
getExternalFilesDir() method except it returns an array of
File objects. Before reading or writing to any of the paths returned by this method, pass the
File object to the new
getStorageState() method to verify the storage is currently available.
Other methods for accessing your app-specific cache directory and OBB directory also now have corresponding versions that provide access to secondary storage devices:
getExternalCacheDirs() and
getObbDirs(), respectively.
The first entry in the returned
File array is considered the device's primary external storage, which is the same as the
File returned by existing methods such as
getExternalFilesDir().
Note: Beginning with Android 4.4, the platform no longer requires that your app acquire the
WRITE_EXTERNAL_STORAGE or
READ_EXTERNAL_STORAGE when you need to access only your app-specific regions of the external storage using the methods above. However, the permissions are required if you want to access the shareable regions of the external storage, provided by
getExternalStoragePublicDirectory().
I pray we get the update! It sounds like it could be a saving grace for us! I will be sorely disappointed if we don't. Cause then it's like LG telling me to go Bjork myself, they got my money, now kick rocks..
On other threads I tried telling them... it was coding and software not hardware causing the storage problem. Read and thee shall find solace and wisdom.
?
