Following LG Patent Deal, Microsoft Execs Taunt Google On Twitter

Boxing gloves pair red

Microsoft this morning announced that it has signed a patent licensing agreement with Android device manufacturer LG, its eleventh deal of the kind.

Microsoft says effectively 70 percent of all Android smartphones sold in the United States today are covered under its patent portfolio, not mentioning the fact that they’re also suing Motorola Mobility and NOOK maker Barnes & Noble over their Android devices.

Continuing a tradition that we hope will stand the test of time, Microsoft’s head of communications, Frank Shaw, took to Twitter to taunt Google.

First, Shaw tweeted “Hey Google – we are the 70% #anotherandroidlicense” with a link to their press release, and later said:

The second one is of course a bit disingenuous, since pretty much every player in this industry employs patents as weapons, will at some point, or wishes they were in a position to do so.

Shaw isn’t alone in his endeavor to try and get a response out of the Google camp, by the way.

Here’s Brad Smith, Microsoft’s EVP and General Counsel, tweeting:

And here’s Horacio E. Gutiérrez, Corporate VP and Deputy General Counsel, tweeting:

We love this stuff. We want more. Come on, Google, it’s your turn. Keep this going.

Update - no comment needed:


The Value Of The Bleeding Edge: Thoughts On A Nexus Tablet

nexustab

Just a few days after the Galaxy Nexus landed in the United States, it appears that Google’s next foray into the consumer electronics space may be a little bigger. According to Italian newspaper Corriere della Sera, Google’s Eric Schmidt has let slip that Google plans to throw its considerable weight behind a tablet within the next six months.

If you’re looking for details, prepare to be disappointed. Schmidt declined to mention anything concrete on the device: there was nary a word on specifications, features, or even potential manufacturers (though Motorola and Samsung would be prime suspects).

In fact, if the Google translation holds true, all we can really tell is that he expects things to heat up between Google and rival Apple.

That hasn’t stopped the rest of the blogosphere from (perhaps erroneously) referring to the nebulous machine as a Nexus tablet. While I admit that my heart goes aflutter at the mere mention of a new Nexus series device, I’m not sure that slapping the Nexus name on a tablet would do Google much good, especially if it turns out that they want to take on the iPad.

What strikes me as particularly odd about the idea of a Nexus tablet is that the Nexus brand has been meant from the beginning to put users right at Android’s cutting edge. Each new Nexus device debuted alongside a major Android update: Eclair debuted with the Nexus One, Gingerbread debuted with the Nexus S, and (as if I have to remind you) Ice Cream Sandwich recently launched with the Galaxy Nexus.

It seems to me that the driving idea behind the Nexus series of devices is that they aim to provide people with the cleanest, most up-to-date version of Google’s Android vision. And that’s great — as an Android nerd (among other things), I rather appreciate it. But when it comes to the mass market, would a strictly vanilla experience (even one that gets updated frequently) appeal to people?

I recently posted an opinion piece on why I didn’t want Samsung to “ruin” Ice Cream Sandwich, in which I mainly asked the company to let Ice Cream Sandwich shine as opposed to completely covering it up with their near-ubiquitous TouchWiz UI. Commentors agreed with me, but Philip Berne tweeted this at me:

MobileBurn’s Dan Seifert followed up with this:

They both had a point, and it got me to thinking: let’s say a Nexus tablet does indeed materialize during the next few months. What exactly does a (probably ICS-powered) tablet need to do to appeal to a wide audience? A constant stream of updates? An unencumbered UI? Love it or hate it, TouchWiz does indeed add a lot to the stock Android experience, and that sort of approach may be closer to what people actually want.

The Nexus line has always been about being on the bleeding edge, and the value of being on the bleeding edge is in the thrill of experiencing something new. Naturally though, not everyone will want to deal with the potential hiccups that could come with it.

Google seems to understand that the Nexus line hasn’t played terribly well with the non-techie audience, which explains the fun, people-oriented tone of their Galaxy Nexus commercials. Would it be impossible for them to spin the Nexus brand into something more approachable, more friendly to your less-than-geeky parents and friends? Of course not, but they couldn’t do it without risking some of the brand’s original audience. A Nexus-branded tablet could be risky no matter how Google chose to spin it.

That is, if it’s a Nexus tablet at all. Schmidt played those cards very close to his chest during the interview, and this talk of a Nexus tablet could turn out to be the work of a few bloggers with high hopes. But if Google truly intends to take to make a big splash in the tablet space, they’ll need a hook, and I don’t think the Nexus brand is it.


Samsung Releases Extended Battery Bundle (With Cover) For Your New Galaxy Nexus

Screen shot 2011-12-16 at 8.40.34 AM

The Galaxy Nexus is a beautiful phone, no doubt about it. That gorgeous 4.65-inch Super AMOLED Plus display paired with LTE support and a fresh build of ICS thrown in there for good measure is about as good as it gets. But the same things that make this phone great — its massive screen and LTE radio — are also the things that will leave you screaming at it at 4p.m. on a Thursday, when it’s completely dead.

But Samsung has prepared for this, launching an extended battery pack/cover bundle specifically for the Galaxy Nexus. It includes a Lithium Ion Extended Battery Cover, which is meant to offer extra coverage for your battery. A 2100 mAh extended battery is also included in the bundle.

Getting a battery life solution out to the masses early is a smart move by Samsung. Some of the biggest complaints about phones these days tend to revolve around battery life, especially when LTE is in the mix. The bundle costs $49.99 and is available now.


Samsung Releases Extended Battery Bundle (With Cover) For Your New Galaxy Nexus

Screen shot 2011-12-16 at 8.40.34 AM

The Galaxy Nexus is a beautiful phone, no doubt about it. That gorgeous 4.65-inch Super AMOLED Plus display paired with LTE support and a fresh build of ICS thrown in there for good measure is about as good as it gets. But the same things that make this phone great — its massive screen and LTE radio — are also the things that will leave you screaming at it at 4p.m. on a Thursday, when it’s completely dead.

But Samsung has prepared for this, launching an extended battery pack/cover bundle specifically for the Galaxy Nexus. It includes a Lithium Ion Extended Battery Cover, which is meant to offer extra coverage for your battery. A 2100 mAh extended battery is also included in the bundle.

Getting a battery life solution out to the masses early is a smart move by Samsung. Some of the biggest complaints about phones these days tend to revolve around battery life, especially when LTE is in the mix. The bundle costs $49.99 and is available now.


Google Granted Patent For Driverless Car “Landing Strip”

big

The age of driverless cars may still be years in the future, but to those playing a long game, that just means that work now will pay off even more later. Google is getting into the business of tracking and managing driverless cars, and while the technology actually steering and perceiving the cars’ surroundings will be undergoing lots of changes, some fundamentals of their interactions with the world can actually be explored today.

For example, Google has been granted a patent for a “landing strip”: a parking spot with special markings that help the car park itself, and then allow it to determine exactly where it is without relying on GPS or landmarks.

A smart parking spot has an air of inevitability to it that suggests it is one of those ideas that last. The patent is fairly specific, though: a visually-indicated landing strip, which in the illustrations is a banded area, would be stopped on by the driver. The car would detect that it had stopped on a landing strip, and would know to search the area for a second indicator, in this case a QR code.

The QR code would direct the car to visit a URL and, presumably, report itself as at location #382B319_g and awaiting instructions. The server would tell the car its exact location down to the inch, and any additional info the car might need: the locations of available parking spaces if the landing strip is at an airport, for instance, or local maps, navigational data, or rules. It could also push other information from local sources: live cameras, information about the location, and so on.

The title of the patent, “Transitioning a mixed-mode vehicle to autonomous mode” refers to this point in the process, after the person has parked or perhaps just driven over the landing strip, at which time the car would switch over to autonomous navigation.

It’s a neat process and there’s no conflict between the driver and the car. On the highway, for instance, things will be much more complicated: the humans will be watching that the car makes no mistakes and will be ready to grab the steering wheel if there’s an error. On the other hand, the car will be watching the human for mistakes, and will hit the brakes or warn the driver if there is danger. The landing strip is a more clear-cut handover.


An iPhone Lover’s Take On The Galaxy Nexus

1

You have to hand it to Google. They know that I prefer Apple products and have been generally critical of many Google moves in the past couple of years. And yet, they’re unafraid to give me their newest products to test out. To be honest, I’m not sure Apple would do the same. But I think this is a smart move on Google’s part. On one hand, they may get a negative review but they know that many will discount the negativity coming from me. On the flip side, if it’s positive: gravy train time.

Thus: my thoughts on the Galaxy Nexus. But before I begin…

Rather than do a full-on review — you’ve probably already seen plenty of those — and given that I now write an Apple-centric column for TechCrunch, I figured it was the perfect opportunity to continue my “An iPhone Lover’s Take…” series. For some background, here are my previous stories from the same angle on the Nexus One, the HTC EVO 4G, the Nexus S, a Windows Phone, and even the iPhone 4.

My colleague Jason Kincaid took a similar approach for a post a few weeks back, but did it from a slightly different angle — call it: An Original iPhone Lover Who Learned To Love Android Until Switching Back To The iPhone… Reviews The Galaxy Nexus. Oddly, he just had just switched back to the iPhone after years of Android use — but he says the Galaxy Nexus and Ice Cream Sandwich in particular may get him to switch back yet again. Meanwhile, GigaOm’s Darrell Etherington also looked at the Galaxy Nexus from an iPhone user’s perspective and ultimately decided the iPhone 4S was still the device for him. So I’m here to break the tie.

I’ve been using an iPhone since the day the first one launched in 2007. It is without question my favorite and most-used gadget of all time. Over that same span, I’ve tried about a dozen different Android devices ranging from the G1 to the Nexus S — the results have been decidedly mixed. I pretty much hated the G1, generally liked the Nexus One, thought the EVO 4G was more or less crap, and basically enjoyed the Nexus S. But none, in my mind, could touch the iPhone.

So what about the Galaxy Nexus?

I was given the device shortly before I took off for Europe a couple weeks ago. Given that it’s unlocked and I got a 3G SIM, I’ve been using it a lot — just as much as I’ve used any of the other Android devices listed above. For a few nights, it has been my primary device when I’ve been out and about. Unfortunately, I have not been able to test any sort of 4G network with it, so consider all of this a Galaxy Nexus 3G review.

First and foremost, the Galaxy Nexus is way too big. The 4.65-inch screen is nice when I’m sitting on my couch, but out and about it feels like I’m Zack Morris holding his Gordon Gekko phone. I’d consider myself to have average sized hands for an adult male, and the screen is so large that it killed several one-handed operations for me (especially since many Android apps use a top nav system). I’ll admit that for some apps, like Gmail, having a screen larger than the iPhone’s 3.5-inch variety is very nice. But 4.3-inch may be better. This is just too big.

While the screen is too big, I am happy that Google has finally decided to get rid of hardware menu buttons and go all-in on the screen. Previous Android hardware was always made worse by the decision to include fixed nav buttons along the button. With Ice Cream Sandwich, all these buttons can now be software-based. There isn’t even a home hardware button like the iPhone has anymore — it’s all software.

I like this. The iPhone home button wears down over time and it makes noise when you click it. (Of course, the Galaxy Nexus still has a wake/power button of the right side.) I hope Apple does something more inventive with the button if they choose to keep it in future iPhone hardware iterations. Perhaps a multi-touch top on the button that allows you to swipe between open iOS apps would make the continuation of the physical button worth it.

I also like the inclusion of an indicator light on the Galaxy Nexus. Both the Galaxy Nexus and iPhone have options to vibrate or give you audio cues to alert you to new messages, but if the phone isn’t on me, I often miss those. The light allows you to see if you have new message waiting without having to turn the screen on. This is one of the few things BlackBerry got right that Apple for whatever reason hasn’t bothered to mimic.

The rest of the Galaxy Nexus hardware leaves something to be desired. The iPhone feels like a completely and thoughtfully designed object. By comparison, the Galaxy Nexus still feels rather cheap and plastic-y. It’s not awful, but you’d think Samsung could do better at this point. Some people will like having the option to remove to the back to get at the battery, but the method for doing so remains a joke. You essentially have to rip it off. I feel like I’m peeling a nail away from a finger every time I do it — it’s that unpleasant.

The battery life itself on the device is very good. I felt like the Galaxy Nexus was lasting at least as long as the iPhone 4S on a fully charged battery, perhaps even a bit longer if some cases. Again, I didn’t try it on a 4G network, which is known to drain battery quicker. (I also haven’t had the battery discharge issues that some iPhone 4S users have been reporting since the launch.) But fear not, this is not the EVO with its temper-melting 30-minute battery.

The camera on the Galaxy Nexus is definitely worse than the iPhone 4S, both in megapixels (8 vs. 5), and in image quality. But the iPhone 4S is also a ridiculously good camera. The Galaxy Nexus is still a fine point-and-shoot replacement, in my opinion. The camera seems better than any other Android device I’ve used. One nit is that while there is a method to go right into the camera from the lock screen (just like iOS 5 has), it’s too slow if the camera isn’t previously running. You’ll hit the camera button and watch as the Android main screen loads and then the camera apps loads. This feels like more of a macro than a feature.

And let’s talk about Ice Cream Sandwich. The artist also known as Android 4.0 is very solid. There is no question that the software is much improved over previous iterations in terms of speed, but mainly usability. I really like things like the multi-task tray and some of the new widgets.

Unfortunately, the system still lacks much of the fine polish that iOS users enjoy. The majority of Android users will probably think such criticism is bullshit, but that has always been the case. I imagine it’s probably hard for a Mercedes owner to describe to a Honda owner how attention to detail makes their driving experience better when both machines get them from point A to point B. As a Honda owner myself, I’m not sure I would buy it — I’d have to experience it to understand it, I imagine. And most Android lovers are not going to spend enough time with iOS to fully appreciate the differences.

Still, if the Android team ever wants to convert (or at least convince) most iOS users, they still have quite a bit of work to do here. Then again, they probably don’t (or shouldn’t) care too much about converting iOS users over to Android. All the non-smartphone users out there remain the much bigger prize to go after (for both Google and Apple).

Other things that will sound like nits but drove me crazy with ICS included the constant focusing on text fields only to have to click again to get the keyboard to pop up. If I’m in a text field, I clearly want to type something. Why should I have to click again? This doesn’t always happen, but it happens a lot — particularly in third-party apps.

Another: why is there a separate app for Messaging and Google+ Messenger? Apple baked iMessage into their SMS app, why didn’t Google? If they’re worried about anti-competitive concerns, why would they bundle all the Google+ stuff into ICS to begin with? Similarly, why do Gmail and Email continue to be two separate apps? And why on Earth is the web browser not Chrome yet!?

The new People app social unification is nice — I love the big pictures. But my god Google needs help with their duplication/merging detection. One of my friends has four separate entries — one for his phone number, one for his Gmail/Google+, one for Twitter, and one for another email. Several others had three different entries. Most had at least two. Also, Google provides an option to link your Facebook account in Accounts & sync, but it does nothing. I’m sure this is due to the Google/Facebook fracas, but why include something in your OS that is completely broken?

Ice Cream Sandwich’s voice command functionality is a joke compared to Siri — but that may be changing soon, we’ll see.

In his write-up, Jason noted that iOS is still far behind Android when it comes to notifications, I have to disagree. I find Android’s notification tray to be far less useful than it is on iOS. For example, if I get three new emails, with Android, I just see that I have three new emails all grouped together. With iOS I can see at least some of the context. Same with Tweets. The size of the alerts in this tray also isn’t uniform in Android, so Facebook alerts seem more important with their huge logo.

I do like the ability to “clear all” in Android’s notification tray though. The iOS micro clear button remains a joke that badly needs to be fixed.

When it comes to web browsers, arguably the most important feature on any of these devices, there is no question that iOS still has a big edge here. I’ve seen arguments on both sides for why one is faster than the other — most recently, data today favors iOS — but just doing a simple use case test, mobile Safari kicks the ass of Google’s don’t-call-it-Chrome mobile web browser across the board. Some pages still refuse to render correctly on Android’s browser. And the ones that do cannot seem to get the simplest feature right: double-tap to zoom. You do it on Android and there’s a good chance you could end up looking at the middle of a random paragraph.

You’ll also still see a bit of lag in ICS when you do seemingly simple things like this. It’s still not as smooth as it should be. For the most part, ICS fixes many of Android’s performance issues, but there are plenty of times that you’ll still see stutters here and there.

And then there are the apps.

To be fair to Google, Ice Cream Sandwich is currently only on the Galaxy Nexus and it still hasn’t even officially launched in the U.S. But there’s a lot of work to do here. One app that I had on my Nexus S constantly crashes now on the Galaxy Nexus. And rather than quietly closing in the background, I get a nice big Windows-style pop-up that it has stopped running. Many other apps look fairly bad on the larger screen simply because they’re not optimized for it — again, something a wider release of ICS will hopefully fix.

The main problem I have with Android apps on the Galaxy Nexus/ICS remains the ones that are also available on iOS. When the apps exist on both platforms, it’s easy to compare them and the iOS version almost always wins — and often by a landslide. Take the latest version of Twitter, for example. It was just updated to run on both. On iOS it’s smooth, on ICS, there is noticeable stutter when scrolling. It’s much worse on Facebook Messenger and Facebook itself — no big deal, only the biggest app on both platforms.

The reason for the app differences between the two platforms remains a hot topic of debate. Again, all I know is what I see: app to app, iOS still easily beats Android in most cases. One counter-example, which I talked about on stage at LeWeb last week, is SoundTracking. I actually think their app is better on Android. But that has less to do with performance, and more to do with the fact that it can access hooks that iOS doesn’t offer, like background Spotify integration. Android developers should focus more on these benefits of Android and less on making their apps exact ports of their iOS ones. Something always seems to get lost in translation — often badly lost.

Now it just sounds like I’m focusing on the negative. It’s important to emphasize the fact that the Galaxy Nexus is without a doubt the best phone I’ve ever used that’s not an iPhone. And there is no question that it does certain things better than an iPhone — namely all of the Google apps and any third-party background/OS integration beyond Twitter, which is now baked into iOS 5. Google has also managed to just about match Apple in app quantity. This is all good — competition is good.

The next step that Google needs to take (or to help third party developers take) involves around app quality. Put simply: they need to create better tools for developers to use in order to take advantage of the strengths ICS offers. This won’t happen in 6 months, but it can happen if Google works at it.

After that, it’s the intangibles where iOS holds the huge advantage. And just like in sports, it’s not clear how well you can “teach” those. At some point, Google may simply have to acknowledge that iOS looks and feels better than Android because Apple’s entire fabric is woven with design, tight integration, and attention to detail. Google’s strengths are elsewhere; they should embrace that.

Google has done some very nice work here. Both the Galaxy Nexus and Ice Cream Sandwich are a new pinnacle of the Android platform. But in the end, it still comes down to something very simple: which device do I want to use day-to-day? Which phone do I reach for when I’m not doing a review? It’s still the iPhone. Without question.

Keep at it, Google.


Chrome Getting Native Gamepad, Webcam, And WebRTC Support In Early 2012

padchrome

It’s not always easy to tell when Chrome has been updated, and at any rate the changes aren’t always significant enough to even wonder about it. But a pair of features worth caring about are user-bound come early 2012, according to Google developer advocate Paul Kinlan, who spoke recently at the Develop conference in Liverpool.

The conference is focused on game development, so it’s no surprise that the features are also game-centric. First, there will be plug-and-play gamepad, webcam, and microphone support in Chrome, and second, the nascent real time communication protocol WebRTC will begin to be implemented as well. This opens the door for seamless video chat and conceivably OnLive-like gaming services.

It’s not as if there are already tons of games and applications waiting to take advantage of gamepads and WebRTC. And while it would extend the capabilities of Chromebooks, for instance, so it would extend the capabilities of any netbook or desktop running Chrome. Still, making the browser platform natively support peripherals is an important step towards making it less of an application layer and more of a primary OS layer.

Replacing the driver layer always introduces all sorts of complications, so it’s no surprise that this hasn’t been properly implemented yet. A passthrough from the OS drivers and device managers has been the standard, and this may take a while to supplant. But if it works, it works, and no one will care whether it’s Microsoft, Apple, Logitech, Adobe, Google, or Halliburton making their webcam work. All they want to do is video chat with their kids.

Kinlan also said that an OnLive-type streaming video/game service is in the works at Google, which should come as no surprise. Google + integration is almost a certainty as well: “Blank is playing Modern Warfare 3! Click here to watch. Click here to rent.” Naturally the hardest part of this service would be the licensing agreements, in which OnLive and others have a long head start. Servers Google has. It’s content they need.

“First quarter” is as specific as Kinlan got, and it’s fairly early to make those determinations anyway, so no doubt we’ll be hearing more when we are nearer the release date.


Chrome Getting Native Gamepad, Webcam, And WebRTC Support In Early 2012

padchrome

It’s not always easy to tell when Chrome has been updated, and at any rate the changes aren’t always significant enough to even wonder about it. But a pair of features worth caring about are user-bound come early 2012, according to Google developer advocate Paul Kinlan, who spoke recently at the Develop conference in Liverpool.

The conference is focused on game development, so it’s no surprise that the features are also game-centric. First, there will be plug-and-play gamepad, webcam, and microphone support in Chrome, and second, the nascent real time communication protocol WebRTC will begin to be implemented as well. This opens the door for seamless video chat and conceivably OnLive-like gaming services.

It’s not as if there are already tons of games and applications waiting to take advantage of gamepads and WebRTC. And while it would extend the capabilities of Chromebooks, for instance, so it would extend the capabilities of any netbook or desktop running Chrome. Still, making the browser platform natively support peripherals is an important step towards making it less of an application layer and more of a primary OS layer.

Replacing the driver layer always introduces all sorts of complications, so it’s no surprise that this hasn’t been properly implemented yet. A passthrough from the OS drivers and device managers has been the standard, and this may take a while to supplant. But if it works, it works, and no one will care whether it’s Microsoft, Apple, Logitech, Adobe, Google, or Halliburton making their webcam work. All they want to do is video chat with their kids.

Kinlan also said that an OnLive-type streaming video/game service is in the works at Google, which should come as no surprise. Google + integration is almost a certainty as well: “Blank is playing Modern Warfare 3! Click here to watch. Click here to rent.” Naturally the hardest part of this service would be the licensing agreements, in which OnLive and others have a long head start. Servers Google has. It’s content they need.

“First quarter” is as specific as Kinlan got, and it’s fairly early to make those determinations anyway, so no doubt we’ll be hearing more when we are nearer the release date.


Intel Itching To Work With Google’s Ice Cream Sandwich

intelsandwich

Intel hasn’t been able to make much of a dent in the smartphone or tablet markets, but they’re not about to give up just yet. ComputerWorld reports that Intel is working to make Ice Cream Sandwich-powered devices a part of their future.

The mobile space represents a huge opportunity for Intel, which is made all the more maddening because they’ve never really been able to crack it. Less than a handful of Intel-powered Android tabs ever saw the light of day, and most (like the Cisco Cius, which ran Froyo of all things) were geared heavily toward enterprise use.

Meanwhile, if you were to peer into the innards of nearly any smartphone or tablet on the market, you would likely see an ARM-based processor. It’s a reality that can elude some, as processors can bear ostentatious names like Snapdragon and Hummingbird that obscure the nature of their architecture.

Now, it looks as though Intel is about to roll their sleeves up and fight ARM’s onslaught. Intel showed off some frankly impressive smartphone and tablet reference designs at a developer event back in September, both of which ran on Intel’s Medfield plaftorm. The company has also promised that the first Intel-powered smartphone would see the a release sometime next year, so it’s apparent they’re beginning to get the lead out.

Given that Intel has their eye on both the smartphone and tablet markets, their apparent zeal for Ice Cream Sandwich makes complete sense. Ice Cream Sandwich is intended to be Google’s unifying OS, one that will bridge the experience gap between smartphones and tablets alike. If Intel can ensure that Ice Cream Sandwich will run without a hitch on whatever mobile chipset they go with, they stand a serious chance at popping up in your next tablet.

For the time being though, Intel is stuck playing the waiting game. According to an Intel spokesperson, Ice Cream Sandwich “includes OS optimization for x86,” so the actual work of getting ICS running may not be too difficult. Still, a concerted effort can’t begin they actually get their hands on the software, so Intel still has a little while to go before they get cracking.


Google Promises Android 4.0 For The Nexus S, “Theoretically” For Gingerbread Devices, Too

android-ice-cream-sandwich

With a few hours of Ice Cream Sandwich familiarity under our belts, the looming question in everyone’s mind is: when will the Android 4.0 update roll out to existing devices? Well, nobody knows. But after talking with a few authorities on the subject, we at least have a few hints.

Google’s Android Product Manager Gabe Cohen and Android User Experience Director Matias Duarte have promised Ice Cream Sandwich for the Nexus S, and hinted that all other Android 2.3 Gingerbread devices should “theoretically” get ICS as well. Here’s the official quote: “Currently in the process for releasing Ice Cream Sandwich for Nexus S. Theoretically should work for any 2.3 device.” According to Engadget, there still isn’t a clear plan for the Nexus One.

HTC has decided to rest heavily on the fence for this one, saying that they do hope to release ICS to the masses, but will have to figure a way to lay their Sense UI on top of it first. Just like Cohen and Duarte, HTC refuses to give a timeline.

In my quest to dig up some answers, I decided to reach out to the big four carriers as well. T-Mobile never responded, while the rest had either no comment to give, or no information regarding the ICS update schedule.

Many owners of Froyo devices purchased early this year are still waiting on Gingerbread, so hopefully the carriers and phone makers have a more efficient plan for Android 4.0.

But I wouldn’t bet on it.


Company: Google
Website: google.com
Launch Date: July 9, 1998
IPO: NASDAQ:GOOG

Google provides search and advertising services, which together aim to organize and monetize the world’s information. In addition to its dominant search engine, it offers a plethora of online tools and platforms including: Gmail, Maps and YouTube. Most of its Web-based products are free, funded by Google’s highly integrated online advertising platforms AdWords and AdSense. Google promotes the idea that advertising should be highly targeted and relevant to users thus providing them with a rich source of information....

Learn more

Get Adobe Flash playerPlugin by wpburn.com wordpress themes
13 visitors online now
3 guests, 10 bots, 0 members
Max visitors today: 21 at 12:32 am EDT
This month: 50 at 05-07-2012 02:31 pm EDT
This year: 63 at 01-28-2012 07:06 am EST
All time: 111 at 12-05-2011 11:10 am EST