Content removed as I am retired from Phandroid/AF.
You can't write to the extsdcard with KitKat?
That's new to me, I'm using Jamal's Nexus rom on my i9505 and can write to the extsdcard just fine so assumed you could on a stock i9505g also.
What are Google thinking?
External storage access
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 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().
ES File Explorer V3.0.8.0
1)Fix Android 4.4 Kitkat external card compatibility
2)Auto upload modified network file
id=com.estrongs.android.pop
You can't write to the extsdcard with KitKat?
That's new to me, I'm using Jamal's Nexus rom on my i9505 and can write to the extsdcard just fine so assumed you could on a stock i9505g also.
What are Google thinking?
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().
This is working as intended. Prior to KitKat, there are no public APIs that give access to secondary external storage devices, so this is not a regression.
Starting in KitKat, apps now have read/write access to their package-specific directories on these devices through public API, but the remainder of those devices remain read-only.
and a quick look around for ES file explorer ( which is the one I'm currently using although not on kitkat) at
V3.0.0~V3.0.9
Recycle bin;Batch rename;GIF;Open as;Select range;New music player,task manager;playlist;New UI;Fast Access;Multi-Windows;WiFi Send;Gesture;Theme;Root Explorer..
Medion... Thanks for taking the time to clarify that. From the link I posted it certainly looked like there were both read and write permissions for external storage. Its been a while since I did any development, and thats certainly the way it looked to me.
I agree with the OP, no sd card slot or removable battery is bad, we need to keep saying this because there are legitimate reasons for wanting them
They sold out to Nestle & changed Key Lime Pie to KitKat.
BOLD - This means that applications no longer need permission to read/write to their /system subfolders that are located on removable/external media.
Underline - These permissions are still needed for addressing shared folders (IE, anything not located in /android or /system). HOWEVER, the getExternalStoragePublicDirectory() grants READ ONLY permission. There is no replacement for WRITE_EXTERNAL_STORAGE.
Glad they added this. Now people don't need to cry when their live wallpaper wants sd card access.
Are you sure that's true. The code posted under getExternalStoragePublicDirectory() has an output stream. Something is being written.
And wouldn't a lot of kitkat owners complain about this. I can't find anything on google.
Interesting & informative read. 1 question, what might you switch to then?
See parameters listed in your link, below the section you're highlighting. It's limited to very specific directories. The application has to request the directory specifically, IE, a photo-editing app making edits to photos within that directory. A File manager won't work (case in point, just tested ES File Explorer again, and it won't do squat with any directories with those names).
It's always been this way, correct? Using MTP, internal memory is now the primary device. Which makes the sd card a non-standard storage device. How were non-standard storage devices dealt with before kitkat?This is working as intended. Prior to KitKat, there are no public APIs that give access to secondary external storage devices, so this is not a regression.
Not quite. Because applications don't have to request permission anymore, they won't show up as needing MicroSD access. Besides, they're not the ones writing here. Technically, its Android writing here on behalf of the app.
Google requires that certain apps are installed on any Android device that uses the Play Store. Don't want Google+, Hangouts, Drive, Quick Office, etc.? Tough. They're coming pre-installed. Google has also stopped updating core AOSP functions as well (Messaging, Gallery, etc.). The result? OEMs have to make their own alternative, or simply rely on Google's closed-source product. This means that AOSP-based ROMs are being left behind by Google. You're essentially being trapped within an Ecosystem, when Android used to be about being able to use what YOU, the user, wanted instead of being trapped in an Apple-like ecosystem.
Google close sourcing it's apps is how it'll maintain control over android. To maintain ecosystem thus far. Google's afraid of Samsung and CyanogenMod. They have enough influence to fork android.
Android has already been forked by a couple of major manufacturers, e.g. Meizu. What runs on their phones is called FlyMe, you don't see the cute green robot, and has its own version numbers. Then there's the MUIU ROM that all Xiaomi phones come with. Although they still call that one "Android"....for the moment at least. Tencent have made a major investment in CyanogenMod. Think there's a lot going on with Android that has absolutely nothing to do with Google(apart from them releasing the source code)....in China at least, don't know about elsewhere.
I have two file manager developers who are working with me at a non-root workaround, though ES has stated that they will introduce a workaround for rooted users. The non-root workaround will be to treat the app-specific subfolder as the SD Card to the user. However, we're going to need a second workaround to make this work properly with the device's media given that the Android subfolder automatically generates a .nomedia file and it cannot be removed by the file manager.
future proof?
that is what RIM thought .. and Palm
We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.