[G2 and Desire Z Android Development] JustAnotherNewbie:
No worries, flames generally aren’t so kind. :P

My reply is a little long, but it is not intended to stoke any flames. (Which don’t exist, but people imagine insult where there is none intended, particularly online. I assure all people, if I mean to insult someone it will be obvious. :P) I just wanted to take the opportunity to show why I included everything that I did, and I appreciate in suggestions on how better to format my posts so that is easier to discern what are the likely causes and the could-be-but-probably-isn’t causes. (I didn’t think to list them separately at the time.)

If I had to place a bet on which of the possible causes that I listed it would be on the fact that I did not wipe the Davlik cache for the initial install. I am even more confident now that your experience seems to back up that theory.

(I was hoping, in fact I continue to hope, that other people who have the random reboot/reset issue will offer feedback on whether or not they wiped Davlik before installing. I think a lot of Newbies made the mistake in thinking that the “Wipe Cache” would have included a wipe of the Davlik cache.)

The problem of random reboots is apparently rare, or at least under-reported. So it may very well be the case that it is simply a bad install, which is known to happen randomly across all ROMs on rare occasions.

Those are the two main theories I have on what was the cause, but I included SetCPU and LauncherPro just in case my theory was wrong. After all, I was hoping to help people who have run into the problem, and I wanted to give the exact steps I took to remedy the situation.

In any case, I included the list of possible causes because it allowed people to look into the situation further.

(The ability of multiple people to tweak the system to tease out the problem is far greater than the ability of a single user with a single phone. I waited nearly 48-hours before feeling confident enough to post that the problem was solved. So if I failed at the 36-hour mark then I would have to start over, and at best it would be 48-hours before I could post; whereas two people tinkering around have an advantage as they can attempt multiple solutions, even independently from each other, and allow for decent time-frame to reach conclusions.)

There was also the hope that the wiser-than-I folk could eliminate any of my possible theories, or use my input to help track the problem.

As my name indicates, and my posts often reference, I am a Newbie; I am not confident enough in my guesses to omit possible causes that I do not feel are likely. This is especially the case when it is a problem that may cause affected users to give up on a ROM, and that my input may help patch the problem, or at least offer a remedy to the affected people that does not including moving to another ROM.

Tonight I might go back to LauncherPro or SetCPU, maybe both; not just to test, but because they are my preferred programs. So hopefully in time I will be able to offer a little more observational evidence. (Though odds are 1.5 will be out before I get a strong feeling one way or the other on what is the cause, so we’ll see.)

Anyway, no worries and no flames. ^.- I was just throwing in what I’ve noticed in a meager effort to give back to the community that has given me all sorts of keen ROMs and toys to tinker with. :P It’s more productive than playing Xbox, anyway.

-Newbie