Commentary

Ed Hansberry
 

Google Wants Android Users To Upgrade To V2.1

It looks like Google may be trying to get all of its Android devices in the hands of consumers upgraded to the latest release, 2.1. This should be welcome news to those who have a device with the older 1.6 or even 1.5 release. The bad news is that some devices will require a total wipe first, and that personal data and applications will have to be reloaded.

It looks like Google may be trying to get all of its Android devices in the hands of consumers upgraded to the latest release, 2.1. This should be welcome news to those who have a device with the older 1.6 or even 1.5 release. The bad news is that some devices will require a total wipe first, and that personal data and applications will have to be reloaded.Android and Me is reporting that more than 80% of its readers are on an outdated version of Android. Claiming insider sources, the article states that every Android device in the United States will be eligible for a bump to 2.1. Since 2.1 is larger than what some of the earlier phones were built for, such as the G1, not all features may work. Live Wallpapers is one example of a feature that you might not get on some devices.

The article also reports that some devices, and perhaps most devices, will require a wipe. The one notable exception is the Motorola Droid which shipped with 2.0.1.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Upgrades should start rolling out in the second quarter of 2010. Some will be over the air and some will require being tethered to your PC to perform the update.

While users will certainly enjoy getting the latest OS version on their devices, the biggest win here is for developers. They will be able to focus on one version of the platform rather than the four versions currently in the wild - 1.5, 1.6, 2.0 and 2.1.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links