| 2024-08-14 14:03:37 |
Simon Fels |
description |
Seeing the following in logs from Anbox with 1.23.0-20240809080136.4a6ba963a images:
Aug 14 13:42:39 foo anbox-starter[1004]: [libprotobuf ERROR google/protobuf/message_lite.cc:133] Can't parse message of type "anbox.protobuf.vhal.EmulatorMessage" because it is missing required fields: (cannot determine missing fields for lite message)
Aug 14 13:42:39 foo anbox-starter[1004]: E0814 13:42:39.470263 4491 streaming_server.cpp:700] Could not retrieve all prop configs from VHAL |
Seeing the following in logs from Anbox with 1.23.0-20240809080136.4a6ba963a images:
Aug 14 13:42:39 foo anbox-starter[1004]: [libprotobuf ERROR google/protobuf/message_lite.cc:133] Can't parse message of type "anbox.protobuf.vhal.EmulatorMessage" because it is missing required fields: (cannot determine missing fields for lite message)
Aug 14 13:42:39 foo anbox-starter[1004]: E0814 13:42:39.470263 4491 streaming_server.cpp:700] Could not retrieve all prop configs from VHAL
The error stays regardless how often you connect again to the stream. The only thing which changes is that the protobuf error is not showing up again:
Aug 14 13:57:09 aaos13 anbox-starter[1005]: I0814 13:57:09.216611 3538 peer_connection.cpp:828] New data channel control added
Aug 14 13:57:09 aaos13 anbox-starter[1005]: E0814 13:57:09.216915 3536 streaming_server.cpp:700] Could not retrieve all prop configs from VHAL
Restarting Anbox + Android typically fixes the problem. |
|
