Go Back   Android Forums > Android Phones > Acer Liquid E

Get excited for the Samsung Galaxy S5! Find everything you need and discuss it in our Galaxy S5 Forum!

test: Reply
 
LinkBack Thread Tools
Old October 11th, 2010, 11:28 AM   #1 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Oct 2010
Posts: 21
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 1 Time in 1 Post
Default closing applications

im just wondering how to close an application? do u need a task killer or just keep pressing back until u see the home screen thanks

G0d___Like16 is offline  
Reply With Quote
sponsored links
Old October 12th, 2010, 01:00 PM   #2 (permalink)
Senior Member
 
HustlinDaily's Avatar
 
Join Date: Apr 2010
Location: Sugar Land, TX
Posts: 1,141
 
Device(s): Motorola Atrix 4G (CM10) & Acer Liquid A1 (LiquidNext 1.9.2 (CM7 ROM))
Carrier: Not Provided

Thanks: 68
Thanked 105 Times in 90 Posts
acurrimbhoy@gmail.com
Default

To completely stop it, you need a task killer.

Personally, I don't use a task killer. Just press the home button to exit out of an application and let it run in the background until the Android system kills it.
HustlinDaily is offline  
Reply With Quote
Old October 12th, 2010, 07:48 PM   #3 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Oct 2010
Posts: 21
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 1 Time in 1 Post
Default

is it better if i use a task killer ? or should i just leave it alone
G0d___Like16 is offline  
Reply With Quote
Old October 13th, 2010, 08:33 AM   #4 (permalink)
Senior Member
 
HustlinDaily's Avatar
 
Join Date: Apr 2010
Location: Sugar Land, TX
Posts: 1,141
 
Device(s): Motorola Atrix 4G (CM10) & Acer Liquid A1 (LiquidNext 1.9.2 (CM7 ROM))
Carrier: Not Provided

Thanks: 68
Thanked 105 Times in 90 Posts
acurrimbhoy@gmail.com
Default

Here is an interesting read on why you shouldn't use a task killer- Droid Den - Android Guide: Should I Use a Task Killer - Droid Den

It is the main reason I don't use one anymore and since I stopped using one, discovered better battery life.
HustlinDaily is offline  
Reply With Quote
Old June 26th, 2011, 03:49 AM   #5 (permalink)
Senior Member
 
ardchoille's Avatar
 
Join Date: Mar 2011
Location: Seattle
Gender: Male
Posts: 3,684
 
Device(s):
Carrier: Not Provided

Thanks: 1,957
Thanked 1,959 Times in 856 Posts
Default

Use the back button. You don't want to be using a task killer, here's why:

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.
ardchoille is offline  
Reply With Quote
Reply

Acer Liquid E
Current Rating:
Rate this Phone:

The Acer Liquid E is practically the same as the Acer A1 the only difference is that it now packs Android 2.1! Bringing additional features to play with too! This beast still packs a Qualcomm Snapdragon processor and a wide 3.5 inch WVGA Capac... Read More



Go Back   Android Forums > Android Phones > Acer Liquid E
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 12:33 AM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.