Forum Discussion
Knox 3.11, SDK restrictions for Android 15
Yes i think it's the best solution . I have found the Google docs documentation . It confirms that only one app can be device owner .
Our driving app is used by different company with different EMM , we need to work with different EMM to provide all the security feature that we needs .
Are you still on Device Administrator enrollment mode, you should switch to Android Enterprise enrollment. Looks like Android Enterprise phones will work the same as earlier.
https://www.ivanti.com/webinars/2021/the-shift-from-device-administrator-da-method-of-management-to-android-enterprise
https://blog.google/products/android-enterprise/da-migration/
Actually our terminal use android entreprise , we use KME and we use Ivanti as our EMM agent . And our app was installed as a device admin and use sdk know restricted method .
As fas as i know , i am forced to declare one app as device owner during the provisionning process .
My only choice now it's either to exclude Ivanti , and our app will manage our app completely with policies, wipe , configuration etc ... Or we keep using Ivanti but we need to find a workaround .But as you see in the website you provided, DA has no access anymore with Android 15, it must be the owner, no matter if DO or PO to have the relevant permissions.
And just as you mention the driving mode, maybe you don't need this app but an MDM/EMM that can provide such solution already (i have no idea about Ivanti and it's features provided).
Example i know of is the Soti Lockdown with speed detection.
Yes i think it's the best solution . I have found the Google docs documentation . It confirms that only one app can be device owner .
Our driving app is used by different company with different EMM , we need to work with different EMM to provide all the security feature that we needs .
