fuquan/allwinner_a64
1
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

upload android base code part4

Browse source
This commit is contained in:
August 2018-08-08 17:00:29 +08:00
parent b9e30e05b1
commit 78ea2404cd
23455 changed files with 5250148 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

2
android/compatibility/cdd/6_dev-tools-and-options/6_0_intro.md Normal file
View file

@ -0,0 +1,2 @@
# 6\. Developer Tools and Options Compatibility

37
android/compatibility/cdd/6_dev-tools-and-options/6_1_developer_tools.md Normal file
View file

@ -0,0 +1,37 @@
## 6.1\. Developer Tools
Device implementations:
* [C-0-1] MUST support the Android Developer Tools provided in the Android
SDK.
* [**Android Debug Bridge (adb)**](http://developer.android.com/tools/help/adb.html)
* [C-0-2] MUST support all adb functions as documented in the Android
SDK including [dumpsys](https://source.android.com/devices/input/diagnostics.html).
* [C-0-3] MUST NOT alter the format or the contents of device system
events (batterystats , diskstats, fingerprint, graphicsstats, netstats,
notification, procstats) logged via dumpsys.
* [C-0-4] MUST have the device-side adb daemon be inactive by default and
there MUST be a user-accessible mechanism to turn on the Android Debug
Bridge.
* [C-0-5] MUST support secure adb. Android includes support for secure
adb. Secure adb enables adb on known authenticated hosts.
* [C-0-6] MUST provide a mechanism allowing adb to be connected from a
host machine. For example:
* Device implementations without a USB port supporting peripheral mode
MUST implement adb via local-area network (such as Ethernet or Wi-Fi).
* MUST provide drivers for Windows 7, 9 and 10, allowing developers to
connect to the device using the adb protocol.
* [**Dalvik Debug Monitor Service (ddms)**](http://developer.android.com/tools/debugging/ddms.html)
* [C-0-7] MUST support all ddms features as documented in the Android SDK.
As ddms uses adb, support for ddms SHOULD be inactive by default, but
MUST be supported whenever the user has activated the Android Debug Bridge,
as above.
* [**Monkey**](http://developer.android.com/tools/help/monkey.html)
* [C-0-8] MUST include the Monkey framework and make it available for
applications to use.
* [**SysTrace**](http://developer.android.com/tools/help/systrace.html)
* [C-0-9] MUST support systrace tool as documented in the Android SDK.
Systrace must be inactive by default and there MUST be a user-accessible
mechanism to turn on Systrace.

19
android/compatibility/cdd/6_dev-tools-and-options/6_2_developer_options.md Normal file
View file

@ -0,0 +1,19 @@
## 6.2\. Developer Options
Android includes support for developers to configure application
development-related settings.
Device implementations MUST provide a consistent experience for
Developer Options, they:
* [C-0-1] MUST honor the [android.settings.APPLICATION_DEVELOPMENT_SETTINGS](
http://developer.android.com/reference/android/provider/Settings.html#ACTION_APPLICATION_DEVELOPMENT_SETTINGS)
intent to show application development-related settings. The upstream Android
implementation hides the Developer Options menu by default and enables users to
launch Developer Options after pressing seven (7) times on the **Settings** >
**About Device** > **Build Number** menu item.
* [C-0-2] MUST hide Developer Options by default and MUST provide a mechanism
to enable Developer Options without the need for any special whitelisting.
* MAY temporarily limit access to the Developer Options menu, by visually
hiding or disabling the menu, to prevent distraction for scenarios where the
safety of the user is of concern.