Forum Gamers Lounge

[agentc13]

Noting a phone has like 200 MB of ram and this app takes up kike 111 MB no wonder my phone was so slow

Android doesn't use ram... Well not that much anyways. That's probably not why it was slow. Maybe it was taking up cpu speed though.

Marc is right, you don't need much free RAM for android. It is quite different than Windows.

 

[blade00000009]

The phandroid app on my phone

 

[blade00000009]

Well I had 24 MD of ram left so that is very bad because some apps wont work

 

[agentc13]

Android use ram but android kills off apps when there are like 20 running so I only have two apps on the market this and advanced, and killer because my phone has like 256 MB sorry for grammar on my phone now

Wrong. It will close out apps when it needs the space to run more. It doesn't go by the number of apps. Get rid of that task killer it doesn't help anything.

 

[blade00000009]

But I had 24 MB left Ans it was really slow a 400 CPU is better than that and even a 100 CPU well my school has a 64 CPU but.it is slow running windows 7 but they lock everything down so you get the windows 95 look

 

[agentc13]

It being slow is probably your processor. I will link you a post here in a sec as to how the OS handles the RAM. It ISN'T like Windows.

 

[agentc13]

It's best to let the system manage things, 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.

I hope this post will shed some light on task killers.

There, read that. Trust me the task killer isn't helping anything, quite the opposite. I even Bolded some stuff for you.

 

[blade00000009]

Ohh yeah said about windows but my phone has a 800 MHz CPU And 600 MHz CPU is fast a little bit but 800 MHz is average but going too get the LG connect for metro in like 2 years matters what price and that has a 1.2 ghz CPU

 

[Metroid Prime]

Plus, task killer aren't good for the phone either. They run constantly trying to kill tasks that keep re-opening and it uses more juice trying to keep those apps closed then it does without it. Android is smart and will take care of itself.

 

[marc12868]

Ohh yeah said about windows but my phone has a 800 MHz CPU And 600 MHz CPU is fast a little bit but 800 MHz is average but going too get the LG connect for metro in like 2 years matters what price and that has a 1.2 ghz CPU

In 2 years a lot can change... By then the normal will be like 16 core phones lol

 

[blade00000009]

But I use the task killer once in a while but I make it kill It self

 

[Yeahha]

OMG I am so tempted to steal this one

Spoiler

[avoids task killer discussion and thinks of both phandroid apps installed on his gnex]

 

[blade00000009]

we are getting a quad core phone a dual core is fast for me and the phone is dual core

 

[Metroid Prime]

Just get rid of the task killer man. There's no need for it buddy.

 

[blade00000009]

OK you swicth your avatar to much yeahha

 

[BabyBlues]

OMG I am so tempted to steal this one

Spoiler

[avoids task killer discussion and thinks of both phandroid apps installed on his gnex]

I like that one

 

[blade00000009]

OK ok

 

[agentc13]

I might actually get rid of the Dalek for this

But I think I saw a couple similar dalek ones which would fit my strategy better.

 

[marc12868]

we are getting a quad core phone a dual core is fast for me and the phone is dual core

Yea. I have a dual core and it's plenty fast. But at the rate we are moving in 2 years phones are gonna be more powerful than computers... they already have a ubuntu desktop os more mobile phones now...

 

[blade00000009]

Computers are never going too be faster than phones ahem i7 in a few years i99

 

[marc12868]

Computers are never going too be faster than phones ahem i7 in a few years i99

Probably not Intel will just move to the 3rd generation and start over at the i3, i5, and i7... Lol. But Computers probably will always be faster but still phones are getting there... If only they had swappable ram and cpus...

 

[blade00000009]

Yea

 

[Metroid Prime]

There neck and neck.

 

[blade00000009]

What

 

[Metroid Prime]

There kinda on even ground...Maybe not.