-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not detecting USB for pairing #1
Comments
Just checking, are you running Unfortunately, I'm unable to test this anymore as I'm on iOS 17 and that's not supported by JitStreamer. Apple has changed the whole process for the latest iOS, and I'm no longer using JIT. 😕 But some ideas I have:
Sorry I can't be more helpful. I'm going to archive this repo soon. |
What I ended up doing was copying the binaries to the host and they worked there. My next issue was with the shortcut seemingly not working anymore, I got a code but after typing the code there was a server error, reading some issues on the original repo reveals something about http and https to original JitStreamer site, which is now completely dead. I think JitStreamer might just be done for, I tried SideStore instead which seems to work great, until it unsigns itself randomly :(. Thanks for the help anyway, maybe once I have some more time I can try and figure out the server error thing. |
Alright, there's an update to this. It works when I use jitterbugpair file instead of trying to use the shortcut. That might be my solution, thanks again. |
Ahh I forgot to mention in the instructions you have to edit the JitSteamer iOS shortcut to point to the IP address or hostname of your JitStreamer instance (and not the public instance that’s no longer available). That’s probably why you couldn’t pair. |
Hey, I'm running iOS 16.3.1 and I was trying to make your docker container work however I am having trouble.
During pairing I'm getting the message
I have usbmuxd installed and running, any idea how I can get it working?
Using Debian 12
The text was updated successfully, but these errors were encountered: