Description
Operating System
Ubuntu 24.04.2 LTS x86_64
Docker Image
budtmo/docker-android:emulator_14.0
Expected behaviour
When running docker exec -it [container] adb emu sms send [number] [message] an sms should show up in android. Using the extended controls > phone meny should also send an sms.
Actual behaviour
Running docker exec -it [container] adb emu sms send [number] [message] still prints "OK" to the terminal. But no SMS shows up in android.
When using the extended controls > phone menu in VNC no feedback is given when the button is pressed, no sms is sent.
If using older android versions sending sms:es works as expected, and when running the emulator manually directly on my machiene (outside docker) sending sms works as well. Only using newer android versions in android does it not work.
Logs
docker logs android-container produces:
2025-06-17 14:37:01,798 INFO supervisord started with pid 8
2025-06-17 14:37:01,798 INFO supervisord started with pid 9
2025-06-17 14:37:01,798 INFO supervisord started with pid 7
2025-06-17 14:37:02,807 INFO spawned: 'android_port_forward' with pid 13
2025-06-17 14:37:02,807 INFO spawned: 'd_screen' with pid 14
2025-06-17 14:37:02,807 INFO spawned: 'appium' with pid 15
2025-06-17 14:37:02,810 INFO spawned: 'device' with pid 16
2025-06-17 14:37:02,810 INFO spawned: 'd_wm' with pid 17
2025-06-17 14:37:02,812 INFO spawned: 'vnc_server' with pid 18
2025-06-17 14:37:02,815 INFO spawned: 'vnc_web' with pid 20
2025-06-17 14:37:02,812 INFO spawned: 'log_web_shared' with pid 19
2025-06-17 14:37:03,227 INFO exited: log_web_shared (exit status 0; not expected)
2025-06-17 14:37:04,194 INFO success: android_port_forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-06-17 14:37:04,229 INFO success: appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-06-17 14:37:04,229 INFO success: device entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-06-17 14:37:04,230 INFO success: d_screen entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-06-17 14:37:04,230 INFO success: d_wm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-06-17 14:37:04,230 INFO success: vnc_server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-06-17 14:37:04,230 INFO success: vnc_web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-06-17 14:37:04,232 INFO spawned: 'log_web_shared' with pid 64
2025-06-17 14:37:04,233 INFO exited: appium (exit status 0; expected)
2025-06-17 14:37:04,440 INFO exited: log_web_shared (exit status 0; not expected)
2025-06-17 14:37:06,442 INFO spawned: 'log_web_shared' with pid 210
2025-06-17 14:37:06,651 INFO exited: log_web_shared (exit status 0; not expected)
2025-06-17 14:37:09,750 INFO spawned: 'log_web_shared' with pid 323
2025-06-17 14:37:10,018 INFO exited: log_web_shared (exit status 0; not expected)
2025-06-17 14:37:10,844 INFO gave up: log_web_shared entered FATAL state, too many start retries too quickly
2025-06-17 14:40:08,189 INFO exited: device (exit status 1; not expected)