Home
last modified time | relevance | path

Searched refs:t (Results 1 – 25 of 89) sorted by relevance

1234

/docs/source.android.com/src/source/community/
Dgroups-charter.jd25 … to join us in accepting nothing less. Being courteous does not mean we can't constructively disag…
27t put hard restrictions on the topics discussed in the group: as long as the topic is relevant to …
29 …sed in support of the completion of specific tasks. On these groups, we don't welcome off-topic co…
35 …d rudeness are not welcome in our community under any circumstances. We don't have a formal policy…
39 …on't have to accept someone else being disrespectful just because it wasn't directed at you. Just …
Dindex.jd19 this page probably isn't for you; you should contact your carrier or retailer
161 not mean we can't constructively disagree with each other, but it does mean
169 discussions of Android or users helping each other. Generally we don't put
175 of articles and ideas critical of Android—after all, we can't improve if
176 we don't listen.
180 completion of specific tasks. On these groups, we don't welcome off-topic
194 are not welcome in our community under any circumstances. We don't have a
201 and you don't have to accept someone else being disrespectful just because it
202 wasn't directed at you. Just remember to be polite and courteous yourself!
203 Don't add fuel to the fire.</p>
/docs/source.android.com/src/source/
Dreport-bugs.jd32 a security vulnerability, <em>please don't use the forms below</em>. Using a public form may
39 your bug</a> to see if anyone has already reported it. Don't forget to
72 that aren't part of AOSP need to be reported with those applications'
74 <p>Please note that we can't guarantee that any particular bug can be fixed in
78 telling us something isn't working is usually useless, and will probably be
90 Happens when "Object o = null". Doesn't happen when changed to "Object o".
93 I wouldn't get the error message--would work with Object o = null.
98 <p>This is a poor bug report because it doesn't provide any context for the
100 something else? It also doesn't provide any code or hint on how to reproduce
101 it. In other words, this bug report doesn't provide enough information for
Dknown-issues.jd34 CellBroadcastReceiver doesn't get included in the system.</p>
45 <p><strong>Cause</strong>: Some makefile references that path, which doesn't exist.</p>
49 doesn't start and stays stuck on a black screen.</p>
51 which doesn't have all the features necessary to run recent versions
59 <h3 id="emulator-built-on-macos-107-lion-doesnt-work">Emulator built on MacOS 10.7 Lion doesn't wor…
61 and/or on XCode 4.x doesn't start.</p>
69 on emulator builds, the resulting build doesn't work.</p>
179 don't change, and if they do and you can't connect you'll have
192 <h3 id="camera-and-gps-dont-work-on-galaxy-nexus">Camera and GPS don't work on Galaxy Nexus.</h3>
193 <p><strong>Symptom</strong>: Camera and GPS don't work on Galaxy Nexus.
[all …]
Dfaqs.jd103 meanwhile, don't want to constantly track new versions of the
112 future work just to keep up. Other parts of the Android system that aren't
124 device's release; however in other releases, this isn't possible. In all cases, we
157 Android ecosystem, including Google Play; devices that don't meet the
172 in the ART runtime. Similarly, we won't accept contributions such as GPL
180 <p>The Android Open Source Project doesn't really have a notion of a
202 But if the device isn't compatible, it's not considered part of the Android
208 shared by all compatible devices. This option isn't available to devices
209 that aren't compatible.</p>
212 including some on which third-party apps won't run properly. The
[all …]
Dcode-style.jd35 <h3 id="dont-ignore-exceptions">Don't Ignore Exceptions</h3>
51 thing to do, but at least you have to think about it. In Java you can't escape
121 <h3 id="dont-catch-generic-exception">Don't Catch Generic Exception</h3>
139 Exception in the code you're calling, the compiler won't help you realize you
140 need to handle that error differently. And in most cases you shouldn't be
161 <p>Rethrow the exception. Many times you don't need to catch the exception at
166 not catching an exception, don't scowl. Smile: the compiler just made it
168 <h3 id="dont-use-finalizers">Don't Use Finalizers</h3>
174 <p>Decision: we don't use finalizers. In most cases, you can do what
285 every local variable declaration should contain an initializer. If you don't
[all …]
Dlife-of-a-bug.jd105 note that this isn't a guarantee, and it's not uncommon for bugs to go from
142 behavior described isn't a bug, but is the intended behavior. This state is
154 The report didn't have enough information to be able to take any action.</p>
191 number of bugs. As a result, sometimes bugs don't make it through all the
Dbuilding-dream.jd43 <p>Run <code>make adb</code> if you don't already have adb in your path.</p>
52 …or dream (the default is the equivalent of "lunch generic-eng", which doesn't contain dream-specif…
Dlicenses.jd69 openness in the mobile world, and we don't believe it's possible to predict or
71 we encourage everyone to make devices that are open and modifiable, we don't
102 our own code. They aren't criticisms of LGPL or other licenses. We are
D64-bit-builds.jd104 <p>In a Multilib build, conditionals like <code>ifeq $(TARGET_ARCH)</code> don’t work any
185 </code>with explicit variables), it won’t reliably work any more. That’s
204 <p>In Multilib, you can’t use <code>TARGET_ARCH</code> (or together with
/docs/source.android.com/scripts/
Dbuild.py45 t = '' variable
47 t += open(os.path.join(TEMPLATE_DIR, f), 'r').read()
48 template = string.Template(t)
/docs/source.android.com/src/devices/sensors/
Dreport-modes.jd50 minute (including at time t=0 because of the activation of the sensor, and t=60
52 minute because the value of the step count didn’t change after t=60 seconds. </li>
Dbatching.jd57 <li> or when the sensor doesn’t have a hardware FIFO (<code>sensor_t.fifoMaxEventCount =
89 <p>As long as the SoC doesn’t enter the suspend mode, no event shall be dropped or
95 <code>max_report_latency</code> of the other sensors didn’t elapse yet. The general goal is
122 <code>max_report_latency</code> of some sensors didn’t elapse yet. This minimizes the risk
154 <li> The user doesn’t move for a long time, causing accelerometer events to continue
159 didn’t walk (bad!) </li>
Dpower-use.jd59 <p>For one-shot wake-up sensors, the power is measured while the sensor doesn’t
60 trigger (so it doesn’t wake the SoC up). Similarly, for other sensors, the
Dsuspend-mode.jd30 doesn't perform any tasks. “Suspend” is a low-power mode where the SoC is not
50 the system doesn't go to suspend, unregister from the sensors when they do
/docs/source.android.com/src/devices/tech/test_infra/tradefed/fundamentals/
Ddevices.jd27 between the case where the command hasn't finished yet, the case where the device doesn't support
53 <p>Suppose you have a test that doesn't interact with a device at all. For instance, it might just
Dindex.jd48 Runners to identify results that don't make sense, and to work with the Developers and
68 things that aren't directly discussed in the documentation.</p>
/docs/source.android.com/src/devices/tech/dalvik/
Dinstruction-formats.jd73 format "<code>21t</code>" is of length two, contains one register reference,
146 <td>t</td>
148 <td>branch <b>t</b>arget</td>
203 <p>In the cases where a format value isn't explictly part of the syntax
251 <td>10t</td>
257 <td>20t</td>
276 <td>21t</td>
316 <td>22t</td>
341 <td>30t</td>
358 <td>31t</td>
/docs/source.android.com/src/devices/graphics/
Darchitecture.jd39 You don't need detailed knowledge of the app framework, and very few API calls
40 will be mentioned, but the material herein doesn't overlap much with other
266 other facts you probably won't care about ("handle" and "hints" and "flags" and
271 shown above are using overlays, FB_TARGET isn’t being used for this frame. The
296 with an overlay, so we can't alter the buffer contents until the display is done
299 scanning the layer list, looking for updates. SurfaceFlinger won't find any new
348 bars, which for our purposes here aren’t changing, so SurfaceFlinger keeps using
354 <p><strong>**</strong> - The buffer doesn’t actually “empty”; if you submit it
361 zero CPU and GPU time. But we can't count on that, so we need to allow a little
483 buffer appropriately. To ensure that a buffer isn't updated by two clients at
[all …]
/docs/source.android.com/src/compatibility/
Dindex.jd30 the Internet. We haven't met a user yet who didn't want to customize it by
40 is a line of code that didn't add a new feature. The more compatible phones
/docs/source.android.com/src/devices/audio/
Davoiding_pi.jd238 between processes, don't
240 are within bounds. This verification isn't needed between threads
318 <code>ps -t -p</code>
326 After all of this discussion, don't be afraid of mutexes. Mutexes
/docs/source.android.com/src/devices/tech/ram/
Dlow-ram.jd41 <li>Don’t allow large services to put themselves back into A Services (so they
42 can’t cause the launcher to be killed).</li>
76 RAM includes RAM of cached processes, so that OEMs don’t try to optimize the
217 <code>swapprio</code> is optional and not needed if you don't have more than one swap
275 <li>Don't enable code that is writing Parcel data to disk and reading it later.</li>
276 <li>Don't subscribe to every package installed, instead use ssp filtering. Add
291 fact that we just don't want them running at all.</p></li>
/docs/source.android.com/src/devices/tech/security/verifiedboot/
Ddm-verity.jd102 <p>If you have a block in a layer that isn't completely filled naturally by the
104 expected 4k. This allows you to know the hash tree hasn't been removed and is
109 out to disk. Note that this doesn't reference layer 0 of the root hash.</p>
166 <p>This makes sure you haven't elected to verify an unverified partition. If so,
/docs/source.android.com/src/devices/tech/ota/
Ddevice_code.jd282 these images you don't need to provide an <code>Init()</code> function. For
370 This mapping does <i>not</i> happen for <code>CheckKey()</code>, so you can't
388 <p class="note"><strong>Note:</strong> If <b>visible</b> is false, it doesn't
390 highlight, invoke highlighted item) since the user can't see the highlight.
690 play audio. (Perhaps you don't want to support a menu or the "text display"
699 doesn't have keys or you want to process them differently.</p>
780 <p><code>ReadValueArgs()</code> doesn't do type-checking, so you must do that
806 </code> both. Don't forget to call <code>FreeValue()</code> on the objects you
815 result->data = strdup(successful ? "t" : "");
828 return StringValue(strdup(successful ? "t" : ""));
[all …]
/docs/source.android.com/src/devices/tv/
DHDMI-CEC.jd33 the TV and switch its input port automatically, so you don’t have to search for
38 standard in different ways, devices don’t always understand each other and
40 can’t safely assume that two products that claim CEC support are completely
207 * It is used when the system doesn't need to process CEC command any more,

1234