Owners of the Samsung Nexus S can now enjoy the latest Android 4. Google has finally released an over-the-air update package for the Nexus S.
Some have already received the update, while others are still waiting for it to arrive on their phones. Unfortunately, the update seems to be only for the T-Mobile and retail variants of the Nexus S.
Take note of the following important things you need to know before you proceed with the updating process:. Did our step-by-step guide work perfectly on your Nexus S? How good is Android 4. How to Install Android 4. How To. Native code compatibility is challenging. For this reason, it should be repeated that device implementers are VERY strongly encouraged to use the upstream implementations of the libraries listed above to help ensure compatibility.
Because it is not feasible to develop a comprehensive test suite for a web rendering system, device implementers MUST use the specific upstream build of WebKit in the WebView implementation. Note that as the web development standards bodies are transitioning to favor IndexedDB over webstorage, IndexedDB is expected to become a required component in a future version of Android.
However, even if an alternate Browser application is used, the android. The behaviors of each of the API types managed, soft, native, and web must be consistent with the preferred implementation of the upstream Android open source project [ Resources, 3 ].
Some specific areas of compatibility are:. The above list is not comprehensive. The Compatibility Test Suite CTS tests significant portions of the platform for behavioral compatibility, but not all. It is the responsibility of the implementer to ensure behavioral compatibility with the Android Open Source Project. Android follows the package and class namespace conventions defined by the Java programming language.
To ensure compatibility with third-party applications, device implementers MUST NOT make any prohibited modifications see below to these package namespaces:. A "publicly exposed element" is any construct which is not decorated with the " hide" marker as used in the upstream Android source code.
Note that the restrictions above correspond to standard conventions for naming APIs in the Java programming language; this section simply aims to reinforce those conventions and make them binding through inclusion in this compatibility definition. Device implementations MUST configure Dalvik to allocate memory in accordance with the upstream Android platform, and as specified by the following table.
See Section 7. Note that memory values specified below are considered minimum values, and device implementations MAY allocate more memory per application. Android defines a component type and corresponding API and lifecycle that allows applications to expose an "AppWidget" to the end user [ Resources, 18 ]. The Android Open Source reference release includes a Launcher application that includes user interface affordances allowing the user to add, view, and remove AppWidgets from the home screen.
Device implementations MAY substitute an alternative to the reference Launcher i. Alternative Launchers MAY omit these user interface elements; however, if they are omitted, the device implementation MUST provide a separate application accessible from the Launcher that allows users to add, configure, view, and remove AppWidgets. Device implementations MUST be capable of rendering widgets that are 4 x 4 in the standard grid size. Android includes APIs that allow developers to notify users of notable events [ Resources, 19 ], using hardware and software features of the device.
Some APIs allow applications to perform notifications or attract attention using hardware, specifically sound, vibration, and light.
Device implementations MUST support notifications that use hardware features, as described in the SDK documentation, and to the extent possible with the device implementation hardware. Note that this behavior is further detailed in Section 7. Additionally, the implementation MUST correctly render all resources icons, sound files, etc. Device implementers MAY provide an alternative user experience for notifications than that provided by the reference Android Open Source implementation; however, such alternative notification systems MUST support existing notification resources, as above.
Android 4. Android includes APIs [ Resources, 22 ] that allow developers to incorporate search into their applications, and expose their application's data into the global system search.
Generally speaking, this functionality consists of a single, system-wide user interface that allows users to enter queries, displays suggestions as users type, and displays results. The Android APIs allow developers to reuse this interface to provide search within their own apps, and allow developers to supply results to the common global search user interface.
Device implementations MUST include a single, shared, system-wide search user interface capable of real-time suggestions in response to user input. Device implementations MUST implement the APIs that allow developers to reuse this user interface to provide search within their own applications.
Device implementations MUST implement the APIs that allow third-party applications to add suggestions to the search box when it is run in global search mode. If no third-party applications are installed that make use of this functionality, the default behavior SHOULD be to display web search engine results and suggestions.
Applications can use the "Toast" API defined in [ Resources, 23 ] to display short non-modal strings to the end user, that disappear after a brief period of time. Device implementations MUST display Toasts from applications to end users in some high-visibility manner. Android provides "themes" as a mechanism for applications to apply styles across an entire Activity or application. Android 3. Android defines a component type and corresponding API and lifecycle that allows applications to expose one or more "Live Wallpapers" to the end user [ Resources, 26 ].
Live Wallpapers are animations, patterns, or similar images with limited input capabilities that display as a wallpaper, behind other applications. Hardware is considered capable of reliably running live wallpapers if it can run all live wallpapers, with no limitations on functionality, at a reasonable framerate with no adverse affects on other applications. As an example, some live wallpapers may use an Open GL 1. Live wallpaper will not run reliably on hardware that does not support multiple OpenGL contexts because the live wallpaper use of an OpenGL context may conflict with other applications that also use an OpenGL context.
Device implementations capable of running live wallpapers reliably as described above SHOULD implement live wallpapers. The upstream Android 4. Device implementations MAY alter or eliminate this user interface; however, a future version of Android is planned to make more extensive use of this functionality. Device implementations are strongly encouraged to use the upstream Android 4. The Android 4. If device implementations do not support the full range of device administration policies, they MUST NOT allow device administration applications to be enabled.
Specifically, if a device does not support all device administration policies, the device implementation MUST respond to the android.
In addition, Android 4. Device implementations MUST provide an implementation of the Android accessibility framework consistent with the default Android implementation. Specifically, device implementations MUST meet the following requirements. An open source implementation of an accessibility service is available from the Eyes Free project [ Resources, 31 ].
Device implementers SHOULD use the reference upstream implementation of Dalvik, and the reference implementation's package management system. Device implementations MUST include at least one form of audio output, such as speakers, headphone jack, external speaker connection, etc.
Device implementations MUST support the core media formats specified in the Android SDK documentation [ Resources, 58 ] except where explicitly permitted in this document. Specifically, device implementations MUST support the media formats, encoders, decoders, file types and container formats defined in the tables below.
All of these codecs are provided as software implementations in the preferred Android implementation from the Android Open Source Project. Please note that neither Google nor the Open Handset Alliance make any representation that these codecs are unencumbered by third-party patents.
Those intending to use this source code in hardware or software products are advised that implementations of this code, including in open source software or shareware, may require patent licenses from the relevant patent holders. Note that these tables do not list specific bitrate requirements for most video codecs because current device hardware does not necessarily support bitrates that map exactly to the required bitrates specified by the relevant standards.
Instead, device implementations SHOULD support the highest bitrate practical on the hardware, up to the limits defined by the specifications. Android device implementations that include a rear-facing camera and declare android. When an application has used the android. AudioRecord API to start recording an audio stream, device implementations that include microphone hardware and declare android. In addition to the above recording specifications, when an application has started recording an audio stream using the android.
That is, these requirements are optional in Android 4. Existing and new devices that run Android 4. Audio latency is broadly defined as the interval between when an application requests an audio playback or record operation, and when the device implementation actually begins the operation. Many classes of applications rely on short latencies, to achieve real-time effects such sound effects or VOIP communication.
Device implementations that include microphone hardware and declare android. See Section 7 for details on the conditions under which microphone hardware may be omitted by device implementations. If a device implementation meets the requirements of this section, it MAY report support for low-latency audio, by reporting the feature "android. PackageManager class. Specifically, devices MUST support the following media network protocols:.
Most Linux-based systems and Apple Macintosh systems recognize Android devices using the standard Android SDK tools, without additional support; however Microsoft Windows systems typically require a driver for new Android devices. If a device implementation is unrecognized by the adb tool as provided in the standard Android SDK, device implementers MUST provide Windows drivers allowing developers to connect to the device using the adb protocol.
If an API in the SDK interacts with a hardware component that is stated to be optional and the device implementation does not possess that component:.
A typical example of a scenario where these requirements apply is the telephony API: even on non-phone devices, these APIs must be implemented as reasonable no-ops. The Android UI framework supports a variety of different screen sizes, and allows applications to query the device screen size aka "screen layout" via android.
Specifically, device implementations must report the correct screen size according to the following logical density-independent pixel dp screen dimensions.
Device implementations MUST correctly honor applications' stated support for small, normal, large, and xlarge screens, as described in the Android SDK documentation.
The Android UI framework defines a set of standard logical densities to help application developers target application resources. Device implementations MUST report one of the following logical Android framework densities through the android. If the standard Android framework density that is numerically closest to the physical density results in a screen size that is smaller than the smallest supported compatible screen size dp width , device implementations SHOULD report the next lowest standard Android framework density.
Device implementations MUST report correct values for all display metrics defined in android. DisplayMetrics [ Resources, 39 ]. Devices MUST support dynamic orientation by applications to either portrait or landscape screen orientation. That is, the device must respect the application's request for a specific screen orientation.
Device implementations MAY select either portrait or landscape orientation as the default. Devices MUST report the correct value for the device's current orientation, whenever queried via the android.
Devices MUST report which screen orientations they support android. For example, a device with a fixed-orientation landscape screen, such as a television or laptop, MUST only report android. That is:. Note that Android 4. These formats are typically vendor-specific. Device implementations are not required by Android 4. In Android 4. Device implementations MUST include support for legacy application compatibility mode as implemented by the upstream Android open source code.
Fixed-pixel device implementations MAY use screens of any pixel dimensions, provided that they meet the requirements defined this Compatibility Definition. Fixed-pixel implementations MAY include a video output port for use with an external display. However, if that display is ever used for running apps, the device MUST meet the following requirements:.
For example, a tablet that is 7" diagonal size with a x pixel resolution is considered a fixed-pixel large mdpi display implementation. If it contains a video output port that displays at p or p, the device implementation MUST scale the output so that applications are only executed in a large mdpi window, regardless of whether the fixed-pixel display or video output port is in use.
Variable-pixel device implementations MUST support one or both of x, or x that is, p or p. Device implementations with variable-pixel screens MAY change screen configuration or mode at runtime or boot-time. For example, a user of a set-top box may replace a p display with a p display, and the device implementation may adjust accordingly. Additionally, variable-pixel device implementations MUST report the following configuration buckets for these pixel dimensions:. For clarity, device implementations with variable pixel dimensions are restricted to p or p in Android 4.
The Android platform includes APIs that allow applications to render rich graphics to the display. The Home, Menu and Back functions are essential to the Android navigation paradigm. Device implementations MUST make these functions available to the user at all times when running applications.
These functions MAY be implemented via dedicated physical buttons such as mechanical or capacitive touch buttons , or MAY be implemented using dedicated software keys, gestures, touch panel, etc. Device implementations MAY use a distinct portion of the screen to display the navigation keys, but if so, MUST meet these requirements:. Touch screen based device implementations are associated with a display [ Resources, 61 ] such that the user has the impression of directly manipulating items on screen.
Since the user is directly touching the screen, the system does not require any additional affordances to indicate the objects being manipulated. In contrast, a fake touch interface provides a user input system that approximates a subset of touchscreen capabilities. In Android 6. On Android 5. Browse All iPhone Articles Browse All Mac Articles Do I need one?
Browse All Android Articles Browse All Smart Home Articles Customize the Taskbar in Windows Browse All Microsoft Office Articles What Is svchost. Browse All Privacy and Security Articles Browse All Linux Articles Browse All Buying Guides. Best Portable Monitors. Best Gaming Keyboards. Best Drones. Best 4K TVs. Best iPhone 13 Cases. Best Tech Gifts for Kids Aged Best 8K TVs.
Best VR Headsets. Best iPad Mini Cases.
0コメント