drgreen/android_frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge "fix code type and mention api level 21 exception for bindService()" into lmp-docs

Browse Source
This commit is contained in:
smain@google.com
2014-11-12 17:41:35 +00:00
committed by Android (Google) Code Review
parent 4b7b68d824 9adc33a658
commit f9c4f6b56e
1 changed files with 8 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/html/guide/components/intents-filters.jd
View File

@ -139,7 +139,9 @@ only with an explicit intent.</p>
intent when starting a {@link android.app.Service} and do not
declare intent filters for your services. Using an implicit intent to start a service is a
security hazard because you cannot be certain what service will respond to the intent,
and the user cannot see which service starts.</p>
and the user cannot see which service starts. Beginning with Android 5.0 (API level 21), the system
throws an exception if you call {@link android.content.Context#bindService bindService()}
with an implicit intent.</p>
@ -424,18 +426,18 @@ android.content.Intent#createChooser createChooser()} and pass it to {@link
android.app.Activity#startActivity startActivity()}. For example:</p>
<pre>
Intent intent = new Intent(Intent.ACTION_SEND);
Intent sendIntent = new Intent(Intent.ACTION_SEND);
...
// Always use string resources for UI text.
// This says something like "Share this photo with"
String title = getResources().getString(R.string.chooser_title);
// Create intent to show chooser
Intent chooser = Intent.createChooser(intent, title);
// Create intent to show the chooser dialog
Intent chooser = Intent.createChooser(sendIntent, title);
// Verify the intent will resolve to at least one activity
// Verify the original intent will resolve to at least one activity
if (sendIntent.resolveActivity(getPackageManager()) != null) {
startActivity(sendIntent);
startActivity(chooser);
}
</pre>