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:
when running:
i can see that the serial port was forwarded:
afterwards i run the adb commands:
Now,
when sending from android shell:
I can see the outcome in windows COM2 port
but, when trying to send from windows:
the emulator crashes with the following information:
did anyone encountered such an issue ?
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
when running:
Code:
adb shell "dmesg|grep tty"
[ 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
afterwards i run the adb commands:
Code:
adb root
adb shell "setenforce 0"
Now,
when sending from android shell:
Code:
echo test >/dev/ttyS1
but, when trying to send from windows:
Code:
echo test > COM2
the emulator crashes with the following information:
and the emulator crash data is (partially):emulator: ERROR: detected a hanging thread 'QEMU2 main loop'. No response for 15058 ms
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
did anyone encountered such an issue ?