On Thu, May 13, 2010 at 9:29 PM, Kevin Brooks bear35...@gmail.com wrote:
I have to shut down the IDE every time I run my application.
If you are having consistent issues where things just aren't working right,
I would just uninstall and re-install everything.
That might not be good enough. I found, for example, that my system
runs Eclipse a LOT better after being upgrade from .5 to 2.5 Gigs of
RAM. But I still have occasional problems with Eclipse locking up the
system completely, usually only when using Ctl-Tab to switch BACK to
Eclipse.
On May 14,
On Wed, May 12, 2010 at 10:43 PM, Kevin Brooks bear35...@gmail.com wrote:
Anyone have a clue what is happening?
In these cases, I usually close everything, run adb kill-server, and
restart.
-
Regarding the path, the installation instructions do say to add SDK
tools folder to your Windows path.
I am a professional Java dev. and I cannot remember the last time I
had to edit the Windows path. Given there is an installer and GUI-
based IDE support, if it is necessary for the Android SDK
if you strictly use Eclipse, then you shouldn't have to change your path.
Eclipse uses the location to the SDK folder (set in the Eclipse
preferences under Android) to find all the external tools it needs.
Xav
On Wed, May 12, 2010 at 2:25 PM, tiger unixep...@mailinator.com wrote:
Regarding the
I am having a similar problem. When I try to launch my application I
receive the following messages even if I already have the emulator running.
[2010-05-12 22:29:37 - FlashcardLoop] --
[2010-05-12 22:29:37 - FlashcardLoop] Android Launch!
[2010-05-12 22:29:37 -
On May 10, 2:55 pm, TreKing treking...@gmail.com wrote:
On Mon, May 10, 2010 at 4:32 AM, tiger unixep...@mailinator.com wrote:
Eclipse does not seem to see the emulator has fully booted up.
Please elaborate.
The last message in the eclipse console is Launching a new emulator
with Virtual
On May 10, 2:55 pm, TreKing treking...@gmail.com wrote:
On Mon, May 10, 2010 at 4:32 AM, tiger unixep...@mailinator.com wrote:
Eclipse does not seem to see the emulator has fully booted up.
Please elaborate.
Last message in Eclipse is: Launching a new emulator with Virtual
Device... I can
Is it displaying the lock screen? If so, you need to unlock the emulator,
and Hello World should be sitting right there waiting for you...
--
There are only 10 types of people in the world...
Those who know binary and those who
Yeah, I definitely unlocked it. As I said from the console messages in
Eclipse, you can see it is stopped at the point where it is waiting
for feedback from the emulator, but it is not getting it.
On May 11, 3:43 pm, Justin Anderson janderson@gmail.com wrote:
Is it displaying the lock
On Tue, May 11, 2010 at 10:26 AM, tiger unixep...@mailinator.com wrote:
Yeah, I definitely unlocked it. As I said from the console messages
in Eclipse, you can see it is stopped at the point where it is waiting for
feedback from the emulator, but it is not getting it.
Instead of launching
On May 11, 5:19 pm, TreKing treking...@gmail.com wrote:
..
Instead of launching your app to trigger the emulator to start, launch the
Emulator from the AVD control window. Wait for it to boot. Unlock the screen
if necessary. Then try running your app, selecting the emulator instance as
your
On Tue, May 11, 2010 at 4:05 PM, tiger unixep...@mailinator.com wrote:
This confirms what I have been saying - that Eclipse is not seeing or
communicating with the running emulator after it starts it.
If you run DDMS, does that list the emulator as a target?
13 matches
Mail list logo
