Tag Archives: ics

Thumbnail

Google begins pushing Android 4.0.4 ICS to GSM Nexus S and GSM Galaxy Nexus, but not Verizon edition yet

Screen Shot 2012 03 28 at 2.36.47 PM 520x245 Google begins pushing Android 4.0.4 ICS to GSM Nexus S and GSM Galaxy Nexus, but not Verizon edition yet

Google has posted a notice on its Android Google+ page that it has begun rolling out Android version 4.0.4 Ice Cream sandwich to several devices. Interesting in its absence is the Galaxy Nexus LTE device for Verizon networks, which currently has the 4.0.2 software as its latest officially supported version.

Google says that it is currently getting the GSM Nexus S, Xoom WiFi and GSM(HSPA+) Galaxy Nexus devices up to date, but will be rolling out the update to more devices in the coming weeks. Some of those devices will be ones that did not have ICS support at all previously.

Some of you will be receiving Ice Cream Sandwich for the first time, while others will be receiving an update to your existing Ice Cream Sandwich experience with stability improvements, better camera performance, smoother screen rotation, improved phone number recognition and more.

The comments section below the post immediately began filling up with requests for ICS to come to the Verizon LTE edition of the Galaxy Nexus, as well as other Android devices like the HTC Thunderbolt and Samsung Galaxy S II, which have yet to get the latest version.

ICSv3 520x942 Google begins pushing Android 4.0.4 ICS to GSM Nexus S and GSM Galaxy Nexus, but not Verizon edition yet

Although the two operating systems cannot be compared directly because of the wide disparity in Android hardware, you can bet that the far greater adoption of newer versions of iOS by iPhone and iPad users is something that Google would love to see happen with Android.

ICS adoption among Android devices still hovers around the 1.6% mark, well behind Gingerbread, which still accounts for 62% of all devices running Google’s OS. Hopefully rolling it out to older devices will help to alleviate the slog and get the actually pretty great ICS out to more users.

H/t Chad Catacchio

See the original post: 

Google begins pushing Android 4.0.4 ICS to GSM Nexus S and GSM Galaxy Nexus, but not Verizon edition yet

Thumbnail

Google Voice now integrates directly with Ice Cream Sandwich’s visual voicemail

Screen Shot 2012 03 22 at 12.19.39 PM 520x245 Google Voice now integrates directly with Ice Cream Sandwichs visual voicemail

Google voice just got a small, but nice, upgrade, adding direct integration with Android 4.x Ice Cream Sandwich. This allows you to grab any Google Voice voicemails right inside the visual voicemail view of your ICS device, without having to jump back to the Google Voice app.

Previous to this update, you could get your Google Voice voicemails in a nice ‘visual voicemail’ interface inside the app itself. This upgrade now lets you see those voicemails in the standard ICS interface instead, so you don’t have to jump back and forth between apps.

voiceshot1 1 220x391 Google Voice now integrates directly with Ice Cream Sandwichs visual voicemailvoiceshot2 220x391 Google Voice now integrates directly with Ice Cream Sandwichs visual voicemail

Your voicemails will appear alongside your outgoing, incoming, and missed calls in your phone’s call log and you can just simply touch them to play them. You can slow down the playback of the message which is great for when someone is telling you their callback number, or you even speed playback up, so you can quickly listen to longer messages.

You can grab the latest version of Google Voice right from the Google Play store or just grab the upgrade.

Continued: 

Google Voice now integrates directly with Ice Cream Sandwich’s visual voicemail

Thumbnail

Some GSM Galaxy Nexus phones can’t get ICS directly from Google due to custom Samsung firmware

Samsung Galaxy Nexus Real 520x245 Some GSM Galaxy Nexus phones cant get ICS directly from Google due to custom Samsung firmware

Update: The latest updates to this conversation on the XDA forums show that the ICS updates, including 4.0.2 are now shipping to some of these devices. The original story dates back to December but users are still reporting that it is spreading slowly.

The Galaxy Nexus is Google’s flagship device, and as with past Nexus devices, it gets priority updates directly from the mother ship. This is because these devices run a stock version of Android and are meant to act as an example of a pure Android experience.

The Verizon edition of the Galaxy Nexus is getting these patches just fine, including the latest 4.0.2 update to Android Ice Cream Sandwich. Unfortunately, as Android and Me reports, some users with the GSM version of the device are having difficulty applying the standard update that comes right from Google.

The version of the Galaxy Nexus that is produced for GSM networks by Samsung is identical aside from the radio that is being used to communicate with cellular network. But only some of the devices that are being shipped out have the ability to apply the bone-stock version of Ice Cream Sandwich, others cannot have the new version installed.

After some digging, it turns out that GSM Nexus devices in some regions have been shipped out with firmware customized by Samsung. This causes a mis-match in the firmware codes for the device and the software. Then, when users go to update their devices manually, the upgrade fails.

The problem with this is that these users are now stuck waiting for Samsung to issue editions of ICS 4.0.2 that match up with the custom software codes that the company saddled the devices with.

Devices that carry Google’s standard software code of ‘yakju’ will update just fine. Some users have flashed their devices with Google’s standard software code, allowing their devices to act as a ‘regular’ Galaxy Nexus device, but this is an unofficial workaround.

One XDA forum member posits that Samsung pushed out a fix to the ICS volume bug early in some batches of the device, tired of waiting for a fix to come from Google, causing it to carry a different software code.

The issue here is that Google has always touted the Galaxy Nexus devices a pure Android experience that always gets the latest updates as soon as they are available. Many of Samsung’s other devices get customized with its TouchWiz interface, including pretty much all of the rest of its Galaxy lineup. The Galaxy S II, in fact, won’t be getting the stock Ice Cream Sandwich. Instead, it will end up with a half-breed version of the OS, likely because Samsung can’t change the entire user interface of those devices on the fly.

Now, users of the GSM Galaxy Nexus are left wondering when Samsung will issue an update for these devices with custom software codes. If it does come, it will likely be flying stock ICS colors, as Google wouldn’t want to split the model’s software versions, but the timing is a mystery.

We have reached out to Samsung and will update this post if we receive a reply.

Original link: 

Some GSM Galaxy Nexus phones can’t get ICS directly from Google due to custom Samsung firmware

Thumbnail

Google’s KeyChain API makes Android more attractive for the enterprise

code21 520x245 Googles KeyChain API makes Android more attractive for the enterprise

Google has been working to ease manageability issues for Android developers focusing on enterprise environments, and now with ICS (Android 4.0), a new KeyChain API should help break down a few barriers that have previously made Android less than compatible with the corporate world.

Of course, the average user and business won’t notice the change, but for developers the API should solve a number of issues where multiple certificates may be shared across a number of apps such as Email and Browser. This is just one way that ICS opens the door for Android to make its way into the industry as BlackBerry continues to be kicked to the curb.

From Tim Bray on the Android developers blog:

To bridge the gap in ICS, there’s a new API named KeyChain that regulates application access to the system key store and allows users to grant application access to the credentials stored there. Additionally, this API enables applications to initiate installation of credentials from X.509 certificates and PKCS#12 key stores.

The KeyChain API is rather simple. To install a key store or a certificate, you retrieve an install intent, supply the raw bytes of the credentials, and use the intent to launch a system installation dialog. If it’s a keystore, as in the example below, you’ll need provide the data in PKCS#12 format, and the user will have to know the PKCS#12 password.

This feature follows a number of other improvements that make Android a much more attractive development platform. Other touted changes include improved security and encryption, VPN access, and powerful productivity features, which all go hand in hand with the more press friendly announcements.

If you’re an eager developer, you can check out the guide on how to utilize the KeyChain API in new apps.

Check out TNW’s Design & Dev channel for daily news, tips and inspiration.

View original post here: 

Google’s KeyChain API makes Android more attractive for the enterprise