Comments on: G1 and Cupcake – What’s the Deal? http://www.androidguys.com/2008/12/30/g1-and-cupcake-whats-the-deal/ The trusted source for Android news and opinion | Est. 2007 Mon, 22 Mar 2010 14:12:42 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: TWCBruh http://www.androidguys.com/2008/12/30/g1-and-cupcake-whats-the-deal/comment-page-1/#comment-2794 TWCBruh Wed, 31 Dec 2008 18:01:50 +0000 http://androidguys.com/?p=3232#comment-2794 They didn't say that anything was 100% factual. I see a reference to what Engadget said and what someone else said too. I think the G1 will get the OTA stuff. If not all of it, most of it. It seems like the hardware is there to support it. It is just that "pieced together" stuff. They didn't say that anything was 100% factual. I see a reference to what Engadget said and what someone else said too. I think the G1 will get the OTA stuff. If not all of it, most of it. It seems like the hardware is there to support it.

It is just that "pieced together" stuff.

]]> By: chefgon http://www.androidguys.com/2008/12/30/g1-and-cupcake-whats-the-deal/comment-page-1/#comment-2793 chefgon Wed, 31 Dec 2008 15:07:03 +0000 http://androidguys.com/?p=3232#comment-2793 Do you really think that Google would have pushed out its own branded version of the G1 as a development tool (and a freebie to every single one of their employees) if they had planned on never updating it again? Cupcake is "very much a work in progress" just as it was announced. It isn't finished yet. When it is, they'll get it onto the G1 with appropriate drivers bundled. Whether that takes the form of an installer or an OTA push is really irrelevant, it WILL get onto the phone somehow. Do you really think that Google would have pushed out its own branded version of the G1 as a development tool (and a freebie to every single one of their employees) if they had planned on never updating it again? Cupcake is "very much a work in progress" just as it was announced. It isn't finished yet. When it is, they'll get it onto the G1 with appropriate drivers bundled. Whether that takes the form of an installer or an OTA push is really irrelevant, it WILL get onto the phone somehow.

]]> By: Marc http://www.androidguys.com/2008/12/30/g1-and-cupcake-whats-the-deal/comment-page-1/#comment-2792 Marc Wed, 31 Dec 2008 10:23:18 +0000 http://androidguys.com/?p=3232#comment-2792 Wow... that sure is one bad article... Your informant doesn't really seem ot understand the whole process of developing software. IF cupcake (which is basically the current SVN version of android) was stable and wouldn't crash, it would have been marekd stable and pushed as an update. People who install a cupcake build on their G1 should know that they are currently working with an unstable version of an operating system and the bundeled (new) applications. Also: what does the radio interface have to do with anything? The communication between android and the Baseband takes place over a small RIL (Radio Interface Layer) as in most smartphones and isn't that big of a part of android. ><em>The G1 contains a significant number of proprietary applications, drivers, etc</em> As on EVERY smartphone (even the freerunner!), the GSM part of the phone won't be accessed though a big open-source driver, but rather a small driver which talks to the Baseband interface. As for the applications: the operating system and the dalvik VM are completely open source and there is a well documented API available for developers to do as they please. Talking about a "significant number" is simply put yellow press level (as a lot of this post) Wow... that sure is one bad article...
Your informant doesn't really seem ot understand the whole process of developing software. IF cupcake (which is basically the current SVN version of android) was stable and wouldn't crash, it would have been marekd stable and pushed as an update.
People who install a cupcake build on their G1 should know that they are currently working with an unstable version of an operating system and the bundeled (new) applications.
Also: what does the radio interface have to do with anything? The communication between android and the Baseband takes place over a small RIL (Radio Interface Layer) as in most smartphones and isn't that big of a part of android.

>The G1 contains a significant number of proprietary applications, drivers, etc
As on EVERY smartphone (even the freerunner!), the GSM part of the phone won't be accessed though a big open-source driver, but rather a small driver which talks to the Baseband interface. As for the applications: the operating system and the dalvik VM are completely open source and there is a well documented API available for developers to do as they please. Talking about a "significant number" is simply put yellow press level (as a lot of this post)

]]> By: Briantist http://www.androidguys.com/2008/12/30/g1-and-cupcake-whats-the-deal/comment-page-1/#comment-2791 Briantist Wed, 31 Dec 2008 08:32:48 +0000 http://androidguys.com/?p=3232#comment-2791 I'm sorry, but I really don't want an onscreen keyboard. The main reason I got a G1 is for the keyboard. I've got fat fingers and they combine with the parallax problem to render ALL onscreen keyboards useless. Also, having watch the Doctor Who episodes Doomsday and Age of Steel, I'm not sure I want stereo Bluetooth... I would honestly prefer a decent version of Google Reader for the device, that's about it. I'm sorry, but I really don't want an onscreen keyboard. The main reason I got a G1 is for the keyboard. I've got fat fingers and they combine with the parallax problem to render ALL onscreen keyboards useless.

Also, having watch the Doctor Who episodes Doomsday and Age of Steel, I'm not sure I want stereo Bluetooth...

I would honestly prefer a decent version of Google Reader for the device, that's about it.

]]> By: Benji http://www.androidguys.com/2008/12/30/g1-and-cupcake-whats-the-deal/comment-page-1/#comment-2790 Benji Wed, 31 Dec 2008 08:09:03 +0000 http://androidguys.com/?p=3232#comment-2790 This article doesn't provide any useful information. All you've done is attempted to present speculative information as factual. Didn't work :( This article doesn't provide any useful information. All you've done is attempted to present speculative information as factual. Didn't work :(

]]> By: Dianne http://www.androidguys.com/2008/12/30/g1-and-cupcake-whats-the-deal/comment-page-1/#comment-2789 Dianne Wed, 31 Dec 2008 07:27:26 +0000 http://androidguys.com/?p=3232#comment-2789 Your informant doesn't really understand how Android operates as an open-source project. The "cupcake" branch that we have is a work-in-progress on the next major feature set for the android platform. Things like video recording don't work because... surprise, it's not yet done. The current code that exists as cupcake is almost but not quite feature complete, which means that it is pre-alpha -- no QA at all has started on it yet, since the basic features are not quite yet implemented. So at some point "cupcake" will become a final release candidate (RC) after going through alpha and beta testing/fixing, at which point it becomes the most recent stable android platform that people can build production phones off of. That will actually be our first RC quality code in the open-source tree, since what is there from before them is based on the 1.0 RC that was the basis of the G1 software but required a number of changes (which are not tested) to be able to make it publicly available. Your informant doesn't really understand how Android operates as an open-source project. The "cupcake" branch that we have is a work-in-progress on the next major feature set for the android platform. Things like video recording don't work because... surprise, it's not yet done. The current code that exists as cupcake is almost but not quite feature complete, which means that it is pre-alpha -- no QA at all has started on it yet, since the basic features are not quite yet implemented.

So at some point "cupcake" will become a final release candidate (RC) after going through alpha and beta testing/fixing, at which point it becomes the most recent stable android platform that people can build production phones off of. That will actually be our first RC quality code in the open-source tree, since what is there from before them is based on the 1.0 RC that was the basis of the G1 software but required a number of changes (which are not tested) to be able to make it publicly available.

]]> By: A S http://www.androidguys.com/2008/12/30/g1-and-cupcake-whats-the-deal/comment-page-1/#comment-2788 A S Wed, 31 Dec 2008 05:26:20 +0000 http://androidguys.com/?p=3232#comment-2788 If I had to guess, I'd say that the Cupcake update to G1 will be handled no different from how T-Mobile handles updates to other operating systems such as the Blackberry. T-Mobile does not push out updates to Blackberry phones as soon as RIM makes them available. T-Mobile takes its own time, but eventually the updates do come. Whatever software features the hardware supports, T-Mobile pretty much passes them on. So, if the G1 supports the features available in Cupcake, it will eventually make its way to the G1. How far out that will be will depend entirely on how nicely the Cupcake update plays on the G1 and how much time/resources T-Mobile can devote to testing and tweaking it to play nicely on the G1. If I had to guess, I'd say that the Cupcake update to G1 will be handled no different from how T-Mobile handles updates to other operating systems such as the Blackberry. T-Mobile does not push out updates to Blackberry phones as soon as RIM makes them available. T-Mobile takes its own time, but eventually the updates do come. Whatever software features the hardware supports, T-Mobile pretty much passes them on. So, if the G1 supports the features available in Cupcake, it will eventually make its way to the G1. How far out that will be will depend entirely on how nicely the Cupcake update plays on the G1 and how much time/resources T-Mobile can devote to testing and tweaking it to play nicely on the G1.

]]>