You need to post the results of your* logcat* output. That is the source
of information you need.
Firewall shouldn't make a difference.
Again: open a command prompt. Type: adb logcat
Look for Stack traces or error messages. They will be there.
On Wednesday, April 4, 2012 1:44:50 AM UTC-7, sgiddings wrote:
>
> Hi Mike,
>
> Ok, have done as you suggested.
>
> - I completed all of the instructions within the Notepadv2 tutorial.
> - I then started the command line tool you indicated.
> - I then returned to eclipse and did "Run As -> Android application".
>
> The emulator started up, but the application (newly built, never run
> before) was not installed on the emulator.
> Here is the full output from the logcat screen :
> C:\android-sdk\platform-tools>adb logcat
> * daemon not running. starting it now on port 5037 *
> * daemon started successfully *
> - waiting for device -
>
> Here is the output from the Android console :
> [... - Notepadv2] ------------------------------
> [... - Notepadv2] Android Launch!
> [... - Notepadv2] adb is running normally.
> [... - Notepadv2] Performing com.android.demo.notepad2.Notepadv2 activity
> launch
> [... - Notepadv2] Automatic Target Mode: launching new emulator with
> compatible AVD 'Embedded-GMaps-device'
> [... - Notepadv2] Launching a new emulator with Virtual Device
> 'Embedded-GMaps-device'
> [... - Emulator] emulator: emulator window was out of view and was
> recentered
> [... - Emulator]
>
> As you may know, the project was copied from the existing project provided
> in the tutorial sources.
> Further information - I still have my commodo
> firewall/anitvirus/defense+/sandbox active.
>
> Are there other sources of information which could help ?
> Simon
>
> On Tuesday, 3 April 2012 16:51:43 UTC+2, Mike Wolfson wrote:
>>
>> That log is showing everything working properly, so we still don't have
>> all the information we need.
>>
>> Do you see a "Force Close" in the emulator window?
>>
>> Run: *ANDROID_HOME\platform-tools\adb logcat *- from a command prompt.
>> This will give you a much more verbose output, which may help identify the
>> exact nature of the problem (it is most likely something particular to your
>> project, and not the environment).
>>
>> The output you included shows everything working correctly (which is
>> probably why you are not getting answers on SO).
>>
>> -M
>>
>> On Tuesday, April 3, 2012 7:40:35 AM UTC-7, sgiddings wrote:
>>>
>>> Hi Mike,
>>>
>>> Thanks for taking the time to answer.
>>> This is what I get in the Android console :
>>> [... Notepadv1] ------------------------------
>>> [... Notepadv1] Android Launch!
>>> [... Notepadv1] adb is running normally.
>>> [... Notepadv1] Performing com.android.demo.notepad1.Notepadv1 activity
>>> launch
>>> [... Notepadv1] Automatic Target Mode: launching new emulator with
>>> compatible AVD 'Embedded-GMaps-device'
>>> [... Notepadv1] Launching a new emulator with Virtual Device
>>> 'Embedded-GMaps-device'
>>> [... Emulator] emulator: emulator window was out of view and was
>>> recentered
>>> [... Emulator]
>>>
>>> It goes no further than that.
>>> Other times I will see the following :
>>> [... Notepadv1] ------------------------------
>>> [... Notepadv1] Android Launch!
>>> [... Notepadv1] adb is running normally.
>>> [... Notepadv1] Performing com.android.demo.notepad1.Notepadv1 activity
>>> launch
>>> [... Notepadv1] Automatic Target Mode: launching new emulator with
>>> compatible AVD 'Embedded-GMaps-device'
>>> [... Notepadv1] Launching a new emulator with Virtual Device
>>> 'Embedded-GMaps-device'
>>> [... Emulator] emulator: emulator window was out of view and was
>>> recentered
>>> [... Emulator]
>>> [... Notepadv1] New emulator found: emulator-5554
>>> [... Notepadv1] Waiting for HOME ('android.process.acore') to be
>>> launched...
>>> [... Notepadv1] HOME is up on device 'emulator-5554'
>>> [... Notepadv1] Uploading Notepadv1.apk onto device 'emulator-5554'
>>> [... Notepadv1] Installing Notepadv1.apk...
>>> [... Notepadv1] Success!
>>> [... Notepadv1] Starting activity com.android.demo.notepad1.Notepadv1 on
>>> device emulator-5554
>>> [... Notepadv1] ActivityManager: Starting: Intent {
>>> act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER]
>>> cmp=com.android.demo.notepad1/.Notepadv1 }
>>>
>>> I removed the date and time data for ease of reading.
>>> The project given as example here is one copied as per the Notepad view
>>> tutorial.
>>> I do not know what other information I can give here.
>>>
>>> As far as StackOverflow is concerned, I have already looked and even
>>> posted a question - no response as yet.
>>>
>>> Simon
>>>
>>> On Tuesday, 3 April 2012 16:09:54 UTC+2, Mike Wolfson wrote:
>>>>
>>>> You will need to give some more information on your particular problem
>>>> (do you see "Insufficient space error" for instance). What exactly is the
>>>> error you are receiving?
>>>>
>>>> It is simple to get everything setup, but their are lots and lots of
>>>> nuances that could cause environment issues - so you will need to be more
>>>> specific about exactly what error you are receiving.
>>>>
>>>> For the most part, I would suggest checking:
>>>> http://www.stackoverflow.com for these sort of technical issues, as
>>>> that is the best place to get these sort of technical answers.
>>>>
>>>> Good luck - it can be a little daunting to get everything setup, but
>>>> once you do - Android development is a lot of fun.
>>>>
>>>> -M
>>>>
>>>> On Tuesday, April 3, 2012 12:49:43 AM UTC-7, sgiddings wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> I am starting to develop an application under android - yes first
>>>>> application.
>>>>> Having more than 20 years of development of applications and web
>>>>> sites, I expected that the eclipse/adk/android emulator environment would
>>>>> work once set up according to instructions.
>>>>>
>>>>> However, when building and running test applications (like the WebView
>>>>> example) it will successfully load into the emulator once or twice and
>>>>> then
>>>>> never again.
>>>>> This is the same weather it is run as "Run" or as "Debug".
>>>>> Even killing the adb and restarting eclipse will not always solve this
>>>>> problem.
>>>>>
>>>>> I am sure that there are steps that I need to take so that I can
>>>>> systematically code and run without environment problems.
>>>>>
>>>>> I work under Windows XP sp3 with the windows firewall disabled (I run
>>>>> the commodo firewall - which is also stopped)
>>>>> Eclipse version is : Indigo Service Release 2 (v1.4.2)
>>>>> Android tools : v17
>>>>> JDK v6u31
>>>>>
>>>>> I have installed Eclipse and all android software in directories which
>>>>> do not contain spaces (just in case).
>>>>> Can anyone please help with this ?
>>>>>
>>>>
--
You received this message because you are subscribed to the Google Groups
"Android Discuss" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/android-discuss/-/EsR2_g8CFR4J.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/android-discuss?hl=en.
