Develop Bugs

Task manager or no task manager

When I got my desire it was stable and fast the more I put on it the slower it gets . I've tried numerous task killers and some of them screw the phone up . On one thread someone suggested leaving the phone to manage its own background programs . What does everyone thing is it better with no task manager ?
-------------------------------------
Sent via the XDA Tapatalk App

My personal choice is to leave taskiller off the desire. I put a taskiller on and almost immedietly the phone started acting wierd eventually getting into some sort of loop rebooting itself. After many reboots it eventually gave me enough time to uninstall the taskiller. Obviously that was the problem as it has never repeated itself since. My phone runs fine without it.

I really cannot understand why people use task killers. As I have said before if you are a real expert and you have a badly behaved program that you have to use you might just have to use of a task killer.
If you are not a real expert or are even asking the question don't use one. You will almost certainly end up with worse performance and decreased battery life.
I have 60 plus applications on my Desire and don't suffer any slowdowns or other problems. There is just no need for task killers/managers. This is NOT windows!
Android has a built in task killer. It's pretty good and IMHO difficult to improve on.

Kill Task Killers!!
Agree with others, you only need it to kill a rogue app without reset.

I have around 100 apps and the only semi-slowdown I can feel is by putting complex widgets and live wallpapers together. Otherwise I've tried some of these task killers and even killing all the 20-30 processes 'frozen' or active in the background had no effect.
Still I keep it in order to kill those badly designed applications that have some glitches in going back to the main screen or rarely get stuck.
I would think that if you experience some problems they are not related to the quantity of applications open in background, but rather by a single one that has some design flaw.

andycted said:
I have around 100 apps and the only semi-slowdown I can feel is by putting complex widgets and live wallpapers together. Otherwise I've tried some of these task killers and even killing all the 20-30 processes 'frozen' or active in the background had no effect.
Still I keep it in order to kill those badly designed applications that have some glitches in going back to the main screen or rarely get stuck.
I would think that if you experience some problems they are not related to the quantity of applications open in background, but rather by a single one that has some design flaw.
Click to expand...
Click to collapse
Well said.
The trouble is people use a task killer when they don't have a problem. They just kill apps. without a clue what they are doing.
I repeat don't use a task killer until you really have too.

and what about battery life?is too many running apps affecting battery?

polystirenman said:
and what about battery life?is too many running apps affecting battery?
Click to expand...
Click to collapse
Doesn't affect battery at all. Almost all apps. are suspended in the background when you move away from them. Task killers are the major cause of poor battery performance as killed apps. then have to be reloaded instead of resumed. Try switching between say six applications, and using them, with and without task killing. I bet you will see a massive performance gain without the task killer.

polystirenman said:
and what about battery life?is too many running apps affecting battery?
Click to expand...
Click to collapse
If an application keeps going in the background in some way/service it's because it's meant to be, like an updating rss feed reader, a live wallpaper, an email client pulling mail from the server, widgets or music player streaming/playing music. If you don't want those to run in the background you obviously should set them not to update, remove them from the desktop, stop them manually, etc.
Otherwise every other application you open and then leave when you switch to another application, gets stopped and 'frozen' in the state it had so that when you switch back to it or reopen it, you find it in the same state, giving you the impression of having been running in the background (but it didn't).
It's a smart way to combine the speed of single-running applications in dumb iphones and the flexibility of more complex os like WinMo. It's also apparently the same way as WP7 will work.
Like mentioned above by killing processes you mostly cause disruption in the pre-ordered way they work and probably cause more battery usage since they have to restart from scratch for the most part. More importantly real-time monitoring of processes and auto-killing them is most likely eating battery a lot since every real time monitoring does that, like many real time battery widgets and such.

Ok.thx for answers guys.i am geting rid of task killer right now.

Same here .. I'm a techie on most things obviously not Android must try harder !
Must admit did complete hard reset yesterday got rid of task killer after first posts phone seems more stable
-------------------------------------
Sent via the XDA Tapatalk App

I have a task killer, but only for killing appliactions which aren't written good and causes some lag or they don't want to close..

I just looked at the comments on the Advanced Task Killer (free, high in the list in the Market).
I wanted to believe you guys here at XDA. But I went trough the comments on that ATK and 95% was 4 to 5 stars. All with reply's like:
"must have app"
"should be included in Android"
"doubled my battery life"
Now if SO many people say that, I can't imagine that they are all wrong. Why would they all lie?
I myself have been using that ATK for a while, killing only some things that don't close (like games,Facebook or Twitter, etc...)... battery life is still not as good as I would like it to be, but I only have had my Desire for a week.
Are you guys REALLY sure that stopping to use ATK will improve battery life?

XDA mark said:
I just looked at the comments on the Advanced Task Killer (free, high in the list in the Market).
I wanted to believe you guys here at XDA. But I went trough the comments on that ATK and 95% was 4 to 5 stars. All with reply's like:
"must have app"
"should be included in Android"
"doubled my battery life"
Now if SO many people say that, I can't imagine that they are all wrong. Why would they all lie?
I myself have been using that ATK for a while, killing only some things that don't close (like games,Facebook or Twitter, etc...)... battery life is still not as good as I would like it to be, but I only have had my Desire for a week.
Are you guys REALLY sure that stopping to use ATK will improve battery life?
Click to expand...
Click to collapse
Read this article:
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/

it's the placebo effect. A While ago there was a thread on a winmo forum for a new overclocking application. It had tons of "amazing", "must have", "goes way faster", comments, it became incredibly popular. then the developer made public the fact that it was a social experiment and the application did absolutely nothing other than having a nice interface for reporting fake cpu .
As said if you have a single bad-behaving application (which is very rate) only kill or rather uninstall it. Games don't run in the background, battery becomes great after one-two weeks, but still you can't expect it to run for 10 hours of continuous heavy usage. Buy a second battery if you need that

XDA mark said:
Now if SO many people say that, I can't imagine that they are all wrong. Why would they all lie?
Click to expand...
Click to collapse
No one is saying they are lying - personally I see it more as a placebo effect, but I do understand there are certain situations where task killers come into there own. Having owned 3 Android phones though, I can say that in my case leaving Android to do its own thing works very well for me - I don't believe that it actually increases battery life significantly, but I do firmly believe it improves the overall stability of the platform.
One thing that probably should be added, is that using swap on an Android device will cause problems with Androids own internal resource management because it cannot distinguish between real memory and the virtual memory made available using swap. See here for more details. I wouldn't be at all surprised if those people who get the most "benefit" from task killers are also using swap.
Regards,
Dave

[Q] Whats the final verdict with "APP KILLERS"

I read and watch so many contradicting things about this subject, I just cannot seem to understand the truth..
I know Android works off of a linux type of OS, and that the memory function is superior to many others..
I read that having any app killer is actually bad because it drains your battery even more than if you don't have it, that the apps running in the background aren't really running as the memory or most of it is now running the application you're using.
Now what if the app killer program has a function that lets you disable the auto kill, I assume that is the part that runs and drains the battery?
would it be good then? or is it still bad?
Finally if so, do I even bother to close out the applications after a full days use?
It just seems very confusing when a large group of people tell you NO and a large group of people tell you YES.
and its reputable places too, not just amatures
http://www.youtube.com/watch?v=DVWZFNHq0uQ

I would just like to add to your confusion by saying that I read that the new Android 2.2 API disables the ability to "kill" apps. It can kill background services or something to that effect, so the program is still in memory, but not actively performing operations or something. That's all paraphrased from a 3 month old memory, so take it with a grain of salt, but if that is true, is there any point to a Task Killer if you have Froyo?

Actually, thinking about a reply gave me a good idea. More on that some other time
Long story short: it all depends.
Short story long:
Anyways, task killers are not inheritly bad, but they are "dangerous". How dangerous depends entirely on how you use them. In general I would say, if you have a device with sufficient memory available, I would only use a task manager to manually kill games (only) that you played but are no longer playing, or some apps if you understand what they do and how they work. Generally we refer to task killers that do not have an automatic component as task managers instead of killers.
One danger is how the app is killed. If it is not killed "gracefully" corruption may occur. This is very rare to occur, though. Apps will almost always be killed gracefully.
Another danger is killing apps that are tied to background services. In most task killers (if not all) there is no way to see if they have such a background service. What most task killer display is actually only visible components of applications. However, killing them will also kill the background services. This may prompt Android to just restart it, but this time invisibly, and you just wasted quite some CPU (not to mention time) to save a little bit of memory you won't miss. Some services are hefty on the initialization but light on running on purpose, and this will make the effect bigger. Another option is that the service simply no longer runs -as it is NOT restarted- and some part of your phone may not behave as you expect it to. Common sense helps here. For example, you could kill the browser like this, but killing a system service app like (I assume) SetCPU, JuiceDefender, etc will generally be a bad idea. Automated task killers do not usually distinguish between these.
Now, Android's internal killer does distinguish between these things (and many more important factors). Say you are in this situation:
- A is running in the foreground
- B is in the background and has a service
- C is in the background
- D is in the background
If we run low on memory, Android will kill C and D before killing B, and it will kill B before killing A. Which is pretty much exactly how we want it done. Android will know when it is necessary to do this. An automated task killer may for example kill B. But B might automatically restart it's invisible parts. Then the automated task killer is in the same situation again, and will shortly after that kill C or D. This operation just wasted a whole bunch of CPU cycles!
Keep in mind, that if an application is not specifically built to do something while it is not in the foreground (i.e. directly visible on your screen), it will not actually be executing any code at all. It will just take up some memory. This is a good thing, because if you go to this app again it will still be exactly as you left it, without the app having to go through all the loading and initialization steps again. How much effect that has depends on the app, obviously. You should see this more as a cache, or ramdisk, or something similar. Well-built apps do generally not have a negative effect on CPU or battery use when they are not in the foreground. They would only use background resources if truely needed.
There is no noticable negative side effect on battery to this. If Android needs the memory and it doesn't have any to spare (for example for your foreground application), it will simply kill off one or more of the background applications.
Also keep in mind that if you "close" an app by using the back button, on many devices and ROMs this will actually close the application instead of keeping it in the background. There is no foreward button, after all.
Now, to the battery issue. I have seen, heard, and read endless complaints by many users regarding poor battery life, RAM being full (there is hardly any reason to care, on a proper firmware), etc. and that these task killers help them. The fact is, that 95 times out of 100 these users are running "a bunch of crap". Because make no mistake, there are a lot of crap apps, widgets, even complete custom ROMs out there. Using system resources when they don't need to, using background services when they don't need to, constantly polling data instead of being event based, etc. Just badly done stuff.
Finding the culprit is often difficult, though in my personal experience (your mileage may vary) the culprit is most often a app+widget combo rather than a bar app. That is, unless you install a serious hack (again, like CPU speed managers, battery savers, etc) and configure them exactly how they shouldn't be configured for your usage situation, with all the resulting adverse effects. When someone I know personally has these issues, the first thing I have them do is uninstall all apps that provide widgets. You would be surprised how often that has solved the issue altogether.
Automated task killers are a band-aid solution in these cases. Of course, there also exist cases of improperly configured Android memory management in the firmware, and if you have a device with very little RAM this can also be problematic, but these are much less common than the user installing crappy stuff (though sometimes it is the carrier with bad bloatware). Usually, automated task killers just fight symptoms, not the cause.
My advice would definitely be, check what you're running and what you install. If you're a bit techsavvy, use a task manager, but only kill tasks manually. Never "kill all" unless absolutely necessary, and don't run it automated unless you are absolutely sure the developer is worth his salt. Even then, don't make a habit out of killing apps manually. Do make a habit out of exiting apps (especially games) with the back button, instead of for example using the home button to switch to the app launcher.
A case can be made for manually killing apps as it gives you more control over what is killed when, but the time you would spend doing it is worth more than what you would save (generally). Also keep in mind that the automated task killer itself will also be running a background process to check on your situation and kill apps, and thus may actually be part of the problem instead of the solution.
@nukedukem: I'm running Froyo and the task manager I'm using kills apps just fine when I tell it to do so...

I say they are bad unless you have rogue apps. And even then they are not needed. Hit Menu-Settings-Applications-Manage Apps-Running Tab-Click App-Kill. But instead of that, you can make a widget on your homescreen that goes straight to it. Long press homescreen-shortcuts-settings-manage applications. Done. I use that when I want to kill a game or something eating CPU. Otherwise I just let Android do its thing. Also, I like Watchdog Lite. It monitors apps using the CPU and alerts you when one exceeds the threshold and gives you option to kill or ignore(app may have a legitimate reason for hogging CPU) the app in question. This is good because app or processes are really only hurting or effecting the battery when they are using the CPU, not RAM. However, another option for task management is Autokiller in the Market. It allows you to change Android's minfree settings, or internal task manager, to kill off apps sooner. I set mine to be aggressive. I actually never worry about task management. Unless Watchdog beeps at me. I think the last time I killed an app was 3 weeks ago. I remember the day Autokiller came out well. I had the HTC Hero back then. To do what that app does I had to change them manually each boot and eventually a script was made to change the settings. Those early days of Android were so much fun. ;D
If anymore questions let us know.

They are just like everything, use in moderation. I use mine all the time but I don't mess with system services and only use it to kill stuff I've been using.
And yes they still work in 2.2 as long as the app is not active

Do we need any kind of task manager or killer?

I see that people have those apps running; its in the status bar.. but is recommended? I just want to make the use of the phone to run on its max without performance loss, as we all. But before, in other forums.. Froyo didn't need any of that... ??????
Sent from my T-Mobile G2 using Tapatalk

I use auto memory manager..
Sent from my T-Mobile G2 using XDA App

no, they're not needed. the OS will handle that got you and if you do need to kill an app or service, you can do it in Settings > Applications.
Sent from my T-Mobile G2 using XDA App

Android is pretty good at battery and performance management so not really.

Ok thanks..i just see pictures of the apps being runand I just wonder if we need it or why people use them.. Or is it just because to make them feel better
Sent from my T-Mobile G2 using Tapatalk

I use a task manager, back in the day with the g1 it really helpped out saving bettery life im not so sure how much extra life I'm going to get with the g2 but we'll see
Sent from my T-Mobile G2 using XDA App

I think it is needed seeing as how apps just start and run on their own.

AreOh said:
I think it is needed seeing as how apps just start and run on their own.
Click to expand...
Click to collapse
Yeah, just once in a while kill some programs, and you'll be fine.

gaarry said:
Yeah, just once in a while kill some programs, and you'll be fine.
Click to expand...
Click to collapse
Sure but you dont need a task killer to do that. Just go to Settings - Running Services and then just touch whatever service you want to kill.
Sent from my T-Mobile G2 using XDA App

Just in case you haven't seen this:
As long as you aren't put off by rooting for some reason, the following thread can help you disable all applications of your choosing from booting up (and the settings stay after a reboot). Goodbye Photobucket and Amazon.
Edit: Err, forgot to add: following that, you will rarely ever need to kill any processes, as the unwanted ones should be off anyway.

task killers usually just kill your available resources:
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them

But is it true that in g2 u can not kill ana app like in older version, u have to force stop? I find my self doing that.
Sent from my T-Mobile G2 using XDA App

U don't really need a task killer. I don't anymore. I just force stop only the apps that hang or stop responding other than that what's the point of killing an app if its just gonna start back up. 2.2 does a really good job of memory management anyway. If u don't want an app running in the background temp root and uninstall it.
Sent from my T-Mobile G2 using XDA App

From what I remember reading, in Froyo their Kill API is handled different in such that the application/service isn't really "killed" it just restarts.
I could be wrong, but my understanding is that memory management and simply just management as a whole is much better in Froyo. I only use a task manager just to see what's running. If something does go haywire or hangs, then I'd step in. Otherwise, I just like the information being displayed; makes me feel like I know what's running back there.

This is from the developer of Mobile Defense:
"Note, we do not recommend installing task killer applications. These type of apps have the ability to kill other running applications with the promise of freeing memory. Not only are these apps unnecessary but they also waste battery and introduce instability by killing necessary processes. Google Android Engineers and leading Android developers are beginning to speak out against task killer apps:
hxxp://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
hxxp://droidtalk.net/should-i-install-a-task-managerkiller-on-my-android-device/
hxxp://android-developers.blogspot.com/2010/04/multitasking-android-way.html
And my favorite, with Cyanogen Twitter quotes:
hxxp://androinica.com/2010/05/07/google-and-cyanogen-comments-imply-task-killermanager-apps-are-pointless/
Even the developer of Advance Task Manager admits that it's not needed on new devices!
Arron La, developer of Advance Task Manager, suggests that task killers are more important for legacy devices like the G1 and phones running older versions of Android.
“Task Managers were absolutely needed in the past before the new services UI came out in Android 2.0 or 2.1,” La said in an e-mail. “Task Managers had a niche of allowing users to quickly kill services associated with apps – including all the other stuff as well, such as alarms – but that was the only way to do it before the introduction of the new services UI.”

Task killers only cause problems and eat up your battery.

Taskillers only for Android < 2.1
On Android 2.1 and later there is no need for task killers, the OS handles memory and apps much more efficiently than in older versions of Android.
Task killers were needed for the best performance on Android before 2.1 but overusing them could be detrimental to performance also.
My general rule is no task killers on 2.1 and later versions but sparring use of task killers on anything earlier.

To me taskers kill ur battery because they r always running. I use hot reboot it restarts the phone from bootscreen not from the slash. So it takes me about 14 too 17 secs to restart my phone. Sense i use my phone for almost everything. Rebooting to kill all apps and start from fresh is good for me sense it takes no time to do so.
sent from the moon on my Evo 4g

[Q] task killer....yea, or nah???

I had it on my first epic and liked it but some say to stay away from it, if i dont use it is there a better safer app or not to use 1 at all and manually stop programs. i c there is a paid and free 1. i guess the free 1 has adds but i didnt on mine??

Nabisco_12 said:
I had it on my first epic and liked it but some say to stay away from it, if i dont use it is there a better safer app or not to use 1 at all and manually stop programs. i c there is a paid and free 1. i guess the free 1 has adds but i didnt on mine??
Click to expand...
Click to collapse
Leave it alone. Android 2.2 + manages tasks for you. Task killers cause instability. Just use the built in task killer on our phones.. (hold the home button and press task manager)

Yeah really shouldn't have to be killing things that often and if you do ever need to that's why there's a built in task manager.
qbking77 said:
Leave it alone. Android 2.2 + manages tasks for you. Task killers cause instability. Just use the built in task killer on our phones.. (hold the home button and press task manager)
Click to expand...
Click to collapse

No matter what people say, there are programs that are not handled properly by Froyo's built in memory handler. If you use a task killer to kill autoreloading tasks (like MAPS for google navigation) then you are causing battery drain by you killing them and then them reloading. If you know what tasks are reloaders, then you can select them to be ignored by the task killer. Some programs hog phone RAM and do not release it like the stock internet browser. Knowing this, I use the Advanced Task Killer for Froyo to kill the browser and make more RAM available for other things.
So yes, use it BUT with proper knowledge of when and how.

Watchdog FTMFW (look it up on the market). Had their widget on my homescreen pretty much from the day I started using Android. Old-style task killers are BS.

If you use the back key or pre-designed exit key, you will close apps properly and they will only rarely reappear. It's part of the Andriod design.

kennyglass123 said:
So yes, use it BUT with proper knowledge of when and how.
Click to expand...
Click to collapse
Yes, this is important. In general, don't use them, but some people don't code their apps right.
Typed by a man standing on a toilet, eating a bacon sammich.

Nay, but as stated some apps just suck, I always take the time to test the app...
Sent from my MyFrankenstein EC05OCE using XDAPA...

I will throw my 2 cents in here for good measure. As far as I can tell, my setup appears to get me generally better battery life than the rest of users, so I believe that qualifies me to comment .
I have used and tested Task Killers since I got my Epic, my first android phone, this passed November. Yes, I still use one. It's called Advanced Task Killer. It's free, and it's simple. As mentioned in a previous post, and by myself many times before, certain tasks will reload with impunity no matter what you do. Aside from freezing these services, which may result in instability in certain instances, you can't stop this. And continually causing them to restart will drain more battery rather than saving any. Which brings me to my main point:
NEVER USE AUTO-KILL! Simply use a task killer widget to "clean up" before you lock your phone, nothing more. If you use it in this way, like me, you'll see battery improvement. Just also ensure to set certain system services to the ignore list to avoid issues.

Cool thanks guys ur input helps alot!

If anything, best bet is a memory tweaker. like "autokiller memory optimizer." I'm sure thats what your looking for =) it's not a task killer.

i used a task manager/killer back in the G1 1.5 days but nowadays android does a much better job of managing memory so a task killer is really not needed anymore in my opinion.

I've used for months without any problems.. I don't kill the essential processes.. just the apps.

Web browsing is MUCH faster if I kill apps before going to the web. It gives more free RAM to cache pages.

Has anyone had any luck with Startup Auditor since Froyo? It doesn't seem to actually do anything when comparing the disabled programs in its list with what is "running" according to the phone Manage Apps setting.

rando991 said:
Has anyone had any luck with Startup Auditor since Froyo? It doesn't seem to actually do anything when comparing the disabled programs in its list with what is "running" according to the phone Manage Apps setting.
Click to expand...
Click to collapse
I'll almost guarantee you that they are just restarting. Thats why taskkillers dont work in 2.2.x, because it just "restarts" them.
[sig]Typed by restless thumbs, that are too tired to help hold my bacon sammiches[sig]

Thanks, that's what I thought.

rando991 said:
Thanks, that's what I thought.
Click to expand...
Click to collapse
Yeah, google removed the code for taskkillers in froyo.

[Q] task killers?

Hey, I noticed that in the screenshots section that everyone has a task killer, aren't they bad for android? I've read that they were needed for android 2.1 and down, not after Froyo.
So, do I need one? Why? Why not?
Thanks guys.
Sent from my SAMSUNG-SGH-I927 using XDA

ajt1995 said:
Hey, I noticed that in the screenshots section that everyone has a task killer, aren't they bad for android? I've read that they were needed for android 2.1 and down, not after Froyo.
So, do I need one? Why? Why not?
Thanks guys.
Sent from my SAMSUNG-SGH-I927 using XDA
Click to expand...
Click to collapse
samsung roms (even stock) have default task killer called "Task Manager", for active apps and if you go to Settings > Applications > Running Services, you can kill apps running in the background or cached processes. The difference is, the default tasker does not have a "Kill All" feature.
Task killer is, well not recommended, because Android has "Low memory Killer" feature, which, from the word itself, Android will kill apps as memory is needed.
It's still up to you if you want the default tasker, or a 3rd party one.

I hate that Samsung put that there. I've always been told that you let android do its job, unless there is a runaway process.
Sent from my SAMSUNG-SGH-I927 using XDA

If you ask me a task killer gets you more battery life and helps reduce data usage by killing apps that you are not acctually using.
Sent from my SAMSUNG-SGH-I927 using XDA

yes but even if you kill some apps they reopen on their own. I am referring to the stock Rogers rom and that dam AP program.

the reason task killers are considered bad is becausw most people blindly kill everything. your phone has a lot of tasks it will automatically relaunch, thus wasting more processor time in the end. if you pay attention to which processes these are and exclude them from your kill list, you can safely use a task killer.
i also suggest apps like autostarts, lots of stuff like to start that dont need to.
im newly registered but not new here! just picked up a glide yesterday and put cwm/osi on already. a keyboard is a must for me and this was the nicest phone i found with one. my d1 was overdue for retirement. i use sipgate/google voice for free calling, texts and vms (wifi) so thankfully carrier didnt matter. very happy with this thing so far. cant wait to see some ics roms?

Advanced task killer shows you which apps automatically restart and lets you disable them from being killed
Sent from my SAMSUNG-SGH-I927 using XDA

Automated task killers generally are bad voodoo because they interfere with Android's own memory management system. Android micromanages memory like you wouldn't believe, and task killers will only slow things down by interfering with it. In particular, you'll lose significant performance and battery life as the phone works harder to reopen apps that could have just been sitting around in otherwise unused memory as intended by the OS. (And of course, the auto-re-open thing mentioned above.) I used to keep a task killer on my OG to troubleshoot misbehaving apps (sometimes killing the process and forcing it to restart would right some issues), but now that Android has the running services dialog, there really is no need for task killers at all.
bobbinthreadbare said:
my d1 was overdue for retirement.
Click to expand...
Click to collapse
So I'm not the only one upgrading from an OG!

roothorick said:
So I'm not the only one upgrading from an OG!
Click to expand...
Click to collapse
It was an excellent phone. Mine finally locked up the other night while I was out and totally died. Doesn't even get the M Moto symbol when you start it up. It had been dropped countless times, entirely submerged in a puddle, whiskey spilled on it. But it soldiered on until the other night. I was even running a very broken ICS ROM (dead project now) on it and it was just as fast CM7. I ran it constantly at 1GHz which impressive for a phone that was stock 550Mhz. Most phones, even the Glide, you can't overclock by more than double like the D1. The fastest kernel I ever had on it, I had edited a version of ChevyNo1's 1.2Ghz kernel to allow 1.3Ghz. I ran it like that for a few days and it was stable.
Great phone. It truly deserves a burial at sea with a 21 gun salute.