- Forum posts: 1
Nov 7, 2018, 8:29:33 AM via Website
Nov 7, 2018 8:29:33 AM via Website
Hi,
I have the following set:
* Windows 10 pro
* Android Studio Emulator 27.3.10
* Virtual Windows COM port bridge COM1 <--> COM2
I start the emulator with a clean API 25
target Android 7.1.1 for x86
with the following windows command:
[CODE]emulator @Device_API_25 -qemu -serial COM1[/CODE]
when running: [CODE]adb shell "dmesg|grep tty"[/CODE]
i can see that the serial port was forwarded:
[QUOTE][ 0.000000] console [ttyS0] enabled
[ 2.399629] 00:04: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 2.430745] 00:05: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A[/QUOTE]
afterwards i run the adb commands:
[CODE]adb root
adb shell "setenforce 0"[/CODE]
Now,
when sending from [B]android shell[/B]:
[CODE]echo test >/dev/ttyS1[/CODE]
I can see the outcome in windows COM2 port
but, when trying to send from [B]windows[/B]:
[CODE]echo test > COM2[/CODE]
the emulator crashes with the following information:
[QUOTE]emulator: ERROR: detected a hanging thread 'QEMU2 main loop'. No response for 15058 ms[/QUOTE]
and the emulator crash data is (partially):
[QUOTE]Operating system: Windows NT
10.0.17134
CPU: amd64
family 6 model 61 stepping 4
4 CPUs
Crash reason: EXCEPTION_ACCESS_VIOLATION_WRITE
Crash address: 0x0
Assertion: Unknown assertion type 0x00000000
Process uptime: not available[/QUOTE]
did anyone encountered such an issue ?
Recommended editorial content
With your consent, external content is loaded here.
By clicking on the button above, you agree that external content may be displayed to you. Personal data may be transmitted to third-party providers in the process. You can find more information about this in our Privacy Policy.