How i can migrate my app from 1.5 to 1.6 api fast and safe???

by saex » Fri, 03 Dec 2010 19:51:25 GMT

Sponsored Links
 Hi, i am making a gigantic app for android, and i start doing it some
moths ago for android 1.5, but now i know that some of the things i
need for my app only can be done if you are programming for 1.6 api.

there is a easy, fast and safe way to migrate my app from 1.5 to 1.6
without having to lose time?



Re: How i can migrate my app from 1.5 to 1.6 api fast and safe???

by Streets Of Boston » Fri, 03 Dec 2010 22:41:23 GMT

 If you don't need/want to support 1.5 phones, just set the project's
Android SDK version to 1.6 (api-level 4). Re-compile. That's it.


Sponsored Links

Re: How i can migrate my app from 1.5 to 1.6 api fast and safe???

by Leon Moreyn-Android Development » Fri, 03 Dec 2010 22:55:12 GMT

 that and if your building in eclipse make sure to change the lib to
1.6. Right click on project, properties, android, then select 1.6


Other Threads

1. Free gesture library


does anyone know if there are any free multi touch gesture libraries out
there? The standard Android SDK only contains the one for pinch
zoom, ScaleGestureDetector, which is kind of limited... I would like
additional basic gestures like two/three finger flings. Perhaps there are
other nice basic gestures too that I haven't thought of... :-)

If someone has any info - please let me know!

... until then I'll start implementing something my self and I'll post it
here if it turns out any good...

    Best Regards


2. Live Wallpaper Memory Allocation

I have a problem with my Live Wallpaper app.

It has a settings button where the user can change the background
image (and a couple of more things).
I store information as shared preferences (see the Live Wallpaper

After starting it the memory allocated by the app is constant and
doesn't seem unreasonably high.

But then if I open up the Live Wallpaper picker again, picks my
wallpaper and then either sets the wallpaper again, or hits home/back
to cancel, the memory usage has increased.

This can be repeated several times and the used memory keeps

Same thing happens if I have a solid background color instead of an
image, but the memory increases with less.

I've made sure that I don't load the same image twice (if the user
selects the same image again I don't load anything). I also tried
recycling the old image before loading the new one.
I use BitmapFactory.decodeFile to read the file from the SD-card. But
since the same thing happens without an image I guess it might not be
that anyway.
I've also made sure to set objects to null when done with them, but
that doesn't make a difference.

Does anyone know what could be wrong? Have any tips what I can look
I tried the DDMS tool to track allocations, but nothing stood out.

Any help to find the source of this problem is greatly appreciated!


3. Couldn't refresh list

4. call .net web service from android

5. Difference between zImage (bootp) and boot.img

6. Honeycomb browser broken?

7. [Idandroid] wtb : dimana ya yang jual boneka android