After manually sideloading update v28, the command adb shell dpm set-device-owner com.bos.oculess/.DevAdminReceiver returns the following error log. No multi accounts being used, it worked fine in v27.

Error: Command failed: "C:\Users\gulop\AppData\Roaming\SideQuest\platform-tools\adb.exe" -s ********* shell dpm set-device-owner com.bos.oculess/.DevAdminReceiver java.lang.IllegalStateException: Not allowed to set the device owner because there are already some accounts on the device at android.os.Parcel.createException(Parcel.java:2079) at android.os.Parcel.readException(Parcel.java:2039) at android.os.Parcel.readException(Parcel.java:1987) at android.app.admin.IDevicePolicyManager$Stub$Proxy.setDeviceOwner(IDevicePolicyManager.java:8392) at com.android.commands.dpm.Dpm.runSetDeviceOwner(Dpm.java:203) at com.android.commands.dpm.Dpm.onRun(Dpm.java:115) at com.android.internal.os.BaseCommand.run(BaseCommand.java:65) at com.android.internal.os.BaseCommand.run(BaseCommand.java:49) at com.android.commands.dpm.Dpm.main(Dpm.java:41) at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method) at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:338) Caused by: android.os.RemoteException: Remote stack trace: at com.android.server.devicepolicy.DevicePolicyManagerService.enforceCanSetDeviceOwnerLocked(DevicePolicyManagerService.java:8652) at com.android.server.devicepolicy.DevicePolicyManagerService.setDeviceOwner(DevicePolicyManagerService.java:7821) at android.app.admin.IDevicePolicyManager$Stub.onTransact(IDevicePolicyManager.java:3270) at android.os.Binder.execTransactInternal(Binder.java:1021) at android.os.Binder.execTransact(Binder.java:994)

Sometimes its useful to disable the guardian if you want to leave your playspace without triggering passthrough. For example if you play in an indefinite playspace or playspace which is bigger than the Quest allows. (Or when your bed is behind the Guardian and you just want to lay down in VR) Normally this setting can be changed in the developer settings (Settings > System > Developer).

However, when disabling oculus companion you wont fine the developer settings anymore to toggle the guardian. Right now its only possible with SideQuest USB/wireless ADB settings when oculus companion is disabled. Would be nice to see this somehow being added in the app (without loosing focus from the active app would be optimal).

I'm just wondering if applying this will impact ability to go wireless?

Not a deal breaker, but it would be nice to know. I would just check but I don't have the headset just yet.

Hi, first of all: thanks for the great utility! Just wanted to point out that the browser does actually still work, it's just the shortcut in the home menu that doesn't. When you exit ALVR, it opens the dashboard in the browser, which works just fine and actually can be used as a workaround. I think it should be possible to create a new shortcut, maybe just a stub apk? Further, this could also mean that TV still works, I haven't tried it yet, but it'd be nice for streaming VR movies I guess.

Edit: I think I found the relevant line

I use a Quest 1. I managed to disable the companion server without light mode(took me a while lol). But now I am stuck again. I cannot remove any accounts. When I click the REMOVE ACCOUNTS option in oculess it just opens up my system display settings. After watching the video tutorial I saw that its supposed to pop up an accounts page, but I don't get that. Is there anything I'm doing wrong?

Hi & thx for this great app!

Just wanted to "free" my Quest 1 from Facebook, but I cannot disable the Companion Server Admin. When clicking the toggle, I only get a white "app screen" without any text. (unlike https://youtu.be/aSokYzpB1D8?t=280) .. do you have any ideas on that? I rebooted the Quest, but nothing changed.

Not an issue ... but a question.

First, thanks for this awesome tool!

Is there a way to verify it's working by, say, checking DNS logs? I still see a lot of traffic to graph.oculus.com, graph.facebook.com, etc ... but that might be unrelated to telemetry.

Thanks

Whenever I try to disable the Oculus Companion Server to remove Facebook/Meta server access, the screen turns white and displays the logo in the corner. Eventually, after randomly clicking the screen long enough, I'm able to locate the button but with extreme difficulty.

Hi,

First of all, thank you for this! Telemetry has been my biggest issue and concern with getting a Quest, and this solves my problem. I really appreciate the time and effort that's been put into this!

Would it be possible to get some sort of feedback on whether or not disabling telemetry was a success, or if telemetry is currently disabled?

From what I understand in the code, you're taking certain services that Facebook uses for telemetry and hiding them (which renders them unusable until unhidden). Using DevicePolicyManager#isApplicationHidden, we could query which of the services are currently hidden and display a status to the user:

• Disabled (all services hidden)
• Partially Disabled (some services hidden)
• Enabled (no services hidden)

Adding this simple addition would make Oculess a lot more user-friendly, and give users confidence that telemetry is actually disabled. I'm no expert on android or Kotlin, but if you think this is something worth having but aren't willing to devote time to it, I could take a crack at it myself. Just let me know!

Thank you for your time, and thanks again for making this awesome app!

I am running v30, with the Air Link enabling package sideloaded to make sure it's not just not rolled out to me yet. This should probably be mentioned in the guide. I can however connect manually with AirLinkConnector.

the adb comand keeps failing -even after removing all fb acounts .the adb comand keeps failing

here are my logs from sidequest

Error: Command failed: "C:\Users\ilco\AppData\Roaming\SideQuest\platform-tools\adb.exe" -s 1WMHH865E71212 shell dpm set-device-owner com.bos.oculess/.DevAdminReceiver java.lang.IllegalStateException: Not allowed to set the device owner because there are already some accounts on the device at android.os.Parcel.createException(Parcel.java:2046) at android.os.Parcel.readException(Parcel.java:2006) at android.os.Parcel.readException(Parcel.java:1954) at android.app.admin.IDevicePolicyManager$Stub$Proxy.setDeviceOwner(IDevicePolicyManager.java:8392) at com.android.commands.dpm.Dpm.runSetDeviceOwner(Dpm.java:203) at com.android.commands.dpm.Dpm.onRun(Dpm.java:115) at com.android.internal.os.BaseCommand.run(BaseCommand.java:65) at com.android.internal.os.BaseCommand.run(BaseCommand.java:49) at com.android.commands.dpm.Dpm.main(Dpm.java:41) at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method) at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:338) Caused by: android.os.RemoteException: Remote stack trace: at com.android.server.devicepolicy.DevicePolicyManagerService.enforceCanSetDeviceOwnerLocked(DevicePolicyManagerService.java:8653) at com.android.server.devicepolicy.DevicePolicyManagerService.setDeviceOwner(DevicePolicyManagerService.java:7822) at android.app.admin.IDevicePolicyManager$Stub.onTransact(IDevicePolicyManager.java:3270) at android.os.Binder.execTransactInternal(Binder.java:1021) at android.os.Binder.execTransact(Binder.java:994)

Whenever I close the Oculess app it resets the Enable Background Audio feature. I had this working yesterday, but today when I try to run amazon music and any full oculus store app it closes oculess and amazon music while the application is booting up. I tried re-removing the accounts and re-running the command to Make Oculess a "Device Owner" but it returned an error and didn't help.

Is there a way to run virtual desktop/alvr on Oculess without installing the oculus companion app on my PC? I'd like to play SteamVR games without using the oculus companion program if possible. How do I do this?

There seems to be a feature that has the Quest 2 disable the ability to turn up the volume without confirming it in the Quest app.

The problem is that I've removed the account login on my quest and can now no longer turn up the volume. It would be great to disable this "feature" if at all possible. (even with ADB)

Quick question, which system version is supported? I've been using v43 and it didn't work, I removed all accounts, did all steps and nothing changed in the app, Everything was still greyed out. (I tried the steps many times and rebooted a few times too.)

Discord screenshare is no longer working as of Quest Firmware Update v44, same with skype screenshare, and I'm assuming every other sideloaded application that tries to capture the screen.

See https://forums.oculusvr.com/t5/Quest-Development/Downgrading-firmware-for-device-management-use/td-p/992199