program som är på hela tiden och ligger i bakgrunden

TheNano · 12 apr 2010

Det är OK , börja inte med taskkiller direkt, Android sköter det, är det just efter en ny app som telefonen mår dåligt kan det vara fel på just den så ni kan avinstallera det, det är ingen bra ide att döda processer höger om vänster
fron Cyanogen via twitter

android works the same way though, you should never have to kill apps unless they suck..
Click to expand...

http://bit.ly/d3c7C
Click to expand...

kort från länken ovan

Activity lifecycle

An activity has essentially three states:

It is active or running when it is in the foreground of the screen (at the top of the activity stack for the current task). This is the activity that is the focus for the user's actions.

It is paused if it has lost focus but is still visible to the user. That is, another activity lies on top of it and that activity either is transparent or doesn't cover the full screen, so some of the paused activity can show through. A paused activity is completely alive (it maintains all state and member information and remains attached to the window manager), but can be killed by the system in extreme low memory situations.

It is stopped if it is completely obscured by another activity. It still retains all state and member information. However, it is no longer visible to the user so its window is hidden and it will often be killed by the system when memory is needed elsewhere.

If an activity is paused or stopped, the system can drop it from memory either by asking it to finish (calling its <code>finish()</code> method), or simply killing its process. When it is displayed again to the user, it must be completely restarted and restored to its previous state.
Click to expand...

och lite mer

A service process is one that is running a service that has been started with the <code><code>startService()</code></code> method and that does not fall into either of the two higher categories. Although service processes are not directly tied to anything the user sees, they are generally doing things that the user cares about (such as playing an mp3 in the background or downloading data on the network), so the system keeps them running unless there's not enough memory to retain them along with all foreground and visible processes.

A background process is one holding an activity that's not currently visible to the user (the Activity object's <code><code>onStop()</code></code> method has been called). These processes have no direct impact on the user experience, and can be killed at any time to reclaim memory for a foreground, visible, or service process. Usually there are many background processes running, so they are kept in an LRU (least recently used) list to ensure that the process with the activity that was most recently seen by the user is the last to be killed. If an activity implements its lifecycle methods correctly, and captures its current state, killing its process will not have a deleterious effect on the user experience.

An empty process is one that doesn't hold any active application components. The only reason to keep such a process around is as a cache to improve startup time the next time a component needs to run in it. The system often kills these processes in order to balance overall system resources between process caches and the underlying kernel caches.

Click to expand...

kort sagt , Android sköter detta helt automagiskt

TheNano · 12 apr 2010

det finns en tråd i allmät om appar som inte låter mobilen sova när man släker skärmen, vilket kan vara en räddning för dålig batteritid

Forum

program som är på hela tiden och ligger i bakgrunden

TheNano Senior Droid Medlem

TheNano Senior Droid Medlem

Snabbsökningar

Forum

Medlemmar

program som är på hela tiden och ligger i bakgrunden

TheNano Senior Droid Medlem

TheNano Senior Droid Medlem