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. Android includes facilities that automatically adjust application assets and UI layouts appropriately for the device, to ensure that third-party applications run well on a variety of hardware configurations [ Resources, 38 ].
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 includes support for applications to optionally specify that they require specific OpenGL texture compression formats. These formats are typically vendor-specific. Device implementations are not required by Android to implement any specific texture compression format. Android includes a mechanism for applications to declare that they wanted to enable hardware acceleration for 2D graphics at the Application, Activity, Window or View level through the use of a manifest tag android:hardwareAccelerated or direct API calls [ Resources, 9 ].
In Android 4. Android specifies a "compatibility mode" in which the framework operates in an 'normal' screen size equivalent dp width mode for the benefit of legacy applications not developed for old versions of Android that pre-date screen-size independence. 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 at least one of x, x, or x that is, p, p, or 4K. 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, p, or 4K in Android 4.
The Android platform includes APIs that allow applications to render rich graphics to the display. Android includes support for secondary display to enable media sharing capabilities and developer APIs for accessing external displays. If a device supports an external display either via a wired, wireless or an embedded additional display connection then the device implementation MUST implement the display manager API as described in the Android SDK documentation [ Resources, 75 ].
Device implementations that support secure video output and are capable of supporting secure surfaces MUST declare support for Display. Specifically, device implementations that declare support for Display. The upstream Android open source implementation includes support for wireless Miracast and wired HDMI displays that satisfies this requirement. The Home, Recents 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 on a distinct portion of the screen, gestures, touch panel, etc. Android supports both implementations.
All of these functions MUST be accessible with a single action e. The Home function MUST have a visible button or icon unless hidden together with other navigation functions in full-screen mode. The Menu function is deprecated in favor of action bar since Android 4. This Menu function should be presented unless hidden together with other navigation functions.
Android supports Assist action [ Resources, 63 ]. Device implementations MUST make the Assist action available to the user at all times when running applications. Device implementations MAY use a distinct portion of the screen to display the navigation keys, but if so, MUST meet these requirements:. Device implementations that do include a pointer input system:.
Android includes support for a variety of touch screens, touch pads, and fake touch input devices. Touch screen based device implementations are associated with a display [ Resources, 81 ] 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.
For example, a mouse or remote control that drives an on-screen cursor approximates touch, but requires the user to first point or focus then click. Numerous input devices like the mouse, trackpad, gyro-based air mouse, gyro-pointer, joystick, and multi-touch trackpad can support fake touch interactions. Device implementations that declare the fake touch feature MUST meet the fake touch requirements in Section 7.
Device implementations MUST report the correct feature corresponding to the type of input used. Device implementations that include a touchscreen single-touch or better MUST report the platform feature constant android. Device implementations that report the platform feature constant android.
Device implementations that declare support for android. Devices that declare support for android. Device implementations MAY omit a microphone. Conversely, device implementations that do possess a microphone:. Android includes APIs for accessing a variety of sensor types. Devices implementations generally MAY omit these sensors, as provided for in the following subsections. For example, device implementations:.
The list above is not comprehensive; the documented behavior of the Android SDK is to be considered authoritative. Some sensor types are synthetic, meaning they can be derived from data provided by one or more other sensors.
Examples include the orientation sensor, and the linear acceleration sensor. Android includes a notion of a "streaming" sensor, which is one that returns data continuously, rather than only when the data changes. Note that the device implementations MUST ensure that the sensor stream must not prevent the device CPU from entering a suspend state or waking up from a suspend state. If a device implementation does include a 3-axis accelerometer, it:.
If a device does include a 3-axis magnetometer, it:. If a device implementation includes a gyroscope, it:. Device implementations MAY include a barometer i. If a device implementation includes a barometer, it:. Device implementations MAY include an ambient thermometer i. Device implementations MAY include a proximity sensor. If a device implementation does include a proximity sensor, it MUST measure the proximity of an object in the same direction as the screen.
That is, the proximity sensor MUST be oriented to detect objects close to the screen, as the primary intent of this sensor type is to detect a phone in use by the user. If a device implementation has a proximity sensor, it MUST be have 1-bit of accuracy or more. While these voice calls may or may not be packet-switched, they are for the purposes of Android considered independent of any data connectivity that may be implemented using the same network.
Android MAY be used on devices that do not include telephony hardware. That is, Android is compatible with devices that are not phones. If a device implementation does include support for If a device implementation includes support for Wi-Fi direct, then it:.
If a device implementation does include NFC hardware, then it:. As the classes android. NdefMessage and android. Device implementations MUST include support for one or more forms of data networking.
Device implementations where a physical networking standard such as Ethernet is the primary data connection SHOULD also include support for at least one common wireless data standard, such as Device implementations MUST have the master auto-sync setting on by default so that the method getMasterSyncAutomatically returns "true" [ Resources, 88 ].
A rear-facing camera is a camera located on the side of the device opposite the display; that is, it images scenes on the far side of the device, like a traditional camera. A front-facing camera is a camera located on the same side of the device as the display; that is, a camera typically used to image the user, such as for video conferencing and similar applications. If a device implementation includes a rear-facing camera, it:. Device implementations MAY include a front-facing camera.
If a device implementation includes a front-facing camera, it:. For instance, cameras that lack autofocus MUST still call any registered android. AutoFocusCallback instances even though this has no relevance to a non-autofocus camera. Note that this does apply to front-facing cameras; for instance, even though most front-facing cameras do not support autofocus, the API callbacks must still be "faked" as described. Device implementations MUST recognize and honor each parameter name defined as a constant on the android.
Parameters class, if the underlying hardware supports the feature. Posted by techavidus. Posted by andrewstevenson. Posted by arthonsys. Posted by kisoo kim. Posted by Pablopablo. Posted by ghosthero. Posted by Kamran Mehmood. Posted by Chandra Mohan. Posted by MrGamix. Posted by Rob Pacinelli. Posted by Uday Shah.
Posted by Jeyanthan Rasalingam. Posted by thibault Posted by Kelly. Posted by Tanushree Pattayat Taps. Posted by asteriou Posted by Xavier Joy Gomes. Posted by Karthik Raja. Posted by Fred. Posted by Thunder Posted by brecklundin. Posted by Rajesh Varanasi. Posted by surfette Posted by El Komander. If you are using Windows 8, you may need to change some settings first.
How to solve driver installation looping on Windows 8 when running Kingo Android Root? Tick "Always allow from this computer". Rooting your Android has its own advantages and at the same time disadvantages. It is a matter of weighing pros and cons. Android rooting is a modification process to the original system, in which the limitations are removed and full-access is allowed and thus resulting in the ability to alter or replace system applications and settings, run specialized apps and even facilitate the removal and replacement of the device's operating system with a custom one.
Rooting your device will immediately void your warranty.. Android Rooting. Ubuntu phone on FP1, similar hardware as the Aquaris E4. This one is for chrmhoffmann: Thank you!
Backup in recovery mode FP1. Fairphone FP1U softbricked. Works perfectly for me! It even fixed the transparency bug in the play store! Please do so, not many downloads so far! Still, my point stands. Thank you chrmhoffmann!!!
0コメント