| /frameworks/opt/bluetooth/src/android/bluetooth/client/pbap/ |
| D | BluetoothPbapCard.java | 99 List<PhoneData> phones = vcard.getPhoneList();
101 if (phones != null) {
102 for (PhoneData phone : phones) {
|
| /frameworks/opt/telephony/src/java/com/android/internal/telephony/dataconnection/ |
| D | DctController.java | 184 public static DctController makeDctController(PhoneProxy[] phones) { in makeDctController() argument
186 logd("makeDctController: new DctController phones.length=" + phones.length); in makeDctController()
187 sDctController = new DctController(phones); in makeDctController()
193 private DctController(PhoneProxy[] phones) { in DctController() argument
194 logd("DctController(): phones.length=" + phones.length); in DctController()
195 if (phones == null || phones.length == 0) { in DctController()
196 if (phones == null) { in DctController()
203 mPhoneNum = phones.length; in DctController()
204 mPhones = phones; in DctController()
|
| /frameworks/base/docs/html/design/style/ |
| D | devices-displays.jd | 2 …roid's flexible layout system and create apps that gracefully scale from phones to tablets and bey…
6 <p>Android powers hundreds of millions of phones, tablets, and other devices in a wide variety of s…
8 gracefully scale from large tablets to smaller phones.</p>
|
| /frameworks/base/docs/html/distribute/stories/ |
| D | tablets.jd | 53 <li>Single APK for phones and tablets</li>
128 <li>Financial management app targeting 7- to 10-inch tablets and phones</li>
151 tablets, they knew that taking the layout that worked for phones and simply
160 of features to Android tablets that aren’t available for phones, including a
163 <p>“Whereas our app for phones is used throughout the day for quick sessions,
171 they are on phones.”</p>
174 longer than they do on phones. “We’ve found that phone usage is indicative of a
218 <li>Game targeting 7- to 10-inch tablets and phones</li>
259 higher than on smaller-screen devices such as phones. Additionally, average
276 retention than on phones.</p>
[all …]
|
| /frameworks/base/docs/html/design/handhelds/ |
| D | index.jd | 6 whether you're designing for phones, tablets, watches, or other form factors.
7 Aspects of UI that are especially important for phones and tablets include
15 the left, after the Devices sections, provide detailed guidelines for phones
82 <p>New for phones in Android 4.0, the navigation bar is present only on devices that don't have
|
| /frameworks/base/docs/html/design/patterns/ |
| D | compatibility.jd | 44 <p>Android phones with traditional navigation hardware keys don't display the virtual navigation ba…
59 <h4>Legacy apps on phones with virtual navigation controls</h4>
|
| D | new.jd | 197 phones by replacing them with a virtual navigation bar that houses
200 pattern to learn how the OS adapts to phones with hardware buttons and
|
| D | multi-pane-layouts.jd | 31 <p>Because tablets have more screen real estate than phones, you can use panels to combine the rela…
|
| /frameworks/base/docs/html/about/ |
| D | index.jd | 60 <blockquote>Easily optimize a single binary for phones, tablets, and other devices.</blockquote>
65 devices—from phones to tablets and beyond.</p>
76 other sets for optimzations specific to phones or tablets.
|
| /frameworks/opt/telephony/src/java/com/android/internal/telephony/ |
| D | PhoneFactory.java | 411 PhoneProxy [] phones = (PhoneProxy[])PhoneFactory.getPhones(); in dump() local
413 for(PhoneProxy phoneProxy : phones) { in dump()
|
| /frameworks/base/docs/html/distribute/users/ |
| D | 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/distribute/googleplay/ |
| D | tv.jd | 101 existing app for phones, tablets, and other devices, using the same package
104 earned in your app for phones and tablets.
113 package name and store listing that you use for phones and tablets.
232 other devices in Google Play Store — on phones and tablets, for
|
| D | about.jd | 274 high-quality apps that show the best of Android on phones and tablets. The
349 great on phones, tablets, and in a web browser.
|
| D | wear.jd | 106 We recommend that you deliver your Wear experience as part of your existing app for phones,
109 ratings you’ve earned in your app for phones and tablets. For wearable apps that depend on an
|
| /frameworks/base/docs/html/guide/practices/ |
| D | index.jd | 4 …ps that look great and perform well on as many devices as possible, from phones to tablets and mor…
|
| /frameworks/base/docs/html/design/wear/ |
| D | index.jd | 6 is substantially different than designing for phones or
33 …timely piece of information. Much like the Google Now feature on Android phones and tablets, users…
|
| /frameworks/base/docs/html/training/tv/start/ |
| D | index.jd | 25 TV apps use the same structure as those for phones and tablets. This approach means you can
|
| D | start.jd | 29 TV apps use the same structure as those for phones and tablets. This similarity means you can
139 activity layout for TV that it does for phones and tablets. The user interface of your TV app (or
151 an app that runs on mobile (phones, wearables, tablets, etc.) as well as Android TV, set the
|
| /frameworks/base/docs/html/wear/design/ |
| D | user-interface.jd | 27 information. Much like Google Now on Android phones and tablets, users swipe vertically to navigate
|
| /frameworks/base/docs/html/distribute/essentials/quality/ |
| D | wear.jd | 32 interaction. Designing apps for wearables is substantially different than designing for phones or
448 Google Play for phones and tablets and still be installable on wearables?</strong>
453 accepted as a Wear app, it will still be available to other device types, such as phones and
|
| D | auto.jd | 396 requirements, will my new or updated app still appear on Google Play for phones and
403 for phones and tablets, your Play Store updates for those devices will not be available until the
|
| /frameworks/base/docs/html/guide/topics/ui/ |
| D | 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/ |
| D | index.jd | 44 ranging from small phones to large TV sets. Therefore, it’s important
|
| /frameworks/base/data/keyboards/ |
| D | Generic.kcm | 450 ### Special keys on phones ###
|
| D | Virtual.kcm | 447 ### Special keys on phones ###
|