VHAL capability not reported for newly created sessions
Bug #2060532 reported by
Michele Lo Russo
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Anbox Cloud |
Confirmed
|
Medium
|
Alexis Janon | ||
Bug 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 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.
| description: | updated |
| summary: |
- VHAL capability reported too late for a newly created session + VHAL capability not reported for newly created sessions |
| Changed in anbox-cloud: | |
| assignee: | nobody → Alexis Janon (ajanon) |
| Changed in anbox-cloud: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| milestone: | none → 1.22.1 |
| milestone: | 1.22.1 → 1.22.0 |
| Changed in anbox-cloud: | |
| milestone: | 1.22.0 → none |
To post a comment you must log in.
