The Crux of Android 14 Software Migration and Its Influence

First I want to give an outline of the Meraki Techniques Supervisor (SM) utility. Techniques Supervisor is Meraki’s endpoint administration product. We help administration for a lot of completely 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 Techniques Supervisor, this administration all occurs by way of Meraki’s on-line interface known as Dashboard. Examples and code snippets talked about on this weblog are extra particular to the Android SM utility.

Migration of purposes to any SDK primarily contains 2 duties from the developer’s perspective. One is – how the appliance behaves when put in on a tool with an Android model aside 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 function, and its affect on the appliance are.

This doc focuses on among the modifications impacting builders with Android 14 migration. It additionally covers migration of the Techniques Supervisor app to Android 14, and challenges encountered in the course of 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 affect the UI of the appliance. Within the utility if font dimensions are declared utilizing sp (scaled pixel) items there are probabilities of minimal affect on the appliance as a result of Android framework would apply these scaling components. 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 dimension.

Background Course of Limitation

Android OS is independent to handle the sources effectively by improvising efficiency as properly. One of many pointers to attain the identical is by caching purposes within the background and solely when the system wants reminiscence these purposes will probably 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 individual utility.

Foreground Service Sorts

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

Among the new service sorts have been additionally launched in Android 14 – well being, remoteMessaging, shortService, specialUse and systemExempted. If service isn’t related to any of the kinds specified, then it is suggested to vary logic to make use of Workmanager or user-initiated knowledge switch jobs. MissingForegroundServiceTypeException will probably be thrown by the system in case service kind shouldn’t be specified.

Service kind permissions should be declared together with specifying the kind in service.

android:title="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 some other malicious apps. Additionally, all mutable pending intent should specify a element or bundle data to the intent, if not the system throws an exception.

Implicit intent needs to be export just like this:

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

If pending intent needs to be mutable, then element information should 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 secure, 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 machine. That is exempted for system broadcasts.

   requireContext(), receiver,intentFilter(),

Non-Dismissable foreground notifications

In Android 14 or increased, foreground notification might be dismissed by the consumer. However exceptions have been offered 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 will cease and fail silently. When App targets Android 14 and if the job exceeds the assured time on the primary thread, the app triggers an ANR with an error message “No response to onStartJob” or “No response to onStopJob”. It’s prompt 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 units and apps within the office. Additionally it is termed as Android for Work. It helps to handle and distribute non-public 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 increased. In Android 14 or increased, DPC apps obtain this intent which may carry the data to help both Absolutely managed mode or work profile mode.

wipeDevice – for resetting machine

Scope of wipeData is now restricted to profile homeowners solely. For apps focusing on Android 14 or increased, this technique would throw system error when known as in machine proprietor mode. New technique wipeDevice for use for resetting the machine 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 telephone numbers from private apps together with READ_CONTACTS permission.

To help setting contact entry coverage and callerID, beneath strategies are newly added;


Deprecated strategies

Beneath strategies are deprecated and as a substitute strategies specified within the earlier part needs to be used.


Challenges throughout Meraki Techniques 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 dimension 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 facility resetting the machine efficiently.
  • Profile data which might be fetched together with intent GET_PROVISIONING_MODE was additionally missed within the migration information. This was discovered in the course of the regression testing part.
  • requestSingleUpdate() of location supervisor at all times requires mutable pending for location updation. However nowhere within the documentation, it’s prescribed about it. On account of this there have been few utility crashes. Needed to determine this out throughout utility testing.

Helpful hyperlinks for reference



Supply hyperlink

We will be happy to hear your thoughts

      Leave a reply

      Easy Click Express
      Compare items
      • Total (0)
      Shopping cart