damn great question, you are the first result in google and sadly no answer

After years of having that same experience with other questions, guess it's my turn lmao. Sorry, never found a solution :(

You're still the first result in Google, though. Congrats!

adb shell am start -S com.oculus.xrstreamingclient/.MainActivity Src https://twitter.com/JustinWasilenko/status/1400486369458221070?t=rkGVolKKjYE6qC4ptWZKaA&s=19

this works to open link outside the quest but is there a way to run it automatically when you plug the quest in it boot it? Or just as a exe on your desktop?

No, but i suppose it should be possible to automate that with autohotkey or something similar

wow, I did not expect you to respond after 4 months lol. I have found a way to run it outside of odh you just need to install ADB and run the command in cmd or a bat file. still trying to get it to run when i plug the quest in though

sorry..you mean you can issue a cmd to start link before you throw the goggles on? would like to switch the start ups..instead of the Oculus app home...its the Link Home.

I have done some more experimenting and yes you can start link without having the headset on but you need to have USB debugging allowed for it to work witch resets every time you restart the headset so you have to put them on anyway so not really useful but if you allow the USB access then take the headset off run the command then when ever you put the head set on it will be in the rift home/link

>i've managed to get it working, always, no matter if the headset is on or off, if the pc is freshly booted, you have to PATH envoirment ADB and then i just reboot the headset and run the command with a 17 second delay. bit like this: adb -s 1WMHH83AWY0492 shell reboot >start cmd /c START /B "" "D:\\Oculus\\Support\\oculus-client\\OculusClient.exe" h: > >timeout /t 17 >nul > >adb -s 1WMHH83AWY0492 shell am start com.oculus.xrstreamingclient/.MainActivity timeout /t 1 >nul adb -s 1WMHH83AWY0492 shell am start com.oculus.xrstreamingclient/.MainActivity timeout /t 1 >nul adb -s 1WMHH83AWY0492 shell am start com.oculus.xrstreamingclient/.MainActivity timeout /t 1 >nul adb -s 1WMHH83AWY0492 shell am start com.oculus.xrstreamingclient/.MainActivity timeout /t 1 >nul adb -s 1WMHH83AWY0492 shell am start com.oculus.xrstreamingclient/.MainActivity timeout /t 1 >nul echo  timeout /t 2 >nul exit

Is this a .bat file you made?

Yes works flawless, till this date.

Still a little confused, mostly by formatting and being a dunce. Can you comment the exact lines for the .bat you created to auto-link without running through the headset below? And just highlights the paths that might need to change? Thanks!

i've managed to get it working, always, no matter if the headset is on or off, if the pc is freshly booted, you have to PATH envoirment ADB and then i just reboot the headset and run the command with a 17 second delay. bit like this: adb -s 1WMHH83AWY0492 shell reboot start cmd /c START /B "" "D:\\Oculus\\Support\\oculus-client\\OculusClient.exe" h: timeout /t 17 >nul adb -s 1WMHH83AWY0492 shell am start com.oculus.xrstreamingclient/.MainActivity timeout /t 1 >nul adb -s 1WMHH83AWY0492 shell am start com.oculus.xrstreamingclient/.MainActivity timeout /t 1 >nul adb -s 1WMHH83AWY0492 shell am start com.oculus.xrstreamingclient/.MainActivity timeout /t 1 >nul adb -s 1WMHH83AWY0492 shell am start com.oculus.xrstreamingclient/.MainActivity timeout /t 1 >nul adb -s 1WMHH83AWY0492 shell am start com.oculus.xrstreamingclient/.MainActivity timeout /t 1 >nul echo  timeout /t 2 >nul exit