To better document how android.control.zoomRatio works, add diagrams to
illustrate its relationship with scalerCropRegion.

Test: Build and read docs
Bug: 144780745
Change-Id: I90b93c4d516f6f1e2d427ed3d56e85b6c94befe8

Intended for backward compatibility support for camera apps that do
not handle multi-window scenarios like inset portrait or foldables
with dynamic screen changes.

Test: New CTS tests pass
Bug: 134631897
Change-Id: I1cc85d4413e6af2b490b86916933a5cd7ce84a6a

To better document the cropping specification for camera2, add diagrams
from source.android.com into the reference docs as well.

Test: Docs build, look correct

Change-Id: I18a9c3801e19f39164f0d8c19c0cc001f142024f

Add code demo and result image.

Bug: 1526775
Test: make offline-sdk-docs
Change-Id: Ie8f7aa67a49dd79389e3973c2d94a204a1315e11

Bug: 112621694
Test: make offline-sdk-docs
Change-Id: I6d8f022eb24d1d1b17a97999d15a798a04ec0df3

Created new BlendMode enum that maps to XferModes with additional
supported native values that map to SkBlendMode constants
Created new BlendModeColorFilter
Deprecated PorterDuffColorMode and PorterDuffColorFilter in
favor of BlendMode and BlendModeColorFilter.
Updated Paint API to use setBlendMode and deprecated setXfermode

Bug: 119671925
Bug: 112166079
Bug: 73224934
Test: Added CTS tests for BlendMode and BlendModeColorFilter
Change-Id: Idd50e2f0b81975c5ecf6f1c0edd4eb68198d9131

Bug: 74942037
Merged-In: I6ac4bd9e7a6d9bb2b8e3d1303656c0cdc525178b
Change-Id: I6ac4bd9e7a6d9bb2b8e3d1303656c0cdc525178b

These files are used by devsite only, so are maintained in piper.

bug: 79155333
test: make ds-docs (human review)

Change-Id: I5d5662a2a401872a669dba0916b20a79bcfca7ae
(cherry picked from commit 9e64abe7)

These files are used by devsite only, so are maintained in piper.

Change-Id: I5d5662a2a401872a669dba0916b20a79bcfca7ae

Fixes: 76462084
Test: make doc-comment-check-docs, open $ANDROID_BUILD_TOP/out/target/common/docs/doc-comment-check/reference/android/view/WindowManager.LayoutParams.html, navigate to LAYOUT_IN_DISPLAY_CUTOUT_MODE_SHORT_EDGES
Change-Id: I8a9df979cbb062896fa874a163414a4f8a095b21

* add an image for better description
* add constraints between TextView height and padding
* fix broken link (getLineSpacing)

Test: make -offline-sdk-docs
Test: Visual inspection on generated doc, screenshot attached to ticket
Bug: 74032223
Change-Id: I34b91454d3a43f8cb5a450c8d34de9f1abde0d52

Bug: 74942037
Change-Id: I6ac4bd9e7a6d9bb2b8e3d1303656c0cdc525178b

Test: TypefaceSpanTest.java
Bug: 26946279
Change-Id: I99a46fbc41ada567731f034f515998654ce77cb2

Test: N/A
Bug: 72092996
Change-Id: Iecd3595a03cde2a1d58e4be00b7cf9b6783d4e2a

spans.

Test: N/A
Bug: 72092996
Change-Id: I716ed3841d7ac0b1cc2f75021ae0e02d1bf05524

Test: QuoteSpanTest
Bug: 72410257
Change-Id: Ie0e159b4f645b7935454ad25fd43c5d0e8f3d7c1

Test: BulletSpanTest
Bug: 72217003
Change-Id: I0ba4d93bd5a7bac02410e0edbd4b20f254959d4e

Test: N/A
Bug:72092996
Change-Id: I2706465d3d61117b0b5b9e6a013f213988c92521

Test: N/A
Bug: 72092996
Change-Id: Iec7f378557759e2fdd2969f579e1dfd4635b123a

We use the devsite tool to stage reference docs for review (to
go/dac-stage). That tool is currently broken, because it's expecting
to find a _reference-head-tags.html file which currently exists in
Piper but not in Gerrit. Copying that file into Gerrit lets us
build the Javadocs and stage them. (Files in p/f/b/docs don't
generally affect anything outside of the doc builds.)

Tested by building docs and staging Adapter.html to:
go/dac-stage/reference/android/widget/Adapter.html

Test: make ds-docs
Bug: 71717397
Change-Id: I05430f2d9f23e62b4423b2d6f304c4be1c43b880

- Move camera reference doc images to /reference/images
- Minor formatting changes due to merging SDK/NDK metadata definitions
- Minor wording changes for the same

Bug: 69175492
Bug: 29102963
Bug: 33262893
Test: Build and manual inspection of generated docs diff
Change-Id: Ieaf0c1943eba378cc94a22d184734602c40e25e7

Previously deleted almost all the docs (with CL http://ag/1970807),
since those docs are now managed and staged/published from Piper.
However, reference docs are still generated in Gerrit, so it's useful
to be able to stage those docs from a Gerrit client--and that was
broken by my change, since the staging tool expects to see
_book.yaml and _project.yaml in the reference doc directory. So,
restoring those files to re-enable staging of reference docs from
Gerrit.

The publish process is *not* changed: we still grab a good build
from the appropriate Gerrit branch and migrate those files into
Piper, then publish the Piper files.

Test: make ds-docs ; devsite stage --site=android en/reference
Change-Id: I392f1699dc68767d1ac9b7113a149062e5e48ef7

It tooks 10 years, but better late than never!

Bug: 32984164
Test: Compiled documentation and checked in Chrome
Change-Id: I6dfd7fba6d3077f8c774b203589083bdbc15f9d2

Original Change-Id: I5331cdc968be817ff70ba32dd03fce76493a6ab8
Test: make ds-docs

Android developer docs are now maintained in Piper, go/dac-source

Removing all files from Gerrit, since these files can cause build
errors if they refer to classes that are later removed (whence
bug b/35849713 ).

Gerrit already has readme files in these directories telling people
docs are not maintained here; these readmes will be a lot easier to
spot now.

Ran a doc build with these files deleted, and it seems to work fine,
so submitting this CL *shouldn't* break anything.

Change-Id: Ic74c3f97f9620daf23543930a8b7ed1386f4d172

Bug: 35849713

Android developer docs are now maintained in Piper, go/dac-source

Removing all files from Gerrit, since these files can cause build
errors if they refer to classes that are later removed (whence
bug b/35849713 ).

Gerrit already has readme files in these directories telling people
docs are not maintained here; these readmes will be a lot easier to
spot now.

Ran a doc build with these files deleted, and it seems to work fine,
so submitting this CL *shouldn't* break anything.

Merged to master to resolve conflict.
Merged-In: Ic74c3f97f9620daf23543930a8b7ed1386f4d172

Bug: 35849713
Change-Id: I5331cdc968be817ff70ba32dd03fce76493a6ab8

Original Change-Id: I5331cdc968be817ff70ba32dd03fce76493a6ab8
Test: make ds-docs

Android developer docs are now maintained in Piper, go/dac-source

Removing all files from Gerrit, since these files can cause build
errors if they refer to classes that are later removed (whence
bug b/35849713 ).

Gerrit already has readme files in these directories telling people
docs are not maintained here; these readmes will be a lot easier to
spot now.

Ran a doc build with these files deleted, and it seems to work fine,
so submitting this CL *shouldn't* break anything.

Bug: 35849713
Change-Id: Ic74c3f97f9620daf23543930a8b7ed1386f4d172

Test: make PRODUCT-sdk_google_aw_x86-sdk
Change-Id: I8e13f43520e609808a9825fa3c89f4233076c5a9

Change-Id: I40cea46efd80c448640ff69753698fe8404da40b

Bug: 32984164
Test: Config_test, AaptConfig_test and aapt2_tests
Change-Id: Ie9c82bfe2d36b1d6180ee223250ab5bb2ce90dd4

Bug: 30989383
Test: Unit test for aapt2
Change-Id: I66dc65af6327b94fed74538bee08cada0b8be4fa

Test: m -j49 -k docs
BUG: 34106216
Change-Id: I366b0bf085ad3fd166b7961301bb8c35da6a7630

Change-Id: Ia091df49099482696abbc3a596cf1787ca904d67

This configuration uses 64 bits per pixel. Heach component is stored as a
half precision float value (16 bits). Half floats can be decoded/encoded
using android.util.Half.

RGBA_F16 bitmaps are used to decode wide-gamut images stored in 16 bit
formats (PNG 16 bit for instance). aapt is currently not aware of PNG
16 bits so such files must be placed in raw/ resource directories.

This first pass provides only partial drawing support with hardware
acceleration. RGBA_F16 bitmaps are stored in linear space and need
to be encoded to gamma space with the appropriate OETF to be rendered
properly on Android's current surfaces. They are however suitable for
linear blending. Full rendering support will be provided in a future
CL (BitmapShaders might be a bit tricky to handle properly during
shader generation).

Bug: 32984164
Test: bit CtsGraphicsTestCases:android.graphics.cts.BitmapRGBAF16Test

Change-Id: I328e6b567441a1b9d152a3e7be944a2cf63193bd

Bug: 33457676
Change-Id: I8be25b41fe54ec3cd328373d4577ee3e292f5581

Bug: 33408968
Test: n/a
Change-Id: I497b2a24248c1511c0d6eca4d5951451e4870b83

Change-Id: Id3c0d448b7aa4cafd87cfa46408c62a6fb0f3e57

ColorSpace.createRenderer() returns a ColorSpace.Renderer which
can be used to visualize multiple color spaces and colors (each
associated with a specific color space) in the same CIE 1931 xyY
chromaticity diagram. This API was used to generate all the
diagrams shown in the documentation.

Bug: 32984164
Test: ColorSpaceTest in CTS
Change-Id: Ic94d939d5cfd563d826701f5e876b67b47ed56ec

Bug: 32984164
Test: make offline-sdk-referenceonly-docs and manual validation of output

Change-Id: I2f0e00e5a0581517bb7c535e8aee150f87ac7a6e

Revised the Drawable example with VectorDrawable-friendly example

Bug: 18009084
Change-Id: Ia6d0ad46a352601c7032244b17d28b9dd690de1d

The "Testing In-app Billing" page now includes a note which explains
that test subscription purchases must use real purchase IDs, not
any of the IDs reserved for testing one-time in-app purchases.

Bug: 27352434
Change-Id: I625178c3517ce9940bc4746d99f1d506fd5e944b