I just noticed our Zebra TC52s drop the session after about 30 seconds in Epic Rover during the 0900 meds on 5W, so we end up rescanning the wristband and med — why do we do it that way? Has anyone extended the device/MDM timeout to about 120 seconds without messing with BCMA safety checks, and did it reduce rescans?
On our TC52s, we set MDM lock to 120s; left Rover ‘session timeout’ 30s — rescans dropped, BCMA intact. @Informatics confirm?
Sounds like Android is dozing Rover: we whitelisted Rover from battery optimization and set Zebra PowerMgr Wi‑Fi to “Keep on during sleep,” which stopped mid-pass drops without touching BCMA. @Informatics, can you confirm your MDM can push the BatteryOptimization whitelist and Wi‑Fi suspend policy? If you’re on Intune or Workspace ONE, I can share the exact payloads — it’s like telling the device not to take a coffee break mid-med.
We cut rescans by enabling 802.11r/k and lowering roam thresholds; @NetOps tuned APs. Anyone tried DataWedge ‘scan timeout’ tweaks?
If you’re running Imprivata MDA/SSO on the TC52s, check its lock timer and mark Rover as a “persistent/trusted” app — bumping MDA to about 90–120s stopped our mid-pass drops without touching Rover’s 30s, and BCMA stayed happy. @shift.mentor312’s Wi‑Fi angle can help, but SSO was the real hall monitor for us. Are you on Imprivata or just a device passcode?
Check your Epic AppConfig for Rover — the ‘InactivityTimeout’ might be set around 30s on the TC52s during the 0900 meds. We bumped it to 120s via MDM (managed config to com.epic.rover) and BCMA still enforced wristband/med checks; just keep it within your SSO grace. Are you pushing AppConfig yet or only device-level timeouts?