meldCX Android APK Preparation Checks

Prior to uploading your Android APK to the meldCX Cloud Console it is important that you do some basic app preparation checks. This is to ensure that your app will run soothly and not encounter any issues when running inside the meldCX Android environment.

To run a native Android apps on a meldCX device your APK must meet the following requirements:

Not Allowed	Reason
No <category android:name="android.intent.category.HOME"/> intent filter should be placed in any Activity in AndroidManifest.xml file	The Android app should not be the device’s home launcher app at any time. meldCX controls the device startup[ experience and will run your application when scheduled in the meldCX Cloud Console.
Any broadcast receiver listens to <action android:name="android.intent.action.BOOT_COMPLETED"/> should not start any foreground Activity	The start/stop of the your Android app should be scheduled and controlled by meldCX Android apps.
Signage Only Devices No user input should be requested (eg. launch the keyboard, button on the screen to click)	For signage based devices meldCX Android app doesn’t support user touch or any other interactions.
The app’s application id (package name) should not be started with com.meldcx or contain any words like meldcx.	com.meldcx or any string contains meldcx are reserved words in meldcx Android OS.
Change the device timezone	The device’s timezone is managed by meldcx apps.
Change the device’s orientation	The device screen orientation is managed by meldcx apps.
Change Internet connection settings (wifi or ethernet)	The device is connected to the Internet and the connection is managed by meldcx apps.
Schedule to start any other app	The start/stop of the your Android app should be scheduled in the meldCX Cloud Consol

Implementation requirement	Reason
The app should have the minSdkVersion as 25	The meldcx Android device is running Android OS 7.1 and above
Release any exclusive hardware resource (eg camera, Bluetooth) being used in the foreground and stop any heavy computation when it is put into the background.	The custom app will be put into the background when meldcx apps switch another app into the foreground which might require the same resources, also it will affect the device performance if the app is still doing heavy work when it’s in the background.
The app should be able to resume its normal state when it is launched from the background.	When the meldcx app is switching apps, the app might be waken up from the background, the app should be able to handle this scenario.
The app code obfuscation is optional