• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

YES, you need a task killer app for the Eris. PERIOD.

Oh fun a Developer!!

BTW I am a Senior Linux Systems Engineer..

I love getting into arguments with your types.. lol..

The task killer is like a task manager..

Like on one of my Linux servers, if it is swapping like crazy

you can do a top or a ps -ef find the app that is using up resources and kill it freeing up resources so the system stops swapping..
 
This is contrary to how electronic devices work. I am an electronics design engineer and an Android developer.

More items in memory do not take more energy. The memory still needs to be powered. More items in virtual memory do not take more energy. The virtual memory (disk) still needs to be powered.

There is not a selective shutoff switch on either device. It is either on or it is off.

If someone can define to me how a task killer works, I might believe them. What I do know is that Android and the underlying Linux OS manage all of this pretty efficiently.

please tell me what apps you've developed so I can delete them off my phone
 
Typical developer, write bad code.. takes down my servers and points the finger at me telling me I dont know how to work a server..

At this point I shut off your application in production, and Senior management forces us all into a meeting and makes the programmer fix it..
 
No they are not. They give the appearance of it but they are not. Learn about how an OS operates before you make judgements about it. If you actually believe they are multi-tasking, you have no idea what that means.

So if they aren't multi-tasking, that would mean they are multithreading?
 
The Eris and it's underlying OS are not multitasking. Neither is any version of Windows, mobile or not. Learn how something works before you start to make judgements on how it works.

Wow, you are so very wrong I joined just to respond. Please tell us exactly what YOU think multitasking is? You can see what I believe it is by going to Wikipedia or any of the other 1000s of sites with information on the matter.

Yeah - I develop software too. Total B2B stuff. Some of you have no doubt run it too.
 
Multi threading is different.. thats when you have an app with different threads doing different tasks..

Multitasking is when you run many of these multi threaded applications at one time..

And when you have too many running at once and use up your RAM, you will start memory swapping and this is what kills your performance..
 
This is also the same "dev" that claimed that switching Hboots from the OTA to the leak is a simple matter. He never responded when asked about passing signature verifications or bypassing them.
 
Alright, now I have to post the obligatory reminder to stay on the actual topic and not post personal attacks towards your fellow members.

In other words, just play nice.
 
Technically speaking, you really dont need one because in the phones settings you can kill processes anyways.. the task killer just improves on this thats all..
 
Yes as apps are open but not used they will slowly swap memory with needed apps that are open. Look up why you don't need a task killer it will explain everything

Sent from my Eris using Tapatalk
Yes, and this swapping is what causes LAG. I dont think you even read this thread....

Technically speaking, you really dont need one because in the phones settings you can kill processes anyways.. the task killer just improves on this thats all..
Yes 2.1 has a very crude task killer app built in but its not something you would want to use to keep your memory free to avoid memory re-allocations and as a result avoid lag.

here is my proof and source, i REALLY want to be disproved:

from my research, programs are going to run in virtual memory...if u have apps like i use (keepscreen, google maps, pandora) runnning in virtual memory...they are still running. using less (or no) memory...but still using battery. the OS has to maintain the state they are in...if the state is using gps or streaming...thats battery power being wasted.

"Linux uses a Least Recently Used (LRU) page aging technique to fairly choose pages which might be removed from the system. "

so it does kill processes by default...
however!
"When physical memory becomes scarce the Linux memory management subsystem must attempt to free physical pages. This task falls to the kernel swap daemon (kswapd).
The kernel swap daemon is a special type of process, a kernel thread. Kernel threads are processes that have no virtual memory, instead they run in kernel mode in the physical address space. The kernel swap daemon is slightly misnamed in that it does more than merely swap pages out to the system's swap files. Its role is make sure that there are enough free pages in the system to keep the memory management system operating efficiently. "

therefore...it can get to the point of OPERATING IN-EFFICIENTLY.
which would lead to sluggishness...even in the desktop OS.
and much like windows (mobile) linux does use virtual memory...having ALOT in common.
android is based off of linux kernel.
source.
http://www.tldp.org/LDP/tlk/mm/memory.html
This is all true in the Eris as well and you can clearly see the daemon process running on the Eris simply by using the alogcat app.

I am new to the Android OS. Been using it since Jan. I currently have a G1 and my friend has an Eris. I use TaskPanel on my G1 when it starts to lag. The lagging I get on the G1 is on incoming calls the display can take 5-10 seconds to show who is calling and with scrolling through menus and such.
I started messing around for the first time on her Eris yesterday. I noticed that it lagged a lot when the keypad pops up and flipping through menus and such. I checked her download history on the Market and she only had 2 apps installed. She doesn't really dwell to much into the market, just got the phone cause it looked cool. I asked if it is always slow like this and she says yes and that's why she hates the phone. I installed TaskPanel and ran it to shutdown all the apps running in the background. I gave the phone to her and she was impressed on how much it improved the Eris. She went from having 28mb free memory to 70mb.
Its weird to me that there is no correct way to shut down apps on the Android OS. I recently switched from RIM OS and each app had an exit or quit option in the menu to fully shut it down. From reading this thread I realize that its not do to the Android OS but the developers fault for not putting in the code to shut down an app you won't be using for a while and leaving it running in the background.
I definitely like the Android OS. Very different from RIM's OS. Still think it needs more tweaks to it, but I see lots of forward progress happening.
This is the perfect example of what I have been stating all along. I think most people not using task killer apps are just dealing with the lag when they dont have to.
 
This is also the same "dev" that claimed that switching Hboots from the OTA to the leak is a simple matter. He never responded when asked about passing signature verifications or bypassing them.
I switch hboots all the time for my own purposes. Give me the binaries for the hboot you want on your phone and I will give you a way to install it.
 
Multi threading is different.. thats when you have an app with different threads doing different tasks..

Multitasking is when you run many of these multi threaded applications at one time..

And when you have too many running at once and use up your RAM, you will start memory swapping and this is what kills your performance..
That makes no sense at all. Build a multi-tasking system sometime and then you will know how they work.
 
Multi threading is different.. thats when you have an app with different threads doing different tasks..

Multitasking is when you run many of these multi threaded applications at one time..

And when you have too many running at once and use up your RAM, you will start memory swapping and this is what kills your performance..

Almost right. The commonly accepted definition of "multitasking" is a systems that "appears to be" running more than one program (or app) at the same time. They don't need to both be multi-threaded and you don't need to have many of them. Two single-threaded apps running at the same time is multitasking.

I say "appears to be" because under this definition, even a single-core system can be "multitasking" simply by switching which app is running often enough that no human can tell that only one of them is running at any moment.

That makes no sense at all. Build a multi-tasking system sometime and then you will know how they work.

I'm a lead software engineer who's been writing software for over 35 years. I've written everything from tiny embedded systems to massively multi-threaded multi-tasking multi-user networked systems. To be blunt, if I don't know what multitasking is, then nobody knows... :cool:

Android, by virtue of being built on Linux (which is already multitasking) is multitasking. Debating this is pointless. If you don't think it is multitasking, I think you need to define your terms more carefully.

I suspect that you're using the literal multi-cores-multi-processes definition rather than the more commonly used anything-that-looks-the-same-to-a-human definition. If this is the case, I'm sorry to break this to you, but you're fighting a loosing battle. Nobody cares that there is a low-level technical difference because it doesn't matter. They both look the same to the user...

If you're using some other definition, then please spell it out and explain the differences rather than being pointlessly condescending.
 
Back
Top Bottom