There obviously can't be a production build of a port of Android for any environment (including the ADP1) until the underlying platform itself is given production-ready status (which only happened very recently).
Distribution of non-production ready parts for the ADP1 is a very thorny issue that's been on our minds since before day 1 of the ADP1 but that we haven't been able to resolve yet. This isn't a technical issue anyway, so I won't say more about it. It'd be an interesting hacking project to maintain an ongoing port of the latest version of Android on top of the latest released production version of the proprietary binaries for ADP1 - right now that'd be 1.1, but it might make more sense to wait until 1.5 files are available to embark on such a project. Just be sure to respect the various rules about intellectual property along the way. The first step, of course, will be to be able to rebuild a working Android 1.5 for ADP1 based on those files. JBQ 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. >> >> > > > > > -- 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 -~----------~----~----~----~------~----~------~--~---
