Android emulator ABI

androidandroid-emulatorcpu-architecture

Preamble: THIS QUESTION IS WILDLY OBSOLETE.

When creating an Android Virtual Device (AVD), there's a selection for CPU/ABI. I've tried all available targets – there is no choice but ARM on all of them. I have targets up to Android 3.2.

I'm assuming this was done for emulating tablets or netbooks on x86. Do those even exist in hardware? What kind of target would support a different ABI?

EDIT: in Android Tools v17, there's an optional Intel Atom x86 image under API level 10.

EDIT2: ARMv7a is there now, too. No MIPS so far though.

EDIT3: MIPS emulator and image is available now, too. Pending some new architecture (ARMv8? Intel flavors for non-Atom? x86_64? SH3/4?), this question is utterly pointless.

Best Answer

There are android devices which run on non-ARM platforms, but it does not appear that the emulator mimics them yet. To my knowledge, there are not presently any first-rate fully supported (ie, "Google Experience") devices which use a different processor architecture.

In theory, you shouldn't need to test an android application that uses only official APIs on the actual target ABI unless you have ndk code, and the official ndk does not yet support non-ARM targets.

For the x86 cases, it tends to be faster to run in something like virtualbox anyway (and comes with its own ndk)

For something else - mips or whatever - at the moment that would probably be a custom hardware device and testing would either be done on the actual device or whatever eval board was used to support the initial work of porting android for it.

As long as non-ARM targets aren't fully official, this kind of support would come from the port author or hardware vendor rather than from Google's official tools.

Related Solutions

Android – How to close/hide the Android soft keyboard programmatically

You can force Android to hide the virtual keyboard using the InputMethodManager, calling hideSoftInputFromWindow, passing in the token of the window containing your focused view.

// Check if no view has focus:
View view = this.getCurrentFocus();
if (view != null) {  
    InputMethodManager imm = (InputMethodManager)getSystemService(Context.INPUT_METHOD_SERVICE);
    imm.hideSoftInputFromWindow(view.getWindowToken(), 0);
}

This will force the keyboard to be hidden in all situations. In some cases, you will want to pass in InputMethodManager.HIDE_IMPLICIT_ONLY as the second parameter to ensure you only hide the keyboard when the user didn't explicitly force it to appear (by holding down the menu).

Note: If you want to do this in Kotlin, use: context?.getSystemService(Context.INPUT_METHOD_SERVICE) as InputMethodManager

Kotlin Syntax

// Only runs if there is a view that is currently focused
this.currentFocus?.let { view ->
    val imm = getSystemService(Context.INPUT_METHOD_SERVICE) as? InputMethodManager
    imm?.hideSoftInputFromWindow(view.windowToken, 0)
}

Android – How to stop EditText from gaining focus at Activity startup in Android

Excellent answers from Luc and Mark. However, a good code sample is missing. Adding the tags android:focusableInTouchMode="true" and android:focusable="true" to the parent layout (e.g. LinearLayout or ConstraintLayout) like in the following example, will fix the problem.

<!-- Dummy item to prevent AutoCompleteTextView from receiving focus -->
<LinearLayout
    android:focusable="true" 
    android:focusableInTouchMode="true"
    android:layout_width="0px" 
    android:layout_height="0px"/>

<!-- :nextFocusUp and :nextFocusLeft have been set to the id of this component
to prevent the dummy from receiving focus again -->
<AutoCompleteTextView android:id="@+id/autotext"
    android:layout_width="fill_parent" 
    android:layout_height="wrap_content"
    android:nextFocusUp="@id/autotext" 
    android:nextFocusLeft="@id/autotext"/>

Best Answer

Related Solutions

Android – How to close/hide the Android soft keyboard programmatically

Android – How to stop EditText from gaining focus at Activity startup in Android

Related Topic