Foxreal109

• Android Studio 2.3.3 Download
• Update Android Studio 2.3 To 3.0

In this document

Yes you can update Android studio to 3.0, as Android studio 3.0 update is targetting only for 64bit OS version. After upgrading you must open and clean the project and then you can directly run on your Android device.

I had 7GB free on the root partition, but Android Studio failed to update because it was dumping all updates in to /tmp, and 7GB was not enough! Turns out it's is a known problem with Android Studio updates. There's a JVM argument to tell Android Studio to use a different tmp location for downloads. In Android Studio 2.3.3, I get dozens of this Logcat message OFTEN. Probably every 5th run: com.android.inputmethod.latin E/RichInputConnection: Unable to connect to the editor to retrieve tex. Android Studio 2.3 3 Free Download For Windows 10 64 Bit. Compatibility with this avd management software may vary, but will generally run fine under Microsoft Windows 10, Windows 8, Windows 8.1, Windows 7, Windows Vista and Windows XP on either a 32-bit or 64-bit setup. A separate x64 version may be available from Google.

Reference

1. APIDifferences Report »

See Also

API Level:10

Android 2.3.3 is a small feature release that adds several improvementsand APIs to the Android 2.3 platform.

For developers, the Android 2.3.3 platform is available as adownloadable component for the Android SDK. The downloadable platform includes an Android library and system image, as well as a set of emulatorskins and more. The downloadable platformincludes no external libraries.

To get started developing or testing against Android2.3.3, use the Android SDK Manager todownload the platform into your SDK. For more information,see Adding SDKComponents. If you are new to Android, download the SDK Starter Packagefirst.

For a high-level introduction to Android 2.3, see the Platform Highlights.

Revisions

The sections below provide notes about successive releases ofthe Android 2.3.3 platform component for the Android SDK, as denoted byrevision number. To determine what revision(s) of the Android2.3.3 platforms are installed in your SDK environment, refer tothe 'Installed Packages' listing in the Android SDK and AVD Manager.

API Overview

The sections below provide a technical overview of what's new for developersin 2.3.3, including new features and changes in the frameworkAPI since the previous version.

Near Field Communications (NFC)

Android 2.3.3 provides improved and extended support for NFC, to allowapplications to interact with more types of tags in new ways.

A new, comprehensive set of APIs give applications read and write accessto a wider range of standard tag technologies, including:

• NFC-A (ISO 14443-3A)
• NFC-B (ISO 14443-3B)
• NFC-F (JIS 6319-4)
• NFC-V (ISO 15693)
• ISO-DEP (ISO 14443-4)
• Mifare Classic
• Mifare Ultralight
• NFC Forum NDEF tags

The platform also provides a limited peer-to-peer communication protocoland API. Foreground Activities can use the API to register an NDEFmessage that will get pushed to other NFC devices when they connect.

Advanced tag dispatching now gives applications more control over how andwhen they are launched, when an NFC tag is discovered. Previously, the platformused a single-step intent dispatch to notify interested applications that a tagwas discovered. The platform now uses a four-step process that enables theforeground application to take control of a tag event before it is passed to anyother applications (android.nfc.NfcAdapter.enableForegroundDispatch()).The new dispatch process also lets apps listen for specific tag content andtag technologies, based on two new intent actions —android.nfc.action.NDEF_DISCOVERED andandroid.nfc.action.TECH_DISCOVERED.

The NFC API is available in the android.nfc and android.nfc.tech packages. The key classes are:

• NfcAdapter, which represents the NFC hardware on the device.
• NdefMessage, which represents an NDEF data message,the standard format in which 'records' carrying data are transmitted betweendevices and tags. An NDEF message certain many NDEF records of different types.Applications can receive these messages from NDEF_DISCOVERED,TECH_DISCOVERED, orTAG_DISCOVERED Intents.
• NdefRecord, delivered in anNdefMessage, which describes the type of data being sharedand carries the data itself.
• Tag, which represents a tag scanned by the device.Multiple types of tags are supported, based on the underlying tagtechnology.
• TagTechnology, an interface that gives applicationsaccess to tag properties and I/O operations based on the technologies presentin the tag. For a full list of tag technologies supported in Android 2.3.3, seeandroid.nfc.tech.

NFC communication relies on wireless technology in the device hardware, andis not present in all Android devices. Android devices that do not supportNFC will return a null object whengetDefaultAdapter(Context) is called, andcontext.getPackageManager().hasSystemFeature(PackageManager.FEATURE_NFC)will return false. The NFC API is always present, however, regardless ofunderlying hardware support.

To use the NFC API, applications must request permission from the user bydeclaring <uses-permissionandroid:name='android.permission.NFC'> in their manifest files.

Additionally, developers can request filtering on Android Market, such thattheir applications are not discoverable to users whose devices do not supportNFC. To request filtering, add<uses-feature android:name='android.hardware.nfc'android:required='true'> to the application's manifest.

To look at sample code for NFC, seeNFCDemo app, filtering by tag technology, using foreground dispatch, and foreground NDEF push (P2P).

Bluetooth

Android 2.3.3 adds platform and API support for Bluetooth nonsecure socketconnections. This lets applications communicate with simple devices that may notoffer a UI for authentication. See createInsecureRfcommSocketToServiceRecord(java.util.UUID) and listenUsingInsecureRfcommWithServiceRecord(java.lang.String, java.util.UUID)for more information.

Graphics

Android Studio 2.3.3 Download

• A new BitmapRegionDecoder class lets applicationsdecode a rectangle region from an image. The API is particularly useful when anoriginal image is large and and the application only need parts of the image.
• A new inPreferQualityOverSpeed field in BitmapFactory.Options allows applications to use a more accuratebut slightly slower IDCT method in JPEG decode. This in turn improves thequality of the reconstructed image.

Update Android Studio 2.3 To 3.0

Media framework

• A new MediaMetadataRetriever class provides a unifiedinterface for retrieving frame and metadata from an input media file.
• MediaRecorder.AudioEncoder and MediaRecorder.OutputFormat include new fields for specifying AMRWideband and AAC formats.

Speech recognition

The speech-recognition API includes new constants to let you manage voicesearch results in new ways. Although the new constants are not needed for normaluse of speech recognition, you could use them to offer a different view of voicesearch results in your application. For information, see RecognizerResultsIntent.

API Level

The Android 2.3.3 platform delivers an updated version ofthe framework API. The Android 2.3.3 APIis assigned an integer identifier —10 — that isstored in the system itself. This identifier, called the 'API Level', allows thesystem to correctly determine whether an application is compatible withthe system, prior to installing the application.

To use APIs introduced in Android 2.3.3 in your application,you need compile the application against the Android library that is provided inthe Android 2.3.3 SDK platform. Depending on your needs, you might also need to add an android:minSdkVersion='10'attribute to the <uses-sdk> element in the application'smanifest. If your application is designed to run only on Android 2.3 and higher,declaring the attribute prevents the application from being installed on earlierversions of the platform.

For more information about how to use API Level, see the API Levels document.

Built-in Applications

The system image included in the downloadable platform provides thesebuilt-in applications:

Locales

The system image included in the downloadable SDK platform provides a variety ofbuilt-in locales. In some cases, region-specific strings are available for thelocales. In other cases, a default version of the language is used. Thelanguages that are available in the Android 2.3.3 systemimage are listed below (with language_country/region localedescriptor).

Note: The Android platform may support morelocales than are included in the SDK system image. All of the supported localesare available in the Android Open SourceProject.

Emulator Skins

The downloadable platform includes a set of emulator skins that you can usefor modeling your application in different screen sizes and resolutions. Theemulator skins are:

• QVGA (240x320, low density, small screen)
• WQVGA400 (240x400, low density, normal screen)
• WQVGA432 (240x432, low density, normal screen)
• HVGA (320x480, medium density, normal screen)
• WVGA800 (480x800, high density, normal screen)
• WVGA854 (480x854 high density, normal screen)

For more information about how to develop an application that displaysand functions properly on all Android-powered devices, see Supporting MultipleScreens.