True. But then to be sure of getting it, I would have to do one of two things: 1) wait until it pops up again on new code as I continue the tutorial (for example), or 2) undo what I have done and go back a couple pages until it happens again.
Neither option really appeals to me. So I gave the vague message and hoped someone would recognize it, since I can't be the only person having the problem. Does anyone else want to volunteer to try the tutorial? It has rough spots, but nevertheless provides good coverage of a few points I have not seen covered in any other Android tutorial; just don't forget to back up to the very first page. However, if I do see it again, I will append the exact message to this thread. But can't one of you Android SDK hotshots just grep the resources for the SDK (or is it the ADT) for the word 'push'? You will find it faster than I would (by either above method) if you do. Or do you think this message is really coming from the emulator itself? On Oct 22, 6:07 pm, Xavier Ducrohet <x...@android.com> wrote: > If you gave us the exact warning it would help :) > > On Thu, Oct 22, 2009 at 6:03 PM, Indicator Veritatis <mej1...@yahoo.com>wrote: > > > > > > > I thought of that solution too. But the problem is, that in a lot of > > my code iterations, say, for example, following the tutorial at > > >http://activefrequency.com/blog/2009/ground-up-android-part-5-tweetin... > > , > > I get a warning message from Android saying that it cannot push the > > code to the emulator. > > > This appears to imply that if I really want to execute the just-built > > code, I have to restart the emulator. On my machine, that causes me to > > wait about 15S watching 'android', then about 30S watching the same > > word in a funny font. Only then am I offered the opportunity to unlock > > the phone via the menu key and finally, finally, see my app. > > > Or are you experienced developers so familiar with what code can be > > pushed, and what cannot, that you can minimize changes that cannot be > > pushed? > > > On Oct 7, 9:33 am, Romain Guy <romain...@google.com> wrote: > > > Just don't quit theemulator:)) > > > > On Wed, Oct 7, 2009 at 4:41 AM, Mika <mts...@googlemail.com> wrote: > > > > > Hello, > > > > > I'm developing a game on the Android and the problem I'm running into > > > > is the fact that the actualemulatortakes long time to boot. I have > > > > to wait roughly 45s to 75seconds to get into my program. And when > > > > actually doing lot of recompiling I'm wasting too much time for that. > > > > > So what can be done to get around this? I'd like to have theemulator > > > > running and just upload the new program into it and run it instantly. > > > > Is there a way to have theemulatorup and running and upload the > > > > program into it every time I compile, so I wouldn't have to wait for > > > > the boot up time of theemulator? > > > > > All tips and tricks are definitely welcome. > > > > Thank you. > > > > > - Mika > > > > -- > > > Romain Guy > > > Android framework engineer > > > romain...@android.com > > > > Note: please don't send private questions to me, as I don't have time > > > to provide private support. All such questions should be posted on > > > public forums, where I and others can see and answer them > > -- > Xavier Ducrohet > Android SDK Tech Lead > Google Inc. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Beginners" group. To post to this group, send email to android-beginners@googlegroups.com To unsubscribe from this group, send email to android-beginners+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~----------~----~----~----~------~----~------~--~---
