Related
I have been using 'Close Everything' app for awhile thinking it does what it suppose to do. Just today I held down the home key and 6 apps are fully opened. Now I need another app that actually does the job of closing apps. Anybody know one?
holding down the home key opens up a window of the last six apps opened and used.
AFAIK, the way Android works, apps don't get closed. If you by some outside means manage to kill an app off, Android will think something's wrong, and resurrect it if it can. The only 100% way to kill an app I know, is to reboot (and then not start it).
/Mats
Advanced task manager by Arron La
They aren't actually running AFAIK
They are the last six apps used, it doesn't matter if they are running or not
Try using task manager for root. I use a combination of several closing apps and this one seems to work well. I'm not sure if its in the market tho. But I found it on one of the threads. Happy searching
Advanced Task Manager will allow you to kill the processes and applications of your choosing. (It is on the market for US, that's where I got it free)
As said, Advanced Task Manager is what you need. It's nice letting you choose apps to never kill so you can just hit the End All button and be lazy
I am having a SGS asia version with latest firmware.
i have rooted it with su access and using process manager to kill those unwanted application (google map, double clock, and others....) running from behind.
but after certain time (range from 1 hour to 2 hours), those unwanted application will load back and take up the memory again. I have to manually killed them again and the remaining RAM is reduced in the process.
Is anyone facing similar problem ?
anyone know how to permanently stop this ? is there any program in the Samsung that keep summoning those application ?
Thank you.
Ya, I've this problem too, but mine is the stock firmware.I've no idea what causes those applications to launch themselves.
yes, a few of my friend also facing this problem. that is why i am thinking is some professional here can help us on this question.
Thanks
If you have rooted your phone, download this app called startup manager from market place, then disable these apps from the start up process. Viola, no more.
Seifer1975 said:
If you have rooted your phone, download this app called startup manager from market place, then disable these apps from the start up process. Viola, no more.
Click to expand...
Click to collapse
Is this startup manager for choosing which applications to auto start during soft reset only though?
You might also want to give "automatic task killer" from the market a go too, first app I would install after flashing roms.
Seifer1975 said:
If you have rooted your phone, download this app called startup manager from market place, then disable these apps from the start up process. Viola, no more.
Click to expand...
Click to collapse
I have installed startup manager application and already disable them at the startup. But they still coming back once a while when the phone is running......
I have successfully stop them from launch at the starting but after a while, it keep coming back. What is more irritating is once i kill them, they launch again 1-2 hours later....
i am thinking , is there any application running underground which keep "calling" them ?
After reading the help section on the system panel I installed, apparently the way android works is by loading up apps that it thinks you might need, so that when you do open them, they're already sitting there ready. system panel shows you a list of apps that are open on your phone and running, open but in the background, and those that on standby. Most task killers only show all these as being open, when they actually all aren't. The maker of the app strongly advises against continually killing all apps, unless any of them have a problem. Anyway, that's just what I read.
Nicolopolus; said:
After reading the help section on the system panel I installed, apparently the way android works is by loading up apps that it thinks you might need, so that when you do open them, they're already sitting there ready. system panel shows you a list of apps that are open on your phone and running, open but in the background, and those that on standby. Most task killers only show all these as being open, when they actually all aren't. The maker of the app strongly advises against continually killing all apps, unless any of them have a problem. Anyway, that's just what I read.
Click to expand...
Click to collapse
I see. Now it does explains everything. Sounds factual to me, if you've read it in the help section of the system panel. Thank you.
Facts are so important in problem solving.
Can you tell us which apps are started every hours like that ??
On my side I would like to know if the following app can be killed :
* Device management
* DRM protected content storage
* SNS
*com.sec.android.app.samsungapps.una
* com.sec.android.providers.downloads
*mobile AP settings
* Mobile Tracker settings
* Log provider
* My upload
* Settings
thanks
So ill go into my system panel and kill all apps. Ill have about 160mb of memory free. Then the launcher obviously restarts and system panel and my widgets all start back up, but what i dint hnderstand is why do thi gs like google voice or the music player start up in the background if i havent even used them? They start up almost instantly....
How can i make sure **** stays off?
Sent from my SGH-T959 using XDA Premium App
Start up manager or similar from the market. Take care though, if you block something that system wants to be launched, it may keep attempting to launch it, leading to high battery consumption
Some app include a service, which they are executed in background. If the service is maually stopped, android can launch it again.
There are many application on the market which stop periodically these app. The point is that if it has a service, there is a reason, and by stopping it, you can obtain a strange comportment.
By example, in the first version of Android, gtalk was used for the authentification on android market, it is very strange but it was like that. The user was not informed of this link which was a kind of transparent. So if you stopped gtalk, you were not able to go on the market.
Do you need a lot of RAM? If yes uninstall the application you don t use, but I advise you to not stop mannually or automatically the application on your phone.
I guess thats how android functions as such. I tried stopping these programs so many times using apps from the market, but it starts again n few minutes. So its like we are wasting our time trying to kill apps.
Autostarts and/or Android Optimizer will stop any unwanted apps from running constantly. Works for me but just make sure you know what you are doing so you don't stop something you need (as described above)..
I hate it when an app runs in the startup specially if the app is not that important. Is there any way of disabling those apps that run in the startup? As well as those apps that runs in the background even if you don't need em to? They eat up RAM and make the NC slow! I wish I can manage them.
Let them be android takes care of itself.
Read this: http://forums.androidcentral.com/general-help-how/102171-apps-always-running.html#post1088042
---
- Sent from my LG Optimus V using Tapatalk
les02jen17 said:
I hate it when an app runs in the startup specially if the app is not that important. Is there any way of disabling those apps that run in the startup? As well as those apps that runs in the background even if you don't need em to? They eat up RAM and make the NC slow! I wish I can manage them.
Click to expand...
Click to collapse
Yes...get an app in the market called Android Optimizer, it is free. In the menu hit the startup manager icon. Disable the app (s) you don't want to run at start up or background.
StarlahRain said:
Yes...get an app in the market called Android Optimizer, it is free. In the menu hit the startup manager icon. Disable the app (s) you don't want to run at start up or background.
Click to expand...
Click to collapse
You sure of that name? I did a search in the market and do not see it.
StarlahRain said:
Yes...get an app in the market called Android Optimizer, it is free. In the menu hit the startup manager icon. Disable the app (s) you don't want to run at start up or background.
Click to expand...
Click to collapse
You do not need an app like this. People use task killers and startup blockers and then complain about how crappy and slow stuff is because THEY ARE NOT ACTUALLY RUNNING IN THE BACKGROUND. They are cached for faster start up next time. They do not take up any battery or CPU power. Android is linex not windows.
--------------------------------------------------
Here is the post i linked to earlier:
I develop Android apps so I though I'd explain why a task killer isn't needed on an Android system.
Activities
Android apps use activites to preform tasks. For example, if you use a file manager to send a picture via email, the file manager calls the send activity within an email app, passes the file name to it and the email app sends the picture.. not the file manager. This will result in seeing the email app as "running" even though the user didn't actually launch that email app.
Smaller apps
Using activites helps developers design smaller apps. A file manager app that contains every bit of code needed to do everything a file manager does would likely be so large that no one would want to install it. Developers know that an android phone more than likely has an email app so there is no need for the developer to include email code in his/her file manager to send a picture when he/she can call an activity in an existing email app to do the job. This results in a smaller file manager app since there is no need to include email code or any other code for an activity that can be done via an app that is already present on the phone. This also alleviates redundant code. When you install an app outside of the android market, also known as sideloading, the file manager app calls the package installer (already present in Android) to install the requested app.
Running apps vs. cached apps
The "Manage Applications" list included in many android devices lists running apps as well as cached apps. Cached apps don't use any CPU or battery, they're cached so they will load faster the next time you need them. Killing cached apps results in those apps requiring more time to load the next time they are launched.
System management
By default, every android application runs in its own Linux process. Android starts the process when any of the application’s code (activities) needs to be executed, and shuts down the process when it’s no longer needed and system resources are required by other applications.
* Android is hard coded to automatically kill a task when more memory is needed.
* Android is hard coded to automatically kill a task when it’s done doing what it needs to do.
* Android is hard coded to automatically kill a task when you haven’t returned to it in a long time.
* Most services (while possibly running in the background) use very little memory when not actively doing something.
* A content provider is only doing something when there is a notification for it to give. Otherwise it uses very little memory.
* Killing a process when it isn’t ready only causes it to have to reload itself and start from scratch when it’s needed again.
* Because a task is likely running in the background for a reason, killing it will only cause it to re-spawn as soon as the activity that was using it looks for it again. And it will just have to start over again.
* Killing certain processes can have undesirable side effects. Not receiving text messages, alarms not going off, and force closes just to name a few.
* The only true way to prevent something from running at all on your phone would be to uninstall the .apk.
* Most applications will exit themselves if you get out of it by hitting “back” until it closes rather than hitting the “home” button. But even with hitting home, Android will eventually kill it once it’s been in the background for a while.
If you see an app running that you didn't launch, it's most likely because an activity within that app was called by another app to perform a task. If you kill the app you didn't launch, the system has to relaunch that app in order to complete its task. This is why some people kill a task and then see it immediately running again. Constantly killing that app creates a situation where the user is battling the system resulting in wasted system resources.
Android is Linux
Android is not a Windows-based OS, it is based on Linux. Many of the apps you think are running aren't actually running, they're cached, this is typical with a Linux operating system and is much more efficient than other systems. Cached apps don't use any CPU or battery, they're cached and will load faster the next time they're needed.
Let the system manage resources.
---
- Sent from my LG Optimus V using Tapatalk
patruns said:
You sure of that name? I did a search in the market and do not see it.
Click to expand...
Click to collapse
I apologize ..it is called Optimize Tool Box...lite version(free)...
koopakid08 said:
You do not need an app like this. People use task killers and startup blockers and then complain about how crappy and slow stuff is because THEY ARE NOT ACTUALLY RUNNING IN THE BACKGROUND. They are cached for faster start up next time. They do not take up any battery or CPU power. Android is linex not windows.
--------------------------------------------------
Here is the post i linked to earlier:
I develop Android apps so I though I'd explain why a task killer isn't needed on an Android system.
Activities
Android apps use activites to preform tasks. For example, if you use a file manager to send a picture via email, the file manager calls the send activity within an email app, passes the file name to it and the email app sends the picture.. not the file manager. This will result in seeing the email app as "running" even though the user didn't actually launch that email app.
Smaller apps
Using activites helps developers design smaller apps. A file manager app that contains every bit of code needed to do everything a file manager does would likely be so large that no one would want to install it. Developers know that an android phone more than likely has an email app so there is no need for the developer to include email code in his/her file manager to send a picture when he/she can call an activity in an existing email app to do the job. This results in a smaller file manager app since there is no need to include email code or any other code for an activity that can be done via an app that is already present on the phone. This also alleviates redundant code. When you install an app outside of the android market, also known as sideloading, the file manager app calls the package installer (already present in Android) to install the requested app.
Running apps vs. cached apps
The "Manage Applications" list included in many android devices lists running apps as well as cached apps. Cached apps don't use any CPU or battery, they're cached so they will load faster the next time you need them. Killing cached apps results in those apps requiring more time to load the next time they are launched.
System management
By default, every android application runs in its own Linux process. Android starts the process when any of the application’s code (activities) needs to be executed, and shuts down the process when it’s no longer needed and system resources are required by other applications.
* Android is hard coded to automatically kill a task when more memory is needed.
* Android is hard coded to automatically kill a task when it’s done doing what it needs to do.
* Android is hard coded to automatically kill a task when you haven’t returned to it in a long time.
* Most services (while possibly running in the background) use very little memory when not actively doing something.
* A content provider is only doing something when there is a notification for it to give. Otherwise it uses very little memory.
* Killing a process when it isn’t ready only causes it to have to reload itself and start from scratch when it’s needed again.
* Because a task is likely running in the background for a reason, killing it will only cause it to re-spawn as soon as the activity that was using it looks for it again. And it will just have to start over again.
* Killing certain processes can have undesirable side effects. Not receiving text messages, alarms not going off, and force closes just to name a few.
* The only true way to prevent something from running at all on your phone would be to uninstall the .apk.
* Most applications will exit themselves if you get out of it by hitting “back” until it closes rather than hitting the “home” button. But even with hitting home, Android will eventually kill it once it’s been in the background for a while.
If you see an app running that you didn't launch, it's most likely because an activity within that app was called by another app to perform a task. If you kill the app you didn't launch, the system has to relaunch that app in order to complete its task. This is why some people kill a task and then see it immediately running again. Constantly killing that app creates a situation where the user is battling the system resulting in wasted system resources.
Android is Linux
Android is not a Windows-based OS, it is based on Linux. Many of the apps you think are running aren't actually running, they're cached, this is typical with a Linux operating system and is much more efficient than other systems. Cached apps don't use any CPU or battery, they're cached and will load faster the next time they're needed.
Let the system manage resources.
---
- Sent from my LG Optimus V using Tapatalk
Click to expand...
Click to collapse
Yes..I have noticed some side effects.alarms and what not. I guess ur right the only real way is to completely uninstall the apk ..would u happen to know why my adw launcher keeps forceclosing each time boot my nook? I am not running any icon packages..so what other source (or app) could be calling on it to run at startup?
StarlahRain said:
Yes..I have noticed some side effects.alarms and what not. I guess ur right the only real way is to completely uninstall the apk ..would u happen to know why my adw launcher keeps forceclosing each time boot my nook? I am not running any icon packages..so what other source (or app) could be calling on it to run at startup?
Click to expand...
Click to collapse
I am not familiar with adw. Is there an option to save it in memory I know that many replacement launchers do so you might want to make sure that is checked.
Also if you are using a task killer, it is probably trying to kill it and that could cause it to force close.
---
- Sent from my LG Optimus V using Tapatalk
StarlahRain said:
Yes..I have noticed some side effects.alarms and what not. I guess ur right the only real way is to completely uninstall the apk ..would u happen to know why my adw launcher keeps forceclosing each time boot my nook? I am not running any icon packages..so what other source (or app) could be calling on it to run at startup?
Click to expand...
Click to collapse
Do you have Titanium Backup installed? You can clear data and uninstall apps with that as well.
auto starts kills those apps... i run it on my NC>.......i dont need dialer /voicemail...etc.....
Just a thought but if you continue to have force close issues with apps, try running fix permissions. This usually ends the issues. I run adw ex and have no problems. Those few times I have had issues, fix permissions has solved the problem. Just sayin.....
Sent from my NookColor using Tapatalk
So after searching google and pretty much everywhere, I STILL haven't been able to find a clear answer on multitasking.
In wp7 I hated the fact that every single time I would open an app, it would restart from the beginning. Yes, I know you could hold the back button and then click on an app to go back to where you were, but I don't like doing that. I'm used to android where I can just click on any app from the home screen and it'll take me right back to where I left off.
A month ago I tried the lumia 900 and took it back after 2 days because of this. In WP8, I heard they brought real multitasking, but I still haven't been able to find a clear answer to my question...if I'm in an app, go back to homescreen, and then click on the app from the homescreen again, will it restart the app (where it looks like you opened it for the first time after a reboot), or will it put me right back where I left off?
Also, is there a good google voice or youtube app yet? I was using govoice but hated the fact that I actually had to open the app to see if I had any new messages.
Thanks.
I believe apps can be coded to fast resume from the home screen. I think the Facebook app does this but I havent tried it. Apps would need to be updated to add this support tho
from what ive read its possible but the current apps that are out have to be updated to add that feature
It depends on the app.
There is really no way around it.
The Android multitasking is unnatural. In windows/linux/whatever, when you press the icon of an application, it usually opens a new window.
WP8 has a feature Fast App resume, the app needs to be updated to make this feature work, you can read about it here
http://mindre.net/Article/Windows_Phone_8_Fast_app_resume
There is no true multitasking in WP8 except for Navigational apps AFAIK.
Well then, no wp8 for me. Thanks guys.
DirectX games also do not stop updating in the background.
Never seen the fuss around multitasking. The multitasking model works as far as I can see on most devices. You background a music player and it carries on playing.
iOS's system used to annoy, double clicking, touch and hold followed by repeatedly closing apps.
On Windows Mobile people used to complain about the close button not closing the application (it would run in the background). Now when you do close an application people are moaning it doesn't run in the background.
deadwrong03 said:
from what ive read its possible but the current apps that are out have to be updated to add that feature
Click to expand...
Click to collapse
this confused me... why does the app need any update, when its the OS that does all the fore/back ground stuff? did I misunderstand you?
I'll agree with the op , Microsoft needs to clarify what its new OS does in the commercials instead of a dance routine.
ohgood said:
this confused me... why does the app need any update, when its the OS that does all the fore/back ground stuff? did I misunderstand you?
I'll agree with the op , Microsoft needs to clarify what its new OS does in the commercials instead of a dance routine.
Click to expand...
Click to collapse
Simple, a phone is a battery operated device which needs a more careful considered approach to multitasking.
When you background a game that is running what should happen? (a) it carries on running, (b) it pauses or (c) it saves its state and closes down.
You have to ask yourself these sort of questions when building the application for a phone, the OS can't make that decision since it doesn't know what is the correct answer. So profiles are added to the OS and the developer of the OS selects one of these profiles.
So a downloading tool would continue to download, a music player would play music in the background, a game would pause or save state and an IM client would either carry on being connected or switch to push notification.
ohgood said:
this confused me... why does the app need any update, when its the OS that does all the fore/back ground stuff? did I misunderstand you?
I'll agree with the op , Microsoft needs to clarify what its new OS does in the commercials instead of a dance routine.
Click to expand...
Click to collapse
One of the reason you are even considering the WP vs Android fight is due to multitasking.
Android has "real multitasking" and that makes it unstable, prone to random crashes, and generally not as smooth as WP.
On top of that, the WP environment does not allow for applications to do things behind your back. Your privacy is more secure with WP than it is with Android, and i like that.
mcosmin222 said:
Android has "real multitasking" and that makes it unstable, prone to random crashes, and generally not as smooth as WP.
Click to expand...
Click to collapse
Do people still actually believe this?
Sent from my iPhone using Tapatalk
vetvito said:
Do people still actually believe this?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Those who have a clue...yes.
The correct answer is "both"
Regarding the question about resume vs relaunch, to the best of my recollection from reading the WP8 SDK notes 12 days ago, the answer is as follows:
1. Existing apps written for WP7 will continue to work as-is. That is, launching the app tosses away the app's back stack and gives the user a "fresh" copy of the app.
2. Apps written for WP8 can indicate that they support resume on relaunch in their "manifest" file. When this is NOT indicated, the WP8 app behaves as the WP7 apps do: launching an app launches a fresh copy; backing into an app reconnects you to that app's back stack/history.
3. When a WP8 app indicates that it can handle resume on relaunch, the already running app is brought to the front, reconnected to its back stack, and has the main page of the app pushed on to the back stack. It is up to the developer of the app to decide which of three things happen at this point:
3a. Blow away the previous back stack (to simulate WP7 behavior);
3b. Pop off the "main page" item that the OS just pushed onto the back stack to effectively return the user to the last viewed page in the app;
3c. Neither, leaving a fresh copy of the main page in screen and the old back stack still present. This is a bad idea because it looks like the user restarted, but the old context is still there.
I'm at an airport now and don't have access to my dev box or SDK docs. Someone with such access can likley find the information in the WP8 SDK documentation (although not on the "What's New" page).
thanks manicotti.. that's the best explanation yet.
that other guy that above that wanted to argue about stuff... I just don't know what to say.
Look here...
http://mindre.net/Article/Windows_Phone_8_Fast_app_resume
This might be the answer to you're question
Sent from my HTC Titan on Deepshining 2.0 Rom using Board Express
gilesjuk said:
On Windows Mobile people used to complain about the close button not closing the application (it would run in the background). Now when you do close an application people are moaning it doesn't run in the background.
Click to expand...
Click to collapse
So true, so true.... I can still hear the HD2 user pool complaining...those were the golden days...
Side note: the "fast app resume" when launched from Start was actually possible on WP7, but its use wasn't permitted in the Marketplace (it's an option in one of the manifest files). Apparently that restriction is now lifted for WP8, but Marketplace apps that want to use it will need to be updated (very simple change, though) to set that option.