[Q] Q]does installing roms reduce internal storage capacity - Android Q&A, Help & Troubleshooting

i know that this is a rather foolish question.but i am 13 years old and i really want an answer.this is the only place i think to find an answer.
i know that our android phone has a specified amount of internal storage.part of it is for storing apk,datas etc.another part is for rom image and all all those stuff.what i want to know is when i am installing a new rom,is it actually overwritting the existing rom.or is it installed alongside it.cause my phone is getting slower each time i install a new custom rom in my htc hero.it has 600 mhz processor.but even angry birds lag in my phone but it works smooth on my nokia 5233 xpress music touch phone.both these games are are of similar size and have same graphics quality.

No the previous rom is over written or in most cases deleted when you carry out the full wipe/delete.
The hero is an old phone and as time goes on and software evolves ect.. it also become larger in size in most cases, if you are after speed, keep away from sense roms, and generally the older the rom the better in terms of performance/free space ect..
I used to own a hero and "eleinux" (i think his name is) had a good rom called speedmachine which was a pretty good rom for the hero while still having some ports from cyanogen, if you really want a sense rom the maybe look up villainrom as they are pretty good at gutting out all the crap within sense. You could always try over-clock your CPU as-well with setCPU or if you have a cyanogen based rom there is a function within there that will allow you to over-clock.
Other than that the hero is a very dated phone, might be time to consider a new one or newer one.

no. your internal memory never ever gets reduced. if u are rooted. u can use apps like setcpu to increase speed by overclocking(at the cost of lil battery life)
you can virtually increase yout internal memory by partition ur sdcard with ext4,3
Sent from my Nexus One using Tapatalk

...and I thought my phone was old.
Your phone is outdated, it will slow down with age. Be sure to fully wipe when flashing roms. At the minimum, wipe caches. If you haven't in a while, you should wipe everything before flashing your next rom. Really you should do a full wipe with each rom flash unless flashing an update.
Try out the V6 Supercharger script for a bit more speed, that should help some. You can buy used phones for less than $50 that are better than yours, like the Evo 4G.

I've heard good things about villianrom as well, so I did some searching for you and found this link
http://forum.xda-developers.com/showthread.php?t=654030
hope it helps, it's very important to do a full wipe of your phone before you install new roms.

Related

Which rom?

Hi,
Hello,
I've been trying to read around but I ended up with nothing.
Can anyone offer suggestions for which ROM i might use.
I've been on stock HC, but got bored with slow speeds and skype playing up... So I just s-off and install stock GB.
Really I want a nice smooth ROM, ideally with pen, hw buttons and root. I don't need any specific OS. But I can't seem to find many non-'stock ROMs that cater for pro-grade which is very important for me.
Any suggestions please. Its late and I've run out of steam for looking.
Thanks,
S.
I'm usually not a fan of "what is the best ROM" threads. But seeing as activity is close to nothing on this forum for some time right now, there aren't really any active threads on the topic, so it seems like a valid question.
When I first switched to HC (must have been way back in late 2011) it seemed to perform close to as smoothly as GB. Really not much different at all in smoothness (insignificant really), despite some people's claims that HC is so laggy compared to GB. Now, I feel the tablet is super laggy. But I think it has more to do with now owning a One X phone since may, which is so much faster, and much better CPU specs. Faster than any Android device on the market when it was released.
At first I thought maybe the ROM had just slowed down over time, and bogged down with processes, apps etc. So I did a full data wipe, and flashed the newest version of the custom ROM I was on. And the performance did not change. So I really do think its just a perception thing.
Now I'm digressing quite a bit from your question. I played around with a few ROMs here and there (mostly earier in the year) and settled on HoneySense. It gives you the option to turn the hardware keys back on, and some other cool features. I don't feel that it makes the tablet any less laggy, even overclocked (maybe just a tiny bit). But I did seem to have a decent gain in idle battery life, which is certainly a good thing.
HC version of LeeDroid is pretty good too. But the app drawer was just too crowded for me. I think the dev was going to make some mods for different app drawer layouts to remedy this, but it never happened AFAIK. Its just a personal taste, you might think its fine.
I also tried the Sense version of IOIDroid for a short time. It had some real potential. Not sure how the dev did it, but it seemed significantly smoother than HoneySense. But there was a few things that were deal breakers for me. It has the AOSP keyboard, (I found this choice a bit odd, since there is also a "Senseless" version of this ROM)where I really prefer the Sense one. Also, I could not get Gmail working, which is a must have for me. Wouldn't even let me install it from the Market.
I never got into the ICS or JB ROMs. Still too many things not working quite right. Development has slowed. But hopefully the dev (Dexter) has not completely left our device.
For fast, lag free and all stuff working use FlyHIGH GB rom. Ull limit yourselves with apps for HC / ICS but hell, rom runs great. I did try HC Leedroid, ICS XXL and JB, LeeDroid GB and ofc stock GB and stock HC. FlyHigh is best for mine usage since on top off all i need phone calls via BT. With good setup ull have good tab look even on GB. I also find out HW keys r awsome compare to HC/ICS/JB low menu buttons. I am missing those a lot on SGT2.
jprednik said:
For fast, lag free and all stuff working use FlyHIGH GB rom. Ull limit yourselves with apps for HC / ICS but hell, rom runs great. I did try HC Leedroid, ICS XXL and JB, LeeDroid GB and ofc stock GB and stock HC. FlyHigh is best for mine usage since on top off all i need phone calls via BT. With good setup ull have good tab look even on GB. I also find out HW keys r awsome compare to HC/ICS/JB low menu buttons. I am missing those a lot on SGT2.
Click to expand...
Click to collapse
Is have to use Bluetooth headset for making the phone call on GB 2.3.4 stock Rom on Flyer?
Is any one use Flyer to make phone call without BT as the way cell phone did?
Is FlyHIGH GB rom still need to use the BT to make the phone call?

(Sola) (Q) RAM Usage on Gingerbread?

Yep, this is still a problem.
I just noticed my that Sony may have been right in directing me to check available RAM on ICS. I have a tiny amount of RAM available and had to delete many apps, still the phone doesn't run smoothly.
Anyone here still on Gingerbread? What's your available RAM like? Roughly, how many apps do you have installed? I may switch back, I've had enough.
I can see why this happened:
http://www.androidauthority.com/o2-sony-xperia-ray-arc-neo-ics-update-112137/
Flashing time maybe
SharpnShiny said:
Yep, this is still a problem.
I just noticed my that Sony may have been right in directing me to check available RAM on ICS. I have a tiny amount of RAM available and had to delete many apps, still the phone doesn't run smoothly.
Anyone here still on Gingerbread? What's your available RAM like? Roughly, how many apps do you have installed? I may switch back, I've had enough.
We do not have the same phones so i do not know if the following is relevant or even possible for you. I recently flashed the ics333 rom with a semaphore kernel on my Galaxy SI and it really flies. If i have understood correctly the semaphore kernel frees up extra ram. I now have on average 140-170Mb available instead of 30-60Mb It makes such a difference. even games like Temple Run which i could not play before work without lag.
You should maybe consider flashing an optimised rom, if available.
Click to expand...
Click to collapse
A better kernel, or simply a custom ROM, I appreciate your help! :victory:
I came back from my first trip to Paris and my camera app kept freezing, it drove me crazy. I'll definitely look into the kernels.
SharpnShiny said:
Yep, this is still a problem.
I just noticed my that Sony may have been right in directing me to check available RAM on ICS. I have a tiny amount of RAM available and had to delete many apps, still the phone doesn't run smoothly.
Anyone here still on Gingerbread? What's your available RAM like? Roughly, how many apps do you have installed? I may switch back, I've had enough.
I just switched back to GB stock ROM (184 kernel) after having tried ICS stock and xICS Hybrid ROM. In both the ICS based ROMs , I found that the battery usage is quite high (both normal usage and standby) . Also the phone started freezing after a certain number of apps were launched. I face no such issues in GB Stock ROM and it is quite fast too. Also Sony has done a good work wid UI esp. Gesture based typing and word predicition(which is quite accurate)
I have around 12-15 apps installed and I use most of them regularly yet I always have around 90-120 MB of free RAM and I have never run into issues with free RAM as such.
Also, while using ICS receiving a call used to be laggy esp when you are in middle of something and u get a call but GB is quite good in that respect. So I can safely suggest GB is well suited for Sola . Go for ICS only if you need a feature specific to it or if you are too crazy about new UI. Hope this helps a bit :laugh:
Click to expand...
Click to collapse
That really helps, thanks! :good:
I couldn't remember much about RAM usage on GingerB but I knew that I didn't have that freezing problem with apps or with phone calls etc. On ICS, I checked my RAM and it was constantly around 20MB, I never imagined I'd be the person that installed too many apps for the RAM to handle. I think Sony made some poor decisions re: RAM and OS upgrade.
Thankfully we can backup our ROMS so easily so I think I'll go back to Gingerbread.
SharpnShiny said:
That really helps, thanks! :good:
I couldn't remember much about RAM usage on GingerB but I knew that I didn't have that freezing problem with apps or with phone calls etc. On ICS, I checked my RAM and it was constantly around 20MB, I never imagined I'd be the person that installed too many apps for the RAM to handle. I think Sony made some poor decisions re: RAM and OS upgrade.
Thankfully we can backup our ROMS so easily so I think I'll go back to Gingerbread.
Click to expand...
Click to collapse
Juts to add to my last post, After switching back to GB I found that the battery usage (on standby ) overnight dropped to 3% from 30-40% in case of ICS based ROMs :laugh:

CM7.2 issues/Recommendations for Daily Driver ROM

Well, due to unexpected turn of events, I am using an HTC Aria as my daily driver phone on Net10, S-OFF and currently running the last CM7.2 Nightly ROM with the included kernel (Max clock 768/Min 245, OnDemand and tried Interactive) and I have been getting daily reboots, not really bad but annoying. Any thoughts on cleaning up the reboots, is the Official Stable version better? I am running at 25 MB free consistently after moving everything to the SD card that can be moved, could this be part of the reboot problem?
Is there a better daily driver ROM, perhaps one with more internal storage free or one that uses the external SD as it's primary storage (acts as internal storage)? Thoughts on MIUI or something else? What is everyone who is still using the Aria using as their daily driver ROM?
I know this is very much a legacy device, but for the next few months at least I need to make this work fairly solid and I really don't like the stock ROM with all it's bloat
I'm not using my Aria anymore, but I gave mine to a friend, and it had the latest CM10 rom(not CM10.1) on it by WinSuk. So far it hasn't been giving him any problems. Maybe you should give CM7.2 Stable a shot before trying CM10 out though, since there are some bugs on CM10. Have you tried using Links2sd or moving the dalvik cache to the sd card for more storage space?
aster190 said:
I'm not using my Aria anymore, but I gave mine to a friend, and it had the latest CM10 rom(not CM10.1) on it by WinSuk. So far it hasn't been giving him any problems. Maybe you should give CM7.2 Stable a shot before trying CM10 out though, since there are some bugs on CM10. Have you tried using Links2sd or moving the dalvik cache to the sd card for more storage space?
Click to expand...
Click to collapse
I have been using DroidSail's App2SD thinking it was the same thing, but I am learning it is very different. I will look into that, thanks. I was short on time yesterday so tried to dirty flash back to CM 7.2 Stable, but it was rather... umm... unsuccessful... Had to nandroid back, when I get some more time this weekend I will probably try again with a clean flash, maybe CM10, and perhaps MIUI as well. Thanks again!
EDIT: Interesting, last night around 7pm I changed the Max Clock speed to 787 MHz instead of 768, and dropped an app I didn't need freeing up 15MB of space (maintaining 41MB free on average), much smoother operation of the phone all around and no reboots in almost 24 hours. Note sure if the extra space helped or changing the clock speed, but seems to make a difference. I would assume that 787 uses a slightly different bus speed than 768 rather than a multiplier change so that alone could make a huge difference if I was at the edge of what the HW could take.
Edit 2: Nvm... it still reboots, back down to 600 MHz max for now.
acejavelin said:
I have been using DroidSail's App2SD thinking it was the same thing, but I am learning it is very different. I will look into that, thanks. I was short on time yesterday so tried to dirty flash back to CM 7.2 Stable, but it was rather... umm... unsuccessful... Had to nandroid back, when I get some more time this weekend I will probably try again with a clean flash, maybe CM10, and perhaps MIUI as well. Thanks again!
EDIT: Interesting, last night around 7pm I changed the Max Clock speed to 787 MHz instead of 768, and dropped an app I didn't need freeing up 15MB of space (maintaining 41MB free on average), much smoother operation of the phone all around and no reboots in almost 24 hours. Note sure if the extra space helped or changing the clock speed, but seems to make a difference. I would assume that 787 uses a slightly different bus speed than 768 rather than a multiplier change so that alone could make a huge difference if I was at the edge of what the HW could take.
Edit 2: Nvm... it still reboots, back down to 600 MHz max for now.
Click to expand...
Click to collapse
I still use my aria as a media player, and keep it as a spare phone. CM9 and 10 were both nicely stable for me, but at this point you pretty much have to run an apps to ext partition solution due to the current size of apps and lack of internal space on the device. In any case, mine has always had random reboot issues if I overclock past 768, on any ROM.
I have CM10.1 on there now... but I can't get s2e to work with it (my old standby for apps to ext) and link 2sd seems to be misbehaving, or I don't know how to use it correctly. I'm going to go back to either cm10, or maybe a stock based froyo rom if I can track one down, just for the heck of it. What I want is attn1's liberated fr008.
Good luck.
Sent from my Optimus G using Tapatalk 4

Trying to get CM10.1 bootloop though

I have Samsung drivers
atlas 2.2
odin 1.3
gbbootloaders
cmw4 fixed for cm7
CI500_VZW_EH03_GB_CM
and mutliple releases of CM10.1
I followed instructions exactly how [GUIDE] Installing a Rom/CWM recovery/Root or going back to Stock say to do.
I always end up with a bootloop after flashing. The instructions are flawed. Or, one or more files are corrupted.
fewert said:
I have Samsung drivers
atlas 2.2
odin 1.3
gbbootloaders
cmw4 fixed for cm7
CI500_VZW_EH03_GB_CM
and mutliple releases of CM10.1
I followed instructions exactly how [GUIDE] Installing a Rom/CWM recovery/Root or going back to Stock say to do.
I always end up with a bootloop after flashing. The instructions are flawed. Or, one or more files are corrupted.
Click to expand...
Click to collapse
Did you look at my post which further explains the process.
http://forum.xda-developers.com/showthread.php?p=53235945
Have you installed cm10.1 multiple times?
Some times it doesn't always set thing up in one flash
hhp_211 said:
Did you look at my post which further explains the process.
http://forum.xda-developers.com/showthread.php?p=53235945
Have you installed cm10.1 multiple times?
Some times it doesn't always set thing up in one flash
Click to expand...
Click to collapse
Yeah I read a post saying to do what you just described with success.
However, this phone is really poor. I have tried GB, ICS, JB and all of them I get similar performance just different features.
The phone can't handle two apps at once regardless of the rom.
I was traveling to a different city to get something on Craigs. It constantly would shutdown my Maps and Navigation when I wanted to read a Kik message.
If I have Kik open and want to read a txt msg, it takes like 10 seconds after clicking the txt msg icon to show the txt.
Is there an app or method that everyone uses on this phone that I don't know about to get this phone to run speedy? Or, is it just so outdated it can't run modern versions of apps?
I just want navigation, txt, kik, and a light browser like dolphin.
Can a Fascinate handle all that and be snappy and quick??
In the mean time, I am switching over to my S3, though I don't like how it's so big I can't reach all the screen with one hand.
fewert said:
Yeah I read a post saying to do what you just described with success.
However, this phone is really poor. I have tried GB, ICS, JB and all of them I get similar performance just different features.
The phone can't handle two apps at once regardless of the rom.
I was traveling to a different city to get something on Craigs. It constantly would shutdown my Maps and Navigation when I wanted to read a Kik message.
If I have Kik open and want to read a txt msg, it takes like 10 seconds after clicking the txt msg icon to show the txt.
Is there an app or method that everyone uses on this phone that I don't know about to get this phone to run speedy? Or, is it just so outdated it can't run modern versions of apps?
I just want navigation, txt, kik, and a light browser like dolphin.
Can a Fascinate handle all that and be snappy and quick??
In the mean time, I am switching over to my S3, though I don't like how it's so big I can't reach all the screen with one hand.
Click to expand...
Click to collapse
i think you should understand that this phone has a single-core CPU. running at 1GHz. this phone is almost 4 years old. it's amazing this thing can even run things like Kitkat at all, let alone with the relative finesse the most recent unjust build provides.
it took me a while to realize that apps these days are not optimized for single-core CPUs, it took upgrading to a gs4 to realize that. the fascinate is an admittedly, well, slow phone. or its not meant for multitasking, definitely.
the s3 runs circles around this phone. almost anything does. i've never really found anything that allows for the multitasking and insane speed that i get out of my s4, the closest i've ever gotten was cm7, but that even in its stable release had tons of SOD problems (sleep of death, phone locks and never comes back on).
part of the issue is that the fascinate has 512MB of RAM. back in 2010, it was adequate. not even good, just.. alright. these days the norm is 2GB. a phone with 1GB of RAM is considered outdated. despite google's efforts to optimize kitkat for 512MB devices, this phone's GPU shares RAM with the system, and depending on the configuration, usually 100+ MB is reserved for the GPU, leaving typically about 360-384MB of RAM. You can get more (the kitkat ROM i've mentioned allows 416MB of RAM to the system) but things will start breaking, particularly HD video recording and torch, among other things
skepticmisfit said:
i think you should understand that this phone has a single-core CPU. running at 1GHz. this phone is almost 4 years old. it's amazing this thing can even run things like Kitkat at all, let alone with the relative finesse the most recent unjust build provides.
it took me a while to realize that apps these days are not optimized for single-core CPUs, it took upgrading to a gs4 to realize that. the fascinate is an admittedly, well, slow phone. or its not meant for multitasking, definitely.
the s3 runs circles around this phone. almost anything does. i've never really found anything that allows for the multitasking and insane speed that i get out of my s4, the closest i've ever gotten was cm7, but that even in its stable release had tons of SOD problems (sleep of death, phone locks and never comes back on).
part of the issue is that the fascinate has 512MB of RAM. back in 2010, it was adequate. not even good, just.. alright. these days the norm is 2GB. a phone with 1GB of RAM is considered outdated. despite google's efforts to optimize kitkat for 512MB devices, this phone's GPU shares RAM with the system, and depending on the configuration, usually 100+ MB is reserved for the GPU, leaving typically about 360-384MB of RAM. You can get more (the kitkat ROM i've mentioned allows 416MB of RAM to the system) but things will start breaking, particularly HD video recording and torch, among other things
Click to expand...
Click to collapse
Lol my phone e400 is super multitasker
Sent from my LG-E400 using XDA Free mobile app
fewert said:
Yeah I read a post saying to do what you just described with success.
However, this phone is really poor. I have tried GB, ICS, JB and all of them I get similar performance just different features.
The phone can't handle two apps at once regardless of the rom.
I was traveling to a different city to get something on Craigs. It constantly would shutdown my Maps and Navigation when I wanted to read a Kik message.
If I have Kik open and want to read a txt msg, it takes like 10 seconds after clicking the txt msg icon to show the txt.
Is there an app or method that everyone uses on this phone that I don't know about to get this phone to run speedy? Or, is it just so outdated it can't run modern versions of apps?
I just want navigation, txt, kik, and a light browser like dolphin.
Can a Fascinate handle all that and be snappy and quick??
In the mean time, I am switching over to my S3, though I don't like how it's so big I can't reach all the screen with one hand.
Click to expand...
Click to collapse
skepticmisfit said:
i think you should understand that this phone has a single-core CPU. running at 1GHz. this phone is almost 4 years old. it's amazing this thing can even run things like Kitkat at all, let alone with the relative finesse the most recent unjust build provides.
it took me a while to realize that apps these days are not optimized for single-core CPUs, it took upgrading to a gs4 to realize that. the fascinate is an admittedly, well, slow phone. or its not meant for multitasking, definitely.
the s3 runs circles around this phone. almost anything does. i've never really found anything that allows for the multitasking and insane speed that i get out of my s4, the closest i've ever gotten was cm7, but that even in its stable release had tons of SOD problems (sleep of death, phone locks and never comes back on).
part of the issue is that the fascinate has 512MB of RAM. back in 2010, it was adequate. not even good, just.. alright. these days the norm is 2GB. a phone with 1GB of RAM is considered outdated. despite google's efforts to optimize kitkat for 512MB devices, this phone's GPU shares RAM with the system, and depending on the configuration, usually 100+ MB is reserved for the GPU, leaving typically about 360-384MB of RAM. You can get more (the kitkat ROM i've mentioned allows 416MB of RAM to the system) but things will start breaking, particularly HD video recording and torch, among other things
Click to expand...
Click to collapse
I have not used the kik so I can't really say about it's performance,,, I have seen on the 4.4 kitkat rom from Unjust when I have used google maps navigation it was a huge battery sucker, no matter if I only put it on device [gps] only. I could barely even use it and on a charge it was still draining it faster than it could take it.
i did not have this on jellybean roms
I have not had the the problems you describe '10 seconds to open an app'.
Hangouts used to be slow opening initially but their latest update has made it much faster
I don't think it's multitasking is bad for what it is as a phone given it's specs,,, but everyone use a phone differently,,,
so I mostly agree with the overall jest of what skept is saying,,, it is ultimately limited by the 512MB ram available to use.
for GB and JB roms you can also look at the V6 Supercharger thread, it does help with multi-tasking, it can be a bit hard to understand how to implement it but once you figure that out it goes decent, boot up and time till initial use are much longer than normal, but you just have to plan your reboots for when plenty of time allows
i think jellybean roms are very good performers and given the face that you can use a different kernel that allows for overclocking up 1400 Mhz if desired,,, it's a give and take though,,,, over 1200Mhz and battery life goes south very quickly. [luckily the battery doesn't take long to charge, usually 1 hour,,, and even 5 minutes here or 10 minutes there will really help it last through the day]
Most of the earlier jellybean [4.1.x] versions seemed to give better battery life from what I remember than the newer [4.2.x] ones
and there are a lot of different ones to choose from to suite your style or needs from basic cm to full customization.
most of them were stable enough to be daily drivers,,, the big thing is you will just have to read up on a particular one or just break down and try some to see if they fit what you want.
With all that said though the fascinate will never perform like an S3, S4, Nexus, Nexus 4, Moto G, Moto X
I would consider checking out the Motorola Moto G, it's physical dimensions are nearly she same as the fassy but a hugely better phone, screen size, etc and depending on your phone carrier needs it can be had for as little as $65 bucks...
Well lg optimus l3 is very powerful and performant in fact of multitasking if you're a dev or not a complete noob.My phone can go until 1.2 ghz without probs and its factory clock speed was 800 mhz.Most apps aren't optimized for multi-cores and l3 is single core.384 mb of ram are enough on stock and 301 mb aren't enough on cm.But my kernels got swap.
Battery is very good:10days in stand by,2 days in normal use.
Antutu sucks but i don't believe in it.
So its up to the devs,we're good devs and there are more than 100000 l3s in the world.Now we're getting dualboot.Its all about devs,its all about devs.
Sent from my LG-E400 using XDA Free mobile app

RAM

Is it just me, or does the phone use a lot of RAM? Mine seems to be using 2.7GB minimum at all times. Seems high.
Higher would be more ideal. The Windows mindset of "I'm running out of RAM!" doesn't get you anywhere here; in Android, empty RAM is wasted RAM. My Droid Turbo averages ~1.8gb used of 3gb. Seems Nougat tries to average 60%-70% usage.
When you switch out of an app, it's moved to the background and (usually) suspended, but kept in memory so you can switch back to it quickly. It's things like this that take up memory you think should be "free".
In the event that you need to load up a big app, stuff running in the background is quickly and gracefully unloaded.
Unless you're getting constant foreground app crashes - which might indicate that something is forcefully keeping itself loaded and starving everything else of needed memory - you shouldn't worry about it. Android is fairly good at handling memory these days.
Septfox said:
Higher would be more ideal. The Windows mindset of "I'm running out of RAM!" doesn't get you anywhere here; in Android, empty RAM is wasted RAM. My Droid Turbo averages ~1.8gb used of 3gb. Seems Nougat tries to average 60%-70% usage.
When you switch out of an app, it's moved to the background and (usually) suspended, but kept in memory so you can switch back to it quickly. It's things like this that take up memory you think should be "free".
In the event that you need to load up a big app, stuff running in the background is quickly and gracefully unloaded.
Unless you're getting constant foreground app crashes - which might indicate that something is forcefully keeping itself loaded and starving everything else of needed memory - you shouldn't worry about it. Android is fairly good at handling memory these days.
Click to expand...
Click to collapse
I notice this issue more on custom ROMs than stock firmware. On mine and my wife's Quarks (3GB RAM, as you well know), running Marshmallow and Lollipop versions of the same ROM, something causes the phones to just freeze up for about a minute, crashes, then RAM is released to use. It was happening at least once a day on my phone, then my wife said it was happening to her phone. (Our old phones, not the new LG V30 phones.) I've messed with the LMK settings, trying different combinations, to no avail. And I did report it in the Nougat ROM thread for that phone. (Marshmallow ROM thread no longer has support.)
So, while I totally agree with your answer, it is the technically correct answer, I do understand the OP's concern. I've gotten to the point where I like to see more free RAM, so I know my phone isn't about to freeze up. At least on my old phone.
I love custom ROMs, but the past couple of weeks it's been nice to run stock on my new LG V30 and have a very fluid experience. I've not disabled anything. I saw some others disable stuff and then got lagging. I've not touched a thing and my phone is very smooth.
Could a "theme" downloaded from play store take up a lot of RAM and/or slow things down, too?
This is my first experience with a theme.
coldbeverage said:
Could a "theme" downloaded from play store take up a lot of RAM and/or slow things down, too?
This is my first experience with a theme.
Click to expand...
Click to collapse
Possibly, but probably not. From what I've seen, LG themes seem to skin far less than say, substratum does, and even substratum is pretty lightweight unless you get into transparent themes.
Keep in mind the default theme is itself...well, a theme. You're not really saving anything by staying on it. If you see a skin you like, use it, if you're really worried use one of the LG-provided ones that come with the phone.
ChazzMatt said:
I notice this issue more on custom ROMs than stock firmware. On mine and my wife's Quarks (3GB RAM, as you well know), running Marshmallow and Lollipop versions of the same ROM, something causes the phones to just freeze up for about a minute, crashes, then RAM is released to use. It was happening at least once a day on my phone, then my wife said it was happening to her phone. (Our old phones, not the new LG V30 phones.) I've messed with the LMK settings, trying different combinations, to no avail. And I did report it in the Nougat ROM thread for that phone. (Marshmallow ROM thread no longer has support.)
So, while I totally agree with your answer, it is the technically correct answer, I do understand the OP's concern. I've gotten to the point where I like to see more free RAM, so I know my phone isn't about to freeze up. At least on my old phone.
I love custom ROMs, but the past couple of weeks it's been nice to run stock on my new LG V30 and have a very fluid experience. I've not disabled anything. I saw some others disable stuff and then got lagging. I've not touched a thing and my phone is very smooth.
Click to expand...
Click to collapse
Interesting. It does seem like stock ROMs tend to be more conservative with RAM usage, whereas custom ROMs will have less aggressive minfree settings in order to keep more stuff loaded up. "Unused RAM is wasted RAM", but only up to a certain point; in my experience (Maserati with its ancient kernel as well as Quark) approaching ~100mb of free memory in LP/MM/N can bring things to a crawl, and pushing it can cause a kernel panic :good:
The only issue I've seen in Quark RR has been with the Pixiv app, though, and it does exactly what you said. But...I'm fairly certain the app itself leaks memory, as it only happens after browsing a while and is perfectly fine for another stretch after it OOMs and restarts.
My experience with stock ROMs in the past - Quark included - has been "smooth but lacking in features/customization" --- I've never really understood the complaints that stock is slow and claims that custom is blazing fast in comparison. The OEM has a decided advantage in that they have all the tools they need to compile the ROM properly, with then-current driver and kernel sources and a deep understanding of the hardware...I'd be really surprised to find a stock ROM from the last few years to be slower than custom.
But to be honest, my sample size is pretty small. *shrugs* I stick by what I've said, though, if anything the V30 doesn't use its memory enough; some people have complained about apps popping out of memory sooner than expected. LG is still putting out updates too, if a memory-management problem is found, hopefully they'll get right on fixing it.

Categories

Resources