#Rollback to ALVR 20.11.1 on Quest 2?

48 messages · Page 1 of 1 (latest)

wispy osprey
#

Moments ago, my Quest Oculus 2 decided to upgrade ALVR from 20.11 to 20.12. My Debian 12.8 box is still running ALVR 20.11.1. Seems like ALVR 20.12 on a Quest Oculus 2 can't handshake nor connect to a Linux box running ALVR 20.11.1. I can't upgrade my Debian box to the libc 2.39 (that's required if I want to upgrade my ALVR on my Linux box) because only libc 2.36 is release for Debian 12. No idea when libc 2.39 for Debian 12 will be released. (I don't want to manually compile and install libc - nightmare).

Easiest solution right now would be to roll back my version of ALVR on my Oculus 2. I need to roll back to ALVR 20.11.1 on my Oculus 2. How do I do that? Can't find anything useful in internet search.

Thanks,

Pete

coarse imp
#

sure, you can use the launcher. download the version you prefer, ignore the server, click on Install APK and it will install it to your headset via cable

#

another thing. you can use v20.12.0 client with v20.11.1 server

wispy osprey
#

Here's the error I get when I attempt to install the APK ver 20.11.1 from the launcher: "ADB install failed: adb: no devices/emulators found" The Oculus is connected to the computer, and the computer can access the file system on the Oculus, so I know it's not a USB device access issue.

coarse imp
#

do you have dev mode enabled?

wispy osprey
#

what's that, and where is it?

coarse imp
#

you can enable it from the oculus app on the phone

#

but you need to create a developer account

wispy osprey
#

Errors I'm seeing on the Oculus and Linux box.

com.oculus.vrshell-20250115-200400.jpg Screenshot_20250115_203633.png
coarse imp
#

You did not roll back the client

#

And yeah the error is our fault, we should make a patch fix

fair portal
#

I have the same issue on quest 2 but windows 10 I can’t do handshake

#

Am going to try do the roll back thing

uncut raptor
#

same issue for me, just going to roll back

uncut raptor
#

cant roll back, apk doesn't install because of a missing adb dll. I'll troubleshoot tomorrow

wispy osprey
wispy osprey
dense igloo
#

uninstall via adb

#

not by clickig in headset

wispy osprey
#

The work-around for this issue is implemented and holding together. I couldn't upgrade my Debian Bookworm box to ALVR 20.12 because Debian's most recent libc is version 2.36, and I need 2.39 for ALVR 20.12. Considered dumping Debian for Ubuntu 24.04.1 because Ubuntu uses libc 2.39, but the thought of starting over from scratch was just too depressing. Decided to try to downgrade ALVR on the Oculus 2 to match the ALVR version on my Debian 12.8 box (ALVR 20.11.1). I was able to create a developer account on the Oculus website and enable developer mode on the Oculus 2. That allowed me to use the ALVR Launcher to sideload the older version of ALVR 20.11.1 with the "Install APK" button. It works!!!!! I just wish that I started with Ubuntu instead of Debian.

dense igloo
#

use a distro that works - so not ubuntu or debian, pretty simple

#

ubuntu 24 still ancient and u shouldnt be using it

#

or u could use flatpak and not have any of these problems

thin mountain
uncut raptor
#

Got it to work also. Deleted everything ( previous adb, alvr on both pc and quest 2), reinstalled steam vr, disabled dev mode on quest and quest app, restarted those and re-enabled dev mode. Restarted both pc and quest, installed ALVR pc, used the apk install on the launcher, and 2.12 works.

#

Plugged in the headset according to the github installation instructions

wispy osprey
# dense igloo or u could use flatpak and not have any of these problems

I didn't even know that flatpak was a thing until you mentioned it. Had to look it up. That looks cool. Quick question on it since I really don't know anything about flatpak other than a few videos I just watched..... If you are in a situation where you have multiple apps working in series to give you a product like: ALVR to SteamVR to X-Plane (or any other app), do all of those elements have to run in the flatpak world, or can say just ALVR run on flatpak, and the other 2 run directly via the OS?

dense igloo
#

but seems to work fine, this is what i use

#

everything in this case is running inside the same "container" as steam - so it all works

#

steam runs its own container no matter what so there is a lot of stuff going on

wispy osprey
#

Groovy. I'll check it out. Thanks. 🙂

dense igloo
#

when you try to mix flatpak with incompatible environments then you will have problem (this can mean system env or other flatpaks)

#

having a consistent environment is the entire point and problem it tries to fix

#

sometimes you can get away with it - because the steam flatpak environment is mostly the same as your arch host anyway - and the communication is done via direct memory or something (e.g. you can run wlx-overlay-s as normal system file, and it will work with steamvr flatpak)

fair portal
fair portal
#

Black screen now

reef magnetBOT
fair portal
#

Guys I copy and paste the command line and the black screen still there

reef magnetBOT
dense igloo
#

show evidence - post all your custom options here

fair portal
#

In presets I put 60hz for not have performance issues encoder preset I have it on speed now on video I have image corruption fix on preferred codec HEVC foveated encoding on Force enable on Force software decoder on

fair portal
dense igloo
#

post your settings, not videos

#

artifacing is because you have settings too high, or network not good enough

#

statistics graph will show

fair portal
#

I do I know how dude

#

How I post my settings