| 2024-04-08 13:42:16 |
Michele Lo Russo |
description |
When creating a new session for an automotive application, and waiting on the session page for the stream to load, the discover message arrives too much time after the stream is ready, causing the VHAL availability to not be correctly detected by the dashboard.
Steps to reproduce:
1. From Anbox Cloud Dashboard, create a new session for an AAOS-based application.
2. Wait for the session stream to start without navigating away from the session page.
3. The Android OS boot logo appears -> the stream is ready, so the dashboard checks if VHAL is available -> the discover message has not arrived yet at this point.
4. The Android OS finishes booting, the discover message arrives, but it's not caught by the dashboard anymore.
5. Final result: the VHAL panel is not shown, and the user is forced to go back to session list and rejoin the session to see it. |
When creating a new session for an automotive application, and waiting on the session page for the stream to load, the discover message arrives too early (during Android boot), causing the VHAL capability to not be correctly reported.
Steps to reproduce:
1. From Anbox Cloud Dashboard, create a new session for an AAOS-based application.
2. Wait for the session stream to start without switching tabs/window and without navigating away from the session page.
3. The Android OS boot logo appears -> the stream is ready, so the discover message is received -> it reports no VHAL capability.
4. Final result: the VHAL panel is not shown, and the user is forced to go back to session list and rejoin the session to see it. |
|
