Related
Those of you running auto killer in your roms, did you use the aggressive settings or custom?
I'm just curious to see if anyone increased the auto kill.
I use either the aggressive or custom depending on the Rom honestly. DC ROMS= Aggressive. FRESH ROMS= strict. and all others = custom
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
I have the damagecontrol rom and I dont know if it came with auto killer or what...I restored my titanium backup and all i know is i dont have it now...is there an apk floating around for it?
Try the market
I thought it was a custom xda application. I didn't see it in
the market.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
I've been using Aggressive on Fresh 2.0d and it's been running great.
I tried Moderate for a while at first, but Homerun Battle 3D wouldn't even startup consistently. Once I changed it to Aggressive it has been working great.
Another quick note. I know Autokiller is supposed to reapply the settings on boot, but I'm not sure mine is. I haven't rebooted for a day or so, but the last couple times I rebooted I couldn't get Homerun Battle to run. Then I went into Autokiller and applied Aggressive again and it would start. Anybody else having similar experiences?
I used either the aggressive or strick on Fresh 2.0d. So far everything is running the smooth and fast. This the way HTC hero should have come out of the box.
What does each preset do? Is this for speed or battery life or both?
flammenwurfer said:
I've been using Aggressive on Fresh 2.0d and it's been running great.
I tried Moderate for a while at first, but Homerun Battle 3D wouldn't even startup consistently. Once I changed it to Aggressive it has been working great.
Another quick note. I know Autokiller is supposed to reapply the settings on boot, but I'm not sure mine is. I haven't rebooted for a day or so, but the last couple times I rebooted I couldn't get Homerun Battle to run. Then I went into Autokiller and applied Aggressive again and it would start. Anybody else having similar experiences?
Click to expand...
Click to collapse
Damn. I wish Homerun Battle 3D would run great for me. Problem is I get crummy service at work and with it going in and out of 1x and EVDO, causes the game to lag.
I have noticed sometimes on first opening HRB, it force closes but it always opens the second time.
james33440 said:
Those of you running auto killer in your roms, did you use the aggressive settings or custom?
I'm just curious to see if anyone increased the auto kill.
Click to expand...
Click to collapse
i'm running aosp 1.6 from gbhil and i used custom autokiller settings.
the way i see it they made these phones with all this ram may as well use it, what good is it to have all this free ram?
1536,3072,4096 (all default) then hidden app is 7680. content provider is 8960 and empty app is 10240. i normally run around 40-45 free ram thats about where i like it. the phone still runs fine all the way down to 20mb free but any less than that it starts going downhill.
so, im MB my settings are 30 then 35 then 40. runs great!
yeah, I get some lag now and then if I don't have great service. Playing offline seems to work fine though. I think it's just the online play that it effects. A co-worker has a Droid and his lags when playing online as well if he's in a spot without good service.
flammenwurfer said:
yeah, I get some lag now and then if I don't have great service. Playing offline seems to work fine though. I think it's just the online play that it effects. A co-worker has a Droid and his lags when playing online as well if he's in a spot without good service.
Click to expand...
Click to collapse
Well, mine actually lags on offline play too. As long as the phone isnt switching back and forth, it runs smooth.
How can you remove this autokiller crap, I have tried freshkitchen, uninstaller, and from settings-applications menu, all to no avail
vedwed said:
How can you remove this autokiller crap, I have tried freshkitchen, uninstaller, and from settings-applications menu, all to no avail
Click to expand...
Click to collapse
Using command prompt (adb)
adb shell
# rm Autokiller.apk
troyboytn said:
Using command prompt (adb)
adb shell
# rm Autokiller.apk
Click to expand...
Click to collapse
Ohh thanks much appreciated.
I did not try that way, I figured if it couldn't be done in freshkitchen then it was just built into the rom. Thanks much again
Just stop using task killers entirely. This isn't Windows Mobile guys. You're getting all OCD in here about the placebo effect.
Sawawa said:
Just stop using task killers entirely. This isn't Windows Mobile guys. You're getting all OCD in here about the placebo effect.
Click to expand...
Click to collapse
Autokiller does have a built in task killer but its real use is to tweak memory settings at boot and then shuts itself down (so Android can take care of the rest). So, in reality it is not really a task killer per say.
Fair enough, but it's still entirely pointless. I trust the device manufacturer and Android far more than I ever would the random numbers that I might otherwise delude myself into believing were somehow better.
Just let Android do its thing all of the time. It doesn't need any additional help (particularly with the process management in 2.1). Stop including this garbage in ROMs.
Sawawa said:
Fair enough, but it's still entirely pointless. I trust the device manufacturer and Android far more than I ever would the random numbers that I might otherwise delude myself into believing were somehow better.
Just let Android do its thing all of the time. It doesn't need any additional help (particularly with the process management in 2.1). Stop including this garbage in ROMs.
Click to expand...
Click to collapse
It actually very useful for making roms run smoother. By default the memory numbers are very low, which lets a TON of apps run at the same time. The higher the memory numbers the more it ends apps that you werent even using. It gives what you are currently running or recently ran more priority. Even if you dont use AutoKiller, which is just an app to adjust the memory setting, every rom comes with an edited memory setting other then htc's default. Its most commonly known as gumbo's memory settings.
Also in AutoKiller you can adjust the settings to default, or just really low like htc would have them set.
Its really not a bad thing to include in roms because most people want there rom to be smooth and as close to lag free as they can get. AutoKiller helps achieve that by ending stuff you dont currently have up making the phone run faster. Thats if you have a decently set setting. I run mine on optimum, and it doenst close unnecessary things like if im on the web it stays running.
I can understand an app like Task Killer which just terminates the apps. AutoKiller is just setting the memory setting of your phone, which end apps the same way as if the phone were running normally. Just if the numbers are higher the more apps it will end quicker freeing up more space.
Also you really trust htc and sprint?? haha good luck with that
Jus10o said:
It actually very useful for making roms run smoother. By default the memory numbers are very low, which lets a TON of apps run at the same time. The higher the memory numbers the more it ends apps that you werent even using. It gives what you are currently running or recently ran more priority. Even if you dont use AutoKiller, which is just an app to adjust the memory setting, every rom comes with an edited memory setting other then htc's default. Its most commonly known as gumbo's memory settings.
Also in AutoKiller you can adjust the settings to default, or just really low like htc would have them set.
Its really not a bad thing to include in roms because most people want there rom to be smooth and as close to lag free as they can get. AutoKiller helps achieve that by ending stuff you dont currently have up making the phone run faster. Thats if you have a decently set setting. I run mine on optimum, and it doenst close unnecessary things like if im on the web it stays running.
I can understand an app like Task Killer which just terminates the apps. AutoKiller is just setting the memory setting of your phone, which end apps the same way as if the phone were running normally. Just if the numbers are higher the more apps it will end quicker freeing up more space.
Also you really trust htc and sprint?? haha good luck with that
Click to expand...
Click to collapse
Either way it should be a choice made by the USER not someone who decides what I need or do not need on my phone. What I choose to have running or not running, there is no need for this garbage for the average joe who just wants something that does not look and feel like Sprint garbage. If its such a great and useful thing put it on the market and let users have a choice.
Hi all,
I've had this phone for a few days now and love it. However I find I have very little RAM available.
I have on average around 30-40mb of ram available and the phone sometimes slows down quite a bit. I've ad a look at the running apps and the main culprit was SPB Shell launcher which was using around 50mb. I have since stopped using this but I am still only getting around 40-50mb remaining (with timescape disabled) and again a sluggish phone at times.
How is everyone else's?
I am thinking of doing a factory reset and start afresh to see what app may be causing the problem.
Any other suggestions or is this normal with this phone?
Thanks for your replies.
I have the same. I thought it was down to having over a thousand contacts all duplicated in exchange and google.
I have 130m of internal space available. Is there any way of re assigning it as you can in windows mobile?
Sent from my LT15i using XDA App
My Average Free ram @150 MB
135 - 140ΜΒ here.
Have been checking with Advanced Task Killer (ofcourse NOT automatically set to kill everything, but fully manually every now and then), and noticed that there were times when the phone just left plenty of unnecessary apps wondering around in the background. Apps that are not the "always-on" by android system. So I kill EVERYTHING else except from:
1) Clock
2) TrackID
3) LiveWare
4) Media Sharing
5) Maps
6) Hanashi (WTF is that?!? it ALWAYS comes back by system.)
7) Setup wizard
(What remains always active by system also depends on the widgets you have, e.g. I have TrackID widget, you might not have it, so you wont need it.)
and have even noticed better battery performance...
EG, during nightime, I left the phone untouched (not used ATK), and when I woke up, I had a 12-13% battery drop, while the other day, after a fresh cleaning before sleeping, got around 4-5% drop. Both times with same conditions...
I have about 140 free and nerver under 100
Sent from my LT15i using Tapatalk
What to you recommend to stop the unused processes from re starting again?
Sent from my LT15i using XDA App
Try Advanced Task Killer
Yeah I have about 150mb free.
And can I say coming from the x10, this phone is rediculously smooth. I love it!
Can we expect more free RAM once it's rooted/a custom fw is available?
This obsession about RAM needs to stop!!!!! 2.3 manages memory very well and you shouldn't be having any issues with the phone, unless you start messing with it (task killing the wrong things for example).. My phone is running really smoothly.
im_iceman said:
This obsession about RAM needs to stop!!!!! 2.3 manages memory very well and you shouldn't be having any issues with the phone, unless you start messing with it (task killing the wrong things for example).. My phone is running really smoothly.
Click to expand...
Click to collapse
The reason I asked is that my phone does not run smoothly at times but very laggy and some items (contacts, emails etc) can take an age to load (well not an age but seconds but it feels like an age )
I was just wondering if this was the norm or not.
im_iceman said:
This obsession about RAM needs to stop!!!!! 2.3 manages memory very well and you shouldn't be having any issues with the phone, unless you start messing with it (task killing the wrong things for example).. My phone is running really smoothly.
Click to expand...
Click to collapse
Yeap, 2.3 handles RAM almos perfectly. EG, if you open as many apps as you want and just leave them in the background, when you try to launch a HUGE game (eg Asphalt 6), the system will free as much RAM as required for the game to run smoothly.
BUT, I have noticed that some apps are left idle without me usng them (and without being system triggered apps, which when closed, are not resprang), and are not automatically closed by system. I tested leaving overnight the phone without killing anything after a days usage (with more than 15 apps in the background), and while being at 15% when left at night (around 01:00 am), it was off in the morning (7:30 am).
Then I did a fresh reset to the device, noticed what apps are automatically opened by system, and protected them (unchecked them) from Advanced Task Killer (which was set to manual), so that it will not shut them down when I click the "kill all" button. Next night, I killed all non-system apps (that do not restart if you do no action), and left the phone overnight again to see if there is any difference. Battery dropped around 5%.
I did this twice under same conditions (same time gap, BT open etc.), and results were almost the same +/- 2%.
So IMHO, if you use a task killer app wisely, you could manage to get better battery performance when the phone is idle, but you will NOT get better performance (smoother UI etc.)
Again, all these IMHO.
@dragunov - completely agree with everything you're saying.. it's the difference between knowing what you're doing and blindly killing tasks because someone said it helps!!!
for the OP - would suggest figuring out what it is you've got running that's causing the lag cos it's not the phone hardware/ OS that's at fault - This is the only drawback of Android vs iPhone -the QA of the apps on the market doesn't pick up this sort of problem.
im_iceman said:
for the OP - would suggest figuring out what it is you've got running that's causing the lag cos it's not the phone hardware/ OS that's at fault - This is the only drawback of Android vs iPhone -the QA of the apps on the market doesn't pick up this sort of problem.
Click to expand...
Click to collapse
Thanks, thats what I intend to do. A factory reset and the re-install gradually my apps to see which ones are the problems.
When I first got the phone I loaded it up with apps so it will now be difficult to retrace so a fresh start is what I will do.
A quick update. I have done a factory reset and although the phone is smoother I still only have 40-50mb free (only app I installed was swype).
Can I just ask what free ram other users have?
Thanks
Right now.. 60Mb.
I had about 150 out of the box while taskkiller always said about 5 apps running background (not installed by me).
Now yesterday my arc froze while browsing the web and rebootet itself (screen was scary, single pixles loosing light while some were still on till everything was off).
Now that was the only time the arc did that and afterwards task killer now (after killing apps) only shows 2 or 3 apps running background and up to 195MB free RAM which is cool but scary at the same time ...
Still can recieve phone calls though and everything works ... well Im happy for more RAM
Oh yeah, got swype on my whitelist.
Honestly I don't understand the need for more ram?
having 60mb is similar to having 200mb, it's all about applications reserving their spots, once they needed they'll kick in, otherwise they stay idle ( talking about system apps and well developed applications )
even if you have 60mb you still can run games that require 100mb... smoothly
the lag some face is due to background application using the processor
I usese autokiller memory optimizer. See unlike the other appear that kill everything, autokiller mo just optimizes the Android system so you wont have to go hunting for those apps.
Sent from my CM 7 Monster Evol.
MJ_QaT said:
Honestly I don't understand the need for more ram?
having 60mb is similar to having 200mb, it's all about applications reserving their spots, once they needed they'll kick in, otherwise they stay idle ( talking about system apps and well developed applications )
even if you have 60mb you still can run games that require 100mb... smoothly
the lag some face is due to background application using the processor
Click to expand...
Click to collapse
Doesn't matter how many times we say it people just won't get it!!..
Spare memory is WASTED memory.. this is ANDROID/ Linux.. this is NOT MS Windows... it's DIFFERENT!!
Greetings! I've read all about not using task killers and refrained myself from using one. But now i'm a bit confused with the efficiency of android RAM management. I simply can't use my Nexus S smoothly beyond 100 hrs of uptime. after which the 'running' tab usually shows >200mb ram used with roughly 50mb of free.
I understand the used RAM was supposed to keep the previously opened apps in cache for faster subsequent execution time. But thats not what going on under the hood, i suppose, after 3/4 days of uptime. When i view 'show cached process' from the 'running' tab, it barely lists the default launcher and 1/2 other apps whereas this menu usually shows more that 10 apps being cached after a fresh boot.
The horrible thing that starts to happen then, most of the apps start exiting as soon as i touch the back button. Nothing except the foreground app stays in the RAM and everything else get dumped out of it and reloads at next launch.
Whats keeping the RAM then, if there's no space for app caching after merely 100hrs of uptime?
I'm not sure but the whole thing has led me believe my system has a major memory leak somewhere. Or, as i've read that the Nexus S actually have quite a bit lees than stated 512mb ram available for user apps… but should i expect this to be normal behaviour? Then why google released this model with inadequate amount of ram in the first place? I'm rebooting my phone every other night to keep it smooth!
Please shed some light, feeling totally lost. I'm moderately heavy user and come from symbian background.
PS: my phone is factory installed stock 2.3.4 with default launcher and widgets since i purchased if 2 mnths ago. no root done yet.
The cached app list in normal Android settings is inaccurate. Try apps like SystemPanel Lite.
Android does take care of RAM usage perfectly usually. Are you saying that your phone gets slower over time? That is quiet impossible unless you got a faulty installation of Android.
Also the "back" button does mean "exit and don't cache" for some/many apps.
Actually I agree my phone gets slow after time. I have to reset then after that it flys aagain
Sent from my Nexus S using XDA App
I noticed this problem as well, and i had read about it before, there are more people noticing it.
Maybe it happens only when you have too much stuff installed and running, if you are not a power user you might not notice it.
I think the android memory management is lacking here and the launcher app should be more robust, but the issue could also be solved if we had more memory.
I have 200+ apps installed in my nexus, some of them have services that run in the background automatically (and some of them didn't even have to, like some games and apps) and this uses memory.
I have around 15 or 20 apps always running as services, this uses 150mb+ memory. If i close any of these they will just start again in a few seconds automatically. The only way to stop this (my ns is not rooted) is if i uninstall them.
So, after a while, the most noticeable effect is that the launcher gets more sluggish and lagging. if i force close all apps it's smooth again, but only for a while. Also after i run a heavier app (like a game) and close it the launcher will restart/reload.
The workaround i found is to uninstall some of the apps/games that run as services until things get smoother again, but i don't want to give up most of them so i have to put up with a bit of sluggishness.
rentaric said:
The cached app list in normal Android settings is inaccurate. Try apps like SystemPanel Lite.
Android does take care of RAM usage perfectly usually. Are you saying that your phone gets slower over time? That is quiet impossible unless you got a faulty installation of Android.
Also the "back" button does mean "exit and don't cache" for some/many apps.
Click to expand...
Click to collapse
Yeah.... my phone gets slow over time, kind of. Let me explain it...
after a fresh boot, i can browse, email, check facebook, make calls, send sms and then come back to browser to find my last loaded page still there. but after 2/3 days of up time, whenever i leave a foreground app and go somewhere else, it gets killed. the worst case i faced was, from the google search app, after inputting my query, it had to close itself before opening the browser to perform the search. it gets that bad.
during these times i usually face a slight delay and jittery animation while opening each app. and the cached processes usually shows only the launcher occupying ~30mb of space and 1 or 2 other very small apps. it appears, because of lack of RAM the system also stops caching the usual number of processes.
i've also thought that my installation could be faulty. i'm using it purely stock for the first few months to get the hang of the way android works. what bothers me, without even rooting it, how can can it get faulty. i even did a factory reset after taking it out of the box.
I'll monitor the situation with the SystemPanel Lite and report back. Thanks for the reply.
temp9300 said:
I noticed this problem as well, and i had read about it before, there are more people noticing it.
Maybe it happens only when you have too much stuff installed and running, if you are not a power user you might not notice it.
I think the android memory management is lacking here and the launcher app should be more robust, but the issue could also be solved if we had more memory.
I have 200+ apps installed in my nexus, some of them have services that run in the background automatically (and some of them didn't even have to, like some games and apps) and this uses memory.
I have around 15 or 20 apps always running as services, this uses 150mb+ memory. If i close any of these they will just start again in a few seconds automatically. The only way to stop this (my ns is not rooted) is if i uninstall them.
So, after a while, the most noticeable effect is that the launcher gets more sluggish and lagging. if i force close all apps it's smooth again, but only for a while. Also after i run a heavier app (like a game) and close it the launcher will restart/reload.
The workaround i found is to uninstall some of the apps/games that run as services until things get smoother again, but i don't want to give up most of them so i have to put up with a bit of sluggishness.
Click to expand...
Click to collapse
This sounds exactly like what i'm facing. thanks for the input. I've also lost my launcher once after exiting the browser with several tabs open.. had to click the home button and then launcher again to get icons back on it. This usually doesn't happen after first 10-15 hrs but after several days of uptime.
I respect the way android tries to manage RAM automatically even by re-spawning the apps if it thinks they needed to be kept cached even after a force close from default task manager. With this kind of supreme automatic power comes huge responsibility of managing it well. It should count for every bits of data (concurrent garbage collection system?). But somehow it appears the ram management system is failing to count some of it and letting parts of the RAM go un accounted for.
I have like 30 apps installed from market with roughly 5 of them having active background process running. And I believe and hope this shouldn't be enough to take the android RAM management system down only after a few days of uptime.
Thanks again for the reply.
I'm going to try "auto memory manager" i read about in other thread as a way of forcing a minimum amount of free ram a bit higher than standard Android does.
It's one more service using memory but if does what is supposed to, maybe at least the launcher will stay more responsive.
The mild setting is too close to default so i have created a custom that looks roughly between mild and agressive.
I'll report back later.
the phone gets horribly slow when the RAM drops to below 50 Mb free
in which point i always have to use task killer to kill them all, and it's fast again until it again reaches less than 50 Mb RAM
another thing i noticed is that with very heavy high quality pictures/icons loaded to customize the launcher it will slow down the performance
instead if the whole launcher theme is less than 2 Mb or less then the phone also works very fast.
AllGamer said:
the phone gets horribly slow when the RAM drops to below 50 Mb free
in which point i always have to use task killer to kill them all, and it's fast again until it again reaches less than 50 Mb RAM
another thing i noticed is that with very heavy high quality pictures/icons loaded to customize the launcher it will slow down the performance
instead if the whole launcher theme is less than 2 Mb or less then the phone also works very fast.
Click to expand...
Click to collapse
...and its unfortunate that i'm hitting the 50mb free RAM barrier with the stock launcher in only 3/4 days of uptime, regularly. why does the default app kill option let the memory go below 50mb then, if this can potentially hamper performance? and i'm not talking about any android phone here, but google's own Nexus flagship.
i remember reading a blog post by an android engineer explaining the merits of memory management by the OS and how task killers only worsen the situation. could they possibly optimize the OS ram management for light to moderate use and expected the heavy users to root and manage it on their own by tinkering the free mem settings? what else could explain the situation?
i wonder how things are with other skinned androids with similar hardware configuration if a Nexus is having tough time behaving well even with its trimmed software package. and i consider myself as only a moderately heavy user.
the memory cleanup isn't perfect in Android.
As much as everyone likes to say that Google tells you not to use task killers or any thing and that Android can take care of itself, every nice ROM out there plays with the minfree settings.
Fact is Android isn't perfect.
I know this from a 256MB device. We set it to it could boot with 30mb free. You could do maps and stuff, but a day later Maps would crash left and right because you ran out of memory. Even if it said 30mb free still in About phone.
The same with the Nexus S. Stock settings allow little free memory. I saw this in CM7. It gets slow after a day. A reboot fixes it all.
I suggest tweaking the minfree values or something so you can get decent performance. Fact is that performance will drop off a bit with up time, but at least if you tweak your minfree settings it should last a LONG time without needing to reboot.
this works great after patched my phone never gets slow
http://forum.xda-developers.com/showthread.php?t=1111145
just an FYI if you try it dont use the CWM version doesn't work on NS for some reason at least it didn't for me
just manually move with root-explorer and set perm to 777 and enjoy
edit
OP not rooted this requires root
dmo580 said:
the memory cleanup isn't perfect in Android.
As much as everyone likes to say that Google tells you not to use task killers or any thing and that Android can take care of itself, every nice ROM out there plays with the minfree settings.
Fact is Android isn't perfect.
I know this from a 256MB device. We set it to it could boot with 30mb free. You could do maps and stuff, but a day later Maps would crash left and right because you ran out of memory. Even if it said 30mb free still in About phone.
The same with the Nexus S. Stock settings allow little free memory. I saw this in CM7. It gets slow after a day. A reboot fixes it all.
I suggest tweaking the minfree values or something so you can get decent performance. Fact is that performance will drop off a bit with up time, but at least if you tweak your minfree settings it should last a LONG time without needing to reboot.
Click to expand...
Click to collapse
thanks for the informative reply. i've started to get the point about the situation. maybe a little more RAM would've delayed this kind of clogging but at its current state our little green robot simply isn't mature enough to carry the load we're putting on its shoulder. it that case i would accuse google of spreading the word that manual intervention isn't necessary. thats simply misleading. they way they've programmed the stock rom appears to be optimum for light use only.
anyway, i guess re-adjusting the minfree values require root, right? i should better start reading up on rooting then.
demo23019 said:
this works great after patched my phone never gets slow
http://forum.xda-developers.com/showthread.php?t=1111145
just an FYI if you try it dont use the CWM version doesn't work on NS for some reason at least it didn't for me
just manually move with root-explorer and set perm to 777 and enjoy
edit
OP not rooted this requires root
Click to expand...
Click to collapse
i'm thinking of learning about rooting now. i like android for everything else it does and this particular device got me hooked with its unusual and clean look, and i don't wanna give up on it easily. but i think i'll have to gather up a lot of knowledge from this forum pages before i can attempt something like you've described.
thanks a lot for the solution anyway. i'll try it as soon as i feel comfortable with my understanding of android internals.
its not really that complicated just a script file you put into /system/etc/init.d with Root Explorer and set full permissions with root explorer and reboot and it starts working and if you dont like or dont want to sue anymore you simply delete the file.
but yea get rooted definitely worth it and you will gain more knowledge
temp9300 said:
I'm going to try "auto memory manager" i read about in other thread as a way of forcing a minimum amount of free ram a bit higher than standard Android does.....
I'll report back later.
Click to expand...
Click to collapse
well, things didn't exactly as i had planned, the test with memory optimizer was going ok but i only did for a day.
After that, i managed to sell my Nexus and went for an SGS2!
So far no lag/sluggishness issues and i have installed most of what i had in the NexusS, this phone has 2 important advantages, it has double the ram (so it should take longer to fill) and also it's faster which might compensate.
demo23019 said:
this works great after patched my phone never gets slow
http://forum.xda-developers.com/showthread.php?t=1111145
Click to expand...
Click to collapse
Dun use the script if you're running netarxhy, mathkid95;16006240 or trinity kernel. It will just made you worst. Oh yea, and also dun use it on Brainmaster miui rom
Sent from my Google Nexus S using XDA Premium App
window7 said:
Dun use the script if you're running netarxhy, mathkid95;16006240 or trinity kernel. It will just made you worst. Oh yea, and also dun use it on Brainmaster miui rom
Sent from my Google Nexus S using XDA Premium App
Click to expand...
Click to collapse
really?? but simms22 use auto memory manager too.. so i think we can still use the script with trinity kernel
king23adrianc said:
really?? but simms22 use auto memory manager too.. so i think we can still use the script with trinity kernel
Click to expand...
Click to collapse
auto memory manager and the script are two different things. honestly, i havent tried the script because auto memory manager works for me. ive been setting it higher than the aggressive setting lately btw...
{
"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"
}
As a developer I've had to deal a lot with Android's memory management. Simply put, Google is correct in saying that Task Killers do more harm than good. Android is pretty smart about clearing memory.
However, a lot of apps and even some basic framework level calls cause memory leaks, which the garbage collector can't clean. So the only solution is a device reboot.
window7 said:
Dun use the script if you're running netarxhy, mathkid95;16006240 or trinity kernel. It will just made you worst. Oh yea, and also dun use it on Brainmaster miui rom
Sent from my Google Nexus S using XDA Premium App
Click to expand...
Click to collapse
I use matrix, and worked fine on netarchy when i was testing.
and Brainmaster MIUI ROM already has script so yea dont need with his ROM also he provides trinty kernels on his ROM page so if trinity had issues with ram script i dont think he would be providing download links to use with his ROM
My note's ram is always above 600 mb. ...pls help
Sent from my GT-N7000 using XDA App
I always use back button to close apps. Clicking home button will not close apps but minimized. More apps opened equal more RAM used.
Sent from my GT-N7000 using Tapatalk
Totally normal. Apps are loaded into RAM so when you want to open an app it loads faster. That's how Android works.
My advice is to not go on a killing spree and kill every app that's running. This will make your device slower and it'll use more battery since it has to use more power to load the apps again and again - and again.
If you want to free up some RAM you can do this:
- Switch launcher. TouchWiz is a resource hog, and you'll gain some RAM if you switch to another launcher like ADW, GO Launcher or LauncherPro
- Freeze/Delete system apps that you don't use/want. If you're not using SocialHub, Reader and Swipe, there's no reason having them. Freeze them and they won't use RAM.
- Flash a custom ROM. You can flash a custom ROM if you want. Your device will be faster and use less battery. Some ROMs has been stripped for "bloatware" like SocialHub etc. so they're fast "out of the box".
I'm currently running ROMOW ROM with ADW EX (and i've frozen a lot of system apps), and my Note is only using around 250MB on boot.
What's the problem with that? You have 800 MB for OS and applications, it's meant to be used. Applications loaded, compiled and the code is stored in RAM, the more RAM you have the more apps you can keep open. With less RAM (like my previous phone, Galaxy S, which had only 330 MB available), the apps have to be unloaded from RAM when you open a new one, so the CPU works more, loading apps again and again.
The RAM contains compiled apps and cached data, to make access faster and save battery, it's good that it's used. Android manages the RAM itself, if you launch an app that needs RAM, it will make room for it, discarding the least used pages. You don't need to take care of this yourself.
In the Samsung system administrator there's a button to clear RAM, press it and it will unload even the touchwiz interface, you'll end up with 400 MB used, but it will increase soon, as apps are opened.
The issue is that when you run a high resource game, have a few web pages open or use google earth then the device closes down touchwiz to free up memory so you may find your homescreen empty or on other occassions android closes the internet application if you switch to another program even briefly so multitasking is poor on the Note.
Its absolutely true,RAM management is implemented very badly on the GNote.Even my HD2 has much much better RAM management with its mere 480MB.
However since this is my first Android device I am not quite sure if this is a Samsung thing or an OS inconvenience.
On my HD2 I could keep multiple web pages open for latter offline reading when internet access is not available and it would keep it in memory even though many services would still be running.
Unfortunately its not the same with my Note,it just rushes to close apps on the first occasion.
Say what you may but being a long time PDA user I found that the old shot-in-the-head by its very same creator the Windows Mobile is the best multitusker I have ever used despite the fact that on those days the RAM was just minimal.
High RAM usage is due to the high number of pixels that need RAM & processing to drive them.
On my old stock rom (KKA) I had the same....usually over 600Mb used.
A few days ago I flashed the latest LA4 stock rom. And what a big improvement that was. Smoother, 2 days on a battery with moderate use. And about 420MB ram used on average. A very big improvement.
I think it would be better if we know which version you have.
So you could upgrade to a newer version or just flash a custom rom.
most of the customroms are better than the stockrom
airwater9 said:
High RAM usage is due to the high number of pixels that need RAM & processing to drive them.
Click to expand...
Click to collapse
Yup, that's also correct.
Hello everyone.
My issue is rather simple.
I used to have a Galaxy S3 that had a really poor multi-tasking experience with its very limited 1Gb of RAM.
So I bought the Note 3 that was bound to provide me with enough RAM for a better multitasking experience.
So far it was OK and way better than S3 capability but then KitKat came along and this is where my nightmare began.
Simply put, I cannot take benefit of the 3Gb of RAM I have on my device.
My Galaxy Note 3 is the international version bought in France with a Snapdragon S800 and 3Gb of RAM.
During my every day usage, I ofently switch between a certain sets of applications so to me, it is very important that these applications are not killed.
My original settings :
OOM is untouched, though I tried to set it to light with System Tuner but it did not help.
I have a few services that are launched when the device boot : Network Speed to measure bandwith in real time, OS Monitor to display CPU and RAM usage in real time as well and finally System Tuner.
Under develpoment options in the Settings, the limit of apps in background is set to standard (by default)
This is a sequence of test runs I made to show what is going on and why I deem my multitasking experience poor.
In the aim to offer accurate data, this is the list of apps I am using a lot :
app 1 = World War - a 2D non dynamic video game ;
app 2 = iMobster - same as above ;
app 3 = TweetCaster - a twitter client
app 4 = EvolveSMS - a SMS client. Can take a lot of RAM if many SMS are loaded (over thousands of SMS = 100Mb of RAM)
app 5 = Google Chrome - the web browser (not beta) with one tab loaded, two tabs saved but unloaded
Here we go.
Reboot phone -> 1.5Gb of free RAM (1.9Gb at the beginning then 1.5Gb in average after waiting for the aforementioned on-boot apps to be launched)
Launch app 1 -> 1.4Gb of free RAM
Launch app 2 -> 1.3Gb of free RAM
Launch app 3 -> 1.0Gb of free RAM
Launch app 4 -> 800Mb of free RAM
Launch app 5 -> 600Mb of free RAM
Upon each launch I waited for the app to be completely loaded (no splashscreen or loading screen). Then I check with both OS Monitor and System Tuner's widgets to check up the free RAM (sometimes their data differ, but not a lot ~100/200mb).
Repeating this particular sequence bears the same results : when launching app 5 (Google Chrome), app 1 and 3 are closed.
Some time only one of them. But most of the time two apps are closed.
Futhermore, I notice I can't not get less than 500Mb of free RAM. Unless I use Google Chrome to load heavy websites, there is no way than by launching more apps I will get under this limit.
Simply put, I cannot have more than 4 to 5 apps running in background.
I tried different ROMS :
- 2 based on Samsung KitKat ROMs : Jackyaway and S5 port V6. I have the same issue.
- CM 11. : too unstable at the time but perhaps better because the OS takes less RAM than Samsung.
So here I am.
When I was on Android 4.3, it was nice, Moving to 4.x is a disaster.
What can I do ? How is your experience ? How many apps do you manage to keep in the background ?
You are aware that the default setting for 'keep in background' equals 4?
Sent from my SM-N9005 using Tapatalk 2
ShadowLea said:
You are aware that the default setting for 'keep in background' equals 4?
Sent from my SM-N9005 using Tapatalk 2
Click to expand...
Click to collapse
Then how can I change it ???
This is really common and isn't an issue. Android will cache a lot of resources in RAM. When that RAM space is needed, the cache is freed. Do not worry.
Colton127 said:
This is really common and isn't an issue. Android will cache a lot of resources in RAM. When that RAM space is needed, the cache is freed. Do not worry.
Click to expand...
Click to collapse
Sorry but no.
How come ..
In Android 4.3 I had better multi-tasking experience (more apps in background) while having a smooth system ...
In Android 4.4,x I have an horrible multi-tasking experience (less apps in background).
I mean I have been doing more tests and it's driving me CRAZY ! After just rebooting my phone, I have about 1300Mb of FREE RAM and then after starting my 4 usual applications, it still have 1Gb of FREE RAM, why, please tell me why would Android feel the need to kill one of these apps after I launched a 5th one ?
This is getting ridiculous ! In what world could Android based on Linux kernel simply decide to kill my apps when it has 1Gb of FREE RAM !
When I was on 4.3 I could have ;
- my 2 2D video games
- my twitter client
- my SMS application
- chrome with 3 tabs opened
- play store opened,
- galerie displaying a picture
etc etc.. all stayed in background. They just got killed whenever I started a heavy application such as a 3D video game and in that case it's completely normal.
Heck I even recalled playing to Asphalt 7 then having a phone call while replying to an SMS (or checking my tweets) all at the same time.
Guess what I can do, now in KitKat ?
Oh god I hate my self for moving to kitkat. Makes me want to throw my phone away.
Search for zeppelinrox's V6 supercharger, I recall it has a feature to allow more apps to run in the background.
I am yet to do this myself, noticed the poor multitasking also.
Someguyfromhell said:
Search for zeppelinrox's V6 supercharger, I recall it has a feature to allow more apps to run in the background.
I am yet to do this myself, noticed the poor multitasking also.
Click to expand...
Click to collapse
That could be a solution. I used in on my Galaxy S3 but it did little help since the phone was lame at the beginning.
I never believed I would use it again on the phone I deemed good for multitasking.
But I am glad to hear that I am not the only one thinking the same thing.
I will try the fix and post here my findings. Should you try the same thing, do not hesitate to share your experience here.
Bump
Quite some time have passed since my last post here ... but my problem remains still.
I've juste moved to Cynogen Mode 11 as of last Snapshot (stable) version.
Overall, the system is stable. Much faster, way smoother. I won't miss TouchWiz I think.
RAM usage is lower : now on boot with the same services I like to have, it sill have over 1.6Gb of free RAM.
That's quite a lote I would like to use, but still can't.
But I must be fair, my multitasking experience is slightly better. First because I can finally have other options to switch between apps other than by long-pressing the home button.
But also because it seems I can finally have a few more apps staying in the background.
When looking for solutions to my problem, I ran across this : RAM and multitasking...so bad.
I said : "finally, someone understanding me".
I read all replies, and this is what seems to come out : KitKat seems to have a built-in feature that auto-kills app whenever a limit of active apps is reached.
This limit is around 10 and 20. I don't know where this limit is set, how it is defined, where I can find, how I can change, and why it exists.
I believe V6 Supercharger did change that limit on Jelly Bean and ICS. I thought this limit disappeared in 4.3.... did it come back in 4.4 ?
Does it work on KitKat ?
Well, I hope someone here can help me. Thanks !
Bump to this. I have a Xperia Z3 Compact and experience the same problem... I never have this problem before with other devices in 4.3.. The multitask since Kitkat is just horrible.