-
-
Notifications
You must be signed in to change notification settings - Fork 209
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
[Feature] "View only" mode #50
Comments
Hi! You simply don't give the input permission when asked for. Does this solve your issue? |
Yes, I just found out that it works anyway, but the sign that shows up is kind of intimidating. I'll see if there's a way I can hide it. Thanks for your work! |
Hi, which sign? |
alright, that could be a config |
Hi Christian. I'm just checking to make sure the ask here would solve what I'm looking for too. Basically, I'm needing an automatic, always running, read-only VNC server for Android devices. And I've issued the command "adb shell cmd appops set net.christianbeier.droidvnc_ng PROJECT_MEDIA allow" as mentioned in order to allow screen recording (current devices are Android 10 and 11). I don't want remote control/input, only remote view. And I'd like it to auto-start on boot. But currently that doesn't work because it still requires me to answer the "Do you want to enable accessibility" pop-up (displayed in an earlier post here) every time it runs. I tried also giving the "SYSTEM_ALERT_WINDOW allow" permission too, and although that does keep me from having to stop/start from the droidVNC-NG admin panel every time, it basically just moved the "Accessibility" question (that I need to answer No to) outside of the manual start from the UI and into its boot process when it first starts as a service. What I'm hoping for is a way to not have to answer that question anymore once I've issued the adb command for "PROJECT_MEDIA allow". Also, icing on the cake would be that even when running as a service, it shouldn't show the "screen recording" icon at the top unless a VNC client is actually connected (as right now it displays it the whole time when it's running in "Start on Boot" mode). |
@bradaker yeah, that issue here is for having a setting: "no remote control" or "view-only-mode" so that the server never needs to ask the user for permission. |
Great, thanks! |
Hi, I would like to know if there is any way I can use the program in "view only" mode, without using the accessibility permissions, as in Android 9 Go they are usually disabled and do not allow me to run the server at startup. Really I like much this app, I want to remotely control a bunch of Android tablets from a PC, but with this problem it gets very complicated.
The text was updated successfully, but these errors were encountered: