"Yes" doesn't really cover all the situations. Google has attempted
to make code you write for 1.5 (code level 3) or 1.6 (code level 4)
forwards compatible with Android 2.0 (code level 5). This works
"mostly" but you may have to make a few tweaks.
In my case when they went from 1.6 they broke al
I'd say if you want to support as many handsets as possible, take
pcm2a's advice and target 1.5. However if you really need to take
advantage of new resolutions or you're not worried about download
totals I'd say target 1.6 and wait for the other devices to catch up.
On Dec 1, 10:14 am, bennyb wr
On Dec 1, 6:46 pm, Dianne Hackborn wrote:
> Just to reiterate -- there is really no reason not to build against the most
> recent (2.0) SDK, as long as you test against the older ones. Use
> android:targetSdkVersion to tell the system that you have developed against
> the newer version so they
On Tue, Dec 1, 2009 at 10:12 AM, pcm2a wrote:
> Another fine example is with the higher screen resolutions. If you
> made the mistake of using of a font size of say "12pt" in 1.5, thats
> going to look like crap on a Droid with a higher resolution. I had to
> change a lot of stuff like that to
On Tue, Dec 1, 2009 at 10:39 AM, Andrex wrote:
> I'd say if you want to support as many handsets as possible, take
> pcm2a's advice and target 1.5. However if you really need to take
> advantage of new resolutions or you're not worried about download
> totals I'd say target 1.6 and wait for the o
I think this has been brought up before and I've seen this as well. If you
open the AVD manager that has the older platforms on it, you can manually
start an emulator with one of them from there, then select the running
emulator as your target when you do "Debug" or "Run".
6 matches
Mail list logo
