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.
Is it possible to run this script from galaxy w? I have some ram issues and sometimes my phone lags.
In running services these applications are always open:
Facebook
hotmail
go launcher ex + go launcher notification + go locker
maps
swiftkey
I have read somewhere that this script is not very good with multitasking but it makes the phone run faster and smoother. These applications are considered in multitasking? Or in this case multitasking means for example to have messaging, browser etc running at the same time?
Thanks
Yes u can install v6 script in GW
Ur phone will be faster
But u should search the forum before posting
From My GWonder
Okay thank you!
Sent from my GT-I8150 using xda app-developers app
I've had some probless with supercharger, when closing apps with stock task manager, launcher would always close, and have to reload all the apps and widgets (stock touchwiz launcher). Can this be solved?
Sent from my bananaphone.
piefert said:
I've had some probless with supercharger, when closing apps with stock task manager, launcher would always close, and have to reload all the apps and widgets (stock touchwiz launcher). Can this be solved?
Sent from my bananaphone.
Click to expand...
Click to collapse
That is called "Launcher Redraw", technically, when you clear memory or run a resource-demanding apps, Launcher will be killed as well to give more memory.
To prevent this, set the "lock home in memory" option in V6Supercharger. Note that doing this will make your home launcher unkillable and thus your free memory will be lower.
My advice: If you do want to lock launcher in memory, use a low memory usage launcher, such as zeam, Go Launcher uses too much memory.
Hope this helps.
Reidzeibel
Sent from my Modded Stock DXLA2 (Didn't have the mood to update)
I installed Supercharger on my phone and now it works better altough some games runs slower and freezes on my device,
reidzeibel said:
That is called "Launcher Redraw", technically, when you clear memory or run a resource-demanding apps, Launcher will be killed as well to give more memory.
To prevent this, set the "lock home in memory" option in V6Supercharger. Note that doing this will make your home launcher unkillable and thus your free memory will be lower.
My advice: If you do want to lock launcher in memory, use a low memory usage launcher, such as zeam, Go Launcher uses too much memory.
Hope this helps.
Reidzeibel
Sent from my Modded Stock DXLA2 (Didn't have the mood to update)
Click to expand...
Click to collapse
Ehhh??
Lock home in memory is not in V6....actually, if it is enabled in Launcher or ROM, Zepp recommends not to do this!!!
From my memory, you got "Hard to Kill", "Die Hard" or "Bulletproof" depending on OOM and Minfree values you choose in the script....
Obviously, Bulletproof means Launcher will never be killed!!
But, the script expects that "lock home in memory" to be disabled, AFAIK.....if I am wrong, I apologise in advance!!!
BTW, if your not on ICS, can I recommend that old favorite Launcher Pro.....it may lack support from the Dev, but it runs silky smooth on GB and is lightweight with many options!!!
Sent either from my Sammy GT-i8150 or my Momo11 Bird Tablet!!
irishpancake said:
Ehhh??
Lock home in memory is not in V6....actually, if it is enabled in Launcher or ROM, Zepp recommends not to do this!!!
From my memory, you got "Hard to Kill", "Die Hard" or "Bulletproof" depending on OOM and Minfree values you choose in the script....
Obviously, Bulletproof means Launcher will never be killed!!
But, the script expects that "lock home in memory" to be disabled, AFAIK.....if I am wrong, I apologise in advance!!!
BTW, if your not on ICS, can I recommend that old favorite Launcher Pro.....it may lack support from the Dev, but it runs silky smooth on GB and is lightweight with many options!!!
Sent either from my Sammy GT-i8150 or my Momo11 Bird Tablet!!
Click to expand...
Click to collapse
Yes, Zepp advise not to enable the option IF you don't know what it is used for
Yes, If the launcher or ROM supports "Keep home in memory", do this instead of using supercharger script, I forgot to write this, thanks Irish for adding that part
Sent from my Modded Stock DXLA2 (Didn't have the mood to update)
reidzeibel said:
Yes, Zepp advise not to enable the option IF you don't know what it is used for
Yes, If the launcher or ROM supports "Keep home in memory", do this instead of using supercharger script, I forgot to write this, thanks Irish for adding that part
Sent from my Modded Stock DXLA2 (Didn't have the mood to update)
Click to expand...
Click to collapse
Well, I don't know friend.....
every tutorial I have seen or read including Zepp on the V6 Thread, says you should disable this setting if you have it, as it interferes with how V6 manages memory.....
and if you leave it enabled, it may cause lag on your device, the advice is to disable it, and Compcache [zRam]....If you don't have the option, it don't matter, so it's mainly aimed at CM7/9 ROMs.......
to achieve same result, V6 uses the Bullet Proof Launcher, but I think Zepp now advises to use the HTK option, as BPL breaks some other stuff in ICS.....
just to emphasise, it is important to read the outputs given in the script......
Zepp can be a hard taskmaster if you ask something covered there or in help files, etc.
Small example of his comments 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"
}
//EDIT2:
My original writing here was:
Forget the Supercharger. Instead take cear of the number of your apps and their intent-behavior.
Scripts like Supercharger are pure mess when targeting a solid daily driver system.
The number of people using this script is only high because there are a lot of folks with little knowledge about the underlying techniques.
Click to expand...
Click to collapse
These words might have been choosen to sharp for this given thread. See the further discussion for more details.
The essential core of my statement is to use the Supercharger with care, as you might run in more problems than before, if you do not know about your usage scenario and the side effects that come with every change in those parameters.
Tweaking settings like those of Supercharger is always a trade-off - but you can only adjust them if you know which flavor of system-behavior you prefer. Most users don't have a clue, so they have to believe magicians - Unlucky for them, because the provided magic potions are not more than nicely advertised placebo.
But at least, they got some great funky banners, so you can easily spread your unawareness in the whole xda forums via your signature through adding them.
// EDIT:
You can optimize memory management for either single task scenarios or multitasking scenarios. Logically, this is a classic trade-off.
To give an simplified example:
- Higher low-memory-killer-borders increase the chances of getting a smoother experience when running only one specific app most the time.
- On the other side, multitasking user experience will suffer, as activities get flushed out of memory earlier, when free memory decreases.
Other example: The VFS Cache Pressure parameter, which controls the weight between file system cache and application memory space.
- Lower values should give you better experience, wenn handling similar task scenarios most of the time, since their access patterns improve through caching
- On the other side, there is less memory space for applications, so this setup will give you slower task switching, as it is more likely now, that your desired new foreground application is not present in memory anymore.
XR-7 said:
Forget the Supercharger. Instead take cear of the number of your apps and their intent-behavior.
Scripts like Supercharger are pure mess when targeting a solid daily driver system.
The number of people using this script is only high because there are a lot of folks with little knowledge about the underlying techniques.
Tweaking settings like those of Supercharger is always a trade-off - but you can only adjust them if you know which flavor of system-behavior you prefer. Most users don't have a clue, so they have to believe magicians - Unlucky for them, because the provided magic potions are not more than nicely advertised placebo.
But at least, they got some great funky banners, so you can easily spread your unawareness in the whole xda forums via your signature through adding them.
// EDIT:
You can optimize memory management for either single task scenarios or multitasking scenarios. Logically, this is a classic trade-off.
To give an simplified example:
- Higher low-memory-killer-borders increase the chances of getting a smoother experience when running only one specific app most the time.
- On the other side, multitasking user experience will suffer, as activities get flushed out of memory earlier, when free memory decreases.
Other example: The VFS Cache Pressure parameter, which controls the weight between file system cache and application memory space.
- Lower values should give you better experience, wenn handling similar task scenarios most of the time, since their access patterns improve through caching
- On the other side, there is less memory space for applications, so this setup will give you slower task switching, as it is more likely now, that your desired new foreground application is not present in memory anymore.
Click to expand...
Click to collapse
Sounds like you've been reading my thread.
Thanks for confirming everything I've said LOL
Fact is, nobody can preach about android memory management and be right without confirming my findings.
So you're right.
And you confirm my findings.
Thanks and you're welcome.
PS. People know they hate launcher redraws and know they like it fixed.
But then again, you haven't read the thread or tried supercharger otherwise you'd know that it has different flavours for multitasking, aggressiveness and balanced.
And it's popular because it's for those that do know, and those that don't - not to mention that it works and does what it says.
If anybody thinks it's a placebo, it's in their head.
And you're wrong when you say "scripts like SuperCharger" because there is no such thing as a script like SuperCharger... silly.
edit: oh about VFS cache pressure, you can check that and all the other placebos in the Kick Ass Kernelizer script.
You fail to mention the importance of min_free_kbytes and dirty ratios and lease-break-time in your attempt to sound knowledgeable.
I guess you were too busy enjoying hearing yourself talk.
Man...
I woz goin to write that....but you just did it for me....
from the horses mouth, so to say!!!
Thanx....
hope you didn't mind the pic.....captures the essence of Zepp
EDIT....of course in XR's OP the EDIT bit was missing, so of course be had a quick look at the V6 thread....went Ohh Ohhhh!!!!
Code:
Edit:
I withdraw offending remarks about XR.....
as I have no knowledge as to his level of knowledge....
and in all humility I know phuck all myself....
OK??
Peace
Sent either from my Sammy GT-i8150 or my Momo11 Bird Tablet!!
irishpancake said:
Duplicate post!!! Sorry
Sent either from my Sammy GT-i8150 or my Momo11 Bird Tablet!!
Click to expand...
Click to collapse
irishpancake said:
Man...
EDIT....of course in XR's OP the EDIT bit was missing, so of course be had a quick look at the V6 thread....went Ohh Ohhhh!!!!
Click to expand...
Click to collapse
Sounds logic. I see that a am completely wrong at the V6-thread, so i go back, place a big EDIT-Label under my text, and add more text, so that every one can cen see it? Not.
Seriously, the examples i gave are there to line up the claim i did in the first part: V6 SuperCharger is no the glory fire-and-forget solution, most of those performance-increases come with some kind of accordant disadvantage. This should be mentioned.
irishpancake said:
Man...
but he is so "knowledgeable" or some kinda know-it-all know-nuttin
Click to expand...
Click to collapse
For some kind of stuff, one does not need >500 posts, but a solid technical comprehension, common sense and some research on the web.
---------- Post added at 03:47 PM ---------- Previous post was at 03:36 PM ----------
@zeppelinrox
What i wanted to express is: Those settings are trade-offs concerning the user experience. This stands in contrast to your explanations, which claim to bring both speed and multitasking to every phone. Forcing the home launcher to stay in memory is a good idea, but it was a one-liner until ICS came, so this can't be the reason for running hundreds LOCs at system startup.
The majority of users has a bunch of other problems, with their device configuration messed up, too much resource-intensive apps installed or a bad-performing ROM installed at some time.
And then there comes this shiny tool, it sounds like the good old american way of life (and is named like it): giving resources here, spending some more memory here - there's no limit, it makes your device blazing fast, it gives you all the things you dreamed of, on your old sluggish device.
Naturally, thats not the case: Yes, there might be useful scenarios, as it allows switching beetween LMK-profiles etc. But lets be honest: Normal users have no clue what they are doing there, playing around and getting more problems than before.
Actually, i like your idea of making those parameters accessible with more ease. As a advanced user, you can archive performance gains, because you know what to set for your specific usage scenario.
Its simply not the fire-and-forget-speedup for android, but people tend to believe this.
// Update:
I added a more diplomatic statement to my original post. Although my technical base argumenttion is the same as before, i guess its good for the discussion if there are less misleading emitotional expressions.
Just read post 3 in my thread.
It was never a one-liner. (well bulletproof launcher used to be at first)
Lock Home in Memory was a one-liner and it wasn't good enough.
All 3 launcher strengths are stronger than "lock home in memory" and there are 3 strengths precisely because there are trade offs...
Reading the script output would explain it anyway but suffice to say, you have said nothing that contradicts anything that I've said.
And very few users have problems with it and has a very good reputation.
Otherwise, this wouldn't happen:
http://goo.gl/qM6yR+
http://goo.gl/1JPl8+
Of course, that is only counting clicks on the goo.gl links... not all clicks.
But you get the idea: the sky's the limit.
And yep... it's like getting a brand new phone.
I've listened to you talk in circles so here's some advice: know what you're talking about before talking about it.
XR-7 said:
Sounds logic. I see that a am completely wrong at the V6-thread, so i go back, place a big EDIT-Label under my text, and add more text, so that every one can cen see it? Not.
Seriously, the examples i gave are there to line up the claim i did in the first part: V6 SuperCharger is no the glory fire-and-forget solution, most of those performance-increases come with some kind of accordant disadvantage. This should be mentioned.
For some kind of stuff, one does not need >500 posts, but a solid technical comprehension, common sense and some research on the web.
---------- Post added at 03:47 PM ---------- Previous post was at 03:36 PM ----------
@zeppelinrox
What i wanted to express is: Those settings are trade-offs concerning the user experience. This stands in contrast to your explanations, which claim to bring both speed and multitasking to every phone. Forcing the home launcher to stay in memory is a good idea, but it was a one-liner until ICS came, so this can't be the reason for running hundreds LOCs at system startup.
The majority of users has a bunch of other problems, with their device configuration messed up, too much resource-intensive apps installed or a bad-performing ROM installed at some time.
And then there comes this shiny tool, it sounds like the good old american way of life (and is named like it): giving resources here, spending some more memory here - there's no limit, it makes your device blazing fast, it gives you all the things you dreamed of, on your old sluggish device.
Naturally, thats not the case: Yes, there might be useful scenarios, as it allows switching beetween LMK-profiles etc. But lets be honest: Normal users have no clue what they are doing there, playing around and getting more problems than before.
Actually, i like your idea of making those parameters accessible with more ease. As a advanced user, you can archive performance gains, because you know what to set for your specific usage scenario.
Its simply not the fire-and-forget-speedup for android, but people tend to believe this.
// Update:
I added a more diplomatic statement to my original post. Although my technical base argumenttion is the same as before, i guess its good for the discussion if there are less misleading emitotional expressions.
Click to expand...
Click to collapse
OK man XR......I have removed my offensive comment about you, mainly becoz I don't know you and have no basis for the comment I made, and also becoz I think I cannot stand over it, so accept my apology please....
its not my usual form at all!!
You can check my posts!!
But, you were being provocative IMHO, and that is usually a good basis for discussion
OK!!
Sent either from my Sammy GT-i8150 or my Momo11 Bird Tablet!!
irishpancake said:
I have removed my offensive comment about you, mainly becoz I don't know you and have no basis for the comment I made, and also becoz I think I cannot stand over it, so accept my apology please....
its not my usual form at all!!
Click to expand...
Click to collapse
That's okay. As i mentioned above, i had also choosen sharp words, guess there might have been some more suitable writing style.
Nevertheless, i also guess that both sides - positive and negative - of the supercharger script should be discussed, as it is definitely note the magic silver bullet as it is sometimes perceived.
zeppelinrox said:
But you get the idea: the sky's the limit.
And yep... it's like getting a brand new phone.
Click to expand...
Click to collapse
Yes, it's remarkable. Not only one's device becomes at least a Galaxy Nexus, but it also increases display size, brigths up your teeth and pleasures your girlfriend.
You should get this for your girlfriend: https://play.google.com/store/apps/...GwsMSwxLDEsImF0dGljbGFiLkRyb2lkVmlicmF0b3IiXQ..
But if her device is SuperCharged, you're out of a job but mostly because you bore everybody to death.
i try v6 for a day, at night i realized that sms that i send in a day just keeping sending without being sent, i've tried to unsupercharged and reboot phone, but sms still sending, until i restore system to earlier setting than restart the phone, and check for the messages are sent
what is wrong with it?
what version of v6 that support stock rom?
is v6 increase free ram or is it does anything else? because i see no different on free ram that showed in ram booster
one more thing, when i run the script, i see text "it will not run on this rom, but you still can cook bla bla bla" is it normal?
Sent from my GT-I8150 using xda app-developers app
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.
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.
Its almost been a week since Android Pie was released for H930...
I have been using it since release... I have observed that RAM Management on this firmware is very bad...Like... Almost impossible....Unable to listen to music and scroll though my mailbox too....
Is anyone else facing this issue..or only specific set of people like me
Although Ram management is also poor in Pixel phones... but..Its not this bad...
Hope anyone finds a solution ?
Some workarounds:
For Non Rooted Users:
thefpspower said:
I found a REALLY WEIRD and really SIMPLE solution for this ACCIDENTALLY.
So just like you guys, I had this issue with ram management, asked around on reddit and stuff, really weird because even when there is enough ram is just doesn't let apps in the background, even lost calls because of it apparently.
Solution: Make a backup using LG Bridge
It sounds weird, but it worked for me. Somehow, after I made a backup with LG Bridge, all my app permissions got reset, so FluidNG for example stopped working out of nowhere and I had to reboot the phone.
After rebooting I gave the apps I wanted the permissions they needed and SOMEHOW that fixed the issue, I can open more than 7 apps in the background with no issue.
Don't ask me how the hell this works, but it did so I'm sharing it here to see if it works for you too. I didn't need to reset the phone at all.
Click to expand...
Click to collapse
For Rooted Users:
tech_infinity said:
If you guys are rooted then set zram to around 900 and swapiness to 60. All will be good.
Click to expand...
Click to collapse
PS: This will result in faster battery drain.
[email protected] said:
Its almost been a week since Android Pie was released for H930...
I have been using it since release... I have observed that RAM Management on this firmware is very bad...Like... Almost impossible....Unable to listen to music and scroll though my mailbox too....
Is anyone else facing this issue..or only specific set of people like me
Although Ram management is also poor in Pixel phones... but..Its not this bad...
Hope anyone finds a solution ?
Click to expand...
Click to collapse
I do not know what this could be caused by. My phone also uses a lot of RAM since the pie update. But: In doing so it is absolutely smooth and very conservative with the battery. I do not experience lags or bad performance.
I came from LiquidRemix and flashed the KDZ. Set up the phone. Then formated it again and flashed the TWRP zip and started over once more because I messed around with deleting system apps too much in the first try.
Koersten said:
I do not know what this could be caused by. My phone also uses a lot of RAM since the pie update. But: In doing so it is absolutely smooth and very conservative with the battery. I do not experience lags or bad performance.
I came from LiquidRemix and flashed the KDZ. Set up the phone. Then formated it again and flashed the TWRP zip and started over once more because I messed around with deleting system apps too much in the first try.
Click to expand...
Click to collapse
Performance and Battery is fine for mee too... But when it comes to multi-tasking.... Its almost impossible....
Home launcher gets killed in the background when I open Camera app?
Hm. Ok strange. This works for me. I can open a dozen apps in parallel and switch between them without problems. But I am not a ultra heavy multitasker either
I am facing the same issue currently and it drives me crazy. If I just listen to music on Spotify and browse through my mails, Spotify gets killed. This is a total joke IMHO I will try a factory reset now to see if that helps.
H930 is my model btw.
If it doesn't get better, I will have to go back to a custom ROM I guess.
Yeah bro ram management is very poor. I only get 700mb free ram.
BlueFlame4 said:
I am facing the same issue currently and it drives me crazy. If I just listen to music on Spotify and browse through my mails, Spotify gets killed. This is a total joke IMHO I will try a factory reset now to see if that helps.
H930 is my model btw.
If it doesn't get better, I will have to go back to a custom ROM I guess.
Click to expand...
Click to collapse
Literally Same problem here.... And I tried factory reset too...it didn't help...
Poor optimization by LG..
Yep same here. Spootify is killied in the background and switching between cards in samsung or chrome browser causes cards reloading.
trouble. said:
Yeah bro ram management is very poor. I only get 700mb free ram.
Click to expand...
Click to collapse
For the record, free RAM is not an indicator of poor management. Modern operating systems like Android use up as much RAM as reasonably possible, as the OS will run faster that way.
I'm not saying that Pie is better/worse... just saying that free RAM is not a good metric. My Oreo phone is running fine with 771 MB free right now... again, this is normal.
schwinn8 said:
For the record, free RAM is not an indicator of poor management. Modern operating systems like Android use up as much RAM as reasonably possible, as the OS will run faster that way.
I'm not saying that Pie is better/worse... just saying that free RAM is not a good metric. My Oreo phone is running fine with 771 MB free right now... again, this is normal.
Click to expand...
Click to collapse
You are right, but...
On my 3GB RAM Quark unless I had 1GB free RAM, the phone would lag severely and stop responding well. I could "clear all" Recents to get 1GB RAM back, and it would spring to life.
On both V30 and V30+, on rooted stock Oreo firmware, I consistently have 600MB - 1GB free and have no lags.
However, if it got down to 200MB, would it start acting wonky like the Quark?
Enough people are complaining about it, I'm starting to get concerned. This isn't buggy beta tests any more. Hopefully they'll fix it before they roll out the North American variants.
But see next post. Maybe not RAM, but kernel governor or something?
trouble. said:
Yeah bro ram management is very poor. I only get 700mb free ram.
Click to expand...
Click to collapse
I have less than that 700MB free RAM right now on rooted stock Oreo and have no problems. I have 549MB free and my phone is not lagging at all.
So, it's not RAM, maybe it's something else with Pie. Maybe the kernel governor?
ChazzMatt said:
I have less than that right now on rooted stock Oreo and have no problems. I have 549MB free and my phone is not lagging at all.
So, it's not RAM, maybe it's something else with Pie. Maybe the kernel governor?
Click to expand...
Click to collapse
That's what I was thinking, that the governor or kernel might even be an issue. First step, can people seeing the problem tell us what governor is activated? Most kernel tools will tell you what you have turned on. CPU-Z tells me that I'm running Interactive... and kernel version is "4.4.78-perf+". Again, this may not be enough info to work from, but it would be a start for looking at least.
Maybe spending some time with our kernel devs would help explain, too, as they'd probably have a better idea of what to look for.
In my case it was extremely bad when I updated using OTA, Messenger would literally get killed while I was typing a message. Performing a fresh install helped to some extent and the phone is usable and running otherwise pretty smoothly now, but still kills background apps much quicker than on Oreo. (edit) just tested, taking a picture in the stock camera app closes the app launcher (Nova).
H930, Interactive, 4.4.153-perf+
ChazzMatt said:
Enough people are complaining about it, I'm starting to get concerned. This isn't buggy beta tests any more. Hopefully they'll fix it before they roll out the North American variants.
Click to expand...
Click to collapse
I could have sworn I read an XDA article that Pie had RAM management issues.
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
I could have sworn I read an XDA article that Pie had RAM management issues.
Click to expand...
Click to collapse
Maybe it does. But it's just the RAM available people are complaining about on Pie is the same RAM or more than we have on Oreo...
And I have no lags on US998 Oreo with less than 600MB RAM. So, wondering if it's CPU Governor or something.
tepalas said:
In my case it was extremely bad when I updated using OTA, Messenger would literally get killed while I was typing a message. Performing a fresh install helped to some extent and the phone is usable and running otherwise pretty smoothly now, but still kills background apps much quicker than on Oreo. (edit) just tested, taking a picture in the stock camera app closes the app launcher (Nova).
H930, Interactive, 4.4.153-perf+
Click to expand...
Click to collapse
I also wonder if the update process is not done well. In other words, I might suggest trying a factory reset and starting from scratch again? I know updating across a large OS change can often cause problems... I've seen this happen on other devices...
schwinn8 said:
I also wonder if the update process is not done well. In other words, I might suggest trying a factory reset and starting from scratch again? I know updating across a large OS change can often cause problems... I've seen this happen on other devices...
Click to expand...
Click to collapse
I tried installing the ROM from scratch with "Refurbish" option on LGUP and did not restore any backup. Same thing. I think LG just rushed this update too fast.
Oreo keeps all the apps I mostly use, about 10-15 of them, in RAM indefinitely. Pie just can't keep anything running in th background.
I check governor and its interactive, I think its the same i oreo?
{
"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"
}
Dizzyrul3z said:
I check governor and its interactive, I think its the same i oreo?
Click to expand...
Click to collapse
Yep...Same as oreo..
btw...I have tried all the governor... all same... in terms of RAM Management... nothing improves
[/COLOR]
[email protected] said:
Yep...Same as oreo..
btw...I have tried all the governor... all same... in terms of RAM Management... nothing improves
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-...k-pie-t3954653
Flash this pie kernel and see if things become better