This undoes the automerger skip which occured in
commit e740c84dc3 and
replays it as a standard (NOT -s ours) merge.
Change-Id: If5a47be26f73d6a0735c425cd66310a3e2a89086
In N and above when using an Android Network Security Config the
cleartext configuration from that is used and
android:usesCleartextTraffic in the manifest is ignored.
Bug:27596429
Change-Id: I50ec765cead6cfd6bbaec585723f99d72e0fd945
The end of the first paragraph of the "Creating a Notification"
section (within the "Notifications" page) now links to the correct
version of notify() -- i.e. the one within the NotificationManager
class.
Bug: 27708810
Change-Id: I7cc9608f646518bf5f7fc3f4a231c9dece693363
Bug: 22767853
- Correct the description about renderscriptTargetApi: Use the lowest
API level providing all the functionality in the code.
- Update the sample gradle config to use the up-to-date and stable
version of Build-Tools.
Change-Id: Ie8008acafb270fda9e2c928953568461f6f6f476
The table listing the different Android API levels (within the
"<uses-sdk>" page) now contains accurate links for "Android 6.0" APIs
and "Platform Highlights."
Bug: 27725763
Change-Id: I7cc9734b84ac530223a6bae58aed0072dcd214aa
Make the docs reflect changes in private file access permissions.
Starting with API level 24 app private files are exclusively accessible
to the owning app. Files can no longer be shared by name because apps
cannot relax the files system permissions.
Bug: 27636012
Change-Id: Iac80504b06f6e37ce109222092f77788ed388393
Within the "Resource values" sub-section within the "File Conventions"
section of the "App Manifest" page, changed the separator between the
name/value pair for resources and themes such that it is now
consistently a '/' character.
Bug: 27070041
Change-Id: Ie299fbb866b9de3afaffa8fb70e3ca3709c45735
Make the docs reflect changes in private file access permissions.
Starting with API level 24 app private files are exclusively accessible
to the owning app. Files can no longer be shared by name because apps
cannot relax the files system permissions.
Bug: 27636012
Change-Id: Ibcb5032986c819829fa13ba07a74f20f2997e995
Added a curly brace at the beginning of "onProvideShadowMetrics()."
This method appears within the sample code associated with step 2 of
the "Designing a Drag and Drop Operation" section of the topic.
Bug: 24561657
Change-Id: Icb06a65f63bc57c747bb6f244f6b623c17bdfc45
In the previous version, if a device had both a gravity sensor and
an accelerometer, but did not have the Google Inc. version 3 gravity
sensor, we would end up using no sensor at all. We change this to
have the code use an accelerometer in this case, which more closely
matches the surrounding description text.
Change-Id: I095b94d0d8207d3106db022dc337dd537ee0fa82
Initial pass at Network Security Config documentation, this also adds a
Security section to the list of topics which is currently just a stub.
Bug: 26931435
Change-Id: Iae0ec98a202ad3222b8f3ef39df77ecd2316504a
While checking the manifest for N permissions changes, I saw a
normal permission that had been added in M and not documented.
(The permission was added to AndroidManifest.xml, so it *was*
being listed in the android.Manifest javadoc.)
See first comment for doc stage location.
bug: 27222922
Change-Id: I5740fdb3da3cac37b15d87fe5f092d305c52449d
List of normal permissions had drifted from alphabetical order;
fixed.
See first comment for doc stage location.
Change-Id: I031d1142275c9fd53a2ce16fcd54fdcf206d03a7
Per bug b/26383626 , the FLASHLIGHT permission was never actually
used, and isn't checked by the new CameraManager.setTorchMode()
method. The permission has been removed from the manifest on
master; there's no reason to list it now in the list of normal
permissions.
See first comment for doc stage location.
bug: 26383626
Change-Id: I0c39dd5e1cdde1fc6a85759663b7e5ad669dc280
Just a missing period; I'll build (see first comment for stage
location) then if it looks good I'll submit.
bug: 26359756
Change-Id: I1f0619f23559abadacccc9a60d19aaf69713a6e2
Fixed a typo and also removed a couple of extra blank lines. I'll
build (to make sure I didn't break anything) then if it looks good
I'll self-+2 and commit.
bug: 26359706
Change-Id: Idc873ad774769819708c3d227d23e676a7fa1a90
The doc previously said that you need just the normal FLASHLIGHT
permission to turn on the flashlight. This was wrong in a couple of
ways: For the (deprecated) Camera API, you need CAMERA permission just
to get the Camera object (which you use to turn on the flash); for
the new Camera2 API, you don't need any permissions at all to turn
on "torch mode". So I've removed this example and replaced with a more
straightforward example of a normal permission (setting the time
zone).
I've filed a separate bug, b/26308110 , to update the FLASHLIGHT
permission docs (once I've confirmed the right update to make).
See first comment for doc stage location, but if the build is
okay I'll just go ahead and submit.
bug: 26104001
Change-Id: Ie0802b4818bd0ba4d3fd026e32620978827e50df
