Lines Matching full:emulator
12 <li><a href="#nodevice">ADB reports "no device" when an emulator is running</a></li>
23 <li><a href="#eclipse">Eclipse isn't talking to the emulator</a></li>
27 app in the emulator</a></li>
69 <a name="nodevice"></a><h2>ADB reports "no device" when an emulator is running</h2>
76 <li>You often must restart your device or emulator before a new activity shows
134 the emulator not being started, not being able to run the application, or even seeming to run an old version of the application.</p>
167 <a name="eclipse"></a><h2>Eclipse isn't talking to the emulator</h2>
168 <p>When communication doesn't seem to be happening between Eclipse and the emulator, symptoms can include: nothing happening when you press run, the emulator hanging waiting
170 to find the emulator or shell. By far the most common symptom is that when you press run, the emulator starts (or
178 Quit the emulator if it is running
181 Check that any emulator processes are killed (sometimes they can hang, use ps on unix or mac, or task manager in the process view on
203 applications included with the SDK are preinstalled on the emulator and for that reason have been
207 so only after you uninstall the <em>preinstalled</em> version of the app from the emulator. If
216 onto the emulator, a copy that is signed with a different certificate (the Android IDE tools will
225 <li>If no emulator instance is running, start an emulator using using the command <code>emulator &</code>.</li>
231 <p>Note that if multiple emulator instances are running, you need to direct your uninstall/install
232 commands to the emulator instance that you are targeting. To do that you can add the
235 <pre>adb -s emulator-5556 install</pre>
241 app in the emulator</a></h2>
244 you cannot fix it by uninstalling GestureBuilder from the emulator. The
250 <ul><li><p>You cannot run GestureBuilder in the emulator:</p>
281 <li>Run the GestureBuilder application on the emulator.</li>
