• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

The "OMG I just ['got updated' OR 'updated'] to Cupcake" Thread...

Status
Not open for further replies.
One would feel fortunate and honored to have an OTA update sent to their G1.
Nothing in Colorado yet. I wonder if it will have anything to do with area?

T
 
me 2. . .
i was so excited only to realize of wait. . .they're just apps i can't even update yet bcuz I don't have cupcake yet. . .
t-mo ftl. . .
 
exactly...I just left mine alone gently placing my phone down with rage and not messing with the updates lol
 
yes ban him for false information. saw that link and almsot got a damn hard on only to be blue balled yet again by cupcake
 
Just in case folks were curious...

OTA updates work in a specific way...geographic, length of being a customer, etc are all ignored...they are sent out in small batches of 1000 to a completely random distribution network wide.

Here are the reasons:

- if there is a hiccup, customer service can alert the OTA dept to stop updating before they are flooded (#1 reason)

- they are sending out a lot of data over the network, no reason to chance calls or other data needs suffer due to this rollout

Both reasons above are why they don't want there to exist a way to "force the update" as it would eat up bandwidth and could be a customer service nightmare.

If anyone had a sidekick this same method was used and the same reasons existed.

This is also why they don't even offer a non xda style link from the Tmobile site to download and manually update the device on using your PC, again the customer service calls.

It is interesting when you think of the limiting factor, but it doesn't help all of us eager early adopters.
 
Just in case folks were curious...

OTA updates work in a specific way...geographic, length of being a customer, etc are all ignored...they are sent out in small batches of 1000 to a completely random distribution network wide.

Here are the reasons:

- if there is a hiccup, customer service can alert the OTA dept to stop updating before they are flooded (#1 reason)

- they are sending out a lot of data over the network, no reason to chance calls or other data needs suffer due to this rollout

Both reasons above are why they don't want there to exist a way to "force the update" as it would eat up bandwidth and could be a customer service nightmare.

If anyone had a sidekick this same method was used and the same reasons existed.

This is also why they don't even offer a non xda style link from the Tmobile site to download and manually update the device on using your PC, again the customer service calls.

It is interesting when you think of the limiting factor, but it doesn't help all of us eager early adopters.

This actually makes sense. They have three weeks to get to everyone, while still keeping up a usable network. The problem with giving a specific date is that, of course, at 12:01am SOMEONE is going to freak out and call CS to complain. "It's 12:01am, where's my cupcake??!! Waaaah! You lied to me, I'm getting an iphone!!!" :-p
 
It is confirmed that they are sending OTA cupcake update in LA (Los Angeles) , i say this because i work in Pinkberry. Whenever i see a customer carrying a G1 i ask if they gotten update (cupcake). 12 out of 7 said yes. Also asked when they got it and most of em are either on the month of November(Release) or middle December. Which means they are doing the OTA by date purchased. I may be wrong but i've waited for this update and i try to find out as much as i can. so if you guys dont believe me you don't have too, but this is what i got and i just wanna share it. Hopefully people would be more patient just because there are so many of us (g1 owners) and a fair amount of T-mobile/google employees. Well thats all i have. :rolleyes:
 
It is confirmed that they are sending OTA cupcake update in LA (Los Angeles) , i say this because i work in Pinkberry. Whenever i see a customer carrying a G1 i ask if they gotten update (cupcake). 12 out of 7 said yes. Also asked when they got it and most of em are either on the month of November(Release) or middle December. Which means they are doing the OTA by date purchased. I may be wrong but i've waited for this update and i try to find out as much as i can. so if you guys dont believe me you don't have too, but this is what i got and i just wanna share it. Hopefully people would be more patient just because there are so many of us (g1 owners) and a fair amount of T-mobile/google employees. Well thats all i have. :rolleyes:
No. The update is random. I know people who have had their G1's less time than myself that got updated before I did.
 
12 people out of 7 people said yes they got it? how? am I missing something?

i believe its out, and coming to me soon, but 12 out of 7 people? lol i guess the tall in LA are really 2 midgets standing on top of each other.
 
Well as i said this is just according to my personal research, it can be random but i was just saying that those 12 people i got 7 to show me that they did get the update. Maybe it is random or by IMEI idk, but all we can really do is just wait for the long awaited update! I sure am excited.:D
 
Well as i said this is just according to my personal research, it can be random but i was just saying that those 12 people i got 7 to show me that they did get the update. Maybe it is random or by IMEI idk, but all we can really do is just wait for the long awaited update! I sure am excited.:D

Evey update the blogs light up with people who get it, different regions, different purchase dates. If there was a pattern AF, Phandroid, or someone else would've figured it out by now. You've asked 12 people in LA. That's not random, nor is it representative, nor is it a large enough sample to observe a pattern. Perhaps if there were only 50 Android phones, and they were all in LA -- your research would be very useful. There are thousands of Android phones, perhaps millions, any sample that's less than a couple hundred to a thousand and covers less than 25 geographic areas in the US isn't enough to tease out a pattern.
 
Status
Not open for further replies.
Back
Top Bottom