| /frameworks/base/docs/html/guide/topics/ui/notifiers/ |
| D | index.jd | 15 <p>Several types of situations may arise that require you to notify the user
16 about an event that occurs in your application. Some events require the user to respond
21 <li>If the application is running in the background and needs the user's attention,
22 the application should create a notification that allows the user to respond at
25 performing work that the user must wait for (such as loading a file),
34 that come from the background and request the user's response.</li>
38 <p>This document summarizes each of these techniques for notifying the user and includes
47 It only fills the amount of space required for the message and the user's current
53 when you're fairly certain the user is paying attention
54 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 | 8 user interaction with the phone. By itself, the touch mode is something very
9 easy to understand as it simply indicates whether the last user interaction was
13 you will enter touch mode. When the user is not in touch mode, we talk about the
29 keyboard. Based on the hardware capabilities of the he user can interact with
35 for example, that shows a list of text items. The user can freely
38 how to handle the selection properly when the user manipulates the list
41 <p>In this case, if the user selects an item at the top of the list and then
43 it remain on the item and scroll off the screen? What should happen if the user
45 happen if the user presses the trackball to act upon the currently selected
49 when the user manipulates the UI through the touch screen.</p>
[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 | 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 | 41 <li><a href=#notifications_get_back_tip>Notifications should let user easily get back</li>
59 framework, from a high-level, user-centric perspective useful to
108 components</a>)--> for the user to interact with, typically bundled up
118 which the user can pick to start an application.
131 cohesive user interface. An activity has a distinct visual user
135 of user action. Any application that presents anything on the display
140 When using an Android device, as the user moves through the user
149 set of related user actions. In general, each activity has a
153 launched (started) independently, and the user or system can start,
237 As the user moves from activity to activity, across applications, the
[all …]
|
| D | menu_design.jd | 57 A menu holds a set of commands (user actions) that are normally hidden, and
62 user controls in the content area of your application.
72 It is typically invoked by a user pressing a hard button, often labeled MENU.</li>
74 selected item. It is typically invoked by a user's touch & hold
110 On most devices, a user presses the MENU button to access the Options menu,
111 as shown in the screenshot below. To close the menu, the user presses
156 On some versions of Android, the user can display keyboard shortcuts in the
170 A user can touch & hold on content on the screen to
180 For example, in an email message list, a user can touch & hold on
186 A user can also touch & hold a <em>location</em> on the screen to
[all …]
|
| /frameworks/base/include/camera/ |
| D | CameraHardwareInterface.h | 43 void* user);
47 void* user);
52 void* user);
99 void* user) = 0;
|
| /frameworks/base/docs/html/guide/topics/search/ |
| D | index.jd | 25 <p>Search is a core user feature on Android. Users should be able
37 <p>Android's search framework provides a user interface in which users can perform a search and
39 your own search Activity. Instead, a search dialog appears at the top of the screen at the user's
50 <li>Provide search suggestions based on recent user queries</li>
79 <p>When you implement search in your application, take steps to protect the user's
81 be private information. To protect each user's privacy, you should abide by the following
91 you don't need to send the user ID as well; send only the zip code to the server. If you must
95 <li><strong>Provide the user with a way to clear their search history.</strong>
96 <p>The search framework helps your application provide context-specific suggestions while the user
98 suggestions are based on previous searches or other actions taken by the user in an earlier
[all …]
|
| /frameworks/base/docs/html/guide/topics/manifest/ |
| D | permission-element.jd | 28 <dd>A user-readable description of the permission, longer and more
30 permission to the user — for example, when the user is asked
50 strings in the user interface.
85 minimal risk to other applications, the system, or the user.
88 asking for the user's explicit approval (though the user always
93 access to private user data or control over the device that can
94 negatively impact the user. Because this type of permission
98 user and require confirmation before proceeding, or some other
99 approach may be taken to avoid the user automatically allowing
106 automatically grants the permission without notifying the user or
[all …]
|
| /frameworks/base/docs/html/resources/faq/ |
| D | security.jd | 33 The Android user can choose to grant or deny an application's request for
65 keeping the user and security community informed of bugs and fixes. We will
81 developer onto a device. As with a home PC, the user must be
84 This decision can be informed by the user's judgment of the software
109 <li>shows the user unsolicited messages (especially messages urging the
110 user to buy something);</li>
111 <li>resists (or attempts to resist) the user's effort to uninstall it;</li>
114 <li>discloses the user's private information to a third party, without the
115 user's knowledge and consent;</li>
116 <li>destroys the user's data (or the device itself) without the user's
[all …]
|
| /frameworks/base/docs/html/guide/appendix/faq/ |
| D | security.jd | 33 The Android user can choose to grant or deny an application's request for
65 keeping the user and security community informed of bugs and fixes. We will
81 developer onto a device. As with a home PC, the user must be
84 This decision can be informed by the user's judgment of the software
109 <li>shows the user unsolicited messages (especially messages urging the
110 user to buy something);</li>
111 <li>resists (or attempts to resist) the user's effort to uninstall it;</li>
114 <li>discloses the user's private information to a third party, without the
115 user's knowledge and consent;</li>
116 <li>destroys the user's data (or the device itself) without the user's
[all …]
|
| /frameworks/base/media/libmedia/ |
| D | AudioRecord.cpp | 92 void* user, in AudioRecord() argument
98 frameCount, flags, cbf, user, notificationFrames, sessionId); in AudioRecord()
125 void* user, in set() argument
211 mUserData = user; in set()
296 mNewPosition = mCblk->user + mUpdatePeriod; in start()
401 *position = mCblk->user; in getPosition()
489 "user=%08x, server=%08x", cblk->user, cblk->server); in obtainBuffer()
522 uint32_t u = cblk->user; in obtainBuffer()
616 if (mCblk->user >= mMarkerPosition) { in processAudioBuffer()
624 while (mCblk->user >= mNewPosition) { in processAudioBuffer()
[all …]
|
| D | AudioTrack.cpp | 89 void* user, in AudioTrack() argument
95 frameCount, flags, cbf, user, notificationFrames, in AudioTrack()
107 void* user, in AudioTrack() argument
113 0, flags, cbf, user, notificationFrames, in AudioTrack()
143 void* user, in set() argument
240 mUserData = user; in set()
519 …oopCount %d, framecount %d, user %d", loopStart, loopEnd, loopCount, cblk->frameCount, cblk->user); in setLoop()
602 if (position > mCblk->user) return BAD_VALUE; in setPosition()
812 if (cblk->user < cblk->loopEnd) { in obtainBuffer()
814 "user=%08x, server=%08x", this, cblk->user, cblk->server); in obtainBuffer()
[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/include/media/ |
| D | AudioEffect.h | 195 typedef void (*effect_callback_t)(int32_t event, void* user, void *info);
243 void* user = 0,
255 void* user = 0,
277 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 | 103 typedef void (*callback_t)(int event, void* user, void *info);
151 void* user = 0,
171 void* user = 0,
195 void* user = 0,
|
| /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
133 <td>Specifies how many times a user can enter the wrong password before the
140 <td>Sets the length of time since the user last touched the screen or
150 <li>Prompt user to set a new password.</li>
170 with a user interface that lets them enable the device admin application. Once
171 they've enabled the application, they can use the buttons in the user interface
175 <li>Specify the minimum length for the user's password.</li>
247 user-readable label for the activity.</li>
[all …]
|
| /frameworks/base/telephony/java/com/android/internal/telephony/gsm/ |
| D | ApnSetting.java | 34 String user; field in ApnSetting
46 String user, String password, int authType, String[] types, in ApnSetting() argument
57 this.user = user; in ApnSetting()
|
| /frameworks/base/services/camera/libcameraservice/ |
| D | CameraService.h | 137 … static void notifyCallback(int32_t msgType, int32_t ext1, int32_t ext2, void* user);
138 … static void dataCallback(int32_t msgType, const sp<IMemory>& dataPtr, void* user);
139 … dataCallbackTimestamp(nsecs_t timestamp, int32_t msgType, const sp<IMemory>& dataPtr, void* user);
141 static sp<Client> getClientFromCookie(void* user);
|
| /frameworks/base/cmds/keystore/ |
| D | keystore.c | 487 static struct user { struct
500 struct user *user = users; in process() argument
504 while (~user->uid && user->uid != uid) { in process()
505 ++user; in process()
513 if (!(action->perm & user->perms)) { in process()
519 if (~user->euid) { in process()
520 uid = user->euid; in process()
|
| /frameworks/base/docs/html/guide/topics/processes/ |
| D | process-lifecycle.jd | 12 that the system knows are running, how important these things are to the user,
42 what the user is currently doing. Various application components can
48 at the top of the screen that the user is interacting with (its
62 reached a memory paging state, so this action is required in order to keep the user
67 that is visible to the user on-screen but not in the foreground (its
78 processes are not directly visible to the user, they are generally doing things
79 that the user cares about (such as background mp3 playback or background
85 that is not currently visible to the user (its
87 have no direct impact on the user experience. Provided they implement
93 by the user is the last to be killed when running low on memory.
|
| /frameworks/base/docs/html/guide/webapps/ |
| D | webview.jd | 52 provide information in your application that you might need to update, such as an end-user agreement
53 or a user guide. Within your Android application, you can create an {@link android.app.Activity}
58 data to the user that
62 the user data, rather than performing a network request, then parsing the data and rendering it in
140 custom user agent string with {@link android.webkit.WebSettings#setUserAgentString(String)
141 setUserAgentString()}, then query the custom user agent in your web page to verify that the
191 message using the new interface when the user clicks a button:</p>
221 should also not allow the user to
223 (instead, allow the user's
224 default browser application to open foreign links—by default, the user's web browser
[all …]
|