View Single Post
Old 06-28-2012, 03:15 PM   #50
=X=
Wizard
=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.
 
=X='s Avatar
 
Posts: 3,672
Karma: 12205348
Join Date: Mar 2008
Device: Galaxy S, Nook w/CM7
Quote:
Originally Posted by HarryT View Post
But doesn't Android already need to address all those issues, regardless of whether the manufacturer chooses to have an SD card slot on a particular device?
Kind of but not really, murraypaul is partly correct.... Removing a card slot does lead to a simpler design. I'm of the type that would spend a little more time learning so I can optimize my usage. Many folks aren't.


Android is really only optimized to have one SD Card slot. Apps that can make use of card slots or install on a card slot can only save to the default /sdcard directory unless developers, manufactures write software to handle different locations. It's usually file managers and games that do this.

However many of the manufactures, including google, have defaulted to using the /sdcard slot to mount internal memory. Which makes some of the issues murraypual made moot in most cases.

=X=
=X= is offline   Reply With Quote