Database Users

Official 2.3.4 - I've lost 130Mb of free RAM

After the official 2.3.4 OTA upgrade I've lost about 130Mb of RAM.
Nothing installed or changed from before to after the upgrade....but 130Mb were disappears.
I was usual to have 500Mb of free RAM but now that amount is reduced to 370....
Is there an explanation?

You have more apps running in the background now. I wouldn't worry about it. The OS will manage everything for you.
If you are really that bothered, you need to go through all the running apps, see what doesn't need to be running, and then use something like Optimize Tool Box from the market to prevent start up of those items. I have 534MB free at the moment myself.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I've specifie "Official 2.3.4 Android"...
Your screenshot is not about that version but about a CustomROM.
(I'm an advanced software programmer and I know very well how an OS works, but in this case I've got any solution)
The services are the same, the widgets are the same, I've not installed nothing more than before, but I've lost 130Mb of free RAM.
I've installed "Advanced Task Killer" and I can "Kill" all listed programs (and System's listed services/executables) but I can't get more then 395 MB of free RAM also if I close all of them and clear Program's cache.
I remember with 2.2.2 I was always over 500 of free RAM, also after 10 days of use (of course after killed task/executables before watch amount of free RAM).

emandt said:
I've specifie "Official 2.3.4 Android"...
Your screenshot is not about that version but about a CustomROM.
(I'm an advanced software programmer and I know very well how an OS works, but in this case I've got any solution)
Click to expand...
Click to collapse
Go back to programming school then..............that is not a custom ROM. It's ADW EX launcher with customized switches, icons, etc. (I guess it's mildly customized in that it's KP's 2.3.4, but for all intense and purposes, it is as close to stock 2.3.4 as it can be). I had the same issue as you, and my lowly mechanical engineering degree got me through it!
I gave you an answer which works for me. Task killers don't work for me. Preventing start up at boot time does! If you are such a good programmer, why can't you figure this out yourself, or at least show a little gratitude when someone tries to help you.

Did you unlock? Some report memory leakage after unlock for international users.
Sent from my MB860 using Tapatalk

CaelanT said:
Go back to programming school then..............that is not a custom ROM
Click to expand...
Click to collapse
It's doesn't matter to go to programming school in this case.
Knowing what type of "launcher" it is doesn't makes someone better at programming.
SetCPU works at least with bootloader unlocked (from stock 2.3.4 or prev CustomROMs) AND with Root Privs.
I mean full stock OS (not custom rom and not rooted), and your case is not like mine.
However ADW EX Launcher is a software which is running OVER Motoblur (on not rooted OS), so it will use additional RAM then full-stock smartphone.
It's easy.
CaelanT said:
it's KP's 2.3.4, but for all intense and purposes, it is as close to stock 2.3.4 as it can be
Click to expand...
Click to collapse
You can't say a CustomROM is "as close to stock".
It's simple different and you are not capable to really know what are the effective changes under the "surface".
CaelanT said:
Task killers don't work for me. Preventing start up at boot time does!
Click to expand...
Click to collapse
Definitly a rooted phone.
So you case is definitly different from a stock OS.
CaelanT said:
If you are such a good programmer, why can't you figure this out yourself?
Click to expand...
Click to collapse
Be a good programmer (I've not tell you in which language. It could be Python, ASP, PHP, Cobol, AS400 or Visual Basic which is not correlate to Android OS) doesn't means I have all the answers about a STOCK OS with unviewable files (due to lack of root privs).

emandt said:
It's doesn't matter to go to programming school in this case.
Knowing what type of "launcher" it is doesn't makes someone better at programming.
SetCPU works at least with bootloader unlocked (from stock 2.3.4 or prev CustomROMs) AND with Root Privs.
I mean full stock OS (not custom rom and not rooted), and your case is not like mine.
However ADW EX Launcher is a software which is running OVER Motoblur (on not rooted OS), so it will use additional RAM then full-stock smartphone.
It's easy.
You can't say a CustomROM is "as close to stock".
It's simple different and you are not capable to really know what are the effective changes under the "surface".
Definitly a rooted phone.
So you case is definitly different from a stock OS.
Be a good programmer (I've not tell you in which language. It could be Python, ASP, PHP, Cobol, AS400 or Visual Basic which is not correlate to Android OS) doesn't means I have all the answers about a STOCK OS with unviewable files (due to lack of root privs).
Click to expand...
Click to collapse
What a bull*** Please give us some real deal infirmation/screenshot or whatever to show us how much memory you have got in total. If you have around 900mb then everything is fine. If it's less then we can try to find out why.
Sent from Motorola Atrix

Maybe someone ar making mistakes....
I was talking about FREE RAM avaiable on Atrix.
Total RAM is always near 900MB, but avaiable/free one is 130MB lower then Froyo 2.2.2, even if nothing changes from before to after upgrade.
So the new STOCK 2.3.4 (not from CustomROM!!!!!!) eats others 130MB of RAM even if services and executables are always the same, in the lists (Task/Process managers), as before.

CaelanT said:
You have more apps running in the background now. I wouldn't worry about it. The OS will manage everything for you.
If you are really that bothered, you need to go through all the running apps, see what doesn't need to be running, and then use something like Optimize Tool Box from the market to prevent start up of those items. I have 534MB free at the moment myself.
Click to expand...
Click to collapse
where can I get ur background lol?

IrshaadH said:
where can I get ur background lol?
Click to expand...
Click to collapse
Second best post here lol

emandt said:
After the official 2.3.4 OTA upgrade I've lost about 130Mb of RAM.
Nothing installed or changed from before to after the upgrade....but 130Mb were disappears.
I was usual to have 500Mb of free RAM but now that amount is reduced to 370....
Is there an explanation?
Click to expand...
Click to collapse
I have noticed the same thing, but I'm not worried about it though. 350 MB is good enough for me. I went from Ken's beta 4 to the official OTA.
Sent from my MB860 using XDA App

Dell, sure....it's not the end of the world, however (as a programmer as I am) I can't find the reason why of that loss of free memory.
There is nothing for explain that drain of RAM.

emandt said:
Dell, sure....it's not the end of the world, however (as a programmer as I am) I can't find the reason why of that loss of free memory.
There is nothing for explain that drain of RAM.
Click to expand...
Click to collapse
There is plenty to explain it. One small change in how aggressively the OS pages memory. If they relax it then it won't page as quickly resulting in less "free ram". Not that it matters at all though, you still have 370 MB free, why do you want the OS paging aggressively when you still have 370 MB free?

I reinstalled CherryBlur and skipped the blur install. I have 2 extended control Widgets and sense clock widget running and fauxs kernel and I'm getting 550mb free. I've been having a huge problem with unknown ram usage until now. I think it's blur eating up ram in background processes.

Sometimes a simple reboot opens up more ram for me. If you are really into software and programming, why aren't you modifying your phone with custom roms, kernels, etc? Im chilling at around 500+ megabytes of ram with the ninja rom.
Sent from my MB860 using XDA App

well mine says
836220 total
230196 free
224868 cached
i am on kenn's 4.5 beta, some moto apps frozen, stock home launcher, with apps like: twitter, liveprofile, whatsapp, facebook.

emandt said:
After the official 2.3.4 OTA upgrade I've lost about 130Mb of RAM.
Nothing installed or changed from before to after the upgrade....but 130Mb were disappears.
I was usual to have 500Mb of free RAM but now that amount is reduced to 370....
Is there an explanation?
Click to expand...
Click to collapse
Hi,
Other than the obvious, that you are running Gingerbread vs Froyo? It isn't likely to be more video ram allocated, so it must be something extra running, another mode of an application that supports gingerbread in a different way than froyo, different versions of installed apps, a ramdisk/temp file/cache/swap added or different reporting of available ram.
If you have adb access, and are rooted, type cat /proc/meminfo. It gives you a break down of various mem usage. Setcpu also shows this.
Cheers!

franciscojavierleon said:
well mine says
836220 total
230196 free
224868 cached
i am on kenn's 4.5 beta, some moto apps frozen, stock home launcher, with apps like: twitter, liveprofile, whatsapp, facebook.
Click to expand...
Click to collapse
+1
For total RAM I don't know why its around 800 MBs all of the sudden. Before I would have 900 something total and 500+ free now I'm at 120 free... Not happy at all.
Sent from my MB860 using XDA Premium App

alphadg21 said:
If you are really into software and programming, why aren't you modifying your phone with custom roms, kernels, etc?
Click to expand...
Click to collapse
1) phone warranty (the most important for a 500$ phone!!)
2) every CustomROM has some issue, and I do not want to do experiments. I want a full working phone 24h/24 in every functionality.

cwburns32 said:
+1
For total RAM I don't know why its around 800 MBs all of the sudden. Before I would have 900 something total and 500+ free now I'm at 120 free... Not happy at all.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Best bet, download and run "System Panel" and find the memory hog apps.
Then freeze them with Titanium Backup...
Sent from my MB860 using XDA Premium App

an app for closing applications automatically

hi
please give me an app for closing applications automatically for more space ram
thanks

http://lmgtfy.com/?q=android+application+to+free+up+ram

Why?
Android will handle the memory by itself if needed.

Got to ask why? As said above it manages its own memory. Free ram is wasted!
Sent from my GT-N7000

PJ147 said:
Got to ask why? As said above it manages its own memory. Free ram is wasted!
Sent from my GT-N7000
Click to expand...
Click to collapse
And i.say why not. Why let the system manage the ram. The ram manage is poor. They are apps that that always run on its self but they a not used all the time and that's why its good to have a app killer. I using ES task manger its free and good.
Sent from my GT-N7000

testacount said:
And i.say why not. Why let the system manage the ram. The ram manage is poor. They are apps that that always run on its self but they a not used all the time and that's why its good to have a app killer. I using ES task manger its free and good.
Sent from my GT-N7000
Click to expand...
Click to collapse
for the last time android handles its RAM well, free RAM is completely wasted, it keeps apps running so you can quickly re open them...its called multitasking.
If a app (like a game) is opened that needs alot of RAM the manger just kills some apps to free enough RAM for it.
There is no need for free ram at all its doing NOTHING

testacount said:
And i.say why not. Why let the system manage the ram. The ram manage is poor. They are apps that that always run on its self but they a not used all the time and that's why its good to have a app killer. I using ES task manger its free and good.
Sent from my GT-N7000
Click to expand...
Click to collapse
It is well known that most automatic task killers actually cause poor performance and battery life because they don't allow the OS to manage itself properly.
Task killers do have a place in killing errant processes, but never automatically.
Remember, just because a process is "running" doesn't mean it is consuming any CPU cycles, and as has already been mentioned, free RAM is wasted RAM.
Regards,
Dave
Sent from my GT-N7000 using Tapatalk 2

I do not agree
If free RAM is wasted RAM, then why does phone get fast and more responsive when you clear RAM from (default) task manager ?
It means free RAM is doing something.
If free RAM was wasted RAM, phone should be always running snappier with everything kept in the memory. But it does not.
I never used any third party task manager though, but tweaking LMK always yieds better performance. That means default memory management is not so good.

Boy124 said:
I do not agree
If free RAM is wasted RAM, then why does phone get fast and more responsive when you clear RAM from (default) task manager ?
It means free RAM is doing somthing.
If free RAM was wasted RAM, phone should be always running snappier with everything kept in the memory. But it does not.
I never used any third party task manager though, but tweaking LMK always yealds better performance. That means default memory management not so good.
Click to expand...
Click to collapse
If your device it slowing down when less ram is free then you have a rouge app taking up processing time, its processing time that slow down the phone NOT free ram, when a app is 'running' in the background it shouldnt be using any processing time however some rouge apps do not manger this well at all and keep running processors

ES Task manager from Google play. Just put system apps to ignore list. But...
Sent from my GT-N7000 using Tapatalk

zacthespack said:
If your device it slowing down when less ram is free then you have a rouge app taking up processing time, its processing time that slow down the phone NOT free ram, when a app is 'running' in the background it shouldnt be using any processing time however some rouge apps do not manger this well at all and keep running processors
Click to expand...
Click to collapse
Methinks the word you are looking for is rogue, unless you really mean "red" apps!
Apologies - pet hate of mine on this site, but.nowhere near as much as the "loose when they mean lose" brigade!
Regards,
Dave
Sent from my GT-N7000 using Tapatalk 2

foxmeister said:
Methinks the word you are looking for is rogue, unless you really mean "red" apps!
Apologies - pet hate of mine on this site, but.nowhere near as much as the "loose when they mean lose" brigade!
Regards,
Dave
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I do yes, sorry being dyslexic is never good on forums

It's not needed. Consider the RAM as some food. The food not eaten is just wasted food. Unused RAM is just wasted. When you run an app or game that needs much more RAM, some other apps are killed. Android manages it's RAM really very efficiently. Specially on note, I never have to use any app killer.
Edit: Task killers do nothing but use more CPU and decrease battery life. If you kill 10 'good' apps with X task killer, and then have to open them again, you are doing nothing but using CPU cycles and battery to reopen the same apps that you closed. You walk 10 miles and then come back from where you started for no reason and again walk the same 10 miles just consume more energy, apart from making you look like a complete fool. Do not use task killers. Just check if you got a bad app.
Sent from my GT-N7000 using XDA

testacount said:
And i.say why not. Why let the system manage the ram. The ram manage is poor. They are apps that that always run on its self but they a not used all the time and that's why its good to have a app killer. I using ES task manger its free and good.
Sent from my GT-N7000
Click to expand...
Click to collapse
But when you kill these "not used" apps the system will have to reload from scratch when required consuming more CPU (and battery) most apps task killers say are running are mearly cached. Read up on this as it is different from running. Android is not windows!

V6 Supercharger?

I was wondering if it is possible to get it working on the N7?
Sent from my Nexus 7 using xda premium

bcvictory said:
I was wondering if it is possible to get it working on the N7?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
why?

It is possible it works on jelly bean just fine. I use it now on my gnex. Helps with memory management and improves battery because the system isn't using so many resources.
Sent From My Toro+ via RED Tapatalk

simms22 said:
why?
Click to expand...
Click to collapse
Mostly cause my home screen keeps reloading. I used to use it on my old tablet and it never reloaded.
Sent from my Nexus 7 using xda premium

bcvictory said:
Mostly cause my home screen keeps reloading. I used to use it on my old tablet and it never reloaded.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
if its reloading, you have an issue somewhere. the seven has enough ram for that not to happen. are you using the stock launcher or replacement? ive never seen my homecreens reload on the n7.
---------- Post added at 06:31 PM ---------- Previous post was at 06:27 PM ----------
ÜBER™ said:
It is possible it works on jelly bean just fine. I use it now on my gnex. Helps with memory management and improves battery because the system isn't using so many resources.
Sent From My Toro+ via RED Tapatalk
Click to expand...
Click to collapse
oh, i know what it does. and its nice with low end devices with very limited ram. my why was meant as why is it needed. if it is needed, its probably a symptom of something else(thats what im trying to figure out )

simms22 said:
if its reloading, you have an issue somewhere. the seven has enough ram for that not to happen. are you using the stock launcher or replacement? ive never seen my homecreens reload on the n7.
---------- Post added at 06:31 PM ---------- Previous post was at 06:27 PM ----------
oh, i know what it does. and its nice with low end devices with very limited ram. my why was meant as why is it needed. if it is needed, its probably a symptom of something else(thats what im trying to figure out )
Click to expand...
Click to collapse
Yeah, it's a symptom of misplaced priorities.
Compare to money management.
You can make lots of money, but it will just take you longer to go broke if you spend too much.
Lots of ram can hide memory management problems when you don't have much stuff installed.
But spend too much, or install a bunch of apps, and it's the same old song and dance.

zeppelinrox said:
Yeah, it's a symptom of misplaced priorities.
Compare to money management.
You can make lots of money, but it will just take you longer to go broke if you spend too much.
Lots of ram can hide memory management problems when you don't have much stuff installed.
But spend too much, or install a bunch of apps, and it's the same old song and dance.
Click to expand...
Click to collapse
while in theory, i completely agree with you. except that i have a lot of apps and games installed, a lot. yet ive never seen the home screen reload on the seven. at any given point, i have between 550mb-650mb free ram. if the op is seeing his home screen reload, then there is a problem somewhere. where that is i dont know. it can be the ops sloppy memory management, a badly written app(s), his kernel/rom.. personally, i think that it would be better to find and solve the problem.

Well, I know for a fact that it isn't only the OP.
A Nexus 7 user who regularly posts in the SuperCharger thread reported that there is always a redraw/lag thread in whatever N7 forum he visits.
Be it Rootzwiki or wherever.
SGS III is no slouch either... and yet... users still report lag/redraw and of course, SuperCharge that beast.
Fact is, the more ram that a device has, the more it can afford to SuperCharge with a BulletProof launcher.
Lock it in and forget about it

zeppelinrox said:
Well, I know for a fact that it isn't only the OP.
A Nexus 7 user who regularly posts in the SuperCharger thread reported that there is always a redraw/lag thread in whatever N7 forum he visits.
Be it Rootzwiki or wherever.
SGS III is no slouch either... and yet... users still report lag/redraw and of course, SuperCharge that beast.
Fact is, the more ram that a device has, the more it can afford to SuperCharge with a BulletProof launcher.
Lock it in and forget about it
Click to expand...
Click to collapse
i do a lot of reading and responding, especially in this forum, and except for this thread, i have never heard of this being an issue on the nexus 7.

I use Apex and am using PA ROM. I didn't see it on stock.
Sent from my Nexus 7 using xda premium

bcvictory said:
I use Apex and am using PA ROM. I didn't see it on stock.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
i believe that apex has an option to set the launcher into memory.

one of my friends made me a screenshot of apexs' settings, heres the option..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yeah the keep in memory option sets the launcher's adj to 2 but since all other priorities/adjs of the other app groupings (perceptible, visible, hidden, etc) remain unchanged, it's still less important than alot of those other apps.
SuperCharger would make it adj 0, 1, or 2 but because of the other changes adj changes, the launcher's importance is much higher (even if supercharged with adj 2/hard to kill ie. adj 2 when supercharged is stronger than adj 2 with stock adj priorites)
It's all about relative importance of one app type (home) to other app types and not solely about it's adj value.
Interestingly enough, if you're supercharged with die-hard launcher (home's adj=1) and you enable apex's keep home in memory option, it makes it weaker with adj 2 so you can actually make it more killable on the fly by enabling it.

zeppelinrox said:
Yeah the keep in memory option sets the launcher's adj to 2 but since all other priorities/adjs of the other app groupings (perceptible, visible, hidden, etc) remain unchanged, it's still less important than alot of those other apps.
SuperCharger would make it adj 0, 1, or 2 but because of the other changes adj changes, the launcher's importance is much higher (even if supercharged with adj 2/hard to kill ie. adj 2 when supercharged is stronger than adj 2 with stock adj priorites)
It's all about relative importance of one app type (home) to other app types and not solely about it's adj value.
Interestingly enough, if you're supercharged with die-hard launcher (home's adj=1) and you enable apex's keep home in memory option, it makes it weaker with adj 2 so you can actually make it more killable on the fly by enabling it.
Click to expand...
Click to collapse
Yeah exactly. I have Apex's option enabled. It works half the time but not all. So how do it get V6 supercharger working on the n7?
Sent from my Nexus 7 using xda premium

If on ICS or JB, just follow post 2 of the supercharger thread and use the Jelly I Scream windows exe for patching services.jar - It does it all via adb - pull services.jar, patches it, installs the new one.

Its designed for GB as that had aggressive RAM management
Sent from my Nexus 7 using xda app-developers app

That's like saying today's cars are made for dirt roads and paths - since there weren't paved roads when the horseless carriage (ie. car) was first invented.
Basics are still the same tho - 4 wheels and a motor vs. low priority launcher with lag & redraw.
Some things never change... and both enjoy SuperCharging lol

[Q] How much available RAM is there after boot?

I would be very grateful if you G2 owners could reboot your phones and report how much RAM you have available after a fresh start.
The reason I'm asking is that I noticed in a video that the RAM was only around 500 MB with only 5 apps open, and then I saw this screenshot: just 320 MB of available with only 2 apps open!
Is the G2 really that low on RAM??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

hduty said:
I would be very grateful if you G2 owners could reboot your phones and report how much RAM you have available after a fresh start.
The reason I'm asking is that I noticed in a video that the RAM was only around 500 MB with only 5 apps open, and then I saw this screenshot: just 320 MB of available with only 2 apps open!
Is the G2 really that low on RAM??
Click to expand...
Click to collapse
have you shut off services/apps you don't need? i noticed this on a verizon model they had at the store. Had 500mb left. i then tinkered and disabled many of the bloat apps and took the phone to 1.2GB of free ram. i don't know if this relates to your phone too. but the bloat slowly kills it at first.

pilot85 said:
have you shut off services/apps you don't need? i noticed this on a verizon model they had at the store. Had 500mb left. i then tinkered and disabled many of the bloat apps and took the phone to 1.2GB of free ram. i don't know if this relates to your phone too. but the bloat slowly kills it at first.
Click to expand...
Click to collapse
That's not a screenshot of my G2, it's from GSMArenas review. I don't own a G2 (yet), the low RAM figures I have seen makes me hesitant to buy one - hence my question.
But if I go ahead and get one it will be an unlocked/unbranded phone, so there will be no carrier apps on it.
Either way, what apps did you close down/disable on the model at the store?

Mines AT&T, but with most of the bloat disabled, I'm at 832. That's with stuff running and not a clean boot. Keep in mind, however, how Linux uses memory. Empty memory is wasted memory.
Sent from my LG-D800 using Tapatalk 4

RAM is meant to be used or it is useless. Android OS caches a ton of things in RAM since it doesnt cost anything or drain any significant extra battery so it looks like a lot of memory is used. If you need more RAM for your own open apps it will flush out unused cached data and apps to make room for whatever you are actually wanting to run. Having 300-400MB free RAM is pretty much perfect amount because it means a bunch of stuff is cached and ready to load fast but it also leaves enough space for a good number of your own things to be open and running before old stuff gets flushed out.

lastdeadmouse said:
...Empty memory is wasted memory.
Click to expand...
Click to collapse
EniGmA1987 said:
RAM is meant to be used or it is useless.... Having 300-400MB free RAM is pretty much perfect amount because it means a bunch of stuff is cached and ready to load fast but it also leaves enough space for a good number of your own things to be open and running before old stuff gets flushed out.
Click to expand...
Click to collapse
400 MB is what I have on my Xperia T after a reboot (no bloatware), as soon as you leave the browser and check 2-3 other apps and then return to the browser (20 seconds later) it has flushed the pages from memory and has to redownload the pages. In Pulse it kicks you out from the story (and even the category) you were reading when the app reloads, all as a result of the low RAM.
I also have the Asus Padfone 2 which has 1.5 GB of free RAM after boot, and it doesn't do any of that flushing, all your opened apps are in memory (because there is room for it), and the user experience compared to the Xperia T is like day and night due to that extra RAM.
So that's only partially true: used memory is good as long as it's made up of YOUR apps that are in memory, but 400 MB of free RAM for user-running apps is simply too little on Android, and I have my own experience, and couple of "Android-geek" friends who also complain the very same issue on their phones (Galaxy Nexus + S3), to back it up.
Since I only buy unbranded phones I'm curious what kind of bloatware you have disabled on your carrier-branded phones?

I'm having concerns with the ram. I usually have 750 on a fresh boot and 300 -400 average daily. My issues are when apps close randomly such as Sirius radio or tune in radio.
For example I'll be listening to one of those apps and get a call or pause it, when I go back to listen the app is closed. Or after a call on my previous phones it would resume. On the G2 it doesn't resume playing because the app is closed. That is not acceptable.
Another example is in the stock task switcher is I try to go back to an app I used say yesterday it will still be in the task switch but if I press it to go back to it will not respond to my touch. I have to actually go back and relaunch the app from the menu. Anyone else having these issues?
Sent from my LG G2

EniGmA1987 said:
RAM is meant to be used or it is useless. Android OS caches a ton of things in RAM since it doesnt cost anything or drain any significant extra battery so it looks like a lot of memory is used. If you need more RAM for your own open apps it will flush out unused cached data and apps to make room for whatever you are actually wanting to run. Having 300-400MB free RAM is pretty much perfect amount because it means a bunch of stuff is cached and ready to load fast but it also leaves enough space for a good number of your own things to be open and running before old stuff gets flushed out.
Click to expand...
Click to collapse
Yeah, I don't get people. They think free ram is magically going to make the phone faster. RAM is meant to be used. If your phone is not using ram, then it's not going as fast as it could. I usually have around 400-600MB free. I have frozen all apps that I think are bloat or I don't use.

Using cleanrom 1.0 I have over 600MB free. With open apps. No complaints.
Sent from my LG-D800 using xda app-developers app

To less off fee ram and android will start shut down backgroundapps to free up some. So little free ram is good on any linux. You surf the net on your browser and want to have any backgroundapps alive and kicking? You need ram So kill all bloatware and services you don't need, works in S4 and should work on the clone
Skickat från min HTC One via Tapatalk 2

verks said:
I'm having concerns with the ram. I usually have 750 on a fresh boot and 300 -400 average daily. My issues are when apps close randomly such as Sirius radio or tune in radio.
For example I'll be listening to one of those apps and get a call or pause it, when I go back to listen the app is closed. Or after a call on my previous phones it would resume. On the G2 it doesn't resume playing because the app is closed. That is not acceptable.
Another example is in the stock task switcher is I try to go back to an app I used say yesterday it will still be in the task switch but if I press it to go back to it will not respond to my touch. I have to actually go back and relaunch the app from the menu. Anyone else having these issues?
Click to expand...
Click to collapse
Your Sirius app closing when you switch to another app is a typical behavior when you are low on ram, so the system immediately closes down an app when it goes to the background in order to free up memory. It's very frustrating, and it was the only reason I stopped using my Xperia T. Never had that problem with my Padfone 2 though, precisely because of all that free ram available at any point.
The task switcher issue you're describing is a bug though, I have never heard of it before but the OS should not behave like that.
Gasaraki- said:
Yeah, I don't get people. They think free ram is magically going to make the phone faster. RAM is meant to be used. If your phone is not using ram, then it's not going as fast as it could. I usually have around 400-600MB free. I have frozen all apps that I think are bloat or I don't use.
Click to expand...
Click to collapse
And I don't get people who reply to threads they haven't read (or don't understand). It's not about speed.

dondavis007 said:
To less off fee ram and android will start shut down backgroundapps to free up some. So little free ram is good on any linux. You surf the net on your browser and want to have any backgroundapps alive and kicking? You need ram So kill all bloatware and services you don't need, works in S4 and should work on the clone
Click to expand...
Click to collapse
^This
All that "free memory is wasted memory"-talk is nonsense in this context, but people have read that phrase someplace and are now throwing it around whenever they hear the word "RAM", regardless of context.

hduty said:
I also have the Asus Padfone 2 which has 1.5 GB of free RAM after boot
Click to expand...
Click to collapse
Proof or GO of this thread. Nonsense and BS. Padfone 2 can haz 1.5 AVAILABLE memomy from boot, but it's not FREE memory. And that't ppl such as you that constantly spreading BS all around making other ppl believe that something's wrong with G2

hduty said:
^This
All that "free memory is wasted memory"-talk is nonsense in this context, but people have read that phrase someplace and are now throwing it around whenever they hear the word "RAM", regardless of context.
Click to expand...
Click to collapse
Exactly! I too own an HTC One X+ and the biggest and only real complain is the crappy ram management. My device does only have 1gb of ram though. Say i'm using Pandora, i receive a call, end call, phone goes back to Pandora but opens it from scratch, that to me is crappy app/ram whatever you want to call it management. I just figured it was due to my device only having 1gb of ram but does Pandora and stock Dialer app really use that much ram? No, not even close which again concludes me to think crappy Android OS 4.1 ram management.
Sad to see this G2 device "top of the line hardware" with 2gb or ram does the same exact thing. Only thing these two devices have in common, using Android OS. Mine is 4.1 and this device 4.2 but obviously no difference as users saying they get the same issue here.
I'm also using a custom rom with as many tweaks possible "to prevent this"
from happening.
I remember my old HTC Diamond doing this too and that device only came with i believe 256mb of ram, sad that to today there is still no resolution to this issue.
Worst part is if you're playing a graphics intense game like dead trigger, get a phone call, even if you ignore it and device goes back to dead trigger, the game now restarts from scratch and all progress never saved as if you weren't even playing the game. Total waste!

My att G2 has about 650 with alll loatwear installed,
after clean tool i get around 800.
When more dev. happens its going to be possible to have 1.2+ with optimization , LG has alot crap running.

People should actually go read how Android manages RAM before spewing nonsense. Stop caring about free ram. Android will manage the amount of RAM it uses. I had the GNex and when using slacker with maps and glympse I would get the low memory message sometimes but at no time did those apps close or crash. With the G2's 2GB of RAM, it's should be able to run all your apps just fine.
http://www.androidcentral.com/ram-what-it-how-its-used-and-why-you-shouldnt-care
http://developer.android.com/reference/android/app/Activity.html#ProcessLifecycle
"Process Lifecycle
The Android system attempts to keep application process around for as long as possible, but eventually will need to remove old processes when memory runs low. As described in Activity Lifecycle, the decision about which process to remove is intimately tied to the state of the user's interaction with it. In general, there are four states a process can be in based on the activities running in it, listed here in order of importance. The system will kill less important processes (the last ones) before it resorts to killing more important processes (the first ones).
The foreground activity (the activity at the top of the screen that the user is currently interacting with) is considered the most important. Its process will only be killed as a last resort, if it uses more memory than is available on the device. Generally at this point the device has reached a memory paging state, so this is required in order to keep the user interface responsive.
A visible activity (an activity that is visible to the user but not in the foreground, such as one sitting behind a foreground dialog) is considered extremely important and will not be killed unless that is required to keep the foreground activity running.
A background activity (an activity that is not visible to the user and has been paused) is no longer critical, so the system may safely kill its process to reclaim memory for other foreground or visible processes. If its process needs to be killed, when the user navigates back to the activity (making it visible on the screen again), its onCreate(Bundle) method will be called with the savedInstanceState it had previously supplied in onSaveInstanceState(Bundle) so that it can restart itself in the same state as the user last left it.
An empty process is one hosting no activities or other application components (such as Service or BroadcastReceiver classes). These are killed very quickly by the system as memory becomes low. For this reason, any background operation you do outside of an activity must be executed in the context of an activity BroadcastReceiver or Service to ensure that the system knows it needs to keep your process around.
Sometimes an Activity may need to do a long-running operation that exists independently of the activity lifecycle itself. An example may be a camera application that allows you to upload a picture to a web site. The upload may take a long time, and the application should allow the user to leave the application will it is executing. To accomplish this, your Activity should start a Service in which the upload takes place. This allows the system to properly prioritize your process (considering it to be more important than other non-visible applications) for the duration of the upload, independent of whether the original activity is paused, stopped, or finished."

BTW, this is what I get on fresh boot, and I haven't even frozen or uninstalled all of the bloatware apps in the ROM.
On another note, you should stop acting like a **** OP. If you ask a question on a forum expect answers from all sorts of people. If you dont like some of those answers dont ask in the first place.

Billy Madison said:
Proof or GO of this thread. Nonsense and BS. Padfone 2 can haz 1.5 AVAILABLE memomy from boot, but it's not FREE memory. And that't ppl such as you that constantly spreading BS all around making other ppl believe that something's wrong with G2
Click to expand...
Click to collapse
So who's spreading the BS?
Now GO of this thread.

Gasaraki- said:
People should actually go read how Android manages RAM before spewing nonsense. Stop caring about free ram. Android will manage the amount of RAM it uses. I had the GNex and when using slacker with maps and glympse I would get the low memory message sometimes but at no time did those apps close or crash. With the G2's 2GB of RAM, it's should be able to run all your apps just fine.
Click to expand...
Click to collapse
The only nonsense around here is the assertion that the amount of free ram on a phone is of no concern. Android's memory management can't perform miracles, nor circumvent basic computer science. If this was all about memory management we wouldn't be seeing phones with 2GB, and even 3GB of ram instead of 1GB, would we?
An app can only be loaded into and run from free memory, and if there is not enough of it the OS will try to make more available, i.e close down/cache/freeze/tombstone/swap some other running process that's currently alive (e.g. some other app that's currently running). If that closed process happens to be an app the user was running, and that the user expects to be alive when he returns to it, then you can encounter the scenarios described by some people in this thread - including myself, with apps being shut down unexpectedly in the background (I'm simplifying a little but for this discussion it's close enough...). More free ram means the OS is much less likely to close down apps opened by the user, simply because there is no reason to close them (and *here* is where the expression "unused memory is wasted memory" becomes relevant).
The exact implementation of *how* and *when* Android closes/freezes apps is what the memory management is all about, and what the text you posted explains. The talk about Android's memory management originally came from all the task managers people were using on their Android phones up until 2-3 years ago, which started to interfere with how the OS was supposed to work. But that is a completely separate discussion, irrelevant to what we are talking about here.
I honestly can't explain it any simpler than that. In other words, free (as in "unused") memory is fundamental in *any* OS for a good user experience, because your apps are going to run in that free memory, and the more of it you have the more apps you can run simultaneously without the OS closing them down in the background.
EDIT:
Just found this while I was searching for another story:
http://www.androidpolice.com/2013/08/30/htc-one-mini-review-the-awkward-ram-deprived-middle-child/
Note the title, and the "Not so good"-summary:
RAM. There isn't enough. 1GB does not cut it, HTC, and it was a tragic misstep to only give the One mini a single gig. Task switching and opening / closing apps becomes maddeningly slow the more you use the phone. It ruins the experience for me when this is happening many, many times a day.
Click to expand...
Click to collapse
So how come it's an issue on the Mini if the concern for free ram is "nonsense" and it's all about Android's memory management??
The issues described in the Mini-review is exactly what I faced with my Xperia T, and the reason why I asked the question here in the first place.
So I will repeat it for the last time: the amount of free ram you have on your phone is fundamental and - contrary to what some of you believe and have repeated here over again - anything but "nonsense", and has nothing to do with "unused memory is wasted memory" and all that talk about Android's memory management.

EniGmA1987 said:
BTW, this is what I get on fresh boot, and I haven't even frozen or uninstalled all of the bloatware apps in the ROM.
On another note, you should stop acting like a **** OP. If you ask a question on a forum expect answers from all sorts of people. If you dont like some of those answers dont ask in the first place.
Click to expand...
Click to collapse
No more **** than someone who replies with "yeah, I don't get people", acting like a smarta**, while in reality completely missing the point of the question.
Either way, thanks for posting your numbers.

Free Memory in Marshmallow

Hi guys i have just sideloaded OTA to my nexus 9. It seems to consume quite a lot of memory. when i first booted it was using 1.7-1.8gb.
I closed all the apps by swiping on the task switcher and got to 1.5gb as below
Could anyone who have been recently clean flashed tell me how much memory their device is using?
Cheers
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

That seems to be the norm based on my experience, even back on the previews.
I don't think there's much we can do. I uninstalled Facebook as it was the main culprit, but other apps just picked up the slack.
Google was dead wrong not giving this device 3 GB for the price we paid.

Same here
Sent from my One X using XDA Free mobile app

Android OS seems to use a lot more than on nexus 5!
Sent from my Nexus 5 using Tapatalk

Really, really disappointed from day 1, worst battery life, insufficient ram, laggy here and there, memory leaks and redraws, black smudges on white screen while scrolling, this is my second replacement, and Android 6.0 which I had I hopes for fixing the nexus 9 is even worse, I just moved back to lollipop the new build lmy48t.
I'm selling my nexus 9, I love nexus and their products, I own a nexus 5 and nexus 7, they both get more battery than the nexus 9, they are faster than the nexus 9, nor have I had a bad experiences with them, they both have 2gb ram and can open crazy tons of apps without redraws or any lock ups, $610 AU dollars in the trash, buying either a new nexus 7 2013 or a Samsung tab s2. Don't say oh factory reset, bro I've tried all ROMs, ive done 1000s of factory resets and this crap ain't working with me, the only thing the nexus 9 hasn't let me down is gaming that's IT!!!, BESIDES ITS A BLOODY HEATER, 80 DEGRESS Celsius, I'll probably use this as a heater in winter.

You guys do know that's average use
Also even closing all the apps it will stay high because it's average over time
To get to the real one.
Go to developer options
Then to running services

HasnaCuz said:
Really, really disappointed from day 1, worst battery life, insufficient ram, laggy here and there, memory leaks and redraws, black smudges on white screen while scrolling, this is my second replacement, and Android 6.0 which I had I hopes for fixing the nexus 9 is even worse, I just moved back to lollipop the new build lmy48t.
I'm selling my nexus 9, I love nexus and their products, I own a nexus 5 and nexus 7, they both get more battery than the nexus 9, they are faster than the nexus 9, nor have I had a bad experiences with them, they both have 2gb ram and can open crazy tons of apps without redraws or any lock ups, $610 AU dollars in the trash, buying either a new nexus 7 2013 or a Samsung tab s2. Don't say oh factory reset, bro I've tried all ROMs, ive done 1000s of factory resets and this crap ain't working with me, the only thing the nexus 9 hasn't let me down is gaming that's IT!!!, BESIDES ITS A BLOODY HEATER, 80 DEGRESS Celsius, I'll probably use this as a heater in winter.
Click to expand...
Click to collapse
ok, you said this already on a thread you started!! if it was from day 1, why didn't you return it!

Used memory is a GOOD thing as long as it is releasing it when a new app requests it. Why have RAM sitting around unused when it can be used for helping the OS/apps run faster?

knitler said:
Used memory is a GOOD thing as long as it is releasing it when a new app requests it. Why have RAM sitting around unused when it can be used for helping the OS/apps run faster?
Click to expand...
Click to collapse
The ram usage is for a base system, the absolute minimum for the Google software stack to run. There is basically no more ram left for any other applications without paging out essential processes. Hence the home screen redraws, background media being killed, redraws on tab switching in chrome, lag on application start up. 2gb is simply not enough for a 64bit android environment.

I have 1.3GB Used, 21 in memory in the last 3hrs. No problems so far. I also have HW rendering turned on not software, that may help some too.

Here is another data point. Been running 6 for about 5 days, no problems at all. Bone stock, unrooted/unlocked.

Mine too guys. Clean installation and always 1.5-1.6 ram used in idle. Hopefully in the future this will change.

Best advice I can give... Use Fire-Ice kernel.
Use zram at about 200mb. And activate KSM.
KSM will save you at least 300mb (it did for me), while zram will make sure that you still have a bit of extra RAM for ram intensive apps, like chrome.
Update:
I'm currently sitting at 1.3GB and I have not closed any of my extra applications.
Between Android OS, System UI, Android System and Launcher3 I'm using 1026MB.
This is not that bad
If you have background apps which are consuming a lot of memory even though you're not using them.
Use greenify to keep them closed, this will keep memory free for apps you actually use.
This managed to keep me afloat when it was still on Lollipop with its damned memory leaks. Im pretty sure it can handle MM.

device slows to a crawl......to the point i can't even unlock the device without waiting 10-15 seconds for it to respond. Marshmallow on Nexus 9 is not good....

rogerchew said:
device slows to a crawl......to the point i can't even unlock the device without waiting 10-15 seconds for it to respond. Marshmallow on Nexus 9 is not good....
Click to expand...
Click to collapse
I'm on marshmallow and my N9 is faster than when it was on lollipop. Battery life is better.
Sent from my Nexus 9 using Tapatalk

rogerchew said:
device slows to a crawl......to the point i can't even unlock the device without waiting 10-15 seconds for it to respond. Marshmallow on Nexus 9 is not good....
Click to expand...
Click to collapse
Do a factory data resrt. That should help quite a bit.
Sent from my Nexus 9 using Tapatalk

Does nobody think that the differing experiences are not due to hardware/Marshmallow but to errors in the coding of apps used? Google has extensive documentation on app coding and memory performance diagnostics - start here http://developer.android.com/training/articles/memory.html

Mine is around 1.6GB running on stock Marshmallow.
Grinds to a halt at times, so frustrating!

AlanS181824 said:
Mine is around 1.6GB running on stock Marshmallow.
Grinds to a halt at times, so frustrating!
Click to expand...
Click to collapse
Read my previous post. It will help you quite a lot.
For MM most people are recommending to use a custom ROM and Kernel.

It's the same on mine. Everything works great except multitasking. It's impossible to multitask like on phones (or video reviews of Nexus 9!).
The worst is Chrome - only one tab can stay loaded, if I have two or three or more it has to reload them every time I switch a tab.
- Yesterday I clered cache and data - it works better now (usually Google's apps like gmail and drive stay loaded - Chrome still has the same problems).
Android 6.0 MRA58K