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.
We have about 60 MC9300's. All of them are on Android 13. I upgraded one of our test devices to the latest Android 14 lifeguard patch to test the applications, however Xsight is not working properly on this device now. It has all the same profiles at the 13 devices, which all work fine with Xsight. When connecting to the 14 device, the file manager and task manager buttons are missing and the screen never connects. I can turn off Kiosk, Turn on Kiosk, Enter admin mode. I compared the Xsight info on the 13 devices to this one and they are identical. Anyone else have this issue?
We’re running into an issue with our Zebra VC8300 devices on Android 14 where DataWedge configurations are not importing. Our current process works fine on Android 13 — the .db file is stored on the device in /sdcard/, and we push it via SOTI MobiControl using the DataWedgeMgr XML. <wap-provisioningdoc> <characteristic version="9.2" type="DataWedgeMgr"> <parm name="ConfigurationFile" value="/sdcard/UlineMX/datawedge.db"/> <parm name="AutoImporting" value="1"/> </characteristic></wap-provisioningdoc> On Android 14, the same .db file will not import — even if I go into the DataWedge app on the device and attempt to import it manually. No errors appear; it simply doesn’t apply the configuration. I also tried creating a new StageNow Profile with a higher MX but that did not solve the problem. Has anyone run into this with Android 14? Did the import location change? Is there a new permission requirement for DataWedge to access files? Is .db importing deprecated in favor of another method? Any insight or workaround would be appreciated.
Hi All I can see lots of posts regarding remote control stays black on Android 13 and 14 Samsung devices and generally the advice is to start your RC session, once connected to the device it will show a black screen, use Page Up on your keyboard, followed by the PIN (you won't see it on screen) followed by enter and you will then be able to see the screen. This method works fine for android 12 and 15 devices, but not for android 13 and 14. The android 13 and 14 devices just can't be woken remotely - has anyone got any extra tips or know if an agent is available to support this function. In the past we've just been told this is just the way android 13 and 14 are, but since it is still in support and these are still supported devices (the OS can't be upgraded) then has there been any fixes or workarounds? The test device in question is SM-G780F (max OS is 13) We have Samsung on android 12 and typing the PIN on black screen is fine We have Samsung on android 14 and it has the same issue as android 13 - can't get past the black screen even after typing PIn in blind. We have Samsungs on android 15 and no issues. Any advice appreciated, but please note what I have already tried above and the comparison between android 12 and 15 above. Many Thanks
hello, i have there an Zebra TC21 running OEMversion: 14-26-08.00-UG-U00-STD-HEL-04. On the device was set an PinLock using Soti Script : " resetpassword 1234 -bypass_secure_startup". Now the owner live and i need to remove the Passkey. The problem is that the device is connectet to the correct network but didnt show up online in the Mobicontrol console (2024.1.2). Enrolled as Enterprise device. Any idea ? Kind regards Günter
Hello, We are not able to remote control our scanners anymore since Android 14. anyone else has this problem or has a solution for this? Devices: Zebra TC52, MC3300X tested on mobi versions: V2025.0 15.4.1.4828 Agent versions: 2025.0.2.1045 15.4.6.1013
Dears,I'm facing an issue on new devices running Android 14, Samsung Galaxy Tab Active 4 Pro.Agent Version: 2024.0.5.1062MobiControl Version: 2024.0.1.1020I have a profile applied, with Lockdown and Camera and Gallery added to the Lockdown screen. Both apps has been enabled with script enable_system_app com.sec.android.app.camera/com.sec.android.gallery3d. However, when trying to open a camera, I got a pop up that "Security policy preventing use of Camera". Camera is enabled in feature control. I do have the same device running Android 13, enrolled with the same profile, where this issue is not present.Does someone faced similar issue, and have a solution?Best regards,Wiktor Mlynski
Hello,Following the update to Android 14 on our managed Samsung devices, we are getting a net::ERR_UNKNOWN_URL_SCHEME when trying to access the wifi app using the action ''action://CONFIGURE_WIFI'' in lockdown mode.Is there any workaround or fix to this? I've tried sending intents with ''android.settings.WIFI_SETTINGS'' without luck.Thank you,
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
