Android 5. Revision 1 March Initial release for Android 5. Revision 2 December Updated layouts in the Support Library and fixed various issues.
Revision 1 October Initial release for Android 5. Android 4. Revision 2 October Updated the rendering library. Revision 1 June Initial release for Android Wear.
Revision 2 December Maintenance release. Revision 1 October Initial release. Revision 2 August Maintenance update. Revision 1 July Initial release. Revision 2 February Maintenance update. Dependencies: SDK Tools r21 or higher is required. Revision 1 November Initial release. Dependencies: SDK Tools r20 or higher is required.
Revision 3 October Maintenance update. Revision 2 July Maintenance update. Revision 1 June Initial release. Revision 2 January Maintenance update. Dependencies: SDK Tools r14 or higher is required.
Revision 1 December Initial release. Android 3. SDK Tools r12 or higher is recommended. Notes: Improvements to the platform's rendering library to support the visual layout editor in the ADT Eclipse plugin. Notes: Fixes an issue with the visual layout editor rendering library that prevented Android 3. Android 2. Improve incremental installation performance. Fix adb push --sync with multiple inputs. Improve performance of incremental apk installation.
Improve error handling for incremental apk installation. Fix adb install-multi-package. Fix some more crashes related to adb wireless pairing. Improve some error messages. Fix fastboot flashall on older devices such as Nexus 7. Fix crash when using adb -H. Fix hang in adb logcat when run before a device is connected. Improve performance of adb install-multi on Android 10 or newer devices.
Update support for wireless pairing. Add support for incremental APK installation. Improve performance of adb push on high-latency connections. Fix hang when using adb install on something that isn't actually a file. Add --fastdeploy option to adb install , for incremental updates to APKs while developing. This also fixes a related bug in the Android Studio Profilers that causes an AdbCommandRejectedException , which you can see in the idea.
Fix devices going offline on Windows. Improve adb install output and help text. On Linux, when connecting to a newer adb server, instead of killing the server and starting an older one, adb attempts to launch the newer version transparently. Previously, adb root; adb wait-for-device could mistakenly return immediately if adb wait-for-device started before adb noticed that the device had disconnected. Fixes authentication—when the private key used for authentication does not match the public key—by calculating the public key from the private key, instead of assuming that they match.
Updated Windows requirements The platform tools now depend on the Windows Universal C Runtime, which is usually installed by default via Windows Update. If you see errors mentioning missing DLLs, you may need to manually fetch and install the runtime package.
Upon disconnection, adb will attempt to reconnect for up to 60 seconds before abandoning a connection. Fix Unicode console output on Windows. Thanks to external contributor Spencer Low! Fix a file descriptor double-close that can occur, resulting in connections being closed when an adb connect happens simultaneously.
Fix adb forward --list when used with more than one device connected. For example, let's suppose that we want to use the NotificationBuilder. SetCategory method to categorize a notification when running on Android 5.
Referring to the Android version table at the beginning of this guide, we see that the build version code for Android 5. To support older versions of Android where SetCategory is not available, our code can detect the API level at runtime and conditionally call SetCategory only when the API level is greater than or equal to the Lollipop build version code:.
In this example, our app's Target Framework is set to Android 5. Lollipop and later, this example code will call SetCategory only when it is actually available — it will not attempt to call SetCategory when the API level is 16, 17, 18, 19, or The functionality is reduced on these earlier Android versions only to the extent that notifications are not sorted properly because they are not categorized by type , yet the notifications are still published to alert the user.
Our app still works, but its functionality is slightly diminished. In general, the build version check helps your code decide at runtime between doing something the new way versus the old way. For example:. There's no fast and simple rule that explains how to reduce or modify your app's functionality when it runs on older Android versions that are lacking one or more APIs.
In some cases such as in the SetCategory example above , it's sufficient to omit the API call when it's not available. However, in other cases, you may need to implement alternate functionality for when Android. SdkInt is detected to be less than the API level that your app needs to present its optimum experience. When you create a Xamarin.
Android library project such as a class library or a bindings library , you can configure only the Target Framework setting — the Minimum Android version and the Target Android version settings are not available. That is because there is no Android Manifest page:. Android library project, there is no Android Application page where you can configure the Minimum Android version and the Target Android version — the Minimum Android version and Target Android version settings are not available.
The Minimum Android version and Target Android version settings are not available because the resulting library is not a stand-alone app — the library could be run on any Android version, depending on the app that it is packaged with. You can specify how the library is to be compiled , but you can't predict which platform API level the library will be run on.
With this in mind, the following best practices should be observed when consuming or creating libraries:. When consuming an Android library — If you are consuming an Android library in your application, be sure to set your app's Target Framework setting to an API level that is at least as high as the Target Framework setting of the library.
When creating an Android library — If you are creating an Android library for use by other applications, be sure to set its Target Framework setting to the minimum API level that it needs in order to compile. These best practices are recommended to help prevent the situation where a library attempts to call an API that is not available at runtime which can cause the app to crash. If you are a library developer, you should strive to restrict your usage of API calls to a small and well-established subset of the total API surface area.
Doing so helps to ensure that your library can be used safely across a wider range of Android versions. This guide explained how Android API levels are used to manage app compatibility across different versions of Android.
It provided detailed steps for configuring the Xamarin. It also provided a comprehensive list that relates API levels to Android version numbers such as Android 4. Android build version codes. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No. Any additional feedback? Using the drop-down menu to the right of Minimum Android version , you can set the Minimum Android version for your application: If you select Automatic — use target framework version , the Minimum Android version will be the same as the Target Framework setting.
In the drop-down menu under Target Android version you can select the Target Android version for your application: We recommend that you explicitly set the Target Android version to the latest version of Android that you use to test your app. Using the drop-down menu to the right of Target Android version , you can set the Target Android version for your application: We recommend that you explicitly set the Target Android version to the latest version of Android that you use to test your app.
That is because there is no Android Manifest page: When you create a Xamarin.
0コメント