[Q] Stock ROMs vs custom size - Verizon Samsung Galaxy S 4

There doesn't seem to be a lot of real function in the stock rom vs AOSP. The air gestures are a barely working gimmick, the added apps are almost 100% useless but what gets me is the size of the ROMS, almost 2GB for full stock and around 1.2GB for a "debloated" when the AOSP ROMS are from 150-200MB.
As I understand it the size difference doesn't matter though because the partition structure doesn't change when switching roms so the space savings is just wasted.
Is there a way to actually recover this space?
What I would like most is as much space as possible be available as primary and the fake sd card to be as small as possible (so i can really use the 64GB sd card) and the ROM partition to be as small as possible.
Is this just a pipe dream or is this a real possibility?

Related

Custom ROMS and Memory

Greetings,
Please forgive me if this is a stupid question or the wrong thread.
I am curious about memory allocation in Custom ROMS. I have an ATT Fuze and the Stock ROM stripped of junk had over 200MB of Program memory available. It seems like most of the Custom ROMs on this forum only start with 120MB or so.
It seems like most of the Custom ROMS all focus on the amount of Storage available rather than Program memory. With SD cards being priced so low that they are almost free, why is there more focus on Storage rather than Program memory? The phone cost close to $1,000 but I have an 8GB storage card that cost me $10.
I have migrated from an eTen X500 where I always struggled to find ways to free up program memory. Here it seems like there is no interest in program memory, only storage.
Not being critical, just curious about what I am missing.
Thanks for any advice.
Doug M.
You are in the wrong thread just so you know for future reference, but I'll answer your question. Many of the cooks do try to get you as much program memory as possible, and if you look on the threads for cooked roms, you'll find that they usually post the numbers for both. Several of the cooks also have a few different versions of their roms, so you can choose a lighter version that gives you more program memory. That being said, the TP already has tons of memory and gives you enough room to install tons of programs, especially if you're running a cooked rom.
There is only so much you can squeeze out of the Program Memory. I may be wrong but the Program Memory acts like memory cache for running programs. About the only way you can lower Program Memory is from removing files from the payload when you dump it and by moving around the different partitions to recover unused space. When I build my ROMs I have been using 16MB pagepool which eats away from the program memory but increases the quickness of windows a bit.
Storage on the other hand is so much easier to gain back...

Enlarge CM7 partition

Is there a way to enlarge CM7's sdcard partition?
Since CM7 i dont use WebOS at all and dont plan to use it in the future.
Im hoping once everything is stable there will be a utility to blow out the while webos I really don't need to os's too
Sent from my Nexus S 4G using Tapatalk
http://forum.xda-developers.com/showthread.php?t=1312049
The sdcard partition is shared between the two OSes so you have access to everything from both. The WebOS boot partition is small and doesn't take up much space. And with 3.0.4 it seems to be running smoother without OC, and battery lasts longer (for me at least) than CM7.
Plus, from CyanogenMod original FAQ:
WILL YOU TELL ME HOW TO REMOVE WEBOS ENTIRELY?
Nah. We like WebOS. Furthermore, we don't recommend removing it. In future it may be needed for updates and such. Plus it doesn't take up much space, and you may find yourself wanting to give it a second look some day
I dont want to remove WebOS, i just want to have more space for CM7
Do you _really_ need the extra ~500MB?
I think WebOS is marvellous. If it wasn't for the fact that a couple of apps I want to use are only on Android, I'd stick with it, largely for the fact that the battery lasts for ages and the cards system is so nice to use.
Thats all 500MB? I've got the 16Gb version and the virtual sdcard has like 6-7Gb total space. Where did the rest go?

[Q] Size of ROM:slots in Safestrap

If I just use one ekstra rom slot to the Stock:Slot
How big should this be? What is the benefits or drawbacks to a bigger Rom:slot to a smaller?
If I choose the maximum size of a Rom slot wich is 3Gb, does this mean that 3 GB is all I have to install my apps, store pictures and everything else?
Also wondering about the stock Rom slot?
Does this take up the up the same amout of space always? Even if choose rom slot one and do a system format on it?
I always leave the stock slot as-is and test out different ROMs on slot one as 1GB. Haven't seen any performance differences or otherwise problems with increased slot size. 1GB seems to be fine for every ROM I've tested.
Sent from my DROID RAZR using Tapatalk 2
mr.lysgaard said:
If I just use one ekstra rom slot to the Stock:Slot
How big should this be? What is the benefits or drawbacks to a bigger Rom:slot to a smaller?
If I choose the maximum size of a Rom slot wich is 3Gb, does this mean that 3 GB is all I have to install my apps, store pictures and everything else?
Also wondering about the stock Rom slot?
Does this take up the up the same amout of space always? Even if choose rom slot one and do a system format on it?
Click to expand...
Click to collapse
I'm not 100%, but I'm pretty sure its only for your apps and app data. You will lose approximately 3GB from your internal storage or whatever amount you chose.

the CM, AOSP etc ROMs getting better and better...

One of the main reasons for using the stock ROMs is for stability etc. I know, I tried the earlier custom (CM, AOSP AOKP etc. ones) and there was always something not right... my reason for wanting to use the custom ROMs was simple... size, the average stock ROM is between 1gig and 1.6 gig (with some levels of de-bloating) and a full stock ROM is about 2gig. and given we (on the 16gig versions of the G2) only have about 10gig to 'play with' means that with your nandroid backup and titanium backup you'll be lucky to have 2 or 3gig for stuff. with the CM based or AOSP ROMs etc. you are looking at a ROM size of about 250mb incl. GApps... so you save a LOT of space (nandroids, titanium etc are way smaller) and now you have about 5gig odd available, much better.
I've tried Nameless and ProBam (SlimKat RC2 is still buggy on 802) and they are both rock solid and have better battery life than any stock ROM (I was getting 40 to 55 hrs with stock and I easily get to 70 odd hours now with the custom ROMs). So I really just wanted to say a massive thanks to the developers, for taking the time and effort to get the customs ROMs to where they are, its much appreciated!
Make donation.
Jostian said:
One of the main reasons for using the stock ROMs is for stability etc. I know, I tried the earlier custom (CM, AOSP AOKP etc. ones) and there was always something not right... my reason for wanting to use the custom ROMs was simple... size, the average stock ROM is between 1gig and 1.6 gig (with some levels of de-bloating) and a full stock ROM is about 2gig. and given we (on the 16gig versions of the G2) only have about 10gig to 'play with' means that with your nandroid backup and titanium backup you'll be lucky to have 2 or 3gig for stuff. with the CM based or AOSP ROMs etc. you are looking at a ROM size of about 250mb incl. GApps... so you save a LOT of space (nandroids, titanium etc are way smaller) and now you have about 5gig odd available, much better.
I've tried Nameless and ProBam (SlimKat RC2 is still buggy on 802) and they are both rock solid and have better battery life than any stock ROM (I was getting 40 to 55 hrs with stock and I easily get to 70 odd hours now with the custom ROMs). So I really just wanted to say a massive thanks to the developers, for taking the time and effort to get the customs ROMs to where they are, its much appreciated!
Click to expand...
Click to collapse
I don't know how you are gaining that much space? The system partition is a fixed size of about 2.7gig. You're not going to gain any of that back.
Good to know the ROMS are stable though... I've only just got the device and set it up the way I like it on stock.. I thought I'd give the custom roms some time to let the bugs get ironed out
baileyjr said:
I don't know how you are gaining that much space? The system partition is a fixed size of about 2.7gig. You're not going to gain any of that back.
Click to expand...
Click to collapse
Aside from dalvik cache, yeah, this.. You get no space back if /system is full or empty..
What about gaming on aosp Roms? I tried to play granny Smith and angry birds go and I couldn't get to the game play without It FCing
Sent from my LG-D800 using Tapatalk
baileyjr said:
I don't know how you are gaining that much space? The system partition is a fixed size of about 2.7gig. You're not going to gain any of that back.
Click to expand...
Click to collapse
khaytsus said:
Aside from dalvik cache, yeah, this.. You get no space back if /system is full or empty..
Click to expand...
Click to collapse
Not so much on the reading comprehension. Emphasis added.
"your nandroid backup and titanium backup you'll be lucky to have 2 or 3gig for stuff. with the CM based or AOSP ROMs etc. you are looking at a ROM size of about 250mb incl. GApps... so you save a LOT of space (nandroids, titanium etc are way smaller)"
Stock camera is the reason I stick to stock ROMs
Sent from my LG-D802 using xda app-developers app
nagel said:
Stock camera is the reason I stick to stock ROMs
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
You can use the LG camera app on AOSP ROMs.
Sent from my Nexus 5
on the 16gig model we have access to about 10gig (for our stuff), so if I do a nandroid with a stock rom your nandroid is quite big (mine was 2.7gig), and if you keep a copy of the rom on your phone for emergencies (which I do thats another 1.5 gig odd, depending on which stock rom you use), so together those 2 = about 4gig, if I use a custom rom like nameless or probam, the rom incl. Gapps is 220mb vs 1.5gig and my nandroid is just over 1gig vs 2.5gig, thus I have at least 2gig more available space using a custom rom. my titanium backups are around 30% smaller too depending on what you backup. so instead of having 2.5 gig available after I have my phone setup like I want I now have just under 5 gig available...makes a difference for sure.
Jostian said:
on the 16gig model we have access to about 10gig (for our stuff), so if I do a nandroid with a stock rom your nandroid is quite big (mine was 2.7gig), and if you keep a copy of the rom on your phone for emergencies (which I do thats another 1.5 gig odd, depending on which stock rom you use), so together those 2 = about 4gig, if I use a custom rom like nameless or probam, the rom incl. Gapps is 220mb vs 1.5gig and my nandroid is just over 1gig vs 2.5gig, thus I have at least 2gig more available space using a custom rom. my titanium backups are around 30% smaller too depending on what you backup. so instead of having 2.5 gig available after I have my phone setup like I want I now have just under 5 gig available...makes a difference for sure.
Click to expand...
Click to collapse
OK now I understand, its because you are keeping a copy of the system partition contents, as a nandroid, on the data partition :good:
baileyjr said:
OK now I understand, its because you are keeping a copy of the system partition contents, as a nandroid, on the data partition :good:
Click to expand...
Click to collapse
I guess there is no way (yet) to get access to any of the 'locked' 6 gig? is there another option(s) to minimize the loss of space, just curious in case someone is doing something better, more efficient in terms of available space, thanks
dallashigh said:
Not so much on the reading comprehension. Emphasis added.
"your nandroid backup and titanium backup you'll be lucky to have 2 or 3gig for stuff. with the CM based or AOSP ROMs etc. you are looking at a ROM size of about 250mb incl. GApps... so you save a LOT of space (nandroids, titanium etc are way smaller)"
Click to expand...
Click to collapse
Nandroid will be smaller yes. Tibu, not at all. Who backs up system apps in tibu?
Jostian said:
I guess there is no way (yet) to get access to any of the 'locked' 6 gig? is there another option(s) to minimize the loss of space, just curious in case someone is doing something better, more efficient in terms of available space, thanks
Click to expand...
Click to collapse
Some of that 6gig is lost in the formatting, 16Gb is the unformatted space. The system partition will remain the same size. However if you use something like "Nandroid manager" from the play store you can restore apps from the nandroid so you shouldn't need to back them up in TB, you could save space by just backing up the most recent data for your user apps
You do have the option to convert user apps to system apps in TB so you may want to play around with that. I'm "assuming" that will move them from the data partition to the system partition. Im not 100% on that but you could always just move one and check.... Having said that the apk's themselves are usually relatively small, its the data stored in Android/Data that usually account for most of the install size.
Few ideas there for you anyway, other that that your obviously better off with a 32gig version. After my apps installed, 1 Nandroid, some local music, and user apps backed up in TB I have approx 15gb free.
Here a comparison between CM10.2 and stock rom, I have about 2gb more free space for data.
I think partitions are dynamic and not fixed.

How to reclaim unused Android System space in internal storage?

I have no real knowledge of the workings of the Android OS, so please forgive me if I'm asking stupid questions.
I'm on MM, internal storage reports that the Android system is taking up 9.42GB of space.
However, after deleting various Sony and Google bloat in /system, I found that it STILL reports 9.42GB used.
I am positively sure I deleted hundred of MB of files, so I highly doubt that's the real number.
I presume that 9.42GB is actually just the size of the partition reserved for the Android system, as opposed to the actual size of files taking up space.
If true, then there must be lots of potentially wasted free space on there that I could use.
How do I reclaim the unused space? Is there a tool to easily do it? I couldn't find any information related to Xperias, most were discussing Nexuses.
I'm rooted, so I don't have FOTA concerns. I don't necessarily need to reclaim every single bit that's not used if it's wise to leave a certain amount of free space for the OS to work with.
But if say it's only really using 4GB, and needs 1GB extra, then I'd like the remaining 4GB back.
If it affects or prevents me from updating to future stock firmware releases, please also let me know.
Thanks!

Categories

Resources