- 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
Docs had incorrectly said the element was named
<uses-permission-sdk23> (missing a hyphen in sdk-23). Fixing all
references to that element, and renaming the reference page
accordingly. A separate CL sets up a redirect from the old page
name to the new one.
See first comment for doc stage location.
Change-Id: I6e675e03f87851d36465a8fdf3de730de524c4a8
bug: 25346975
Removed the now-obsolete ActionBar API guide; it's been
superseded by the AppBar training class
(http://developer.android.com/training/appbar/ )
Changed the most important ActionBar links and references to point to
the AppBar docs (or some other appropriate page).
A separate CL will set up redirects from the ActionBar API guide.
See first comment for doc stage location.
bug: 25194804
Change-Id: I0859ea1712971fcf2f6cf131b2a5221b5bf3ea44
There are a couple of 'signature' permissions that have a special
user-authorization process; mentioned them and put in a link to their
reference docs.
The reference docs for those methods is being updated in a separate
CL, http://ag/784299
See first comment for doc stage location.
bug: 24673125
Change-Id: I4f17784b570d6154482e3fe965bd2de1043babb6
The "Hello Views" tutorial no longer exists, links to it redirect
to the "Declaring Layouts" API guide. Removing old links to that page.
See first comment for doc stage location.
bug: 21674339
Change-Id: I885a41fb3b213d4dc6257959d43dbf73e0c753bd
With Android M, the Apache HTTP client is no longer supported.
Removing references to that client and the clients that depend
on it (DefaultHttpClient and AndroidHttpClient). Replacing, when
appropriate, with references to HttpURLConnection.
Also removing references to the 2011 blog post "Android's HTTP
Clients" (https://goto.google.com/cusll) since that post is largely
about the ex-clients.
Fixed a couple of other small errors while I had the files open
(for example, changed a sample URL in a code snippet to the safe
www.example.com).
bug: 19696844
Change-Id: Iabf780140c37d5fc95c0d45542c425a945c69337
Updates the docs to reflect the new Android M "runtime permissions"
model. (There's also a new training class, in a separate CL:
http://ag/762246 ) Removed the M Preview permissions page (but didn't
remove all references to it--Q will do that in a separate CL).
See first comment for doc stage location.
bug: 23725768
Change-Id: Iafb801f1188d1bb6b66ac19c9c1dfce0114df271
Replacing the existing "ActionBar" training docs with new, up-to-date
ones focused on using the appcompat Toolbar. Ultimately these lessons
will also replace the existing ActionBar UI guide.
See first comment for doc stage location.
Change-Id: Ic20362ec4c4fc872c4388b05367451ae8072938b
List of issues from https://code.google.com/p/android/issues that are fixed by this CL: 183476,183249,183248,183241,183222,183142,183093,183329,182385,182311,182193,182019,73149,181589,179740,179384,178322,178189,178086,178020,177169,176312,175138,172322,172030,171820,170647,167288,163574,161580,161041,159199,151347,144290,136137,132505
Change-Id: I2e96f7444048abd2f666c75bd6ab9640019afb75
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
