Database Users

Alarm woes with CM 5.0

Since no one replied to this message in the official CM 5.0 thread. I have decided to create a new thread and hope to find a solution to this problem.
My alarm clock would stop working randomly ever since I flashed to CM 5.0, from Beta 4 to 5..2, the problem persists. If i set an alarm that is about one hour from now, it would go off. But the real alarm I need which is supposed to go off at 8 am in the morning never goes off. Anyone had similar problems? I read Cyanogen's warning about the alarm clock problem. But seems he's just trying to remind you to reset your alarm after flashing to CM. Unluckily, I've reset my alarm numerous times and it never goes off in the morning.
Anyone can give me a hand? Thanks in advance! Overall, CM is a great ROM which gives me the option to use open vpn, which is vital for me since I'm living in China behind the GFW.

Are you by chance using any taskillers?

I do use a task-killer program. But I always keep the clock app on while i'm sleeping to try to make sure the alarm goes off on time. But it never does in the morning.

Don't use task killers on the N1, there really is no need.

cyanogen said:
Don't use task killers on the N1, there really is no need.
Click to expand...
Click to collapse
I wouldn't say that's accurate... The phone does slow down noticeably when you have 20-30+ things open
Sometimes a lot of them are running as well (using TasKiller, a lot of Yellow, including Camera, Gmail etc even when not in use and no emails being downloaded). This probably affects battery life as well.

Paul22000 said:
I wouldn't say that's accurate... The phone does slow down noticeably when you have 20-30+ things open
Sometimes a lot of them are running as well (using TasKiller, a lot of Yellow, including Camera, Gmail etc even when not in use and no emails being downloaded). This probably affects battery life as well.
Click to expand...
Click to collapse
Do you have any evidence to back this up? Yes this was a problem on older devices because many things would be fighting over the tiny amount of RAM.
You'll see lots of processes running but that's just the way Android works. Since it doesn't really benefit from simple caching like a normal linux system would, it just keeps everything running and kills unused stuff when memory is low. Most of the things you see running are either paused and using no CPU, or are services that would be periodically launched anyway.
http://developer.android.com/guide/topics/fundamentals.html#lcycles
Keeping these processes alive should actually be saving you battery rather than using it. It's more expensive to launch and restore the state of an application or service after being killed than it is to simply resume one that's been paused.

cyanogen said:
Do you have any evidence to back this up? Yes this was a problem on older devices because many things would be fighting over the tiny amount of RAM.
You'll see lots of processes running but that's just the way Android works. Since it doesn't really benefit from simple caching like a normal linux system would, it just keeps everything running and kills unused stuff when memory is low. Most of the things you see running are either paused and using no CPU, or are services that would be periodically launched anyway.
http://developer.android.com/guide/topics/fundamentals.html#lcycles
Click to expand...
Click to collapse
Yes. The phone gets slow when TasKiller shows 30 things in it. I click close all, and it's faster. Do you know my personal experiences more than I do?

Paul22000 said:
Yes. The phone gets slow when TasKiller shows 30 things in it. I click close all, and it's faster. Do you know my personal experiences more than I do?
Click to expand...
Click to collapse
I think there is likely one or two specific misbehaving applications that are giving you trouble, rather than the way the system works as a whole, thats all.

I think what Cyanogen is saying is that android does not handle running processes the way other os's do They have a lifecycle that is non-obvious to someone just looking at a process list. If you insist on killing tasks outside of the activity/service lifecycle they you _will_ get service failures (like the alarm clock) its up to you what you value more.

I have not installed any sort of task manager (outside what's in astro but I don't use it) and never see any noticeable slow down.

Anyway - back on topic.
Yes I have the same issue, never had it before.
Since flashine 5.0.2 my alarm doesn't work in the morning.

The linux kernel keeps a buffer cache of recently used files in RAM. So whenever an application wants to access something on the flash, instead of going to the flash file system, it can just get it from the file buffer cache in RAM, a significant speed increase.
If the RAM is currently being taken up by unused android apps, then that leaves less room for the buffer cache, so in theory, by killing off unused android apps more quickly, that will allow the linux kernel to allocate more space for the buffer cache and thus speeding up the system.
Am I way off here?
Dave
cyanogen said:
Do you have any evidence to back this up? Yes this was a problem on older devices because many things would be fighting over the tiny amount of RAM.
You'll see lots of processes running but that's just the way Android works. Since it doesn't really benefit from simple caching like a normal linux system would, it just keeps everything running and kills unused stuff when memory is low. Most of the things you see running are either paused and using no CPU, or are services that would be periodically launched anyway.
http://developer.android.com/guide/topics/fundamentals.html#lcycles
Keeping these processes alive should actually be saving you battery rather than using it. It's more expensive to launch and restore the state of an application or service after being killed than it is to simply resume one that's been paused.
Click to expand...
Click to collapse

I would have to agree with Cyanogen on this one. When I first got my N1, I looked towards task killers to help alleviate slowdown, but in the end, I think it's just the placebo effect in a way; you did something to try to solve the problem, and so therefore you perceive a difference.
In other words, task killers aren't needed on this beast of a phone. As for battery life (if that's an issue), look into SetCpu.

Thanks for the reply Cyanogen. I think not using task-killer, or at least not killing the clock app got my alarm working this morning. But I use task-killer not for the purpose of saving ram, but for using less data. Some programs such as facebook or a twitter client would try to connect to the internet every once in a while. I'm on a low data limit plan in China. So I don't want those programs to eat up all my data. When I'm on wifi at home, I don't worry about that. Thanks again.

Same problem. Don't use taskkillers, flashed last CM last night and didn't wake up on time this morning - alarm didn't work, thought I checked that clock icon was on place on notification bar

amwayorlando said:
But I use task-killer not for the purpose of saving ram, but for using less data. Some programs such as facebook or a twitter client would try to connect to the internet every once in a while. I'm on a low data limit plan in China. So I don't want those programs to eat up all my data.
Click to expand...
Click to collapse
Have you thought about using something like APNDroid or Toggle Data, to just switch off the cell data when you don't want to use it?

Or, Modify the behavior of the applications you don't want using data?
I have my facebook and twitter for example set to manual update only (for battery saving purposes) because there's nothing there that is critical important info, and I don't need to be notified.
Nice thread though, I'm pretty sure I try to keep people informed that task-killers aren't needed and cause issues, everywhere where it comes up. I find humor that people will still argue, even with a developer, this fact. I've had 150+ hours uptime with no slowdown (and 30 apps running) on the stock rom (without highmem support).

bofslime said:
Or, Modify the behavior of the applications you don't want using data?
I have my facebook and twitter for example set to manual update only (for battery saving purposes) because there's nothing there that is critical important info, and I don't need to be notified.
Nice thread though, I'm pretty sure I try to keep people informed that task-killers aren't needed and cause issues, everywhere where it comes up. I find humor that people will still argue, even with a developer, this fact. I've had 150+ hours uptime with no slowdown (and 30 apps running) on the stock rom (without highmem support).
Click to expand...
Click to collapse
Then please inform us of a thread that can verify what you all are saying. Not in an argumentative tone, my linpack score drastically improves after 16 hours of uptime, and a task-killer.
Rom:CM 5.0.2 -OC Kernel

wesbalmer said:
Then please inform us of a thread that can verify what you all are saying. Not in an argumentative tone, my linpack score drastically improves after 16 hours of uptime, and a task-killer.
Rom:CM 5.0.2 -OC Kernel
Click to expand...
Click to collapse
This has basically been discussed into the ground. In my eye's, its a fight vs what I like to call "Windows XP mentality", and that there was benefit on phones like the G1. With the copious amounts of memory on the N1 and droid, they cause way more harm, and immeasurable good (if any).
Summary thread: http://forum.xda-developers.com/showthread.php?t=627836
I've linked to quotes from others.
Threads/posts of interest: http://forum.xda-developers.com/showthread.php?p=5494890#post5494890
And: http://forum.xda-developers.com/showthread.php?p=5298630#post5298630

Well, this discussion is very interesting, but lets return to our problem with non-working alarm.

the lag vs apps

Now when installed a lot of apps including juicedefender and advanced task killer (set to aggressive when screen off with lots of exclusions) the lag has become more of an issue.
Now tell me whats the logic behind having installed a lot of apps and a lag? Running several apps multitasked will offcource produce performance-dips but just having them installed?
What exactly is "aggressive" on the task killer anyway? Some people say its just bad to kill tasks.
I have the idea that its the widgets that causes trouble, since they actually needs to run in the background all the time. I noticed today that the fancy-widget got stuck on upboot for like 60 seconds, that caused the 4 buttons below to not load properly. Alto the rather useless "daily brefing" seems to slow down.
I dont want to root and hack with sd-hacks now when froyo is confirmed to be released officially soon.
Do you have experice with sertain apps/widgets causing lag. If so, it would be great to make a list of "bad" apps.
PS, I tested the 30-day navigon today in car and it worked with no problems at all. Fix in 2 seconds and right on track.

robnil said:
Now when installed a lot of apps including juicedefender and advanced task killer (set to aggressive when screen off with lots of exclusions) the lag has become more of an issue.
Now tell me whats the logic behind having installed a lot of apps and a lag? Running several apps multitasked will offcource produce performance-dips but just having them installed?
What exactly is "aggressive" on the task killer anyway? Some people say its just bad to kill tasks.
I have the idea that its the widgets that causes trouble, since they actually needs to run in the background all the time. I noticed today that the fancy-widget got stuck on upboot for like 60 seconds, that caused the 4 buttons below to not load properly. Alto the rather useless "daily brefing" seems to slow down.
I dont want to root and hack with sd-hacks now when froyo is confirmed to be released officially soon.
Do you have experice with sertain apps/widgets causing lag. If so, it would be great to make a list of "bad" apps.
PS, I tested the 30-day navigon today in car and it worked with no problems at all. Fix in 2 seconds and right on track.
Click to expand...
Click to collapse
I haven't used it in a while, but "spare parts" in the marketplace tells you which apps are consuming your processor IIRC. This will obviously give you a temporary hit to your ability to load and run processes but will let you know more details about your phone that you don't already have and the battery use section of settings obviously only talks about what is using your battery but that isn't going to tell you the whole picture.
I am also someone who says you shouldn't use ATK, at least the way you do, but I have it installed and use it a bit differently. What I try to do is kill all tasks after I've used the marketplace or before I do anything intensive (gaming, GPS tracking) and I kill all apps including ATK. ATK will consume processor, battery and will free up memory which then Android uses to open more tasks you don't need (using processor and battery in the process -> repeat cycle). If you need to free up memory 1-5 times a day I think my way will save maybe 15-30% of your battery over a 24 hour period while costing you less than a minute of hassle (too much for some, sure). Again, I only kill after marketplace (because everything opens to check for updates, AFAIK) and before something that will use heavy memory and processor.

robnil said:
Now when installed a lot of apps including juicedefender and advanced task killer (set to aggressive when screen off with lots of exclusions) the lag has become more of an issue.
Now tell me whats the logic behind having installed a lot of apps and a lag? Running several apps multitasked will offcource produce performance-dips but just having them installed?
What exactly is "aggressive" on the task killer anyway? Some people say its just bad to kill tasks.
I have the idea that its the widgets that causes trouble, since they actually needs to run in the background all the time. I noticed today that the fancy-widget got stuck on upboot for like 60 seconds, that caused the 4 buttons below to not load properly. Alto the rather useless "daily brefing" seems to slow down.
I dont want to root and hack with sd-hacks now when froyo is confirmed to be released officially soon.
Do you have experice with sertain apps/widgets causing lag. If so, it would be great to make a list of "bad" apps.
PS, I tested the 30-day navigon today in car and it worked with no problems at all. Fix in 2 seconds and right on track.
Click to expand...
Click to collapse
Forgot the first part of your question, forgive me. I believe, the reason for more apps causing more lag is at least 2 fold. There are more apps that can be opened when you have free memory (in the vicious cycle I described above). There is also something that might be a bit unique to our phone, and I've only recently read this, it's a bit of speculation so I'm not trying to pass it off as fact but I think it's likely to be knowledgeable on the issue, even if not completely correct. Samsung's internal storage method is an SD card, that allows extra apps to be written to the internal storage but comes with a trade off of lag due to a potential combination of:
slow random-access
bad partition
I think I'm missing an important reason, I'll try to look and edit.

When I initially got my SGS I loaded it with a heap of apps and suddenly noticed the lag and quick battery drain. Problem was I couldn't track down the culprit.
I recently reset my device and was a bit more organized with what I installed. One of the things I started doing was checking what services were being used in the process which you can find under the manage apps part of the system.
So while you can load apps and they may/may not be killed by android or a task killer, the services will always be running - taking up memory, sometimes cpu, network. Things like weather checking, news checking, even email sync are some examples. These services plus any apps you run are I think what starts the lag. You need to be aware of which apps are also run as services.
Yes, there are some bad apps (last Facebook version was found to be a heavy drain) but I think they tend to add up with all the other services running.
As for 'Aggressive' depends on the app killer but my understanding (with the one I use), is that there is a memory limit before the app is killed. Once the limit is reached on aggressive, it doesn't take much before memory is cleared.
One thing to install is SeePU as this gives an indication of CPU, memory and network on the top menu bar. This also helps when the system lags (usually CPU is high and memory is low) and helps to know when to clean (or what threshold to set).
Hope this helps.

This may help your battery life.

Today I had been experimenting with my battery life again and stumbled across this.
If you download advance task manager from the market. *NOTE* It is a paid application or *NOTE* This is illegal but you can download an .apk but again it is illegal and I am not encouraging you do it. *NOTE* You can purchase it and return it within 24 hours with your money back.
Step 1- Get advance task manager.
Step 2- Go into your home system and go into your default home or your home system.
Step 3- Now choose a screen in the home. Eg: 1,2,3 etc...
Step 4- Keep your finger tap'ed on the empty screen or somewhere empty in the screen. You can also just press the menu button and tap *ADD*.
Step 5- Choose widgets and find advance task manager.
Step 6- Now when you tap the widget icon, it will terminate all your applications.
Step 7- It will then direct you to a choice for your home application/s.
Step 8- You can just press lock and not choose your home and it will stay draining very little battery.
*Note* I do not guarantee this to work but it worked for me since I had my phone on the lock where I had a choice of home screen since 3:00 PM and it is now 6:00 PM...
3 hours and still full battery.
I have also previously managed to keep the battery up for 3 days and in the 3 days I was left with 15 percent battery.
I will post images if you people are having trouble *JUST PM ME OR POST BELOW IF YOU WANT IMAGES*

Appreciate the tip but since the inception of the Android OS this was one of the first and biggest tips amongst all of the community. It's nothing new. The Android OS actually does a damn good job of killing apps by itself. Unused RAM is useless RAM. It's a *nix based system.
The only time where this is good is when you have a stray app that's using CPU when it opens in the background when it shouldn't. Especially when it's keeping things awake. I only advise that you use this before locking the phone intentionally, and when you'd like it to go into a deep sleep.
I use task killers only when I'm putting my phone away for a while. Works better than when I used task killers. I'm also mindful about the apps I install and I uninstall and reinstall when need be, format my phone occasionally (I am an extremely heavy user) and defrag my SD card because of the heavy usage.

bongd said:
Appreciate the tip but since the inception of the Android OS this was one of the first and biggest tips amongst all of the community. It's nothing new. The Android OS actually does a damn good job of killing apps by itself. Unused RAM is useless RAM. It's a *nix based system.
The only time where this is good is when you have a stray app that's using CPU when it opens in the background when it shouldn't. Especially when it's keeping things awake. I only advise that you use this before locking the phone intentionally, and when you'd like it to go into a deep sleep.
I use task killers only when I'm putting my phone away for a while. Works better than when I used task killers. I'm also mindful about the apps I install and I uninstall and reinstall when need be, format my phone occasionally (I am an extremely heavy user) and defrag my SD card because of the heavy usage.
Click to expand...
Click to collapse
I agree but this worked for me and I recommend trying this. Also I agree with everything you have said and sometimes when I am out somewhere I tend to keep the phone in a deep sleep but I do not want to miss any calls or texts happening to me so I do this.
Appreciate what you have told me as well.
Also what good does formating do? (NOT SAYING IN AN OFFENSIVE MANNER, I AM JUST CURIOUS)

zm4 said:
I agree but this worked for me and I recommend trying this. Also I agree with everything you have said and sometimes when I am out somewhere I tend to keep the phone in a deep sleep but I do not want to miss any calls or texts happening to me so I do this.
Appreciate what you have told me as well.
Also what good does formating do? (NOT SAYING IN AN OFFENSIVE MANNER, I AM JUST CURIOUS)
Click to expand...
Click to collapse
Bongd is absolutely correct in what he says, the whole android system is designed to manage apps automatically, therefore while an app may appear on the task manager, they do not necessarily waste battery as they are sitting "idle"- that also means that an app will load up quicker when you go to open it, rather than if you kill the task.
Also my other point, and this is the big one, killing tasks can not only corrupt an app from working correctly but also it can cause instability to your system in the long run (because you are also killing certain tasks which are system processes) thus you notice bugs ion your phone and required to flash firmware again.
I've used advanced task manager and task panel side by side quite religiously for a while, yes it is faster and battery life does SLIGHTLY improve but trust me your phone doesn't like it.
Sent from my X10i using XDA App

zm4 said:
I agree but this worked for me and I recommend trying this. Also I agree with everything you have said and sometimes when I am out somewhere I tend to keep the phone in a deep sleep but I do not want to miss any calls or texts happening to me so I do this.
Appreciate what you have told me as well.
Also what good does formating do? (NOT SAYING IN AN OFFENSIVE MANNER, I AM JUST CURIOUS)
Click to expand...
Click to collapse
Formatting is good because just like a computer, things can get f***ed up for no reason. You can have all the correct settings but things don't happen as anticipated. It happens with any complex electronic devices, so this is why I recommend it every few months but this varies depending on how intensely you use your phone.
I use mine like crazy and tweak the hell out of it. I do it about once a month, but then again I have cell phone OCD.

The task manager helps to close apps that constantly keep connecting to the Internet, it's not about freeing up RAM it's about using the Internet connection

Some "apps" are some bad hogs when it comes to the phones recourses
Some "apps" are quite some hogs when it comes to the phones recourses.
Internet connection, Syncing, Updating ads and so on.
Some of these "bad hogs" also keep running "at full speed" in the background.
They have no whatsoever routines to save energy/recourses once loaded (background or not).
Designers of these "bad apps" don't care about battery-life, or they simply have no whatsoever knowledge/experience about mobile devices and how an application should behave on a such device.
If one are the kind who downloads lots of "cool" applications from the market, a task-killer can help allot, depending on how many "recourse hog" application one have installed and loaded in the background.

SysGhost said:
Some "apps" are quite some hogs when it comes to the phones recourses.
Internet connection, Syncing, Updating ads and so on.
Some of these "bad hogs" also keep running "at full speed" in the background.
They have no whatsoever routines to save energy/recourses once loaded (background or not).
Click to expand...
Click to collapse
yeah but we don't have any app that tells us which app is using the battery and data connections right? sure the android OS tells us the battery usage, but data?

A app to stay away from is eBay it hogs cpu time and constantly refreshes in the background, my batt goes from 2days down to 8ish hours when the eBay app is installed
Sent from my X10a using XDA App

tookieboy said:
yeah but we don't have any app that tells us which app is using the battery and data connections right? sure the android OS tells us the battery usage, but data?
Click to expand...
Click to collapse
System Panel can do this

Taskkiller stuff is not welcomed by my X10. When I kill all the apps , sometimes my connection to my operator goes down. I don't know how many necessary process' this taskkiller stuff kills as well.. I avoid "kill all" , instead I kill the ones that I'm sure that they're using internet and cpu in vain. Wish all the mobile developers use the close() method , then we won't be facing that kind of problems..

Alternatives To Task/App/Ram Killers????

Many people say it's harmful using app killers, especially on android as it may interfere with important system resources or close important system files and can do harmful damage in the longrun such as errors, things not working, etc...
When you open various programs such as file manager, picture gallery, etc you then see a list of all running programs in system/task manager.
Many of these running programs are ones you have recently used and are draining ram/cpu/battery.
Is there not ANY safe app to use that will ONLY close apps that YOU have used?
There must be some app out there that closes/kills open apps, not system or phone apps but only the ones you have installed and used?
This could be a ram killer or maybe a simple app which is not dangerous and will safely close running apps not needed.
Looking forwards to seeing what others recommend.
Thanks in advance guys,,,

kanej2006 said:
There must be some app out there that closes/kills open apps
Click to expand...
Click to collapse
yes, there are, but android just restarts them after they have been closed (froyo only)

panyan said:
yes, there are, but android just restarts them after they have been closed (froyo only)
Click to expand...
Click to collapse
Names please of a good app that kills ONLY programs you open, not system files.
What if I was to install an appkiller, but instead of having it on autokill, I was to manually click apps I opened and kill them?
Surely this way there is no danger as I'm only closing selected apps, not system files?

kanej2006 said:
Names please of a good app that kills ONLY programs you open, not system files.
What if I was to install an appkiller, but instead of having it on autokill, I was to manually click apps I opened and kill them?
Surely this way there is no danger as I'm only closing selected apps, not system files?
Click to expand...
Click to collapse
The point is, even after killing your own apps, most of the time froyo will restart them
I very much like ES' offerings - ES File Explorer and ES Task Manager. They're both free, give em a birl.

You can install Advanced Task Killer (free) and there you can perfectly select which apps to close and which not... still I rarely use it
for example your homescreen widgets are always unchecked when killing tasks, so unless you check them, they won't be killed...

Hmmm, ok.
What is the BEST way to preserve & save battery/cpu & free up as much ram as possible without harming/interfering with the phone??
When I used to use the task killer app it would consistently give me around 400-424mb free ram.
Without the app killer I would only have around 100mb of free ram since all the programs are running in the backround.
So to all you experts out there, what can I do or what options do I have in which I can safely free up as much ram as possible and safely close running apps not needed when not using the phone?
I just want the best and most effective way to make my battery last longer.
I'm having to charge my phone every day, it struggles to get through the day even when hardly used.
Looking forwards to hearing some expert opinions based on the above.

kanej2006 said:
I'm having to charge my phone every day, it struggles to get through the day even when hardly used.
Click to expand...
Click to collapse
There's definitely a problem there but you're not going to find it chasing free ram. I have approx 20Mb free ram at the moment, the phone hasn't been rebooted for at least a week but I'm easily getting through 2 days with light use. Task killers / app killers are not the answer, (in froyo at least) free ram is wasted ram.
The programs that are 'running' in the background are not actually using CPU resources unless they have a service running (see the eBay app/service for an example). Your best bet is to check the running services (settings/applications/running services) and battery usage to work out what process is hogging the CPU time. Also check your sync settings, though I'd imagine you've already tried that.

christonabike said:
There's definitely a problem there but you're not going to find it chasing free ram. I have approx 20Mb free ram at the moment, the phone hasn't been rebooted for at least a week but I'm easily getting through 2 days with light use. Task killers / app killers are not the answer, (in froyo at least) free ram is wasted ram.
The programs that are 'running' in the background are not actually using CPU resources unless they have a service running (see the eBay app/service for an example). Your best bet is to check the running services (settings/applications/running services) and battery usage to work out what process is hogging the CPU time. Also check your sync settings, though I'd imagine you've already tried that.
Click to expand...
Click to collapse
Maybe it's the anipet fish aquarium live screensaver...

Systempanel is good, I use it to stop a bad app thats using to much memory..you should never kill your apps with froyo, the OS wasn't designed like that, thats the whole point of Android, it looks after the apps perfectly well by itself, systempanel is just there as a....just in case method.
Saving battery power is a common misconception, Task killers actually get in the way of Android handling memory management as intended.....a pointless app to have with 2.2 which actually drains you battery quicker.
The LCD screen is the biggest drain on battery power, turning the brightness down, stop using a live wallpaper, turn off wifi, bluetooth, GPS ect....
With all that said the 1250mah battery is just not powerful enough to run this device period...but then most of us knew this before we bought the phone..we needed a 2000mah battery really, its just a lipo battery and can be easily increased, maybe next year we will see an improvement in the new smartphones.

kanej2006 said:
Maybe it's the anipet fish aquarium live screensaver...
Click to expand...
Click to collapse
I hope you're joking

Black1982 said:
I hope you're joking
Click to expand...
Click to collapse
LOL, well some people do say that live wallpaper kills battery...

How to Stop Certain Apps from Loading ....

There are many apps that keep loading, not only after a Reboot, but even when I use System Monitor to stop all programs, then when I open an app and check System Monitor again, a bunch of apps have relaunched!
This is really annoying, especially when memory is at a premium on the Archos 70 ....

Honestly, I think that is just an Android thing. No idea how to help you except to say it did that on my G1, my Evo, my Epic, my wife's Intercept, the Nook I had on loan, and my Archos 101...
You just have to roll with it I guess...

ExploreMN said:
Honestly, I think that is just an Android thing. No idea how to help you except to say it did that on my G1, my Evo, my Epic, my wife's Intercept, the Nook I had on loan, and my Archos 101...
You just have to roll with it I guess...
Click to expand...
Click to collapse
That's pretty much what I figured .... So far, it isn't a serious issue, but is a hassle to have to keep using System Monitor to close out running apps.
I'm still enjoying my Archos 70 Internet Tablet 250GB.
Working on preparing my iTunes music to transfer to my Archos 70 and my son's Archos 20b (his birthday present surprise will be preloaded with some of his favorite music!).

http://www.appbrain.com/app/autostarts/com.elsdoerfer.android.autostarts
but you would need root

vja4Him said:
This is really annoying, especially when memory is at a premium on the Archos 70 ....
Click to expand...
Click to collapse
android will clear these apps from memory when needed
you should only worry if these background apps use CPU (and battery) all the time

Something I posted to another forum.
Android uses a method to kill background apps automatically when space is needed in RAM. So effectively it cleans up after itself.
Here is a fairly good explanation of how the system is designed.
http://android-developers.blogspot.com/2010/04/multitasking-android-way.html
and
http://lmgtfy.com/?q=android+why+you+don't+need+a+task+killer

Try "autorun" from the market. It can stop some 3rd party apps from starting. No root required.

wdl1908 said:
Something I posted to another forum.
Android uses a method to kill background apps automatically when space is needed in RAM. So effectively it cleans up after itself.
Here is a fairly good explanation of how the system is designed.
http://android-developers.blogspot.com/2010/04/multitasking-android-way.html
and
http://lmgtfy.com/?q=android+why+you+don't+need+a+task+killer
Click to expand...
Click to collapse
If a task killer is not needed, then why are there task killer apps available for Android?
Should I not be using the System Monitor to kill apps when memory is low?

vja4Him said:
If a task killer is not needed, then why are there task killer apps available for Android?
Should I not be using the System Monitor to kill apps when memory is low?
Click to expand...
Click to collapse
Most taskkillers started their life a year (and several Android versions) ago. Back then, Android's memory management was less mature and phone memory was smaller. The improvements that came with Froyo make them obsolete and even troublesome.
When Froyo senses low memory, it will kill stuff. Otherwise, it leaves stuff in memory, operating with the thinking that "unused memory is wasted memory". As new apps open, it kills off older- open apps.
The problem with taskkillers is when the user sets them to automatically start killing stuff. Some apps have the rude behavior of self-restarting. In this case, when the taskkiller kills an app, the app will restart itself, putting it back in memory. Suddenly you have tug-of-war game between the taskkiller & the app. This increases cpu usage and kills your battery faster.
Killing things with the System monitor is alright, because it is a single time action by you. If an app restarts, that is it. There is no ongoing battle.
I do use the Autorun Manager app. It lets you pick apps you want to keep from starting at boot. The nice thing, it tells you if they are self-restarters, if they are there is no need to check them. It is useful to kill the nonrestarters (like the XDA app) that don't really need to be in memory when you first start.
I hope that helps.

vja4Him said:
If a task killer is not needed, then
why are there task killer apps available for Android?
Click to expand...
Click to collapse
Because they can.
vja4Him said:
Should I not be using the System Monitor to kill apps when memory is low?
Click to expand...
Click to collapse
No.
I'v been running my A101IT for about 3 weeks now without rebooting without killing any app and it works great before i killed some apps every hour and had lots of problems.

wdl1908 said:
Because they can.
No.
I'v been running my A101IT for about 3 weeks now without rebooting without killing any app and it works great before i killed some apps every hour and had lots of problems.
Click to expand...
Click to collapse
I stopped killing apps, and now my Archos 70 is running much smoother! I watched a video about someone using their Archos, claiming that the apps need to be loaded, in order to keep things cached, which helps the Archos apps run smoother, with fewer glitches.
My Archos runs less choppy now, but still a few glitches here and there.
I'm still very pleased with this 7-inch tablet! Took it out for a test run while riding my Surly Long Haul Trucker around town yesterday -- listening to my music in PowerAmp.