G300 most RAM efficient ICS/JB ROM out there?

[Guest xnokia]

G300 is a great phone, after going through all the thread still don't have it clear which ICS/JB ROM is the most efficient and unveils phone's full capabilities without draining too much RAM.

[Guest Mrian]

this is a great thread/question... this is seems to be the biggest draw back of the g300, 512 ram...

perform of the system seems to stutter when less than 100mb ram is available.

im guessing ICS is the best for this as ... jelly bean has been recommend for machines running with more than 512mb ram

[Guest tcpaulh]

This is a bad question :) ICS and to a greater extent JB are supposed to use available ram whenever sensible so that your frequently used app doesn't have to load into memory from storage every time it runs. It takes no time to unload an app if it's idle and something else needs the space.

Not having much ram means (to put it simply) that you're more likely to have the thing you need already in ram when it comes time to use it.

[Guest fr0do]

Big issue for me. All ROMs except cm10 slow down badly. The cm10 team's kernel for ICS seems to fix it too.

[Guest unaszplodrmann]

As has been said, a poor question. RAM utilisation in Linux (and thus Android) is not like in Windows. It doesn't help that Google pander to false preconceptions by having a "free" RAM indicator in the app manager.

Android wants to fill all available RAM with data, as Paul indicated, essentially because it is faster to read from RAM than other media. What then becomes important is how it shuffles that data about, especially with regard to what it chooses to discard in order to make space for additional data. Furthermore, AFAIK, there is nothing in CM10 that miraculously circumvents the G300s limited amount of RAM and CPU horse power.

[Guest tcpaulh]

RIght now, CM9 and Stock+ are pretty good choices. CM10 is in flux ;-)

[Guest fr0do]

What then becomes important is how it shuffles that data about, especially with regard to what it chooses to discard in order to make space for additional data.

Indeed. RAM isn't the problem but memory allocation. That's what I believe Daz & Faggy sorted.

Edited December 24, 2012 by fr0do

[Guest Mrian]

memory management is an important question, and some variant os's handle it better than others..

It is time consuming to manually manage apps, i don't see why lots of apps are left running, unless they are active in some way.

Unfortunately the real and costly way to solve this issue is to buy a phone with more RAM. More applications = More resources

needed. for me the best OS is infusion B6.

pretty solid. I have around 80mb free and anything less than 100mb seems to cause the system stutter on occasion. which can be frustrating. not long until my g3 jiayu arrives, i hope.

[Guest fr0do]

Unfortunately the real and costly way to solve this issue is to buy a phone with more RAM. More applications = More resources

I disagree Marian

More cores = more resources. More ram = more slow memory access.

[Guest unaszplodrmann]

Indeed. RAM isn't the problem but memory allocation. That's what I believe Daz & Faggy sorted.

Adjusting the lowmemkiller values doesn't yield a day/night difference. The defaults are setting for balanced performance, with "multitasking" and speed at either side of the scale; tradeoffs are made.

i don't see why lots of apps are left running, unless they are active in some way

It's not rocket science. Inactive processes are cached in RAM so that they become responsive more rapidly when they become active again. Loading them into RAM from non-volatile storage takes longer and is also a needless waste of processor cycles. They're not just sat there wasting space; this is a well established design, developed over decades. Android != Windows. "Free" RAM is irrelevant; what is important is how much and quickly occupied memory can be released.

Edited December 24, 2012 by unaszplodrmann

[Guest Mrian]

I disagree Marian

More cores = more resources. More ram = more slow memory access.

Well the idea I was responding to was that more apps, the way to deal with problem is to get more ram. The problem being that

more apps are being run then the system has ram for. And well in this day and age, apps are using more and more RAM, and we're running more and more apps concurrently.

Adjusting the lowmemkiller values doesn't yield a day/night difference. The defaults are setting for balanced performance, with "multitasking" and speed at either side of the scale; tradeoffs are made.

It's not rocket science. Inactive processes are cached in RAM so that they become responsive more rapidly when they become active again. Loading them into RAM from non-volatile storage takes longer and is also a needless waste of processor cycles. They're not just sat there wasting space; this is a well established design, developed over decades. Android != Windows. "Free" RAM is irrelevant; what is important is how much and quickly occupied memory can be released.

things like camera don't need to run in a ram, settings, text messages, i don't know, but they can load when need but to be kept in RAM seems a waste. Unless its whatsapp, facebook, etc where updates are regular, then they need to be active.

Anyway, running out of ram or cpu usage im not sure where the bottleneck occurs.

Edited December 24, 2012 by Mrian

[Guest PACOSH]

and i think that dazz (and tillaz b4 with infusion) made a good job with setting up their defaults..

[Guest unaszplodrmann]

things like camera don't need to run in a ram, settings, text messages, i don't know, but they can load when need but to be kept in RAM seems a waste. Unless its whatsapp, facebook, etc where updates are regular, then they need to be active.

Again, you're not wrapping your head around the basics of how memory utilisation works under Linux, and more specifically Android. What seems like a waste to you, is not in fact a waste. I'm oversimplying here, but if an app is unused it will be removed from the cache when memory need to be freed for another active app. Manually killing processes actually harms performance.

Anyway, running out of ram or cpu usage im not sure where the bottleneck occurs.

It is most probably RAM. This is the same across ALL ROMs you find here. None of them has significantly better memory management than the other. CM9/10 has some small enhancements, but the G300 has only 512MB RAM, so the user has two choices: 1) run only select number of persistent services to avert memory getting tight, or 2) put up with a bit of sluggishness and occasional "force closing" of foreground apps.

[Guest Pyntux]

When you start some game for example, cache is gonna be free, because game need more ram, but in regular work with phone, ram is used with cache of apps to start them quick...So, free ram is wasted ram! :)