Home
last modified time | relevance | path

Searched refs:always (Results 1 – 25 of 163) sorted by relevance

1234567

/frameworks/support/v4/java/android/support/v4/util/
DTimeUtils.java35 static private int accumField(int amt, int suffix, boolean always, int zeropad) { in accumField() argument
36 if (amt > 99 || (always && zeropad >= 3)) { in accumField()
39 if (amt > 9 || (always && zeropad >= 2)) { in accumField()
42 if (always || amt > 0) { in accumField()
49 boolean always, int zeropad) { in printField() argument
50 if (always || amt > 0) { in printField()
52 if ((always && zeropad >= 3) || amt > 99) { in printField()
58 if ((always && zeropad >= 2) || amt > 9 || startPos != pos) { in printField()
/frameworks/base/core/java/android/util/
DTimeUtils.java146 static private int accumField(int amt, int suffix, boolean always, int zeropad) { in accumField() argument
147 if (amt > 99 || (always && zeropad >= 3)) { in accumField()
150 if (amt > 9 || (always && zeropad >= 2)) { in accumField()
153 if (always || amt > 0) { in accumField()
160 boolean always, int zeropad) { in printField() argument
161 if (always || amt > 0) { in printField()
163 if ((always && zeropad >= 3) || amt > 99) { in printField()
169 if ((always && zeropad >= 2) || amt > 9 || startPos != pos) { in printField()
/frameworks/base/core/java/android/view/
DWindowManagerPolicy.java950 public void showBootMessage(final CharSequence msg, final boolean always); in showBootMessage() argument
975 public boolean performHapticFeedbackLw(WindowState win, int effectId, boolean always); in performHapticFeedbackLw() argument
DIWindowSession.aidl123 boolean performHapticFeedback(IWindow window, int effectId, boolean always); in performHapticFeedback() argument
/frameworks/base/docs/html/guide/developing/tools/
Dzipalign.jd17 <p>This tool should always be used to align your .apk file before
55 This must always be 4 (which provides 32-bit alignment) or else it effectively
/frameworks/base/docs/html/guide/topics/manifest/
Dactivity-element.jd9 android:<a href="#always">alwaysRetainTaskState</a>=["true" | "false"]
97 Therefore, by definition, a root activity is always in a task with the
105 <dt><a name="always"></a>{@code android:alwaysRetainTaskState}</dt>
106 <dd>Whether or not the state of the task that the activity is in will always
121 However, when this attribute is "{@code true}", users will always return
130 "{@code true}" if the task is always stripped down to its root activity, and
141 <code><a href="#always">alwaysRetainTaskState</a></code> attribute), but not always.
235 activity always handles this configuration change itself (this configuration change does not restart
245 your activity always handles this configuration change itself (this configuration change does not
418 can only begin a task. They are always at the root of the activity stack.
[all …]
Ddata-element.jd79 case-sensitive, unlike the formal RFC. As a result, you should always specify
89 case-sensitive, unlike formal RFC MIME types. As a result, you should always
155 case-sensitive, unlike the RFC. As a result, you should always specify schemes
Duses-sdk-element.jd24 The API Level is always a single integer. You cannot derive the API Level from
57 this attribute. You should always declare this attribute.
/frameworks/base/tools/layoutlib/bridge/src/com/android/layoutlib/bridge/android/
DBridgeWindowSession.java66 public boolean performHapticFeedback(IWindow window, int effectId, boolean always) { in performHapticFeedback() argument
/frameworks/base/docs/html/intl/ja/
Dindex.jd80 …value="always"></param><embed src="http://www.youtube.com/v/GARMe7Km_gk&hl=en&fs=1" type="applicat…
/frameworks/base/docs/html/guide/practices/design/
Dperformance.jd36 algorithms and data structures should always be your priority, but is
78 code for a device with a JIT is not always the best code for a device
89 is always more expensive than not allocating memory.</p>
94 should always be avoided.</p>
101 will always be appended to a StringBuffer anyway, change your signature
174 in the public interface, but within a class you should always access
386 <p>One last thing: always measure. Before you start optimizing, make sure you
/frameworks/base/core/java/android/widget/
DSlidingDrawer.java486 private void performFling(int position, float velocity, boolean always) {
491 if (always || (velocity > mMaximumMajorVelocity ||
508 if (!always && (velocity > mMaximumMajorVelocity ||
/frameworks/base/docs/html/guide/topics/fundamentals/
Dtasks-and-back-stack.jd229 <li><a href="{@docRoot}guide/topics/manifest/activity-element.html#always">{@code
330 the task holding the instance. The activity is always the single and only member of its task;
336 always open in its own task&mdash;by specifying the {@code singleTask} launch mode in the <a
345 started it, the BACK key always takes the user to the previous activity. However, if you
406 the incoming intent. That's because a new instance is always created for a new intent when the
452 notification manager) always start activities in an external task, never as part of their own, so
453 they always put {@code FLAG_ACTIVITY_NEW_TASK} in the intents they pass to {@link
493 href="{@docRoot}guide/topics/manifest/activity-element.html#always">alwaysRetainTaskState</a></code>
504 href="{@docRoot}guide/topics/manifest/activity-element.html#always">{@code
505 alwaysRetainTaskState}</a>. The user always returns to the task in its
[all …]
/frameworks/base/docs/html/sdk/
Dandroid-2.0-highlights.jd34 <param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"><…
36 allowscriptaccess="always" allowfullscreen="true" width="278" height="180"></embed>
Dandroid-1.6-highlights.jd29 <param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"><…
31 allowscriptaccess="always" allowfullscreen="true" width="278" height="180"></embed>
/frameworks/base/services/java/com/android/server/wm/
DSession.java203 boolean always) { in performHapticFeedback() argument
209 effectId, always); in performHapticFeedback()
/frameworks/base/docs/html/resources/articles/
Dfuture-proofing.jd18 though we've always strongly advised against doing so, some developers
53 layouts are now likely to cause crashes. This was always a risk for
Dlayout-tricks-merge.jd61 root tag and tags in XML layouts always represent view instances.</p>
101 parent of an activity's content view is always a <code>FrameLayout</code>. You
/frameworks/base/docs/html/guide/topics/testing/
Dcontentprovider_testing.jd100 ensures that tests always run against data dependencies set explicitly in the test case. It
155 {@link android.test.ProviderTestCase2}, you should always test with a resolver object
167 data tables. These should always be constants publicly defined by the provider.
/frameworks/base/docs/html/guide/topics/resources/
Dmenu-resource.jd46 android:showAsAction=["ifRoom" | "never" | "withText" | "always" | "collapseActionView"]
131 <tr><td><code>always</code></td><td>Always place this item in the Action Bar.
132 Avoid using this unless it's critical that the item always appear in the action
133 bar. Setting multiple items to always appear as action items can result in them overlapping
Dcolor-list-resource.jd88 <p>The value always begins with a pound (#) character and then followed by the
124 default value should always be last (as demonstrated in the following example).</p>
/frameworks/base/docs/html/guide/topics/media/
Dmediaplayer.jd185 that you must always be aware of when writing your code, because certain operations
220 Therefore, you should always take extra precautions to make sure you are not
222 are done with it, you should always call
361 <p class="caution"><strong>Notice:</strong> You should always use wake locks sparingly and hold them
478 you should always request audio focus. Once it has focus, it can use the sound output freely, but it
480 always listen for focus changes. If it is notified that it has lost the audio
642 So, in the case when you're using a service, you should always override the
658 <p>You should always look for other opportunities to release your {@link android.media.MediaPlayer}
/frameworks/base/docs/html/guide/topics/processes/
Dprocess-lifecycle.jd80 network data upload or download), so the system will always keep such processes
120 classification will always be at least as important as process A's.</p>
/frameworks/support/v4/java/android/support/v4/view/
DViewPager.java332 void setCurrentItemInternal(int item, boolean smoothScroll, boolean always) { in setCurrentItemInternal() argument
333 setCurrentItemInternal(item, smoothScroll, always, 0); in setCurrentItemInternal()
336 void setCurrentItemInternal(int item, boolean smoothScroll, boolean always, int velocity) { in setCurrentItemInternal() argument
341 if (!always && mCurItem == item && mItems.size() != 0) { in setCurrentItemInternal()
/frameworks/base/docs/html/guide/basics/
Dappmodel.jd86 task the new activity will run in: it will always run in the task of the
138 impact on tasks: it causes the activity to always be started in
246 This means that <em>implementations of IBinder interfaces must always be
253 This means that <em>implementations of these methods must always be

1234567