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.

Have an issue with com.oculus.unifiedtelemetry. I used my quest without internet access for a long time.
Realized recently that free space almost drained out. According to app manager com.oculus.unifiedtelemetry size near 20gig now. Looks like it has been collecting data all the time, and if have no internet access, it store logs on internal memory. Also according to forums - it's common issue.

I'm at firmware V36 now. After removing all accounts - sucsessfully enabled Ocules and disable all telemetry via your app. That helped to stop free space draining. Now i'm trying to find a way how to clean all telemetry data without factory reset.

Will it be possible for you add call dpm.clearApplicationUserData in addition with dpm.setApplicationHidden?

Thank you!

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)

Hey there, sorry for bothering you but Oculess is a great app and I'm very happy to use it for background music and stuff but I was wondering if it's possible to dim the lights in the oculus environments.

Backthen when oculus tv was good, you could launch your own 3rd party apps on oculus tv and the lights around you would go dark or dim. Ever sense oculus tv updated, they removed the dim feature when launching an app and they remove the ability to launch 3rd party apps and that eliminated controller input support which sucks so I was wondering if it's possible to have a button to dim the lights out like how oculus tv would do it.

If it is possible, that would be great and thanks for hearing me out.

I understand that Oculus is designed for the Quest platform, but if you attempt to disable the companion on Oculus Go, it boots you out of Home and makes it completely unable to operate, giving a three dot loading animation in a black void, and the Oculus Go control. I understand if it's completely out of scope, but if there's any suggestions you would have or troubleshooting you would want me to do, I'm ready to help.

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!

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).

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'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.

https://github.com/basti564/Oculess#make-oculess-a-device-owner

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?

A feature I have really been wanting is custom startup apps (like Discord) so it could show you notifications and have them run in the background, I know it already enables for background audio and stuff (love using Spotify with this) Now all we need is some sort of multimedia overlay (for skipping songs, leaving calls, accepting incomming calls, etc)

After disabling telemetry with Oculess v1.3.1
com.oculus.appsafety is showing as enabled. How can I turn it off?

What is the chance I will be banned for this?

i try to use the adb install -r oculess-1.3.5.apk command after i install the 1.3.5 apk and it says "Error: Command failed: "C:\Users\Alex\AppData\Roaming\SideQuest\platform-tools\adb.exe" -s 1WMHH832AR1137 install -r oculess-1.3.5.apk adb: failed to stat oculess-1.3.5.apk: No such file or directory" i cant seem to see why

I recently purchased a new Quest 2 and have Oculess installed, but when I attempt to disable the device owner, the white screen appears. I see in the instructions to enable light mode, but this does not appear to be possible - the option does not exist in experimental settings on my device (my Quest updated to v37 during setup.)

Is there a workaround/ADB command/etc. that can be run to change the device owner instead?

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

According to https://stackoverflow.com/questions/49128293/how-to-remove-set-device-owner-in-android-dpm & https://snow.dog/blog/kiosk-mode-android. if <application> includes the property android:testOnly="true", then the application's device administration can be removed using ADB via adb shell dpm remove-active-admin [package]/[adminReceiver] without factory reset.

Normally, recommendations are to remove this property for production deployment, as typical device administrator apps are used for MDM, and as such should not be user-removable. However, for Oculess' purposes, this is rather the opposite.

In theory, this would mean, if this property were set in the Oculess package manifest, users would no longer require a factory reset to remove device ownership. Instead, adb shell dpm remove-active-admin com.bos.oculess/.DevAdminReceiver would be enough to remove ownership of oculess, as easy as it was to add it.

e.g. as part of AndroidManifest.xml:

...

<application
        android:allowBackup="true"
        android:banner="@mipmap/ic_banner"
        android:icon="@mipmap/ic_launcher"
        android:label="@string/app_name"
        android:roundIcon="@mipmap/ic_launcher_round"
        android:supportsRtl="true"
        android:theme="@style/Theme.Oculess"
        android:testOnly="true"> <!-- Note added property on this line -->

...

Would this be something worth testing and confirming? If so, it saves users the headache of having to reset.

should it be disabled?
What does it do?

For some reason the disable button enables telemetry and the enable button disables it.

subj

Since v38 march 2022 update I can no longer set light theme the shortcut for settings no longer works

Never used a Facebook Accout only an Oculus Dev account.

Cant disable telemtry. Error: "The device owner was not set."

Hi i recently got oculess but there was a problem with all the options being grayed out. after i deleated oculess i tried to reinstall it but when i put it in side quest it says its compleat but its not on my oculus

Hello Basti564,
I don't know if it's possible but it would be nice to disable the proximity sensor.
Thank you and amazing job on the app!

Question - is the inbuilt casting to TV still not working after I remove Facebook account? Don't have the device yet on my hands
Is the only alternative screencasting by using sidequest?
Is disabling telemetry (without removing Facebook account) enough to stay on the safer side and not getting spotted by facebook (I know that facebook hasn't banned anyone yet, but better safe than sorry)

All the guides I have found have said that my account should be removed after reset. However, upon following the instructions, I am still logged in, and no matter how many times I've repeated disabling companion and resetting it's just not working. I don't have many details because I don't know what is causing the problem, and the only details I can offer at the current time that might be relevant are the following:
a) Oculess is the device owner. b) All account features are retained through the reset. c) Software Version: 41.0.0.124.268.379035663 d) Runtime Version: 41.0.0.124.307379035701 e) Oculess Version: 1.3.5 f) Has been tested with both WiFi off & on, as well as before and after the cache was cleared. f) This is on a Quest 1.

Edit: I've fixed this in a way. I boot with wifi off and use TrackerControl (From F-Droid) to block the system using WiFi. I can still use wifi on browsers (Have only tried with DuckDuckGo) and mostly use the internet (Works with Webtoon, not with QuestCraft) but I don't know if this disables the piracy switch and I can't use another tracking blocker, a VPN, or a DNS (Anything that requires the VPN capability) because TrackerControl takes that spot. I can also use my apps from the Store, so I'm not sure if that introduces any complications.

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.

After disabling telemetry, adb shell pm list packages -d lists any package but com.oculus.appsafety. adb shell pm path com.oculus.appsafety lists appsafety too but that goes for any of the packages.

If Oculess is set as a device owner, would it be possible to install custom certificates with the app,
or is there something blocking it or making it useless I don't know about?

e.g. with https://developer.android.com/reference/android/app/admin/DevicePolicyManager#installCaCert(android.content.ComponentName,%20byte[]) or installKeyPair

If it works it would be great to have that feature in Oculess!

I'm not sure if this expected behavior, but after disabling "Companion Server" under "Device admin apps" and restarting my Oculus Quest 2, "Companion Server" is automatically re-enabled.

Telemetry and updates remain disabled on restart, and Oculess remains a "Device Owner".

Model: Quest 2
Android version: Android 10
Build number: user-28467500769800000

i have installed the apk, when i run the adb command i get the following error:

➜ ~ adb shell dpm set-device-owner com.bos.oculess/.DevAdminReceiver
error: insufficient permissions for device: user in plugdev group; are your udev rules wrong?
See [http://developer.android.com/tools/device.html] for more information

The title should be self explanatory, there's absolutely nothing but the sync toggle when trying to remove my accounts

I disabled telemetry using Oculess and can't add another Oculus account on my Quest 2, neither using the account settings on the Quest, nor using the account manager in Oculus Developer Hub. In another issue @basti564 mentioned multi-account might cause problems. Is there a way to disable telemetry and still get multi-account working?

Hi just wondering what the right step is to update Oculess after a new Oculess version comes out?

can you use oculess just for the features it has and not have to remove my oculess account

I have side loaded the apk and tried to disable companion by following the instructions to the letter. When I run the app and choose Disable Companion and OK. It then shows a windows titled Device Admin Apps with Companion Server and Oculess listed with switches next to them. Companion server is running so the switch is blue. If I click on it as described in the instructions I get a white window with companion written in the top left corner and the oculus logo (Nothing Else). As per the instructions I rebooted the console and guess what... when I run the app again companion server is still running. THIS DOES NOT WORK. Please update with new instructions or inform end users that it no longer works. Perhaps FB rushed a firmware update that killed this process but that seems unlikely as many other users are able to get this working.

Another issue. ADB command for disabling Updates and Telemetry are not working either. I successfully removed all accounts using the app then connected to sidequest and sent the ADB command "adb shell dpm set-device-owner com.bos.oculess/.DevAdminReceiver" as per instructions and got the followinf error message:-

Error: Command failed: "C:\Users\Sion\AppData\Roaming\SideQuest\platform-tools\adb.exe" -s 1WMHHB61UJ1385 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)

Is there any way to get this working? Maybe update the github if this is indeed broken to save users the trouble of finding out the hard way.

I cannot choose anything beneath deleteing accounts or enabling services, most important to me is enabling background audio. See screenshot for more:

Sorry if this was solved/mentioned somewhere else already.

Thanks so much, basti564 - I've been following your Oculus Quest 2 work for a while and st0ked that I got Oculess running... So far I removed my accounts, ran adb command and enabled background music.
I got my Spotify music (and other apps sound) playing thru my game sessions/other apps. What I want to do is play Spotify music so that other PLAYERS can hear. (PokerStarsVR) ... I know this capability is doable using PCVR, but I was hoping that background Spotify would bleed thru... it does not.
Is there any wizardry we could work for that? Specifically I want background Spofify music to be heard by all users at my PokerStars VR table. Any ideas?

Thank you so much for Oculess - I'm researching turning off telemetry and POSSIBLY NULLing my FB account - can I turn off telemetry and still have my FB accounts active safely? Very much appreciate this project and thank you kindly, r0ckstar!!!!!

pAULIE42o
. . . . . . . . . . .
/s

hi dear,
does exists any method to start specific apk [i mean app] after boot on quest 2 without using launcher?

thanks a lot.

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)

Right away - THANKS FOR MAKING OCULESS! I've been wanting something like this for a long time.

Right, to the bug now. I found that initially after installing Oculess my custom home environment worked fine (just a black void). Since then it's gone away and reverted back to the default Oculus home environment. I've also noted that the menu which allows you to select your home environment appears not to work anymore.

There's a community focused on developing these custom home environments here:
https://discord.gg/fY2aD9B

I don't think many of them are using Oculess yet - I'd like to help close this bug but I'm not sure where to start.

i just get this when entering the command

usage: dpm [subcommand] [options]
usage: dpm set-active-admin [ --user <USER_ID> | current ]
usage: dpm set-device-owner [ --user <USER_ID> | current EXPERIMENTAL ] [ --name ]
usage: dpm set-profile-owner [ --user <USER_ID> | current ] [ --name ]
usage: dpm remove-active-admin [ --user <USER_ID> | current ] [ --name ]

dpm set-active-admin: Sets the given component as active admin for an existing user.

dpm set-device-owner: Sets the given component as active admin, and its package as device owner.

dpm set-profile-owner: Sets the given component as active admin and profile owner for an existing user.

dpm remove-active-admin: Disables an active admin, the admin must have declared android:testOnly in the application in its manifest. This will also remove device and profile owners.

dpm clear-freeze-period-record: clears framework-maintained record of past freeze periods that the device went through. For use during feature development to prevent triggering restriction on setting freeze periods.

dpm force-network-logs: makes all network logs available to the DPC and triggers DeviceAdminReceiver.onNetworkLogsAvailable() if needed.

dpm force-security-logs: makes all security logs available to the DPC and triggers DeviceAdminReceiver.onSecurityLogsAvailable() if needed.
usage: dpm grant-profile-owner-device-ids-access: [ --user <USER_ID> | current ]

Just what it says on the tin: Can I disable just the telemetry but still have the store and oculus games function correctly.

The option to change themes to light mode no longer exists. I've checked everywhere in settings. It's not in experimental or personalization.
Perhaps add support for dark mode or a guide for us to disable the companion blind?

I removed the accounts and ran the command but enabling background audio is grayed out on default