| /prebuilts/ndk/9/sources/cxx-stl/EH/stlport/stlport/stl/ |
| _range_errors.h | 22 // _STLP_DONT_THROW_RANGE_ERRORS is a hook so that users can disable
|
| /system/security/keystore/include/keystore/ |
| keystore_get.h | 27 * Users are required to link against libkeystore_binder.
|
| /external/chromium/chrome/browser/chromeos/login/ |
| base_login_display_host.cc | 121 std::vector<chromeos::UserManager::User> users = local
124 // Fix for users who updated device and thus never passed register screen.
125 // If we already have users, we assume that it is not a second part of
127 if (!WizardController::IsDeviceRegistered() && !users.empty()) {
128 VLOG(1) << "Mark device registered because there are remembered users: "
129 << users.size();
137 sign_in_controller_->Init(users);
|
| views_login_display.cc | 27 // Max number of users we'll show. The true max is the min of this and the
31 // Minimum number of users we'll show (including Guest and New User pods).
42 // tooltips with full emails to let users distinguish their accounts.
84 void ViewsLoginDisplay::Init(const std::vector<UserManager::User>& users,
94 size_t visible_users_count = std::min(users.size(), max_users -
96 for (size_t i = 0; i < users.size(); ++i) {
97 UserController* user_controller = new UserController(this, users[i]);
|
| /frameworks/base/docs/html/about/versions/ |
| android-2.2-highlights.jd | 55 users and developers. This document provides a glimpse at some of the new user features
78 <p style="margin-top:0">New Home screen <span class="green">tips widget</span> assists new users on
104 application, enabling users to auto-complete recipient names from the directory.</p>
159 <p>Multi-lingual users can add multiple languages to the keyboard and <span class="green">switch
236 reports from their users. The reports will be available when they log into their publisher
273 <p>Apps can participate in data backup and restore, to ensure that users maintain their data
281 and so on. Users can select the administrators that are enabled on their devices.</p>
|
| /frameworks/base/docs/html/google/play-services/ |
| id.jd | 14 users better controls and provides developers with a simple, standard system
16 purposes and enables users to reset their identifier or opt out of interest-based
34 <h4>Giving users control</h4>
35 <p>Users can reset their advertising ID or opt out of interest-based ads at any time, right from the Google Settings app.
68 Users can reset their advertising ID at any time, right from the Ads section of the
69 Google Settings app on their devices. From the same app, users can also
154 The advertising ID APIs do not include a "reset" method. Only users can initiate a
|
| /external/chromium_org/chrome/browser/chromeos/login/ |
| user_manager_impl.h | 176 // Retrieves trusted device policies and removes users from the persistent
177 // list if ephemeral users are enabled. Schedules a callback to itself if
182 // and ephemeral users are enabled.
185 // Returns a list of users who have logged into this device previously.
292 // Adds |user| to users list, and adds it to front of LRU list. It is assumed
341 // List of all known users. User instances are owned by |this|. Regular users
346 // List of all users that are logged in current session. These point to User
350 // A list of all users that are logged in the current session. In contrast to
386 // such users by not adding them to the persistent user list, not downloadin
[all...] |
| user_manager_impl.cc | 71 // A vector pref of the the regular users known on this device, arranged in LRU
116 // Helper function that copies users from |users_list| to |users_vector| and
117 // |users_set|. Duplicates and users already present in |existing_users| are
267 const UserList& users = GetUsers(); local
268 for (UserList::const_iterator it = users.begin(); it != users.end(); ++it) {
366 // Place user who just signed in to the top of the logged in users.
460 // Sanity check: do not allow any of the the logged in users to be removed.
519 NOTREACHED() << "Users are not loaded yet.";
577 const UserList& users = GetUsers() local
1155 const UserList& users = GetUsers(); local
1175 UserList& users = GetUsersAndModify(); local
1436 std::set<std::string> users; local
[all...] |
| user_manager.h | 22 // Base class for UserManagerImpl - provides a mechanism for discovering users
88 // Domain that is used for all locally managed users.
128 // Returns a list of users who have logged into this device previously. This
132 // Returns list of users admitted for logging in into multiprofile session.
135 // Returns a list of users who are currently logged in.
138 // Returns a list of users who are currently logged in in the LRU order -
143 // Returns a list of users who can unlock the device.
208 // There could be multiple users logged in at the the same but for now
348 // Returns true if locally managed users allowed.
|
| /frameworks/base/docs/html/distribute/googleplay/policies/ |
| ads.jd | 27 the best experience for users visiting and downloading apps from the store.
94 content in the app, <em>including ads</em>, is suitable for all users
120 If your app displays ads, it should do so in ways that do not interrupt users,
180 <h2 id="disclosure" style="clear:right">Disclosure of Ads to Users</h2>
183 It's important to sufficiently disclose to users how your app will use ads.
184 You must make it easy for users to understand what ads will be shown in your
192 <strong>Tell users about your ads</strong>—Create a simple,
193 complete disclosure that tells users how your app uses ads, where the ads
207 <strong>Make sure users know</strong>—Present your ads disclosure
208 is an easy-to-see location, rather than hiding it where users are no
[all...] |
| /external/chromium_org/components/policy/resources/ |
| policy_templates.json | 141 'desc': '''Configure the default home page in <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> and prevents users from changing it.
158 'desc': '''Configures the default home page URL in <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> and prevents users from changing it.
164 If you enable this setting, users cannot change their home page URL in <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph>, but they can still can choose the New Tab Page as their home page.
182 'desc': '''Configures the type of the default home page in <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> and prevents users from changing home page preferences. The home page can either be set to a URL you specify or set to the New Tab Page.
188 If you enable or disable this setting, users cannot change their homepage type in <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph>.
206 'desc': '''Configures the default browser checks in <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> and prevents users from changing them.
228 'desc': '''Configures the application locale in <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> and prevents users from changing the locale.
248 'desc': '''Enables the use of alternate error pages that are built into <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> (such as 'page not found') and prevents users from changing this setting.
254 If you enable or disable this setting, users cannot change or override this setting in <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph>.
271 'desc': '''Enables search suggestions in <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph>'s omnibox and prevents users from changing this setting
[all...] |
| /external/chromium_org/chrome/browser/ui/ash/ |
| session_state_delegate_chromeos.cc | 33 // TODO(nkostylev): Show some UI messages why no more users could be added
35 // We limit list of logged in users to 10 due to memory constraints.
36 // Note that 10 seems excessive, but we want to test how many users are
124 void SessionStateDelegateChromeos::GetLoggedInUsers(ash::UserIdList* users) {
130 users->push_back(user->email());
|
| /external/llvm/test/Transforms/SLPVectorizer/X86/ |
| debug_info.ll | 60 !0 = metadata !{i32 786449, metadata !1, i32 12, metadata !"clang version 3.4 (trunk 187335) (llvm/trunk 187335:187340M)", i1 true, metadata !"", i32 0, metadata !2, metadata !2, metadata !3, metadata !2, metadata !2, metadata !""} ; [ DW_TAG_compile_unit ] [/Users/nadav/file.c] [DW_LANG_C99]
61 !1 = metadata !{metadata !"file.c", metadata !"/Users/nadav"}
65 !5 = metadata !{i32 786473, metadata !1} ; [ DW_TAG_file_type ] [/Users/nadav/file.c]
77 !17 = metadata !{i32 786443, metadata !1, metadata !4, i32 3, i32 0, i32 0} ; [ DW_TAG_lexical_block ] [/Users/nadav/file.c]
85 !25 = metadata !{i32 786443, metadata !1, metadata !17, i32 3, i32 0, i32 1} ; [ DW_TAG_lexical_block ] [/Users/nadav/file.c]
|
| /frameworks/base/docs/html/guide/faq/ |
| security.jd | 22 <p>The security and privacy of our users' data is of primary importance to the
58 users are at risk. In return, we will make sure to keep the researcher informed
75 with the users permission.</p>
78 users only download and install software from known sources.</p>
80 <p>As an open platform, Android allows users to visit any website and load
|
| /frameworks/base/docs/html/distribute/googleplay/quality/ |
| tablet.jd | 28 <p>Before you publish an app on Google Play, it's important to make sure that the app meets the basic expectations of tablet users through compelling features and an intuitive, well-designed UI. </p>
33 and monetization</a>. If your app is targeting tablet users, this document helps
80 all of your targeted devices. However, to give your users the best possible
116 users when holding a tablet, such as toward the sides when in
186 displaying content and engaging users. </p>
198 users to navigate your app. </li>
392 </a> to learn about implementation strategies to help most of your users. To
393 meet the accessibility needs of certain users, it may be appropriate to use
474 <h2 id="offer-full-feature-set">7. Offer the app's full feature set to tablet users</h2>
476 <p>Let your tablet users experience the best features of your app. Here ar
[all...] |
| /external/llvm/lib/Transforms/Utils/ |
| SimplifyIndVar.cpp | 67 /// Iteratively perform simplification on a worklist of users of the
69 /// all simplicitions to users of an IV.
278 // Also ensure unique worklist users.
307 /// simplifyUsers - Iteratively perform simplification on a worklist of users
309 /// more users which may themselves be candidates for simplification.
313 /// variables bottom-up from their users, it transforms a chain of IVUsers
326 // Use-def pairs if IV users waiting to be processed for CurrIV.
329 // Push users of the current LoopPhi. In rare cases, pushIVUsers may be
382 /// simplifyLoopIVs - Simplify users of induction variables within this
|
| /frameworks/base/docs/html/guide/topics/ui/accessibility/ |
| checklist.jd | 28 details right and delighting your users. This document provides a checklist of accessibility
44 restructuring. Rather, it means working through the subtle details of how users interact with your
65 <a href="{@docRoot}guide/topics/ui/accessibility/apps.html#focus-nav">users can navigate</a>
79 feedback mechanism to support users who are deaf or hard of hearing. For example, a sound alert
117 attribute <em>instead</em> of a content description, to help users understand what content is
123 not provide adequate descriptions for users, and you should consider providing a
133 accessibility services to perform this action for users. For more information, see
145 playback, it must support captioning and subtitles to assist users who are deaf or hard of
152 users. Provide the prompting information with a
|
| /external/chromium_org/third_party/mesa/src/src/mesa/drivers/dri/nouveau/ |
| nv04_3d.xml.h | 21 - B. R. <koala_br@users.sourceforge.net> (koala_br)
22 - Carlos Martin <carlosmn@users.sf.net> (carlosmn)
24 - Dawid Gajownik <gajownik@users.sf.net> (gajownik)
26 - Dmitry Eremin-Solenikov <lumag@users.sf.net> (lumag)
27 - EdB <edb_@users.sf.net> (edb_)
28 - Erik Waling <erikwailing@users.sf.net> (erikwaling)
30 - imirkin <imirkin@users.sf.net> (imirkin)
32 - Jeremy Kolb <kjeremy@users.sf.net> (kjeremy)
39 - nvidiaman <nvidiaman@users.sf.net> (nvidiaman)
42 - Peter Popov <ironpeter@users.sf.net> (ironpeter
[all...] |
| /external/mesa3d/src/mesa/drivers/dri/nouveau/ |
| nv04_3d.xml.h | 21 - B. R. <koala_br@users.sourceforge.net> (koala_br)
22 - Carlos Martin <carlosmn@users.sf.net> (carlosmn)
24 - Dawid Gajownik <gajownik@users.sf.net> (gajownik)
26 - Dmitry Eremin-Solenikov <lumag@users.sf.net> (lumag)
27 - EdB <edb_@users.sf.net> (edb_)
28 - Erik Waling <erikwailing@users.sf.net> (erikwaling)
30 - imirkin <imirkin@users.sf.net> (imirkin)
32 - Jeremy Kolb <kjeremy@users.sf.net> (kjeremy)
39 - nvidiaman <nvidiaman@users.sf.net> (nvidiaman)
42 - Peter Popov <ironpeter@users.sf.net> (ironpeter
[all...] |
| /frameworks/base/docs/html/google/play/billing/ |
| billing_testing.jd | 26 <li>Test purchases, which let test account users make real purchase your published in-app items,
45 <li><strong>Test purchases</strong>, which let your selected license test users
48 <li><strong>Real purchases</strong>, which let regular users make real purchases
51 the users who can make ?live? purchases using your implementation. </li>
65 <p>Once authorized with testing access, those users can side-load your app and
85 <p>Next, create license test accounts for authorized users. In the Developer
91 <p>Once you?ve added the users as license tester accounts and saved the change,
92 within 15 minutes those users can begin making test purchases of your in-app
100 account.Users can confirm the account that is making a purchase by expanding the
110 <p>During a test purchase, users can test the actual merchandising, purchase
[all...] |
| /development/scripts/app_engine_server/gae_shell/ |
| shell.py | 26 The logging, os, sys, db, and users modules are imported automatically.
48 from google.appengine.api import users namespace
74 'from google.appengine.api import users',
190 'user': users.get_current_user(),
191 'login_url': users.create_login_url(session_url),
192 'logout_url': users.create_logout_url(session_url),
|
| /external/llvm/include/llvm/Analysis/ |
| PtrUseVisitor.h | 46 /// After walking all the users (recursively) of a pointer, the basic
153 /// \brief Enqueue the users of this instruction in the visit worklist.
155 /// This will visit the users with the same offset of the current visit
180 /// are visited. Note that this does *not* mean before any of its users are
181 /// visited! This is because users can be visited multiple times due to
256 // Enqueue the users now that the offset has been adjusted.
|
| /frameworks/base/docs/html/training/tv/ |
| optimizing-navigation-tv.jd | 49 On a TV, users navigate with controls on a TV remote, using either a D-pad or arrow keys.
61 <li>For scrolling lists with focus, D-pad up/down keys scroll the list and Enter key selects an item in the list. Ensure that users can
68 makes navigation difficult, or if you want users to move through the layout in a specific way, you can set up explicit navigation for your
112 Use appropriate color highlights for all navigable and selectable elements in the UI. This makes it easy for users to know whether the control
152 Users should be able to navigate to any UI control with a couple of D-pad clicks. Navigation should be easy and intuitive to
153 understand. For any non-intuitive actions, provide users with written help, using a dialog triggered by a help button or action bar icon.
|
| /frameworks/base/docs/html/distribute/googleplay/spotlight/ |
| tablets.jd | 75 users have the opportunity to see all of their data in context and drill down
80 and the Nexus 7 is now the most popular Android device amongst our users. For us,
85 for their users.</p>
135 <li>Longer sessions — more Android tablet users have sessions longer than 5 minutes</li>
155 immersive experience for our users? said Ken Sun, Intuit Group Product Manager
168 users are interacting with their own budgets in the tablet app. Customer budget
172 <p>Fifty percent more Android tablet users have Mint sessions of 5 minutes or
244 base of Android tablet users represented a huge opportunity.</p>
264 important metrics for games — if you can get users to both stay around
330 great UI for Android tablet users would be an essential part of their initial launc
[all...] |
| /docs/source.android.com/src/devices/tech/security/ |
| index.jd | 25 environment that ensures the security of users, data, applications, the device,
31 protection for all users of the platform.</p>
38 <p>Android was designed with device users in mind. Users are provided visibility
41 attacks, such as social engineering attacks to convince device users to install
96 users hundreds of thousands of applications.</p>
104 allow users to discover, install, and purchase applications from their Android
106 users and potential customers. Google Play also provides community review,
155 such as the Linux kernel. Google Play provides a forum for users and companies
156 to provide information about specific applications directly to users.</li
[all...] |
