Samsung Devices: Can't call from a personal app
Hi everyone we received some reports from our users in the last couple of month that suddently the phone app on COPE devices (Samsung A-series) starts to show "Can't call from a personal app" - Your organisation only allows you to make calls from work apps. Workaround: Reboot the device. For most of the reports this workaround has to take place once and the message is gone forever. A very small amount of devices starts to show this message again after a couple of weeks. Rebooting is resolving the issue again. Any idea of how to prevent this? Even emergency calls are not possible if this error is appearing! Does anyone else have seen this behavior? Raised a case with Samsung today. Thanks! Daniel
Google Play Console : delete an application, ID transaction
Hi everyone, I noticed that it is now possible to delete an application that has been unpublished for a long time, for example. When you click on delete application, you are asked for the transaction ID of the developer account and the package name. I have my transaction ID (which can be found on payments.google.com), but it is not in the same format as the examples given and is not recognised. Have you ever tried to delete an application? Have you also encountered a problem with this ID? Best regards, NB : The ID I have is in the format xxx.registration-xxx-xxx-xxx-xxx-xxxDefault browser app not resettable
Hey! We are currently testing a few apps in Work Profile, for which we need 2FA. The second factor is a FIDO2 token that can be used via NFC or USB. If you have a FIDO2 token with USB-C, everything is fine. But we also have some with USB-A. If you don't have an adapter, you're more likely to resort to NFC. Chrome supports FIDO2/NFC directly, which makes logging in quite easy. However, most web views cannot do this, and a passcode must be entered manually. The pure FIDO2 NFC tag basically contains a URL with the passcode. You open the webpage via NFC, copy the passcode, and enter it when logging in. So far, so good. However, we encountered a problem that prevents us from using the FIDO2 token via NFC in the Work Profile properly. There are default apps for different categories such as browser, wallet, caller ID, etc. If you need to launch one of the app categories and there are several apps available, you will be asked which app you want to use and just for once or always. The app preferences can be reset via the settings so that the query will reappear the next time. This works without any problems with “Home app,” for example. But the Default Browser? No. The Browser app default remains after the reset. Even if a browser was set as the default and was deleted, it will just switch to another app and won't ask. The problem with a permanently set default browser is that links from NFC tags are immediately opened in the personal space. If there is a copy & paste lock on the work profile, you cannot use the code. (Unless you type >40 characters) If you are asked for an app to open the URL, you can also select the browser in Work Profile. Can anyone reproduce this behavior? Or does anyone know if something has changed for the Browser-Default in Android 15/16? On a device running Android 13, resetting the app defaults works reliably. It doesn't seem right that the browser default cannot be reset properly with Android 15/16.
Bug? G-board removes additional languages post BYOD Enrollment?
We noticed a strange behaviour, If G-board has additional languages added apart from English like Polish or German, post enrolling into a work profile, the additional languages disappear from the keyboard. I was able to reproduce with Intune, WorkspaceOne and even TestDPC app. This is true even if no Device Restrictions are applied. It seems like a bug. Has anyone else seen this issue?
Application report not getting collected on Xiaomi mix fold devices
We have couple of users who have the Xiaomi Fold device and in the application report section of status report notifications we are only getting the android device policy app. None of the other applications are getting returned. Is this a known issue? How can we debug the issue? I was not able to see anything obvious in the device logs. We are getting the full application report for the other devices.Requirement for developer verification for app install
Hi all, Last weekend someone pointed out to me that Google has announced that it will only allow app installs from developers that are verified with Google. This includes side loaded apps and third party play stores. See this article https://9to5google.com/2025/08/25/android-apps-developer-verification/ and this blog post from F-Droid: https://f-droid.org/en/2025/09/29/google-developer-registration-decree.html I'm curious, how does this community think about this change? The reason for posting is that i'm not yet convinced this is a good change, it is presented as a security feature but I think we can all agree on that malware developers will find a way to register and push there malware anyway. Meanwhile developers need to start paying a fee, even when they aren't even using the Google Play store to push their apps. And that might backfire to us as users, prices going up, apps being removed or no longer developed, more in app advertisements etc. To me it feels like locking down Android to a way that side loading and third party app stores will be blocked in the feature, " because they are not secure". It feels like Google moving to an Apple strategy while Apple is forced by the EU (DMA) to open up. I've added this to my list of things that are happening even though I told people this will never ever happen to android. Android (even with google services) was, and should always be, an open platform where you are able to use a device as you wish. Google shouldn't be the one decided how and with what I use my device. Its a good idea to have a verification system available, and give a warning to users when an app is not verified, but there should always be a way to install it anyway. Am I the only one seeing this as a bad decision which could potentially get worse?
Activating Device Owner in Android 16
I’m building a parental control app that relies on Device Owner mode. This worked fine on older devices (e.g. Samsung Galaxy S8 running Android 8/9), but it fails on a Pixel 10 Pro running Android 16. Process: I factory reset the Pixel. At the welcome screen, I scan a QR provisioning code. The QR downloads my signed APK, installs it, and should activate it as the Device Owner. Problem: On Android 16, the app is installed but Device Owner is not activated. In Settings > Device Admin, my app is listed, but the toggle is off. My MyDeviceAdminReceiver never fires — I see no provisioning broadcast (PROVISIONING_COMPLETE or PROVISIONING_SUCCESSFUL) and no debug logs. Here is my provisioning json as a starter - juyst in case I am doing something stupid!! { "android.app.extra.PROVISIONING_MODE": "device_owner", "android.app.extra.PROVISIONING_DEVICE_ADMIN_COMPONENT_NAME": "com.xxxx.yyyy/.MyDeviceAdminReceiver", "android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_DOWNLOAD_LOCATION": "https://test.app.com/app-release.apk", "android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_CHECKSUM": "rePWsxWwsW2wycUDiE_hVHSczS3qaJIdk7fnzDMPDV0", "android.app.extra.PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED": false, "android.app.extra.PROVISIONING_SHOULD_LAUNCH_RESULT_INTENT": true, "android.app.extra.PROVISIONING_ADMIN_EXTRAS_BUNDLE": { "provision_token": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx......." } }
