Update summary descriptions for new samples.
Change-Id: Icf39a554cb6a91d4ba9e8d76c3f40dae3ace60ac
This commit is contained in:
Dirk Dougherty
@@ -6,8 +6,8 @@ sample.group=RenderScript
|
|||||||
@jd:body
|
@jd:body
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
|
This sample demonstrates the basic steps for using RenderScript. In this
|
||||||
BasicRenderScript sample demonstrates basic steps how to use renderScript.
|
example, the app uses <a href=
|
||||||
In the sample, it performs graphical filter operation on a image with renderScript.
|
"{@docRoot}guide/topics/renderscript/compute.html">RenderScript</a> to
|
||||||
|
perform graphical filter operations on a image.
|
||||||
</p>
|
</p>
|
||||||
|
|||||||
@@ -6,16 +6,22 @@ sample.group=Sensors
|
|||||||
@jd:body
|
@jd:body
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
|
This sample demonstrates the use of the two step sensors (step detector and
|
||||||
This sample demonstrates the use of the two step sensors (step detector and counter) and
|
counter) and sensor batching. It shows how to register a {@link
|
||||||
sensor batching.\n\n It shows how to register a SensorEventListener with and without
|
android.hardware.SensorEventListener} with and without batching and shows how
|
||||||
batching and shows how these events are received.\n\nThe Step Detector sensor fires an
|
these events are received.
|
||||||
event when a step is detected, while the step counter returns the total number of
|
</p>
|
||||||
steps since a listener was first registered for this sensor.
|
|
||||||
Both sensors only count steps while a listener is registered. This sample only covers the
|
<p>
|
||||||
basic case, where a listener is only registered while the app is running. Likewise,
|
The Step Detector sensor fires an event when a step is detected, while the
|
||||||
batched sensors can be used in the background (when the CPU is suspended), which
|
step counter returns the total number of steps since a listener was first
|
||||||
requires manually flushing the sensor event queue before it overflows, which is not
|
registered for this sensor. Both sensors only count steps while a listener is
|
||||||
covered in this sample.
|
registered.
|
||||||
|
</p>
|
||||||
</p>
|
|
||||||
|
<p>
|
||||||
|
This sample only covers the basic case, where a listener is only registered
|
||||||
|
while the app is running. Likewise, batched sensors can be used in the
|
||||||
|
background (when the CPU is suspended), which requires manually flushing the
|
||||||
|
sensor event queue before it overflows, which is not covered in this sample.
|
||||||
|
</p>
|
||||||
|
|||||||
@@ -6,12 +6,14 @@ sample.group=Connectivity
|
|||||||
@jd:body
|
@jd:body
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
|
This sample demonstrates how to emulate an NFC card, using the <a href=
|
||||||
This sample demonstrates how to emulate an NFC card, using the "host card emulation"
|
"{@docRoot}guide/topics/connectivity/nfc/hce.html">Host Card Emulation</a>
|
||||||
feature added in Android 4.4. This sample makes the device appear as a loyalty card
|
feature added in Android 4.4. This sample makes the device appear as a
|
||||||
whenever the screen is on and the user taps their device on an appropriately configured
|
loyalty card whenever the screen is on and the user taps their device on an
|
||||||
NFC reader.
|
appropriately configured NFC reader.
|
||||||
|
</p>
|
||||||
|
|
||||||
The "CardReader" sample can be used to read the loyalty card implemented in this sample.
|
<p>
|
||||||
|
The <a href="{@docRoot}samples/CardReader/index.html">CardReader</a> sample
|
||||||
</p>
|
can be used to read the loyalty card implemented in this sample.
|
||||||
|
</p>
|
||||||
|
|||||||
@@ -6,12 +6,15 @@ sample.group=Connectivity
|
|||||||
@jd:body
|
@jd:body
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
|
This sample demonstrates how to implement a low-level NFC card reader, for
|
||||||
This sample demonstrates how to implement a low-level NFC card reader, for reading cards
|
reading cards that do not contain NDEF or Android Beam data. This sample is
|
||||||
that do not contain NDEF or Android Beam data. This sample is designed to read the virtual
|
designed to read the virtual loyalty card implemented in the <a href=
|
||||||
loyalty card implemented in the "CardEmulation" sample.\n\n
|
"{@docRoot}samples/CardEmulation/index.html">CardEmulation</a> sample.
|
||||||
|
</p>
|
||||||
|
|
||||||
In particular, this sample demonstrates how to disable Android Beam, select which AIDs the
|
<p>
|
||||||
reader is interested, and establish communication with the card
|
In particular, this sample demonstrates how to disable Android Beam, select
|
||||||
|
which AIDs the reader is interested in, and establish communication with the
|
||||||
</p>
|
card. See <a href="{@docRoot}guide/topics/connectivity/nfc/hce.html">Host-based
|
||||||
|
Card Emulation</a> for more information on the HCE APIs.
|
||||||
|
</p>
|
||||||
|
|||||||
@@ -6,9 +6,10 @@ sample.group=RenderScript
|
|||||||
@jd:body
|
@jd:body
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
|
This sample demonstrates how to use <a href=
|
||||||
RenderScriptIntrinsic sample that demonstrates how to use RenderScript intrinsics.
|
"http://android-developers.blogspot.com/2013/08/renderscript-intrinsics.html">
|
||||||
Creates several RenderScript intrinsics and shows a filtering result with various parameters.
|
RenderScript intrinsics</a>. The app creates several RenderScript intrinsics
|
||||||
Also shows how to extends RedioButton with StateListDrawable.
|
and shows a filtering result with various parameters. The sample also shows
|
||||||
|
how to extend {@link android.widget.RadioButton} with {@link
|
||||||
</p>
|
android.graphics.drawable.StateListDrawable}.
|
||||||
|
</p>
|
||||||
|
|||||||
@@ -4,10 +4,6 @@
|
|||||||
page.tags="RepeatingAlarm"
|
page.tags="RepeatingAlarm"
|
||||||
sample.group=Background
|
sample.group=Background
|
||||||
@jd:body
|
@jd:body
|
||||||
|
|
||||||
<p>
|
|
||||||
|
<p>This sample demonstrates how to implement a repeating alarm using an {@link android.app.AlarmManager}.</p>
|
||||||
Introductory text that explains what the sample is intended to demonstrate. Edit
|
|
||||||
in template-params.xml.
|
|
||||||
|
|
||||||
</p>
|
|
||||||
|
|||||||
@@ -6,8 +6,9 @@ sample.group=UI
|
|||||||
@jd:body
|
@jd:body
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
|
This sample shows how to use <code><a href=
|
||||||
A basic sample which shows how to use SlidingTabLayout to display a custom
|
"{@docRoot}samples/SlidingTabsBasic/src/com.example.android.common/view/SlidingTabLayout.html">
|
||||||
ViewPager title strip which gives continuous feedback to the user when scrolling.
|
SlidingTabLayout</a></code> to display a custom {@link
|
||||||
|
android.support.v4.view.ViewPager ViewPager} title strip that gives
|
||||||
</p>
|
continuous feedback to the user when scrolling.
|
||||||
|
</p>
|
||||||
@@ -6,8 +6,9 @@ sample.group=UI
|
|||||||
@jd:body
|
@jd:body
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
|
This sample shows a more advanced example of how to use a <code><a href=
|
||||||
A more advanced sample which shows how to use SlidingTabLayout to display a custom
|
"{@docRoot}samples/SlidingTabsColors/src/com.example.android.common/view/SlidingTabLayout.html">
|
||||||
ViewPager title strip, with custom coloring for each tab.
|
SlidingTabLayout</a></code> to display a custom {@link
|
||||||
|
android.support.v4.view.ViewPager ViewPager} title strip, with custom
|
||||||
</p>
|
coloring for each tab.
|
||||||
|
</p>
|
||||||
Reference in New Issue
Block a user