Hi,
someone with the firmware JM6 can check the size of the folder "cache"? I have JK5 and i'm considering to update the firmware if they have rised the size of the cache folder over the 30mb cap.
Thank you.
Related
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.
According to http://forum.xda-developers.com/report.php?p=12847978
LG GT540 is equipped with 512Mb ROM which is divided into boot partition(5 MB), system partition(245 MB), userdata partition(138 MB) and cache partition (64 MB).
I did checked out data2system and Mur4ik's KDZ that repartitions.
My quesion is, has anyone tried to move the cache partition to SD and use the internal memory for cache to store data? If you add a 64MB to the already hacked up 234MB, it could be 298MB and we'd never need app2sd or link2sd.
I don't think cache really needs to be on the phone. They are just temporary files like downloaded market apks and email attachments.
THC HD2 How 170MB system partition and at least 2MB cache partition with HD2ToolKit4.2.0.1?
Step bay step?
On left click 170, below that enter 2 in cache box, click repartition.
Cabron
Dasis said:
THC HD2 How 170MB system partition and at least 2MB cache partition with HD2ToolKit4.2.0.1?
Step bay step?
Click to expand...
Click to collapse
eiy seems like AOKP but using HD2Toolkit, min. for cache is 5mb, try the link below it could give you an idea
Installations:
Please use at least 170MB system partition and at least 2MB cache partition.
Please refer to ksubedi's HD2 NAND Toolkit and/or mskip's guide.
Cache partition (/dev/block/mtdblock4) is only mounted and used by CWM.
Cache partition size is not important because the data partition (/dev/block/mtdblock5) is used as the cache space when running Android.
If your HD2 has bad NAND blocks, you may need larger partitions.
Wipe
Wipe Data/Factory Reset while doing a fresh install. (Optional: also delete /sdcard/Android folder or format your SD card if you have any strange issue.)
Advanced -> Wipe Dalvik Cache while upgrading from an old version and wanting to retain data.
Flash this ROM.
I click custom and below that enter 2 in cache box, click repartition. Show new table "What do you want the custom partition size to be 5-445 MB allowed. I write 170 click OK.
I give table sorry chase size must be 5 to 45MB.
Where is I did mistake ?
samsamuel said:
On left click 170, below that enter 2 in cache box, click repartition.
Click to expand...
Click to collapse
raziel024 said:
Cabron
Click to expand...
Click to collapse
You haven't helped in any way, thats rude. Cabron.
Dasis said:
Installations:
Please use at least 170MB system partition and at least 2MB cache partition.
Please refer to ksubedi's HD2 NAND Toolkit and/or mskip's guide.
Cache partition (/dev/block/mtdblock4) is only mounted and used by CWM.
Cache partition size is not important because the data partition (/dev/block/mtdblock5) is used as the cache space when running Android.
If your HD2 has bad NAND blocks, you may need larger partitions.
Wipe
Wipe Data/Factory Reset while doing a fresh install. (Optional: also delete /sdcard/Android folder or format your SD card if you have any strange issue.)
Advanced -> Wipe Dalvik Cache while upgrading from an old version and wanting to retain data.
Flash this ROM.
I click custom and below that enter 2 in cache box, click repartition. Show new table "What do you want the custom partition size to be 5-445 MB allowed. I write 170 click OK.
I give table sorry chase size must be 5 to 45MB.
Where is I did mistake ?
Click to expand...
Click to collapse
1 -In the main HD2 android NAND toolkit window, look left for "Choose system partition size(MAGLDR)" and select "CUSTOM"
2 -Below this window change "cache size", but smallest possible is 5MB. It doesn't matter if it's bigger, won't give trouble.
3-after those step choose "Repartition" button below 'Functions' and type desired (4) system partition size.
Have fun.
Dasis said:
I click custom and below that enter 2 in cache box, click repartition. Show new table "What do you want the custom partition size to be 5-445 MB allowed. I write 170 click OK.
I give table sorry chase size must be 5 to 45MB.
Where is I did mistake ?
Click to expand...
Click to collapse
retsam88 said:
2 -Below this window change "cache size", but smallest possible is 5MB. It doesn't matter if it's bigger, won't give trouble.
Click to expand...
Click to collapse
as retsam88 said, it deoesnt matter the cache size, most people leave it at 5, some roms say 45, (but i haven't seen that for a while).
As far as i know, (i've read it once or twice) on most roms, only recovery uses the cache partition.
misc ya 1M
boot yboot|ro 5M or 6M // According to their Recovery
system ya 150M // Minimal Installation
system ya 240M // Full Installation
system ya 150M - 275M // Custom Installation
cache ya 2M
userdata ya|asize|hr allsize
if you have Bad Sectors, please add 5MB more, to System Partition
I like to do this partition. What do i have to make it work with hd2toolkit ? Thanks
saigon66 said:
What do i have to make it work with hd2toolkit ? Thanks
Click to expand...
Click to collapse
you cant because the toolkit writes a new flash.cfg each time when you choose custom, or uses an .nbh when you choose a preselected size.
You should find the daf.exe flash version of cwm, and when you extract it into a folder you will find one file called flash.cfg, , open that in notepad you will see a list like teh one you posted, , edit the numbers, save it, then run daf.exe with teh phone in usb flasher mode.
Hello all,
After wiping my N7 and reinstalling stock 4.3 on my 16GB Wifi N7, I noticed that my storage is only 6.02GB total. Where did my other ~8GB go? I'm tried multiple times now to fully wipe and reinstall stock (even going back to 4.2.1 stock as well).
Any help would be very much appreciated.
Resolved!!
Found my issue:
I was using the excellent toolkit by WugFresh (v1.7.5) to push my stock images, and I had been forcing it push due to a previous error I had. This was causing my incorrect partition sizes. After pushing stock once, I unchecked the force option and pushed again. This time, the partitions came up proper.
When in panic, when in doubt: run in circles; scream and shout!
The simpliest solution is: in recovery do a wipe data/cache
Your tablet size is 8Gb ?
ROM = 512Mb
/dev directory (DON'T DELETE ! !!!!) = 1Gb
Other sys directory = 512Mb
It's normal, try to flash a stock ROM, download firmware package from Google Nexus Factory Image page (http://developers.google.com site), extract archive, connect tablet on fastboot to PC and launch "flash-all.bat"
Been there...
bigsee said:
The simpliest solution is: in recovery do a wipe data/cache
Click to expand...
Click to collapse
I did try that, and all it did was wipe the (then) ~6GB partition, but it didn't reset the size. Good thought, though.
Galaxy_Ace_Love said:
Your tablet size is 8Gb ?
ROM = 512Mb
/dev directory (DON'T DELETE ! !!!!) = 1Gb
Other sys directory = 512Mb
It's normal, try to flash a stock ROM, download firmware package from Google Nexus Factory Image page (http://developers.google.com site), extract archive, connect tablet on fastboot to PC and launch "flash-all.bat"
Click to expand...
Click to collapse
I wish I remembered to take a screenshot at the time. I've fixed the issue now, but I was definitely a wee bit panicked when I initially saw the storage size. I did try to go back to stock, but that's when I saw the storage "loss".
I am using Hongkong version of SM-N9005, everything worked just fine earlier, but recently after I flashed stock NB3 the total amount of internal storage I could use cut down to about 28GB. Then I tried XNOTE v10 and official CM11 as well, but the internal memory kept getting smaller and smaller after every flash as I could see it when I attached my phone to my computer. I tried factory reset in the ROM and also wipes in CMW recovery, but neither seems to be working. And I found out that Storage→System memory took up a space about 6.5G.
Does anyone have an idea about this? How should I wipe correctly and get my memory back? Thanks in advance.
When flashing in cwm I usually wipe in mounts and storage first. Research which ones to wipe...as I cant remeber which ones exactly. Things like format cache...format system...format sdcard(but the internal sd card - what it is named depends on which recovery is flashed)...just remeber this will wipe alk ur internal data like game saves, game data, local pictures etcetc...but should clear the excess storage being used.
Example...if you flash CM11 it uses a seperate sub-directory as main storage...and reverting back to stock changes to normal but the CM11 directory remains...something similar to sdcard/0/ ...soooo....if you are on stock now...use a file manager and if you have a folder named '0' ypu can usually delete what's in there...but the folder itself remains unless u change write permissions or formate ur internal storage.
Sent from my SM-N9005 using XDA Premium 4 mobile app
ZH_Ray said:
I am using Hongkong version of SM-N9005, everything worked just fine earlier, but recently after I flashed stock NB3 the total amount of internal storage I could use cut down to about 28GB...
Click to expand...
Click to collapse
It is not uncommon for stock ROMs released by Samsung to come with a new partitioning scheme to make slightly more space in certain partitions. In this regard the HK N9005 was already known to have a system partition that was smaller than the EU N9005 (which resulted in some of the problems seen when the first XEO 4.4.2 leak was attempted on HK 9005).
"fastboot flash userdata userdata_64g.img"
xclub_101 said:
It is not uncommon for stock ROMs released by Samsung to come with a new partitioning scheme to make slightly more space in certain partitions. In this regard the HK N9005 was already known to have a system partition that was smaller than the EU N9005 (which resulted in some of the problems seen when the first XEO 4.4.2 leak was attempted on HK 9005).
Click to expand...
Click to collapse
Fix partition table with this:
http://www.androidheadlines.com/2014/07/android-flash-oneplus-one-stock-cyanogenmod-11s.html