- Clarify hardware.camera feature being only for the back camera
- Clarify what setting a CaptureRequest field to null does
- Use preCorrectionActiveArray instead of activeArray in list of
possible raw output sizes
- Clarify length of GPS processing field for camera1 API
Bug: 24540625
Bug: 23908116
Bug: 23051627
Bug: 17345901
Change-Id: Iaf11fdf626268cf30f66b3628153ec3ac770c4f4
Per Chris, the existing doc was incorrect: you *can't* check for a
button press and a switch flip the same way. (The button triggers a
click event, but the switch does not.) Chris suggested that we just
remove the reference to onClick and suggest using a listener for
both kinds of buttons (ToggleButton and Switch).
Also pulled one note out of a section where it didn't fit (the bit
about changing a button/switch's state programmatically didn't have
much to do with listening for clicks) and put it at the top, and I
fixed a Javadoc typo for a relevant class that I happened to notice.
See first comment for doc stage location.
bug: 20625504
Change-Id: I9c8975111381e5b169f6a61454ef3a93da635759
* commit 'c8a94c5b6df42b631e52dcae03d0243454886ecb':
Doc change: Explicitly state the initial API level that supports maxSdkVersion attr in uses-permission.
Per bug b/10641907, putting fragments in the root view *only* works
if the device runs Android 3.0 or later. Chris and Adam say
we don't really want to suggest that work flow even for these devices,
so I'm taking that info out.
bug: 10641907
Change-Id: Ie44acbb534b8e0cea8dbbfaaf2c65836b1c31be6
Removing the read/write profile/social stream permissions as they
are not needed anymore. These permissions are for accessing data
nested in the conacts provider which is already guaded by the
read/write contacts runtime permissions. The removed permissions
would be in the contacts group which means they would not provide
more protection compated to read/write contacts. Also removing
the permissions voids the need for app op support for legacy apps.
Removed deprecated APIs for social streams as these were deprecated
and will go away in the next release. We want apps targeting M to
not be able to compile if still suing these APIs to help with
migration.
Change-Id: I26ed9055847af7f92c78eb0f4ac8f9f1aa616fcd
* commit 'c3fbb0ce6c04ea5ece37bf4529271cb14296135b':
Fixes a typo where parens were used instead of curly braces, preventing a link from being created at build time.
- The dev guide has moved to Github, where we can easily maintain it
together with the code.
- I'd like us to still keep this page on the Android site, to direct
developers toward using ExoPlayer.
- I have no idea what branch this should be on, but can easily cherry-pick
to another one as required.
Change-Id: I9179b822988698053463eed7162e970cab3e1ae4
cherry-pick from CL: https://android-review.googlesource.com/148241
This CL replaces the Doxygen generated documentation by one that's created
by our internal tool found in framework/rs/api. The big advantages:
- Can handle overloaded functions. Doxygen could not and RenderScript has many.
- Can have version information.
- Can match the look of the Java documentation.
- Cleaner look and no leaking of internal paths.
This CL also include changes introduced by the L release which was missing
previously.
Change-Id: Icade41d04d35e45c445ad952bb8ce14389f9f59f
* commit '62eaad7200e172404db587ecec9940670946e92a':
cherrypick from lmp-docs Docs: Correcting how to escape quotes. Original Change-Id: I417546a473f0ebe76a6e4102b87883a85365ac26
Original Change-Id: I417546a473f0ebe76a6e4102b87883a85365ac26
The behavior for single and double-quotes is different--I expanded
this section to note how they differ.
bug: 19959941
Change-Id: I9be9c066c416e9403a3ac164af0b1ce35f7ab1dd
