Why in Technical Specifications of the Inspire 4G say that is Internal memory storage 4 GB internal memory and the cellphone say me that is 1.21 GB in the Titanium Backup APP????????????????????????????????????????????????????
Its 4gb total. But only about 1gb is user accessible. There is an old thread about this where someone explained this in much better detail Ill see if I can find it
no hay de queso no mas de papa
i think its because you didnt add enough ?? to your confusion
ever wondered where your ROM resides? a rom is more than just /system. the partitions you DONT see are:
/data
/cache
/devlog
and a few more i am forgetting at the moment
Thanks for clarify my question. and sorry if it was before I don't found it :/
It also depends on how the NAND is setup. Certain partitions are considered more important and have more bytes allocated error correction and bad block recovery. Here's a document I found some time ago that explains it in excruciating detail:
http://tjworld.net/wiki/Android/HTC/EMMC/UnderstandingUserCapacity
Related
I was reading in the desire forums and saw this thread.
[DEV][S-OFF] Custom MTD Partitions (resize data, system, and cache)
I've always been disappointed with the small amount of space the Aria has for internal storage. Would it be possible to change the partition size of the aria to allow for more internal storage?
KillerBeaver said:
I was reading in the desire forums and saw this thread.
[DEV][S-OFF] Custom MTD Partitions (resize data, system, and cache)
I've always been disappointed with the small amount of space the Aria has for internal storage. Would it be possible to change the partition size of the aria to allow for more internal storage?
Click to expand...
Click to collapse
just use s2e or darktremors apps2sd and have all the internal storage you want lol
I had heard that battery life and r/w speed could be better on the internal. Is that incorrect? I thought it could be done relatively simply with a hex editor, but i'm not very knowledgeable in that specific department. So, that's why i wanted to ask.
I've been reading into this topic for two days now, and I still did not have what I need.
From the installer scripts, and such, I saw that almost every partition is mounted as /dev/block/mmcblk0p[n]. But teardown images show that the Transformer actually got a built in NAND memory(Kingston 16/32GB), not an internal SD.
So, my question is, which one is correct? Is it an SD card, a NAND chip, or what?
I think both are correct. I think there are 2 partitions on the nand, one for the os and the other one acts as an internal sdcard. Because when you wipe and factory reset the system, all the data on the internal storage are preserved.
Then why is the system partition referred as /dev/block/mmcblk0p1, and such? Staging can be understood, as it is the easiest to refer as such partition, but system, etc, are totally unnecessary, mtd partitions would be the most AOSP way :S
I mostly need this info as I'm setting up a CyanogenMod device tree, and for that there is a new switch (BOARD_HAS_INTERNAL_SD), and for that I have to decide how to go with...
Sorry I can't help you more. I'm just assuming. Hope someone can help you better.
RK3066 data sheet brief
fonix232 said:
I've been reading into this topic for two days now, and I still did not have what I need.
From the installer scripts, and such, I saw that almost every partition is mounted as /dev/block/mmcblk0p[n]. But teardown images show that the Transformer actually got a built in NAND memory(Kingston 16/32GB), not an internal SD.
So, my question is, which one is correct? Is it an SD card, a NAND chip, or what?
Click to expand...
Click to collapse
Could this help maybe?
HyperTextTransferProtocol://tabreview.ru/content/pdf_docs/RK3066_datasheet_brief.pdf
With all the lighter custom ROMs we have today, the default huge /system partition we have in the O3D is a waste of space. Same with the /data partition. For those who don´t know, both /system and /data (and other smaller ones) are actual internal SD Card space!
That´s why we have LG specs saying we have 8GB of internal flash storage, when in fact we have just 5.5GB available.
So my question is: is there a (safe) way to wipe all internal SD partitions and then recreate them with more appropriate sizes, earning back all the wasted space?
Thanks a lot!
Marcovecchio said:
With all the lighter custom ROMs we have today, the default huge /system partition we have in the O3D is a waste of space. Same with the /data partition. For those who don´t know, both /system and /data (and other smaller ones) are actual internal SD Card space!
That´s why we have LG specs saying we have 8GB of internal flash storage, when in fact we have just 5.5GB available.
So my question is: is there a (safe) way to wipe all internal SD partitions and then recreate them with more appropriate sizes, earning back all the wasted space?
Thanks a lot!
Click to expand...
Click to collapse
Have you read about data2ext? I think it would be a very good solution to us.
Sent from my LG-P920 using XDA App
Thanks for the reply, ThiaiZ!
However, I think I´m looking for something different: as far as I know, data2ext changes the /data partition pointer to external memory (SD Card), so the original /data partition will never be used by the OS, and it´s space will be wasted, right?
I would like to find a way to get this wasted space back! If we could repartition /system, /data, /cache, to smaller sizes, we would have more storage space for stuff on the internal SD. Does it make sense? Thanks!
Well, since I had no solutions here, I would like to post some examples of this for other phone models:
MyTouch 3G Slide - http://forum.xda-developers.com/showthread.php?t=893706
LG GT540 - http://forum.xda-developers.com/showthread.php?t=1171531
The MyTouch 3G Slide thread is particularly good because it explains in detail how to check the partition sizes, and shows how much space is wasted on the /system partition.
Marcovecchio said:
Well, since I had no solutions here, I would like to post some examples of this for other phone models:
MyTouch 3G Slide - http://forum.xda-developers.com/showthread.php?t=893706
LG GT540 - http://forum.xda-developers.com/showthread.php?t=1171531
The MyTouch 3G Slide thread is particularly good because it explains in detail how to check the partition sizes, and shows how much space is wasted on the /system partition.
Click to expand...
Click to collapse
Don't we have to be s-off to be able to resize the partitions ?
I did it a lot on my HTC Desire.
BTW do you have any idea in which block data and sd-ext are mounted on our device ?
I believe the S-OFF flag exists only in HTC devices. I read that somewhere here, at XDA. The guy seemed to know what he was talking about, and he said LG never implemented any kind of protection like S-ON / S-OFF.
About the block names, I believe you can list the blocks and the partition names they´re mounted as, with the "df" command. I know almost nothing about Linux, and even less about how Android manage it´s partitions, but that would be nice to be able to tweak their sizes...
LG GT540's partitions can easily be resized by flashing an MBN file. Don't know if this phone can get that done too
http://forum.xda-developers.com/showthread.php?t=1171531
Don't try resizing partitions.
You'll brick your phone.
I just found this very interesting MOD on the HTC Sensation Forum and wanted to share it with you, since it's also available for our DS!
http://forum.xda-developers.com/showthread.php?t=2145133
Basically they offer a script with which you can use your cache partition (and even the data partition) as swap and hereby boost your phones speed!
From the original Thread:
"The HTC Sensation has 768 MB ram and 4 GB internal eMMC memory. The eMMC is separated into several partitions (e.g. /system, /boot, /data, /cache). In former times of Android, the /cache partition was used for caching. Nowadays, in ICS times, the applications are using the /data partition to save information, libraries and cache data. So /cache is no longer used by the operating system or applications.
Therefore, this partition is empty except 4ext-logfiles, last recovery-log and an obligatory and empty lost+found directory. So we have got another 114 MB of space that can now be used as fast swap space for the kernel. As this is internal memory, it is faster, than a swap area on the sdcard!
TRY IT – YOU WILL BE CONVINCED AT ONCE!
If you are afraid of too many read/write requests to /cache, which may harm your eMMC memory of your phone, then don’t read further – we are not afraid, because there are also a lot of read/write requests to the /data partition as well and this is in Android “by design”."
Please post your questions, suggestions and problems in the thread above! Hope this Information might be useful
All Credits to delta-roh & Harbir! Thank them!
thanks
thanks for the introduction to our family. It could be better if you can leech a few paragraphs from that thread to this thread. and ye, put credits.
Swap support?
I have installed this mod but i cannot turn on the swap. The amidabuddha's kernel have swap support? I have read the topic but only z-ram support was pesent and z-ram support are disabled..
Can't turn swap on too,I use ROM is VierSaga 2.2.0,just report the results.
Sent from my HTC Desire S using xda app-developers app
Guys, I don't think this should be the support thread. Go to the original thread for help
Sent from my supercharged :tank:
thanks ...
The Hefe Hook kernel allows you to mount a partition of your microSD as /data, getting 2 GB (or more) for your apps and their data.
Please ask your questions here about installation, use, or general approach.
This is great @jeffsf and can u show me how to re-partition the "real internal" storage? I mean expanding the /system since u put the /data out of it. Thanks man
Sent from my GT-N7000 using Tapatalk 2
daothanhduy1996 said:
This is great @jeffsf can u show me how to re-partition the "real internal" storage? I mean expanding the /system since u put the /data out of it.
Click to expand...
Click to collapse
Yes, you've hit on another of the reasons I've been exploring using the microSD for "live" storage. It's one thing to use potentially slow storage for photos that you basically write once or "app to SD" where you read the APK at boot time, make sure your ODEX in the Davlik cache is good, then generally read from the internal-flash cache. It is another when that memory is being read and written "constantly" when your phone is running.
The good thing is that once /data is not part of the internal flash filesystem, you don't have to worry about one ROM (kernel) thinking it begins at one place and another saying it starts at another. Previously, if one ROM had one /system size and another and a different one, the next partition, /data, would look to be corrupt when you swapped ROMs.
As a warning, not all users have fast microSD cards. Some that say "Class 10" on them really are dogs, especially for small reads/writes. The "Class" ratings are for sustained writes, as you would have with a camera recording video. If your ROM is "external /data" only, or even defaults to that, be prepared for a slew of "Your ROMs sucks. It is so slow." complaints.
You'll also need a way to automate formatting the card. It can be done on the phone, as long as you aren't trying to preserve any data.
As I recall, the layout of the MTD partitions is done in drivers/mtd/onenand/samsung_galaxys4g.h I would be careful not to move the partition boundary for efs, as you'd have to move the data it contains in your updater script. Repeating the warning about not moving the boot and recovery partitions is probably a good idea as well!
Your build tree may need some of these values, or at least think it needs some of these values. For example, device/samsung/aries-common from the CyanogenMod/cm-11.0 (KitKat) branch calls out NAND page sizes, partition sizes, and flash block sizes. I haven't looked in detail at your build tree so I can't comment on how it might handle things differently than the CyanogenMod one.
itzik2sh said:
Hi
I hope I don't ask anything silly, but please let me know if any of my assumptions is wrong :
1. I take FBi's251's AOKP milestone 6 (ICS 4.0.4)
2. 8GB SDCard was formatted to FAT32 (4GB) and EXT3 (4GB) using TWRP kernel
(Beastmode's proton kernel to be exact).
3. I would flash this kernel and it would move apps and their data to the sd-ext
without any special additions.
Thanks. I read the thread, but unfortunately 8GB SD is what i have and I think it should be enough.
Thanks again.
P.S - it's for 2 guys I already sold them my SGS4Gs. I want them to be happy...
Click to expand...
Click to collapse
AOKP should be fine. I haven't tried it recently, but it was the tree in which I did the early Hefe Kernel development.
As I understand it, you have a microSD with
partition 1: 4 GB FAT32
partition 2: 4 GB ext3
So that can work, but will need some tweaking of the init-on-fs.sh script. I intentionally didn't use the second partition as so many scripts gobble that up as sd-ext and do who knows what to it.
My first preference would be to reformat the cards, perhaps:
6 GB FAT32
1 MB ext2/3/4 (Yes, 1 MB, a sliver, choice of ext2, ext3, ext4 up to you)
2 GB ext4
since then the script will work without modification and if they install a third-party script that uses the second partition, it won't corrupt their data.
If you were to keep the formatting the way that it is now, you'd need to edit the mount commands in the script to look something like:
Code:
/system/xbin/busybox umount /data
/system/xbin/busybox mount -t ext3 -o noatime /dev/block/mmcblk0p2 /data
(removing the sd-ext mount)
I'm not sure what your expectations are, but all that the kernel and that script will do is mount a different disk partition on /data -- you need to manually move the data over (or restore from something like Titanium Backup). There may be some trickery in renaming that could be used with TWRP backups to restore from data.yaffs2.win to the new /data partition, but I haven't tried that at all.
Hi Jeff
Thanks for your quick reply, and sorry again for not seeing the Q&A thread.
I think making it :
partition 1: 4 GB FAT32 (sdcard)
partition 2: 2 GB ext3 (sd-ext)
partition 3: 2 GB ext3 (data)
partition 4: 1 MB (spare)
would be better and handle data as well. don't you think ?
Would it be worth doing with a "Team" micro-SD card (class 6 I believe) ?
Thanks.
I haven't tried a Class 6 card, but my gut feeling is that it will be dicey. I didn't "commit" to using /data on microSD until I had tried it for several days using Titanium Backup's ability to move both apps and app data to the external card. I would try that first, especially as the phones in question aren't going to be in your hands (I consider you an expert user, able to manage things outside the UI with ease).
I've attached some testing I did a while ago with Transcend and SanDisk cards. When you look at them, realize that the speed scale changes between them. I have a feeling that the real "performance" on a device is going to be related to relatively small reads and writes, not the ability to stream video to the card. I also don't know much about the Team brand, but I found that even some well-known brands didn't have the performance of the Transcend or SanDisk in the same category.
However you configure your cards, I would definitely recommend a journaling filesystem of some sort. I've had my microSD come loose inside the phone. The journal will at least help to reduce any filesystem corruption should that happen.
You don't need the fourth partition -- I have it there to be able to keep rsync backups for fast ROM swapping.
.
Regarding the apps data, have you tried exploring the Mount2SD script ?
sent from me
I've tried a couple of the scripts out there in the past. Since backing up my data is very important to me, I trust the scripts in Titanium Backup to work well with its backup/restore strategies.
Mounts2SD looks like it has gotten a lot more sophisticated than it was when I tried it in the past. It sounds like something worth trying in its current state. At a quick glance (and not looking at the code), I'd personally make some different choices about features; enabling journaling, and being concerned about why lost+found was filling up (things should only appear there if the file system is found to be corrupt).