Related
I have started to notice the performance of my htc Desire degrading.
Apps take longer to load. Where before it was almost instant, now I have to look at plain black or white screens while the apps load.
Not sure what could be causing the problem. Anyway i can find out whats the causel?
Its a stock unrooted 2.1 desire.
Only things i have loaded recently is HTC IME keyboard mod and "what the doodle". all other apps were running for a long time.
Stock Unrooted 2.1? Just install 2.2, it's much faster.
I have found that the amount of available memory/RAM decreases the more you use the device. Not sure if its due to a memory leak somewhere, apps getting greedy with RAM, or what. I find that when it gets to a point thats too low for my taste, or performance starts to degrade, a simple restart works to clear up the issue. This happens even with a task manager, so I am not sure what the cause of the memory degradation is.
Mine did the same whilst on 2.1
Does a re-boot not speed things back up? If not it could be a dodgy app hogging memory.
When this happened to me, I fixed it by backing up using mybackup pro (worth every penny) and doing a factory reset. Takes only half an hour, and gets your desire back to box fresh speedy. Just be mindful of which apps you put back on.
I also take it your stock desire is branded? When your carrier releases 2.2 to you, you'll see a vast improvement too.
Sent from my HTC Desire using XDA App
I noticed this on my Desire (2.2 custom ROM) just now, and it seems to be a memory thing as according to "Android System Information" the CPU usage is low (under 10%) while the RAM usage is high (only 7% free). Is there any way to prevent the RAM going so low and performance degrading as a result? Will a task killer help for this? (I've read not to use them as Android's meant to take care of tasks but if it's not doing a good enough job of clearing up old tasks then surely it would be better to use one?)
Es task manager works well for me when my ram is getting low. Nice not having to reboot. Im on froyo 2.2
Sent from my HTC Desire using XDA App
Stock Desire on 2.1 used to slow down once it got to about 40mb free. Now running 2.2 and its always above 100mb. Runs fast all the time now but I keep my task manager from the 1.5 days as its handy to know what is running and using up the RAM
Sent from my HTC Desire using XDA App
ergoulf said:
Es task manager works well for me when my ram is getting low. Nice not having to reboot. Im on froyo 2.2
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
What do you do in ES Task Manager to free up your RAM? I tried "Kill All" but it didn't seem to have much effect (still stays at around 40 MB free). Had to restart in the end to get the performance back up to scratch (now has over 140 MB free).
Whiterin said:
I have found that the amount of available memory/RAM decreases the more you use the device. Not sure if its due to a memory leak somewhere, apps getting greedy with RAM, or what. I find that when it gets to a point thats too low for my taste, or performance starts to degrade, a simple restart works to clear up the issue. This happens even with a task manager, so I am not sure what the cause of the memory degradation is.
Click to expand...
Click to collapse
Same issue here and i suspect that default browser is the cause.
When free RAM goes very low, generally after one or two days from the startup in my case, i use free app OSManager to see all running processes. This app shows several instances of default browser process (called Internet), each one eating 40-50 Mb of RAM and in sleep state (not zombie). System never removes them and manual killing doesn't work, so there stay in memory over time. I tried different task managers, but only OSManager shows this detail.
To confirm this hypothesis, now i start to use Dolphin instead of default browser: in a couple of days, i will know if the issue is still present.
onmichele said:
Same issue here and i suspect that default browser is the cause.
When free RAM goes very low, generally after one or two days from the startup in my case, i use free app OSManager to see all running processes. This app shows several instances of default browser process (called Internet), each one eating 40-50 Mb of RAM and in sleep state (not zombie). System never removes them and manual killing doesn't work, so there stay in memory over time. I tried different task managers, but only OSManager shows this detail.
To confirm this hypothesis, now i start to use Dolphin instead of default browser: in a couple of days, i will know if the issue is still present.
Click to expand...
Click to collapse
Well, this isn't the cause for me as I have always run Dolphin Browser HD on the Desire. I don't use the default browser. I think it's mainly system processes that just stack up in the background. I found that going through and trimming the list of system processes did free up the memory, but it's just as fast to restart the device.
Hi i found an app called auto killer memory which ive been running for a while. this app has worked wonders for my wilderbeast, its on fire. so ive been tampering alot with things but this seems to have stabalised my phone loads. presets i set to lost, enabled advance mode,apply at boot,ticked all system tweaks and of course when promted enabled super user. my phone is now running sweet and battery has improved too. i dont know if this makes any sense but i have noticed a difference. whoop whoop. am i over optimistic that this works the same as the v6 super charger/juwes ram optimiser ???
Ok I've ammended my settings within this app after doing some research And in memory values I'm now running at 6/10/16/100/120/160 to keep my phone running snappppppy. To explain the values in brief...... if free memory goes below 160mb my phone starts to kill empty apps etc etc as free memory goes below next value the phone starts to kill corresponding apps. Kind of makes sense to me now. Ok I know my settings makes the phone kill more frequently but its damn snappy now,and it can lower the oom settings by long pressing the app in processes section you wish to lower and choosing lower oom. Lowering the oom basically gives the app less chance of being killed.
Personally I haven't had a low memory situation since I rooted and installed cm7, the app your talking about I have installed after reading one of your other posts about it, I presume that it would work the same way as juwes after setting the low memory values, I don't use those settings with it though as I have juwes script installed, the other tweaks seem fine but again I think I had some of them covered from editing my build.prop (still have work to do on that though) and a few other little things, I can't knock this app though as it does seem to have made my battery last a bit longer since installing yesterday, I'd personally rather change the settings myself than have yet another app doing it for me but until I figure which setting seems to be helping my battery out I'll keep it installed.
A couple of other apps which might help you keep it smooth,
Autostarts- I swear by this app its one of my best buys from the market, why use a task killer when you can just stop the app starting in the first place??
Fast reboot pro- after time apps hold memory which they don't really need, hit this and it'll quickly reboot everything (unless you tell it to leave something alone) freeing up spare ram.
Sent from my HTC Wildfire using xda premium
Cheers for info,really happy with this app at the moment.by the sounds of things its doing similar job to other script mods,which I can't get working cos of s - off issue. Posted this for s on users benefit. Hope it helps others.
Edit my settings. Read 1st post.
sent from my wilderbeast/buzz
The only problems I see with having higher settings are if it closes something you use regular it'll be slower to open that app, I'd rather keep them set low and have apps open quickly.
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
The only problems I see with having higher settings are if it closes something you use regular it'll be slower to open that app, I'd rather keep them set low and have apps open quickly.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
I agree but this app lets you temporary lower the oom level for apps,so I just lower oom on most important. Long click on process or service and to lower.
sent from my wilderbeast/buzz
Does it?..........I didn't spot that nice find!!
Sent from my HTC Wildfire using xda premium
Yep,long click app in service or process then choose to lower oom.it resets if you reboot so get your settings desired then leave by pressing home button.
sent from my wilderbeast:buzz
whats up with these settings for the pages? what do these settings change?
atm i have these settings:
2560
4096
25600
30720
40960
gozzaa said:
whats up with these settings for the pages? what do these settings change?
atm i have these settings:
2560
4096
25600
30720
40960
Click to expand...
Click to collapse
Change the view from pages to mb and these are the values when it will start killing processes etc. Ie. When your memory gets to the amount your phone starts freeing up starting with the highest setting (empty apps)
Its all explained above,just that you have the pages view instead of mbs.
Quote " its healthy to have enemies, it means you've stood up for something you believe in "
ahh the pagesettings are the same as the MB ones?
i thought its two different things
thanks for the explanation!
btw. do you still use the same settings?
Yes to this day I still use this app even though I'm now s-off with the settings I posted,I will just double check and ammend if needed on 1st post.
" once its gone,its GONE."
slymobi said:
am i over optimistic that this works the same as the v6 super charger/juwes ram optimiser ???
Click to expand...
Click to collapse
I used to use that too and I felt some differance too but I think you have to open the program every boot. But some told me that it isn't just powerful as Supercharger so I deleted the optimiser and tried Supercharged and got a bootloop instead. I didn't get it to work but I believe that Supercharger is a better solution.
zephyri-xr said:
I used to use that too and I felt some differance too but I think you have to open the program every boot. But some told me that it isn't just powerful as Supercharger so I deleted the optimiser and tried Supercharged and got a bootloop instead. I didn't get it to work but I believe that Supercharger is a better solution.
Click to expand...
Click to collapse
i tried supercharger and juuwes but had issues which i think were specific to me but one of the issues was bootlooping from supercharger as well as other things. im not saying one is better than the other but as you and myself had issues with one of the mods then its an alternative for others to use. i prefer this as you get to control the settings and mods yourself from the app. also this is available for s-on whilst the others i believe need s-off.
zephyri-xr said:
I used to use that too and I felt some differance too but I think you have to open the program every boot. But some told me that it isn't just powerful as Supercharger so I deleted the optimiser and tried Supercharged and got a bootloop instead. I didn't get it to work but I believe that Supercharger is a better solution.
Click to expand...
Click to collapse
I got a boot loop from supercharger. I had to wipe my phone and start again from an RUU as all my previous backups became corrupted. Nightmare. TBH in the few days that it did work, i saw/felt no difference.
Using CM_7.1.0.1 probably wouldnt advise to use the supercharge, CM_7 minfree values are set to a pretty good level to keep things in order i think
slymobi said:
Hi i found an app called auto killer memory which ive been running for a while. this app has worked wonders for my wilderbeast, its on fire. so ive been tampering alot with things but this seems to have stabalised my phone loads. presets i set to lost, enabled advance mode,apply at boot,ticked all system tweaks and of course when promted enabled super user. my phone is now running sweet and battery has improved too. i dont know if this makes any sense but i have noticed a difference. whoop whoop. am i over optimistic that this works the same as the v6 super charger/juwes ram optimiser ???
Ok I've ammended my settings within this app after doing some research And in memory values I'm now running at 6/10/16/100/120/160 to keep my phone running snappppppy. To explain the values in brief...... if free memory goes below 160mb my phone starts to kill empty apps etc etc as free memory goes below next value the phone starts to kill corresponding apps. Kind of makes sense to me now. Ok I know my settings makes the phone kill more frequently but its damn snappy now,and it can lower the oom settings by long pressing the app in processes section you wish to lower and choosing lower oom. Lowering the oom basically gives the app less chance of being killed.
Click to expand...
Click to collapse
I have tried supercharge script and does make phone smooth. Also Ive use ram manager new app and that too made phone smooth. But this app (Pro) is so far great. I tried out your settings for now to see if it suits me and had the app for an hour and the phone is very snappy and smooth (which is most important to me). I hope there is a slight battery improvement that many have said on the net but will test more and will leave feed back. A big thx m8!
no probs mate, like i said i have tried the lot and this one for me is really good and you get to be the controller lol.the only drawback i have noticed is that it takes a little longer for the phone to boot after a reboot but !!!!! im ok with that.
LMFAO looks like I didn't pay enough attention... I've used a lot of tweaks already to make my Willy faster, more snappy and stable but to be honest nothing gave it such a boost like that
BTW: are you still using the settings of the op?
Holy crap, I've read that really often here and elsewhere but it's the first it applies to myself: feels like a new phone
eventcom said:
LMFAO looks like I didn't pay enough attention... I've used a lot of tweaks already to make my Willy faster, more snappy and stable but to be honest nothing gave it such a boost like that
BTW: are you still using the settings of the op?
Holy crap, I've read that really often here and elsewhere but it's the first it applies to myself: feels like a new phone
Click to expand...
Click to collapse
I use aggressive setting mostly, all advanced tweaks except sdcard boost one as this bumps read ahead up to 2048, just my preference you might prefer 2048.
Say oooh la la
slymobi said:
I use aggressive setting mostly, all advanced tweaks except sdcard boost one as this bumps read ahead up to 2048, just my preference you might prefer 2048
Click to expand...
Click to collapse
I see. I just have to sort things out now. Regarding the SD card read - I have it already done by sdbooster (@2048) - I'm at a point where I should make a documentation to stay on track and to avoid double tweaks lol.
I'm also very interested into scratch's build.prop lol (guess that would help to drop even more tweaks). Thx again - I've not forgotten about your tip re. AMO - just shifted it too far lol.
Has anyone noticed that tasks tend to get auto killed a bit overzealously on ICS? I'm running 4.0.2 on mine. On many apps, if I switch to the browser to look at even one single page, I flip back only to find that the app I was just in has been killed, and it's loading from scratch. This was never the case for me on Gingerbread (CM7.1 stable, Glacier). Any thoughts?
Sent from my Galaxy Nexus using Tapatalk
Yes this phone has way too agressive task killing. Its been discussed already. The browser for example gets kicked from memory very quickly and too frequently. Sometimes i press the home button and go right back to the browser and it was killed. I really hope google tweaks it.
I kill apps after using them anyway, never have any open in the 'Recent apps' as I like to keep it clean
Same here...
I did take a glance at memory usage. It could be in part because I'm using Nova Launcher, Light Flow,SwiftKey X and Tasker... If enough apps that think they're important are competing for memory, the OS could be making misguided choices on what to kill.
Sent from my Galaxy Nexus using Tapatalk
You can always tweak your minifree values yourself.
WiredPirate said:
You can always tweak your minifree values yourself.
Click to expand...
Click to collapse
Can you clarify what you mean by this?
Sent from my Galaxy Nexus using Tapatalk
I dont have a vast knowledge of how it works, I have done it on my Captivate and Atrix but have not had the need yet to do it on Nexus. This app is about the extent of what I know. Give it a try. When you find some values you like post back here what they are. And if you require more information you can always do a search or a Google search.
Here is the YouTube video for the app.
WiredPirate said:
You can always tweak your minifree values yourself.
Click to expand...
Click to collapse
This is what ive been meaning to do, just been lazy. It may be the only way to fix this.
Thanks I'll take a look at it. It's minfree (not mini), which makes more sense as I presume it stands for "minimum free" memory.
Sent from my Galaxy Nexus using Tapatalk
Just tried experimenting with minfreemanager and i have excellent results so far with the following:
Change the last 3 values (free version only) to 46, 48, 50. So here are my values:
29, 37, 44, 46, 48, 50
This keeps things in memory much better and longer so the browser for example doesnt get kicked out of memory so often.
Actually i had to go more aggressive. I used the preset called system default.
My understanding was that aggressive in the context of that app meant leave more memory open / let the system kill more tasks. If you want tasks to actually stay open, you'd have to go less aggressive.
cmstlist said:
My understanding was that aggressive in the context of that app meant leave more memory open / let the system kill more tasks. If you want tasks to actually stay open, you'd have to go less aggressive.
Click to expand...
Click to collapse
Well in my case i dont want apps killed so easily. So the lower the numbers the better. This means that more apps will be left open. So i guess youre right i should have said less aggressive.
The title is basically the question, im fed up of alot of programs auto opening on my android phone, it takes battery and is slightly annoying receiving notifications off apps i dont really care about such as the NFL game tells me about small things in the NFL, im in the UK, i dont care.
If you argue that it doesnt take alot of battery currently have 117mb free ram, (2 secs later) killed all my selected apps now have 201mb free so im using 80mb of ram on apps im not using. Ive made 2 or 3 phone calls today no more than 30 mins long altogether and ive lost 55% of my battery since about midday, which is when i unplugged the phone.
And I think all these apps are the problem so how can I stop them from auto opening, please help
Search the market for startup cleaner
Sent from my A101IT using xda premium
yusuo said:
If you argue that it doesnt take alot of battery currently have 117mb free ram
Click to expand...
Click to collapse
More free RAM doesn't really equate to longer battery life or lower power consumption.
Better search for auto starts, this asp shows you the conditions an asp can turn back on and you can bin it off, Facebook for example had like 8 conditions, from full to medium battery life, on charge and change in network....... Use it
Sent from my HTC Desire using xda premium
rootSU said:
More free RAM doesn't really equate to longer battery life or lower power consumption.
Click to expand...
Click to collapse
There's still no reason for most of this apps to use RAM. Apps like facebook and skype shouldn't be actice without user permission. Without login they are complete useless.
I'll try Startup Cleaner, thx.
It's how android works and what RAM is for. There is always a reason.
Sure if someone doesn't use Facebook, it should be uninstallable, but its not and its not causing any harm
Sent from my HTC Desire using Tapatalk
The problem isn't that apps start when I turn on the phone its that even after i use task manager to close they keep reopening and use over 100mb of ram, earlier I checked and only had 78mb ram available.
This must have an effect on battery to some degree i want to kinda ban certain apps from running in the background unless i specifically tell them to
RAM doesn't use more power, the more its used, no.
You don't need a task killer. You do not need to obsess about RAM. Forget about RAM and enjoy your phone
Sent from my HTC Desire using Tapatalk
rootSU said:
RAM doesn't use more power, the more its used, no.
You don't need a task killer. You do not need to obsess about RAM. Forget about RAM and enjoy your phone
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Thanks for you reply but its not really an answer its more of a contradiction, what I was asking is how to I stop apps from auto starting and eating up RAM, regardless of how long the phones been on
...and I'm telling you its a pointless, unecessary waste of time. Also it is not possible. Autostarts as already mentioned is the closest you'll get
Sent from my HTC Desire using Tapatalk
I also turned off the autorun permissions of a lot of apps, for 2 reasons: 1) a device that is smooth sooner after booting, using less cpu cycles/power. 2) preventing Sense from reloading due to RAM shortage and have smooth multitasking.
1) Android loads a bunch of apps to the RAM that have the autorun permission, until it thinks it is "enough" and useful to you. No matter how many apps you have installed, the amount of free RAM is always about the same, just the number of "unwanted" apps in the RAM differs. Removing the autorun on boot permissions prevents the loading of unnecessary apps that will immediately be removed from the RAM the moment you start the browser/a game, saving cpu cycles=power. So for me there is no point in loading them in the first place, because I am never going to use them (right away). I want the apps that don't to any syncing loaded on demand.
2) I hate slow multitasking and I hate it even more when Sense reloads because it got kicked out of the RAM after each time I press HOME.
I use 3G Watchdog (~12MB RAM), Unlock with Wifi (~8MB), Whatsapp (~15MB), Handcent SMS (~18MB), Droidstats (~13MB), Extended Controls (~12MB), Battery Monitor Widget Pro (~13MB). Okay, I maybe could delete some of them, but these app are "OK" to me, because I use them actively or just need a background service to operate normally.
With Gemini I disabled apps like Facebook, a screenshot tool (just load when I want to make a screenshot..), various public transport planning tools, etc from autostarting.
No joy moment: after using the Facebook app (market version), it may take up 50+ MB and it will not be closed when I start another RAM intensive app, because it is a high priority service. Result: Sense gets kicked out of the RAM. Or, when the situation is somewhat less critical: multitasking is as good as unusable: switching between apps makes them load over and over again, because app2 kicks app1 out of the RAM and vice versa, causing unnecessary lag. Therefore: when I am done with facebook, I close it, then STAY the hell closed It may only autostart when it receives a push message. In that case it is nice to have FB already in RAM when I tap the notification.
Why do even some games have background services, or the Engadget app, or .. , or... all eating precious RAM. And yes, I know, once IN the RAM they eat no battery, but they DO eat battery when the app loads itself back in the RAM when it thinks it needs to, after it got kicked the moment I decided to so something else.
Hmm, spent way too much time to try to explain my frustration Oh and by the way, I have a Legend, but the basics are the same of course.
Dwnload an app called internet commander from the market. It shuts off the internet when your screen turns off but still let's you get calls and texts. I've got my phone , rooted of course, clocked to 710 and my battery will last for days.
Sent from my Eris using xda premium
I just re read your post, that won't help with apps but it will help save battery. And when you turn your screen on the internet kicks right on instantly. Good luck
Sent from my Eris using xda premium
yusuo said:
The problem isn't that apps start when I turn on the phone its that even after i use task manager to close they keep reopening and use over 100mb of ram, earlier I checked and only had 78mb ram available.
This must have an effect on battery to some degree i want to kinda ban certain apps from running in the background unless i specifically tell them to
Click to expand...
Click to collapse
The guys here have already suggested you use a certain program from the Market. Have you tried it?
Regarding the whole RAM consumption issue, Android has its own built-in memory management system that ensures that there's always enough RAM for an app whenever it needs it, even if the memory manager shows like 40 MB free. Basically it "ejects" all background, unused apps, from memory making room for the foreground app which needs it most. If for some reason you need to fiddle with that, you can try using the V6 Supercharger script. I find it suitable for my needs but YMMV. It's completely reversible, so if you don't like it you can uninstall it just like that.
P.S. - I agree with rootSU, the ammount of free RAM has nothing to do with battery consumption. If you suspect that an app is draining your battery, check Android's battery statistics to find the culprit.
TVTV said:
Regarding the whole RAM consumption issue, Android has its own built-in memory management system that ensures that there's always enough RAM for an app whenever it needs it, even if the memory manager shows like 40 MB free. Basically it "ejects" all background, unused apps, from memory making room for the foreground app which needs it most. If for some reason you need to fiddle with that, you can try using the V6 Supercharger script. I find it suitable for my needs but YMMV. It's completely reversible, so if you don't like it you can uninstall it just like that.
P.S. - I agree with rootSU, the ammount of free RAM has nothing to do with battery consumption. If you suspect that an app is draining your battery, check Android's battery statistics to find the culprit.
Click to expand...
Click to collapse
I respectfuly disagree. Android built in ram management is just silly. If I open xda app for example (it could actually be any app for that matter), reply to a few posts, read a few more and close it, why does it need to stay in ram? It reloads anyway when I run it again after I've closed it (using the back button or the actual exit command in the app itself). Why does the camera app need to stay in the background after I just shot a few photos and closed it? Because I may or may not use it again in some time? It's rediculous. And the whole theory that ram management doesn't require any power/cpu usage, how do you guys think all those apps get killed? Android will power?! No, kernel scans all running apps and kills the ones based on built in heuristics so it also reads them first. So that doesn't require any power/battery? Awesome if it's true! Although I wouldn't bet on that. And all this fuss just because you may or may not launch the same app sometime during the next day/week/month/year or it'll eventually get killed? Now that's just plain stupid. I get apps that need services like widgets, push notifications etc. but random apps like root explorer, xda app, titanium, youtube etc. which are opened specificly by the user shouldn't be in ram just for the sake of it after they're closed. I closed it, meaning I don't need it anymore. And I don't need the kernel to scan all apps and running services every time I launch an app so it could provide the free ram that app needs. Consumes cpu time, battery, i/o ... every piece of hardware actually just to free some ram that shouldn't be occupied in the first place. Every app that I ever opened on my phone got loaded almost instantly and that's just after phone had been booted. So after that it should stay in ram so I could open it in a blink of an eye instead of instantly? That's just funny.
Anyway, I'm just thinking out loud so don't flame me immediately. There probably are apsects of it that I didn't mention here or am not aware of. And I'm not saying that I'm right and you guys are wrong, I'm just saying what I know and think about this subject.
-. typewrited .-
PlayPetepp, while it might be true that the OS allocates (thus use) some resources to memory maintenance, the impact on battery life is negligible. In the Android OS, apps in memory are ordered according to priority and state, so the OS always knows which apps to kill first if it needs to make room in RAM, without much of a hassle. The only bad consequence of this system seems to be the fact that once the memory fills up, the launcher may lag or even be evacuated from memory. But, as i've mentioned in my previous post, there are ways to prevent that, either via scripts or, if you know what you're doing, via editing system files.
So the OS doesn't need to scan anything as it keeps everything in memory again? Seems like an endless loop. Open, sort, kill if needed, reopen, sort again, kill ... to what end, constant unneccessary multitasking that user is unaware of? I really don't see any benefit of that system and am only seeing the downsides. I mean, who needs every app they ever run remain in ram even if they close them after using? And then opening another app and "waiting" for whatever needs to be closed to get it running. Sure you can mess with the scripts (init.d, init.rc, etc.) but the underlined conditions stay the same. I hope I'm making sense here. Or am I fighting against windmills.
I just figured out that I strayed from the topic of this thread so won't be continuing this discussion if it's considered offtopic.
-. typewrited .-
Stop looking for excuses for poor multitasking in Sense 3+ roms
erklat said:
Stop looking for excuses for poor multitasking in Sense 3+ roms
Click to expand...
Click to collapse
Hello again nice to see you here
Here's an interesting article on what I was talking about. Sense 3.5 doesn't need that many mbs of ram to work smoothly. After booting and setting everything up I have 150+ mb free. That should be enough for decent multitasking but all those apps not getting killed when you close them are eating too much. Can anyone explain in detail what hidden app, perceptible app, backup app and heavy_weight app means? I've been googling this for a week and can't find any decent explanation.
@PlayPetepp - I think i have already said (in my previous post) that the OS does indeed use some resources for managing the memory, but they are negligible in terms of their impact on battery life. IMHO, the only thing a 3'rd party memory manager (task killer) WILL do is improve lanuncher responsiveness (lag) as the lag does increase when free RAM drops under a certain limit. Thus used wisely, a task killer can improve responsiveness, but battery life... very little, in rare cases (it does the opposite, most of the time).
Regarding the so called "memory slots", here's an excerpt from this article:
FOREGROUND_APP: This is the application currently on the screen, and running
VISIBLE_APP: This is an application that is open, and running in the background because it's still doing something
SECONDARY_SERVER: This is a process (a service that an application needs) that is alive and ready in case it's needed to do something
HIDDEN_APP: This again is a process, that sits idle (but still alive) in case it's needed by an app that's alive and running
CONTENT_PROVIDER: This is apps that provide data (content) to the system. HTC Facebook Sync? That's a CONTENT_PROVIDER. So are things like the Android Market, or Fring. If they are alive, they can refresh and provide the content they are supposed to at the set interval. If you kill them, they can't of course.
EMPTY_APP: I call these "ghosts." They are apps that you have opened, but are done with them. Android uses a unique style of handling memory management. When an activity is ended, instead of killing it off Android keeps the application in memory so that opening them again is a faster process. Theses "ghost" apps use no battery or CPU time, they just fill RAM that would be otherwise empty. When this memory is needed by a different application or process, the RAM is flushed and made available for the new app. To satisfy the geekier people (like myself) Android does this by keeping a list of recently used apps, with the oldest apps in the list given the lowest priority -- they are killed first if RAM is needed elsewhere. This is a perfect way to handle 'ghost' processes, so there's no need to touch this part
Click to expand...
Click to collapse
>> A super easy way to improve One X Multitasking significantly (rooted phone only)
Guys, there are some discussion on different post indicated One X Multitasking is not as good as previous HTC phones. Sometimes you can only have very few APPs in background, and sometimes you switch APPs and find it has to reload or not return to the place where you were.
Here is a method I have tried which is significantly improve the Multitasking for One X. It only worked for rooted phone, so if you are not rooted, no need to try below action. It will not work.
1. Go to Google Player store to download and install APP "System Tuner" (it is free)
2. Run System Tuner. In its main screen push "Active Tweaks" (right besides the CPU button)
3. In the new windows, up right press Auto-kill tweaks. It will bring another screen show all the value indicate the lowest memory to trigger auto-kill by system default during out-of-memory for each group. (you do not need to care what does it means if you not know it). You'd better to make a screen shot to save these value. So if you do not like the change below you can modify to the default value.
4. There are two buttons at the bottom of screen, press the bottom left button, then in pop windows choose the second choice which I think is good enough for One X. I do not see the need you manually change the value for each group and try to figure out that is the best, just choose from list provided is enough).
After that you will see all the 6 figures has changed to 4M, 8M,10M,16M,24M,32M. And it is done. Now you can try to see how good Multitasking is on your One X.
You do not need to keep System Tuner APP alive, after the action above it has change some files in system and it will mostly kept there. These change make the auto-killer not so strictly like before. Of course if you reboot the phone those setting will change back to default. And you can do those action again. And you can use the bottom right button setting to make it works after even reboot but I do not want to go into detail for that.(not to change make it works after the reboot make it easy for you to change back to default value just by re-boot the phone).
Some notes: you do not need to read below at all if you not interested in)
- System Tuner is a very powerful tool can do lots of thing. I would not recommend you use it for other modification of the system unless you know what you are doing.
- Some simple explanation of the display info's meaning for action 3 above -
Android puts each running app into 1 of 6 Out Of Memory(OOM) groups based on their priority. They are FOREGROUND_APP, VISIBLE_APP, SECONDARY_SERVER, HIDDEN_APP, CONTENT_PROVIDER, and EMPTY_APP. The value after each group is the amount of memory limits trigger OOM condition that will start kill APP. The lowest group (EMPTY_APP) get killed first.
For my One X EMPTY_APP is set to 80M as default. And if you click right white icon on that screen it will show what APPs under each group. Actually most APPs you have will be in EMPTY_APP group which being killed first.
- Since some guy reported that latest ROM update make multitask better, so probably HTC has changed the value for each group to small limit. If you can give screen shot and tell which ROM version you are on we can verify that. Or you can just report the value for EMPTY_APP. (mine is 80 and not upgrade to latest rom yet)
I hope it will helps those who suffered from bad multitask performance of One X. Enjoy and thanks the author of "System Tuner"
Thanks for the great easy to follow post will respond and let you know any improvements.
The OOM values don't help much with the situation as the phone has plenty of memory for our applications. This can be demonstrated by checking the list of running applications in Task Manager. Notice how fast it takes to start up the application but it takes a second or two to reload the information in it? Many of the programs that will have to reload are loaded into the memory. The problem is the way HTC has set the system to deal with the caches of each program (Caches or something else, I'm no Android programmer so bear with me.). HTC has made the One X aggressively kill that cache in order to stop a program from possibly running in the background in order to drain battery life. So if there is a setting that deals with that, that's what I would be looking to tweak.
This phone sounds have lot of memory but actually not.
Not let the theory to prevent you trying the method. It works great on my one X.
mmx6688 said:
This phone sounds have lot of memory but actually not.
Not let the theory to prevent you trying the method. It works great on my one X.
Click to expand...
Click to collapse
I have tried the method. There isn't a perceivable difference. The issue isn't memory available, but of how the phone manages saved states.
dosen't work, what we need is something that can just terminate the process that phone is using to kill all processes, just wondering about other devices on ICS, do they behave same or its just HTC.