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. Using NDK for native apps (Segmentation fauult)

Hi all,
I am trying to compile and execute the simple hello world native app
from the NDK (many components are yet to be provided in this I guess).

I am using Beagle board OMAP3530 as the hardware device

The path for the sample application is


I have made several changes to the config.mk and the Makefile itself.
Tried using both the prebuild compiler as well as the CodeSourcery
arm-2007q3-51-arm-none-linux-gnueabi.bin .
2. The include and lib folders are missing in the NDK have given the

For includes:

for lib

The project compiles and hello is generated.

Since I do not have adb support on my board I copy the hello
executable to the rootfs and boot it.

I get a shell prompt on my minicom
cd to system/app and I execute

I get a segmentation fault.

I would like to know if I am doing something fundamentally wrong. how
can I introduce some kind of debugging facility to this. Do let me
know in case you need further data that might be of some help to you.

unsubscribe: android-porting+unsubscr...@googlegroups.com

2. How to Code following logic to make a turning effect of page.


Here, i m proposing a logic to make a turn over of page....


but how to implement it in android.


3. how to create Page turn effect

4. how to set width of gridview from java code(dynamically)

5. How to mute the player when I got an incoming call?

6. Android Developers Available For Hire?

7. how to enable internet access in emulator v1.0