Forum Discussion
crossmr
4 years agoProtege
ADB not running logcat properly
Adb does not seem to be behaving properly with my quest 2.
Windows 10, connecting over wifi.
I plugged the quest in with USB, did an adb devices and the quest was listed. I ran:
adb tcpip 5555 and then unplugged the quest
I ran adb connect IPaddress
and it connected. I then attempted to run logcat because I'm trying to get crash information for an app I'm working on. At this point, it starts behaving oddly.
When I run: adb logcat all I get is:
adb server is out of date. killing...
* daemon started successfully *
- waiting for device -
adb server is out of date. killing...
* daemon started successfully *
error: protocol fault (couldn't read status): Invalid argument
over and over. In fact any command I try to run starts with 'adb server is out of date'. Some googling indicates that his might be due to having multiple SDKs on the machine and someone even wrote a tool to detect that (adbfixer) however running that tool doesn't show any conflicting versions. So I'm manually running a search on my machine to see if I can find multiple copies of adb.exe or not. But that's taking quite a bit of time. Any other suggestions?
No RepliesBe the first to reply
Quick Links
- Horizon Developer Support
- Quest User Forums
- Troubleshooting Forum for problems with a game or app
- Quest Support for problems with your device
Other Meta Support
Related Content
- 3 years ago
- 3 years ago
- 3 years ago
- 2 months ago