The Crux of Android 14 Software Migration and Its Affect

First I wish to give an outline of the Meraki Methods Supervisor (SM) software. Methods Supervisor is Meraki’s endpoint administration product. We assist administration for a lot of totally different platforms, together with iOS, Android, macOS, and Home windows. “Managing” a tool can imply monitoring its on-line standing, pushing profiles and apps to it, and/or imposing safety insurance policies, amongst different issues. With Methods Supervisor, this administration all occurs by Meraki’s on-line interface referred to as Dashboard. Examples and code snippets talked about on this weblog are extra particular to the Android SM software.

Migration of purposes to any SDK primarily consists of 2 duties from the developer’s perspective. One is – how the appliance behaves when put in on a tool with an Android model apart from the goal SDK of the app. And secondly, how the app will behave when the goal SDK is modified. Builders want to know what new options, or updates of any present characteristic, and its influence on the appliance are.

This doc focuses on a few of the modifications impacting builders with Android 14 migration. It additionally covers migration of the Methods Supervisor app to Android 14, and challenges encountered throughout the migration and testing.

Android application migration

Font Scaling

In earlier variations of Android i.e., 13 Non-linear font scaling was supported as much as 130% however in Android 14, it’s supported as much as 200% which may influence the UI of the appliance. Within the software if font dimensions are declared utilizing sp (scaled pixel) items there are possibilities of minimal influence on the appliance as a result of Android framework would apply these scaling elements. Due to nonlinear scaling of font density scaling is not going to be correct.
Key factors

  • TypedValue.applyDimension() to transform from sp items to pixels.
  • TypedValue.deriveDimension() to transform pixels to sp
  • LineHeight items needs to be laid out in sp to handle proportion together with textual content measurement.

Background Course of Limitation

Android OS is autonomous to handle the assets effectively by improvising efficiency as nicely. One of many pointers to realize the identical is by caching purposes within the background and solely when the system wants reminiscence these purposes might be faraway from reminiscence. All purposes ought to adjust to Google Play coverage and therefore killing of processes of different purposes are strictly restricted in Android 14. Therefore killBackgroundProcessess() can kill solely the background processes of your personal software.

Foreground Service Sorts

In Android 10, a brand new attribute was launched to specify service sort for foreground companies. When utilizing location info within the foreground service it was required to specify the sort as “location”. Whereas in Android 11, mentioning service sort for utilization of digital camera or microphone in foreground service was mandated. However in Android 14 or above, all foreground companies have to be declared with their service varieties.

A number of the new service varieties had been additionally launched in Android 14 – well being, remoteMessaging, shortService, specialUse and systemExempted. If service isn’t related to any of the categories specified, then it is suggested to alter logic to make use of Workmanager or user-initiated information switch jobs. MissingForegroundServiceTypeException might be thrown by the system in case service sort isn’t specified.

Service sort permissions have to be declared together with specifying the sort in service.

android:identify="android.permission.FOREGROUND_SERVICE_SYSTEM_EXEMPTED" />

            android:exported="false" />

Limitations on Implicit Intent and Pending Intent

Implicit intents are solely delivered to exported elements. This restriction ensures the appliance’s implicit intents aren’t utilized by another malicious apps. Additionally, all mutable pending intent should specify a element or package deal info to the intent, if not the system throws an exception.

Implicit intent needs to be export much like this:

   android:exported="true"> <!-- This have to be TRUE in any other case this can throw 
exception when beginning the activity-->
      <motion android:identify="com.instance.motion.APP_ACTION" />
      <class android:identify="android.intent.class.DEFAULT" />

If pending intent needs to be mutable, then element data have to be specified.

val flags = if (MerakiUtils.isApi31OrHigher()) {
} else {

val pendingIntent = PendingIntent.getActivity(
   Intent(context, {
      putExtra(ACTION, KioskActivity.BREAK_OUT_SINGLE_APP)

Export conduct to be specified for Runtime-registered broadcasts

Previous to Android 13, there have been no restrictions on sending broadcasts to a dynamically registered receiver when it’s guarded by signature permission. Whereas in Android 13, aiming at making runtime receivers protected, an optionally available flag was launched to specify whether or not the receiver is exported and visual to different purposes. To guard apps from safety vulnerabilities, in Android 14 or above context-registered receivers are required to specify a flag RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED to point whether or not receiver needs to be exported or to not all different apps on the system. That is exempted for system broadcasts.

   requireContext(), receiver,intentFilter(),

Non-Dismissable foreground notifications

In Android 14 or larger, foreground notification will be dismissed by the consumer. However exceptions have been supplied for Gadget coverage Controller (DPC) and supporting packages for enterprise.

JobScheduler reinforces callback and community conduct

Previous to Android 14, for any job operating for too lengthy, it could cease and fail silently. When App targets Android 14 and if the job exceeds the assured time on the principle thread, the app triggers an ANR with an error message “No response to onStartJob” or “No response to onStopJob”. It’s instructed to make use of WorkManager for any asynchronous processing.

Modifications particular to Android Enterprise

Android Enterprise is a Google-led initiative to allow the usage of Android gadgets and apps within the office. It’s also termed as Android for Work. It helps to handle and distribute personal apps alongside public apps, offering a unified enterprise app retailer expertise for finish customers.


For signing in with a Google account, GET_PROVISIONING_MODE was launched in Android 12 or larger. In Android 14 or larger, DPC apps obtain this intent which may carry the knowledge to assist both Totally managed mode or work profile mode.

wipeDevice – for resetting system

Scope of wipeData is now restricted to profile homeowners solely. For apps focusing on Android 14 or larger, this methodology would throw system error when referred to as in system proprietor mode. New methodology wipeDevice for use for resetting the system together with USES_POLICY_WIPE_DATA permission.

Newly added fields and strategies


When cross-profile contacts coverage is allowed in DevicePolicyManager, these fields can be utilized for itemizing all work profile contacts and cellphone numbers from private apps together with READ_CONTACTS permission.

To assist setting contact entry coverage and callerID, under strategies are newly added;


Deprecated strategies

Beneath strategies are deprecated and instead strategies specified within the earlier part needs to be used.


Challenges throughout Meraki Methods Supervisor App Migration

  • To make sure there was no UI breakage, we needed to recheck all of the code base of xml recordsdata associated to all fragments, alert dialog and textual content measurement dimensions.
  • Few APIs like wipeDevice(), weren’t talked about within the Android migration 14. Through the testing part it was discovered that wipeData() is deprecated in Android 14 and wipeDevice() was supposed for use for manufacturing unit resetting the system efficiently.
  • Profile info which will be fetched together with intent GET_PROVISIONING_MODE was additionally missed within the migration information. This was discovered throughout the regression testing part.
  • requestSingleUpdate() of location supervisor all the time requires mutable pending for location updation. However nowhere within the documentation, it’s prescribed about it. As a consequence of this there have been few software crashes. Needed to determine this out throughout software testing.

Helpful hyperlinks for reference



Recent Articles

Related Stories

Leave A Reply

Please enter your comment!
Please enter your name here