Skip to content
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

Android Screen Record Stops after hours (service killed by system) #6192

Open
vavolkova opened this issue Oct 25, 2023 · 26 comments
Open

Android Screen Record Stops after hours (service killed by system) #6192

vavolkova opened this issue Oct 25, 2023 · 26 comments
Labels
💎 Bounty Fund help wanted Extra attention is needed question Further information is requested

Comments

@vavolkova
Copy link

vavolkova commented Oct 25, 2023

Hi guys,

Not sure if that has been discussed before, but I didn't find anything under this topic. I was looking to set unattended access on few Android devices (Android 11). I have set Pro account with Linux server and it all worked properly until I noticed that after 2-3 hours the service stops (Screen Record automatically turns off) and I need to manually turn it on and continue using it.

Is there a solution for that?

Upvote & Fund

  • We're using Polar.sh so you can upvote and help fund this issue.
  • We receive the funding once the issue is completed & confirmed by you.
  • Thank you in advance for helping prioritize & fund our backlog.
Fund with Polar
@21pages
Copy link
Collaborator

21pages commented Oct 25, 2023

During the 2-3 hours, was the Android screen on or off?

@vavolkova
Copy link
Author

Screen was off in 10-15 minutes, but it stopped working in 2-3 hours

@21pages
Copy link
Collaborator

21pages commented Oct 25, 2023

Thanks, I'll test with screen off.

@vavolkova
Copy link
Author

Thank you, appreciated

@21pages
Copy link
Collaborator

21pages commented Oct 26, 2023

I ran a test on my phone for about 3 hours. The connection was Remote desktop is offline, the service button still showed as on, probably because Android stopped it. We talked about it and would like to improve this, but need to find a good solution and it will take some time.

@vavolkova
Copy link
Author

Thanks, can you, please, keep me posted?

@21pages
Copy link
Collaborator

21pages commented Oct 26, 2023

Preferably close this and post a link on rustdesk repo.

@rustdesk rustdesk transferred this issue from rustdesk/rustdesk-server-pro Oct 27, 2023
@rustdesk rustdesk changed the title Android Screen Record Stops Android Screen Record Stops after hours Oct 27, 2023
@rustdesk
Copy link
Owner

rustdesk commented Oct 27, 2023

Frankly, we still have no good solution, also this is not our high priority. Not sure if awaking service via message notification is feasible.

@rustdesk rustdesk added the help wanted Extra attention is needed label Oct 27, 2023
@rustdesk
Copy link
Owner

/bounty $100

@algora-pbc
Copy link

algora-pbc bot commented Oct 27, 2023

💎 $100 bounty • RustDesk

Steps to solve:

  1. Start working: Comment /attempt #6192 with your implementation plan
  2. Submit work: Create a pull request including /claim #6192 in the PR body to claim the bounty
  3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

Thank you for contributing to rustdesk/rustdesk!

Add a bountyShare on socials

Attempt Started (GMT+0) Solution
🔴 @scshiv29-dev Oct 27, 2023, 4:32:08 AM WIP
🟢 @nagasai-iitr Oct 27, 2023, 11:42:32 AM WIP

@rustdesk rustdesk changed the title Android Screen Record Stops after hours Android Screen Record Stops after hours (service killed by system) Oct 27, 2023
@rustdesk
Copy link
Owner

rustdesk commented Oct 27, 2023

May work, may not on some phone
https://support.anydesk.com/knowledge/anydesk-for-android-chromeos

image

@rustdesk
Copy link
Owner

image

@scshiv29-dev
Copy link

scshiv29-dev commented Oct 27, 2023

/attempt #6192

Options

@nagasai-iitr
Copy link

nagasai-iitr commented Oct 27, 2023

/attempt #6192

Options

@algora-pbc
Copy link

algora-pbc bot commented Oct 27, 2023

Note: The user @scshiv29-dev is already attempting to complete issue #6192 and claim the bounty. If you attempt to complete the same issue, there is a chance that @scshiv29-dev will complete the issue first, and be awarded the bounty. We recommend discussing with @scshiv29-dev and potentially collaborating on the same solution versus creating an alternate solution.

@TheGrave
Copy link

I have the same issue on Xperia 5 and Xperia 1. It's utterly ridiculous - I need to keep TeamViewer Host installed so that I can re-enable the service. This also forces me to have no screen lock on these phones as TeamViewer Host cannot get to an unlock prompt with them.

@vavolkova
Copy link
Author

Hi @scshiv29-dev ,

I'm not sure how the bounty process works, but is there going to be a solution for this problem anytime soon?

Thanks!

@scshiv29-dev
Copy link

Hey @vavolkova the bounty process is designed to give incentives and get open source contributions to the project. The thing is I did the battery optimization setting on my phone and tried 2-3 other phones and rustdesk was working fine . I still think this is an android issue rather than the app code itself, like if the app is stopped from running in the background it will just terminate the session with the server and it would stop.

@rustdesk
Copy link
Owner

@scshiv29-dev Thanks for your effort.

@scshiv29-dev
Copy link

@rustdesk Yea sure, I figured this was getting stopped by the android OS only. It would be better if we also ask users to add the app to ignore list of battery optimization.

@rustdesk
Copy link
Owner

ignore list of battery optimization.

I have never seen any app does this. Need a good design for this.

@scshiv29-dev
Copy link

scshiv29-dev commented Nov 23, 2023

@rustdesk for me the 'allow background activity ' is the setting that basically made sure the app was working fine even for long hours but the battery consumption is obviously higher.
I don't have rustdesk installed anymore so sending a generic screenshot.

Screenshot_2023-11-23-20-29-25-79_0ba066473b79d6e213a1f6f52505e2ee.jpg

@cikeZ00
Copy link

cikeZ00 commented Nov 23, 2023

Stock android only has these options. They don't guarantee it won't get killed tho.
Screenshot_20231123-161239_Settings.png

@TheGrave
Copy link

@rustdesk Yea sure, I figured this was getting stopped by the android OS only. It would be better if we also ask users to add the app to ignore list of battery optimization.

This won't be sufficient. I have battery optimization for the app turned off and it still dies. There are vendor-specific battery optimizations (usually called Adaptive Battery or something similar) which surely can contribute to the problem.

@scshiv29-dev
Copy link

@TheGrave okay , for the devices I tested it did not stopped for me so I thought this was android setting specific.

@vavolkova
Copy link
Author

Hi everyone,

I just wanted to drop a quick update to let you know that the issue I was facing with Rustdesk has been successfully resolved on my Samsung A10. Big thanks to all of you for the valuable advice and suggestions!

For those who might be experiencing a similar problem, here's what worked for me:

  1. Allow Background Activity:
    Make sure to allow Rustdesk to run in the background. Sometimes, restrictive background activity settings can interfere with the app's functionality.
  2. Remove Rustdesk from Battery Optimization:
    Go to your phone's settings and navigate to the list of apps with battery optimization. Remove Rustdesk from this list to ensure it can operate without any restrictions.

By following these steps, I was able to get Rustdesk up and running smoothly on my Samsung A10. I hope this solution proves helpful to others facing the same issue.

Once again, thank you all for your support and suggestions!

@rustdesk rustdesk added question Further information is requested Fund labels Jan 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💎 Bounty Fund help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

7 participants