Hello,

I meant to post, for some time now, a request to same effect as points
1 and 2 (from Karl's message).
Shipping a dev device with a firmware and the ability to flash a new
one without making the original firmware available forces me to boot
an hacked recovery image to backup the original firmware so I can
restore it at a later stage, which is rather unprofessional.
I understand that the dev firmware contains a few closed source
components and apps (maps API and application and gmail app for
instance) so it is not possible to rebuild an exact replica of the
original firmware from source. It would be sufficient if the repo was
tagged for each official release of the SDK so that it would compile
to a working firmware minus the closed source API and apps.

thanks
--
Delio

On Feb 20, 4:10 pm, "waters.k...@gmail.com" <waters.k...@gmail.com>
wrote:
> Hi JBQ,
>
> You are right, you have answered that question a lot, although I had a
> some trouble finding posts on it.
>
> A solution to everyone's problem might be a web page with some
> information. A page onhttp://developer.android.com/
> orhttp://code.google.com/android/
> orhttp://www.android.com/
> that would provide the following information would be incredibly
> helpful.
>
> 1. An image of the original firmware release, so that I can easily
> return to a stable state.
> 2. What steps are needed to check out the source code for that
> original stable state (source control revisions/tags/versions -
> whatever git calls them) so that I can build the above original
> firmware release myself. It would be really awesome if I could start
> my code modifications with a stable android tree that I know is
> already running and working on my device.
> 3. Essentially the same blurb you posted above, about the next
> firmware release.
>
> It seems like that shouldn't take more then a few minutes of work, and
> maybe a few weeks of hassling the web guys. When the next release
> comes up, just add items 1 and 2 for it, and update item 3 for the
> next release.
>
> Thanks,
> Karl
>
> On Feb 19, 8:58 am, Jean-Baptiste Queru <j...@android.com> wrote:
>
> > My gripe about your post is that you didn't search the archives or
> > read the messages of the last few days.
>
> > I've personally answered question #1 more times than I can remember,
> > so I guess that one more time won't hurt: "it's not available yet,
> > we're working on it".
>
> > I'm not allowed to answer question #2.
>
> > JBQ
>
> > On Wed, Feb 18, 2009 at 6:10 PM, shimsim <shim....@gmail.com> wrote:
>
> > > This is my first post and i am new to Android so excuse my ignorance
> > > if this is well documented and common knowledge.
> > > I have a stock ADP, firmware 1.0, no updates no mods and of course i
> > > want to get the latest features such as voice control, latitude etc,
> > > and so begins the fun .... Why is there nothing official that can be
> > > easily found which states what is going on for people that own the
> > > ADP? I must have read dozens of articles showing update procedures and
> > > claiming to have leaked OFFICIAL developer updates and only recently
> > > did i find 2 thread that eventually end with something stating there
> > > is NO official update for developer phones yet.
>
> > > I have 2 gripes about this:
>
> > > 1. Why no official and clear statement from the development team to
> > > clarify this before people start scrambling desperately to install
> > > leaked versions that are false? (i know i almost did)
> > > 2. Why as a developer do i have to wait for features that are already
> > > available to end users? Am i missing something or is that the wrong
> > > way around
>
> > > As i said above, excuse me if i have missed the obvious flashing sign
> > > on the front page of the android website that clarifies all this but
> > > from what i have read on other sites i'm not the only person who has
> > > these questions and cant find the answers.
>
> > > thanks!
>
> > --
> > Jean-Baptiste M. "JBQ" Queru
> > Android Engineer, Google.

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

Reply via email to