Related
Hey guys
Im on holiday now so cannot really check myself the differences, but just wanted some quick info on the A2SD, with the official froyo i was hoping everybody will start using it, but somehow people still using the old method, whys that?
thanks
Froyo A2SD is completely reliant on app developers. If the devs doesn't allow it in their app then it can't be moved to the SD card. This is really only a problem because Froyo is still new.
Old A2SD you can dump everything on the SD
However, I'd be interested in seeing if there is a way to force an app onto the nand using A2SD+. Would work better for things like widgets, home replacements etc, as they'd run quicker for people with slow sd cards.
Probably because the FroYo one sucks !
Why ? Well, mostly because devs have to rewrite their apps so they can use FroYo's app2sd function...
With the "old-fashioned" a2sd, there is no need to do anything, just sit and enjoy the free space
APP2SD allows you to move certain apps to your SD card and run them from there BUT as these are placed on the normal root of the SD when you mount the SD, via USB for example, you loose access to these apps until you remount SD. This means you cant install widgets to the SD and such like.
APP2SD+ on the other hand uses an ext3 partition (or ext4 on newer versions) which then installs all apps & widgets to that partition and when the SD is mounted you dont lose any apps or widgets as is located in a seperate partition.
Hope that helps.
Sent from my HTC Desire using XDA App
Sent from my HTC Desire using XDA App
wow! thats quick thanks for you input guys think you explained everything i wanted to know really
Id want to use the offical a2sd as i think using ext3 partitioned sd card have already slightly damaged the card cuz it keeps giving me errors everytime i connect it to a pc
mrwookie6379 said:
APP2SD allows you to move certain apps to your SD card and run them from there BUT as these are placed on the normal root of the SD when you mount the SD, via USB for example, you loose access to these apps until you remount SD. This means you cant install widgets to the SD and such like.
APP2SD+ on the other hand uses an ext3 partition (or ext4 on newer versions) which then installs all apps & widgets to that partition and when the SD is mounted you dont lose any apps or widgets as is located in a seperate partition.
Hope that helps.
Click to expand...
Click to collapse
So let me understand the names:
APPS2SD = Froyo Original (comes with official Froyo release)
APPS2SD+ = Hacked version which has been out since FRF50 leak?
EDIT: But if APPS2SD+ is so much better (keeps apps on ext3 partition), why to people keep using the original APPS2SD on their ROMs?
Check this explaination. Quoted from neoKushan from yesterdays thread.
neoKushan said:
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".
Click to expand...
Click to collapse
That's a great summary, thanks for that!
But... how can I create an ext3 partition on a new SD card? I don't want to use ROM Manager because that has a maximum of 512Mb for ext3, I want to make 1gb or more.
Also, what size should I make swap partition?
Vice83 said:
That's a great summary, thanks for that!
But... how can I create an ext3 partition on a new SD card? I don't want to use ROM Manager because that has a maximum of 512Mb for ext3, I want to make 1gb or more.
Also, what size should I make swap partition?
Click to expand...
Click to collapse
You can do that thru recovery-windows.bat by going thru recovery mode by volume down + power, go to recovery then when the red exclamation point appears just run the recovery-windows.bat by double clicking on it. You can get these files from r5-desire-root-alt from the rooting process files (search the forums for this if you don't have it). But be cautious cause when you partition your sd card, all your files will be wiped so make sure to backup everything you need. Cheers!
Edit:
Actually this summary about the ap2sd and ap2sd+ and froyo ap2sd should be stickyed for everyone, so it would not be ask over and over again.
Couple of extra ways to partition:
1) Flash AmonRA's Recovery to your phone (I used Unrevoked to do it)
2) Use GParted on a Linux LiveCD (e.g Slax) to partition your card exactly how you want it
Vice83 said:
That's a great summary, thanks for that!
But... how can I create an ext3 partition on a new SD card? I don't want to use ROM Manager because that has a maximum of 512Mb for ext3, I want to make 1gb or more.
Also, what size should I make swap partition?
Click to expand...
Click to collapse
ROM Manager is probably the easiest way to do it, but I was stuck with EXACTLY the same problem when I rooted. I chose to flash AMON Ra recovery (don't have the link, but you can google it up), and then used that to create a 1024MB ext partition. Then used AMON Ra again to convert the ext partition to ext3. Hope that helps.
However, one question I have regarding neoKushan's explanation is that if I did create a 1024MB ext3 partition, then the same capacity should be visible in the phone's internal memory. However, after I rooted and restored my apps, I could only see about 100+ MB of free internal memory. Can anyone help me with this please? Am using the Opendesire Official Froyo 1.0c ROM that has A2SD built in
deepdevil said:
ROM Manager is probably the easiest way to do it, but I was stuck with EXACTLY the same problem when I rooted. I chose to flash AMON Ra recovery (don't have the link, but you can google it up), and then used that to create a 1024MB ext partition. Then used AMON Ra again to convert the ext partition to ext3. Hope that helps.
However, one question I have regarding neoKushan's explanation is that if I did create a 1024MB ext3 partition, then the same capacity should be visible in the phone's internal memory. However, after I rooted and restored my apps, I could only see about 100+ MB of free internal memory. Can anyone help me with this please? Am using the Opendesire Official Froyo 1.0c ROM that has A2SD built in
Click to expand...
Click to collapse
I'm not sure about what exact capacity for the internal memory after partitioning to ext3 but when I was on Opendesire before for the eclair 2.1 after I'm done flashing the rom and setting up the whole ap2sd+ my internal memory was 410mb. I used:
swap=0
ext=1024
fat32 is for the rest of the card
Then after upgrading to froyo rooted ROM, I'm only getting 140mb tops. I dunno... I'm too lazy now to get into it right now... maybe soon I'll play around with it again so I can get back my 410mb internal space with the ap2sd+
Stewge said:
Froyo A2SD is completely reliant on app developers. If the devs doesn't allow it in their app then it can't be moved to the SD card. This is really only a problem because Froyo is still new.
Click to expand...
Click to collapse
Not 100% true, because you can change the default install location to SD card (via ADB if stock, and an app if rooted) and then you can have the vast majority of your apps on SD card even if they've not been updated for Froyo.
Regards,
Dave
I always thought the main negative with A2SD+ was that the cache was moved to the sdcard, which of course would wear out the sdcard (slightly) quicker.
Vice83 said:
So let me understand the names:
APPS2SD = Froyo Original (comes with official Froyo release)
APPS2SD+ = Hacked version which has been out since FRF50 leak?
EDIT: But if APPS2SD+ is so much better (keeps apps on ext3 partition), why to people keep using the original APPS2SD on their ROMs?
Click to expand...
Click to collapse
Not exactly!
Prior to Froyo, there were principally two versions of Apps2SD:
1. APPS2SD (or A2SD )
2. APPS2SD+ (or A2SD+)
The first would move your apps to the EXT partition, and the second would move your apps and the Dalvik cache to the EXT partition (see here for an explanation of the Dalvik cache).
Now we have Froyo, we have "native", or "Froyo" apps2sd as well, which does much the same as (1) above except that there is no EXT partition and the apps are on the FAT32 partition of your SD card.
Regards,
Dave
sparksalot said:
I always thought the main negative with A2SD+ was that the cache was moved to the sdcard, which of course would wear out the sdcard (slightly) quicker.
Click to expand...
Click to collapse
Dalvik cache is only actually updated when a new app is installed or and old app is updated, so whilst it will incur more writes to SD card, it probably isn't anywhere near as much as the apps write themselves to the FAT32 partition.
Regards,
Dave
Great summary, but can I format my 8 GB SD card as EXT3 and just forget about the FAT partition? I'm using Ubuntu on my laptop and my EXT4 /home partition is just fine for storing images, movies etc. I really don't get this ado about having an EXT and a FAT partition. Or am I wrong here?
quick question, if i move to another bigger sd card, can i copy my card and transfer it to the new one without losing the EXT, and the apps on it? would i need to make a image of the card? thanx for any advice.
make a backup of them first on your pc and copy them to the newly partitioned sdcard....ext to ext and fat to fat
So there is 3 versions?
1. Froyo A2sd = fat32 only = apps installed to sd
2. A2sd = fat32 + ext = apps installed to sd in ext partition
3. A2sd+ = fat32 + ext = apps installed and Dalvik cache moved to sd in ext partition
Is there any more variants? lol
Sent from my HTC Desire using XDA App
Hi,
I'm using OpenDesire 4.0.34 and have partitioned my sdcard to have 3 partitions:
1 - FAT32 14GB
2 - EXT3 512MB
3 - SWAP/CACHE 32MB
Now I have one question:
I have enabled the "Allow application moving" setting in Settings->CyanogenMod settings->Application settings and selected Install location: Internal the same screen.
My question is: I've installed a bunch of apps I often use and they used to leave me with only 19MB free in internal phone memory. Now it shows free internal memory around 120MB?! I've checked all the apps in the Manage applications and they are on the phone (at least it says so). I've mounted /sd-ext in recovery and all the apps are there...
Can anyone explain me what's goin' on here?
Thanks for your help!
Uhm... you do know that the partition of an ext3 sd-ext system is exactly to provide greater storage space for your applications, don't you?!
Guess not...
The /sd-ext is the mount point of my ext3 partition on the sd card?
Anyway, I didn't move any app to sd card (at least explicitily).
z7x8c9 said:
Guess not...
The /sd-ext is the mount point of my ext3 partition on the sd card?
Anyway, I didn't move any app to sd card (at least explicitily).
Click to expand...
Click to collapse
When you use Ext3 partition youll get "A2SD+" and both your internal memory and your Ext3 partiton will become your new "internal" space on phone. So if the setting is set to "internal" the apps will go to ext3 and internal phone memory.
The internal phone memory counter however only show how much space you have on the internal phone memory where only small parts of the apps is installed.
I just removed my sdcard to see what would happen and all my apps are gone.
As such I assume they are all on the sdcard...
So when using the ext3 partition, how can I choose if an app is installed to the phone memory or to the sdcard? Is this possible at all?
Also, when I go to manage applications, I can "move to sd card" any app, but what does this do then?
I'm a bit confused...
Moved to Q&A as not development.
Please do not make new threads in development to ask questions
z7x8c9 said:
I just removed my sdcard to see what would happen and all my apps are gone.
As such I assume they are all on the sdcard...
So when using the ext3 partition, how can I choose if an app is installed to the phone memory or to the sdcard? Is this possible at all?
Also, when I go to manage applications, I can "move to sd card" any app, but what does this do then?
I'm a bit confused...
Click to expand...
Click to collapse
you are getting apps2sd confused with the native android move to sd function!!, when you create an ext partition and use a rom that supports apps2sd, the developer has used a script that point the device to the /sd-ext as the INTERNAL STORAGE location, where as if you use the move to sd function in android, the apk's are move to the Androidsecure folder in the root of your sd card, as aposed to being stored in /data/app
I think I've got it...
On an a2sd enabled rom, I'm not required to do anything in order to install apps on the sdcard.
The move to sdcard button is the native android method to move apps to the sdcard.
I got confused because in OpenDesire in the Settings->CyanogenMod settings->Application settings there is an option to allow application moving, but all this does is enable me to move any app to the .android_secure using the move to sdcard button. It's got nothing to do with a2sd, right?
Thanks for your help!
So, you are thinking 'not again the *** apps2sd n00b question', but here I am
I did some research on XDA and the rest of the internet though, but nobody seems to have this problem.
I have a rooted Desire with DeFrost 6.0. With it, it is very easy to install your apps on the SD-card. I have only 8 apps on the ROM itself, but those are widgets and apps with notifications like Facebook (notifications don't work if they are installed on de sd-card is my experience).
The rest of my applications are installed on the sd-card (around 80 apps). But the problem is that all apps also have a piece of dalvikCache on the ROM as well. You all know that of course. For instance, I installed Documents To Go (5MB) on the sd-card. It also has 5MB dalvikCache on the ROM, so thats double the price .
Now if people ask here 'is it safe to move the cache to the sd-card', most of you say 'unless you want to show off how much empty space you have on your phone, I would just keep it on the phone'. But I do not have any free space.
With DiskUsage I can see that I have around 150 MB of data: 26MB system data, 15MB free space (and he is already nagging the telephone is running out of space), and more than 100MB of applications, with most of it is dalvikCache.
So is this normal? Is 80 apps really the max you can have?
My biggets app is by the way Documents To Go (5MB), and I had to delete it. So I don't have very big apps.
Just want to know how much apps you guys have
Thanks.
How have you forced the Dalvik Cache to stay on the phone memory and why/how have you copied your widgets on your phone memory?
PS: Do you use an EXT3 Partition or the Froyo legacy A2SD?
It's not unusual to move dalvik cache as well as the app. You will need root though, and then just partition your sd-card and install a rom with a2sd+. The only /data/data will take up space on the phone.
UpSpin said:
How have you forced the Dalvik Cache to stay on the phone memory and why/how have you copied your widgets on your phone memory?
PS: Do you use an EXT3 Partition or the Froyo legacy A2SD?
Click to expand...
Click to collapse
I didn't do anything to force the cache to stay on de phone. But it's normal the dalvikCache is on the phone memory right?
I use defrost 6.0 and in it you can go to settings > applications > manage applicatons, an you can move all your apps to the sd-card. I'm not sure what kind of A2SD that is.
I move any applications with widgets to my phone memory, because otherwise widgets don't work anymore if you reboot your phone.
@mortenmhp: But also a lot of people do not recommend to move the dalvikcache. Is it safe to do?
you're confusing a few things:
APPS2SD:
There are two methods used at the moment.
The Froyo method, made by Google, which you use at the moment. It installs the app on the phone memory and is able to outsource a small amount of data to the FAT32 partition on your SD-card. It does create failures with apps that use widgets or run in the background.
The A2SD+ method, integrated in DeFroST and almost every other custom ROM. You have to create an EXT3 partition on your SD card (use ROM manager for this) and then reflash the rom. After that it gets activated automatically. All apps and also the dalvik cache gets moved on the EXT3 partition on your SD card. You don't have to and you shouldn't move any apps around afterwards with the Froyo A2SD described above. Only some small data gets stored by the apps itself on the internal phone memory.
Moving the dalvik cache is safe. Maybe you confuse it with SWAP? Which isn't necessary on the HTC Desire.
ok, this is a little confusing
I'm running defrost
let's suppose that I installed the firefox app.
the diskusage tool tells me that it takes 13,4 MB in internal memory.
in applications settings, I have the option to move the app to sd card.
When I do this, my available memory does not change (102 mb)
Does that mean that firefox was already on the sd card ?
In that case how do I know what eats up my data storage ?
Thanks for precisions ?
Do you use A2SD+ together with an EXT3 partition.
If so, every app you install will get installed on the EXT3 partition on your SD-card together with the Dalvik cache, instead of your internal phone memory. If you move this app with the Froyo A2SD tool to the SD card then you'll move the app from the EXT3 partition to your FAT32 partition, stupid.
However, every app, while running, creates some temporary data files. Those files remain on the internal phone memory. And maybe Firefox mobile creates some huge data files, but the main app is installed on the EXT3 partition, now, because you moved it with Froyo A2SD, a small part is installed on the EXT3 partition and some part, the moved on the FAT32 partition. The created data remains untouched.
I had 106 MB free internal memory. Then I installed Firefox and still had 106MB free. I started Firefox, 103 MB free.
Diskusage tells me Firefox needs 2.81MB internal memory. 2.81MB of this is data.
In the Android app settings android tells me Firefox occupies 16.19 MB, 13.38 MB for the app, 2.81 MB data.
So those 13.38 MB are located on the EXT3 partition. If I move Firefox now, parts of the 13.38 MB get moved from the SD card to the SD card.
Ah, I get it now. Thank you very much. I did everything you said, so it should be ok now. So there is no need anymore to move apps, with widgets for instance, to the memory of the phone?
Thanks!
If you use app2sd with the ext partition now, then no, you don't have to move any app or widget around, and you shouldn't.
With Quick System Info you can check how much free space is left on your ext partition.
Sent from my HTC Desire using XDA App
hey everyone
i have rooted my phone and installed cyanongen mod7, the fact is that i followed the noobprrof tutorial, and as he stated i partitioned my sd card, i left 1 gb ( its a 4gb memory now its divided to 3 and 1 ), but i didnt know where did it go and why i did partition my sd card, i thought it would add up to internal memory but it didnt...
please can anyone tell me whats the purpose of paritioning it ?? and how can i let apps get installed on this paritioned part if its purpose is so...
thanks in advance
It's for a2sd, it doesn't add up in internal memory, if you want to check if it's there download quick sytem info from the market, it's purpose is to store apps on your sd(mainly, there's always some data left.) for example when i had stock 2.2 froyo on my desire non rooted, i couldn't have more than 165-170 apps, now i have 379 and ext is also for the rom itself, like a sense rom doesn't fit totally on the system partion, so the part which doesn't fit is on your sd
Hope you understand it
thank u, i actually understood wut ur saying
for instance, i have downloaded games and stuff, now the phone says that the phonememory is on low storage, i still have like 30 mb... i tend to move apps from phone to sd card...
incase all internal memory is used will it conitinue installing on the 1gb i have paritioned... and is it just a notification that doesnt effect anything...
i also would like to ask if i can i can automatically download & install the apps from the market on the sd card...
thanks again
ps: i checked the system info and yes it is there... a2sd 0.96gb and 0.9gb free
It's not just like that
If you install an app for instance google earth, it's around 24mb, 300-400kb will stay on your phone and the rest will go to that partition automatically, although some apps like this iBeer i installed is fully on sd, it depends, but if you're low on memory just move some apps manually to your sd(this doesn't make them move to the ext but fat32 partition(the part that windows can see). If you just insert a SD and applt android's app2sd not a lot of the app will go to the sd, on the other hand the a2sd implied in rom's doesn't give you limitless place till you sd is full. If you want that apply data2sd, that adds to the internal memory as you thought
the max apps you can put on your desire with a2sd is max 400 i think, as i can't move any app manually to sd, and i have 35mb left with 379 apps
hope u understand it even better now
ok i did move the apps 2 sdcard, but they are moved to the 3gb partition and not the 1gb partition which i cant see, i only want to know what is the purpose of this 1gb that i made due to the tutorial... since i cant move apps to it or even put files on via usb ( as music and stuff )... then why is it created... ??
ps : the 1 gb is ext4 the 3gb is the fat32
i really wish there was some thread explaining all , maybe i would have let ur life easier hehe, im sory but im new on android...
thanks again
What did you use to create the 1gb partition? Did you use something like mini partition .. under windows?
I had a hell of a time trying to get it to work this way (if you did) the solution i found was to get the gparted live cd (google it) and run the partitioning wizard on that and the auto apps2sd will work.
The point of doing it is that some roms need more space than the desire has, I'm using insert coin and it needs a proparly formatted ext3 to work to fit the whole rom onto the phone.
Have you checked using quick system info to see if the a2sd storage is being recognised?
hey amriving
actually i did divide my sd card with gparted, everythings going great, but the fact that i cant use the 1000 mb ext2 partition (app2sd) is wut im asking about... (total of 4gb memory)
i mean when i move the apps to sd card they go to the 3gb fat32 space i have, and not the 1gb i partitioned...
so what i want to know is what is the purpose of this (app2sd) 1gb ext2 partition, how can i use it
i checked the system info and i found that there is 0.96gb of the app2sd partition and there is free 0.9 gb,
i have cyanogen mod7 rom
and thanks for the reply
Don't move it to sd, i think you didn't understood me, it does it automatically, just install a app, look at it's size, then delete it, you'll see that not that size went away from your memory but much less
You can't use it through windows, only if you have linux you'll be able to see inside the ext also with root explorer( go to recovery and then mounts then press mount EXT )
And they go to the 1GB partition. There will be an android.secure in your sd with apps, but if it wouldn't work, i wouldn't have 55mb android.secure with 390 apps now! and just 100mb free on 1.4GB ext, Just don't question this anymore, download 100 apps, you'll see it very well then if you don't then you obviously have a problem
thanks everyone
android.secure is on 3gb fat32 not the 1 gb ext...
i also went to recovery its on mount sd ext...
guys what i want to know is why when moving the apps to sdcard, they are going to 3gb fat32 partition instead of 1gb ext4 partition...
is nt it supposed to go to 1gb ext4 partition ?! which is the reason every android user is doing for ... ?
i have checked the ap2sd and yes it is there
android.secure file is in 3gb partition not the 1gb ext4 partition
No no you didn't understand me, look normally with 160 apps would your phone memory be full, and your android.secure(on the 3gb partition) be large, now it shouldn't be very big anymore, because for example city story is 23mb, 1mb on phone memory and 22 on ext. normally this would be 5-10 mb on phone memory and remainder on the 3gb(fat32 partition) now this is most of the times divided over the 3 or just in ext and phone memory, and the main reason is a lot of the app goes on the ext
answer
F*S Even i, a noob understood it 3 times allready..
btw this answers my final question here
listen(more like read), i'll try to resimplify the answer for you, think of an android app as a windows app.
a windows app is Commonly installed in 3 - yes THREE seprate location at once!
1. Main Program Files - C:\program files\<APP NAME HERE>
this contains all the app's inner working, modules, GUI, sound, pictures and stuff - most of the app is located here so this folder is 'heavy'
2. appdata - C:\Users\<USER NAME HERE>\appdata\<Local \ Roaming>\<APP NAME HERE>
this may contain any setting, saves, projects, and temp files for the app to use.
so only some parts make it here - litewight but still takes up space..
3. Registry - run>regedit.exe
this is sort of a log file for all windows operation, installaions, apps location and sometimes even app settings
again litewight but takes place..
SAME WITH ANDROID - sort of..
an android app contains Resource Data - like program files, the 'exeutable', settings, modules, critical data for the exeutable and more..
and so when you use the traditional APPS2SD that comes Froyo+ ( settings>apps>google earth>move to SD/PHONE )
all the non-critical data and resources move to the SD fat32 patition.
all the remaining critical data, 'exeutable' and stuff remain on the internal memory which still takes up valuable internal space, that's where a2sd+ comes in, as mentioned before, a2sd+ again moves to rest of the remaining appdata to the ext, and only tiny critical part of the app remains on the internal memory - therefor you get to install many apps until you internal memory fills up or the ext fills up, this time only the absolute critical app files that cant be moved to the ext OR the fat32..
as TopGear63z said:
most of the times divided over the 3 or just in ext and phone memory, and the main reason is a lot of the app goes on the ext
Click to expand...
Click to collapse
data2sd extends your internal storage..
a2sd+ lets you install more aps
EXPERTS: Please verify my answer as i am also a noob and this is my understanding on the subject, i maybe very wrong or very right
PS: Why double post
thankyou asaf400
actually i know all this and i really appreciate ur reply
but wut i wanted is to install apps on ext, and actually i found it i downloaded simple2ext app and now i have 150mb free internal memory, see now all apps are on ext part of the memory card... this is what i wanted to know...
thanks all
or you could just flash a data2sd based custom rom like droidzone's starburst or gingerburst... you'll get upto 2gb of internal memory from the start
I'm having trouble getting link2sd to work
As soon as I got my phone & found out how little internal storage there is for games, I read about link2sd. I didn't know that I was supposed to make an extra partition on my SD card. Whoops.
I moved a bunch of apps to the SD card (main FAT partition) and they all still ran, though I was still really short on space on the /Data partition of my internal storage. I guess there's still data & cache being stored in there.
Recently I found out that I was supposed to have made an extra partition, so I added an ext3 partition and a swap partition (both Primary) after my main FAT32 partition. CWM is able to mount the ext3 partition, but FreeSpace does not see it, and S2E doesn't appear to see it either. Link2SD sees it, though, so I figured it was fixed (maybe?).
I was thinking that if I moved some apps from SD back to internal, and to SD again, maybe ALL the associated files would be moved and I'd have more free space. No luck. It takes FOREVER to move an app from SD to internal storage now, and I don't wind up with any extra space when I move them back to the SD again.
Could somebody please help me troubleshoot & correct this mess?
Phone is an AT&T Xperia Play R800at, Android version 2.3.3 if it matters. It's rooted, but no custom ROM.