Custom Android Client set Start on Boot in Advanced settings

[PaulDK89]

Can i request to add an overide command in the custom client section, under Advanced settings, for android client builds(Web interface), to set the start on Boot to enbled?
example "start-on-boot=Y"

[jjw-ryan]

I've been having a read into this today, we're using Denso BHT handheld terminals for use in retail and this is really important as these devices are usually left to run out of battery by users.
I have seen there is an ADB workaround posted in August 2022 that says to enable 'Start on boot' option but I can't see this in the application UI on the Android device.

[jjw-ryan]

I think that is because we disabled settings on the UI, but an advanced parameter would be needed so we can set it without granting user's access to the settings.

[cwarf5]

Did you ever find a good, working solution to this?

[rustdesk]

@21pages let's work on this. This option seems not as easy as others. Not sure if it is feasible since this seems requiring user interaction.

[rustdesk]

adb shell appops set com.carriez.flutter_hbb PROJECT_MEDIA allow

https://www.reddit.com/r/rustdesk/comments/1ntm48n/comment/nhc3poh/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

[21pages]

When enabling the "Start on Boot" option, the app requests the REQUEST_IGNORE_BATTERY_OPTIMIZATIONS and SYSTEM_ALERT_WINDOW permissions:

• There is no corresponding ADB command for REQUEST_IGNORE_BATTERY_OPTIMIZATIONS, but on my phone, I found that using adb shell dumpsys deviceidle whitelist +com.carriez.flutter_hbb works as a replacement. However, I am unsure if this will work on other devices. Alternatively, could REQUEST_IGNORE_BATTERY_OPTIMIZATIONS also be forcibly requested when "Start on Boot" is detected as enabled when starting the service?

• The SYSTEM_ALERT_WINDOW permission is also requested when starting the service. This could be handled by forcing the SYSTEM_ALERT_WINDOW permission request when "Start on Boot" is detected as enabled (currently, it’s not forced). Interestingly, even when clicking "Back", the permission is granted on my phone.

This approach would allow users to enable the necessary permissions by clicking only once on the permissions screen to enable other permissions, without needing to specifically click "Start on Boot" to enable that option.

related: rustdesk/rustdesk#1330

[Omeryl]

Both of these permissions are thankfully able to be automated on Zebra's flavor of Android via EMDK profiles.

[rustdesk]

https://deepwiki.com/search/now-we-can-start-the-rustdesk_b9ccd942-fbc6-4e0a-99ac-f371c8db3a20?mode=fast

adb shell am startservice com.carriez.flutter_hbb/.MainService

Starting service: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=net.dikon.cockpitsupport/.MainService }

Error: Requires permission not exported from uid 10188

In theory, the user presses on "Start Service" button === adb shell am startservice com.carriez.flutter_hbb/.MainService

But it is not, https://deepwiki.com/search/is-the-user-presses-on-start-s_0ddb08d9-b128-4b3a-8c60-ccf99e697111?mode=fast

Our dev will find out why above adb does not work, also tried to make start_service toggle option works for Android, they are the same problem.

I will update our finding and progress here, but sorry, there is no ETA.

We might learn more from DroidVNC:
rustdesk/rustdesk#1330 (reply in thread)

[Cheesebaron]

Would it be possible, to allow setting the option, with a documented caveat that MDM systems/Users have to ensure all permissions are allowed for it to work properly?