Risk of upgrading to 1.1?

by Tim Bray » Thu, 12 Mar 2009 04:17:35 GMT

Sponsored Links
 I was going to keep my SDK at 1.0 because for my own app I don't need
any 1.1 stuff and I'd like it to work on as many devices as possible.
If I upgrade my dev-phone to 1.1 just because I'd like a nicer phone,
is there any appreciable risk that it will fail to detect problems
that might occur on 1.0 devices?  -Tim


Risk of upgrading to 1.1?

by Stoyan Damov » Thu, 12 Mar 2009 04:57:42 GMT

 I have released my game on 19th of February, built against SDK 1.1 but
no minSdkVersion, and tested on my G1 w/ 1.1, i.e. it should be
working on 1.0 devices. So far I haven't got a report that it's not
working on any device, other than the intermittent "Force Close"
issues after an update.

Bottom line is, don't worry, install 1.1 and build against SDK 1.1 - I
haven't had any problems. Surely I haven't used any feature from 1.1,
not that there are many.

Do read  http://developer.android.com/sdk/android-1.1.html to get more 



Sponsored Links

Risk of upgrading to 1.1?

by Jean-Baptiste Queru » Thu, 12 Mar 2009 04:59:08 GMT

 Well, there is a risk that a bug in 1.0 that would have been fixed in
1.1 could be hit by your application. I'm not explicitly aware of such
situations, but that's definitely possible in theory.

It is possible (and in fact reasonably easy) to downgrade an ADP1 back
to 1.0, the drawback being that you need to wipe your data in that


Jean-Baptiste M. "JBQ" Queru
Android Engineer, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further


Risk of upgrading to 1.1?

by MrSnowflake » Thu, 12 Mar 2009 05:36:20 GMT


A very valid situation. But does it matter? All Android devices have
the posibility to run 1.1, so if you build for 1.1, why not set
minSdkVersion? You only are making your app more secure, and you are
not excluding anyone (except for some developer still running 1.0 for
some very specific reason).

And if you are still on 1.0, I think upgrading always is the better
option, because all devices support it and 1.1 will have less bugs, or
at least less bugs in code which was available in 1.0. Though staying
with 1.0 won't really have any negative results.


Other Threads

1. Notificationbar on top of a fullscreen application.

There have been a lot of changes in cupcake to how the status bar is
hidden/shown, so it may be fixed there.

Dianne Hackborn
Android framework engineer

Note: please don't send private questions to me, as I don't have time to
provide private support.  All such questions should be posted on public
forums, where I and others can see and answer them.


2. No callback when list item is touched.

I have a ListView that is populated with a custom adapter.  When an
item is clicked with the trackball, it works fine, i.e. I can catch
the event and move on, though when I touch an item with my finger
there is no callback from the listener.  The item does respond to the
touch, by turning orange for that moment.

Here is how I've setup the listener.  This is within an Activity, not
a ListActivity.

AdapterView.OnItemClickListener() {

                                        public void onItemClick(AdapterView<?> 
arg0, View arg1,
                                                        int position, long id) {


What am I missing? Is there another listener I need to configure?

3. OnGestureListener vs ContextMenu, do they play together?

4. TabHost and Scrollbars

5. need some collection help

6. Bouncing ListView?

7. emulator versus real target...