Lines Matching full:application
23 but still sends users in a fiery rage when they try to use the application.
30 Application Not Responding (ANR) dialog, shown at right in Figure 1. The user
31 can choose to let the application continue, but the user won't appreciate having
32 to act on this dialog every time he or she uses your application. It's critical
33 to design responsiveness into your application, so that the system never has
36 <p>Generally, the system displays an ANR if an application cannot respond to
37 user input. For example, if an application blocks on some I/O operation
38 (frequently a network access), then the main application thread won't be able to
40 application is frozen, and displays the ANR to give the user the option to kill
43 <p>Similarly, if your application spends too much time building an elaborate in-memory
45 conclude that your application has hung. It's always important to make
58 application is not responding and provides guidelines for ensuring that your
59 application stays responsive. </p>
63 <p>In Android, application responsiveness is monitored by the Activity Manager
65 for a particular application when it detects one of the following
77 Android applications and how best to structure your application to avoid ANR.</p>
80 This means that anything your application is doing in the main thread that
82 application is not giving itself a chance to handle the input event or Intent
97 Designing your application in this way will allow your main thread to remain
112 application should start a {@link android.app.Service Service} if a
116 whatever application the user is currently has running. If your application
124 lag (or lack of "snappiness," if you will) in an application. As such, here
126 make your application seem responsive to users.</p>
129 <li>If your application is doing work in the background in response to
135 <li>If your application has a time-consuming initial setup phase, consider
139 the application is frozen.</li>
