Searched refs:problem (Results 1 – 25 of 42) sorted by relevance
12
| /frameworks/base/core/java/android/view/ |
| D | InputEventConsistencyVerifier.java | 217 problem("ACTION_DOWN but key is already down and this event " in onKeyEvent()
228 problem("ACTION_UP but key was not down."); in onKeyEvent()
237 problem("Invalid action " + KeyEvent.actionToString(action) in onKeyEvent()
269 problem("ACTION_DOWN but trackball is already down."); in onTrackballEvent()
279 problem("ACTION_UP but trackball is not down."); in onTrackballEvent()
291 problem("Invalid action " + MotionEvent.actionToString(action) in onTrackballEvent()
297 problem("Trackball is down but pressure is not greater than 0."); in onTrackballEvent()
299 problem("Trackball is up but pressure is not equal to 0."); in onTrackballEvent()
302 problem("Source was not SOURCE_CLASS_TRACKBALL."); in onTrackballEvent()
344 problem("Touch event stream contains events from multiple sources: " in onTouchEvent()
[all …]
|
| /frameworks/base/docs/html/resources/articles/ |
| D | can-i-use-this-intent.jd | 67 but it only lets you react to the problem, you cannot predict it and update the
|
| D | touch-mode.jd | 74 problem with new Android developers is to rely on
122 solution they need to "fix" the problem of "disappearing" selection/focus. We
|
| D | painless-threading.jd | 55 <p>At first, this code seems to be a good solution to your problem, as it does
94 <p>To remedy this problem, Android 1.5 and later platforms offer a utility class
|
| D | ui-1.6.jd | 72 <p>The problem is that this layout uses forward references. For instance, the
|
| D | future-proofing.jd | 55 better than 1.1 at exposing this problem. Most developers won't need to
|
| D | faster-screen-orientation-change.jd | 75 problem is to temporarily cache the images. They could be cached on the SD card
|
| D | layout-tricks-efficiency.jd | 151 where to position the title's bottom edge. To solve this problem, you
|
| D | layout-tricks-merge.jd | 12 easier to understand the problem this tag solves by looking at an example. The
|
| D | glsurfaceview.jd | 221 This makes it tricky problem to choose the best available surface on
|
| /frameworks/base/docs/html/resources/faq/ |
| D | troubleshooting.jd | 173 You may find any of these steps will fix the problem and with practice you
243 <p>This is similar to the ApiDemos problem described above, except that
295 <p>The problem occurs because the Keytool utility — included in the JDK and used by the Andro…
297 <p>If you encounter this problem, follow these steps to work around it: </p>
311 <p>This problem has been verified on Windows and may apply to other platforms. </p>
|
| /frameworks/base/tools/orientationplot/ |
| D | README.txt | 71 greatly exceeds 60ms then there is a problem with the accelerometer or the
|
| /frameworks/base/docs/html/sdk/1.1_r1/ |
| D | upgrading.jd | 149 apps in my IDE because of a signing error</a> for information about how to solve the problem.</p>
|
| /frameworks/base/docs/html/guide/topics/processes/ |
| D | process-lifecycle.jd | 31 it terminates the spawned thread running in the process. The solution to this problem
|
| /frameworks/base/docs/html/guide/practices/design/ |
| D | seamlessness.jd | 32 <p>A common seamlessness problem is when an application's background process
51 <p>Another example of a seamlessness problem is when an activity inadvertently
|
| D | responsiveness.jd | 53 level, you can think of responsiveness as a <em>class</em> problem. (Compare
|
| D | performance.jd | 302 <p>The problem is that the VM considers direct access to <code>Foo</code>'s
387 have a problem. Make sure you can accurately measure your existing performance,
|
| /frameworks/base/docs/html/resources/ |
| D | community-groups.jd | 69 help others understand your problem. Code or log snippets, as well as
|
| /frameworks/base/docs/html/resources/tutorials/opengl/ |
| D | opengl-es10.jd | 330 being rendered in a frame which is not perfectly square. You'll fix that problem using a projection
342 system onto your typically non-square screen. To solve this problem, you can apply an OpenGL
|
| D | opengl-es20.jd | 410 being rendered in a frame which is not perfectly square. You'll fix that problem using a projection
422 system onto your typically non-square screen. To solve this problem, you can apply an OpenGL
|
| /frameworks/base/docs/html/guide/topics/resources/ |
| D | localization.jd | 153 <li>This application might compile without a problem. An IDE such as Eclipse
156 the application might run without a problem, because
357 highlight this kind of error, and you will not see the problem when you
|
| /frameworks/base/docs/html/guide/developing/tools/ |
| D | proguard.jd | 175 …you ensure that you can debug a problem if a user encounters a bug and submits an obfuscated stack…
|
| /frameworks/base/docs/html/guide/topics/fundamentals/ |
| D | processes-and-threads.jd | 264 <p>To fix this problem, Android offers several ways to access the UI thread from other
362 <p class="caution"><strong>Caution:</strong> Another problem you might encounter when using a worker
|
| /frameworks/base/docs/html/sdk/ |
| D | RELEASENOTES.jd | 469 problem is being investigated.</li>
631 problem, you can close the file in the editor and open it again, or you
797 problem, you can close the file in the editor and open it again, or you
|
| /frameworks/base/docs/html/guide/practices/ |
| D | screen-compat-mode.jd | 53 problem, screen compatibility mode can make the application a little more usable on larger
|
12