2 ms·
There is one project called SideQuest that--if you enable developer options on your Go or Quest, which requires a developer account with Oculus--uses Android si
by moron4hire 6y ago
There is one project called SideQuest that--if you enable developer options on your Go or Quest, which requires a developer account with Oculus--uses Android side-loading from a PC to get apps onto the Quest. When you side-load an app on the Go, you also have to have a key file embedded in it that was generated from the device's own serial number, so SideQuest has to have you generate an OSIG for your device, upload it to your profile, then hack your OSIG into any APKs you download from their store. Quest doesn't have the OSIG requirement, but you still need the developer account to enable developer options.
And you're still stuck using Oculus' APIs. There are no open source APIs for accessing the device sensor data or rendering. Regular Android apps (minus Google Play Services) can run on the devices as tiny windows, and then you can get some super-hacky input as touch events on the app view, but it's really not usable. I think it even forces software rendering, because I've seen some really bad performance out of it (I found out about it after not having an app configured incorrectly before uploading it on my own for my own development). It's basically there as a fallback for Android's default Settings view, which you use to configure the developer settings like enabling USB debugging.