Hi guys,
I was wondering, now that I no longer use a TouchWiz-based ROM, if there's an easy way to reclaim the "lost" space available in the /system folder after flashing a now much small ROM. I know TW-based ROMs use at least 1GB of space, if not more, but my current ROM barely pushes 200MB used of the /system folder, leaving with me a lot of unused space I would like to use for the integrated storage.
Regards
gonXed said:
Hi guys,
I was wondering, now that I no longer use a TouchWiz-based ROM, if there's an easy way to reclaim the "lost" space available in the /system folder after flashing a now much small ROM. I know TW-based ROMs use at least 1GB of space, if not more, but my current ROM barely pushes 200MB used of the /system folder, leaving with me a lot of unused space I would like to use for the integrated storage.
Regards
Click to expand...
Click to collapse
It's about partitions, no matter what rom you use.
Imagine you have a 1gig harddisk. You partitioned it into four 250gig harddisks as C,D,E,F
You have installed Windows 7 on C drive but then you installed XP to save some spaces for the harddisks D,E,F
Would it be possible? No!
You have to resize all the partitions which would cause you bigger problems.
I think is something to do with the pit files.
I read something about Sammy offering a new Flash for the s4 with some Chinese rom that enables them to get another couple gig space whilst losing some trash.
I hope we can get something similar either officially or through our devs
Sent from my GT-N7105 using xda app-developers app
[email protected] said:
It's about partitions, no matter what rom you use.
Imagine you have a 1gig harddisk. You partitioned it into four 250gig harddisks as C,D,E,F
You have installed Windows 7 on C drive but then you installed XP to save some spaces for the harddisks D,E,F
Would it be possible? No!
You have to resize all the partitions which would cause you bigger problems.
Click to expand...
Click to collapse
I don't think I follow you. You're telling me resizing partitions is not possible? Theoretically, it is with any type of filesystem and partition table that supports differently sized partitions/blocks. I'm not asking if it's possible to do it, I'm asking if it's possible to do it in an easy way.
My question wasn't if it was possible to do it with the new ROM, I was asking if it was possible to do, now that I have some abundant disk space for /system.
On my Nokia N900 this was extremely straightforward as I basically had the full GNU coreutils available - and with some hacking I resized the partitions to better fit my needs - and even flashed the fat32 filesystem to ext3 while I was at it.
And since it's possible with S4 as 3vo3d mentioned, there's no reason it shouldn't with the GN2.
gonXed said:
I don't think I follow you. You're telling me resizing partitions is not possible? Theoretically, it is with any type of filesystem and partition table that supports differently sized partitions/blocks. I'm not asking if it's possible to do it, I'm asking if it's possible to do it in an easy way.
My question wasn't if it was possible to do it with the new ROM, I was asking if it was possible to do, now that I have some abundant disk space for /system.
On my Nokia N900 this was extremely straightforward as I basically had the full GNU coreutils available - and with some hacking I resized the partitions to better fit my needs - and even flashed the fat32 filesystem to ext3 while I was at it.
And since it's possible with S4 as 3vo3d mentioned, there's no reason it shouldn't with the GN2.
Click to expand...
Click to collapse
No, I didn't say that you cannot resize partitions
I said that you cannot gain more space in other partitions by just installing a lighter OS. I said exactly what you said in the rest.
Related
Are there any roms or other easy ways to increase the size of the partition /data/data on the Droid Incredible? To this day, all I really find are ways to save space in there. That's been covered - everything from Cachemate to not using certain apps. I want to know if there are any roms out there that use space from internal or other areas and reroute them so that /data/data shows more space. Any help would be appreciated.
+1
I've run into this a lot lately. Even my Eris never had this problem.
enigmatl said:
Are there any roms or other easy ways to increase the size of the partition /data/data on the Droid Incredible? To this day, all I really find are ways to save space in there. That's been covered - everything from Cachemate to not using certain apps. I want to know if there are any roms out there that use space from internal or other areas and reroute them so that /data/data shows more space. Any help would be appreciated.
Click to expand...
Click to collapse
No roms do it currently. But its probably doable.
Sent from my ADR6300 using Tapatalk
There is an app on the market called Notenoughspace. I have never used it, but it is supposed to take stuff out of your data/data, and insert it somewhere else. I here it is tricky, so be careful if you use it. I really don't know much about it. The first couple of times I ran into this problem it drove me crazy. Have you read all of the threads for what causes this? Stay away from Facebook. If you sync contacts in Facebook it can cause this. I am a crackflasher, so I rarely run into the problem. I don't think that a Rom can fix this, but I am a newb myself. Really just wanted TP help since I saw your disgruntled post in the developers section....good luck
Thanks for the reply. But here's the thing. Please let's not go into the likes of notenoughspace and cachemate and whiping out facebook. This is what people say in EVERY thread on this from the beginning of the droid incredible.
I'm not looking for a solution that at best can let an extra app or 2 get installed on the droid incredible. I'm looking for a way to INCREASE the size of the /data/data partition by way of taking some unused space from other areas like system or cache or better yet, from that pointless internal storage (for all the SD card users).
There is a lot of extra space on these phones. Thus it is nonsensical to have a measly 150mb to use in that area.
AS this phone is for a friend (and I generally do the upgrading or fixing), I do not experience this on my photon nor do I experience it on my Iconia tab. There was a limit for /data/data on my evo but it was about twice the Droid Incredible I believe.
So this most likely has to be a partition issue. Is there really no fix for it? Since it's not a hardware limit, I'm surprised as I've seen some out of this world ROMs for the device (like Skyraider's which I hoped would make it to the Evo when I had that).
enigmatl said:
Thanks for the reply. But here's the thing. Please let's not go into the likes of notenoughspace and cachemate and whiping out facebook. This is what people say in EVERY thread on this from the beginning of the droid incredible.
I'm not looking for a solution that at best can let an extra app or 2 get installed on the droid incredible. I'm looking for a way to INCREASE the size of the /data/data partition by way of taking some unused space from other areas like system or cache or better yet, from that pointless internal storage (for all the SD card users).
There is a lot of extra space on these phones. Thus it is nonsensical to have a measly 150mb to use in that area.
AS this phone is for a friend (and I generally do the upgrading or fixing), I do not experience this on my photon nor do I experience it on my Iconia tab. There was a limit for /data/data on my evo but it was about twice the Droid Incredible I believe.
So this most likely has to be a partition issue. Is there really no fix for it? Since it's not a hardware limit, I'm surprised as I've seen some out of this world ROMs for the device (like Skyraider's which I hoped would make it to the Evo when I had that).
Click to expand...
Click to collapse
I have had the same problem, and I haven't seen any roms that come close to solving it. And there is no quick and easy solution.
The best work around I could find was to mod the stock rom and add Dark Tremor's APP2SD, and use notenoughspace.
With dtapps2sd you have to partiton the SD card so that you have a ext3 partition on it that can be mounted and apps can be ran from it. It does this for /data/app and a couple of other folders.
Notenoughspace will let you move folders in /data/data to the sd partition that dtapps2sd has mounted, and that survive through a reboot. The extra partition option is what you would use, not the NES partition.
Using this work around I have about 300 apps on my phone, and about 70mb free in /data/data.
My Android version is GB 2.3.4 (build 4.06.605.3).
enigmatl said:
Are there any roms or other easy ways to increase the size of the partition /data/data on the Droid Incredible? To this day, all I really find are ways to save space in there. That's been covered - everything from Cachemate to not using certain apps. I want to know if there are any roms out there that use space from internal or other areas and reroute them so that /data/data shows more space. Any help would be appreciated.
Click to expand...
Click to collapse
Bootmanager will install the whole rom on /sdcard or emmc storage and as an added bonus, /data and /data/data are all in one image so you have shared space. By default you have 950 MB to share for apps and app data. As an added bonus you have the ability to boot multiple roms and have them all loaded at once. It's available on the market and the devs who made it are awesome. However it costs a few dollars.
If you don't want to go that route then it's possible to create an image on the sdcard or emmc and symlink it to /data/data and you could set the size of the file. Then the ramdisk would need to be modified and maybe a couple of things done on the rom. You asked for an easy way and this is one but not easy though. Bootmanager is pretty easy though and no coding changes need to be done to the roms and it will leave your original rom intact.
I've been wondering about this as well.
I've tried a couple different approaches, and ended up sticking with one: it takes some setup overhead for every ROM I install, but it helps a lot.
I ended up deleting the datadata mount from init.inc.rc in boot.img (get ROM, unpack, edit init.inc.rc, repack, flash), and booting in recovery mode to move the data from ([email protected])/ over to (mmcblk0p1)/data (which is now just a subdir on the 768MB /data partition.)
Initial tests repartitioning mmcblk0 (houses /data, /cache, and /emmc) to make /data larger for this purpose didn't work out well: the bootloader rewrites the MBR/partition table when it finds that they don't match metrics it likes. /emmc can not really be reformatted because the bootloader updates some bits that it expects to be FAT32 on boot time as well, corrupting other filesystems.
Why on earth HTC would ship a phone in this day and age with such a crippled storage layout is beyond me.
DHowett said:
I've been wondering about this as well.
I've tried a couple different approaches, and ended up sticking with one: it takes some setup overhead for every ROM I install, but it helps a lot.
I ended up deleting the datadata mount from init.inc.rc in boot.img (get ROM, unpack, edit init.inc.rc, repack, flash), and booting in recovery mode to move the data from ([email protected])/ over to (mmcblk0p1)/data (which is now just a subdir on the 768MB /data partition.)
Initial tests repartitioning mmcblk0 (houses /data, /cache, and /emmc) to make /data larger for this purpose didn't work out well: the bootloader rewrites the MBR/partition table when it finds that they don't match metrics it likes. /emmc can not really be reformatted because the bootloader updates some bits that it expects to be FAT32 on boot time as well, corrupting other filesystems.
Why on earth HTC would ship a phone in this day and age with such a crippled storage layout is beyond me.
Click to expand...
Click to collapse
That doesn't sound too difficult (i moved CM7 from emmc img to the actual phone partitions so that should be pretty simple). The only downside is you do lose space for apps (easily solved with apps2sd). I haven't seen you around since you posted your idea for multiboot. Been busy?
Well, the emmc method would be a loopback image which would not touch the fat32 filesystem.
Or if you're doing nightlies for instance once you mod the boot.img just add it to each new nightly.
Would Conap's dual boot work the same way? I am comfortable with this, and all the coding is intimidating for this newb. Would one of you smarter members put out a small guide as to exactly how to do this. I know it is time consuming, but it would really be worth it to us low lifes. Thanks
How can you do this?
DHowett said:
I've been wondering about this as well.
I've tried a couple different approaches, and ended up sticking with one: it takes some setup overhead for every ROM I install, but it helps a lot.
I ended up deleting the datadata mount from init.inc.rc in boot.img (get ROM, unpack, edit init.inc.rc, repack, flash), and booting in recovery mode to move the data from ([email protected])/ over to (mmcblk0p1)/data (which is now just a subdir on the 768MB /data partition.)
Initial tests repartitioning mmcblk0 (houses /data, /cache, and /emmc) to make /data larger for this purpose didn't work out well: the bootloader rewrites the MBR/partition table when it finds that they don't match metrics it likes. /emmc can not really be reformatted because the bootloader updates some bits that it expects to be FAT32 on boot time as well, corrupting other filesystems.
Why on earth HTC would ship a phone in this day and age with such a crippled storage layout is beyond me.
Click to expand...
Click to collapse
Wow, that sounds like a great idea. Like the above poster, can I also ask if someone who knows how would write up some instructions on how to to this? It certainly would be appreciated by many! With Gingerbread, there's not much Incredible users can do about the tiny /data size. Thanks!
I'm encountering this issue with 384MB of phone storage free and nearly 4GB of SD free. When I checked, I only had 14.5MB free in /data/data. 150MB for this is ridiculous! I would appreciate any fix, preferably one I can set and forget (don't want to have to constantly move or create symlinks for ever new app I install).
possible fix
You should check out jermaine151's Stock+ version 2.1. http://forum.xda-developers.com/show....php?t=1260994. I can't personally vouch for it as he just released it and it's a little late to start reinstalling everything, but it looks promising.
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
All of the new ICS roms talk in their instructions to partition your sd card. Some also have a non partition version for those that wish to not partition but those releases take longer to come out.
So why should I partition? I am asking in a general I really want to know why as on all of the rom release pages it just says to partition but no one every talks about why. Why do the newer roms require partitions while the 2.x Android roms never needed this.
Can't anyone let me know?
A lot of ROMs in 2.x support DarkTremor which allows many of the ROMs files to go onto a separate partition on the SD Card. This speeds up the phones response time as you run various apps.
This is most likely why the ICS builds are asking for you to partition the SD Card since they are automatically enabling this which is unlike the 2.. builds in which it was an option.
Doc
DocEsq said:
A lot of ROMs in 2.x support DarkTremor which allows many of the ROMs files to go onto a separate partition on the SD Card. This speeds up the phones response time as you run various apps.
This is most likely why the ICS builds are asking for you to partition the SD Card since they are automatically enabling this which is unlike the 2.. builds in which it was an option.
Doc
Click to expand...
Click to collapse
Is this new automatic thing part of ICS or just something differently the rom developers are now doing?
Was DarkTremor built into the 2.x roms? When I first moved from stock to Cyanogen all I remember doing was wiping and installing the zip file, never did anything extra.
LordJezo said:
Is this new automatic thing part of ICS or just something differently the rom developers are now doing?
Was DarkTremor built into the 2.x roms? When I first moved from stock to Cyanogen all I remember doing was wiping and installing the zip file, never did anything extra.
Click to expand...
Click to collapse
I believe that this is something being put in by the developers. The ICS you get from HTC, LG, Samsung etc.. does not have this.
DarkTremor was built into a lot of the 2.x roms and would only become active if you you had the SD Card partitioned properly. It is in Cyanogen but it is something that you did not need to use if you did not want to.
There are some good tutorials out there if you want to give it a try. The big advantages are that it speeds up your phone and frees up precious space on your internal memory.
Doc
I believe the simple answer is that ICS has a bigger footprint and therefore requires more internal system capacity. The phones that come stock with ICS have more system capacity than our EVO 4G. A2sd and an ext partition effectively expand the system partition so that these larger footprints will work on our phones.
Non-a2sd versions take longer because the dev has to figure out how to get ICS working with "insufficient" capacity.
Another development to look at is firerat's mtd mod that allows one to reconfigure the system, cache, and consequently data partitions.
Sent from my NookColor using Tapatalk 2
dcharleyultra said:
I believe the simple answer is that ICS has a bigger footprint and therefore requires more internal system capacity. The phones that come stock with ICS have more system capacity than our EVO 4G. A2sd and an ext partition effectively expand the system partition so that these larger footprints will work on our phones.
Non-a2sd versions take longer because the dev has to figure out how to get ICS working with "insufficient" capacity.
Another development to look at is firerat's mtd mod that allows one to reconfigure the system, cache, and consequently data partitions.
Click to expand...
Click to collapse
Thanks! That was exactly what I was looking for.
When people use in in GB roms is it just them trying to optimize things better by freeing up system memory by utilizing sd space?
LordJezo said:
Thanks! That was exactly what I was looking for.
When people use in in GB roms is it just them trying to optimize things better by freeing up system memory by utilizing sd space?
Click to expand...
Click to collapse
Yes, that's what I think.
Sent from my NookColor using Tapatalk 2
That is why I partitioned my drive (to move apps to my sd card and to free up space on the phone). I am on the MikG ROM.
Sent from my PC36100 using xda premium
1TonyC said:
That is why I partitioned my drive (to move apps to my sd card and to free up space on the phone). I am on the MikG ROM.
Click to expand...
Click to collapse
Why would you need to partition the sd card to move apps? That's a built in feature of GB.
Or do you mean system apps?
I was constantly getting alerts that I was running out of internal memory. This was after I transferred as many apps as I could to the sd card.
So I partitioned my sd card and flashed the MikG ROM. No more memory problems .
Sent from my PC36100 using xda premium
Partitioning for apps2sd is not to move ur apps to SD card. It will automatically install ALL apps downloaded from play store to the SD. No need to move anything! Its like adding internal memory to our phones! I was hesitant at first but now I wouldn't do it any other way. I noticed a nice increase in performance on ics roms and I can now download whatever the hell I want and not worry about bogging down my internal memory
Sent from my D.I.R.T.y CM9'd EVO 4G using xda premium!
Rather than posting a new thread, I'll ask my question here since it is somewhat relevant to the conversation.
I'm at work while I was updating to jmztaylor's latest nightly, so I do not want to backup my SD onto my work computer. Can apps2sd be flashed at any point after flashing the ROM or does it have to be at the same time as flashing the ROM?
Jaxp3r said:
Rather than posting a new thread, I'll ask my question here since it is somewhat relevant to the conversation.
I'm at work while I was updating to jmztaylor's latest nightly, so I do not want to backup my SD onto my work computer. Can apps2sd be flashed at any point after flashing the ROM or does it have to be at the same time as flashing the ROM?
Click to expand...
Click to collapse
It can be done later.
Captain_Throwback said:
It can be done later.
Click to expand...
Click to collapse
Great, thanks for the info!
The main difference between the built-in moving of apps and the partition is where the apps go.
With GB's moving (a2sd) the .apk file is moved to a directory on your SD card called .android-secure. The big con to this is that if your SD isn't mounted (for example, if you're moving files from your computer, or on the initial error check on boot), you can't access these apps. You also cannot use any widgets an app might have if it's been moved to .android-secure.
If you have a partition (ext3 generally) then it's a different story. Generally, what happens is that the /data/app directory in your internal storage is symlinked to your partition, /ext. (I think it's /ext/data/app, but I can't remember and haven't used the sd partition for a bit). Pros to this one are much more space, since assuming you have the space and your SD is fast enough you can also symlink your appdata and dalvik-cache. Plus, you are able to use widgets because Android thinks the apps are installed to the internal data. One major con is that you can potentially reduce your SD card's life, since it will be reading and writing a lot more from that portion of it.
And a symlink explanation: In a sense, it points one directory to another area of the filesystem. When I was partitioned Root Explorer showed my symlinked /data/app as this: "/data/app > /ext/data/app". It's a way to have parts of the filesystem "appear" in other areas without having to copy/paste. I've used it to get a few directories to sync to Dropbox without having to keep spare copies of my files in the main Dropbox ones.
Be careful. I just did it an hour ago and everything disappeared from my sd card. So pissed.
Sent from my PC36100 using xda premium
What are partitions..
SLB9884 said:
Be careful. I just did it an hour ago and everything disappeared from my sd card. So pissed.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
That is because when you re-partition your card (or hard drive,etc..) it basically wipes it. What you are doing is redefining the very volumes that take up space on your card and giving them a starting and ending block address based on the size of the card and the defined size of the partition. You can think of it has a two pieces of glass and you are pouring colored sand in. You pour red in and get your data partition, then you pour in green and get your swap partition so on. Eventually all partitions are defined and ideally will make the most use of the total space on your card.
So when you partition, it's very low level and requires abandoning all data and prior formats on the card unless you are using some special software that attempts to adjust the sizes of the partitions.
Somewhere at the beginning of your card is a small sector that lists all the partitions and their starting/ending blocks, plus other relevant informationj.
So if you plan to partition, you need to back up the data first to your pc or what not.
Storage
Because its an entire system you'll want to to save space on your card, make a backup of any important files because its gonna wipe it and you cant undo it
Here's a couple of great guides for a2sd. Once I finally did my phone performed much better.
http://therootofallevo.com/2011/04/10-step-guide-properly-set-darktremors-a2sd/
http://androplasty.com/2011/08/mini-guide-how-to-re-partition-your-sd-card/
Hello everyone,
I know I'm pretty new here but I have been digging these forums for a few days right now.
I recently bought a faster 16 GB SD Card and rooted my phone to install bigger and other ROM.
But I found verry little info (maybe I didn't looked has much or at the right place) about the swap space you can create in your sd card.
What I read was that it was usefull for the system but when I look at the differents ROM thread they never or very rarely talk about a needed swap place in the sd card partitioning.
Right now I created an ext4 partition with a little bit more than 1gb and a swap with +- 400 mb.
So my question is, is it really usefull or no?
ps: sorry for my english
Gil- said:
Hello everyone,
I know I'm pretty new here but I have been digging these forums for a few days right now.
I recently bought a faster 16 GB SD Card and rooted my phone to install bigger and other ROM.
But I found verry little info (maybe I didn't looked has much or at the right place) about the swap space you can create in your sd card.
What I read was that it was usefull for the system but when I look at the differents ROM thread they never or very rarely talk about a needed swap place in the sd card partitioning.
Right now I created an ext4 partition with a little bit more than 1gb and a swap with +- 400 mb.
So my question is, is it really usefull or no?
ps: sorry for my english
Click to expand...
Click to collapse
As far as I know, there are vrey few ROMs that require swap partition. It is usually requested in the first post of the ROM's thread.
Ciobby said:
As far as I know, there are vrey few ROMs that require swap partition. It is usually requested in the first post of the ROM's thread.
Click to expand...
Click to collapse
Ok, thanks !
I will re create my sd card then
Well after a few rom tested I'm not so sure about this...
Ok they never talk about swap space. But the general problem I have when I install a big rom with Android 4.x is that the memory is always full.
Therefore the phone becomes extremly slow when I launch a few applications.
The only solution I found is to install an app to manage the RAM and free some space. But even with this, I need more ram as it's almost alway full.
I will try with a swap of 512 Mo but I have no idea how other people can manage this.
If anyone have a tip about this, it would be great .
Gil- said:
Well after a few rom tested I'm not so sure about this...
Ok they never talk about swap space. But the general problem I have when I install a big rom with Android 4.x is that the memory is always full.
Therefore the phone becomes extremly slow when I launch a few applications.
The only solution I found is to install an app to manage the RAM and free some space. But even with this, I need more ram as it's almost alway full.
I will try with a swap of 512 Mo but I have no idea how other people can manage this.
If anyone have a tip about this, it would be great .
Click to expand...
Click to collapse
If you use the native a2sd scripts that come with 4.x ROMs, then that's your problem. Those scripts only move data/app to sd-ext, leaving the rest on internal. Most of the memory is occupied by dalvik cache.
This script should also move dalvik to ext. Try it.
http://db.tt/m4sQLDOI
Don't forget to backup first.
I never used a swap partition. I think there's no need for it.
abaaaabbbb63 said:
If you use the native a2sd scripts that come with 4.x ROMs, then that's your problem. Those scripts only move data/app to sd-ext, leaving the rest on internal. Most of the memory is occupied by dalvik cache.
This script should also move dalvik to ext. Try it.
http://db.tt/m4sQLDOI
Don't forget to backup first.
I never used a swap partition. I think there's no need for it.
Click to expand...
Click to collapse
Thanks for your anwser but right now I'm using this rom:
http://forum.xda-developers.com/showthread.php?t=2213033
And I already moved dalvik and data to sd in the installation. I tried every option there, only data, only dalvik and both. Only both is working.
But this doesn't change the RAM used (or maybe it's not so important that the RAM becomes full?)
I also tried other 4.x rom and moved everything but at some point I think there is too many info in the ram and the Desire becomes really laggy.
Gil- said:
Thanks for your anwser but right now I'm using this rom:
http://forum.xda-developers.com/showthread.php?t=2213033
And I already moved dalvik and data to sd in the installation. I tried every option there, only data, only dalvik and both. Only both is working.
But this doesn't change the RAM used (or maybe it's not so important that the RAM becomes full?)
I also tried other 4.x rom and moved everything but at some point I think there is too many info in the ram and the Desire becomes really laggy.
Click to expand...
Click to collapse
creating a 512MB swap partition is pretty much useless as most ROMs don't implement it. It's a redundant partition which could either be used as extra sd-ext for apps or FAT32 space for music etc. It can cause problems as well depending on the order of partitions.
Even if somehow it could be used, it won't suddenly turn the desire into a phone with 1GB RAM...that's not the way it works. In cases where it is used, only a small swap partition ~25-32MB to occasionally swap a few things in and out of memory. Even then whether it actually makes a difference is dubious imo.
I would recommend repartitioning from scratch again, remove the swap partition. You don't need it, and the ROM you're running won't recognise it's even there.
It's laggy not only because of RAM, and can't be solved by magically adding more of it . Android memory works differently as well, so free RAM is wasted RAM, you shouldn't have to monitor how much is free at any given time. A big part of the lag is simply because it's a JB ROM which is simply very resource heavy on the desire relative to GB ones.
eddiehk6 said:
creating a 512MB swap partition is pretty much useless as most ROMs don't implement it. It's a redundant partition which could either be used as extra sd-ext for apps or FAT32 space for music etc. It can cause problems as well depending on the order of partitions.
Even if somehow it could be used, it won't suddenly turn the desire into a phone with 1GB RAM...that's not the way it works. In cases where it is used, only a small swap partition ~25-32MB to occasionally swap a few things in and out of memory. Even then whether it actually makes a difference is dubious imo.
I would recommend repartitioning from scratch again, remove the swap partition. You don't need it, and the ROM you're running won't recognise it's even there.
It's laggy not only because of RAM, and can't be solved by magically adding more of it . Android memory works differently as well, so free RAM is wasted RAM, you shouldn't have to monitor how much is free at any given time. A big part of the lag is simply because it's a JB ROM which is simply very resource heavy on the desire relative to GB ones.
Click to expand...
Click to collapse
Thanks for the informations.
Right now I only have an Ext4 of 1 Gb + 15 gb in Fat32. I didn't had the time to recreate the partitions again. So won't do it.
Well I thought it was a RAM issue because without the ram manager app some functions becomes hard to load like.
If I receive a call the phone rings but wait some time before loading the info to display about the call.
Or if I want to answer an sms the keyboard takes time to load.
Same thing with the apps.
With the ram manager it generally loads faster but some time it gets buggy because there is too much work to do to free space (I suppose).
Well that leave me not alot of options about the capacities of the phone .
Maybe just go back to 2.3.x
I have 1.8GB of free space on my SYSTEM partition. Is there any way to shred that down so I can have more space on my DATA partition?
I'm running cm12.1 on my t805
slobodan0104 said:
I have 1.8GB of free space on my SYSTEM partition. Is there any way to shred that down so I can have more space on my DATA partition?
I'm running cm12.1 on my t805
Click to expand...
Click to collapse
As far as I know it is not possible because system partition size is fixed in source of the ROM. Theoretically it could be done but I am not sure if custom recovery also needs to be customised like ROM? I think best solution would be to buy large sdcard (64GB) ?
T.
Sent from my SM-T805 using Tapatalk
It is somewhat possible to resize partitions by adjusting the parameters in the pit file.
However how risky this is for the sake of what, 1.5gb, I don't know?
The better option, if you don't want to waste that space, is to use it.
Move your apps from user to system apps.
Its easy enough to do and can be accomplished with little effort using apps already available and with the bonus of gaining the extra space on the data partition.
Thanks guys. I just moved some of my bigger apps to system partition.