CN115080158B - Interface display method, device, terminal equipment and computer readable storage medium - Google Patents

Abstract

The embodiment of the application discloses an interface display method, a device, terminal equipment and a computer readable storage medium, wherein the method is applied to the terminal equipment and comprises the following steps: when a first operating system in a terminal device receives a system switching request sent by a second operating system, the first operating system loads a first display module in the first operating system according to the system switching request; in the process of loading the first display module by the first operating system, rendering the display interface by the first operating system, and writing display data of the display interface into a shared display buffer area; and the second operating system acquires display data from the shared display buffer area and controls the screen to display a display interface according to the display data. The interface display method, the device, the terminal equipment and the computer readable storage medium can greatly improve the conditions of picture blocking, discontinuous display and the like when the operating system is switched.

Description

Interface display method, device, terminal equipment and computer readable storage medium

Technical Field

The present application relates to the field of computer technology, and in particular to an interface display method, device, terminal equipment and computer-readable storage medium.

Background technique

In order to meet the different needs of more users for terminal devices, many terminal devices that support multiple operating systems have appeared on the market. Terminal devices can be installed with multiple operating systems. When users use fewer functions, terminal devices can choose to run operating systems with lower power consumption, and run operating systems with rich functions but higher power consumption when users have needs, thereby improving the endurance of terminal devices. However, when current terminal devices switch operating systems, the switching process takes a long time, resulting in freezes and discontinuous displays on the terminal device screen.

Summary of the invention

The embodiments of the present application disclose an interface display method, apparatus, terminal device and computer-readable storage medium, which can greatly improve the situation of screen freeze or discontinuous display when switching operating systems.

The present application embodiment discloses an interface display method, which is applied to a terminal device, and the method includes:

When the first operating system in the terminal device receives a system switching request sent by a second operating system, the first operating system loads a first display module in the first operating system according to the system switching request, wherein the second operating system is an operating system currently running in the terminal device;

During the process of the first operating system loading the first display module, the first operating system renders a display interface and writes display data of the display interface into a shared display buffer area, where the shared display buffer area is a display buffer area shared between the first operating system and the second operating system;

The second operating system obtains the display data from the shared display buffer area, and controls the screen to display the display interface according to the display data.

The embodiment of the present application discloses an interface display device, which is applied to a terminal device, and the device includes:

a loading module, configured to load the first display module in the first operating system through the first operating system when the first operating system in the terminal device receives a system switching request sent by the second operating system, wherein the second operating system is the operating system currently running in the terminal device;

a rendering module, configured to render a display interface through the first operating system during the process of the first operating system loading the first display module, and write display data of the display interface into a shared display buffer area, wherein the shared display buffer area is a display buffer area shared between the first operating system and the second operating system;

The display module is used to obtain the display data from the shared display buffer area through the second operating system, and control the screen to display the display interface according to the display data.

An embodiment of the present application discloses a terminal device, including a memory and a processor, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the processor implements the method described above.

An embodiment of the present application discloses a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the method described above is implemented.

The interface display method, apparatus, terminal device and computer-readable storage medium disclosed in the embodiments of the present application, when the first operating system in the terminal device receives a system switching request sent by the second operating system, the first operating system loads the first display module in the first operating system according to the system switching request. During the process of the first operating system loading the first display module, the first operating system renders the display interface and writes the display data of the display interface into a shared display cache area. By establishing a shared display cache area between the first operating system and the second operating system, when the system is switched, the first operating system to be switched in renders the display interface and writes it into the shared display cache area, and then the second operating system to be switched out obtains the display data from the shared display cache area and controls the screen display. There is no need to wait for the first display module of the first operating system to be loaded before the display interface rendered by the first operating system can be displayed. This can greatly improve the screen freeze or display discontinuity that occurs when the operating system is switched, and achieve continuous, smooth and seamless switching of the interface display.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

FIG1 is an application scenario diagram of an interface display method in one embodiment;

FIG2 is a system architecture diagram of a terminal device in one embodiment;

FIG3 is a flow chart of an interface display method in one embodiment;

FIG4 is a schematic diagram of a screen display of a terminal device in one embodiment;

FIG5 is a flow chart of an interface display method in another embodiment;

FIG6 is a flow chart of an interface display method in another embodiment;

FIG7 is a schematic diagram of display interfaces corresponding to different applications in one embodiment;

FIG8A is a timing diagram of switching from the second operating system to the first operating system in one embodiment, where the second operating system uses a shared display buffer;

FIG8B is a timing diagram of switching from the second operating system to the first operating system, in which the first operating system uses a shared display buffer, in one embodiment;

FIG9 is a schematic diagram of a second operating system controlling a screen to display a dynamic display interface in one embodiment;

FIG10 is a block diagram of an interface display device in one embodiment;

FIG. 11 is a structural block diagram of a terminal device in one embodiment.

Detailed ways

The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

It should be noted that the terms "including" and "having" and any variations thereof in the embodiments of the present application and the accompanying drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device including a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products or devices.

It is understood that the terms "first", "second", etc. used in this application may be used herein to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish a first element from another element. For example, without departing from the scope of this application, a first operating system may be referred to as a second operating system, and similarly, a second operating system may be referred to as a first operating system. Both the first operating system and the second operating system are operating systems, but they are not the same operating system.

FIG1 is an application scenario diagram of an interface display method in an embodiment. As shown in FIG1 , the interface display method in the embodiment of the present application can be applied to a terminal device that supports multiple operating systems, and the terminal device may include but is not limited to a smart phone 10, a smart wearable device 20, a tablet computer, a laptop computer, a vehicle terminal, a PC (Personal Computer), etc. At least two operating systems may be installed in the terminal device. For example, the terminal device may be installed with an embedded operating system (such as RTOS (Real Time Operating System, real-time operating system)) and an intelligent operating system (such as IOS system, Android system, etc.), or multiple intelligent operating systems or multiple embedded systems may be installed at the same time. The specific operating system installed on the terminal device is not limited in the embodiment of the present application.

In some embodiments, the terminal device may include multiple processors, or may include a multi-core processor, for example, may include a dual-core processor, a quad-core processor, etc., so that different operating systems can be run through different processors, or through different cores in the same processor.

In related technologies, the switching process of a terminal switching between different operating systems usually includes the following stages: a wake-up stage of waking up the operating system to be switched in, a loading stage of loading a display module of the operating system to be switched in, and if an application needs to be started, a startup stage of the operating system to be switched in starting the application, etc. The entire switching process takes a long time. The interface of the operating system to be switched in can only be displayed normally after the system switching is completed, which may cause the screen of the terminal device to freeze and display discontinuity during the switching process.

The embodiments of the present application disclose an interface display method, apparatus, terminal device and computer-readable storage medium. By establishing a shared display cache area between a first operating system and a second operating system, when a system switch is performed, the first operating system to be switched in renders a display interface and writes display data into the shared display cache area, and then the second operating system to be switched out obtains the display data from the shared display cache area and controls the screen display. There is no need to wait for the first display module of the first operating system to be loaded before displaying the display interface rendered by the first operating system. This can greatly improve the screen freeze or display discontinuity that occurs when the operating system is switched, and achieve continuous, smooth and seamless switching of the interface display.

FIG2 is a system architecture diagram of a terminal device in an embodiment. As shown in FIG2 , an operating system A and an operating system B may be installed in the terminal device, and the operating system A may include an application layer, a framework layer, and a kernel layer, etc. Among them, the application layer may be installed with one or more applications. The framework layer may provide corresponding interfaces or services for the operation of the operating system A and the operation of each application in the application layer. Optionally, the framework layer may include system services, dual-core communication services, switching services, interface services, etc. The system service may provide various functional interfaces for applications such as application startup, loading and running. The operating system A may communicate with the operating system B through the dual-core communication service, and may realize message control, function control, etc. during the operating system switching process through the switching service. The interface service may provide interfaces for display data control, etc. The kernel layer may include the kernel of the operating system A and various hardware drivers, such as display drivers, camera drivers, sensor drivers, etc. The kernel of the operating system A may be used to provide the most basic functions of the operating system A.

The B operating system may be similar to the A operating system. The B operating system may also include an application layer, a framework layer, and a kernel layer. The B operating system may communicate with the A operating system through a dual-core communication service, and implement message control, function control, etc. during the operating system switching process through a switching service.

In an embodiment of the present application, the terminal device can establish a shared display cache area between operating system A and operating system B. When either operating system receives a system switching request sent by the other operating system, the operating system to be switched out can obtain the display data filled by the operating system to be switched in from the shared display cache area, and control the screen for display.

Taking the switching from operating system B to operating system A as an example, when operating system A receives a system switching request sent by operating system B, operating system A can load the display module in operating system A according to the system switching request. The display module may include a display driver and display-related interface services in the framework layer. Only when the display module is loaded can operating system A control the screen for display through the display module.

During the process of operating system A loading the display module, operating system A can render the display interface and write the display data of the display interface into the shared display buffer area. Furthermore, operating system A can write the display data of the display interface into the shared display buffer area of operating system B through the dual-core communication service. Operating system B can obtain the display data from the shared display buffer area and control the screen to display the display interface rendered by operating system A according to the display data. Before the display module of operating system A is loaded, operating system B controls the screen display in advance, and there is no need to wait for the display module of operating system A to be loaded before displaying the display interface rendered by operating system A, which can greatly improve the screen freeze or discontinuous display when switching operating systems.

It should be noted that FIG. 2 only shows a system architecture diagram of a terminal device in one embodiment, and the system architecture of the terminal device may also be other architectures, which is not limited here.

As shown in FIG3 , in one embodiment, an interface display method is provided, which can be applied to the above-mentioned terminal device. The method may include the following steps:

Step 310: When the first operating system in the terminal device receives a system switching request sent by the second operating system, the first operating system loads a first display module in the first operating system according to the system switching request.

The second operating system may refer to the operating system currently running in the foreground of the terminal device, that is, the operating system to be switched out, wherein the operating system running in the foreground may refer to an operating system that can directly interact with the user through a screen display interface, and the user can directly see the interface displayed by the operating system through the screen of the terminal device. The first operating system may refer to the operating system to be switched in. When the second operating system detects a system switching operation, it may trigger the generation of a system switching request and send the system switching request to the first operating system.

Optionally, the system switching operation can be an operation actively triggered by the user, such as the user actively switching the operating system, the user clicking to start the application of the first operating system, etc.; the system switching operation can also be a switching operation actively triggered by the terminal device according to the actual operating conditions. For example, when the application of the first operating system receives a push message, it can send a notification triggering the system switching operation to the second operating system, and the second operating system generates a system switching request based on the notification triggering the system switching operation.

In some embodiments, when the second operating system is running, the first operating system may be in a dormant state, thereby reducing the power consumption of the terminal device. When the first operating system receives a system switching request sent by the second operating system, the first operating system may be awakened based on the system switching request and load the first display module in the first operating system, wherein the dormant state may refer to the data of the first operating system being stored in the memory, the processing core or processor corresponding to the first operating system being partially or completely powered off, and other associated hardware (such as a hard disk, etc.) may also be in a power-off state. The first display module may include a display driver in the first operating system, and connections or services related to screen display, etc. The first operating system loading the first display module may include the first operating system loading the display driver, connections or services related to screen display, etc., and may initialize and configure the display bus controller and the screen, etc. Only after the first display module is loaded, the display interface rendered in the first operating system can be output to the screen for display.

Step 320 , when the first operating system loads the first display module, the first operating system renders the display interface and writes the display data of the display interface into the shared display buffer area.

In related technologies, the first operating system needs to wait until the first display module is loaded before rendering the display interface and controlling the screen to display through the first display module. However, since the loading process of the first display module takes a long time, screen freezes and discontinuous displays are prone to occur, causing users to mistakenly believe that the terminal device has a system freeze, affecting the user's experience of using the terminal device.

In the embodiment of the present application, the first operating system can directly render the display interface during the process of loading the first display module. The display interface can be the system interface of the first operating system, the main interface of the application started by the first operating system, or a pre-set transition interface for operating system switching, etc., but is not limited thereto. The first operating system renders the display interface to obtain one or more frames of display data of the display interface, and writes the display data into the shared display buffer area.

The shared display cache area can be a display cache area shared between the first operating system and the second operating system. Both the first operating system and the second operating system have access rights to the shared display cache area. Both the first operating system and the second operating system can write display data to the shared display cache area and obtain display data from the shared display cache area.

In some embodiments, the shared display cache area may be the same storage area in the terminal device that can be used by the first operating system and the second operating system. The shared display cache area may also be respectively set with a first storage area corresponding to the first operating system and a second storage area corresponding to the second operating system. The first storage area and the second storage area may be independent storage areas. The first operating system may send display data to the second storage area corresponding to the second operating system through inter-system communication, and the second operating system may also send display data to the first storage area corresponding to the first operating system through inter-system communication. There may be many different ways of communication between the systems. For example, communication may be performed using a dual-core communication service or through a shared memory bus.

The first operating system may send the display data of the rendered display interface to the shared display buffer area of the second operating system through the communication between systems, and the shared display buffer area of the second operating system stores the display data.

Step 330: The second operating system obtains display data from the shared display buffer area, and controls the screen to display a display interface according to the display data.

The second operating system can obtain the display data written by the first operating system from the shared display buffer area, and control the screen to display the corresponding display interface through the second display module in the second operating system. Since the second operating system is always in operation, the second display module in the second operating system can send the display data to the screen for display without loading, thereby achieving the effect of immediately displaying the display interface rendered by the first operating system, and ensuring the continuity of the display screen.

If the first operating system continuously writes display data to the shared display buffer of the second operating system, the second operating system can sequentially obtain display data from the shared display buffer, and control the screen to continuously refresh and display a display interface corresponding to the obtained display data.

FIG4 is a schematic diagram of the screen display of a terminal device in an embodiment. Exemplarily, as shown in FIG4 , interface 402 is the interface currently displayed by the second operating system, and interface 404 is the system interface of the first operating system. After the first operating system receives the system switching request sent by the second operating system, in the process of loading the first display module, interface 404 can be rendered, and the display data of interface 404 obtained by rendering can be written into the shared display buffer of the second operating system. The second operating system can obtain the display data of interface 404 from the shared display buffer, and control the screen display interface 404 according to the display data. There is no need to wait until the first operating system completes loading the first display module before the screen of the terminal device can display interface 404. Instead, the second operating system prompts the display interface 404, which can greatly improve the screen freeze or discontinuous display when switching operating systems, and realize continuous, smooth and seamless switching of interface display.

In some embodiments, when the first display module in the first operating system is loaded, the first operating system may stop writing the display data of the rendered display interface to the shared display buffer area, and control the screen to display the rendered display interface through the first display module. After the first display module is loaded, the terminal device may switch back to the normal display process of the first operating system, and the first operating system may no longer write display data to the shared display buffer area of the second operating system, but directly send the display data of the rendered display interface to the screen through the first display module, and control the screen to display.

In some embodiments, when the first display module in the first operating system is loaded, the first operating system may send a first message to the second operating system, and the first message may be used to notify the second operating system that the switch is complete. The second operating system may stop acquiring display data from the shared display buffer area according to the first message and enter a dormant state. After receiving the first message sent by the first operating system, the second operating system may stop acquiring display data from the shared display buffer area and stop controlling the screen for display. The first operating system takes over the control authority of the screen and returns to the normal screen display process of the first operating system.

It should be noted that, in the embodiment of the present application, only the interface display of switching from the second operating system to the first operating system is described, and the method flow of switching from the first operating system to the second operating system can be similar to the method flow of switching from the second operating system to the first operating system, and will not be repeated here. In addition, a third operating system and a fourth operating system can also be installed in the terminal device, and the switching between any two operating systems can refer to the method flow description of switching from the second operating system to the first operating system, and the embodiment of the present application does not limit the specific operating system.

In an embodiment of the present application, when the first operating system in the terminal device receives a system switching request sent by the second operating system, the first operating system loads the first display module in the first operating system according to the system switching request. During the process of the first operating system loading the first display module, the first operating system renders the display interface and writes the display data of the display interface into a shared display cache. By establishing a shared display cache between the first operating system and the second operating system, when the system is switched, the first operating system to be switched in renders the display interface and writes it into the shared display cache, and then the second operating system to be switched out obtains the display data from the shared display cache and controls the screen display. There is no need to wait for the first display module of the first operating system to be loaded before the display interface rendered by the first operating system can be displayed. This can greatly improve the screen freeze or display discontinuity that occurs when the operating system is switched, and achieve continuous, smooth and seamless switching of the interface display.

As shown in FIG5 , in one embodiment, another interface display method is provided, which can be applied to the above-mentioned terminal device. The method may include the following steps:

Step 502: When the first operating system in the terminal device receives a system switching request sent by the second operating system, the first operating system wakes up the system service according to the system switching request.

The framework layer of the first operating system may include multiple services, which may include but are not limited to system services, switching services, dual-core communication services, interface services, etc. Each service may provide a variety of interfaces for applications in the application layer, so that each application can use the system functions of the first operating system or the hardware of the terminal device by calling the interface or service. The system service may provide a control interface for the system layer of the first operating system, such as power management services, window management services, etc., but is not limited thereto.

When the terminal device is not running the first operating system, the first operating system may be in a dormant state. When the first operating system receives a system switching request sent by the second operating system, the first operating system may wake up the system service according to the system switching request.

Exemplarily, taking the first operating system as the Android operating system, when the Android operating system receives a system switching request sent by other operating systems, a wakelock can be created to wake up system services such as AMS (Activity Manager Service), WMS (Window Manager Service) and/or PMW (PowerManage Service). The wakelock is a lock mechanism in the Android operating system. As long as the wakelock is held, the Android operating system cannot enter a sleep state.

Step 504: The first operating system sends a loading instruction to the interface service through the system service.

After the system service of the first operating system is awakened, the system service can communicate with the interface service and send a loading instruction to the interface service. The interface service can be used to implement functions such as establishing, controlling and managing the interface. The loading instruction can be used to instruct the interface service to load the first display module.

Step 506: After receiving the loading instruction, the interface service immediately returns a preparation instruction to the system service, and loads the first display module according to the loading instruction. The preparation instruction is used to instruct the system service to render the display interface.

After the interface service receives the loading instruction, since the loading of the first display module takes a long time, the interface service can immediately return a preparation instruction to the system service, and the preparation instruction can be used to inform the system service that the first display module is "ready". After the interface service sends the preparation instruction, the first display module can be abnormally continued to be loaded. After the system service receives the preparation instruction returned by the interface service, the first operating system can normally start to request to render the display interface.

For example, taking the first operating system as an Android operating system, after the system services such as AMS, WMS, and PMW of the Android operating system are awakened, SurfaceFlinger can be called through SurfaceFlinger.setDisplayPowerMode to enable SurfaceFlinger to load the first display module. The SurfaceFlinger is an interface service in the Android operating system and can be used to control the interface display.

Step 508: The first operating system sends a start shared display buffer area message to the interface service through the switching service. The start shared display buffer area message is used to instruct the interface service to write the display data of the rendered display interface into the shared display buffer area.

The switching service in the first operating system can be used to control the switching function between systems. After the interface service returns the preparation instruction and the first operating system starts to render the display interface, the switching service can send a message to start the shared display buffer area to the interface service. After receiving the message, the interface service can write the display data of the rendered display interface into the shared display buffer area of the second operating system according to the message. Furthermore, the interface service can be sent to the second operating system through the dual-core communication service and written into the shared display buffer area in the second operating system.

While the interface service is controlling the rendered display data, the interface service is also loading the first display module. The interface service can establish two threads to execute different tasks in the interface service. The first display module is loaded through the first thread, and the display data is sent to the shared display buffer area of the second operating system through the second thread. The dual-thread working mode will not affect each other and can ensure that the two are carried out simultaneously, thereby improving the working efficiency of the interface service.

In some embodiments, the step of writing display data of the display interface into a shared display cache may include: when the first operating system receives a second message sent by the second operating system, writing the display data of the display interface into the shared display cache according to the second message, and the second message is used to indicate that the second operating system has enabled the shared display cache.

After the second operating system sends a system switching request to the first operating system and receives a confirmation message from the first operating system, the second operating system can prepare to enable the shared display cache to refresh the screen. The second operating system can send a second message to the first operating system through the dual-core communication service. After receiving the second message, the first operating system determines that the second operating system has completed the switching preparation, and sends a message to start the shared display cache to the interface service through the switching service. The interface service writes the display data of the display interface into the shared display cache of the second operating system. The first operating system writes the display data to the shared display cache only after receiving the second message indicating that the second operating system has enabled the shared display cache. This ensures that the second operating system can normally and accurately read the display data from the shared display cache and control the screen for display, further ensuring the smoothness of the screen display.

Step 510: The second operating system obtains display data from the shared display buffer area, and controls the screen to display a display interface according to the display data.

Step 510 may refer to the relevant description of step 330 in the above embodiment, which will not be repeated here.

In some embodiments, after the second operating system sends a system switching request to the first operating system, the screen can be controlled to display an initial transition screen according to the stored interface resources. Optionally, the stored interface resources can be the display interface displayed in the first frame during the system switching process. After waiting for the first duration, the second operating system can obtain the display data written by the first operating system from the shared display buffer area, and control the screen to display the display interface according to the display data. The first duration can be set according to actual needs, such as 30 milliseconds or 20 milliseconds, so as to reduce the time the second operating system waits for the first operating system to render and write the display data of the first frame display interface, and better realize the continuity and seamless switching of the screen. In addition, the second operating system only stores the interface resources of the initial transition screen, which will not occupy too much storage space of the second operating system, thereby ensuring the system performance of the second operating system.

Step 512, when the first display module is loaded, the first operating system sends a stop shared display cache message to the interface service through the switching service. The stop shared display cache message is used to instruct the interface service to stop writing the display data of the rendered display interface into the shared display cache, and control the screen to display the rendered display interface through the first display module.

When the first display module in the first operating system is loaded, the first operating system may stop writing the display data of the rendered display interface into the shared display buffer. In some embodiments, after monitoring that the first display module has been loaded, the switching service in the first operating system may send a stop shared display buffer message to the interface service. After receiving the stop shared display buffer message, the interface service may stop writing the display data of the rendered display interface into the shared display buffer according to the stop shared display buffer message, and resume the normal display process. The interface service may control the screen to display the rendered display interface through the first display module.

Optionally, the switching service of the first operating system may also send a first message to the second operating system via the dual-core communication service, indicating that the first display module has been loaded. The second operating system may stop obtaining display data from the shared display buffer area according to the first message and enter a sleep state.

In an embodiment of the present application, multiple services in the first operating system and the second operating system cooperate with each other to control the interface display during the system switching process, so that when the system is switched, the display interface rendered by the first operating system is displayed in advance by the second operating system, and there is no need to wait for the first display module of the first operating system to be loaded before the display interface rendered by the first operating system can be displayed. This can greatly improve the screen freeze or display discontinuity that occurs when the operating system is switched, and achieve continuous, smooth and seamless switching of the interface display.

As shown in FIG6 , in one embodiment, another interface display method is provided, which can be applied to the above-mentioned terminal device, and the method may include the following steps:

Step 602: When the second operating system detects an application startup operation for a target application, in response to the application startup operation, a system switching request is sent to the first operating system, where the system switching request includes an application identifier of the target application.

When the terminal device is running the second operating system, one or more application icons of the target application may be displayed in the interface of the second operating system. The target application may refer to an application that needs to be run by the first operating system. For example, if the first operating system is a function-rich but high-power operating system, the target application may be a game application, a video application, or other application that requires complex functions; the target application may also be an application installed in the first operating system. The user may trigger the start of the target application in the interface of the second operating system. When the second operating system detects an application start operation for the target application, it may generate a system switching request based on the application identifier of the target application and send the system switching request to the first operating system. The system switching request may be used to request the first operating system to start the target application. The application identifier may include, but is not limited to, information such as the application number, the package name of the application, and the version number of the application.

Step 604: the first operating system starts and loads the target application according to the application identifier in the system switching request, and simultaneously loads the first display module in the first operating system.

After receiving the system switching request, the first operating system may parse the system switching request to obtain the application identifier of the target application, and start and load the target application according to the application identifier, and simultaneously load the first display module in the first operating system. In some embodiments, after the first operating system wakes up the system service according to the system switching request, the system service may create an active process, and start and load the target application in the active process, and simultaneously load the first display module through the interface service.

Step 606, when the first operating system starts and loads the target application and synchronously loads the first display module, the first operating system renders the display interface corresponding to the target application and writes the display data of the display interface into the shared display buffer area.

The display interface rendered by the first operating system may be a display interface corresponding to the target application. For example, the display interface may be a startup interface, a main interface, etc. of the target application. The display interfaces corresponding to different applications may be different and may be designed by the developers of each application. During the process of starting and loading the target application and loading the first display module, the first operating system may render the display interface corresponding to the started target application through a rendering engine, etc., to obtain display data of the display interface corresponding to the target application. The interface service may send the rendered display data to the shared display buffer in the second operating system.

Step 608: The second operating system obtains display data from the shared display buffer area, and controls the screen to display a display interface corresponding to the target application according to the display data.

The second operating system can obtain display data from the shared display buffer area, and send the display data to the screen for display through the second display module, and control the screen to display the display interface corresponding to the target application, so there is no need to wait for the first operating system to start and load the target application, and load the first display module, before the display interface can be displayed, so as to achieve continuous and seamless system switching. Different applications are started, and different display interfaces are displayed, which can improve the richness of the interface and the visual effect of the interface display.

FIG7 is a schematic diagram of display interfaces corresponding to different applications in an embodiment. For example, as shown in FIG7, when a user triggers the start of a call application that needs to be run on the first operating system, the second operating system can control the screen display interface 702 according to the display data obtained from the shared display buffer area; when a user triggers the start of a heart rate measurement application that needs to be run on the first operating system, the second operating system can control the screen display interface 704 according to the display data obtained from the shared display buffer area; when a user triggers the start of a sleep monitoring application that needs to be run on the first operating system, the second operating system can control the screen display interface 706 according to the display data obtained from the shared display buffer area. Different applications can be started and different interfaces can be displayed.

When the first operating system monitors that the target application is started and loaded, and the first display module is loaded, the first operating system can stop writing the display data of the rendered display interface into the shared display buffer area, and control the screen to display the interface of the target application through the first display module. The second operating system can stop obtaining display data from the shared display buffer area and enter a dormant state, completing the system switch, and the user can use the target application normally.

In some embodiments, the display interface rendered by the first operating system may also be a fixedly designed transition display interface. For any application that is launched, the transition display interface may be consistent, or the user may select a favorite image as the transition display interface, which will be displayed each time the operating system is switched.

In the embodiment of the present application, the first operating system can render the display interface corresponding to the target application according to the launched target application, and the second operating system will first display the display interface when the target application is not launched and loaded, thereby reducing the visual waiting time of the user, preventing the user from having the false impression of system freeze, and achieving continuous, smooth and seamless switching of the interface display. Different launched applications will display different display interfaces, which can improve the richness of the interface and the visual effect of the interface display.

To better illustrate the communication interaction process between the first operating system and the second operating system in the embodiment of the present application, please refer to Figure 8A and Figure 8B. Figure 8A is a timing diagram of switching from the second operating system to the first operating system in one embodiment, and the second operating system uses a shared display buffer area; Figure 8B is a timing diagram of switching from the second operating system to the first operating system in one embodiment, and the first operating system uses a shared display buffer area.

As shown in FIG8A , when switching from the second operating system 810 to the first operating system 820 , the timing steps of the second operating system 810 using the shared display buffer may include:

1. The user triggers the start of a target application of the first operating system 820 in the second operating system 810. The second operating system 810 detects the trigger operation and sends a message to the switching service 812 requesting the start of the target application of the first operating system 820.

2. The switching service 812 of the second operating system 810 initiates the system switching process, and sends a message requesting to start the target application (i.e., the above-mentioned system switching request) to the first operating system through the dual-core communication service 816 in the second operating system 810; after receiving the request message, the first operating system 820 replies with a confirmation message (ack message), wakes up the relevant system services, starts and loads the target application, and loads the first display module.

3. The switching service 812 of the second operating system 810 sends a message to the display driver 814 to start using the shared display buffer area to refresh the screen, and after the switching service 812 returns a confirmation message, it sends a switching preparation completion message (i.e., the above-mentioned second message) to the first operating system through the dual-core communication service 816; after receiving the switching preparation completion message, the first operating system 820 replies with a confirmation message and notifies the interface service to send the rendered display data to the shared display buffer area of the second operating system 810.

4. The first operating system 820 sends display data to the second operating system 810. The second operating system 810 receives the display data sent by the first operating system 820 through the dual-core communication service 816, and writes the display data into the shared display buffer area of the second operating system 810. The display driver 814 of the second operating system 810 no longer uses the display data of the system interface, but obtains the written display data from the shared display buffer area and controls the screen to continuously refresh the display.

5. When the target application of the first operating system 820 is started and loaded, and the first display module is loaded, the first operating system 820 sends a message that the target application is started and loaded (i.e., the first message mentioned above). After receiving the message that the target application is started and loaded sent by the first operating system 820 through the dual-core communication service 816, the switching service 812 replies a confirmation message to the first operating system 820.

6. The switching service 812 sends a message to the display driver 814 to stop using the shared display buffer to refresh the screen, and the display driver 814 stops obtaining display data from the shared display buffer.

7. The first operating system 820 takes over the control of the screen, notifies the interface service to stop sending display data to the shared display buffer of the second operating system 810, and refreshes the display normally.

As shown in FIG. 8B , when switching from the second operating system 810 to the first operating system 820 , the timing steps of the first operating system 820 using the shared display buffer may include:

1. The switching service 828 in the first operating system 820 receives the message sent by the second operating system 810 requesting to start the target application through the dual-core communication service 822, and replies a confirmation message to the second operating system 810 through the dual-core communication service 822. The switching service 828 in the first operating system 820 can create the relevant system service 826 in the WakeLock wake-up system according to the message requesting to start the target application.

2. The system service 826 may send a loading instruction such as sf.setDisplayPowerMode to the interface service 824. After receiving the loading instruction, the interface service 824 immediately returns a preparation instruction to the system service and continues to load the first display module asynchronously.

3. The switching service 828 starts to start the target application, and the system service 826 normally requests the display buffer (acquireBuffer) and the message display buffer (releaseBuffer) from the interface service 824, so as to render the display interface and obtain the display data, but the display interface is not actually displayed.

4. The second operating system 810 sends a switching preparation completion message to the first operating system 820. After receiving the switching preparation completion message through the dual-core communication service 822, the switching service 828 of the first operating system 820 replies a confirmation message to the second operating system 810 through the dual-core communication service 822. The switching service 828 may send a start shared display buffer area message to the interface service 824, and the interface service 824 writes the rendered display data to the shared display buffer area of the second operating system through the dual-core communication service 822.

5. The second operating system 810 obtains display data from the shared display buffer area and continuously controls the screen to refresh the display.

6. After the switching service 828 monitors that the target application has started (Activity Ready), since the first display module and the target application are in synchronous timing, the first display module is indeed loaded. Then, a message to stop sharing the display cache area can be sent to the interface service 824. The interface service 824 stops sending display data according to the message to stop sharing the display cache area.

7. The switching service 828 sends a message to the second operating system 810 through the dual-core communication service 822 that the target application is started and loaded. After receiving the message, the second operating system 810 returns a confirmation message, stops obtaining display data from the shared display cache, and stops refreshing the screen.

8. The first operating system 820 resumes normal screen refresh display, and the switching service 828 sends a normal refresh message to the interface service 824 to completely enter the interface of the target application started in the first operating system 820.

In an embodiment of the present application, a shared display cache area is established between the first operating system and the second operating system. When the system is switched, the first operating system to be switched in renders the display interface and writes it into the shared display cache area, and then the second operating system to be switched out obtains the display data from the shared display cache area and controls the screen display. There is no need to wait for the first display module of the first operating system to be loaded before displaying the display interface rendered by the first operating system. This can greatly improve the screen freeze or display discontinuity that occurs when switching operating systems, and achieve continuous, smooth and seamless switching of the interface display.

In some embodiments, the step of the first operating system rendering the display interface and writing the display data of the display interface into a shared display cache may include: the first operating system renders the display interface according to the designed dynamic display style, obtains the display data of multiple frames of the display interface, and writes the display data of the multiple frames of the display interface into the shared display cache.

The display interface displayed during the system switching process can be a display interface with animation effects. The first operating system can render the display interface according to the designed dynamic display style to obtain display data of multiple frames of the display interface. Optionally, the dynamic display style can be used to represent the animation display style of the display interface. For example, the dynamic display style may include a fade-in and fade-out style, a jitter trajectory style, a gradual zoom-in style, a gradual zoom-out style, etc.

In some embodiments, the shared display buffer may include multiple buffer sub-blocks. The first operating system writes the display data of multiple frames of display interfaces into the shared display buffer, which may include: the first operating system writes the display data of each frame of the display interface into the buffer sub-block of the shared display buffer in sequence according to the display timing of each frame of the display interface, and each buffer sub-block corresponds to the display data of one frame of the display interface.

The dynamic display style can be set with the display style of each frame of the display interface, and the display style may include but is not limited to the display content, interface size, and the position of the interface in the screen. Each frame of the display interface may correspond to a different display timing, and the display interface is displayed frame by frame according to the display timing to form a display interface with an animation effect. The shared display buffer area may include multiple cache sub-blocks, each of which can be used to store the display data of a frame of the display interface. The interface service in the first operating system can write the display data of each frame of the display interface into each cache sub-block of the shared display buffer area of the second operating system in sequence through the dual-core communication service.

The second operating system can obtain the display data of each frame of the display interface from the shared display buffer area one by one, and control the screen to display the display interface with a dynamic display style according to the display data of each frame of the display interface obtained. Furthermore, the second operating system can obtain the display data of each frame of the display interface from each cache sub-block in the shared display buffer area one by one and send it to the screen, thereby controlling the screen to continuously refresh and display each frame of the display interface, forming an animation effect, and enriching the display style of the interface.

FIG9 is a schematic diagram of a second operating system controlling a screen to display a dynamic display interface in an embodiment. As shown in FIG9 , the second operating system can read the first frame display data from the first cache sub-block of the shared display cache area, and control the screen to display the first frame display interface 902 according to the first frame display data, can read the second frame display data from the second cache sub-block of the shared display cache area, and control the screen to display the second frame display interface 904 according to the first frame display data, can read the third frame display data from the third cache sub-block of the shared display cache area, and control the screen to display the third frame display interface 906 according to the third frame display data. From the first frame display interface 902 to the third frame display interface 906, a dynamic and gradually enlarged display effect can be formed.

In an embodiment of the present application, a shared display cache area is established between the first operating system and the second operating system. When the system is switched, the display interface is rendered by the first operating system to be switched in and written into the shared display cache area. There is no need to pre-set the display data of the dynamic transition display interface in the second operating system, which can reduce the consumption of storage space and facilitate each application in the first operating system to update the display interface according to demand, thereby improving the overall performance of the terminal device.

It should be noted that in addition to establishing a shared display cache area between the first operating system and the second operating system to solve problems such as screen freezes or discontinuous display when the terminal device switches operating systems, the first operating system and the second operating system can also share a set of display modules, using the same display driver and adapter interface, services, etc. When switching operating systems, since the shared display module is always in use and does not need to be reloaded, the waiting time for loading can be directly avoided, so as to achieve continuous, smooth and seamless switching of interface display.

As shown in FIG10 , in one embodiment, an interface display device 1000 is provided, which can be applied to the above-mentioned terminal device. The interface display device 1000 may include: a loading module 1010 , a rendering module 1020 and a display module 1030 .

The loading module 1010 is used to load the first display module in the first operating system through the first operating system when the first operating system in the terminal device receives a system switching request sent by the second operating system, wherein the second operating system is the operating system currently running in the terminal device.

The rendering module 1020 is used to render the display interface through the first operating system during the process of loading the first display module, and write the display data of the display interface into the shared display buffer area, which is the display buffer area shared between the first operating system and the second operating system.

The display module 1030 is used to obtain display data from the shared display buffer area through the second operating system, and control the screen to display the display interface according to the display data.

In one embodiment, the interface display device 1000 may further include a stop module.

The stopping module is used to stop the first operating system from writing the display data of the rendered display interface into the shared display buffer area when the first display module in the first operating system is loaded completely.

The display module 1030 is also used for the first operating system to control the screen to display the rendered display interface through the first display module.

In one embodiment, the interface display device 1000 may further include a communication module.

The communication module is used for sending a first message from the first operating system to the second operating system when the first display module in the first operating system is loaded completely.

The stopping module is also used for the second operating system to stop acquiring display data from the shared display buffer area according to the first message and enter a dormant state.

In an embodiment of the present application, a shared display cache area is established between the first operating system and the second operating system. When the system is switched, the first operating system to be switched in renders the display interface and writes it into the shared display cache area, and then the second operating system to be switched out obtains the display data from the shared display cache area and controls the screen display. There is no need to wait for the first display module of the first operating system to be loaded before displaying the display interface rendered by the first operating system. This can greatly improve the screen freeze or display discontinuity that occurs when switching operating systems, and achieve continuous, smooth and seamless switching of the interface display.

In one embodiment, the rendering module 1020 is also used for the first operating system to send a start shared display buffer area message to the interface service through the switching service, and the start shared display buffer area message is used to instruct the interface service to write the display data of the rendered display interface into the shared display buffer area.

In one embodiment, the rendering module 1020 is also used to write the display data of the display interface into the shared display cache according to the second message when the first operating system receives the second message sent by the second operating system, and the second message is used to indicate that the second operating system has enabled the shared display cache.

In one embodiment, the stop module is also used to send a stop shared display buffer area message to the interface service through the switching service in the first operating system, and the stop shared display buffer area message is used to instruct the interface service to stop writing the display data of the rendered display interface into the shared display buffer area.

The display module 1030 is also used for the interface service to control the screen to display the rendered display interface through the first display module.

In one embodiment, the loading module 1010 is also used by the first operating system to send a loading instruction to the interface service through the system service. After the interface service receives the loading instruction, it immediately returns a preparation instruction to the system service, and loads the first display module according to the loading instruction. The preparation instruction is used to instruct the system service to render the display interface.

In an embodiment of the present application, multiple services in the first operating system and the second operating system cooperate with each other to control the interface display during the system switching process, so that when the system is switched, the display interface rendered by the first operating system is displayed in advance by the second operating system, and there is no need to wait for the first display module of the first operating system to be loaded before the display interface rendered by the first operating system can be displayed. This can greatly improve the screen freeze or display discontinuity that occurs when the operating system is switched, and achieve continuous, smooth and seamless switching of the interface display.

In one embodiment, the interface display device 1000 includes, in addition to the loading module 1010 , the rendering module 1020 , the display module 1030 , the stop module and the communication module, an operation response module.

The operation response module is used to respond to the application startup operation for the target application through the second operating system when the second operating system detects the application startup operation for the target application, and send a system switching request to the first operating system, wherein the system switching request includes the application identifier of the target application.

The loading module 1010 is further configured to start and load the target application according to the application identifier in the system switching request by the first operating system, and to synchronously load the first display module in the first operating system.

In one embodiment, the rendering module 1020 is further configured to render a display interface corresponding to the target application through the first operating system during the process of starting and loading the target application and synchronously loading the first display module.

In one embodiment, the display module 1030 is also used to control the screen to display an initial transition screen according to the stored interface resources after the second operating system sends a system switching request to the first operating system, and after waiting for a first period of time, obtain display data from the shared display buffer area through the second operating system, and control the screen to display the display interface according to the display data.

In the embodiment of the present application, the first operating system can render the display interface corresponding to the target application according to the launched target application, and the second operating system will first display the display interface when the target application is not launched and loaded, thereby reducing the visual waiting time of the user, preventing the user from having the false impression of system freeze, and achieving continuous, smooth and seamless switching of the interface display. Different launched applications will display different display interfaces, which can improve the richness of the interface and the visual effect of the interface display.

In one embodiment, the rendering module 1020 is also used for the first operating system to render the display interface according to the designed dynamic display style, obtain display data of multiple frames of the display interface, and write the display data of the multiple frames of the display interface into the shared display buffer area.

In one embodiment, the shared display buffer includes a plurality of buffer sub-blocks. The rendering module 1020 is further configured to, by the first operating system, sequentially write the display data of each frame of the display interface into the buffer sub-blocks of the shared display buffer according to the display timing of each frame of the display interface, wherein each buffer sub-block corresponds to the display data of one frame of the display interface.

The display module 1030 is also used for the second operating system to obtain display data of each frame of the display interface from the shared display buffer area one by one, and control the screen to display a display interface with a dynamic display style according to the obtained display data of each frame of the display interface.

In an embodiment of the present application, a shared display cache area is established between the first operating system and the second operating system. When the system is switched, the display interface is rendered by the first operating system to be switched in and written into the shared display cache area. There is no need to pre-set the display data of the dynamic transition display interface in the second operating system, which can reduce the consumption of storage space and facilitate each application in the first operating system to update the display interface according to demand, thereby improving the overall performance of the terminal device.

Figure 11 is a block diagram of a terminal device in an embodiment. As shown in Figure 11, the terminal device 1100 may include one or more of the following components: a processor 1110, a memory 1120 coupled to the processor 1110, wherein the memory 1120 may store one or more computer programs, and the one or more computer programs may be configured to implement the methods described in the above embodiments when executed by one or more processors 1110.

The processor 1110 may include one or more processing cores. The processor 1110 uses various interfaces and lines to connect the various parts of the entire terminal device 1100, and executes various functions and processes data of the terminal device 1100 by running or executing instructions, programs, code sets or instruction sets stored in the memory 1120, and calling data stored in the memory 1120. Optionally, the processor 1110 can be implemented in at least one hardware form of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), and programmable logic array (Programmable Logic Array, PLA). The processor 1110 can integrate one or a combination of a central processing unit (Central Processing Unit, CPU), a graphics processing unit (Graphics Processing Unit, GPU) and a modem. Among them, the CPU mainly processes the operating system, user interface and application programs; the GPU is responsible for rendering and drawing display content; and the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 1110, but may be implemented separately through a communication chip.

The memory 1120 may include a random access memory (RAM) or a read-only memory (ROM). The memory 1120 may be used to store instructions, programs, codes, code sets or instruction sets. The memory 1120 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc. The data storage area may also store data created by the terminal device 1100 during use, etc.

It is understandable that the terminal device 1100 may include more or fewer structural elements than those in the above structural block diagram, for example, a power module, physical buttons, a WiFi (Wireless Fidelity) module, a speaker, a Bluetooth module, a sensor, etc., and is not limited here.

An embodiment of the present application discloses a computer-readable storage medium storing a computer program, wherein the computer program implements the method described in the above embodiment when executed by a processor.

An embodiment of the present application discloses a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, and the computer program can be executed by a processor to implement the methods described in the above embodiments.

Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing related hardware through a computer program, and the program can be stored in a non-volatile computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium can be a disk, an optical disk, a ROM, etc.

As used herein, any reference to memory, storage, database, or other medium may include non-volatile and/or volatile memory. Suitable non-volatile memory may include ROM, programmable ROM (Programmable ROM, PROM), erasable PROM (Erasable PROM, EPROM), electrically erasable PROM (Electrically Erasable PROM, EEPROM), or flash memory. Volatile memory may include random access memory (RAM), which is used as an external cache memory. By way of illustration and not limitation, RAM may be in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (Double Data Rate SDRAM, DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), memory bus direct RAM (RDRAM) and direct memory bus dynamic RAM (DRDRAM).

It should be understood that "one embodiment" or "an embodiment" mentioned throughout the specification means that specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. Those skilled in the art should also be aware that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily required by the present application.

In the various embodiments of the present application, it should be understood that the size of the serial numbers of the above-mentioned processes does not necessarily mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

If the above-mentioned integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-accessible memory. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a memory and includes several requests for a computer device (which can be a personal computer, a server or a network device, etc., specifically a processor in a computer device) to perform some or all of the steps of the above-mentioned methods of various embodiments of the present application.

The above is a detailed introduction to an interface display method, device, terminal device and computer-readable storage medium disclosed in the embodiment of the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method and core ideas of the present application. At the same time, for those of ordinary skill in the art, according to the ideas of the present application, there will be changes in the specific implementation methods and application scopes. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims (14)

1. An interface display method, which is applied to a terminal device, the method comprising:

When a first operating system in the terminal equipment receives a system switching request sent by a second operating system, the first operating system loads a first display module in the first operating system according to the system switching request, wherein the second operating system is an operating system currently running in the foreground in the terminal equipment;

In the process that the first operating system loads the first display module, the first operating system renders a display interface, and display data of the display interface are written into a shared display buffer zone, wherein the shared display buffer zone is a display buffer zone shared between the first operating system and the second operating system;

and the second operating system acquires the display data from the shared display buffer area and controls a screen to display the display interface according to the display data.

2. The method according to claim 1, wherein the method further comprises:

When loading of the first display module in the first operating system is completed, the first operating system stops writing display data of the rendered display interface into the shared display buffer area, and controls the screen to display the rendered display interface through the first display module.

3. The method according to claim 2, wherein the method further comprises:

when the first display module in the first operating system is loaded, the first operating system sends a first message to the second operating system;

and the second operating system stops acquiring display data from the shared display buffer according to the first message and enters a dormant state.

4. The method of claim 2, wherein writing the display data of the display interface to a shared display buffer comprises:

The first operating system sends a message for starting a shared display buffer zone to an interface service through a switching service, wherein the message for starting the shared display buffer zone is used for indicating the interface service to write the display data of the rendered display interface into the shared display buffer zone;

The first operating system stops writing the display data of the rendered display interface into the shared display buffer area, and controls the screen to display the rendered display interface through the first display module, and the method comprises the following steps:

And sending a message for stopping sharing the display buffer area to the interface service through a switching service in the first operating system, wherein the message for stopping sharing the display buffer area is used for indicating the interface service to stop writing display data of the rendered display interface into the shared display buffer area, and controlling the screen to display the rendered display interface through the first display module.

5. The method of claim 4, wherein loading the first display module in the first operating system comprises:

The first operating system sends a loading instruction to an interface service through a system service;

And after the interface service receives the loading instruction, immediately returning a preparation instruction to the system service, loading the first display module according to the loading instruction, wherein the preparation instruction is used for indicating the system service to render the display interface.

6. The method according to claim 1, wherein, before the first operating system loads the first display module in the first operating system according to the system switching request when the first operating system in the terminal device receives the system switching request sent by the second operating system, the method further comprises:

When the second operating system detects an application starting operation aiming at a target application, responding to the application starting operation, and sending a system switching request to the first operating system, wherein the system switching request comprises an application identifier of the target application, and the target application is an application which needs to be run by the first operating system;

the first operating system loads a first display module in the first operating system according to the system switching request, and the method comprises the following steps:

And the first operating system starts and loads the target application according to the application identifier in the system switching request, and synchronously loads a first display module in the first operating system.

7. The method of claim 6, wherein the first operating system rendering a display interface during the loading of the first display module by the first operating system comprises:

and in the process that the first operating system starts and loads the target application and synchronously loads the first display module, the first operating system renders a display interface corresponding to the target application.

8. The method of any one of claims 1 to 7, wherein the first operating system renders a display interface and writes display data of the display interface to a shared display buffer, comprising:

The first operating system renders the display interface according to the designed dynamic display style to obtain display data of a multi-frame display interface, and writes the display data of the multi-frame display interface into a shared display buffer;

the second operating system obtains the display data from the shared display buffer area, and controls a screen to display the display interface according to the display data, and the second operating system comprises:

And the second operating system acquires the display data of each frame of display interface from the shared display buffer area one by one, and controls the screen to display the display interface with the dynamic display mode according to the acquired display data of each frame of display interface.

9. The method of claim 8, wherein the shared display buffer comprises a plurality of buffer sub-blocks, and wherein writing the display data of the multi-frame display interface to the shared display buffer comprises:

and the first operating system sequentially writes the display data of each frame of display interface into the cache sub-blocks of the shared display cache area according to the display time sequence of each frame of display interface, and each cache sub-block corresponds to the display data of one frame of display interface.

10. The method according to any one of claims 1 to 7, wherein writing the display data of the display interface into a shared display buffer comprises:

When the first operating system receives a second message sent by the second operating system, the display data of the display interface are written into a shared display buffer area according to the second message, and the second message is used for representing that the second operating system enables the shared display buffer area.

11. The method of any of claims 1-7, wherein prior to the second operating system obtaining the display data from the shared display cache and controlling a screen to display the display interface based on the display data, the method further comprises:

after the second operating system sends the system switching request to the first operating system, an initial transition picture is displayed according to a stored interface resource control screen;

And after waiting for the first time period, the second operating system executes the steps of acquiring the display data from the shared display buffer area and controlling a screen to display the display interface according to the display data.

12. An interface display device, characterized in that it is applied to a terminal device, said device comprising:

The loading module is used for loading a first display module in a first operating system through the first operating system when the first operating system in the terminal equipment receives a system switching request sent by a second operating system, wherein the second operating system is the operating system currently running in the terminal equipment;

The rendering module is used for rendering the display interface through the first operating system in the process of loading the first display module by the first operating system, and writing display data of the display interface into a shared display buffer area, wherein the shared display buffer area is a display buffer area shared between the first operating system and the second operating system;

and the display module is used for acquiring the display data from the shared display buffer area through the second operating system and controlling a screen to display the display interface according to the display data.

13. A terminal device comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, causes the processor to implement the method of any one of claims 1 to 11.

14. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the method according to any one of claims 1 to 11.