Related
Can someone please tell me what the biggest differences between these 2? both advantages and disadvantages.
I have ext4, but I do not know anything about it; I have it b/c it's newer than ext3 and everyone else is having it, lol.
thanks
I upgraded from ext3 to ext4 a couple of weeks back and haven't had any issues. I believe you will get slightly better performance out of ext4, but I haven't noticed anything different. It's not like the set up from ext2 to ext3, which was a lot faster due to journaling.
Basically, it doesn't really make a difference, I'm sticking with ext4.
Yeah i have ext4 but i dont see much difference from 3
ext4 doesn't offer any advantage in this application. The dev's support it for the same reason YOU have selected it... because it is "newer". ext2 or ext3 may even be better since its (yes, I refer to them as the same thing since ext3 is just ext2+journal) been out for a lot longer and is extremely stable.
I've read that EXT4 supports delayed allocation/journalling so its not always writing to the SD card as often.
http://en.wikipedia.org/wiki/Ext4
I'm still on EXT3 myself but am planning to play with swap and other goodies when I get some more free time.
The makers of some Linux distributions (notably Fedora) will not let users format their boot partitions to ext4 on a fresh installation. There's a reason. They don't want a relatively new filesystem type in a production environment.
Those who use ext4 are not unlike the old Bugs Bunny cartoons where they're doing testing work in the bomb plant...with a hammer.
beartard said:
The makers of some Linux distributions (notably Fedora) will not let users format their boot partitions to ext4 on a fresh installation. There's a reason. They don't want a relatively new filesystem type in a production environment.
Those who use ext4 are not unlike the old Bugs Bunny cartoons where they're doing testing work in the bomb plant...with a hammer.
Click to expand...
Click to collapse
lol I'm so proud of myself cuz I've been testing bomb for the last month and still breathing lol lol lolz
beartard said:
The makers of some Linux distributions (notably Fedora) will not let users format their boot partitions to ext4 on a fresh installation. There's a reason. They don't want a relatively new filesystem type in a production environment.
Those who use ext4 are not unlike the old Bugs Bunny cartoons where they're doing testing work in the bomb plant...with a hammer.
Click to expand...
Click to collapse
Not correct.
In older versions of fedora, ext4 was not allowed in /boot because ext4 was not supported by GRUB -- the bootloader. Fedora 12 comes with a new version of GRUB that has been updated to support ext4.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
now onto serious anwer
Extents are introduced to replace the traditional block mapping scheme used by ext2/3 filesystems. An extent is a range of contiguous physical blocks, improving large file performance and reducing fragmentation. A single extent in ext4 can map up to 128MB of contiguous space with a 4KB block size.[1] There can be 4 extents stored in the Inode. When there are more than 4 extents to a file, the rest of the extents are indexed in an Htree.
The ext4 filesystem allows for pre-allocation of on-disk space for a file. The current methodology for this on most file systems is to write the file full of 0s to reserve the space when the file is created. This method would no longer be required for ext4; instead, a new fallocate() system call was added to the Linux kernel for use by filesystems, including ext4 and XFS, that have this capability. The space allocated for files such as these would be guaranteed and would likely be contiguous. This has applications for media streaming and databases.
Delayed allocation
Ext4 uses a filesystem performance technique called allocate-on-flush, also known as delayed allocation. It consists of delaying block allocation until the data is going to be written to the disk, unlike some other file systems, which may allocate the necessary blocks before that step. This improves performance and reduces fragmentation by improving block allocation decisions based on the actual file size.
Ext4 uses checksums in the journal to improve reliability, since the journal is one of the most used files of the disk. This feature has a side benefit; it can safely avoid a disk I/O wait during the journaling process, improving performance slightly. The technique of journal checksumming was inspired by a research paper from the University of Wisconsin titled IRON File Systems (specifically, section 6, called "transaction checksums").[7]
gridlock32404 said:
now onto serious anwer
Extents are introduced to replace the traditional block mapping scheme used by ext2/3 filesystems. An extent is a range of contiguous physical blocks, improving large file performance and reducing fragmentation. A single extent in ext4 can map up to 128MB of contiguous space with a 4KB block size.[1] There can be 4 extents stored in the Inode. When there are more than 4 extents to a file, the rest of the extents are indexed in an Htree.
The ext4 filesystem allows for pre-allocation of on-disk space for a file. The current methodology for this on most file systems is to write the file full of 0s to reserve the space when the file is created. This method would no longer be required for ext4; instead, a new fallocate() system call was added to the Linux kernel for use by filesystems, including ext4 and XFS, that have this capability. The space allocated for files such as these would be guaranteed and would likely be contiguous. This has applications for media streaming and databases.
Delayed allocation
Ext4 uses a filesystem performance technique called allocate-on-flush, also known as delayed allocation. It consists of delaying block allocation until the data is going to be written to the disk, unlike some other file systems, which may allocate the necessary blocks before that step. This improves performance and reduces fragmentation by improving block allocation decisions based on the actual file size.
Ext4 uses checksums in the journal to improve reliability, since the journal is one of the most used files of the disk. This feature has a side benefit; it can safely avoid a disk I/O wait during the journaling process, improving performance slightly. The technique of journal checksumming was inspired by a research paper from the University of Wisconsin titled IRON File Systems (specifically, section 6, called "transaction checksums").[7]
Click to expand...
Click to collapse
Nerd.......
Nah preme, it's called copy and paste from wikipedia
gridlock32404 said:
Nah preme, it's called copy and paste from wikipedia
Click to expand...
Click to collapse
I was just f'n with you anyways.
gridlock32404 said:
Nah preme, it's called copy and paste from wikipedia
Click to expand...
Click to collapse
Nah grid, it's called how to complete an essay in 2 minutes
AdrianK said:
Nah grid, it's called how to complete an essay in 2 minutes
Click to expand...
Click to collapse
And means he's a cheater cheater pumpkin eater.
So i can run newer jacheroski on EXT3
cj_fiasco said:
So i can run newer jacheroski on EXT3
Click to expand...
Click to collapse
Yeah, ext3 is best supported, ext2 is slower due to lack of journalling and ext4 is newer but not supported by all ROMs.
As we all know, most of our phones have at least a couple of bad blocks in the NAND memory. The biggest and most common problem because of this is that when you create a partition of 'x'MB, the actual partition will be 'x-something'MB. This is because partitioning does not account for bad blocks.
So if a ROM requires 150MB of /system partition (which you create - using HD2 Toolkit or cLK 1.5), you *might* end up with less than 150MB. ROM devs usually factor this in and give a room of at least 5 ~10 MB for installing additional stuff in /system as well as bad blocks. But you will have a problem if the 150 MB partition you create has enough bad blocks making it less than, in my example, 145 or 140 MB.
The most safest way I have seen to make sure you /system has enough space-
Extract you ROM's zip file, and check the size of the directory named system
Repartition your phone like you normally do
Boot to ClockWorkMod and format all partitions
Mount the /system partition in ClockWorkMod
Connect your phone to your computer, ensure you had ABD drivers installed
Head to QtADB and download the most appropriate version for you - there is one for Linux x86, Linux x64, Windows and Mac. Also download the required binary files for Linux, Windows or MacOS. Extract all QtADB zip as well as the binary zip to the same directory. Launch QtADB. On first launch, if it asks for the binaries, point it to the right directory
In QtADB, select the "Phone Info" icon. You will see something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you can see from the image, my /system is 195.31 MB. I had partitioned my NAND for 200 MB system partition, but am losing 4.69MB to bad blocks
If I am installing a ROM, I need to make sure the system directory in its zip file does not exceed this size, or increase the partition size accordingly.
Also, when flashing a ROM, you can refresh QtADB to see the /system partitioning filling up. Make sure the actual space in the system partition is 10 or 15 MB larger than the ROM's system directory. The most common symptom of an inadequate system partition is bootlooping, and other weird/ uncommon behavior.
Hope this little guide helps at least some of us. Happy Flashing
ph03n!x said:
As we all know, most of our phones have at least a couple of bad blocks in the NAND memory. The biggest and most common problem because of this is that when you create a partition of 'x'MB, the actual partition will be 'x-something'MB. This is because partitioning does not account for bad blocks.
So if a ROM requires 150MB of /system partition (which you create - using HD2 Toolkit or cLK 1.5), you *might* end up with less than 150MB. ROM devs usually factor this in and give a room of at least 5 ~10 MB for installing additional stuff in /system as well as bad blocks. But you will have a problem if the 150 MB partition you create has enough bad blocks making it less than, in my example, 145 or 140 MB.
The most safest way I have seen to make sure you /system has enough space-
Extract you ROM's zip file, and check the size of the directory named system
Repartition your phone like you normally do
Boot to ClockWorkMod and format all partitions
Mount the /system partition in ClockWorkMod
Connect your phone to your computer, ensure you had ABD drivers installed
Head to QtADB and download the most appropriate version for you - there is one for Linux x86, Linux x64, Windows and Mac. Also download the required binary files for Linux, Windows or MacOS. Extract all QtADB zip as well as the binary zip to the same directory. Launch QtADB. On first launch, if it asks for the binaries, point it to the right directory
In QtADB, select the "Phone Info" icon. You will see something like this:
View attachment 1081288
As you can see from the image, my /system is 195.31 MB. I had partitioned my NAND for 200 MB system partition, but am losing 4.69MB to bad blocks
If I am installing a ROM, I need to make sure the system directory in its zip file does not exceed this size, or increase the partition size accordingly.
Also, when flashing a ROM, you can refresh QtADB to see the /system partitioning filling up. Make sure the actual space in the system partition is 10 or 15 MB larger than the ROM's system directory. The most common symptom of an inadequate system partition is bootlooping, and other weird/ uncommon behavior.
Hope this little guide helps at least some of us. Happy Flashing
Click to expand...
Click to collapse
Thanks for this, I've been looking for a way to check something like this out. I don't have the time now though, but I might try it later depending again on time constraints. I feel that for now I'm OK since I've only had the phone since Jan 2011 and I used SD Android for quite a while before switching to NAND, but it never hurts to know things like this. Thus far though the recommended partition size has always worked for me and I've always seen 2-3Mb space free in the 'System ROM' setting in Titanium backup.
In fact, that gets me wondering can you literally just do step 1, then flash a partition size larger than needed (e.g. for a 150Mb ROM flash a 200Mb partition), calculate how much space you should have free (i.e. 50Mb in this case), check in Titanium Backup how much space you actually have free and subtract the latter from the first, giving you the free space? If this would work, it would save even more time.
Of course, I may be COMPLETELY misunderstanding what the 'System ROM' thing in Titanium Backup is, tbh I'm not into the technical side of things very much.
@Nigeldg- Titanium Backup is something I used to check the sizes earlier. But then, it's not quite accurate. My 200MB /system partition shows as 209MB in Titanium
I have never had any issues in using a bigger partition than required. I initially had a 445 MB as default when I was trying out a bunch of ROMs...
Swyped from my HTC HD2 (ICS 4.0.4)
ph03n!x said:
@Nigeldg- Titanium Backup is something I used to check the sizes earlier. But then, it's not quite accurate. My 200MB /system partition shows as 209MB in Titanium
I have never had any issues in using a bigger partition than required. I initially had a 445 MB as default when I was trying out a bunch of ROMs...
Swyped from my HTC HD2 (ICS 4.0.4)
Click to expand...
Click to collapse
Actually I see you're right, my 165mb partition reads as 173mb. Still, perhaps it's consistently 8-9mb over? Just a guess, although I would obviously need someone with a different partition size to confirm this
Nigeldg said:
Actually I see you're right, my 165mb partition reads as 173mb. Still, perhaps it's consistently 8-9mb over? Just a guess, although I would obviously need someone with a different partition size to confirm this
Click to expand...
Click to collapse
For a raw sizing, open terminal emulator (or ADB shell) and type df
Again, this wont count the bad blocks you have...
when you wantto flash a new rom, first resize the system partition with more 10M than the new rom needed... it is a simple method to solve the problem...
Good find ph03n!x !!! I just use root explorer to determine my partition sizes. Lucky, ive only had bad blocks in my userdata partition. (Knocks on wood) Hopefully i wont have anymore
ph03n!x said:
@Nigeldg- Titanium Backup is something I used to check the sizes earlier. But then, it's not quite accurate. My 200MB /system partition shows as 209MB in Titanium
I have never had any issues in using a bigger partition than required. I initially had a 445 MB as default when I was trying out a bunch of ROMs...
Swyped from my HTC HD2 (ICS 4.0.4)
Click to expand...
Click to collapse
I know this thread is a bit old now and generally I don't bring up an old thread again, but in Tytungs CM9 there was a short discussion about this and I was given a solution by agbommarito:
agbommarito said:
Titanium Backup has an option under GUI Preferences to change its interpretation of memory. If it is set for binary units, a kilobyte = 1024 bytes and Titanium will display MiB. If it is set for decimal units, a kilobyte is 1000 bytes and Titanium will display MB (without the little "i').
165 MiB (where a MiB is 1024x1024) = 173 MB (where a MB is 1000x1000).
Click to expand...
Click to collapse
So if anyone wanted to check their partition size, they CAN just use Titanium to do it
@nigeldg, I tried that and am getting 200MB, which is indeed my partition size- but it is not accounting for the bad block I have in my /system!
_
Swyped from my HTC HD2 (ICS 4.0.4)
ph03n!x said:
@nigeldg, I tried that and am getting 200MB, which is indeed my partition size- but it is not accounting for the bad block I have in my /system!
_
Swyped from my HTC HD2 (ICS 4.0.4)
Click to expand...
Click to collapse
Alright I get it now. Perhaps flashing a larger partition size, then seeing how much free space you should have in /system versus seeing how much space you actually have in /system would do the trick (basically a combination of the first thing I suggested a while back and the new solution as well). Of course, this wouldn't tell you how many bad blocks you have but the amount of space which is taken up should be sufficient data. Again, I'm not sure whether or not this would work but in theory I think it should.
Well, my point is to check the partition size before flashing a ROM, making sure the actual size on /system is sufficient- by checking the size of the system directory in the ROM's zip
_
Swyped from my HTC HD2 (ICS 4.0.4)
Hey out there, I could use your help. As you'll see by the screen shots on my nexus storage space is running low but I have only half the space used.
I've done a factory data reset that didn't do the trick
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can someone please help?
Sent from my Obsession
Disconnect from the computer and let the SD reload. See what you have, then. Also, you might want to put your music in the Cloud and the songs you want to listen to for the day/time, have them play offline...
jamerican413 said:
Disconnect from the computer and let the SD reload. See what you have, then. Also, you might want to put your music in the Cloud and the songs you want to listen to for the day/time, have them play offline...
Click to expand...
Click to collapse
Thanks - I'll give it a shot
Did it do the trick?
hullbay said:
Did it do the trick?
Click to expand...
Click to collapse
Unfortunately not - but it's all good, I did a factory restore and the storage space is back, just gotta copy files/flash rom again etc. I'm just glad I figured it out.
So you did a factory reset twice?
adamhlj said:
So you did a factory reset twice?
Click to expand...
Click to collapse
The first time I did a factory reset from settings>backup & reset and that didn't work.
2nd: I followed this method to return to factory stock: http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html
3rd: I used the nexus root toolkit found here: http://forum.xda-developers.com/showthread.php?t=1766475
-Good times :cyclops:
I am having the same issue.. Also I was wondering why there was 13.24 available when the internal memory has its own ~half gig of storage.. shouldn't the SD card storage have 16 gigs altogether?
Anyhow does anyone know how I could retrieve my extra storage space without restoring factory defaults?
Sent from my Nexus 7 using xda app-developers app
Deazul said:
I am having the same issue.. Also I was wondering why there was 13.24 available when the internal memory has its own ~half gig of storage.. shouldn't the SD card storage have 16 gigs altogether?
Anyhow does anyone know how I could retrieve my extra storage space without restoring factory defaults?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi All
13.24GB is normal (16GB formated will around 15.2GB usable, Android OS requires around 2GB) - You can get more space is you flash custom slim line ROM
Nexus 7 has 1GB of RAM - this is not storage, RAM is used to running Applications on Android
I having any similar issue with this too. when i copy a 5GB 720p mkv to Nexus 7 split over 2 x 2.5GB after watching and deleting the files Andriod does not reclaim the free space. A reboot of the Nexus 7 is required for Andriod to see the space again.
Sweet dude, thank you. I actually discovered several GB of reclaimed space after a reboot earlier today. Bonus: I got stickmount running so now I have another 8gb to play with on my flash drive with an OTG cable!!
Thanks again
-deazul
Sent from my Nexus 7 using xda app-developers app
toker_X1 said:
A reboot of the Nexus 7 is required for Andriod to see the space again.
Click to expand...
Click to collapse
Just grab SDrescan app to refresh the media database rather then reboot.
I'm having a similar problem with the 8GB version. Had been happily using it and installing a few games, then the other day attempted to install a rather large game (which was a huge play download rather than a smaller one that then downloads game data). It was a 1.3GB download and my device reckoned it had about 1.4GB of space.
The install failed and despite not installing, my device was then reporting only 270MB of space instead of the 1.4GB I had before.
I am now getting a message in the system bar telling me: "Storage space running out", even though the Storage Settings page tells me I've got about 270MB. But this means that certain apps have stopped working (gmail and gtalk), I can't install or update any apps from the play store anymore (I have even tried uninstalling a couple of things but that hasn't helped).
If I adb shell into the device and run df I get:
Code:
Filesystem Size Used Free Blksize
/dev 487M 32K 487M 4096
/mnt/asec 487M 0K 487M 4096
/mnt/obb 487M 0K 487M 4096
/system 639M 427M 212M 4096
/cache 436M 7M 428M 4096
/data 5G 5G 278M 4096
/storage/sdcard0 5G 5G 278M 4096
So the Android status message seems to be at odds with the actual storage space available. Plus I can't figure out where the extra 1GB+ I had before has gone.
Is there any way to fix this without resorting to a factory reset since I don't fancy having to start again. I wanted to ask google but the "Contact Us" link on their Nexus 7 support page is a bad link.
Dan
EDIT: My device is running completely unmodified/unrooted stock JB
See the attachment, it makes no sense.
The bar graph at the top suggests that I have about 25% free space, which is actually what I would expect since there was about 1.4GB free before things went wrong.
The available space listed at the bottom suggests that I only have 4.5% free space.
The messages tell me that I am running out and if I try and install anything it refuses which suggests I have 0% free space.
Is the Nexus 7 incapable of consistent maths?
Code:
df
Filesystem Size Used Free Blksize
/dev 486M 48K 486M 4096
/mnt/asec 486M 0K 486M 4096
/mnt/obb 486M 0K 486M 4096
/system 639M 306M 333M 4096
/cache 436M 71M 364M 4096
/data 13G 11G 1G 4096
I'm getting same "out of space" error now. got over 1.5gig free. Any idea's? I've cleared the database
It's really strange how the storage works out.
I have 16GB N7:
Total Space: 13.24GB
Apps: 1.97GB
Pictures, Videos: 2.25MB
Audio: 20.00KB
Downloads: 16.44MB
Available: 6.40GB
Really seems I should have more storage space then 6.40GB, I mean I'm using like 2GB total storage, no movie downloads, or music on the tablet. Anyone know whats happening?
My numbers don't add up also mine says 889mb for my apps but when I click it it says I'm using 3.9 GB I added it up and the storage doesn't add the cache space your apps uses for some reason at least after I got my calculator and did some math mine doesn't
Sent from my Nexus 7 using xda premium
If you made a cmw backup that could be the cause. That happened to me. Lost about a gig or so. Go to the clockwordmod folder and you should see two folders, backup and blobs. Cmw 6 changed some stuff up. Might wanna run a search on it but it is probably the blob folder in the clovkwordmod folder.
Sent from my Nexus 7 using xda premium
naveen94 said:
If you made a cmw backup that could be the cause. That happened to me. Lost about a gig or so. Go to the clockwordmod folder and you should see two folders, backup and blobs. Cmw 6 changed some stuff up. Might wanna run a search on it but it is probably the blob folder in the clovkwordmod folder.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Was about to post the same comment. If using Cwm you may loose a gig or more space not related to the actual backup file, that may not be reflected in the total free space for the SD drive. Also if you have down loaded the Transformers movie that will suck up an additional 2 gigs.
Sent from my Nexus 7 using Tapatalk 2
Well my Nexus 7 is completely unmodified, so no cwm and no root.
I had in fact downloaded the free Transformers film - that was accounted for in the Apps (app data & media content) section of the storage screen. Now that I've watched the film and deleted it I've taken another screenshot (see attached image). The report of free space has not really changed, but the bar graph at the top suggests I have plenty of room!
Having done some digging with the device mounted over MTP it seems that Android had removed the downloaded film from the library but had not physically deleted it from storage, so it still existed in Android/data/com.google.android.videos/files/Movies. Also the failed install of the large game had left a big file in Android/obb which had never been cleared up by the play store application after the failure.
Having deleted those things manually, the system now appears to be reporting the correct amount of storage available.
Google advertizes that I can get up to 32GB of internal memory on the Nexus 10.
I am thinking about getting this tablet, but it doesn't have a MicroSD card slot, so I need to know this:
How much of the internal 32GB can I actually use?
Does the ROM take up some of that space, and how much?
isaacwg said:
Google advertizes that I can get up to 32GB of internal memory on the Nexus 10.
I am thinking about getting this tablet, but it doesn't have a MicroSD card slot, so I need to know this:
How much of the internal 32GB can I actually use?
Does the ROM take up some of that space, and how much?
Click to expand...
Click to collapse
29.71 GB of free space + you can get more via usb otg.
Not bad...
lKBZl said:
29.71 GB of free space + you can get more via usb otg.
Click to expand...
Click to collapse
Well, that's not too bad. And USB OTG looks quite interesting.
Thanks for the quick reply.
isaacwg said:
Well, that's not too bad. And USB OTG looks quite interesting.
Thanks for the quick reply.
Click to expand...
Click to collapse
I ordered a USB OTG from Amazon but it's coming from China is there a USA source?
This may help you...
ClutchKargo said:
I ordered a USB OTG from Amazon but it's coming from China is there a USA source?
Click to expand...
Click to collapse
On Amazon's website, when looking at a product, under the "add to cart" box, there is another box labeled "More Buying Choices".
That is probably what you want.
So what about the ROM?
OK, here is one thing that is not quite clear to me.
lKBZl, you said that the Nexus 10 has 29.71 GB of free space, but where is the ROM stored?
Am I right in assuming the ROM is stored on a separate partition, and the usable partition is 32GB?
So wouldn't that make the internal memory's real capacity larger than 32GB?
16gig
What about 16gig version ?
Ashirmittal said:
What about 16gig version ?
Click to expand...
Click to collapse
13.05gb on my 16gig, but I have an USB otg so no worries for me as I have plenty micro SD cards for storage.
Sent from my Nexus 10 using XDA Premium HD app
isaacwg said:
OK, here is one thing that is not quite clear to me.
lKBZl, you said that the Nexus 10 has 29.71 GB of free space, but where is the ROM stored?
Am I right in assuming the ROM is stored on a separate partition, and the usable partition is 32GB?
So wouldn't that make the internal memory's real capacity larger than 32GB?
Click to expand...
Click to collapse
32 gb is the total size of the storage capacity.
29.71gb is what is left for you to use as you wish.
Of the 3 or so gb missing, part of that is the os partition (/system) that contains the rom, kernel, etc.
And a smaller portion of that is strictly from the format process, small files that allow the memory to work.
trickster2369 said:
32 gb is the total size of the storage capacity.
29.71gb is what is left for you to use as you wish.
Of the 3 or so gb missing, part of that is the os partition (/system) that contains the rom, kernel, etc.
And a smaller portion of that is strictly from the format process, small files that allow the memory to work.
Click to expand...
Click to collapse
OK, thanks. That clears things up for me.
isaacwg said:
OK, thanks. That clears things up for me.
Click to expand...
Click to collapse
Lol I though you'd have understood that with the space left from the 29,71 to 32, it means that there is rom and etc.
If you guys want to buy an otg adapter, I recommend not to buy a cable like this: http://www.amazon.com/T-Flash-Adapt..._2?ie=UTF8&qid=1357413912&sr=8-2&keywords=otg
since then you won't be able to use a pendrive and a headphones. Something like this is better (in my opinion):
http://www.amazon.com/SANOXY-Micro-...F8&qid=1357413953&sr=8-7&keywords=otg+adapter
I looked at afew of the otg cables when I ordered my case, but none of them get any really good reviews. Maybe I am to picky dunno I will look to see if I can find any around where I live.
Can someone with a Nexus 10 tell me how much total space is on the /system partition, how much on the /data partition and how much on the mnt/sdcard partition. Also of which how much of that is available on a clean phone on each partition. Thanks
Gizmotech said:
Can someone with a Nexus 10 tell me how much total space is on the /system partition, how much on the /data partition and how much on the mnt/sdcard partition. Also of which how much of that is available on a clean phone on each partition. Thanks
Click to expand...
Click to collapse
Total values are what you're looking for.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks. And this is for a clean rom with nothing installed yet right?
It looks like /data and /sdcard are not separate partitions instead directories on the same partition unless you have binded the 2 directories Can someone confirm this please?
I'm a little late to the party but a 32GB once formated usually lose ~7% once formated as FAT/NTFS.
EXT4 should probavbly be no difference.
MB
->
300GB=279GB
320GB=297GB
400GB=372GB
500GB=465GB
1TB=0.931TB
2TB=1.86TB
3TB=279TB
->
PB
So the 32GB without any files* should have 29.7GB
*No OS or boot files etc.
It's not exactly 7% but it's close and easier to calculate than the "1024^1000=banana/shoe+cat=value".
Thank you but I was more concerned with the partition sizes as if /system partition is full, it doesn't matter how much space you have available in /data or /sdcard, it won't allow to install apps or games. I can't understand why they didn't have one partition with directories instead of partitions. That way we wouldn't have issues such as free space on one directory/partition and full up on another. I think in this sense, the iphone storage management is better.
Gizmotech said:
Thank you but I was more concerned with the partition sizes as if /system partition is full, it doesn't matter how much space you have available in /data or /sdcard, it won't allow to install apps or games. I can't understand why they didn't have one partition with directories instead of partitions. That way we wouldn't have issues such as free space on one directory/partition and full up on another. I think in this sense, the iphone storage management is better.
Click to expand...
Click to collapse
Apps (end user installed) aren't stored in the /system partition the OS is. Apps go in /data.. It would be insanely hard, and nearly impossible to fill up the /system partition.
The only phone I know (probably more) that has ever ran out of useful /system space is the Nexus One which is the reason Google stopped upgrading it because ICS wouldn't fit on the /system partition. End users got crafty though and figured out a way around the limitation by crafty partitioning magic with the Micro SDCard slot.
Yes, but the Nexus 10 does not have an SD Card slot so there won't be any other way of expanding storage once the internal storage fills up. But I see what you mean about the /system partition.
Could never get my head around this Android partitions. So am I correct to say the APK and App data are stored in the /data partition? And Game that require additional download able content is stored in the /Sdcard partition?
Now my question is, is the /data partition and /sdcard partition two separate partitions or two directories on a single partition on the nexus 10? The reason why I am asking is because if you look at the storage info of my phone (screenshot below) /data partitiom and /sdcard partition are showing different storage capacity and usage whereas your nexus 10 shows those two to have identical capacity and usage.
My concern is if one partition is full up, and you may have useless space on the other partition where as if they were directories, either they will share the space on demand. Not sure if I am explaining it correctly but for example I have a Galaxy Ace 2 which if I was to fill up the /sdcard partition, and have a adequately free /data partition, then often that free space is useless for some apps as it requires available space on the /sdcard partition. Now if they weren't partitions and instead directories, which I think the configuration is on the nexus 10, it would still show available space as both directories combined would make one partition. Which would then leave me to wonder why didn't they do the same for my Galaxy Ace 2
Ignore sdcard 2nd part, this is created on removable sdcard for purposes of Link2SD app.
Gizmotech said:
Yes, but the Nexus 10 does not have an SD Card slot so there won't be any other way of expanding storage once the internal storage fills up. But I see what you mean about the /system partition.
Could never get my head around this Android partitions. So am I correct to say the APK and App data are stored in the /data partition? And Game that require additional download able content is stored in the /Sdcard partition?
Now my question is, is the /data partition and /sdcard partition two separate partitions or two directories on a single partition on the nexus 10? The reason why I am asking is if one partition is full up, and you may have useless space on the other partition where as if they were directories, either they will share the space on demand. Not sure if I am explaining it correctly but for example I have a Galaxy Ace 2 which if I was to fill up the /sdcard partition, and have a adequately free /data partition, then often that free space is useless for some apps as it requires available space on the /sdcard partition. Now if they weren't partitions and instead directories, it would still show available space as both directories combined would make one partition.
Click to expand...
Click to collapse
They are essentially in the simplest terms exactly as you described. Two folders pointing to the same partition. That is why you can wipe your "sdcard" but all your apps remain intact in /data even though it's the same partition.
The reason your Galaxy Ace is like that is because you have a legit removable SDCard storage and it isn't part of the internal storage.. This complication in partitions w/ real sdcards is why Google refuses to put SDCard slots on any of their devices.
Internal Memory Repartition
Hey guys, after a very long time I show you the way to repartition your internal memory (EMMC).
You can modify partitions as you want, increase data partition to install more apps, increase internal storage for media files...
It's based on a little Linux binary called Parted, it's a part of CWM/TWRP recovery ramdisk.
This means that you can repartition in any recovery of any 4.2/4.3/4.4 ROM.
==========WARNING==========
Operations on EMMC partitions could be EXTREMELY DANGEROUS if you don't understand well what you do.
If you touch wrong partitions (CSPSA, EFS, SBLs...) you can lose your IMEI or hardbrick your device (in this case only JTAG can save you) so...
READ CAREFULLY!!!!!
Responsibility is all yours, but if you follow well this guide you will not risk anything.
Stock partition table is designed to be used in stock ROM, since it uses preload partition to store some system apps and needs bigger system (ROM is heavier than CM-based ones) and bigger cache partitions (more system apps=more dalvik-cache).
This mod is compatible with any ROM except stock and stock-based.
This is the stock partition table:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can touch ONLY:
Kernel2
SYSTEM
DATAFS
CACHEFS
HIDDEN
FOTA
UMS
Kernel2 is the backup of stock kernel, we don't need it.
SYSTEM is the /system partition (where the ROM is installed/stored).
DATAFS is /data partition (default 1.97 GB where are stored installed apps, Android settings, contacts, messages... User data).
CACHEFS is /cache partition (art/dalvik-cache is stored here, together with recovery logs/temporary files. In stock ROM here is stored also CSC. If you repartition to the minimum (at least 5 MB needed for recovery) you need to put dalvik.vm.dexopt.data-only=1 flag in system/build.prop
HIDDEN is /preload partition (some Samsung TouchWiz system apps are stored here and symlinked with /system/app. This is a swap partition on MIUI v5, CM10.2 and all CM11/Omni 4.4 builds (these 4.4 before 15 June), also every custom ROM based on Canjica device tree 4.3/4.4 (always before 15 June), resize it to the minimum (128 KB to format it as EXT2).
FOTA is Firmware Over The Air, so is needed to get OTA updates while on stock ROM, can be directly deleted.
UMS is the internal storage (3.96 GB one), you can repartition this to have less/more space, or repartition to the minimum (8 MB or less, you will need to swap internal/external storages).
Parted commands useful for us:
rm (to delete a partition)
mkpart primary (to make a partition)
format (to format a partition, only in ext2)
name (to rename a partition)
For an extended list/explanation of commands, type "help" without quotes
Let's go!
First make a nandroid backup of your current ROM, to be restored after repartition
If you touch UMS you will lose all the content of /sdcard (internal storage), so make a backup first!
You need a Linux distro or Windows with ADB configured.
Reboot device in recovery and connect to USB, then open ADB and write:
Code:
adb shell
parted /dev/block/mmcblk0
You can choose to display partitions as Gigabytes, Megabytes, Kilobytes (suggested), or Bytes by "unit **" command, where ** can be gb/mb/kb or b
Now type "print" to display partition table.
Parted create new partitions by following "Number", for example SYSTEM is 3, CACHEFS is 4 and DATAFS is 5 (for other partitions is the same), so when you create new partitions, you need to make them in order!! For example:
SYSTEM is 3 and its size is from 105906KB to 747635KB
CACHEFS is 4 and its size is from 2895118KB to 3215983KB
DATAFS is 5 and its size is from 747635KB to 2895118KB
The "end" of a partition is the "start" of the next partition
As you can see, DATAFS is between SYSTEM and CACHEFS. This means that after you create SYSTEM, you need to calculate new DATAFS size that you want and then first create CACHEFS (at the end of calculated DATAFS size) then create DATAFS from the end of SYSTEM to the start of CACHEFS.
To understand more:
We will resize now CACHEFS from 320864 KB to 5000 KB gaining 315864 KB for DATAFS:
Unmount /cache from recovery first!
Code:
rm 4 (to delete CACHEFS)
rm 5 (to delete DATAFS)
calculate now the new size of DATAFS, in this case add 315864 KB to DATAFS end: 2895118+315864=3210982 KB
calculate now the new end of CACHEFS, in this case add 5000 KB to 3210982 KB: 3210982+5000=3260982 KB
mkpart primary 3210982 (end of DATAFS and start of CACHEFS) 3260982 (end of CACHEFS, start of the next partition)
Now we made a new partition, its number is 4. Do: name 4 CACHEFS
It's time to make new DATAFS partition: from the end of SYSTEM to the start of CACHEFS
mkpart primary 747635 (end of SYSTEM and start of DATAFS) 3210982 (end of DATAFS and start of CACHEFS)
New partition has number 5, name it DATAFS by name 5 DATAFS
Basically the method is this, you can apply it to partitions listed above.
Remember to reboot recovery, go in Mounts and storage then (depending on what partitions you touched in Parted, excluding /preload) do the appropriate formats after repartition. Now you're ready to restore your nandroid backup (needs to have less size than new partitions) or install a ROM.
I suggest an useful program to check partition size on Android, Partition Table
If you touch HIDDEN partition and you are on 4.2 ROM or 4.4 builds after 15 June:
Code:
format
y
9
ext2
If you repartition UMS to the minimum, you will need to swap internal and external storages (MicroSD card will be the new internal storage):
On 4.2 open system/etc/vold.fstab and replace the content with this:
Code:
# MicroSD as internal storage
dev_mount sdcard0 /storage/sdcard0 auto /devices/sdi0/mmc_host/mmc1/mmc1
# UMS as external storage
dev_mount sdcard1 /storage/sdcard1 8 /devices/sdi2/mmc_host/mmc0/mmc0 nonremovable,encryptable
# usbdisk
dev_mount usbdisk0 /storage/usbdisk0 auto /devices/platform/msm_hsusb_host.0
On 4.3 ROMs open system/build.prop and add these lines at the end of the file:
Code:
persist.sys.vold.switchexternal=1
ro.vold.switchablepair=/storage/sdcard0,/storage/sdcard1
On 4.4 ROMs just open NovaThor Settings and enable "Swap Storages"
To restore original partition table flash stock ROM through Odin with "Repartition" enabled and correct PIT file for your model, in attachment (extract zip), soon CHN pits too
I know that it's difficult to understand well the first times, but think at me that I developed this method, a lot of testing and bricks on bricks
If you found this useful, you can support me at least by pressing "Thanks" or considering to offer me a beer, a coffee... Any kind of support will be very appreciated
Reserved for "The PIT Zone" (soon available!)
Reserved
Another reserved just in case!!
So, I want to shrink UMS (let's say by 1GB) and use it in DATAFS.
What would be the command sequence?
Thank you,
Tasos
tasosf said:
So, I want to shrink UMS (let's say by 1GB) and use it in DATAFS.
What would be the command sequence?
Thank you,
Tasos
Click to expand...
Click to collapse
All what you should know it's wrote in the OP.
You can make our way... rm anything after Kernel2, calculate datafs+1024MB more and make again all partitions, name and format them. Read again and well the OP for clarifications, it's all wrote there
Inviato dal mio GT-I9505
I didnt found any info about it in OP so i ask:
Every partition made using this guide will be formatted as ext2? Ext2 is worse than ext4 so probably it will affect performance, am i right about it?
Command "format" didnt work for me
Instead i used "mkfs <number> ext2" (however it asks about number and filesystem later) and i think "mkpartfs primary ext2 <start> <end>" could be the easiest as it create partition and format it in the same moment so its not needed to remember later
ch3mn3y said:
Command "format" didnt work for me
Instead i used "mkfs <number> ext2" (however it asks about number and filesystem later) and i think "mkpartfs primary ext2 <start> <end>" could be the easiest as it create partition and format it in the same moment so its not needed to remember later
Click to expand...
Click to collapse
Format didn't work for me either. I formatted everything through TWRP to ext4.
So, this method works! I now have 3GB for data so to have all the apps installed in the internal storage and not the internal sd card (ums). This way all apps are faster because ums is formatted as fat 32 in order to be recognised on Windows.
One tricky thing was that you have to mkpart from low numbers to high, regardless if you leave for a moment organ intermediate megabytes. The system always gives the next available number to the partition you make. It may not make sense how I try to explain it, but keep it in mind when you try it.
Sent from my GT-I9070 using XDA Free mobile app
I do exactly opposite thing as made smaller DATAFS, SYSTEM and CACHEFS to have bigger UMS. Its googd that Kernel2, HIDDEN and Fota are after "more" important partitions, so we can get rid of them and get lot of space
tasosf said:
The system always gives the next available number to the partition you make. It may not make sense how I try to explain it, but keep it in mind when you try it.
Click to expand...
Click to collapse
Yep, its important to not make mistakes, coz who wants to do something few times?
ch3mn3y said:
I do exactly opposite thing as made smaller DATAFS, SYSTEM and CACHEFS to have bigger UMS. Its googd that Kernel2, HIDDEN and Fota are after "more" important partitions, so we can get rid of them and get lot of space
Click to expand...
Click to collapse
How come you want to have bigger UMS? Not all apps can be installed there and DATAFS gets full very easily. Also, it's fat32 which creates some problems by itself.
Sent from my GT-I9070 using XDA Free mobile app
I just dont use this phone as my primary and as i have xplay for games i dont need to have lots of apps on it. Additionaly i have only 4gb sdcard for it, so my internal memory is now bigger than external
Sent using TF300T - CyanogenMod 11.0/GRIMLOCK (F2FS)
i'd really like to repartition my phone's memory but i fear i'm gonna screw everything up
i see a coming soon "pit zone" in the second post, does that mean that there is an automatic way to repartition the internal memory without directly using commands?
If u knows how to make pit file after repartitioning its probably possible to use odin to repartition
Sent using GT-i9070 - VanirAOSP
You need to use "format" command in ext2 only for HIDDEN partition that it's unneeded on custom ROMs.
For other partitions (SYSTEM, CACHEFS, DATAFS) format through recovery mode (automatically formatted in ext4), and for UMS through Android.
Yes, the PIT zone will have PIT files ready to be flashed to autorepartition along with a kernel that brings you CWM recovery to install/restore your ROM after repartition.
Inviato dal mio GT-I9505
AntaresOne said:
You need to use "format" command in ext2 only for HIDDEN partition that it's unneeded on custom ROMs.
For other partitions (SYSTEM, CACHEFS, DATAFS) format through recovery mode (automatically formatted in ext4), and for UMS through Android.
Yes, the PIT zone will have PIT files ready to be flashed to autorepartition along with a kernel that brings you CWM recovery to install/restore your ROM after repartition.
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
i will definitely wait for the pit files then all i'm looking for is to get rid of those useless partitions like FOTA, Kernel2 etc. just to have more space on the internal memory for apps
TheSteve87 said:
i will definitely wait for the pit files then all i'm looking for is to get rid of those useless partitions like FOTA, Kernel2 etc. just to have more space on the internal memory for apps
Click to expand...
Click to collapse
Completely agree mate. Also HIDDEN, you don't need it on CM/CM-based custom ROMs
Inviato dal mio GT-I9505
I really have to say this guide is just A-W-E-S-O-M-E
The process is not that easy but very well explained
A complicated by well explained method for partition........But i am a bit afraid to use .... Can u help out with the step for my issue...?
My Phone: S Advance
(Rooted with the help of http://forum.xda-developers.com/showthread.php?t=2087424)
RAM= 768 MB RAM,
ROM= 2 GB //*Note phone shows this as device storage, Pl correct if I am wrong*//
Internal=16 GB (user available=11.31 GB), //*Note phone shows this as USB storage, Pl correct if I am wrong*//
external micro SD card = Nil
I want to increase the RAM Or ROM so that my mobile should not lags/hangs
I feel that mobile is slow mainly due to less RAM......pl correct if I am wrong
I want to use the the 1GB/2GB/3GB/4GB out of Internal 16 GB to increase the size of ROM from 2GB to 3GB/4GB or RAM from 768 MB to 1GB/2GB/3GB/4GB more.....
Pl help me out with the specific steps.....
Thanks a lot @AntaresOne
@anil.xda
Yes, just 768 MB of RAM is one of the biggest performance limiting factors of this phone but sadly you can't just "increase it". You'll have to use something like a zRAM or a SWAP script. But this is just a workaround - and it too has some drawbacks I think.
Sent from my GT-I9070