I am currently developing a Unity-based launcher application using the Spaces SDK on a Qualcomm XR2-Gen 1 All-In-One device, which is an AR glasses(Android 12) device we have designed and built in-house. Naturally, the launcher app is configured with the system UID and signed with the platform key.
We have observed that launching the Android Settings app from our launcher—which utilizes a virtual display provided by the Spaces SDK—results in a black screen, even though other Android native 2D apps (such as Camera and Calendar) render correctly. The Settings app is also a native 2D app, so this behavior appears inconsistent.
Based on log analysis, it appears that the Settings app fails to render due to surface or display attachment issues. We would like to inquire about the following:
Q1. Are system apps like com.android.settings officially supported on the virtual display created by the Spaces SDK?
Q2. Does the SDK provide any fallback or workaround when a system app fails to attach to the virtual display?
Q3. To what extent does the Spaces SDK support SystemUI components on the virtual display?
Additionally, if there are any required modifications on the Android BSP side to support such use cases, please let us know.
Hglee
Dear Spaces Team,
I am currently developing a Unity-based launcher application using the Spaces SDK on a Qualcomm XR2-Gen 1 All-In-One device, which is an AR glasses(Android 12) device we have designed and built in-house. Naturally, the launcher app is configured with the system UID and signed with the platform key.
We have observed that launching the Android Settings app from our launcher—which utilizes a virtual display provided by the Spaces SDK—results in a black screen, even though other Android native 2D apps (such as Camera and Calendar) render correctly. The Settings app is also a native 2D app, so this behavior appears inconsistent.
Based on log analysis, it appears that the Settings app fails to render due to surface or display attachment issues. We would like to inquire about the following:
Q1. Are system apps like com.android.settings officially supported on the virtual display created by the Spaces SDK?
Q2. Does the SDK provide any fallback or workaround when a system app fails to attach to the virtual display?
Q3. To what extent does the Spaces SDK support SystemUI components on the virtual display?
Additionally, if there are any required modifications on the Android BSP side to support such use cases, please let us know.
Best Regards,