Community - SOTI MobiControl

Community - SOTI MobiControl

There's a new home for Articles. Find Articles on Our Product Support Page.

Android Discussions


  • 0 votes 5 answers

    Add device rule with specific AD group does not work

    Hello everybody, We created an Add device rule to automatically assign the tablets that are using this rule to a specific device groupWe set the authentication option to "Utilize directory services to authenticate users during device enrollment".As long as we allow all authenticated users to use this rule, it works fine. But as soon as we enter a specific AD group, no one can use this rule. Not even the users who are member of this specific group.After entering the credentials in MobiControl on the tablet, we get the error message "No registration. Please try again or contact administrator". We tried different AD groups and different users, all with the same behaviour. We are currently using Samsung Galaxy Tab A SM-T585 devices. SOTI Server is v.14.2.1.4394, Android Plus device Agent is Samsung ELM v13.6.0 Any ideas on how to solve this?RegardsRobin

    Android
    7 years ago
  • 1 votes 2 answers

    Device Enrollment with LDAP - MC v14.1 & v14.3 Solved

    Hi everyone, i have some trouble enrolling my devices with LDAP on MC version 14.3 The server cant find my users or groups. It was working without anyproblems before i updated MC from 14.2 to 14.3. I noticed in the directory service connections the new pane "ID" atgroup attributes and user attributes. This pane seems to be new andit is used for the GUID ( Globally Unique Identifier). But our LDAP dont have this attribute. Do i need the GUID to get myenrollment with LDAP work again? Or has someone else the same issue?

    Android
    7 years ago
  • 0 votes 1 answer

    PIN code without secure start-up

    Hi! I have a case with a custumer that is running Honeywell CT50 (android 6) enrolled as AEDO on MC14.3. they would like to use a PIN kode to unlock the screen witch we have enabled with "resetpassword 12345" as a script we send to the device. That is working fine, the downside and my isse is that this also enables the secure start-up and the user have to enter the PIN/pw to boot the device, witch prevents us from rebboting the device remotly as it wont boot up until the user unlocks it. if you set the password manually on the device you get a question if you want to enable this feature or not, when you set it with script it enables it by default anyone with a suggestion on have we can solve this? the customer have around 200 sites with different PINkodes on each sites so i use a macro from the custum attribute to set the PIN on each site using the same package/script.

    Android
    7 years ago
  • 0 votes 7 answers

    Android+ open pdf on lockdown

    Hello, we work with zebra device TC75X with mobicontrol client on version: 13.6.1476 The server version is : 13.3.0.3454 I would like to put on our lockdown a short cut to the documentation in pdf file This pdf is locate on sdcard at the root for to do that, i have add a menu into the lockdown as this: File://SDCARD/PDFFILENAME.pdf add tag <a href="<MCLINK1>">OPEN DOC</a> but when i click on this link nothing happen i have a list of available application BUT no one CAN open a pdf file any idea ? what's wrong ? thanks

    Android
    7 years ago
  • 0 votes 4 answers

    Android OS Updates on Lockdown devices

    Hello everybody, we are currently using Samsung Galaxy Tab A SM-T585 devices. SOTI Server is v.14.2.1.4394, Android Plus device Agent is Samsung ELM v13.6.0 After configuring Lockdown mode for those tablets, the users are no longer able to confirm the OS updates on the tablet. From what i have read, it is not possible to force the OS updates from SOTI server side. Is there a possibility to grant the user the right to run OS updates even in Lockdown mode, or is there any other way to ensure that OS updates can be done? Right now we would have to disable Lockdown on the device, run the update and then enable Lockdown again. Regards Robin

    Android
    7 years ago
  • 0 votes 8 answers

    Enrolling interactive whiteboards with android 7/8

    Hi everyone, some customers asking me if its possible to enroll some interactive whiteboards.Their whiteboards are running with the android 7 and android 8 os. I thought that i could enroll them by using the android generic agent. But i had noluck. And the generic client is end of life. So my question is if it's somehow possible to enroll such devices? Does anyone have experience with it? Or is it impossible (at the moment?) to enroll interactive white boards based on android? Thank you.

    Android
    7 years ago
  • 0 votes 2 answers

    PIN Code of SIM Card disabling on Tomtom Bridge

    Hi, We are deploying a project with Tomtom Bridge Android 6.0 Tablets. We receive the SIM card with PIN 0000. Is there a way to disable this code in Mobicontrol ? Thanks

    Android
    7 years ago
  • 0 votes 2 answers

    How to make a custom keyboard the default keyboard on SOTI Version: 14.1.5.1284 via SOTI Intent Script

    Hello, Is it possible to send an intent via SOTI for Android Enterprise on a Zebra T56 running Android Nougat 7.1.2 to change the default keyboard from Google keyboard (Gboard) to a 3rd party keyboard. App Name : Retriever Keyboard 3rd Party Keyboard ID Name: "com.retriever.cust.retrieverkeyboard/com.retrievercommunications.cust.retrieverkeyboard.RetrieverAndroidKeyboard" Have managed to successfully do this via ADB commands by using : ime set com.retriever.cust.retrieverkeyboard/com.retrievercommunications.cust.retrieverkeyboard.RetrieverAndroidKeyboard But need assistance with doing it via an intent script via SOTI as device would be locked down with KIOSK Mode and over the air without the device been unlocked. Regards Tien

    Android
    7 years ago
  • 0 votes 5 answers

    Profile not applying on Android+ Device - Error message received from device (Internal storage decryption not supported)

    Hi, I am trying to apply a profile to a TC75X Android+ device but I am having issues applying the profile and getting changes to apply on the device. I managed to get the device to apply the profile by removing it from the folder and adding it again but now any changes I make to the profile, nothing happens on the device and it just says "Pending Install". I just checked the Logs and we're receiving error message "Error message received from device (Internal storage decryption not supported)" This is happening on multiple devices.

    Android
    7 years ago
  • 0 votes 8 answers

    Android bundle id for telephone app? Solved Locked

    Hi everybody, we would like to publish the default telephone app of a Samsung S5 mini in our lockdown. Does anybody know the bundle id (identifier) for this app? Thank you!

    Android
    7 years ago
  • 0 votes 2 answers

    Update apps automatically on Android+ devices and MobiControl upgrades

    This post has three main questions. First, I would like to be able to install/update apps automatically on Android+ devices. The majority of these apps are available on the play store. I created an application catalog rule and added apps from both the managed Google Play account and the normal Google Play apps. Google Play store apps are showing on the device, but the managed Google Play apps are not. These are COPE devices so we don't want to use the regular Google Play store method since the users will be able to install any apps they want.  Second question involves upgrading MobiControl. Since it's on the cloud I know I'm supposed to contact support and I have done that last Wednesday I think, but still didn't get a reply. But I need more information about the process before starting since it's my first time. Do I have to specify which version I want to upgrade to or do they always upgrade to the latest version? How long does the upgrade take? Is there any downtime or lost data to worry about? Can I take a backup? How will users be affected by the upgrade? Lastly, does Soti MobiControl require some form of root access to the device? I think I know the answer to this but my manager asked me so I figured I'd ask on here. The reason being is I was testing the Android Enterprise agent on one of the test devices and it wouldn't complete the configuration because I kept getting a "custom OS" error. I looked into it and found posts on here saying it's got to do with the device being rooted at some point in time. I dug deeper and read about Samsung's Knox warranty bit which is like a switch that once triggered cannot be switched off. Samsung's official solution is to replace the motherboard which is expensive and frankly environmentally irresponsible, but that's not the issue here. I discovered that our other test device also had this Knox warranty bit triggered and so far, every device I checked has it triggered which means I cannot install the Android Enterprise agent on any of them. So I'm just trying to rule out the possibility that it was caused by MobiControl. Current system info that might be needed: MobiControl version: 14.1.4.1693 (on cloud) Agent version: Samsung ELM 13.5.0 Android version: 7.0 Nougat

    Android
    7 years ago
  • 0 votes 5 answers

    Set PTP as USB Default Mode Solved Locked

    Hey Guys, does anyone knows an app, intent, script command or something else to change the USB Mode in Android Nougat to PTP? Our Devices (Zebra TC20) running in an kioskmode and our Users don't have access to the Filesystem and I dont want to grant them just for copying some pictures. Unfortunately the USB-Setting for PTP by Zebra MX is not working on the TC20 Devices so I'm looking for an alternative way. I already wrote an App for some other Systemsettings to set, so feel free to send me every single Idea ;-) Thanks

    Android
    7 years ago
  • 1 votes 15 answers

    Failed install package File I/O error Solved

    Good morning, my install package profile failed and the error is: File I/O Why? My profile install an android apk. Web console versione is: 14.2.0.2894 Agent version is: 13.6.0 Build 1844 Device: TC25 Oreo Thank you. Best regards.

    Android
    7 years ago
  • 0 votes 9 answers

    App-Catalog Apps are getting deleted /reinstalled randomly overnight (deletePackageX). Honeywell CT60 Adroid O

    Hello, we have a new SOTI install with honeywell CT60 devices and I have provisioned 3 mandatory apps via an app catalog rule (honeywell movilizer apps and a netsuite app) for managed google play. Seemingly randomly overnight these three apps are uninstalled on a device check-in and then reinstalled at a subsequent check-in.  Unfortunately this is deleting the app data as well and we're constantly having to reconfigure the apps and re-sync all data in the mornings. I've tried: enabling kiosk on some and not others thinking that has something to do with it, Leaving some on the chargers and others separate, sometimes helps other times not (I suppose based on check-in times). Leaving the app running vs not running (still gets killed). Haven't been able to discern any pattern that can give me a consistently reproducible occurrence. Hopefully missing some obvious setting. There are no logs in the mobicontrol console for the devices other than a 'device check-in' at the same time the apps are uninstalled (nothing mentioned about app catalogs etc). The apps are not being upgraded as there have been no new recent versions, and I assume an upgrade would leave data intact. Has anyone else hit issues like this with managed google play?  Wanted to check here first before asking support. Looking at an ADB logcat from the devices at the time the apps are uninstalled,  I can see a call to deletePackageX which seems to be related to play store upgrades but in our case the apps we're using haven't had new versions a month.  The times of the removal and add are coincident with the check-in to mobicontrol. Package removal logs: 130|CT60-L0-C:/ $ logcat|grep -i '02:18'04-05 02:18:13.526  1588  1602 I ActivityManager: Force stopping com.movilizer.client.android.app.demo appid=10141 user=0: deletePackageX04-05 02:18:13.526  1588  1602 I ActivityManager: Killing 19154:com.movilizer.client.android.app.demo/u0a141 (adj 0): stop com.movilizer.client.android.app.demo04-05 02:18:13.553  1588  1602 W ActivityManager: Scheduling restart of crashed service com.movilizer.client.android.app.demo/com.movilizer.client.android.push.PushListenerService in 1000ms04-05 02:18:13.557  1588  1602 I ActivityManager: Killing 19221:com.movilizer.client.android.app.demo:foregroundService/u0a141 (adj 200): stop com.movilizer.client.android.app.demo04-05 02:18:13.558  1588  1602 W ActivityManager: Scheduling restart of crashed service com.movilizer.client.android.app.demo/com.movilizer.client.android.services.MovilizerForegroundService in 10995ms04-05 02:18:13.564  1588  1602 I ActivityManager:   Force finishing activity ActivityRecord{a0b3026 u0 com.movilizer.client.android.app.demo/com.movilizer.client.android.app.MovilizerClientMain43 t101}04-05 02:18:13.575  1588  1602 I ActivityManager:   Force finishing activity ActivityRecord{a0b3026 u0 com.movilizer.client.android.app.demo/com.movilizer.client.android.app.MovilizerClientMain43 t101 f}04-05 02:18:13.576  1588  1602 W ActivityManager: Duplicate finish request for ActivityRecord{a0b3026 u0 com.movilizer.client.android.app.demo/com.movilizer.client.android.app.MovilizerClientMain43 t101 f}04-05 02:18:13.576  1588  1602 I ActivityManager:   Force stopping service ServiceRecord{6ca845b u0 com.movilizer.client.android.app.demo/com.movilizer.client.android.services.MovilizerForegroundService}04-05 02:18:13.576  1588  1602 I ActivityManager:   Force stopping service ServiceRecord{c1c479d u0 com.movilizer.client.android.app.demo/com.movilizer.client.android.push.PushListenerService}04-05 02:18:13.631  1588  2489 I WindowManager: WIN DEATH: Window{f3c02ae u0 com.movilizer.client.android.app.demo/com.movilizer.client.android.app.MovilizerClientMain43}04-05 02:18:13.636  1588  1609 W ActivityManager: setHasOverlayUi called on unknown pid: 1915404-05 02:18:14.128  1588  1614 I ActivityManager: Start proc 4888:com.android.defcontainer/u0a6 for service com.android.defcontainer/.DefaultContainerService04-05 02:18:14.129  1588  1614 I ActivityManager: Force stopping com.movilizer.client.android.app.demo appid=10141 user=0: pkg removed04-05 02:18:14.142  1588  1614 I ActivityManager: Force stopping com.movilizer.client.android.app.demo appid=10141 user=0: pkg removed04-05 02:18:14.157  1588  1614 D KernelUidCpuTimeReader: Removing uids 10141-1014104-05 02:18:14.199  1588  1588 I ConditionProviders: Disallowing condition provider com.movilizer.client.android.app.demo04-05 02:18:14.229  1588  2488 I ActivityManager: Start proc 4905:com.android.musicfx/u0a23 for broadcast com.android.musicfx/.Compatibility$Receiver04-05 02:18:14.339  1588  2521 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.movilizer.client.android.app.demo flg=0x4000010 (has extras) } to com.android.vending/com.google.android.finsky.packagemanager.impl.PackageMonitorReceiverImpl$RegisteredReceiver04-05 02:18:14.340  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.movilizer.client.android.app.demo flg=0x4000010 (has extras) } to com.android.vending/com.google.android.finsky.instantapps.appmanagement.InstantAppRemoveMonitor04-05 02:18:14.341  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.movilizer.client.android.app.demo flg=0x4000010 (has extras) } to com.google.android.gms/.games.chimera.GamesSystemBroadcastReceiverProxy04-05 02:18:14.341  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.movilizer.client.android.app.demo flg=0x4000010 (has extras) } to com.google.android.gms/.photos.autobackup.PhotosAppUninstalledReceiver04-05 02:18:14.341  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.movilizer.client.android.app.demo flg=0x4000010 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver04-05 02:18:14.341  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.movilizer.client.android.app.demo flg=0x4000010 (has extras) } to com.google.android.googlequicksearchbox/com.google.android.apps.gsa.googlequicksearchbox.GelStubAppWatcher04-05 02:18:14.342  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.movilizer.client.android.app.demo flg=0x4000010 (has extras) } to com.honeywell.tools.appsconfig/.PackageChangeReceiver04-05 02:18:14.342  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.movilizer.client.android.app.demo flg=0x4000010 (has extras) } to com.honeywell.tools.ezmenu/.EZMenuReceiver04-05 02:18:14.342  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.movilizer.client.android.app.demo flg=0x4000010 (has extras) } to net.soti.mobicontrol.androidwork/net.soti.mobicontrol.broadcastreceiver.DelayedBroadcastReceiver04-05 02:18:14.403  1588  2521 I ActivityManager: Start proc 4966:com.android.documentsui/u0a11 for broadcast com.android.documentsui/.PackageReceiver04-05 02:18:14.723  1588  1602 I ActivityManager: Force stopping com.netsuite.nsforandroid.app appid=10142 user=0: deletePackageX04-05 02:18:15.126  1588  1614 I ActivityManager: Force stopping com.netsuite.nsforandroid.app appid=10142 user=0: pkg removed04-05 02:18:15.134  1588  1614 I ActivityManager: Force stopping com.netsuite.nsforandroid.app appid=10142 user=0: pkg removed04-05 02:18:15.146  1588  1614 D KernelUidCpuTimeReader: Removing uids 10142-1014204-05 02:18:15.171  1588  1588 I ConditionProviders: Disallowing condition provider com.netsuite.nsforandroid.app04-05 02:18:15.238  1588  2628 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.netsuite.nsforandroid.app flg=0x4000010 (has extras) } to com.android.vending/com.google.android.finsky.packagemanager.impl.PackageMonitorReceiverImpl$RegisteredReceiver04-05 02:18:15.238  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.netsuite.nsforandroid.app flg=0x4000010 (has extras) } to com.android.vending/com.google.android.finsky.instantapps.appmanagement.InstantAppRemoveMonitor04-05 02:18:15.243  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.netsuite.nsforandroid.app flg=0x4000010 (has extras) } to com.google.android.gms/.games.chimera.GamesSystemBroadcastReceiverProxy04-05 02:18:15.243  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.netsuite.nsforandroid.app flg=0x4000010 (has extras) } to com.google.android.gms/.photos.autobackup.PhotosAppUninstalledReceiver04-05 02:18:15.243  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.netsuite.nsforandroid.app flg=0x4000010 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver04-05 02:18:15.243  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.netsuite.nsforandroid.app flg=0x4000010 (has extras) } to com.google.android.googlequicksearchbox/com.google.android.apps.gsa.googlequicksearchbox.GelStubAppWatcher04-05 02:18:15.243  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.netsuite.nsforandroid.app flg=0x4000010 (has extras) } to com.honeywell.tools.appsconfig/.PackageChangeReceiver04-05 02:18:15.243  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.netsuite.nsforandroid.app flg=0x4000010 (has extras) } to com.honeywell.tools.ezmenu/.EZMenuReceiver04-05 02:18:15.243  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.netsuite.nsforandroid.app flg=0x4000010 (has extras) } to net.soti.mobicontrol.androidwork/net.soti.mobicontrol.broadcastreceiver.DelayedBroadcastReceiver04-05 02:18:15.891  1588  1602 I ActivityManager: Force stopping com.movilizer.client.android.app appid=10143 user=0: deletePackageX04-05 02:18:16.295  1588  1614 I ActivityManager: Force stopping com.movilizer.client.android.app appid=10143 user=0: pkg removed04-05 02:18:16.305  1588  1614 I ActivityManager: Force stopping com.movilizer.client.android.app appid=10143 user=0: pkg removed04-05 02:18:16.360  1588  1588 I ConditionProviders: Disallowing condition provider com.movilizer.client.android.app04-05 02:18:16.362  1588  1614 D KernelUidCpuTimeReader: Removing uids 10143-1014304-05 02:18:16.389  1588  2521 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.movilizer.client.android.app flg=0x4000010 (has extras) } to com.android.vending/com.google.android.finsky.packagemanager.impl.PackageMonitorReceiverImpl$RegisteredReceiver04-05 02:18:16.389  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.movilizer.client.android.app flg=0x4000010 (has extras) } to com.android.vending/com.google.android.finsky.instantapps.appmanagement.InstantAppRemoveMonitor04-05 02:18:16.389  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.movilizer.client.android.app flg=0x4000010 (has extras) } to com.google.android.gms/.games.chimera.GamesSystemBroadcastReceiverProxy04-05 02:18:16.389  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.movilizer.client.android.app flg=0x4000010 (has extras) } to com.google.android.gms/.photos.autobackup.PhotosAppUninstalledReceiver04-05 02:18:16.391  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.movilizer.client.android.app flg=0x4000010 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver04-05 02:18:16.392  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.movilizer.client.android.app flg=0x4000010 (has extras) } to com.google.android.googlequicksearchbox/com.google.android.apps.gsa.googlequicksearchbox.GelStubAppWatcher04-05 02:18:16.392  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.movilizer.client.android.app flg=0x4000010 (has extras) } to com.honeywell.tools.appsconfig/.PackageChangeReceiver04-05 02:18:16.392  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.movilizer.client.android.app flg=0x4000010 (has extras) } to com.honeywell.tools.ezmenu/.EZMenuReceiver04-05 02:18:16.396  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.movilizer.client.android.app flg=0x4000010 (has extras) } to net.soti.mobicontrol.androidwork/net.soti.mobicontrol.broadcastreceiver.DelayedBroadcastReceiver04-05 02:18:23.559  1588  2353 I ActivityManager: Killing 27110:com.google.android.gms.unstable/u0a12 (adj 906): empty for 35135s04-05 02:18:23.561  1588  2353 I ActivityManager: Killing 25582:com.google.android.gms:snet/u0a12 (adj 906): empty for 43841s04-05 02:18:46.352  1588  1601 I ActivityManager: Killing 22602:android.process.acore/u0a0 (adj 906): empty for 14345s And the reinstall action at next check-in: 04-05 04:18:27.501  1588  2572 D PackageInstaller: Ignoring abandon after commit relinquished control04-05 04:18:27.583  1588  2353 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.movilizer.client.android.app.demo flg=0x4000010 (has extras) } to com.android.vending/com.google.android.finsky.packagemanager.impl.PackageMonitorReceiverImpl$RegisteredReceiver04-05 04:18:27.584  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.movilizer.client.android.app.demo flg=0x4000010 (has extras) } to com.google.android.gms/.games.chimera.GamesSystemBroadcastReceiverProxy04-05 04:18:27.586  1588  1588 I Telecom : DefaultDialerCache: Refreshing default dialer for user 0: now com.android.dialer: DDC.oR@AKI04-05 04:18:27.587  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.movilizer.client.android.app.demo flg=0x4000010 (has extras) } to com.google.android.gms/.gass.chimera.PackageChangeBroadcastReceiver04-05 04:18:27.588  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.movilizer.client.android.app.demo flg=0x4000010 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver04-05 04:18:27.589  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.movilizer.client.android.app.demo flg=0x4000010 (has extras) } to com.google.android.googlequicksearchbox/com.google.android.apps.gsa.googlequicksearchbox.GelStubAppWatcher04-05 04:18:27.589  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.movilizer.client.android.app.demo flg=0x4000010 (has extras) } to com.google.android.ims/.receivers.RcsAutoStartReceiver04-05 04:18:27.591  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.movilizer.client.android.app.demo flg=0x4000010 (has extras) } to com.honeywell.systemtools.autoinstall/.utils.CheckUpdateFileReceiver04-05 04:18:27.592  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.movilizer.client.android.app.demo flg=0x4000010 (has extras) } to com.honeywell.tools.appsconfig/.PackageChangeReceiver04-05 04:18:27.592  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.movilizer.client.android.app.demo flg=0x4000010 (has extras) } to com.honeywell.tools.ezmenu/.EZMenuReceiver04-05 04:18:27.592  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.movilizer.client.android.app.demo flg=0x4000010 (has extras) } to com.honeywell.tools.provisioner/.ProvisionerReceiver04-05 04:18:27.592  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.movilizer.client.android.app.demo flg=0x4000010 (has extras) } to net.soti.mobicontrol.androidwork/net.soti.mobicontrol.broadcastreceiver.DelayedBroadcastReceiver <snipped> 04-05 04:18:29.928  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver04-05 04:18:29.929  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver04-05 04:18:32.184  1588  1588 I Telecom : DefaultDialerCache: Refreshing default dialer for user 0: now com.android.dialer: DDC.oR@AKs04-05 04:18:32.186  1588  2666 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.netsuite.nsforandroid.app flg=0x4000010 (has extras) } to com.android.vending/com.google.android.finsky.packagemanager.impl.PackageMonitorReceiverImpl$RegisteredReceiver04-05 04:18:32.190  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.netsuite.nsforandroid.app flg=0x4000010 (has extras) } to com.google.android.gms/.games.chimera.GamesSystemBroadcastReceiverProxy04-05 04:18:32.190  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.netsuite.nsforandroid.app flg=0x4000010 (has extras) } to com.google.android.gms/.gass.chimera.PackageChangeBroadcastReceiver04-05 04:18:32.191  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.netsuite.nsforandroid.app flg=0x4000010 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver04-05 04:18:32.191  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.netsuite.nsforandroid.app flg=0x4000010 (has extras) } to com.google.android.googlequicksearchbox/com.google.android.apps.gsa.googlequicksearchbox.GelStubAppWatcher04-05 04:18:32.191  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.netsuite.nsforandroid.app flg=0x4000010 (has extras) } to com.google.android.ims/.receivers.RcsAutoStartReceiver04-05 04:18:32.192  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.netsuite.nsforandroid.app flg=0x4000010 (has extras) } to com.honeywell.systemtools.autoinstall/.utils.CheckUpdateFileReceiver04-05 04:18:32.192  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.netsuite.nsforandroid.app flg=0x4000010 (has extras) } to com.honeywell.tools.appsconfig/.PackageChangeReceiver04-05 04:18:32.192  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.netsuite.nsforandroid.app flg=0x4000010 (has extras) } to com.honeywell.tools.ezmenu/.EZMenuReceiver04-05 04:18:32.194  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.netsuite.nsforandroid.app flg=0x4000010 (has extras) } to com.honeywell.tools.provisioner/.ProvisionerReceiver04-05 04:18:32.195  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.netsuite.nsforandroid.app flg=0x4000010 (has extras) } to net.soti.mobicontrol.androidwork/net.soti.mobicontrol.broadcastreceiver.DelayedBroadcastReceiver<snipped>04-05 04:18:37.188  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver04-05 04:18:37.189  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver04-05 04:18:38.937  1588  2461 D PackageInstaller: Ignoring abandon after commit relinquished control04-05 04:18:39.036  1588  2353 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.movilizer.client.android.app flg=0x4000010 (has extras) } to com.android.vending/com.google.android.finsky.packagemanager.impl.PackageMonitorReceiverImpl$RegisteredReceiver04-05 04:18:39.037  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.movilizer.client.android.app flg=0x4000010 (has extras) } to com.google.android.gms/.games.chimera.GamesSystemBroadcastReceiverProxy04-05 04:18:39.037  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.movilizer.client.android.app flg=0x4000010 (has extras) } to com.google.android.gms/.gass.chimera.PackageChangeBroadcastReceiver04-05 04:18:39.037  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.movilizer.client.android.app flg=0x4000010 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver04-05 04:18:39.037  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.movilizer.client.android.app flg=0x4000010 (has extras) } to com.google.android.googlequicksearchbox/com.google.android.apps.gsa.googlequicksearchbox.GelStubAppWatcher04-05 04:18:39.037  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.movilizer.client.android.app flg=0x4000010 (has extras) } to com.google.android.ims/.receivers.RcsAutoStartReceiver04-05 04:18:39.037  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.movilizer.client.android.app flg=0x4000010 (has extras) } to com.honeywell.systemtools.autoinstall/.utils.CheckUpdateFileReceiver04-05 04:18:39.037  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.movilizer.client.android.app flg=0x4000010 (has extras) } to com.honeywell.tools.appsconfig/.PackageChangeReceiver04-05 04:18:39.037  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.movilizer.client.android.app flg=0x4000010 (has extras) } to com.honeywell.tools.ezmenu/.EZMenuReceiver04-05 04:18:39.037  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.movilizer.client.android.app flg=0x4000010 (has extras) } to com.honeywell.tools.provisioner/.ProvisionerReceiver04-05 04:18:39.037  1588  1602 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.movilizer.client.android.app flg=0x4000010 (has extras) } to net.soti.mobicontrol.androidwork/net.soti.mobicontrol.broadcastreceiver.DelayedBroadcastReceiver04-05 04:18:39.060  1588  1588 I Telecom : DefaultDialerCache: Refreshing default dialer for user 0: now com.android.dialer: DDC.oR@ALQ04-05 04:18:39.231  1588  2666 D CryptdConnector: SND -> {41 cryptfs getpwtype}04-05 04:18:39.231   587   593 D VoldCryptCmdListener: cryptfs getpwtype04-05 04:18:39.233  1588  1708 D CryptdConnector: RCV <- {213 41 default}04-05 04:18:53.063  1588  1736 I SecurityLogMonitor: notify DO04-05 04:19:22.835  1588  2436 D BatteryService: Intnet.putExtra -- BatterySwapping = false04-05 04:19:22.835  1588  2436 I BatteryService: BatteryInfo ledsetting 1 level 93 status 5 health 2 mPlugType 1 mLastBatteryTemperature 30004-05 04:19:40.760  1588  2436 I ActivityManager: Start proc 6837:android.process.acore/u0a0 for content provider com.android.providers.contacts/.ContactsProvider204-05 04:19:58.398  1588  2353 D BatteryService: Intnet.putExtra -- BatterySwapping = false04-05 04:19:58.399  1588  2353 I BatteryService: BatteryInfo ledsetting 1 level 93 status 5 health 2 mPlugType 1 mLastBatteryTemperature 30004-05 06:04:13.111  1588  2436 D BatteryService: Intnet.putExtra -- BatterySwapping = false04-05 06:04:13.111  1588  2436 I BatteryService: BatteryInfo ledsetting 1 level 93 status 5 health 2 mPlugType 1 mLastBatteryTemperature 29004-05 09:04:11.326 10658 10723 I chatty  : uid=10119(net.soti.mobicontrol.androidwork) pool-7-thread-1 expire 1 line

    Android
    7 years ago
  • 0 votes 5 answers

    CT 60 Android agent enrollment

    Looking for help with CT 60 Android agent enrollment. We currently have a CT 60, and I worked with SOTI Support to enroll this device. We tried many times, only to receive an “Empty Token” error. After a month of trying, the SOTI support shared there were a few open tickets with the same problem. The SOTI support finally “injected” the agent directly into the device and going through the Android + path. The help I need now is we are planning to purchase more CT 60s with in the next month and I need info on how do I enroll the new devices?  Do I need to “inject” each device?  Do I use an "add device rule"? Mahalo (thank you) in advance.  

    Android
    7 years ago

Top 3 Contributors of The Week

View All

Earn Contributor Badge

More info
  • Diamond
    Diamond New

    Top-tier experts who are delivering outstanding content. Should have more than 7000 points.

  • Platinum
    Platinum

    Experts who are consistent with great content. Should have more than 1000 points.

  • Gold
    Gold

    Highly experienced members with valuable inputs. Should have more than 700 points.

  • Silver
    Silver

    Beginners taking the initiative. Should have more than 500 points.

  • Bronze
    Bronze New

    New contributors starting their journey. Should have more than 250 points.