Home
last modified time | relevance | path

Searched refs:safe (Results 1 – 25 of 70) sorted by relevance

123

/frameworks/rs/api/
Drs_atomic.spec39 summary: Thread-safe addition
58 summary: Thread-safe bitwise and
79 summary: Thread-safe compare and set
102 summary: Thread-safe decrement
119 summary: Thread-safe increment
137 summary: Thread-safe maximum
157 summary: Thread-safe minimum
177 summary: Thread-safe bitwise or
197 summary: Thread-safe subtraction
216 summary: Thread-safe bitwise exclusive or
/frameworks/rs/scriptc/
Drs_atomic.rsh40 * rsAtomicAdd: Thread-safe addition
61 * rsAtomicAnd: Thread-safe bitwise and
83 * rsAtomicCas: Thread-safe compare and set
109 * rsAtomicDec: Thread-safe decrement
129 * rsAtomicInc: Thread-safe increment
149 * rsAtomicMax: Thread-safe maximum
171 * rsAtomicMin: Thread-safe minimum
193 * rsAtomicOr: Thread-safe bitwise or
215 * rsAtomicSub: Thread-safe subtraction
236 * rsAtomicXor: Thread-safe bitwise exclusive or
/frameworks/base/docs/html/guide/topics/renderscript/reference/
Drs_atomic.jd30 Thread-safe addition
38 Thread-safe bitwise and
46 Thread-safe compare and set
54 Thread-safe decrement
62 Thread-safe increment
70 Thread-safe maximum
78 Thread-safe minimum
86 Thread-safe bitwise or
94 Thread-safe subtraction
102 Thread-safe bitwise exclusive or
[all …]
Doverview.jd2128 Thread-safe addition
2136 Thread-safe bitwise and
2144 Thread-safe compare and set
2152 Thread-safe decrement
2160 Thread-safe increment
2168 Thread-safe maximum
2176 Thread-safe minimum
2184 Thread-safe bitwise or
2192 Thread-safe subtraction
2200 Thread-safe bitwise exclusive or
Dindex.jd1659 Thread-safe addition
1667 Thread-safe bitwise and
1675 Thread-safe compare and set
1683 Thread-safe decrement
1691 Thread-safe increment
1699 Thread-safe maximum
1707 Thread-safe minimum
1715 Thread-safe bitwise or
1723 Thread-safe subtraction
1731 Thread-safe bitwise exclusive or
/frameworks/av/media/libnbaio/
DREADME.txt13 no mutexes, so safe to use between SCHED_NORMAL and SCHED_FIFO threads
29 no mutexes, so safe to use between SCHED_NORMAL and SCHED_FIFO threads
/frameworks/base/docs/html/wear/preview/features/
Dcomplications.jd305 <li>The provider is a "safe" system provider,
311 <li>The provider whitelists the watch face as a "safe" watch face, or
348 <h4 id="safe-providers">
353 Some system providers are considered "safe", because they only supply
359 in the wearable support library. Whether a system provider is safe is
364 <h4 id="provider-specified-safe-watch-faces">
365 Provider-specified safe watch faces
369 Providers can specify certain watch faces as "safe" to receive their
376 To declare watch faces as safe, the provider adds metadata with a key of
383 specified app is considered safe).
[all …]
/frameworks/base/docs/html/training/tv/start/
Dlayouts.jd121 overscan safe area. Adding a 5% margin of 48dp on the left and right edges and 27dp on the top and
123 safe area.
127 clipped to the overscan safe area. This approach ensures that background screen elements look
132 child layout that has a 5% margin and can contain elements within the overscan safe area:
142 &lt;!-- Screen elements that can render outside the overscan safe area go here --&gt;
144 &lt;!-- Nested RelativeLayout with overscan-safe margin --&gt;
153 &lt;!-- Screen elements that need to be within the overscan safe area go here --&gt;
162 widgets, as those layouts already incorporate overscan-safe margins.
/frameworks/base/docs/html-intl/intl/in/guide/components/
Dprocesses-and-threads.jd19 <li><a href="#ThreadSafe">Metode thread-safe</a></li>
219 <p>Selain itu, toolkit Android UI <em>bukan</em> thread-safe. Jadi, Anda tidak harus memanipulasi
284 <p>Kini implementasi ini thread-safe: operasi jaringan dilakukan terpisah dari thread
360 <h3 id="ThreadSafe">Metode thread-safe</h3>
363 dan karena itu harus ditulis agar menjadi thread-safe. </p>
376 IBinder} karenanya harus diimplementasikan sebagai thread-safe.</p>
387 sekaligus, metode-metode ini juga harus diimplementasikan sebagai thread-safe. </p>
/frameworks/base/docs/html-intl/intl/id/guide/components/
Dprocesses-and-threads.jd19 <li><a href="#ThreadSafe">Metode thread-safe</a></li>
219 <p>Selain itu, toolkit Android UI <em>bukan</em> thread-safe. Jadi, Anda tidak harus memanipulasi
284 <p>Kini implementasi ini thread-safe: operasi jaringan dilakukan terpisah dari thread
360 <h3 id="ThreadSafe">Metode thread-safe</h3>
363 dan karena itu harus ditulis agar menjadi thread-safe. </p>
376 IBinder} karenanya harus diimplementasikan sebagai thread-safe.</p>
387 sekaligus, metode-metode ini juga harus diimplementasikan sebagai thread-safe. </p>
/frameworks/base/docs/html/guide/components/
Dprocesses-and-threads.jd19 <li><a href="#ThreadSafe">Thread-safe methods</a></li>
223 <p>Additionally, the Andoid UI toolkit is <em>not</em> thread-safe. So, you must not manipulate
289 <p>Now this implementation is thread-safe: the network operation is done from a separate thread
336 <p>Now the UI is safe and the code is simpler, because it separates the work into the
367 <h3 id="ThreadSafe">Thread-safe methods</h3>
370 therefore must be written to be thread-safe. </p>
384 IBinder} methods must, therefore, be implemented to be thread-safe.</p>
395 same time, they too must be implemented to be thread-safe. </p>
/frameworks/base/core/java/android/os/
DMessageQueue.java413 void quit(boolean safe) { in quit() argument
424 if (safe) { in quit()
/frameworks/av/services/audiopolicy/engineconfigurable/parameter-framework/examples/Settings/
Ddevice_for_strategy_sonification_respectful.pfw11 # - Otherwise follows sonification by replacing speaker with speaker safe if speaker is
35 # Follows sonification strategy if not in call and replace speaker by speaker safe
/frameworks/base/docs/html/training/safebrowsing/
Dindex.jd82 "https://developers.google.com/safe-browsing/terms">Terms of Service</a>.
313 "https://developers.google.com/safe-browsing/v4/usage-limits#suggested--warning-language">
/frameworks/base/docs/html/work/
Dmanaged-profiles.jd62 settings), so it is not safe to attach file URIs to intents.</li>
87 resolve the intent, and it is safe to fire off the intent. In this case, the
115 // Intent resolves, it's safe to fire it off
/frameworks/base/docs/html/training/camera/
Dvideobasics.jd99 your app will crash. So as long as the result is not null, it's safe to use the intent. </p>
/frameworks/base/docs/html-intl/intl/zh-cn/training/basics/intents/
Dsending.jd202 // Start an activity if it's safe
/frameworks/base/docs/html-intl/intl/ja/training/basics/intents/
Dsending.jd202 // Start an activity if it's safe
/frameworks/base/docs/html-intl/intl/zh-tw/training/basics/intents/
Dsending.jd202 // Start an activity if it's safe
/frameworks/base/docs/html-intl/intl/ko/training/basics/intents/
Dsending.jd202 // Start an activity if it's safe
/frameworks/base/docs/html/training/in-app-billing/
Dpurchase-iab-products.jd80 …n the query operation has completed and handles the query response. It is safe to make this call f…
110 …as completed and handles the consumption response from Google Play. It is safe to make this call f…
/frameworks/base/docs/html-intl/intl/ru/training/basics/intents/
Dsending.jd202 // Start an activity if it's safe
/frameworks/base/docs/html/design/tv/
Dstyle.jd49 outside of a safe zone that most TVs could reliably display. Even on some of today’s HDTV flat
/frameworks/base/docs/html/training/basics/supporting-devices/
Dplatforms.jd102 <code>android:showAsAction="ifRoom"</code> in your menu resource XML. It's safe to do this
/frameworks/base/docs/html/topic/performance/
Dthreads.jd57 blocks of work from a thread-safe work queue until its app is terminated. The
97 UI objects are not thread-safe</a>. An app is expected to create, use, and
344 to an object does not make the object thread-safe; the

123