Lines Matching full:applications
52 integrating connected peripherals with applications running on the platform.
55 interactions. Using the APIs, developers can create applications that are able to
82 both USB devices and USB accessories. Applications can acquire an instance of
114 their applications are not availabe to users whose devices do not provide the
133 <p>For complete information about how to develop applications that interact with
137 <p class="note">To look at sample applications that use the USB host API, see <a
144 <p>Android 3.1 exposes a new MTP API that lets applications interact directly
185 specification. Methods in the class let applications get a device?s
189 5.3.1 of the MTP specification. Methods in the class let applications get an
200 these capabilities to let users interact with their applications using mice,
257 motion data to applications. For a full list of axes and their intended
261 <p>The platform provides motion events to applications in batches, so a single
263 Applications should use {@link android.view.MotionEvent#getHistorySize()} to get
267 getHistoricalAxisValue()}. After that, applications should process the current
273 getAxisValue()}, applications can call {@link android.view.MotionEvent#getX(int)
289 instead. For this reason, it's important for applications to interpret axis
291 event, applications should use methods on the {@link android.view.InputDevice}
293 applications can use {@link android.view.InputDevice#getMotionRanges()
314 receive joystick events. If needed, applications can handle these events at the
328 stack, which applications
362 <p>To use the RTP API, applications must request permission from the user by
451 <li>Applications can use a new method
454 to a View. This gives applications improved control over 3D transformations of
481 applications intercept fragment-breadcrumb clicks and take any action needed
562 <li>A new high-performance Wi-Fi lock lets applications maintain
564 Applications that stream music, video, or voice for long periods can acquire the
566 is off. Because it uses more power, applications should acquire the
577 <li>Applications can now access statistics about more types of network usage
578 using new methods in {@link android.net.TrafficStats}. Applications can use the
585 <li>Applications can now get and set the SIP auth username for a profile
600 <li>Applications can now initiate downloads that notify users only on
601 completion. To initiate this type of download, applications pass {@link
616 <li>Applications can start the Downloads application in sort-by-size mode by
656 applications</h3>
659 applications that are in a stopped state and provides a means of controlling
660 their launch from background processes and other applications.</p>
671 Include intent filters of stopped applications in the list of potential targets
674 Exclude intent filters of stopped applications from the list of potential
679 behavior is to include filters of stopped applications in the list of
685 inadvertently or unnecessarily launching components of stoppped applications.
688 intents that should be allowed to activate stopped applications.</p>
690 <p>Applications are in a stopped state when they are first installed but are not
692 Applications).</p>
722 <li>A new {@link android.util.LruCache} class lets your applications benefit
723 from efficient caching. Applications can use the class to reduce the time spent
790 applications:</p>
825 <p>Google Play filters applications based on features declared in <a
