Us early adopters of new technology have to put up with the quirks and speed bumps that this new tech has to offer. I know this, you know this, we all know this, but sometimes they can be frustrating nonetheless. Less than a week after the launch of maybe one of the most hyped phones on the planet, the Galaxy Nexus, users are running into some major and minor bugs. Even with the 4.0.2 update right out of the gate, and a swift push for Android 4.0.3 in the coming weeks (though we aren’t sure when), some of these bugs are hard to over look.
While users have reported some bugs, even our writers have reported issues in their 24hr and 48hr initial impressions of the phone, some of them can be overlooked. However there appears to be a slew of newer found bugs that are giving users even more headaches. The folks over at RootzWiki are reporting that users are having issues with Multitouch in 3D games like Gun Bros and Shadowgun. Apparently after playing the game for a little bit, sensitivity on the right side of the touch screen is lost. This can be remedied with a quick turning off then back on of the display leading folks to believe that this is software related. Read more
Quickly after the release of Android Ice Cream Sandwich 4.0.3 and the push to AOSP, developers over at XDA have created an almost fully functional ROM for both versions of the Xoom. A few issues for both the WiFi and 3G/4G versions are apparent and they are as follows:
What is working: (That I can tell so far)
– All the basics
What is not working:
-3G/4G – baseband issue?
*Need binaries from Moto
There also seems to be an issue with some green coloring on the screen at times, but it appears that we are pretty close to seeing a fully functional Android 4.0.3 ROM for the Xoom.
So if you have a rooted Xoom and want to give this a try, you can hit the break below to download the files and get the instructions on how to do this. Those who want to try this I wish you good luck and let us know how it goes, although if you have 3G/4G I would hold off until those work. A big thanks to razorbladex401, xxspark89xx and XDA for developing these. Note: You need to use fastboot for the 3G/4G files.
If you are anything like me then I bet you were pretty excited when you got your Galaxy Nexus yesterday. I bet you were also excited that there was already an update out to fix bugs on your phone moments after you got it into your hands. Well if you were impressed with that, Google has even more awesome news for you. Google announced today an incremental increase from yesterday’s update bringing it to 4.0.3.
Some of the new APIs in Android 4.0.3 include:
– Social stream API in Contacts provider: Applications that use social stream data such as status updates and check-ins can now sync that data with each of the user’s contacts, providing items in a stream along with photos for each. This new API lets apps show users what the people they know are doing or saying, in addition to their photos and contact information.
– Calendar provider enhancements: Apps can now add color to events, for easier tracking, and new attendee types and states are now available.
– New camera enhancements: Apps can now check and manage video stabilization and use QVGA resolution profiles where needed.
- – Accessibility refinements: Improved content access for screen readers and new status and error reporting for text-to-speech engines.
– Incremental improvements in graphics, database, spell-checking, Bluetooth, and more.
So there we have it. Although I have no idea on when this update will come out, I know I will be checking my status update option constantly. If you do get the update let us know and tell us what you think.
[via Android Developers Blog]
More good news for those of you who managed to score the Galaxy Nexus on this Merry Nexus Day. Not even two hours after the Android 4.0.1 images were released for the Verizon Nexus, Google has decided to drop the 4.0.2 factory images on us as well. The build for ICS 4.0.2 is ICL53F and is the current build you’ll have after the phone updates shortly after activation. For those of you who are wanting to flash, mod and tweak your phone it is suggested that you tuck these away just in case. Check back and we should have an update on how to flash these to your phones should you botch a flash.
maguro/yakju download link
toro/mysid download link
Yesterday we posted an article concerning the discovery of alternative builds on GSM Galaxy Nexus Phones. Google’s own build for the Galaxy Nexus is named “yakju,” however some owners who were not receiving updates for their device discovered the problem lay in the fact that their phone sported a different fingerprint, “yakjuwx.” Android software engineer Jean-Baptise Queru, shed some light on the information, declaring that yakjuwx and yet another alternative build yakjusc are from Samsung, not Google. While the experience is largely the same between the versions, only Google’s yakju build is guranteed updates as they happen. Samsung will presumably distribute the updates to their modified build at unknown time intervals. Not having to wait on updates is one of the major draws of the Nexus brand, so it comes as no surprise that many, discovering they had the yakjuwx build, were a bit disappointed. Others, however, turned their gaze to the impending release of the Galaxy Nexus on Verizon. Would it be receiving updates through Google, Samsung, or shudder Verizon?
It appears that those of us waiting to purchase the Verizon version can all take a big sigh of relief today, as JBQ has chimed in once more on the situation. He writes,
After reviewing the situation, Google concluded that the only Galaxy Nexus that can be supported in AOSP are the ones that are originally sold with a “yakju” or “mysid” system.
yakju is one of the GSM/CDMA+ variants, while mysid is indeed the CDMA/LTE variant for VZW.
There you have it folks. Verizon Galaxy Nexus gets its updates through Google. Rest a little easier, until our next startling discovery…
[via Google Groups]
The Samsung Galaxy Nexus, a phone which should stand as the epitome of a pure Google Experience device, has been receiving a lot of flak lately for inclusion of bloatware and exclusion of Google Wallet, at least in the Verizon version. That being the case, many have resorted to obtaining a purer version elsewhere, purchasing the GSM counterpart for use on alternative networks. As it turns out the GSM version may have its fair share of problems as well, besides the volume bug. One of the key aspects of a Nexus device is the fact that it is updated before any other devices, and the updates come to you straight from Google immediately thereafter they release them. As expected, Google pushed out update 4.0.1 and people started receiving it without missing a beat, some people that is. A buzz began when select XDA community members realized they had failed to receive the 4.0.1 update. Many of them anything but new to Android took matters into their own hands and decided to flash the update to their devices manually using the Google provided update zip file. They subsequently found that they could not manually install either.
What’s going on here?
It’s a work in progress and a pleasure watching it in the making as ICS comes to the Droid Razr. The folks over at RootzWiki managed to successfully boot Ice Cream Sandwich on the device. They’ve dedicated this a whole thread to keeping you up to date in what’s working, what’s not working, all features, news, pics and videos of the port. And if you can get through a ton of heavy metal music and bad viewing angles, check out the video of the new OS on the Razr and don’t forget to let us know what you think of it.
The other day we told you about the CyanogenMod team bringing CM7 to the Kindle Fire. Well as of today you can too. However, this is a lengthy process (43 steps and use of ADB) and I suggest taking extreme caution by reading through the entire guide before you take on this task. According to the post, this is still an alpha build and some stuff doesn’t work. We reported before that the wifi wasn’t working, but both that and the touchscreen are working just fine. The sound and hardware acceleration aren’t working however. According to the post:
“- First, this method will require some knowledge of ADB.
– This version is very much an alpha build, and as such there are features that are not yet working, though most of the important stuff is.
– Wifi and touchscreen controls are reported to work just fine, however sound and hardware acceleration are not.
– This has been tested with firmware versions 6.0 and 6.1, but not on 6.2.
– In addition, there is no way (currently) to return to the stock software.
– There are likely other issues as well, but if you’re willing to test it then proceed.”
So, those of you that are interested in trying this out, I still, advise extreme caution in flashing this, and like with rooting and flashing on other devices, it does void your warranty. If you haven’t rooted your Kindle Fire yet and want to, you can go here. There is no way to get back to the Stock software as of yet, so again, extreme caution advised, have I stressed this enough yet?
If this doesn’t deter you from trying this out, hit the break below to download the files and for the install process. Those of you that successfully flash this, we would love to hear from you. How well does it work? Read more
Good news for those with rooted Bionics. A somewhat functional, alpha build of Ice Cream Sandwich has been released for the Bionic thanks to dhacker29 of the Th3ORY ROM team. Not everything works as of right now, so using this as a daily driver is probably not a good idea. Here is what works:
– Graphics working smooth now
– Adb is working so we can track the rest
– Capacitive buttons
– Charging indicator
– External SD Card
– Builtin Screenshot
– Reboot menu
However, wifi and phone data aren’t working and the developer still needs to get the internal SD card to mount. This should happen sooner rather than later though.
If you are interested in trying this out, you need to make sure your Bionic is rooted, which you can do by going here. Keep in mind that this is an alpha build and is intended for preview purposes only. As always, what happens when flash the ROM is your responsibility. If that doesn’t deter you, hit the break below to download the ROM or view the source for more details. Read more
Chomping at the bit for some Ice Cream Sandwich action brought to you by CM9? Then you’re in luck, sort of. The developers of CyanogenMod released an update to their blog showing progress for CM9. As they say things are “slowly starting to come together.” I think however, that given they got the source code a little over two weeks ago, they are moving along pretty well. They have a number of devices running CM9 and they are focusing on getting it on more devices. OMAP4, MSM8660/7×30 and Exynos devices will most likely be the first ones ready for this ROM. Tablets are being shown some love too as both the Galaxy Tab 10.1 and the Asus Transformer are in the “pipeline” early.
Older devices will be seeing CM 9 as well. As the blog put it:
“Our goal is to provide continued support to all CM7 devices back to the QSD8250 series of devices such as the Nexus One. I don’t want to make any promises at this time, but that is the plan.”
Bad news for those of you with the original Droid. CM9 will not be seen on your device. As the CyanogenMod puts it, “time to upgrade.” Given that the Android framework has had some major changes the CyanogenMod team has had trouble with compatibility with older proprietary camera and graphics drivers, but, they are pretty confident that they will be able to overcome these issues like they have in the past. The CM team has also created a solution to CM7‘s long spin-up time by adding new devices on-demand which saves bandwidth and avoids long start-up time. Read more