There are a lot of us opposed to task killers in Android.
At one point, I used them - but life improved when I stopped. When we went to from 2.1 to 2.2 (Froyo), there were notes and warnings that the task killing protocols in Froyo had changed. Some devs answered that call and claim to have fixed their task killers - whether or not they did any good is anyone's guess.
~~~~
As far as running nothing in the backwrong - incorrect.
Here's an under-the-hood snapshot of the services that might be running at any one time - note that I'm only running one or two actual apps at this point (warning - very boring Linux process dump occurs here):
View attachment sample_of_stock_evo_processes.pdf
So - it's really impossible for us mere users to correlate what we think might be running to what might be running - and causing the problem.
~~~~
Hardware version is faulty?
I dunno - for what it's worth, I'm at rev 0002 hardware, over 60 apps installed. I used to have the reboot problem - first month I had it - but after the first update, and I re-installed my apps - no problems. (Yeah, lucky me - not trying to rub it in - my point is that correlating to a hardware rev might not be the way to go.)
~~~~
Android is open source and therefore unstable.
Hogwash. Where's my revolver?
~~~~
What can cause an Android phone (read: specialized Linux) to reboot?
OK, some of this answer is _known_ for a _certain fact_ -- which part might apply to each of you we'll have to zero in on:
- Faulty hardware:
- One of your onboard chips is bad - handset replacement is required. The common culprits here would be memory or power-supply related.
- Your SD card is - or has gone - flaky. If you've been mounting your phone as a USB drive, and just unplugging it without doing the eject/unmount thing (because many people think that's ok because stuff works when they skip that step), then you've been playing Russian Roulette. You might have an error on your SD card such that some data an app is using (or an SD-card installed app) that is otherwise ok is now being sent to screwball-land: garbage-in, reboot-out. You can actually fix this doing the appropriate first aid/cleanup on your SD card - I recall more than one person solving their reboot problem this way.
- You have a faulty USB cable. This could cause reboots while plugged in - and if that's happened, then that _might_ (I say might) have included some shorting that could've degraded your main board hardware (first bullet point above).
- Faulty battery. C'mon - on a new phone, I totally doubt it - but it's possible. If you've been in and out of your case or doing battery pulls and have problems - now's the time to clean your battery contacts. Might not help, but it couldn't hurt when chasing something this nefarious.
- Poor application software - VERY POOR:
- I'm unqualified to say what the state of the software developer's kit is like (the tools the devs use) for Android - but it's not uncommon for devs to cut corners - especially the less-experienced ones.
- It's next to impossible to find The Silver Bullet - that one app that we can agree causes reboots - because of the old Firesign saying: two wrongs don't make a right - but three do.
- Some combination of apps and background services CAN lead to a system fault that would cause a reboot. Taking just me as but one case - I have over 60 apps installed. Who of us mere users has about a man-year to put together a survey and correlation matrix to zero in on the problem? Not me.
- About the only thing you can do to narrow this one down is painful - but insanely effective: remove your apps, run your phone stock. If it reboots and you've got a clean setup, the phone's defective, take it back. Otherwise - install one app, run a day or two, confirm no reboots, install the next app - lather, rinse, repeat. If it's app related, you WILL find either the offending app - or - will have an app that is unhappy with another.
- Unstable operating system:
- Android 2.2 on the Evo is well-designed and stable. The large number of people without the reboot problem proves that out.
- Dirty and tangled caches and data areas, unique to Android:
- A big culprit. These get cleaned up when you do a factory reset. Many have solved their reboot problems following this backup/reset/restore procedure. Again - it's not The Silver Bullet that will kill monster - but has worked for some people. (I'm reading lately this hasn't worked for many of you, so I'm not posting without reading - I'm just putting this out for those that haven't tried it you - because it has worked for some people. See: http://androidforums.com/evo-4g-support-troubleshooting/141369-how-fix-froyo.html
OK - that all said, I totally empathize and sympathize with each and every one of you having this problem.
I can't say that I expect this post to be totally helpful per se, but maybe we can use this info together to take a sorta engineering or sorta systematic, step-by-step approach and see if we can collaborate until we narrow in on a fix for this very terrible problem.
I'm up for it, we've solved other big problems in this Evo forum this way before, and I'm pulling for you guys.
I'll agree in advance that this should be Sprint/HTC's job - but we know that can be hit or miss - and users pulling together is what we do best around here.