From 904785be3b6dc1ec532532bbee019dbbac26cda4 Mon Sep 17 00:00:00 2001
From: Dirk Dougherty
| Platform Version | API Level | |||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Android 2.3 | 9 | |||||||||||||||||||||||||
| Android 2.2 | 8 | |||||||||||||||||||||||||
| Android 2.1 | 7 | |||||||||||||||||||||||||
| Android 2.0.1 | 6 | The application uses the device's proximity sensor. | - | |||||||||||||||||||||||
| SIP/VOIP | -android.hardware.sip |
- The application uses SIP service on the device. - | -- | |||||||||||||||||||||||
android.hardware.sip.voip |
- Subfeature. The application uses SIP-based VOIP service on the device. - | -If declared with the "android:required="true" attribute, this
-subfeature implicitly declares the android.hardware.sip
-parent feature. |
-||||||||||||||||||||||||
| Telephony | android.hardware.telephony |
@@ -711,17 +695,33 @@ in a separate
| Feature | -Attribute Value | -Description | -|
|---|---|---|---|
| Live Wallpaper | -android.software.live_wallpaper |
- The application uses or provides Live Wallpapers. - | -|
| Feature | +Attribute Value | +Description | +Comments | +
| Live Wallpaper | +android.software.live_wallpaper |
+ The application uses or provides Live Wallpapers. | ++ |
| SIP/VOIP | +android.software.sip |
+ The application uses SIP service on the device. + | ++ |
android.software.sip.voip |
+ Subfeature. The application uses SIP-based VOIP service on the device. + | +If declared with the "android:required="true" attribute, this
+subfeature implicitly declares the android.software.sip
+parent feature. |
+
The Android 2.3 platform introduces many new and exciting features for +users and developers. This document provides a glimpse at some of the new user features +and technologies in Android 2.3. For detailed information about the new developer APIs, see the Android 2.3 version notes.
+ + + + +
+
+
+The user interface is refined in many ways across the system, making it +easier to learn, faster to use, and more power-efficient. A simplified +visual theme of colors against black brings vividness and contrast to the +notification bar, menus, and other parts of the UI. Changes in menus and +settings make it easier for the user to navigate and control the features +of the system and device.
+ +The Android soft keyboard is redesigned and optimized for faster text input +and editing. The keys themselves are reshaped and repositioned for improved +targeting, making them easier to see and press accurately, even at high speeds. +The keyboard also displays the current character and dictionary suggestions in a +larger, more vivid style that is easier to read.
+ +The keyboard adds the capability to correct entered words from suggestions in +the dictionary. As the user selects a word already entered, the keyboard +displays suggestions that the user can choose from, to replace the selection. +The user can also switch to voice input mode to replace the selection. Smart +suggestions let the user accept a suggestion and then return to correct it +later, if needed, from the original set of suggestions.
+ +New multitouch key-chording lets the user quickly enter numbers and symbols +by pressing Shift+<letter> and ?123+<symbol>, +without needing to manually switch input modes. From certain keys, users can +also access a popup menu of accented characters, numbers, and symbols by holding +the key and sliding to select a character.
+

When entering text or viewing a web page, the user can quickly select a word +by press-hold, then copy to the clipboard and paste. Pressing on a word enters a +free-selection mode — the user can adjust the selection area as needed by +dragging a set of bounding arrows to new positions, then copy the bounded area +by pressing anywhere in the selection area. For text entry, the user can +slide-press to enter a cursor mode, then reposition the cursor easily and +accurately by dragging the cursor arrow. With both the selection and cursor +modes, no use of a trackball is needed.
+ +

The Android system takes a more active role in managing apps that are keeping +the device awake for too long or that are consuming CPU while running in the +background. By managing such apps — closing them if appropriate — +the system helps ensure best possible performance and maximum battery life.
+ +The system also gives the user more visibility over the power being consumed +by system components and running apps. The Application settings provides an +accurate overview of how the battery is being used, with details of the usage +and relative power consumed by each component or application.
+ +A shortcut to the Manage Applications control now appears in the Options Menu +in the Home screen and Launcher, making it much easier to check and manage +application activity. Once the user enters Manage Applications, a new Running +tab displays a list of active applications and the storage and memory being used +by each. The user can read further details about each application and if +necessary stop an application or report feedback to its developer.
+An updated set of standard applications lets the user take new approaches to +managing information and relationships.
+ +
+Internet calling
+ +The user can make voice calls over the internet to other users who have SIP +accounts. The user can add an internet calling number (a SIP address) to any +Contact and can initiate a call from Quick Contact or Dialer. To use internet +calling, the user must create an account at the SIP provider of their choice +— SIP accounts are not provided as part of the internet calling feature. +Additionally, support for the platform's SIP and internet calling features on +specific devices is determined by their manufacturers and associated carriers. +
+ +
Near-field communications
+ +An NFC Reader application lets the user read and interact with near-field +communication (NFC) tags. For example, the user can “touch” or “swipe” an NFC +tag that might be embedded in a poster, sticker, or advertisement, then act on +the data read from the tag. A typical use would be to read a tag at a +restaurant, store, or event and then rate or register by jumping to a web site +whose URL is included in the tag data. NFC communication relies on wireless +technology in the device hardware, so support for the platform's NFC features on +specific devices is determined by their manufacturers. +
+Downloads management
+ +The Downloads application gives the user easy access to any file downloaded from +the browser, email, or another application. Downloads is built on an completely new +download manager facility in the system that any other applications can use, to +more easily manage and store their downloads.
+ +Camera
+ +The application now lets the user access multiple cameras on the device, +including a front-facing camera, if available.
+ + +Android 2.3 delivers a variety of features and APIs that +let developers bring new types of applications to the Android +platform.
+ + + +Performance
+ +Android 2.3 includes a variety of improvements across the system that make +common operations faster and more efficient for all applications. Of particular +interest to game developers are:
+ +Native input and +sensor events
+ +Applications that use native code can now receive and process input and +sensor events directly in their native code, which dramatically improves +efficiency and responsiveness.
+ +Native libraries exposed by the platform let applications handle the same +types of input events as those available through the framework. Applications +can receive events from all supported sensor types and can enable/disable +specific sensors and manage event delivery rate and queueing.
+ + +Gyroscope and other +new sensors, for improved 3D motion processing
+ +Android 2.3 adds API support for several new sensor types, including +gyroscope, rotation vector, linear acceleration, gravity, and barometer sensors. +Applications can use the new sensors in combination with any other sensors +available on the device, to track three-dimensional device motion and +orientation change with high precision and accuracy. For example, a game +application could use readings from a gyroscope and accelerometer on the device +to recognize complex user gestures and motions, such as tilt, spin, thrust, and +slice.
+ +Low-latency native +audio
+ +The platform provides a software implementation of Khronos OpenSL ES, a standard API +that gives applications access to powerful audio controls and effects from +native code. Applications can use the API to manage audio devices and control +low-latency audio input, output and processing directly from native code
+ +Native graphics +management
+ +The platform provides an interface to its Khronos EGL library, which lets +applications manage graphics contexts and create and manage OpenGL ES textures +and surfaces from native code.
+ + +Native access to +Activity lifecycle, window management
+ +Native applications can declare a new type of Activity class,
+NativeActivity whose lifecycle callbacks are implemented directly
+in native code. The NativeActivity and its underlying native code
+run in the system just as do other Activities — they run in the
+application's system process and execute on the application's main UI thread,
+and they receive the same lifecycle callbacks as do other Activities.
The platform also exposes native APIs for managing windows, including the +ability to lock/unlock the pixel buffer to draw directly into it. Through the +API, applications can obtain a native window object associated with a framework +Surface object and interact with it directly in native code.
+ + +Native access to +assets, storage
+ +Applications can now access a native Asset Manager API to retrieve
+application assets directly from native code without needing to go through JNI.
+If the assets are compressed, the platform does streaming decompression as the
+application reads the asset data. There is no longer a limit on the size of
+compressed .apk assets that can be read.
Additionally, applications can access a native Storage Manager API to work +directly with OBB files downloaded and managed by the system. Note that although +platform support for OBB is available in Android 2.3, development tools for +creating and managing OBB files will not be available until early 2011.
+ + +Robust native +development environment
+ +The Android NDK (r5 or higher) provides a complete set of tools, toolchains, +and libraries for developing applications that use the rich native environment +offered by the Android 2.3 platform. For more information or to download the +NDK, please see the Android NDK +page.
+ + +Internet +telephony
+ +Developers can now add SIP-based internet telephony features to their +applications. Android 2.3 includes a full SIP protocol stack and integrated call +management services that let applications easily set up outgoing and incoming +voice calls, without having to manage sessions, transport-level communication, +or audio record or playback directly.
+ +Support for the platform's SIP and internet calling features on specific +devices is determined by their manufacturers and associated carriers.
+ + +Near Field +Communications (NFC)
+ +The platform's support for Near Field Communications (NFC) lets developers +get started creating a whole new class of applications for Android. Developers +can create new applications that offer proximity-based information and services +to users, organizations, merchants, and advertisers.
+ +Using the NFC API, +applications can respond to NFC tags “discovered” as the user “touches” an +NFC-enabled device to elements embedded in stickers, smart posters, and even +other devices. When a tag of interest is collected, applications can respond to +the tag, read messages from it, and then store the messages, prompting +the user as needed.
+ +NFC communication relies on wireless technology in the device hardware, so +support for the platform's NFC features on specific devices is determined by +their manufacturers.
+ + +Mixable audio +effects
+ +A new audio effects API lets developers easily create rich audio environments +by adding equalization, bass boost, headphone virtualization (widened +soundstage), and reverb to audio tracks and sounds. Developers can mix multiple +audio effects in a local track or apply effects globally, across multiple +tracks.
+ +Support for new media +formats
+ +The platform now offers built-in support for the VP8 open video compression +format and the WebM open container format. The platform also adds support for +AAC encoding and AMR wideband encoding (in software), so that applications can +capture higher quality audio than narrowband.
+ +Access to multiple +cameras
+ +The Camera API now lets developers access any cameras that are available on a +device, including a front-facing camera. Applications can query the platform for +the number of cameras on the device and their types and characteristics, then +open the camera needed. For example, a video chat application might want to access a +front-facing camera that offers lower-resolution, while a photo application +might prefer a back-facing camera that offers higher-resolution.
+ + +For more information about the new developer APIs, see the Android 2.3 version notes and the API Differences Report.
diff --git a/docs/html/sdk/android-2.3.jd b/docs/html/sdk/android-2.3.jd new file mode 100644 index 000000000000..5438adc135f5 --- /dev/null +++ b/docs/html/sdk/android-2.3.jd @@ -0,0 +1,942 @@ +page.title=Android 2.3 Platform +sdk.platform.version=2.3 +sdk.platform.apiLevel=9 + + +@jd:body + ++API Level: {@sdkPlatformApiLevel}
+ +For developers, the Android {@sdkPlatformVersion} platform is available as a +downloadable component for the Android SDK. The downloadable platform includes +an Android library and system image, as well as a set of emulator +skins and more. The downloadable platform +includes no external libraries.
+ +To get started developing or testing against Android +{@sdkPlatformVersion}, use the Android SDK Manager to +download the platform into your SDK. For more information, +see Adding SDK +Components. If you are new to Android, download the SDK Starter Package +first.
+ +For a high-level introduction to Android {@sdkPlatformVersion}, see the Platform Highlights.
+ + +The sections below provide notes about successive releases of +the Android {@sdkPlatformVersion} platform component for the Android SDK, as denoted by +revision number. To determine what revision(s) of the Android +{@sdkPlatformVersion} platforms are installed in your SDK environment, refer to +the "Installed Packages" listing in the Android SDK and AVD Manager.
+ + + + +
+ Android {@sdkPlatformVersion}, Revision 1 (December 2010)
+ Requires SDK Tools r8 or higher.
+The sections below provide a technical overview of what's new for developers +in {@sdkPlatformVersion}, including new features and changes in the framework +API since the previous version.
+ + +The platform now includes a SIP protocol stack and framework API that lets +developers build internet telephony applications. Using the API, applications can offer +voice calling features without having to manage sessions, transport-level +communication, or audio — these are handled +transparently by the platform's SIP API and services.
+ +The SIP API is available in the {@link android.net.sip android.net.sip} +package. The key class is {@link android.net.sip.SipManager}, which applications +use to set up and manage SIP profiles, then initiate audio calls and receive +audio calls. Once an audio call is established, applications can mute calls, +turn on speaker mode, send DTMF tones, and more. Applications can also use the +{@link android.net.sip.SipManager} to create generic SIP connections.
+ +The platform’s underlying SIP stack and services are available on devices at +the discretion of the manufacturer and associated carrier. For this reason, +applications should use the {@link android.net.sip.SipManager#isApiSupported +isApiSupported()} method to check whether SIP support is available, before +exposing calling functionality to users.
+ +To use the SIP API, applications must request permission from the user by
+declaring <uses-permission
+android:name="android.permission.INTERNET"> and <uses-permission
+android:name="android.permission.USE_SIP"> in their manifest files.
Additionally, developers can request filtering on Android Market, such that
+their applications are not discoverable to users whose devices do not include
+the platform’s SIP stack and services. To request filtering, add <uses-feature
+android:name="android.software.sip"
+android:required="true"> and <uses-feature
+android:name="android.software.sip.voip"> to the application manifest.
To look at a sample application that uses the SIP API, see SIP Demo.
+ +Android 2.3 includes an NFC stack and framework API that lets developers +read NDEF tags that are discovered as a user touches an NFC-enabled device +to tag elements embedded in stickers, smart posters, and even other devices.
+ +The platform provides the underlying NFC services that work with the device +hardware to discover tags when they come into range. On discovering a tag, the +platform notifies applications by broadcasting an Intent, appending the tag's +NDEF messages to the Intent as extras. Applications can create Intent filters to +recognize and handle targeted tags and messages. For example, after receiving a +tag by Intent, applications extract the NDEF messages, store them, alert the +user, or handle them in other ways.
+ +The NFC API is available in the {@link android.nfc} package. The key classes are:
+ +NFC communication relies on wireless technology in the device hardware, so +support for the platform's NFC features on specific devices is determined by +their manufacturers. To determine the NFC support on the current device, +applications can call {@link android.nfc.NfcAdapter#isEnabled isEnabled()} to +query the {@link android.nfc.NfcAdapter}. The NFC API is always present, +however, regardless of underlying hardware support.
+ +To use the NFC API, applications must request permission from the user by
+declaring <uses-permission
+android:name="android.permission.NFC"> in their manifest files.
Additionally, developers can request filtering on Android Market, such that
+their applications are not discoverable to users whose devices do not support
+NFC. To request filtering, add
+<uses-feature android:name="android.hardware.nfc"
+android:required="true"> to the application's manifest.
To look at a sample application that uses the NFC API, see +NFCDemo.
+ +Android 2.3 adds platform and API support for several new sensor reading +types — gyroscope, rotation vector, linear acceleration, gravity, and barometer. +Developers can use the new sensor readings to create applications that respond +quickly and smoothly to precise changes in device position and motion. The +Sensor API reports gyroscope and other sensor changes to interested +applications, whether they are running on the application framework or in native +code.
+ +Note that the specific set of hardware sensors available on any given device +varies at the discretion of the device manufacturer.
+ +Developers can request filtering in Android Market, such that their
+applications are not discoverable to users whose devices do not offer a
+gyroscope sensor. To do so, add <uses-feature
+android:name="android.hardware.sensor.gyroscope"
+android:required="true"> to the application manifest.
For API details, see {@link android.hardware.Sensor}
+ + +Applications can now make use of any cameras that are available on a device, +for either photo or video capture. The {@link android.hardware.Camera} lets +applications query for the number of cameras available and the unique +characteristics of each.
+ +To look at sample code for accessing a front-facing camera, see CameraPreview.java +in the ApiDemos sample application.
+ +The Camera API also adds:
+The platform's media framework adds support for new per-track or global audio effects, +including bass boost, headphone virtualization, equalization, and reverb.
+To look at sample code for audio effects, see +AudioFxDemo.java +in the ApiDemos sample application.
+ +The media framework also adds:
+The platform includes a new {@link android.app.DownloadManager} system service
+that handles long-running HTTP downloads. Applications can request that a URI be
+downloaded to a particular destination file. The DownloadManager
+will conduct the download in the background, taking care of HTTP interactions
+and retrying downloads after failures or across connectivity changes and system
+reboots.
To help developers monitor and improve the performance of their applications, +the platform offers a new system facility called {@link android.os.StrictMode}. +When implemented in an application, StrictMode catches and notifies the +developer of accidental disk or network activity that could degrade application +performance, such as activity taking place on the application's main thread +(where UI operations are received and animations are also taking place). +Developers can evaluate the network and disk usages issues raised in StrictMode +and correct them if needed, keeping the main thread more responsive and +preventing ANR dialogs from being shown to users. + +
For more information about how to use StrictMode to optimize your +application, see the class documentation and sample code at {@link +android.os.StrictMode android.os.StrictMode}.
+ +overScrollMode, overScrollFooter, and
+overScrollHeader attributes for <ListView> elements,
+for controlling overscroll behavior.filterTouchesWhenObscured attribute for view elements,
+which declares whether to filter touches when the view's window is obscured by
+another visible window. When set to "true", the view will not
+receive touches whenever a toast, dialog or other window appears above the
+view's window. Refer to View security
+documentation for details.To look at sample code for touch filtering, see +SurfaceView.java +in the ApiDemos sample application.
+setComposingRegion method lets an application mark a
+region of text as composing text, maintaining the current styling. A
+getSelectedText method returns the selected text to the
+application. The methods are available in {@link
+android.view.inputmethod.BaseInputConnection}, {@link
+android.view.inputmethod.InputConnection}, and {@link
+android.view.inputmethod.InputConnectionWrapper}.textSelectHandle, textSelectHandleLeft,
+textSelectHandleRight, and textSelectHandleWindowStyle
+attributes for <TextView>, for referencing drawables that will be
+used to display text-selection anchors and the style for the containing
+window.The platform now supports extra large screen sizes, such as those that might
+be found on tablet devices. Developers can indicate that their applications are
+designed to support extra large screen sizes by adding a <supports
+screens ... android:xlargeScreens="true"> element to their manifest
+files. Applications can use a new resource qualifier, xlarge, to
+tag resources that are specific to extra large screens. For
+details on how to support extra large and other screen sizes, see Supporting Multiple
+Screens.
ACTION_SET_ALARM Intent
+action and extras that can be used to start an Activity to set a new alarm in an
+alarm clock application. Applications that wish to receive the
+SET_ALARM Intent should create an activity that requires the
+the SET_ALARM permission. Applications that wish to create a new
+alarm should use {@link
+android.content.Context#startActivity(android.content.Intent)
+Context.startActivity()}, so that the user has the option of choosing
+which alarm clock application to use.The LocationManager keeps track
+of all clients requesting periodic updates, and tells its providers
+about them as a WorkSource parameter, when setting their minimum
+update times.
+The network location provider uses WorkSource to track the
+wake and wifi locks initiated by an application and adds it to the application's
+battery usage reported in Manage Applications.
Android 2.3 exposes a broad set of APIs to applications that use native +code. Framework classes of interest to such applications include:
+ +NativeActivity and its underlying native code run in the system
+just as do other Activities — specifically they run in the Android
+application's system process and execute on the application's main UI thread,
+and they receive the same lifecycle callbacks as do other Activities. For full information on working with native code or to download the NDK, +see the Android NDK page.
+ + +binarySearch(),
+ copyOf(), copyOfRange(), and others.xlargeScreens attribute for <supports-screens>
+element, to indicate whether the application supports
+extra large screen form-factors. For details, see Supporting Multiple
+Screens.android:screenOrientation attribute of
+<activity> element:
+"reverseLandscape" — The Activity would like to have the
+screen in landscape orientation, turned in the opposite direction from normal
+landscape."reversePortait" — The Activity would like to have the
+screen in portrait orientation, turned in the opposite direction from normal
+portrait."sensorLandscape" — The Activity would like to have the
+screen in landscape orientation, but can use the sensor to change which
+direction the screen is facing."sensorPortrait" — The Activity would like to have the
+screen in portrait orientation, but can use the sensor to change which direction
+the screen is facing."fullSensor" — Orientation is determined by a physical
+orientation sensor: the display will rotate based on how the user moves the
+device. This allows any of the 4 possible rotations, regardless of what the
+device will normally do (for example some devices won't normally use 180 degree
+rotation).com.android.permission.SET_ALARM — Allows an application
+to broadcast an Intent to set an alarm for the user. An Activity that handles
+the {@link android.provider.AlarmClock#ACTION_SET_ALARM SET_ALARM} Intent action
+should require this permission.android.permission.USE_SIP — Allows an application to use
+the {@link android.net.sip SIP API} to make or receive internet calls.
+android.permission.NFC — Allows an application to use the
+{@link android.nfc NFC API} to make or receive internet calls.The platform adds several new hardware features that developers can declare +in their application manifests as being required by their applications. This +lets developers control how their application is filtered, when published on +Android Market.
+ +For full information about how to declare features and use them for
+filtering, see the documentation for <uses-feature>.
For a detailed view of all API changes in Android {@sdkPlatformVersion} (API +Level {@sdkPlatformApiLevel}), see the API +Differences Report.
+ + +The Android {@sdkPlatformVersion} platform delivers an updated version of +the framework API. The Android {@sdkPlatformVersion} API +is assigned an integer identifier — +{@sdkPlatformApiLevel} — that is +stored in the system itself. This identifier, called the "API Level", allows the +system to correctly determine whether an application is compatible with +the system, prior to installing the application.
+ +To use APIs introduced in Android {@sdkPlatformVersion} in your application,
+you need compile the application against the Android library that is provided in
+the Android {@sdkPlatformVersion} SDK platform. Depending on your needs, you might
+also need to add an android:minSdkVersion="{@sdkPlatformApiLevel}"
+attribute to the <uses-sdk> element in the application's
+manifest. If your application is designed to run only on Android 2.3 and higher,
+declaring the attribute prevents the application from being installed on earlier
+versions of the platform.
For more information about how to use API Level, see the API Levels document.
+ +The system image included in the downloadable platform provides these +built-in applications:
+ +
+
|
+
+
|
+
The system image included in the downloadable SDK platform provides a variety of +built-in locales. In some cases, region-specific strings are available for the +locales. In other cases, a default version of the language is used. The +languages that are available in the Android {@sdkPlatformVersion} system +image are listed below (with language_country/region locale +descriptor).
+ +
+
|
+
+ |
+
Note: The Android platform may support more +locales than are included in the SDK system image. All of the supported locales +are available in the Android Open Source +Project.
+ +The downloadable platform includes a set of emulator skins that you can use +for modeling your application in different screen sizes and resolutions. The +emulator skins are:
+ +For more information about how to develop an application that displays +and functions properly on all Android-powered devices, see Supporting Multiple +Screens.
diff --git a/docs/html/sdk/images/2.3/ffc.png b/docs/html/sdk/images/2.3/ffc.png new file mode 100644 index 000000000000..136a395fad1b Binary files /dev/null and b/docs/html/sdk/images/2.3/ffc.png differ diff --git a/docs/html/sdk/images/2.3/home-menu.png b/docs/html/sdk/images/2.3/home-menu.png new file mode 100644 index 000000000000..e9c8620bf0b3 Binary files /dev/null and b/docs/html/sdk/images/2.3/home-menu.png differ diff --git a/docs/html/sdk/images/2.3/home-plain.png b/docs/html/sdk/images/2.3/home-plain.png new file mode 100644 index 000000000000..a6255f6a4bb1 Binary files /dev/null and b/docs/html/sdk/images/2.3/home-plain.png differ diff --git a/docs/html/sdk/images/2.3/nfc.png b/docs/html/sdk/images/2.3/nfc.png new file mode 100644 index 000000000000..a21b6ab90a33 Binary files /dev/null and b/docs/html/sdk/images/2.3/nfc.png differ diff --git a/docs/html/sdk/images/2.3/onetouch.png b/docs/html/sdk/images/2.3/onetouch.png new file mode 100644 index 000000000000..2789612f02a6 Binary files /dev/null and b/docs/html/sdk/images/2.3/onetouch.png differ diff --git a/docs/html/sdk/images/2.3/power.png b/docs/html/sdk/images/2.3/power.png new file mode 100644 index 000000000000..7b0785d8351e Binary files /dev/null and b/docs/html/sdk/images/2.3/power.png differ diff --git a/docs/html/sdk/images/2.3/running.png b/docs/html/sdk/images/2.3/running.png new file mode 100644 index 000000000000..fe9a1a08f870 Binary files /dev/null and b/docs/html/sdk/images/2.3/running.png differ diff --git a/docs/html/sdk/images/2.3/selection.png b/docs/html/sdk/images/2.3/selection.png new file mode 100644 index 000000000000..46ff28c92523 Binary files /dev/null and b/docs/html/sdk/images/2.3/selection.png differ diff --git a/docs/html/sdk/images/2.3/sipcall.png b/docs/html/sdk/images/2.3/sipcall.png new file mode 100644 index 000000000000..48a5a1d12919 Binary files /dev/null and b/docs/html/sdk/images/2.3/sipcall.png differ diff --git a/docs/html/sdk/sdk_toc.cs b/docs/html/sdk/sdk_toc.cs index 0b74bd6d26b2..fe71914d98de 100644 --- a/docs/html/sdk/sdk_toc.cs +++ b/docs/html/sdk/sdk_toc.cs @@ -72,6 +72,14 @@ Started