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.
Earlier today, Engadget posted a pretty sensationalist article (now deleted) implying that Gingerbread OTA updates are being streamed down to Nexus One device owners. Since I haven't seen a single confirmation yet, I grew more and more skeptical. To put an end to all rumors, Google's own Reto Meier just sent out a tweet refuting any OTA rumors and putting the Gingerbread update timeline as "in a few weeks":
And so the wait begins.
As is traditional following the leak of a new ROM dump, developers have already set to work porting the novel Android flavour to other devices. As he did with the Desire HD ROM, XDA-developers' eVil D: has stepped forward to provide a working port of yesterday's HTC Glacier/myTouch 4G ROM to the Nexus One. Cautioning that he "may or may not support this", eVil D: goes on to describe the semi-functional state that the port is currently in:
What doesn't work:
Wifi UMA calling = bootloop (you've been warned!)
Common Sense (this is a VERY EARLY build)
SDEXT (512mb) partition *Use clockworkmod or RA 1.9.0+
AndroidCentral got the ROM running on their own Nexus One, and their screenshots provide a good insight into the "Espresso" Sense UI of the myTouch 4G itself.
We received a tip in the wee hours of the morning that we managed to miss until now, despite its overwhelming awesomeness. In short, it's a video demonstration of a Senseta rover running with custom hardware and controlled by a Nexus One, although it looks like it will run on any Android device with Bluetooth.
The combination of Android and the simplified hardware allows for a simpler setup that saves weight, and in a little bugger like this, any lost weight counts for a lot.
This is what happens when you try to one-up the open-source community. Just when we were beginning to think HTC Sense might have come up trumps with a real killer feature in their Fast Boot, CyanogenMod creator Steve Kondik's right there with a cheeky "Yeah, CM6 "does" too :)". Tweeting that the feature will be committed to the CyanogenMod source soon (possibly with the arrival of version 6.1), Cy noted that the Nexus One would likely last in this hibernation state for about a week.
Well, it looks like that shortage of AMOLED screens people have been talking about has finally started to affect more devices than just the Nexus One. This snapshot of a Verizon internal memo reveals that the Droid Incredible will, in fact, be making a change from AMOLED to S(uper)LCD:
Basically, this means that the quality of the Droid Incredible's screen is going to go down a little bit. While SLCD is still definitely high-end smartphone worthy (It's what the HTC Desire has in the U.S.), there will be a noticeable difference.
Ever since HTC released its version of Google’s Nexus One, the Desire, people have wondered why Google haven’t given the N1 any FM Radio capability. The HTC Desire uses the same Broadcom chipset as the Nexus One, so why does one have FM Radio and the other doesn't?
Asked about this at their I/O conference, a Google rep said the company had no plans to bring FM Radio to the Nexus One and told everyone to turn to the hacking community for support, as there are a number of custom ROMs out there for the device.
The latest version of the popular CyanogenMod has been released, offering bug fixes and various improvements over the previous version.
Available to download for the Nexus One, Droid, Dream and Magic, CM 5.0.8 sees some great speed increases on older devices that were still a little sluggish under the previous version.
A particularly noticeable addition to 5.0.8 is ADW Launcher, a home replacement app, which is now included in the ROM by default. Accompanying this is 720p video recording support, which we first saw appear in CM5.0.8-test3 earlier this month.