How can I switch from the internal ClockworkMod to the microsd version?
I already have the internal version installed, and I copied the update.zip and recovery folder to the root of my microsd card. Then I rebooted using the recovery install instructions, and nothing changed. Is there a config file that needs to be modified to point to the new location?
bjhanifin,
Either way you just install CWM to your tablet. Only reason for having multiple ways
to install it is for use when folks are having problems.
rev
I want to store my ROMs and backups on my microsd card. I'm uptight about my file organization like that. Besides I have a 16 gb microsd card, I would rather keep the internal memory as free as possible.
I should point out that the internal CWM does not -- as far as I can tell -- allow me to install ROMs or place backups on the microsd card. Which I why I want to make the switch. I was just going to muck about and tinker until I hopefully got it working, but I thought I should check in for some tips before I risk fouling things up.
Would placing a /recovery/command file, which points to sdcard2 do the trick? Or am I going to have to use nvflash to restore to stock?
I think you're a bit mixed up. Internal or MicroSD are just the install methods. After installation, they are the same.
To make sure we're on the same page:
The G-tab comes with an internal 16GB card. Most of us partition 2 GB of that for the system to use, leaving the other 14GB to be used as the eMMC card, which is seen by many things as the SDCard. Any external microSD card you install will be SDCard2 (or just SDCard for something that references the internal extra space as eMMC). This is what gets the most confusing - most things refer to that extra space on the internal card as the SDCard.
I should point out that the internal CWM does not -- as far as I can tell -- allow me to install ROMs or place backups on the microsd card.
Click to expand...
Click to collapse
Since the extra 14GB from the internal card shows up as the SDCard, this is where backups and media are normally stored. ROMs get installed to the 2GB partition. Though you might be referring to where you put the ROM files to be able to install them, this is not actually the installation location.
Now, if you want your external card to be used as the eMMC, so it will be the one you connect to over USB, your backups go to, etc., you have to change a system file. (Note - some ROMs already have this reversed) To do this, you'll need to use Root Explorer (this costs about $4, but it's the only thing that makes this easy), and edit the file /system/etc/vold.fstab. in there, you will see two lines that look like this:
Code:
dev_mount emmc /mnt/emmc auto /devices/platform/tegra-sdhci.2/mmc_host/mmc1
dev_mount sdcard /mnt/sdcard auto /devices/platform/tegra-sdhci.3/mmc_host/mmc2
Changing those will reverse which is used in what role:
Code:
dev_mount sdcard /mnt/sdcard auto /devices/platform/tegra-sdhci.2/mmc_host/mmc1
dev_mount emmc /mnt/emmc auto /devices/platform/tegra-sdhci.3/mmc_host/mmc2
This second one will allow your external card to be used as you want.
OK, I made the assumption that the difference between the two ClockworkMod installers was a different "sdcard" pointer. I thought one build would point to the external card, instead of the internal card. When in fact the build is identical, only the location of the initial cwm update.zip changes.
Thank you for setting me straight. I guess I was trying to recreate the cwm environment I have been used to on my droid phone. Perhaps I will setup a (Tasker?) routine to monitor the download folder for .zip files which I can then automatically copy over to my ROM folder on the internal memory to streamline my ROM update process.
I know what you mean, I expected it to be like my Droid, too.
When I update ROMs, I start by doing a USB mount in Clockword mod, then copy the ROM over, then do the update.
Clear your doubts guys!!!
Ok, so here's the deal, in a very longwinded way that should hopefully explain everything and answer ALL questions.
You have an SD card in your phone and, a bit like normal PC Hard Drives, you can "partition" them (split them into two or more sections of different filesystems). Normally, your SD card is just one big FAT32 partition, which is fine for storing your pics, messages, emails, etc.
Now, other then your Phone's SD card, your phone will have its own internal flash memory (or "NAND") storage. Tradditionally with Android, you could only install applications to this NAND storage, you cannot install them onto your SD card. So if you have an empty 32GB SD card, but only 5Mb of internal phone storage, you still wont be able to install many apps, if any at all.
This was done to protect the apps from things like piracy - it's not easy to access the location where apps are installed on your phone's internal storage (normally impossible without root), so you can't for example buy an app, copy it, refund it, then install it again.
Still, this is no good for those of us who like to install lots and lots of apps, legitimately, as we run out of internal storage very quickly.
So Google came up with a way to install apps to the SD card. A folder is created called something like .android_secure and this stores (I believe) encrypted versions of applications, but there's a few catches:
1) Apps aren't automatically stored here, you have to manually "move" them
2) Not all apps are capable of being moved, in fact most apps aren't, the developer needs to update their app and allow it. Some apps aren't and wont be updated and some developers may not want to allow it for whatever reason.
3) Not all app data is moved, most of it is but some data is left on your phone so many people still run out of internal storage quickly.
4) You can force ALL apps to be moved to this area by default, but it breaks incompatible ones - such as Widgets, which are unable to load due to the SD card not being "prepared".
So that's Froyo's version. Before Froyo existed, some very clever people came up with a thing called "Apps2SD". Remember I said that your SD card normally is one big FAT32 partition? Well, Apps2SD works by having your SD card patitioned into TWO filesystems. A normal FAT32 partition for your usual stuff and a secondary "EXT" partition. EXT is just a filesystem, like FAT32 or NTFS, but it's the filesystem used by Android internally. The SD card is normally FAT32 because it's a "universal" filesystem, that just about any machine will be able to read, whereas EXT filesystems are generally Linux only, but I digress.
EXT has several different versions. The most common one you'll see is ext3. The main difference between ext2 and ext3 is "journaling", which is just a fancy way of saying that should an operation (such as copying, writing or reading) be interrupted unexpectedly (say, by you turning your phone off), then no data should be lost or corrupted. You know how when you turn your phone on, it says "preparing SD card"? It takes a few minutes, but what it's actually doing is checking that the FAT32 partition hasn't been damaged, because FAT does NOT have journaling. If you used a computer back in the Windows 98 days, you may remember that lovely blue "Scandisk" screen that had to run every time you didn't shut your computer down correctly - that's the same thing. But then Windows 2000/XP came along with NTFS, which also has journaling, meaning you had less chance of loosing data. But I digress once more.
So you have your SD card partitioned into EXT and FAT32. Generally it doesn't matter if it's ext3 or ext4, but you don't get any real advantage with ext4 over ext3 in this instance. Apps2SD then runs a special script on your phone which "symbolically links" the folder from your phone's internal storage where your apps are normally stored, to the ext partition on your SD card. A symbolic link is a bit like a shortcut for folders, except it's transparent to the OS: In other words, Android doesn't know that when it's installing it's apps to the internal phone storage, it's actually being stored on the SD card. This effectively boosts your internal phone memory from the previous 5mb that you had in my example above, up to whatever size you made the ext partition on your SD card (often 512Mb or 1Gb, but it depends on how many apps you install).
Plus, because it's "journaled", it doesn't need to be "prepared", meaning it's ready to go as soon as the phone starts - so your widgets and apps work immediately (unlike "forced" Froyo Apps2SD, where widgets disappear).
The catch with Apps2SD is that whatever space the ext partition takes up is taken away from the SD card. So if you have a 4Gb card (with something like 3.5Gb of actual storage) and you make a 512Mb ext partition, your SD card will "shrink" to 3Gb. The space isn't actually lost, it's just being used by the ext partition. If you reformat your card, you'll get it back.
Finally, there's a difference between "Apps2SD" and "Apps2SD+". Remember I said that your apps are stored on a special folder inside your Phone's NAND storage? Well, that was a bit of a lie. It's actually stored in TWO places. There's a second area which is called the Davlik Cache. You don't really need to worry about what this is for (Hint: IT's to do with the Java runetime your phone uses to run apps), all you need to know is that apps use it to store data, which also eats up internal phone memory. Apps2SD+ moves davlik cache to the ext partition on your SD card as well, freeing up even more space. Some people believe that this may come at the cost of performance, as the internal NAND memory should be faster than your SD card (Which is why you also get people arguing over which "class" SD card is better for Apps2SD - the logic being that a faster SD card means less impact from this move), but the truth of the matter is that your applications will be running from your Phone's RAM anyway, so performance isn't really impacted at all. Since most apps are only a few hundred Kb's in size, or a couple of MB at the most, it's a non-issue.
Finally, any recent version of Apps2SD/Apps2SD+ should work with an SD card that is or isn't formatted with an ext partition. It'll check for this partition when your phone first boots and if it's not there, just use internal phone storage.
Having an ext partition WITHOUT Apps2SD+ shouldn't cause any issues, either, so you can format your SD card whenever you're ready.
So in summary:
Apps2SD "fakes" your phone's internal memory and puts it all on a hidden section of your SD card.
Apps2SD+ pushes even more content to the SD card, freeing up even more space on the phone itself.
"Froyo" Apps2SD has various limitations that "old" apps2SD does not, but is much easier to handle as it doesn't involve any kind of "partitioning".
IF U LIKE HIT THANKS​
Good idea, mate
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.
Just got my E4GLTE and of course the first thing I did was root it, unlock it, and make a nandroid backup. I just moved from a Motorola Photon 4G and on that device the internal memory (pseudo sdcard) is mounted on /mnt/emmc and the external card is on /mnt/sdcard. Assuming you run out of app space in base memory, you can always move most of your app to the SD Card. Since the E4GLTE mounts the external SD Card on /mnt/sdcard/ext_sd, it appears that actual external storage can only be used for media or data where the app (or the system using the Storage tool) has a function to map to a different directory.
Have I described the situation properly? Does anybody else see the limitations this might pose or suggest workarounds?
..rob
bitbearmi said:
Just got my E4GLTE and of course the first thing I did was root it, unlock it, and make a nandroid backup. I just moved from a Motorola Photon 4G and on that device the internal memory (pseudo sdcard) is mounted on /mnt/emmc and the external card is on /mnt/sdcard. Assuming you run out of app space in base memory, you can always move most of your app to the SD Card. Since the E4GLTE mounts the external SD Card on /mnt/sdcard/ext_sd, it appears that actual external storage can only be used for media or data where the app (or the system using the Storage tool) has a function to map to a different directory.
Have I described the situation properly? Does anybody else see the limitations this might pose or suggest workarounds?
..rob
Click to expand...
Click to collapse
Yes I see this as a problem as well. I have looked into the vold.fstab file (where the system looks to see how it should mount partitions) but changing them just makes neither partition mount. I have a feeling that it might be something in the kernel but I will keep digging around.
Also if someone does figure it out how do you prefer them to be mounted? Internal as /emmc and external as /sdcard? Internal as /sdcard/int_sd and external as /sdcard? Maybe something else?
I guess it would depend how the apps and the kernel handle it, which of course, would vary with a custom ROM. Early builds of CM9 for the MoPho alternated back and forth, but there is also an option to swap what is internal and external as well. When it wasn't mounting at all, you could edit the vold.fstab, which would be my first inclination, so thanks for saving me that step!
I think, from most implementations I've seen, when a device has internal and external storage its been mounted as /mnt/emmc and /mnt/sdcard. Its like that on most of the custom ROMs I've used (on Nook, OG EVO, Hero, MoPho).
..rob
Im really lost on the whole external sd thing. I just want to be able to have my apps on there but android has made it seemingly impossible to do so anymore. Is there a write up or something on how this can be done with todays ICS?
Sent from my EVO using xda premium
Hi, I'm currently running Firmware MediaPad ICS 4.0.3 HWMOD C232B005 which supposedly is pretty similar to stock. My problem is that the internal memory which apps are installed to, ae on the very same partition as the intenal sd card (mounted as /sdcard). Thus the andoird a2sd does not work, I get no "move to sd card option in Settings->Apps. With several games exceeding 500MB with the texture for the high resolution on the MediaPad, I need to be able to move some of them to SD. Also, I need the ames that store their data on /sdcard even if they shouldn't by Android standards (boo, Gameloft) to be stored on the REAL sdcard, whic is mounted as sdcard2. Preferably, I'd be able to do this without mucking about too much. Maybe the best option is to use CM10 if it's about ready for prime time? I guess it'll give me the choice of using /sdcard or /emmc as main storage. (Though it IS annoying CM by default incorrectly labels the sdcard as emmc and the internal memory as mmc - strictly opposite of defined standards for embedded devices.)
naguz said:
Hi, I'm currently running Firmware MediaPad ICS 4.0.3 HWMOD C232B005 which supposedly is pretty similar to stock. My problem is that the internal memory which apps are installed to, ae on the very same partition as the intenal sd card (mounted as /sdcard). Thus the andoird a2sd does not work, I get no "move to sd card option in Settings->Apps. With several games exceeding 500MB with the texture for the high resolution on the MediaPad, I need to be able to move some of them to SD. Also, I need the ames that store their data on /sdcard even if they shouldn't by Android standards (boo, Gameloft) to be stored on the REAL sdcard, whic is mounted as sdcard2. Preferably, I'd be able to do this without mucking about too much. Maybe the best option is to use CM10 if it's about ready for prime time? I guess it'll give me the choice of using /sdcard or /emmc as main storage. (Though it IS annoying CM by default incorrectly labels the sdcard as emmc and the internal memory as mmc - strictly opposite of defined standards for embedded devices.)
Click to expand...
Click to collapse
It's really easy, do this
settings > storage > set primary storage > SD card > restart tablet
all apps will be moved to external sd card, and hopefully also games data like gameloft files. if this didn't happen then do it manualy. if none of that worked well... just download the data again
I think even if you set primary storage to SD, your apps remain on internal. However it will force the Gameloft etc /sdcard storage to external.
I thought the old native apps to external SD functionality was deprecated from ICS onwards? But I could be wrong...
Sent from my HUAWEI MediaPad using Tapatalk 2
Setting the primary storage is the only option ICS provides, no other apps like app2sd work actualy, i tried them
but... root opens new doors remember, i'm sure there are some apps that can move all apps to external sd, although i son't think that's possible when it comes to system apps.
and here i have a question: is it possible to set en ext3 partition on the external sd so that apps can be moved there? i did this on my beloved "dead" htc wildfire and i tell you I LOVE IT! all apps on ext3 partition (256 mb) but when looking at storage settings they appear in internal memory!! crazy right? and that makes those apps load really fast whenturning the phone on.
Don't bother trying to use old a2sd hacks that were designed for Gingerbread and Froyo phones with only a few hundred MB of internal storage.
But I did verify, yes, if you select the option to designate primary (/sdcard) storage as the external SD, the option to move apps to SD reappears. I prefer to store as much as possible on internal rather than external, because the read/write speeds are faster. Of course, regardless of which you select, any app that does allow you to change its storage directory can have a path entered that locates the correct place.
Thanks for the replies everypne! My CM9 Galaxy S II does have an option for moving apps to sd card in the settings->apps menu for compatilbe apps, so I don't think this has been discontinued in ICS+?
Anyway, I figured there WAS enough space on the internal memory for the app I was installing when I got the insufficient space error. I also noticed I had different available memory on sdcard0 (internal storage) and /data (also the same partition of the internal storage) when I ran df in a terminal, and figured something was off, so I ditched the ROM I was using, wiped it all form recovery, and installed CM9. Seems to be working OK for now.
I'll still run out of space in the internal sd card - but for the huge data guzzlers like gameloft I'll try to use Directory Bind which I vaguely remembered reading about and so googled up. As mentioned, it is not really an option to have all apps default to save stuff on the external sd card for security reasons. But if directory bind works (or manually editing in bind mounts in init files), and hopefully it should still be smooth sailing.
Still not sure whether I want to trade it in for a 10" though. Such a pity I can't find any 10" without acceptable resolution, gps, 3g and a price I can justify. The Mediapad sure is a nifty device with a good screen, even though it is a little heavy. But no I'm going way of topic.