Quote:
Originally Posted by gTen
But at the same time you can look at it this way..SGS came out same time as the EVO..and yet international SGS has 2.2.1 and HTC doesn't..so wouldn't that put HTC behind?
The problem that happened was this..The hummingbird was made in late 2009, so the cellphone had a much shorter cycle then say an EVO that already 2 years old...(they planned t release it earlier but they had the wimax issues remember?)...
At the time SGS was released Froyo just came out...by the time Samsung started working on 2.2...2.2.1 came out..so they decided to go with 2.2.1..I'm not denying that Samsung needs to restructure somehow to make it work faster..but in this case it seems more circumstantial.
The AT&T and T-Mobile need to load it up with their bloatware...samsung already gave Froyo to all the carriers..its in their hands...
|
HTC has more than one style of phone out currently, I wasn't aware that
NONE of their phones had 2.2.1 as of yet both domestic or internationally. I wasn't aware of the time line about the EVO or how new the Hummingbird is, but they are doing themselves a disservice by dragging this one out.
I've been waiting and waiting for a new phone, almost 18 months now, nothing prior to the Epic was that appealing to warrant a new 2 year contract with Sprint, so I waited. Now the Epic is getting up there in age and it still hasn't been upgraded. What Samsung hasn't figured out yet, I guess, is that if a new phone with better specifications gets announced say dual core and has Froyo to start with or possibly Gingerbread, why will I care about the Epic and 2.2.1 anymore? I'd just wait for that release and then those are lost sales. I'd rather buy a phone that ships with 2.2 so that most likely you'll see Gingerbread or 3.0 rather then the hopes that the Epic will see either of those two.
Sprint and Samsung has got to remember that between Verizon, HTC and Apple there's going to be some stiff competition coming in January.
Please correct me if I'm wrong, but what guarantee do we even have that Sprint will decide to pass the certification of build 2.2.1? What happens after Sprint or other carriers reject that the new build is still flawed and it goes back to Samsung? Is there a time limit Samsung has with returning a flawed build back to Sprint to test or could that as well take more time? If the newest beta is time lagging for example, wouldn't Samsung be required to then fix the lag issue before Sprint pushes the update out?