[Q] Might this be the reason for Gingerbread OTA delay?

UCFJake

Senior Member
Dec 21, 2010
205
30
0
Savannah
Computer World has an article about the impending update

I can't post links but Computer World has an article written by JR Raphael in the section called Android Power saying that the OTA is 'on it's way' for the Nexus One according to an 'android team member'.
 

nexus-six

Member
Nov 20, 2010
44
0
0
People are upset over the hypocrisy that Google is practicing, and rightfully so.

Google loves to expound over their principles, so it's okay to call them on it when they fail to meet their own words.
Hear, hear! Very true.
But if you say anything against the big GOOG, the hordes will lynch you.
 

tech338

Senior Member
Jul 14, 2010
148
42
0
Baltimore
I can't post links but Computer World has an article written by JR Raphael in the section called Android Power saying that the OTA is 'on it's way' for the Nexus One according to an 'android team member'.
http://blogs.computerworld.com/17687/nexus_one_gingerbread
"A representative from the Android team tells me there have been no unexpected hurdles and that the rollout should be starting soon."

I feel like we have been hearing 'soon' for fat too long. ARG!
 

nexus-six

Member
Nov 20, 2010
44
0
0
Google is turning into the next Cerulean Studios. This is getting ridiculous. Anybody familiar with their Astra back peddling of "soon" will understand.
Yup. Gingerbread is turning into one big joke.

Really "smart" of Google to pull such a stunt when android is getting attacked by lawsuits and the iPhone is finally available on Verizon.
And don't even get started on fragmentation ... devs are really starting to hate android.
 

crachel

Retired Senior Moderator
Jul 13, 2008
3,883
3,024
0
Texas
Yup. Gingerbread is turning into one big joke.

Really "smart" of Google to pull such a stunt when android is getting attacked by lawsuits and the iPhone is finally available on Verizon.
And don't even get started on fragmentation ... devs are really starting to hate android.
Assuming your name is a Blade Runner reference, l like to assume you're not a troll but in fact a Replicant, that's why your posting isn't quite right. Now where's Harrison Ford? :D
 

ohgood

Senior Member
Aug 8, 2009
1,612
93
0
Birmingham
Yup. Gingerbread is turning into one big joke.

Really "smart" of Google to pull such a stunt when android is getting attacked by lawsuits and the iPhone is finally available on Verizon.
And don't even get started on fragmentation ... devs are really starting to hate android.
please explain how gingerbread is a joke. not having a cookie in your hands doesn't mean it sucks, it just means you don't have it.

android is being attacked ? by who ? what lawsuit ?

iphone will sell if Nigeria-INC was the ISP. people just want an iphone, this doesn't impact android SOFTWARE DEVELOPMENT in the least.

fragmentation ? ok, let's all toss our favorite handsets (for the moment) in a pile and burn them. because they're different. i'm sure all those developers will be smiling and glad to light the fire and throw gas on it.

we should all have the same handset, just a candybar 1Ghz 512Mb, and make the software people cram their wares on the device. HTC, Samsung, and all the other electronics makers should die, and only one maker be left. Because that would ROCK, and we don't need choices. Monopolization ? Nah, that would never happen. Couldn't ! Right ?
 

k_myk

Senior Member
May 6, 2009
228
25
0
Warsaw
[...]fragmentation ? ok, let's all toss our favorite handsets (for the moment) in a pile and burn them. because they're different. i'm sure all those developers will be smiling and glad to light the fire and throw gas on it. [...]
IMHO "fragmentation issue" only applies to devices with somehow locked bootloaders where ONLY manufacturer can decide wich version you will be honored with... I've been there... I've had Moto FailStone and I still wake up at night with nightmeres about Moto Europe fcuked up update and PR policy...
 

draugaz

Senior Member
May 13, 2009
520
141
0
IMHO "fragmentation issue" only applies to devices with somehow locked bootloaders where ONLY manufacturer can decide wich version you will be honored with... I've been there... I've had Moto FailStone and I still wake up at night with nightmeres about Moto Europe fcuked up update and PR policy...
But this is not something most developers worry about. In my opinion this "problem" is really blown out of proportions. I think (and I am a developer) el goog handles the platform compatibility very nicely.

As to the "old" versions, this is a natural process and happens to any platform. Even super homogeneous apple iphones are getting fragmented. WP7 down the road will surely get exactly the same problem too.
What bothers me as developer most are those stupid bugs planted by OEMs in large quantities. But it is not fragmentation, it is a general device quality issue. This is main source of the "this app works on X but does not work on Y" problems. Not the different SDK revisions.
 
D

diversificationied

Guest
Everyone is gonna be crying all the way up to the next update. Once that hits everybody will be "OMG I LOVE GOOGLE NEXUS PHONE".

Gingerbread will never officially hit the N1, it will be the bees knees instead.
 

draugaz

Senior Member
May 13, 2009
520
141
0
And actually bragged about how easy it was to deal with the so-called fragmentation. They loved how the SDK does all the hard work for them. :)
This still does not mean, that they occasionally do not produce a bug or two of their own. Which after the upgrade often comes around and bites in the a** :)

No doubt, developers would love just a single identical version running everywhere. But in reality it would mean a complete stagnation, so nobody really wants it.
So the real art is to introduce the new features while still keeping the compatibility as long as needed but sawing it off it as soon as reasonably possible.
 

morfy50

Senior Member
Apr 16, 2010
93
4
0
This still does not mean, that they occasionally do not produce a bug or two of their own. Which after the upgrade often comes around and bites in the a** :)

No doubt, developers would love just a single identical version running everywhere. But in reality it would mean a complete stagnation, so nobody really wants it.
So the real art is to introduce the new features while still keeping the compatibility as long as needed but sawing it off it as soon as reasonably possible.
Agreed. Also I was reading about the new Sony Arc. It sounds like they learned their lesson from the X10. Their newest version of Timescape is more akin to widgets than a deeply customized UI.

They learned from the X10 that all the heavy customizations are a roadblock when it comes to updating their phone.

Not to defend the manufacturers who are sorrily late with updates or not updating all, but I think there was a learning curve in the way they should modify Android to separate themselves from the pack. Hopefully they'll do better and keep the devices more up-to-date.
 

draugaz

Senior Member
May 13, 2009
520
141
0
Agreed. Also I was reading about the new Sony Arc. It sounds like they learned their lesson from the X10. Their newest version of Timescape is more akin to widgets than a deeply customized UI.

They learned from the X10 that all the heavy customizations are a roadblock when it comes to updating their phone.

Not to defend the manufacturers who are sorrily late with updates or not updating all, but I think there was a learning curve in the way they should modify Android to separate themselves from the pack. Hopefully they'll do better and keep the devices more up-to-date.
Yes, indeed. Don't know about your side of the pond, but here in Europe Ericsson (and later SonyEricsson) was a major player in mobile phone business (together with Nokia).
Even in Symbian times they had their own custom UI engine different and incompatible to other Symbian solutions. They could afford it.
Then fortunes turned, they begun to shrunk, lay off people and otherwise "increased their ability to compete".
I.e. the same stuff which was happening to Motorola. But while Motorola draw the right conclusions and produced their Droid with almost vanilla Android 2.0 (but on time), SonyEricsson management first needed to realize the simple fact, that thinned out development can't move at the same pace as in the old times.
They are learning it now the hard way. I am not sure if they did learn enough.