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.
Related
i have been in search for something to speed up the desire and decided that task managers just **** your phone up .... I was surfing the web the other day for new programs to use and came across a program called "memory boost" ITS SUPERB .... the lite version is free and available on market
the phone since installing is so fast and definately stable ... I upgraded to the full program for $1.99 (click upgrade on the program)
the program keeps your ram at a optimal level ..... it doesnt cause the phone any issues and its remained stable unlike a lot of task managers
the upgrade is via paypal and not the market - I was initally worried but shouldnt have been cos as soon as I paid the link arrived via email at the same time as the paypal confirmation - the download is via pc as you cant do it via your phone
HIGHLY RECOMEND
was going to download it and try it, but i seriously can't find 1 decent review
"Probably does work for most people, but just slowed the system"
"It freed mem on myTouch3G but killed some apps I wanted running! Then graph shows the mem is taken back up? Pointless! Not needed!"
"just killed everything, even my Atk manager then want a $1.99 for full version. ...junk"
it must have been improved since you used it - it really speeds up the system and it hasnt killed anything important ...
as said when i used task killers it screwed my phone up .. touch wood it is running like a well oiled machine
Where do I get this?
-------------------------------------
Sent via the XDA Tapatalk App
"the phone since installing is so fast and definately stable"
Does that mean the Desire without this app isnt fast enough and isnt stable (keeps crashing)?
Search memory boost in market top application
If you like it defo suggest upgrade to pro version which is done via app press menu when in app and follow instructions
-------------------------------------
Sent via the XDA Tapatalk App
no it means that it sometimes lags ..... happy with normal speed but a boost is always good !!!
plus task killers makes the phone unstable (what i meant not the desire)
i have bought the app...gonna try it out....
This sounds a lot like a commercial from the creator of the program.
"Have you always had trouble getting your Desire to run fast? Well, not anymore. Try Ultraboostfastmegasuper optimizer! It will improve your mom."
Sorry if this offends anyone, but someone saying "I really think you should consider buying it" gets my guard up.
By the way. Autokiller does the same and is free ;o)
Auto killer made my phone unstable. Been using this for a few days had no problems what so ever
-------------------------------------
Sent via the XDA Tapatalk App
You will most probably find its an automatic task killer, seeing as the only way to free up RAM is to actually stop processes from using it, it will be killing tasks in the background rather than letting the user select them via a UI like most do. In my opinion best avoided. I won't be using it, just let Android do what it does, and reboot yer phone every couple of days and all will be well.
-------------------------------------
Sent via the XDA Tapatalk App
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
This sounds a lot like a commercial from the creator of the program.
"Have you always had trouble getting your Desire to run fast? Well, not anymore. Try Ultraboostfastmegasuper optimizer! It will improve your mom."
Sorry if this offends anyone, but someone saying "I really think you should consider buying it" gets my guard up.
By the way. Autokiller does the same and is free ;o)
Click to expand...
Click to collapse
Yeah.he is just selling it.i've seen posts like this before.
-------------------------------------
Sent via the XDA Tapatalk App
have the decency of posting it in themes and apps
does using apps to kill open processes make the phone unstable?? I've been using advanced task killer for over 1 month and so far my phone is fine, i open it after several hours to find maybe 12 apps open, meaning I would have maybe 40mb or 50mb free.. then after killing all open up it jumps to 150mb free.
If google has designed the phone to handle open apps properly then why does the ram memory get so low??
any info would be great - I like learning new stuff
It doesn't /get so low/
THAT'S THE WAY LINUX WORKS
1. Overview of memory management
Traditional Unix tools like 'top' often report a surprisingly small amount of free memory after a system has been running for a while. For instance, after about 3 hours of uptime, the machine I'm writing this on reports under 60 MB of free memory, even though I have 512 MB of RAM on the system. Where does it all go?
The biggest place it's being used is in the disk cache, which is currently over 290 MB. This is reported by top as "cached". Cached memory is essentially free, in that it can be replaced quickly if a running (or newly starting) program needs the memory.
The reason Linux uses so much memory for disk cache is because the RAM is wasted if it isn't used. Keeping the cache means that if something needs the same data again, there's a good chance it will still be in the cache in memory. Fetching the information from there is around 1,000 times quicker than getting it from the hard disk. If it's not found in the cache, the hard disk needs to be read anyway, but in that case nothing has been lost in time.
Click to expand...
Click to collapse
The percentage of RAM used by the cache doesn't affect in any form or shape the battery or the performance of your phone, since it will be freed when another app needs it.
The only point of Task Killers is to kill background apps that may consume CPU % (but then again, if they're coded the way they're supposed to, it doesn't happen.)
{
"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"
}
Fitting picture.
http://www.linuxatemyram.com/
koolbear said:
i open it after several hours to find maybe 12 apps open, meaning I would have maybe 40mb or 50mb free.. then after killing all open up it jumps to 150mb free.
Click to expand...
Click to collapse
It's an intelligent utilization of resources!
Android will keep stuff in memory whilst it can to improve performance, and will start killing things of itself if resources get too low. Note that just because an app is open and "consuming" memory doesn't mean it is consuming CPU cycles and battery power.
Having loads of free memory is actually just a waste of resources.
Regards,
Dave
Hmm.. no 'fence but sounds a little like a sales pitch to me.
-------------------------------------
Sent via the XDA Tapatalk App
I don't use so called cleaners, and their idea's aren't factual. I do use one basic app to kill two very rarely used installed apps which start running at boot without giving an option to disable, since they maintain a CPU wake lock losing me heavy battery-life.
It is also used to kill processes that are running in the background and not emptying their cache, when my storage memory falls to 15MB due to their heavy cache use (occurs rarely), and so when I need to install some app but it won't install giving me the low memory warning (where emptying cache through App Manager in Settings doesn't work).
Last use is for three buggy apps, one being the Chrome browser, which at times takes my memory down to 5% in use, and after throwing it to low priority through the back button because I need to use another app, won't let go of that memory space for other apps and so many apps start crashing including Sense, and others fail to open complaining of low memory, until I manually kill it. The automated kernel management doesn't suffice here and a task manager is useful here.
Other than that, avoid them like most "cleaners" for Windows with a PC. As someone said, maximizing use of available resources like OS memory is an efficient scheme overall.
-------------------------------------
- Sent via my HTC Desire -
foxmeister said:
It's an intelligent utilization of resources!
Android will keep stuff in memory whilst it can to improve performance, and will start killing things of itself if resources get too low. Note that just because an app is open and "consuming" memory doesn't mean it is consuming CPU cycles and battery power.
Having loads of free memory is actually just a waste of resources.
Regards,
Dave
Click to expand...
Click to collapse
mate thanks for clarifying what you, sruon and others have said makes total sense.. so I'll sit back and allow the device to handle ram memory by itself.
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?
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.
Hi,
working daily with linux-OS and beeing actively using custom roms since Android 2.1 I have a bit of knowledge on RAM usage on Linux and Android. As many know and like to post "free RAM is wasted RAM" - we all know that. But why? Because all not actively used RAM (lets call it "free") can be used as a cache for applications you likely will need in future. But what if your GNEX runs out of free RAM an is not able to cache any more? What if you start a new huge application like your browser and free RAM has to be obtained to give it to your starting application? Yes - bad things can happen!
But lets start from the beginning:
1. If you go to Settings->Applications->Running you get the RAM-bar at the bottom of the screen. This is splitted in two parts: used and free (like defined above). Used RAM seems to be actively allocated RAM which cannot be used for other things like starting applications and free is the RAM which can be obtained because it only containes caches apps which are not running.
2. Directly above that bar you se a kind of brace which seems not to be just eye-candy but has some meaning: The lower and thiner part of that brace seems to show the part of that RAM (used or free) that is used by the applications/service in the list above. Example: if you switch to cached applications the brace will jump to that part of the bar and by killing some of the cached apps you will change the width of the brace.
Lets put things together:
viewing the used RAM you will notice that the brace does not cover the whole used-ram-bar but, in my case, about the half. I also noticed that the width of the brace does not change greatly with uptime of the device as all listed services will stay at their size more or less so their sum is not going to change greatly. In my case all services sum up to about 250MB meaning the braces width is about 1/3 of the screen assuming that GNEX has 700MB total RAM (the rest of 1GB total physical RAM is allocated to other parts of the SOC-chip like Baseband and GPU and not available to linux-kernel or android).
But one thing does change greatly!!! The part of the used-ram-bar which is not covered by the brace will be very small after rebooting and will grow with uptime. As the part covered by the brace is a fixed factor this means that the free ram is the trade-off for the growing uncovered part of the used-ram. In my case I get after rebooting the device: 250MB free, 450MB used of which 250 are covered by the brace, leaving 200MB used RAM for whatever (kernel, non-android stuff like filesystem caches, ideas?) After some days of usage this changes to 50MB free, 650MB used of which still about 250MB are covered by the brace, leaving 400MB used for other things (NOT app-cache).
Consequences:
From the assumptions above this means that android is not able to cache apps anymore (because they live in the free RAM) and my device beginns to lag while opening new apps. To obtain enough RAM for starting apps like browers (stock or firefox tested) it will even need to kill services!!! And in extreme low-memory situations it even kills the foreground app you are using (to me it happened while I used firefox). Also when you go to settings->applications->running again you will notice that android will be restarting your services over and over again to obtain more RAM without much success. In the situations my actively used firefox got killed something different happened: the launcher also had been killed because it was starting over but more importently settings->applications->running showed that much of the used RAM not covered by the brace was gone! Free RAM jumped from 50MB to about 200MB which is nearly what I get after a fresh reboot. I assume that in this extreme low memory situation also the kernel did clean up things.
From my observations you will get the following if your free RAM accoring to settings->applications->running is very low:
1. no cached apps if you swich to settings->applications->running->cached
2. laggy phone
3. your launcher gets killed more oftern when returning from e.g. browser
4. more apps get killed when returning to launcher meaning that they will get restarted if you return to that app
5. in low memory situations (app does not fit into free-RAM-part) services will get restarted frequently
6. in extreme low-memory situations kernel cleans up everything (i guess)
The question now is: what is using so much RAM and growing over uptime until our GNEX has no more free RAM? I alread checked different ROMs including stock 4.1.2, stock 4.2.2 slimbean 4.2.2 cm10-stable cm10.1-nightly and all of them show this behavior. The only thing I noticed: all 4.1 ROMS perform better in this area: their RAM does not fill up that quickly but it does. On 4.2 ROMs it takes just few days to run out of free RAM for me. I already wiped my device and installed only realy needed apps (20 out of 140!!!) but it still happens.
I think this happen in any OS
A daily reboot is always a must in my opinion, to free ram, to stop some services, to stop wake locks, to stop battery drain without sense..
Inviato dal mio Galaxy Nexus con Tapatalk 2
That's what always makes me ask : Is Gnex really have 1gb of memory?
Other phones with same spec. uses same OS have more than 693mb that in gnex , why the hell our phone has the lowest read ram in 1GB category phones
I'm sure this is the only weak-point in gnex
300MB is GPU reserved for camera.
madd0g said:
300MB is GPU reserved for camera.
Click to expand...
Click to collapse
Why?
Sent from my Galaxy Nexus using Tapatalk 2
I didn't engineer the device. But I presume it's a requirement by the GPU PowerVR chip, since it uses alot of RAM on the Nexus S, which had the same chip only downclocked. It was 330MB usable out of 512MB advertised there. The amount reserved is bigger on GN obviously because of HD video capture option.
madd0g said:
I didn't engineer the device. But I presume it's a requirement by the GPU PowerVR chip, since it uses alot of RAM on the Nexus S, which had the same chip only downclocked. It was 330MB usable out of 512MB advertised there. The amount reserved is bigger on GN obviously because of HD video capture option.
Click to expand...
Click to collapse
I agree GPU shared system RAM, but 300MB is wayy too much bro. I checked my N4 it has 1.82GB of 2GB total considering N4 Adreno and camera chip is more powerful than i9250
It's (again probably) not because of the speed/power etc. but that it's like that by design. Adreno ain't the same as the one used on GN, so there's no comparison.
I'm sure Google didn't allocate that much memory just to screw us up, but instead there's a legit need for it. For instance, the amount of RAM available on a Galaxy S2 is much bigger, around 830-850MB out of 1 GB and it has a completely different camera/GPU combo, spite full HD video and 8 mpix instead of GNs 5. That's why I presume it's just PowerVRs "fault".
Perhaps, i just checked galaxy tab 2 ics available ram, it less than 700, but after flashed stock JB, it shows more RAM, about 770MB. Tab 2 uses OMAP and PowerVR right? Imho. i just curious why it reserves so much ram. Searched google and can't found the reason :S
Sent from my Galaxy Nexus using Tapatalk 2
*Update*
An galaxy S2 with all stock (Android 4.1.2) shows the same amount of used RAM after 10 days of uptime (380MB free and 380MB used - a nearly perfect 50/50 ratio). No sign of degradation so far. Honestly this phone is not used much but still it feels very different from what I see on my Gnex.
Has someone shorlty fully wiped and reflashed his phone to stock 4.2.2 (JDQ39). How does the RAM usage look like after fresh reboot?
RAM problem
This is what i get today. Using liquidsmooth 2.4 fraco kernel. But i know its not abut apps i use. I dont know where are all that RAM. After reboot with same apps runing in background i have 230-260MB free RAM. But if i using phone day or so it look like this.
Phone get laggy, slow with high latency. Im not sure if its 4.2.2 bug for Gnex or just some mess with ROM but its same on any custom ROM. ill try flash stock and see what i get.
castaway1 said:
This is what i get today. Using liquidsmooth 2.4 fraco kernel. But i know its not abut apps i use. I dont know where are all that RAM. After reboot with same apps runing in background i have 230-260MB free RAM. But if i using phone day or so it look like this.
Phone get laggy, slow with high latency. Im not sure if its 4.2.2 bug for Gnex or just some mess with ROM but its same on any custom ROM. ill try flash stock and see what i get.
Click to expand...
Click to collapse
I'm experiencing the same problem with AXI0M and AK kernel.
castaway1 said:
This is what i get today. Using liquidsmooth 2.4 fraco kernel...
Click to expand...
Click to collapse
Hi, this is exaclty what i was talking about... very frequent service restarts and laggy phone and even basic things like keyboard and music-playback can quit while in use. While I tried to compose an email to send a screenshot to my desktop to post it here my stock-mail-app died and the phone rebooted. At least I have now both an after reboot and an after two days of using PARANOID ROM screenshot
I recently switches to PARANOID 3.55 and now have even more issues as the phone boots with just 200MB free RAM. This ROM seems to demand very much RAM.
BTW. I installed Stock for more than a week before switching to PARANOID and had around 260MB free after booting and around 150MB free after some days of usage. Increase was ways lower than on any custom rom. Can anyone comment on this? Same or contrary stock-experience?
Stock JDQ39 rooted. (running one week)
kernel stock or lean both are perfect and have no affect RAM or smoothness. Screenshot is after some days of full usage. Battery life i getting is about 1day with 2h screen on.
now someone tell me that its not custom ROM problem. 4.2.2 stock is just awesome. Im sad that custom ROMs not..
castaway1 said:
Stock JDQ39 rooted. (running one week)
kernel stock or lean both are perfect and have no affect RAM or smoothness. Screenshot is after some days of full usage. Battery life i getting is about 1day with 2h screen on.
now someone tell me that its not custom ROM problem. 4.2.2 stock is just awesome. Im sad that custom ROMs not..
Click to expand...
Click to collapse
2h screen time is really bad..
But nice to know that stock works well for you..
Mach3.2 said:
2h screen time is really bad..
But nice to know that stock works well for you..
Click to expand...
Click to collapse
its average +/- 30min and for me its not so bad for 24h
castaway1 said:
its average +/- 30min and for me its not so bad for 24h
Click to expand...
Click to collapse
As long as it makes your boat float, why not?
Beamed from my Grouper
castaway1 said:
Stock JDQ39 rooted. (running one week)...
Click to expand...
Click to collapse
Next step would be to deodex this ROM and to try again because Stock is odexed in contrast to any custom rom. I realy would like to figure out the reason for this bad RAM usage on custom roms.
fajabird said:
Next step would be to deodex this ROM and to try again because Stock is odexed in contrast to any custom rom. I realy would like to figure out the reason for this bad RAM usage on custom roms.
Click to expand...
Click to collapse
yes im on odexed rom. and im curious if deodexing some custom ROM will help with this. I think about slighty modified vanilla rascarlo ROM with kernel that work perfect lean 6.4 is smooth like stock and dont broke anything. Its deodexed rom so i can propably try THIS to odex it.
http://fitsnugly.euroskank.com/?rom=rasbeanjelly&device=maguro-vanilla
castaway1 said:
... im curious if deodexing some custom ROM will help with this...
Click to expand...
Click to collapse
I thing you ment odexing some custom ROM, right? I'm thinking about to try the odex-me apk you can find on XDA which will odex all apks from /system/app but leave the framework.jar stuff untouched. But its far more easy to deodex the stock ROM and to try again
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.