few memory - HD2 Android Q&A, Help & Troubleshooting and Genera

why i have after installing a rom only free 120 mb free memory on phone i made partition 250 mb

The rom you installed probably has /system/app and /system/framework moved to /data, hence the small data size.

Related

Why does desire builds take so much space

http://www.htc.com/www/product/desire/specification.html
ROM: 512 MB
Click to expand...
Click to collapse
http://www.htc.com/www/product/hd2/specification.html
ROM: 512 MB
Click to expand...
Click to collapse
Euro HD2 have same size of storage than Desire. Then how can we have such small amount of free storage after installing? Or desire also have only 180MB free after install? That sounds a bit too small for real android device.
What am i missing here?
Part of the problem is that "devs" are de-odexing apks and jars. While it's true that the system image is larger with the odexes (roughly about 20 MB), that space is soon used up, but on /data when the build first-boots and creates the dalvik-caches for system files (which don't need to be created in builds that are pre-odexed).
I'll give you an example. framework.jar (in /system/framework) is around 2.5-3 MB on a de-odexed system. The classes.dex inside it gets uncompressed to dalvik-cache, and uses an addiional 6 MB, for a total file of 8.5-9 MB.
On a regular, odexed system, framework.jar is around 30kb (since it doesn't contain a classes.dex inside) and the respective odex uses up 6 MB (and since it's already an odex, it doesn't have to be uncompressed to dalvik-cache). Total size for framework: 6.03 MB.
Now, for your question. Original desire builds are odexed, so they're about 20-40 MB smaller on a shipped device. You get about 220 MB free on a stock Desire.
On top of the de-odexing, something that costs space is that the devs write larger partition than necessary, but you can fix this when you flash your build by editing the flash.cfg and writing smaller partitions for all but userdata (that way you have more space available for apps), here's what I use:
Code:
boot ya|boot|ro filesize boot.img
system ya filesize system.img
cache ya 3M
userdata ya|asize|hr allsize
cache might be unnecessary now since 2.2. It's used for OTA updates (we don't care about those) and market cache, but since 2.2 market downloads are cached on SD if there's no space on cache, so that might be another 3 MB you can get back.
Plus my personal build is odexed, so I have (on TMOUS HD2) ~800 MB free on first boot.
jubeh said:
Part of the problem is that "devs" are de-odexing apks and jars. While it's true that the system image is larger with the odexes (roughly about 20 MB), that space is soon used up, but on /data when the build first-boots and creates the dalvik-caches for system files (which don't need to be created in builds that are pre-odexed).
I'll give you an example. framework.jar (in /system/framework) is around 2.5-3 MB on a de-odexed system. The classes.dex inside it gets uncompressed to dalvik-cache, and uses an addiional 6 MB, for a total file of 8.5-9 MB.
On a regular, odexed system, framework.jar is around 30kb (since it doesn't contain a classes.dex inside) and the respective odex uses up 6 MB (and since it's already an odex, it doesn't have to be uncompressed to dalvik-cache). Total size for framework: 6.03 MB.
Now, for your question. Original desire builds are odexed, so they're about 20-40 MB smaller on a shipped device. You get about 220 MB free on a stock Desire.
On top of the de-odexing, something that costs space is that the devs write larger partition than necessary, but you can fix this when you flash your build by editing the flash.cfg and writing smaller partitions for all but userdata (that way you have more space available for apps), here's what I use:
Code:
boot ya|boot|ro filesize boot.img
system ya filesize system.img
cache ya 3M
userdata ya|asize|hr allsize
cache might be unnecessary now since 2.2. It's used for OTA updates (we don't care about those) and market cache, but since 2.2 market downloads are cached on SD if there's no space on cache, so that might be another 3 MB you can get back.
Plus my personal build is odexed, so I have (on TMOUS HD2) ~800 MB free on first boot.
Click to expand...
Click to collapse
Might I ask what build you're using with 800Mb free?
Wow, thanks for the explanation. So what are the pros of de-odexed builds?
I will ask that here instead of starting new thread:
Is there a way to change treshold for "Low Disk Space" error message? According to the DiskSpace application, i have around 50MB of the free space, which is quite a lot when max is 180. But still i got Low Disk Space and i can't install any applications.
Friend have real Desire with 20MB of free space and he don't have that message.

Removing Bloatware

Due to the fact that I can't directly reply to the thread that was created because I don't have enough posts, I'm posting here looking for an answer.
I followed the advice in this post. The only difference is that I used Super Manager instead of Root Explorer to delete the files from /system/app/.
Here is the odd part, after finishing I rebooted and when I powered back up and checked my available memory, it didn't change at all. Naturally I went back in with Super Manager and checked for the files and they are not there. I also looked with Astro File Manager and the files were not in /system/app/. I don't understand that if I deleted the files, why didn't my available memory increase? That is the whole reason I removed.
Thanks,
Why do you need more space in system folder?...
Go in data folder and check dalvick and data folders for leftovers.
Sent from my S7 using Tapatalk
Removing the so-called "bloatware" won't free up app storage space.
The tablet uses different partitions to store different things. System applications are stored on a different partition than user-installed apps. They each have their own space, indepentantly of each other.
When I started this exercise in removing the "bloatware" from my S7, I had a little over 85 MB free from the 175 MB available. After removing the "bloatware" I didn't see a change. Over the weekend, I removed the battery from my S7 to check the version number. After starting the S7 again, I check the memory and I now have 101 MB free. The only change was to remove the "bloatware". After installing two more apps on the tablet and moving the .apk file to my Link2SD partition on the internal SD card, I now have 98.97 MB of available space.
For the other post about removing the cache, I just ran cachemate and now I have 105 MB of available space.
Removing the "bloatware" does have an effect on the available memory.
While I did restart my S7 after removing the "bloatware", I didn't remove the battery. I don't know what I had the difference, but by completely removing the battery I saw that I had more space available after removing the "bloatware".
Couldn't have been. All of the apps you deleted reside in /system/app. That's on a completely separate partition from /data.
/data is where apps you install from Market go. It's also the space listed under "Internal Tablet Storage".
/system is where the system core files (and any pre-bundled apps) reside. There is no way to see the space free/used without going into a root terminal and running "df -h"
There is no way deleting system applications freed any sort of space on your /data partition.
It would be like if you had two hard drives in your computer, labled C:\ and D:\. Why would deleting files from C:\ free space on D:\? It's the same concept.
Ok. I understand what you are saying. However, I'm just reporting what I see when I look under:
Internal Tablet Storage
Total Space = 175 MB
Available Space = 100 MB
After removing the .apk "bloatware" files from /system/apps the available space increased.
tedkitch said:
Ok. I understand what you are saying. However, I'm just reporting what I see when I look under:
Internal Tablet Storage
Total Space = 175 MB
Available Space = 100 MB
After removing the .apk "bloatware" files from /system/apps the available space increased.
Click to expand...
Click to collapse
he's just being hostile and doesn't understand...
the bloatware resides in /system... now some of those files are Maps.apk which is an outdated version, and when you update it to the newest version from the market it installs to /data...
now...
it says it is updated, but we still have the outdated version which is still in /system taking up INTERNAL space. removing that apk from within /system and rebooting will add that much more space to your internal and the maps will still be installed because they are updated and installed to /data.
if you want to be so high and mighty, think before you talk.
also... data is installed internally, hence why we have the a2sd or links2sd method.
joenilan said:
it says it is updated, but we still have the outdated version which is still in /system taking up INTERNAL space. removing that apk from within /system and rebooting will add that much more space to your internal and the maps will still be installed because they are updated and installed to /data.
if you want to be so high and mighty, think before you talk.
Click to expand...
Click to collapse
I think you need to think before you talk.
Space on /system is not (normally) accessible to the user to use for storage of any kind. It's reserved solely for the OS' system files to be stored.
I think this is where you all are getting confused. Yes, the entire storage (including the internal storage) is all on the same flash ROM chip. But, it's not all contiguous space. It's broken up into partitions, and changes you make to a single partition does not affect any of the other partitions.
I'm not TRYING to be hostile, and I understand more than you think I do. I understand the underlying Android OS' mounts, whereas it seems you do not.
If you had said "removing these apps keeps them from running and using up CPU cycles and ram" I wouldn't have an issue with it. But, saying they free up space for the user to install apps to is just plain wrong.

Ok how much free space do you have?

I have yet to unlock the bootloader and have decided to see what happens first. But i did root my play.
But as per the title, how much space is to little.
So the space i'm referring to is the 400 mb of internal storage.
I have remove alot of apps and ringtones to free up space. Well i can't seem to get more than 60 mb of free space on the internal flash drive.
So my question for everyone is have you been able to free up more space? and if so how did you do it.
Oh yeah, i have also moved all my apps to the sd card, well all the apps that thr app lets me.
Search & read my friend, this topic has been run over more times than a flat cat.
For starters any apps or data you remove from /system/ will not effect your internal storage, because it is a diffrent partition to the /data/ partition, the latter being your internal storage, i have 300 apps on my fone and just under 100mb and we do not get 400mb of internal storage, that is just the total, after a clean install you get about 230-240mb
Sent from my R800i using Tapatalk

[INFO] Xperia Neo partitions

Do Xperia Neo ownwers really have only 380 Mb to for their applications and other stuff? Not really, we have system partition of 312,5 Mb in size as well.
I've noticed there are other partitions on Xperia Neo.
Here are all partitions I have found on Xperia Neo.
/cache --> 225 Mb
/data --> 380 Mb
/dev --> 167,77 Mb 76 k used
/etc --> 312,5 Mb
/mnt/asec --> 167,09 Mb This partition houses secure information about for example apps you bought from Market. It might show as 0Kb used but check individual folders and you see each is made into separate partition with around 1-2Mb in size.
/mnt/obb --> 167,09 Mb
/mnt/secure/asec this is using your sdcard but showing only files ending with *.asec
/system --> 312,5 Mb
Total Mb size adding them all would be 1731,95.
That's not correct since:
/etc and /system are in fact 1 partition. Considering this, the size is 1419,45
/mnt/asec and /mnt/obb could be as well same partitions. If it's true then total size is 1252,36 Mb.
Apps that show partition information show max total space around 917 Mb. But they show info only about /cache, /data, /system and no other system specific partitions.
its written on the sony ericsson website that neo has Internal phone storage: 1GB
(up to 320MB free)
The truth of which I am trying to figure out seeing those numbers I've presented. So far for me it seems the exact size is 1,2 Gb.
Official information about 1 Gb RAM for example for PC is always inaccurate, it's more like 1,1 GB or 1,2GB.
Seems the same case here. It's more convenient to type 1Gb and since most users will never notice those extra 200 Mb used by system specific partitions then who cares...
Well I do.
This 252,36 MB extra means I have some more room to play around with seeing that not much is getting written there by system.
I've noticed the same thing on my xplay it would be really cool to be able to have at least 500mb free
Sent from my R800i using XDA App
You sure there's no symlinks inflating the numbers?
You have assume that /data --> 380 Mb, when it's up to 380Mb free, must have 128Mb free with 252Mb of apps installed, to recover use app2sd or similar.
I've moved as many apps to the sd card but there some that won't move and I'm left with 190Mb free and 205.3Mb after cache clearing
You sure there's no symlinks inflating the numbers?
Click to expand...
Click to collapse
If you read last lines of OP you notice I try to calculate out possible symlinks.
I've moved as many apps to the sd card but there some that won't move and I'm left with 190Mb free and 205.3Mb after cache clearing
Click to expand...
Click to collapse
That is fine or what? Those apps need to be somewhere anyway. Total space is 380 Mb and that's what matters.
i have to ask a thing
is normal that in "settings"--> "applications", i see only 335 mb of ram in total (not free) ?
but the phone should't have 512 mb?
where is the other ram?
maRRRco89 said:
i have to ask a thing
is normal that in "settings"--> "applications", i see only 335 mb of ram in total (not free) ?
but the phone should't have 512 mb?
where is the other ram?
Click to expand...
Click to collapse
Hello. Exact. The neo has 512 Mb of Ram but just around 320 are available for users (the rest is used by the system )

[Q] unusable internal memory

Hi, I am using MIUI with Android version 2.3.7. Everything is allright, but I only have 217 mb of internal memory in total. The MIUI ROM and other apss take up about 180 mb and although I have moved some apps to sd I now only have 40 mb available. It should have 512 mb internal memory. Why can't I see and use all of it? Is it possible that I didn't delete windows mobile or one of the other android roms I have used so far, though I am sure I have tried "clean install" a few times?
Dalvik cache & app data take up a lot of space too, you could move these to th SD ext partition to free up more internal memory. You will need a2sd installed I think to enable this.
Peace
Sent from my HD2
the 'available internal memory' figure only counts the data partition size.
so (for example) if your rom requires a 200 meg system partition, you would show..
512 minus 200 minus whatever cache size you flashed minus the boot and recovery partitions (lets guess 50 meg) so your available internal memory on a completely fresh install, no data or apps, would still only show a max of 262meg available.
Also, if you flash a system partition bigger than required, you dont get the extra space to use. So flash a 180meg rom onto a 250 meg system partition, and you lose 70meg, the system wont use it for anything.
samsamuel said:
the 'available internal memory' figure only counts the data partition size.
so (for example) if your rom requires a 200 meg system partition, you would show..
512 minus 200 minus whatever cache size you flashed minus the boot and recovery partitions (lets guess 50 meg) so your available internal memory on a completely fresh install, no data or apps, would still only show a max of 262meg available.
Also, if you flash a system partition bigger than required, you dont get the extra space to use. So flash a 180meg rom onto a 250 meg system partition, and you lose 70meg, the system wont use it for anything.
Click to expand...
Click to collapse
Thank you so much. My ROM itself is about 100 mb. How much data partition size should I actually spare for such a rom? Also could you please direct me to the post that tells me how to arrange the data partition size and do the rest of flashing my rom again? I would really like to have more available internal memory. Also I would be happy if you told me what ext 3 or ext 4, whatever it is called, is and if it has anything to do with internal memory.
If the rom is 100mb then you need a partion of at most 110 so if your using clk or magdlr..after you have wiped nand...partition it to 110 if possible or use 105 even cos you don't wanna be giving up wanted space..

Categories

Resources