SOTI Pulse Logo

Samsung Remote Control not working

Solved
B
BD
***

Hi,

maybe we did something wrong because remote control from MobiControl is not working for Samsung devices.

 

We have models SM-T636B, SM-X356B

The devices are enrolled with knox EMM (one with afw#mobicontrol)

Supported API is showing: Samsung MDM V5.7, Samsung RC V1, Samsung KNOX v3.3, Work Managed Device

Knox Service Plugin is installed v1.5.64 (26.05)

Our onprem mobicontrol is 2026.1.0.11865

 

RC works with another manufacturer.

Trying to open RC to any one of the Samsung device shows: Connection lost! WebSocket closed without sending a close frame.

 

We have a running support case open but no solution yet, so i thought i might ask the community for any hint that might lead to a wrong configuration or enrollment process from our end.

 

Thanks, BD

21 days ago
SOTI MobiControl
ANSWERS
B
BD
19 days ago

Hi Raymond,

 

thanks for your reply.

I had a session today with support to collect logs.

During that session when the xsight services restarted automatically the remote control started working again.

While the situation still seemed strange: Other manufacturer RC worked but Samsung only not

A restart of the services resolved the issue and now RC works for all devices.

 

 

Solution
RC
Raymond Chan
19 days ago (edited 19 days ago)

I have no problem starting both legacy and html5 remote-control session on Samsung test device with exactly the same MDM API versions and MobiControl server version as in your case.

Do you have Soti XSight installed on your MobiControl server?

Also, have you tried starting remote-control session on different Samsung device models and on other device brand(s)?  Is the problem consistent for ALL your tested Samsung device model(s) but absent for all other device brand(s)? 

 

Similar Discussions