Android 15 - CredentialProviderPolicy not surfaced by Intune
I have been having an issue with Android 15 devices. We use Authenticator as our password autofill provider. As soon as a device is updated from Android 14 to Android 15, the password autofill provider is no longer set and the setting to change it is 'blocked by work policy.' I have already tried removing all policies that apply to the devices (device config and device compliance policies) and factory resetting them. Simply having them enrolled as corporate owned fully managed devices causes this to happen. I raised the issue in the Android Enterprise community blog. A link to that is included below. Someone on that thread found that there is a policy in Android 14/15 called the credentialproviderpolicy. When that policy is blocked or unconfigured, this behavior happens. I cannot find anywhere in Intune where I can set this policy. It seems that it is allowed by default when managing Android 14 with Intune, but not set or blocked when the device switches to Android 15. Is there any way to specifically set a policy that is not reflected in the Intune UI? This is a blocker for being able to move more phones to Android 15. Link to Android Enterprise thread: Re: Android 15 - Cannot set default password app - Android Enterprise Customer Community - 8708 Thanks, Tom
Incorrect touch coordinates on the internal screen of Honor Magic V2
Problem description: On the Honor Magic V2 smartphone, when using the internal screen in an unfolded state, Microsoft Edge incorrectly registers touch input. The touch position is shifted by approximately 5 mm vertically, making the browser nearly unusable. Details: Edge works correctly on the external screen when the device is folded. All other applications (system apps and those from the Play Store) work without this issue, confirming that screen calibration is correct. The problem persists after reinstalling Edge and clearing the cache. Steps to reproduce: 1. Open Microsoft Edge on a Honor Magic V2. 2. Unfold the phone and use the internal screen. 3. Try tapping on elements in the browser. 4. Notice that the touch coordinates are vertically offset (up) by approximately 5 mm. Expected behavior: Touch input should be registered at the correct coordinates, as it works in other apps and on the external screen. Device and software details: Microsoft Edge version: 132.0.2957.129 Android version: 15 Device: Honor Magic V2 Additional information: The issue persists the standard, Beta and Canary versions of Edge.