From 7076e3d268f60260cd12f0891e0817b6e51b2ede Mon Sep 17 00:00:00 2001 From: Android Partner Docs Date: Mon, 30 Jul 2018 13:18:19 -0700 Subject: Docs: Changes to source.android.com - 206634774 Fix the the typo by Danielle Roberts - 206631277 Cloned from CL 206063702 by 'g4 patch'. by Android Partner Docs - 206601799 Devsite localized content from translation request 959539. by Android Partner Docs - 206372799 Removing link to Amazon search results for Hikey 960 board by Heidi von Markham - 206195220 Add descriptions for the userdebug and eng build, and add... by Christina Nguyen - 206182120 Updating link for Amazon Hikey960 board by Heidi von Markham - 206055823 Update list view image by Kenneth Lau - 206043905 Devsite localized content from translation request 953120. by Android Partner Docs - 206017492 Devsite localized content from translation request 956349. by Android Partner Docs - 205941731 Devsite localized content from translation request 956391. by Android Partner Docs PiperOrigin-RevId: 206634774 Change-Id: I2960075d48d06acb2accb3663399f02f0706b734 --- en/devices/_toc-tech.yaml | 10 +- en/devices/architecture/vintf/index.html | 2 +- en/devices/tech/config/update.html | 227 +++++++++++++++++++++ .../tech/settings/images/settings-guidelines06.png | Bin 88777 -> 88179 bytes en/setup/build/building.html | 56 +++-- en/setup/build/devices.html | 5 +- en/setup/develop/new-device.html | 24 +++ 7 files changed, 296 insertions(+), 28 deletions(-) create mode 100644 en/devices/tech/config/update.html (limited to 'en') diff --git a/en/devices/_toc-tech.yaml b/en/devices/_toc-tech.yaml index 632c6778..211a990e 100644 --- a/en/devices/_toc-tech.yaml +++ b/en/devices/_toc-tech.yaml @@ -28,7 +28,13 @@ toc: - title: Ambient Capabilities path: /devices/tech/config/ambient - title: Carrier Customization - path: /devices/tech/config/carrier + section: + - title: Carrier Configuration + path: /devices/tech/config/carrier + - title: APN and CarrierConfig + path: /devices/tech/config/update + - title: UICC + path: /devices/tech/config/uicc - title: File DAC Configuration path: /devices/tech/config/filesystem - title: Namespaces for Libraries @@ -39,8 +45,6 @@ toc: path: /devices/tech/config/runtime_perms - title: Time Zone Rules path: /devices/tech/config/timezone-rules - - title: UICC - path: /devices/tech/config/uicc - title: USB HAL path: /devices/tech/config/usb-hal - title: Visual Voicemail diff --git a/en/devices/architecture/vintf/index.html b/en/devices/architecture/vintf/index.html index b0517a32..fe1fc07d 100644 --- a/en/devices/architecture/vintf/index.html +++ b/en/devices/architecture/vintf/index.html @@ -84,7 +84,7 @@ it is statically-defined.

  • The device manifest describes the static component of what -the device can provide to the the framework.
    • +the device can provide to the framework.
  • The framework compatibility matrix describes what the Android framework expects from a given device. The matrix is a static entity whose composition is determined manually during development of the next release diff --git a/en/devices/tech/config/update.html b/en/devices/tech/config/update.html new file mode 100644 index 00000000..db1a9cd9 --- /dev/null +++ b/en/devices/tech/config/update.html @@ -0,0 +1,227 @@ + + + APN and CarrierConfig + + + + + + +

    Carriers can update their Access Point Name (APN) information and their +carrier-specific configuration settings +(CarrierConfig) +in the Android Open Source Project (AOSP).

    + +

    Google Account with your corporate email address

    + +

    To update APN information or your CarrierConfig, you need +to submit the request using a Google Account with an active corporate email +address (e.g., An APN update request from Acme Company should come from an +email address such as foobar@acme.com).

    +

    If you do not have a Google Account that links to your corporate email +address, sign out of all Gmail accounts from your browser (we recommend you use +a private browsing feature such as an incognito window to avoid confusion with +your other accounts) and then + create a Google +account with your corporate email address.

    + + + + + + +

    Prepare a local development environment

    + +

    If you've never submitted code to AOSP before, you will +need to initialize your build environment, become familiar with the tools, and +understand how to submit patches:

    + + +

    In addition, we strongly recommend that you use the +Google Issue Tracker +to track changes.

    + +

    File a bug

    + +
      +
    1. Go to issuetracker.google.com + and sign in using your corporate email address (see + Google Account with your corporate email address).
      2. + +
    2. After logging in, click Create issue on the left side of the + screen.
      3. +
    3. In Component, select Android Public Tracker > Framework
      4. +
    4. Continue to APN update or + CarrierConfig update, as appropriate, + to enter the Title and Description.
      5. +
    + +

    APN bug

    + +

    Set the bug attributes as follows:

    +

    Title: Add/Modify/Remove APNs for CarrierXYZ

    +

    Description: Add a detailed description of the changes you're +requesting, including the APN settings themselves.

    + +

    CarrierConfig bug

    + +

    Set the bug attributes as follows:

    +

    Title: Config changes for CarrierXYZ

    +

    Description: Add a detailed description of the changes you're +requesting.

    + +

    Submit changes

    + +

    When you're ready to make changes, follow these steps:

    +
      +
    1. Identify which file to change.
      2. +
    2. Make changes to the file.
      3. +
    3. Commit the changes to your local repository by following the instructions + for + submitting patches, paying attention to the commit message guidelines, + including recommended format.
      4. +
    4. After you commit your change to your personal history, upload it to Gerrit + using the repo upload command.
      5. +
    5. Following a successful upload, repo provides the URL of a new page on + Gerrit. Use this URL to: +
        +
      • View your patch on the review server
        • +
      • Add comments
        • +
      • Request specific reviewers for your patch
        • +
      +
      6. +
    + + + +

    APN syntax

    + +

    Android project name - device/sample

    +

    File name(s) - etc/apns-full-conf.xml +(Google +Git master link)

    +

    The file contains APN settings in XML format and serves as a sample file +so there is no change in the behavior of Android devices.

    +

    A typical APN config looks like this:

    + +
    <apn carrier="CarrierXYZ"
+      mcc="123"
+      mnc="123"
+      apn="carrierxyz"
+      type="default,supl,mms,ims,cbs"
+      mmsc="http://mms.carrierxyz.com"
+      mmsproxy="0.0.0.0"
+      mmsport="80"
+      bearer_bitmask="4|5|6|7|8|12"
+/>
+
    + +

    Testing

    +
      +
    1. Connect any Android device for which you have root access.
      2. +
    2. Add settings to /etc/apns-conf.xml.
      3. +
    3. Reset APN settings.
      4. +
    4. In APN settings, confirm that profiles are loaded correctly.
      5. +
    5. For each profile, test data connectivity, Wi-Fi hotspot, and MMS + to make sure they work correctly.
      6. +
    + +

    Commit message

    + +
    [Example - "Add CarrierXYZ apns to sample apns"]
+Bug: [Issue ID from Google Issue Tracker]
+Test: No change to behavior as this is only a sample file
+
    + +

    Sample CL

    +

    See +Sample BICS APNs for an example CL.

    + +

    CarrierConfig syntax

    + +

    Project name - platform/packages/apps/CarrierConfig

    +

    File name(s) - assets/carrier_config_.xml +(Google +Git master link)

    +

    Identify the relevant XML file(s) in the assets folder by the relevant MCC/MNC +tuple(s). The file contains the carrier config object in XML format. The +attribute names are defined as keys under the + +CarrierConfigManager, and the type of value (int/string/bool) is indicated +by the suffixes.

    +

    Typical int/string/bool attributes look like this:

    + +
    <int name="vvm_port_number_int" value="5499" />
+<string name="vvm_type_string">vvm_type_omtp</string >
+<boolean name="vvm_cellular_data_required_bool" value="true" />
+
    + +

    Commit message

    + +
    [Example - "Add VVM settings for CarrierXYZ"]
+
+[Example - "Updated <mccmnc> carrier config file to include VVM settings
+as defined by CarrierXYZ."]
+
+Bug: [Issue ID from Google Issue Tracker]
+Test: [Testing notes]
+
    + +

    Sample CL

    +

    See an +updated carrier config file for an example CL.

    + +

    Request a review

    + +

    To request a review:

    +
      +
    • Go to the Gerrit URL of your change and add + android-carrier-config-review@google.com as a reviewer.
      • +
    • You can also add your Google contact to the CC list on Gerrit.
      • +
    • For tracking purposes, you can change the assignee of the issue to + android-carrier-config-review@google.com.
      • +
    + +

    After a submission makes it through the review and verification process, +Gerrit automatically merges the change into the public repository. Other users +can run repo sync to pull the update into their local client.

    + + + + diff --git a/en/devices/tech/settings/images/settings-guidelines06.png b/en/devices/tech/settings/images/settings-guidelines06.png index ab48475a..369c9380 100644 Binary files a/en/devices/tech/settings/images/settings-guidelines06.png and b/en/devices/tech/settings/images/settings-guidelines06.png differ diff --git a/en/setup/build/building.html b/en/setup/build/building.html index 43054987..0cc83c3a 100644 --- a/en/setup/build/building.html +++ b/en/setup/build/building.html @@ -91,28 +91,42 @@ target from the menu.

    BUILD is a codename referring to the particular feature combination. The BUILDTYPE is one of the following:

    - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + +
    BuildtypeUse
    userlimited access; suited for production
    userdebuglike user but with root access and debuggability; preferred for -debugging
    engdevelopment configuration with additional debugging tools
    BuildtypeUse
    userlimited access; suited for production
    userdebuglike user but with root access and debuggability; preferred for + debugging
    engdevelopment configuration with additional debugging tools
    + +

    The userdebug build should behave the same as the user build, with the +ability to enable additional debugging that normally violates the security +model of the platform. This makes the userdebug build good for user testing +with greater diagnosis capabilities. When developing +with the userdebug build, you should follow the +userdebug guidelines.

    + +

    The eng build prioritizes engineering productivity for engineers who work on +the platform. The eng build turns off various optimizations used to provide a +good user experience. Otherwise, the eng build behaves similar to the user and +userdebug builds so that device developers can see how the code behaves in +those environments.

    +

    For more information about building for and running on actual hardware, see Running Builds.

    diff --git a/en/setup/build/devices.html b/en/setup/build/devices.html index 20aa2a80..ad24391b 100644 --- a/en/setup/build/devices.html +++ b/en/setup/build/devices.html @@ -48,9 +48,8 @@ or HiKey960 development board.

    HiKey960 boards

    -

    The HiKey960 board is available in a 3GB RAM configuration from LeMaker (via -Amazon.com) -and from Lenovator. +

    The HiKey960 board is available from Amazon.com and + Lenovator.

    HiKey960 board image diff --git a/en/setup/develop/new-device.html b/en/setup/develop/new-device.html index 6f7b3e72..35aa1936 100644 --- a/en/setup/develop/new-device.html +++ b/en/setup/develop/new-device.html @@ -143,6 +143,30 @@ addition to tagged modules.
    • +

    userdebug guidelines

    + +

    Running userdebug builds in testing helps device developers understand +performance and power of in-development releases. To maintain consistency +between user and userdebug builds, and to achieve reliable metrics in builds +used for debugging, device developers should follow these guidelines:

    + +
      +
    • userdebug is defined as a user build with root access enabled, except: +
        +
      • userdebug-only apps that are run only on-demand by the user
        • +
      • Operations that run only during idle maintenance (on charger / fully + charged), such as using dex2oatd versus + dex2oat for background compiles
        • +
      +
      • +
    • Do not have any features that depend on the build type in order to be + enabled by default or not. Developers are discouraged from using any form of logging that affects battery life, such as debug logging or heap dumping.
      • +
    • Any debugging features that are enabled by default in userdebug should be + clearly defined and shared with all developers working on the project. Only + enable those debugging features on a limited-time basis until the issue is + resolved.
      • +
    +

    Customize the Build with Resource Overlays

    The Android build system uses resource overlays to customize -- cgit v1.2.3