You can adjust the scope for SAM to include or exclude the devices you want without having to touch the devices physically. Target an energy saver profile that has a really short sleep time at the group you use to exclude SAM which would turn off the display which is about as close as you will get. There is not a way to tell the display to turn off (go black) on the spot that I am aware of.
As far as supporting SAM, that is something you would want to raise with the application developer.
You can adjust the scope for SAM to include or exclude the devices you want without having to touch the devices physically. Target an energy saver profile that has a really short sleep time at the group you use to exclude SAM which would turn off the display which is about as close as you will get. There is not a way to tell the display to turn off (go black) on the spot that I am aware of.
As far as supporting SAM, that is something you would want to raise with the application developer.
So you're saying excluding the devices from the SAM will eventually make them go to sleep. However, with passcodes set on these, would simply putting them back in scope of the SAM wake them up and bypass the lock screen? or would I have to disable the passcodes altogether?
So you're saying excluding the devices from the SAM will eventually make them go to sleep. However, with passcodes set on these, would simply putting them back in scope of the SAM wake them up and bypass the lock screen? or would I have to disable the passcodes altogether?
You did not mention passcodes. Unless you remove the passcode it will need to be entered. This is a behavior you really want to test in a controlled environment, more so because its not a common or well documented workflow.
You did not mention passcodes. Unless you remove the passcode it will need to be entered. This is a behavior you really want to test in a controlled environment, more so because its not a common or well documented workflow.
Thank you for your input AJ!