Group items tagged

Since: API Level 3

Constants for supporting speech recognition through starting an Intent

Authentication with App Engine, regardless of where you're doing it, is a three-stage process: Obtain an authentication token. This can be done with ClientLogin for installed apps, for example, or with AuthSub for a webapp. When logging in directly to an application, this is the part of the login process where your user sees a Google signin screen. Take that authentication token, and use it to obtain an authentication cookie. Use that authentication cookie in all subsequent requests.

<uses-permission android:name="android.permission.GET_ACCOUNTS"></uses-permission> <uses-permission android:name="android.permission.USE_CREDENTIALS"></uses-permission> <uses-permission android:name="android.permission.INTERNET"></uses-permission>

When onReceive() returns

by the system at any time

This projects aims to provide a way to access unread emails regardless of label directly from the android home screen. This project releases directly to the Android Market and as such the download section here may be behind.

Calling a Javascript method from your Java code: webView.loadUrl("javascript:jsToggle()"); Calling a Java method from Javascript: window.jsinterface.nativeToggle(); /*   // Before using the above code, you have to inject the interface object which   // has a name "jsinterface"   webView.addJavascriptInterface(jsInterface, "jsinterface"); */

Adds multi-touch zoom to; ImageViews, WebViews, and MapViews. Simply use the corresponding object in place of the default, and the "pinch" functionality will be usable. Also includes misc. Views which can be useful for development.

I am just trying to display a list from an array that I have in my arrays.xml.

String[] testArray = getResources().getStringArray(R.array.testArray); /** Called when the activity is first created. */ @Override protected void onCreate(Bundle savedInstanceState)

You can't initialize your testArray field this way, because the application resources still aren't ready.

The density of a screen is important because, other things being equal, a UI element (such as a button) whose height and width are defined in terms of screen pixels will appear larger on the lower density screen and smaller on the higher density screen.

The density-independent pixel is equivalent to one physical pixel on a 160 dpi screen, the baseline density assumed by the platform (as described later in this document). At run time, the platform transparently handles any scaling of the dip units needed, based on the actual density of the screen in use. The conversion of dip units to screen pixels is simple: pixels = dips * (density / 160). For example, on 240 dpi screen, 1 dip would equal 1.5 physical pixels. Using dip units to define your application's UI is highly recommended, as a way of ensuring proper display of your UI on different screens.

On an HTC Hero, this EXTRA_OUTPUT doesn't even work. It doesn't put your picture in the file you specify, but it hands it to you thru a Mediastore uri. Apparently, the only way to get a full size picture is to do all camera handling in your app instead of using the IMAGE_CAPTURE intent.

I think Google have missed a trick on this one. They have defined standard intents for media capture, but not specified standard responses (ie. the "data" parameter in the onActivityResult Activity callback method). Other Android vendors (e.g. HTC Hero) have created their own Camera applications that handle the standard IMAGE_CAPTURE intent, but return different data & have different ways to save/return the image information. All I want is to be able to fire a IMAGE_CAPTURE intent from my own app, and get back a Uri reference to the captured image. Simple. I have no requirement to further manipulate the image .. I just need the Uri to store in my app's database for future reference.