There are also various references to actions like “”, “_ASSISTANT” and “_ASSISTANT”, but I found no use in them 🙁 Looking at LogCat (the logger of Android), you can spot that the problem is that the current user is not authorized to use the vocal assistant.Ġ2-03 17:22:08.496 30845-30845/? I/VrDesktopPanelApp: Target: LaunchConfiguration from uid 1000 on display 50Ġ2-03 17:22:55.426 30826-30826/? D/AssistantService: OnCreateĠ2-03 17:22:55.435 30826-30826/? E/AssistantService: Assistant is not enabled for this user on this device This is what you obtain launching the assistant test app. If you run that activity (using the command “adb shell am start -n /.testui.AssistantVRShellActivity”), you see in your Quest a window about the Oculus Assistant popping up, with just a rotating waiting gizmo. This is the sign of a future feature that Facebook is going to introduce: according to rumors, Oculus is working on a vocal assistant for your Quest, that should help you in launching your apps without using controllers, plus other stuff that we still don’t know. I got the list of packages installed by typing “adb shell dumpsys package r”, obtaining a super long list of info.Īs previously spotted by Upload VR, when you go through the list of the intents available on the device, you can see that there is the package “/.testui.AssistantVRShellActivity” available. It is curious that even after the launch, those devices keep many references to their previous internal names. Oculus Go was codenamed “Pacific”, instead. Monterey is the codename of the Quest, and in fact, you can find its name everywhere when pinging the parameters and infos of the device through “adb shell getprop”.
This is good for cybersecurity and privacy, but bad for me: no MR on Quest this time 🙁 Codename Monterey They are probably a tracking device, a guardian system as a whole. So, for the Quest OS, those cameras are not really cameras, in the Android sense of the term.
I asked the OS what are the features of the device, and there is no. I’ve verified it by attaching the Quest to my PC and writing “adb shell pm list features” in the command line. There’s no intent associated with taking a picture, there’s no media service launched, and there’s not even “camera” listed as a hardware capability of the device.
I had the idea of accessing the cameras via standard Android interface (so, without going through the Oculus SDK, but using Android tools), but it seems that Oculus has been very paranoid regarding cameras, and in fact, t hey aren’t accessible in any way. I remember Eduardo Siman telling that if someone could unlock that feature, that could be me (I’m very flattered by his esteem), so I tried not disappoint him and find a way to get access to the cameras.
Unluckily, this is not possible on the Quest, because the SDK doesn’t give you access to the cameras.
0 kommentar(er)
