System application upgrade and system app versions?

by Peter Neubauer » Mon, 27 Apr 2009 19:41:47 GMT

Sponsored Links
I am having a scenario where I want to upgrade a preinstalled
application (let's say version 1.0). AFAIK, the new version (1.1) will
be installed on /data and will shadow the one in the system image.

However, if a new system image upgrade woudl contain a newer version
again (2.0), would Android run the 1.1 from /data or the 2.0 from the
new system image?

Another question - is there a <uses-sdk
android:maxSdkVersion="integer" /> tag that lets me specify that I do
not want to run on newer versions of the SDK, in case these wil
introduce unwanted behaviour and incompatible changes?



GTalk:      neubauer.peter
Skype       peter.neubauer
Phone       +46 704 106975
Twitter      - New Energy for Data - The Graph Database.      - New Energy for OSS Communities - Open
Participation Software.         - New Energy for Java - Domain Driven Development.


Other Threads

1. Different screen sizes x different layouts


Im facing a problem that probably many of you have faced before:
supporting multiple screens (sizes and resolutions). Ive searched not
only this forum but many different websites and the android
documentation but Im probably doing a small mistake so things are not
working properly.

Well, my main layout was designed with a HVGA screen, and it works
great. When I try the same app on a WVGA, FWVGA, WQVGA or FWQVGA, I
always get an unused space in the end of the layout because the screen
s "heightnes" is proportionally bigger than HVGAs.

So I consulted the documentation and decided to give a try on resource
qualifiers, so I then created a nonsense UI and placed it on layout-
large, created a new AVD using the WVGA skin and launched the app.
Well, all I got was my old and not well stretched layout. The same
happened to a FWVGA AVD.

This is the first problem. The second is:
medium high density medium size screens and medium density large
screens have the same resolution: how can I create a layout that is
loaded for both, but not for (for example) medium size medium density
or small size medium density screens?

Thanks for your help,
Gabriel Simes

ps: all my widgets are using the default Android resources, so theres
no need to worry now about imagess densities.


2. onLocationChanged - differences between emulator 1.5 and emulator 2.1


I would really appreciate if an experienced Android developer could
provide their insights regarding the following.

I am testing requestLocationUpdates/onLocationChanged on emulator
using Eclipse emulator control in Debug perspective. Everything works
as expected when I test on emulator running AVD 2.1. (Both manual mode
and GPX file works as expected)

However when I run the same code on emulator running AVD 1.5,
onLocationChanged is never called.  onStatusChanged is called only
once with TEMPORARILY_UNAVAILABLE only once.

I found the following link regarding this.

However there are lot of conflicting comments in this thread. I would
really appreciate if someone could clarify the following:

1.) Does the onLocationChanged bug exist only the Android 1.5 emulator
or does it also reproduce on real devices running Android 1.5?

2.) How do you write code that needs periodic location updates that
works on all Android versions including 1.5?




3. Help With Drawable.getPadding ?

4. How to add new field(s) and records to the call logs(call history) database?

5. Swap not active

6. Android SDK: Extending the ant build file?

7. Sending programmatic email with attachment