Early this morning (or late last night if you want to get technical), Samsung made its quarterly earnings call, and the company's mobile division is doing quite well - profits are up 38%, thanks in large part to the Galaxy S line of phones.

Samsung managed to sell over 10 million Galaxy S handsets in 2010, comprising roughly a third of all the manufacturer's smartphone sales. Given the Galaxy S's global launch along with its premium hardware and fair pricing, it's no surprise that device has been a big hit.

A few weeks ago, Samsung USA tweeted that Froyo updates for the Galaxy S phones are being delayed due to further testing. Then, just 4 days ago, AndroidSPIN reported that the Vibrant update (if not others) wasn't rolling out so that the Vibrant wouldn't steal the Vibrant 4G+'s thunder. And now the saga continues, as a new anonymous source has stepped forth to clarify the issue.

We won't lie - it's a slow news day in the world of Android. And with all the bad press Samsung's been getting today over an alleged filing of a class-action suit regarding the Froyo update on US Galaxy S phones, we're going to stay on the lighter side of things (for now).

It doesn't seem like it, but just a year and a few days ago, Google made available the first handset to bear the Nexus name - and what a long way we've come since. When the Nexus One was released, there were cries of "iPhone killer" and of Google entering the handset arena in direct competition with Apple. While the latter assertion remains debatable - the first does not. The Nexus One was a near-total commercial failure next to the iPhone 3GS, and even the original Motorola DROID ate the Nexus One for breakfast in terms of sales.

If you were one of the early adopters of the Samsung Nexus S, chances are you have been plagued by the highly obnoxious reboot syndrome experienced during daily phone calls. Upon making or receiving a phone call, the phone will suddenly and unexpectedly go black and reboot for no apparent reason. Up until recently, Nexus S owners have felt ignored by Google in regards to this issue. Previously, Google has qualified their negligible stance on the issue with claims that the issue was not with Android 2.3 Gingerbread, but instead Samsung's fault because of the hardware itself.

As promised, Google's Samsung-made Nexus S went on sale today at 8 a.m. at Best Buy stores across the United States (online sales start at 8 a.m. EST). Google's flagship phone - the first to natively run Android 2.3 - retails at $199.99 with a 2-year T-Mobile contract or $529.99 unlocked and without a contract. To promote the release of the phone, Best Buy is offering free overnight shipping if you choose to buy this phone online.

T-Mobile UK is certainly digging itself into a ditch on this one, and seriously pissing customers off in the process. You can't really blame people for being upset: after promising the Froyo update for Samsung Galaxy S owners by November 30 via FOTA, then reiterating just two days ago that the update was ready to roll out, they've now pushed it back at least a week. Turns out they're also not going to be able to do it over-the-air, either - rather, it's going to be installed with Samsung KIES instead.

We have good news and bad news (x2), world. The good: the first CM6.1 build for the Samsung Galaxy S has been released. The first (and worst) bit of bad news: at this point, it looks like it's for the GT-i9000 only, and not the US versions of the SGS (though I'm no dev, so I'm not positive). The other bad news: this is apparently a very bug-laden release ("Holy crap, it's full of BUGS!").

We have good news and bad news for Samsung Galaxy S owners. The good: the Froyo update source code released a few days ago is now officially being rolled out by Samsung. The bad news: they're starting with the Nordic countries... then "gradually" moving across Europe, Asia, North America, Africa, and everyone else.

The word "gradually" isn't exactly encouraging, and neither is the fact that North America is towards the end of the list.

Galaxy Not-So “S”

Is your Galaxy S a little laggy (experiences stutters, delays) at times, even on Froyo? It’s not your imagination; your phone’s internal storage is probably the culprit, and LagFix addresses the problem quite cleverly, helping you put the “S” back in your Galaxy.

As you probably know, Galaxy S phones boast either 8GB and 16GB of internal memory. Pretty hefty for an Android phone (the most spacious available, in fact).