OpenGrok
Home
Sort by relevance
Sort by last modified time
Full Search
Definition
Symbol
File Path
History
|
|
Help
Searched
full:handset
(Results
1 - 25
of
142
) sorted by null
1
2
3
4
5
6
/frameworks/opt/vcard/tests/res/raw/
v30_simple.vcf
5
ORG:Open;
Handset
; Alliance
/packages/apps/Contacts/tests/assets/
v30_simple.vcf
5
ORG:Open;
Handset
; Alliance
/external/android-clat/
BUGS
7
- assumes the
handset
has its own (routed) /64 ipv6 subnet
/cts/tests/tests/accessibilityservice/res/values/
strings.xml
133
computers. It is developed by the Open
Handset
Alliance, led by Google, and other companies.
136
Handset
Alliance, a consortium of 86 hardware, software, and telecommunication </string>
146
computers.\n\n It is developed by the Open
Handset
Alliance, led by Google, and other companies.
149
Handset
Alliance, a consortium of 86 hardware, software, and telecommunication companies
/sdk/templates/activities/SettingsActivity/
template.xml
6
description="Creates a new application settings activity that presents alternative layouts on
handset
and tablet-size screens."
/frameworks/base/docs/html/guide/practices/
tablets-and-handsets.jd
49
handset
device usually requires that you split those sets apart and display them separately. So
57
tablet or place in separate activities when running on a
handset
. Android 3.0 also introduced
170
article on the left updates the article view on the right. On a
handset
, however, these two
182
one activity; on a
handset
, use separate activities to host each fragment. For example,
184
supply an alternative layout that includes just the first fragment. When running on a
handset
and
198
fragments for your
handset
design can make your code more complicated, because you must manage all
210
both handsets and tablets when using separate activities for the
handset
design:</p>
220
<li>On a
handset
-sized screen, the Activity A layout contains only Fragment A (the list
225
container to present Fragment B, so is only used on
handset
devices when the two fragments must
285
handset
or tablet layout. See the sidebar for more information.</p
[
all
...]
screen-compat-mode.jd
62
normal size
handset
(emulating a 320dp x 480dp screen), with a black border that fills
81
it would on a normal size
handset
(approximately emulating a 320dp x 480dp screen), then scales it
196
handset
screens with a 320dp width, so screen compatibility mode is not applied to any device if
240
handset
screens with a 320dp width, so screen compatibility mode is not applied to any device if
/frameworks/base/docs/html/guide/topics/manifest/
supports-screens-element.jd
34
extra work to make your application work on screens larger than a
handset
device. However, it's
38
when it is on a tablet compared to when running on a
handset
device.</p>
98
than a "normal"
handset
screen, and thus might require some special care
139
<p>For example, a typical
handset
screen has a smallestWidth of 320dp, a 7" tablet has a
189
<p class="note"><strong>Note:</strong> Currently, screen compatibility mode emulates only
handset
207
<p class="note"><strong>Note:</strong> Currently, screen compatibility mode emulates only
handset
/hardware/qcom/audio/legacy/libalsa-intf/
msm8960_use_cases.h
231
#define SND_USE_CASE_DEV_TTY_HANDSET_RX "TTY
Handset
Rx"
232
#define SND_USE_CASE_DEV_TTY_HANDSET_TX "TTY
Handset
Tx"
233
#define SND_USE_CASE_DEV_TTY_HANDSET_ANALOG_TX "TTY
Handset
Analog Tx"
/external/qemu/docs/
ANDROID-SKIN-FILES.TXT
13
an image of a fake
handset
and associated controls (e.g. D-Pad, trackball,
20
emulated
handset
.
25
handset
type. See the last section regarding info on dynamic controls.
236
can be used in any
handset
. All these parts have both an enabled and a
/frameworks/base/core/java/android/app/backup/
RestoreSet.java
31
* of the
handset
model, e.g. "T-Mobile G1".
/sdk/templates/activities/MasterDetailFlow/root/src/app_package/
ContentDetailActivity.java.ftl
11
* activity is only used on
handset
devices. On tablet-size devices,
/frameworks/base/docs/html/training/implementing-navigation/
descendant.jd
47
<p>
Handset
touchscreens are most suitable for displaying one screen at a time (either the master or the detail screen); this concern is further discussed in <a href="{@docRoot}training/design-navigation/multiple-sizes.html">Planning for Multiple Touchscreen Sizes</a>. Descendant navigation in this case is often implemented using an {@link android.content.Intent} that starts an activity representing the detail screen. On the other hand, tablet displays, especially when viewed in the landscape orientation, are best suited for showing multiple content panes at a time: the master on the left, and the detail to the right). Here, descendant navigation is usually implemented using a {@link android.app.FragmentTransaction} that adds, removes, or replaces the detail pane with new content.</p>
49
<p>The basics of implementing this pattern are described in the <a href="{@docRoot}training/multiscreen/adaptui.html">Implementing Adaptive UI Flows</a> lesson of the <em>Designing for Multiple Screens</em> class. The class describes how to implement a master/detail flow using two activities on a
handset
and a single activity on a tablet.</p>
/device/asus/flo/
mixer_paths.xml
259
<path name="
handset
">
263
<path name="
handset
-mic">
285
<path name="voice-
handset
-tmus">
286
<path name="
handset
" />
445
<path name="voice-tty-hco-
handset
">
447
<path name="
handset
" />
458
<path name="voice-tty-vco-
handset
-mic">
/device/lge/mako/
mixer_paths.xml
243
<path name="
handset
">
252
<path name="
handset
-mic">
273
<path name="voice-
handset
-tmus">
274
<path name="
handset
" />
428
<path name="voice-tty-hco-
handset
">
430
<path name="
handset
" />
441
<path name="voice-tty-vco-
handset
-mic">
device.mk
139
# FIXME: Remove persist.audio.
handset
.mic and persist.audio.fluence.mode
142
persist.audio.
handset
.mic.type=digital \
145
persist.audio.
handset
.mic=dmic \
/development/ndk/platforms/android-3/include/linux/
telephony.h
48
handset
,
enumerator in enum:__anon1204
/docs/source.android.com/src/devices/tech/security/
enhancements42.jd
56
been provided to Open
Handset
Alliance members and fixes are available in
enhancements43.jd
84
to Open
Handset
Alliance members and fixes are available in Android Open
/docs/source.android.com/src/source/
index.jd
37
Handset
Alliance, led by Google. Today, many companies -- both original members
/external/skia/legacy/src/effects/
SkBlurMaskFilter.cpp
90
//
handset
) we limit the radius so something manageable. (as opposed to
/frameworks/base/docs/html/design/style/
metrics-grids.jd
9
<li>The size buckets are <em>
handset
</em> (smaller than
/frameworks/base/docs/html/guide/topics/sensors/
sensors_position.jd
48
handset
and tablet manufacturers include a geomagnetic field sensor. Likewise,
handset
manufacturers
49
usually include a proximity sensor to determine when a
handset
is being held close to a user's face
265
of a
handset
device (for example, when a user is making or receiving a phone call). Most
/prebuilts/ndk/4/platforms/android-3/arch-arm/usr/include/linux/
telephony.h
48
handset
,
enumerator in enum:__anon30574
/prebuilts/ndk/4/platforms/android-4/arch-arm/usr/include/linux/
telephony.h
48
handset
,
enumerator in enum:__anon30928
Completed in 3804 milliseconds
1
2
3
4
5
6