Lines Matching full:application
28 a Surface or a SurfaceTexture. When rendering to a SurfaceTexture, the application can apply
59 stream and one AAC audio elementary stream. The application provides
98 <h3>Adding OpenMAX AL to your application source code</h3>
120 Finding or creating useful multimedia content for your application is
321 OpenMAX AL for Android supports a single engine per application, and
331 OpenMAX AL and OpenSL ES may be used together in the same application.
334 The application should first create both engines, then use both engines,
349 can be significant for an application developer, so it is important
356 standard. An application developed with this version should
363 your application source code to conform to the new API. We expect
368 We recommend that your application follow these guidelines,
378 Application callback handlers generally run in a restricted context,
433 Note that use these extensions will limit your application's
455 optionally specified by the application at time of <code>Enqueue</code>.
467 application in synchrony with the completion callback.
470 recorder object), and a <code>void *</code> for application.
483 The application enqueues filled buffers of data in MPEG-2 transport
489 An application may supply zero or one of these item codes
494 The application must not call <code>Enqueue</code> again.
504 the stream. The application should flush its internal data, then send
520 consumed buffer is available for the application to re-fill.
568 As part of the API to create an object, an application specifies
582 After the object is created and realized, the application should
592 After your application is done with the object, you should explicitly
633 Be sure to destroy all objects on exit from your application. Objects
647 cause your application to crash or behave in unpredictable ways.
659 <i>asynchronous</i> with respect to the application. Thus you should
661 to any variables shared between the application and the callback
667 non-application thread(s) which are not attached to the Dalvik virtual machine and thus
676 Note that the converse is safe: a Dalvik application thread which has
679 the main thread, as they may result in the dreaded "Application Not
684 As OpenMAX AL is a native C API, non-Dalvik application threads which
691 implementations continue to evolve, an OpenMAX AL application can
