Like I said, so far we (Google) haven't been able to resolve the issue
of the pre-release availability of the proprietary bits necessary to
run the latest Android from source on ADP1. We know the issue is
there, we've known about it for a very long time, we know how painful
it is for anyone who tries to actively participate to platform
development, but that doesn't mean that anybody who takes part in the
discussion here has the power to fix it (and I've already talked to
the people who talk to the people who can fix it... to the point where
I was asked to stop as I was getting annoying and no progress was
coming out of it).

Now, it's up to you to decide whether you want to be constructive, or
whether your interest lies in whining and pointing fingers. We have a
saying in French that goes along the lines of "critique is easy, art
is hard". If you want to permanently stay on the sidelines (or in the
stands) waiting for someone else to deal with problems that you can't
be bothered to tackle yourself, it's your choice. If you want to
actually walk on the field and be part of the action, come on in.

Your continuous stance toward Google is evidence that you believe that
actions speak louder than words. The ball is now in your camp,
everybody is waiting for your actions. Set your priorities, publish
your roadmaps, deliver on your promises, show everyone how it's done.

Re-saying what I wrote earlier, one way to participate would be to
un-evolve/down-port the lower layers of Android so that they can
continue running on a given released version of the Dream proprietary
files. If that's not good enough for you, you could also participate
in the efforts to get Android running on some hardware that's more
open than that, e.g. the Openmoko Freerunner, the Nokia Internet
Tablets, or the Trolltech Greenphone (each of those has advantages and
drawbacks, and I know that there are people already actively working
on the first two).

JBQ

On Sun, Apr 26, 2009 at 7:26 AM, Disconnect <[email protected]> wrote:
> You have an interesting concept of platform hacking I guess. I don't mean
> "running a new image." (Or are you saying that new releases leap, fully
> formed, from the head of the android statue and nobody at google does any
> development on them? While that would explain some things, I find it
> unlikely. :) ..)
>
> I mean, specifically, putting outside platform developers on the same
> footing (device-wise) as the google developers. If cupcake uses a new rild,
> new radio firmware, gl library, or what have you, why do external developers
> have to hack and tape to get a working image? It is what the device was sold
> for!
>
> (Yes. Some platform devs inside google use only the emulator. Thats great.
> But for a lot of things, the emulator is very limited - that is why platform
> hackers were encouraged to buy an adp1. And realistically, its been proven
> pretty well that you can't even do basic app dev on just the emulator -
> without testing on a phone, you'll never have a working app.)
>
> On Sat, Apr 25, 2009 at 10:30 AM, Romain Guy <[email protected]> wrote:
>>
>> It isn't behind at the moment since Android 1.5 final has not been
>> released, be it the SDK or firmwares for existing phone.
>>
>> On Sat, Apr 25, 2009 at 6:30 AM, Disconnect <[email protected]>
>> wrote:
>> > Will the ADP1 "phone for platform hacking" always be behind the final
>> > releases of the platform?
>> >
>> > That seems .. not good. (Esp since quite a few people bought it to do
>> > platform work.)
>> >
>> > On Sat, Apr 25, 2009 at 9:08 AM, Jean-Baptiste Queru <[email protected]>
>> > wrote:
>> >>
>> >> -The T-Mobile G1 isn't meant to be updated with arbitrary versions of
>> >> the system.
>> >>
>> >> -If you have an Android Dev Phone 1 (same hardware), the proprietary
>> >> files necessary to run 1.5 on it aren't currently available anywhere.
>> >>
>> >> JBQ
>> >>
>> >> On Fri, Apr 24, 2009 at 10:09 PM, Venkatarangan MJ
>> >> <[email protected]>
>> >> wrote:
>> >> > Does anyone has a good reference of the exact procedure from
>> >> > downloading
>> >> > say
>> >> > Android SDK cupcake version 1.5, building it and finally updating the
>> >> > T
>> >> > G1
>> >> > Mobile? There are some references like but still may not be very
>> >> > clear
>> >> > to
>> >> > new ones.
>> >> > http://forum.xda-developers.com/showthread.php?t=462512
>> >> >
>> >> > I have had some references with available images uploaded but not
>> >> > really
>> >> > a
>> >> > good tutorial to do everything ourselves from scratch.
>> >> >
>> >> > But I think we need to document it better for the community. I was
>> >> > planning
>> >> > to do one but if any of you know a reference, I thought it would be
>> >> > better I
>> >> > start from there, identify the deficiency and improve on it.
>> >> >
>> >> >
>> >> > Regards
>> >> > Rangan.
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Jean-Baptiste M. "JBQ" Queru
>> >> Android Engineer, Google.
>> >>
>> >> Questions sent directly to me that have no reason for being private
>> >> will likely get ignored or forwarded to a public forum with no further
>> >> warning.
>> >>
>> >>
>> >
>> >
>> > >
>> >
>>
>>
>>
>> --
>> Romain Guy
>> Android framework engineer
>> [email protected]
>>
>> Note: please don't send private questions to me, as I don't have time
>> to provide private support.  All such questions should be posted on
>> public forums, where I and others can see and answer them
>>
>>
>
>
> >
>



-- 
Jean-Baptiste M. "JBQ" Queru
Android Engineer, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Beginners" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-beginners?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to