[TIMOB-13381] Android Emulator: process launches in new terminal on Windows

GitHub Issue	n/a
Type	Bug
Priority	High
Status	Closed
Resolution	Won't Fix
Resolution Date	2013-11-09T00:56:05.000+0000
Affected Version/s	Release 3.1.0
Fix Version/s	2013 Sprint 23, 2013 Sprint 23 Core
Components	Android, Tooling
Labels	androidbuild, cb-verified, qe-3.1.0, regression
Reporter	Dustin Hyde
Assignee	Chris Barber
Created	2013-04-04T21:59:29.000+0000
Updated	2017-03-22T18:06:30.000+0000

Description

Android Emulator: process launches in new terminal. The emulator output should exist in the Studio console. See screenshots. Test Steps: 1. Run Android Emulator. Test Results: Process launches in new OS terminal, logs appear in external terminal. Stable Results: Process launches and log appear in Studio console.

Attachments

File	Date	Size
regression.png	2013-04-04T21:59:30.000+0000	166613
stable.png	2013-04-04T21:59:30.000+0000	41583

Comments

Shalom Gibly 2013-04-04

Moving this to Titanium Mobile. This one happens from the command-line as well. Instead of the output from the "emulator.exe" should be tunneled to the titanium build process. That way, the Studio will automatically grab and display the output is its console.
Ingo Muschenetz 2013-04-06

It appears that fixing this will require a significant amount of rework. Deferring from 3.1.0, but would like to get it into 3.1.1 if we can figure out a way to do it without rewriting the Android build scripts just yet.

Shawn Lipscomb 2013-08-23

Still a problem in Ti Studio 3.1.2.201308091617 and mobile SDK 3.1.2.GA: - - Emulator.exe DOS window appears and persists the entire time the emulator is running. - - All emulator output (logcat) is captured in that window only and does not appear in the "Console" area of Ti Studio. In fact, when looking at the "Console" tab at the bottom of Ti Studio, the following log entries (below) appear with the title "Android Emulator Process". However, shouldn't these log entries show in the subview entitled "Studio Console"? When I click on the little dropdown that looks like a computer monitor, I get 3 choices: "Studio Console", "FastDev Process", and "Titanium Android Emulator". And then only the Android emulator output should show in the subview entitled "Titanium Android Emulator". {panel}

   Titanium Command-Line Interface, CLI version 3.1.2, Titanium SDK version 3.1.2.GA
   Copyright (c) 2012-2013, Appcelerator, Inc.  All Rights Reserved.
   [INFO] :   Running emulator process: python "C:\Users\Shawn\AppData\Roaming\Titanium\mobilesdk\win32\3.1.2.GA\android\builder.py" "emulator" "Test App" "C:\Program Files (x86)\Android" "C:\Titanium\Workspace\TestApp" "com.eCotton.TestApp" "4" "HVGA" "armeabi"
   [INFO] :   Running build process:  python "C:\Users\Shawn\AppData\Roaming\Titanium\mobilesdk\win32\3.1.2.GA\android\builder.py" "simulator" "Test App" "C:\Program Files (x86)\Android" "C:\Titanium\Workspace\TestApp" "com.eCotton.TestApp" "4" "HVGA"
   [INFO] logfile = C:\Titanium\Workspace\TestApp\build.log
   [INFO] Building Test App for Android ... one moment
   [INFO] Titanium SDK version: 3.1.2 (08/14/13 12:45 5ceaff8)
   [INFO] :   Emulator is running
   [INFO] Waiting for the Android Emulator to become available
   [INFO] Fastdev server running, deploying in Fastdev mode
   [INFO] Copying CommonJS modules...
   [INFO] Copying project resources..
   [INFO] Detected change in tiapp.xml, or assets deleted. Forcing full re-build...
   [INFO] Force including all modules...
   [INFO] Force including all modules...
   [INFO] Compiling Javascript Resources ...
   [INFO] Copying platform-specific files ...
   [INFO] Compiling Android Resources... This could take some time
   [WARN]     (skipping dir '.Documents' due to ANDROID_AAPT_IGNORE pattern '.*')
   [INFO] Installing application on emulator
   [INFO] Launching application ... Test App
   [INFO] Deployed Test App ... Application should be running.
   [INFO] :   Project built successfully in 2m 2s 370ms
   [INFO] :   Running logcat process: python "C:\Users\Shawn\AppData\Roaming\Titanium\mobilesdk\win32\3.1.2.GA\android\builder.py" "logcat" "C:\Program Files (x86)\Android" "-e"

{panel}

Ingo Muschenetz 2013-08-23

[~bitshftr] Thank you. This is going to be addressed with the rewrite of the Android build scripts, happening for 3.2.0
Chris Barber 2013-11-09

After trying numerous ways around this, there's nothing we can do from Node.js to prevent the terminal window from opening AND detach the process so that the emulator will continue to run after the build completes or is aborted. I've tried spawning intermediate processes, but that produced the results. We might have been able to solve it with a small win32 app that spawns it, but that's a lot of work for something that is just an annoyance. As a workaround, simply launch the Android emulator ahead of time.
Lee Morris 2017-03-22

Closing ticket as the issue will not fix and with reference to the above comments. A workaround has also been provided.

JSON Source