I have a 8gb class 4 card. Been using it for over a year. I've just noticed lately that sometimes I bring up all the apps on the phone and I see some loading up. Maybe its due to the class 4...so I've been thinking of getting rid of A2SD. Just formatting the card and leaving it as is. No Fat32, linux-swap or ext3. Would that be an issue running Cyanogen 5.0.7 Test 3?
flexnix said:
I have a 8gb class 4 card. Been using it for over a year. I've just noticed lately that sometimes I bring up all the apps on the phone and I see some loading up. Maybe its due to the class 4...so I've been thinking of getting rid of A2SD. Just formatting the card and leaving it as is. No Fat32, linux-swap or ext3. Would that be an issue running Cyanogen 5.0.7 Test 3?
Click to expand...
Click to collapse
Do some research, half of this post makes no sense. Fat32 will just have to exist if you want any music, files, etc. Swap can be enabled/disabled. And you can move apps to and from SD and Internal whenever you'd like through application settings on the new CM rom.
Seeing apps loading in the app drawer is most likely based on your class 4 card. If your apps will have no problem fitting on your internal storage then there is really no reason for you to have apps2sd enabled. If you have no intention of going over your internal storage with your apps then I agree with your assessment and opinion of getting rid of apps2sd.
Use the option in CM rom to move the apps you have to the internal storage and reformat your sd card to have one partition for FAT32 so you can use if for storage and be done with it.
flexnix said:
I have a 8gb class 4 card. Been using it for over a year. I've just noticed lately that sometimes I bring up all the apps on the phone and I see some loading up. Maybe its due to the class 4...so I've been thinking of getting rid of A2SD. Just formatting the card and leaving it as is. No Fat32, linux-swap or ext3. Would that be an issue running Cyanogen 5.0.7 Test 3?
Click to expand...
Click to collapse
Seeing the applications filling in to the app drawer is a function of having a LOT of applications installed. It takes time for each application to process and get added. It would be the same on internal if you had enough space to install that many applications.
Of course a C6 sdcard would be faster than your C4.
Note: The secondary benefit to having applications on the sdcard is BANDWIDTH. Each storage device is capable of transferring data as some maximum speed. Distributing reads/writes across two devices can produce a peak bandwidth equal to the SUM of the bandwidths of the individual devices. To take proper advantage of this would, however, require that you carefully BALANCE the location of the various bits of data you are accessing such that it actually WILL try to access data from the two locations simultaneously.
Related
Unless I'm misunderstanding...It's true that mounting your SD card in Froyo with apps installed to the FAT32 partition means that your phone can't access applications on that FAT32 partition right?
Yeah, you're right. That's why Google doesn't support having Widgets, keyboards, and other always running services on the SD card. Its a trade off, but a sensible one I think. Having two volumes on the SD card is likely to confuse inexperienced users. Also they need to decide ahead of time how much space to reserve for apps on the sdcard. Too much and they can run out of room for their other data, not enough and they are right back to the old problem of no room for apps.
Anyway, there's no reason you need all your apps on your sdcard. As long as you can put your big apps like games and Google earth on SD you should have plenty of room for other stuff on internal memory.
No, you're not the only one who likes it.
I sure hope that ROM creators leave the option of using old Apps2SD.
That is the only reason I switched back to 2.1
What are the advantages of using an ext partition to store apps/cache/data on an android phone. I have been using an unpartitioned sd card with no problems, but I've seen a lot of people with ext.
Sent from my Nexus One using XDA App
Using EXT allows you to put Root apps, and protected apps automatically onto the SD card. With the FAT i was still filling up my internal storage. I can also still use my apps when i have the fat partition mounted on the computer.
Makes sense, thats actually a bigger advantage then what I was expecting. What about widget functionality? I know most widgets won't work if they are stored on a sd card. Does ext fix that problem?
Also, what is preferable, ext3 or ext4?
So just to make it clear, your SD card is not ntfs, ever.....
And the advantage of Apps2Ext is so that ALL apps can install to the SD card, apps that run 24/7, widgets, and no special coding etc...
Froyo Apsp2SD only moves some apps, and as you mention, moving apps with widgets or that run all the time are going to eventually stop working correctly, especially if you ever mount the SD card over USB.
If your ROM supports Apps2Ext, use it unless you only have a handful of apps installed and you don't need the space..
so the system treats the ext partition like a part of the internal memory? haven't heard about this option ever. sound very interesting since I'm always out of memory.
Sent from my Nexus One using XDA App
Yeah it moves the entire app to the card, unlike the stock froyo version that only moves the binary part of the app I believe. Making a 1 gb partition is literally just like having 1 gb of internal storage just like The nexus s etc.
Is making 4gb ext good?
It doesn't do it by default - default allows to move only the app (no app data) and Dalvik cache to SD. But that's enough for vast majority of people - allows to have equal of ~600 MB of app space before you run out of internal phone space.
There is an option to move the data to SD too, but that's not trivial and not part of any stable DT Apps2SD release, AFAIK.
There is no point in EXT anywhere above 1GB, just for that reason.
Tiberx said:
Is making 4gb ext good?
Click to expand...
Click to collapse
As long as you are willing to give up teh space on your SD card. I only made a 512mb partition, and that has fixed any and all storage issues i had.
1GB it's enough... even with ~120 apps
can someone link a tutorial? search doesn't work properly on my phone!
Sent from my Nexus One using XDA App
In my signature. No need to search.
can't see that either in the xda app... mind posting the link?
Sent from my Nexus One using XDA App
http://forum.xda-developers.com/showthread.php?t=715940
I have CM7 stable booting off an 8G SD card. Once I registered Google nicely downloaded all the apps I have on my phone. I'm slowly adding and removing apps as I tweak my Nook. At one point when I tried to install an app it failed with an insufficient memory error. Thinking this was like my phone I went through and moved a bunch of apps to the "SD card". The app still wouldn't install. It wasn't until I uninstalled several unneeded apps that I was able to install the one I wanted.
I don't have my Nook in front of me but did look at the various memory sizes several times and always had plenty of internal and SD free memory. Obviously everything is on the SD card but I thought that moving from "phone" to "SD" might be moving from one partition to the another.
So how does the memory scheme work in this case that so it prevented me from installing? Does moving from Phone to SD actually accomplish anything in this case? Curious minds (well one anyway) want to know.
Why does my Captivate only limit me to having 2GB of space for apps? I'm not using an external SD card and I want to install my apps onto my internal SD card or atleast move them there.
It's been a while since I have been on a stock ROM so please correct me if I'm wrong, but I believe you can move at least some of the apps by going to settings / applications and then, in the individual application settings, select "Move to SD."
I know you can't move widgets or alarm applications because they will break if they aren't on internal memory, but you should be able to move games, etc. with no problem.
Move to SD was not available on Eclair... what are you running?
Sent from my Cappy
I'm on 2.2 right now. There is an option to move to SD but it only moves it to external SD not the internal one. It's split up into 3 sections
Internal Memory
Internal SD Card(I want apps to go here)
External SD card
muh316 said:
I'm on 2.2 right now. There is an option to move to SD but it only moves it to external SD not the internal one. It's split up into 3 sections
Internal Memory
Internal SD Card(I want apps to go here)
External SD card
Click to expand...
Click to collapse
Ah, now I understand. I never had enough apps on Froyo to play with moving them but shooting from the hip, have you tried removing your external card and see if it will let you move them then? If not, I know that there are apps2sd applications on the market that should help you, but I haven't used any of them to give you a recommendation.
apbthe3 said:
Ah, now I understand. I never had enough apps on Froyo to play with moving them but shooting from the hip, have you tried removing your external card and see if it will let you move them then? If not, I know that there are apps2sd applications on the market that should help you, but I haven't used any of them to give you a recommendation.
Click to expand...
Click to collapse
I've used all of those methods and none work.
Did you find solution? I have same situation here, it's pretty weird internal SD could only be stored with application data instead of application itself.
I'm almost positive that you can't move apps to your "internal SD card" regardless of whether or not you have an external sd card installed.
My understanding is that you can only move apps to the external SD card (at least that's how it's been on any ROM I've ever used)
why... Why! WHY!!! . . . oh >.>
muh316 said:
Why does my Captivate only limit me to having 2GB of space for apps? I'm not using an external SD card and I want to install my apps onto my internal SD card or atleast move them there.
Click to expand...
Click to collapse
Why you ask...
Well simple, your limited to only 2GB because this size was choosen by phone manufacturors years ago when they were first designing the phone.
Consider that most of the phones in use back when 2.2 was released did not, for the full storage potential, even have the 2GB that we have just for apps (16GB in total). Heck most did not even have 1GB (I think 512MB was the standard). There was no separation between app storage and other media. This lead to users running out of space for both rather quickly. The solution then was to find use for the external SD as it could be as large as 32GB of storage.
The whole "internal SD" thing was thought up because it seemed wise to separate app storage from media storage. Also back when 2.2 was first released we did not have such massive apps as on the market today, so 2GB was plenty of any and all user (excluding the ppl who felt a need to have 200+ user apps...)
So, you can't store apps to the "internal SD" because that's not what it is meant to be used for. When companies decided to start putting such massive storage into the phone there was no reason for it to be any bigger.
As to only being able to move apps to the external SD, simple; Google did not design Android to do so.
To allow such would require changing how Android sees the "Internal SD" and to change how the app to SD function works, it is not currently written to check for multiple SD cards. I don't see any Dev willing to take up the task when the solution to running out of app space has already been solved by a much better means.
A different way to view the problem would be to ask (or learn, as that's the xda way) about re-sizing the partition to make the app storage larger. If enough people ask (politely!) maybe one of the Devs can be convinced to make it standard in their ROM that it be more then the default 2GB, or someone might make an app or flashable .zip that allows for re-sizing.
lt:dr - phone is old, based on old specs (think pre- 2.1 Android).
Sigh, this is exactly what I was worried about when upgrading from my EVO 3D.
I noticed my new M8 has a sdcard0 and extsdcard folder. And of course, the apps and games which download hundreds of megs of data in order to run are downloading to the 24 gig internal sdcard0 mount point instead of the nearly empty 64gig extsdcard0 mountpoint. I really REALLY hate how so many Android phones seem to do this, why can't it just be partitioned as internal instead of faking a sdcard, thus making large apps install to internal with no option of installing to the actual external card?
Anyway, without rooting my phone, is there any way I can somehow set it so apps download and install their data to the actual SD card? The whole reason I didn't get the M7 was because I don't want my data to be stuck on the phone's internal memory in case anything happens, as well as to not waste internal memory space on several hundred megs or even gigs of data when I can use a large sdcard for that.
I believe u can go to manage apps and move apps to the sd card. Some may not be able to if it's not comparable but a lot of them should.
Sent from my iPad using Tapatalk
aaron130 said:
I believe u can go to manage apps and move apps to the sd card. Some may not be able to if it's not comparable but a lot of them should.
Click to expand...
Click to collapse
I tried that, it only moves the app executable to the SD card, not the hundreds of megs of additional data it downloaded. The app management screen even tells me how much of this additional data is on the internal memory and how much of it is on the SD card (it's all on internal), but moving the app doesn't move the additional data to the SD card.
One would assume that the ext sd 's bus interface would be quick enough to not bog any app which would be using it. That being the case htc has no excuse for not having interchangeable symbolic mounting points between the two sd's. Ive physcally moved some of the data from app's (dcim, and random music ) directories to the extsd, and at least it unburdens the internal sd.
The apk resource fork in these systems could be processed better in android and it's sdk, or even the runtime.
F yes it sucks.