Choice of API Level

by Kevin » Fri, 13 Nov 2009 07:22:45 GMT


Sponsored Links
 The developer guide recommends choosing the lowest API level your
application can support.  However, the current SDK only includes
images down to level 2.  What about level 1?  Aren't there devices "in
the wild" that will use the 1.0 Platform?  If you want to target level
1, do you need to use an old SDK?

--



Other Threads

1. Contact Picking on Motorola Cliq (1.5)?

I'm able to successfully use the contact picker on the Motorola Cliq
using the intent:

new Intent(Intent.ACTION_PICK, People.CONTENT_URI)

It works as expected, and I'm able to get the contact data in
onActivityResult()

However, every single time, I get an error dialog: "The application
Contacts (process com.motorola.blur.contacts) has stopped
unexpectedly. Please try again. (Force Close)"

The error in LogCat:
android.app.SuperNotCalledException: Activity
{com.motorola.blur.contacts/
com.motorola.blur.contacts.picker.PickPeopleActivity} did not call
through to super.onDestroy()

So does this mean the contacts picker on the Cliq is just plain
broken? Has anyone else seen this error, and/or been able to
successfully use the contacts picker on the Cliq without getting error
messages?

-- 

2. Use of final for locals on Dalvik

I've seen a lot of use of final for local primitives.

Presumable to indicate to the compiler that the value shouldn't be changed.

However, what's the implication of this on Dalvik?

I believe final local variables are usually placed on the heap for extended
lifetime (for use in inner classes), so is their a runtime overhead rather
than using simple locals (which use Dalvik registers)?


Thanks,
 Tim

-- 

3. Android's support for multiple screens

4. AppWidget Update on Orientation Change

5. Start a service on device start up.

6. Interconnecting emulators by networ

7. Snapit lagi