RobotiumRC: Emulator unexpected terminated after launching on Mac

[GoogleCodeExporter]

What steps will reproduce the problem?
1. After launching emulator, it is terminated unexpected suddenly.

What is the expected output? What do you see instead?
Expected: Keep working.
Actual: Emulator closed.

What version of the product are you using? On what operating system?
RobotiumRCOverlay2013809, mac os x 10.8.3

Please provide any additional information below.

console log:

Attempting to initialize Android Tools...
C:\Program Files\Android\android-sdk doesn't exist.
Setting Android Tools SDK Dir to /Users/TobyTang/android/android/sdk
SoloTest INFO: Detected 0 device/emulators attached.
SoloTest INFO: Attempting to launch EMULATOR_AVD: Test_A2
Bypassing ServerSocket Socket Thread...
Watching emulator for boot completion within 300 seconds.
Boot detection checking Window for Launcher Activity...
HAX is working and emulator runs in fast virt mode
Boot detection has not found Launcher Activity yet...
Boot detection has not found Launcher Activity yet...
Boot detection has not found Launcher Activity yet...
Emulator boot completion detected!
Emulator: null, Bypassing Reaper Thread...
Emulator launch appears successful.
SoloTest INFO: Emulator launch appears to be successful...
error: device not found
May have failed to unlock device screen due to RuntimeException, Tool return 255
SoloTest INFO: Emulator screen was NOT successfully unlocked!
SoloTest DEBUG: BYPASSING INSTALLATION of target AUT...
SoloTest DEBUG: INSTALLING ./Apks/SAFSTCPMessenger-debug.apk
INSTALLING ./Apks/SAFSTCPMessenger-debug.apk
Checking for devices going offline...
No 'offline' devices detected.
ATTEMPTING ADB Install command: adb [Ljava.lang.String;@7a0d85cc
error: device not found
- waiting for device -

Original issue reported on code.google.com by enduranc...@gmail.com on 22 Aug 2013 at 2:43

[GoogleCodeExporter]

Interesting...it sounds like the action to unlock the screen actually closed 
(or crashed) the emulator.  Can you provide details of your emulator 
configuration?  The type and settings?

Original comment by carl.na...@sas.com on 22 Aug 2013 at 3:18

[GoogleCodeExporter]

I tried two emulators, 

1. Android 2.3.3 

Settings:

avd.ini.encoding=ISO-8859-1
hw.dPad=no
hw.lcd.density=240
sdcard.size=50M
hw.cpu.arch=x86
hw.device.hash=499058361
hw.camera.back=none
disk.dataPartition.size=200M
skin.path=480x800
skin.dynamic=no
hw.keyboard=yes
hw.ramSize=343
hw.device.manufacturer=Google
hw.sdCard=yes
hw.mainKeys=yes
hw.accelerometer=yes
skin.name=480x800
abi.type=x86
hw.trackBall=no
hw.device.name=Nexus S
hw.battery=no
hw.sensors.proximity=yes
image.sysdir.1=system-images/android-10/x86/
hw.sensors.orientation=yes
hw.audioInput=yes
hw.camera.front=none
hw.gps=yes
vm.heapSize=32

2. Android 4.2.2

Settings:

avd.ini.encoding=ISO-8859-1
hw.dPad=no
hw.lcd.density=240
sdcard.size=128M
hw.cpu.arch=x86
hw.device.hash=499058361
hw.camera.back=none
disk.dataPartition.size=256M
partition-size = 128M
hw.gpu.enabled=yes
skin.path=480x800
skin.dynamic=no
hw.keyboard=yes
hw.ramSize=343
hw.device.manufacturer=Google
hw.sdCard=yes
hw.mainKeys=yes
hw.accelerometer=yes
skin.name=480x800
abi.type=x86
hw.trackBall=no
hw.device.name=Nexus S
hw.battery=no
hw.sensors.proximity=yes
image.sysdir.1=system-images/android-17/x86/
hw.sensors.orientation=yes
hw.audioInput=yes
hw.camera.front=none
hw.gps=yes
vm.heapSize=32

Original comment by enduranc...@gmail.com on 22 Aug 2013 at 3:35

[GoogleCodeExporter]

I have successfully duplicated the issue in my environment and have started to 
evaluate causes and solutions.

Original comment by carl.na...@sas.com on 29 Aug 2013 at 6:17

• Changed state: Accepted

[GoogleCodeExporter]

This has been fixed and the code has been pushed to CVS.

This fixes launch detection issues, abrupt closure at launch, and emulators 
sometimes left running at test completion.

This will be available in the next release of RobotiumRC. This is tentatively 
set for later this week or next week alongside an anticipated tentative core 
Robotium release.

Carl Nagle
SAS Research & Development
Planning, Operations and Strategy
General Applications and Tools
carl.nagle@sas.com

Original comment by carl.na...@sas.com on 4 Sep 2013 at 3:36

• Changed state: Fixed