Can't get customers 6 Zebra TC77's out of 'Airplane Mode' long enough for new Verizon SIM card to register itself on the network

JS
Jamie, Sims
Peak-Ryzex, Inc.

I'm having some major issues with Zebra TC77 devices, enrolled via AE, in lockdown mode, that immediately go into 'Airplane Mode' when a new data-only Verizon SIM card is placed into the device and powered on. The OS/Firmware build on each of the devices has been updated to 01-23-18.00-OG-U00-STD, which supposedly has a fix for a previously known issue with the TC77's doing exactly what I'm describing. Unfortunately, I'm finding this build may not have fixed the issue and I can't get around it to get this customers devices set up with mobile data and shipped back to him. If anyone here knows of a fix, please let me know. Thank you.

Additional Information:

- Every time I enter the go into admin password on the device to toggle Airplane Mode off, after a few seconds it turns right back on, and doesn't give the SIM card enough time to even register on the network, get whatever OTA updates it requires, and finally connect with mobile data.

- The device recognizes it's a Verizon SIM card and uses the correct APN 'vzwinternet'...it just can't/won't connect

- Running MobiControl 14.4.9

5 years ago
Android
ANSWERS
D
DDMOD@SOTI Platinum Contributor
5 years ago (edited 5 years ago)

Hi Jamie,

Thanks for the interesting post!

If you are able to manage the device through MobiControl web-console, there is a toggle button under "Device Functionality" in the "Feature Control" payload titled "Allow Airplane Mode" within AE profiles.
This option is toggled ON by default
When "Allow Airplane Mode" is toggled off, device users should not be able to activate/toggle on airplane mode in settings or quick settings, and the Airplane Mode should not be enabled

Save and assign it to those devices and share the outcome.

If the above solution does not work then try sending the legacy scripts to the device:

writesecuresetting -glo airplane_mode_on 1
(turns on/off airplane mode using 0/1)

Regards,

RC
Raymond Chan Diamond Contributor
5 years ago

Hi Jamie,

If either the feature control or writesecuresetting  script command approach works, you can consider, as a precaution of getting stuck in the problematic state again accidentially, by adding the correspnding script to an Out-Of-Control profile payload for execution upon 1 or 2 minutes of out-of-contact.