Database Info

[Q] Custom MTD Partitions

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.

[Q] How to resize/recreate /system and /data partitions?

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.

[MOD][ALPHA][2013-02-14] Save internal memory: dalvik-cache on /system AROMA

WARNING: This is far from complete, read carefully to know whether it is safe!
I created a tiny mod that automatically moves dalvik-cache to your /system partition in order to gain space on /data. The idea to do it came from here: http://petermolnar.eu/linux-tech-coding/how-to-move-dalvik-cache-to-system-partition-in-android/
Fiddling with the bootimage seemed to cumbersome and on a ROM supporting init.d-scripts, it should be possible to fix all from there (remount /system rw and check whether symlink is damaged from a dalvik-cache wipe attempt). This is my first working-for-me zip to automate the process in a flashable zip.
The installer contains an option to revert the mod -- works for me.
Prerequisites
For this to work, you need:
A ROM that supports init.d scripts
busybox installed (of course)
A custom recovery with all busybox links in place (should work on most)
Enough free space on /system for dalvik-cache
Limitations
Untested -- so far tested only on my Sensation with SuperXE 4.2.1 ROM
Prerequisites unchecked -- this includes busybox and space requirements on /system. Check yourself for now before flashing
Dalvik cache wipe non-functional -- at least for me on 4EXT Touch recovery. But it doesn't do any harm, at least.
Benefits
More space on /data -- around 150 MB for me
Downsides
/system must be kept rw
TODOs
Check some prerequisites to make it safer to flash
Analyze why dalvik-cache wiping does not work, maybe provide own wiping-option in AROMA
Check whether this works on ROMs with dalvik-cache on /cache; it already looks there after /data, so it SHOULD work
dalvik-syscache_0.2a_ALPHA.zip - use at your own risk.Nandroid keeps you safe, so please test after backup !
Older versions
dalvik-syscache_0.1a_ALPHA.zip
Changelog
* 0.2a:
Added dalvik-cache wipe option in AROMA
Minor cosmetic changes

Very nice idea!
On a related note - is there no safe way to repartition our device and just shrink the /system partition, giving it to /data instead?

manuelkuhs said:
Very nice idea!
Click to expand...
Click to collapse
Thanks, although the idea is old, just tried to automate it.
On a related note - is there no safe way to repartition our device and just shrink the /system partition, giving it to /data instead?
Click to expand...
Click to collapse
I don't think so. No idea what kind of partition table is used, but given the fact it's all on the same internal mmc block device, even the recovery partition, I assume it would be quite risky. But maybe someone around knows better?

wipe dalvike-cache option added in aroma ...

great job!
but i want to know if there any harm to our phone when system partition been read and write much more frequently than before?

AW: [MOD][ALPHA][2013-02-14] Save internal memory: dalvik-cache on /system AROMA
theggs said:
great job!
but i want to know if there any harm to our phone when system partition been read and write much more frequently than before?
Click to expand...
Click to collapse
No worries there, it's the same underlying block device. The only "issue" with having /system rw is it's maybe easier to accidently mess with your Rom at the command prompt. But wear on the flash is the same, no matter what partition is used for dalvik-cache.
Sent from my HTC Sensation XE using xda app-developers app

trying it out

trying it on cm10.1..it works!save 200+mb in /data. now more apps can be installed. now i can install much more apps thx for your great job!
just for one thing, this mod just move dalvik-cache in /data to /system, and dalvik-cache in /cache is still there. so still can only creat 50mb swap partition in /cache with the turbo boost.
Sent from my HTC Sensation using Tapatalk 2

theggs said:
trying it on cm10.1..it works!save 200+mb in /data. now more apps can be installed. now i can install much more apps thx for your great job!
just for one thing, this mod just move dalvik-cache in /data to /system, and dalvik-cache in /cache is still there. so still can only creat 50mb swap partition in /cache with the turbo boost.
Click to expand...
Click to collapse
Hi, thanks for testing!
For your issue: I think there should be only one dalvik-cache (either in /data or in /cache), the other one probably being a leftover of another rom. could you try wiping dalvik-cache & cache and see which one is re-created at boot? [If really both, I'll gonna have a look at CM 10.1 myself...]
edit: uninstall the mod before wiping please ...

tired and still get dalvik-cache in both /date and /cache without this mod. and with this mode, dalvik-cache in both /cache(67.73mb) and /system(238.32mb).

theggs said:
tired and still get dalvik-cache in both /date and /cache without this mod. and with this mode, dalvik-cache in both /cache(67.73mb) and /system(238.32mb).
Click to expand...
Click to collapse
Ok thanks ... I just researched a little on this and probably your ROM splits dalvik-cache in two parts, for system apps (on /cache) and user apps (on /data).
Of course I could make this mod move both of them to /system, but I think I'll first try to implement some checks for available space in order to make this a safe operation. I'll think about solutions ...
edit: for stripped-down / AOSP roms, this should always be safe, having around 450 to 500 MB free space on /system -- but in order to make this mod safe for all, I think I'll have to work a little on it

Looking forward to the next vision. thx for your work again!

Nice idea!
Just wondering since most of us have s-Off, isn't there a way to repartition the band, so I can make more space on data instead of system? I always use aosp roms, so there isn't needed much space on system for me
Sent from my HTC Sensation using xda premium

Caspertje19 said:
Just wondering since most of us have s-Off, isn't there a way to repartition the band, so I can make more space on data instead of system? I always use aosp roms, so there isn't needed much space on system for me
Click to expand...
Click to collapse
Yep, I had that idea, too. Especially using AOSP, the space on /system is wasted.
I'm still not sure whether repartitioning is possible, but now I think I wouldn't dare to, given the fact that recovery resides on the same block device -- I'd worry to brick my phone fiddling with the partition table.
So, for me, moving dalvik-cache to system and installing apps I constantly use to /system/app seemed to be the "next-best" solution.
I'll update this mod probably this weekend, adding some logic checking space-requirements should make it safe to flash.

Caspertje19 said:
Nice idea!
Just wondering since most of us have s-Off, isn't there a way to repartition the band, so I can make more space on data instead of system? I always use aosp roms, so there isn't needed much space on system for me
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Only people I know who can create custom hboots are alpharev and thalmus_
Sent from my HTC Sensation using xda app-developers app

It's an old thread, but has anyone a working link to download this ?

I think this is relevant for today.

[MOD] TURBO BOOST - Triple Swap Space in Cache, Data, System ...

Hi guys...
I used this mod on a friend's sensation xe and saw huge performance increase. I tried it on htc explorer but it didn't work... I was in the hurry ... I might have skipped some steps by mistake!
Could you please test it? then you can notify the dev to make it available for our PICO through Aroma! so everybody can install it in several minutes!
Thanks in advance!
[MOD][2013-08-10][V3.03]TURBO BOOST - Triple Swap Space in Cache, Data, System ...
See support your device section:
http://forum.xda-developers.com/showpost.php?p=37905396&postcount=4

hrkh83 said:
Hi guys...
I used this mod on a friend's sensation xe and saw huge performance increase. I tried it on htc explorer but it didn't work... I was in the hurry ... I might have skipped some steps by mistake!
Could you please test it? then you can notify the dev to make it available for our PICO through Aroma! so everybody can install it in several minutes!
Thanks in advance!
[MOD][2013-08-10][V3.03]TURBO BOOST - Triple Swap Space in Cache, Data, System ...
See support your device section:
http://forum.xda-developers.com/showpost.php?p=37905396&postcount=4
Click to expand...
Click to collapse
i have already asked this months ago
its not the problem of working or not our internal is nand and that method if for emmc
when we use swap it uses lot of read write cycles and nand have limited no. of cycles and cant cope up to the speed
so it will harm our memory
sodrop the ideo of it in our pico

sakshamx said:
i have already asked this months ago
its not the problem of working or not our internal is nand and that method if for emmc
when we use swap it uses lot of read write cycles and nand have limited no. of cycles and cant cope up to the speed
so it will harm our memory
sodrop the ideo of it in our pico
Click to expand...
Click to collapse
It's a myth!
TRY IT – YOU WILL BE CONVINCED AT ONCE!
If you are afraid of too many read/write requests to /cache, /data, /system, 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”. Furthermore there are devices, that have a preconfigured eMMC-swap space "by design", as for exaple the HTC One C.

hrkh83 said:
It's a myth!
TRY IT – YOU WILL BE CONVINCED AT ONCE!
If you are afraid of too many read/write requests to /cache, /data, /system, 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”. Furthermore there are devices, that have a preconfigured eMMC-swap space "by design", as for exaple the HTC One C.
Click to expand...
Click to collapse
our device has nand not emmc can;t u understand ?
then go kill ur pico :cyclops:

sakshamx said:
our device has nand not emmc can;t u understand ?
then go kill ur pico :cyclops:
Click to expand...
Click to collapse
From what I see pico has SU04G eMMC chip.

hrkh83 said:
From what I see pico has SU04G eMMC chip.
Click to expand...
Click to collapse
AFAIK I know if we had emmc then we dont have nand burns
maybe @cute_prince could clarify u

Thread moved to Q&A.
Please post all questions in Q&A, especially if it involves testing something which could potentially ruin someone's device. This is definitely not the kind of thing we need in development considering it's untested and simply a request for others to test it.

[Q&A] 2 GB External Data -- Hefe Hook Kernel and others

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).