Android Tablet Update

Android developer Jean-Baptiste Queru, or JBQ as he’s so lovingly called, has announced today that Android 4.0.4 is finally being pushed into the Android Open Source Project.

According to JBQ, Android 4.0.4 features “a few hundred changes over 4.0.3,” and it “matches the update that has been sent to a few devices since yesterday” (more on that below). As previously mentioned by Google, “files related to CDMA devices have not been tested in the context of AOSP.” There’s no solid timeframe for when 4.0.4 will reach all of the various Google Experience Devices out there, but some devices are already seeing the update.

The WiFi version of the Motorola Xoom has already been pushed the update, and an update file for the Nexus S has made available online.

That’s right, after months of waiting for Google to finally get their act together, an Android 4.0.4 update file for the Samsung Nexus S has finally been uploaded to Google’s servers, ready to be manually flashed over the botched update to Android 4.0.3.

Coming in at just 18MB, today’s update for the Nexus S is meant strictly for flashing over Android 4.0.3. It has been confirmed to work on both the i9023, and i9020-T (the T-Mobile Nexus S variant). There’s good reason to believe 4.0.4 should hit be available as an over the air update sooner than later, but if you don’t want to wait to receive it on your stock Nexus S, you can download it directly from Google now.

According to those who have successfully flashed the update to 4.0.4, it runs much smoother than 4.0.3, and features quite a few big fixes to well documented problems.

To check and see if your Xoom is ready for the update, simply head to Settings > About tablet. For GSM Nexus S users, check XDA for more info.

I’ve been running CM9 nightly builds on my Nexus S for quite some time now, but I may revert back to stock to see if the update fixes any major problems. Let us know if you’ve given the update a shot.

Update: Google just announced that Android 4.0.4, Ice Cream Sandwich, is rolling out to mutiple devices. The latest update includes “stability improvements, better camera performance, smoother screen rotation, improved phone number recognition and more.” Some devices are seeing Ice Cream Sandwich for the first time, while others are receiving updates from previous versions of Android 4.x.

More devices will be supported soon, but the first wave of devices includes:

• UMTS/GSM Nexus S
• Xoom WiFi
• HSPA+ Galaxy Nexus

Word on the street is that Google will start rolling out the Android 4.0 update for the Nexus S and Nexus S 4G within the coming weeks. This new information comes from one of Engadget’s trusted sources which we assume has provided accurate information in the past.

As Dustin pointed out a few days ago, Google did push out an Android 4.0 update for the T-Mobile (i9020-T) Nexus S in December which was quickly pulled due to a number of bugs. We’re hoping that Google has finally been able to sort things out and will be able to deliver a stable update before the end of March.

Will the Android 4.0 update for the Nexus S and Nexus S 4G restore your trust in the Nexus brand or will you consider an OEM branded phone the next time you make a purchase?

Time, and time, and time again, I’ve been known to sing the praises of Google’s Nexus series devices, because they are updated directly by Google. Which should mean fast, consistent updates to the latest version of software Google is working on (or at the very least, a fully functioning device). Right? As a large group of Reddit users have been discussing for the past day, wrong.

Back in October of 2011, Nexus One owners were given quite the shock when it was revealed that the first Pure Google Experience device would not be updated to Android 4.0, Ice Cream Sandwich. Less than two years after it had been released, it was already being abandoned by Google. Consumers were being abandoned by Google.

Fast forward to now, and Nexus S owners are facing a similar problem. An update to Android 4.0 was being rolled out for the T-Mobile (i9020-T) Nexus S, until some battery life issues prompted Google to put the update on hold. That was in December of 2011. Anyone who received the update could be faced with any number of bugs. Anyone who didn’t receive the update is likely wondering what the hell is going on. Google has not issued any comments on the situation.

Despite being advertised as the phone for “Android-powered players who want the latest Google Apps and OS updates as soon as humanly possible,” Sprint’s Nexus S 4G, and AT&T’s Nexus S for that matter, have not received any information about Android 4.0 at all.

I use a T-Mobile Nexus S, and I thought I was one of the lucky ones to receive the update shortly after it was announced. I couldn’t have been more wrong. After a good couple weeks of use, my phone had reached the point of being unusable. Ice Cream Sandwich was a disaster. Nine hours of battery life on low to moderate usage, when I used to get over 24 (!!!) on Android 2.3, Gingerbread. A ton of apps didn’t work. I was constantly getting storage error messages. And probably the thing that infuriated me the most, the camera data had been corrupted. To this day, even after rooting my device and trying both MIUI and CyanogenMod 9, my camera doesn’t work. It worked fine before my phone was updated to Android 4.0.

Unfortunately, Google’s actions toward the issues and problems surrounding the update to Android 4.0 aren’t new. Many users, like our own Taylor, experienced issues with their Nexus S randomly rebooting on Android 2.3. It took nearly two months for Google to release an update that remedied the problem. Which means that for two months, a good portion of Nexus S users found their device practically unusable. And there was nothing they could do about it.

At this point, I find myself wondering, would Samsung have fixed an issue like this sooner on a TouchWiz device? Would HTC come to my rescue and fix my broken camera if my phone was running some Sense slathered version of Android? The Galaxy S II is already being updated before the Nexus S (there goes the whole ‘Nexus devices get updates before anyone else’ thing), so maybe they would have.

Instead of seeing my device updated with the latest version of Android and enjoying a bug-less build of vanilla Android the way it was meant to be, much like thousands of other Nexus S owners in the world out there, I’m left feeling abandoned and thrown away. Why should I buy another Nexus device again? There’s other ways to use a stock Android device. And besides, maybe third-party skins aren’t so bad. I’m going to have to go with Reddit on this one, “FUCK YOU GOOGLE.” I won’t be buying a Nexus device again.

After much hoopla Google Wallet finally launched on the Nexus S last September, but it was only available on Sprint’s version of the phone and not T-Mobile’s. Then when Verizon announced their Galaxy Nexus, it was soon discovered that they would not support Google Wallet. Verizon claimed that Google Wallet “needs to be integrated into a new, secure and proprietary hardware element in our phones” and they were continuing their commercial discussions with Google on the issue.

Thanks to a recent app update, Nexus users on AT&T and Verizon can now install Google Wallet directly from the Android Market. Many users previously obtained a hacked copy or side-loaded it onto their device, but now they can have the comfort of getting the latest official version from Google.

AT&T users with the Nexus S or GSM Galaxy Nexus just need to search for Galaxy Nexus and install it. Those devices are recognized as supported in the Market and it’s a 1-click isntall.

Google Wallet Google Inc. MARKET QR POWERED BY APPAWARE

For Verizon owners of the Galaxy Nexus, the process takes a few extra steps. They need to visit the Android Market website from their browser and then trick their device into installing the official app. It might sound like a little much, but it only takes around one minute to complete.

1. From your phone open the browser and head to http://market.android.com. (Tip:  You may want to clear data and defaults on browser and Market before doing this.)
2. Search for “Google Wallet.” (If your browser prompts you to open the Market, don’t. Just stay in the browser.)
3. When the results come back, tap on the Google Wallet icon.
4. Tap the “Install” button from within the browser and then sign into your Google account. (Again, this is all from the browser, not the Market app.)
5. Once you have signed in, you should be redirected back to the Market page in the browser.
6. Obviously, you will not have the option to install there since the VZW Nexus is not supported.
7. Tap the back button until you are prompted for the Market or Browser again, this time choosing the Market.
8. The Android Market should open to the Google Wallet page with an option to install.

If it doesn’t work right away, just sign out of the Android Market website from your browser and try the steps again. I tried this on my Verizon Galaxy Nexus and it worked on the 2nd try. Previously I had side-loaded an older version of Google Wallet, and the install updated it to the latest version with no problems.

We don’t have a Nexus S or GSM Galaxy Nexus on T-Mobile to test this trick out, but hopefully it works on that device as well. If you happen to have one on hand, let us know if you were able to install Google Wallet from the Market.

At least AT&T is now allowing Google Wallet on some Android phones with NFC, and hopefully Verizon is close to reaching an agreement with Google.

Nexus S users are currently enjoying their update to Android 4.0, Ice Cream Sandwich. The new UI and features are awesome, but there is one little thing last year’s Nexus was missing – Face Unlock.

While some consider Face Unlock to be a gimmick, others find it to be one of the coolest features in ICS. It was only a matter of time before developers were able to make this feature possible for the Nexus S. Some members of the Android Central Forums have gone ahead and snatched Face Unlock from the Galaxy Nexus and created a ROM for all the brave flashers out there.

As always, there is the accustomed disclaimer. These are AOSP custom ROMs, and flashing such may void your warranty and/or affect your device’s functionality. Those brave users who choose to go this route do so assuming all responsibility. The ROMs are not perfect (just like all others) as there could be some bugs. Don’t forget to follow instructions well and read everything before proceeding.

If you still want to unlock your device à la Science fiction, go ahead and get the ROM files from the Android Central Forums. There is a version available for both the GSM (T-Mobile) and the Sprint version – so everyone is covered. Links are right below.

Get the ROM for the Sprint Nexus S 4G.

Get the ROM for the GSM Nexus S.

Are you guys flashing one of these ROMs? Let us know how it goes! Happy Holidays!

It was four days ago now, December 16th, when Google first announced they’d be rolling out an update to Ice Cream Sandwich for the Samsung Nexus S. Due to various errors and problems being reported by users from all over the web, the update is being put on hold for some.

Problems associated with the update to Ice Cream Sandwich include everything from high spikes in CPU usage, to major battery drain. Because of this, even if you receive a notification to download the update to your device, doesn’t mean you will be able to apply it. In areas where Google is monitoring feedback, they have paused the update process. Once the update is cleared for those regions being monitored, a new notification to update will appear.

If you received an update notification a little while ago but the update isn’t currently available for your phone, this is likely the result of Google pausing the update in your area while we monitor feedback. The Android 4.0 update is continuing to roll out around the world so your phone will receive another update notification when it’s available again in your region.Paul WilcoxCommunity Manager, Google

Personally, I have seen great battery life on Ice Cream Sandwich, and no spikes in CPU usage. However, I am having my own set of problems with the camera app. At first, it would only force close after a minute or two of doing nothing. Then, I started seeing an error message saying that my phone can’t connect to the camera. That same error message also popped up when I tried using CameraFX. Now, the camera will load sometimes, but nothing works. The viewfinder area stays black. As you can imagine, this is seriously frustrating.

It’s incredibly disappointing to see the update play out this poorly, but I wouldn’t wish battery, CPU or camera problems (especially ones this bad) on my worst enemy. Hopefully, Google will have the update figured out before too long.

Google promised that the Nexus S would be updated to Android 4.0 shortly after the Galaxy Nexus was released. Sure enough, just one day after the Verizon Nexus hit shelves across the nation, Ice Cream Sandwich for the Nexus S has hit the air.

As for how the update will play out, it will be rolled out in waves (much like every other update has), with GSM devices first in line. Sprint’s Nexus S 4G will come later on. It may take around a month for the update to be completely deployed, but rest assured you shouldn’t have to wait that long. Once the update is out there, developers usually release a flashable update file that doesn’t require root to use.

When it comes to the changes in store for Nexus S users, Google has published a “Tips for Android 2.3 Users” page that offers some words of advice on making the upgrade. The page features information like how to change the wallpaper, create a folder and view recent apps. There’s also information on the new lock screen, the gestures found throughout Ice Cream Sandwich and app upgrades.

I’m still waiting for the update to hit my handset, but once it does, I’ll be sure to share my experiences. If you feel up to it, you can do the same in the comments below.

Update:

The manual update file for the T-Mobile (not sure about AT&T) Nexus S is live. I have successfully update my Nexus S, but keep in mind that this is a download at your own risk situation. Famed Android developer JBQ has put out some release notes on the update, saying that this is the first AOSP build that supports three devices: the Nexus S, Galaxy Nexus and Motorola Xoom. To download the update, I recommend visiting this Google+ post where you can also find instructions. Good luck!

Throughout the madness that has become the US launch of the Galaxy Nexus, it’s been easy to forget that Samsung’s latest device won’t be the only US phone to run stock Android before the year is over. Some time ago, Google made an announcement that Android 4.0 would be rolled out to Nexus S devices just as soon as the Galaxy Nexus was released. Well, as that time inches ever closer, Google is taking the proper measures to make sure Nexus S owners get their dose of ICS right on schedule.

According to some Google+ posts from AdSense Policy Applications and Signals Developer Adel Saoud, Google employees are already receiving test builds of Ice Cream Sandwich for the Nexus S. The purpose of updating Google employee’s devices before consumer’s is so that developers can help iron out any kinks before the update goes live. The Google+ posts revealing this information doesn’t give away any details on the update, just that it’s not ready for prime time.

If previous updates are any indication of how this one will roll out, it shouldn’t be long before anyone still holding onto a Nexus S gets brought up to speed. I’ll still be using my Nexus S for quite some time to come, so once the update is live, we’ll be sure to bring you plenty of in-depth coverage on what Android 4.0 brings to the device.

Ice Cream Sandwich ROMs have been coming out of the woodwork for the past couple weeks now, but there are none as anticipated as CyanogenMod 9.

The amount of work that goes into a stable CyanogenMod release is astonishing. Not only does the build have to be fully functional, but bug free as well. With every new release, be it alpha or nightly, more bugs are discovered. So as time goes on, it becomes more and more tedious to perfect a single ROM. It’s going to be awhile before any stable CyanogenMod ROMs go up for download, but alpha builds are already finding their way online.

If you are lucky enough to own a Nexus S, then you can download and try out CyanogenMod 9 now. In its current stage, CyanogenMod 9 alpha 11 for the Nexus S is missing very few essential functions. There some issues with video playback and MMS isn’t perfect, but there are a lot of people using the ROM as a daily driver. As time goes on more bugs will be found and ironed out, and customization features will be piled on until you can change and tweak nearly every aspect of the device. But for now, this is as good as it gets.

If you’re looking to get CyanogenMod 9 onto your Nexus S, you can find all the info in this XDA thread. Of course the standard only you are responsible for hacking your phone disclaimers apply.

While we’re on the subject of CyanogenMod 9, what feature are you dying to try out? Personally, I’d love to see how themes work. The theme engine is CyanogenMod 7 was great, especially once you were sick to death of the orange highlights and black notification bar. The blue highlights in Ice Cream Sandwich will be a welcome change, but for how long? I’ll take my Ice Cream Sandwich in purple or gray please.