Related
Ok, so there are task killer threads that lead me to believe that they a are a waste of time by and large, and that android automatically sorts things out. Those same posts also point out that task killers are an extra drain on the battery having to start applications over again uses more battery than leaving something dormant in the background. These posts are not the thoughts of one person but unanimous to those threads. All very well, but then there are the battery saving threads that say to close down all applications that aren't being used to save additional battery??? Again this is the view of everyone in those particular threads, so is there any chance of getting the two camps to FIGHT! And then I can decide which I shall choose to do!
For info I currently have task killer and use it all the time and get a full days use out of my battery which is good because I cane the hell out of it! But If I could improve it that would be good. I have however this afternoon decided to not use task killer for a few days and see how I get on. But an explanation would be good from both sides.
I never use a task killer and get 2 or 3 days use out of of my Desire. No point in a war just use your Desire for a week without a task killer and then a week with. I am pretty sure you will just find the task killer slows things down and doesn't improve battery life. You will not find any of the ROM chefs using a task killer either!
HI
I was reading one of those posts this morning and decided to uninstall task-killer.I have to say that after half day of heavy use my device started to be so laggy it took contacts or calendar 5 seconds to open!then I checked running processes and pretty much everything I was playing with was still running.memory dropped to 10MB and device became unusable.cannot say battery use has improved.I think it was the same.
But my task-killer is back up and running.
I must say that I am new to Android.I was using WM for long time.I can cook my own ROMs so I am not a noob but I know very little about Android.so if anyone knows what could be the reason of this huge slowdown I will be grateful for explanation.
And one more thing that needs to be said...
My device is rooted and I am using a2sd too.
polystirenman said:
HI
I was reading one of those posts this morning and decided to uninstall task-killer.I have to say that after half day of heavy use my device started to be so laggy it took contacts or calendar 5 seconds to open!then I checked running processes and pretty much everything I was playing with was still running.memory dropped to 10MB and device became unusable.cannot say battery use has improved.I think it was the same.
But my task-killer is back up and running.
I must say that I am new to Android.I was using WM for long time.I can cook my own ROMs so I am not a noob but I know very little about Android.so if anyone knows what could be the reason of this huge slowdown I will be grateful for explanation.
And one more thing that needs to be said...
My device is rooted and I am using a2sd too.
Click to expand...
Click to collapse
You may like to read this:
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
dhiral.v said:
You may like to read this:
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
Click to expand...
Click to collapse
well.i did read that before.that is why i do not understand why my phone was so slow.they are claiming that android should close apps by itself to reclaim memory.but in my case that wasn't true.everything was running and nothing was getting closed by system.
Here's another good read:
Google and Cyanogen comments imply task killer/manager apps are pointless
Both Dianne Hackborn and Cyanogen say Task Killers are useless, even developers of these apps concur. You should listen to them, I guess they understand juuust a little bit more than we do what Android is about.
pascanu said:
Here's another good read:
Google and Cyanogen comments imply task killer/manager apps are pointless
Both Dianne Hackborn and Cyanogen say Task Killers are useless, even developers of these apps concur. You should listen to them, I guess they understand juuust a little bit more than we do what Android is about.
Click to expand...
Click to collapse
i would like to believe it.i was so excited when i saw a post saying that i should get rid of task-killer.but as i wrote before after half day of heavy use(my phone is new so i play with it a lot :-D ) without task killer my phone was soooooo slow i couldn't use it anymore.today i had task-killer back on the phone and all day no slowdown what so ever.i don't understand that.i am starting to think it is related to A2SD and memory being relocated to SD card.
I also agree that taskkiller (the way it works for WM) is not good for android, because android has a better memory management...
but there is another flavour of taskkiller in the market... which are based on this:
How to configure Android's *internal* taskkiller
Unfortunately, your phone needs to be rooted before you can use that method.
If you worry about memory remember that the worst kind of memory is...free memory ! Because it's not being used. Obviously ram gets reclaimed and freed when it's needed.
As said in a couple more redundant threads, there might be a rogue app which you are better off closing because it stays in the background wrongly eating cpu cycles, but this is very very rare. Otherwise I think it's just the usual placebo effect...
andycted said:
If you worry about memory remember that the worst kind of memory is...free memory ! Because it's not being used. Obviously ram gets reclaimed and freed when it's needed.
As said in a couple more redundant threads, there might be a rogue app which you are better off closing because it stays in the background wrongly eating cpu cycles, but this is very very rare. Otherwise I think it's just the usual placebo effect...
Click to expand...
Click to collapse
Have you read the link in my previous post?
ANOTHER thread about this... There must be plenty of threads on this now, but I'll just once more give my impression.
Personally I have had HTC widgets like NEWS or MAIL or CALENDER hang or crash on me and I could not restart them unless I restarted the phone. In this case an app killer was ESSENTIAL. I don't believe you need to leave the app killer running always and kill every single task when your done, but its essential to have one installed so if a widget hangs (as has happened quite a few times on the Desire) you can kill the hung app without having to try a 5 hour shut down(another desire issue) and battery removal.
Also... after 2 days use of many apps and camera use and internet and youtube app etc, your internal RAM will be about 50mb available to programs. yes, android is supposed to kill stuff as it needs, and Im sure it does, but 50mb free memory compared to 150mb the lag is VERY obvious. So I do tend to kill tasks like camera and youtube etc if I have not used them in a day and my phone seem slaggy. the phone definetly runs faster then. Thats just a fact. So the internal android task killer is not as efficent as you'd like to think. Android 2.2 runs 450% faster than 2.1 so maybe then no lag will EVER be noticable. I'll still keep a task killer installed though in case widgets crash or hang.
I found my battery most efficient with this setup:
- Installed Advanced Task killer (free)
- Security level: High (it doesn't show system apps)
- I have put all frequently using apps on ignore list: ATK, Messages, BatteryTimeLite, Internet, Weather, Clock, Calendar (so Android manage with those apps)
- Auto kill Level: Safe
- Auto kill Frequency: 2 hours
With that setup battery lasts almost half time longer than without TK or with killing all apps when screen goes off. Also I don't have any force closes / lag.
Never experienced lag at 100 or 20 mb free.
mcgon1979 said:
but 50mb free memory compared to 150mb the lag is VERY obvious.
Click to expand...
Click to collapse
The amount of free memory doesn't necessarily have anything to do with lag.
As Android does not use virtual memory (unless you've hacked in swapper, which is a bad idea anyway), it will attempt to make best use of available memory which may mean keeping recently used items in memory, and thus "consuming" free memory. However, if those items are not actively processing, they should not be consuming CPU cycles and therefore consuming little to no power.
As far as a running system is concerned, having lots of free memory just means that it is being underutilized.
I don't kill tasks and my phone never lags - that's just a fact too!
Regards,
Dave
boge said:
I also agree that taskkiller (the way it works for WM) is not good for android, because android has a better memory management...
but there is another flavour of taskkiller in the market... which are based on this:
How to configure Android's *internal* taskkiller
Unfortunately, your phone needs to be rooted before you can use that method.
Click to expand...
Click to collapse
Using this method it is possible to make the native task killer a bit more aggresive. I did some experiments with this on the HTC Hero and it just might have improved speed slightly but at the expense of stability.
"Normal" task killers are completely pointless but if people want to use them why not? It they want to sacrifice both battery life and performance by using one surely that is their choice. Whatever the experts says will not convince them.
I suppose you could use one to kill the very occasional hung app. i.e. Once every few days, but most people seem to use them constantly and totally indiscriminately.
1. About Cpu: get a task manager with cpu monitoring and verify for yourself, frozen applications in background don't do anything.
2. About memory: If an application needs 10 MB it just uses 10 MB and couldn't care less if there are 11, 100, 1000 MB free. The only moment you COULD see a tiny slowdown is the instant it needs 20 and there are only 10 available, but the system is quite good in managing that, and freeing resources (there are six levels of memory cleaning which progressively remove unused applications from the background)
3. If you stop monitoring memory usage, stop worrying about the system, you'll find out it manages itself perfectly and you enjoy the phone a lot more.
Interesting article about installed apps and a battery.
http://blog.gsmarena.com/android-handsets-batteries-should-last-for-more-than-a-day-google-says/
"...Page accused the installed apps of causing the problems and claimed that software running in the background exhausts the battery quickly...."
Interesting article about installed apps and a battery.
http://blog.gsmarena.com/android-handsets-batteries-should-last-for-more-than-a-day-google-says/
"...Page accused the installed apps of causing the problems and claimed that software running in the background exhausts the battery quickly...."
Click to expand...
Click to collapse
as said in the post above, get a cpu monitoring task manager and see for yourself if you have something wrong. Personally I don't have any.
Also watch battery history which tells you if the phone doesn't manage to go properly to sleep (partial wake)
regarding that article, iphone users get way less battery time and they don't even have multitasking...
-------------------------------------
Ipad's dont have "Spell Check" thery have "Replace" built into Safarii adn it wokrs just fineq!!!
I personally installed auto memory manager, an app that configures android's internal task killer. Its not a task manager by itself, uses android's task manager. You can set the limits in MB for all the app categories android has.
I was using it in my hero as well and found it really useful. Before having it installed, after some time my free memory was ~50mb, thus my phone was sometimes lagging. Now its always above 100mb and no lag at all
Okay, so I hear in FroYo that you're not suppose to kill and end tasks? Does that means services as well? And if I wasn't suppose to kill them, then wouldn't that make my battery life worse because of all the things running in the background?
TIA
Sent from my Epic 4G
You shouldn't use a task killer in any version of android from Froyo on, froyo handles its memory management extremely well when left alone, using a task killer could result in apps constantly opening and closing in the back ground, which would use a lot of battery .
Texted while driving
Alright. I got rid of my task killers. Is ending services fine though? And what about the task manager that the phone provides? (I'm guessing the second one is a no?)
And what other precautions should I take for battery (other than having low brightness, of course)
Sent from my Epic 4G
Only use the one built into the touchwiz framework if you have an app running out of control hogging resources.
If you're looking to improve battery, I strongly suggest Juicedefender with ultimatejuice, I have almost tripled my battery since I started using them.
Texted while driving
063_XOBX said:
Only use the one built into the touchwiz framework if you have an app running out of control hogging resources.
If you're looking to improve battery, I strongly suggest Juicedefender with ultimatejuice, I have almost tripled my battery since I started using them.
Texted while driving
Click to expand...
Click to collapse
Thanks. Just got both. What do you reccomend I put the aggressiveness on?
Sent from my Epic 4G
I keep it on custom and 15 minutes every 2 hours.
Texted while driving
063_XOBX said:
I keep it on custom and 15 minutes every 2 hours.
Texted while driving
Click to expand...
Click to collapse
Wait, I'm a bit confused. What do you mean 15 min every 2 hours? Like I can only put my frequency to 15 min OR 2 hours? Sorry if I seem stupid lol
Sent from my Epic 4G
Data on for 15 minutes every 2 hours.
Texted while driving
063_XOBX said:
Data on for 15 minutes every 2 hours.
Texted while driving
Click to expand...
Click to collapse
I figured it out
Thanks for everything.
Sent from my Epic 4G
I use the Advanced Task Killer for Froyo. Several apps I have like the Weather Channel and stock browser lower my available memory to a minute amount of what it was at boot up and do not reload if killed.
BONSAI 4 and loving it!
kennyglass123 said:
I use the Advanced Task Killer for Froyo. Several apps I have like the Weather Channel and stock browser lower my available memory to a minute amount of what it was at boot up and do not reload if killed.
BONSAI 4 and loving it!
Click to expand...
Click to collapse
The amount of memory available on your phone is supposed to become low. Apps are stored in memory when not being used. This does not take battery and allows the program to start in a faster fashion then otherwise.
Sent from my Incredible using Tapatalk
I'm sorry guys, but the information given in response here is really dangerous. Yes Froyo, and all versions of Android have built in memory management. HOWEVER, it is the job of the application developer to use the proper calls and closes to make sure the application isn't holding onto resources when in a background state. This is NOT always the case, and is constantly overlooked on all OS platforms, especially with how fast application development is happening on mobile platforms.
YMMV, when and if you should be using task killers.
linuxmotion said:
The amount of memory available on your phone is supposed to become low. Apps are stored in memory when not being used. This does not take battery and allows the program to start in a faster fashion then otherwise.
Sent from my Incredible using Tapatalk
Click to expand...
Click to collapse
No it's not. There is only 337MB of RAM available of which about 150 is used by system. If I keep loading apps that stay in memory when not being used I will have no resources or memory available for additional web pages or other apps. Why should the Weather Channel app load 50 MB of memory and stay there if I use it twice a week? When an app is closed I want it out of RAM. I can wait the 50 milliseconds to reload if I want to use it again.
BONSAI 4 and loving it!
Here we go again another argument of task manager for android
For me i use advanced task manager to kill some apps to speed up my phone a little and also use it to switch between programs that are already open where as if you try reopening some programs the restart,
I also ignore apps that i need to open and stay open like beuatiful widgets, word games to get more reliable notifications and widget locker.
I freeze with titanium some services such as drm and sns...
Free RAM is wasted RAM. Unless your trying to track down rogue processes, task killers are totally unnecessary.
http://lifehacker.com/#!5650894/and...ed-what-they-do-and-why-you-shouldnt-use-them
mattallica76 said:
Free RAM is wasted RAM. Unless your trying to track down rogue processes, task killers are totally unnecessary.
http://lifehacker.com/#!5650894/and...ed-what-they-do-and-why-you-shouldnt-use-them
Click to expand...
Click to collapse
I like to save some for a rainy day
mattallica76 said:
Free RAM is wasted RAM. Unless your trying to track down rogue processes, task killers are totally unnecessary.
http://lifehacker.com/#!5650894/and...ed-what-they-do-and-why-you-shouldnt-use-them
Click to expand...
Click to collapse
What that article hints at but doesn't exactly explain is that due to how the Dalvik JIT works, killing those apps that aren't actively consuming CPU will cause worse performance over the long run. The JIT has to spin up everytime the app is loaded - if it is already in memory then it's already optomized.
At least that's my understanding! I could be totally talking out my arse
EDIT:
Here is its straight from the Dalvik lead dev.
Well don't know about performance but yesterday killing apps with ATK Froyo especially the browser, I came home with 62% battery left. Today had about the same use but disabled ATK and never used it and came home with 31% battery left. ATK is doing something for my battery and will give up apps loading quickly for battery life any day.
OK just to clarify things with you guys, I'm not a noob at this stuff and I am pretty experienced with roms, kernels, flashing, and a little bit with creating roms. The biggest problem I'm having is my phones memory is very low compared to other EPIC phones. For example Ive placed the new urban fury 1.4 rom on 2 epic phones both completely reset through odin and when the rom is on there are the same FEW apps that come with the rom, my phones max memory that my task manager shows is about 198 and the other phones max is about 241. When using both phones I use 2 seperate task managers to kill memory and the "running servives" shortcut in the settings menu to completely kill some. Over a span of about 6-8 hours of using both phones with gradual use the max memory dropped on my phone from about 198 to 168 and the other phone dropped only from 238 to 231. These numbers dont make much sense to me because they have both been completely wiped, they have the same stock apps (no more), and I've tried this on many many roms through eb13 and ec05. The only difference between the 2 is that my phones SD card has like 14.5 out of 16GB full and the other phone only has 3GB full out of 16. Im about to just replace the phone with sprint (first reset the root, etc.) but if anyone can give me a second option I would greatly appreciate it.
bestcavsfan said:
OK just to clarify things with you guys, I'm not a noob at this stuff and I am pretty experienced with roms, kernels, flashing, and a little bit with creating roms. The biggest problem I'm having is my phones memory is very low compared to other EPIC phones. For example Ive placed the new urban fury 1.4 rom on 2 epic phones both completely reset through odin and when the rom is on there are the same FEW apps that come with the rom, my phones max memory that my task manager shows is about 198 and the other phones max is about 241. When using both phones I use 2 seperate task managers to kill memory and the "running servives" shortcut in the settings menu to completely kill some. Over a span of about 6-8 hours of using both phones with gradual use the max memory dropped on my phone from about 198 to 168 and the other phone dropped only from 238 to 231. These numbers dont make much sense to me because they have both been completely wiped, they have the same stock apps (no more), and I've tried this on many many roms through eb13 and ec05. The only difference between the 2 is that my phones SD card has like 14.5 out of 16GB full and the other phone only has 3GB full out of 16. Im about to just replace the phone with sprint (first reset the root, etc.) but if anyone can give me a second option I would greatly appreciate it.
Click to expand...
Click to collapse
Is it possible that one phone has a swap partition set up? That would explain the memory differences. What happens if they are both Odin'd to straight stock?
kennyglass123 said:
Is it possible that one phone has a swap partition set up? That would explain the memory differences. What happens if they are both Odin'd to straight stock?
Click to expand...
Click to collapse
I dont think so ill check that out but like stock dk18 or eb13 or what?
bestcavsfan said:
I dont think so ill check that out but like stock dk18 or eb13 or what?
Click to expand...
Click to collapse
You can grab the EC05 tar here:
http://forum.xda-developers.com/showthread.php?t=1052813
2 phones, set back to stock with the same tar should have exactly the same amount of memory free.
kennyglass123 said:
You can grab the EC05 tar here:
http://forum.xda-developers.com/showthread.php?t=1052813
2 phones, set back to stock with the same tar should have exactly the same amount of memory free.
Click to expand...
Click to collapse
Ya i know i have that tar and did exactly what u just told me to do and im still having this memory problem. its not like this problem had just started, its been going on for...around 5 months, idk i lost track lol. With this info do u think it would just be best to have sprint replace my phone (for free of course)?
Is it bad then that my epic with a fresh rom flash averages about 120mb, and max is about 160mb?
bestcavsfan said:
Ya i know i have that tar and did exactly what u just told me to do and im still having this memory problem. its not like this problem had just started, its been going on for...around 5 months, idk i lost track lol. With this info do u think it would just be best to have sprint replace my phone (for free of course)?
Click to expand...
Click to collapse
What is sounds like to me is you have some bad memory blocks and that is the reason for less memory free. If both phones were Odin'd back and yours shows the same behavior then it may be worth your time to try and get a replacement. The only thing is it does not make the phone non-functional so you will have to find an agreeable tech.
ac16313 said:
Is it bad then that my epic with a fresh rom flash averages about 120mb, and max is about 160mb?
Click to expand...
Click to collapse
That all depends on what you have loading at startup. Sync services, DRM, Maps, all use memory on startup. If you killed all your apps at bootup you would have more to start out with. So without more info there is no way of knowing. I would say starting around 160MB free after a fresh boot is good though.
kennyglass123 said:
That all depends on what you have loading at startup. Sync services, DRM, Maps, all use memory on startup. If you killed all your apps at bootup you would have more to start out with. So without more info there is no way of knowing. I would say starting around 160MB free after a fresh boot is good though.
Click to expand...
Click to collapse
i have everything but sprint bloatware starting up, but at boot i get about 160 but after about an hour it drops to usually around 100. i noticed that when i would kill tasks running in background like gallery opening up by itself , i tend to fall below that so ive recently stopped killing task. I use the go launcher widget to kill the tasks.
ac16313 said:
i have everything but sprint bloatware starting up, but at boot i get about 160 but after about an hour it drops to usually around 100. i noticed that when i would kill tasks running in background like gallery opening up by itself , i tend to fall below that so ive recently stopped killing task. I use the go launcher widget to kill the tasks.
Click to expand...
Click to collapse
160MB is fine then. Froyo does memory switching so mostly a memory killer isn't needed. I still use one because when I run the browser and close it, it is still eating all my memory down to 40MB, so I kill it.
kennyglass123 said:
160MB is fine then. Froyo does memory switching so mostly a memory killer isn't needed. I still use one because when I run the browser and close it, it is still eating all my memory down to 40MB, so I kill it.
Click to expand...
Click to collapse
hmm i guess 90 isnt all that bad compared to 40
I can't explain it, but I see almost exactly the same thing. Three epics, mine, wife's, mother in law. All the same, all different memory available.
-Sent from my custom ACS Epic.
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.
Hey guys,
I like to have the developer option "max background processes" set to 2. It kind of disables multitasking a bit, but it keeps like 1000mb ram available which keeps my phone nice and fast.
Only problem is, I have to re-enable this everytime I reboot my device, which isnt terrible, but its not as smooth as Id like it to be.
I also do this on my tf201.
Just wondering if theres anyway to force those settings to stay on.
Thanks,
Super
superostrich said:
Hey guys,
I like to have the developer option "max background processes" set to 2. It kind of disables multitasking a bit, but it keeps like 1000mb ram available which keeps my phone nice and fast.
Only problem is, I have to re-enable this everytime I reboot my device, which isnt terrible, but its not as smooth as Id like it to be.
I also do this on my tf201.
Just wondering if theres anyway to force those settings to stay on.
Thanks,
Super
Click to expand...
Click to collapse
Using ram does not slow your phone down, unless it is using cpu cycles and if it is then it is either a bad app or is running still.
Randomacts said:
Using ram does not slow your phone down, unless it is using cpu cycles and if it is then it is either a bad app or is running still.
Click to expand...
Click to collapse
But as with any computing system, if you are taking up all the ram with background processes, your phone is going to run like 's***'
superostrich said:
But as with any computing system, if you are taking up all the ram with background processes, your phone is going to run like 's***'
Click to expand...
Click to collapse
I haven't been able to slow down my AT&T SGS III even when I try I can't use 2gigs of ram.
In unix/linux unused ram is wasted ram. Often stuff will use *if coded properly* extra ram if there is lots of extra to use.
Randomacts said:
I haven't been able to slow down my AT&T SGS III even when I try I can't use 2gigs of ram.
In unix/linux unused ram is wasted ram. Often stuff will use *if coded properly* extra ram if there is lots of extra to use.
Click to expand...
Click to collapse
Ah. I see. I know that its better to have ram in use, than not too. But I was finding that I would have 300-400mb free, and my phone ran like crap. Put on the limited background processes to 2, and it ran a lot smoother.
Do you have any idea to keep that kept on after reboots?
superostrich said:
Ah. I see. I know that its better to have ram in use, than not too. But I was finding that I would have 300-400mb free, and my phone ran like crap. Put on the limited background processes to 2, and it ran a lot smoother.
Do you have any idea to keep that kept on after reboots?
Click to expand...
Click to collapse
Your issue is not your "ram" is the fact you got some ****ty apps probally taking a lot of CPU cycles.
To check what app this is *best time to check for your issue would be when your phone starts to be slow*
Hold the home button and then click task manger. From there go to Applications on the very left *probably the default place it puts you*
You can see the CPU usage on that page..
If anything is above 0% it might be what is casing the issue. If you want you can post a screenshot of that page and we can see if there are any known bad apps there.