Non-Native Display Module for Android Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Android system terminal devices cannot run or display applications developed for non-Android systems, such as those written in C or C++ languages, due to compatibility issues with different system frameworks and plug-ins, limiting data processing efficiency and compatibility.
Innovation Solution
A display method is introduced that includes a non-native display module interface in the Android system, allowing the invocation of custom display modules based on non-Android systems, with dynamic loading to select appropriate display modules based on application refresh frequency, and hardware acceleration for efficient data transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the Android system uses its standard display framework to display applications, then the system maintains stability and ease of operation, but it cannot display applications developed for non-Android systems
Solution Approach 1:
The patent introduces a non-native display module as an intermediary component that sits between the Android system framework and non-Android applications. This module contains a non-Android system library that can load and execute application code from non-Android systems, while the Android framework continues to operate normally without modification. The non-native display module acts as a bridge that translates and adapts non-Android application interfaces to be compatible with the Android display framework, thereby enabling compatibility without increasing overall system complexity.
2Productivity
If applications written in Java are used, then compatibility with Android system is maintained, but data processing efficiency is reduced compared to C or C++ applications
Solution Approach 1:
The patent segments the application execution environment into two distinct parts: the Android system framework layer (written in Java) and the non-native application execution layer (capable of running C/C++ code). The non-native display module creates a separate execution context that can load native libraries and run high-performance C/C++ applications directly, while the Android framework continues to provide system-level compatibility. This segmentation allows applications to achieve high data processing efficiency through native code while the Android system maintains its compatibility through the framework layer.
3Adaptability or versatility
If multiple display modules are supported for different refresh frequencies, then adaptability to various application requirements is improved, but device complexity increases
Solution Approach 1:
The patent implements a dynamic display module selection mechanism where the system can load and switch between different display modules based on the specific requirements of each application. The non-native display module includes a dynamic loading capability that can determine the appropriate refresh frequency and load the corresponding display module at runtime. This dynamic approach allows the system to adapt to different application needs (high refresh rate for games, standard rate for general apps) without permanently maintaining multiple display modules, thereby reducing overall system complexity while preserving adaptability.
Data Source
AI summary
A display method of multi-application based on an Android system and a terminal device are provided. The display method includes: upon reception of a first instruction, determining whether a first application is a non-Android application, where the first instruction is configured to start the first application; when the first application is the non-Android application, invoking a non-native display module; and drawing a display interface of the first application based upon the non-native display module.