Do it baby. That is what your phone is for.
The point is that HTC/Google are not issuing an official ROM.
The only diff is that HTC/Google have access to some of the
proprietary drivers to things like the camera/ bluetooth etc.
For instance, the latest greatest 2.1 release I could find says it may
leak memory for camera apps. This is a result of not having access to
the proprietary code.
ADP3 is really the nexus one isn't it? Google claimed to soon be
selling it via the developer site though people say it isn't there
Here is how I got 2.1 up. 2.2 is also available from cyanogenmod
though at this point I don't know how stable.
Our path with an adp to do this is much easier and less risky than
what others face (who don't have a bootloader which allows this and so
must be hacked)
I can't speak for google, I don't even work there.
> 2) If the point of the ADPs is to enable developers to i.e. tweak the
> linux kernel etc. etc. then its not a rom developers need, its all the
> constituent parts that go into a rom, so they can build their own rom
> image. Are the constituent parts available to do this for 1.6 with an
> ADP? But they haven't issued the bits for 2.1/2.2.
All the parts are there for 1.6. I believe some parts are binary
like the camera and bluetooth stuff.
Most of the parts are there for 2.1/2.2. I think the community
version of the proprietary stuff google doesn't release (likely due to
licensing woes with the hardware manufacturers), is in Git.
> I'm being pedantic about the term rom, because if I want to do
> something such as tweak the kernel, even if google release an official
> rom for ADP for 2.2 its useless to me? I need to make my own rom and
> thus need the ingredient building blocks to put into my rom which is
> the important thing.
Tweaking the kernel is can do. That's there. It's just a few
components like the camera and bluetooth stuff that we don't have
access to the src for. It's been worked around though not perfectly.