Dave, I'm not after G1 device images, I would be happy if I could get access to a fully working cupcake emulator, but no one in the public development community can. I said before the G1 launch I see Android as the platform, not the G1, Magic or any specific device implementation, but at the moment there is *nothing* which we can use to can prepare us for the imminent release of a cupcake device from an OHA member. No one I know would recommend last minute rushed coding, but as every day goes past you're pushing developers further and further into that situation. Vodafone have set a date for the Cupcake powered device release and that's our deadline (which is just over 2 weeks away at best according to Vodafones website), and yet we still don't have *anything* which allows us to do full cupcake testing. The closest we can get is emulators with broken networking. Btw, I do not and have never expect Google to support my SDK builds. The closest I have got to statement like that is asking developers to submit bugs to b.android.com, and expected Google, who have final sign-off on all of the checkins to the public repository, to focus on fixing fundamental bugs like broken networking. After a quick bit of work it looks like the fix for http://code.google.com/p/android/issues/detail?id=996 only made into master branch and not into cupcake and that fix dates back to November last year. Using the master branch would be fine, if you could tell us it would give a good representation of what to expect from cupcake. So what do you expect us to do?, Do you expect the development community to sit back and take the flak when users start complaining that developers apps don't work correctly on the HTC-Magic?, or do you expect many of us to start pulling all nighters whenever you decide to release an official SDK to make sure our apps are cupcake ready?, because at the moment I can only see we have those two options and to me both of those sound like the OHA and Google really doesn't give a shizzle about the public development community despite its' efforts to help Android become popular. Al. ---
* Written an Android App? - List it at http://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. ________________________________ From: android-developers@googlegroups.com [mailto:android-develop...@googlegroups.com] On Behalf Of David Turner Sent: 13 April 2009 11:14 To: android-developers@googlegroups.com Subject: [android-developers] Re: SDKs & comparison with the iPhone On Sat, Apr 11, 2009 at 9:34 AM, Al Sutton <a...@funkyandroid.com> wrote: Now before I start on the iPhone comparison I'm going to pre-empt the normal "But Android is open source....." response by saying lets be honest and admit it as it stands Android is not an open source project because the public "open source" repository is pretty worthless in its' current state. As far as I know, "open-source" is not a value statement, but a set of conditions that rule how sources can be distributed and used. What is available from the git repositories is as open-source as it can be. You seem to believe that the fact that you can't produce exact G1 device images from them makes them worthless, but many people are already using them to port the platform to various other devices. Also, the Android team is trying to make these sources more useful to ADP1 owners, and closer to the internal tree used to prepare certain shipped device binaries. This is something that has been already discussed heavily in these forums and is quite well documented. There are some valid criticisms about this project's roadmap and management but I don't think this is one of them. The last time I tried to build the master branch it failed missing some Google internal API classes. It is expected in any open-source project that sometimes the build of the most recent sources will not work correctly, or will not generate properly working code. This is generally fixed by providing patches, notifying of the problem, and/or waiting a bit for the fixes to be submitted. For the record, I did a full fresh download and build of the master branch two days ago and it built without any problem the "generic-eng" build product which is the only one you should care about at the moment. Oh, and networking is working in the emulator too. The SDKs I've produce from the cupcake branch seem to be considered by Google employees as pretty useless with comments like "This is why we want to be clear it is "unofficial," because it is not actually a working SDK" being thrown around First, it has been said several times in these forums that the cupcake branch is only there to reflect all the non-proprietary bits used by the internal Android source tree, and that you should not rely on it to build anything that works (be it system images or an SDK). You should really work from the master branch for anything "real". Also, the SDK is, compared to generic-eng, a very special build product for a variety of nasty technical details. Due to this it is very frequent that its build will not work or will miss crucial configuration files that break certain features. For cupcake, the tools team has also made a really big number of drastic changes to the way the SDK tools work in order to support new features like platforms, add-ons and AVDs, which did break custom SDK builds more than once. The SDK is also very special because when we release an official one, it comes with official documentation on the public web site, a set of publicly supported APIs which are a very strongly binding contract between app developers and the platform, plus quite a lot of testing to ensure that it works reasonably well in terms of features and host platform support. Believe it or not, this takes a lot of time These are the reasons we say the things you mention: you are packaging non-working SDKs and should not expect us to throw much of our support behind them. At the moment, we don't encourage application developers to use custom SDKs to test their code against Cupcake, do so at your own risk. and networking in the emulator still being broken a week after users started reporting the showstopper problem (And Romain did hint that Google have a fix, I read http://groups.google.com/group/android-developers/msg/41fcefc36bd16d44 as "there is a version where this is fixed"). Networking works well in the "generic-eng" build product of the master branch. I have tested the SDK build yet, but I wouldn't be surprised if it is broken, as explained previously. However, this is the kind of thing that will get fixed when preparing an official SDK release. Or you could look at this forum post, and integrate it into your custom build: http://groups.google.com/group/android-developers/msg/bcd639ecee7f270b --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
