-
-
Notifications
You must be signed in to change notification settings - Fork 203
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
App frequently asks for screen recording permissions #99
Comments
I don't really know what's going on to be honest. What might happen is that Android kills the Service and restart it, you might find something in the logs. What you might try is:
|
i have extensive experience with the old droid vnc |
is the permmision grant via adb permanent? even if the device restarts? |
That's tracked in #31, please have a look there and subscribe, if you like. |
AFAIK yes. You should try it out. Please report here if it works for you. |
Tentatively closing, feel free to post here if there are news. |
Describe the bug
I use droidVNC on a phone that acts as a smart-home display that shows Home Assistant in kiosk mode. I find myself unable to perform any screen input actions via VNC, although I'm able to connect and see the screen as well as press the "Home button" via VNC client. Once I unlock the screen manually, the android request to grant screen-recording permissions is shown, once I allow it everything works correctly.
To Reproduce
Expected Behavior
The screen-recording permission is persistent
Actual Behavior
The screen-recording permission is revoked and must be "re-granted"
Your environment (please complete the following information):
Additional context
I'm not sure how much time do I have to wait for the permissions to be revoked, but it might be related to the fact that the screen becomes blocked. It usually happens after I update my Home Assistant server and as a consequence the HA client app running on the phone shuts down, thus eventually blocking the screen and revoking permissions for droidVNC
The text was updated successfully, but these errors were encountered: