i have done alot of nonsense to my tablet, but for some reason i don't think my tablet is recognizing my internal sd card as memory. I tried downloading a file from a website and it said that i needed an sd card to download the file...this never happened to me before recently. I remember the tablet recognizing the 16 gigs of internal memory as essentially an sd card on the system. I think it now recognizes it as maybe internal memory and needs to show it as an sd... i don't know for sure... is there anything i missed. do i need to partition something? i just flashed cyanogen 7.0.3..
so it happened just after flashing, or already before? in cm in a file manager do you see sdcard?
Dunno about thekafka, but I have just flashed the same version of cyanogen to my G-tab, and am now experiencing the same issue. This did not start until after the installation. File Manager and CWM do find the SD card.
Is there an optimal partitioning scheme to use when flashing this ROM?
In CM-7.0.x, the internal SD card is mounted at /mnt/emmc and the external SD card, if one is attached, will be mounted at /mnt/sdcard. They're not trying to make things difficult for new users--it's just what's sensible for the wide range of devices that CM runs on: internal SD cards at /mnt/emmc and removable SD cards at /mnt/sdcard, whether on phones (remember, most phones don't have internal SD cards) or tablets.
If you're coming from another ROM where the internal SD is at /sdcard (or /mnt/sdcard) and the external is at /mnt/sdcard2, you, and some of the applications that you use, might get confused.
It's easy enough to switch the mount points so that internal SD is at /mnt/sdcard and the external will be mounted under /mnt/emmc. There is even a CWM-installable zip file floating around to do this easily. Search around here or at the cyanogenmod gtabet forum.
Thanks for being helpful and smart and stuff.
Here's the address of a thread with fixes, including the ZIP file that rajeevvp mentioned:
forum.cyanogenmod.com/topic/19492-no-sd-card-apps-fail-to-use-emmc/
I don't understand storage on Android and how it works. I would be grateful if someone could explain it.
Normally I thought that Phone memory refers to the storage space on the phone (like ROM) that was fixed and not removable. SD card is the microsd card that I physically insert into a slot on the phone. However, it seems that Android has 3 types of storage: Phone, Internal SD and External SD. Is this correct? I would appreciate if someone could clarify. Also, when I do move Apps to SD card on my CyanogenMod ROM, it seems to only move them from phone memory to internal SD, not external SD. As a general rule, is is better in terms of speed to keep the apps on internal or external SD? I don't want to keep in Phone memory since it is quite small, only about 1.8 GB. I should point out that I am using a Class 10 MicroSD, so it should be quite fast, or so I've been told.
What you refer to as Internal SD is probably not on the SD at all but read/write memory in the device itself. Basically built in storage that's an addition to the read only memory where the important stuff is.
As an example, the Omnia i900 had ROM + 8GB Storage in the Phone, with whatever you wanted to add as External SD. Plug the Omnia into a PC and you had two lot's of storage that you could drag and drop files to.
Basically you have 3 things:
ROM (Read-Only-Memory): This is where Android itself resides. All the OS stuff is here.
Phone Storage: You may consider this as the phones HDD. This is where all the apps/SMS/MMS/... are stored. (This is usually not meant to be accessed by the user to place files there, thats what the SD-Card is for)
SD-Storage: Your SD-Card where you can put everything you want. Music/Pictures/Files...
m0jo said:
Basically you have 3 things:
SD-Storage: Your SD-Card where you can put everything you want. Music/Pictures/Files...
Click to expand...
Click to collapse
Is it possible to run apps off the SD-Card? When I use an app like App2SD, does it actually copy to the SD Card or just to the Phone storage? This is what confuses me, because I selected 'move to SD' on my phone (I'm using Cyanogen 7.1.0). But its still in the Phone Storage. I know this because when I put the SD card into my laptop, it does not show any of the software files.
When you move apps to the SD not all data is moved to the SD. The phone needs some files on the internal storage to run, since it needs to know that the apps are installed on the phone. When it needs to run it'll find the executable files in the internal storage, and run the data files from the SD card. Much like on a computer when you've installed an application and install it on an external HDD.
Apps you move to the SD will be moved to /Android/data/ and /data i believe since i have quite a bit of appdata in these folders.
It's a noobish question, but I'm still a bit confused as to the internal vs external sd card usage. I know that in some ROMs (currently using SHOstock) the internal 12GB sd is under /mnt/sdcard and the external is under /mnt/sdcard/external_sd, but I never can get anything to use the external card. Why do we have the ability to stick one in our phones if none of our apps can be moved there? The only thing I've been able to use it for is Vignette or things like that where the app configuration allows you to browse to what folder you'd like to use for storage.
What I'm getting at, is that I'd like to move the apps themselves to the external SD, because I have the ability to put a 32GB card in, as opposed to the 12GB internal. Is this possible?
Another related question - TiBu sees my external card's free space, but whenever I use the App2SD function to move it to the "external" card, it moves it to the internal card. Anyone know how to fix this? I'm guessing that it has to do with no ext4 partition on the external SD, but I could be wrong. If that's the case, we're out of luck unless we're running Linux boxes, correct? If that's the case, then I return to my original question - what is the point of having an external SD card if the only thing you can put on it is pictures and/or manually move stuff over using a file explorer app?
The point is to store large media files like movies.
TiBu will also save to external SD.
Note that some apps use the newer Android standard for internal/sdcard mountpoints (/emmc for internal, /sdcard for external), which Samsung does NOT follow. (CyanogenMod, however, does follow this standard.)
Entropy512 said:
TiBu will also save to external SD.
Click to expand...
Click to collapse
Thats a negative. TiBu save files are stored in internal.
Main bonus for having external sdcard for me, is the abilitiy to store pictures and videos. Anything that is no on external sdcard will be lost if the phone gets broken.
They save to internal as default but you can change it to the external SD in the settings options.
Sent from my GT-I9100 using Tapatalk
MotoMudder77 said:
Thats a negative. TiBu save files are stored in internal.
Main bonus for having external sdcard for me, is the abilitiy to store pictures and videos. Anything that is no on external sdcard will be lost if the phone gets broken.
Click to expand...
Click to collapse
If you noticed he said "will" which means it has the capability. It's in TiBu settings.. You can move them to your external sdcard with TiBu as well...
Sent from my SAMSUNG-SGH-I777 using xda premium
MotoMudder77 said:
Thats a negative. TiBu save files are stored in internal.
Main bonus for having external sdcard for me, is the abilitiy to store pictures and videos. Anything that is no on external sdcard will be lost if the phone gets broken.
Click to expand...
Click to collapse
That's not true - you can have TiBu save backups to external storage in the settings menu - you just browse to where you want it to save it.
In either case, so really, just to move movies and other large media over to it? Nothing (aside from the few cases) automatically? Like I can't move apps over to it? It has to be the internal? To me that mostly defeats the purpose of having external storage.
DJLittleMike said:
That's not true - you can have TiBu save backups to external storage in the settings menu - you just browse to where you want it to save it.
In either case, so really, just to move movies and other large media over to it? Nothing (aside from the few cases) automatically? Like I can't move apps over to it? It has to be the internal? To me that mostly defeats the purpose of having external storage.
Click to expand...
Click to collapse
Where do you store your. Nandroid backups? I use the external card for that as well, along with TiBu backups, photos and videos. I sure as hell would not want all of that stuff on the internal storage?
Sent from my GT-I9100 using xda premium
... I'll try to answer the OP question. However, I haven't been around android long enough for this to be an authoritive answer. It's more along the lines of a guess...
The reason for the whacky naming is historical. Back in the early days of android, devices only had a small amount of user storage. It was generally mounted as "/data" and was probably 1-2 GB in size. This area was limited to storing application specific data (and downloaded applications.) Same examples might be your contacts list, your high score in angry birds, etc.
Many of those phones had a SDCard slot, however. Actually, many of the phones not only had the slot, but came with a card as well. The idea was that you could put music files, photo's, etc on this extra sdcard. A user could easily upgrade the card to whatever size was supported by android. In development terms, this became known as the external sdcard (or external memory) because it was user accessible and not required for the device to function. Traditionally, it was mounted as "/sdcard"
As time went on, more and more phones came with this extra storage. At some point, it was no longer user accessible or removable. However, it was still used the same way and for the same purpose (afterall, why would you need more than 1-2 GB for just app storage?) It's still mounted as /sdcard. When you move applications from "internal storage" to "external storage" you are really moving the bulk of the app data from /data to /sdcard.
Of course, competition goes on, and everyone wants to have the biggest and greatest phone. So, why not do something done before and go BACK to adding a user accessible memory card slot in ADDITION to the existing /sdcard "external memory"? The only problem is that android doesn't really have a proper way to address that, so different phones mount it in different ways. For some, it might be "/sdcard2". For others, it might be mounted as a sub directory of /sdcard (sdcard/ext_storage, etc)
Of course, this causes all kind of problems for programs designed to work on both older phones (where /sdcard was actually external) and newer phones (where /sdcard is built in.)
There are efforts with newer versions of android to try and correct this, but legacy stuff holds us back. In honeycomb (and ICS), "/data" and "/sdcard" are actually the same partition. In fact, "/sdcard" actually points to "/data/media." They use the same space, however. There's no longer a concept of "external memory." (However, its still confusing because programs are usually written to work for many different versions of android.)
Want to make things more confusing? Add in CWM Recovery. In that recovery, "sdcard" refers to the /sdcard partition that is often called "external" memory in android development. Then it refers to "internal sdcard" when talking about any additional memory card that is user accessible. (so "sdcard" is built in memory, and "internal sdcard" is the sdcard that's physically external.)
Confused yet? Me too.
Gary
garyd9 said:
... I'll try to answer the OP question. However, I haven't been around android long enough for this to be an authoritive answer. It's more along the lines of a guess...
The reason for the whacky naming is historical. Back in the early days of android, devices only had a small amount of user storage. It was generally mounted as "/data" and was probably 1-2 GB in size. This area was limited to storing application specific data (and downloaded applications.) Same examples might be your contacts list, your high score in angry birds, etc.
Many of those phones had a SDCard slot, however. Actually, many of the phones not only had the slot, but came with a card as well. The idea was that you could put music files, photo's, etc on this extra sdcard. A user could easily upgrade the card to whatever size was supported by android. In development terms, this became known as the external sdcard (or external memory) because it was user accessible and not required for the device to function. Traditionally, it was mounted as "/sdcard"
As time went on, more and more phones came with this extra storage. At some point, it was no longer user accessible or removable. However, it was still used the same way and for the same purpose (afterall, why would you need more than 1-2 GB for just app storage?) It's still mounted as /sdcard. When you move applications from "internal storage" to "external storage" you are really moving the bulk of the app data from /data to /sdcard.
Of course, competition goes on, and everyone wants to have the biggest and greatest phone. So, why not do something done before and go BACK to adding a user accessible memory card slot in ADDITION to the existing /sdcard "external memory"? The only problem is that android doesn't really have a proper way to address that, so different phones mount it in different ways. For some, it might be "/sdcard2". For others, it might be mounted as a sub directory of /sdcard (sdcard/ext_storage, etc)
Of course, this causes all kind of problems for programs designed to work on both older phones (where /sdcard was actually external) and newer phones (where /sdcard is built in.)
There are efforts with newer versions of android to try and correct this, but legacy stuff holds us back. In honeycomb (and ICS), "/data" and "/sdcard" are actually the same partition. In fact, "/sdcard" actually points to "/data/media." They use the same space, however. There's no longer a concept of "external memory." (However, its still confusing because programs are usually written to work for many different versions of android.)
Want to make things more confusing? Add in CWM Recovery. In that recovery, "sdcard" refers to the /sdcard partition that is often called "external" memory in android development. Then it refers to "internal sdcard" when talking about any additional memory card that is user accessible. (so "sdcard" is built in memory, and "internal sdcard" is the sdcard that's physically external.)
Confused yet? Me too.
Gary
Click to expand...
Click to collapse
To expand on Gary's comments here a little bit - I came to the SGS2 from an HTC Aria, which was released roughly 18 months ago (I didn't bother to look up the exact date). This was the first 'decent' Android device available on AT&T.
*ducks the flamethrower blasts from backflip owners*
The Aria had no internal SD storage (or more appropriately named EMMC I guess) and stock had 185MB - yes MB - user available app storage on /data. Needless to say, that is pretty severely limiting as far as app storage goes. To make this even more fun, the phone shipped with Android 2.1 (Eclair) which had NO built in provisions for apps to SD.
Thankfully, the dev community got us a FroYo port fairly quickly - so at least we had Android built-in apps to SD at that point. However, if you take a look at any apps you have Apps2SD'ed on your device, you'll see that in many cases, only about half of the storage cost of these apps actually gets moved to your SD card (internal in the case of the SGS2, external on the Aria).
Later, via CM6 and still later in CM7 we got the ability to move apps to an ext partition on SD cards (this may have eventually been possible at some point on HTC based roms as well, I can't recall). The downside to this was the requirement to "trick" the OS into seeing that ext partition on the external SD card as part of the device's internal storage, and it also meant that putting apps there was an all-or-nothing option. Therefore, if you wanted to switch external SD cards, you had to have a linux box to make a copy of the ext partition on one card, and put it on the other card, or all your apps were gone. This was a royal pain in the arse. On the Aria, I typically ran a 1 GB ext partition on an 8Gb card, and stored both my apps and dalvik cache there.
I currently have a bunch of apps on my SGS2 that I never use, but since I'm only using about 500MB of the available 2GB of internal app storage, I dont' bother to delete them. I don't run a ton of games, but the only time I'd think you'd even want to consider the hassle of moving apps to an ext partion on an external card with the SGS2 would be if you are running out of the internal app storage on /data. It's not getting used for anything at all if you move apps to the external card. If you're committed to doing this though, I'd guess if you grabbed a CM7 build for the SGS2 and an app called S2E in the market, you could probably do it.
sorry for the novel.....
DD
garyd9 said:
... I'll try to answer the OP question. However, I haven't been around android long enough for this to be an authoritive answer. It's more along the lines of a guess...
The reason for the whacky naming is historical. Back in the early days of android, devices only had a small amount of user storage. It was generally mounted as "/data" and was probably 1-2 GB in size. This area was limited to storing application specific data (and downloaded applications.) Same examples might be your contacts list, your high score in angry birds, etc.
Many of those phones had a SDCard slot, however. Actually, many of the phones not only had the slot, but came with a card as well. The idea was that you could put music files, photo's, etc on this extra sdcard. A user could easily upgrade the card to whatever size was supported by android. In development terms, this became known as the external sdcard (or external memory) because it was user accessible and not required for the device to function. Traditionally, it was mounted as "/sdcard"
As time went on, more and more phones came with this extra storage. At some point, it was no longer user accessible or removable. However, it was still used the same way and for the same purpose (afterall, why would you need more than 1-2 GB for just app storage?) It's still mounted as /sdcard. When you move applications from "internal storage" to "external storage" you are really moving the bulk of the app data from /data to /sdcard.
Of course, competition goes on, and everyone wants to have the biggest and greatest phone. So, why not do something done before and go BACK to adding a user accessible memory card slot in ADDITION to the existing /sdcard "external memory"? The only problem is that android doesn't really have a proper way to address that, so different phones mount it in different ways. For some, it might be "/sdcard2". For others, it might be mounted as a sub directory of /sdcard (sdcard/ext_storage, etc)
Of course, this causes all kind of problems for programs designed to work on both older phones (where /sdcard was actually external) and newer phones (where /sdcard is built in.)
There are efforts with newer versions of android to try and correct this, but legacy stuff holds us back. In honeycomb (and ICS), "/data" and "/sdcard" are actually the same partition. In fact, "/sdcard" actually points to "/data/media." They use the same space, however. There's no longer a concept of "external memory." (However, its still confusing because programs are usually written to work for many different versions of android.)
Want to make things more confusing? Add in CWM Recovery. In that recovery, "sdcard" refers to the /sdcard partition that is often called "external" memory in android development. Then it refers to "internal sdcard" when talking about any additional memory card that is user accessible. (so "sdcard" is built in memory, and "internal sdcard" is the sdcard that's physically external.)
Confused yet? Me too.
Gary
Click to expand...
Click to collapse
Hey Gary,
Makes sense, but at the same time, you can mount a share however you'd like in Linux and therefore should be able to do the same in Android. Phones that have two SD cards obviously are able to mount both, and it would make sense to have software use Android's internal mapping for them.
So I guess the real answer is a) I can't move apps to the *external* SD card, b) the mount points differ by phone manufacturer/ROM used, and c) because there is no standard, it's impossible to do everything I want automatically, but for most things I can still move them myself. Does that sound about right?
We need to mount another 16GB card and figure a way to RAID em for faster access..
Edit: yeah been drinking again...
Sent from my SAMSUNG-SGH-I777 using xda premium
garyd9 said:
Want to make things more confusing? Add in CWM Recovery. In that recovery, "sdcard" refers to the /sdcard partition that is often called "external" memory in android development. Then it refers to "internal sdcard" when talking about any additional memory card that is user accessible. (so "sdcard" is built in memory, and "internal sdcard" is the sdcard that's physically external.)
Confused yet? Me too.
Gary
Click to expand...
Click to collapse
This was mainly due to the fact that the Android standards got firmed up during the development of CWM 5.x (which is where support for the "internal" sdcard was first implemented)
Initially, CWM only supported one sdcard - and nearly all integrators chose this to be the internal memory.
Then later in 5.x, CWM added support for external/internal sdcards, following the new Android standard of internal on /emmc and external (but not labeled as such) on /sdcard
The problem is - almost all CWM implementations at this point used /sdcard for the internal mount point.
So the choice when I upgraded to CWM 5.0.2.7 was:
Leave things swapped as is and have the "internal" mislabeled (I had not yet figured out how to build CWM from source at this point)
Swap things and have tons of people be like, "WHERE MAI BACKUPZ?"
I'm thinking of doing the swap next time I update CWM - which might be later this weekend.
Entropy512 said:
I'm thinking of doing the swap next time I update CWM - which might be later this weekend.
Click to expand...
Click to collapse
I'd suggest not directly swapping. The confusion for people switching between different devices with CWM Recovery would be annoying. (I could even see it confusing an experienced user when they jump between different devices that both have CWM Recovery, but use opposite labels.)
Instead of redefining existing terms, it might make things easier to understand if you replace the string "internal sdcard" with a different, but non-conflicting term, such as: "microSD card" or "replaceable sdcard." When a user sees two options, such as "backup to sdcard" and "backup to replaceable sdcard", it's more obvious which one is which. (Of course, "backup to built-in memory" would be even more clear for the former option.)
Take care
Gary
Great info, thanks to all. Now let me throw in another term, "USB Storage." I ran across this in file manager after I had done a complete factory wipe, cache wipe, format, et al. In "USB Storage" was several files I had thought were on the 16Mb Class 6 microSDHC I had just formatted. So, where does this fit in the grand scheme?
BadElf said:
Great info, thanks to all. Now let me throw in another term, "USB Storage." I ran across this in file manager after I had done a complete factory wipe, cache wipe, format, et al. In "USB Storage" was several files I had thought were on the 16Mb Class 6 microSDHC I had just formatted. So, where does this fit in the grand scheme?
Click to expand...
Click to collapse
Oo! Oo! I can actually answer this one. USB storage is the "internal" SD card. I know this because I added labels to them in Windows and tested this myself. So you have 2GB of internal storage (not an SD card) SD Card (the user-replaceable one) and then USB storage (the internal SD card.)
Yes, very confusing, and I'm glad I made this thread, because I found out I'm not an idiot. Okay, I still may be but not because I don't know the difference and/or usage. It seems there are at least a few others that got confused as well.
Entropy, so the naming convention is controlled by kernel and you can name that whatever you want? I'm for the switch, but maybe make two versions available? One with the old naming convention and one with the new. For the new, my suggestion would be to name all three something descriptive. IE:
internal storage = internal storage (it's 2GB, I don't think people confuse this much)
USB storage = permanent SD card or non-removable SD card
SD Card = external SD card or even removable SD card
I think that should be clear enough. One is internal storage... not an SD card. Out of the two SD cards, one is removable and the other is not. Simple enough.
resurrecting a dead thread
I'm curious why this has not been brought up...It appears with Custom ROMs we can have apps install direct from Play store to removable sd. We just need to properly partition the removable sd : http://forum.xda-developers.com/showthread.php?t=1158993 .
I am actually looking into this practice. Does Shostock v4 not support such thing?
Also, folks who do partition their removable sd seem to favor amonRA over CWM...
Can someone shed some lights on this?
tora67 said:
I'm curious why this has not been brought up...It appears with Custom ROMs we can have apps install direct from Play store to removable sd. We just need to properly partition the removable sd : http://forum.xda-developers.com/showthread.php?t=1158993 .
I am actually looking into this practice. Does Shostock v4 not support such thing?
Also, folks who do partition their removable sd seem to favor amonRA over CWM...
Can someone shed some lights on this?
Click to expand...
Click to collapse
For starters that's a completely different device. Different manufacturer. HTC does things differently. They used to ship their phones with little storage like 4gb for OS and app install. They didn't provide gobs of onboard storage like Samsung.
Secondly that thread is over a year old.
AmonRA isn't available on this device. Again completely different devices, different methodologies.
The gs2 has plenty of storage and app install space available. Why does everyone think that installing your apps to external SD is a good thing?
Sent from my Nexus 7 using Tapatalk 2
we want more space
I bet many like the OP would like apps and app data stored on their removable sd especially nowadays you can get a class 10 sd for cheap.
Have you noticed how many apps will not work at all with apps on the SD card?
If you have the apps installed on the sdcard and you plug into your computer the apps become unavailable and Widgets for those apps stop working.
Sent from my Galaxy Nexus using Tapatalk 2
Pirateghost said:
. . . Widgets for those apps stop working.
Click to expand...
Click to collapse
And I'm pretty sure you have to re-add them.
Ok so far Ive found the mod to swap the internal and external sd,
The ideal mod for me is to merge all the 16gb internal into one partition and mount my sd card as a normal sd instead of external sd.
If anyone knows of the mod to do it the way ideal for me please link me. If you are a dev and like this idea would you take the challenge to make this happen? I will gladly beta test as long as a fastboot is available.
You want volume management on a phone?
Just get a big honking SD card. I have a SanDisk 64GB sdxc.
The 128GB cards will probably be available by October.
That said, you can probably get LVM working under Android, but you'll only be able to work with it from the phone itself (no browsing from a PC or putting stuff on the microSD directly w/o totally breaking the logical volume).
You can also format the SD space as ext3, then set up /etc/fstab to mount the external SD on a folder on the internal SD eg, /mnt/sdcard/Music Library. You won't be able to read/write that space from Microsoft (no, e2fsd won't do it), but any other OS can browse it like any other disk drive. Also, the drives will still appear separate from outside the phone.
the ext3 sounds nice but I like my idea better, my idea is pretty much the way samsung/htc/lg formats their storage, one is phone storage, other is sd, not the phone, sd (other internal) and extended sd(actual sd card)
and sorry for some confusion for anyone I meant Extended sd not external, kinda a noob in here coming from a sammy prepaid android.
Iirc in ICS the internal memory is counted as one part. So the 4gb and 8gb will be 12gb or whatever. Android 2.3 and below use the partitioned method.
Sent from my XT910 using xda premium
Edit; therefore wait till ICS comes out
Hi guys I am new to android and I got myself a Micromax A110 running on android ics with 2 gb of internal SD card memory...
As you guys can figure, the internal memory just isn't enough for installing heavy games and storing and downloading large videos and music, so I added a 32 gb external micro SD card.. the card shows in my file manager and its contents are accessible, most apps like ttpod, ttorrent, vlc, chrome etc don't detect my external card. They only access the contents of my internal SD card, download to it.. I can't set the default directory to the external card...
When I installed nfs most wanted to my phone, it asked me to free up data in my SD card or insert another one as there was no space left due to obvious reasons of my internal SD card being filled with other apps.. I uninstalled and reinstalled it after setting the default storage location to the external storage... I found that the game installed in the internal storage this time and on startup, it gave the same message..
Is it a common problem or a limitation to the OS? Is there a work around for this? If so how? Does my phone needs to be rooted for the purpose? Please help as the problem is getting annoying.. my external card is lying almost empty...
Thanks in advance,
Extremely sorry for the long post...
Sent from my Micromax A110 using Tapatalk 2
It's because Google made the stupid decision, starting with Honeycomb (which is why the Motorola Xoom, the first Honeycomb device needed an update to enable use of it's MicroSD card slot) to merge the /data/ and /sdcard/ partitions. What that means is that the SD card becomes a virtual space (a folder, in fact) located in the same place where all your apps are stored. Why is it stupid? If you have a phone that actually has a MicroSD card slot, like yours or the Galaxy S III, the MicroSD card becomes a different "folder" (something like /sdext/, which stands for either extension or external). Only apps that specifically are programmed to look for that mount point/folder will be able to use it. Most music/video/picture players/viewers can, because it makes sense to automatically program to do that. But with large games, like you said, NFS Most Wanted (which I also have), it sucks because the game is like 2GB.
My Galaxy S3 has 16GB internal and a 32GB card. I'm forced to use the internal storage only for large games because they don't see the memory card. It sucks. The good thing about merging /data/ and /sdcard/ is that it simplifies things, like on the iPhone where your space is your space, no matter how you use it. It used to be that you had like 1GB or 2GB for apps (the APK files only, not the files that games download for example) (which the HTC One X does, but still only uses internal storage because there's no card slot), and the rest went to your MicroSD card slot. Now it's all to internal storage because your internal storage IS your MicroSD card slot at system level.
Product F(RED) said:
It's because Google made the stupid decision, starting with Honeycomb (which is why the Motorola Xoom, the first Honeycomb device needed an update to enable use of it's MicroSD card slot) to merge the /data/ and /sdcard/ partitions. What that means is that the SD card becomes a virtual space (a folder, in fact) located in the same place where all your apps are stored. Why is it stupid? If you have a phone that actually has a MicroSD card slot, like yours or the Galaxy S III, the MicroSD card becomes a different "folder" (something like /sdext/, which stands for either extension or external). Only apps that specifically are programmed to look for that mount point/folder will be able to use it. Most music/video/picture players/viewers can, because it makes sense to automatically program to do that. But with large games, like you said, NFS Most Wanted (which I also have), it sucks because the game is like 2GB.
My Galaxy S3 has 16GB internal and a 32GB card. I'm forced to use the internal storage only for large games because they don't see the memory card. It sucks. The good thing about merging /data/ and /sdcard/ is that it simplifies things, like on the iPhone where your space is your space, no matter how you use it. It used to be that you had like 1GB or 2GB for apps (the APK files only, not the files that games download for example) (which the HTC One X does, but still only uses internal storage because there's no card slot), and the rest went to your MicroSD card slot. Now it's all to internal storage because your internal storage IS your MicroSD card slot at system level.
Click to expand...
Click to collapse
Hey man! Thanks for the reply....
Can you tell me how to work out a solution for this?
Is directory bind or fstab file hack the only solution?
Is it possible to overcome this without root?
And some apps do detect my Micro SD card... It is in the directory mnt/sdcard2
Please post questions one time only and in the proper Q&A section.
http://forum.xda-developers.com/showthread.php?t=2019921