Looking for solutions to assist in Bulk Management (Wipe) of Android Enterprise devices
Hi everyone, I'm turning to the community to see if there are any solutions being used out in the wild that assist with bulk wiping Android devices. I suspect that what I'm asking may not be possible - mainly due to the nature of Android Developer Options, USB Debugging etc. - but I've been I've been tasked by our management to investigate and possibly propose a solution. As an example, we currently use several Cambrionix ThunderSync3 16 port devices to DFU both iOS and macOS devices but they don't offer a similar solution for Android. Are there any solutions that can be used either in tandem with docking stations like Cambrionix or some other. Our use case is Work Managed and we use Omnissa Workspace ONE UEM to manage the devices. The devices themselves are Pixels and Samsungs. and each device is loaded into either the Google Zero Touch Portal or the Samsung Knox Portal. The expectation is that when a large number of Androids are returned for whatever reason, we'd like to be able to plug the device into a "station" and programatically wipe them en masse. Personally, I think we need to simplify our returns process and use the MDM in a controlled environment but I have to have asked these questions, due diligence and all that. Thanks in advance for your input.
Control Wi-Fi Calling settings
Hi there, hope you're well. Just wondering is it possible to control the Wi-Fi Calling settings within Android via MDM? The closest thing I've seen is to use Knox Asset Intelligence to check Wi-Fi Calling setting status on Samsung devices: https://docs.samsungknox.com/admin/knox-asset-intelligence/dashboard/network-insights/wifi-calling-setting-status/ Thank you for your help & input in advance!
Is there an alternative way to perform the same function as UpdateApplication on Android 15?
Hi everyone, We are currently managing Samsung enterprise devices via Knox Manage under Android Enterprise DA mode (Device Admin) . Our in-house application previously used the UpdateApplication API to update itself silently without user interaction. This worked well under Android 14. However, after updating to Android 15, this API no longer functions. Based on the Samsung Knox SDK documentation, it appears that UpdateApplication is now restricted to Device Owner (DO) and Profile Owner (PO) apps. We have tried to assign all delegated scopes to our app via Knox Manage policy settings (Android Enterprise → App Restrictions → Delegated Scopes for Apps). Unfortunately, the API call still fails. ✅ What we’re looking for: - Is there any alternative methods that allows silent or managed updates of enterprise apps on Android 15, without being a DO/PO app? - Or is DO/PO elevation now the only viable path? - If so, is there an official onboarding flow or protocol to request DO/PO designation for an app via Knox Manage? Any guidance, references, or examples would be greatly appreciated. Thank you! — Environment: - Android 15 - Knox Manage (latest) - Samsung A9+ tablets - Device Admin mode
Samsung Tab Active5 Side Button Configuration
Is there any way to change the default configuration for press and hold from "Wake Bixby" to "Power off menu". Trying to run a kiosk application and it's confusing for users to need to hold the side and volume down button to open the power control. Bixby is otherwise disabled so holding the side button currently does nothing in its default configuration. Samsung support has unfortunately been less than helpful, and will only lift a finger if you pay for full Knox EMM.
Request for Android Community: Advice and Help on Playing Pre-Recorded Voice on Calls
To the Esteemed Android Developer Community, I am seeking your expert advice to understand whether my task is feasible on the Android platform. I aim to implement the following functionality: Task Description: Objective: I want to create an Android app that plays a pre-recorded voice message during a phone call. The app will: Automatically answer an incoming call when it is ON. Play a pre-recorded audio file stored on the user's phone (recorded by the user). Audio Content: “I am busy right now, call back after some time.” Disconnect the call after playing the message. Usage Scenario: This feature will be used only when the app is ON. It is intended for times when the user is busy and wants to inform the caller without manually attending the call. Key Requirements: Detect and answer incoming calls automatically. Play the recorded voice message to the caller. Ensure the caller hears the message clearly on their end. Disconnect the call programmatically after the message is played. Questions for the Community: Is this Task Feasible? Can the Android platform route a pre-recorded voice file to the call audio stream (STREAM_VOICE_CALL) so the caller can hear it? Are there technical or carrier-level restrictions that could prevent this functionality? Android APIs or Services: Are there specific APIs, such as TelecomManager, CallScreeningService, or AudioManager, that can handle this requirement effectively? Privacy and Legal Concerns: Are there any privacy or legal considerations (e.g., notifying the caller) that I should be aware of when implementing this feature? Compatibility Across Devices: How can I ensure compatibility across different Android devices and versions (API 26 and above)? Additional Information: Voice File: The pre-recorded message is stored locally on the user’s phone in a secure folder. App Activation: The functionality will work only when the app is manually turned ON by the user. Intent: This is a personal productivity tool to handle calls during busy periods. Help Needed: Advice: Can you confirm whether this task is achievable on the Android platform with existing APIs and hardware? Are there specific approaches or best practices to consider for implementing this? Code Implementation: I am looking to hire an experienced Android developer who can: Write fully working code to achieve this task. Ensure the solution is robust, privacy-compliant, and compatible across devices. I deeply appreciate the Android community's expertise and guidance. Your input will help me determine the feasibility and approach for this project. If you have any suggestions, insights, or are interested in developing this, please reply to this request.
Samsung Galaxy Active 5 tablet Power Off Menu
In Kiosk Mode on the Samsung Galaxy Active 5 tablet, holding the side button currently activates Bixby, even though Bixby has been disabled. The expected behavior is for holding the side button to open the Power Off menu, as it does in normal usage. Are there any settings or configurations that can bypass this behavior and allow the side button to open the Power Off menu directly while in Kiosk Mode?Samsung S23 with Knox Mobile Enrollment fails to enroll in Intune
I was wondering if anyone else was having problems enrolling Samsung S23s using Samsung Knox Mobile Enrollment into MS Intune? I read the other thread about S23s and Zero-Touch failing, but that seems different than what we see. We get to a point where Chrome browses to https://play.google.com. The page says: Please click here to continue. No matter how many times you tap that link, nothing happens. Everything is just stuck. If you wait a long time, the phone just restarts and is in some weird state. Using the QR code works fine. Also, other models, like the Samsung S20, enroll just fine using Knox Mobile Enrollment into Intune. This is what it looks like. I opened a case with MS, but they say that is Google's page, and they can't control what it does.
Welcome to Chrome prompt during Samsung Knox + Intune Enrolment
I am deploying fully managed work profile through Knox+Intune, after the end user sets Wi-Fi (or uses Mobile Date) and downloads the Knox settings to point to the chosen EMM Provider the prompt below is encountered Normally there used to be "Accept and continue", which led to credentials to 365 and Intune. Now there is "Add account to device", where I can set profile to Work and Personal profiles. And "Use without an account", which leads to 365 and Intune like before. Its very confusing, especially for end users and they also have the ability to exit out of the enrolment process altogether which bypasses the process and reverts to the device home screen Does anyone know, how this can either revert get back to old "Accept and continue" in Welcome to chrome or if not ensure the screen is locked down and can't be exited?
