ARCHIVED - Feedback & General Discussion

[ArronL]

Cupcake is still a development branch.  It being merged to the public, master branch has nothing on it being ready.  It merely means the Android team is now trying to be more open about their development. I recently installed it into my G1 (you can read more about it here with pictures and my personal opinion) but it's very much unusable right now.  It is very laggy and many things are still broken.

There is a leaked 1.1 version but I am not sure if Tmobile is releasing that or not.  I personally felt that version was going to be the RC31 update.

[rantrav]

I am sure that one main problem is that Tmo is dealing with an outside company and with an outside companies program or OS. This said there may be some problems with things that we do not know about such as contracts. This update seems to be part of Google and Tmo was used to release their new system, one would think that they wuold work hard to make it seem like the best throwing out fixes and update as fast as they can. As we are seeing there are different phones coming out with the android system on it, making quick fixes for this G1 phone a need.

To clear up what I am trying to say...... There may be some conflict with Tmo and Google as far the release. Maybe Tmo does not want certain things on it or they want it a certain way. All we can do is speculate and wait to see what happens. Me personally, I am beyond ready for this update and have put off getting root so that I can do my own little personal updates and mods. Seeing how this updatemight not be released as soon as we want I am going to stick with checking exd to see how their "cupcake" project is going. Usually you can go to the middle man (the small guy) and complain about things and hope that they can press the issues to both sides, but in this case there is no middle man and we are stuck waiting for something that we really do not know anything about yet.... But be patient and hope for the best, what happens happens 

[Starplaya]

Well look at it this way guys... At least we know tmo and google are taking there time with this update instead of just rushing it (wasnt just about everybody complaining about tmobile rushing the G1...) Im sure they are just trying to perfect this update and make sure there are know bugs and things the might have missed. Be pacient and im sure this update will be well worth the wait.....Thanks Will

[googleandblog]

Thats the same response as Google Android engineers provide, but as with previous updates T-Mobile did, such as RC29 & RC30, they werent in parallel with Android Master build updates but when T-Mobile itself incorporated elements into its own release to its G1 customers.

Time will tell but T-Mobile is actively preparing an RC31 update which should have some cupcake "elements" - what they are and exactly when is pure speculation at this point.

[BBGuy1009]

The Cupcake update, will NOT be available for the G1, it was made for the Android platform, currently not compatible with T-mobiles G1. However, we are all really awaiting the new operating software RC 31...... 

[hondarider525]

Please do tell me where you got the information that "cupcake" will not come to the G1. Sounds like your stating FACT to me =].

[GTeye]

Their official word is they have no official word?

They told the community nothing except to add to further speculation because of a lack of committment regarding the cupcake features.

I appreciate passing it along but I hope you pass back to them that what they stated was pointless and doesn't provide anything regarding the future of the phone.  It's actually pretty funny,

We already know cupcake is a work in progress. 

They told us they will tell us about future updates for the g1, imagine that?

They have yet to use the term cupcake or cupcake features and g1 in the same sentence it seems.

Not a very good way to get referral customers.

[Jrbourque]

agreed with gt fully

[ardchoille42]

Well, I'm happy my g1 works the same way it did the day I bought it. I don't remember T-Mobile nor Google making any promises about future updates, so any updates we get are, in my opinion, frosting on the cake (pun not intended). But, then again, I don't waste my time with rumors.

[bartolin]

with the way technology goes this phone is entering adulhood after 3 month accept it the way it is , there will be a g2 and after that a g3 and a  lot more, il like my g1 but my next phone will be the one that get adobe flash, stereo bluetooth, an more memory in that order, i feel lucky i havent had a single problem with my phone and i hope adobe comes to the g1 first so i dont have to get another one if not BRING THE G2.

[flarbear]

---

ROMzombie wrote:

Uh, no.  "Cupcake" WAS a development branch, but was merged to the core codebase over a month ago.

http://source.android.com/roadmap/cupcake

---

Update: cupcake has been merged into master.

---

If T-Mobile isn't going to push it as an update for another three months, that's fine, although disapointing, but don't lie to us quite so blatantly.

---

The following statement is also on that same cupcake web page maintained by the android team:

• cupcake is still very much a work in progress.  It is a development branch, not a release.

This is identical to what the T-Mobile statement said.

The fact that cupcake was merged into the master doesn't mean the master is now cupcake - it means the master now contains everything that was pioneered in cupcake.  But cupcake still is a development branch - albeit hopefully one that will be closed and left undeveloped with the work focusing back on the master so they don't create any further splits.

The paragraph near the top of the page mentions cupcake's origins.  It was a parallel branch that was used for further development while they took on the task of converting a main code branch into an open source format.  They merged it back when they were done with the open source transition, not because the engineers working on cupcake had produced a final solid product-worthy result.  So, some "work in progress" that had been going on in a dead end parallel branch was merged into master.  That doesn't mean it is ready for release, and the statement above, quoted both on the cupcake web page and in the memo that Will forwarded to us, clearly states this.

The following statements:

1. cupcake is a work in progress
2. cupcake is merged into the android master
3. cupcake is a development branch

None of those statements are in conflict with each other, though there is some ambiguity when they say "cupcake is a work in progress" I believe they mean that the work that was in cupcake - and which is now living in the master branch - is the work in progress.  I don't think they meant to imply that they will continue working on it in the branch labeled cupcake - that would just continue the fracturing of the code base.  They could stand to update the page and say "cupcake was a work in progress at the time it was merged into the master and the results of that merge still represent a work in progress which will continue to evolve in the master repository".  To me, this is just the result of shoddy web page editing - someone updated the line that talked about the timeline of merging and didn't really look at all of the ways that the milestone of finishing the merge affected the other statements on the page.

[silk7]

From the OSP page 

"Update: The changes introduced in the cupcake branch have been merged into the master branch, preserving all of the previous commits to master.  The same will happen for each future drop to cupcake."

So we may have more than just one cupcake?

[tracksforhire]

i personally think this google phone was a bad investment for me i should have waited. the only thing i love about it is the browser. the app market is 90% garbage, instant messaging is a joke etc etc plenty of us bought into this phone hoping that alot of these problems would be fixed due to it being open source open source has yet to show some real meaning. i think in about 2 years android will be a good device but i just dont have time to sit and wait and check blogs everyday for that day to reach.

[Paranoid-Androi]

---

Will wrote:

My fellow citizens:

I bring to you a message crafted with great care by our Product Development and Public Relations departments. A message approved by Google and delivered to me only moments ago. A message I now post for you, our loyal community members:

According to the Android team, "Cupcake," which is the code name for an Android software build, is still a work in progress that is considered to be a development branch and not for general availability.

We will update you as T-Mobile GO software updates are made available to T-Mobile customers.

There you have it. Kind what you expected... Right?

Now... I'm not exactly sure what 'internal memo' some have claimed to have seen (personally I get emails, not Memos.  Memos are kind Office Space)... or where these release dates originated or whom supposedly confirmed them. Seems one or more dates have already come and gone with no OTA or download location. I'd expect the same series of blogosphere promises and broken promises to continue for some time. Honestly, I've been making calls and sending emails to all the 'Right' people and no one I've spoken to knows more than this. Disappointing? Indeed it is.

All that said, the staff and I will continue to communicate the need for additional information on our side and post what we can as we find out. For now... this is all T-Mobile has to say about Cupcake.

---

The mere mention of something having to be crafted has me worried.  I'm not shooting the messenger but that message says nothing, and nothing that hasn't been said before.

My analysis on this is that there is no guarantee that there will be any new feature updates.  And that updates may be provided as warranted by the carrier.

Is this going to be played out with typical OSS fashion where if you don't like what you're given then fix it yourself?

Time to market a new Android device.  Profit!

[Tula]

Well if your looking for quick fixes for some of the bugs then go here.

Having problems with your secondary email not notifying you?

http://code.google.com/p/k9mail/

K9 mail is AWESOME. I'm still having a couple problems with Exchange but I'm sure they'll fix it soon.

If you hate the slow choppy scrolling and freezing of text messages?

http://brad.livejournal.com/2399403.html

Scroll down to the link with the APK and dl it. It's k9 messaging. Which kind of leads me to believe the update Google is working on is codenamed or somewhat related to these k9 apps that Google employees are working on.

Either way Google needs to address these bugs in the G1 whatever the name of the updates may be.  

[t1n0m3n]

---

silk7 wrote:

So we may have more than just one cupcake?

---

Dude, I have been saying this for weeks, "we" will never see Cupcake.  It is a development branch.  However, it is very likely that we will see some of the fruits of the cupcake labor.  This will come to us as RC31.  Just because some cupcake elements have been "merged to master" (which by the way will happen many many times in the future) doesn't mean that we will ever see anything that ever gets merged.  Not only does Google have to work the bugs in the master branch for the cupcake elements that get pushed to it, T-Mobile will most likely have to do the same thing for the G1 specifically for the main branch code that Google pushes to TMO.

Message Edited by t1n0m3n on 21/01/2009 11:37 PM

[t1n0m3n]

Google / T-Mobile, if you are listening, now would be a good time to outline the development processes from "Google dev" to "T-Mobile OTA."

[Tula]

They arent listening.

[huzzah42]

My crystal ball is on fire tonight: RC31, out by end of month, so perhaps look for it starting late next week. 

[jamesd86]

well i'd say towards the end of Q1 2009 is a more realistic release date, if not early Q2