/external/bluetooth/bluedroid/bta/include/ |
bta_pan_api.h | 23 * phones.
|
/external/chromium_org/net/data/filter_unittests/ |
google.txt | 9 We also provide ways to access all this information without making a special trip to the Google homepage. The Google Toolbar enables you to conduct a Google search from anywhere on the web. And for those times when you're away from your PC altogether, Google can be used from a number of wireless platforms including WAP and i-mode phones.
|
/external/replicaisland/src/com/replica/replicaisland/ |
InputSystem.java | 67 // Some devices call landscape "ROTAION_90" (e.g. phones), while others call it
|
/external/svox/pico/lib/ |
picokdbg.c | 49 * @b Phones
|
picoktab.c | 640 /* Phones */ 643 /* overview binary file format for phones kb: 645 phones-kb = specids propertytable 658 PHONEPROP2: one byte, max. of 256 phones directly access this table 743 /* Phones methods */ [all...] |
picokdt.h | 284 13-15 the three following phones predicted 317 dtvres: phones vector classification result 453 dtres: phones vector classification result
|
/frameworks/base/core/res/res/values-land/ |
dimens.xml | 47 phones -->
|
/frameworks/base/docs/html/guide/practices/ |
index.jd | 4 page.landing.intro=Design and build apps the right way. Learn how to create apps that look great and perform well on as many devices as possible, from phones to tablets and more.
|
/frameworks/base/docs/html/guide/topics/providers/ |
content-providers.jd | 42 "Cursor (Phones)"</a>
|
/frameworks/base/docs/html/guide/topics/ui/ |
index.jd | 48 small phones to large TV sets. This class shows you how to implement a user interface that's
|
/frameworks/base/docs/html/training/multiscreen/ |
index.jd | 44 ranging from small phones to large TV sets. Therefore, it?s important
|
/frameworks/base/docs/html/wear/design/ |
user-interface.jd | 27 information. Much like Google Now on Android phones and tablets, users swipe vertically to navigate
|
/frameworks/base/telecomm/java/android/telecom/ |
PhoneAccountHandle.java | 62 * collide with values generated on other phones or after a data wipe of a given phone.
|
/frameworks/opt/telephony/src/java/com/android/internal/telephony/ |
PhoneFactory.java | 226 throw new IllegalStateException("Default phones haven't been made yet!"); 236 throw new IllegalStateException("Default phones haven't been made yet!"); 255 throw new IllegalStateException("Default phones haven't been made yet!"); 263 throw new IllegalStateException("Default phones haven't been made yet!");
|
Phone.java | [all...] |
/frameworks/opt/vcard/java/com/android/vcard/ |
VCardConfig.java | 177 * phones', which are probably not able to parse full-width hiragana/katakana for 221 * For example, there's a possibility Japanese mobile phones are expected to have 222 * just numbers, hypens, plus, etc. but not usual alphabets, while US mobile phones 357 * mobile phones, where phonetic names are translated to half-width katakana if
|
VCardParser_V21.java | 40 * (possible in Japanese mobile phones).
|
/external/srec/seti/sltsEngine/src/ |
SWIslts.c | 184 /* send phones to internal buffer */ 294 pfprintf(PSTDOUT,"number of phones: %d\n ", num_phones);
|
run_seq_lts.c | 341 pm->phones = (char**) lts_alloc(pm->num_phones, sizeof(char*)); 342 if (pm->phones == NULL) { 351 pm->phones[i] = ph = (char*) lts_alloc(len+1, sizeof(char)); 360 pm->phoneH = my_PHashTableCreate_FromStrings( (const char**)pm->phones, 384 if (pm->phones) { 386 if (pm->phones[i]) { 387 FREE(pm->phones[i]); 388 pm->phones[i] = NULL; 391 FREE(pm->phones); 392 pm->phones = NULL [all...] |
/external/svox/pico_resources/tools/LingwareBuilding/PicoLingware_tools_windows/tools/ |
picoloaddbg.lua | 9 -- load pico phones src file and create dbg pkb file
146 -- write out Phones pkb
|
/frameworks/base/docs/html/design/wear/ |
index.jd | 7 is substantially different than designing for phones or 34 <p>The context stream is a vertical list of cards, each showing a useful or timely piece of information. Much like the Google Now feature on Android phones and tablets, users swipe vertically to navigate from card to card. Only one card is displayed at a time, and background photos are used to provide additional visual information. Your application can create cards and inject them into the stream when they are most likely to be useful.</p>
|
/frameworks/base/docs/html/distribute/users/ |
your-listing.jd | 43 As higher density screens on both phones and tablets gain popularity, it's 76 <strong>Tip:</strong> If your app runs on both phones and tablets, be
|
/frameworks/base/docs/html/sdk/api_diff/5/changes/ |
fields_index_changes.html | 155 <A HREF="android.provider.Contacts.People.Phones.html#android.provider.Contacts.People.Phones.CONTENT_DIRECTORY" class="hiddenlink" target="rightframe">android.provider.Contacts.People.Phones</A> 171 <nobr><A HREF="android.provider.Contacts.Phones.html#android.provider.Contacts.Phones.CONTENT_FILTER_URL" class="hiddenlink" target="rightframe">CONTENT_FILTER_URL</A> 189 <A HREF="android.provider.Contacts.Phones.html#android.provider.Contacts.Phones.CONTENT_ITEM_TYPE" class="hiddenlink" target="rightframe">android.provider.Contacts.Phones</A> 212 <A HREF="android.provider.Contacts.Phones.html#android.provider.Contacts.Phones.CONTENT_TYPE" class="hiddenlink" target="rightframe">android.provider.Contacts.Phones</A [all...] |
alldiffs_index_changes.html | 376 <!-- Class Contacts.People.Phones --> 377 <A HREF="android.provider.Contacts.People.Phones.html" class="hiddenlink" target="rightframe">Contacts.People.Phones</A><br> 380 <!-- Class Contacts.Phones --> 381 <A HREF="android.provider.Contacts.Phones.html" class="hiddenlink" target="rightframe">Contacts.Phones</A><br> 413 <A HREF="android.provider.Contacts.People.Phones.html#android.provider.Contacts.People.Phones.CONTENT_DIRECTORY" class="hiddenlink" target="rightframe">android.provider.Contacts.People.Phones</A> 436 <nobr><A HREF="android.provider.Contacts.Phones.html#android.provider.Contacts.Phones.CONTENT_FILTER_URL" class="hiddenlink" target="rightframe">C (…) [all...] |
/external/chromium_org/components/autofill/core/browser/ |
autofill_ie_toolbar_import_win.cc | 187 // Now re-construct the phones if needed. 269 // Combine phones into whole phone #.
|