-
Notifications
You must be signed in to change notification settings - Fork 63
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
Mandatory to use a RM account to start Screen Share? #103
Comments
[I assume by "Live View" you mean the new "Screen Share" feature] |
Thanks @bordaigorl for the detailed explanation. You are right with your assumption, when I first got my device, I think it was called Live View not Screen Share, so sorry for the misleading wording. What you described is exactly what I wanted to know, and I think my way to go. I will give it a try this evening ;) |
It is working fine, thanks again. |
So am I correct, then, that fallback to the old VNC server solution for 2.9 and above is no longer available and only the ScreenShare client mode will be supported? Or have I just missed something? I can't connect my RM their cloud for data protection reasons, and I also have no interest in turning off Wifi as that's how I get content to the device, which means that the ScreenShare client method is unfortunately a non-starter for me. :( |
@fancypantalons fallbak to VNC server is not an option at the moment. |
Yup, no problem! I wasn't sure, from the thread here, what the situation was. Understanding the VNC server doesn't yet support the latest firmware, obviously there's not much you can do at the moment.
TBH, I hadn't looked too closely at the subscription service model, and now that I see screen sharing is part of the "premium" tier... yeah... I'm afraid you might be right... |
Hi,
due to our company data policy, I can not use the remarkable cloud.
I'm on fw 2.9 and can't start Live View in order to use the original streaming API. Do I need to register my device to a remarkable account to get this option to show up?
The text was updated successfully, but these errors were encountered: