Why does my system ROM say it only has 324MB of space? It is almost full?
Im running Navalynt's cherryblur? My internal ROM is still 2GB and has plenty of space but I was installing an app and it said insufficient storage?
Thanks
Sent from my MB860 using XDA App
tykazowsky said:
Why does my system ROM say it only has 324MB of space? It is almost full?
Im running Navalynt's cherryblur? My internal ROM is still 2GB and has plenty of space but I was installing an app and it said insufficient storage?
Thanks
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
..Mine too..
on my HTC Amaze 4G, at least 250 MB ROM memory is needed before the "insufficient memory available" bug appears everytime you install an app. As soon as you move apps to external memory in order to save ROM memory, your apps will start to lose integrity and the whole android experience will suck. HTC Amaze 4G has 2.5 GB ROM in total, apparently HTC one S has ~2.2 GB ROM in total but with the same number of apps, one S can achieve 1.8 GB free ROM memory. Correct me if I'm wrong, One series users. There must be something wrong with Amaze's ROM memory utilisation.
otivaeey said:
on my HTC Amaze 4G, at least 250 MB ROM memory is needed before the "insufficient memory available" bug appears everytime you install an app. As soon as you move apps to external memory in order to save ROM memory, your apps will start to lose integrity and the whole android experience will suck. HTC Amaze 4G has 2.5 GB ROM in total, apparently HTC one S has ~2.2 GB ROM in total but with the same number of apps, one S can achieve 1.8 GB free ROM memory. Correct me if I'm wrong, One series users. There must be something wrong with Amaze's ROM memory utilisation.
Click to expand...
Click to collapse
Wrong manufacturer, wrong phone model, wrong forum!!!
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?
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.
Uh, so yeah. Pretty sure I'm missing a pretty big chunk of my storage space. I currently have the Nexus 4.4.4 ROM flashed, and I'm only showing about 11 gigs of total storage space, with approximately 6 gigs available. I thought I had removed all of the rom slots in Safestrap awhile back, but perhaps not. I have no backups saved either, according to TWRP.
Is there anyway to determine where this other ~5 gigs of space is tied up, like a partition?
Thanks in advance.
PariahNine said:
Uh, so yeah. Pretty sure I'm missing a pretty big chunk of my storage space. I currently have the Nexus 4.4.4 ROM flashed, and I'm only showing about 11 gigs of total storage space, with approximately 6 gigs available. I thought I had removed all of the rom slots in Safestrap awhile back, but perhaps not. I have no backups saved either, according to TWRP.
Is there anyway to determine where this other ~5 gigs of space is tied up, like a partition?
Thanks in advance.
Click to expand...
Click to collapse
Nexus rom will show ~11.4Gb total on a 16Gb device. The balance is a fixed allocation (partition) used for system files and can not be easily adjusted. The values will be similar for CM11 and FireOS.
Sounds like storage allocations are as they should be assuming it's a 16Gb model.
Is it still possible to increase the RAM size of the Poco F1? I have the 6gb/128gb variant and I want to have maybe 2 to 4gb more RAM. I read around that it can be done with a swap file on older phones but I already tried that and even added up to 6gb but it doesn't seem to get used. Is there a custom ROM or magisk zip that can be used for that? My phone currently runs on Corvus with NGK.
The reason why I want more RAM? Egg NS. My phone frequently runs out of RAM and the game force closes.
Thanks!
Oyee said:
Is it still possible to increase the RAM size of the Poco F1? I have the 6gb/128gb variant and I want to have maybe 2 to 4gb more RAM. I read around that it can be done with a swap file on older phones but I already tried that and even added up to 6gb but it doesn't seem to get used. Is there a custom ROM or magisk zip that can be used for that? My phone currently runs on Corvus with NGK.
The reason why I want more RAM? Egg NS. My phone frequently runs out of RAM and the game force closes.
Thanks!
Click to expand...
Click to collapse
What are these apps and games you use?
How do you fill the entire memory?
I switched to LineageOS + NGK because it's more stable. So far I only have DamonPS2 and Egg NS installed after flashing the ROM. Had no problems with DamonsPS2 even with stock ROM. Anyway, I said before the app in question is Egg NS, a switch emulator. The app needs 8gb RAM so the Poco F1 is short of 2gb that's why it force closes randomly. I get smoother framerates compared to stock but then I still run out of RAM.
Well, short of swapping the DRAM modules for bigger ones it would be impossible, and even then who knows if it would work?
Although now that you've posted this question, I'm left wondering if anyone has successfully done this… I know that Scotty from Strange Parts (and others) have swapped NANDs for bigger storage, but RAM I've never seen.
I think ram is included in the SOC, which means cpu, gpu, controllers, everything else will be also replaced if someone were to upgrade ram, basically changing the core of the phone.
I'm trying to make it work like this one. A really old post from 2012 so I doubt it'll still work for Android 10.
https://forum.xda-developers.com/showthread.php?t=1659231
Oyee said:
I'm trying to make it work like this one. A really old post from 2012 so I doubt it'll still work for Android 10.
https://forum.xda-developers.com/showthread.php?t=1659231
Click to expand...
Click to collapse
In that case why don't you try zRAM instead? Depending on the kernel your zRAM (or swap, for that matter) capabilities may differ, but give it a go!
IDK about other kernel utility apps, but EX Manager has the options.
Ok I'll give that one a try. Just tried Roehsoft RAM expander and it still works but the game runs really slow when it's already using the swap memory. At least it doesn't force close now. lol