[android-developers] Re: Why oh why did Google let manufacturers take over the getExternalStorageDirectory() API?
the naming of the function is bad, but the manufacturers are not to blame.. they actually do what google declared the function to be: http://developer.android.com/reference/android/os/Environment.html#getExternalStorageDirectory() 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[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: http://developer.android.com/reference/android/os/Environment.html#getExternalStorageDirectory() 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Why oh why did Google let manufacturers take over the getExternalStorageDirectory() API?
On Wednesday, 12 December 2012 20:54:10 UTC+1, 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 Not exactly. It is confusing because of the unfortunate naming of getExternalStorageDirectory(). In Google's speak, Extenal Storage doesn't refer to physical external storage (like USB stick, external HDD, ...) but to storage that can be access from an *external* device like a computer. Physical internal SD card qualify as external storage since you can read it from a PC a MAC or whatever. Now were manufacturers did not their job, is when they added additional External storage (whether it is physically external or not), and put the damn mount point not in a subdirectory of directory returned by getExternalStorageDirectory(). So for apps to have access to this additional storage, apps have to expose all kind of crazy stuff like letting users enter mount points, parse /etc/fstab (WTF), etc. Long story short: all External Storage whether physically external or not should reside in getExternalStorageDirectory() so apps and users do not have to deal with anything else. -- 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Why oh why did Google let manufacturers take over the getExternalStorageDirectory() API?
A user should be able to move an SD card from one device to the next and have all of there data in the expected location and be ready to go from an app standpoint without jumping through these hoops. This is so broken it's pathetic. Yeah, this is where the pain comes. And when your app is installed on the phone and tablet, and they want to copy the config across with the SD card. Pent -- 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
