Can't see why this is the case (but it obviously is) as long as I have lots of free disk space and not many apps running at the same time. Any logic in this?
I've been experiencing the same issue and wondering the same thing...
Sent from my Samsung Galaxy S GT-I9000 using Tapatalk Pro
There seems to be several things causing this, but the two key issues are:
The moviNAND (the internal flash drive/"SSD") firmware seems to have an issue with fsync() taking extremely long. E.g., it slows down whenever a file is written/updated on the internal storage.
RFS, the file system used by Samsung is buggy as hell and corrupts data after a while.
There are several topics on these issues in the Android Development forum. There are also several "lag fixes" trying their best to overcome these issues. Go check them out
Einride said:
There seems to be several things causing this, but the two key issues are:
RFS, the file system used by Samsung is buggy as hell and corrupts data after a while.
Click to expand...
Click to collapse
We have no idea if that is ACTUALLY true.. Just because fsck picked some things up on 1 phone, doesn't mean it happens everywhere.. Furthermore, it doesn't mean the problems detected affect operations
that has no truth at all about more apps slowing down the phone, my phone is the prove
Before jpk i didn't noticed slowdowns with aprox 100 apps, now i do on jpk =/
Prolly that all pictures/links/info stays in his workmemory?
probably cause some of them run in the system memory or run at startup
KaliKot said:
probably cause some of them run in the system memory or run at startup
Click to expand...
Click to collapse
Bingo!
and that is what most people does not realize
they need to Optimize the phone, most people take it for granted
the phone is not a phone, the phone is a mini computer that fits in your hands
just like your big desktop PC it can go crazy if you don't take care of it
AllGamer said:
Bingo!
and that is what most people does not realize
they need to Optimize the phone, most people take it for granted
the phone is not a phone, the phone is a mini computer that fits in your hands
just like your big desktop PC it can go crazy if you don't take care of it
Click to expand...
Click to collapse
Can you tell me why with the same apps installed on the Nexus it doesn't lag like the SGS?
Can you stop blaming users when is the phone which doesn't work as expected?
Oletros said:
Can you tell me why with the same apps installed on the Nexus it doesn't lag like the SGS?
Can you stop blaming users when is the phone which doesn't work as expected?
Click to expand...
Click to collapse
utter ****e -i have well over 100 apps on my sgs and experience NO lag whatsoever!
bonehooch said:
utter ****e -i have well over 100 apps on my sgs and experience NO lag whatsoever!
Click to expand...
Click to collapse
Utter ****e? Why?
it was mentioned many many times
just install autorunkiller and a good task manager then all the problems will be gone
stock ROM is very fast when you maintain the phone
AllGamer said:
it was mentioned many many times
just install autorunkiller and a good task manager then all the problems will be gone
stock ROM is very fast when you maintain the phone
Click to expand...
Click to collapse
With autokiller the phone is still laggy.
And please, stop thinking I'm stupid or I don't know a **** about smartphones, ROM's changing, firmware or knowing how a phone must run.
AFAIK this topic and its responses are for the OP
I have about 190 Apps installed and do not experience any diferene in overall speed of the phone. But only because i know that a lot of the programms start on boot and stay in background.
I have more than 15 apps turned off with the full version of autorun killer to prevent the auto restart of the apps. Otherwise the phone would definetaly slow down.
It´s really incredible what apps start on the boot!
TMReuffurth said:
I have about 190 Apps installed and do not experience any diferene in overall speed of the phone. But only because i know that a lot of the programms start on boot and stay in background.
I have more than 15 apps turned off with the full version of autorun killer to prevent the auto restart of the apps. Otherwise the phone would definetaly slow down.
It´s really incredible what apps start on the boot!
Click to expand...
Click to collapse
Do you need to be rooted ti use all of the functions in autorun killer? I am not rooted.
Can you compile a breif list of the "biggest culprits" to stop with this utility to gain back the most speed and efficiency? I am a bit nervous that I will stop the wrong items and somehow damage my phone...
Autokiller and task killers are not the solution here! Quick lesson on Android, and why having even A SINGLE BAD APP is going to ruin your whole phone!
Android has something called an 'Intent'. In order to start an app, an intent is made by your launcher or a button you press, and the Android system reads this intent and works out what app it needs to start up.
There is a second type of intent though, called a 'Broadcast Intent'. This is an intent that is sent out to anything that is registered to listen to it. This means that an app can register to listen to all sorts of events, such as battery level changed, application start, or a tons of other things. Even if the application is closed, if it is registered as a listener, Android will start it right back up so it can deal with the intent. If the intent comes every 5 seconds, Android will run this app every 5 seconds even if you have a taskkiller killing the app.
The only real solution is to not install apps which are bad! Finding bad apps is a real mission, too. Hopefully in the future, utilities will be available to let us track down these terrible apps, but till then, you'll have to work it out yourself.
yiannisthegreek said:
Do you need to be rooted ti use all of the functions in autorun killer? I am not rooted.
Can you compile a breif list of the "biggest culprits" to stop with this utility to gain back the most speed and efficiency? I am a bit nervous that I will stop the wrong items and somehow damage my phone...
Click to expand...
Click to collapse
No need for Root to use all features of Autorun Killer. I would disable only the apps you know and which you do not need at startup and running in background, such as (in my case) Paypal, App Center from Androidpit, Daily Briefing, Photoshop Express, Word Press, TweetCaster, etc.
Every of these apps works normal, even when deactivatet on startup.
So unless you do not disable system apps (must be previously set enabled in settings) you are safe.
RyanZA said:
(...)There is a second type of intent though, called a 'Broadcast Intent'. This is an intent that is sent out to anything that is registered to listen to it.(...)
Click to expand...
Click to collapse
Is there any possibility/app to show what is registered for which app?
watching the apps
Samga said:
Is there any possibility/app to show what is registered for which app?
Click to expand...
Click to collapse
There is an app called Autostarts at 0.95$.
It shows what is launched au startup, when you enable/disable wifi etc.
It think it gives insight on how apps seems launching out of nowhere.
I also reccomend Watchdog Task Manager Lite, the free version.
It does not kill anything, but notifies and logs the bad apps that consumes over a certain CPU percentage.
Related
Seems the N1 has memory management issues. Instead of constantly closing apps to free up memory or have some app try to manage things, be nice to just kill the thing on exit. Any app that will auto-kill when an app exits?
Sent from my Nexus One using XDA App
It would be nice to have, say, long press back key to kill the current app.
Big_O said:
Seems the N1 has memory management issues. Instead of constantly closing apps to free up memory or have some app try to manage things, be nice to just kill the thing on exit. Any app that will auto-kill when an app exits?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
You obviously didn't search for this:
http://forum.xda-developers.com/showthread.php?t=678205
You DON'T need to intervene with N1 memory management, since you don't know how it works. You assume wrong. And most bad gossips are created by people wrongly assuming something, thinking they know something while they actually don't.
My N1 runs equally well with 40MB and 250MB free. The only reason I use a task killer is to kill apps that I want to return to their "initial" state for some reason, or to kill apps that I suspect of wrongdoing.
Exactly, the nexus has no memory management issues. It is just your misunderstanding of how Android works. Leave your tasks alone.
If you have one or two particular apps that are bad citizens and should be shutting down in the background but don't... you can use "1Kill" from the market to create a home screen shortcut that kills that specific app when you press it.
Fring used to be a bad citizen - it would lock my wifi on even when I didn't want to be using it, and had no exit feature. So I'd always have to kill it after finishing up with it. Now it does have a proper exit, thankfully.
Jack_R1 said:
My N1 runs equally well with 40MB and 250MB free. The only reason I use a task killer is to kill apps that I want to return to their "initial" state for some reason, or to kill apps that I suspect of wrongdoing.
Click to expand...
Click to collapse
Ditto!
1 app running or 50 apps running they all still run the same.
I find it even funnier how iOS4 users in Apple-land are suddenly freaking out that so many applications appear to be open "in the background" and complaining that they have to spend so much time "killing" apps.
Big_O said:
Seems the N1 has memory management issues. Instead of constantly closing apps to free up memory or have some app try to manage things, be nice to just kill the thing on exit. Any app that will auto-kill when an app exits?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I think you have the memory management issues.
Before anyone gets tarred and feathered, that explains why many users on unrooted stock roms ha e frequent touchscreen lockups, hesitation and freezes. Guess theres a reason why the market has so many task killers. Maybe the devs should read this thread also lol. Instead of flaming, positive feedback is appreciated. I did search, but its a bit time consuming sifting through 5000 posts. Maybe you guys o rooted phones have no lockups, but google shows an azzload of people with similar issues.
Sent from my Nexus One using XDA App
1) You've been given some answers in the thread, if you cared to look.
2) App that loses focus goes to background. That's the way OS is built. If you want apps to be killed on losing focus, get iOS 3 to run on your device. Seriously, what kind of answer would you expect, if you want to turn multitasking OS into non-multitasking?
3) The market has task killers because they can be written for multitasking OS, and because they help dealing with bad apps. Not for any other reason.
4) The OS loads some of your most used tasks when it runs, even if you don't know about it. Just loads in the memory, and allocates no CPU time. If you leave your phone unattended, your free memory goes down by itself. Why? Because free memory is wasted memory. You can check the "EMPTY" processes in Astro, for example.
5) The best task killer is careful selection of your apps. You see hangups? Find out the app that's doing it and remove it, or kill it specifically after running if it's necessary.
6) Task killers are a good source of lockups and freezes too, did you know? I guess you didn't read that thread...
All this meant to say: instead of looking for a way to cripple your OS, learn to select your apps, and don't solve issues that you don't have.
cmstlist said:
I find it even funnier how iOS4 users in Apple-land are suddenly freaking out that so many applications appear to be open "in the background" and complaining that they have to spend so much time "killing" apps.
Click to expand...
Click to collapse
Yeah, I think Apple needs to tweak their multi-tasking still. I've played with my gf's iPhone a bit this week, and it's a little annoying how now you have to explicitly quit every app. For example, with the Settings app if I go to change a preference quickly then return to home Settings app is still in the running apps list. I think little utilities like that should be able to quit themselves automatically.
I know the app isn't wasting memory or CPU down there, but I just don't see why you would want it cluttering up your app switcher forever.
Oh well, it's progress though. At least now you don't have to quit everything else you're doing to listen to Pandora
well android does the same thing. if you go into the settings menu, then hit home button, the settings is still running in the background. of course andoird will kill it later when it needs to.
could be a noob question
every once in a while i will go into my advance task killer and see a bunch of apps running that i didnt manually open. i just checked my phone to see sprint nav, mp3 store, droid locator, internet, ringdroid, etc.. it also takes my phone from 71m free to about 35-40m. ill kill the apps, and they will be open again without me touching the phone. am i stupid, or is there actually a problem?
Okay bc those stock apps are coded to run at startup, and open themselfs for ease-of-access, this is normal. If you want to stop that, add them to autokill, and use a startup manager (market) to remove them from the start up screen.
For the mem issues, try disabling the GPS lovation services, that eats up battery life AND mem, same with internet.
If you really want your phone to fly, don't use a task killer.
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
abcdfv said:
If you really want your phone to fly, don't use a task killer.
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
Click to expand...
Click to collapse
In theory this is true but in reality it couldn't be more misleading. Yes a task killer, especially one that is always running and using up resources itself is probably less than optimal in an Android environment, however they are sometimes necessary because things do not always work as they are supposed to. If you have root it is better to just use AutoKiller as it doesn't just kill programs but helps the OS by allowing you to set the limits for when the OS should start closing things. It also allows you to manually kill anything not working right.
Of course this is just my opinion, but I have tried it both ways on 3 different Android phones and my results were the same on all.
jlem26 said:
however they are sometimes necessary because things do not always work as they are supposed to.
Click to expand...
Click to collapse
There's a section at the bottom that goes over this.
It's really more of an explanation that "Having free RAM will make my phone faster" will not make your phone faster.
I am running auto nooter on my nc (lovin it) but i have noticed that the available memory is slowly leaking. On reboot, i usually have around 300 available and that number slowly but surely decreases until its so low that it reboots automatically.
I have advanced task killer installed and periodically kill all the tasks to make sure nothing is running in the background.
Any idea what might be causing this?
Advanced Task Killer is not helping you. Google has come right out and said Task Killers will do more harm than good on your Android device. Here is a good read:
http://android-developers.blogspot.com/2010/04/multitasking-android-way.html
The fact that you can see an application's process "running" does not mean the application is running or doing anything. It may simply be there because Android needed it at some point, and has decided that it would be best to keep it around in case it needs it again.
...
Once Android determines that it needs to remove a process, it does this brutally, simply force-killing it. The kernel can then immediately reclaim all resources needed by the process, without relying on that application being well written and responsive to a polite request to exit. Allowing the kernel to immediately reclaim application resources makes it a lot easier to avoid serious out of memory situations.
Click to expand...
Click to collapse
czarjohn said:
I am running auto nooter on my nc (lovin it) but i have noticed that the available memory is slowly leaking. On reboot, i usually have around 300 available and that number slowly but surely decreases until its so low that it reboots automatically.
I have advanced task killer installed and periodically kill all the tasks to make sure nothing is running in the background.
Any idea what might be causing this?
Click to expand...
Click to collapse
It will not reboot when it runs out of ram. My suspicion is you're seeing the 'random reboot' problem that happens on the stock B&N ROM. See here for a workaround: http://nookdevs.com/NookColor_Issues
mrapollinax said:
Advanced Task Killer is not helping you. Google has come right out and said Task Killers will do more harm than good on your Android device. Here is a good read:
Click to expand...
Click to collapse
I totally agree with this on 2.2 upwards... Unfortunately 2.1 is a little more lax about memory handling, and can sometimes get quite slow and jumpy and can benefit from a flush. I use System Panel and exclude all of my important tasks and widget, and if I see my NC getting jumpy or such, I'll kill all (which excludes those already excluded apps of course). But auto task killers are always a bad idea.
mrapollinax said:
Advanced Task Killer is not helping you. Google has come right out and said Task Killers will do more harm than good on your Android device. Here is a good read:
http://android-developers.blogspot.com/2010/04/multitasking-android-way.html
Click to expand...
Click to collapse
Thanks for the post, that was a great read and I am uninstalling my task killer now.
Mike
Regarding task killing, I recommend something like Watchdog to monitor apps as opposed to an auto-task killer. Watchdog has a really nice widget for monitoring system resources and in the rare occasion that an app starts misbehaving, it will give you a notification and the option to kill it. Otherwise letting the OS handle things itself is the best option. I've been using computers for a very long time and idea of leaving apps running seems counter-intuitive, but in my experience there is no reason to not trust what Google says about the issue.
czarjohn said:
I am running auto nooter on my nc (lovin it) but i have noticed that the available memory is slowly leaking. On reboot, i usually have around 300 available and that number slowly but surely decreases until its so low that it reboots automatically.
I have advanced task killer installed and periodically kill all the tasks to make sure nothing is running in the background.
Any idea what might be causing this?
Click to expand...
Click to collapse
i am also having these problems but im on honeycomb
i dont have any task killer installed but i installed one last week to check if my memory was leaking or if the rom was just rebooting
Great stuff here. Thanks for all the info. I think it was the random reboot since it did seem to happen most often when i was putting the nc in to standby.
Lots of good stuff here. Gonna miss the little green widget on my home screen, but i guess google knows best...
czarjohn said:
Great stuff here. Thanks for all the info. I think it was the random reboot since it did seem to happen most often when i was putting the nc in to standby.
Lots of good stuff here. Gonna miss the little green widget on my home screen, but i guess google knows best...
Click to expand...
Click to collapse
well i installed honeycomb preview v2 on my eemc from samuallhaff and it seems to remove this problem
i suggest you switch to his rom if you want the memory leaks to stop
luigi90210 said:
well i installed honeycomb preview v2 on my eemc from samuallhaff and it seems to remove this problem
i suggest you switch to his rom if you want the memory leaks to stop
Click to expand...
Click to collapse
Don't confuse "memory leaks" with "weird wifi sleep reboot bug".
im reading that advanced task killer is good and bad, so is it bad to install or does it really work? im running CM7 Stable.
EverythingNook said:
im reading that advanced task killer is good and bad, so is it bad to install or does it really work? im running CM7 Stable.
Click to expand...
Click to collapse
Everything I've read says you don't need it with Android 2.2 and above.
I use it, nice quick and easy way to close things (like emulators that normally won't shut themselves off.)
dsf3g said:
Everything I've read says you don't need it with Android 2.2 and above.
Click to expand...
Click to collapse
me too but my friends have 2.3 and they use it.
I use it if videos start to stutter (ie youtube etc). It seems to help.
It's bad if you set it to Auto-Kill. The reason is because from 2.2 onward, if you kill (not Force Close) and app, it'll just restart itself. That being said, Linux is not like Windows. With Linux, the OS will fill up memory (RAM) with whatever it can, in this case applications, even if you're not using them. HOWEVER, it will only dedicate the CPU to whatever you're actually using, so whatever is in memory and isn't being used won't affect you (aside from poorly-coded apps). You can use ATK to kill an app if it's just one or two, but not everything.
If you set ATK to auto-kill everything or if you hit Kill Everything, you'll have a ton of apps restarting at the same time, slowing down your phone for a while and eating battery.
Product F(RED) said:
It's bad if you set it to Auto-Kill. The reason is because from 2.2 onward, if you kill (not Force Close) and app, it'll just restart itself. That being said, Linux is not like Windows. With Linux, the OS will fill up memory (RAM) with whatever it can, in this case applications, even if you're not using them. HOWEVER, it will only dedicate the CPU to whatever you're actually using, so whatever is in memory and isn't being used won't affect you (aside from poorly-coded apps). You can use ATK to kill an app if it's just one or two, but not everything.
If you set ATK to auto-kill everything or if you hit Kill Everything, you'll have a ton of apps restarting at the same time, slowing down your phone for a while and eating battery.
Click to expand...
Click to collapse
alright ill stay away from it thanks!
That about sums it up. The only time an app should be killed is if a bug causes it to hang or slow down severely. Otherwise, let the Android system handle things itself.
In my experience it's nice to have for when you need to kill off a specific game or resource intensive app that seems to be slowing things down.
Product F(RED) said:
It's bad if you set it to Auto-Kill. The reason is because from 2.2 onward, if you kill (not Force Close) and app, it'll just restart itself. That being said, Linux is not like Windows. With Linux, the OS will fill up memory (RAM) with whatever it can, in this case applications, even if you're not using them. HOWEVER, it will only dedicate the CPU to whatever you're actually using, so whatever is in memory and isn't being used won't affect you (aside from poorly-coded apps). You can use ATK to kill an app if it's just one or two, but not everything.
If you set ATK to auto-kill everything or if you hit Kill Everything, you'll have a ton of apps restarting at the same time, slowing down your phone for a while and eating battery.
Click to expand...
Click to collapse
so would you recommended going into the app itself and picking the apps i want to be closed? or could i also use the widget to close all of them?
I would only recommend going into the app itself, long-pressing on the app you want to kill, and then pressing kill. Closing all of them just forces a large number of apps to restart. I really only use it to kill certain apps that are more difficult to close.
Please tell my which is best software that stops applications to run automatically at startup
tell me the application which works
no one is using any app. to stop unnecessary start up of tasks
try autostarts its very good
Sent from my GT-I9000 using Tapatalk
Ditto on Autostarts. Also, Autokiller Memory Optimzer works really well, it doesn't kill tasks itself, it tweaks the Android function thar does it to work better.
auto killer mem optimizer workd well for me.but now i simply don use any of those batt saving app,mem apps etc i jus kill apps in inbuilt task killer...iam using my phone to the peek cause at the end ill b getting a 2ghz dual core by selling sgs.......cant stick to old things lol........cheeerz
tarunagg said:
Please tell my which is best software that stops applications to run automatically at startup
tell me the application which works
Click to expand...
Click to collapse
... what?
Do any of you even understand how Android works?
so mind sharing ur exp wiv us on how it works???
manosv said:
try autostarts its very good
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
+1 Autostarts. It amazes me what runs on the phone after start-up, after you switch states or update apps. The perfect cure for batt draining nonsense
rocky23 said:
so mind sharing ur exp wiv us on how it works???
Click to expand...
Click to collapse
Google it. Android is Linux based. Its memory management is not the same as Windows. I'd explain further, but you're the 4,753,857,195 person to ask.
I spent 10s and googled it for you. Here's a quick link that explains it in simple terms.
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
Basically having applications in RAM is a GOOD thing. Constantly killing them is likely to WORSEN PERFORMANCE AND BATTERY LIFE.
Shanakin said:
I spent 10s and googled it for you. Here's a quick link that explains it in simple terms.
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
Basically having applications in RAM is a GOOD thing. Constantly killing them is likely to WORSEN PERFORMANCE AND BATTERY LIFE.
Click to expand...
Click to collapse
That's right. On the other hand - permitting almost every app to load at startup isn't the best approach, as you will soon run out of memory - therefore using apps like autostart makes sense imho. But constantly killing everything isn't the right approach either. Android removes "old" apps automatically.
Bottom line:
- just letting those apps load at startup, which you use on regular basis, is fine
- using a "ram tweaker", auto-kill app, etc. is not
Kind regards,
ww
webwude said:
That's right. On the other hand - permitting almost every app to load at startup isn't the best approach, as you will soon run out of memory - therefore using apps like autostart makes sense imho. But constantly killing everything isn't the right approach either. Android removes "old" apps automatically.
Bottom line:
- just letting those apps load at startup, which you use on regular basis, is fine
- using a "ram tweaker", auto-kill app, etc. is not
Kind regards,
ww
Click to expand...
Click to collapse
And when you run out of memory, Android will free memory by automatically killing cached (unused) apps. Therefore, I don't see the point of stopping apps from running at start--unless they're actually doing something in the background and not letting your phone sleep.
RAM tweaks (or memory management), on the other hand, is the only thing I use. I adjust OOM settings to adjust which apps Android closes to free memory, as well as how much free RAM Android should keep open in various situations.
upichie said:
And when you run out of memory, Android will free memory by automatically killing cached (unused) apps. Therefore, I don't see the point of stopping apps from running at start--unless they're actually doing something in the background and not letting your phone sleep.
RAM tweaks (or memory management), on the other hand, is the only thing I use. I adjust OOM settings to adjust which apps Android closes to free memory, as well as how much free RAM Android should keep open in various situations.
Click to expand...
Click to collapse
Well actually I don't see the point that an app, that I hardly use once per month should be loaded everytime I start the phone or change my internet connection. Also more apps at startup increase the time when the phone is available...
But on the other hand, you are certainly right, after a while, only the latest apps are still in background / memory. What I have recognized nevertheless: if you use a lot of apps with push functionality and load on startup, the phone runs out of memory...
Kind regards,
ww