- About this guide
- BlackBerry Dynamics background
- BlackBerry Dynamics API reference
- FIPS 140-2 compliance
- Easy Activation
- Securing cut-copy-paste on devices (Data Leakage Prevention, or DLP)
- Shared Services Framework
- Support for fingerprint authentication
- Support for client certificates
- Support for the "Do not require password" setting
- Bypassing the App Lock screen
- BlackBerry Dynamics contributor code on GitHub
- Supported languages
- BlackBerry Dynamics software versions
- Requirements
- Compatibility with earlier releases
- Software requirements
- BlackBerry Dynamics entitlement ID and version
- Supported launchModes
- Compatibility with the BlackBerry Dynamics Launcher Library
- Supported CPU architectures
- Supported and unsupported Android and third-party features
- FIPS-linking on Android: automatic
- Restricted key prefix
- Steps to get started with the BlackBerry Dynamics SDK
- Installing the BlackBerry Dynamics SDK for Android
- Integrating the BlackBerry Dynamics SDK in .aar format
- Using the branding API to add a custom logo and colors
- Info: Add Samsung Pass to your BlackBerry Dynamics app
- Info: APIs for secure clipboard management
- Info: Preventing autobackup to Google Drive
- Info: APIs for network status
- BlackBerry Dynamics SDK for Android: Wearable Framework
- Programming with the BlackBerry Dynamics SDK and BlackBerry Enterprise Mobility Server services
- Sample apps
- Testing and troubleshooting
- Readying your app for deployment: server setup
- Details of support for client certificates
Logging and diagnostics
The processing activity of the
BlackBerry Dynamics Runtime
is logged by the
runtime itself. The activity log is written to the BlackBerry
Dynamics
secure container
on the device after deployment. You might be asked to provide the log file to the BlackBerry
Dynamics
technical support
team, but this is typically only necessary for complex support issues.