On Sun, Jan 3, 2010 at 11:11 PM, Alessandro Pellizzari <[email protected]>wrote:
> Please also consider devices with more than one SD card, like the > Samsung Galaxy (/sdcard is the internal 6.5 GB flash, /sdcard/sd is the > external removable SD card). > In theory, your app should do nothing special about this. There is a public API to get the path the external storage; you should use that, and never hard-code paths. Currently the platform only supports one external storage location, so I would suggest using that and staying blissfully unaware of whatever other stuff Samsung does. Unless they provide their own well-defined API to their own storage paths (via a library your app can link to), or contribute a patch to the platform to support other kinds of external storage, you should treat whatever else they are doing as non-existent: you have no way to know if that will exist in the future in the current form or at all. If you need to store big chunks of data, you could let the user > configure the path in which to save them. > That's one of the things we really don't want applications doing. :} We try very hard to keep paths out of the UI for users; for some specific kinds of apps it can make sense to expose them (such as file browsers), but users should not be confronted with paths when dealing with normal applications. -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
