The code snippet was copied straight from the MediaBrowserService
sample app. Since the code snippet consisted almost entirely of
calls to *other* methods in that sample app, the snippet wasn't
very helpful--and it wouldn't be helpful to add a lot of verbiage
explaining the sample app. So instead, I made the code more generic
(e.g. comments saying "You need to write code to check for XYZ")
followed by a link to the sample app.
Fixed other miscellaneous problems in the code snippets while we had
the file open.
See first comment for doc stage location.
bug: 20008288
Change-Id: Ic080ebffcc43e332ec3335b730c07ef5f8b64fa9
Updated reference to note that SYSTEM_ALERT_WINDOW is now "signature"
instead of "dangerous". (The Manifest.permission class and javadoc
is automatically generated from Manifest.xml.)
Also clarified how an app can request SYSTEM_ALERT_WINDOW and
WRITE_SETTINGS privileges (it's different than for ordinary
'dangerous' permissions).
See first comment for doc stage location.
bug: 24673125
Change-Id: Id5908b6cc8c8ea3d6901f245cd35c771bdd2eb87
Update storage related docs on Context to be consistent, and to call
out relevant Environment methods. Start calling it "shared" storage,
and only mention external for historical reasons. Mention that there
isn't much benefit to using emulated storage over private data
directories to help guide developers to safer locations.
Point out which paths can change over time, so developers know to
only persist relative paths.
Update Environment docs to reflect how they behave for the new
class of adopted storage devices.
Bug: 24251945
Change-Id: Ie5ab337649b4740dfd7594997bbb19c4969cfd2f
(cherry picked from commit 59d28dc82000b1696ed9ef7ef2c0d7fbb2834100)
Replaces the existing action views/action providers section in the
(soon to be removed) "ActionBar API Guide" page. Builds on
http://ag/730414 (which covers the basic app bar topics).
Some of the action providers doc is being moved into the
Javadoc reference for appropriate classes--that's being tracked
with CL http://ag/748902
See comment on patch set 2 for doc stage location.
Change-Id: Ia62b5155d7f67dc8922fc11917a12a957bf27fb1
Fixing erroneous putString() call, replaced with putBitmap().
Confirmed in search that error is not present elsewhere in the docs.
Bug: 19129506
Change-Id: I00152480cbdcd1b655c093e789a0462d80d5f829
As per Robert Anderberg's recommendation, removed the manifest example that
doesn't include android:required="false" and updated description text to
indicate the example works with apps that "support" a game controller rather
than "require". Updated Robert's suggestion with more concise version from
Andrew's suggestion. Note that we're not adding info on specifying
android:required="true" because this causes the app to not be installable on
any devices (because controllers aren't currently considered part of a device,
so it ends up looking like no devices have controllers at install time)
Bug: 22727418
Bug: 24098562
Change-Id: Ie4dd02d5599b9ffda53e46dc5af4765d888e81a4
