Share via

Shared device mode Samsung Xcover 7 frictions and delays

Alin Sfiriac 0 Reputation points
2025-10-08T10:58:32.68+00:00

Hi Comunity.

We are in the stage of rollout Samsung Xcover 7 phones to be used with Teams client as a replacement of our current IP Phones. Configurations for now are simple, with Teams and some additional system apps like gallery, camera and calendar available in MHS. For shared devices sign-in is enabled, AAD, and domain pre-filled in App configuration.

All apps are up to date, devices are also up to date.

During the first tests, we spot two really annoying problems:

  1. Teams client doesn't get the sso token from MHS sign in all the time. From our tests, there are 50% changes that after sign in in MHS, when i start Teams app, it requires me to enter the user name.
  2. Teams app works really slow. Every time i open the app i get "Getting things ready" Happens also when the device is in idle, or with screen locked, and i receive a call on Teams. First screen is with "Getting things ready" then after 10-20 seconds i can see the callUI. Edge browser also has this "getting things ready" then the app is started

We tested a similar configuration on a dedicated device enrolled with user (not in SDM) and these issues are not present on that config.

As a workaround we tried to add Teams and Authenticator in battery exclusion, memory exclusion, increase virtual RAM plus from 4 to 6 gb, but the behavior is slightly the same.

Anyone has some suggestions for these "issues" ?

Microsoft Teams | Microsoft Teams for business | Teams on mobile devices
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Amanda Zhu 80 Reputation points
    2026-03-07T21:36:57.59+00:00

    This doesn’t look like expected behavior. With Enable sign in in Managed Home Screen on a device in Microsoft Entra shared device mode, Microsoft says the MHS sign-in should sign the user into participating apps, so a 50 percent Teams username prompt points to device registration or auth flow drift, not normal behavior.

    For the delays, I’d focus on identity policy before battery tuning. Microsoft documents that Conditional Access-related issues for Teams Android devices can cause sign-in loops, random sign-outs, and even Teams freezes, especially with sign-in frequency, MFA, Terms of Use, or noncompliance. Also, if these handsets are really replacing lobby or floor phones rather than being personal shift devices, the supported Android mobile pattern is common area phone, not MHS user SSO.

    I'd review one failed launch in Entra sign-in logs and confirm whether sign-in frequency, MFA, Terms of Use, or noncompliant-device conditions were applied. Rebuild one XCover 7 from scratch as Android Enterprise dedicated + shared device mode with only MHS, Authenticator, Teams, and Company Portal. This will tell you whether the issue is caused by the shared-device build state or by tenant policy and app interaction, because a clean baseline should remove drift from converted devices, stale registration, or leftover app state.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.