Develop Bugs

[Q] RAM availability varying figures

Ok so in the BLISS beta thread there was some discussion about available RAM. To keep that thread clear of our BS i decided to post this up for us.
I do recall Tiny mentioning something in the Bliss thread about us needing to read into Android Memory Management so I took a peak using trusty old Google and didn't find too much, then again I am at work. I'm sure there is more to It than I have stumbled upon though but I didn't want us to continuing threadjacking.
Anyway, Bob was posting how he had this amount of RAM available that we thought was unheard of. Upon further investigation, I believe the app he/she is using is pulling up data from here:
{
"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"
}
While most of us have been using task manager in the notification pulldown to see this:
Those screens were taken literally less than a minute apart. Why do these figures vary so much? I have no clue.
Discuss.

Marcismo55 said:
Ok so in the BLISS beta thread there was some discussion about available RAM. To keep that thread clear of our BS i decided to post this up for us.
I do recall Tiny mentioning something in the Bliss thread about us needing to read into Android Memory Management so I took a peak using trusty old Google and didn't find too much, then again I am at work. I'm sure there is more to It than I have stumbled upon though but I didn't want us to continuing threadjacking.
Anyway, Bob was posting how he had this amount of RAM available that we thought was unheard of. Upon further investigation, I believe the app he/she is using is pulling up data from here:
While most of us have been using task manager in the notification pulldown to see this:
Those screens were taken literally less than a minute apart. Why do these figures vary so much? I have no clue.
Discuss.
Click to expand...
Click to collapse
Hmmm. Weird, I am currently downloading the rom. Perhaps sense is using a different amount of RAM than the rest of the OS is.
I'm sure we will have closure on this in the next release from the developers.

Marcismo55 said:
Ok so in the BLISS beta thread there was some discussion about available RAM. To keep that thread clear of our BS i decided to post this up for us.
I do recall Tiny mentioning something in the Bliss thread about us needing to read into Android Memory Management so I took a peak using trusty old Google and didn't find too much, then again I am at work. I'm sure there is more to It than I have stumbled upon though but I didn't want us to continuing threadjacking.
Anyway, Bob was posting how he had this amount of RAM available that we thought was unheard of. Upon further investigation, I believe the app he/she is using is pulling up data from here:
While most of us have been using task manager in the notification pulldown to see this:
Those screens were taken literally less than a minute apart. Why do these figures vary so much? I have no clue.
Discuss.
Click to expand...
Click to collapse
Very good idea by the way. I can't actually answer why the two screenshots are different other than to assume where they get their information is obviously different as the free RAM is not going to vary that way. I actually never care about memory too much as long as the ROM runs smooth. It sounds like people are benchmarking using free RAM which is totally dependent on what apps you have running and in fact installed. Read on if you're still curious.
Let me try to summarize from what I understand. Basically from what I found by googling the Android OS does memory management different than Windows. More total RAM is definitely better in both scenarios as you can run more apps before the system has to load them to RAM. However, Android loads apps in memory at boot so having more apps could cut back on memory and I think it learns what is more popular on usage and prioritizes those. If you go killing apps, it may just reload them, using more battery than leaving them running, or they may stay stopped. I think the task manager should be used in a similar instance to Windows like if you have an app that's not responding or frozen. The lag actually stems from background processes such as reloading apps that it suspends from RAM. If you are having lag issues from low RAM (I would say around 50 MB reported in task manager though 60-70 MB could start leading to lag), I might be able to do something to assist with the lag on the kernel side. I can't promise this before the source is released. I actually don't plan new features until HTC releases source, just bugfixes if there are any (besides the unfortunate issue with USB mounting on some ROMs).
I'm aware that Sense uses more RAM and basically swap support could be added on the kernel side to allow virtual RAM and it should hopefully be smoother.
Sorry if I got too technical.

tiny4579 said:
Very good idea by the way. I can't actually answer why the two screenshots are different other than to assume where they get their information is obviously different as the free RAM is not going to vary that way. I actually never care about memory too much as long as the ROM runs smooth. It sounds like people are benchmarking using free RAM which is totally dependent on what apps you have running and in fact installed. Read on if you're still curious.
Let me try to summarize from what I understand. Basically from what I found by googling the Android OS does memory management different than Windows. More total RAM is definitely better in both scenarios as you can run more apps before the system has to load them to RAM. However, Android loads apps in memory at boot so having more apps could cut back on memory and I think it learns what is more popular on usage and prioritizes those. If you go killing apps, it may just reload them, using more battery than leaving them running, or they may stay stopped. I think the task manager should be used in a similar instance to Windows like if you have an app that's not responding or frozen. The lag actually stems from background processes such as reloading apps that it suspends from RAM. If you are having lag issues from low RAM (I would say around 50 MB reported in task manager though 60-70 MB could start leading to lag), I might be able to do something to assist with the lag on the kernel side. I can't promise this before the source is released. I actually don't plan new features until HTC releases source, just bugfixes if there are any (besides the unfortunate issue with USB mounting on some ROMs).
I'm aware that Sense uses more RAM and basically swap support could be added on the kernel side to allow virtual RAM and it should hopefully be smoother.
Sorry if I got too technical.
Click to expand...
Click to collapse
Not technical enough for me. I'll eat up as much info as you wanna dish.

loonatik78 said:
Not technical enough for me. I'll eat up as much info as you wanna dish.
Click to expand...
Click to collapse
Ok, we'll see. This is all from memory. Maybe I'll try again but I'm tired. I might have to do some more research.
Oh, I forgot, the Inc actually has 512 MB of RAM but about 100MB of it is dedicated to the kernel and OS processes that cannot be used by apps and such including the homescreen app. Google wasn't too helpful but this is just from my observations.
If anyone has more information please share as I'm curious why task manager is different than the RAM shown in running. I know there is a command in Linux called free that can be run from terminal emulator but it doesn't report accurately what is available for the system.
Sorry I need sleep so that's all for tonight.
As far as developers knowing, I think the CM devs would be knowledgable on this subject as they see the inner workings of Cyanogenmod and the AOSP framework so they see the source code of Android which is not available for the Sense framework.
FYI, CUViper is one of the maintainers for the Inc for Cyanogenmod so he oversees code changes for the Inc and I know he has also worked on the kernel for Cyanogenmod.

For what it's worth - system panel reports about the same as task manager for me (around 95mb) - and my running apps screen shows a huge amount of ram free - 288mb at the moment

Thank for breaking it down the best you can Tiny.
I don't have the greatest amount of computer knowledge but when I think if scarce free RAM I think that would contribute to a slow running system but I wasn't aware that Android handles memory so much differently but I guess that's why people were starting to have issues with Synergy due to the cache partition filling up with memory from apps? I read users of Synergy were having issues with the ROM becoming unstable and it was necessary to clear the cache partition in order to regain usability. I'm probably trailing off in the wrong direction though...
I did find this post in the Desire S forum under their Bliss port of a user who stated an app called Swapper really sped things up. HERE is the post.
I haven't done too much research on it but curious if anyone else does?

How do I stop apps auto opening

The title is basically the question, im fed up of alot of programs auto opening on my android phone, it takes battery and is slightly annoying receiving notifications off apps i dont really care about such as the NFL game tells me about small things in the NFL, im in the UK, i dont care.
If you argue that it doesnt take alot of battery currently have 117mb free ram, (2 secs later) killed all my selected apps now have 201mb free so im using 80mb of ram on apps im not using. Ive made 2 or 3 phone calls today no more than 30 mins long altogether and ive lost 55% of my battery since about midday, which is when i unplugged the phone.
And I think all these apps are the problem so how can I stop them from auto opening, please help

Search the market for startup cleaner
Sent from my A101IT using xda premium

yusuo said:
If you argue that it doesnt take alot of battery currently have 117mb free ram
Click to expand...
Click to collapse
More free RAM doesn't really equate to longer battery life or lower power consumption.

Better search for auto starts, this asp shows you the conditions an asp can turn back on and you can bin it off, Facebook for example had like 8 conditions, from full to medium battery life, on charge and change in network....... Use it
Sent from my HTC Desire using xda premium

rootSU said:
More free RAM doesn't really equate to longer battery life or lower power consumption.
Click to expand...
Click to collapse
There's still no reason for most of this apps to use RAM. Apps like facebook and skype shouldn't be actice without user permission. Without login they are complete useless.
I'll try Startup Cleaner, thx.

It's how android works and what RAM is for. There is always a reason.
Sure if someone doesn't use Facebook, it should be uninstallable, but its not and its not causing any harm
Sent from my HTC Desire using Tapatalk

The problem isn't that apps start when I turn on the phone its that even after i use task manager to close they keep reopening and use over 100mb of ram, earlier I checked and only had 78mb ram available.
This must have an effect on battery to some degree i want to kinda ban certain apps from running in the background unless i specifically tell them to

RAM doesn't use more power, the more its used, no.
You don't need a task killer. You do not need to obsess about RAM. Forget about RAM and enjoy your phone
Sent from my HTC Desire using Tapatalk

rootSU said:
RAM doesn't use more power, the more its used, no.
You don't need a task killer. You do not need to obsess about RAM. Forget about RAM and enjoy your phone
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Thanks for you reply but its not really an answer its more of a contradiction, what I was asking is how to I stop apps from auto starting and eating up RAM, regardless of how long the phones been on

...and I'm telling you its a pointless, unecessary waste of time. Also it is not possible. Autostarts as already mentioned is the closest you'll get
Sent from my HTC Desire using Tapatalk

I also turned off the autorun permissions of a lot of apps, for 2 reasons: 1) a device that is smooth sooner after booting, using less cpu cycles/power. 2) preventing Sense from reloading due to RAM shortage and have smooth multitasking.
1) Android loads a bunch of apps to the RAM that have the autorun permission, until it thinks it is "enough" and useful to you. No matter how many apps you have installed, the amount of free RAM is always about the same, just the number of "unwanted" apps in the RAM differs. Removing the autorun on boot permissions prevents the loading of unnecessary apps that will immediately be removed from the RAM the moment you start the browser/a game, saving cpu cycles=power. So for me there is no point in loading them in the first place, because I am never going to use them (right away). I want the apps that don't to any syncing loaded on demand.
2) I hate slow multitasking and I hate it even more when Sense reloads because it got kicked out of the RAM after each time I press HOME.
I use 3G Watchdog (~12MB RAM), Unlock with Wifi (~8MB), Whatsapp (~15MB), Handcent SMS (~18MB), Droidstats (~13MB), Extended Controls (~12MB), Battery Monitor Widget Pro (~13MB). Okay, I maybe could delete some of them, but these app are "OK" to me, because I use them actively or just need a background service to operate normally.
With Gemini I disabled apps like Facebook, a screenshot tool (just load when I want to make a screenshot..), various public transport planning tools, etc from autostarting.
No joy moment: after using the Facebook app (market version), it may take up 50+ MB and it will not be closed when I start another RAM intensive app, because it is a high priority service. Result: Sense gets kicked out of the RAM. Or, when the situation is somewhat less critical: multitasking is as good as unusable: switching between apps makes them load over and over again, because app2 kicks app1 out of the RAM and vice versa, causing unnecessary lag. Therefore: when I am done with facebook, I close it, then STAY the hell closed It may only autostart when it receives a push message. In that case it is nice to have FB already in RAM when I tap the notification.
Why do even some games have background services, or the Engadget app, or .. , or... all eating precious RAM. And yes, I know, once IN the RAM they eat no battery, but they DO eat battery when the app loads itself back in the RAM when it thinks it needs to, after it got kicked the moment I decided to so something else.
Hmm, spent way too much time to try to explain my frustration Oh and by the way, I have a Legend, but the basics are the same of course.

Dwnload an app called internet commander from the market. It shuts off the internet when your screen turns off but still let's you get calls and texts. I've got my phone , rooted of course, clocked to 710 and my battery will last for days.
Sent from my Eris using xda premium

I just re read your post, that won't help with apps but it will help save battery. And when you turn your screen on the internet kicks right on instantly. Good luck
Sent from my Eris using xda premium

yusuo said:
The problem isn't that apps start when I turn on the phone its that even after i use task manager to close they keep reopening and use over 100mb of ram, earlier I checked and only had 78mb ram available.
This must have an effect on battery to some degree i want to kinda ban certain apps from running in the background unless i specifically tell them to
Click to expand...
Click to collapse
The guys here have already suggested you use a certain program from the Market. Have you tried it?
Regarding the whole RAM consumption issue, Android has its own built-in memory management system that ensures that there's always enough RAM for an app whenever it needs it, even if the memory manager shows like 40 MB free. Basically it "ejects" all background, unused apps, from memory making room for the foreground app which needs it most. If for some reason you need to fiddle with that, you can try using the V6 Supercharger script. I find it suitable for my needs but YMMV. It's completely reversible, so if you don't like it you can uninstall it just like that.
P.S. - I agree with rootSU, the ammount of free RAM has nothing to do with battery consumption. If you suspect that an app is draining your battery, check Android's battery statistics to find the culprit.

TVTV said:
Regarding the whole RAM consumption issue, Android has its own built-in memory management system that ensures that there's always enough RAM for an app whenever it needs it, even if the memory manager shows like 40 MB free. Basically it "ejects" all background, unused apps, from memory making room for the foreground app which needs it most. If for some reason you need to fiddle with that, you can try using the V6 Supercharger script. I find it suitable for my needs but YMMV. It's completely reversible, so if you don't like it you can uninstall it just like that.
P.S. - I agree with rootSU, the ammount of free RAM has nothing to do with battery consumption. If you suspect that an app is draining your battery, check Android's battery statistics to find the culprit.
Click to expand...
Click to collapse
I respectfuly disagree. Android built in ram management is just silly. If I open xda app for example (it could actually be any app for that matter), reply to a few posts, read a few more and close it, why does it need to stay in ram? It reloads anyway when I run it again after I've closed it (using the back button or the actual exit command in the app itself). Why does the camera app need to stay in the background after I just shot a few photos and closed it? Because I may or may not use it again in some time? It's rediculous. And the whole theory that ram management doesn't require any power/cpu usage, how do you guys think all those apps get killed? Android will power?! No, kernel scans all running apps and kills the ones based on built in heuristics so it also reads them first. So that doesn't require any power/battery? Awesome if it's true! Although I wouldn't bet on that. And all this fuss just because you may or may not launch the same app sometime during the next day/week/month/year or it'll eventually get killed? Now that's just plain stupid. I get apps that need services like widgets, push notifications etc. but random apps like root explorer, xda app, titanium, youtube etc. which are opened specificly by the user shouldn't be in ram just for the sake of it after they're closed. I closed it, meaning I don't need it anymore. And I don't need the kernel to scan all apps and running services every time I launch an app so it could provide the free ram that app needs. Consumes cpu time, battery, i/o ... every piece of hardware actually just to free some ram that shouldn't be occupied in the first place. Every app that I ever opened on my phone got loaded almost instantly and that's just after phone had been booted. So after that it should stay in ram so I could open it in a blink of an eye instead of instantly? That's just funny.
Anyway, I'm just thinking out loud so don't flame me immediately. There probably are apsects of it that I didn't mention here or am not aware of. And I'm not saying that I'm right and you guys are wrong, I'm just saying what I know and think about this subject.
-. typewrited .-

PlayPetepp, while it might be true that the OS allocates (thus use) some resources to memory maintenance, the impact on battery life is negligible. In the Android OS, apps in memory are ordered according to priority and state, so the OS always knows which apps to kill first if it needs to make room in RAM, without much of a hassle. The only bad consequence of this system seems to be the fact that once the memory fills up, the launcher may lag or even be evacuated from memory. But, as i've mentioned in my previous post, there are ways to prevent that, either via scripts or, if you know what you're doing, via editing system files.

So the OS doesn't need to scan anything as it keeps everything in memory again? Seems like an endless loop. Open, sort, kill if needed, reopen, sort again, kill ... to what end, constant unneccessary multitasking that user is unaware of? I really don't see any benefit of that system and am only seeing the downsides. I mean, who needs every app they ever run remain in ram even if they close them after using? And then opening another app and "waiting" for whatever needs to be closed to get it running. Sure you can mess with the scripts (init.d, init.rc, etc.) but the underlined conditions stay the same. I hope I'm making sense here. Or am I fighting against windmills.
I just figured out that I strayed from the topic of this thread so won't be continuing this discussion if it's considered offtopic.
-. typewrited .-

Stop looking for excuses for poor multitasking in Sense 3+ roms

erklat said:
Stop looking for excuses for poor multitasking in Sense 3+ roms
Click to expand...
Click to collapse
Hello again nice to see you here
Here's an interesting article on what I was talking about. Sense 3.5 doesn't need that many mbs of ram to work smoothly. After booting and setting everything up I have 150+ mb free. That should be enough for decent multitasking but all those apps not getting killed when you close them are eating too much. Can anyone explain in detail what hidden app, perceptible app, backup app and heavy_weight app means? I've been googling this for a week and can't find any decent explanation.

@PlayPetepp - I think i have already said (in my previous post) that the OS does indeed use some resources for managing the memory, but they are negligible in terms of their impact on battery life. IMHO, the only thing a 3'rd party memory manager (task killer) WILL do is improve lanuncher responsiveness (lag) as the lag does increase when free RAM drops under a certain limit. Thus used wisely, a task killer can improve responsiveness, but battery life... very little, in rare cases (it does the opposite, most of the time).
Regarding the so called "memory slots", here's an excerpt from this article:
FOREGROUND_APP: This is the application currently on the screen, and running
VISIBLE_APP: This is an application that is open, and running in the background because it's still doing something
SECONDARY_SERVER: This is a process (a service that an application needs) that is alive and ready in case it's needed to do something
HIDDEN_APP: This again is a process, that sits idle (but still alive) in case it's needed by an app that's alive and running
CONTENT_PROVIDER: This is apps that provide data (content) to the system. HTC Facebook Sync? That's a CONTENT_PROVIDER. So are things like the Android Market, or Fring. If they are alive, they can refresh and provide the content they are supposed to at the set interval. If you kill them, they can't of course.
EMPTY_APP: I call these "ghosts." They are apps that you have opened, but are done with them. Android uses a unique style of handling memory management. When an activity is ended, instead of killing it off Android keeps the application in memory so that opening them again is a faster process. Theses "ghost" apps use no battery or CPU time, they just fill RAM that would be otherwise empty. When this memory is needed by a different application or process, the RAM is flushed and made available for the new app. To satisfy the geekier people (like myself) Android does this by keeping a list of recently used apps, with the oldest apps in the list given the lowest priority -- they are killed first if RAM is needed elsewhere. This is a perfect way to handle 'ghost' processes, so there's no need to touch this part
Click to expand...
Click to collapse

Multi-tasking woes with AOSP (CM10, AOKP, PA)

This is not meant to be a complaining post, mostly I wanted to see if anyone else is having my problems.
I am currently running ParanoidAndroid 2.50 (CM10 based ROM) and I absolutely love how all AOSP ROMs look and feel. TouchWiz had some neat things, but it felt really bloated.
My problem is, multi-tasking on AOSP blows, really, really, really, BAD. I mean it's downright as bad as HTC One X's Sense UI multitasking. For whatever reason, I can never get my free RAM to dip below the 600 MB limit. Usually it hovers around 750 MB, and occasionally I can get it down to 650 MB.
I am not a huge multitasker, but I HATE HATE HATE app re-draws and reloads. This was the one nice thing about TouchWiz, it would keep my opened applications running until I was absolutely at the bottom of my free RAM (~150 MB). My frequently used applications almost never needed to be reloaded/redrawn. This is especially big for applications like Youtube and Browser/Firefox, as you lose everything that you had loaded otherwise.
I've tried spamming opening apps, and the most apps I seem to be able to have open at once is around 8-10 depending on the circumstances. As soon as I cross that threshold of open apps, my other opened apps start being force closed, and require a redraw/reload. This is an absolutely pitiful amount of apps, especially with the whopping 600-800 MB of free RAM that I usually have.
I also have the issue that sometimes even when I don't open a lot of apps, some of my apps like to force close for no reason after a few minutes of being idle. My MailDroid and Firefox apps seem to be extra susceptible to this random time based force close compared to GoSMS, which rarely closes after an inactive period of time.
I have tried multiple kernels, multiple ROMS, multiple governers and I/O schedulers, and I even tried zeppelinrox's V6 supercharger + multitask mods. Nothing I do seems to allow me to crack into that 600 MB of unused RAM. I am so flustered by this that I'm actually considering going back to TouchWiz.
Could anyone else provide me with some feedback with their multitasking app limits/free RAM? Is this a known CM10 issue?
TL : DR
-I can never get below around 600 MB (usually hovers around 700MB) of free RAM
-My running app limit seems to be 8-10 with about 6 widgets
-My apps seem to force close after short durations of inactivity
-I experienced NONE of these problems on TouchWiz
-Could someone post their numbers for some of these things, and is this a known problem for CM10?

Same problem here... I think most people like this problem though. Many like to see more free ram, but I prefer faster multitasking. My main concern is my downloads being closed and interrupted.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Yeah definitely a known issue on AOSP. Memory allocation issues I guess. I've never seen a dev comment on it, despite the fact it has been brought up several times. I suspect we won't get a fix until the JB sources are released for the d2.

Post your services.jar
If you used the windows tool to patch it, it may not have worked - I've made quite a few changes for greater compatibility since it's last update.
btw what are your minfree settings?
Did you do the aLogcat test?

zeppelinrox said:
Post your services.jar
If you used the windows tool to patch it, it may not have worked - I've made quite a few changes for greater compatibility since it's last update.
btw what are your minfree settings?
Did you do the aLogcat test?
Click to expand...
Click to collapse
Oh wow it's zeppelinrox! Hi
Yes, I used the Windows Jellyscream tool to patch my services.jar. The ICS Service Center in your script insists that it worked, but CM10 does not currently have a "Charge Only" or "No Action" mode when the cable is plugged in, I'm forced to mount the SD card(s). Your tool specifically says do not do that, but I don't really have a choice :/
My current MinFree values are:
8, 14, 40, 50, 60, 75
I have also tried the auto-calculated ones (which in my opinion leaves way too much free RAM theoretically):
8, 16, 325, 358, 390, 423
Both of them didn't seem to make a difference.
I have attached my services.jar to this post as well as requested.
As for aLogcat, I'm not sure what that is or how to do that

Hi
Well I can't open it up... is the file size correct?
Maybe it's an incomplete upload.
I assume that it's for ParanoidAndroid 2.50 so try upping it again since I haven't cracked one of those open yet lol
The service centre only looks at the supercharged launcher aspect and the windows exe isn't up to date for the multitasking mods.
I've actually just updated the ultimate jar script today... and also has an SGS3 specific edit
However it may be only for the stock rom.
The aLogcat test is described in the ultimate jar thread OP.

Weird, I'm also not able to open the one on my phone, that's kinda scary.
Ok, I'll give your new ultimate script a spin, and I'll look into the aLogcat thing as well and try to provide you some information.
Here's the services.jar file that was leftover in the Jellyscream directory (JellyScreamPatcherV6_0.9.0.6/framework/services.jar). I chose not to delete the temp files, so I'm guessing it's the same file.

WOOOOOOOOOOOOOOOOO!!!!
Wow you were right zeppelinrox, I tried out your Ultimate Jars script and BAM, my phone is hauling ass right now. Down to 234 MB of free RAM and none of my apps have force closed on me at the moment even after running ~20. Also, my list of cached apps is MASSIVE now, my RAM is finally being utilized!!!!
Time will tell if my apps auto-close after inactivity, but damn this is awesome, THANK YOU SO MUCH, you rock .
Hopefully the windows tool gets updated eventually so it's easier for people to do this, it was a bit tedious to figure it out haha xD
Edit:
My only question now is why oh why do the default AOSP settings suck so bad?

ChrisG683 said:
WOOOOOOOOOOOOOOOOO!!!!
Wow you were right zeppelinrox, I tried out your Ultimate Jars script and BAM, my phone is hauling ass right now. Down to 234 MB of free RAM and none of my apps have force closed on me at the moment even after running ~20. Also, my list of cached apps is MASSIVE now, my RAM is finally being utilized!!!!
Time will tell if my apps auto-close after inactivity, but damn this is awesome, THANK YOU SO MUCH, you rock .
Hopefully the windows tool gets updated eventually so it's easier for people to do this, it was a bit tedious to figure it out haha xD
Edit:
My only question now is why oh why do the default AOSP settings suck so bad?
Click to expand...
Click to collapse
I think that's to make me look good
I hope to have it automated somehow like the outdated ics webapp.
btw how did you decompile?
I'll try again when on the PC.
edit: ok that second one you posted opens up fine. I guess that's CM10?
It looks like CyanogenMod is following my lead... https://github.com/CyanogenMod/andr...mmit/9a8117c4f887c8b0df9cadb5d9aa7689a878752a
am: Allow more hidden apps on devices with lots of RAM
* If more than 1.5GB is present, allow up to 40 hidden apps. * Number is somewhat arbitrary, but was found to work well on D2. * Also look at the sys.mem.max_hidden_apps value if given.
Click to expand...
Click to collapse
Uh yeah... you get a 40 app limit only if you have 1.5GB of RAM - otherwise, you're STILL stuck at 15 hidden apps... lol
I had already seen the "sys.mem.max_hidden_apps" code in ProcessList.smali before the last script update - so that's already been bypassed to 70.
I just didn't know where that setting came from lol
So if you're on CM10, the Ultimate Jar Power Tools script that's currently available already fixes that.
Of course, "sys.mem.max_hidden_apps" was introduced after my mucking around

zeppelinrox said:
btw how did you decompile?
Click to expand...
Click to collapse
Hmm, I'm not sure what you are asking here, could you clarify?

zeppelinrox said:
I think that's to make me look good
I hope to have it automated somehow like the outdated ics webapp.
btw how did you decompile?
I'll try again when on the PC.
edit: ok that second one you posted opens up fine. I guess that's CM10?
It looks like CyanogenMod is following my lead... https://github.com/CyanogenMod/andr...mmit/9a8117c4f887c8b0df9cadb5d9aa7689a878752aUh yeah... you get a 40 app limit only if you have 1.5GB of RAM - otherwise, you're STILL stuck at 15 hidden apps... lol
I had already seen the "sys.mem.max_hidden_apps" code in ProcessList.smali before the last script update - so that's already been bypassed to 70.
I just didn't know where that setting came from lol
So if you're on CM10, the Ultimate Jar Power Tools script that's currently available already fixes that.
Of course, "sys.mem.max_hidden_apps" was introduced after my mucking around
Click to expand...
Click to collapse
hey zeppelinrox....
And to think, that I read some debates with users downplaying the usefulness of 2gb ram vs 1gb. When I was on my HD2 with Swap/Zram, I was using your script(s)...but at one point, I had OS AutoKilling disabled entirely (can't even remember how I did it) and was using a fairly complex Tasker profile(s) to Kill ALL if my memory ran down to a critical stage....all except apps that I put in an EXCEPTION list. So basically, I had MAX multitasking...and the use of all available memory unless I hit a critical threshold...and then, aside from those apps on the exception list, all other apps would get killed. To this day, I believe that Android should be built with an Exception list for power users similar to your Bullet Proof thing.
My Stock S3 rom and kernel seem to handle things pretty darn well. I use Go Launcher EX and experience zero redraws and my tests so far indicate that the OS has great multitasking behavior. I can open quite a few apps for a good amount of time. Eventually they get killed, but as you know, it's a bit unpredictable. When I last ran the memory down to about 250mb, which was very difficult to do even with large games, the OS hardly killed anything. It wasn't a scientific test but feel factor based. One of these days SOON, I need to play with your scripts again. Only reason I haven't with the s3...is because so far the stock setup is working really well.

ChrisG683 said:
Hmm, I'm not sure what you are asking here, could you clarify?
Click to expand...
Click to collapse
OH that's ok.
The second file you posted decompiled fine
themadproducer said:
hey zeppelinrox....
And to think, that I read some debates with users downplaying the usefulness of 2gb ram vs 1gb. When I was on my HD2 with Swap/Zram, I was using your script(s)...but at one point, I had OS AutoKilling disabled entirely (can't even remember how I did it) and was using a fairly complex Tasker profile(s) to Kill ALL if my memory ran down to a critical stage....all except apps that I put in an EXCEPTION list. So basically, I had MAX multitasking...and the use of all available memory unless I hit a critical threshold...and then, aside from those apps on the exception list, all other apps would get killed. To this day, I believe that Android should be built with an Exception list for power users similar to your Bullet Proof thing.
My Stock S3 rom and kernel seem to handle things pretty darn well. I use Go Launcher EX and experience zero redraws and my tests so far indicate that the OS has great multitasking behavior. I can open quite a few apps for a good amount of time. Eventually they get killed, but as you know, it's a bit unpredictable. When I last ran the memory down to about 250mb, which was very difficult to do even with large games, the OS hardly killed anything. It wasn't a scientific test but feel factor based. One of these days SOON, I need to play with your scripts again. Only reason I haven't with the s3...is because so far the stock setup is working really well.
Click to expand...
Click to collapse
Yes you were using dorimanx's trick to break the lowmemorykiller on HD2
He asked me to break it on ICS and above, which I did.
But that only lasted a day because I found another way to do it... boost number of running apps without breaking lowmemorykiller.
Needless to say, dorimanx got real happy lol.
See post 2 of the ultimate jar thread for more about that.
So yeah, you still have the app limit and lots of room for more multitasking since you can't get very low on ram.
I've added more mods to reduce the likelihood of apps closing on you. (Check the change log)
Sense users are ecstatic with the latest
Anyway, I'm sure that if you try it, you'll notice a difference - it's just a matter of you not knowing how much better it can be

What program are you using to put on the app kill exception list?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Deoxlar said:
What program are you using to put on the app kill exception list?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Deoxlar...are you asking me?
With the HD2, I had the OS rigged to NOT kill any apps EVER and used System Tuner Pro as my APP Killer with exceptions checked off. I used Tasker to determine the ram availability each time a window opened or changed, and Tasker would trigger STP when necessary.
But Zepplinrocks' V6 Supercharger as a very unique system for doing similar...but overall, it handles everything to do with ram management and better. Also, for some people's setup, it is a dramatic improvement...a FIX... a LIFE SAVER. (Basically the rom Devs are going to eventually slowly STEAL Zeps ideas. But we will not forget.
My old HD2 memory mngt system was an ALL or NOTHING workaround so it suffered in that regard.. The way my S3 with stock ICS is handling things right now is surprisingly good. I did a test last night opening as many apps as possible until I basically ran out of FREE ram. At that point, the OS was doing it's thing, killing another app or 2 so it could run the new app launched. Multitasking...or switching to newly launched apps and then returning to previously launched apps where they left off....worked near flawless and FAST on my i747m. When I woke up today, 3/4 of the apps were still in memory ready for resuming.
This is why I went from 2 years of OBSESSIVE flashing and tweaking....to using my new S3 with the Stock rom and about 1/100th of the tweaks. Super STABLE and not a slouch. I hope the upgrade to JB...well....is an UPGRADE. yadda yadda yadda...:good:

Hey, for shi.tz n giggles do that aLogcat test that I describe in the multitasking OP... I'd be interested to see what your max hidden app limit is
Install aLogcat, run as many apps as you can, run aLogcat and search for longer.
Most people get this before the mod...
{
"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"
}
The 16th hidden app gets killed because the limit is usually 15.

zeppelinrox said:
Hey, for shi.tz n giggles do that aLogcat test that I describe in the multitasking OP... I'd be interested to see what your max hidden app limit is
Install aLogcat, run as many apps as you can, run aLogcat and search for longer.
Most people get this before the mod...
The 16th hidden app gets killed because the limit is usually 15.
Click to expand...
Click to collapse
For you Zep, I do about any test you asked me to do! Respect! :good:
Stay tuned....possible depression, followed by possible "V6...light at the end of the tunnel".

themadproducer said:
For you Zep, I do about any test you asked me to do! Respect! :good:
Stay tuned....possible depression, followed by possible "V6...light at the end of the tunnel".
Click to expand...
Click to collapse
LOL thanks for the kind words man

zeppelinrox said:
LOL thanks for the kind words man
Click to expand...
Click to collapse
OK, I used System Tuner Pro's log and guess what....checked a dozen times....
hidden #51
Yup...and also using "free" in STP terminal, I have 115mb free close to 1.6gb used.
I cross referenced by reopening the apps and most of them were still in ram memory.
Actually, a few games I was testing almost 20hrs ago, were still in ram. That surprised me.
So these games/apps were not killed off by idle time auto killing.
This is why I haven't tried any CM or custom roms. This thing seems to be doing way better...then the forums would lead me to believe. I was FLASH happy with my HD2 and never quite satisfied but this thing is so much better...and mostly stock.
What do you think Zep...honestly, have you heard any similar reports?
UPDATE: now i am down to 83mb free...still rock solid smooth.

So, you're using the "ultimate jars" script in conjunction with which ROM? And did you use in conjunction with the supercharger script?
Just trying to understand exactly what is required to "fix" the multitasking issue.

themadproducer said:
OK, I used System Tuner Pro's log and guess what....checked a dozen times....
hidden #51
Yup...and also using "free" in STP terminal, I have 115mb free close to 1.6gb used.
I cross referenced by reopening the apps and most of them were still in ram memory.
Actually, a few games I was testing almost 20hrs ago, were still in ram. That surprised me.
So these games/apps were not killed off by idle time auto killing.
This is why I haven't tried any CM or custom roms. This thing seems to be doing way better...then the forums would lead me to believe. I was FLASH happy with my HD2 and never quite satisfied but this thing is so much better...and mostly stock.
What do you think Zep...honestly, have you heard any similar reports?
UPDATE: now i am down to 83mb free...still rock solid smooth.
Click to expand...
Click to collapse
Wow I've never heard of a stock rom having the app limit set to 50.
However when you type free in terminal, how much is system tuner reporting as free?
There is a difference because the free command in terminal is always very low whereas apps like system tuner/task managers always report free ram as "free ram + cached apps" which is a much bigger number.
Can you post a deodexed services.jar (it's probably odex tho since it's a stock rom) or at least the smali files?
The windows patcher should be able to decompile it.
If it's not sense I'd only have to look at ActivityManagerService.smali and ProcessList.smali.

AOKP RAM issues

i've have AOKP_JB_MR1_Build-6 and its been good.
My only complaint is the ram usage. I know most of you
guys are firm believers in letting the system manage the memory.
I enabled the the ram bar in the apps switcher, and
I constantly have 22 mb of ram out of 654 MB.
My phone constantly feels slow and lags.
When I clear all the apps, and regain Ram
my phone feels speedy, and runs good.
A phone with 1GB of Ram shouldn't be slow
or eat this much ram. Are there bugs or what?
Thanks guys

beniamin said:
i've have AOKP_JB_MR1_Build-6 and its been good.
My only complaint is the ram usage. I know most of you
guys are firm believers in letting the system manage the memory.
I enabled the the ram bar in the apps switcher, and
I constantly have 22 mb of ram out of 654 MB.
My phone constantly feels slow and lags.
When I clear all the apps, and regain Ram
my phone feels speedy, and runs good.
A phone with 1GB of Ram shouldn't be slow
or eat this much ram. Are there bugs or what?
Thanks guys
Click to expand...
Click to collapse
@beniamin it doesnt lag for me at all even with high ram usage i got like 4 mb free right now and it runs butter smooth lol fyi -im running it with purity v30 kernel

It's partially an AOKP thing and also a 4.2 thing. AOKP and CM always ate more RAM for me since ICS.
On stock 4.2, ram management is also bad.
Everyone like to say android bla bla bla manages RAM well bla bla bla.
Android manages RAM well IF the core system doesn't rape RAM.
So basically the android uses some ram. And leaves the remaining ram for caching apps all the time. Now when the system runs out ram, the phone will kill an app to free RAM. Sounds good right? Well, the problem is that on 4.2, the system eats up so much RAM that apps don't even get a chance to be cached. And when you switch over to another app the system will kill other apps first then launch your requested app. This whole process takes a long time as the system is now hogging more ram all the time.
The best part is the system will continue to leak more and more ram as uptime increases.
As 4.2 have so many RAM leaks,the only quick solution will be to use a 4.1 rom.
I measure RAM used like this, works pretty well. Go to settings - apps - running. The blue is Android system + services. Services are apps that will not be killed unless absolutely necessary. Gray is not exactly "free RAM". The gray portion is the amount of RAM the system can use for caching purposes. You actually want the gray portion to be as high as possible.
A picture of 4.1 and 4.2 can sum this entire paragraph xD
I use stock 4.1 and 4.2 as comparison as custom roms almost always have higher ram utilisation.
On stock 4.1,
{
"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"
}
On stock 4.2
Sent from my Galaxy Nexus using Tapatalk 4 Beta

What's going on?
Linux is borrowing unused memory for disk caching. This makes it looks like you are low on memory, but you are not! Everything is fine!
Why is it doing this?
Disk caching makes the system much faster! There are no downsides, except for confusing newbies. It does not take memory away from applications in any way, ever!
What if I want to run more applications?
If your applications want more memory, they just take back a chunk that the disk cache borrowed. Disk cache can always be given back to applications immediately! You are not low on ram!
Do I need more swap?
No, disk caching only borrows the ram that applications don't currently want. It will not use swap. If applications want more memory, they just take it back from the disk cache. They will not start swapping.
How do I stop Linux from doing this?
You can't disable disk caching. The only reason anyone ever wants to disable disk caching is because they think it takes memory away from their applications, which it doesn't! Disk cache makes applications load faster and run smoother, but it NEVER EVER takes memory away from them! Therefore, there's absolutely no reason to disable it!
Why does top and free say all my ram is used if it isn't?
This is just a misunderstanding of terms. Both you and Linux agree that memory taken by applications is "used", while memory that isn't used for anything is "free".
But what do you call memory that is both used for something and available for applications?
You would call that "free", but Linux calls it "used".
Click to expand...
Click to collapse
AOKP and android respect this concept, AOKP use more ram because loading more App ( idk why ) on memory, there's no lag. The system will be more smooth and faster than before, because AOKP don't reload from disk app but "launch" from ram ( ram is alot faster than SSD ).
If this things cause lag, there's some "malformed" app that use resource.

d0ge01 said:
AOKP and android respect this concept, AOKP use more ram because loading more App ( idk why ) on memory, there's no lag. The system will be more smooth and faster than before, because AOKP don't reload from disk app but "launch" from ram ( ram is alot faster than SSD ).
If this things cause lag, there's some "malformed" app that use resource.
Click to expand...
Click to collapse
Doesn't matter what they say, if you feel that there is lag when you are using your phone, then there is lag, no 2 ways around it.
4.1.2 is more fluid than 4.2.2 with the same apps running for me, seems like a memory leak issue on 4.2.2, hopes 4.3 fixes this..

Here is the comparison of AOKP vs AOSP 4.2 ( dark and grey backgrounds accordingly). The setups are 95% identical - same apps, same usage pattern. After some time both needs to rebooted due to memory leaks
Sent from my Galaxy Nexus

g1DDriver said:
Here is the comparison of AOKP vs AOSP 4.2 ( dark and grey backgrounds accordingly). The setups are 95% identical - same apps, same usage pattern. After some time both needs to rebooted due to memory leaks
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
i saw screen, but i don't think there are some memory leak, AOKP team hardly work over to fix them, anyway it's possible, but i used AOKP 4.2 for without any problem, without rebooting for days ( max uptime is 4 days )

d0ge01 said:
i saw screen, but i don't think there are some memory leak, AOKP team hardly work over to fix them, anyway it's possible, but i used AOKP 4.2 for without any problem, without rebooting for days ( max uptime is 4 days )
Click to expand...
Click to collapse
I was talking about memory leaks in Android in general (not AOKP related), and that's definitely the case with 4.2 The screens are for demonstration that AOKP needs more RAM to begin with. If you try most recent PA builds with halo, there you need even more memory. I guess it the price you pay for additional stuff under the hood
Sent from my Galaxy Nexus

my thoughts about this RAM issues:
https://plus.google.com/u/0/106590215548240805185/posts/MECZP5mqKfJ

beniamin said:
i've have AOKP_JB_MR1_Build-6 and its been good.
Click to expand...
Click to collapse
Why are you running an old build? Try updating to the 5/18 build or even Milestone 1 after a full wipe and don't restore any apps until you see if the RAM issue's still there.
Sent from my Mahjong Nexus

Try to reinstall another rom

Finally!! I thought it was just me. It was same for me on CM,AOKP,PA,AK47, all of them....I dont know why. I have greenify, plus I try to make sure least no. of apps run in background.
Finally switched to stock 4.2.2. Not a big issue now, very very rarely does it go below 80mb. Plus its fairly smooth. Oh well.....

I've never had lag issues with AOKP and ram

Try Using....
beniamin said:
i've have AOKP_JB_MR1_Build-6 and its been good.
My only complaint is the ram usage. I know most of you
guys are firm believers in letting the system manage the memory.
I enabled the the ram bar in the apps switcher, and
I constantly have 22 mb of ram out of 654 MB.
My phone constantly feels slow and lags.
When I clear all the apps, and regain Ram
my phone feels speedy, and runs good.
A phone with 1GB of Ram shouldn't be slow
or eat this much ram. Are there bugs or what?
Thanks guys
Click to expand...
Click to collapse
I run Aokp 4.2.2 Milestone Build with Franco Kernel, I was having a pretty similar issue not so much of the lag necessarily but my ram drain was unbelievable, well anyway i was on "Android Police" one day and was reading an article about apps running in background blah blah blah and came across an app recommendation called "GREENIFY" You go threw and hibernate a few if not all the apps that dont have anything to do with the system like Facebook or GMapps, Gmail Etc... and once they are grennifyed they will stay closed no random background data will start app untill you either open that app again or you go back in and ungreenify it, the only downfall (and only to some) is that, say you greenify facebook you will not receive instant notifications from a post or msg etc... Ive been using this for almost three months now, works awesome it remembers all the apps you greenify and will stay every time you reboot your phone,
---------- Post added at 07:51 AM ---------- Previous post was at 07:45 AM ----------
Rich8692 said:
I run Aokp 4.2.2 Milestone Build with Franco Kernel, I was having a pretty similar issue not so much of the lag necessarily but my ram drain was unbelievable, well anyway i was on "Android Police" one day and was reading an article about apps running in background blah blah blah and came across an app recommendation called "GREENIFY" You go threw and hibernate a few if not all the apps that dont have anything to do with the system like Facebook or GMapps, Gmail Etc... and once they are grennifyed they will stay closed no random background data will start app untill you either open that app again or you go back in and ungreenify it, the only downfall (and only to some) is that, say you greenify facebook you will not receive instant notifications from a post or msg etc... Ive been using this for almost three months now, works awesome it remembers all the apps you greenify and will stay every time you reboot your phone,
Click to expand...
Click to collapse
http://www.androidpolice.com/2013/02/15/new-app-greenify-keeps-rooted-devices-running-smoothly-by-hibernating-specified-apps-when-theyre-not-in-the-foreground/
Enjoy! Hopefully that helps.

[Q] 4.3 high RAM usage?

I did fresh install of 4.3 and it runs very nice... well until it runs out of RAM.
I`ve noticed this couple of times that device slows down and when I press home icon there`s nothing on the "desktop" only launcher apps icon and I have to wail couple of seconds while thing loads into memory...
I don`t have many 3rd party apps and have disabled some on the system side.
When problem occurs I can see in Settings that there is only 30-40MB of RAM left.
For an example I was surfing today (system browser) while listening to music with doubletwist music player and doubletwist suddenly stopped playing because it was stopped to free some memory for browser...
Anybody noticed this too?
There is obviously a high memory usage on 4.3. Any advice for this?
I`m running stock unrooted
Sorry for my bad english

ciao sei italiano vero? Cmq io ti consiglierei di aspettare la cyanogen 10.2 è sempre meglio ottimizzata rispetto alla stock, I have the same problem with 4.2.2 but with greenify(app) and lagfix free, is partitially solved, or you can try to set 4 app backgroud in developer option and disable all animation in developer option

ram usage should be fine on stock. on cm10.2 this is the situation after 50 hours of uptime
{
"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"
}

shriom_manerker said:
ram usage should be fine on stock. on cm10.2 this is the situation after 50 hours of uptime
Click to expand...
Click to collapse
I hope you're not saying that screen shot is an example of fine, you've got basically no memory free.
Memory use in 4.3 is definitely higher. You can pretty much forget about multitasking with Chrome now, as soon as I start using it other apps start getting killed left and right.

pfmiller said:
I hope you're not saying that screen shot is an example of fine, you've got basically no memory free.
Memory use in 4.3 is definitely higher. You can pretty much forget about multitasking with Chrome now, as soon as I start using it other apps start getting killed left and right.
Click to expand...
Click to collapse
Think you might have hit on the magic word.... Chrome (or any other browser). On the Xperia forum lots are noticing that browsers (all of which open @ about 40MB ram usage) are just continuing to grow in ram usage, even when not being used, to ridiculous levels (100's of MB)
Maybe you could take a look at individual process ram usage and report back.... Curious to see if there's the same happening on GNexi
sent from my still superb Google I/O 7510 (xda hd)

pfmiller said:
I hope you're not saying that screen shot is an example of fine, you've got basically no memory free.
Memory use in 4.3 is definitely higher. You can pretty much forget about multitasking with Chrome now, as soon as I start using it other apps start getting killed left and right.
Click to expand...
Click to collapse
what i meant was , it is definitely high on cm10.2 roms but its fine on stock roms and stock based custom roms like catacalysm, the free ram is about 120 mb even after 50 hours of usage but on cm 10.2 and other JSS15J based roms its really crazy and phone runs out of memory

tanasczn said:
You can pretty much forget about multitasking with Chrome now!!!
Click to expand...
Click to collapse
Almost all the browsers are facing memory issues.
I use a few other browsers like Dolphin and UC and even they are eating up memory
Especially during downloads, these browsers crossed 170MB RAM usage :cyclops:
You can send feedback to help the devs to help them with this.
But I'm sure they have already started working on these issues.

tanasczn said:
You can pretty much forget about multitasking with Chrome now!!!
Click to expand...
Click to collapse
neerajvd said:
Almost all the browsers are facing memory issues.
I use a few other browsers like Dolphin and UC and even they are eating up memory
Especially during downloads, these browsers crossed 170MB RAM usage :cyclops:
You can send feedback to help the devs to help them with this.
But I'm sure they have already started working on these issues.
Click to expand...
Click to collapse
So this pretty much confirms what i asked in post #5

Possibly related to DoubleTwist?
For an example I was surfing today (system browser) while listening to music with doubletwist music player and doubletwist suddenly stopped playing because it was stopped to free some memory for browser...​
I am running stock rooted 4.1.1 on my toroplus and am only posting here because DoubleTwist (DT) was mentioned in OP. DT must be a memory hog because when I try to stream music with DT over BT simultaneously with Google Nav, DT and Google Nav seem to knock each other out of memory, i.e., sometimes DT will quit while Nav remains running and other times Nav will quit while DT remains running. Bottom line is both apps won't stay running simultaneously for any appreciable length of time.
I then used Poweramp for BT streaming and experienced no such issues, that is, I can listen to music and turn-by-turn nav directions at same time w/o apps killing each other off.

.....uh.... JSS15J isn't a build for the gnex. JWR66Y is.
a manta sent this.

I'm running 4.3 (second update) on a stock galaxy necus ROM (takju) and my free ram nowadays is 18MB
When i restart the phone i get about 350MB of RAM free, which immediately start decreasing as i use the phone until it gets to the 18MB.
I know i ran out of memory when i press the home button and i have to wait for the items to be drawn on the desktop again ... I'm considering flashing back to original 4.3 or 4.2 because of this

Free ram is idle ram... Having free ram means its lazy and not doing anything. High ram usage simply means apps are stored in it... Shouldn't really concern yourself with ram.
Sent from my Galaxy Nexus using xda app-developers app

cstrife999 said:
Free ram is idle ram... Having free ram means its lazy and not doing anything. High ram usage simply means apps are stored in it... Shouldn't really concern yourself with ram.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
...but having more idle RAM means you have space for more running background apps, i.e. apps will be less probably closed and cleared out of RAM. If one really runs that many app, the difference of free RAM actually tells.
And my GNex always has ~500MB free RAM (not just after boot!), ready for action.
Sent from Google Nexus 4 @ CM10.2

cstrife999 said:
Free ram is idle ram... Having free ram means its lazy and not doing anything. High ram usage simply means apps are stored in it... Shouldn't really concern yourself with ram.
Click to expand...
Click to collapse
No, the memory is being used up by the system not by apps. The system should use as little memory as possible so that it is available to your apps. Wasted memory is as bad as fee memory, either way it's not being put to proper use.

so basically there's a lot of talk about this,a lot of people with the same problem and no solution whatsoever !?

AndyYan said:
...but having more idle RAM means you have space for more running background apps, i.e. apps will be less probably closed and cleared out of RAM. If one really runs that many app, the difference of free RAM actually tells.
And my GNex always has ~500MB free RAM (not just after boot!), ready for action.
Sent from Google Nexus 4 @ CM10.2
Click to expand...
Click to collapse
Can u tell me how u get so much free ram.
sent from a phone running on SLIM ROM

This is my ram usage before and after a game my phone still runs smooth and fast as someone said left over ram is lazy if you have left over ram be great full. Touchwiz always uses alot of ram from my experience
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

DaveyRepairs said:
This is my ram usage before and after a game my phone still runs smooth and fast as someone said left over ram is lazy if you have left over ram be great full. Touchwiz always uses alot of ram from my experience
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

atishey23 said:
Can u tell me how u get so much free ram.
sent from a phone running on SLIM ROM
Click to expand...
Click to collapse
Advanced Task Killer Pro (kill ALL apps except Launcher and IME) and Autostarts (ban most auto-start privileges for apps, prevents apps from eating up memory automatically).
Do note that this is not practical for daily use, as this may sacrifice some functionalities (e.g. Bluetooth file transfer function). I don't use my GNex as my primary device so it doesn't matter for me. You can still get ~400MB free RAM if you don't ban privileges related to functionalities.
Sent from Google Nexus 4 @ CM11
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
DaveyRepairs said:
This is my ram usage before and after a game my phone still runs smooth and fast as someone said left over ram is lazy if you have left over ram be great full. Touchwiz always uses alot of ram from my experience
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
...It doesn't look like you have a GNex...
Sent from Google Nexus 4 @ CM11

I wouldn't recommend to use a task killer.
A better solution is Greenify which hibernates the app if it is in background. It's using less RAM when hibernated but it is started pretty fast if needed.
Another solution would be to flash a big memory kernel, or use ZRAM.
You can also try Android 4.4 where the RAM management improved a lot.