Skip to content

Latest commit

 

History

History
196 lines (153 loc) · 11.7 KB

README.md

File metadata and controls

196 lines (153 loc) · 11.7 KB
Raw

Oculess

Support Basti (Creator of Oculess, Everything but Audio) on Ko-Fi

Support Threethan (Developed Oculess Background Audio) on Ko-Fi

Important Info

Much of this app's functionality no longer works, and/or requires device owner which may cause issues. Read further for more information and non device-owner alternatives.

Telemetry apps may be disabled using ADB, and similar background audio functionality can be found in this launcher.

IMPORTANT Oculess will no longer allow you to use Spotify, as the Spotify app no longer allows you to log in on Quest. Discord also has some serious issues with buttons appearing off-screen. As an alternative, you can use the web versions of both in LightningLauncher

PLEASE READ COMMON ISSUES BEFORE CREATING A NEW ISSUE ON THIS REPO! If you can't find Oculess in "Unknown Sources", check "Company Managed"

Features

Note The setup process for newer versions is quite involved, but it should not take too long if you follow the guide, and only needs to be performed once. If you're just here for background audio, you want to:

  1. Remove Accounts
  2. Make Oculess a "Device Owner"
  3. Restore Meta Account
  4. Enable Background Audio (Finally!)

Enable Background Audio For All Apps

If you just want Discord, Spotify, etc., LightningLauncher is a much simpler alternative. Video tutorial: https://www.youtube.com/watch?v=aMnHgz2Zo3E (Slightly outdated, so it doesn't include the Restore Meta Account step, but still very helpful)

  1. Follow the steps in the Make Oculess a "Device Owner" section.
  2. Press the "Background Audio for All" button in Oculess, and click okay to open accessibility settings
  3. Select "Oculess" and enable it (or disable it, if you want to turn this feature off)
  4. Play audio through any sideloaded android app, such as Discord or Spotify

Note All Apps will now be allowed to play audio in the background. This functions similarly to the Background Audio experimental setting available to Quest Pro, and formerly available on Quest 2 Music may be paused when a game is quit. If this happens, you will have to reopen the music app and click play. Note that apps might still occasionally be killed. You may need to reopen apps if Oculess is killed.

Remove Accounts

This option is only needed for the Make Oculess a "Device Owner" section.

Note If the the "Remove/Check Accounts" button brings you to an empty settings page try the following ADB command to get to the Settings app and manually navigate to the Accounts section. adb shell "monkey -p com.android.settings -c android.intent.category.LAUNCHER 1"

Note If you cannot access the app launcher after this, restart your device OR: open Oculess using adb shell am start -n com.bos.Oculess/com.bos.Oculess.MainActivity and follow the steps to Restore Accounts

Warning Removing a Meta account will disable some features, depending on system version. If you are unable to perform the restore process listed below, it can only be returned by a Factory Reset

Warning You will permanently delete all non-primary users on the device. You will be unable to enable library sharing unless device owner is disabled.

  1. Open Settings
  2. Click "Accounts"
  3. If there is more than one account: Click the three-dot icon on every account but the primary account and remove it.
  4. Open Oculess
  5. Click on "Remove/Check Accounts" then "OK"
  6. Click on every account (typically only Oculus and Meta), then "REMOVE ACCOUNT" (Your Oculus account should return after like 5 minutes or a restart. Meta account seems unrecoverable.)

Make Oculess a "Device Owner"

WARNING The device may not start up properly if Oculess is set as a device owner and an unlock code is set. (Issue)

This only needs to be done once and after that you will never need to do it again.

  1. Follow the steps in the Remove Accounts section first.

Warning After running this command, you will be unable to uninstall the app until you open it and select "Remove Device Owner" Note After running this command, Oculess may show up under "Company Managed" rather than "Unknown Sources"

  1. Run this command (if you haven't before) adb shell dpm set-device-owner com.bos.oculess/.DevAdminReceiver (if the command fails try to delete apps with accounts like Prime Video, VRChat, AltspaceVR, Whatsapp or similar)
  2. (RECOMMENDED) Follow the steps in Restore Meta Account

Restore Meta Account

Warning This might not work, be warned!

  1. Open Oculess
  2. Click on "Remove/Check Accounts" then "OK" If "Meta" account is there, you do not need to restore it. Stop here!
  3. If "Oculus" account is there: Click "Oculus", then "REMOVE ACCOUNT" Otherwise, continue
  4. Open the Meta Quest app on your phone.
  5. On the phone app, navigate to Menu > Devices. Pair the Quest if prompted, then ensure it is connected. Keep the phone and the quest on, and wait. Wake up your phone if/when it goes to sleep. In a few minutes, both Oculus and Meta accounts should be restored. If the accounts page closes, it probably worked. Open it again using "Remove/Check Accounts" in Oculess to confirm.

Disable Telemetry Apps

Text tutorial: https://blahaj.life/disable-telemetry

Note As of v50, not all apps will be disabled, and doing so may cause issues with WiFi settings. If you encounter issues re-enable telemetry apps, then disable again if/when desired.

Disable/Enable Telemetry Apps using Oculess

Video tutorial: https://www.youtube.com/watch?v=ArXk_hob4RE

  1. Follow the steps in the Make Oculess a "Device Owner" section first.
  2. Click on "TELEMETRY" in the app
  3. Choose "DISABLE TELEMETRY" (or "ENABLE TELEMETRY")

Disable/Enable Telemetry Apps using ADB

Here's an alternative that achieves the same effect with less setup. Disable Telemetry Apps

adb shell pm disable com.oculus.unifiedtelemetry
adb shell pm disable com.oculus.gatekeeperservice
adb shell pm disable com.oculus.notification_proxy
adb shell pm disable com.oculus.bugreporter
adb shell pm disable com.oculus.os.logcollector
adb shell pm disable com.oculus.appsafety

Enable Telemetry Apps

adb shell pm enable com.oculus.unifiedtelemetry
adb shell pm enable com.oculus.gatekeeperservice
adb shell pm enable com.oculus.notification_proxy
adb shell pm enable com.oculus.bugreporter
adb shell pm enable com.oculus.os.logcollector
adb shell pm enable com.oculus.appsafety

Disable Device Companion

Note This fully logs you out and disables most FB/meta stuff on v41 or lower. It can be done safely on newer versions, but doesn't seem to have much of an effect, and may be reverted at random

Text tutorial: https://blahaj.life/quest-account-logout

Video tutorial: https://www.youtube.com/watch?v=vIwUvtxd2-U

  1. (Recommended) Change your system theme to light mode (sideload Settings Shortcut and navigate to Display>Dark Theme and turn it off)
  2. Open Oculess
  3. Click on "DISABLE COMPANION", then "OK"
  4. Choose “Companion Server” from the List
  5. Click “Deactivate this device admin app” (If you're on dark mode, this is the upper of two white-on-white buttons)
  6. (v41 or lower) Restart your device (If you want your account back just restart your Quest and connect with the Oculus Phone App)

Disable Updates

Warning Oculess can no longer disable the updater service, as it can now make your device unusable. If you have a device on v42 or greater, the home menu will not load while the updater is disabled.

Disable: adb shell pm disable --user 0 com.oculus.updater Enable: adb shell pm enable --user 0 com.oculus.updater

Workaround for Multiple Users

If you have Oculess set as device owner, you cannot setup new users normally. However, they can still be added through the hidden android settings.

  1. (Recommended) Change your system theme to dark mode & restart if necessary, otherwise text may be invisible.
  2. Sideload [Settings Shortcut](https://github.com/basti564/SettingsShortcut/releases/
  3. Open android settings using Settings Shortcut
  4. Scroll down and click "System"
  5. Click "Multiple Users"
  6. Click "Add User" (not add guest)
  7. Setup the new user as normal

Screenshot

image

Common Issues

Thoroughly re-read the instructions above, and the solutions below, BEFORE CREATING A GITHUB ISSUE.

Oculess does not show up in "Unknown Sources"!

Once device owner is enabled, Oculess can be found under "Managed Apps" or "Company Managed" instead.

This was noted before you set Oculess as device owner. You might want to look through the README again.

I cannot open the App Launcher after removing accounts

Depending on your Quest OS version, the default app library will not open unless an Oculus account is present, or - on some versions - unless both Oculus and Meta accounts are present.

Follow the instructions to (restore meta account)[https://github.com/basti564/Oculess#restore-meta-account].

You can use adb shell "monkey -p com.bos.oculess -c android.intent.category.LAUNCHER 1" to open Oculess without using the built-in launcher.

Some telemetry apps are still enabled

Some apps cannot be disabled as of v42. You may use the application NetGuard to prevent them from connecting to the internet.

Note: NetGuard is in no way affiliated with Oculess or its developers, please do not ask us for help with NetGuard.

Issues with Guardian/lag/crashes

Sometimes issues will occur, particularly with Guardian losing tracking, when background apps are running on the headset. This is not caused by Oculess, but by the audio-playing apps you're using alongside it. You might want to restart your device.

Oculess's own background service should have minimal performance impact, and can be disabled in the same manner as it was enabled.

If disabling the Oculess accessiblity service fixes your issue, but a restart does not, please do open an issue!

Any issue persists after a factory reset

Oculess cannot possibly modify your device in any way that persists through a factory reset. Note that a factory reset is NOT the same as restarting the device.

Any issue which persists through a factory reset was not caused by Oculess or any other software modification. Your issue is either a defect with your device or, more likely, an issue with a recent system software update from Meta.