/frameworks/compile/linkloader/tests/images/ |
D | simple-test.c | 25 unsigned int user = 100; in main() local 31 while (user != ans) { in main() 34 if (scanf("%u", &user) != 1) { in main() 38 if (user < left || user > right) { in main() 41 } else if (user == ans) { in main() 44 } else if (user < ans) { in main() 45 left = user; in main() 47 right = user; in main()
|
/frameworks/base/services/tests/servicestests/src/com/android/server/pm/ |
D | UserManagerTest.java | 43 for (UserInfo user : users) { in tearDown() 44 if (!user.isPrimary()) { in tearDown() 45 mUserManager.removeUser(user.id); in tearDown() 62 for (UserInfo user : list) { in testAddUser() 63 if (user.id == userInfo.id && user.name.equals("Guest 1") in testAddUser() 64 && user.isGuest() in testAddUser() 65 && !user.isAdmin() in testAddUser() 66 && !user.isPrimary()) { in testAddUser() 100 for (UserInfo user : list) { in findUser() 101 if (user.id == id) { in findUser()
|
/frameworks/base/docs/html/guide/topics/ui/notifiers/ |
D | index.jd | 6 <p>Several types of situations may arise that require you to notify the user 7 about an event that occurs in your application. Some events require the user to respond 12 <li>If the application is running in the background and needs the user's attention, 13 the application should create a notification that allows the user to respond at 16 performing work that the user must wait for (such as loading a file), 25 that come from the background and request the user's response.</li> 29 <p>This document summarizes each of these techniques for notifying the user and includes 38 It only fills the amount of space required for the message and the user's current 44 when you're fairly certain the user is paying attention 45 to the screen. A toast can not accept user interaction events; if you'd like [all …]
|
/frameworks/base/docs/html/resources/articles/ |
D | touch-mode.jd | 10 user interaction with the phone. By itself, the touch mode is something very 11 easy to understand as it simply indicates whether the last user interaction was 15 you will enter touch mode. When the user is not in touch mode, we talk about the 31 keyboard. Based on the hardware capabilities of the he user can interact with 37 for example, that shows a list of text items. The user can freely 40 how to handle the selection properly when the user manipulates the list 43 <p>In this case, if the user selects an item at the top of the list and then 45 it remain on the item and scroll off the screen? What should happen if the user 47 happen if the user presses the trackball to act upon the currently selected 51 when the user manipulates the UI through the touch screen.</p> [all …]
|
/frameworks/base/services/camera/libcameraservice/ |
D | CameraHardwareInterface.h | 37 void* user); 42 void* user); 47 void *user); 119 mHalPreviewWindow.user = this; in setPreviewWindow() 121 &mHalPreviewWindow, mHalPreviewWindow.user); in setPreviewWindow() 132 void* user) in setCallbacks() argument 137 mCbUser = user; in setCallbacks() 445 int32_t ext2, void *user) in __notify_cb() argument 449 static_cast<CameraHardwareInterface *>(user); in __notify_cb() 456 void *user) in __data_cb() argument [all …]
|
/frameworks/base/core/java/com/google/android/util/ |
D | AbstractMessageParser.java | 960 private String user; field in AbstractMessageParser.Photo 964 public Photo(String user, String album, String photo, String text) { in Photo() argument 966 this.user = user; in Photo() 971 public String getUser() { return user; } in getUser() 1001 public static String getRssUrl(String user) { in getRssUrl() argument 1002 return "http://picasaweb.google.com/data/feed/api/user/" + user + in getRssUrl() 1007 public static String getAlbumURL(String user, String album) { in getAlbumURL() argument 1008 return "http://picasaweb.google.com/" + user + "/" + album; in getAlbumURL() 1012 public static String getPhotoURL(String user, String album, String photo) { in getPhotoURL() argument 1013 return "http://picasaweb.google.com/" + user + "/" + album + "/photo#" in getPhotoURL() [all …]
|
/frameworks/base/docs/html/guide/practices/design/ |
D | index.jd | 4 …m, to ensure that your applications offer outstanding performance and a great user experience. </p> 6 …n design that directly influence the user experience of your application, when in the hands of a m… 8 …user experience, in addition to a compelling technical feature set. The user experience is more th… 10 <p>An outstanding user experience has three key characteristics: it is
|
D | accessibility.jd | 13 accessibility events during user interaction</li> 53 feedback, and trackball/d-pad navigation that augment the user experience.</p> 60 <li>Make all of your user interface controls accessible with a trackball or directional 80 touchscreen. On some devices, a user can also navigate to the top or bottom of a list by holding 112 <p>When the user navigates in any direction using the directional controls, focus is passed from one 122 <dd>Defines the next view to receive focus when the user navigates down.</dd> 125 <dd>Defines the next view to receive focus when the user navigates left.</dd> 128 <dd>Defines the next view to receive focus when the user navigates right.</dd> 131 <dd>Defines the next view to receive focus when the user navigates up.</dd> 179 <p>Many input widgets rely on visual cues to inform the user of their meaning. For example, a [all …]
|
D | responsiveness.jd | 19 <p><strong>Figure 1.</strong> An ANR dialog displayed to the user.</p> 29 responsive for a period of time by displaying a dialog to the user, called the 30 Application Not Responding (ANR) dialog, shown at right in Figure 1. The user 31 can choose to let the application continue, but the user won't appreciate having 34 cause to display an ANR dialog to the user. </p> 37 user input. For example, if an application blocks on some I/O operation 39 process incoming user input events. After a time, the system concludes that the 40 application is frozen, and displays the ANR to give the user the option to kill 50 most of your work there. This keeps the main thread (which drives the user 116 whatever application the user is currently has running. If your application [all …]
|
D | seamlessness.jd | 37 not have user focus at the time your background process displays the dialog. So 40 display the dialog in front of whatever the user was doing (such as dialing a 42 for the user. </p> 45 facility for notifying the user — the 47 notifications, your application can signal the user that an event has 49 focus and interrupting the user.</p> 52 loses state or user data because it doesn't correctly implement the onPause() 75 <p>If the user was editing data in your application when the other Activity 80 fashion. When the user revisits the application, she should be able to 84 user was composing an email when another Activity started up, the application [all …]
|
/frameworks/base/docs/html/guide/practices/ui_guidelines/ |
D | activity_task_design.jd | 43 <li><a href=#notifications_get_back_tip>Notifications should let user easily get back</li> 61 framework, from a high-level, user-centric perspective useful to 112 components</a>)--> for the user to interact with, typically bundled up 122 which the user can pick to start an application. 135 cohesive user interface. An activity has a distinct visual user 139 of user action. Any application that presents anything on the display 144 When using an Android device, as the user moves through the user 153 set of related user actions. Each activity has a 157 launched (started) independently, and the user or system can start, 240 As the user moves from activity to activity, across applications, the [all …]
|
D | menu_design.jd | 59 A menu holds a set of commands (user actions) that are normally hidden, and 64 user controls in the content area of your application. 74 It is typically invoked by a user pressing a hard button, often labeled MENU.</li> 76 selected item. It is typically invoked by a user's touch & hold 112 On most devices, a user presses the MENU button to access the Options menu, 113 as shown in the screenshot below. To close the menu, the user presses 158 On some versions of Android, the user can display keyboard shortcuts in the 172 A user can touch & hold on content on the screen to 182 For example, in an email message list, a user can touch & hold on 188 A user can also touch & hold a <em>location</em> on the screen to [all …]
|
/frameworks/base/media/libmedia/ |
D | AudioTrack.cpp | 94 void* user, in AudioTrack() argument 100 frameCount, flags, cbf, user, notificationFrames, in AudioTrack() 112 void* user, in AudioTrack() argument 118 0, flags, cbf, user, notificationFrames, in AudioTrack() 149 void* user, in set() argument 256 mUserData = user; in set() 564 …oopCount %d, framecount %d, user %d", loopStart, loopEnd, loopCount, cblk->frameCount, cblk->user); in setLoop_l() 649 if (position > mCblk->user) return BAD_VALUE; in setPosition() 882 if (cblk->user < cblk->loopEnd) { in obtainBuffer() 884 "user=%08x, server=%08x", this, cblk->user, cblk->server); in obtainBuffer() [all …]
|
D | AudioRecord.cpp | 95 void* user, in AudioRecord() argument 101 frameCount, flags, cbf, user, notificationFrames, sessionId); in AudioRecord() 129 void* user, in set() argument 227 mUserData = user; in set() 325 mNewPosition = cblk->user + mUpdatePeriod; in start() 433 *position = mCblk->user; in getPosition() 536 "user=%08x, server=%08x", cblk->user, cblk->server); in obtainBuffer() 570 uint32_t u = cblk->user; in obtainBuffer() 687 if (cblk->user >= mMarkerPosition) { in processAudioBuffer() 695 while (cblk->user >= mNewPosition) { in processAudioBuffer() [all …]
|
/frameworks/base/docs/html/guide/topics/manifest/ |
D | permission-element.jd | 30 <dd>A user-readable description of the permission, longer and more 32 permission to the user — for example, when the user is asked 52 strings in the user interface. 87 minimal risk to other applications, the system, or the user. 90 asking for the user's explicit approval (though the user always 95 access to private user data or control over the device that can 96 negatively impact the user. Because this type of permission 100 user and require confirmation before proceeding, or some other 101 approach may be taken to avoid the user automatically allowing 108 automatically grants the permission without notifying the user or [all …]
|
/frameworks/base/docs/html/guide/topics/location/ |
D | obtaining-user-location.jd | 12 <li>Obtaining user location can consume a lot of battery, so be careful how 25 <li><a href="#Flow">Flow for obtaining user location</a></li> 43 <p>Knowing where the user is allows your application to be smarter and deliver 44 better information to the user. When developing a location-aware application for Android, you can 45 utilize GPS and Android's Network Location Provider to acquire the user location. Although 47 the location as quickly as users want. Android's Network Location Provider determines user location 49 works indoors and outdoors, responds faster, and uses less battery power. To obtain the user 56 <p>Obtaining user location from a mobile device can be complicated. There are several reasons 58 Some sources of error in the user location include:</p> 66 <p>Because the user location changes, you must account for movement by re-estimating user [all …]
|
/frameworks/base/docs/html/resources/faq/ |
D | security.jd | 38 The Android user can choose to grant or deny an application's request for 84 software from any developer onto a device. As with a home PC, the user must be 87 This decision can be informed by the user's judgment of the software 107 been granted by the user</li> 108 <li>shows the user unsolicited messages (especially messages urging the 109 user to buy something);</li> 110 <li>resists (or attempts to resist) the user's effort to uninstall it;</li> 113 <li>discloses the user's private information to a third party, without the 114 user's knowledge and consent;</li> 115 <li>destroys the user's data (or the device itself) without the user's [all …]
|
/frameworks/base/docs/html/guide/topics/search/ |
D | index.jd | 25 <p>Search is a core user feature on Android. Users should be able 40 the search dialog or widget to provide search suggestions as the user types. Figure 1 shows an 47 <li>Provide search suggestions based on recent user queries</li> 82 <p>When you implement search in your application, take steps to protect the user's 84 be private information. To protect each user's privacy, you should abide by the following 94 you don't need to send the user ID as well; send only the zip code to the server. If you must 99 <p>The search framework helps your application provide context-specific suggestions while the user 101 suggestions are based on previous searches or other actions taken by the user in an earlier 102 session. A user might not wish for previous searches to be revealed to other device users, for 103 instance, if the user shares the device with a friend. If your application provides suggestions that [all …]
|
/frameworks/base/include/media/ |
D | AudioEffect.h | 182 typedef void (*effect_callback_t)(int32_t event, void* user, void *info); 230 void* user = 0, 242 void* user = 0, 264 void* user = 0,
|
D | Visualizer.h | 70 void* user = 0, 88 typedef void (*capture_cbk_t)(void* user, 97 status_t setCaptureCallBack(capture_cbk_t cbk, void* user, uint32_t flags, uint32_t rate);
|
D | AudioTrack.h | 102 typedef void (*callback_t)(int event, void* user, void *info); 150 void* user = 0, 170 void* user = 0, 194 void* user = 0,
|
/frameworks/base/telephony/java/com/android/internal/telephony/ |
D | ApnSetting.java | 33 public final String user; field in ApnSetting 57 String user, String password, int authType, String[] types, in ApnSetting() argument 68 this.user = user; in ApnSetting()
|
/frameworks/base/docs/html/guide/topics/admin/ |
D | device-admin.jd | 80 <li>The system prompts the user to enable the device admin application. How 87 <p>If a user fails to comply with the policies (for example, if a user sets a 89 how to handle this. However, typically this will result in the user not being 187 <td>Specifies how many times a user can enter the wrong password before the 194 <td>Sets the length of time since the user last touched the screen or 210 <li>Prompt user to set a new password.</li> 230 with a user interface that lets them enable the device admin application. Once 231 they've enabled the application, they can use the buttons in the user interface 235 <li>Specify requirements for the user's password, such as minimum length, the minimum number of 317 user-readable label for the activity.</li> [all …]
|
/frameworks/base/docs/html/guide/topics/fundamentals/ |
D | tasks-and-back-stack.jd | 11 <li>A task contains a collection of activities in the order in which the user interacts with 48 should be designed around a specific kind of action the user can perform and can start other 50 When the user selects an email, a new activity opens to view that email.</p> 57 support the same intent, then the system lets the user select which one to use). When the email is 59 though the activities may be from different applications, Android maintains this seamless user 73 other being a layout to display an item from the list (fragment B). When the user selects an item 75 desireable for the user to navigate back to reveal fragment B, using the BACK key.</p> 87 <p>The device Home screen is the starting place for most tasks. When the user touches an icon in the 95 stops, the system retains the current state of its user interface. When the user presses the BACK 99 the current activity and popped off when the user leaves it using the BACK key. As such, the back [all …]
|
/frameworks/base/core/java/com/android/internal/net/ |
D | VpnConfig.java | 55 public String user; field in VpnConfig 73 out.writeString(user); in writeToParcel() 90 config.user = in.readString();
|