Thursday, December 13, 2012

[android-developers] Re: Why oh why did Google let manufacturers take over the getExternalStorageDirectory() API?

Well, the confusing thing is that the function usually returns '/mnt/sdcard' when that's not actually the SD card.



On Thursday, December 13, 2012 2:06:27 AM UTC-6, Piren wrote:
the naming of the function is bad, but the manufacturers are not to blame.. they actually do what google declared the function to be:

The real issue is that there's no easy way to get the sdcard,,, but that function does exactly what it's supposed to do.

On Wednesday, December 12, 2012 9:54:10 PM UTC+2, niko20 wrote:
Just what the title says,

The getExternalStorageDirectory API is supposed to GET EXTERNAL STORAGE. But manufacturers have all turned it into "point to the internal storage on the device". There should have been a "getInternalStorageDirectory()" API to go along with this.

I don't mind, I've "solved" this problem a long time ago, but just letting users type in the "real" path to the external card into my app. But many apps don't do this yet. So you get lots of apps that put everything on the internal storage when you have a 64GB card which is getting nothing put on it (I'm looking at you, Amazon MP3 and Amazon Kindle).

Who let this slide man!

-niko

--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

No comments:

Post a Comment