No Matches Found!
Try with a different search term
No Matches Found!
Try with a different search term
There's a new home for Articles. Find Articles on Our Product Support Page.
Has anyone else had this issue? I'm trying to enroll an Android 10 device but it fails to connect to the server. Cloud based server, running 13.4. Zebra TC57x running OS10. MobiControl is set as DO. TIA.
Occasionally, a couple of our T56s and T57s will ask for a Google account to use Google Maps even after they have been successfully able to use the maps for months at a time. Our only method of fixing these have been to have them factory reset but have seen the same ones come back some time later to have the same issue. Is there a fix for this that we are unaware of? I assume it is an enrollment issue as I always thought that it pulls the Google account from the enrollment.
In MobiControl (Version 15.2.0) I wanted to change the Application Run Control (Android Enterprise) in an existing Profile. Adding a blacklist works fine, but not deselecting. This has no effect on the device (Zebra TC57), even after a reboot. How can I achieve that an application is not on a blacklist at the device anymore? Doing a factory reset is not an option (but works).
This might not make sense. The devices we are going to deploy will not be easily physically accessible once they are out in the field. Is it possible to update the MC agent remotely? If so, how is it done? Since we plan on setting up the devices in Kiosk mode, will I have to unlock them all first before I do an upgrade? Is it necessary to upgrade the agent each time there is a new version?
Is it possible to send a script or have a package, that will create a text file on Zebra Android 8.1 device which will contain device's name %DEVICENAME% ? Reason behind is that my company is using in-house built app that has it's own launcher. So Kiosk mode from SOTI will not be used. They would like to have device name shown in their app, but how to make it happen? My idea would be to create on all devices a text file that will only have %DEVICENAME% written in it. So that they can make app pull value from that text file in order to show in our app, the device name of it's device. So, is there a way to create such text file on device automatically? Thanks
Is there a way, to close the app through soti on zebra TC-57, Oreo 8.1 devices? Since kill and kill_application don't work, is it possible in some other way to kill the app remotely? Perhaps via sendintent? Currently what I'm doing is using 2 scripts that use mxconfig. One to Disable and other to Enable the app.
Is there an automated way to enable Google speech-to-text? Our customer is using Zebra TC57's (Android 8.1.0, OEM 01-23-18.00-OG-U09-STD) and both Gboard as Google speech-to-text was disabled for security reasons. Instead of Gboard they're using Zebra's Enterprise Keyboard. All's well except that they'd like speech-to-text back. Most of the devices are being used by truck drivers and they think it's better for them to talk to their devices instead of manually typing messages. Using Zebra's StageNow, I'm able to put the microphone key back into their Enterprise Keyboard. But it's not functioning with Google speech-to-text disabled. StageNow doesn't seem to offer a way to enable it, so I tried identify_activity through MobiControl (15.0.2.1049)(Android enterprise agent version 14.2.0.1069) but I can't seem to find the command to switch it on. Any ideas? What can I try?
Hi everyone, Does anyone know how to disable Back button TC57 Regards, Luke
Hi All, Does anyone know if it is possible to lock down chromium on the TC57. Also. whats the best agent for the NON-JMS (TC57 Chinese) scanner Regards, Luke
Hi All, I need some help trying to hide the navigation bar on a android device. The device i'm using is a TC57. Is there any way i can do this through Soti? Luke
Hi, I've been trying to lockdown a TC57 Zebra scanner to just launch chrome without displaying a URL bar. The issue is i cannot use Soti Surf as the website we are accesssing only supports Google Chrome. IS there any way to achieve this?
If the device name used in the ADD DEVICE RULE is updated to a NEW device name, would new devices enrolled after the device name was changed enroll with the older device name or the updated device name? For instance, if the name originally configured in the ADR was "TC57_%ESN%", and the MCSETUP.ini file was downloaded and being used. At some point the ADR is updated and the new device name is now "TC57_%SerialNumber% but the MCSETUP.ini file is NOT re-downloaded. What would the device name of newly enrolled devices be if the original MCSETUP.ini file is still being used? Would SOTI set the device name to the updated ADR configuration or would the MCSETUP.ini configuration be used?
I have searched the forum and I know that there are issues with Android Enterprise disabling auto rotate. I haven't seen any new posts so i thought I would ask. Is there any way in Soti or StageNow that you can disable auto rotate with Android Enterprise?
Aloha, I am testing a Zebra TC 57 and spent almost all week on the phone with support trying to get this device to work properly. SOTI support actually did everything for me to ensure it was done correctly. Created the add device rule, then walked me through the rest of the steps to set up this device. Every thing looked great until I tried to make a call, there was no contact in my contacts list. I thought it would have populated through Google since our account is binned. But I just added another Goggle account (same account that is binned) to populate the contact list. Problem solved...nope open the contact list and could not call though the contacts but if I switch to favorite list I am able. Made another call to SOTI and they verified everything is set up correctly, but found on the Kiosk, advanced setting I needed to check off the Activity Suppression. That fixed the contact list problem. But I also had a Blue tooth failed to pair problem. I shared with support I noticed a lot of apps was uninstalled and sure enough we found the Bluetooth paired utility was uninstalled. Support sent a script to reinstall and that seemed to work. Everything looked fine and worked. Excited I made my way to our vehicle to pair the device, dun, dun duuuunnnnnn. Bluetooth was not finding any active blue tooth devices, I decided to reboot the device. And as the device powered up it got stuck on the splash screen. Could not power off, nothing. I pulled the battery and tired to restart it same this stuck on the splash screen. Finally I did a factory reset (thank God that work) and tried to re-enrolled the device and was successful but all the problems still exist. If any one has been successful enrolling their device please share your victory and how you did it. I would like this device to be set up as a Work managed device, Kiosk/Lockdown, including Setting manager and feature Control. If any one has any detailed info on how to enroll that would be awesome! Mahalo (thank you) in advance
Hello everybody, I'm encountering a problem with the remote control functionality on Zebra TC57 and Zebra TC77 devices. On our end, the remote control (both via HTML5 and the legacy downloadable plugin) shows a black screen inside the device skin. Yet if we click somewhere in that black screen, the remote control does actually work and we're able to control the device. Its screen just will not show. So if we haven't got the device itself nearby, we can't see what we're doing. Here's what we're using: MobiControl version: 14.3.1.1189 (cloud-based)Zebra TC57 and Zebra TC77Android 8.1.0, OEM version 01-13-20.00-OG-U12-STDAgent version: 13.7.0.1031 (GoogleMobiControl1370_1031.apk, DO mode)Remote control version 1.15.3.109 ("MDMPlugin_Notification" v1.0 from Zebra_Hawkeye_RC_AE_1.6.0.102.pcg) Any ideas? Thanks in advance. Cheers, Theun
Top-tier experts who are delivering outstanding content. Should have more than 7000 points.
Experts who are consistent with great content. Should have more than 1000 points
Highly experienced members with valuable inputs. Should have more than 700 points
Beginners taking the initiative. Should have more than 500 points
