Nexus One
Latest
Nexus One's multitouch confused more easily than Droid's?
Thought all multitouch-capable displays were created equal? Think again -- Android and Me has posted a rather fascinating (if not somewhat depressing) video showing a demo multitouch app created by a game developer who'd grown suspicious after running into all sorts of trouble getting the feature to work the way he wanted on the Nexus One. First up, the Droid handles the demo with aplomb -- two thumbs are recognized smoothly and consistently. Next, though, the Nexus One gets confused after a while and starts registering presses at the wrong corners of the on-screen box formed by the placement of the thumbs. There's always hope that this could be fixed with a firmware bump, but that hope looks to be in jeopardy from language posted by a Google engineer in the official Android dev forums: "...this is how the touch screen hardware on the Nexus One works (which is essentially the same screen as on the G1 and myTouch). The Droid has a sensor from a different manufacturer, with different behavior. Other phones will likewise have different sensors." In other words, Google seems to think that HTC's just using a lower-quality sensor than Motorola is. That's good news for Droid owners, we suppose -- but with game development on Android still something of a non-starter, hardware issues like this keep fragmenting the user base and preventing big-name developers from jumping in and betting on the platform. Follow the break for video proof of the wackiness.
Nexus One coming to Verizon March 23rd?
What better way to start your Saturday afternoon than with another Nexus One release rumor. Without further ado, today we've got whispers care of Neowin that the recently-FCC'd CDMA device is launching on Verizon's network March 23rd, perfect timing for the beginning of CTIA. And while that fits pretty neatly into that initial "Spring 2010" launch window, there's really no way for us to corroborate at this point other than just taking their word for it. You can wait diligently, can't ya?
How would you change Google's Nexus One?
It hasn't quite been out (in public hands, anyway) for two months, but Google's Nexus One has managed to grab the world's attention and focus it squarely on Android. Specs wise, it's not the superphone that many had expected, but it's certainly delightful in its own right. For those who have sprung for one, we're bubbling over in anticipation to hear how you'd change it. Would you have snuck an overclocked processor in there? Would you have ditched the trackball for a sensor pad? Do you wish it were available on more carriers? Is the call quality up to snuff? Look -- there's a better-than-decent chance that you threw down some serious bills on this, so don't hold back. The Nexus Two just won't be the same without your pair of pennies.
Nexus One hits FCC again, this time in CDMA trim
Remember how we figured out that an AT&T 3G-equipped Nexus One had stumbled its way into FCC certification not long ago? Using the same logic -- mainly label shape and model number -- we can safely say that this latest version to get approval is the dual-band CDMA variant that's almost certainly destined for Verizon within the next few months. There's not terribly much to see in the filing, but hey, take solace in knowing they've cleared this crucial bureaucratic hurdle (of course, Verizon's infamous internal testing is another bureaucratic hurdle altogether). [Thanks to everyone who sent this in]
Flash 10.1 might just not be a battery hog on Android
Looking to fight an apparent outbreak of FUD, Adobe's Flash evangelist Mark Doherty has posted some hard numbers (and accompanying video) on the effect Flash 10.1 has on the Nexus One -- and put simply, it really doesn't appear to have much effect at all. To back up his cause, Doherty plays a 17-minute embedded video in the full YouTube site then pops over to Android's built-in battery use utility, which indicates that only 6 percent of the juice has gone to power the browser (of course, leaving the screen on to watch the video is another story altogether). He says that the company's tests suggest they can get about three hours of H.264 playback over WiFi, which is theoretically enough to watch a movie or two; obviously the proof is in the pudding here, but this is a promising sign that these guys have taken battery optimization very, very seriously for this mobile push. Video after the break.
HTC Desire ROM shoehorns HTC Sense and Flash 10.1 onto the Nexus One
Want some of that colorful, homescreen-juggling, Android 2.1 Sense UI that HTC has prepped for the HTC Desire? Well, the previously promised hacked ROM is ready for your Nexus One's consumption. It's in alpha right now, so install at your own risk, and does indeed support Flash 10.1, so also beware of the risk of browsing the real internet. What more danger, excitement, and grassroots handset support could you possibly want out of life? Hit up the source link for the full instructions, video of the ROM in action is after the break.
Sony Ericsson CEO: Google asked us to build the Nexus One, we refused
Aw, why don't these CEOs say stuff like this in press conferences? Sony Ericsson's head Bert Nordberg has shared with Swedish publication Sydsvenskan the rather salacious news that his company was asked to build the so-called Google phone before HTC... and it turned down the opportunity. Fearing brand dilution or something equally crazy, Nordberg states that Sony Ericsson is committed to building only its own-branded hardware and will not be a subcontractor to anyone. Haughty words from a company whose own Android device is still a good couple of months away from hipsters' pockets, but we're sure Bert knows best. After all, it's not like HTC got a ton of positive press and brand awareness out of its partnership with Google, and it's exceptionally clear that SE doesn't need a dime of additional revenue. Oh, wait. [Thanks, Michael N]
HTC Desire ROM makes Sense on the Nexus One
It's no secret that the HTC Desire is the exact same hardware as the Nexus One with a Sense-based Android build on top of it, so it shouldn't be any surprise that an enterprising hacker has already started porting the Desire's ROM over to Google's baby. Interestingly, the system file is a little too big for the Nexus One's internal storage, so some rearranging was necessary, and not everything works yet, but it's a start -- and apparently Flash 10.1 is included and enabled, so this one should be a hot ticket when it's released. [Thanks, Thalib]
iPhone 3GS pitted against Nexus One in 3D frame rate test (video)
We'd already seen first hand what kind of GPU improvements Apple made with the iPhone 3GS (in comparison to the iPhone 3G, anyway), but if you've ever wondered how Cupertino's latest stacked up against Google's Nexus One in the graphical department, your answer is just a click away. The technical gurus over at Distinctive Developments set out to determine which handset was capable of pushing more frames per second when really taxed, and through a series of pinpoint tests, they discovered that the Nexus One (in general) lagged behind. The reason? Reportedly, Google's phone isn't using Neon floating-point optimization, but if it did, the scores you'll see just past the break could be quite different. Hey Mountain View, you getting all this?
New Nexus One ROM leaks, fixes more radio issues?
Remember that hand-waving trick that got a Nexus One to give up the 3G ghost way, way too easily? Well, we don't want to pop the champagne just yet, but there's a new non-over-the-air firmware update floating around that includes yet another radio bump among its sundry features, suggesting HTC isn't quite done yet tuning this thing to get proper HSPA without freaking out from time to time. Whatever this update is, it may never see the official light of day in its current form -- it includes Google Maps 3.4, for one thing, while Google's already gone ahead and upped the ante to 4.0 for Buzz support -- but at least it seems engineers aren't done trying to make this thing work properly. [Thanks, b3ast]
Nexus One 3G problems persist after update -- is it a design problem?
Looks like someone at Google should fast forward those Nexus One design videos to the radio integration portion and figure out what went wrong, because it seems like the 3G coverage problem still hasn't been fixed, even after that last big OTA update. What's more, many in Google's support forums are noting that the phone will drop a weaker 3G signal merely when held by the bottom, as the video below clearly shows. Oops. We're not at all sure what's going on here, but we're hoping this issue can yet be solved with a software patch -- things are going to get messy if this is purely a hardware issue. [Thanks, Geathan]
Google starts live phone support for Nexus One owners
Google readily admits that its Nexus One customer support at launch was lacking. However, the Goog says that it's committed to improving the experience as it blazes a path into the world of consumer handset sales. Today, more than a month since the launch of the Nexus One, Google is offering owners access to a real live person via 888-48NEXUS (63987). The new support line is operational from 07:00am to 10:00pm PST and augments Google's support forums, FAQs and email support. Unfortunately, Google's live support line seems limited to status and shipping issues -- for live tech support you'll still have to call either HTC customer care number or T-Mobile depending upon the issue. And of course, the whole thing changes if you're an international user. As convoluted as it all sounds, an unamed Google spokesperson still claims that "live phone support from Google, combined with an optimized on-line support experience, enables a superior Nexus One customer experience." Sure it does: the average consumer just loves looking through on-line forums and FAQs to solve issues before picking up the phone to complain. [Thanks, Phil L.]
Google's Nexus One 'equipment recovery fee' slashed to $150, still a pain
So the good news here is that Google appears to have heard the cries for help, having taken a chainsaw to its brutal $350 "equipment recovery fee" that had been lumped on top of T-Mobile's $200 ETF for subsidized Nexus One contracts canceled in the first 120 days. The bad news, though, is that it still exists at all -- a hairy precedent for an industry being watched with eagle eyes by the FCC right now. The company has knocked $200 off the fee, bringing it down to $150; in other words, if you break your contract, you'll pay the same ETF that Verizon now charges on its "advanced devices." Whether that was a deliberate move to let 'em say that they're no more expensive than Verizon is unclear, but let's be honest: $350 is extreme, $550 was highway robbery. At least we're going in the right direction.
Google working on voice translator phone, redefining synergy
Okay, so Google has this expansive online translation service, which we all know, use, and sometimes even love. Google also has its own branded phone, with a voice recognition function that we frankly adore. So what's a brave new age company with bottomless pockets to do but try to splice the two together into some kind of omnilingual instant translator? Speech-to-speech translation -- long the exclusive plaything of fanciful sci-fi writers -- is said by Franz Och, Google's head of translation services, to be a viable possibility within a measly couple of years. The Mountain View approach to overcoming the inherent problems of variable pitch, tone and accents in speech will be to use each person's phone to accrue data on his or her linguistic idiosyncrasies, so that the more the phone's voice recognition is used, the more accurate it becomes. Sounds tres bien to us.
Watch Nexus One get built, then beaten mercilessly
This might be the best entry yet in Google's Nexus One video series. Today's double feature is marked by the testing and manufacturing of the device, and while the all-white facilities and assembly lines can be interesting in their own right, we love nothing more than seeing just how Google and HTC stress test its labor of love. Watch it dropped, slammed, bent, poked, and detonated -- okay, maybe not detonated, and we unfortunately don't get to see any phones crack, but it's still good fun. The big game's not on yet, so give yourself a few minutes and hit up the two short videos after the break.
Engadget Podcast 182 - 02.07.2010
What do three bloggers huddled around microphones in frigid locales across the country have on 22 of America's beefiest athletes gathered on the field in Miami? An iPhone app. Oh, actually, no. But Josh Tops, Nilz, and P-Mill most certainly comprise the universe's largest repository of JooJoo insight. That's worth something, right?Hosts: Joshua Topolsky, Nilay Patel, Paul MillerProducer: Trent WolbeSong: Disco Rehab - KidsHear the podcast01:22 - Nexus One gets a software update, enables multitouch (updated with video!)05:00 - Motorola Droid gets official multitouch support -- in Google Maps, anyway14:34 - Nook firmware 1.2 ready for download now (Update: video!)20:05 - Joojoo tablet now in production, will support full Flash at launch30:15 - Acer not making a tablet, will focus on ultra-thin laptops42:20 - Former Microsoft VP Dick Brass weighs in on why Microsoft 'no longer brings us the future'45:00 - Microsoft responds to Dick Brass: 'We measure our work by its broad impact'48:20 - Steve Jobs compares iPad battery life to Kindle's: 'You're not going to read for 10 hours' (video)48:30 - Hachette Book Group also pulls away from Amazon48:35 - Amazon pulled Macmillan titles due to price conflict -- confirmed (update: they're back!)51:45 - Verizon advertising says Droid is for men, Pre is for women (video)58:09 - We're turning comments off for a bit59:00 - Commenting on Engadget: a human's guide Subscribe to the podcast[iTunes] Subscribe to the Podcast directly in iTunes (enhanced AAC).[RSS MP3] Add the Engadget Podcast feed (in MP3) to your RSS aggregator and have the show delivered automatically.[RSS AAC] Add the Engadget Podcast feed (in enhanced AAC) to your RSS aggregator.[Zune] Subscribe to the Podcast directly in the Zune MarketplaceDownload the podcastLISTEN (MP3)LISTEN (AAC)LISTEN (OGG)Contact the podcast1-888-ENGADGET or podcast (at) engadget (dot) com.Twitter: @joshuatopolsky @futurepaul @reckless @engadget
Nexus One video series, part two: Google schools us on OLED displays
The first installment of Google's fancy Nexus One design series focused on the sound quality of the device, and on the overall design. Well, part two is here now, and this time, we get to watch while HTC project manager Tomasz Hasinki and Android software engineer Romain Guy give us the goods on the Nexus One's OLED display and the interactive, 3D framework. We're expecting a couple more videos in the series, so grab a very tiny bowl of popcorn (it's pretty short) and check out the video, which is after the break.
The Flash saga continues: Adobe responds to charges of "laziness"
Kevin Lynch, CTO of Adobe, has posted the latest riposte in the ongoing fencing match between Apple and Adobe concerning the lack of Flash support in Apple's portable products, including the iPad. Apple's latest word on the subject reputedly came from Steve Jobs himself at the recent Town Hall meeting with Apple employees, where he characterized Adobe as "lazy," condemned the plugin's poor performance on the OS X platform, and predicted a future where HTML5 would supplant Flash. Presumably in response to those comments, Adobe's Lynch has argued in favor of Flash, citing the plugin's ubiquity, flexibility, and Adobe's commitment to "focus on enabling our customers to do their best work, and helping them reach people effectively and reliably around the world across operating systems, browsers, and a variety of devices." Lynch acknowledges the rise of HTML5 video in his post, but he notes that he sees the two technologies as co-existing rather than "one replacing the other." He also claims that since no standard implementation of HTML5 video exists, widespread adoption of HTML5 in place of Flash would lead us back to the "dark ages of video on the Web with incompatibility issues." He also re-affirms Adobe's commitment to bring Flash 10.1 to mobile platforms like the Nexus One, and he claims that 10.1 provides enhanced performance across a variety of platforms. His claim is true -- our own testing showed substantial improvements in Flash 10.1's performance on OS X -- but whether those improvements are enough to enable it to run well on iPhone OS is another story. What's most interesting about Lynch's post isn't within the main body of the post, but rather in the comments that follow. Read on to find out more. [Via The Register]
Google waxes poetic on Nexus One's design in video series, new docks shown off
Curious about the bright minds behind the OLED-wrapped, Android-powered Snapdragon in your pocket? Google's just posted its first in a series of videos about the Nexus One's magical journey from concept to production, and this particular episode calls in Mountain View's own Erick Tseng alongside HTC project manager Tomasz Hasinski and Lloyd Watts of Audience, which provided the phones dual-mic noise reduction tech. Don't expect too much depth here -- the entire video's only four minutes long -- but after Erick talks about the Nexus One's unprecedented fusion of bleeding-edge hardware and software design, we get to hear a little bit about HTC's selection of soft-touch materials and a large display for the device and Audience's involvement in improving voice quality before getting a super-brief glimpse at three docks. One of them is already available -- the desktop dock -- but the other two appear to be a standard desktop dock with an integrated spare battery charger and the nav-friendly car dock on the left and right, respectively. The video gives no clues when we might actually see these available for purchase -- but since they've finally shown them off here, it can't be long, right? Follow the break to check out episode one in full.
Motorola Devour spotted in the wild, sized up against a Nexus One
While just recently made official, there have been plenty of Motorola Devour leaks over the years (er, months) to keep us occupied. This latest one has the aluminum colored phone sized up in bokeh-filled and yet surprisingly small, compressed and grainy shots -- as if Mr. Blurrycam is holding up a nice, low aperture DSLR lens to his RAZR's sensor. Oh well, it's the thought that counts. What's particularly helpful here is this comparison shot with the Nexus One, which shows the Devour to be a good bit larger, despite its significantly smaller screen size. Size isn't everything, of course. [Thanks, Phillip L.]
