Since the Samsung S5e tablet and S10 phone came out, we have not had any success with using mobile rescue with them. It looks as if it will work on the tablet and phone side, but the screen does not display once "on" the device and then when trying to remote control to it, the screen is completely white. We use Sophos for security on it and Airwatch for MDM properites. I've tried remoting on with it unenrolled in Airwatch and Sopohs and the same thing still happens. It works fine on older devices such as the S9 phone and S4 tablet. Anyone else experiencing this as well? Makes it very difficult when we are all working remotely.
Please verify, that “Screen capture” related policies in their MDM system are enabled. We use Android’s default screen capture technology on Samsung devices with Android 10 (instead of Samsung’s screen capture technology), because of technical reasons. In general, there are multiple factors (device type, Android operating system, MDM software, etc.) that effects Rescue behavior.It may be possible that Samsung’s screen capture bypasses some MDM policy that Android’s screen capture does not use by default.
Thank you for the suggestion. I will look into our MDM settings. But we are having the same issue when a device is not even enrolled in an MDM. Would there be a settings in the Rescue Mobile admin console that we would need to take a look at as well?
Does LMI have the capability to test/reproduce this issue on the same device we use
Samsung 5Se tablet from Verizon SM-T727V Android 9
Samsung S10 phone from Verizon SM-G973U Andoid 10
or only via software emulation?
Even without MDM and A/V installed, the issue is present on these devices.
I'm afraid we don't have the ability to test with every new piece of hardware on the market, though those devices are pretty standard so they should react identically. Are there any options to switch networks for these Samsung mobiles?