I do nightly builds (well.. when there are changes) that can be flashed with
"fastboot flash {partition} {partition.img}" (system, userdata, boot) at
http://andblogs.net/images/snapshotsThere is no official way back, but I also have update.zip and fastboot versions of the stock images on my site (backed up off JF's adp1 way back when they first started arriving). 2009/2/27 JustAnotherDe <[email protected]> > > Would Google have excluded any source from the tree that's available? > > How difficult might it be to build a version and flash it to the dev1? > I've built the code - pulled in the "extra proprietary" files from the > vendors directory. All I've got to do now is actually flash the phone > - I'm just a bit scared. I don't know too much about it and don't want > to have to spend days going through forums and sites to figure out how > to get my phone back if I brick it. > > Anyone willing (daring enough?) to test out my build is welcome to get > in touch with me for a copy... > > > On Feb 27, 2:40 pm, Al Sutton <[email protected]> wrote: > > I'd wait for firm release dates before saying there will be dozens of > > 'phones. Most (if not all) of the devices could run Symbian, Win Mobile, > > etc., and until they're formally announced, all the licensing agreements > > are in place, and have shipping dates I wouldn't bank on them being > > Android 'phones. > > > > Al. > > > > > > > > Christine wrote: > > > On Feb 27, 8:39 am, Muthu Ramadoss <[email protected]> wrote: > > > > >> Right now G1 is for GMail, and Pacman. Nothing else. > > > > > wow... > > > > > Right now, there's G1s. In April, there will be G2s. At the end of > > > this year, there will be dozens of phones, all different. Some you > > > will like, others you won't. By the time the phones get more mature, > > > we'll all have the knowledge and experience to develop great apps. > > > > > So what's your point? > > > > > Christine > > > > >> take care, > > >> Muthu Ramadoss. > > > > >> > http://linkedin.com/in/tellibitz+91-9840348914http://androidrocks.in-AndroidConsulting. > > > > >> 2009/2/27 Al Sutton <[email protected]> > > > > >>> I'm not really feeling pitty for then as a lot of the problems have > been > > >>> brought about by a bad development and release process. > > > > >>> - Someone, somewhere signed off on a design which had limited > internal > > >>> memory and no ability to install apps outside of the internal memory. > > >>> Did this person or group not think that users would ever want to > install > > >>> 10+ apps? > > >>> - Did no-one think about supporting the ADP1 when a 1.1 firmware > > >>> codebase was handed over to T-Mobile?, or did someone just not think > > >>> about rolling new firmware for ADP1s when Google started selling > them? > > >>> - Someone signed off on taking live the paid-apps implementation, did > > >>> they not think about the problems it would create for the existing > > >>> owners of ADP1s? > > > > >>> To me it just seems that the mentality is that of a development shop > run > > >>> wild. > > > > >>> One of the most of the successful projects I've worked on had a QA > > >>> manager who would organise peer reviews, look for inconsistencies in > > >>> approaches to problems and put developers together to see which > approach > > >>> offered the best benefits, but they would never claim they knew which > > >>> approach was "best" because they didn't write code for the product > > >>> (about the only things he would challenge developers on was spelling > > >>> mistakes and basic coding errors, apart from that he'd just arrange > for > > >>> two or more developers to highlight problems and work out solutions). > > >>> This would have thrashed algorithmic problems such as copy-protection > > >>> being easily circumventable and having the debug flag left on which > > >>> allowed the "type reboot to reboot" problem. > > > > >>> After the QA manager rubber stamped a release it would then go to a > > >>> release manager whose sole job was to look at the big picture. He'd > say > > >>> to developers things like "How does this affect the version we have > > >>> running at customer X's site?", or "Is this release really of value > to > > >>> our customers or are we making it because a developer has come up > with > > >>> something cool that they want to show off?", and maintained a list of > > >>> issues and considerations for the various deployments. This is where > > >>> things like not allowing developers to see comments on their own > apps, > > >>> not allowing developers to list prices in other currencies, and not > > >>> being able to create a firmware release for the ADP1 would have > arisen. > > > > >>> To me it seems that these two jobs are either missing from the > Android > > >>> process or not being done very well. > > > > >>> Al. > > > > >>> Muthu Ramadoss wrote: > > > > >>>> I can only feel pity for the poor Googs. Man, my head is spinning > with > > >>>> the number of must fix issues going rounds already. > > > > >>>> Increasing internal memory > > >>>> SDcard applications support > > >>>> ADP1 updates > > >>>> ADP1 paid app support > > >>>> Providing Google binaries > > > > >>>> and on and on and on > > >>>> ... > > > > >>>> take care, > > >>>> Muthu Ramadoss. > > > > >>>>http://linkedin.com/in/tellibitz+91-9840348914 > > >>>>http://androidrocks.in-Android Consulting. > > > > >>>> 2009/2/27 vendor.net <http://vendor.net> <vendor.net > > >>>> <http://vendor.net>@gmail.com <http://gmail.com>> > > > > >>>> Don`t be so sure. There is no official statement about that. > I`ve > > >>>> asked google (JBQ as a representative) if there will be paid > apps and > > >>>> copy protected apps in ADP 1, but he didn`t answer me with > positive > > >>>> maybe because they don`t know or don`t want to tell us their > plans... > > >>>> The whole concept of Android and the first android phone and > ADP1 was > > >>>> great till I found that we were kicked out of the paid apps. > This > > >>>> issue should be (I think - must be) resolved and ADP 1 should > support > > >>>> installing paid apps. > > > > >>>> On 25 Фев, 04:58, Muthu Ramadoss <[email protected] > > >>>> <mailto:[email protected]>> wrote: > > >>>> > Yes, paid markets will be visible only after ADP updates that > > >>>> google will > > >>>> > hopefully provide soon. > > > > >>>> > take care, > > >>>> > Muthu Ramadoss. > > > > >>>http://linkedin.com/in/tellibitz+91-9840348914http://androidrocks.in- > > > > >>>> Android Consulting. > > > > >>>> > On Tue, Feb 24, 2009 at 11:42 PM, Troglodad < > [email protected] > > >>>> <mailto:[email protected]>> wrote: > > > > >>>> > > Sorry for the noob question, but do I understand that we > can't > > >>>> access > > >>>> > > paid apps on the Dev1 until we get it updated? And that > > >>>> whether we get > > >>>> > > an update is up in the air? > > > > >>>> > > (I got my Dev1 in hopes of havign the time to learn the code > > >>>> and start > > >>>> > > making apps, but work and life are conspiring against me and > > >>>> devouring > > >>>> > > all my free time) > > > > >>> -- > > > > >>> * Written an Android App? - List it athttp://andappstore.com/* > > > > >>> ====== > > >>> Funky Android Limited is registered in England & Wales with the > > >>> company number 6741909. The registered head office is Kemp House, > > >>> 152-160 City Road, London, EC1V 2NX, UK. > > > > >>> The views expressed in this email are those of the author and not > > >>> necessarily those of Funky Android Limited, it's associates, or it's > > >>> subsidiaries. > > > > -- > > > > * Written an Android App? - List it athttp://andappstore.com/* > > > > ====== > > Funky Android Limited is registered in England & Wales with the > > company number 6741909. The registered head office is Kemp House, > > 152-160 City Road, London, EC1V 2NX, UK. > > > > The views expressed in this email are those of the author and not > > necessarily those of Funky Android Limited, it's associates, or it's > > subsidiaries. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
