Is there a way to partition the internal memory that is now mounted a emmc then format one partition to ext2 or ext3? It would be nice the then modify the phone to mount /data/data to this new partition rather then its current location because it seems as of late I am always running out of space of /data/data.
Thanks,
CG
I'm interested in this too. I think the simpler thing would be to shrink /mnt/emmc and use the leftover space to expand /data.
I'm also wondering if it's possible to format /data to ext4, and if so if there are any advantages.
Maybe someone else has some ideas?
anyone have any thoughts?
cmgrant said:
anyone have any thoughts?
Click to expand...
Click to collapse
Check this work-in-progress project out::
http://forum.xda-developers.com/showthread.php?t=853001
(It is NES, for exactly this sort of problem) :: PS: Be sure to participate in the beta and provide some feedback if you try this out. It is close, and being modified for GB at this point because GB changed their packager paradigm.
Related
We only get about roughly 40mb of phone storage for Android. Is there anyway I could expand the size? I know on my TP2 version I think we got like 100mb of space?
xxjoshuaaxx said:
We only get about roughly 40mb of phone storage for Android. Is there anyway I could expand the size? I know on my TP2 version I think we got like 100mb of space?
Click to expand...
Click to collapse
install /data to ext2 partition.
robuser007 said:
install /data to ext2 partition.
Click to expand...
Click to collapse
But I am on NAND
xxjoshuaaxx said:
But I am on NAND
Click to expand...
Click to collapse
*Correct me if I'm wrong but I believe...*
The TP2 has 512 mb internal storage, kaiser (tilt) has 256.
The only way to get more storage is to use ext2 partitions on your sd card and install either system OR data to the partition and the other to nand. Depending on how big you make the partition will determine how much storage you have.
Sorry guys I am still a newbie at this. I see what ya' mean. Thanks for giving me some common sense.
xxjoshuaaxx said:
Sorry guys I am still a newbie at this. I see what ya' mean. Thanks for giving me some common sense.
Click to expand...
Click to collapse
/sys @NAND and /data on microSD (for nand installations) on one ext2 partition(no need for fat32).
So long as we have a ext2 partition on our SD cards, choosing /data on microSD will install applications on the SD card?
Or use apps2sd
how to use apps2sd plz?
hello everybody
I didn't find the answer to my question (I used the search tool) so forgive me if it has allready been answered:
is it possible, in order to improve performance, to format /data which is actually using the samsung rfs into ext4 so that the hack of formating the external sd card and moving /data on it will be unnecessary?
thank you by advance.
As of now we have no way at all to modify what file system is on the internal storage devices. Besides I do not believe that the we evildoer in this case is a poor fs.
Sent from my GT-I9000 using XDA App
gontran said:
hello everybody
I didn't find the answer to my question (I used the search tool) so forgive me if it has allready been answered:
is it possible, in order to improve performance, to format /data which is actually using the samsung rfs into ext4 so that the hack of formating the external sd card and moving /data on it will be unnecessary?
thank you by advance.
Click to expand...
Click to collapse
'
I've just been reading this about RFS, you might find it interesting:
http://forum.samdroid.net/f16/what-we-know-about-samsung-rfs-30/
Darkstriker said:
As of now we have no way at all to modify what file system is on the internal storage devices. Besides I do not believe that the we evildoer in this case is a poor fs.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Is there no way to umount /data and then format it into ext4?
Rfs seems to have pretty poor performances compared to ext4 but I'm not an expert so maybe is it useless.
Did you not read what you quoted from me there?
We do NOT have a way to modify the filesystem on the internal storage. We can unmount it but we CANNOT format it!
Darkstriker said:
Did you not read what you quoted from me there?
We do NOT have a way to modify the filesystem on the internal storage. We can unmount it but we CANNOT format it!
Click to expand...
Click to collapse
A little less attitude please!
He asked a perfectly valid question, all that is required are the file system tools format, partition and check the partition and an understanding of the init.rc files that mount the partition on boot.
Hi!
Just would like to know the pros and cons of formatting into ext4 on my SD.
As far as I can find :
Pros : Supports files larger than 4GB as Fat32 cannot
That's about it I think...
Cons : Windows cannot natively detect such a partition
Why I ask this is I just saw a this post
blahbl4hblah said:
Having sd-ext partition on your sdcard will always be benefical, the phone will run so much better believe me
Click to expand...
Click to collapse
I'm ready to go ext4 if there's any performance gain, who wouldn't? But what gain is there, and what would I lose in return?
ArmedandDangerous said:
Hi!
Just would like to know the pros and cons of formatting into ext4 on my SD.
As far as I can find :
Pros : Supports files larger than 4GB as Fat32 cannot
That's about it I think...
Cons : Windows cannot natively detect such a partition
Why I ask this is I just saw a this post
I'm ready to go ext4 if there's any performance gain, who wouldn't? But what gain is there, and what would I lose in return?
Click to expand...
Click to collapse
You're mixing things up here a bit I think. Sd-ext referrs to having a partition on your sdcard to allow support for Apps2SD (basically being able to move apps to your SD card and run them from there in order to free up space); you'd basically repartition the card so that there's an ext3/4 partition for apps and a FAT32 partition for data.
As for the ext4 filesystem, it does allow for larger file sizes and is also a bit faster but you're correct in the fact that you won't be able to natively mount it on a Windows system.
Sent from my T-Mobile G2 using XDA App
OriginalGabriel said:
You're mixing things up here a bit I think. Sd-ext referrs to having a partition on your sdcard to allow support for Apps2SD (basically being able to move apps to your SD card and run them from there in order to free up space); you'd basically repartition the card so that there's an ext3/4 partition for apps and a FAT32 partition for data.
As for the ext4 filesystem, it does allow for larger file sizes and is also a bit faster but you're correct in the fact that you won't be able to natively mount it on a Windows system.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
But don't we already have Apps2SD in GB, + all the apps that do it for you. How is this different, apart from some apps that can't natively be moved? And why is it faster? Internal memory should always load faster, should it not?
ArmedandDangerous said:
But don't we already have Apps2SD in GB, + all the apps that do it for you. How is this different, apart from some apps that can't natively be moved? And why is it faster? Internal memory should always load faster, should it not?
Click to expand...
Click to collapse
GB has the ability to do Apps2SD but it requires the partitioning as, I believe, a symlink is set up so that partition on the sdcard acts as a part of the devices internal storage.
As for speed, just moving apps to your sdcard won't speed up your phone; what that poster you quoted was talking about (most likely, I'd have to see the original thread) was converting your devices partitions (/system, /data, /cache, etc.) from ext3 to ext4. ext4 is a bit faster however some ROMs do not fully support it.
Sent from my T-Mobile G2 using XDA App
Ok, let's clear this up. GB has Apps2FAT32 (a2sd) natively. A2EXT is completely different but none of that is the point of the OP's question.
When it comes to our phones - there is almost no notable performance gain when using EXT4 over any other EXT format. Our phones don't utilize FAT32 internally - just on the sdcard. EXT4 is designed for use with massive file systems. A couple Gigs really doesn't access it's full potential.
While the question is interesting, I'm not really sure what you're planning on doing. Don't format your sdcard entirely in EXT format, and don't attempt to format your phones partitions as FAT32. The result would be... just don't do it.
Just read this on the portal
http://www.xda-developers.com/andro...hd2-data-successfully-moved-to-ext-partition/
This has two main advantages: larger sized data partition and more speed as EXT is inherently faster for I/O purposes.
Click to expand...
Click to collapse
How do I go about formatting a section of my SD into ext4, with existing SD data intact.
And how do I move apps that area already in my phone's internal memory to the ext4 partition? I know there's an option in ROM Manager and CWM, but just don't want to mess anything up
ArmedandDangerous said:
Just read this on the portal
http://www.xda-developers.com/andro...hd2-data-successfully-moved-to-ext-partition/
How do I go about formatting a section of my SD into ext4, with existing SD data intact.
And how do I move apps that area already in my phone's internal memory to the ext4 partition? I know there's an option in ROM Manager and CWM, but just don't want to mess anything up
Click to expand...
Click to collapse
As far as I know, only two ROMs actually support the real A2SD: PyroMod and MexDroid. It's recommended you format the EXT partition to EXT4 before you actually flash either of those ROMs, and you have to rename MexDroid in order to get A2SD working.
blackknightavalon said:
As far as I know, only two ROMs actually support the real A2SD: PyroMod and MexDroid. It's recommended you format the EXT partition to EXT4 before you actually flash either of those ROMs, and you have to rename MexDroid in order to get A2SD working.
Click to expand...
Click to collapse
Thankfully I am already using meXdroid~ Guess I'll just wait for the new version in the next few days to do the formatting. Can I backup all my apps with Titanium Backup, flash ROM (wipe data/cache and dalvik cache), restore with Titanium.
Or would I have to reinstall every app again so that it goes into the ext4 partition?
blackknightavalon said:
As far as I know, only two ROMs actually support the real A2SD: PyroMod and MexDroid. It's recommended you format the EXT partition to EXT4 before you actually flash either of those ROMs, and you have to rename MexDroid in order to get A2SD working.
Click to expand...
Click to collapse
There's a script to accomplish this on pretty much any ROM. It *should* work on current ROMs too. It's called 'darktremor a2sd'. Still find it amazing people forget about that one when this question comes up because it's one oldest methods of obtaining a2sd.
I'm still not understanding the OP's question. Are you wanting to do this for an IO performance gain or for space? I can understand doing it for space if you have a ton of apps but if you're doing it for performance it's a waste of your time. You're internal partitions should already be in EXT4 format (use 4EXT Recovery if they're not).
KCRic said:
There's a script to accomplish this on pretty much any ROM. It *should* work on current ROMs too. It's called 'darktremor a2sd'. Still find it amazing people forget about that one when this question comes up because it's one oldest methods of obtaining a2sd.
I'm still not understanding the OP's question. Are you wanting to do this for an IO performance gain or for space? I can understand doing it for space if you have a ton of apps but if you're doing it for performance it's a waste of your time. You're internal partitions should already be in EXT4 format (use 4EXT Recovery if they're not).
Click to expand...
Click to collapse
I'm doing it for the performance. Have been using 4EXT for a few days and loving it. Already converted internal memory to ext4 from ext3. If further partitioning my SD card for performance is really not noticeable, then I guess I've got nothing to worry about
Has anyone successfully reformatted either /sdcard or /sdcard/external_sd/ /emmc as ext3? I'm not talking about an Apps2SD partition, I'm talking about reformatting the whole volume as one partition, transparent to apps. I do not use Windows so I do not need interoperability, I am fine with ext filesystems.
My goal is to be able to use symlinks (not to mention a more robust filesystem) to redirect certain hard-coded items to store on a different storage volume than it defaults to, but symlinks are not permitted on vfat (FAT32) filesystems.
Thanks!
Anything that I look an answer for, is just not answered. :-(
I am looking for the same information. Wonder why the native ext file systems are not allowed, given that its a Linux kernel running.
You could format it to ext3 and see how it works. Worst case scenario is your phone will tell that sdcard to fu*k off. Given that our phones can and do read the ext format I'm sure you can do it. I'm just not sure how well it will work as far as mounting and such.
On top of that, Windows can read ext formats. You just need a program to do it. I use it all the time.
Thanks for reviving this thread. Surely there must be someone out there who has tried this, and I was hoping to hear from them before I gave it a go, but looks like I'll just have to give it a shot myself.
When I find the time to backup & wipe my sdcard to try and reformat & mount it, I'll report back here.
With my Galaxy Note N7000 I can format a USB Stick to EXT3, and the phone uses it perfectly well as USB Storage...
(rooted, w/w SpeedMod kernel)
I know I'm late to the party and this was probably already discussed, but I couldn't find it with search. Has anyone considered converting the inc to a data media device (http://www.xda-developers.com/android/what-is-a-data-media-device/)? I've seen this done with other devices (e.g. hp touchpad). I'd be nice to be able to use the EMMC partition for storage and data. I know there is ext4all but I still seem to run out of space quickly since dalvik-cache is half of /data.
Not sure if hboot will let you combine partitions to do what you want; however, lvm can probably accomplish what you're hoping to achieve but it takes quite a bit of effort to setup.
Sent from my One using Tapatalk
I wasn't necessarily thinking we need to combine any partitions. Just don't mount the existing /data and /data/data partitions, and mount the EMMC partition as /data with an emulated sdcard at /data/media. I think this is how the Samsung phones work; you have both "internal" and "external" sdcards. Seems like it should just be some config changes and maybe a recovery that is datamedia aware so you don't erase the emulated sdcard when wiping data.
Smells like a project. I'll see if I will get around to this but this sounds doable.
No promises but my Inc could get bricked and I wouldn't cry over it so I can take a few risks.
Sent from my One using Tapatalk
I've only done a little research so far, but it seems like you'd only need to change a few configuration files. I don't think you could truly brick your Inc, could you? I'm tempted to try and get it working myself but I can't risk bricking my dd.
Sent from my ADR6300 using Tapatalk
ive got 2 incs so I dont mind messing with it, I have a touchpad tho and from what I know (I am decent friends with invisiblek and he does work on the touchpad) the only real difference, is re-partitioning your internal and setting the device tree to mount data as data/media instead of for say /data or /data/data
I have a TouchPad too. Finally made the leap to kk and datamedia there which is what got me thinking about the Inc. The repartioning done for the TouchPad was too make the data partition larger since it now holds both apps and sdcard data. We shouldn't have to do that for the Inc since we already have a partition with 6.6 gig available. Nothing is mounted at /data/media, it's just another directory on the main /data partition. That's why you need a special recovery that "wipes" data instead of formatting...
I've been looking at the changes milaq made. I assume invisiblek did something similar if not the same.
Sent from my ADR6300 using Tapatalk
natediggity said:
I have a TouchPad too. Finally made the leap to kk and datamedia there which is what got me thinking about the Inc. The repartioning done for the TouchPad was too make the data partition larger since it now holds both apps and sdcard data. We shouldn't have to do that for the Inc since we already have a partition with 6.6 gig available. Nothing is mounted at /data/media, it's just another directory on the main /data partition. That's why you need a special recovery that "wipes" data instead of formatting...
I've been looking at the changes milaq made. I assume invisiblek did something similar if not the same.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
A fancy flashable script to convert your boot.img to use /data/media should be possible. So far I told it to switch to mmcblk03 from 01 for /data so it's 6.6GB. The other part is relocating fuse to use /data/media for the internal storage instead of /emmc. That should be somewhat easy to change but a bit harder to script.
/data/media was designed for devices that don't have an sdcard slot which the Inc does have so this is more of a proof of concept idea for me than actual utility.
Ok, the last part is recovery and the current recovery images appear to be large enough to make the recovery build part fail. I'm not sure the actual recovery partition size on the inc but the images come to be about 4.5 MB and fail.
zachf714 said:
ive got 2 incs so I dont mind messing with it, I have a touchpad tho and from what I know (I am decent friends with invisiblek and he does work on the touchpad) the only real difference, is re-partitioning your internal and setting the device tree to mount data as data/media instead of for say /data or /data/data
Click to expand...
Click to collapse
/data/media uses fuse on an existing ext4 partition so the recovery as nate said has to be told to wipe /data instead of format (in other words, using an rm command and excluding /data/media).
This makes filesystem corruption harder to fix since the partition can't be wiped from recovery normally unless it's a format which TWRP does have an option to format /data.
tiny4579 said:
A fancy flashable script to convert your boot.img to use /data/media should be possible. So far I told it to switch to mmcblk03 from 01 for /data so it's 6.6GB. The other part is relocating fuse to use /data/media for the internal storage instead of /emmc. That should be somewhat easy to change but a bit harder to script.
/data/media was designed for devices that don't have an sdcard slot which the Inc does have so this is more of a proof of concept idea for me than actual utility.
Ok, the last part is recovery and the current recovery images appear to be large enough to make the recovery build part fail. I'm not sure the actual recovery partition size on the inc but the images come to be about 4.5 MB and fail.
Click to expand...
Click to collapse
Check my device tree, I have a commit on omni that compresses recovery a bit more and I use it to build
Sent from my SCH-I535 using Tapatalk
tiny4579 said:
A fancy flashable script to convert your boot.img to use /data/media should be possible. So far I told it to switch to mmcblk03 from 01 for /data so it's 6.6GB. The other part is relocating fuse to use /data/media for the internal storage instead of /emmc. That should be somewhat easy to change but a bit harder to script.
Click to expand...
Click to collapse
I don't need a flashable script unless it's required. Personally, I'm fine just building a new system image and flashing that.
tiny4579 said:
/data/media was designed for devices that don't have an sdcard slot which the Inc does have so this is more of a proof of concept idea for me than actual utility.
Click to expand...
Click to collapse
datamedia can be used in conjunction with sdcards. This is what the new samsung phones do. I thought the HTC One did as well, but I just remembered it doesn't have a sdcard slot. If you haven't already, check out this page: https://source.android.com/devices/tech/storage/config-example.html. Our config would be similar to the Xoom's.