[FactoryD]

Here's some useful info from the http://groups.google.com/group/hosted-the-basics group

Out of the box, it worked. I put in my n...@mydomain.com and password
and the G1 picked up my personal domain settings just fine. But I
guess in the less than 24hours I had this little bugger, I got a
little too app-happy and so I got the utterly annoying
"android.process.acore" error which according to t-mo help, required a
hard reset to clear up. After the hard reset, I got the missing
application: cl error and I spent the greater part of this evening
troubleshooting this message.
Im certain it has to do with enable service settings in the dashboard.
Here's what I did to get it working. Since the error mentions
contacting the domain administrator for my domain (me), I had a hunch
this had something to do with my domain settings. I went into
Dashboard and began enabling and disabling services. After disabling
chat and trying to log in on the phone, I got the error "This account
cannot be used on the phone because it is missing the following
applications: chat, cl."

This gave me the hint that the error was directly related to my
domain's service settings. I disabled all services, including mail and
tried once more, getting the error: "This account cannot be used on
the phone because it is missing the following applications: chat, cl,
mail."

After re-enabling all three chat, mail, and calendar I still got the
error again but only referring to the application "cl". I then went in
to "Change URLs for multiple services" at:
https://www.google.com/a/cpanel/mycu....org/CustomUrl
I changed all the domain names to the default and after that was able
to log in successfully.

> Is there a setting that I'm missing somewhere? Or do I need to create
> *another* google account and setup forwarding and all that headache?


In conclusion, I believe that to initialize the G1, the essential
services are mail, chat, and calendar; and the G1 is using some simple
method of determining the URLs for those services. Im not sure why the
above last step worked being as how the default URLs are always active
regardless of custom settings, but I guess this is just another one of
those early adopter bugs. Funny, before I got this one resolved, I
contacted T-mo again and got a return authorized for this as a
malfunctioning phone. Perhaps everyone's learning the rules as we go
along.
...