Lines Matching refs:will
73 This will fire the onSaveInstanceState() and onPause() methods, and will likely result in
77 appeared, your application will likely lose that data when your application is
111 the background. Doing so will interrupt whatever application is currently
118 instead use the NotificationManager to set Notifications. These will appear in
129 computation, you should probably move it to a thread. This will prevent the
140 <p>If you have long-running code, running it inline in your Activity will run it
141 on the event handler thread, effectively blocking the event handler. This will
149 <p>Any application worth using will probably have several different screens.
163 of Activity objects. This will make your code a lot more maintainable in the long
179 <p>Different Android-powered devices will support different screen resolutions.
180 Some will even be able to change resolutions on the fly, such as by switching
193 <p>Android devices will come with a variety of network-connectivity options. All
194 will have some data-access provision, though some will be faster than others.
196 GSM networks. Even 3G-capable devices will spend lots of time on non-3G
197 networks, so slow networks will remain a reality for quite a long time to
203 then that's great — their experience will only improve. You want to avoid the
220 Android will support a variety of handset form-factors. That's a fancy way of
221 saying that some Android devices will have full "QWERTY" keyboards, while
222 others will have 40-key, 12-key, or even other key configurations. Similarly,
223 some devices will have touch-screens, but many won't.