Develop Bugs

Memory management

Het me start saying that I nove mt Desire. One thing not so good is the short memory, at least in my opinion... I've been testing all sort of apps and after one month of fun, I only have 30mb free space on internal memory. I've been using apps2sd to move apps to SD but a lot of then don't allow it.
What's your opinion and experience on that issue? Can you give me some advice to "grow" my memory?
Thanks in advance...
Sent from my HTC Desire using XDA App

verdura said:
Het me start saying that I nove mt Desire. One thing not so good is the short memory, at least in my opinion... I've been testing all sort of apps and after one month of fun, I only have 30mb free space on internal memory. I've been using apps2sd to move apps to SD but a lot of then don't allow it.
What's your opinion and experience on that issue? Can you give me some advice to "grow" my memory?
Thanks in advance...
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
fyi the term memory management refers to the way android handles the ram not the internal storage, as for apps2sd your getting confused, the move to sd function in froyo has nothing to do with apps2sd, to get apps2sd to work you must create an ext 2/3/4 partition on your sd card

Thanks for the info.
But one thing. I've been using the app2sd to move some apps to the SD card and my SD OS fat32. What do I gain by formatting to ext2/3/4?
But still, how do you overcome these memory limitation?
Sent from my HTC Desire using XDA App

verdura said:
Thanks for the info.
But one thing. I've been using the app2sd to move some apps to the SD card and my SD OS fat32. What do I gain by formatting to ext2/3/4?
But still, how do you overcome these memory limitation?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
if you have a rom that is apps2sd enabled, make a partiton on your sd card that is ext 2/3/4, this is the same as the native linux fs, then the apps2sd script creates a symlink between /data/app/, the dalvik cache and your ext partition, moving everything from thoes locations to the ext saving alot of space

Thanks a lot for your help!
I already have apps2sd working. At least I think so ... He moves the apps to the card. You think I should format in ext?
What other advice can you give to a beginner to improve the storage space? Can I force some of the applications that app2sd doesn't allow me to move to SD to go anyway? Games and so...

[Q] After partitioned my SD card, where the space had gone ?

Hi all "I am new at this stuff so apologies for my ignorance in the following explanation"
I have a rooted desire phone with a 4GB class 4 SD card and clockwork recovery
The internal free phone storge was 51.2MB, and I decided to partitioned my SD card in order to free more space for the app. "which is 90% of them are on the SD card" and for using some custum room "I actually dont konw the use of partitionning in custum room" but that what I read
So, I partitioned my SD card using Rom Manager with 512mb ext and zero swap with no errors, after that I put all the app. back to the SD card with no problem and all app. run smoothly from the SD card
I checked the internal phone storge using "DiskUsage" and it was as follows
Data 147.6MB
Application 35.4 MB "some of this app. can not move to the SD card & the other I wanted on the internal memory like Astro"
System data : 61.0MB
Free space 51.2MB "which is the same as befor partitioned as well as all the above sizes "
And the SD card total space was 3.21 GB which mean that the 512 MB suppose to be ext. partion right now
The Qustion is where is the 512 MB that suppose to be ext. partion ? Should this partitionning prosses free the internal memory of the phone ? and what is the use of partitionning in custum room ?

It is kind of weird at first when your new to it all. Took me a few weeks to get use to it and understand how it roughly works.
When you partition your SD card so you have an ext partition, it won't actually show up as internal memory. The internal memory is being read off of the /data partition. To make it simple, the ext partition acts like it's "hidden" so to speak. To get it working you would need an A2SD script at least. Depending on what rom you have, the script could be an addon, where you have to flash it after the rom, or it would be built in so it's just up and running anyway.
You can check to see if the ext partition is working. Apps can see if it's working, just search around in the market. To get the apps onto the ext partition, you would probably have to move them, but don't use the moving feature in Settings > Manage applications.

Thanks for your reply
I actually didnt flashed any custom rom yet "I am planning to" and I am running the stock rom froyo 2.2 which have the move 2 SD card feature, and the only app. that I had in this matter is "Move 2SD Enabler" which with It I moved almost all the application that I want to the SD card "some app I cant like the maps"
But even after the moving of all app. the internal phone memory is the same
I mean I cant feel any deference after the partitionning
So How can I use this 512MB ext partition or when ?
and also are these free space on the internal phone healthy ? or may I suffer a space problem when I tried to flash a rom? and what kind of ext does the rom manager do ext.2 or 3 or 4 ? and does it matter when flashing a rom ?
Sorry for the dozen of questions

With most roms it comes with A2SD (there are other deviations of it but the same principle). This is a script which tells the rom to install apps to the ext partition on your SD card instead of the internal memory. Thus, you get more app storage.
When you have A2SD, only the apps get put on the ext partition. Other things like the data for the apps and the dalvik cache stay on the internal memory and will (eventually) fill up the internal memory. That's where d2ext for example comes in. (You can read about all this stuff in your own spare time).
Recovery/rom manager uses ext3 but you can upgrade it to ext4.

[Q] APPS2SD+

hi,
I have just installed my first custom ROM - PyramidMod007_v10... thanks to all the great resources on these forums that helped me get away from the Official Gingerbread.
I have a question about the APPS2SD feature... I don't really understand how it works. I created a 512mb ext3 partition on my SD Card and installed the new ROM.
My question is... Do the apps automatically get installed to the Ext partition now... therefore do I not need to move to SD Card? It seems when i do move to SD card as an experiment - sometime the APPS2SD storage goes up and sometimes the Internal Storage goes up??
I'm confused - owing mainly to the fact that I have no idea how this all works!
This is the data from Quick System Info:
SD Storage - 6.92GB Free: 6.19GB
A2SD - Total: 504MB Free: 213MB
Internal - Total 148MB Free 122MB
System Storage - Total 250MB Free: 13.12MB
System Cache - Total 220MB Free: 202MB
Thanks

Its a script that runs at start up (/system/etc/init.d/)
The a2sd script symbolically links /data/app (where your apps are installed) to /sd-ext/app. This means any app in /data/app is "moved" by the script to /sd-ext/app.
However an app is more than the apk in data/app. It also has /data/data/ and in there are libs, preferences and data for each app. Also there is /data/dalvik-cache. This is usally also symlinked (to /sd-ext/dalvik-cache/)
Using "move to SD" uses googles own implementation. Historically, this literally moved the apk to /sdcard/.android_secure/ however now in Gingerbread it also moves the libs (if an app has libs).
"move to SD" moves more in GB than in Froyo but still not more than a2sd+ (if dalvik is moved) however, you will find as it moves the libs, if you combine both, even more space is spared but to me this is far too reliant on the SD card

app2sd
Hello XDA!!
i am just giving the some information here for my fellow android mates!!
here's all u need to know about Ext2,Ext3,Ext4 app2sd
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"

Hello AlAxe
Thanks for great discription of How A2SD works. I have a question:
AlAxe said:
Hello XDA!!
i am just giving the some information here for my fellow android mates!!
here's all u need to know about Ext2,Ext3,Ext4 app2sd
....
.....
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
Is this www.beginnerstech.co.uk/apps2sd-for-rooted-androids APP2SD+ you mention above? or there are another link you have?
Also, between above app and this one [Script] App2sd which one do you prefer? thanks again...
Regards

That script you posted is very old, a lot of custom Roms have their own scripts built in so you don't have to worry about this any more
If you really want to use that one, read the differences in that post to find out which you prefer. Depends on how many apps you have and how fast your sdcard is.
Personally I think there are better / easier methods, some use apps or flashable zips to make installation much easier and don't require a full wipe. Search for mount2sd, or cronmod int2ext for instance. Whichever one you choose, it doesn't matter too much in the end, whatever 'name' they give it, they all do similar things in slightly different ways, but ultimately the objective is so you can install more apps.
Oh and if you're partitioning for Desire, use 4EXT recovery or gparted, not clockworkmod recovery

[Q] Internal Memory question

So, I got my device s-off and rooted, was pretty excited when I had those stuff done.
But now,
Internal memory is still an issue, I read on xda like, removing the bundled or stock software comes with the phone won't make the internal memory get increased because those files are stored somewhere else that won't effect the total usable internal memory. Plus removing stock apps will stop using OTA updates.
So is there a trick that I can increase the internal memory of my phone? I already use the default save location setted to sd card, and moving apps to sd but it always leaves some files at internal memory.
I read somewhere like, I can make phone use my sd card's some part as internal memory, I saw a rom offering that but except that is there any program offering this without flashing rom?
And I have some knowledge about Linux, so I was wondering do I have a chance to use symlink command (symbolic link) to link my internal memory to sd card ?

Best way is to use a ROM with Darktremor Apps2SD preinstalled. I don't know whether it will work if you install it now.
The best alternative, in my opinion, is to format a partition of your SD card to ext3 with this guide and then use Link2SD.The partition can be as big as you want, but I believe that 500 MB should be enough.
It will earn you some space but not as much as the Darktremor Apps2SD will.

Thanks for the answer, I used the guide and Link2SD, but i am a bit confused here, I also use apps 2 sd program,
So for using less possible internal memory of my phone,
Should I install apps to phone memory and then link to sd card with link2sd
or
Install app in sd card (or move it with link2sd to sd card) then link?
Right now one of apps shown as Linked -> SD card. So is this the best scenario?
Because when I choose move to SD in Apps 2 SD, Link2SD says move to SD also, so it kinda like they conflict

To tell you the truth I'm not completely sure for what is better, but what I did was to first link all of them (application, dalvik & library if possible) and then move them to sd card with App2SD. I think there was a slight difference to the free space but nothing noticeable. Sorry, but I'm no expert, so everything I did was by trial and error!

Newb question regarding ext2 format for sdcard

Newb question, why format the sd card with ext2 or ext3 if the rom is still being put on the phone?

If you are partitioned, the speed will be vastly improved and your space will double. Every time you install an app, it goes to external storage instead of internal storage, thus giving you more space. It also keeps the program. From closing every time you exit. For example, if you close a game with the app on internal, it exits and closes the app from memory leaving any non-saved progress gone. When on external, it caches the progress leaving the game running while using the phone for other purposes.
So in the end, the partition is better than no partition. :thumbup:

gbdavidx said:
Newb question, why format the sd card with ext2 or ext3 if the rom is still being put on the phone?
Click to expand...
Click to collapse
The benefit of partitioning your sd card is it saves alot of internel space on your phone and using a htc evo,you will benefit tremendously,because the OG has very little memory to begin with,by this i mean it will move all of the apps/cache/delvik/temp files to your sd card,hence the sd ext.Alot of the OSes 3.5 sense/ICS/JB arent meant for the OG,they just take up way too much memory,so partitioning is the best thing to happen to the evo and all of the latest recoveries and roms are being built to be compatible with ext 4 and swap,with partitioning and a2sd combined,it gives you the needed internal memory for those memory hogs they call android operating systems,lol.