You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently porting a Unity 2022 OpenVR game to OpenXR so I can do an Android Arm64 build for the Frame.
For an unknown reason, the apk I've built fails to launch on Frame (Steam says 'running' but no display ever opens). I installed the Utilities package hoping the Lepton Validator would highlight something, but although it picked up one issue (android SDK level) I still am unable to launch the apk.
So I guess my questions are:
Is there an example AndroidManifest which I can reference? My current manifest has inherited a lot from the Quest build, but I have no idea how many of these are required or even used by Lepton. The steamworks docs don't really mention this at all so a reference manifest would be very handy.
Is it possible to get one of the samples (eg. the refresh rate sample) as a complete project, rather than just injecting into an existing one?
No, I ended up using Proton/FEX to run our Win64 build on Frame, rather than Android/Lepton. As far as I know my two original points are still valid - there's no documentation on what Steam Frame cares about for an Android Manifest, and in lieu of any explicit documentation I think a standalone sample would be a good idea.
Activity
carrotstien commentedon Jul 16, 2026
Are you still having a problem? I found some things which cause exactly what you are saying but not others.
For example, it seems (in a barebones project), if you break one of these requirements while the feature is enabled, you get no display
keithbradner commentedon Sep 22, 2026
Hello, have you resolved this issue?
OrangyTang commentedon Sep 28, 2026
No, I ended up using Proton/FEX to run our Win64 build on Frame, rather than Android/Lepton. As far as I know my two original points are still valid - there's no documentation on what Steam Frame cares about for an Android Manifest, and in lieu of any explicit documentation I think a standalone sample would be a good idea.